WO2024160143A1 - Procédé et appareil de communication - Google Patents

Procédé et appareil de communication Download PDF

Info

Publication number
WO2024160143A1
WO2024160143A1 PCT/CN2024/074214 CN2024074214W WO2024160143A1 WO 2024160143 A1 WO2024160143 A1 WO 2024160143A1 CN 2024074214 W CN2024074214 W CN 2024074214W WO 2024160143 A1 WO2024160143 A1 WO 2024160143A1
Authority
WO
WIPO (PCT)
Prior art keywords
dci
cell
candidate pdcch
candidate
pdcch
Prior art date
Application number
PCT/CN2024/074214
Other languages
English (en)
Chinese (zh)
Inventor
高飞
花梦
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2024160143A1 publication Critical patent/WO2024160143A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1273—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of downlink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling

Definitions

  • the present application relates to the field of communication technology, and in particular to a communication method and device.
  • CA Carrier aggregation
  • NR new radio access technology
  • PUSCH physical uplink share channel
  • UE user equipment
  • 3rd generation partnership project (3GPP) Rel-18 has established the use of a single DCI to schedule PDSCH or PUSCH transmission on multiple frequency bands or carriers, thereby reducing the control channel overhead and avoiding placing a physical downlink control channel (PDCCH) on each carrier.
  • 3GPP 3rd generation partnership project
  • the embodiments of the present application provide a communication method and device, which can reduce the blind detection complexity of UE, improve scheduling flexibility, and reduce the PDCCH blocking probability.
  • an embodiment of the present application provides a communication method, including: a terminal device receives configuration information sent by a network device, the configuration information is used to indicate that a first downlink control information DCI and a second DCI are simultaneously monitored on a candidate physical downlink control channel PDCCH included in a user-specific search space USS set, the first DCI is used to schedule data channels of multiple cells, and the second DCI is used to schedule a data channel of one cell; according to the configuration information, the first DCI and the second DCI are simultaneously monitored on the candidate PDCCH included in the USS set, and the candidate PDCCH corresponding to the second DCI is the same as the cell in which the candidate PDCCH corresponding to the first DCI occupies counting resources.
  • the network equipment is configured to monitor both legacy DCI and single DCI on the candidate PDCCH included in a USS set.
  • the UE can monitor both legacy DCI and single DCI on the candidate PDCCH included in the USS set. It is also stipulated that legacy DCI follows the counting method of single DCI in terms of BD/CCE counting and DCI size budget, which further constrains the scheduling method of legacy DCI, so that the cells occupied by legacy DCI and single DCI are the same, avoiding two counting methods for one USS and reducing the complexity of UE blind detection.
  • the cell in which the candidate PDCCH corresponding to the first DCI occupies counting resources is a reference cell.
  • the reference cell is a primary cell among multiple cells
  • the cell in which the candidate PDCCH corresponding to the second DCI occupies counting resources is the primary cell.
  • the second DCI is only used for self-carrier scheduling.
  • the counting resources occupied by the first DCI and the second DCI are both the primary cell, that is, only the resources of one cell are occupied.
  • the terminal device selects a search space set to be monitored from the search space set configured on the primary cell according to the PDCCH mapping rule, wherein the search space set configured on the primary cell includes at least one of the following: a user-specific search space set for receiving the first DCI, a user-specific search space set for receiving the second DCI, and a type 3 common search space set for receiving DCI for scheduling multicast.
  • the terminal device selects the candidate PDCCH configured by the network device. Screening is performed to select the number of candidate PDCCHs that need to be blindly detected within a range, thereby ensuring the feasibility of the terminal equipment.
  • the cell in which the candidate PDCCH corresponding to the first DCI occupies counting resources is a reference cell.
  • the reference cell is a secondary cell among multiple cells
  • the cell in which the candidate PDCCH corresponding to the second DCI occupies counting resources is the secondary cell. Since both the first DCI and the second DCI occupy the counting resources of the secondary cell, the scheduling of the first DCI and the second DCI in the primary cell does not occupy the counting resources of the primary cell, so the USS set does not participate in the PDCCH mapping operation of the primary cell, thereby avoiding the candidate PDCCH included in the USS set from being deleted. Without increasing the complexity of blind detection, fallback DCI and other DCI can obtain more blind detection positions, making PDCCH scheduling more flexible and reducing the probability of PDCCH blocking.
  • the terminal device sends indication information to the network device, where the indication information is used to indicate support for simultaneously monitoring the first DCI and the second DCI on the candidate PDCCH included in the USS set.
  • the indication information it is determined whether the terminal device is configured to simultaneously monitor the first DCI and the second DCI on the candidate PDCCH included in a USS set, thereby ensuring the validity of the configuration information.
  • the candidate PDCCH corresponding to the second DCI and the candidate PDCCH corresponding to the first DCI occupy counting resources including at least one of the following: a blind detection BD count, a control channel element CCE count, and a DCI size budget count.
  • an embodiment of the present application provides a communication method, including: a network device sends configuration information to a terminal device, the configuration information being used to indicate simultaneous monitoring of a first downlink control information DCI and a second DCI on a candidate physical downlink control channel PDCCH included in a user-specific search space USS set, the first DCI being used to schedule data channels of multiple cells, and the second DCI being used to schedule a data channel of one cell; sending the first DCI and the second DCI on the candidate PDCCH included in the USS set, wherein the candidate PDCCH corresponding to the second DCI is the same as the cell in which the candidate PDCCH corresponding to the first DCI occupies counting resources.
  • the network equipment is configured to monitor both legacy DCI and single DCI on the candidate PDCCH included in a USS set.
  • the UE can monitor both legacy DCI and single DCI on the candidate PDCCH included in the USS set. It is also stipulated that legacy DCI follows the counting method of single DCI in terms of BD/CCE counting and DCI size budget, which further constrains the scheduling method of legacy DCI, so that the cells occupied by legacy DCI and single DCI are the same, avoiding two counting methods for one USS and reducing the complexity of UE blind detection.
  • the cell in which the candidate PDCCH corresponding to the first DCI occupies counting resources is a reference cell.
  • the reference cell is a primary cell among multiple cells
  • the cell in which the candidate PDCCH corresponding to the second DCI occupies counting resources is the primary cell.
  • the second DCI is only used for self-carrier scheduling.
  • the counting resources occupied by the first DCI and the second DCI are both the primary cell, that is, only the resources of one cell are occupied.
  • the cell in which the candidate PDCCH corresponding to the first DCI occupies counting resources is a reference cell.
  • the reference cell is a secondary cell among multiple cells
  • the cell in which the candidate PDCCH corresponding to the second DCI occupies counting resources is the secondary cell. Since both the first DCI and the second DCI occupy the counting resources of the secondary cell, the scheduling of the first DCI and the second DCI in the primary cell does not occupy the counting resources of the primary cell, so the USS set does not participate in the PDCCH mapping operation of the primary cell, thereby avoiding the candidate PDCCH included in the USS set from being deleted. Without increasing the complexity of blind detection, fallback DCI and other DCI can obtain more blind detection positions, making PDCCH scheduling more flexible and reducing the probability of PDCCH blocking.
  • the network device receives indication information sent by the terminal device, and the indication information is used to indicate support for simultaneously monitoring the first DCI and the second DCI on the candidate PDCCH included in the USS set. Through the indication information, it is determined whether to configure the terminal device to simultaneously monitor the first DCI and the second DCI on the candidate PDCCH included in a USS set, thereby ensuring the validity of the configuration information.
  • the candidate PDCCH corresponding to the second DCI and the candidate PDCCH corresponding to the first DCI occupy counting resources including at least one of the following: a blind detection BD count, a control channel element CCE count, and a DCI size budget count.
  • an embodiment of the present application provides a communication device, including:
  • a receiving module configured to receive configuration information sent by a network device, wherein the configuration information is used to indicate to simultaneously monitor first downlink control information DCI and second DCI on a candidate physical downlink control channel PDCCH included in a user-specific search space USS set, wherein the first DCI is used to schedule data channels of multiple cells, and the second DCI is used to schedule a data channel of one cell;
  • a processing module is used to simultaneously monitor the first DCI and the second DCI on the candidate PDCCH included in the USS set according to the configuration information, wherein the candidate PDCCH corresponding to the second DCI and the candidate PDCCH corresponding to the first DCI occupy the same cell of counting resources.
  • the cell whose candidate PDCCH occupies counting resources corresponding to the first DCI is a reference cell.
  • the reference cell is a primary cell among multiple cells
  • the cell whose candidate PDCCH occupies counting resources corresponding to the second DCI is the primary cell.
  • the processing module is also used to select a search space set to be monitored from the search space set configured on the main cell according to the PDCCH mapping rule, wherein the search space set configured on the main cell includes at least one of the following: a user-specific search space set for receiving the first DCI, a user-specific search space set for receiving the second DCI, and a type 3 public search space set for receiving DCI for scheduled multicast.
  • the cell whose candidate PDCCH occupancy counting resources corresponds to the first DCI is a reference cell.
  • the reference cell is a secondary cell among multiple cells
  • the cell whose candidate PDCCH occupancy counting resources corresponds to the second DCI is the secondary cell.
  • the apparatus further includes: a sending module, configured to send indication information to the network device, wherein the indication information is used to indicate support for simultaneously monitoring the first DCI and the second DCI on the candidate PDCCH included in the USS set.
  • the candidate PDCCH corresponding to the second DCI and the candidate PDCCH corresponding to the first DCI occupy counting resources including at least one of the following: a blind detection BD count, a control channel element CCE count, and a DCI size budget count.
  • the operations and beneficial effects performed by the communication device can refer to the method and beneficial effects described in the first aspect above, and the repeated parts will not be repeated.
  • an embodiment of the present application provides a communication device, including:
  • a sending module configured to send configuration information to a terminal device, wherein the configuration information is used to indicate to simultaneously monitor first downlink control information DCI and second DCI on a candidate physical downlink control channel PDCCH included in a user-specific search space USS set, wherein the first DCI is used to schedule data channels of multiple cells, and the second DCI is used to schedule a data channel of one cell;
  • the sending module is further used to send the first DCI and the second DCI on the candidate PDCCH included in the USS set, wherein the candidate PDCCH corresponding to the second DCI and the candidate PDCCH corresponding to the first DCI occupy the same cell of counting resources.
  • the cell whose candidate PDCCH occupies counting resources corresponding to the first DCI is a reference cell.
  • the reference cell is a primary cell among multiple cells
  • the cell whose candidate PDCCH occupies counting resources corresponding to the second DCI is the primary cell.
  • the cell whose candidate PDCCH occupancy counting resources corresponds to the first DCI is a reference cell.
  • the reference cell is a secondary cell among multiple cells
  • the cell whose candidate PDCCH occupancy counting resources corresponds to the second DCI is the secondary cell.
  • the device further includes:
  • a receiving module is used to receive indication information sent by the terminal device, where the indication information is used to indicate support for simultaneously monitoring the first DCI and the second DCI on the candidate PDCCH included in the USS set.
  • the candidate PDCCH corresponding to the second DCI and the candidate PDCCH corresponding to the first DCI occupy counting resources including at least one of the following: a blind detection BD count, a control channel element CCE count, and a DCI size budget count.
  • the operations and beneficial effects performed by the communication device can refer to the method and beneficial effects described in the second aspect above, and the repeated parts will not be repeated.
  • an embodiment of the present application provides a communication device, which is configured to implement the method and functions performed by the terminal device in the first aspect above, and is implemented by hardware/software, and its hardware/software includes modules corresponding to the above functions.
  • an embodiment of the present application provides a communication device, which is configured to implement the method and functions performed by the network device in the second aspect above, and is implemented by hardware/software, and its hardware/software includes modules corresponding to the above functions.
  • the present application provides a communication device, which may be a terminal device, or a device in a terminal device, or a device that can be used in combination with a terminal device.
  • the communication device may also be a chip system.
  • the communication device may execute the method described in the first aspect.
  • the functions of the communication device may be implemented by hardware, or by hardware executing corresponding software implementations.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the module may be software and/or hardware.
  • the operations and beneficial effects performed by the communication device may refer to the methods and beneficial effects described in the first aspect above, and the repetitive parts will not be repeated.
  • the present application provides a communication device, which may be a network device, or a device in a network device, or a device that can be used in combination with a network device.
  • the communication device may also be a chip system.
  • the communication device may execute the method described in the second aspect.
  • the functions of the communication device may be implemented by hardware, or by hardware executing corresponding software implementations.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the module may be software and/or hardware.
  • the operations and beneficial effects performed by the communication device may refer to the methods and beneficial effects described in the second aspect above, and the repetitive parts will not be repeated.
  • the present application provides a communication device, comprising a processor, and when the processor calls a computer program in a memory, the method described in any one of the first aspect and the second aspect is executed.
  • the present application provides a communication device, which includes a processor and a memory, the memory being used to store a computer program; the processor being used to execute the computer program stored in the memory so that the communication device performs a method as described in any one of the first aspect and the second aspect.
  • the present application provides a computer-readable storage medium, wherein the computer-readable storage medium is used to store instructions.
  • the instruction is executed, the method described in any one of the first aspect and the second aspect is implemented.
  • the present application provides a computer program product comprising instructions, which, when executed, enables the method described in any one of the first and second aspects to be implemented.
  • an embodiment of the present application provides a communication system, which includes at least one terminal device and at least one network device, the terminal device is used to execute the steps in the above-mentioned first aspect, and the network device is used to execute the steps in the above-mentioned second aspect.
  • FIG1 is a schematic diagram of a communication system provided in an embodiment of the present application.
  • FIG2 is a schematic diagram of a carrier scheduling method
  • FIG3 is a schematic diagram of another carrier scheduling method
  • FIG4 is a schematic diagram of non-overlapping CCEs
  • FIG5 is a schematic diagram of a self-carrier scheduling method
  • FIG6 is a schematic diagram of self-carrier scheduling and cross-carrier scheduling
  • FIG7 is a schematic diagram of scheduling of a reference cell
  • FIG8 is a schematic diagram of another scheduling of reference cells
  • FIG9 is a flow chart of a communication method provided in an embodiment of the present application.
  • FIG10 is a schematic diagram of a scheduling method in which a reference cell is a primary cell
  • FIG11 is a schematic diagram of a scheduling method in which a reference cell is a secondary cell
  • FIG12 is a flow chart of another communication method provided in an embodiment of the present application.
  • FIG13 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application.
  • FIG14 is a schematic diagram of the structure of another communication device provided in an embodiment of the present application.
  • FIG15 is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application.
  • FIG. 16 is a schematic diagram of the structure of a network device provided in an embodiment of the present application.
  • Figure 1 is a schematic diagram of a communication system provided in an embodiment of the present application.
  • the communication system may include communication equipment, and communication equipment may use air interface resources for wireless communication.
  • the communication equipment may include network equipment and terminal equipment.
  • the air interface resources may include at least one of time domain resources, frequency domain resources, code resources and space resources.
  • at least one may also be described as one or more, and a plurality may be two, three, four or more, which is not limited in the present application.
  • the terminal device involved in the embodiments of the present application can also be called a terminal, which can be a device with wireless transceiver function, which can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted. It can also be deployed on the water surface (such as ships, etc.). It can also be deployed in the air (for example, on airplanes, balloons, and satellites, etc.).
  • the terminal device can be a user equipment (UE), wherein the UE includes a handheld device, a vehicle-mounted device, a wearable device, or a computing device with wireless communication function.
  • the UE can be a mobile phone, a tablet computer, or a computer with wireless transceiver function.
  • the terminal device can also be a VR terminal device, an AR terminal device, a wireless terminal in industrial control, a wireless terminal in unmanned driving, a wireless terminal in telemedicine, a wireless terminal in a smart grid, a wireless terminal in a smart city, a wireless terminal in a smart home, and the like.
  • the network devices involved in the embodiments of the present application include access network devices, such as base stations (BS), which can be a device deployed in a wireless access network that can communicate wirelessly with a terminal.
  • the base station may have multiple forms, such as a macro base station, a micro base station, a relay station, and an access point.
  • the base station involved in the embodiments of the present application may be a base station in 5G or an evolved base station (evolved Node B, eNB) in long-term evolution (LTE), wherein the base station in 5G can also be called a transmission reception point (TRP) or a 5G base station (next-generation Node B, gNB).
  • eNB evolved base station
  • LTE long-term evolution
  • TRP transmission reception point
  • gNB 5G base station
  • the device for realizing the function of the network device may be a network device; it may also be a device that can support the network device to realize the function, such as a chip system, which can be installed in the network device.
  • the device for realizing the function of the network device is a network device, and the network device is a base station as an example to describe the technical solution provided in the embodiments of the present application.
  • the technical solution provided in the embodiment of the present application can be applied to wireless communication between communication devices.
  • the wireless communication between communication devices may include: wireless communication between network devices and terminal devices, wireless communication between network devices and network devices, and wireless communication between terminal devices and terminal devices.
  • Communication In the embodiments of the present application, the term “wireless communication” may also be referred to as “communication”, and the term “communication” may also be described as "data transmission”, “information transmission” or “transmission”.
  • Cell and carrier An area of wireless coverage identified by a base station identification code or a global cell identification code.
  • a cell is an area where a base station provides wireless coverage.
  • the UE in non-carrier aggregation (CA) scenarios, the UE is generally connected to only one cell, which can be considered as the user's only serving cell.
  • the carrier is a radio signal (also called electromagnetic wave) with a specific frequency, bandwidth, and format emitted by network equipment. It is used to carry the main body of information, so it is called “carrier” or “carrier frequency”.
  • a UE may be connected to multiple cells.
  • the cell that initiates the initial access is called the primary cell (PCell), which is used by the UE to establish a radio resource control (RRC) connection with the network device.
  • the network device can configure a secondary cell (SCell) for the UE to provide additional uplink or downlink transmission resources.
  • the secondary cell can be configured through the RRC signaling of the primary cell, and can be flexibly activated/deactivated through the media access control control element (MAC CE) and/or downlink control information (DCI) signaling.
  • MAC CE media access control control element
  • DCI downlink control information
  • Carrier aggregation is a key technology to solve the problem of limited bandwidth of a single carrier.
  • Carrier aggregation aggregates two or more component carriers (CCs) to support a larger transmission bandwidth.
  • CCs component carriers
  • the multiple service cells of the UE include a primary cell and one or more secondary cells.
  • FIG. 2 is a schematic diagram of a carrier scheduling method.
  • the DCI that schedules the transmission of PDSCH or PUSCH on one carrier is also sent on the downlink carrier corresponding to the carrier or the uplink carrier. It can be understood that the DCI and the data scheduled by the DCI are on the same carrier.
  • the DCI that schedules the transmission of PDSCH or PUSCH on one carrier can be sent on another carrier or on other downlink carriers other than the downlink carrier corresponding to the uplink carrier, thereby achieving the effect that the DCI is sent on only one carrier.
  • the number of DCIs required is proportional to the number of carriers used simultaneously.
  • discrete multi-carriers based on the existing CA mechanism require more control channel resources to carry multiple DCIs.
  • the control channel overhead is increased.
  • the UE needs to blindly detect multiple DCIs, and the UE's blind detection budget will increase with the increase in the number of carriers.
  • the complexity of UE blind detection is increased.
  • 3GPP Rel-18 has established the use of a single DCI (Single DCI) to schedule PDSCH or PUSCH transmissions on multiple frequency bands or carriers, thereby reducing the overhead of the control channel and avoiding the placement of PDCCH on each carrier.
  • Figure 3 is a schematic diagram of another carrier scheduling method.
  • the use of Single DCI in discrete multi-carriers can significantly reduce the overhead of the control channel, release more downlink resources for PDSCH or PUSCH transmission, and improve downlink capacity.
  • CRC cyclic redundancy check
  • the single DCI is used to schedule data channels of one or more cells.
  • the single DCI format used to schedule uplink cell data channels can be DCI format 0_X or DCI format 0_5; the single DCI format used to schedule downlink cell data channels can be DCI format 1_X or DCI format 1_5.
  • the original intention of the single DCI design is to schedule data on multiple uplink carriers through one uplink DCI, and to schedule data on multiple downlink carriers through one downlink DCI.
  • single DCI also includes the function of legacy DCI to schedule data on one carrier, that is, single DCI can schedule data channels of one cell as well as data channels of multiple cells. Therefore, in order to distinguish it from legacy DCI, regardless of whether single DCI schedules data of multiple cells at the same time or schedules data of one cell in a real scheduling, it is understood here that single DCI is used to schedule data of multiple cells.
  • the UE needs to be scheduled by the gNB for sending uplink data and receiving downlink data.
  • the scheduling information is sent through the DCI carried by the PDCCH channel.
  • the UE does not know the exact location of the PDCCH carrying the scheduling information. Therefore, the UE performs blind detection (BD) in the search space set (SS set) within the control-resource set (CORESET).
  • BD blind detection
  • SS set search space set
  • CORESET control-resource set
  • the network device can configure the number of candidate PDCCHs. For example, the network device can configure multiple candidate PDCCHs for the UE. Not all of the multiple candidate PDCCHs carry the DCI that the UE expects to receive, that is, not all of the candidate PDCCHs carry the DCI sent to the UE. Therefore, the UE needs to attempt to decode each candidate PDCCH in the search space set to determine whether these candidate PDCCHs carry the DCI that it expects to receive. Among them, the behavior of the UE attempting to decode each candidate PDCCH in one or more search space sets according to the corresponding configuration information (such as DCI format, etc.) can be called blind detection (abbreviated as: blind detection). Monitoring DCI on a candidate PDCCH can be understood as performing blind detection on a candidate PDCCH.
  • the CRC of the DCI that the UE expects to receive is masked by the cell-radio network temporary identifier (C-RNTI).
  • C-RNTI cell-radio network temporary identifier
  • the UE can perform a cyclic redundancy check (CRC) on each candidate PDCCH in the search space set according to the C-RNTI. If the CRC succeeds, the UE determines that the DCI that it expects to receive is decoded on the candidate PDCCH. Otherwise, the UE determines that the DCI that it expects to receive is not decoded on the candidate PDCCH.
  • CRC cyclic redundancy check
  • the blind detection upper limit may refer to the maximum number of candidate PDCCHs supported by the UE for monitoring in a time slot or a time span. For example, the UE will not monitor (or will not blindly detect) candidate PDCCHs exceeding the maximum number of candidate PDCCHs monitored.
  • the blind detection upper limit may be predefined by the protocol.
  • the non-overlapping CCE upper limit may be related to information such as the subcarrier spacing and UE capabilities. For example, for a cell with a subcarrier spacing of 15kHz, the blind detection upper limit corresponding to 1 time slot is 44.
  • Control channel element (CCE), non-overlapping CCE and non-overlapping CCE limit
  • CCE is the smallest unit of resource allocation for control information, that is, resource allocation for control information is based on CCE as the smallest unit.
  • One CCE is equal to six resource element groups (REGs), and one REG is defined as one physical resource block (PRB) on one OFDM symbol.
  • REGs resource element groups
  • PRB physical resource block
  • the UE needs to perform channel estimation on the pilot inserted in the PDCCH to offset the impact of the wireless channel on the transmission signal and try to accurately restore the transmission signal of the transmitter at the receiving end.
  • the pilot sequence is located on the pattern of the #1, #5 and #9 RE on 1 RB, and the PDCCH is allocated in CCE as the minimum unit, so the number of times the UE performs PDCCH channel estimation is counted in units of CCE. For multiple overlapping CCEs, the UE only needs to perform one PDCCH channel estimation, while for multiple non-overlapping CCEs, the UE needs to perform multiple PDCCH channel estimations.
  • the counting rule of non-overlapping CCE is: the CCE count corresponding to one configured candidate PDCCH is one non-overlapping CCE; or, the CCE count corresponding to multiple or any two configured candidate PDCCHs overlapping in the time-frequency resource position is multiple or two non-overlapping CCEs, and the multiple configured candidate PDCCHs overlapping in the time-frequency resource position need to meet at least one of the two conditions.
  • the two conditions are: the CCEs corresponding to multiple configured candidate PDCCHs overlapping in the time-frequency resource position belong to different CORESETs.
  • PDCCH#1 belongs to CORESET#1
  • the aggregation level (aggregation level, AL) of PDCCH#1 is 2, that is, PDCCH#1 occupies 2 CCEs
  • candidate PDCCH#2 belongs to CORESET#2
  • the AL of PDCCH#2 is also 2, that is, PDCCH#2 also occupies 2 CCEs.
  • the four CCEs corresponding to PDCCH#1 and PDCCH#2 are non-overlapping CCEs, that is, a total of four non-overlapping CCEs.
  • the number of non-overlapping CCEs in a search space set can be understood as the number of non-overlapping CCEs corresponding to candidate PDCCHs for monitoring obtained by a search space set according to a non-overlapping CCE counting rule.
  • FIG. 4 is a schematic diagram of non-overlapping CCEs.
  • CCE 0 belongs to CORESET#0, and the reception start symbol of the PDCCH corresponding to CCE 0 is OFDM symbol #0.
  • CCE 0 and CCE 1 belong to the same CORESET, and the reception start symbol of the PDCCH corresponding to CCE 0 and CCE 1 is the same, since the two CCEs do not overlap in time-frequency resources, CCE 0 and CCE 1 are two non-overlapping CCEs.
  • CCE 0 and CCE 2 do not overlap in time-frequency resources, and there is no need to judge the two conditions, so CCE 0 and CCE 2 are two non-overlapping CCEs.
  • CCE 1 and CCE 2 overlap in time-frequency resources, but CCE 1 belongs to CORESET#0 and CCE 2 belongs to CORESET#1, CCE 1 and CCE 2 are also two non-overlapping CCEs.
  • CCE 0 and CCE 3 do not overlap in time-frequency resources, so there is no need to judge the two conditions.
  • CCE 0 and CCE 3 are two non-overlapping CCEs.
  • CCE 1 and CCE 3 are also two non-overlapping CCEs
  • CCE 2 and CCE 3 are also two non-overlapping CCEs.
  • Figure 4 includes 4 non-overlapping CCEs.
  • the non-overlapping CCE upper limit may refer to the maximum number of non-overlapping CCEs supported by the UE in a time slot or a time span. For example, the UE will not monitor (or will not blindly detect) candidate PDCCHs exceeding the maximum number of non-overlapping CCEs. Among them, the non-overlapping CCE upper limit may be predefined by the protocol. The non-overlapping CCE upper limit may be related to information such as the subcarrier spacing and UE capabilities. For example, for a cell with a subcarrier spacing of 15kHz, the non-overlapping CCE upper limit corresponding to 1 time slot is 56.
  • NR currently has 19 DCI formats, of which DCI format 0_0/0_1/1_0/1_1/0_2/1_2 is the DCI used for uplink and downlink scheduling.
  • DCI format 0_0/0_1/1_0/1_1/0_2/1_2 is the DCI used for uplink and downlink scheduling.
  • the first number represents uplink and downlink
  • "0" represents uplink
  • “1” represents downlink.
  • the second number “0” can represent fallback
  • "1” can represent non-fallback
  • or "2" represents load compression.
  • DCI format 1_0 represents the fallback DCI format for scheduling downlink data PDSCH reception
  • DCI format 1_1 represents the non-fallback DCI format for scheduling downlink data PDSCH reception
  • DCI format 0_2 represents the compressed DCI format for scheduling uplink data PDSCH transmission.
  • the characteristic of DCI format 0_0/1_0 is that most of the domain information is not affected by the high-level parameter configuration, and the bit size of the domain information is fixed. Therefore, compared with other DCI formats, the payload bits of DCI format 0_0/1_0 are relatively stable, and the communication link can be kept uninterrupted during the period of RRC parameter reconfiguration. It can be understood that DCI format 0_0/1_0 supports basic NR features for better robustness.
  • DCI format 0_1/1_1 The characteristic of DCI format 0_1/1_1 is that the size of most of the domain information of DCI will be affected by the configuration of high-level parameters (such as RRC parameters) related to different features.
  • DCI can schedule downlink multiple-input multiple-output (MIMO) dual codeword transmission to improve data transmission efficiency, or DCI can schedule CBG-level transmission to improve the hybrid automatic repeat request acknowledgment (HARQ-ACK) codebook feedback and data retransmission efficiency.
  • MIMO downlink multiple-input multiple-output
  • HARQ-ACK hybrid automatic repeat request acknowledgment
  • DCI format 0_1/1_1 is compatible with more NR features for flexibility.
  • DCI format 0_2/1_2 The characteristic of DCI format 0_2/1_2 is that the size of most field information of DCI can be directly configured through high-level parameters (such as RRC parameters), which makes the overall DCI load size relatively small and the transmission bit rate relatively low, thereby improving transmission reliability and can be used in high-reliability communication scenarios.
  • high-level parameters such as RRC parameters
  • the remaining DCI formats are DCIs for other purposes, such as DCI format 2_0 for indicating the time slot format of a group of UEs, DCI format 2_1 for notifying a group of UEs that there is no signal transmission on the indicated PRB and OFDM symbols, DCI format 3_0 for NR sidelink scheduling in one cell, DCI format 3_1 for LTE sidelink scheduling in one cell, DCI format 4_0 for broadcast PDSCH scheduling, DCI formats 4_1 and 4_2 for multicast scheduling, etc.
  • the DCI length alignment operation in this application does not involve these DCI formats and will not be described in detail.
  • NR defines a DCI length budget of "3+1" for each cell, that is, the UE monitors at most 3 DCIs scrambled by C-RNTIs of different lengths in one cell, and the total number of DCIs of different lengths is at most 4. Therefore, it can be inferred that other RNTIs except unicast scheduled DCIs (the RNTI scrambled by CRC is C-RNTI, or CS-RNTI, or MCS-C-RNTI) occupy at least 1 DCI size budget.
  • the PDCCH configuration information sent by the base station to the UE needs to meet both conditions of "3+1" after the DCI length alignment rule (DCI size alignment), otherwise the UE will consider this PDCCH configuration to be an invalid configuration, and no requirements are made for the UE behavior protocol. For example, the UE can monitor one or some DCI formats in the PDCCH configuration that are identified as invalid, or not monitor the PDCCH at all.
  • FIG. 5 is a schematic diagram of the self-carrier scheduling method.
  • CC1 self-carrier schedules CC1, then there is a "3+1" DCI length margin for CC1, and all DCI configured on CC1 need to meet the "3+1" constraint.
  • Figure 6 is a schematic diagram of self-carrier scheduling and cross-carrier scheduling.
  • CC1 self-carrier schedules CC1, and CC1 cross-carrier schedules CC2. There are "3+1" constraints for CC1 and CC2 respectively.
  • the RAN1#111 meeting defined single DCI BD/CCE counting cells and DCI size counting cells as reference cells.
  • the definition of reference cells is divided into the following two scenarios:
  • the cell set is a set of cells that can be scheduled by single DCI.
  • Figure 7 is a scheduling diagram of a reference cell.
  • the cell set includes PCell (cell index is 0), SCell#1 (secondary cell 1, cell index is 1) and SCell#2 (secondary cell 2, cell index is 2).
  • the base station can configure the cell set to which the UE belongs to be associated with USS#1 through high-level parameters (such as RRC parameters).
  • the single DCI monitored by the UE in USS#1 can schedule any combination of cells included in the cell set.
  • PCell, SCell#1 and SCell#2 can be scheduled at the same time, or SCell#1 and SCell#2 can be scheduled at the same time. It can also be only one cell in the cell set, for example, only SCell#2 is scheduled.
  • the cell set may be a co-scheduled cell set, the cells included in the set may be simultaneously scheduled by one DCI, and any combination of the cells included in the set may also be simultaneously scheduled by one DCI. Cells from different cell sets may not be simultaneously scheduled by one DCI.
  • FIG. 8 is a scheduling diagram of another reference cell.
  • the base station may select a cell with sufficient PDCCH resources as a reference cell and configure USS on this cell to implicitly notify the UE that the number of BD/CCEs corresponding to the single DCI monitored in this USS on the main scheduling cell is counted to the reference cell, and the size budget of the single DCI is also counted to the reference cell.
  • the cell with sufficient PDCCH resources can be understood as a cell with less occupied DCI size margin 3+1, and there is still a lot left.
  • the number of BD/CCEs corresponding to the DCI scheduled for this cell is far from reaching the upper limit of the UE blind detection capability of the cell.
  • the network side believes that there is sufficient BD/CCE and DCI size budget on a SCell, it will configure the USS to the SCell to indicate to the UE the BD/CCE and DCI size budget of the USS to be allocated to or occupy the SCell.
  • the PDCCH configured by the base station for the UE does not exceed the blind detection capability of the UE.
  • the base station may configure a search space set that exceeds the blind detection capability of the UE for the UE in the primary cell, namely PDCCH overbooking.
  • PDCCH overbooking In order not to exceed the blind detection capability of the UE, NR introduces the PDCCH mapping rule.
  • the UE selects the search space set to be monitored from the PDCCH configuration sent by the base station according to the PDCCH mapping rule. Among them, the selected search space set to be monitored will not exceed the blind detection capability of the UE.
  • the specific information of the PDCCH mapping rule is in Chapter 10.1 of the communication protocol 38.213.
  • the existing protocol does not specify whether it is allowed to monitor single DCI and legacy DCI simultaneously on the candidate PDCCH included in the USS. And if it is allowed to monitor single DCI and legacy DCI simultaneously on the candidate PDCCH included in the USS, how to define the counting rules of which cell the BD/CCE of this USS is counted to and which cell's DCI size budget is occupied by the load size of the DCI corresponding to this USS.
  • Figure 9 is a flow chart of a communication method provided in an embodiment of the present application. The method mainly includes the following steps:
  • the terminal device receives configuration information sent by the network device, the configuration information is used to indicate to simultaneously monitor the first downlink control information DCI and the second DCI on a candidate physical downlink control channel PDCCH included in a user-specific search space USS set, the first DCI is used to schedule data channels of multiple cells, and the second DCI is used to schedule a data channel of one cell.
  • the first DCI may be a single DCI
  • the second DCI may be a legacy DCI.
  • the first DCI is used to schedule multiple uplink carrier units or multiple downlink carrier units
  • the second DCI is used to schedule one uplink carrier unit or one downlink carrier unit.
  • the corresponding DCI format includes at least one of the following: DCI format 0_0, DCI format 1_0, DCI format 0_1, DCI format 1_1, DCI format 0_2, and DCI format 1_2.
  • the format of a single DCI includes a DCI format for scheduling multiple uplink carrier units and a DCI format for scheduling multiple downlink carrier units.
  • DCI format 0_X represents a DCI format for scheduling multiple uplink carrier units
  • DCI format 1_X represents a DCI format for scheduling multiple downlink carrier units.
  • the value of X may be any number different from the second number in the DCI format of the legacy DCI.
  • X may be 5, DCI format 0_X may be replaced by DCI format 0_5, and DCI format 0_X may be replaced by DCI format 1_5.
  • the network device may receive indication information from the terminal device, the indication information being used to indicate support for simultaneously monitoring the first DCI and the second DCI on the candidate PDCCH included in the USS set.
  • the network device may determine, based on the indication information, whether to configure the terminal device to simultaneously monitor the first downlink control information DCI and the second DCI on the candidate PDCCH included in a USS set.
  • the indication information may also be used to indicate that simultaneously monitoring the first DCI and the second DCI on the candidate PDCCH included in the USS set is not supported, and the network device may determine, based on the indication information, not to configure the terminal device to simultaneously monitor the first DCI and the second DCI on the candidate PDCCH included in a USS set.
  • the indication information may be indication information of the terminal device capability.
  • the terminal device monitors the first DCI and the second DCI simultaneously on the candidate PDCCH included in the USS set according to the configuration information, and the candidate PDCCH corresponding to the second DCI and the candidate PDCCH corresponding to the first DCI occupy the same cell of counting resources.
  • the candidate PDCCH corresponding to the second DCI and the candidate PDCCH corresponding to the first DCI occupy counting resources including at least one of the following: the count of blind detection BD, the count of CCE and the count of DCI size budget.
  • the count of blind detection BD can indicate the count of the terminal device attempting to decode each candidate PDCCH in the search space set to determine whether the candidate PDCCH carries the DCI it expects to receive.
  • the count of CCE can indicate the number of times the terminal device performs PDCCH channel estimation in units of CCE.
  • the count of DCI size budget indicates the count of the terminal device monitoring C-RNTI-scrambled DCI of different lengths and/or the count of DCI of different lengths on a cell.
  • the second DCI is only used for self-carrier scheduling.
  • the counting resources occupied by the first DCI and the second DCI are both primary cells, that is, only resources of one cell are occupied.
  • the terminal device may select a search space set to be monitored from the search space set configured on the primary cell according to the PDCCH mapping rule, wherein the search space set configured on the primary cell includes at least one of the following: a user-specific search space set for receiving the first DCI, a user-specific search space set for receiving the second DCI, and a type 3 public search space set for receiving DCI for scheduling multicast. That is, the search space set configured on the primary cell participates in the PDCCH mapping operation.
  • the format of the DCI for scheduling multicast may include DCI format 4_1 and DCI format 4_2.
  • the terminal device screens the candidate PDCCHs configured by the network device, and screens the number of candidate PDCCHs that need to be blindly detected into a range, thereby ensuring the feasibility of the terminal device.
  • Figure 10 is a schematic diagram of a scheduling method in which a reference cell is a primary cell.
  • the first DCI is a single DCI
  • the second DCI is a traditional DCI.
  • the co-scheduled cell set includes a primary cell, secondary cell 1, and secondary cell 2.
  • a single DCI is used to schedule the primary cell (PCell), secondary cell #1 (SCell#1), and secondary cell #2 (SCell#2).
  • Traditional DCI is used to schedule the primary cell. Since the primary cell is a reference cell, a single DCI occupies the count of blind detection BD, the count of CCE, and the count of DCI size budget of the primary cell.
  • the traditional DCI occupies the same cell of counting resources as a single DCI, and also occupies the count of blind detection BD, the count of CCE, and the count of DCI size budget of the primary cell.
  • the cell of the candidate PDCCH occupancy counting resource corresponding to the first DCI is a reference cell
  • the cell of the candidate PDCCH occupancy counting resource corresponding to the second DCI is the secondary cell.
  • the multiple cells may belong to the same co-scheduled cell or different co-scheduled cells, or the multiple cells may belong to the same co-scheduled cell set or different co-scheduled cell sets.
  • the network device can select a secondary cell with sufficient PDCCH resources as a reference cell, configure USS on the secondary cell, and instruct the terminal device to count the BD/CCE and DCI size budget corresponding to a single DCI monitored in the USS on the primary cell to the secondary cell.
  • the index (index) of the USS configured in the secondary cell to monitor a single DCI is the same as the index of the USS configured on the primary cell to monitor a single DCI
  • the configuration parameters of the USS configured on the secondary cell are not configured except for the parameter used to indicate the number of candidate PDCCHs (nrofCandidates) of an aggregation level.
  • both the first DCI and the second DCI occupy the counting resources of the secondary cell, the first DCI and the second DCI do not occupy the counting resources of the primary cell in the primary cell, so the USS set does not participate in the PDCCH mapping operation of the primary cell, thereby avoiding the candidate PDCCH included in the USS set from being deleted.
  • fallback DCI and other DCI (2_x, 4_x) can obtain more blind detection positions, making PDCCH scheduling more flexible and reducing the probability of PDCCH blocking.
  • FIG. 11 is a schematic diagram of a scheduling method in which the reference cell is a secondary cell.
  • the first DCI is a single DCI
  • the second DCI is a traditional DCI.
  • the single DCI is used to schedule the primary cell (PCell), secondary cell #1 (SCell #1), and secondary cell #2 (SCell #2).
  • the traditional DCI is used to schedule the primary cell. Since secondary cell #1 is a reference cell, the single DCI occupies the count of the blind detection BD of the secondary cell #1, the CCE
  • the conventional DCI occupies the same counting resource as the single DCI cell, and also occupies the blind detection BD count, CCE count and DCI size budget count of the secondary cell #1.
  • the second DCI can be used for self-carrier scheduling, that is, the DCI for scheduling the transmission of PDSCH or PUSCH on one carrier is also sent on the carrier.
  • the DCI sent on the primary cell is used to schedule the transmission of PDSCH or PUSCH on the primary cell.
  • the second DCI can also be used for cross-carrier scheduling, and the DCI for scheduling the transmission of PDSCH or PUSCH on one carrier can be sent on another carrier.
  • the DCI sent on the primary cell is used to schedule the transmission of PDSCH or PUSCH on the secondary cell #1.
  • the terminal device may also use the second DCI for cross-carrier scheduling of any one of multiple cells according to the cell scheduling relationship configured by the RRC parameters.
  • the candidate PDCCH corresponding to the second DCI is the same as the cell in which the candidate PDCCH corresponding to the first DCI occupies counting resources.
  • the reference cell is a primary cell among multiple cells
  • the cell in which the candidate PDCCH corresponding to the second DCI occupies counting resources is the primary cell
  • the search space set configured on the primary cell participates in the PDCCH mapping operation.
  • the reference cell is a secondary cell among multiple cells, the cell in which the candidate PDCCH corresponding to the second DCI occupies counting resources is the secondary cell.
  • the USS set does not participate in the PDCCH mapping operation of the primary cell.
  • the network device monitors legacy DCI and single DCI simultaneously on the candidate PDCCH included in a USS set by configuration.
  • the UE can monitor legacy DCI and single DCI simultaneously on the candidate PDCCH included in the USS set. It is also stipulated that legacy DCI follows the counting method of single DCI in terms of BD/CCE counting and DCI size budget, thereby constraining the scheduling method of legacy DCI, so that the cells occupied by legacy DCI and single DCI are the same, avoiding two counting methods for one USS, and reducing the complexity of UE blind detection.
  • Figure 12 is a flow chart of another communication method provided in an embodiment of the present application. The method mainly includes the following steps:
  • the terminal device receives configuration information sent by the network device, the configuration information is used to indicate monitoring of a first DCI on a candidate PDCCH included in a first USS set, and monitoring of a second DCI on a candidate PDCCH included in a second USS set, the first DCI being used to schedule data channels of multiple cells, and the second DCI being used to schedule a data channel of one cell.
  • the index of the first USS set is different from the index of the second USS set.
  • first DCI and the second DCI reference may be made to the first DCI and the second DCI in the embodiment shown in FIG9 .
  • the terminal device monitors the first DCI on the candidate PDCCH included in the first USS set and monitors the second DCI on the candidate PDCCH included in the second USS set according to the configuration information.
  • the first DCI and the second DCI cannot be configured in the same USS set.
  • the first DCI and the second DCI can be configured in the same USS set, that is, the first DCI and the second DCI can be monitored simultaneously on the candidate PDCCH included in one USS set, and the second DCI occupies the same cell of counting resources as the candidate PDCCH corresponding to the first DCI.
  • the first DCI and the second DCI cannot be configured in the same USS set, that is, the first DCI is monitored on the candidate PDCCH included in the first USS set, and the second DCI is monitored on the candidate PDCCH included in the second USS set.
  • the UE does not expect (UE does not expect or UE is not expected) to be configured to monitor the first DCI and the second DCI simultaneously in the same USS, or the UE does not expect to be configured to include the first DCI and the second DCI in one USS at the same time. If the UE finds that at least one USS includes both the first DCI and the second DCI according to the configuration information sent by the network device, or is configured to monitor the first DCI and the second DCI in one USS at the same time, the configuration information is determined to be incorrect configuration information. The terminal device may further operate to ignore the configuration, or not process, or not monitor the PDCCH, or not decode, etc.
  • the network device monitors legacy DCI and single DCI on candidate PDCCHs included in different USS sets by configuration.
  • the UE can monitor legacy DCI and single DCI on candidate PDCCHs included in different USS sets.
  • the implementation is simple and the communication efficiency is improved.
  • the methods and operations implemented by the terminal device can also be implemented by components that can be used for the terminal device (such as chips or circuits), and the methods and operations implemented by the network device can also be implemented by components that can be used for the network device (such as chips or circuits).
  • the embodiments of the present application can divide the functional modules of the terminal device or network device according to the above method examples.
  • each functional module can be divided according to each function, or two or more functions can be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or software functional modules. It should be noted that the division of modules in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. The following uses the corresponding modules to implement the functions of the terminal device or network device. The functional division is explained by taking each functional module as an example.
  • the communication device may include a receiving module 1301, a processing module 1302 and a sending module 1303.
  • the receiving module 1301 and the sending module 1303 can communicate with the outside, and the processing module 1302 is used to perform processing, such as performing PDCCH mapping operations.
  • the receiving module 1301 and the sending module 1303 can also be referred to as a communication interface, a transceiver unit or a transceiver module.
  • the receiving module 1301 and the sending module 1303 can be used to perform the actions performed by the terminal device in the above method embodiment.
  • the communication device may implement the steps or processes executed by the terminal device in the above method embodiment, for example, it may be a terminal device, or a chip or circuit configured in the terminal device.
  • the receiving module 1301 and the sending module 1303 are used to perform the receiving and sending related operations on the terminal device side in the above method embodiment, and the processing module 1302 is used to perform the processing related operations of the terminal device in the above method embodiment.
  • a receiving module 1301 is configured to receive configuration information sent by a network device, wherein the configuration information is used to indicate that first downlink control information DCI and second DCI are monitored simultaneously on a candidate physical downlink control channel PDCCH included in a user-specific search space USS set, wherein the first DCI is used to schedule data channels of multiple cells, and the second DCI is used to schedule a data channel of one cell;
  • the processing module 1302 is used to simultaneously monitor the first DCI and the second DCI on the candidate PDCCH included in the USS set according to the configuration information, wherein the candidate PDCCH corresponding to the second DCI and the candidate PDCCH corresponding to the first DCI occupy the same cell of counting resources.
  • the cell whose candidate PDCCH occupancy counting resources corresponds to the first DCI is a reference cell.
  • the reference cell is a primary cell among multiple cells
  • the cell whose candidate PDCCH occupancy counting resources corresponds to the second DCI is the primary cell.
  • the processing module 1302 is also used to select a search space set to be monitored from the search space set configured on the main cell according to the PDCCH mapping rule, wherein the search space set configured on the main cell includes at least one of the following: a user-specific search space set for receiving the first DCI, a user-specific search space set for receiving the second DCI, and a type 3 common search space set for receiving DCI for scheduled multicast.
  • the cell of the candidate PDCCH occupancy counting resources corresponding to the first DCI is a reference cell.
  • the reference cell is a secondary cell among multiple cells
  • the cell of the candidate PDCCH occupancy counting resources corresponding to the second DCI is the secondary cell.
  • the sending module 1303 is used to send indication information to the network device, where the indication information is used to indicate support for simultaneously monitoring the first DCI and the second DCI on the candidate PDCCH included in the USS set.
  • the candidate PDCCH corresponding to the second DCI and the candidate PDCCH corresponding to the first DCI occupy counting resources including at least one of the following: a blind detection BD count, a control channel element CCE count and a DCI size budget count.
  • each module can also correspond to the corresponding description of the method embodiment shown in Figures 9 and 12, and execute the methods and functions executed by the terminal device in the above embodiments.
  • the communication device may include a receiving module 1401 and a sending module 1402, and the receiving module 1401 and the sending module 1402 may communicate with the outside.
  • the receiving module 1401 and the sending module 1402 may also be referred to as a communication interface, a transceiver module, or a transceiver unit.
  • the receiving module 1401 and the sending module 1402 may be used to perform the actions performed by the network device in the above method embodiment.
  • the communication device can implement the steps or processes executed by the network device in the above method embodiment, for example, it can be a network device, or a chip or circuit configured in the network device.
  • the receiving module 1401 and the sending module 1402 are used to perform the sending and receiving related operations on the network device side in the above method embodiment.
  • a sending module 1402 is configured to send configuration information to a terminal device, where the configuration information is used to indicate to simultaneously monitor first downlink control information DCI and second DCI on a candidate physical downlink control channel PDCCH included in a user-specific search space USS set, where the first DCI is used to schedule data channels of multiple cells, and the second DCI is used to schedule a data channel of one cell;
  • the sending module 1402 is further configured to send the first DCI and the second DCI on the candidate PDCCH included in the USS set, wherein the candidate PDCCH corresponding to the second DCI and the candidate PDCCH corresponding to the first DCI occupy the same cell of counting resources.
  • the cell whose candidate PDCCH occupancy counting resources corresponds to the first DCI is a reference cell.
  • the reference cell is a primary cell among multiple cells
  • the cell whose candidate PDCCH occupancy counting resources corresponds to the second DCI is the primary cell.
  • the cell of the candidate PDCCH occupancy counting resource corresponding to the first DCI is a reference cell.
  • the reference cell is multiple
  • the secondary cell is the secondary cell.
  • the receiving module 1401 is used to receive indication information sent by the terminal device, where the indication information is used to indicate support for simultaneously monitoring the first DCI and the second DCI on the candidate PDCCH included in the USS set.
  • the candidate PDCCH corresponding to the second DCI and the candidate PDCCH corresponding to the first DCI occupy counting resources including at least one of the following: a blind detection BD count, a control channel element CCE count and a DCI size budget count.
  • each module may also correspond to the corresponding description of the method embodiments shown in FIG. 9 and FIG. 12 , and execute the methods and functions executed by the network devices in the above embodiments.
  • Fig. 15 is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application.
  • the terminal device can be applied to the system shown in Fig. 1 to perform the functions of the terminal device in the above method embodiment, or to implement the steps or processes performed by the terminal device in the above method embodiment.
  • the terminal device includes a processor 1501 and a transceiver 1502.
  • the terminal device also includes a memory 1503.
  • the processor 1501, the transceiver 1502 and the memory 1503 can communicate with each other through an internal connection path to transmit control and/or data signals.
  • the memory 1503 is used to store a computer program, and the processor 1501 is used to call and run the computer program from the memory 1503 to control the transceiver 1502 to send and receive signals.
  • the terminal device may also include an antenna for sending the uplink data or uplink control signaling output by the transceiver 1502 through a wireless signal.
  • the processor 1501 and the memory 1503 may be combined into a processing device, and the processor 1501 is used to execute the program code stored in the memory 1503 to implement the above functions.
  • the memory 1503 may also be integrated into the processor 1501, or independent of the processor 1501.
  • the processor 1501 may correspond to the processing module in FIG13.
  • the transceiver 1502 may correspond to the receiving module and the sending module in FIG13 , and may also be referred to as a transceiver unit or a transceiver module.
  • the transceiver 1502 may include a receiver (or receiver, receiving circuit) and a transmitter (or transmitter, transmitting circuit). The receiver is used to receive signals, and the transmitter is used to transmit signals.
  • the terminal device shown in FIG15 can implement various processes involving the terminal device in the method embodiments shown in FIG9 and FIG12.
  • the operations and/or functions of each module in the terminal device are respectively to implement the corresponding processes in the above method embodiments.
  • the processor 1501 can be used to execute the actions implemented by the terminal device in the previous method embodiment, and the transceiver 1502 can be used to execute the actions of the terminal device sending to or receiving from the network device in the previous method embodiment. Please refer to the description in the previous method embodiment for details, which will not be repeated here.
  • the processor 1501 can be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It can implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application.
  • the processor 1501 can also be a combination that implements a computing function, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and the like.
  • the communication bus 1504 can be a peripheral component interconnection standard PCI bus or an extended industrial standard structure EISA bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc.
  • the communication bus 1504 is used to realize the connection communication between these components. Among them, in the embodiment of the present application, the transceiver 1502 is used to communicate signaling or data with other node devices.
  • the memory 1503 may include a volatile memory, such as a nonvolatile random access memory (NVRAM), a phase change RAM (PRAM), a magnetoresistive RAM (MRAM), etc., and may also include a nonvolatile memory, such as at least one disk storage device, an electrically erasable programmable read-only memory (EEPROM), a flash memory device, such as a NOR flash memory or a NAND flash memory, a semiconductor device, such as a solid state disk (SSD), etc.
  • the memory 1503 may optionally be at least one storage device located away from the aforementioned processor 1501.
  • the memory 1503 may optionally store a set of computer program codes or configuration information.
  • the processor 1501 may also execute the program stored in the memory 1503.
  • the processor can cooperate with the memory and the transceiver to execute any one of the methods and functions of the terminal device in the above-mentioned application embodiments.
  • Figure 16 is a schematic diagram of the structure of a network device provided in an embodiment of the present application.
  • the network device can be applied to the system shown in Figure 1 to perform the functions of the network device in the above method embodiment, or to implement the steps or processes performed by the network device in the above method embodiment.
  • the network device includes a processor 1601 and a transceiver 1602.
  • the network device also includes a memory 1603.
  • the processor 1601, the transceiver 1602 and the memory 1603 can communicate with each other through an internal connection path to transmit control and/or data signals, the memory 1603 is used to store a computer program, and the processor 1601 is used to call and run the computer program from the memory 1603 to control the transceiver 1602 to send and receive signals.
  • the network device may also include an antenna for sending the uplink data or uplink control signaling output by the transceiver 1602 through a wireless signal.
  • the processor 1601 and the memory 1603 may be combined into a processing device, and the processor 1601 is used to execute the program code stored in the memory 1603 to implement the above functions.
  • the memory 1603 may also be integrated into the processor 1601, or independent of the processor 1601.
  • the transceiver 1602 may correspond to the receiving module and the sending module in FIG14 , and may also be referred to as a transceiver unit or a transceiver module.
  • the transceiver 1602 may include a receiver (or receiver, receiving circuit) and a transmitter (or transmitter, transmitting circuit). The receiver is used to receive signals, and the transmitter is used to transmit signals.
  • the network device shown in FIG16 can implement various processes involving the network device in the method embodiments shown in FIG9 and FIG12.
  • the operations and/or functions of each module in the network device are respectively to implement the corresponding processes in the above method embodiments.
  • the processor 1601 can be used to execute the actions implemented by the network device in the previous method embodiment, and the transceiver 1602 can be used to execute the actions of the network device sending to or receiving from the terminal device described in the previous method embodiment. Please refer to the description in the previous method embodiment for details, which will not be repeated here.
  • the processor 1601 can be the various types of processors mentioned above.
  • the communication bus 1604 can be a peripheral component interconnection standard PCI bus or an extended industrial standard structure EISA bus, etc.
  • the bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in Figure 16, but it does not mean that there is only one bus or one type of bus.
  • the communication bus 1604 is used to realize the connection communication between these components.
  • the transceiver 1602 of the device in the embodiment of the present application is used to communicate signaling or data with other devices.
  • the memory 1603 can be the various types of memories mentioned above.
  • the memory 1603 can also be at least one storage device located away from the aforementioned processor 1601.
  • a group of computer program codes or configuration information are stored in the memory 1603, and the processor 1601 executes the program in the memory 1603.
  • the processor can cooperate with the memory and the transceiver to execute any method and function of the network device in the above-mentioned application embodiment.
  • the embodiment of the present application also provides a chip system, which includes a processor for supporting a terminal device or a network device to implement the functions involved in any of the above embodiments, such as generating or processing the SDT data involved in the above method.
  • the chip system may also include a memory, which is used for the necessary program instructions and data for the terminal device or the network device.
  • the chip system can be composed of a chip, or it can include a chip and other discrete devices. Among them, the input and output of the chip system correspond to the receiving and sending operations of the terminal device or the network device in the method embodiment.
  • the present application also provides a computer program product, which includes: a computer program, when the computer program is run on a computer, the computer executes the method of any one of the embodiments shown in Figures 9 and 12.
  • the present application also provides a computer-readable medium, which stores a computer program.
  • the program code runs on a computer, the computer executes the method of any one of the embodiments shown in Figures 9 and 12.
  • the present application also provides a communication system, which includes one or more terminal devices and one or more network devices as mentioned above.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center.
  • 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 or data center that includes one or more available media integrated.
  • the available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a high-density digital video disc (DVD)), or a semiconductor medium (e.g., a solid state disc (SSD)), etc.
  • a magnetic medium e.g., a floppy disk, a hard disk, a magnetic tape
  • an optical medium e.g., a high-density digital video disc (DVD)
  • DVD high-density digital video disc
  • SSD solid state disc

