CN111148260A

CN111148260A - Method for transmitting and receiving data and communication device

Info

Publication number: CN111148260A
Application number: CN201811303221.0A
Authority: CN
Inventors: 杭海存; 葛士斌; 王潇涵; 纪刘榴
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-11-02
Filing date: 2018-11-02
Publication date: 2020-05-12
Anticipated expiration: 2038-11-02
Also published as: WO2020088551A1; CN111148260B; US20210259003A1; EP3863356A4; US11956794B2; EP3863356A1

Abstract

The application provides a method for sending and receiving data, which is beneficial to improving the data transmission performance. The method comprises the following steps: the method comprises the steps that terminal equipment receives a first PDCCH and a second PDCCH, wherein the first PDCCH is used for scheduling a first PDSCH, and the first PDSCH is used for transmitting first data; determining a first resource for transmitting first data based on the first PDCCH and the second PDCCH, wherein the first resource is part or all of resources in the first PDSCH; the terminal device receives first data from the network device on the first resource. By determining the first resource by combining the first PDCCH and the second PDCCH, the problem that the receiving performance of the first PDSCH and the second PDCCH may be reduced under the condition that the second PDCCH and the first PDSCH are overlapped in resource can be avoided, thereby being beneficial to improving the data transmission performance.

Description

Method for transmitting and receiving data and communication device

Technical Field

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

Background

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 by transmitting Downlink Control Information (DCI) in a Physical Downlink Control Channel (PDCCH). The terminal device may receive downlink data on the PDSCH scheduled for it by the network device.

However, in some cases, the network device may urgently schedule the PDSCH for the terminal device through the PDCCH based on some emergency traffic, such as Ultra Reliable Low Latency Communication (URLLC) traffic. Both the PDCCH and PDSCH may collide with the previously scheduled PDSCH resources, respectively, resulting in a degradation of the performance of the terminal device in receiving data.

Disclosure of Invention

The application provides a method for sending and receiving data and a communication device, aiming to improve the data transmission performance.

In a first aspect, a method of receiving data is provided. The method may be executed by the terminal device, or may also be executed by a chip configured in the terminal device, which is not limited in this application.

Specifically, the method comprises the following steps: receiving a first PDCCH (physical downlink control channel) which is used for scheduling a PDSCH (physical downlink shared channel) and transmitting first data; receiving a second PDCCH; determining a first resource for transmitting the first data based on the first PDCCH and the second PDCCH, the first resource being a part or all of the resources of the first PDSCH; the first data is received on the first resource.

Therefore, the terminal device may determine, in combination with the first PDCCH and the second PDCCH, a first resource for transmitting the first data in case of receiving the first PDCCH and the second PDCCH. Due to the consideration of the resources scheduled by the first PDCCH and the second PDCCH, the transmission resources of the first data can be reasonably determined, and possible resource conflict is avoided, so that the data transmission performance is favorably improved.

In a second aspect, a method of transmitting data is provided. The method may be performed by a network device, or may be performed by a chip configured in the network device, which is not limited in this application.

Specifically, the method comprises the following steps: sending a first Physical Downlink Control Channel (PDCCH), wherein the first PDCCH is used for indicating and scheduling a first Physical Downlink Shared Channel (PDSCH), and the first PDSCH is used for transmitting first data; transmitting a second PDCCH; determining a first resource for transmitting the first data based on the first PDCCH and the second PDCCH, the first resource being a part or all of the resources of the first PDSCH; the first data is transmitted on the first resource.

Accordingly, the network device may determine, in conjunction with the first PDCCH and the second PDCCH, a first resource for transmitting the first data in a case where the first PDCCH and the second PDCCH are transmitted. Due to the consideration of the resources scheduled by the first PDCCH and the second PDCCH, the transmission resource of the first data can be reasonably determined, the possible resource conflict can be avoided, the possible interference caused by the use of the same time-frequency resource for transmitting different data can be avoided, and the data transmission performance can be favorably improved.

With reference to the first aspect or the second aspect, in some possible implementations, in a case that a second PDCCH and a first PDSCH have resource overlap, determining a first resource for transmitting first data based on the first PDCCH and the second PDCCH includes: and determining the resources except the second PDCCH in the first PDSCH scheduled by the first PDCCH as the first resources.

When the second PDCCH and the first PDSCH have resource overlap, both the terminal device and the network device may remove the overlapped resource from the first PDSCH, and determine the remaining resource in the first PDSCH after removing the resource occupied by the second PDCCH as the first resource. Therefore, interference of data transmission on the first PDSCH to the second PDCCH can be avoided, and correct reception and decoding of the second PDCCH are ensured, so as to avoid losing important signaling and data.

With reference to the first aspect or the second aspect, in some possible implementations, the second PDCCH is used to schedule the second PDSCH, and in a case that the second PDSCH and the first PDSCH have resource overlap, determining a first resource for transmitting first data based on the first PDCCH and the second PDCCH includes: determining resources other than the second PDSCH in the first PDSCH as first resources.

When the second PDSCH and the first PDSCH have resource overlap, both the terminal device and the network device may remove the overlapped resources from the first PDSCH, and determine the remaining resources in the first PDSCH after removing the resources occupied by the second PDSCH as the first resources. Therefore, mutual interference between the first PDSCH and the second PDSCH can be avoided, and data transmission performance can be improved.

And, when the first PDSCH and the second PDSCH are from the same network device or the same network device group, the second data transmitted by the second PDSCH may be data of emergency traffic, such as data of URLLC traffic. In this embodiment, by discarding the resource in the overlapping region of the first PDSCH and the second PDSCH and transmitting the second data through the second PDSCH, reliable transmission of the emergency service can be preferentially ensured.

With reference to the first aspect or the second aspect, in some possible implementations, the second PDCCH is used to schedule the second PDSCH, and when the second PDCCH and the second PDSCH both overlap with the first PDSCH in terms of resources, determining a first resource for transmitting the first data based on the first PDSCH and the second PDCCH includes: and determining the resources except the second PDCCH and the second PDSCH in the first PDSCH scheduled by the first PDCCH as the first resources.

When the second PDCCH and the second PDSCH are both overlapped with the first PDSCH, the terminal device and the network device may remove the overlapped resources from the first PDSCH, and determine the remaining resources in the first PDSCH after removing the resources occupied by the second PDCCH and the second PDSCH as the first resources. Therefore, mutual interference between the first PDSCH and the second PDCCH and the second PDSCH can be avoided, and data transmission performance is improved.

And, when the first PDSCH or the second PDSCH is from the same network device or the same network device group, the second PDCC may schedule physical downlink resources for emergency traffic, such as URLLC traffic, in general. The second data transmitted by the second PDSCH may typically be data of emergency traffic, such as data of URLLC traffic. In this embodiment, by discarding the resource in the overlapping region of the first PDSCH with the second PDCCH and the second PDSCH, the correct reception of the second PDCCH can be ensured, the data loss of the emergency service is avoided, and the second data can be transmitted through the second PDSCH, thereby ensuring the reliable transmission of the emergency service.

With reference to the first aspect or the second aspect, in some possible implementations, a second PDCCH is used to schedule a second PDSCH, and in a case that neither the second PDCCH nor the second PDSCH has resource overlap with the first PDSCH, the determining, based on the first PDSCH and the second PDCCH, a first resource for transmitting the first data includes: determining the first PDSCH scheduled by the first PDCCH as the first resource.

When neither the second PDCCH nor the second PDSCH has resource overlap with the first PDSCH, the terminal device and the network device can still transmit according to the method of the prior art. The terminal device may receive different data on the first PDSCH and the second PDSCH, respectively.

With reference to the first aspect, in some possible implementations, determining a first resource for transmitting first data based on a first PDCCH and a second PDCCH includes: and under the condition that the first PDCCH and the second PDCCH meet preset conditions, determining the first resource for transmitting the first data according to the first PDSCH and the second PDCCH.

When the first network device and the second network device are the same network device or belong to the same network device group, the first PDCCH and the second PDCCH may be scheduled based on different traffic types, respectively. For example, a first PDSCH scheduled by a first PDCCH may be used to transmit data for non-emergency traffic and a second PDSCH scheduled by a second PDCCH may be used to transmit data for emergency traffic. Therefore, the network device and the terminal device may determine the first resource based on the first PDCCH and the second PDCCH, respectively, to avoid the first resource from overlapping with the second PDCCH and/or the second PDSCH to cause erroneous reception or loss of data of the emergency service, so as to ensure the transmission reliability of the emergency service.

With reference to the first aspect, in some possible implementations, the determining, based on the first PDCCH and the second PDCCH, a first resource for transmitting the first data includes: and determining the first resource for transmitting the first data according to the first PDCCH when the first PDCCH and the second PDCCH do not meet a preset condition.

When the first network device and the second network device are different network devices or belong to different network device groups, the first PDCCH and the second PDCCH may be scheduled based on the same traffic type or may be scheduled based on different traffic types. Since different data can be transmitted between two network devices in the space division multiplexing transmission mode, the terminal device can receive data from different network devices based on the method in the related art. The first PDSCH and the second PDCCH may or may not overlap; the first PDSCH and the second PDSCH may or may not overlap, which is not limited in this application. By adopting the space division multiplexing transmission mode, different data can be transmitted on the same time frequency resource, so that the utilization rate of frequency spectrum resources can be improved, and the system performance can be improved.

With reference to the first aspect, in some possible implementations, the preset condition includes one or more of:

the PDCCH configuration of the first PDCCH is the same as that of the second PDCCH;

the control resource set of the first PDCCH and the control resource set of the second PDCCH belong to the same control resource set;

the control resource set of the first PDCCH and the control resource set of the second PDCCH belong to the same control resource set group;

the search space set of the first PDCCH and the search space set of the second PDCCH belong to the same search space set;

the search space set of the first PDCCH and the search space set of the second PDCCH belong to the same search space set group;

a port of a Demodulation Reference Signal (DMRS) indicated by the first PDCCH and a port of a DMRS indicated by the second PDCCH belong to the same DMRS port group (DMRS port group);

the first PDCCH and the second PDCCH are from the same cell;

the first PDCCH and the second PDCCH are from the same cell group;

the first PDCCH and the second PDCCH are both primary PDCCHs;

the receiving wave beam of the first PDSCH scheduled by the first PDCCH and the receiving wave beam of the second PDSCH scheduled by the second PDCCH are the same receiving wave beam group;

the receiving beam of the first PDCCH and the receiving beam of the second PDCCH are the same receiving beam group; and

the PDSCH configuration of the first PDSCH scheduled by the first PDCCH is the same as the PDSCH configuration of the second PDSCH scheduled by the second PDCCH.

