CN111200871B

CN111200871B - Method and communication device for receiving data

Info

Publication number: CN111200871B
Application number: CN201811369613.7A
Authority: CN
Inventors: 王潇涵; 杭海存; 葛士斌; 纪刘榴; 毕晓艳
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-11-16
Filing date: 2018-11-16
Publication date: 2022-02-18
Anticipated expiration: 2038-11-16
Also published as: WO2020098685A1; CN111200871A

Abstract

The application provides a method for receiving data and a communication device. The method comprises the following steps: the terminal equipment receives the PDSCH, and the PDCCH of the PDSCH is scheduled to comprise an indication of an HARQ process number; determining the HARQ process number corresponding to the PDSCH according to the HARQ process number and one or more of the following items: configuration parameters of PDCCH, DMRS port, BWP and network equipment group for sending PDSCH; and processing the data carried by the PDSCH according to the determined HARQ process. Since the network device is invisible to the terminal device, when the terminal device receives multiple PDSCHs, if the HARQ process is determined only according to the HARQ process number, the HARQ process number may correspond to multiple HARQ processes, and an error may occur in processing data. The method provided by the application can accurately determine the HARQ process corresponding to the PDSCH, and is beneficial to improving the data transmission performance.

Description

Method and communication device for receiving data

Technical Field

The present application relates to the field of wireless communications, and more particularly, to a method and a communication apparatus for receiving data.

Background

Coordinated multiple point (CoMP) transmission is a method for solving the inter-cell interference problem and improving the throughput of cell-edge users. In downlink transmission, a network device, such as a Transmission and Reception Point (TRP), may schedule a Physical Downlink Shared Channel (PDSCH) for a terminal device through Downlink Control Information (DCI). The network device may indicate to the terminal device which HARQ process the carried Transport Block (TB) corresponds to through a hybrid automatic repeat request (HARQ) process number (HPN) in the DCI.

However, in some scenarios, such as a non-ideal backhaul (NIB) scenario, a scheme of multi-site scheduling based on multiple DCIs (hereinafter may be referred to as multi-site scheduling based on multiple DCIs) is proposed due to a large communication delay between sites. When multiple stations send DCI to the same terminal device to schedule their respective PDSCHs, because HARQ processes between the stations cannot be coordinated, when the terminal device receives the PDSCHs from the multiple stations, it may not be able to accurately determine the HARQ processes corresponding to the PDSCHs according to the HARQ process numbers. Thus, data transmission performance is affected.

Disclosure of Invention

The application provides a method for receiving data and a communication device, aiming at improving data transmission performance.

In a first aspect, a method of receiving data is provided. The method may be performed by the terminal device, or may be performed by a chip configured in the terminal device. This is not a limitation of the present application.

Specifically, the method comprises the following steps: receiving a PDSCH, wherein the PDSCH is scheduled by a PDCCH, and DCI carried by the PDCCH comprises an indication of an HARQ process number; determining the HARQ process corresponding to the PDSCH according to the HARQ process number and one or more of the following items: configuration parameters of a PDCCH, a network device group transmitting the PDSCH, a port and a bandwidth part (BWP) of a demodulation reference signal (DMRS) indicated in the DCI; and processing the data carried by the PDSCH according to the determined HARQ process.

Based on the above technical solution, the terminal device may determine the HARQ process corresponding to the first PDSCH according to the HARQ process number and one or more of the configuration parameters of the PDCCH, the network device group transmitting the first PDSCH, the DMRS port and the BWP indicated in the first DCI, and may accurately determine the corresponding HARQ process when receiving multiple PDSCHs.

Since the network device is invisible to the terminal device, the terminal device may not know whether it is currently in a single-site service or a multi-site service scenario. When the terminal device receives multiple PDSCHs scheduled by multiple PDCCHs, the value ranges of HARQ process numbers of transport blocks carried by the multiple PDSCHs may be the same. This may be the case when the same HARQ process number corresponds to multiple HARQ processes. If the terminal device determines the HARQ process based only on the HARQ process number, errors in processing the data may be caused. For example, two transport blocks that are not in the same HARQ process are decoded in a combining manner, which results in decoding failure and triggers another retransmission. In fact, two transport blocks of the same HARQ process can be decoded successfully, only because the terminal device misuses one transport block to cause unnecessary retransmission, thereby affecting the data transmission performance.

In the embodiment of the present application, the terminal device determines the HARQ process corresponding to the PDSCH by combining the HARQ process number with one or more of the configuration parameters of the PDCCH, the port group to which the DMRS port belongs, the BWP, and the network device group that transmits the first PDSCH, so that the HARQ process corresponding to the PDSCH can be accurately determined, thereby avoiding errors that may occur in the data processing process of the terminal device, and facilitating improvement of data transmission performance.

With reference to the first aspect, in certain implementations of the first aspect, the configuration parameters of the PDCCH include: PDCCH configuration of PDCCH, BWP downlink dedicated parameters of a bandwidth part to which the PDCCH configuration belongs, BWP downlink parameters to which the PDCCH configuration belongs, serving cell configuration to which the PDCCH configuration belongs, a control resource set of PDCCH, a control resource set group to which the control resource set of PDCCH belongs, a search space set of PDCCH or a search space set group to which the search space set of PDCCH belongs.

The protocol may be predefined to be used in conjunction with the HARQ process number according to some configuration parameter listed above to determine the HARQ process corresponding to the PDSCH. When a certain configuration parameter listed above is defined by the protocol to be used for determining the HARQ process, the configuration parameter may be considered to have a corresponding relationship with the network device group. The terminal device may consider two or more PDCCHs received based on the same configuration parameters as PDCCHs from the same network device group.

With reference to the first aspect, in certain implementations of the first aspect, the DCI includes an indication of a network device group transmitting the PDCCH.

That is, the network device group transmitting the PDCCH may be indicated by adding an indication field of the network device group to the DCI. It should be understood that indicating the network device group by the DCI is only one possible implementation and should not constitute any limitation to the present application.

It should be noted that the above scheme may be applied to a single-site service scenario and may also be applied to a multi-site service scenario, which is not limited in this application. The terminal device may further distinguish different scenarios, and determine the HARQ process corresponding to the PDSCH in different manners.

With reference to the first aspect, in some implementations of the first aspect, the determining a HARQ process corresponding to the PDSCH according to the HARQ process number and one or more of the following: the configuration parameters of the PDCCH, the network equipment group for sending the PDSCH, the port and the BWP of the DMRS indicated in the DCI comprise: and under the condition of receiving the configuration parameters of the plurality of PDCCHs, determining the HARQ process corresponding to the PDSCH according to the HARQ process number and the configuration parameters of the PDCCHs.

That is, the terminal device may determine, according to the number of received configuration parameters of the PDCCH, whether the terminal device is currently in a single-site service or a multi-site service, and may determine, based on the above scheme, an HARQ process corresponding to the PDSCH in a multi-site service scenario; and under the single-site service scene, the HARQ process corresponding to the PDSSCH is determined directly according to the HARQ process number.

With reference to the first aspect, in some implementations of the first aspect, the determining a HARQ process corresponding to the PDSCH according to the HARQ process number and one or more of the following: the configuration parameters of the PDCCH, the network equipment group for sending the PDSCH, the port and the BWP of the DMRS indicated in the DCI comprise: and under the condition that the indication of the port groups of the plurality of DMRSs is received, determining the HARQ process corresponding to the PDSCH according to the HARQ process number and the port group to which the port of the DMRS indicated in the DCI belongs.

That is, the terminal device may determine whether the terminal device is currently in a single-site service or a multi-site service according to the number of the received DMRS port groups, and may determine, based on the above scheme, an HARQ process corresponding to the PDSCH in a multi-site service scenario; and under the single-site service scene, the HARQ process corresponding to the PDSSCH is determined directly according to the HARQ process number.

It should be understood that the specific manner of determining, by the terminal device, whether the terminal device is in the single-site service or multi-site service scenario is not limited to the above list, and the terminal device may also determine, based on other manners, whether the terminal device is currently in the single-site service or multi-site service, and may determine, in the multi-site service scenario, the HARQ process corresponding to the PDSCH according to the HARQ process number and one or more of the following: configuration parameters of PDCCH, a network device group transmitting PDSCH, a port of DMRS indicated in DCI and BWP.

With reference to the first aspect, in some implementations of the first aspect, the DCI includes an indication of a plurality of transport blocks, the PDSCH carries one or more transport blocks, and each transport block corresponds to one HARQ process; and determining the HARQ process corresponding to the PDSCH according to the HARQ process number and one or more of the following items: the configuration parameters of the PDCCH, the network equipment group for sending the PDSCH, the port and the BWP of the DMRS indicated in the DCI comprise: 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 items: configuration parameters of PDCCH, a network device group transmitting PDSCH, a port of DMRS indicated in DCI and BWP.

In the case that the PDSCH carries one or more transport blocks, the HARQ process corresponding to the PDSCH may be one or more, respectively corresponding to one or more transport blocks. The terminal device may further determine, by combining with the indication of the transport block in the DCI, the HARQ process corresponding to each transport block in the PDSCH.

In a second aspect, a communication device is provided, which comprises means for performing the method of any one of the possible implementations of the first aspect.

In a third aspect, a communications apparatus is provided that includes a processor. The processor is coupled to the memory and is operable to execute instructions in the memory to implement the method of any one of the possible implementations of the first aspect. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises a communication interface, the processor being coupled to the communication interface.

In one implementation, the communication device is a terminal device. When the communication device is a terminal device, the communication interface may be a transceiver, or an input/output interface.

In another implementation, the communication device is a chip configured in the terminal equipment. When the communication device is a chip configured in a terminal device, the communication interface may be an input/output interface.

Alternatively, the transceiver may be a transmit-receive circuit. Alternatively, the input/output interface may be an input/output circuit.

In a fourth aspect, a processor is provided, comprising: input circuit, output circuit and 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 method of the first aspect and any one of the possible implementations of the first aspect.

In a specific implementation process, the processor may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a flip-flop, various logic circuits, and the like. The input signal received by the input circuit may be received and input by, for example and without limitation, a receiver, the signal output by the output circuit may be output to and transmitted by a transmitter, for example and without limitation, and the input circuit and the output circuit may be the same circuit that functions as the input circuit and the output circuit, respectively, at different times. The embodiment of the present application does not limit the specific implementation manner of the processor and various circuits.

In a fifth aspect, a processing apparatus is provided that includes a processor and a memory. The processor is configured to read instructions stored in the memory, and may receive a signal via the receiver and transmit a signal via the transmitter to perform the method of the first aspect and any possible implementation manner of the first aspect.

Optionally, the number of the processors is one or more, and the number of the memories is one or more.

Alternatively, the memory may be integral to the processor or provided separately from the processor.

In a specific implementation process, the memory may be a non-transient memory, such as a Read Only Memory (ROM), which may be integrated on the same chip as the processor, or may be separately disposed on different chips.

It will be appreciated that the associated data interaction process, for example, sending the indication information, may be a process of outputting the indication information from the processor, and receiving the capability information may be a process of receiving the input capability information from the processor. In particular, data output by the processor may be output to a transmitter and input data received by the processor may be from a receiver. The transmitter and receiver may be collectively referred to as a transceiver, among others.

The processing device in the fifth aspect may be a chip, the processor may be implemented by hardware or software, and when implemented by hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory, which may be integrated with the processor, located external to the processor, or stand-alone.

In a sixth aspect, there is provided a computer program product comprising: a computer program (also referred to as code, or instructions), which when executed, causes a computer to perform the method of any of the possible implementations of the first aspect and the first aspect described above.

In a seventh aspect, a computer-readable medium is provided, which stores a computer program (which may also be referred to as code or instructions) that, when executed on a computer, causes the computer to perform the method of any one of the above-mentioned first aspect and possible implementation manners of the first aspect.

Drawings

Fig. 1 is a schematic diagram of a communication system suitable for use in a method of transmitting and receiving data according to an embodiment of the present application;

FIG. 2 is a schematic flow chart diagram of a method for transmitting and receiving data provided by an embodiment of the present application;

fig. 3 and fig. 4 are schematic diagrams of different PDCCH configurations corresponding to different HARQ process sets according to an embodiment of the present application;

fig. 5 shows indication bits of transport block #1 and transport block #2 in DCI;

fig. 6 to fig. 10 are schematic diagrams of different PDCCH configurations and different transport blocks corresponding to different HARQ processes according to an embodiment 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 in an embodiment of the present application;

fig. 13 is a schematic structural diagram of a network device according to an embodiment of the present application.

Detailed Description

The technical solution in the present application will be described below with reference to the accompanying drawings.

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a global system for mobile communications (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) system, a General Packet Radio Service (GPRS), a Long Term Evolution (LTE) system, a LTE Frequency Division Duplex (FDD) system, a LTE Time Division Duplex (TDD), a universal mobile telecommunications system (universal mobile telecommunications system, UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication system, a fifth generation (5G) or a new radio NR (NR) system, and the like.

It should be understood that the network device in the communication system may be any device with wireless transceiving function or a chip disposed on the device, and the device includes but is not limited to: evolved Node B (eNB), Radio Network Controller (RNC), Node B (Node B, NB), Base Station Controller (BSC), Base Transceiver Station (BTS), Home Base Station (e.g., Home evolved Node B, or Home Node B, HNB), BaseBand Unit (Base band Unit, BBU), Access Point (AP) in Wireless Fidelity (WIFI) system, Wireless relay Node, Wireless backhaul Node, Transmission Point (TP), or Transmission Reception Point (TRP), etc., and may also be 5G, such as NR, a gbb in the system, or, a transmission Point (TRP or BBU), one or a group (including multiple antenna panels) of Base stations in the 5G system, or may also be a Network panel of gbb or transmission Point, such as a Base band Node (TP), such as a BBU), or a Distributed Unit (DU), etc.