Landscapes

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

Abstract

Des modes de réalisation de la présente demande divulguent un procédé et un appareil de communication. Le procédé comprend les étapes suivantes : un équipement terminal reçoit des informations de configuration envoyées par un dispositif de réseau, les informations de configuration étant utilisées pour indiquer que des premières informations de commande de liaison descendante (DCI) et des secondes DCI sont surveillées simultanément sur un canal physique de contrôle descendant (PDCCH) compris dans un ensemble d'espaces de recherche spécifiques à l'utilisateur (USS), les premières DCI étant utilisées pour planifier des canaux de données d'une pluralité de cellules, les secondes DCI étant utilisées pour planifier un canal de données d'une cellule ; et l'équipement terminal, selon les informations de configuration, surveille simultanément les premières DCI et les secondes DCI sur le PDCCH candidat compris dans l'ensemble USS, la cellule dans laquelle un PDCCH candidat correspondant aux secondes DCI occupe une ressource de comptage étant identique à la cellule dans laquelle un PDCCH candidat correspondant aux premières DCI occupe une ressource de comptage. En utilisant les modes de réalisation de la présente demande, la complexité de détection aveugle par un équipement utilisateur peut être réduite, la flexibilité de planification est améliorée, et la probabilité de blocage PDCCH est réduite.
PCT/CN2024/074214 2023-02-02 2024-01-26 Procédé et appareil de communication WO2024160143A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202310120366.1A CN118433904A (zh) 2023-02-02 2023-02-02 一种通信方法及装置
CN202310120366.1 2023-02-02