It should be understood that the preset conditions listed above are only examples and should not constitute any limitation to the present application. When the protocol defines one or more conditions as preset conditions, the terminal device and the network device may determine whether the first resource needs to be re-determined according to the first PDCCH and the second PDCCH based on the same preset conditions.

With reference to the first aspect or the second aspect, in some possible implementations, the first PDCCH is located before the second PDCCH in a time domain.

That is, the terminal device may determine the first PDCCH and the second PDCCH according to the time sequence of the received PDCCHs. The terminal device may determine a PDCCH received first as a first PDCCH, and may determine a PDCCH received later as a second PDCCH.

With reference to the first aspect or the second aspect, in some possible implementations, a mapping type of a time domain resource location of the first PDSCH is type a; and the mapping type of the time domain resource position of the second PDSCH scheduled by the second PDCCH is type B.

That is, the terminal device may determine the first PDCCH and the second PDCCH according to a mapping type of a time domain resource location of the PDSCH indicated in the PDCCH. The terminal device may determine, as the first PDCCH, a PDCCH corresponding to a PDSCH whose mapping type of the time domain resource location of the PDSCH is type a, and may determine, as the second PDCCH, a PDCCH corresponding to a PDSCH whose mapping type of the time domain resource location of the PDSCH is type B.

Specific contents regarding type a and type B may refer to the prior art, for example, refer to the relevant description in NR protocols TS38.211 and TS 38.214. For brevity, detailed descriptions of type a and type B are omitted herein.

With reference to the first aspect or the second aspect, in some possible implementation manners, the starting symbol of the downlink DMRS of the first PDSCH is the 2 nd or 3 rd symbol of the time slot in which the first PDSCH is located; and the starting symbol of the downlink DMRS of the second PDSCH scheduled by the second PDCCH is the first symbol of the second PDSCH.

That is, the terminal device may determine the first PDCCH and the second PDCCH from a starting symbol of the DMRS in a time domain. The terminal device may determine, as the first PDCCH, a PDCCH corresponding to a PDSCH whose starting symbol of the DMRS is located in the 2 nd or 3 rd symbol of the time slot in which the PDSCH is located, and may determine, as the second PDCCH, a PDCCH corresponding to a PDSCH whose starting symbol of the DMRS is located in the first symbol of the PDSCH.

Based on the above-listed methods, the terminal device may determine which PDCCH is the first PDCCH and which PDCCH is the second PDCCH, and may then determine the first resource for transmitting the first data based on the first PDCCH and the second PDCCH.

With reference to the first aspect, in some possible implementations, the method further includes: determining a second PDSCH according to the second PDCCH; second data is received on the second PDSCH.

The terminal device and the network device may transmit second data based on the second PDSCH scheduled by the second PDCCH. The second data may be data of an emergency service. That is, the method and the device can preferentially ensure normal transmission of the emergency service data so as to ensure the reliability and low time delay of the transmission of the emergency service.

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

In a fourth 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 fifth aspect, a communication device is provided, which comprises various modules or units for performing the method of any one of the possible implementations of the second aspect.

In a sixth aspect, a communications apparatus is provided that includes a processor. The processor is coupled to the memory and is operable to execute the instructions in the memory to implement the method of any one of the possible implementations of the second 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 network device. When the communication device is a network 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 network device. When the communication device is a chip configured in a network device, the communication interface may be an input/output interface.

In a seventh aspect, a processor is provided, including: input circuit, output circuit and processing circuit. The processing circuitry is configured to receive signals via the input circuitry and to transmit signals via the output circuitry, such that the processor performs the method of the first or second aspect and any possible implementation of the first or second 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 an eighth 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 to receive signals via the receiver and transmit signals via the transmitter to perform the method of the first or second aspect and any possible implementation of the first or second 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 above eighth aspect may be a chip, the processor may be implemented by hardware or may be implemented by 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 ninth aspect, there is provided a computer program product, the computer program product comprising: a computer program (which may also be 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 or second aspect and aspects described above.

A tenth aspect provides a computer-readable medium storing a computer program (which may also be referred to as code, or instructions) which, when run on a computer, causes the computer to perform the method of any of the above-described first or second aspects and possible implementations of the first or second aspects.

In an eleventh aspect, a communication system is provided, which includes the foregoing network device and terminal device.

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 to 5 are schematic diagrams of resource locations of a first PDSCH, a second PDCCH and a second PDSCH provided in an embodiment of the present application;

fig. 6 is a schematic block diagram of a communication device provided by an embodiment of the present application;

fig. 7 is a schematic structural diagram of a terminal device provided in an embodiment of the present application;

fig. 8 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 (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) system, or a New Radio (NR), etc.

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 NodeB, or Home Node B, HNB), BaseBand Unit (BaseBand 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, a), one or a group (including multiple antenna panels) of Base stations in a 5G system, or may also be a Network panel forming a gbb or a transmission Point, such as a BaseBand Node (BBU) or a BBU, distributed Units (DUs), and the like.

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 the function of a Radio Resource Control (RRC) layer, a Packet Data Convergence Protocol (PDCP) layer, and the DU implements the function of a Radio Link Control (RLC), a Medium Access Control (MAC), and a Physical (PHY) layer. 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 telemedicine (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. Control resource set (CORESET) and control resource set group (CORESET): 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 the LTE protocol, 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 set included in the control resource set group may be configured, for example, by a higher layer parameter, for example, by a PDCCH configuration information element (PDCCH-configuration element, PDCCH-configuration ie), or by a ControlResourceSet information element, which is not limited in this application.

2. 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, this set of search spaces may also be referred to as Search Spaces (SS). 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 SearchSpaceinformation 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.

3. 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.

4. 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 add list) and a control resource set release list (control resource set release list). 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.