In some deployments, the gNB may include a Centralized Unit (CU) and a DU. The gNB may also include a Radio Unit (RU). The CU implements part of the function of the gNB, and the DU implements part of the function of the gNB, for example, the CU implements Radio Resource Control (RRC) and Packet Data Convergence Protocol (PDCP) layers, and the DU implements Radio Link Control (RLC), Medium Access Control (MAC) and Physical (PHY) layers. Since the information of the RRC layer eventually becomes or is converted from the information of the PHY layer, the higher layer signaling, such as RRC layer signaling or PHCP layer signaling, may also be considered to be transmitted by the DU or by the DU + RU under this architecture. It is to be understood that the network device may be a CU node, or a DU node, or a device including a CU node and a DU node. In addition, the CU may be divided into network devices in the access network RAN, or may be divided into network devices in the core network CN, which is not limited herein.

It should also be understood that terminal equipment in the communication system may also be referred to as User Equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user device. The terminal device in the embodiment of the present application may be a mobile phone (mobile phone), a tablet computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an Augmented Reality (AR) terminal device, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in remote medical treatment (remote medical), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), and the like. The embodiments of the present application do not limit the application scenarios.

To facilitate understanding of the embodiments of the present application, a brief description of several terms referred to in the present application will be given first.

1. HARQ process and HARQ process number: HARQ uses stop-and-wait protocol (stop-and-wait protocol) to transmit data. Taking downlink transmission as an example, after a network device sends a transmission block, it stops to wait for acknowledgement information. The terminal device may perform Acknowledgement (ACK) or Negative Acknowledgement (NACK) on the transport block through the HARQ information. But the terminal device stops waiting for an acknowledgement after each transmission, resulting in a low throughput. The terminal device may use multiple parallel HARQ processes. While one HARQ process is waiting for acknowledgement information, the terminal device may continue to transmit data using another HARQ process.

The HARQ process number is also called HARQ process Identification (ID). Typically, one HARQ process number may be used to indicate one HARQ process. One HARQ process can process one transport block in one time unit. Thus, one HARQ process may correspond to one transport block. The correspondence between the transport block and the HARQ process may be embodied by the correspondence between the transport block and the HARQ process number.

The terminal device may decode the received transport block. For the initially transmitted transport block, the terminal device may decode successfully or fail. The transport blocks that fail decoding may contain useful information, although they cannot be decoded correctly. The terminal device may store it in a buffer (buffer). The cache may be a pool of caches. For example, the buffer may be a HARQ buffer in the prior art. The buffer may be located at the physical layer so that the physical layer performs soft combining and decoding processing on the received data.

The terminal device may obtain the transport block of the same HARQ process from the HARQ buffer when receiving the retransmitted transport block, and combine the transport block with the retransmitted transport block, so as to obtain a transport block more reliable than single decoding. The terminal equipment can decode the combined transmission block, so that the decoding success rate can be improved, and the transmission performance can be improved.

If the decoding is failed, the retransmission can be requested again, and the soft combining and decoding processing can be carried out again.

As for the specific procedure of the soft combining and decoding process, reference may be made to the prior art, and a detailed description thereof is omitted herein.

It can be understood that the transport block corresponding to the HARQ process indicated by the HARQ process number may be an initial transport block or a retransmission transport block. This is not a limitation of the present application.

In addition, the transport blocks successfully decoded may also be stored in the HARQ buffer. This is not a limitation of the present application.

2. A transmission block: may be a block of data from a higher layer. A transport block may include, for example, a data block of a Media Access Control (MAC) Protocol Data Unit (PDU), and the data block may be transmitted over a time unit or may be a unit of HARQ retransmission. By way of example and not limitation, the time unit may be a Transmission Time Interval (TTI).

For example, in NR, a network device may transmit a maximum of two transport blocks per time unit. In multi-station cooperation, each network device may transmit one transport block per time unit.

It should be understood that the above listed number of transport blocks transmitted by the network device in each time unit is only an example, and should not limit the present application in any way. For example, in multi-station cooperation, each network device may also transmit two transport blocks, or more, per time unit. This is not a limitation of the present application.

3. Control resource set (CORESET) and control resource set group (CORESET group): the control resource set may be a resource set for transmitting Downlink Control Information (DCI), and may also be referred to as a control resource region or a physical downlink control channel resource set.

Each control resource set may be a set of Resource Element Groups (REGs). The REG is a basic unit for physical resource allocation of downlink control signaling, and is used to define mapping from the downlink control signaling to Resource Elements (REs). For example, in LTE, one REG consists of 4 REs of non-Reference Signals (RSs) that are contiguous in the frequency domain. It should be understood that REG is only a unit for resource allocation, and should not constitute any limitation to the present application, and the present application does not exclude the definition of a new resource allocation unit to achieve the same or similar functions in future protocols.

For a network device, a control resource set may be understood as a set of resources that may be used to transmit a PDCCH; for the terminal device, the resource corresponding to the search space of the PDCCH of each terminal device belongs to the control resource set. In other words, the network device may determine, from the set of control resources, resources used for transmitting the PDCCH, and the terminal device may determine a search space of the PDCCH according to the set of control resources.

The control resource set may include time-frequency resources, for example, a segment of bandwidth in a frequency domain, or one or more subbands; may be one or more symbols in the time domain; one control resource set may be a continuous or discontinuous resource unit, e.g., a continuous Resource Block (RB) or a discontinuous RB, in the time-frequency domain.

It should be understood that the specific contents of the frequency domain resource, the time domain resource and the time frequency domain resource listed above are only exemplary and should not limit the present application in any way. For example, the RB is an example of a resource unit, and the size of the RB may be a resource defined in the NR protocol, may be a resource defined in a future protocol, or may be replaced with another name. For another example, the control resource set may also be one or more slots, radio frames, subframes, minislots (or sub-slots), or Transmission Time Intervals (TTIs) in the time domain, which is not particularly limited in this embodiment of the present application.

The control resource set may be configured, for example, by a control resource set information element (controlresource information element) in a higher layer parameter. The higher layer parameter may include, for example, an Identifier (ID) of a control resource set, a frequency domain resource, the number of symbols included in a duration (duration), and the like. The present application does not limit the specific parameters for configuring the control resource set.

In addition, the embodiment of the application provides a concept of controlling the resource set group. A control resource set group may include one or more control resource sets. The control resource sets contained in the control resource set group may be configured, for example, by higher layer parameters. For example, the PDCCH may be configured by a PDCCH configuration information element (PDCCH-configuration IE), or may be configured by a ControlResourceSet information element, which is not limited in the present application.

4. Search Space (SS) and search space groups: search space set (search space set) and search space set group: the set of search spaces may be a collection of search spaces described from a physical layer perspective. For the higher layers, the set of search spaces may also be referred to as a search space. In the embodiments of the present application, for the sake of convenience of distinction from the search space described below, it is referred to as a search space set in the present application.

The network device may configure the search space set by a high-level parameter, for example, may be configured by a search space information element (SearchSpace information element). The high-level parameters may include, for example, an identifier of a search space set, an identifier of a control resource set, a period and an offset of a monitoring slot, a monitoring symbol in the slot, an Aggregation Level (AL), and the like. The present application does not limit the specific parameters for configuring the search space.

In addition, the embodiment of the application provides a concept of search space set group. A search space set group may include one or more search space sets. The search space set included in the search space set group may be configured by, for example, a higher layer parameter, for example, a PDCCH-configuration information element, or a SearchSpace information element, which is not limited in the present application.

Here, the SearchSpace information element is a high-level parameter, and the high-level parameter may be considered to be used for configuring the search space set in the physical layer. Hereinafter, the search space may be understood as a set of search spaces of the physical layer when it relates to the configuration of the higher layer parameters. For the sake of brevity, the description of the same or similar cases is omitted hereinafter.

5. Searching a space: the search range of blind detection of the terminal device, or in other words, the set of candidate downlink control channels that the terminal device needs to monitor. The physical resources of the search space may be collectively determined by the set of control resource collections search spaces. For example, the set of control resources may indicate a frequency domain location and a duration of a search space, and the set of search spaces may indicate a starting location of the search space in a time domain, such as a starting time slot. In this embodiment, the terminal device may 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.

6. PDCCH configuration (PDCCH configuration): the network device may configure PDCCH parameters, such as control resource sets, control resource set groups (CORESET groups), search space sets, search space set groups (SS groups), and other parameters that may be used to blindly detect PDCCH, based on each bandwidth part (BWP) in each cell (cell). The PDCCH configuration may be configured, for example, by PDCCH-Config IE in higher layer parameters. The PDCCH-Config IE may include, for example, a control resource set addition status list (control resource set toaddmodlist) and a control resource set release list (control resource set torereleaselist). An identification of one or more control resource sets can be included in each list. The PDCCH-Config IE may further include a search space addition status list (searchSpacesToAddModList) and a search space release list (searchSpacesToReleaseList), for example. The listings may include an identification of one or more search spaces.

Optionally, one or more control resource set groups and/or one or more search space groups may also be indicated in each PDCCH configuration. For example, the control resource set addition status list in the PDCCH-Config IE may include one or more control resource set groups and an identification of the control resource sets contained in each control resource set group. For another example, the search space addition list in the PDCCH-Config IE may include one or more search space groups and an identification of a search space included in each search space group.

One or more search spaces may be determined by the PDCCH configuration. In this embodiment, for a terminal device, PDCCH configuration of a PDCCH may be understood as PDCCH configuration based on which the PDCCH is received, or the terminal device blindly detects the PDCCH in a search space determined by the PDCCH configuration; for a network device, the PDCCH configuration of a PDCCH may be understood as a PDCCH configuration on which the PDCCH is transmitted, or the network device may transmit the PDCCH on a part of resources in a search space determined by the PDCCH configuration.

7. Serving cell configuration (serving cell configuration): may be used to configure a serving cell for the terminal device. The network device may configure the serving cell for the terminal device through a higher-layer parameter, such as a serving cell configuration control element (servingcellconfiguration information element).

In the embodiment of the present application, 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). Each set of BWP downlink parameters may be configured for one BWP, for example, an ID of the BWP may be indicated in the BWP downlink parameters. Each set of BWP upstream parameters may also be configured for one BWP, for example, an ID of the BWP may be indicated in the BWP downstream parameters. Each set of BWP downlink parameters may include a BWP downlink dedicated (DL-dedicated) parameter and a BWP downlink common (DL common) parameter, where the BWP downlink dedicated parameters may specifically include PDCCH configuration and PDSCH configuration. Each set of BWP uplink parameters may include a BWP uplink dedicated parameter (UL dedicated) and a BWP uplink common parameter (UP common), where the BWP uplink dedicated parameter may specifically include a PUCCH configuration and a PUSCH configuration. In addition, one or more CSI reporting configurations may be included in the CSI measurement configuration.

It should be noted that the common parameter may be understood as a cell specific parameter (cell specific) and the dedicated parameter may be understood as a UE-level parameter. The BWP uplink dedicated parameter may be embodied in the NR protocol, and the BWP downlink dedicated parameter may be embodied in the NR protocol.

8. Cell (cell): or serving cell. Is described at a high level from the point of view of a resource management or mobility management or serving unit. The coverage area of each network device may be divided into one or more serving cells, and the serving cells may be considered to be composed of certain frequency domain resources. In the embodiment of the present application, a cell may be replaced with a serving cell or a carrier component carrier (CC, or referred to as a component carrier, a carrier, or the like). In the present embodiment, "cell", "serving cell", and "CC" are used interchangeably, and the intended meaning thereof is consistent when the distinction thereof is not emphasized.

The network device of cell #1 and the network device of cell #2 may be the same network device, which may be, for example, a base station, such as a gNB or a TRP.

The network device of cell #1 and the network device of cell #2 may be different antenna panels of the same base station. That is, cell #1 and cell #2 may be managed by the same base station, have the same baseband processing unit and if processing unit, but have different rf processing units. This is not a particular limitation in the present application.

9. Antenna port (antenna port): referred to as a port for short. A transmit antenna identified by the receiving end device, or a spatially distinguishable transmit antenna. One antenna port may be configured for each virtual antenna, each virtual antenna may be a weighted combination of multiple physical antennas, and each antenna port may correspond to one reference signal port.

In NR, DCI may include an indication field of antenna ports, which may be used to indicate ports of DMRSs. Specifically, the indication field may be an index value, and a correspondence relationship between the index value and a port of the DMRS may be predefined, such as protocol definition. Each index value may correspond to a port of one DMRS or a combination of ports of multiple DMRSs. From the index value, the terminal device may determine a port of the DMRS. Among them, the ports of DMRS may be distinguished by port numbers, for example.