Publications (1)

Publication Number Publication Date
WO2024160143A1 true WO2024160143A1 (fr) 2024-08-08

Family

ID=92034976

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/074214 WO2024160143A1 (fr) 2023-02-02 2024-01-26 Procédé et appareil de communication

Country Status (2)

Country Link
CN (1) CN118433904A (fr)
WO (1) WO2024160143A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115053613A (zh) * 2020-01-29 2022-09-13 高通股份有限公司 用于从辅小区到主小区的跨载波调度的技术
US20220346131A1 (en) * 2020-08-07 2022-10-27 Zte Corporation Methods and devices for scheduling multiple cells with single downlink control information
CN115443715A (zh) * 2021-04-05 2022-12-06 苹果公司 无线网络中的控制信道和参考信号传输
CN115443693A (zh) * 2021-04-06 2022-12-06 苹果公司 用于高频通信的多时隙监测能力

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115053613A (zh) * 2020-01-29 2022-09-13 高通股份有限公司 用于从辅小区到主小区的跨载波调度的技术
US20220346131A1 (en) * 2020-08-07 2022-10-27 Zte Corporation Methods and devices for scheduling multiple cells with single downlink control information
CN115443715A (zh) * 2021-04-05 2022-12-06 苹果公司 无线网络中的控制信道和参考信号传输
CN115443693A (zh) * 2021-04-06 2022-12-06 苹果公司 用于高频通信的多时隙监测能力