5. Cell (cell) and cell group (cell group): a cell may also be referred to as a serving cell (serving cell). A cell may be understood as being described by a higher layer from the point of view of resource management or mobility management or serving elements. 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 (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.

It should be noted that a cell may be an area within the coverage of the wireless network of the network device. In the embodiment of the present application, different cells may correspond to different network devices. For example, the network device in cell #1 and the network device in cell #2 may be different network devices, such as base stations. That is, cell #1 and cell #2 may be managed by different base stations, and in this case, it may be referred to that cell #1 and cell #2 are co-sited, or co-sited. The network device in the cell #1 and the network device in the cell #2 may also be different radio frequency processing units of the same base station, for example, Radio Remote Units (RRUs), that is, the cell #1 and the cell #2 may be managed by the same base station, have the same baseband processing unit and intermediate frequency processing unit, but have different radio frequency processing units. This is not a particular limitation in the present application.

The terminal device may acquire the cell identity in advance. The network device may indicate the cell identity to the terminal device via high-level signaling. For example, the terminal device may acquire the cell identifier during the downlink synchronization process. The present application does not limit the specific method for the terminal device to obtain the cell identifier.

A group of cells, which may also be referred to as a serving cell group. A cell group may be a set of one or more cells. The cells included in the cell group may be indicated by higher layer signaling. For example, the network device may indicate the cells included in each cell group to the terminal device through an RRC message.

In the same cell group, the backhaul link that can be established between the network devices may be an ideal backhaul (idealbackhal), and a plurality of network devices in the same cell group may cooperate with each other and perform scheduling through one Downlink Control Information (DCI). The backhaul links between network devices in different cell groups may be non-ideal backhaul (non-ideal backhaul), and the network devices in different cell groups may be scheduled by respective transmitted DCIs.

The terminal device may acquire information of the cell group in advance. For example, the terminal device may determine in advance whether cells having communication connections belong to the same cell group. The network device may indicate the cells included in the cell group to the terminal device through higher layer signaling. For example, the network device may indicate the cells included in the cell group to the terminal device through higher layer signaling, such as an RRC message.

6. Wave beam: the representation of the beams in the NR protocol may be spatial filters, or so-called spatial filters or spatial parameters. A beam used for transmitting a signal may be referred to as a transmission beam (Tx beam), or may also be referred to as a spatial domain transmit filter (spatial domain transmit filter) or a spatial transmit parameter (spatial domain transmit parameter); the beam for receiving the signal may be referred to as a reception beam (Rx beam), a spatial reception filter (spatial domain reception filter), or a spatial reception parameter (spatial domain reception parameter).

The transmission beam may refer to the distribution of signal strength formed in different spatial directions after the signal is transmitted through the antenna, and the reception beam may refer to the distribution of signal strength of the wireless signal received from the antenna in different spatial directions.

7. Beam pairing relationship: i.e. the pairing between the transmit beam and the receive beam, i.e. the pairing between the spatial transmit filter and the spatial receive filter. A large beamforming gain can be obtained for transmitting signals between the transmitting beam and the receiving beam having the beam pairing relationship.

In one implementation, a transmitting end (e.g., a network device) and a receiving end (e.g., a terminal device) may obtain a beam pairing relationship through beam training. Specifically, the transmitting end may transmit the reference signal in a beam scanning manner, and the receiving end may also receive the reference signal in a beam scanning manner. Specifically, the transmitting end may form beams with different directivities in space by means of beam forming, and may poll on a plurality of beams with different directivities to transmit the reference signal through the beams with different directivities, so that the power of the reference signal transmitted in the direction in which the transmitted beam is directed may be maximized. The receiving end can also form beams with different directivities in space in a beam forming mode, and can poll on a plurality of beams with different directivities to receive the reference signal through the beams with different directivities, so that the power of the reference signal received by the receiving end can be maximized in the direction pointed by the received beam.

By traversing each transmitting beam and each receiving beam, the receiving end can perform channel measurement based on the received reference signal, and report the measured result to the transmitting end through Channel State Information (CSI). For example, the receiving end may report a part of reference signal resource with larger Reference Signal Receiving Power (RSRP) to the transmitting end, for example, report an identifier of the reference signal resource, so that the transmitting end receives and transmits signals by using a beam pairing relationship with better channel quality when transmitting data or signaling.

8. Transmission Configuration Indicator (TCI) state: may be used to indicate a quasi-co-location (QCL) relationship between two reference signals. An index (servececellindex), a bandwidth part (BWP) Identifier (ID), and a reference signal resource identifier (rs ID) of the serving cell may be included in each TCI state. The reference signal resource identifier may be at least one of the following: non-zero power (NZP) CSI-RS reference signal resource identification (NZP-CSI-RS-resource id), non-zero power CSI-RS reference signal resource set identification (NZP-CSI-RS-resource eSetId), or SSB Index (SSB-Index).

The index of the serving cell, the BWP ID, and the reference signal resource identification refer to a reference signal resource used in a beam (beam) training process and a corresponding serving cell and BWP. In the beam training process, the network equipment sends the reference signals through different transmitting beams based on different reference signal resources, so the reference signals sent through different transmitting beams can be associated with different reference signal resources; the terminal device receives the reference signal through different receiving beams based on different reference signal resources, so the reference signal received through different receiving beams can be associated with different reference signal resources. In the beam training process, the terminal device may maintain the correspondence between the index of the serving cell, the BWP ID, and the reference signal resource identifier and the receive beam, and the network device may maintain the correspondence between the index of the serving cell, the BWP ID, and the reference signal resource identifier and the transmit beam. By referring to the signal resource identification, the pairing relationship between the receiving beam and the transmitting beam can be established.

During the communication process thereafter, the terminal device may determine a receive beam based on the TCI status indicated by the network device, and the network device may determine a transmit beam based on the same TCI status.

Specifically, the network device may configure a TCI status (TCIstate) list for the terminal device through higher layer signaling (e.g., RRC message). The TCI status list may include a plurality of TCI statuses. Thereafter, the network device may activate one or more TCI states via higher layer signaling (e.g., MAC CE). The activated TCI state is a subset of the list of TCI states configured by the RRC message. Thereafter, the network device may also indicate a selected TCI status via a TCI field in physical layer signaling (e.g., DCI). The DCI may be, for example, a DCI scheduling physical downlink resources (e.g., PDSCH).

9. PDSCH configuration (PDSCH configuration): for configuring PDSCH parameters for the terminal device. The PDSCH parameters may include information such as scrambling code identification, DMRS mapping type, TCI status added list, TCI status released list, and resource allocation.

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, the 0 th symbol in a certain slot may refer to the first symbol of the slot. Of course, the specific implementation is not limited thereto. For example, the numbers may be consecutively numbered from 1. For example, the 1 st symbol in a certain slot may also refer to the first symbol of the slot. Because the starting values of the numbers are different, the numbers corresponding to the same symbol in the time slot are also 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 transmission and data provided by 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 the method of transmitting and receiving data of 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 UE independently demodulates the PDSCH scheduled by the UE according to the DCI sent by each network device; optionally, the UE feeds back Acknowledgement (ACK) information/Negative Acknowledgement (NACK) information corresponding to the PDSCH transmitted by different network devices to the corresponding network devices, respectively. That is, the UE 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 UE independently demodulates the PDSCH corresponding thereto according to each PDCCH. Optionally, the UE feeds back ACK information/NACK 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.

For example, network device #1102 of fig. 1 may transmit PDCCH #1 to terminal device 101, where PDCCH #1 may carry DCI #1, and DCI #1 may be used to schedule PDSCH #1 for terminal device 101. Network device #2103 in fig. 1 may also transmit PDCCH #2 to terminal device 101, where PDCCH #2 may carry DCI #2, and DCI #2 may be used to schedule PDSCH #2 for terminal device 101. The PDSCH #1 and PDSCH #2 may or may not overlap in resources. The network device #1102 and the network device #2103 can transmit PDSCH to the terminal devices, respectively, by the transmission mode of space division multiplexing.

However, in some cases, a network device, such as network device #1102, may urgently schedule PDSCH for the terminal device through another PDCCH based on certain emergency services, such as Ultra Reliable and Low Latency Communication (URLLC) services. The PDCCH may be referred to as PDCCH #3, for example, and the PDSCH may be referred to as PDSCH #3, for example. The PDCCH #3 may overlap with the PDSCH #1 previously scheduled by the network device #1102, and the PDSCH #3 may overlap with the PDSCH #1 previously scheduled by the network device # 1102. If the network device #1102 does not perform any processing, the terminal may be interfered by data transmitted on the PDSCH #1 when receiving the PDCCH #3 or the PDSCH #3, which may result in a decoding failure of the PDCCH #3 or the PDSCH # 3; accordingly, PDCCH #3 or PDSCH #3 may cause interference to data transmitted on PDSCH #1, resulting in degradation of the reception quality of PDSCH #1 and even decoding failure. Therefore, data transmission performance may be degraded, and system performance may be degraded.

In view of the above, the present application provides a method for transmitting and receiving data, so as to improve data transmission performance.

The following describes in detail a method for transmitting and receiving data according to an embodiment of the present application with reference to the drawings.

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

It should be noted that the method for transmitting and receiving data provided in the present application can be applied to a wireless communication system, for example, the communication system 100 shown in fig. 1. Communication devices in a communication system may have wireless communication connections between them. For example, the terminal apparatus 101 shown in fig. 1 may 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 there is an 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 the same network device group. 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 PDCCHs based on the same PDCCH configuration, and the like.

The first network device shown hereinafter may correspond to, for example, network device #1102 in fig. 1, and the second network device may correspond to, for example, network device #2103 in fig. 1. For convenience of description, the following describes in detail the method for sending and receiving data provided in the embodiment of the present application by taking the first network device and the second network device as the same network device or different network devices, respectively. It should be understood that in the embodiments shown below, the first network device and the second network device are the same network device, and alternatively, the first network device and the second network device belong to the same network device group; the first network device and the second network device are different network devices, and alternatively, the first network device and the second network device belong to different network device groups.

In step 210, the terminal device receives a first PDCCH, which may be used to schedule a first PDSCH.

For the convenience of differentiation and illustration, the PDCCH received by the terminal device in step 210 is referred to as a first PDCCH, and the PDSCH scheduled by the first PDCCH is referred to as a first PDSCH. The first PDCCH may be, for example, a PDCCH transmitted by any of the one or more network devices to the terminal device. The network device that transmits the first PDCCH is referred to as a first network device, for example. That is, in step 210, the first network device transmits a first PDCCH. That is to say, the first PDSCH is a physical downlink resource scheduled by the first network device for the terminal device through the first PDCCH.

Specifically, DCI may be transmitted on the first PDCCH. For the sake of distinction, 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 PDSCH mapping types of the first PDSCH scheduled by the first DCI.

In this embodiment, the first PDSCH may be used to transmit first data. Optionally, the first data is data of a service other than emergency service, or data of a non-emergency service, or data with a lower transmission priority. By way of example and not limitation, the first data is data of enhanced mobile bandwidth (eMBB) service.

In step 220, the terminal device receives a second PDCCH.

For the convenience of differentiation and explanation, the PDCCH received by the terminal device in step 220 is denoted as a second PDCCH, and the DCI transmitted on the second PDCCH is denoted as a second DCI. This second PDCCH may be sent by the first network device as described above based on some emergency traffic, such as URLLC traffic, scheduling resources for the terminal device urgently, or may be sent by another network device, such as the second network device.

Since the network device is transparent to the terminal device. The terminal device cannot know in advance which network device or devices send the PDCCH and PDSCH to it. For the sake of distinction and illustration, the network device that transmits the second PDCCH to the terminal device in step 220 is referred to as the second network device. That is, in step 220, the second network device transmits the second PDCCH.

It should be understood that the second network device may be the same network device as the first network device described above, or may be a different network device; the first network device and the second network device may belong to the same network device group or may belong to different network device groups. Hereinafter, a specific process of the terminal device determining whether the first network device and the second network device are the same network device or belong to the same network device group based on the method provided by the embodiment of the present application will be described in detail, and a detailed description of the specific process will be omitted for the time being.

It should also be understood that the figures are merely schematic representations, and that the first network device and the second network device are shown as two different network devices, which should not limit the present application in any way. When the first network device or the second network device is the same network device, the steps performed by the first network device and the second network device in the figure may be performed by the same network device, such as the first network device.

In step 230, the terminal device determines a first resource for transmitting first data based on the first PDCCH and the second PDCCH.

Specifically, the terminal device may determine a first resource for transmitting first data based on a first PDSCH scheduled by a first PDCCH and a second PDCCH. The first resource belongs to a first PDSCH. Alternatively, the first resource may be a part of or all of the resource in the first PDSCH. In other words, the first network device may indicate to the terminal device the resource range for transmitting the first data through the first PDCCH, and the terminal device may further determine the first resource for transmitting the first data from within the resource range in conjunction with the second PDCCH.

Optionally, the second PDCCH is used for scheduling a second PDSCH.

For the sake of distinction, the PDSCH scheduled by the second PDCCH is denoted as the second PDSCH. The DCI in the second PDCCH may include information such as a time-frequency resource, an antenna port, and a PDSCH mapping type of the second PDSCH scheduled by the DCI.

For convenience of understanding, fig. 3 to 5 are schematic views of resource distributions of the second PDCCH, the first PDSCH and the second PDSCH. It should be understood, however, that the drawings are designed for the purpose of illustration only and not as a definition of the limits of the application.

Optionally, when the second PDCCH and the first PDSCH have resource overlap, step 230 specifically includes: the terminal device determines the resources except the second PDCCH in the first PDSCH as first resources.

As shown in fig. 3, the entire resources of the second PDCCH fall within the range of the first PDSCH. It should be understood that fig. 3 is only an example, and the size and the overlapping position of the overlapping region between the second PDCCH and the first PDSCH are not limited in the present application. The resource overlapping of the second PDCCH and the first PDSCH may specifically include: part of the resources of the second PDCCH overlap with the first PDSCH, or all the resources of the second PDCCH overlap with the first PDSCH. The second PDCCH may overlap resources at a start position of the first PDSCH, may overlap resources at an end position of the first PDSCH, may overlap resources at an intermediate position of the first PDSCH, or may overlap resources at all positions of the first PDSCH. This is not limited in this application.

In the case where the second PDCCH overlaps the first PDSCH, the terminal device may determine, as the first resource, a resource of the first PDSCH excluding the second PDCCH.

In other words, when the terminal device detects the second PDCCH in the process of receiving the first PDSCH, the terminal device may determine the first resource according to the resource occupied by the first PDSCH and the resource occupied by the second PDCCH, which are indicated by the first PDCCH, receive and demodulate the first data on the determined first resource, and may receive and demodulate the second data on the second PDSCH according to the second PDCCH.

Optionally, when the second PDSCH overlaps with the first PDSCH, step 230 specifically includes: the terminal device determines the resources of the first PDSCH except the second PDSCH as the first resources.

As shown in fig. 4, the entire resources of the second PDSCH fall within the range of the first PDSCH. It should be understood that fig. 4 is only an example, and the size and the overlapping position of the overlapping region between the second PDSCH and the first PDSCH are not limited in the present application. The resource overlapping of the second PDSCH and the first PDSCH may specifically include: partial resources of the second PDSCH overlap with the first PDSCH, or all resources of the second PDSCH overlap with the first PDSCH. The second PDSCH may overlap with the start position of the first PDSCH, the end position of the first PDSCH, the middle position of the first PDSCH, or all the positions of the first PDSCH. This is not a limitation of the present application.

In the case where the second PDSCH overlaps the first PDSCH, the terminal device may determine, as the first resource, a resource of the first PDSCH excluding the second PDSCH. In other words, when the terminal device determines that the second PDSCH arrives while receiving the first PDSCH, the terminal device may determine the first resource according to the resource occupied by the first PDSCH indicated by the first PDCCH and the resource occupied by the second PDSCH indicated by the second PDCCH, may receive and demodulate the first data on the determined first resource, and may receive and demodulate the second data on the second PDSCH according to the second PDCCH.

Optionally, when the second PDCCH and the second PDSCH both overlap with the second PDCCH, step 230 specifically includes: the terminal device determines the resources of the first PDSCH except for the second PDCCH and the second PDSCH as the first resources.

As shown in fig. 5, all resources of the second PDCCH and the second PDSCH fall within the range of the first PDSCH. It should be understood that fig. 5 is only an example, and the size and the overlapping position of the overlapping region between the second PDCCH and the second PDSCH and the first PDSCH are not limited in the present application. The resource overlapping of the second PDCCH and the second PDSCH with the first PDSCH may specifically include: part of resources of the second PDCCH overlap with the first PDSCH, and part of resources of the second PDSCH overlap with the first PDSCH; or, all resources of the second PDCCH overlap with the first PDSCH, and part of the resources of the second PDSCH overlap with the first PDSCH; or, part of the resources of the second PDCCH overlap with the first PDSCH, and all the resources of the second PDSCH overlap with the first PDSCH; alternatively, all resources of the second PDCCH overlap with the first PDSCH, and all resources of the second PDSCH overlap with the first PDSCH. And, the second PDCCH may overlap with a start position of the first PDSCH, and the second PDSCH may overlap with a middle position or an end position of the first PDSCH; alternatively, the second PDCCH may overlap with resources at a middle position of the first PDSCH, the second PDSCH may overlap with a middle position or an end position of the first PDSCH, or the second PDCCH and the second PDSCH may also overlap with resources at all positions of the first PDSCH. This is not a limitation of the present application.

In a case where both the second PDCCH and the second PDSCH overlap with the second PDCCH, the terminal device may determine, as the first resource, a resource other than the second PDCCH and the second PDSCH in the first PDSCH.

In other words, the terminal device detects the second PDCCH during the process of receiving the first PDSCH, and determines that resource overlapping occurs between the second PDSCH and the first PDSCH according to the second PDCCH. The terminal device may determine the first resource according to the resource occupied by the first PDSCH indicated by the first PDCCH, the resource occupied by the second PDCCH, and the resource occupied by the second PDSCH indicated by the second PDCCH, and receive and demodulate the first data on the first resource. The terminal device may also receive and demodulate the second data on the resources occupied by the second PDSCH.

In the process of determining the first resource, the terminal device may remove a part of the first PDSCH that overlaps with the second PDCCH and/or the second PDSCH. The first resource may be a resource of the first PDSCH excluding the second PDCCH and/or the second PDSCH. This may be understood as the terminal device dropping part of the resources of the first PDSCH that overlap with the second PDCCH and/or the second PDSCH, or the terminal device dropping part of the resources of the first PDSCH.

When the terminal device discards the overlapped resources from the first PDSCH, the terminal device may use time-frequency unit as a unit, for example, Resource Block (RB) as granularity, or may use time-domain unit as a unit, for example, symbol as granularity. For example, when the first PDSCH and the second PDCCH overlap on a certain RE, the RB where the RE is located may be removed from the first PDSCH; for another example, when the first PDSCH and the second PDSCH overlap on a certain RE, the physical resource on the symbol where the RE is located may be removed from the first PDSCH.

It should be understood that the processing granularity of the resources listed here is only an example and should not constitute any limitation to the present application.

Optionally, when neither the second PDCCH nor the second PDSCH has resource overlap with the second PDCCH, step 230 specifically includes: and under the condition that neither the second PDCCH nor the second PDSCH has resource overlapping with the first PDSCH, determining the first PDSCH scheduled by the first PDCCH as the first resource.

That is, when the first PDSCH and neither the second PDCCH nor the second PDSCH have resource overlap, the first PDSCH may be determined directly according to the first PDCCH. In this case, the first resource may be all resources of the first PDSCH.

In step 240, the first network device determines a first resource for transmitting the first data.

The first network device may know in advance if the first PDCCH and the second PDCCH are transmitted by the same network device. In this case, the first network device may determine the first resources for transmitting the first data based on the method as described in step 230.

Based on the method for determining the first resource described in step 230, when determining that the first PDSCH has resource overlap with any one of the second PDCCH and the second PDSCH, the first network device may determine the resource of the first PDSCH except the resource overlap region as the first resource. The resource overlapping region may be, for example, an overlapping region of the first PDSCH and the second PDCCH, an overlapping region of the first PDSCH and the second PDSCH, or an overlapping region of the first PDSCH, the second PDCCH, and the second PDSCH. This is not a limitation of the present application.

In other words, the first network device may preferentially transmit the second PDCCH and/or the second PDSCH without transmitting the first data in the resource overlapping region.

The terminal device does not want the first PDSCH to overlap with any of the second PDCCH and/or the second PDSCH. Therefore, the first network device may avoid resource overlap of the first resource and any one of the second PDCCH and the PDSCH when scheduling the resource.

Further, there may be scheduling rules, such as the terminal device does not want the previously received PDCCH scheduled PDSCH to be received later.

For example, it is assumed that a PDCCH received by the terminal device first is a first PDCCH, and a PDCCH received later is a second PDCCH. Optionally, the terminal device does not want the starting symbol position of the second PDSCH scheduled by the second PDCCH to be earlier than the ending symbol position of the first PDSCH scheduled by the first PDCCH. Optionally, the terminal device does not want the starting symbol position of the second PDSCH scheduled by the second PDCCH to be earlier than the starting symbol position of the first PDSCH scheduled by the first PDCCH. That is, the terminal device wishes to receive the first PDSCH before the second PDSCH.

That is, the network device may perform scheduling of the first PDSCH and the second PDSCH based on the scheduling rule described above, so that the scheduled first PDSCH and the scheduled second PDSCH can satisfy the requirements described above.

If the first PDCCH and the second PDCCH are transmitted by different network devices, the first network device may also not know that other network devices are serving the terminal device. In this case, the first network device may still transmit the first data directly through the first PDSCH without re-determining the first resources for transmitting the first data according to the prior art.

In step 250, the terminal device receives first data on a first resource. Accordingly, the first network device transmits the first data on the first resource.

That is, the terminal device does not want the first resource to overlap with any of the second PDCCH and the second PDSCH regardless of whether the first network device and the second network device are the same network device. In other words, the terminal device does not want to receive the first data on the second PDCCH or on the second PDSCH simultaneously.

In other words, the terminal device may not receive the first data in the resource overlapping region to guarantee successful reception of the second PDCCH and/or the second PDSCH.

Optionally, in step 260, the terminal device receives second data on the second PDSCH.

If the first network device and the second network device are the same network device, in step 260, the first network device sends second data on the second PDSCH; if the first network device and the second network device are different network devices, then in step 260, the second network device transmits second data on the second PDSCH.

Since in NR, a plurality of services can coexist. When some traffic with high transmission priority comes, such as emergency traffic, for example, URLLC traffic, the network device may schedule resources urgently to ensure that the emergency traffic is transmitted first. In this embodiment, optionally, the second data is data of an emergency service. By way of example and not limitation, the second data is data of URLLC traffic.

It should be understood that the second data is only one possibility for emergency services, and should not constitute any limitation to the present application. The second data may also be data of non-emergency services, such as the data of the eMBB service described above.

It can be appreciated that when the first network device and the second network device are the same network device, the first network device typically does not schedule another PDSCH (e.g., the second PDSCH) to transmit data of a new eMBB traffic in case the data of the eMBB traffic that was previously scheduled for PDSCH (e.g., the first PDSCH) transmission is not complete.

When the first network device and the second network device are different network devices, the first data and the second data may also be data of different service types, or data of the same service type, which is not limited in this application. For example, the first data is data of non-emergency service, and the second data is data of emergency service. The terminal device may preferentially receive the second data when receiving the scheduling of the emergency service, thereby ensuring reliable transmission of the second data. As described above, since the terminal device preferentially receives the second PDCCH and/or the second PDSCH when the first PDSCH and any one of the second PDCCH and the second PDSCH have resource overlap, that is, preferentially receives the second data. Therefore, the successful receiving of the data of the emergency service can be ensured, and the transmission reliability is ensured.

Optionally, when the traffic types to which the data transmitted by the first PDSCH and the second PDSCH belong are both non-emergency traffic, the first PDSCH and the second PDSCH may be from different network devices or different network device groups. The first network device and the second network device may transmit different data by a transmission mode of space division multiplexing.

Since different traffic types may be associated with the mapping type of the time domain resource location of the PDSCH. Optionally, when the mapping types of the time domain resource locations of the first PDSCH and the second PDSCH are both type a, the first PDSCH and the second PDSCH may be from different network devices or different network device groups. The first network device and the second network device may transmit different data by a transmission mode of space division multiplexing.

In this case, the terminal device may determine the first PDSCH according to the first PDCCH and receive the first data on the first PDSCH; the terminal device may also determine a second PDSCH from the second PDCCH and receive second data on the second PDSCH. The terminal device may demodulate the received first data and second data, respectively.

Optionally, when the traffic types of the data transmitted by the first PDSCH and the second PDSCH are both emergency traffic, the first PDSCH and the second PDSCH may also be from different network devices. The first network device and the second network device may transmit the same data through a transmission mode of diversity transmission, i.e., the first data and the second data may be the same data.

Since different traffic types may be associated with the mapping type of the time domain resource location of the PDSCH. Optionally, when the mapping type of the time domain resource location of the first PDSCH and the mapping type of the time domain resource location of the second PDSCH are both type B, the first PDSCH and the second PDSCH may also be from different network devices or different network device groups. The first network device and the second network device may transmit the same data through a transmission mode of diversity transmission.

In this case, the terminal device may determine the first PDSCH according to the first PDCCH and receive the first data on the first PDSCH; the terminal device may also determine a second PDSCH from the second PDCCH and receive second data on the second PDSCH. The terminal device may jointly demodulate the received data.

Optionally, when the traffic types of the data transmitted by the first PDSCH and the second PDSCH are both emergency traffic, or when the mapping type of the time domain resource location of the first PDSCH and the mapping type of the time domain resource location of the second PDSCH are both type B, the first PDSCH and the second PDSCH may also be from different network devices.

The terminal device may also determine a first resource for transmitting the first data according to the first PDCCH and the second PDCCH, respectively, and receive the first data on the first resource; the terminal device may determine a second PDSCH from the second PDCCH and receive second data on the second PDSCH. The terminal device may demodulate the received first data and second data, respectively.

Or, the terminal device may further determine the first PDSCH according to the first PDCCH, and receive first data on the first PDSCH; and may determine a second PDSCH based on the second PDCCH and receive second data on the second PDSCH. The terminal device may demodulate the received first data and second data, respectively.

Optionally, when the traffic type of the data transmitted by the first PDSCH is non-emergency traffic and the traffic type of the data transmitted by the second PDSCH is emergency traffic, the first PDSCH and the second PDSCH may be from the same network device, or from the same network device group, or from different network devices in the same network device group, or from different network device groups.

Since different traffic types may be associated with the mapping type of the time domain resource location of the PDSCH. Optionally, when the mapping type of the time domain resource location of the first PDSCH is type a and the mapping type of the time domain resource location of the second PDSCH is type B, the first PDSCH and the second PDSCH may be from the same network device, or from the same network device group, or from different network devices, or from different network device groups.

In this case, the terminal device may determine a first resource for transmitting the first data according to the first PDCCH and the second PDCCH, and receive the first data on the first resource; the terminal device may determine a second PDSCH from the second PDCCH and receive second data on the second PDSCH. The terminal device may demodulate the received first data and second data, respectively.

In fact, when the first PDSCH and the second PDSCH are from different network devices, the first network device and the second network device may transmit data to the terminal device, for example, in a spatial multiplexing manner. The terminal device may receive data via different receive beams. Therefore, when the first network device and the second network device are different network devices, the first network device and the second network device may respectively send downlink data to the terminal device. In this case, the second data transmitted by the second network device may be data of non-emergency services, such as data of eMBB services; or may be data of an emergency service, such as data of URLLC service, which is not limited in this application. In other words, when the first network device and the second network device are different network devices, or when the first network device and the second network device belong to different network device groups, the second PDCCH and the second PDSCH may overlap with the first PDSCH; when the first network device and the second network device are the same network device, or when the first network device and the second network device belong to the same network device group, the terminal device does not want any one of the second PDCCH and the second PDSCH to overlap with the first PDSCH.

Optionally, step 230 further comprises: and the terminal equipment determines a first resource for transmitting first data according to the first PDCCH and the second PDCCH when the first PDCCH and the second PDCCH meet preset conditions.

Optionally, step 230 further comprises: and the terminal equipment demodulates the first PDSCH according to the first PDCCH and demodulates the second PDSCH according to the second PDCCH under the condition that the first PDCCH and the second PDCCH do not meet the preset condition.

That is, when the terminal device may determine, through a preset condition, whether the first resource used for transmitting the first data is the first PDSCH or the part of the first PDSCH excluding the second PDCCH and/or the second PDSCH. When the first PDCCH and the second PDCCH satisfy a preset condition, the terminal device may receive first data on a part of resources of the first PDSCH excluding resources overlapping with the second PDCCH and/or the second PDSCH, and receive second data on the second PDSCH; when the first PDCCH and the second PDCCH do not satisfy the preset condition, the terminal device may receive first data on the first PDSCH and receive second data on the second PDSCH.

When the terminal device removes the part of the first PDSCH that overlaps with the second PDCCH and/or the second PDSCH, it may be understood that the terminal device discards the part of the first PDSCH that overlaps with the second PDCCH and/or the second PDSCH, or the terminal device discards the part of the first PDSCH. Therefore, when the first PDCCH and the second PDCCH satisfy a preset condition, the terminal device may discard a part of resources of the first PDSCH to receive the second PDCCH and/or the second PDSCH on the discarded part of resources; otherwise, the terminal device may receive the first PDSCH and the second PDSCH separately and independently.

Optionally, the preset condition may be used to determine whether the first network device and the second network device are the same network device or the same network device group.

When the first network device and the second network device are in a non-ideal backhaul link, the first network device and the second network device may perform scheduling through their respective PDCCHs.

Therefore, when the terminal device determines that the first network device and the second network device are the same network device, it may be determined that the first PDCCH and the second PDCCH are from the same network device, that is, it may be determined that the first PDSCH and the second PDSCH are from the same network device. In this case, the terminal device does not want the first resource to overlap with any one of the second PDCCH and the second PDSCH. The terminal device may discard a portion of the resources in the first PDSCH in the manner described above in connection with step 230 and the figures to receive the second PDCCH and/or the second PDSCH on the portion of resources.

When the terminal device determines that the first network device and the second network device are different network devices, it may be determined that the first PDCCH and the second PDCCH are from different network devices, that is, it may be determined that the first PDSCH and the second PDSCH are from different network devices. In this case, the terminal device may receive data from different network devices on the first PDSCH and the second PDSCH, respectively. The first data transmitted on the first PDSCH and the second data transmitted on the second PDSCH may be independent of each other. The terminal device may decode and demodulate the received first data and second data, respectively.

It should be noted that the above description is merely for convenience of explanation, and the method of transmitting and receiving data is described based on the assumption that there is a non-ideal backhaul link between the first network device and the second network device. When the first network device and the second network device are an ideal backhaul link, the first network device and the second network device may perform scheduling through one PDCCH. In this case, the first network device and the second network device may satisfy the preset conditions listed below although they are different network devices. Therefore, whether the first network device and the second network device are the same network device described in the above embodiments may be replaced with whether the first network device and the second network device are the same network device group. For example, the first network device and the second network device are the same network device, alternatively, the first network device and the second network device are from the same network device group. For another example, the first network device and the second network device are different network devices, and the first network device and the second network device may be from different network device groups instead.

Optionally, the preset condition may be used to determine whether the first network device and the second network device are from the same network device group.

A network device group may include one or more network devices. The network devices in the same network device group may be considered as ideal backhaul, and therefore one or more 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. A non-ideal backhaul may be considered between network devices of different groups of network devices. Therefore, network devices of different network device groups can perform scheduling through respective PDCCHs.

It is to be understood that the above listing of two possible understandings of the preset conditions should not constitute any limitation to the present application. When the protocol determines to use one or more preset conditions to determine whether to determine the first resource in combination with the first PDCCH and the second PDCCH, the terminal device does not care whether the first PDCCH and the second PDCCH are from the same network device or different network devices, nor whether the first PDCCH and the second PDCCH are from the same network device group or different network device groups.

The following describes in detail whether the terminal device determines the first PDCCH and the second PDCCH satisfy the preset condition.

It should be noted that, the following listed items may be used alone or in combination to determine whether to re-determine the first resource according to the first PDCCH and the second PDCCH. The protocol may predefine the preset condition. For example, the preset condition may be one item listed below, may be a combination of a plurality of items listed below, may be other conditions than those listed below, and the present application is not limited thereto. For the sake of understanding only, several possible preset conditions are given by way of example and should not constitute any limitation to the present application.

Optionally, when the PDCCH configuration of the first PDCCH is the same as the PDCCH configuration of the second PDCCH, the terminal device determines that the first PDCCH and the second PDCCH satisfy a preset condition.

In other words, when the first PDCCH and the second PDCCH satisfy a preset condition, the first PDCCH and the second PDCCH may have the same PDCCH configuration, or the PDCCH configuration of the first PDCCH and the PDCCH configuration of the second PDCCH belong to the same PDCCH configuration.

As previously described, the PDCCH configuration may be used to determine one or more search spaces. For a terminal device, the PDCCH configuration of the PDCCH may be understood as the PDCCH configuration based on which the PDCCH is received, or the terminal device may blindly detect 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.

When the terminal device determines that the search space in which the first PDCCH is blindly detected and the search space in which the second PDCCH is blindly detected are based on the same PDCCH configuration, it may be considered that the PDCCH configuration of the first PDCCH is the same as the PDCCH configuration of the second PDCCH.

In this embodiment, different network devices may transmit PDCCH based on different PDCCH configurations. Or, each network device may correspond to one PDCCH configuration. When the first network device and the second network device are the same network device, the first PDCCH and the second PDCCH may be transmitted based on the same PDCCH configuration; when the first network device and the second network device are different network devices, the first PDCCH and the second PDCCH may be transmitted based on different PDCCH configurations, respectively.

As an embodiment, if the terminal device receives the first PDCCH and the second PDCCH based on the same PDCCH configuration, or the first network device and the second network device send the first PDCCH and the second PDCCH to the terminal device based on the same PDCCH configuration, the terminal device may determine that the first network device and the second network device are the same network device, or that the first network device and the second network device belong to the same network device group. The terminal device may further re-determine the first resource according to the first PDCCH and the second PDCCH.

If the terminal device receives the first PDCCH based on one PDCCH configuration, receives the second PDCCH based on another PDCCH configuration, or in other words, the first network device sends the first PDCCH to the terminal device based on one PDCCH configuration, and the second network device sends the second PDCCH to the terminal device based on another PDCCH configuration. The terminal device may determine that the first network device and the second network device are different network devices or that the first network device and the second network device belong to different network device groups. The terminal device may receive first data directly on the first PDSCH scheduled by the first PDCCH.

The terminal device does not want to transmit resource overlap between PDSCHs scheduled by two PDCCHs transmitted based on the same PDCCH configuration. In other words, when the PDCCH configuration corresponding to the first PDCCH is the same as the PDCCH configuration corresponding to the second PDCCH, the terminal device does not want resource overlapping between the first PDSCH scheduled by the first PDCCH and the second PDSCH scheduled by the second PDCCH.

Optionally, the first network device and the second network device belong to the same cell. That is, the same cell may configure two or more PDCCH configurations, each of which may correspond to one network device.

It should be understood that the first network device and the second network device may also be two network devices of different cells, and the above examples are only examples, and should not limit the present application in any way.

In addition, the correspondence of the network device with the PDCCH configuration may be negotiated and determined in advance. For example, the network devices may negotiate and configure a corresponding relationship between the network devices and PDCCH configurations through the backhaul link. The present application does not limit the correspondence between the network device and the PDCCH configuration and the configuration manner of the correspondence.

Optionally, when the control resource set of the first PDCCH and the control resource set of the second PDCCH belong to the same control resource set, the terminal device determines that the first PDCCH and the second PDCCH satisfy a preset condition.

In other words, when the first PDCCH and the second PDCCH satisfy a preset condition, the control resource set of the first PDCCH is the same as the control resource set of the second 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 PDCCH may be understood as a control resource set on which the PDCCH is received, or the terminal device may blindly detect the PDCCH in a search space determined by the control resource set; for a network device, a control resource set of a PDCCH may be understood as a control resource set on which the PDCCH is transmitted, or the network device may transmit the PDCCH on a portion of resources in a search space determined by the control resource set.

When the terminal device determines that the search space in which the first PDCCH is blindly detected and the search space in which the second PDCCH is blindly detected are based on the same control resource set, it may be considered that the control resource set of the first PDCCH is the same as the control resource set of the second PDCCH.

As an embodiment, if the terminal device receives the first PDCCH and the second PDCCH based on the same control resource set in the same PDCCH configuration, or the first network device and the second network device respectively send the first PDCCH and the second PDCCH based on the same control resource set in the same PDCCH configuration, the terminal device may determine that the first network device and the second network device are the same network device, or that the first network device and the second network device belong to the same network device group. The terminal device may further re-determine the first resource according to the first PDCCH and the second PDCCH.

If the terminal device receives a first PDCCH based on one control resource set and receives a second PDCCH based on another control resource set, or the first network device sends the first PDCCH to the terminal device based on one control resource set, and the second network device sends the second PDCCH to the terminal device based on another control resource set, the terminal device may determine that the first network device and the second network device are different network devices, or that the first network device and the second network device belong to different network device groups. The terminal device may receive first data directly on the first PDSCH scheduled by the first PDCCH.

Optionally, the first network device and the second network device belong to the same cell. That is, the same cell may be configured with two or more control resource sets, each of which may correspond to one network device.

Further, the correspondence of the network device to the set of control resources may be pre-negotiated. For example, the network devices may negotiate and configure their correspondence with the set of control resources via the backhaul link. The corresponding relationship between the network device and the control resource set and the configuration mode of the corresponding relationship are not limited in the present application.

Optionally, when the control resource set of the first PDCCH and the control resource set of the second PDCCH belong to the same control resource set group, the terminal device determines that the first PDCCH and the second PDCCH satisfy a preset condition.

In other words, when the first PDCCH and the second PDCCH satisfy the preset condition, the control resource set of the first PDCCH and the control resource set of the second PDCCH belong to the same resource set group.

Each network device may correspond to one or more control resource sets. That is, each network device may transmit PDCCH based on the corresponding one or set of control resources. One or more control resource sets corresponding to the same network device may be defined as a control resource set group. That is, each network device may correspond to a control resource set group. When the terminal device determines that the control resource set based on the blind detection of the search space of the first PDCCH and the control resource set based on the blind detection of the search space of the second PDCCH belong to the same control resource set group, it may be considered that the control resource set of the first PDCCH and the control resource set of the second PDCCH belong to the same control resource set group.

As an embodiment, if the terminal device receives the first PDCCH and the second PDCCH based on a control resource set in the same control resource set group, or the control resource sets on which the first network device sends the first PDCCH and the second network device sends the second PDCCH belong to the same control resource set group, the terminal device may determine that the first network device and the second network device are the same network device, or the first network device and the second network device belong to the same network device group. The terminal device may further re-determine the first resource according to the first PDCCH and the second PDCCH.

If the terminal device receives a first PDCCH based on a control resource set in one control resource set group and receives a second PDCCH based on a control resource set in another control resource set group, or the first network device sends the first PDCCH based on the control resource set in one control resource set group and the second network device sends the second PDCCH based on the control resource set in another control resource set group, the terminal device may determine that the first network device and the second network device are different network devices, or the first network device and the second network device belong to different network device groups. The terminal device may receive first data directly on the first PDSCH scheduled by the first PDCCH.

Optionally, the first network device and the second network device belong to the same cell. That is, the same cell may configure two or more control resource set groups, each of which may correspond to one network device.

In addition, the correspondence of the network device to the control resource set group may be negotiated in advance. For example, the network devices may negotiate and configure their correspondence with the control resource set group via the backhaul link. The corresponding relationship between the network device and the control resource set group and the configuration mode of the corresponding relationship are not limited in the present application.

Optionally, when the search space set of the first PDCCH and the search space set of the second PDCCH belong to the same search space set, the terminal device determines that the first PDCCH and the second PDCCH satisfy a preset condition.

In other words, when the first PDCCH and the second PDCCH satisfy a preset condition, the search space set of the first PDCCH is the same as the search space set of the second 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 a terminal device, a search space set of a PDCCH may be understood as a search space set on which the PDCCH is received, or the terminal device may blindly detect the PDCCH in a search space included in the search space set; for a network device, a search space set of a PDCCH may be understood as a search space set on which the PDCCH is transmitted, or the network device may transmit the PDCCH on a certain search space included in the search space set.

When the terminal device determines that the search space set in which the first PDCCH is blindly detected and the search space set in which the second PDCCH is blindly detected are the same search space set, it may be considered that the search space set of the first PDCCH is the same as the search space set of the second PDCCH.

The specific method for the terminal device to determine whether the first PDCCH and the second PDCCH satisfy the preset condition has been described in detail above with reference to the control resource set, and the specific method for the terminal device to determine whether the first PDCCH and the second PDCCH satisfy the preset condition based on the search space set is similar to the specific method, and for brevity, details are not repeated here.

Further, the correspondence of the network device to the set of search spaces may be negotiated in advance. For example, the network devices may negotiate and configure their correspondence with the set of search spaces via backhaul links. The corresponding relationship between the network device and the search space set and the configuration mode of the corresponding relationship are not limited in the present application.

Optionally, when the search space set of the first PDCCH and the search space set of the second PDCCH belong to the same search space set group, the terminal device determines that the first PDCCH and the second PDCCH satisfy a preset condition.

In other words, when the first PDCCH and the second PDCCH satisfy a preset condition, the search space set of the first PDCCH and the search space set of the second PDCCH belong to the same search space set group.

Each network device may correspond to one or more sets of search spaces. That is, each network device may transmit PDCCH based on the corresponding one or search space set. One or more search space sets corresponding to the same network device may be defined as a search space set group. That is, each network device may correspond to a search space set group.

When the terminal device determines that the search space set to which the search space of the first PDCCH belongs and the search space set to which the search space of the second PDCCH belongs belong to the same search space set group, it may be considered that the search space set of the first PDCCH and the search space set of the second PDCCH belong to the same search space set group.

The specific method for the terminal device to determine whether the first PDCCH and the second PDCCH satisfy the preset condition has been described in detail above with reference to the control resource set, and the specific method for the terminal device to determine whether the first PDCCH and the second PDCCH satisfy the preset condition based on the search space set is similar to the specific method, and for brevity, will not be described again here.

Further, the correspondence of the network device to the search space set group may be negotiated in advance. For example, the network devices may negotiate and configure their correspondence with the search space set group via the backhaul link. The corresponding relationship between the network device and the search space set group and the configuration mode of the corresponding relationship are not limited in the present application.

Optionally, when the port of the DMRS indicated in the first PDCCH and the port of the DMRS indicated in the second PDCCH belong to the same DMRS port group, the terminal device determines that the first PDCCH and the second PDCCH satisfy a preset condition.

In other words, when a port of a DMRS for a first PDSCH scheduled by a first PDCCH and a port of a DMRS for a second PDSCH scheduled by a second PDCCH belong to the same DMRS port group, the terminal device may determine that the first PDCCH and the second PDCCH satisfy a preset condition.

When two or more network devices serve the same terminal device, if the same port is used, interference may be caused between the two or more network devices; if the 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 that different network devices use the same port when serving the same terminal device, different network devices or different network device groups may be limited, and ports in different port groups are used to serve the same terminal device. It should be understood that each network device is not limited to using one port group.

The ports in different port groups are completely different, or there is no duplication between ports in different port groups. The ports included in each port group may be predefined, such as protocol definition, or may be indicated by the network device, such as the network device may notify the terminal device of the ports in each port group through high-layer signaling.

The network device may indicate a port of the DMRS of the scheduled PDSCH in the PDCCH. The terminal device may determine a port for demodulating a DMRS of the first PDSCH from the received first PDCCH, and may determine a port for demodulating a DMRS of the second PDSCH from the received second PDCCH.

If the terminal device determines that the port of the DMRS indicated by the first PDCCH and the port of the DMRS indicated by the second PDCCH belong to the same DMRS port group, it may be determined that the first network device and the second network device are the same network device, or that the first network device and the second network device are from the same network device group. The terminal device may further re-determine the first resource according to the first PDCCH and the second PDCCH.

If the terminal device determines that the port of the DMRS indicated by the first PDCCH and the port of the DMRS indicated by the second PDCCH belong to different DMRS port groups, it may be determined that the first network device and the second network device are different network devices, or that the first network device and the second network device belong to different network device groups. The terminal device may receive first data directly on the first PDSCH scheduled by the first PDCCH.

Optionally, when the first PDCCH and the second PDCCH are from the same cell, the terminal device determines that the first PDCCH and the second PDCCH satisfy a preset condition.

In other words, when the first PDCCH and the second PDCCH satisfy a preset condition, the first PDCCH and the second PDCCH may be from the same cell; in other words, the first network device transmitting the first PDCCH and the second network device transmitting the second PDCCH may be from the same cell.

In the NR protocol, serving cell configuration (serving cell configuration) may be used to configure a serving cell for a terminal device. The serving cell configuration may include a set of bandwidth portion downlink Dedicated parameters (BWP downlink Dedicated, BWP DL Dedicated). The BWP downlink dedicated parameter may include a PDCCH configuration. In other words, one cell may correspond to one PDCCH configuration.

When receiving the first PDCCH and the second PDCCH, the terminal device may determine whether the first network device and the second network device are from the same cell according to whether the PDCCH configurations based on the first PDCCH and the second PDCCH are the same. While there may be an ideal backhaul between two network devices in the same cell. Therefore, if the terminal device determines that the first PDCCH and the second PDCCH are from the same cell, it may be determined that the first network device and the second network device are the same network device, or that the first network device and the second network device belong to the same network device group. The terminal device may further re-determine the first resource according to the first PDCCH and the second PDCCH.

On the contrary, if the terminal device determines that the first PDCCH and the second PDCCH are from different cells, it may be determined that the first network device and the second network device are different network devices, or that the first network device and the second network device belong to different network device groups. The terminal device may receive first data directly on the first PDSCH scheduled by the first PDCCH. Optionally, when the first PDCCH and the second PDCCH are from the same cell group, the terminal device determines that the first PDCCH and the second PDCCH satisfy a preset condition.

A cell group may include one or more cells. There may be ideal backhaul links between network devices in the same cell group. Therefore, when receiving the first PDCCH and the second PDCCH, the terminal device may determine the cells from which the PDCCHs are received according to the PDCCH configuration based on which the PDCCHs are received, and may further determine whether the cell from which the first PDCCH is received and the cell from which the second PDCCH is received belong to the same cell group.

If the terminal device determines that the first PDCCH and the second PDCCH are from the same cell group, it may be determined that the first network device and the second network device are the same network device, or that the first network device and the second network device belong to the same network device group. The terminal device may further re-determine the first resource according to the first PDCCH and the second PDCCH.

If the terminal device determines that the first PDCCH and the second PDCCH are from different cell groups, it may be determined that the first network device and the second network device are different network devices, or that the first network device and the second network device belong to different network device groups. The terminal device may receive first data directly on the first PDSCH scheduled by the first PDCCH. Optionally, when the first PDCCH and the second PDCCH are both primary PDCCHs, the terminal device determines that the first PDCCH and the second PDCCH satisfy a preset condition.

Based on the difference in content contained in DCI, DCI may be classified into main DCI and auxiliary DCI. A PDCCH for transmitting the main DCI corresponding to the main DCI may be referred to as a main PDCCH. 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. In other words, the secondary DCI includes only the indication field included in the partial primary DCI, i.e., the primary DCI includes 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. The secondary DCI may include a DCI of at least one of: resource allocation (resource allocation), Modulation and Coding Scheme (MCS), Redundancy Version (RV), New Data Indicator (NDI), and hybrid automatic repeat request (HARQ) process ID.

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 one implementation, the emergency traffic is transmitted by the primary station. I.e., PDSCH transmission scheduled by the primary PDCCH and scheduled by the primary PDCCH. Therefore, when the first PDCCH and the second PDCCH received by the terminal device are both primary PDCCHs, it may be determined that the first PDCCH and the second PDCCH are from the same network device or the same network device group. And the second PDCCH is used for scheduling of emergency services.

Optionally, when the receiving beam of the first PDSCH scheduled by the first PDCCH and the receiving beam of the second PDSCH scheduled by the second PDCCH are in the same receiving beam group, the terminal device determines that the first PDCCH and the second PDCCH satisfy a preset condition.

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.

As described above, the network device may carry a TCI in the DCI, and indicate a selected TCI state through the TCI, where each TCI state may include an identifier for determining a reference signal resource for receiving a PDSCH. 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 receiving beam according to the identifier of the reference signal resource indicated in the TCI state, and receive the PDCCH from the network device through the receiving beam corresponding to the reference signal resource. When the terminal device receives the first PDCCH and receives the second PDCCH, the terminal device transmits the first PDCCH in a first DCI format, and transmits the second PDCCH in a second DCI format, and the second PDCCH transmits the second DCI format, and the terminal device receives the second PDCCH in the second DCI format. At this time, the first network device and the second network device may be considered to be the same network device, or the first network device and the second network device belong to the same network device group. When the reception beam used by the terminal device to receive the first PDCCH and the reception beam used to receive the second PDCCH belong to different reception beam groups, the reference signal resource contained in the TCI state indicated by the TCI in the first DCI and the reference signal resource contained in the TCI state indicated by the TCI in the second DCI belong to different reference signal resource groups. At this time, the first network device and the second network device may be considered to be different network devices, or the first network device and the second network device may belong to different network device groups.

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. When the antenna panel indicated in the TCI state indicated by the TCI in the first TCI and the antenna panel indicated by the TCI state indicated by the TCI in the second DCI are the same antenna panel, the first network device and the second network device may be considered to be the same network device. When the antenna panel indicated in the TCI state indicated by the TCI in the first TCI is a different antenna panel than the antenna panel indicated in the TCI state indicated by the TCI in the second DCI, the first network device and the second network device may be considered different network devices.

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 determination of whether the first PDCCH and the second PDCCH are from the same network device or the same network device group by distinguishing different reception beam groups with reference to the signal resource and the antenna panel is merely one possible implementation manner for determining whether the first network device and the second network device are the same network device or the same network device group, and should not constitute any limitation to the present application. This application does not exclude the possibility of using other ways to distinguish between different groups of received beams.

It should be understood that the above-mentioned "the reception beam of the first PDSCH scheduled by the first PDCCH is the same reception beam group as the reception beam of the second PDSCH scheduled by the second PDCCH" may be considered equivalent to "the transmission beam of the first PDSCH is the same transmission beam group as the transmission beam of the second PDSCH". 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.

Optionally, when the receiving beam of the first PDCCH and the receiving beam of the second PDCCH are in the same receiving beam group, the terminal device determines that the first PDCCH and the second PDCCH satisfy a preset condition.

The method of receiving a beam group and determining whether it is the same has been described above in detail. For brevity, no further description is provided herein.

When transmitting the PDCCH, the network device may activate a TCI state in 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.

When the receiving beams of the first PDCCH and the second PDCCH belong to the same receiving beam group, the first network device and the second network device may be considered to be the same network device, or the first network device and the second network device belong to the same network device group.

It should be understood that "the reception beam of the first PDCCH is the same reception beam set as the reception beam of the second PDCCH" may be considered equivalent to "the transmission beam of the first PDCCH is the same transmission beam set as the transmission beam of the second PDCCH". The correspondence between the transmit beam group and the receive beam group has been described in detail above, and for brevity, no further description is given here.

Optionally, when the PDSCH configuration of the first PDSCH scheduled by the first PDCCH is the same as the PDSCH configuration of the second PDSCH scheduled by the second PDCCH, the terminal device determines that the first PDCCH and the second PDCCH satisfy a preset condition.

The network device may indicate a PDSCH configuration of the scheduled PDSCH in the DCI when the PDSCH is scheduled through the DCI. When the terminal device may determine the PDSCH configuration of the first PDSCH according to the first PDCCH, and may determine the PDSCH configuration of the second PDSCH according to the second PDCCH. If the PDSCH configuration of the first PDSCH is the same as the PDSCH configuration of the second PDSCH, the first PDCCH and the second PDCCH may be considered to satisfy a preset condition. The terminal device may re-determine the first resource according to the first PDCCH and the second PDCCH. If the PDSCH configuration of the first PDSCH is different from the PDSCH configuration of the second PDSCH, the terminal device may determine that the first PDCCH and the second PDCCH do not satisfy the preset condition. And the terminal equipment directly receives the first data scene on the first PDSCH scheduled by the first PDCCH.

Various implementations for determining whether the first PDCCH and the second PDCCH satisfy the preset condition are listed above, but it should be understood that this should not constitute any limitation to the present application. For example, the preset condition is not limited to the above list, for example, two or more items listed above may be used in combination, such as the PDCCH configuration of the first PDCCH is the same as the PDCCH configuration of the second PDCCH, and the receive beam of the first PDSCH scheduled by the first PDCCH and the receive beam of the second PDSCH scheduled by the second PDCCH are the same receive beam group, which is listed here for brevity. The preset conditions may also include other conditions, and those skilled in the art may substitute or modify the above-listed conditions based on the same concept, and may obtain more possible conditions. These conditions are all intended to fall within the scope of protection of the present application.

After determining that the first PDCCH and the second PDCCH satisfy the preset condition, the terminal device may determine, in step 240, to determine the first resource according to the first PDCCH and the second PDCCH.

After receiving the first PDCCH and the second PDCCH, the terminal device cannot determine which PDCCH is the first PDCCH and which PDCCH is the second PDCCH. In this embodiment, the terminal device may determine the first PDCCH and the second PDCCH according to a preset rule, and further determine the first resource.

Optionally, the first PDCCH precedes the second PDCCH in the time domain, or a starting symbol of the first PDCCH is earlier than a starting symbol of the second PDCCH.

That is to say, the terminal device may determine which is the first PDCCH and which is the second PDCCH according to the time sequence of receiving the PDCCHs, and then determine the first resource according to the first PDCCH and the second PDCCH.

The first PDCCH is located before the second PDCCH in the time domain, which may mean that the terminal device receives the first PDCCH before the second PDCCH.

Optionally, the mapping type of the time domain resource location of the first PDSCH is type a; the mapping type of the time domain resource location of the second PDSCH is type B.

When the network device schedules the PDSCH, the mapping type of the time domain resource location of the scheduled PDSCH may be indicated by DCI in the PDCCH. When in the NR protocol, the mapping type may include type a and type B. In some implementations, type a may be applicable to services with lower requirements for reliability and latency, for example, may be applicable to the non-emergency services described above, such as the eMBB service; type B may be applicable to services with high reliability and latency requirements, for example, may be applicable to the emergency services described above, such as URLLC services. Specific contents regarding type a and type B may refer to the prior art, for example, refer to the relevant description in NR protocols TS38.211 and TS 38.214. For brevity, a detailed description of the specific mapping manner of the type a and the type B is omitted here.

In this embodiment, optionally, the first PDSCH is used to transmit first data, the second PDSCH is used to transmit second data, and the first data may be data of non-emergency traffic; the second data may be data of emergency services.

The terminal device may determine which PDCCH is a first PDCCH for scheduling and transmitting first data and which PDCCH is a second PDCCH for scheduling and transmitting second data according to a mapping type of a time domain resource location of the PDSCH indicated in the received PDCCH, and then determine the first resource according to the first PDCCH and the second PDCCH.

Optionally, the starting symbol of the downlink DMRS of the first PDSCH is the 2 nd or 3 rd symbol of the time slot in which the first PDSCH is located; and the starting symbol of the downlink DMRS of the second PDSCH scheduled by the second PDCCH is the first symbol of the second PDSCH.

The mapping position of the downlink DMRS on the time domain is related to the mapping type of the time domain resource position of the PDSCH. For example, when the mapping type of the time domain resource location of the PDSCH is type a, the starting symbol of the downlink DMRS may be the 2 nd or 3 rd symbol of the time slot in which the PDSCH is located; when the mapping type of the time domain resource location of the PDSCH is type B, the starting symbol of the downlink DMRS may be the first symbol of the PDSCH.

Therefore, the terminal device may determine a mapping type of a time domain resource location of a received PDCCH-scheduled PDSCH according to a time domain location of a DMRS indicated in a PDCCH, and may further determine which PDCCH is a first PDCCH for scheduling and transmitting first data and which PDCCH is a second PDCCH for scheduling and transmitting second data, thereby determining the first resource according to the first PDCCH and the second PDCCH.

Based on the above listed rules, the terminal device may determine the first PDCCH and the second PDCCH, and then determine the first resource according to the first PDCCH and the second PDCCH.

It should be understood that the method for the terminal device to determine the first PDCCH and the second PDCCH is not limited to the foregoing description, and for brevity, the description is not repeated. Many more possible implementations will occur to those skilled in the art based on the same concept.

Therefore, in the embodiment of the present application, a first resource for transmitting first data is determined based on a first PDCCH and a second PDCCH, and when a first PDSCH scheduled by the first PDCCH overlaps with a second PDCCH or a second PDSCH transmission resource scheduled by the second PDCCH, the second PDCCH is preferentially received, and according to the priority of the traffic type, under the condition that the priority of the second data is higher, the second data transmitted on the second PDSCH is preferentially received, so as to ensure reliable transmission of the second data.

In contrast, if the terminal device has resource overlap between the first PDSCH and the second PDCCH, when the terminal device receives the first PDSCH and the second PDCCH, the first PDSCH and the second PDCCH may interfere with each other, which may cause a reduction in reception quality and may even cause a decoding failure. If the first PDSCH and the second PDSCH have resource overlap, the reception quality of the first PDSCH and the second PDSCH may be degraded for the same reason, and decoding may even fail. Therefore, data transmission performance is degraded.

Even if the network device does not transmit the first PDSCH on the resource overlapping with the second PDSCH and/or the second PDCCH in order to ensure the performance of the emergency service in the second PDSCH, the terminal device may still receive data on the first PDSCH because the terminal device does not know in advance, so that the terminal device still cannot successfully acquire the first PDSCH and the second PDSCH.

In the embodiment of the present application, the terminal device may determine the first resource for transmitting the first data based on the first PDCCH and the second PDCCH, so as to remove the resource overlapped with the second PDCCH and/or the second PDSCH from the first PDSCH, which may avoid a problem of data transmission quality degradation caused by mutual interference, ensure reliability of emergency data, and be beneficial to improving data transmission performance.

In addition, the terminal device may further determine whether the first PDSCH and the second PDSCH can be received simultaneously according to a preset condition, so as to fully utilize resources, for example, different data may be transmitted by way of space division multiplexing. The resource utilization rate is improved, and the system performance is improved.

It should be understood that the above has described the method of transmitting and receiving data in detail, taking the first and second PDCCHs and the first and second PDSCHs scheduled by the first PDCCH as an example, only for convenience of understanding. This should not be construed as limiting the application in any way. The terminal device may receive more PDCCHs and PDSCHs. The terminal device, upon receiving the scheduling of multiple PDCCHs, can still determine resources and receive data based on the method described above. The number of PDCCHs and the number of PDSCHs received by the terminal device are not limited, and the number of network devices serving the terminal device is also not limited.

The method provided by the embodiment of the present application is described in detail above with reference to fig. 2 to 5. Hereinafter, the communication device according to the embodiment of the present application will be described in detail with reference to fig. 6 to 8.

Fig. 6 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, 220, 250 and 260 in the method 200, and the processing unit 1200 may be used to execute the step 230 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. 7, and the processing unit 1200 in the communication apparatus 1000 may correspond to the processor 2010 in the terminal device 2000 shown in fig. 7.

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, and may be, for example, a network device or a chip configured in a network device.

In another possible design, the communication apparatus 500 may correspond to the network device in the above method embodiment, and may be, for example, a network device or a chip configured in a 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 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 used to execute the method 200 in fig. 2, the communication unit 1100 may be used to execute the steps 210 and 250 in the method 200, or alternatively, the processing unit 1200 may be used to execute the steps 210, 220, 240 and 250 in the method 200.

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. 8, and the processing unit 1200 in the communication apparatus 1000 may correspond to the processor 3100 in the network device 3000 shown in fig. 8.

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. 7 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. 6.

The transceiver 2020 may correspond to the communication unit in fig. 6, and may also be referred to as a transceiver unit. The transceiver 2020 may include a receiver (or receiver, receiving circuit) and a transmitter (or transmitter, transmitting circuit). 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. 7 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. 8 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. 6. 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 is a control center of the base station, and may also be referred to as a processing unit, and may correspond to the processing unit 1100 in fig. 6, and is mainly used for completing baseband processing functions, such as channel coding, multiplexing, modulation, spreading, and the like. For example, the BBU (processing unit) may be configured to control the base station to perform an operation procedure related to the network device in the foregoing method embodiment, for example, to generate the foregoing indication information.

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 base station 3000 shown in fig. 8 is capable of implementing various processes involving network devices 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 controller (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 first Physical Downlink Control Channel (PDCCH), wherein the first PDCCH is used for scheduling a first Physical Downlink Shared Channel (PDSCH), and the first PDSCH is used for transmitting first data;

receiving a second PDCCH;

determining a first resource for transmitting the first data based on the first PDCCH and the second PDCCH, wherein the first resource is a part of or all of resources of the first PDSCH;

receiving the first data on the first resource.

2. The method of claim 1, wherein the determining the first resource for transmitting the first data based on the first PDCCH and the second PDCCH in a case where resource overlap occurs between the second PDCCH and the first PDSCH comprises:

determining a resource other than the second PDCCH in the first PDSCH scheduled by the first PDCCH as the first resource.

3. The method of claim 1, wherein the second PDCCH is used to schedule a second PDSCH, and wherein the determining the first resources for transmitting the first data based on the first PDCCH and the second PDCCH if the second PDSCH has resource overlap with the first PDSCH comprises:

determining resources of the first PDSCH other than the second PDSCH as the first resources.

4. The method of claim 1, wherein the second PDCCH is used to schedule a second PDSCH, and wherein the determining the first resources for transmitting the first data based on the first PDSCH and the second PDCCH if the second PDCCH and the second PDSCH both have resource overlap with the first PDSCH comprises:

determining, as the first resource, a resource of the first PDSCH scheduled by the first PDCCH except for the second PDCCH and the second PDSCH.

5. The method of claim 1, wherein the second PDCCH is used to schedule a second PDSCH, and wherein the determining the first resources for transmitting the first data based on the first PDSCH and the second PDCCH if neither the second PDCCH nor the second PDSCH has resource overlap with the first PDSCH comprises:

determining the first PDSCH scheduled by the first PDCCH as the first resource.

6. The method of any one of claims 1-5, wherein the determining the first resource for transmitting the first data based on the first PDCCH and the second PDCCH comprises:

determining the first resource for transmitting the first data according to the first PDSCH and the second PDCCH when the first PDCCH and the second PDCCH meet a preset condition.

7. The method of claim 1, wherein the determining a first resource for transmitting the first data based on the first PDCCH and the second PDCCH comprises:

and determining the first resource for transmitting the first data according to the first PDCCH when the first PDCCH and the second PDCCH do not meet a preset condition.

8. The method of claim 6 or 7, wherein the preset conditions include one or more of:

the PDCCH configuration of the first PDCCH is the same as the PDCCH configuration of the second PDCCH;

a port of a demodulation reference signal (DMRS) indicated in the first PDCCH and a port of a DMRS indicated in the second PDCCH belong to the same DMRS port group;

the first PDCCH and the second PDCCH are from the same cell;

the first PDCCH and the second PDCCH are from the same cell group;

the first PDCCH and the second PDCCH are both primary PDCCHs;

the receiving beam of the first PDSCH scheduled by the first PDCCH and the receiving beam of the second PDSCH scheduled by the second PDCCH are the same receiving beam group;

9. The method of any one of claims 1 to 8, wherein the first PDCCH precedes the second PDCCH in a time domain.

10. The method of any one of claims 1 to 8, wherein a mapping type of time domain resource locations of the first PDSCH is type A; and the mapping type of the time domain resource position of the second PDSCH scheduled by the second PDCCH is type B.

11. The method according to any one of claims 1 to 8, wherein a starting symbol of a downlink demodulation reference signal (DMRS) of the first PDSCH is a 2 nd or 3 rd symbol of a time slot in which the first PDSCH is located; and the starting symbol of the downlink DMRS of the second PDSCH scheduled by the second PDCCH is the first symbol of the second PDSCH.

12. A method of transmitting data, comprising:

sending a first Physical Downlink Control Channel (PDCCH), wherein the first PDCCH is used for indicating and scheduling a first Physical Downlink Shared Channel (PDSCH), and the first PDSCH is used for transmitting first data;

transmitting a second PDCCH;

transmitting the first data on the first resource.

13. A communications apparatus, comprising: a communication unit, configured to receive a first physical downlink control channel PDCCH, where the first PDCCH is used to schedule a first physical downlink shared channel PDSCH, and the first PDSCH is used to transmit first data; and is further configured to receive a second PDCCH;

a processing unit, configured to determine a first resource for transmitting the first data based on the first PDCCH and the second PDCCH, where the first resource is a part or all of the first PDSCH;

the communication unit is further configured to receive the first data on the first resource.

14. The apparatus of claim 13, wherein in a case that the second PDCCH and the first PDSCH have resource overlap, the processing unit is specifically configured to determine, as the first resource, a resource other than the second PDCCH in the first PDSCH scheduled by the first PDCCH.

15. The apparatus of claim 13, wherein the second PDCCH is configured to schedule a second PDSCH, and wherein the processing unit is specifically configured to determine, as the first resource, a resource of the first PDSCH other than the second PDSCH, if the second PDSCH and the first PDSCH have resource overlap.

16. The apparatus of claim 13, wherein the second PDCCH is configured to schedule a second PDSCH, and wherein the processing unit is specifically configured to determine, as the first resource, a resource other than the second PDCCH and the second PDSCH in the first PDSCH scheduled by the first PDCCH, when the second PDCCH and the second PDSCH both overlap with the first PDSCH in terms of resources.

17. The apparatus of claim 13, wherein the second PDCCH is configured to schedule a second PDSCH, and wherein the processing unit is specifically configured to determine the first PDSCH scheduled by the first PDCCH as the first resource if neither the second PDCCH nor the second PDSCH has resource overlap with the first PDSCH.

18. The apparatus according to any one of claims 13 to 17, wherein the processing unit is specifically configured to determine the first resource for transmitting the first data according to the first PDSCH and the second PDCCH when the first PDCCH and the second PDCCH satisfy a preset condition.

19. The apparatus of claim 13, wherein the processing unit is specifically configured to determine the first resource for transmitting the first data according to the first PDCCH when the first PDCCH and the second PDCCH do not satisfy a preset condition.

20. The apparatus of claim 18 or 19, wherein the preset conditions comprise one or more of:

the first PDCCH and the second PDCCH are from the same cell;

the first PDCCH and the second PDCCH are from the same cell group;

the first PDCCH and the second PDCCH are both primary PDCCHs;

21. The apparatus of any one of claims 13-20, wherein the first PDCCH precedes the second PDCCH in a time domain.

22. The apparatus of any one of claims 13-20, wherein a mapping type of time domain resource locations of the first PDSCH is type a; and the mapping type of the time domain resource position of the second PDSCH scheduled by the second PDCCH is type B.

23. The apparatus according to any one of claims 13 to 20, wherein a starting symbol of a downlink demodulation reference signal, DMRS, of the first PDSCH is a 2 nd or 3 rd symbol of a slot in which the first PDSCH is located; and the starting symbol of the downlink DMRS of the second PDSCH scheduled by the second PDCCH is the first symbol of the second PDSCH.

24. A communications apparatus, comprising:

a communication unit, configured to send a first physical downlink control channel PDCCH, where the first PDCCH is used to instruct scheduling of a first physical downlink shared channel PDSCH, and the first PDSCH is used to transmit first data; and is used for the generation of the second PDCCH;

the communication unit is further configured to transmit the first data on the first resource.

25. A communications apparatus comprising at least one processor configured to perform the method of any of claims 1-12.

26. 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 12.