In addition, in order to facilitate understanding of the embodiments of the present application, the following description is made.

First, in the present application, for convenience of description, when numbering is referred to, the numbering may be continued from 0. For example, for N HARQ processes, the value of the HARQ process number may range from 0 to N-1. Of course, the specific implementation is not limited thereto. For example, the numbers may be consecutively numbered from 1. For example, the N process numbers may range from 1 to N. Because the starting values of the numbers are different, the numbers of the HARQ processes corresponding to the same HARQ process are different.

It should be understood that the above descriptions are provided for convenience of describing the technical solutions provided by the embodiments of the present application, and are not intended to limit the scope of the present application.

Second, the first, second and various numerical numbers in the embodiments shown below are merely for convenience of description and are not intended to limit the scope of the embodiments of the present application. For example, different PDCCHs, different PDSCHs, etc. are distinguished.

Third, in the embodiments illustrated below, "pre-acquisition" may include signaling by the network device or pre-defined, e.g., protocol definition. The "predefined" may be implemented by saving a corresponding code, table, or other means that can be used to indicate the relevant information in advance in the device (for example, including the terminal device and the network device), and the present application is not limited to a specific implementation manner thereof.

Fourth, the term "store" referred to in the embodiments of the present application may refer to a store in one or more memories. The one or more memories may be provided separately or integrated in the encoder or decoder, the processor, or the communication device. The one or more memories may also be provided separately, with a portion of the one or more memories being integrated into the decoder, the processor, or the communication device. The type of memory may be any form of storage medium and is not intended to be limiting of the present application.

Fifth, the "protocol" referred to in the embodiments of the present application may refer to a standard protocol in the communication field, and may include, for example, an LTE protocol, an NR protocol, and a related protocol applied in a future communication system, which is not limited in the present application.

Sixth, "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, and c, may represent: a, or, b, or, c, or, a and b, or, a and c, or, b and c, or, a, b and c. Wherein a, b and c may be single or plural respectively.

For the convenience of understanding the embodiments of the present application, a communication system suitable for the method for receiving data provided in the embodiments of the present application will be described in detail below by taking the communication system shown in fig. 1 as an example. Fig. 1 shows a schematic diagram of a communication system 100 suitable for use in a method of receiving data according to an embodiment of the present application. As shown, 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, such as network device #1102 or network device #2103 as shown.

Alternatively, the communication system 100 may include a plurality of network devices, such as network device #1102 and network device #2103 as shown. The network device #1102 and the network device #2103 may be network devices in the same cell or network devices in different cells, which is not limited in this application. The figure shows an example in which network device #1102 and network device #2103 are located in the same cell, for example only.

In communication system 100, network device #1102 and network device #2103 may communicate with each other via a backhaul link, which may be a wired backhaul link (e.g., fiber, copper cable) or a wireless backhaul link (e.g., microwave). Network device #1102 and network device #2103 may cooperate with each other to provide services to terminal device 101. Thus, the terminal apparatus 101 can communicate with the network apparatus #1102 and the network apparatus #2103, respectively, through wireless links.

In addition, one or more of network device #1102 and network device #2103 may also schedule PDSCH for terminal device 101 on one or more CCs, respectively, using carrier aggregation techniques. For example, network device #1102 may schedule PDSCH for terminal device 101 on CC #1 and CC #2, and network device #2103 may schedule PDSCH for terminal device 101 on CC #1 and CC # 3. The CCs scheduled by network device #1102 and network device #2103 may be the same or different, and the present application does not limit this.

Communication delays between cooperating network devices can be divided into ideal backhaul (idealol backhaul) and non-ideal backhaul (non-idealol backhaul). Communication delay between two sites under ideal backhaul can be microsecond level, and can be ignored compared with millisecond level scheduling in NR; communication delay between two stations under non-ideal backhaul can be on the millisecond level, and cannot be ignored compared with the millisecond level scheduling in NR.

Therefore, a multi-site scheduling scheme based on multiple DCIs is proposed. The multi-site scheduling scheme based on the multiple DCIs supports the multiple network devices to schedule the respective PDSCHs for the terminal device through the respective DCIs, so as to perform data transmission, wherein the PDSCHs can be completely overlapped, partially overlapped or not overlapped on time domain and/or frequency domain resources. Optionally, the terminal device independently demodulates the PDSCH scheduled by the terminal device according to the DCI sent by each network device; optionally, the terminal device feeds back HARQ information corresponding to the PDSCH sent by different network devices to the corresponding network devices. That is, the terminal device may receive PDCCHs scrambled by a plurality of cell radio network temporary identifiers (C-RNTIs) and/or Modulation Coding Schemes (MCS) -C-RNTIs, where the PDCCHs may be scheduled to PDSCHs that are completely overlapped, partially overlapped, or non-overlapped in a time domain and/or a frequency domain, respectively. Optionally, the terminal device independently demodulates the PDSCH corresponding thereto according to each PDCCH. Optionally, the terminal device feeds back HARQ information corresponding to the scheduled PDSCH thereof according to the PDCCH attribute.

Since the network device is transparent to the terminal device, the terminal device may receive multiple DCIs, but does not know whether the multiple DCIs are from one network device or multiple network devices. Therefore, such a multi-site scheduling scheme based on multiple DCIs may also be referred to as a multi-DCI scheduling scheme.

It should be understood that multiple DCIs may be completely independent from each other, each containing all the information that may be used to schedule PDSCH. Each DCI may have the same format as DCI transmitted by a network device in a single-site scenario in the related art. There may also be associations between multiple DCIs, for example, a main DCI and a secondary DCI, respectively. However, regardless of the relationship between the plurality of DCIs, each DCI includes an indication of the HARQ process number of the scheduled PDSCH.

For example, the network device #1102 in fig. 1 may transmit PDCCH #1 to the terminal device 101, where the PDCCH #1 may carry DCI #1, the DCI #1 may be used to schedule PDSCH #1 for the terminal device 101, and the DCI #1 may include an indication of a HARQ process number corresponding to a transport block carried in PDSCH # 1. Network device #2103 in fig. 1 may also transmit PDCCH #2 to terminal device 101, where PDCCH #2 may carry DCI #2, where DCI #2 may be used to schedule PDSCH #2 for terminal device 101, and where DCI #2 may include an indication of HARQ process number corresponding to a transport block carried in PDSCH # 2. Since the two network devices are in non-ideal backhaul, the used HARQ processes may not be coordinated, and therefore, the value ranges of the HARQ process numbers used by the two network devices may be the same. This may cause a problem that the same HARQ process number corresponds to two HARQ processes. Since the terminal device cannot distinguish between different transport blocks, the transmission performance of data may be affected.

In view of the above, the present application provides a method for receiving data, which can improve data transmission performance.

The method for receiving data and the communication device provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

It should be noted that the method for receiving data provided in the embodiment of the present application may be applied to a wireless communication system, such as the communication system 100 shown in fig. 1. Communication devices in a wireless communication system may have a wireless communication connection relationship therebetween. As shown, the terminal apparatus 101 shown in fig. 1 can have a wireless communication connection relationship with the network apparatus #1102 and the network apparatus #2103, respectively. The network device #1102 and the network device #2103 may be an ideal backhaul link or a non-ideal backhaul link, which is not limited in this application.

When the backhaul link between the network device #1102 and the network device #2103 is ideal, the network device #1102 and the network device #2103 may be considered to belong to the same network device group, or the network device #1102 and the network device #2103 may be considered to belong to different network device groups. When there is a non-ideal backhaul link between network device #1102 and network device #2103, the network device #1102 and network device #2103 can be considered to belong to different groups of network devices. For example, network devices in the same network device group may perform scheduling through one DCI, or may perform scheduling through one scheduling entity, or may transmit a PDCCH based on the same PDCCH configuration, and the like. It will be appreciated that whether or not the backhaul link between the network devices is ideal is transparent to the network devices. Therefore, this should not constitute any limitation on the applicable scenarios of the methods provided herein.

The first network device group shown below may include, for example, network device #1102 in fig. 1, and the second network device group may correspond to, for example, network device #2103 in fig. 2. For convenience of description, the following describes in detail a method for receiving data provided in an embodiment of the present application, by taking interactions between a first network device group and a terminal device, and a second network device group as an example.

It should be understood that in the embodiments shown below, 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 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. When the first network device group includes only one network device (which may be referred to as a first network device, for example) and the second network device group includes only one network device (which may be referred to as a second network device, for example), the first network device group and the second network device group are the same network device group, and may instead be the same network device; the first network device group and the second network device group are different network device groups, and alternatively, the first network device and the second network device are different network devices.

It should be noted that, when network devices in the same network device group (for example, the first network device group) transmit PDSCH to the terminal device, scheduling may be performed in advance through PDCCH. The network devices in the network device group may negotiate through a backhaul link in advance, and then transmit the PDCCH through a certain network device (e.g., a first network device) therein, so as to schedule the PDSCH for the terminal device. Thus, the network device group may 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, which simply receives the PDSCH from the network device group and does not know whether the PDSCH is from one or more network devices. Or, the terminal device does not know whether the received PDSCH was transmitted by one network device or by a group of network devices. In other words, the PDSCH received by the terminal device from one network device or one network device group may be one PDSCH scheduled based on one PDCCH.

When the network device group includes a plurality of network devices, the sending of the PDSCH to the terminal device by the network device group may mean that the plurality of network devices in the network device group cooperate to send the PDSCH to the terminal device. For example, a plurality of network devices may transmit PDSCH to a terminal device by a diversity transmission or space division multiplexed transmission mode.

Fig. 2 illustrates a schematic flow chart of a method 200 for transmitting and receiving data provided by an embodiment of the present application from a device interaction perspective. As shown, the method 200 may include steps 210 through 240. The steps in method 200 are described in detail below.

In step 210, the terminal device receives a first PDSCH carrying at least one transport block.

For the sake of distinction and illustration, the PDSCH received by the terminal device in step 210 is referred to as the first PDSCH. The first PDSCH may be a PDSCH transmitted 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 group of network devices over a PDCCH. The first PDSCH may be scheduled over the PDCCH, for example, by a first network device in the first network device group. For convenience of distinction and explanation, a PDCCH for scheduling the first PDSCH is referred to as a first PDCCH. DCI may be transmitted on the first PDCCH.

Optionally, before step 210, the method 200 further comprises: in step 220, the terminal device receives a first PDCCH, where the first PDCCH is used for scheduling a first PDSCH. Accordingly, a first network device in the first network device group transmits the first PDCCH.

For the sake of distinction and explanation, the DCI transmitted on the first PDCCH is referred to as a first DCI. The first DCI may include information such as time-frequency resources, antenna ports, and HARQ process numbers of the first PDSCH scheduled by the first DCI.

It should be understood that PDCCH may be used for transmitting DCI. In the present application, scheduling PDSCH through PDCCH and scheduling PDSCH through DCI may be considered equivalent. Alternatively, DCI may be replaced with PDCCH.

One or more transport blocks may be carried in the first PDSCH. For example, in NR, a network device may transmit a maximum of two transport blocks per TTI. That is, a maximum of two transport blocks may be carried in the first PDSCH. The number of transport blocks that can be carried at most in the PDSCH can be indicated, for example, by higher layer signaling, such as RRC messages.

Specifically, if the number of transport blocks that can be carried by the PDSCH at most is indicated to be 1 in the RRC message, the number of transport blocks that can be carried by each PDSCH is 1. In this case, the DCI scheduling the PDSCH may include only configuration information of one transport block. The configuration information of the transport block may include, for example: MCS, New Data Indicator (NDI), and Redundancy Version (RV).

If the number of transport blocks that can be carried by the PDSCH at most is indicated to be 2 in the RRC message, the number of transport blocks that can be carried by the PDSCH may be 1 or 2. At this time, the DCI scheduling the PDSCH may include configuration information of two transport blocks, and a certain transport block may be enabled in a predefined manner. For example, when the MCS in the configuration information of a certain transport block is 26 and the RV is 1, it may implicitly indicate that the transport block is disabled; otherwise, the transport block is an enable transport block. The de-enabled transport block may be understood as a transport block not carrying data, and the enabled transport block may be understood as a transport block carrying data. When a certain transport block in the PDSCH is disabled, the number of transport blocks carried by the PDSCH may be considered to be 1; when a transport block in the PDSCH is not disabled, the number of transport blocks carried by the PDSCH may be considered to be 2.

It should be understood that the specific contents of the configuration information of the transport block listed above are only examples, and should not constitute any limitation to the present application. Moreover, the method for disabling the transport block is only one possible implementation manner by using predefined values of the MCS and RV of the configuration information, such as MCS 26 and RV 1, and should not be limited in any way in this application.

It should also be understood that this should not constitute any limitation to the present application, which does not exclude the possibility of defining in future protocols to transmit more transport blocks per TTI or per time unit.

Optionally, the method further comprises: the terminal device receives a second PDCCH, which is used for scheduling the PDSCH. The second PDCCH may be transmitted by a second network device in a second group of network devices. Optionally, the method further comprises: the terminal device receives the second PDSCH. The second PDSCH may be scheduled by the second network device group.