Also Published As

Publication number Publication date
CN118433904A (zh) 2024-08-02

Similar Documents

Publication Publication Date Title
US11751206B2 (en) Method and apparatus for sending and receiving downlink control information
US10820338B2 (en) User equipments, base stations and methods for RNTI-based PDSCH downlink slot aggregation
US11057914B2 (en) Downlink control information receiving method and user equipment, and downlink control information transmission method and base station
US20180376497A1 (en) Control information reception method and user equipment, and control information transmission method and base station
US11310779B2 (en) Method and apparatus for transmitting/receiving control information in wireless communication system
US20190223204A1 (en) Method and user equipment for receiving downlink channel, and method and base station for transmitting downlink channel
US11012220B2 (en) Allocation of communication resources for control signals in the uplink
US20210329647A1 (en) Method and apparatus for repeatedly transmitting control information in wireless communication system
US20210250159A1 (en) Resource configuration method and apparatus
WO2016119455A1 (fr) Configuration d'informations de commande de liaison descendante (dci), appareil et procédé de réception de données de liaison descendante
WO2020094019A1 (fr) Procédé et dispositif de transmission d'informations
US9300448B2 (en) Search space for component carrier specific UL/DL configuration
EP2702801B1 (fr) Ressources réservées pour le canal phich dans le cas de différentes configurations de ul/dl en tdd
US20180359125A1 (en) Method and apparatus for downlink control physical structure in reduced latency operation
WO2019037695A1 (fr) Procédé et appareil de communication
CN114731691A (zh) 用于发送下行链路控制信息的方法和基站及用于接收下行链路控制信息的用户设备、设备和存储介质
WO2021204107A1 (fr) Procédé et appareil de communication
US11785607B2 (en) Method and apparatus for transmitting control information in wireless cellular communication system
WO2021090606A1 (fr) Équipements d'utilisateur, stations de base et procédés d'indication de configuration de transmission pour pdsch
WO2019223781A1 (fr) Procédé et appareil de communication
WO2021031948A1 (fr) Procédé de traitement de données et appareil de communication
WO2020228542A1 (fr) Procédé et appareil d'émission et de réception de message d'accusé de réception de demande de répétition automatique hybride (harq-ack)
EP4311355A1 (fr) Procédé de communication et appareil de communication
WO2024160143A1 (fr) Procédé et appareil de communication
WO2022000429A1 (fr) Procédé et appareil de détermination d'une occasion de surveillance de pdcch, dispositif et support de stockage

Legal Events

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

Ref document number: 24749624

Country of ref document: EP

Kind code of ref document: A1