It is to be understood that the first network device may be a network device in a first network device group, and the second network device may be a network device in a 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. When the terminal device receives the first PDCCH, the second PDCCH, the first PDSCH and the second PDSCH, it cannot be predetermined whether the first PDCCH and the second PDCCH are from the same network device group, or whether the first PDSCH and the second PDSCH are scheduled by the same network device.

It should also be understood that, in the present application, there is no limitation on the sequence of receiving the first PDCCH and the second PDCCH by the terminal device, the first PDCCH and the second PDCCH may be received simultaneously, and the first PDCCH may also be received before or after the second PDCCH. The sequence of receiving the first PDSCH and the second PDSCH by the terminal device is not limited, the first PDSCH and the second PDSCH may be received simultaneously, and the first PDSCH may be received before or after the second PDSCH.

When the terminal device receives multiple PDCCHs or multiple PDSCHs, the HARQ process numbers indicated by the DCI in the multiple PDCCHs may be repeated. Therefore, the HARQ processes 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, a 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.

In step 230, the terminal device determines, according to the HARQ process number and one or more of the following, an HARQ process corresponding to the first PDSCH: configuration parameters of the first PDCCH, a network device group transmitting the first PDSCH, a port of the DMRS indicated in the first DCI, and BWP.

As previously described, one or more transport blocks may be carried in the first PDSCH, each transport block may correspond to a HARQ process. Therefore, the HARQ process number indicated in the first DCI may be used to indicate a HARQ process corresponding to one or more transport blocks. That is, the HARQ process corresponding to the first PDSCH may be one HARQ process or may be multiple HARQ processes.

For convenience of understanding, it is assumed that one transport block is carried in the first PDSCH, and a detailed description is given of a specific process of the terminal device for determining the HARQ process corresponding to the first PDSCH. For example, the terminal device may determine that at most one transport block is carried in the first PDSCH according to a previously received RRC message. In this case, the HARQ process corresponding to the first PDSCH, that is, the HARQ process corresponding to the transport block carried in the first PDSCH.

In this embodiment, the terminal device may determine the HARQ process by combining the HARQ process number indicated in the first DCI with one or more of the following: configuration parameters of the first PDCCH, a network device group transmitting the first PDSCH, a port of the DMRS indicated in the first DCI, and BWP.

For ease of understanding and explanation, the concept of a HARQ process set (HARQ process set) is introduced in this application. The set of HARQ processes may correspond to one or more of: configuration parameters of PDCCH, port group of DMRS, BWP, network device (or network device group).

That is, the terminal device may determine the HARQ process set according to one or more of configuration parameters of a PDCCH on which the first PDCCH is received, a network device (or a network device group) that transmits the first PDSCH, a port group to which a port of the DMRS indicated in the first DCI belongs, and BWP, and may further determine the HARQ process from the HARQ process set according to the HARQ process number indicated in the first DCI.

It should be understood that, for convenience of understanding only, the specific process of determining the HARQ process corresponding to the first PDSCH by the terminal device is described by introducing the HARQ process set. This should not be construed as limiting the application in any way. For example, the terminal device may determine the HARQ process corresponding to the first PDSCH directly according to the HARQ process number and one or more of the following: the method comprises the steps that configuration parameters of a PDCCH, a port group to which a DMRS port belongs, a BWP and a network equipment group for sending a first PDSCH are set; or, the terminal device may also determine, according to the HARQ process number, one or more corresponding HARQ processes, and then determine, according to one or more of the following items, an HARQ process corresponding to the first PDSCH from the one or more HARQ processes: the configuration parameters of the PDCCH, the port group to which the DMRS port belongs, the BWP and the network equipment group which sends the first PDSCH.

In other words, the present application does not limit the specific process and the execution sequence for determining the HARQ process corresponding to the first PDSCH by the terminal device, 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 items: the configuration parameters of the PDCCH, the port group to which the DMRS port belongs, the BWP, and the network device group transmitting the first PDSCH all fall within the scope of the present application. Hereinafter, the description of the same or similar cases will be omitted for the sake of brevity.

The following describes the specific process of determining the HARQ process by the terminal device in detail.

Optionally, step 230 specifically includes: and the terminal equipment 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 a time-frequency resource of the first PDCCH, and the like. Specifically, the configuration parameters of the first PDCCH may include one or more of the following: the PDCCH configuration of the first PDCCH, the bandwidth portion BWP downlink dedicated parameter to which the first PDCCH configuration belongs, the BWP downlink parameter to which the first PDCCH configuration belongs, the serving cell configuration to which the first 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 group to which the search space set of the first PDCCH belongs.

In this embodiment, the terminal device may determine the HARQ process corresponding to the first PDSCH according to the HARQ process number and some of the configuration parameters of the first PDCCH listed above.

As an embodiment, the terminal device may determine, according to the HARQ process number and the PDCCH configuration of the first PDCCH, the HARQ process corresponding to the first PDSCH.

In particular, the PDCCH configuration may be used to determine one or more search spaces. For a terminal device, the PDCCH configuration of a first PDCCH may be understood as a PDCCH configuration on which the first PDCCH is received, or the terminal device may blindly detect the first PDCCH in a search space determined by the PDCCH configuration; for the network device, the PDCCH configuration of the first PDCCH may be understood as the PDCCH configuration on which the first PDCCH is transmitted, or the network device may transmit the first PDCCH on a part of resources in the search space determined by the PDCCH configuration.

In other words, in the present embodiment, 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. For example, HARQ process set #1 may correspond to PDCCH configuration #1, and HARQ process set #2 may correspond to PDCCH configuration # 2.

The terminal device may store the transport blocks carried in the received PDSCH in the corresponding HARQ buffer according to the PDCCH configuration based on which the PDCCH that schedules the PDSCH is based.

In a possible implementation manner, the terminal device may divide the HARQ buffer into one or more regions, where each region corresponds to one PDCCH configuration. For example, the storage space occupied by the HARQ buffers of different areas may be different, and the storage space occupied by the different HARQ buffers does not overlap. In other words, different HARQ process sets occupy different areas in the HARQ buffer. It should be understood that the HARQ processes contained in different sets of HARQ processes are each based on different PDCCH schedules.

Fig. 3 shows an example of different PDCCH configurations corresponding to different HARQ buffer areas. As shown, PDCCH configuration #1 may correspond to region #1 in the HARQ buffer, and PDCCH configuration #2 may correspond to region #2 in the HARQ buffer. It is to be understood that the HARQ process in region #1 in the HARQ buffer may belong to HARQ process set #1, and the HARQ process in region #2 in the HARQ buffer may belong to HARQ process set # 2.

It should be understood that fig. 3 is only an example, and shows that PDCCH configuration #1 and PDCCH configuration #2 respectively correspond to different HARQ buffer areas, but this should not limit the present application in any way. The PDCCH configurations are not limited to two, and the PDCCH configurations are not limited to be distinguished by different numbers, which is not limited in this application.

The terminal device may determine, according to the PDCCH configuration based on which the first PDCCH is received, a corresponding HARQ buffer region, and may further determine, according to the HARQ process number indicated in the first DCI, an HARQ process corresponding to the first PDSCH in the HARQ buffer region.

In another possible implementation manner, the terminal device may renumber HARQ processes corresponding to different HARQ process sets according to a preset rule. To distinguish from the HARQ process number indicated in DCI, the number of HARQ processes in different HARQ process sets is referred to herein as the local number of HARQ processes. 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, the local numbers of HARQ processes contained in different sets of HARQ processes are different and not repeated.

Fig. 4 shows an example of local numbers corresponding to different HARQ processes for different PDCCH configurations. For example, HARQ process numbers indicated in two pieces of DCI received by the terminal device are all 0 to N-1, but the two pieces of DCI are received based on PDCCH configuration #1 and PDCCH configuration #2, respectively. HARQ process numbers indicated in DCI received based on PDCCH configuration #1 may correspond to local numbers 0 to N-1, and HARQ process numbers indicated in DCI received based on PDCCH configuration #2 may correspond to local numbers N to 2N-1. It is to be understood that HARQ processes locally numbered 0 to N-1 may belong to HARQ process set #1, and HARQ processes locally numbered N to 2N-1 may belong to HARQ process set # 2.

That is, when the HARQ process number indicated in the DCI received based on PDCCH configuration #1 is N (N is greater than or equal to 0 and less than or equal to N-1, and N is an integer), the corresponding local number may also be N; when the HARQ process number indicated in the DCI received based on PDCCH configuration #2 is N, the corresponding local number may be N + N.

The terminal device may determine, according to the PDCCH configuration based on the first PDCCH and the HARQ process number indicated in the first DCI, the local number of the HARQ process corresponding to the first PDSCH, and may further determine the HARQ process corresponding to the first PDSCH.

It should be understood that, here, only by way of example, two PDCCH configurations are used to illustrate the correspondence between different PDCCH configurations and local numbers of different HARQ processes, but this should not limit the present application in any way. For example, when the PDCCH is configured more, the terminal device may still determine the local number of the HARQ process according to a preset rule.

In one possible design, each network device group may correspond to one PDCCH configuration. That is, the protocol may be predefined, and two or more PDCCH configurations may be configured in the same serving cell configuration, and each PDCCH configuration may correspond to one network device group. Network devices in the network device group may transmit the PDCCH based on the corresponding PDCCH configuration.

It should be understood that the correspondence between the network device groups and the PDCCH configuration may be determined by pre-negotiation between the network device groups. For example, the network device group may negotiate and configure a correspondence between the network device group and the PDCCH configuration through the backhaul link. The present application does not limit the correspondence between the network device group and the PDCCH configuration and the configuration manner of the correspondence.

It should also be understood that one network device group may also have two or more PDCCH configurations, and PDCCH configurations corresponding to different network device groups are different, and the number of PDCCH configurations corresponding to one network device group is not limited in the present application.

It should also be understood that the above description, with reference to the drawings, describes a method for determining a HARQ process set according to a PDCCH configuration, but this should not limit the present application in any way. Those skilled in the art may also determine the HARQ process set according to the PDCCH configuration in other possible ways based on the same concept. The specific manner for determining the HARQ process set corresponding to the first PDSCH according to the PDCCH configuration is not limited in the present application. In addition, the HARQ process set is defined only for ease of understanding, and should not be construed as limiting the present application in any way. Those skilled in the art may also not determine the HARQ process set, and determine the HARQ process corresponding to the first PDSCH directly according to the HARQ process number and the PDCCH configuration.

Furthermore, the above description with reference to fig. 3 and fig. 4 is only an example, and in the various embodiments shown below, the above PDCCH configuration may also be replaced by BWP downlink dedicated parameters, BWP downlink parameters, serving cell configuration, control resource sets, control resource set groups, search space sets, search space set groups, DMRS port groups, BWPs, or network device groups, respectively.

As another embodiment, 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 may configure the serving cell for the terminal device via higher layer parameters, such as RRC messages. A serving cell configuration may include a BWP downlink parameter, which may include BWP downlink specific parameters, each of which may include a PDCCH configuration. In this case, the HARQ process set may correspond to BWP downlink dedicated parameters.

It should be noted that, in this embodiment, a BWP downlink dedicated parameter may include one or more parameters, or may also be referred to as a set of parameters, and is not necessarily limited to only one parameter. The BWP downlink specific parameters may be independent of each other. Alternatively, each BWP downlink specific parameter may be used independently of other BWP downlink specific parameters.

The corresponding relationship between the HARQ process set and the BWP downlink dedicated parameters is similar to the above-described corresponding relationship between the HARQ process set and the PDCCH configuration. For example, HARQ process set #1 may correspond to BWP downlink dedicated parameters #1, and HARQ process set #2 may correspond to BWP downlink dedicated parameters # 2.

The terminal device may determine, according to the BWP downlink dedicated parameter to which the PDCCH configuration based on the first PDCCH belongs, an HARQ process set corresponding to the BWP downlink dedicated parameter, and further determine, according to the HARQ process number indicated in the first DCI, an HARQ process corresponding to the first PDSCH. Since 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 belongs is similar to the specific process of the terminal device determining the HARQ process corresponding to the first PDSCH according to the HARQ process number and the PDCCH configuration of the first PDCCH, further description is omitted here for brevity.

In one possible design, each network device group may correspond to a BWP downstream specific parameter. That is, the protocol may be predefined to configure two or more BWP downlink specific parameters in the same serving cell configuration, and each BWP downlink specific parameter may correspond to one 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.

It should be understood that the correspondence between the network device groups and the BWP downlink dedicated parameters may be determined by pre-negotiation between the network device groups. The present application does not limit the correspondence between the network device group and the BWP downlink dedicated parameter and the configuration manner of the correspondence.

It should also be understood that one network device group may correspond to two or more BWP downlink dedicated parameters, and the BWP downlink dedicated parameters corresponding to different network device groups are different, and the number of the BWP downlink dedicated parameters corresponding to one network device group is not limited in the present application.

As another embodiment, the terminal device may determine, according to the HARQ process number and the BWP downlink parameter to which the PDCCH configuration of the first PDCCH belongs, the HARQ process corresponding to the first PDSCH.

The network device may configure the serving cell for the terminal device via the high-level parameters. One serving cell configuration may include one or more BWP downlink parameters, each BWP downlink parameter may include one BWP downlink specific parameter, and each BWP downlink specific parameter may include one PDCCH configuration. In this case, the HARQ process set may correspond to BWP downlink parameters.

It should be noted that, in this embodiment, a BWP downlink parameter may include one or more parameters, or may also be referred to as a set of parameters, and is not necessarily limited to only one parameter. The BWP downlink parameters may be independent of each other. Alternatively, each BWP downlink parameter may be used independently of other BWP downlink parameters.

The corresponding relationship between the HARQ process set and the BWP downlink parameters is similar to the above-mentioned corresponding relationship between the HARQ process set and the BWP downlink dedicated parameters. For example, HARQ process set #1 may correspond to BWP downlink parameters #1, and HARQ process set #2 may correspond to BWP downlink parameters # 2.

The terminal device may determine, according to the BWP downlink parameter to which the PDCCH configuration based on the first PDCCH belongs, an HARQ process set corresponding to the BWP downlink parameter, and further determine, according to the HARQ process number indicated in the first DCI, an HARQ process corresponding to the first PDSCH. Since 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 parameter to which the PDCCH configuration of the first PDCCH belongs is similar to the specific process of the terminal device determining the HARQ process corresponding to the first PDSCH according to the HARQ process number and the PDCCH configuration of the first PDCCH, details are not repeated here for brevity.

In one possible design, each network device group may correspond to a BWP downlink parameter. That is, the protocol may be predefined, and two or more BWP downlink parameters may be configured in the same serving cell configuration, and each BWP downlink parameter may correspond to one 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 parameters.

It should be understood that the correspondence between the network device groups and the BWP downlink parameters may be determined by pre-negotiation between the network device groups. The present application does not limit the correspondence between the network device group and the BWP downlink dedicated parameter and the configuration manner of the correspondence.

It should also be understood that one network device group may also correspond to two or more BWP downlink parameters, and the BWP downlink parameters corresponding to different network device groups are different, and the number of the BWP downlink parameters corresponding to one network device group is not limited in the present application.

As another embodiment, the terminal device may determine, according to the HARQ process number and the serving cell configuration to which the PDCCH configuration of the first PDCCH belongs, the HARQ process corresponding to the first PDSCH.

The network device may configure the serving cell for the terminal device via the high-level parameters. In this embodiment, the protocol may be predefined, and each terminal device may configure a plurality of serving cells. For example, the first network device group and the second network device group may be located in different serving cells. Each serving cell configuration may include one BWP downlink parameter, each BWP downlink parameter may include one BWP downlink dedicated parameter, and each BWP downlink dedicated parameter may include one PDCCH configuration. In this case, the HARQ process set may correspond to the serving cell configuration.

The corresponding relationship between the HARQ process set and the BWP downlink parameters is similar to the above-described corresponding relationship between the HARQ process set and the BWP downlink parameters. For example, HARQ process set #1 may correspond to serving cell configuration #1, and HARQ process set #2 may correspond to serving cell configuration # 2.

The terminal device may determine, according to the serving cell configuration to which the PDCCH configuration based on the first PDCCH belongs, an HARQ process set corresponding to the serving cell configuration, and then determine, according to the HARQ process number indicated in the first DCI, an HARQ process corresponding to the first PDSCH. Since the specific process of determining the HARQ process corresponding to the first PDSCH by the terminal device according to the HARQ process number and the serving cell configuration to which the PDCCH configuration of the first PDCCH belongs is similar to the specific process of determining the HARQ process corresponding to the first PDSCH by the terminal device according to the HARQ process number and the PDCCH configuration of the first PDCCH, details are not repeated here for brevity.

In one possible design, each network device group may correspond to a serving cell configuration. That is, the network device groups in different serving cells may transmit PDCCH based on different serving cell configurations.

It should be understood that the correspondence between the network device groups and the serving cell configuration may be determined by pre-negotiation between the network device groups. The present application does not limit the correspondence between the network device group and the serving cell configuration and the configuration manner of the correspondence.

As another embodiment, 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.

As previously described, the set of control resources can be used to determine a search space for PDCCH. For a terminal device, a control resource set of a first PDCCH may be understood as a control resource set on which the first PDCCH is received, or the terminal device may blindly detect the first PDCCH in a search space determined by the control resource set; for a network device, the control resource set of a first PDCCH may be understood as the control resource set on which the first PDCCH is transmitted, or the network device may transmit the first PDCCH on a portion of resources in a search space determined by the control resource set. Network devices that transmit PDCCH on the same set of control resources may be considered to be the same network device or to belong to the same network device group.

In this embodiment, the set of HARQ processes may correspond to the set of control resources. For example, HARQ process set #1 may correspond to control resource set #1, and 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 based 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. Since the specific process of the terminal device determining the HARQ process corresponding to the first PDSCH according to the HARQ process number and the control resource set of the first PDCCH is similar to the specific process of the terminal device determining the HARQ process corresponding to the first PDSCH according to the HARQ process number and the PDCCH configuration of the first PDCCH, details are not repeated here for brevity.

In one possible design, multiple network device groups may transmit PDCCH based on the same PDCCH configuration, different sets of control resources. Each network device group may correspond to a set of control resources. Optionally, the network device groups transmitting the PDCCH based on the same PDCCH configuration belong to the same cell. Optionally, the network device groups transmitting the PDCCH based on the same PDCCH configuration belong to different cells.

It should be appreciated that the correspondence between the network device groups and the set of control resources may be determined by pre-negotiation between the network device groups. The present application does not limit the correspondence between the network device group and the control resource set and the configuration manner of the correspondence.

As another embodiment, 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.

In this embodiment, 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 referred to as one control resource set group. For example, HARQ process set #1 may correspond to control resource set group #1, and 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 based 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 specific process of the terminal device determining 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 is similar to the specific process of the terminal device determining the HARQ process corresponding to the first PDSCH according to the HARQ process number and the PDCCH configuration of the first PDCCH, details are not repeated here for brevity.

In one possible design, multiple network device groups may transmit PDCCH based on the same PDCCH configuration, different sets of control resource sets. Each network device group may correspond to a control resource set group. Optionally, the network device groups transmitting the PDCCH based on the same PDCCH configuration belong to the same cell. Optionally, the network device groups transmitting the PDCCH based on the same PDCCH configuration belong to different cells.

It should be appreciated that the correspondence between the network device groups and the control resource set groups may be determined by pre-negotiation between the network device groups. The present application does not limit the correspondence between the network device group and the control resource set group and the configuration manner of the correspondence.

As another embodiment, 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.

As previously mentioned, a set of search spaces may be a collection of search spaces. A set of search spaces may include one or more search spaces. For the terminal device, the search space set of the first PDCCH may be understood as a search space set on which the first PDCCH is received, or the terminal device may blindly detect the first PDCCH in a search space included in the search space set; for the network device, the search space set of the first PDCCH may be understood as a search space set on which the first PDCCH is transmitted, or the network device may transmit the first PDCCH on a certain search space included in the search space set. Network devices that transmit PDCCH based on the same set of search spaces may be considered to be the same network device or belong to the same network device group.

In this embodiment, the set of HARQ processes may correspond to a set of search spaces. For example, HARQ process set #1 may correspond to search space set #1, and 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 based 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. Since the specific process of the terminal device determining the HARQ process corresponding to the first PDSCH according to the HARQ process number and the search space set of the first PDCCH is similar to the specific process of the terminal device determining the HARQ process corresponding to the first PDSCH according to the HARQ process number and the PDCCH configuration of the first PDCCH, details are not repeated here for brevity.

In one possible design, multiple network device groups may transmit PDCCH based on the same PDCCH configuration, different search space sets. Each network device group may correspond to a set of search spaces. Optionally, the network device groups transmitting the PDCCH based on the same PDCCH configuration belong to the same cell. Optionally, the network device groups transmitting the PDCCH based on the same PDCCH configuration belong to different cells.

It should be appreciated that the correspondence of the network device groups to the set of search spaces may be determined by pre-negotiation between the network device groups. The corresponding relationship between the network device group and the search space set and the configuration mode of the corresponding relationship are not limited in the present application.

As another embodiment, 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.

In this embodiment, 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 referred to as a search space set group. For example, HARQ process set #1 may correspond to search space set group #1 and 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 based 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 specific process of the terminal device determining 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 is similar to the specific process of the terminal device determining the HARQ process corresponding to the first PDSCH according to the HARQ process number and the PDCCH configuration of the first PDCCH, details are not repeated here for brevity.

In one possible design, multiple network devices or groups of network devices may transmit PDCCH based on the same PDCCH configuration, different sets of search space sets. Each network device or group of network devices may correspond to a search space set group. Optionally, the network devices transmitting the PDCCH based on the same PDCCH configuration belong to the same cell. Optionally, the network devices transmitting the PDCCH based on the same PDCCH configuration belong to different cells.

It should be appreciated that the correspondence between the network device groups and the search space set groups may be determined by pre-negotiation between the network device groups. The corresponding relationship between the network device group and the search space set group and the configuration mode of the corresponding relationship are not limited in the present application.

It should also be understood that the correspondence between the HARQ process set and the configuration parameters of the PDCCH listed above is only an example, and should not constitute any limitation to the present application. The number of network device groups, the number of network devices in a network device 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, the number of BWP downlink dedicated parameters in the same BWP downlink parameters, the number of PDCCH configurations in the same BWP downlink dedicated parameters, 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 in the present application.

Optionally, step 230 specifically includes: and the terminal equipment 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.

Specifically, when multiple network device groups serve the same terminal device, if the same DMRS ports are used, interference may be caused between the network device groups; if the DMRS ports in the same port group are used, channel estimation of the terminal device may be inaccurate, and signal reception quality may be degraded. In order to avoid different network device groups using the same port group when serving the same terminal device, different network device groups may be generally restricted from using DMRS ports in different port groups to serve the same terminal device. It should be understood that each network device group is not limited to using one port group. One network device group may also correspond to two or more port groups, and ports in port groups corresponding to different network device groups are not repeated.

It should be understood that DMRS ports in different port groups are completely different. Or, there is no repetition between DMRS ports in different port groups. The DMRS ports included in each port group may be predefined, such as protocol definition, or may be indicated by a network device, such as a network device through higher layer signaling, such as RRC message.

The first network device may indicate a DMRS port of the scheduled first PDSCH in the first DCI. The terminal device may determine, from the received first DCI, a DMRS port for demodulating the first PDSCH to demodulate the received first PDSCH.

In this embodiment, the HARQ process set may correspond to a port group. For example, HARQ process set #1 may correspond to port group #1, and HARQ process set #2 may correspond to port group # 2.

The terminal device may determine the port group to which the terminal device belongs according to the port indicated in the first DCI and used for demodulating the DMRS of the first PDSCH, and further 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.

It should be understood that the correspondence between the network device groups and the port groups of the DMRS may be determined by pre-negotiation between the network device groups. The present application does not limit the correspondence between the network device group and the port group of the DMRS and the configuration manner of the correspondence.

It is also understood that DMRS and DMRS ports may be corresponding. Each DMRS may correspond to one DMRS port. In the present application, the meaning of DMRS ports and DMRS ports are expressed in agreement.

Optionally, step 230 specifically includes: and the terminal equipment determines the HARQ process corresponding to the first PDSCH according to the HARQ process number and the BWP indicated in the first DCI.

As mentioned above, the network device may configure the serving cell for the terminal device through the high-level parameters. One serving cell configuration may include one or more BWP downlink parameters. Each BWP downlink parameter may correspond to a BWP. The network device may indicate the ID of the BWP through DCI, for example, through a BWP indication (bandwidth part indicator) field in the DCI. The BWP indicated by the DCI may be understood as an active BWP. The BWP indicated by the DCI may be used for data transmission by the terminal device, e.g., receiving PDSCH.

In this case, the HARQ process set may correspond to BWP. The corresponding relationship between the HARQ process set and the BWP is similar to the above-described corresponding relationship between the HARQ process set and the BWP downlink parameters. For example, HARQ process set #1 may correspond to BWP #1, and HARQ process set #2 may correspond to BWP # 2.

The terminal device may determine, according to an ID of the BWP indicated in the first DCI in the first PDCCH, an HARQ process set corresponding to the BWP, and further determine, according to the HARQ process number indicated in the first DCI, an HARQ process corresponding to the first PDSCH. Since 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 indicated by the first DCI is similar to the specific process of the terminal device determining the HARQ process corresponding to the first PDSCH according to the HARQ process number and the PDCCH configuration of the first PDCCH, details are not repeated here for brevity.

In one possible design, each network device group may correspond to a BWP. Alternatively, each network device group may activate a BWP. The correspondence between the network device group and the BWP may be expressed as a correspondence between the network device group and the BWP downlink parameters, for example. That is, the protocol may be predefined, and multiple or more BWP downlink parameters may be configured in the same serving cell configuration, and each BWP downlink parameter may correspond to one network device group. The network devices in the network device group may indicate (or activate) the corresponding BWP through the DCI based on the corresponding BWP downlink parameter.

It should be understood that the correspondence between the network device groups and the BWP may be determined by pre-negotiation between the network device groups. The correspondence relationship between the network device group and the BWP and the configuration method of the correspondence relationship are not limited in the present application.

It should also be understood that one network device group may correspond to two or more BWPs, and the BWPs corresponding to different network device groups do not overlap, and the number of BWPs corresponding to one network device group is not limited in the present application.

Optionally, step 230 specifically includes: and the terminal equipment determines the HARQ process corresponding to the first PDSCH according to the HARQ process number and the network equipment group for sending the first PDSCH.

As mentioned above, the terminal device does not know whether the first PDSCH is from a network device or a network device group when it receives the first PDSCH. When the network device group includes one network device, the indication of the network device group may be, for example, an identifier of the network device, or an identifier of the network device group; when the network device group includes a plurality of network devices, the indication of the network device group may be, for example, an identification of the network device group. The present application is not limited to the specific manner of indicating the network device group. For example, the indication may be by identification, or may be indicated by other information that may be used to distinguish different groups of network devices.

In this embodiment, the set of HARQ processes may correspond to a group of network devices. For example, HARQ process set #1 may correspond to network device group #1 and HARQ process set #2 may correspond to network device group # 2. The terminal device may determine a corresponding HARQ process set according to the network device that sends the first PDSCH, and further determine a HARQ process corresponding to the first PDSCH according to the HARQ process number indicated in the first DCI.

In one possible design, the group of network devices transmitting the first PDSCH may be indicated by the first DCI. For example, a field indicating a network device group is added in the first DCI to indicate the network device group scheduling the first PDSCH. The terminal device may determine, according to the network device group indicated by the first DCI, a network device group that transmits the first PDSCH, and further determine a corresponding HARQ process set. The terminal device may further determine, according to the HARQ process number indicated in the first DCI, an HARQ process corresponding to the first PDSCH.

It should be understood that the group of network devices transmitting the first PDSCH may be indicated in other ways as well. The present application does not limit the specific manner of indicating the network device group transmitting the first PDSCH.

It should be understood that the above list of one or more of the configuration parameters according to the HARQ process and the PDCCH, the DMRS port, the BWP, and the network device group transmitting the PDSCH is only a few possible implementations for determining the HARQ process corresponding to the first PDSCH, and should not constitute any limitation to the present application. For example, the terminal device may further combine the HARQ process with a DCI type or a reception beam group, etc. to determine the HARQ process corresponding to the first PDSCH.

Optionally, step 230 specifically includes: and the terminal equipment determines the HARQ process corresponding to the first PDSCH according to the HARQ process number and the type of the first DCI.

The DCI type may be classified into a main DCI and a secondary DCI based on a difference in content included in the DCI. The PDCCH for transmitting the main DCI may be referred to as a main PDCCH, corresponding to the main DCI. Corresponding to the secondary DCI, a PDCCH for transmitting the secondary DCI may be referred to as a secondary PDCCH. The information included in the secondary DCI may be a subset of the information included in the primary DCI. Alternatively, the secondary DCI may include only the indication field included in the partial primary DCI, i.e., the primary DCI may include more indication information than the secondary DCI. Alternatively, the primary DCI and the secondary DCI may contain different information. For example, the primary DCI may be a DCI containing a certain one or more specific parameters. Wherein the specific parameter may comprise, for example, at least one of: a carrier indicator (carrier indicator), a partial bandwidth indicator (bandwidth part indicator), a rate matching indicator (rate matching indicator), a zero power channel state information reference signal trigger (ZP CSI-RS trigger); accordingly, the secondary DCI may be a DCI that does not include any one of the specific parameters described above. For another example, the secondary DCI may be a DCI comprising one or more of: resource allocation (resource allocation), MCS, RV, NDI, HARQ process number, etc. It should be understood that the information included in the primary DCI and the secondary DCI listed above is only an example, and the information included in the primary DCI and the secondary DCI should not be limited in any way. The protocol may predefine specific contents contained in the primary DCI and the secondary DCI. When the content included in the PDCCH that is blind-detected by the terminal device belongs to the category of the content included in the primary DCI, the PDCCH may be considered as the primary PDCCH.

In this embodiment, the primary DCI and the secondary DCI may correspond to one HARQ process set, respectively. For example, the main DCI corresponds to HARQ process set #1, and the auxiliary DCI corresponds to HARQ process set # 2.

The terminal device may determine, according to information included in the received first DCI, whether the first DCI is a main DCI or an auxiliary DCI, and further determine a corresponding HARQ process set. Thereafter, the terminal device may further determine, according to the HARQ process number, a HARQ process corresponding to the first PDSCH from the HARQ process set.

Optionally, step 230 specifically includes: and the terminal equipment determines the HARQ process corresponding to the first PDSCH according to the HARQ process number and the receiving beam group of the first PDSCH.

In this embodiment, the receiving beams of the terminal device may be grouped, and the PDCCH and the PDSCH from the same network device or the same network device group may be received through the receiving beams in the same receiving beam group. Thus, one reception beam group may correspond to one HARQ process set. For example, receive beam group #1 may correspond to HARQ process set #1 and receive beam group #2 may correspond to HARQ process set # 2.

The network device may carry a Transmission Configuration Indication (TCI) in the first DCI, and indicate a selected TCI state (TCI state) through the TCI. An identification of reference signal resources used to determine a receive beam for receiving the first PDSCH may be included in each TCI state. In other words, the identity of the reference signal resource has a correspondence with the receive beam. Thus, in one implementation, grouping the receive beams may also be accomplished by grouping the reference signal resources.

In particular, the network device may signal a plurality of reference signal resource groups, each reference signal resource group comprising one or more reference signal resources. The terminal device may determine a receive 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 receive beam corresponding to the reference signal resource.

In general, the receive beams in the same receive beam group may be arranged in the same antenna panel (panel). Thus, in another implementation, an indication field may be added to the existing TCI state to distinguish between different receive beam groups.

For example, an indication field related to the antenna panel may be added to the TCI status, such as "panel 1" for antenna panel 1 and "panel 2" for antenna panel 2. The network device may indicate the available TCI status through the TCI, thereby indicating which antenna panel the terminal device employs to receive the PDSCH.

The terminal device may determine, according to the TCI in the first DCI, a reception beam group to which a reception beam for receiving the first PDSCH belongs, and further determine, according to the HARQ process set corresponding to the reception beam group, a HARQ process set corresponding to the reception beam group. Thereafter, the terminal device may determine, according to the HARQ process number, a HARQ process corresponding to the first PDSCH from the HARQ process set.

It should be understood that the indication field related to the antenna panel is not limited to the above examples, and the application does not limit the indication field related to the antenna panel. It should also be understood that the distinction between different receive beam groups by reference to signal resources and antenna panels is only two possible implementations provided herein and should not constitute any limitation herein. This application does not exclude the possibility of using other ways to distinguish between different groups of received beams.

Optionally, step 230 specifically includes: and the terminal equipment determines the HARQ process corresponding to the first PDSCH according to the HARQ process number and the receiving beam group of the first PDCCH.

In this embodiment, the network device may activate a TCI state through a Media Access Control (MAC) Control Element (CE). The TCI state may include therein a reference signal resource identifier for determining a reception beam for receiving the PDCCH. The terminal device may determine a reception beam for receiving the PDCCH according to the activated TCI state in the MAC CE.

The specific process of determining the HARQ process set according to the received beam group and then determining the HARQ process of the first PDSCH according to the HARQ process number has been described in detail above. For brevity, no further description is provided herein.

It should be understood that since the reference signal resource identifier has a relationship with the receive beam and also has a corresponding relationship with the transmit beam, when the reference signal resource identifier is fixed, the corresponding receive beam and transmit beam can also be determined. When the reference signal resources indicated by the reference signal resource identifier indicated in the TCI belong to the same reference signal resource group, the corresponding transmission beams may also belong to the same transmission beam group. When the receiving beams corresponding to the reference signal resource identifiers indicated in the TCI belong to the same receiving beam group, it can be considered that the transmitting beams corresponding to the reference signal resource identifiers indicated in the TCI also belong to the same transmitting beam group. Therefore, the above "the terminal device determines the HARQ process corresponding to the first PDSCH according to the HARQ process number and the received beam group of the first PDSCH" may be replaced with "the terminal device determines the HARQ process corresponding to the first PDSCH according to the HARQ process number and the transmitted beam group of the first PDSCH"; the above "the terminal device determines the HARQ process corresponding to the first PDSCH according to the HARQ process number and the reception beam group of the first PDCCH" may be replaced with "the terminal device determines the HARQ process corresponding to the first PDSCH according to the HARQ process number and the transmission beam group of the first PDCCH".

It is also understood that one or more of the configuration parameters of the PDCCH, DMRS port, BWP, the set of network devices transmitting the first PDSCH, DCI type, receive beam (or transmit beam) of the first PDSCH, and receive beam (or transmit beam) of the first PDCCH listed above may also be used in conjunction with the HARQ process number to determine the corresponding HARQ process for the first PDSCH. For example, 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. Or, the terminal device may further determine the HARQ process corresponding to the first PDSCH according to the HARQ process number, the PDCCH configuration, and the reception beam group to which the reception beam of the first PDSCH belongs. For the sake of brevity, this is not listed here.

The terminal device may also use one or more of the configuration parameters of the PDCCH, the DMRS port, the BWP, the 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 in combination with the HARQ process number, so that the specific method for determining the HARQ process corresponding to the first PDSCH is similar to the specific method described above, and for brevity, details are not repeated here.

It should be noted that the protocol may define in advance which item is specifically used to determine the HARQ process corresponding to the first PDSCH. For example, the protocol may be predefined, and the HARQ process corresponding to the first PDSCH is determined according to the HARQ process number and the PDCCH configuration. In this case, 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, according to the PDCCH configuration based on which the first PDCCH is blind-checked, an HARQ process corresponding to the first PDSCH by using the HARQ process number.

It is to be appreciated that when the protocol defines other parameters to determine the HARQ process corresponding to the first PDSCH, the network device and the terminal device may process to determine the HARQ process corresponding to the first PDSCH based on methods similar to those described above. Since the specific processes thereof are similar, they will not be described in detail herein for the sake of brevity.

Based on the above technical solution, when receiving multiple PDCCHs for scheduling multiple PDSCHs, the terminal device may determine, according to the HARQ process number, the HARQ process corresponding to each PDSCH in combination with one or more of configuration parameters of the PDCCH, a port of the DMRS, and a network device group that transmits the PDSCH.

For convenience of understanding, the specific process of the terminal device determining the HARQ process corresponding to the first PDSCH is described in detail by taking only one transport block carried in the first PDSCH as an example. In fact, two or more transport blocks may be carried in the first PDSCH, and in the case that the first PDSCH carries multiple transport blocks, the terminal device may determine the HARQ process corresponding to each transport block, for example, according to the method in the prior art.

As described above, the first PDSCH may carry one or more transport blocks. For convenience of understanding, the specific process of the terminal device determining the HARQ process corresponding to the first PDSCH is described in detail by taking the example that one transport block is carried in the first PDSCH. When one or more transport blocks are carried in the first PDSCH, 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 a maximum of two transport blocks are carried in the first PDSCH according to the RRC message received first. In this case, the number of HARQ processes corresponding to the first PDSCH may be one or more.

In a case that the first PDSCH carries one or more transport blocks, after determining the HARQ process set corresponding to the first PDSCH, the terminal device may further determine the HARQ process corresponding to each transport block in the first PDSCH in the HARQ process set. The terminal device may determine the HARQ process corresponding to each transport block according to a method in the prior art, for example.

Optionally, 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 items: configuration parameters of the PDCCH, a network device group transmitting the PDSCH, a port of the DMRS indicated in the first DCI, and the BWP.

In particular, an indication of a transport block may be included in the first PDCCH. The indication of the transport block may be, for example, an identification of the transport block, or other information that may be used to distinguish between different transport blocks. In one implementation, different transport blocks may be distinguished by the order in which the indication fields of their configuration information appear in DCI. For example, the configuration information of the transport block #1 may precede the configuration information of the transport block # 2. Or, the indication bit of the configuration information of the transport block #1 precedes the indication bit of the configuration information of the transport block # 2.

For ease of understanding, (a) and (b) in fig. 5 show two examples of indication bits of transport block #1 and transport block #2 in DCI. As shown, the indication bit of the transport block #1 and the indication bit of the transport block #2 may be consecutive, and the indication bit of the transport block #1 may precede the indication bit of the transport block # 2. It should be understood that the drawings are merely illustrative and should not be construed as limiting the application in any way. For example, the indication bit of the transport block #1 and the indication bit of the transport block #2 may not be consecutive, but the indication bit of the transport block #1 is still before the indication bit of the transport block # 2. The present application does not limit the specific positions of the indication bits of the transport block #1 and the indication bits of the transport block #2 in the DCI.

In addition, distinguishing different transport blocks by indicating the order of bits in DCI is only one possible implementation manner, and should not constitute any limitation in this application. For example, different transport blocks may also be distinguished by different indexes or numbers, and the specific indication manner of the transport blocks is not limited in the present application.

After determining the process set corresponding to the first PDSCH based on the above technical solution, 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.

After receiving the first PDCCH, the terminal device may determine the number of transport blocks carried in the first PDSCH by parsing the indication field of the transport blocks in the first DCI. When the number of transport blocks carried in the first PDSCH is 1, the terminal device may determine, based on the above-described method, the HARQ process corresponding to the transport block; when the number of the transport blocks carried in the first PDSCH is multiple, the terminal device may further determine, according to the HARQ process number and the indication of the transport block, the HARQ process corresponding to each transport block.

In one implementation, the process set corresponding to the first PDSCH may be further divided into two subsets based on different indications of transport blocks. 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. That is, the HARQ process corresponding to the transport block carried in the first PDSCH.

Fig. 6 to fig. 10 are schematic diagrams of different PDCCH configurations and different transport blocks corresponding to different HARQ processes provided in the embodiment of the present application.

Where fig. 6 may correspond to fig. 3, a further refinement of fig. 3 is provided. Specifically, the HARQ buffer may first be divided into different regions based on different PDCCH configurations. Region #1 corresponds to PDCCH allocation #1, and region #2 corresponds to PDCCH allocation # 2. Thereafter, the regions may be further divided to correspond to different transport blocks based on the different transport blocks. For example, the region #1-1 and the region #2-1 may correspond to the transport block #1, and the region #1-2 and the region #2-2 may correspond to the transport block # 2. Therefore, the HARQ process stored in the region #1-1 may correspond to the PDCCH configuration #1 and the transport block #1, i.e., the subset #1 in the HARQ process set # 1; the HARQ processes stored in the region #1-2 may correspond to the PDCCH configuration #1 and the transport block #2, that is, the subset #2 in the HARQ process set # 1; the HARQ processes stored in the region #2-1 may correspond to the PDCCH configuration #2 and the transport block #1, that is, the subset #1 in the HARQ process set # 2; the HARQ processes stored in region #2-2 may correspond to PDCCH configuration #2 and transport block #2, i.e., subset #2 in HARQ process set # 2.

It should be understood that the region #1 and the region #2 may be continuous or discontinuous, and the present application does not limit this. The region #1-1 and the region #1-2 may be continuous or discontinuous, and the region #2-1 and the region #2-2 may be discontinuous, as shown in fig. 7. The arrangement position and the sequence among different areas are not limited by the application.

Fig. 8 may correspond to fig. 4. Specifically, HARQ processes may first be renumbered based on different PDCCH configurations. The HARQ processes with local numbers 0 to 2N-1 correspond to PDCCH configuration #1, and the HARQ processes with local numbers 2N to 4N-1 correspond to PDCCH configuration # 2. Thereafter, the local numbers may be further grouped to correspond to different transport blocks based on the different transport blocks. For example, HARQ processes with local numbers 0 to N-1 may correspond to PDCCH configuration #1, transport block #1, i.e. subset #1 in HARQ process set # 1; the HARQ processes with local numbers N to 2N-1 may correspond to PDCCH configuration #1 and transport block #2, i.e. subset #2 in HARQ process set # 1; HARQ processes with local numbers 2N to 3N-1 may correspond to PDCCH #2, transport block #1, i.e. subset #1 in HARQ process set # 2; the HARQ processes having local numbers 3N to 4N-1 may correspond to PDCCH #2, transport block #2, i.e., subset #2 in HARQ process set # 2.

Fig. 9 is another example corresponding to fig. 4. The local numbering of the HARQ processes in each subset defined in fig. 9 and 8 is the same, but the physical addresses of the occupied HARQ buffers may be different.

It should be understood that the local numbers of the HARQ process sets corresponding to the same PDCCH configuration may or may not be consecutive. As shown in fig. 10, the local numbers of HARQ processes of subset #1 in HARQ process set #1 may be 0 to N-1; the local number of HARQ processes of subset #2 in HARQ process set #1 may be 2N to 3N-1; the local number of HARQ processes of subset #1 in HARQ process set #2 may be N to 2N-1; the local number of HARQ processes of subset #2 in HARQ process set #2 may be 3N to 4N-1. This is not limited in this application.

It should also be understood that the above listed methods of determining different subsets of the HARQ process set according to the PDCCH configuration and the indication of the transport block are only examples. Those skilled in the art may also determine the corresponding subset of HARQ process set according to PDCCH configuration and transport block in other possible ways based on the same concept. 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. In addition, the HARQ process set and the subset are defined only for ease of understanding, and should not constitute any limitation to the present application. Those skilled in the art may also not determine the HARQ process set and the subset, and determine the HARQ process corresponding to the transport block directly according to the HARQ process number, the transport block, and the PDCCH configuration.

In addition, the PDCCH configuration may also be replaced with BWP downlink dedicated parameters, BWP downlink parameters, serving cell configuration, control resource set group, search space set group, DMRS port group, or network device group.

It should be noted that, the above technical solution does not limit the number of network device groups. In other words, the above technical solution can be used to determine the HARQ process of the PDSCH in either a single-site scenario or a multi-site scenario.

In this embodiment, the terminal device may further determine, according to a preset rule, a current scenario of a single-site service or a multi-site service. It should be noted that a single site may be a network device or a network device group; the multi-site may be a plurality of network devices or a plurality of network device groups. This is not a limitation of the present application.

Optionally, the terminal device determines whether to currently be in single-site service or multi-site service according to the number of received configuration parameters of the PDCCH.

Specifically, the configuration parameters of the PDCCH may include at least one of: serving cell configuration, BWP downlink parameters under the serving cell configuration, BWP downlink dedicated parameters under the BWP downlink parameters, PDCCH configuration under the BWP downlink dedicated parameters, and control resource set and search space set under the PDCCH configuration, or control resource set combination search space set group under the PDCCH configuration. The receiving of the configuration parameters of multiple PDCCHs by the terminal device 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, or receiving multiple control resource sets, or receiving multiple control resource set groups, or receiving multiple search space sets, or receiving multiple search space set groups. In other words, when the terminal device receives a plurality of configuration parameters of the above listed PDCCH, it may be determined that the terminal device is currently in a multi-site service scenario.

As mentioned above, the above-mentioned multiple serving cell configurations, multiple BWP downlink parameters, multiple BWP downlink dedicated parameters, multiple PDCCH configurations, etc. are not limited to one parameter, and each configuration parameter may include one or more parameters. For example, a BWP downlink parameter may include a set of parameters, and a BWP downlink dedicated parameter may also include a set of parameters. The present application is not limited to the specific content and number of parameters included in each configuration parameter.

Further, step 230 may further include: and under the condition that the terminal equipment receives the configuration parameters of the plurality of PDCCHs, determining the HARQ process corresponding to the first PDSCH at least according to the HARQ process number and the configuration parameters of the PDCCHs.

That is to say, the terminal device may determine, under the multi-site service, the HARQ process corresponding to the first PDSCH according to the HARQ process number and the configuration parameter of the PDCCH by using the technical scheme 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 the parameter that is 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 at least according to the HARQ process number and the PDCCH configuration.

It should also be understood that the above listed configuration parameters of PDCCH are only examples and should not constitute any limitation to the present application. The configuration parameters of the PDCCH may also include other parameters besides those listed above, or may also include parameters having the same or similar functions as one or more of those listed above, which is not limited in this application.

It should also be understood that the terminal device may also determine the current multi-site service scenario based on other manners, and not necessarily based on the configuration parameters of receiving multiple PDCCHs. For example, the network device may also signal to the terminal device the number of network devices serving the terminal device. The present application does not limit the specific manner in which the terminal device determines whether to use a single station or multiple stations. Therefore, step 230 may further include: and under the condition of multi-site service, the terminal equipment determines the HARQ process corresponding to the first PDSCH at least according to the HARQ process number and the configuration parameters of the PDCCH.

Optionally, the terminal device determines whether to currently be in a single-site service or a multi-site service according to the number of port groups of the received DMRS.

Specifically, when the number of ports of the DMRS received by the terminal device is multiple groups, the terminal device may determine that the terminal device is currently in a multi-site service scenario. The plurality of network device groups may transmit the PDSCH based on DMRS ports in different port groups, respectively.

Further, step 230 may further include: and under the condition that the terminal equipment receives the port groups of the plurality of DMRSs, determining 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.

That is to say, the terminal device may determine, in the case of a multi-site service, 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, by using the technical scheme described above.

It should be understood that the terminal device may also determine the current multi-site service scenario based on other manners, and not necessarily based on the configuration parameters of receiving multiple PDCCHs. For example, the network device may also signal to the terminal device the number of network devices serving the terminal device. The present application does not limit the specific manner in which the terminal device determines whether to use a single station or multiple stations. Therefore, step 230 may further include: and under the condition of multi-site service, the terminal equipment determines the HARQ process corresponding to the first PDSCH at least according to the HARQ process number and the configuration parameters of the PDCCH.

Optionally, the terminal device determines, under the multi-site service, an HARQ process corresponding to the first PDSCH at least according to the HARQ process number and the indication of the network device group.

For example, the terminal device may determine whether it is currently in a multi-site service scenario based on the above-listed methods or other possible approaches. And under the condition of determining the multi-site service, the technical scheme as described above is 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.

Optionally, the terminal device determines, under the multi-site service, an HARQ process corresponding to the first PDSCH at least according to the HARQ process number and the indication of the BWP.

For example, the terminal device may determine whether it is currently in a multi-site service scenario based on the above-listed methods or other possible approaches. And may, in case of determining the multi-site service, determine, by using the technical solution as described above, a HARQ process corresponding to the first PDSCH at least according to the HARQ process number and the indication of the BWP.

In step 240, the terminal device processes the data carried in the first PDSCH according to the HARQ process.

As mentioned previously, the transport blocks carried in the received PDSCH by the terminal device prior to the first PDSCH may be saved in the HARQ buffer. The transport block stored in the HARQ buffer may be, for example, a transport block whose decoding fails, or a transport block whose decoding succeeds, which is not limited in this application.

Take the processing procedure of the retransmission transport block as an example. When determining that the transport block carried by the first PDSCH is a retransmitted transport block, the terminal device may further determine an HARQ process corresponding to the first PDSCH according to the HARQ process number in the first DCI, and one or more of the configuration parameters of the PDCCH, the port group to which the DMRS port belongs, and the network device group that transmits the first PDSCH. The terminal device may obtain the transport blocks of the same HARQ process from the HARQ buffer according to the determined HARQ process. The terminal device may perform soft combining and decoding on multiple transport blocks (e.g., may include an initial transport block and a retransmission transport block) of the same HARQ process.

It should be understood that the specific process of the terminal device processing 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 transport block or the retransmitted transport block may refer to the prior art, and for example, whether the transport block is the initial transport block or the retransmitted transport block may be determined according to whether the NDI field is flipped. A detailed description of this specific method is omitted herein.

In the embodiment of the present application, the terminal device determines the HARQ process corresponding to the first PDSCH according to the HARQ process number, and one or more of 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 that transmits the first PDSCH, the type of the first DCI, the receive beam (or transmit beam) of the first PDSCH, the receive beam (or transmit beam) of the first PDCCH, and the like, and may accurately determine the corresponding HARQ process when receiving multiple PDSCHs. Therefore, the situation that one HARQ process number possibly appears in the same value range of the HARQ process numbers indicated in the PDCCHs corresponds to a plurality of HARQ processes can be avoided under the scene of multi-site service, and the possibility of carrying out combined decoding on two originally different transmission blocks is avoided. Therefore, the decoding efficiency can be improved, and the data transmission performance can be improved. The terminal equipment can correctly process the HARQ process in different scenes, so that the communication system can flexibly adopt different transmission schemes to serve the terminal equipment, and the system performance is favorably improved.

The method provided by the embodiment of the present application is described in detail above with reference to fig. 2 to 10. Hereinafter, a communication device according to an embodiment of the present application will be described in detail with reference to fig. 11 and 12.

Fig. 11 is a schematic block diagram of a communication device provided in an embodiment of the present application. As shown, the communication device 1000 may include a communication unit 1100 and a processing unit 1200.

In one possible design, the communication apparatus 1000 may correspond to the terminal device in the above method embodiment, and may be, for example, the terminal device or a chip configured in the terminal device.

Specifically, the communication apparatus 1000 may correspond to the terminal device in the method 200 according to the embodiment of the present application, and the communication apparatus 1000 may include a unit for executing the method executed by the terminal device in the method 200 in fig. 2. Also, the units in the communication device 1000 and the other operations and/or functions described above are respectively for implementing the corresponding flows of the method 200 in fig. 2.

Wherein, when the communication device 1000 is used to execute the method 200 in fig. 2, the communication unit 1100 may be used to execute the steps 210 and 220 in the method 200, and the processing unit 1200 may be used to execute the steps 230 and 240 in the method 200.

It should be understood that the specific processes of the units for executing the corresponding steps are already described in detail in the above method embodiments, and therefore, for brevity, detailed descriptions thereof are omitted.

It is further understood that when the communication apparatus 1000 is a terminal device, the communication unit 1100 in the communication apparatus 1000 may correspond to the transceiver 2020 in the terminal device 2000 shown in fig. 12, and the processing unit 1200 in the communication apparatus 1000 may correspond to the processor 2010 in the terminal device 2000 shown in fig. 12.

It should also be understood that when the communication apparatus 1000 is a chip configured in a terminal device, the communication unit 1100 in the communication apparatus 1000 may be an input/output interface.

In another possible design, the communication apparatus 1000 may correspond to the network device in the above method embodiment, for example, may be the first network device in the above method embodiment, or a chip configured in the first network device; the second network device in the above method embodiment may also be, or be configured with a chip in the second network device.

Specifically, the communication apparatus 1000 may correspond to the first network device in the method 200 according to the 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. Also, the units in the communication device 1000 and the other operations and/or functions described above are respectively for implementing the corresponding flows of the method 200 in fig. 2.

Wherein, when the communication device 1000 is configured to execute the method 200 in fig. 2, the communication unit 1100 is configured to execute the steps 210 and 220 in the method 200, and the processing unit 1200 is configured to generate the first DCI.

It should also be understood that, in the above method embodiments, the second network device may perform the same actions as the first network device, and therefore, for brevity, the description is omitted here.

It should also be understood that when the communication apparatus 1000 is a network device, the communication unit in the communication apparatus 1000 may correspond to the transceiver 3200 in the network device 3000 shown in fig. 13, and the processing unit 1200 in the communication apparatus 1000 may correspond to the processor 3100 in the network device 3000 shown in fig. 13.

It should also be understood that when the communication device 1000 is a chip configured in a network device, 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 according to an embodiment of the present application. The terminal device 2000 can be applied to the system shown in fig. 1, and performs the functions of the terminal device in the above method embodiment.

As shown, the terminal device 2000 includes a processor 2010 and a transceiver 2020. Optionally, the terminal device 2000 further comprises a memory 2030. The processor 2010, the transceiver 2002 and the memory 2030 may be in communication with each other via the interconnection path to transfer control and/or data signals, the memory 2030 may be used for storing a computer program, and the processor 2010 may be used for retrieving and executing the computer program from the memory 2030 to control the transceiver 2020 to transmit and receive signals. Optionally, the terminal device 2000 may further include an antenna 2040, configured to transmit uplink data or uplink control signaling output by the transceiver 2020 by using a wireless signal.

The processor 2010 and the memory 2030 may be combined into a processing device, and the processor 2010 is configured to execute the program codes stored in the memory 2030 to achieve the above functions. In particular, the memory 2030 may be integrated with the processor 2010 or may be separate from the processor 2010. The processor 2010 may correspond to the processing unit in fig. 11.

The transceiver 2020 may correspond to the communication unit in fig. 11, and may also be referred to as a transmitting/receiving unit. The transceiver 2020 may include a receiver (or receiver, receiving circuit) and a transmitter (or transmitter, transmitting circuit). Wherein the receiver is used for receiving signals, and the transmitter is used for transmitting signals.

It should be understood that terminal device 2000 shown in fig. 12 is capable of implementing various processes involving the terminal device in the method embodiment shown in fig. 2. The operations and/or functions of the modules in the terminal device 2000 are respectively to implement the corresponding flows in the above-described method embodiments. Specifically, reference may be made to the description of the above method embodiments, and the detailed description is appropriately omitted herein to avoid redundancy.

The processor 2010 may be configured to perform the actions described in the preceding method embodiments that are implemented within the terminal device, and the transceiver 2020 may be configured to perform the actions described in the preceding method embodiments that the terminal device transmits to or receives from the network device. Please refer to the description of the previous embodiment of the method, which is not repeated herein.

Optionally, the terminal device 2000 may further include a power supply 2050 for supplying power to various devices or circuits in the terminal device.

In addition, in order to further improve the functions of 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, and the like, and the audio circuit may further include a speaker 2082, a microphone 2084, and the like.

Fig. 13 is a schematic structural diagram of a network device provided in the embodiment of the present application, which may be a schematic structural diagram of a base station, for example. The base station 3000 can be applied to the system shown in fig. 1, and performs the functions of the network device in the above method embodiment.

As shown, 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 (BBUs) (also referred to as digital units, DUs) 3200. The RRU 3100 may be referred to as a transceiver unit and corresponds to the communication unit 1200 in fig. 11. Alternatively, the transceiving unit 3100 may also be referred to as a transceiver, transceiving circuit, or transceiver, etc., which may comprise at least one antenna 3101 and a radio frequency unit 3102. Alternatively, 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 transceiving and converting radio frequency signals to baseband signals, for example, for sending indication information to a terminal device. The BBU 3200 section is mainly used for performing baseband processing, controlling a base station, and the like. The RRU 3100 and the BBU 3200 may be physically disposed together or may be physically disposed separately, i.e. distributed base stations.

The BBU 3200, which is a control center of the base station and may also be referred to as a processing unit, may correspond to the processing unit 1100 in fig. 11, and is mainly used for performing baseband processing functions, such as channel coding, multiplexing, modulation, spreading, and the like. For example, the BBU 3200 (processing unit) may be configured to control the base station to perform an operation procedure related to a network device (e.g., a first network device) in the above method embodiments, for example, to generate a first DCI.

In an example, the BBU 3200 may be formed by one or more boards, and the boards may collectively support a radio access network of a single access system (e.g., an LTE network), or may respectively support radio access networks of different access systems (e.g., an LTE network, a 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 for controlling the base station to perform necessary actions, for example, for controlling the base station to execute the operation flow related to the network device in the above method embodiment. The memory 3201 and processor 3202 may serve one or more boards. That is, the memory and processor may be provided separately on each board. Multiple boards may share the same memory and processor. In addition, each single board can be provided with necessary circuits.

It should be appreciated that the base station 3000 shown in fig. 13 can implement various processes involving a network device (e.g., a first network device or a second network device) in the method embodiment of fig. 2. The operations and/or functions of the respective modules in the base station 3000 are respectively for implementing the corresponding flows in the above-described method embodiments. Specifically, reference may be made to the description of the above method embodiments, and the detailed description is appropriately omitted herein to avoid redundancy.

BBU 3200 as described above can be used to perform actions described in previous method embodiments as being implemented internally by a network device, while RRU 3100 can be used to perform actions described in previous method embodiments as being sent by or received from a terminal device by a network device. Please refer to the description of the previous embodiment of the method, which is not repeated herein.

The embodiment of the application also provides a processing device, which comprises a processor and an interface; the processor is used for executing the communication method in the method embodiment.

It should be understood that the processing means may be a chip. For example, the processing device may be a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), a system on chip (SoC), a Central Processing Unit (CPU), a Network Processor (NP), a digital signal processing circuit (DSP), a Microcontroller (MCU), a Programmable Logic Device (PLD), or other integrated chips.

In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The steps of a method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor. To avoid repetition, it is not described in detail here.

It should be noted that the processor in the embodiments of the present application may be an integrated circuit chip having signal processing capability. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The processor described above 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 device, discrete gate or transistor logic, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A 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 connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.

It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM, enhanced SDRAM, SLDRAM, Synchronous Link DRAM (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

According to the method provided by the embodiment of the present application, the present application further provides a computer program product, which includes: computer program code which, when run on a computer, causes the computer to perform the method of any of the embodiments shown in fig. 2.

According to the method provided by the embodiment of the present application, the present application also provides a computer readable medium, which stores program code, and when the program code runs on a computer, the computer is caused to execute the method of any one of the embodiments shown in fig. 2.

According to the method provided by the embodiment of the present application, the present application further provides a system, which includes the foregoing one or more terminal devices and one or more network devices.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may 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. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a Digital Video Disk (DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), among others.

The network device in the foregoing device embodiments completely corresponds to the terminal device and the network device or the terminal device in the method embodiments, and the corresponding module or unit executes the corresponding steps, for example, the communication unit (transceiver) executes the steps of receiving or transmitting in the method embodiments, and other steps besides transmitting and receiving may be executed by the processing unit (processor). The functions of the specific elements may be referred to in the respective method embodiments. The number of the processors may be one or more.

As used in this specification, the terms "component," "module," "system," and the like are intended to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between 2 or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from two components interacting with another component in a local system, distributed system, and/or across a network such as the internet with other systems by way of the signal).

Those of ordinary skill in the art will appreciate that the various illustrative logical blocks and steps (step) described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

In the above embodiments, the functions of the functional units may be fully or partially implemented by software, hardware, firmware, or any combination thereof. When implemented in software, may 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). The procedures or functions described in accordance with the embodiments of the present application are generated in whole or in part when the computer program instructions (programs) are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of receiving data, comprising:

receiving a Physical Downlink Shared Channel (PDSCH), wherein the PDSCH is scheduled by a Physical Downlink Control Channel (PDCCH), and Downlink Control Information (DCI) carried by the PDCCH comprises an indication of a hybrid automatic repeat request (HARQ) process number;

determining the HARQ process corresponding to the PDSCH according to the HARQ process number and one or more of the following items: configuration parameters of the PDCCH, a network device group transmitting the PDSCH, a port of a demodulation reference signal (DMRS) indicated in the DCI and a bandwidth part BWP;

and processing the data carried by the PDSCH according to the determined HARQ process.

2. The method of claim 1, wherein the configuration parameters of the PDCCH comprise: PDCCH configuration of a PDCCH, BWP downlink dedicated parameters of a bandwidth part to which the PDCCH configuration belongs, BWP downlink parameters to which the PDCCH configuration belongs, serving cell configuration to which the PDCCH configuration belongs, a control resource set of the PDCCH, a control resource set group to which the control resource set of the PDCCH belongs, a search space set of the PDCCH or a search space set group to which the search space set of the PDCCH belongs.

3. The method of claim 1 or 2, wherein the determining the HARQ process corresponding to the PDSCH according to the HARQ process number and one or more of: the configuration parameters of the PDCCH, the network device group sending the PDSCH, the port and the BWP of the DMRS indicated in the DCI comprise:

and under the condition of receiving the configuration parameters of the plurality of PDCCHs, determining the HARQ process corresponding to the PDSCH according to the HARQ process number and the configuration parameters of the PDCCHs.

4. The method of claim 1, wherein the determining the HARQ process corresponding to the PDSCH based on the HARQ process number and one or more of: the configuration parameters of the PDCCH, the network device group sending the PDSCH, the port and the BWP of the DMRS indicated in the DCI comprise:

and under the condition that the indication of the port groups of a plurality of DMRSs is received, determining the HARQ process corresponding to the PDSCH according to the HARQ process number and the port group to which the port of the DMRS indicated in the DCI belongs.

5. The method of any of claims 1-4, wherein an indication of a group of network devices transmitting the PDSCH is included in the DCI.

6. The method of any of claims 1 to 5, wherein an indication of a plurality of transport blocks is included in the DCI, one or more transport blocks are carried in the PDSCH, one HARQ process per transport block; and

determining the HARQ process corresponding to the PDSCH according to the HARQ process number and one or more of the following items: the configuration parameters of the PDCCH, the network device group sending the PDSCH, the port and the BWP of the DMRS indicated in the DCI comprise:

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 items: the configuration parameters of the PDCCH, the network equipment group sending the PDSCH, the port and the BWP of the DMRS indicated in the DCI.

7. A communications apparatus, comprising:

a communication unit, configured to receive a physical downlink shared channel PDSCH, where the PDSCH is scheduled by a physical downlink control channel PDCCH, and downlink control information DCI carried by the PDCCH includes an indication of a HARQ process number;

a processing unit, configured to determine, according to the HARQ process number and one or more of the following items, an HARQ process number corresponding to the PDSCH, and process, according to the determined HARQ process number, data carried by the PDSCH: the configuration parameters of the PDCCH, the network equipment group sending the PDSCH, and the port and bandwidth part BWP of the demodulation reference signal DMRS indicated in the DCI.

8. The apparatus of claim 7, wherein the configuration parameters of the PDCCH comprise: PDCCH configuration of a PDCCH, BWP downlink dedicated parameters of a bandwidth part to which the PDCCH configuration belongs, BWP downlink parameters to which the PDCCH configuration belongs, serving cell configuration to which the PDCCH configuration belongs, a control resource set of the PDCCH, a control resource set group to which the control resource set of the PDCCH belongs, a search space set of the PDCCH or a search space set group to which the search space set of the PDCCH belongs.

9. The apparatus according to claim 7 or 8, wherein the processing unit is specifically configured to, when configuration parameters of a plurality of PDCCHs are received, determine a HARQ process corresponding to the PDSCH according to at least the HARQ process number and the configuration parameters of the PDCCH.

10. The apparatus of claim 7, wherein the processing unit is specifically configured to, upon receiving an indication of a port group for a plurality of DMRSs, determine the HARQ process corresponding to the PDSCH based on at least the HARQ process number and the port group to which the port of the DMRS indicated in the DCI belongs.

11. The apparatus of any one of claims 7-10, wherein an indication of a group of network devices transmitting the PDSCH is included in the DCI.

12. The apparatus of any of claims 7 to 11, wherein an indication of a plurality of transport blocks is included in the DCI, one or more transport blocks are carried in the PDSCH, one HARQ process for each transport block;

the processing unit is specifically configured to determine, according to the HARQ process number, the indication of the transport block, and one or more of the following, a HARQ process corresponding to each transport block in the PDSCH: the configuration parameters of the PDCCH, the network equipment group sending the PDSCH, the port and the BWP of the DMRS indicated in the DCI.

13. A communications apparatus comprising at least one processor configured to implement the method of any one of claims 1 to 6.

14. A computer-readable medium, comprising a computer program which, when run on a computer, causes the computer to perform the method of any one of claims 1 to 6.