WO2022237763A1 - 信道监听方法与装置、终端和网络设备 - Google Patents

信道监听方法与装置、终端和网络设备 Download PDF

Info

Publication number
WO2022237763A1
WO2022237763A1 PCT/CN2022/091921 CN2022091921W WO2022237763A1 WO 2022237763 A1 WO2022237763 A1 WO 2022237763A1 CN 2022091921 W CN2022091921 W CN 2022091921W WO 2022237763 A1 WO2022237763 A1 WO 2022237763A1
Authority
WO
WIPO (PCT)
Prior art keywords
coreset
coresets
css
pdcch
cells
Prior art date
Application number
PCT/CN2022/091921
Other languages
English (en)
French (fr)
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 北京紫光展锐通信技术有限公司
Priority to EP22806726.0A priority Critical patent/EP4340500A1/en
Publication of WO2022237763A1 publication Critical patent/WO2022237763A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053Allocation of signaling, i.e. of overhead other than pilot signals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W74/00Wireless channel access
    • H04W74/08Non-scheduled access, e.g. ALOHA
    • H04W74/0808Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B17/00Monitoring; Testing
    • H04B17/30Monitoring; Testing of propagation channels
    • H04B17/382Monitoring; Testing of propagation channels for resource allocation, admission control or handover
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/0001Arrangements for dividing the transmission path
    • H04L5/0003Two-dimensional division
    • H04L5/0005Time-frequency
    • H04L5/0007Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers

Definitions

  • the present application relates to the technical field of communications, and in particular to a channel monitoring method and device, terminal and network equipment.
  • 3rd Generation Partnership Project 3rd Generation Partnership Project, 3GPP
  • 3rd Generation Partnership Project 3rd Generation Partnership Project
  • 3GPP 3rd Generation Partnership Project
  • the network can configure repeated PDCCHs in the PDCCH candidates associated with different search spaces, so as to realize PDCCH repetition and improve the reliability of the PDCCH.
  • a PDCCH candidate associated with one search space is repeated (or identical to) a PDCCH candidate associated with another search space. That is to say, the PDCCH candidates associated with one search space have the same PDCCH content as the PDCCH candidates associated with another search space, for example, the contents of downlink control information (DCI) carried by the PDCCH candidates are the same.
  • DCI downlink control information
  • the repeated PDCCHs may be associated with different or the same CORESET. It can be seen that in the case of PDCCH repetition, how the terminal monitors the PDCCH still needs further research.
  • the embodiment of the present application provides a channel monitoring method and device, terminal and network equipment, in order to monitor the PDCCH in the repeated CORESETs associated with the PDCCH, improve the reliability of the PDCCH, and then ensure the flexibility, stability and reliability of system communication .
  • the embodiment of the present application provides a channel monitoring method, including:
  • the M CORESETs are monitored PDCCH, so as to monitor the PDCCH in the repeated CORESETs associated with the PDCCH, improve the reliability of the PDCCH, and ensure the flexibility, stability and reliability of system communication.
  • the embodiment of the present application provides a channel monitoring method, including:
  • the network device configures M control resource sets CORESET, and there are duplicate PDCCHs in the PDCCH candidates associated with the M CORESETs, the value of M is an integer greater than or equal to 1.
  • the terminal can monitor the PDCCH in the M CORESETs, so as to monitor the PDCCH in the repeated CORESETs associated with the PDCCH, improve the reliability of the PDCCH, and ensure the flexibility, stability and reliability of system communication.
  • an embodiment of the present application provides a channel monitoring device, the device includes a processing unit, and the processing unit is used for:
  • the value of M is an integer greater than or equal to 1.
  • the embodiment of the present application provides a monitoring device, the device includes a processing unit, and the processing unit is used for:
  • PDCCH monitoring opportunities on the active downlink bandwidth part BWP configure M control resource sets CORESET, and there are repeated PDCCHs in the PDCCH candidates associated with the M CORESETs, and the value of M is greater than or an integer equal to 1.
  • an embodiment of the present application provides a terminal, including a processor, a memory, a communication interface, and one or more programs, wherein the one or more programs are stored in the memory and configured by the The one or more programs include instructions for executing the steps in the first aspect of the embodiments of the present application.
  • an embodiment of the present application provides a network device, including a processor, a memory, a communication interface, and one or more programs, wherein the one or more programs are stored in the memory and configured by The processor executes, and the one or more programs include instructions for executing the steps in the second aspect of the embodiments of the present application.
  • the embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program for electronic data exchange, wherein the computer program enables the computer to execute the computer program according to the embodiment of the present application. Part or all of the steps described in the first aspect or the second aspect.
  • the embodiments of the present application provide a computer program, wherein the computer program is operable to cause a computer to perform some or all of the steps described in the first aspect or the second aspect of the embodiments of the present application.
  • the computer program can be a software installation package.
  • FIG. 1 is a schematic structural diagram of a wireless communication system provided by an embodiment of the present application.
  • FIG. 2 is a schematic flow diagram of a channel monitoring method provided in an embodiment of the present application.
  • FIG. 3 is a schematic flow chart of another channel monitoring method provided by an embodiment of the present application.
  • FIG. 4 is a block diagram of functional units of a channel monitoring device provided in an embodiment of the present application.
  • FIG. 5 is a block diagram of functional units of another channel monitoring device provided by an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a terminal provided in an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a network device provided by an embodiment of the present application.
  • connection in the embodiments of the present application refers to various connection methods such as direct connection or indirect connection to realize communication between devices, and there is no limitation on this.
  • Network and “system” in the embodiments of the present application express the same concept, and the communication system is the communication network.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Advanced Long Term Evolution
  • NR New Radio
  • NR system evolution system LTE (LTE-based Access to Unlicensed Spectrum, LTE-U) system on unlicensed spectrum
  • NR NR-based Access to Unlicensed Spectrum, LTE-U) system on unlicensed spectrum to Unlicensed Spectrum (NR-U) system
  • NTN Non-Terrestrial Networks
  • UMTS Universal Mobile Telecommunications System
  • WLAN Wireless Local Area Networks
  • WiFi 6th-Generation
  • the wireless communication system can not only support the traditional wireless communication system, but also support such as device to device (device to device, D2D) communication, machine to machine (machine to machine, M2M) communication, machine Type communication (machine type communication, MTC), inter-vehicle (vehicle to vehicle, V2V) communication, vehicle networking (vehicle to everything, V2X) communication, narrowband Internet of things (narrow band internet of things, NB-IoT) communication, etc., so
  • D2D device to device
  • M2M machine to machine
  • MTC machine Type communication
  • inter-vehicle vehicle to vehicle
  • V2V vehicle networking
  • narrowband Internet of things narrowband internet of things
  • NB-IoT narrowband Internet of things
  • the wireless communication system in this embodiment of the present application may be applied to beamforming (beamforming), carrier aggregation (carrier aggregation, CA), dual connectivity (dual connectivity, DC) or independent (standalone, SA) deployment scenarios, etc.
  • the wireless communication system in this embodiment of the present application may be applied to an unlicensed spectrum.
  • the unlicensed spectrum can also be regarded as a shared spectrum.
  • the wireless communication system in this embodiment may also be applied to licensed spectrum.
  • the licensed spectrum can also be regarded as a non-shared spectrum.
  • the terminal may be user equipment (user equipment, UE), remote/remote terminal (remote UE), relay equipment (relay UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, mobile device, user terminal, intelligent terminal, wireless communication device, user agent or user device.
  • the relay device is a terminal capable of providing relay and forwarding services for other terminals (including remote terminals).
  • the terminal can also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a wireless Handheld devices with communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminals in next-generation communication systems (such as NR communication systems) or future evolution of public land mobile communication networks (public land mobile network, PLMN) terminals, etc., which are not specifically limited.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • PLMN public land mobile communication networks
  • the terminal can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can be deployed on water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.).
  • the terminal may be a mobile phone (mobile phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (virtual reality, VR) terminal device, an augmented reality (augmented reality, AR) terminal device, an industrial control ( Wireless terminal equipment in industrial control, wireless terminal equipment in unmanned automatic driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid, transportation safety Wireless terminal devices in smart cities, wireless terminal devices in smart cities, or wireless terminal devices in smart homes.
  • a virtual reality (virtual reality, VR) terminal device an augmented reality (augmented reality, AR) terminal device
  • an industrial control Wireless terminal equipment in industrial control, wireless terminal equipment in unmanned automatic driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid, transportation safety Wireless terminal devices in smart cities, wireless terminal devices in smart cities, or wireless terminal devices in smart homes.
  • the terminal may include a device having a sending and receiving function, such as a chip system.
  • the chip system may include a chip, and may also include other discrete devices.
  • the network device may be a device for communicating with the terminal, which is responsible for radio resource management (radio resource management, RRM), service quality (quality of service, QoS) management, data compression and encryption, Data sending and receiving, etc.
  • the network device may be a base station (base station, BS) in a communication system or a device deployed in a radio access network (radio access network, RAN) to provide a wireless communication function.
  • base transceiver station in GSM or CDMA communication system
  • node B node B (node B, NB) in WCDMA communication system
  • evolved node B evolutional node B, eNB or eNodeB
  • the next generation evolved node B (next generation evolved node B, ng-eNB) in the NR communication system
  • the next generation node B node B, gNB
  • the master node in the dual link architecture master node, MN
  • second node or secondary node secondary node, SN
  • the network device may also be other devices in the core network (core network, CN), such as access and mobility management function (access and mobility management function, AMF), user plan function (user plan function, UPF), etc.; It may also be an access point (access point, AP) in a wireless local area network (wireless local area network, WLAN), a relay station, a communication device in a future evolved PLMN network, a communication device in an NTN network, and the like.
  • core network core network, CN
  • AMF access and mobility management function
  • UPF user plan function
  • AP access point
  • WLAN wireless local area network
  • WLAN wireless local area network
  • relay station a communication device in a future evolved PLMN network
  • communication device in an NTN network and the like.
  • the network device may include an apparatus having a wireless communication function for the terminal, such as a chip system.
  • the system-on-a-chip may include a chip, and may also include other discrete devices.
  • the network device can communicate with an Internet Protocol (Internet Protocol, IP) network.
  • Internet Protocol Internet Protocol
  • IP Internet Protocol
  • the Internet Internet
  • private IP network private IP network or other data networks and the like.
  • the network device may be an independent node to implement all the functions of the above-mentioned base station, which may include a centralized unit (centralized unit, CU) and a distributed unit (distributed unit, DU), Such as gNB-CU and gNB-DU; can also include active antenna unit (active antenna unit, AAU).
  • the CU can realize some functions of the network equipment, and the DU can also realize some functions of the network equipment.
  • CU is responsible for processing non-real-time protocols and services, implementing radio resource control (radio resource control, RRC) layer, service data adaptation protocol (service data adaptation protocol, SDAP) layer, packet data convergence (packet data convergence protocol, PDCP) layer function.
  • RRC radio resource control
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • the DU is responsible for processing physical layer protocols and real-time services, realizing the functions of the radio link control (radio link control, RLC) layer, medium access control (medium access control, MAC) layer and physical (physical, PHY) layer.
  • the AAU can implement some physical layer processing functions, radio frequency processing and related functions of active antennas. Since the information of the RRC layer will eventually become the information of the PHY layer, or be transformed from the information of the PHY layer, under this network deployment, high-level signaling (such as RRC layer signaling) can be considered to be sent by the DU, Or sent jointly by DU and AAU.
  • the network device may include at least one of CU, DU, and AAU.
  • the CU can be divided into network devices in an access network (radio access network, RAN), and the CU can also be divided into network devices in a core network, which is not specifically limited.
  • the network device may have a mobile feature, for example, the network device may be a mobile device.
  • the network equipment may be a satellite or a balloon station.
  • the satellite can be a low earth orbit (low earth orbit, LEO) satellite, a medium earth orbit (medium earth orbit, MEO) satellite, a geosynchronous earth orbit (geosynchronous earth orbit, GEO) satellite, a high elliptical orbit (high elliptical orbit, HEO) satellite.
  • the network device may also be a base station installed on land, water, and other locations.
  • the network device can provide services for the cell, and the terminals in the cell can communicate with the network device through transmission resources (such as spectrum resources).
  • the cell may include a macro cell, a small cell, a metro cell, a micro cell, a pico cell, a femto cell, and the like.
  • the wireless communication system 10 may include a terminal 110 and a network device 120 , and the network device 120 may be a device that performs communication with the terminal 110 . Meanwhile, the network device 120 may provide communication coverage for a specific geographical area, and may communicate with the terminal 110 located within the coverage area.
  • the wireless communication system 10 may also include multiple network devices, and a certain number of terminals may be included within the coverage of each network device, which is not specifically limited.
  • the wireless communication system 10 may also include other network entities such as a network controller and a mobility management entity, which is not specifically limited.
  • the communication between the network device and the terminal in the wireless communication system 10 may be wireless communication or wired communication, which is not specifically limited.
  • BWP Bandwidth part
  • overlapping PDCCH monitoring occasion overlapping PDCCH monitoring occasion
  • the BWP is a subset bandwidth of the total bandwidth of the cell, so that the bandwidth received and sent by the terminal does not need to be as large as the total bandwidth of the cell.
  • the downlink BWP may include at least one control resource set (CORESET) associated with the search space.
  • CORESET control resource set
  • the overlapping PDCCH monitoring opportunities can be understood as overlapping PDCCH monitoring opportunities.
  • Aggregation level aggregation level
  • control channel element control channel element
  • the resource element of the PDCCH is a CCE, and one CCE includes 9 resource element groups (resource element group, REG).
  • a CCE is a logical resource unit and corresponds to 9 REGs on the PRB.
  • a PDCCH can be composed of n consecutive CCEs. Among them, n is called the aggregation level, and there are 4 aggregation levels: ⁇ 1,2,4,8 ⁇ . If the aggregation level corresponding to the PDCCH is 8, it means that one PDCCH is composed of 8 consecutive CCEs.
  • Search space search space
  • control resource set control resource set
  • PDCCH In the 5G NR system, due to the large bandwidth of the system and the differences in terminal demodulation capabilities, in order to improve resource utilization and reduce the complexity of blind detection, PDCCH can no longer occupy the entire frequency band in the frequency domain. In addition, in order to increase system flexibility and adapt to different scenarios, the starting position of the PDCCH in the time domain can also be configured. Therefore, in the 5G NR system, information such as the frequency band occupied by the PDCCH in the frequency domain and the number of OFDM symbols occupied in the time domain are usually encapsulated in the CORESET, while the initial OFDM symbol of the PDCCH, the monitoring period of the PDCCH and its associated CORESET, etc. Information is encapsulated in the search space.
  • Types of search spaces may include a common search space (common search space, CSS) and a user-specific search space (UE-specific search space, USS).
  • common search space common search space, CSS
  • UE-specific search space USS
  • a search space will be associated with a CORESET, such as indicated or configured by the high-level parameter controlResourceSetId, and a search space can also be associated with multiple PDCCH candidates (PDCCH candidates), such as indicated or configured by the high-level parameter nrofCandidates. Therefore, an association relationship between one CORESET and multiple PDCCH candidates can be established by means of a search space.
  • a CORESET such as indicated or configured by the high-level parameter controlResourceSetId
  • PDCH candidates PDCCH candidates
  • the CORESET associated with the PDCCH candidate can be configured with at least one transmission configuration indication (transmission configuration indication, TCI) state (state), and the upper layer can configure the QCL through the TCI state, and the TCI Status may be associated with QCL-typeD. Therefore, the TCI state of the CORESET associated with the PDCCH candidate may be associated with QCL-typeD.
  • transmission configuration indication transmission configuration indication, TCI
  • the standard protocol introduces the concept of reference signals with QCL relationship, such as channel state information reference signal (CSI-RS), synchronization signal block (Synchronization signal block, SSB), Therefore, the terminal can estimate large-scale feature parameters according to the CSI-RS.
  • the large-scale feature parameter includes at least one of delay spread, Doppler spread, Doppler frequency shift, average gain, average delay, and spatial domain information.
  • the standard protocol introduces the antenna port QCL.
  • the antenna port QCL can indicate that the signals sent by the antenna port will undergo the same large-scale fading, thus having the same large-scale characteristic parameters.
  • the large-scale characteristic parameters obtained by estimating the signal on the antenna port A are also suitable for the signal on the antenna port B.
  • terminals and network devices may be equipped with a large-scale array structure of multiple antenna panels, and the large-scale characteristics of the beams formed by different antenna panels will also be different.
  • the large-scale characteristic parameters also include the angle of arrival (angle of arrival, AOA), arrival Angle of arival spread (AAS), launch angle of departure (angle of departure, AOD), angle of departure spread (angle of departure spread, ADS) and spatial correlation (spatial correlation), etc.
  • each TCI state includes a demodulation reference signal (demodulation reference symbol, DM-RS) port for configuring one or two downlink reference signals (such as CSI-RS and/or SSB) and PDSCH, PDCCH DM - Parameters of QCL relationship between RS ports or CSI-RS ports of CSI-RS resources.
  • DM-RS demodulation reference symbol
  • the QCL relationship can be configured by the high layer parameter qcl-Type1 for the first DLRS and qcl-Type2 for the second DLRS (if the second DLRS is configured).
  • the QCL types associated with the two downlink reference signals should not be the same.
  • the QCL type associated with each downlink reference signal is determined by the high-level parameter qcl-Type in QCL-Info, and may include:
  • QCL type A QCL-typeA: ⁇ Doppler frequency shift, Doppler spread, average delay, delay spread ⁇ ;
  • QCL type B QCL-typeB: ⁇ Doppler frequency shift, Doppler spread ⁇ ;
  • QCL type C QCL-typeC: ⁇ Doppler frequency shift, average delay ⁇ ;
  • QCL type D QCL-typeD: ⁇ space receiving parameters ⁇ ; etc.
  • the spatial reception parameter may include at least one of the following: AOA, average AOA, AOA extension, AOD, average AOD, AOD extension, receiving antenna spatial correlation, transmitting antenna spatial correlation, transmitting beam, receiving beam, resource identifier, etc.
  • the QCL type is QCL-TypeD
  • the TCI status can be used to indicate the beam.
  • each TCI state can give (contain) 1 or 2 QCL type parameters. If the TCI state contains 2 QCL type parameters, the QCL type will contain QCL-TypeD. That is, TCI status may be associated with QCL-typeD.
  • the TCI state can be activated by an activation command (such as MAC control element CE) issued by the network side and indicated by the TCI field in the DCI.
  • an activation command such as MAC control element CE
  • the network device can first activate 2 N active TCI states through the MAC CE, and then indicate one of the 2 N active TCI states through the N-bit TCI field in the DCI TCI status.
  • the reference signal of the TCI state and the DM-RS port of the PDSCH are QCL.
  • an SSB is considered to have a different QCL-typeD attribute than the CSI-RS
  • the first CSI-RS associated with 1 SSB in the first cell and the second CSI-RS associated with the SSB in the second cell have the same QCL-typeD attribute; etc.
  • the reference signal of QCL-TypeD corresponding to the TCI state of CORESET#1 is the first CSI-RS
  • the reference signal of QCL-TypeD corresponding to the TCI state of CORESET#2 is also the first CSI-RS
  • CORESET#1 and CORESET #2 have the same QCL-typeD attribute between them.
  • the embodiment of the present application provides a schematic flowchart of a channel monitoring method, please refer to Figure 2, the method includes:
  • the terminal monitors the PDCCHs in the M CORESETs, and the value of M is An integer greater than or equal to 1.
  • the network can configure a CORESET for each search space through a high-level parameter (such as controlResourceSetId), that is, a search space may be associated with a CORESET.
  • a high-level parameter such as controlResourceSetId
  • the network can also configure multiple PDCCH candidates for each search space through high-level parameters (such as nrofCandidates), that is, one search space may also be associated with multiple PDCCH candidates. Therefore, an association relationship between a CORESET and PDCCH candidates can be established by means of a search space, that is, one CORESET is associated with multiple PDCCH candidates.
  • the network can configure repeated PDCCHs in the PDCCH candidates associated with different search spaces, thereby achieving PDCCH repetition (PDCCH repetition) , thereby improving the reliability of the PDCCH.
  • a mapping relationship between the PDCCH candidates associated with different search spaces such as a one-to-one mapping relationship
  • the USS when the USS includes USS#1 and USS#2, if the aggregation level corresponding to USS#1 is 4, then USS#1 is associated with 2 PDCCH candidates. Meanwhile, if the aggregation level corresponding to USS#2 is 4, then USS#2 is associated with 2 PDCCH candidates. Among them, if the aggregation level is 4, the first PDCCH candidate associated with USS#1 only has a mapping relationship with the first PDCCH candidate associated with USS#2, and the second PDCCH candidate associated with USS#1 only has a mapping relationship with USS#2 The associated second PDCCH candidate has a mapping relationship.
  • the first PDCCH candidate associated with USS#1 may overlap with (or be the same as) the first PDCCH candidate associated with USS#2. That is to say, the first PDCCH candidate associated with USS#1 may have the same PDCCH content (such as DCI content) with the first PDCCH candidate associated with USS#2, that is, there are duplicate PDCCHs.
  • the second PDCCH candidate associated with USS#1 may overlap with (or be the same as) the second PDCCH candidate associated with USS#2. It can be seen that there are duplicate PDCCHs in the PDCCH candidates associated with the CORESET associated with USS#1 and the PDCCH candidates associated with the CORESET associated with USS#2.
  • the PDCCH repetition in the embodiment of the present application can be understood as that the PDCCH content transmitted by the PDCCH candidates associated with at least two search spaces (or different search spaces) is the same (for example, the content of the DCI carried by the PDCCH candidates is the same) .
  • PDCCH candidates associated with the M CORESETs there are repeated PDCCHs among the PDCCH candidates associated with the M CORESETs. It can be understood that, among the PDCCH candidates associated with the M CORESETs, there are PDCCH candidates that are implicitly or explicitly configured as PDCCH repetitions.
  • the CORESET associated with the repeated PDCCH may exist in different PDCCH listening opportunities.
  • the CORESET associated with one PDCCH among the two repeated PDCCHs belongs to one of the M CORESETs, but the CORESET associated with the other PDCCH may not belong to one of the M CORESETs. That is to say, the CORESETs associated with the two repeated PDCCHs may exist in different PDCCH listening opportunities.
  • the search space associated with repeated PDCCHs can be understood as, if there are repeated PDCCHs between multiple PDCCH candidates associated with a certain search space and multiple PDCCH candidates associated with certain search spaces, then the search space and the These search spaces are collectively referred to as search spaces associated with PDCCH repetition.
  • CSS#1 and CSS#2 are collectively referred to as a search space for associated PDCCH repetition.
  • the search space is associated with the search space, which can be understood as having an association relationship between search spaces in the search spaces associated with PDCCH repetition.
  • the CORESET associated with repeated PDCCHs can be understood as, if there are repeated PDCCHs between multiple PDCCH candidates associated with a certain CORESET and multiple PDCCH candidates associated with some CORESETs, the CORESET and these CORESETs are collectively referred to as CORESET associated with PDCCH repetition.
  • CORESET#1 and CORESET#2 are collectively referred to as CORESETs associated with repeated PDCCHs.
  • the CORESET is associated with the CORESET, and it can be understood that there is an association relationship between each CORESET in the CORESETs associated with PDCCH repetition. For example, if there are overlapping PDCCHs between multiple PDCCH candidates associated with CORESET#1 and multiple PDCCH candidates associated with CORESET#2, CORESET#1 is associated with CORESET#2.
  • the embodiment of the present application considers the following: if there are M CORESETs in overlapping PDCCH monitoring opportunities on the active downlink BWP, and there are duplicate PDCCHs in the PDCCH candidates associated with the M CORESETs, then the M CORESETs
  • the monitoring of the PDCCH is performed in the PDCCH, so as to realize the monitoring of the PDCCH in the CORESET associated with the repeated PDCCH, improve the reliability of the PDCCH, and ensure the flexibility, stability and reliability of the communication system.
  • the quasi-co-located QCL type D attributes of all CORESETs in the M CORESETs are the same; or, there are CORESETs with different QCL type D attributes in the M CORESETs; or, there are QCL type D attributes in the M CORESETs The same CORESET.
  • the CORESET associated with the PDCCH candidate can be configured with at least one TCI state, and the higher layer can configure the QCL through the TCI state, and the TCI state may be associated with the QCL- typeD. Therefore, the TCI state of the CORESET associated with the PDCCH candidate is associated with QCL-typeD. Wherein, in the embodiment of the present application, it may be determined whether the QCL-typeD attributes are the same through reference signals corresponding to the QCL-typeD.
  • repeated PDCCHs may be associated with the same or different CORESETs, and different CORESETs have different QCL-typeD attributes. Therefore, the terminal in the embodiment of the present application can monitor the PDCCH in CORESETs with different QCL-typeD attributes, or monitor the PDCCH in CORESETs with the same QCL-typeD attribute, which is beneficial to ensure the flexibility of the communication system. stability and reliability.
  • the QCL-typeD attributes of all CORESETs in the M CORESETs are the same (that is, all the CORESETs in the M CORESETs have a QCL-typeD attribute); or, there are CORESETs with different QCL-typeD attributes in the M CORESETs (that is, the CORESETs in the M CORESETs have multiple QCL-typeD attributes); or, there are CORESETs with the same QCL-typeD attributes in the M CORESETs (that is, the CORESETs in the M CORESETs have multiple QCL-typeD attributes) . Therefore, there may be the following situations where the terminal monitors the PDCCH in the M CORESETs:
  • the terminal can monitor the PDCCH only in CORESETs with a QCL-typeD attribute, that is, "case 1";
  • the terminal monitors the PDCCH in CORESETs with multiple QCL-typeD attributes, that is, "case 2".
  • the terminal monitors the PDCCH in the M CORESETs, which may include: the terminal monitors the PDCCH in the first reference CORESET and/or a CORESET having the same QCL type D attribute as the first reference CORESET, and the first reference CORESET is one of the M CORESETs.
  • the first reference CORESET may be a CORESET with a QCL-typeD attribute.
  • the CORESET having the same QCL-typeD attribute as the first reference CORESET may include: one or more of the M CORESETs.
  • a CORESET can be associated with one TCI state, and each TCI state may be associated with a QCL-typeD
  • the embodiment of this application can judge the relationship between the QCL-typeD attributes corresponding to the TCI states of different CORESETs Is the same way to select the corresponding CORESET.
  • the embodiment of this application can use the first reference CORESET as a reference CORESET, and then use the first reference CORESET to select from the M CORESETs A CORESET having the same QCL-typeD attribute as the first reference CORESET is determined to obtain other CORESETs, and finally monitor the PDCCH in the other CORESETs.
  • the first reference CORESET can be determined from the M CORESETs through a certain criterion.
  • the terminal monitors the PDCCH only in CORESETs with one QCL-typeD attribute, and the one QCL-typeD attribute is the QCL-typeD attribute of the first reference CORESET.
  • the terminal monitors the PDCCH may include the following three principles: monitor the PDCCH in the first reference CORESET; monitor the PDCCH in the first reference CORESET and a CORESET with the same QCL-typeD attribute as the first reference CORESET; monitor the PDCCH in the first reference CORESET The PDCCH is monitored in the CORESET with the same QCL-typeD attribute.
  • the QCL-typeD attribute corresponding to the TCI state of CORESET#1 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#0;
  • the QCL-typeD attribute corresponding to the TCI state of CORESET#1 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#3;
  • the QCL-typeD attribute corresponding to the TCI state of CORESET#2 is different from the QCL-typeD attribute corresponding to the TCI state of CORESET#0.
  • the first reference CORESET is specifically: in the cell to which the CORESET associated with CSS in the first CORESET belongs In the cell with the smallest index of , the CORESET that belongs to the first CORESET and is associated with the CSS with the smallest index; wherein, the first CORESET includes: the CORESET associated with PDCCH repetition among the M CORESETs.
  • each CORESET can be associated with (or include) CSS and/or USS.
  • each CORESET in the M CORESETs may be associated with (or belong to) a cell, and each cell has its corresponding index (index), ie, the cell index. Therefore, in the embodiment of the present application, the cell with the smallest index can be selected from the cells according to the principle of the smallest index.
  • each search space (CSS and/or USS) also has its corresponding index, so this embodiment of the present application can also select the CORESET associated with the smallest index search space from the CORESETs associated with the search space according to the minimum index principle.
  • cell 1 is associated with CORESET#1_1 (associated with 1 TCI state, associated with CSS#1) and CORESET#1_2 (associated with 1 TCI state, associated with CSS#2); cell 2 is associated with CORESET#2_1 (associated with 1 TCI state state, associated with USS#1) and CORESET#2_2 (associated with 1 TCI state, associated with CSS#3).
  • the index of cell 1 is smaller than the index of cell 2
  • the index of CSS#1 is smaller than the index of CSS#2.
  • the embodiment of the present application considers the CORESET associated with PDCCH repetitions among the M CORESETs as the first CORESET. That is to say, each CORESET in the first CORESET is associated with a repeated PDCCH.
  • the first CORESET includes CORESET#1 and CORESET#2.
  • Example 1 there are 4 CORESETs in overlapping PDCCH monitoring opportunities on a certain active downlink BWP, and CORESET#1 is associated with a repeated PDCCH. Therefore, the first CORESET includes CORESET#1.
  • the CORESET that belongs to the first CORESET and is associated with the CSS with the smallest index among the cells with the smallest index among the cells to which the CORESETs associated with the CSS in the first CORESET belong is used as the first reference CORESET.
  • the embodiment of the present application can accurately and quickly determine an associated PDCCH overlap, an associated minimum cell index, and an associated minimum CSS index in the overlapping PDCCH listening opportunities on the active downlink BWP COSESET (that is, the first reference CORESET), so as to monitor the PDCCH in the repeated CORESETs associated with the PDCCH, thereby ensuring the flexibility, stability and reliability of system communication.
  • the first reference CORESET is specifically: the cells to which the CORESETs associated with the USS in the first CORESET belong The CORESET that belongs to the first CORESET and is associated with the smallest index USS in the cell with the smallest index in .
  • the first CORESET includes: CORESETs associated with PDCCH repetitions in the M CORESETs.
  • the CORESET that belongs to the first CORESET and is associated with the smallest index USS in the cell with the smallest index among the cells of the CORESETs associated with USS in the first CORESET is used as the first reference CORESET . That is to say, first determine the CORESET associated with the USS from the first CORESET to obtain at least one CORESET, then determine the cells to which the at least one CORESET belongs to obtain at least one cell, and then determine the minimum index from the at least one cell , and finally determine the CORESET belonging to the first CORESET and associated with the smallest index USS from the cells with the smallest index to obtain the first reference CORESET.
  • the embodiment of the present application can accurately and quickly determine a COSESET associated with PDCCH overlap, associated minimum cell index, and associated minimum USS index in the overlapping PDCCH monitoring opportunities on the active downlink BWP (that is, the first reference CORESET), so as to monitor the PDCCH in the repeated CORESETs associated with the PDCCH, thereby ensuring the flexibility, stability and reliability of system communication.
  • Cell 1 CORESET#0 (associated with 1 TCI state, associated with CSS#0), CORESET#2 (associated with 1 TCI state, associated with CSS#1), CORESET#3 (associated with 1 TCI state, associated with CSS#4), CORESET#4 (2 TCI states, associated with USS#1);
  • the QCL-typeD attribute corresponding to the TCI state of CORESET#2 of cell 1 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#0 of cell 1;
  • the QCL-typeD attribute corresponding to the TCI state of CORESET#2 of cell 1 is different from the QCL-typeD attribute corresponding to the TCI state of CORESET#3 of cell 1;
  • the QCL-typeD attribute corresponding to the TCI state of CORESET#4 of cell 1 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#2 of cell 1;
  • Cell 2 CORESET#1 (1 TCI state, associated with USS#2), CORESET#2 (1 TCI state, associated with CSS#3);
  • the QCL-typeD attribute corresponding to the TCI state of CORESET#2 of cell 2 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#1 of cell 2;
  • the QCL-typeD attribute corresponding to the TCI state of CORESET#2 of cell 2 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#2 of cell 1;
  • the cells associated with the above CORESETs include cell 1 and cell 2 .
  • the CORESETs associated with cell 1 include CORESET#0, CORESET#2, CORESET#3, and CORESET#4, and the CORESETs associated with cell 2 include CORESET#1 and CORESET#2.
  • CORESET#0 of cell 1 is associated with one TCI state, and the search space associated with CORESET#0 of cell 1 includes CSS#0, which is associated with multiple PDCCH candidates, and other CORESETs can be known in turn.
  • the index of cell 1 is smaller than the index of cell 2
  • the index of CSS#0 is smaller than the index of CSS#1
  • the index of CSS#1 is smaller than the index of CSS#4.
  • CORESET #2 of cell 1 and CORESET #3 of cell 1 (ie, the first CORESET). Since both CORESET#2 of cell 1 and CORESET#3 of cell 1 are CORESETs associated with CSS, that is, there is a CORESET associated with CSS in the first CORESET, so the first reference CORESET is determined to be the CORESET of cell 1 through "Criteria 1-1".
  • CORESET #2 :
  • the terminal listens in "CORESET#2" of cell 1, "CORESET#0" of cell 1, "CORESET#4" of cell 1, "CORESET#1” of cell 2 and "CORESET#2" of cell 2 PDCCH, so as to monitor the PDCCH in the CORESETs associated with the PDCCH repetition.
  • the terminal monitors the PDCCH in the M CORESETs, which may include: the terminal monitors the PDCCH in the second reference CORESET and/or a CORESET having the same QCL type D attribute as the second reference CORESET, and in the third reference CORESET Monitor the PDCCH in the reference CORESE and/or a CORESET having the same QCL type D attribute as the third reference CORESET; wherein, the second reference CORESET is a CORESET in the M CORESETs, and the third reference CORESET is a CORESET in the M CORESETs , the QCL type D attribute of the second reference CORESET is different from the QCL type D attribute of the third reference CORESET.
  • the second reference CORESET may be a CORESET with a QCL-typeD attribute.
  • the CORESET having the same QCL-typeD attribute as the second reference CORESET may include: one or more of the M CORESETs.
  • the third reference CORESET may be a CORESET with a QCL-typeD attribute.
  • the CORESET having the same QCL-typeD attribute as the third reference CORESET may include: one or more of the M CORESETs.
  • the terminal monitoring the PDCCH may include the following principles: monitoring the PDCCH in the second reference CORESET and the third reference CORESET; monitoring the PDCCH in the CORESET having the same QCL type D attribute as the second reference CORESET and the third CORESET; Monitor the PDCCH in the second reference CORESET and the CORESET having the same QCL type D attribute as the third reference CORESET; in the CORESET having the same QCL type D attribute as the second reference CORESET and the CORESET having the same QCL type D attribute as the third reference CORESET; Monitor the PDCCH in the second reference CORESET and the third reference CORESET; monitor the PDCCH in the second reference CORESET, the CORESET having the same QCL type D attribute as the second reference CORESET, and the third CORESET; the second reference CORESET, and the second
  • the second reference CORESET can be used as a reference CORESET, and then determined from the M CORESETs through the second reference CORESET A CORESET having the same QCL-typeD attribute as the second reference CORESET is obtained to obtain other CORESETs, and finally monitor the PDCCH in the other CORESETs.
  • the embodiment of this application can use the third reference CORESET as a reference CORESET, and then use the third reference CORESET to select from the M CORESETs A CORESET having the same QCL-typeD attribute as the third reference CORESET is determined to obtain other CORESETs, and finally monitor the PDCCH in the other CORESETs.
  • the second reference CORESET can be determined from the M CORESETs through a certain criterion.
  • the third reference CORESET can be determined from the M CORESETs through certain criteria.
  • the second reference CORESET may specifically be: a cell with the associated CSS in the first cell set
  • the CORESET with the smallest index CSS is associated with the smallest indexed cell among the cells of the CORESET.
  • the first set of cells includes: the cells corresponding to the M CORESETs.
  • the first cell set in the embodiment of the present application includes the M Each CORESET in the CORESET corresponds to a cell.
  • the CORESET associated with the CSS with the smallest index in the cell with the smallest index among the cells including the CORESET associated with the CSS in the first cell set is used as the second reference CORESET. That is to say, first determine at least one cell of the CORESET containing the associated CSS from the first cell set, then determine the cell with the smallest index from the at least one cell, and finally determine the associated minimum index CSS from the cell with the smallest index CORESET to get the second reference CORESET.
  • the second reference CORESET in 'Criteria 2-1-1' can be an associated minimum The cell index and the COSESET associated with the minimum CSS index.
  • the embodiment of the present application can accurately and quickly determine a COSESE associated with the minimum cell index and the associated minimum CSS index in the overlapping PDCCH listening opportunities on the active downlink BWP (that is, the first 2. Refer to CORESET), so as to monitor the PDCCH in the repeated CORESETs associated with the PDCCH, thereby ensuring the flexibility, stability and reliability of system communication.
  • the second reference CORESET may be: the first cell set contains the associated USS The CORESET associated with the USS with the smallest index in the cell with the smallest index among the cells of the CORESET.
  • the second reference CORESET may be a COSESET associated with the minimum cell index and the minimum USS index.
  • the CORESET associated with the smallest index USS in the cell with the smallest index among the cells including the CORSET associated with the USS in the first cell set is used as the second reference CORESET. That is to say, first determine at least one cell containing the CORESET associated with the USS from the first set of cells, then determine the cell with the smallest index from the at least one cell, and finally determine the associated minimum index USS from the cell with the smallest index. CORESET to get the second reference CORESET.
  • the embodiment of the present application can accurately and quickly determine a COSESET associated with the minimum cell index and the associated minimum USS index in the overlapping PDCCH listening opportunities on the active downlink BWP (that is, the second reference CORESET), so as to monitor the PDCCH in the repeated CORESETs associated with the PDCCH, thereby ensuring the flexibility, stability and reliability of system communication.
  • Cell 1 CORESET#0 (associated with 1 TCI state, associated with CSS#0), CORESET#2 (associated with 1 TCI state, associated with CSS#1), CORESET#3 (associated with 1 TCI state, associated with CSS#4), CORESET#4 (2 TCI states, associated with USS#1);
  • the QCL-typeD attribute corresponding to the TCI state of CORESET#2 of cell 1 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#0 of cell 1;
  • the QCL-typeD attribute corresponding to the TCI state of CORESET#2 of cell 1 is different from the QCL-typeD attribute corresponding to the TCI state of CORESET#3 of cell 1;
  • the QCL-typeD attribute corresponding to the TCI state of CORESET#4 of cell 1 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#2 of cell 1;
  • Cell 2 CORESET#1 (1 TCI state, associated with USS#2), CORESET#2 (1 TCI state, associated with CSS#3);
  • the QCL-typeD attribute corresponding to the TCI state of CORESET#2 of cell 2 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#1 of cell 2;
  • the QCL-typeD attribute corresponding to the TCI state of CORESET#2 of cell 2 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#2 of cell 1;
  • the cells associated with the above CORESETs include Cell 1 and Cell 2, that is, the first set of cells includes Cell 1 and Cell 2.
  • the CORESETs associated with cell 1 include CORESET#0, CORESET#2, CORESET#3, and CORESET#4, and the CORESETs associated with cell 2 include CORESET#1 and CORESET#2.
  • the index of cell 1 is smaller than the index of cell 2
  • the index of CSS#0 is smaller than the index of CSS#1
  • the index of CSS#1 is smaller than the index of CSS#4.
  • the terminal listens in "CORESET#0" of cell 1, "CORESET#2" of cell 1, "CORESET#4" of cell 1, "CORESET#1" of cell 2 and "CORESET#2" of cell 2 PDCCH, so as to monitor the PDCCH in the CORESETs associated with the PDCCH repetition.
  • the second reference CORESET is specifically: in the cells to which the CORESETs associated with the CSS in the second CORESET belong In the cell with the smallest index, the CORESET that belongs to the second CORESET and is associated with the CSS with the smallest index; wherein, the second CORESET includes: CORESETs that are not associated with PDCCH repetition among the M CORESETs.
  • the embodiment of the present application considers repeating the unassociated PDCCHs in the M CORESETs.
  • the CORESET acts as the second CORESET. That is to say, there is no overlapping PDCCH among the CORESETs in the second CORESET.
  • Example 1 there are 4 CORESETs in overlapping PDCCH listening opportunities on a certain active downlink BWP, and CORESET#1 is associated with CORESET#2. Therefore, the second CORESET includes CORESET #0 and CORESET #3.
  • the CORESET that belongs to the second CORESET and is associated with the smallest index CSS in the cell with the smallest index among the cells to which the CORESETs associated with CSS in the second CORESET belong is used as the second reference CORESET.
  • the second reference CORESET is specifically: the respective cells of the CORESETs associated with the USS in the second CORESET The CORESET belonging to the second CORESET and associated with the smallest index USS in the cell with the smallest index in .
  • the second CORESET includes: CORESETs that are not associated with repeated PDCCHs among the M CORESETs.
  • the CORESET that belongs to the second CORESET and is associated with the smallest index USS among the cells with the smallest index among the cells to which the CORESETs associated with the USS in the second CORESET belong is taken as the second CORESET.
  • the embodiment of the present application can accurately and quickly determine an unassociated PDCCH overlapping, associated minimum cell index, and associated minimum USS in the overlapping PDCCH listening opportunities on the active downlink BWP
  • the indexed COSESET that is, the second reference CORESET
  • the embodiment of the present application can accurately and quickly determine an unassociated PDCCH overlapping, associated minimum cell index, and associated minimum USS in the overlapping PDCCH listening opportunities on the active downlink BWP
  • the indexed COSESET that is, the second reference CORESET
  • Cell 1 CORESET#0 (associated with 1 TCI state, associated with CSS#0), CORESET#2 (associated with 1 TCI state, associated with CSS#1), CORESET#3 (associated with 1 TCI state, associated with CSS#4), CORESET#4 (2 TCI states, associated with USS#1);
  • the QCL-typeD attribute corresponding to the TCI state of CORESET#2 of cell 1 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#0 of cell 1;
  • the QCL-typeD attribute corresponding to the TCI state of CORESET#2 of cell 1 is different from the QCL-typeD attribute corresponding to the TCI state of CORESET#3 of cell 1;
  • the QCL-typeD attribute corresponding to the TCI state of CORESET#4 of cell 1 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#2 of cell 1;
  • Cell 2 CORESET#1 (1 TCI state, associated with USS#2), CORESET#2 (1 TCI state, associated with CSS#3);
  • the QCL-typeD attribute corresponding to the TCI state of CORESET#2 of cell 2 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#1 of cell 2;
  • the QCL-typeD attribute corresponding to the TCI state of CORESET#2 of cell 2 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#2 of cell 1;
  • the cells associated with the above CORESETs include cell 1 and cell 2 .
  • the CORESETs associated with cell 1 include CORESET#0, CORESET#2, CORESET#3, and CORESET#4, and the CORESETs associated with cell 2 include CORESET#1 and CORESET#2.
  • the index of cell 1 is smaller than the index of cell 2
  • the index of CSS#0 is smaller than the index of CSS#1
  • the index of CSS#1 is smaller than the index of CSS#4.
  • the CORESETs that is, the second CORESET
  • CORESET#2 of cell 2 Since there is a CORESET associated with the CSS in the second CORESET, the second reference CORESET is determined to be "CORESET#0" of cell 1 through "criteria 2-2-1".
  • the terminal listens in "CORESET#0" of cell 1, "CORESET#2" of cell 1, "CORESET#4" of cell 1, "CORESET#1" of cell 2 and "CORESET#2" of cell 2 PDCCH, so as to monitor the PDCCH in the CORESETs associated with the PDCCH repetition.
  • the third reference CORESET is specifically: the CORESET that belongs to the third CORESET and is associated with the smallest index CSS in the cell with the smallest index among the cells to which the CORESETs associated with the CSS in the third CORESET belong; wherein, the third CORESET includes: The CORESET of the associated PDCCH repetition in the M CORESETs.
  • each CORESET in the third CORESET is associated with a repeated PDCCH.
  • the CORESET belonging to the third CORESET and associated with the minimum index CSS is used as the third reference CORESET.
  • the embodiment of the present application can accurately and quickly determine a QCL-type D that overlaps with the second reference CORESET when the associated PDCCH overlaps the PDCCH monitoring opportunity on the active downlink BWP.
  • the third reference CORESET is specifically: the CORESET that belongs to the third CORESET and is associated with the USS with the smallest index among the cells with the smallest index among the cells to which the CORESETs associated with the USS in the third CORESET belong.
  • the embodiment of the present application can accurately and quickly determine the QCL-typeD of an associated PDCCH overlapping with the second reference CORESET in the overlapping PDCCH monitoring opportunities on the active downlink BWP.
  • the third reference CORESET is specifically: the CORESET that belongs to the fourth CORESET and is associated with the minimum index CSS in the cell with the smallest index among the cells of the CORESET associated with CSS in the fourth CORESET; wherein, the fourth CORESET includes: among the M CORESETs Among the CORESETs associated with the CORESETs that are the same as the QCL type D attributes of the second reference CORESET, the CORESETs that are not the same as the QCL type D attributes of the second reference CORESET; or, the fourth CORESET includes: among the M CORESETs Among the CORESETs associated with PDCCH repetition, a CORESET with a QCL type D attribute different from that of the second reference CORESET.
  • the QCL-typeD attribute corresponding to the TCI state of CORESET#1 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#0;
  • the QCL-typeD attribute corresponding to the TCI state of CORESET#1 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#3;
  • the QCL-typeD attribute corresponding to the TCI state of CORESET#1 is different from the QCL-typeD attribute corresponding to the TCI state of CORESET#2.
  • the CORESETs with the same QCL-typeD attribute as the second reference CORESET include: CORESET#1 and CORESET#3.
  • CORESET#1 is associated with CORESET#2
  • the CORESETs associated with CORESETs having the same QCL-typeD attribute as the second reference CORESET include: CORESET#2.
  • the QCL-typeD attribute of CORESET#2 is different from the QCL-typeD attribute of the second reference CORESET, the fourth CORESET includes: CORESET#2.
  • the embodiment of the present application can accurately and quickly determine the QCL-typeD of an associated PDCCH overlapping with the second reference CORESET in the overlapping PDCCH monitoring opportunities on the active downlink BWP.
  • the third reference CORESET is specifically: the CORESET that belongs to the fourth CORESET and is associated with the USS with the smallest index among the cells with the smallest index among the cells to which the CORESETs associated with the USS in the fourth CORESET belong.
  • the fourth CORESET includes: among the CORESETs associated with the CORESET that is the same as the QCL type D attribute of the second reference CORESET among the M CORESETs, the CORESET that is different from the QCL type D attribute of the second reference CORESET; or, The fourth CORESET includes: among the CORESETs associated with PDCCH repetition in the M CORESETs, the CORESETs whose QCL type D attribute is different from that of the second reference CORESET.
  • the embodiment of the present application can accurately and quickly determine a QCL-typeD that overlaps with the second reference CORESET when the associated PDCCH overlaps the PDCCH monitoring opportunity on the active downlink BWP.
  • Cell 1 CORESET#0 (associated with 1 TCI state, associated with CSS#0), CORESET#2 (associated with 1 TCI state, associated with CSS#1), CORESET#3 (associated with 1 TCI state, associated with CSS#4), CORESET#4 (2 TCI states, associated with USS#1);
  • the QCL-typeD attribute corresponding to the TCI state of CORESET#2 of cell 1 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#0 of cell 1;
  • the QCL-typeD attribute corresponding to the TCI state of CORESET#2 of cell 1 is different from the QCL-typeD attribute corresponding to the TCI state of CORESET#3 of cell 1;
  • the QCL-typeD attribute corresponding to the TCI state of CORESET#4 of cell 1 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#2 of cell 1;
  • Cell 2 CORESET#1 (1 TCI state, associated with USS#2), CORESET#2 (1 TCI state, associated with CSS#3);
  • the QCL-typeD attribute corresponding to the TCI state of CORESET#2 of cell 2 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#1 of cell 2;
  • the QCL-typeD attribute corresponding to the TCI state of CORESET#2 of cell 2 is the same as the QCL-typeD attribute corresponding to the TCI state of CORESET#3 of cell 1;
  • the cells associated with the above CORESETs include Cell 1 and Cell 2.
  • the CORESETs associated with cell 1 include CORESET#0, CORESET#2, CORESET#3, and CORESET#4, and the CORESETs associated with cell 2 include CORESET#1 and CORESET#2.
  • the index of cell 1 is smaller than the index of cell 2
  • the index of CSS#0 is smaller than the index of CSS#1
  • the index of CSS#1 is smaller than the index of CSS#4.
  • the CORESETs with the same QCL-typeD attribute as the second reference CORESET in the above CORESETs include: "CORESET#2" of cell 1 , "CORESET #4" of cell 1, "CORESET #1” of cell 2, and "CORESET #2” of cell 2.
  • the terminal is in "CORESET#0" of cell 1, "CORESET#2" of cell 1, "CORESET#3" of cell 1, “CORESET#4" of cell 1, "CORESET#1” of cell 2 and cell
  • the PDCCH is monitored in "CORESET#2" of 2, so that the PDCCH can be monitored in the CORESETs associated with the PDCCH repetition.
  • the second reference CORESET is specifically: in the cells to which the CORESETs associated with CSS in the fifth CORESET belong In the cell with the smallest index, the CORESET that belongs to the fifth CORESET and is associated with the smallest index CSS; wherein, the fifth CORESET includes: the CORESET associated with PDCCH repetition among the M CORESETs.
  • the "second reference CORESET” is a COSESET that is not associated with PDCCH overlap, associated with the minimum cell index, and associated with the minimum CSS/USS index.
  • the embodiment of the present application can accurately and quickly determine a PDCCH overlapping, an associated minimum cell index, and an associated minimum CSS index in the overlapping PDCCH listening opportunities on the active downlink BWP COSESET (that is, the second reference CORESET), so as to monitor the PDCCH in the repeated CORESETs associated with the PDCCH, thereby ensuring the flexibility, stability and reliability of system communication.
  • the second reference CORESET is specifically: the respective cells of the CORESETs associated with the USS in the fifth CORESET Among the cells with the smallest index in , the CORESET that belongs to the fifth CORESET and is associated with the smallest index USS.
  • the fifth CORESET includes: CORESETs associated with PDCCH repetitions among the M CORESETs.
  • the embodiment of the present application can accurately and quickly determine an associated PDCCH overlap, an associated minimum cell index, and an associated minimum USS index in the overlapping PDCCH listening opportunities on the active downlink BWP COSESET (that is, the second reference CORESET), so as to monitor the PDCCH in the repeated CORESETs associated with the PDCCH, thereby ensuring the flexibility, stability and reliability of system communication.
  • the third reference CORESET is specifically: the cell with the smallest index among the cells to which the CORESET associated with CSS in the sixth CORESET belongs to the sixth CORESET and has the smallest association The CORESET of the index CSS; wherein, the sixth CORESET includes: among the CORESETs associated with the CORESET that is the same as the QCL type D attribute of the second reference CORESET among the M CORESETs, the QCL type D attribute of the second reference CORESET is not the same CORESET; or, the sixth CORESET includes: among the CORESETs associated with PDCCH repetition in the M CORESETs, the CORESETs whose QCL type D attribute is different from that of the second reference CORESET.
  • the embodiment of the present application can accurately and quickly determine the QCL of an associated PDCCH overlapping with the second reference CORESET in the overlapped PDCCH listening opportunity on the active downlink BWP -typeD attributes are different, the COSESET associated with the minimum cell index and the minimum CSS index (that is, the third reference CORESET), so as to monitor the PDCCH in the CORESETs associated with the PDCCH repetition, thereby ensuring the flexibility, stability and reliability of system communication .
  • the third reference CORESET is specifically: the respective cells of the CORESETs associated with the USS in the sixth CORESET Among the cells with the smallest index in , the CORESET that belongs to the sixth CORESET and is associated with the smallest index USS.
  • the sixth CORESET includes: among the CORESETs associated with the CORESET that is the same as the QCL type D attribute of the second reference CORESET among the M CORESETs, the CORESET that is different from the QCL type D attribute of the second reference CORESET; or,
  • the six CORESETs include: among the CORESETs associated with PDCCH repetitions in the M CORESETs, the CORESETs whose QCL type D attribute is different from that of the second reference CORESET.
  • the embodiment of the present application can accurately and quickly determine the QCL of an associated PDCCH overlapping with the second reference CORESET in the overlapped PDCCH monitoring opportunity on the active downlink BWP -The typeD attribute is different, the COSESET associated with the smallest cell index and the associated smallest USS index (that is, the third reference CORESET), so as to monitor the PDCCH in the associated PDCCH repeated CORESETs, thereby ensuring the flexibility, stability and reliability of system communication .
  • this embodiment of the present application provides a schematic flowchart of another channel monitoring method, please refer to FIG. 3 , the method includes:
  • the network device configures M CORESETs, and there are duplicate PDCCHs among the PDCCH candidates associated with the M CORESETs, and the value of M is an integer greater than or equal to 1.
  • the quasi-co-located QCL type D attribute of all CORESETs in M CORESETs is the same; or, there are CORESETs with different QCL type D attributes in M CORESETs; or, there are CORESETs with the same QCL type D attribute in M CORESETs .
  • the M CORESETs include the first reference CORESET and/or a CORESET having the same quasi-co-location QCL type D attribute as the first reference CORESET, and the first reference CORESET is a CORESET in the M CORESETs; or, the M CORESETs include The second reference CORESET and/or the CORESET with the same QCL type D attribute as the second reference CORESET, and the third reference CORESET and/or the CORESET with the same QCL type D attribute as the third reference CORESET; wherein, the second reference CORESET is One of the M CORESETs, the third reference CORESET is one of the M CORESETs, and the QCL type D attribute of the second reference CORESET is different from the QCL type D attribute of the third reference CORESET.
  • the terminal can monitor the PDCCH in the M CORESETs, so as to monitor the PDCCH in the repeated CORESETs associated with the PDCCH, improve the reliability of the PDCCH, and ensure the flexibility, stability and reliability of system communication.
  • the terminal or network device includes corresponding hardware structures and/or software modules for performing various functions.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software in combination with the units and algorithm steps of each example described in the embodiments disclosed herein. Whether a certain function is executed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art may implement the described functionality using different methods for each particular application, but such implementation should not be considered as exceeding the scope of the present application.
  • the terminal or network device may be divided into functional units according to the foregoing method example.
  • each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit.
  • the above-mentioned integrated units can be implemented not only in the form of hardware, but also in the form of software program modules. It should be noted that the division of units in the embodiment of the present application is schematic, and is only a logical function division, and there may be another division manner in actual implementation.
  • FIG. 4 provides a block diagram of functional units of a channel monitoring device.
  • the channel monitoring device 400 includes: a processing unit 402 and a communication unit 403 .
  • the processing unit 402 is configured to control and manage actions of the terminal.
  • the processing unit 402 is configured to support the terminal to execute the steps in FIG. 2 and other processes for the technical solutions described in this application.
  • the communication unit 403 is used to support communication between the terminal and other devices in the wireless communication system.
  • the channel monitoring device 400 may further include a storage unit 401 for storing program codes executed by the channel monitoring device 400 and transmitted data.
  • channel monitoring device 400 may be a chip or a chip module.
  • the processing unit 402 may be a processor or a controller, such as a central processing unit (central processing unit, CPU), a general processor, a digital signal processor (digital signal processor, DSP), an application-specific integrated circuit (application-specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processing unit 402 may also be a combination that implements computing functions, for example, a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like.
  • the communication unit 403 may be a communication interface, a transceiver, a transceiver circuit, etc., and the storage unit 401 may be a memory.
  • the processing unit 402 is a processor
  • the communication unit 403 is a communication interface
  • the storage unit 401 is a memory
  • the channel monitoring device 400 involved in this embodiment of the present application may be the terminal shown in FIG. 6 .
  • the processing unit 402 is configured to perform any step performed by the terminal in the above method embodiments, and when performing data transmission such as sending, the communication unit 403 may be called to complete corresponding operations. Detailed description will be given below.
  • the processing unit 402 is configured to: if there are M CORESETs in overlapping PDCCH monitoring opportunities on the active downlink BWP, and there are duplicate PDCCHs in the PDCCH candidates associated with the M CORESETs, monitor the PDCCHs in the M CORESETs, and the M The value is an integer greater than or equal to 1.
  • the channel monitoring device will The PDCCH is monitored in the CORESET, so that the PDCCH can be monitored in the repeated CORESETs associated with the PDCCH, the reliability of the PDCCH is improved, and the flexibility, stability and reliability of the system communication are ensured.
  • the quasi-co-located QCL type D attributes of all CORESETs in M CORESETs are the same; or, there are CORESETs with different QCL type D attributes in M CORESETs; or, there are QCL type D in M CORESETs CORESET with the same attributes.
  • the processing unit 402 is specifically configured to: monitor PDCCHs in a first reference CORESET and/or a CORESET having the same quasi-co-located QCL type D attribute as the first reference CORESET , the first reference CORESET is one of the M CORESETs; or, monitor the PDCCH in the second reference CORESET and/or a CORESET having the same QCL type D attribute as the second reference CORESET, and monitor the PDCCH in the third reference CORESET and/or Monitor the PDCCH in a CORESET having the same QCL type D attribute as the third reference CORESET; wherein, the second reference CORESET is one of the M CORESETs, the third reference CORESET is one of the M CORESETs, and the second reference CORESET
  • the QCL Type D attribute is not the same as the QCL Type D attribute of the third reference CORESET.
  • the first reference CORESET is specifically: each of the CORESETs associated with the CSS in the first CORESET The CORESET belonging to the first CORESET and associated with the smallest index CSS in the cell with the smallest index in the cell to which it belongs;
  • the first CORESET includes: CORESETs associated with PDCCH repetitions in the M CORESETs.
  • the first reference CORESET is specifically: the CORESET associated with the user-specific search space USS in the first CORESET
  • the second reference CORESET is specifically: the first cell set contains a CORESET associated with a CSS Among the cells with the smallest index among the cells, the CORESET with the smallest index CSS is associated; wherein, the first set of cells includes: the cells corresponding to M CORESETs.
  • the second reference CORESET is specifically: the first cell set contains the associated USS The CORESET associated with the smallest index USS in the cell with the smallest index among the cells of the CORESET.
  • the second reference CORESET is specifically: in the cells to which the CORESETs associated with the CSS in the second CORESET belong In the cell with the smallest index, the CORESET that belongs to the second CORESET and is associated with the CSS with the smallest index; wherein, the second CORESET includes: CORESETs that are not associated with PDCCH repetition among the M CORESETs.
  • the second reference CORESET is specifically: the respective cells of the CORESETs associated with the USS in the second CORESET The CORESET belonging to the second CORESET and associated with the smallest index USS in the cell with the smallest index in .
  • the third reference CORESET is specifically: the CORESET that belongs to the third CORESET and is associated with the smallest index CSS in the cell with the smallest index in the cell to which the CORESET associated with CSS in the third CORESET belongs; wherein, the third CORESET includes: among the M CORESETs The CORESET of the associated PDCCH repetition.
  • the third reference CORESET is specifically: the CORESET that belongs to the third CORESET and is associated with the USS with the smallest index among the cells with the smallest index among the cells to which the CORESETs associated with the USS in the third CORESET belong.
  • the third reference CORESET is specifically: the CORESET that belongs to the fourth CORESET and is associated with the minimum index CSS in the cell with the smallest index among the CORESETs associated with the CSS in the fourth CORESET; wherein, the fourth CORESET includes: among the M CORESETs Among the CORESETs associated with the CORESET with the same QCL type D attribute as the second reference CORESET, a CORESET with a QCL type D attribute different from that of the second reference CORESET; or, the fourth CORESET includes: the associated PDCCH repetition in the M CORESETs A CORESET that does not have the same QCL type D attribute as the second reference CORESET.
  • the third reference CORESET is specifically: the CORESET belonging to the fourth CORESET and associated with the USS with the smallest index among the cells with the smallest index among the cells to which the CORESETs associated with the USS in the fourth CORESET belong.
  • the second reference CORESET is specifically: in the cells to which the CORESETs associated with CSS in the fifth CORESET belong In the cell with the smallest index, belongs to the fifth CORESET and is associated with the CORESET with the smallest index CSS; wherein, the fifth CORESET includes: the CORESET associated with PDCCH repetition among the M CORESETs.
  • the second reference CORESET is specifically: the respective cells of the CORESETs associated with the USS in the fifth CORESET Among the cells with the smallest index in , the CORESET that belongs to the fifth CORESET and is associated with the smallest index USS.
  • the third reference CORESET is specifically: the cell with the smallest index among the cells to which the CORESET associated with CSS in the sixth CORESET belongs to the sixth CORESET and has the smallest association The CORESET of the index CSS; wherein, the sixth CORESET includes: among the CORESETs associated with the CORESET that is the same as the QCL type D attribute of the second reference CORESET among the M CORESETs, the QCL type D attribute of the second reference CORESET is not the same CORESET; or, the sixth CORESET includes: among the CORESETs associated with PDCCH repetition in the M CORESETs, the CORESETs whose QCL type D attribute is different from that of the second reference CORESET.
  • the third reference CORESET is specifically: the respective cells of the CORESETs associated with the USS in the sixth CORESET Among the cells with the smallest index in , the CORESET that belongs to the sixth CORESET and is associated with the smallest index USS.
  • FIG. 5 provides a block diagram of functional units of another channel monitoring device.
  • the channel monitoring device 500 includes: a processing unit 502 and a communication unit 503 .
  • the processing unit 502 is configured to control and manage actions of network devices.
  • the processing unit 502 is configured to support the network device to execute the steps in FIG. 3 and other processes used in the technical solutions described in this application.
  • the communication unit 503 is used to support communication between the network device and other devices in the wireless communication system.
  • the channel monitoring device 500 may further include a storage unit 501 for storing program codes executed by the channel monitoring device 500 and transmitted data.
  • channel monitoring device 500 may be a chip or a chip module.
  • the processing unit 502 may be a processor or a controller, such as a central processing unit (central processing unit, CPU), a general processor, a digital signal processor (digital signal processor, DSP), an application-specific integrated circuit (application-specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processing unit 502 may also be a combination that implements computing functions, for example, a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like.
  • the communication unit 503 may be a communication interface, a transceiver, a transceiver circuit, etc., and the storage unit 501 may be a memory.
  • the processing unit 502 is a processor
  • the communication unit 503 is a communication interface
  • the storage unit 501 is a memory
  • the channel monitoring apparatus 500 involved in this embodiment of the present application may be the network device shown in FIG. 7 .
  • the processing unit 502 is configured to perform any step performed by the network device in the above method embodiments, and when performing data transmission such as sending, may optionally call the communication unit 503 to complete corresponding operations. Detailed description will be given below.
  • the processing unit 502 is configured to: configure M CORESETs in overlapping PDCCH monitoring opportunities on the active downlink BWP, and there are repeated PDCCHs in the PDCCH candidates associated with the M CORESETs, and the value of M is an integer greater than or equal to 1.
  • the terminal can monitor the PDCCH in the M CORESETs, so as to monitor the PDCCH in the repeated CORESETs associated with the PDCCH, improve the reliability of the PDCCH, and ensure the flexibility, stability and reliability of system communication.
  • the quasi-co-located QCL type D attributes of all CORESETs in M CORESETs are the same; or, there are CORESETs with different QCL type D attributes in M CORESETs; or, there are QCL type D in M CORESETs CORESET with the same attributes.
  • the M CORESETs include a first reference CORESET and/or a CORESET having the same quasi-co-located QCL type D attribute as the first reference CORESET, and the first reference CORESET is one of the M CORESETs; or, The M CORESETs include a second reference CORESET and/or a CORESET with the same QCL type D attribute as the second reference CORESET, and a third reference CORESET and/or a CORESET with the same QCL type D attribute as the third reference CORESET; wherein, the first The second reference CORESET is one of the M CORESETs, the third reference CORESET is one of the M CORESETs, and the QCL type D attribute of the second reference CORESET is different from that of the third reference CORESET.
  • the first reference CORESET is specifically: each of the CORESETs associated with the CSS in the first CORESET The CORESET that belongs to the first CORESET and is associated with the minimum index CSS in the cell with the smallest index among the cells to which it belongs; wherein, the first CORESET includes: a CORESET that is associated with PDCCH repetition among the M CORESETs.
  • the first reference CORESET is specifically: the CORESET associated with the user-specific search space USS in the first CORESET
  • the second reference CORESET is specifically: the first cell set contains a CORESET associated with a CSS Among the cells with the smallest index among the cells, the CORESET with the smallest index CSS is associated; wherein, the first set of cells includes: the cells corresponding to M CORESETs.
  • the second reference CORESET is specifically: the first cell set contains the associated USS The CORESET associated with the smallest index USS in the cell with the smallest index among the cells of the CORESET.
  • the second reference CORESET is specifically: in the cells to which the CORESETs associated with the CSS in the second CORESET belong In the cell with the smallest index, the CORESET that belongs to the second CORESET and is associated with the CSS with the smallest index; wherein, the second CORESET includes: CORESETs that are not associated with PDCCH repetition among the M CORESETs.
  • the second reference CORESET is specifically: the respective cells of the CORESETs associated with the USS in the second CORESET The CORESET belonging to the second CORESET and associated with the smallest index USS in the cell with the smallest index in .
  • the third reference CORESET is specifically: the CORESET that belongs to the third CORESET and is associated with the smallest index CSS in the cell with the smallest index in the cell to which the CORESET associated with CSS in the third CORESET belongs; wherein, the third CORESET includes: among the M CORESETs The CORESET of the associated PDCCH repetition.
  • the third reference CORESET is specifically: the CORESET that belongs to the third CORESET and is associated with the USS with the smallest index among the cells with the smallest index among the cells to which the CORESETs associated with the USS in the third CORESET belong.
  • the third reference CORESET is specifically: the CORESET that belongs to the fourth CORESET and is associated with the minimum index CSS in the cell with the smallest index among the CORESETs associated with the CSS in the fourth CORESET; wherein, the fourth CORESET includes: among the M CORESETs Among the CORESETs associated with the CORESET with the same QCL type D attribute as the second reference CORESET, a CORESET with a QCL type D attribute different from that of the second reference CORESET; or, the fourth CORESET includes: the associated PDCCH repetition in the M CORESETs A CORESET that does not have the same QCL type D attribute as the second reference CORESET.
  • the third reference CORESET is specifically: the CORESET belonging to the fourth CORESET and associated with the USS with the smallest index among the cells with the smallest index among the cells to which the CORESETs associated with the USS in the fourth CORESET belong.
  • the second reference CORESET is specifically: in the cells to which the CORESETs associated with CSS in the fifth CORESET belong In the cell with the smallest index of , it belongs to the fifth CORESET and is associated with the CORESET with the smallest index CSS; the fifth CORESET includes: the CORESET associated with PDCCH repetition among the M CORESETs.
  • the second reference CORESET is specifically: the respective cells of the CORESETs associated with the USS in the fifth CORESET Among the cells with the smallest index in , the CORESET that belongs to the fifth CORESET and is associated with the smallest index USS.
  • the third reference CORESET is specifically: in the respective cells of the CORESET associated with CSS in the sixth CORESET The CORESET that belongs to the sixth CORESET and is associated with the smallest index CSS in the cell with the smallest index; wherein, the sixth CORESET includes: among the CORESETs associated with the CORESET that has the same QCL type D attribute as the second reference CORESET among the M CORESETs, A CORESET that is different from the QCL type D attribute of the second reference CORESET; or, the sixth CORESET includes: among the CORESETs associated with PDCCH repetition in the M CORESETs, a CORESET that is different from the QCL type D attribute of the second reference CORESET.
  • the third reference CORESET is specifically: the respective cells of the CORESETs associated with the USS in the sixth CORESET Among the cells with the smallest index in , the CORESET that belongs to the sixth CORESET and is associated with the smallest index USS.
  • FIG. 6 is a schematic structural diagram of a terminal provided in an embodiment of the present application.
  • the terminal 600 includes a processor 610 , a memory 620 , a communication interface 630 , and a communication bus for connecting the processor 610 , the memory 620 , and the communication interface 630 .
  • Memory 620 includes, but is not limited to, random access memory (random access memory, RAM), read-only memory (read-only memory, ROM), erasable programmable read-only memory (erasable programmable read-only memory, EPROM) or A portable read-only memory (compact disc read-only memory, CD-ROM), the memory 620 is used to store program codes executed by the terminal 600 and transmitted data.
  • random access memory random access memory
  • ROM read-only memory
  • EPROM erasable programmable read-only memory
  • a portable read-only memory compact disc read-only memory, CD-ROM
  • the communication interface 630 is used to receive and transmit data.
  • the processor 610 may be one or more CPUs. In the case where the processor 610 is one CPU, the CPU may be a single-core CPU or a multi-core CPU.
  • the processor 610 in the terminal 600 is used to read one or more programs 621 stored in the memory 620, and perform the following operations: If there are M CORESETs in the overlapping PDCCH listening opportunities on the active downlink BWP, and the M CORESETs are associated with If there is a repeated PDCCH among the PDCCH candidates, the PDCCH is monitored in the M CORESETs, and the value of M is an integer greater than or equal to 1.
  • each operation can use the corresponding description of the method embodiment shown in FIG. 2 above, and the terminal 600 can be used to execute the method on the terminal side of the above method embodiment of the present application, which will not be described in detail here.
  • FIG. 7 is a schematic structural diagram of a network device provided by an embodiment of the present application.
  • the network device 700 includes a processor 710 , a memory 720 , a communication interface 730 , and a communication bus for connecting the processor 710 , the memory 720 , and the communication interface 730 .
  • Memory 720 includes, but is not limited to, random access memory (random access memory, RAM), read-only memory (read-only memory, ROM), erasable programmable read-only memory (erasable programmable read-only memory, EPROM) or A portable read-only memory (compact disc read-only memory, CD-ROM), the memory 720 is used to store program codes executed by the network device 700 and transmitted data.
  • random access memory random access memory
  • ROM read-only memory
  • EPROM erasable programmable read-only memory
  • a portable read-only memory compact disc read-only memory, CD-ROM
  • the communication interface 730 is used to receive and transmit data.
  • the processor 710 may be one or more CPUs. In the case where the processor 710 is one CPU, the CPU may be a single-core CPU or a multi-core CPU.
  • the processor 710 in the network device 700 is configured to read one or more programs 721 stored in the memory 720, and perform the following operations: configure M CORESETs in overlapping PDCCH listening opportunities on the active downlink BWP, and the M CORESETs There is a repeated PDCCH among the associated PDCCH candidates, and the value of M is an integer greater than or equal to 1.
  • the terminal can monitor the PDCCH in the M CORESETs, so as to monitor the PDCCH in the repeated CORESETs associated with the PDCCH, improve the reliability of the PDCCH, and ensure the flexibility, stability and reliability of system communication.
  • An embodiment of the present application also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program for electronic data exchange, wherein the computer program enables the computer to execute the terminal or manage some or all of the steps described by the device.
  • the embodiment of the present application also provides a computer program product, wherein the computer program product includes a computer program, and the computer program is operable to enable the computer to perform part or all of the functions described by the terminal or the management device in the above method embodiments. step.
  • the computer program product may be a software installation package.
  • the steps of the methods or algorithms described in the embodiments of the present application may be implemented in the form of hardware, or may be implemented in the form of a processor executing software instructions.
  • Software instructions can be composed of corresponding software modules, and software modules can be stored in RAM, flash memory, ROM, erasable programmable read-only memory (erasable programmable ROM, EPROM), electrically erasable programmable read-only memory (electrically EPROM, EEPROM), registers, hard disk, removable hard disk, compact disc read-only (CD-ROM), or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium.
  • the storage medium may also be a component of the processor.
  • the processor and storage medium can be located in the ASIC.
  • the ASIC can be located in the terminal or management device. Certainly, the processor and the storage medium may also exist in the terminal or the management device as discrete components.
  • the functions described in the embodiments of the present application may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it 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.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions may be stored in, or transmitted from, one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions can be sent from a 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.) Transmission to another website site, computer, server or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media.
  • the available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital video disc (digital video disc, DVD)), or a semiconductor medium (for example, a solid state disk (solid state disk, SSD)) Wait.
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, a digital video disc (digital video disc, DVD)
  • a semiconductor medium for example, a solid state disk (solid state disk, SSD)
  • each module/unit contained in each device and product described in the above embodiments may be software modules/units, hardware modules/units, or partly software modules/units and partly hardware modules/units.
  • each module/unit contained therein may be realized by hardware such as a circuit, or at least some modules/units may be realized by a software program, and the software program Running on the integrated processor inside the chip, the remaining (if any) modules/units can be realized by means of hardware such as circuits; They are all realized by means of hardware such as circuits, and different modules/units can be located in the same component (such as chips, circuit modules, etc.) or different components of the chip module, or at least some modules/units can be realized by means of software programs,
  • the software program runs on the processor integrated in the chip module, and the remaining (if any) modules/units can be realized by hardware such as circuits; /Units can be realized by means of hardware such as circuits, and different modules/units can be located in

Landscapes

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

Abstract

本申请实施例公开了一种信道监听方法与装置、终端和网络设备;该方法包括:若在活跃下行带宽部分BWP上重叠的物理下行控制信道PDCCH监听时机中存在M个控制资源集CORESET,且该M个CORESET关联的PDCCH候选中存在重复的PDCCH,则终端在该M个CORESET中监听PDCCH,M的取值为大于或等于1的整数,从而实现在关联PDCCH重复的CORESETs中监听PDCCH,提升PDCCH的可靠性,进而保证系统通信的灵活性、稳定性和可靠性。

Description

信道监听方法与装置、终端和网络设备 技术领域
本申请涉及通信技术领域,尤其涉及一种信道监听方法与装置、终端和网络设备。
背景技术
目前,第三代合作伙伴计划(3rd Generation Partnership Project,3GPP)正在标准化支持物理下行控制信道重复(physical downlink control channel repetition,PDCCH repetition),其实现如下:由于一个搜索空间可能会关联多个PDCCH候选,因此网络可以在不同的搜索空间各自关联的PDCCH候选中配置重复的PDCCH,从而实现PDCCH重复,进而提升PDCCH的可靠性。
例如,一个搜索空间所关联的PDCCH候选与另一个搜索空间所关联的PDCCH候选重复(或相同)。也就是说,一个搜索空间所关联的PDCCH候选与另一个搜索空间所关联的PDCCH候选之间具有相同的PDCCH内容,如PDCCH候选承载的下行控制信息(downlink control information,DCI)的内容相同。
然而,由于一个搜索空间又会关联一个控制资源集(control resource set,CORESET),因此重复的PDCCH各自可能关联不同或者相同的CORESET。可见,在存在PDCCH重复的情况下,终端如何监听PDCCH,还需要进一步研究。
发明内容
本申请实施例提供一种信道监听方法与装置、终端和网络设备,以期望实现在关联PDCCH重复的CORESETs中监听PDCCH,提升PDCCH的可靠性,进而保证系统通信的灵活性、稳定性和可靠性。
第一方面,本申请实施例提供一种信道监听方法,包括:
若在活跃(active)下行带宽部分BWP上重叠的物理下行控制信道PDCCH监听时机中存在M个控制资源集CORESET,且所述M个CORESET关联的PDCCH候选中存在重复的PDCCH,则终端在所述M个CORESET中监听PDCCH,所述M的取值为大于或等于1的整数。
可以看出,本申请实施例中,若在活跃下行BWP上重叠的PDCCH监听时机中存在M个CORESET,且该M个CORESET关联的PDCCH候选中存在重复的PDCCH,则在该M个CORESET中监听PDCCH,从而实现在关联PDCCH重复的CORESETs中监听PDCCH,提升PDCCH的可靠性,进而保证系统通信的灵活性、稳定性和可靠性。
第二方面,本申请实施例提供一种信道监听方法,包括:
在活跃下行带宽部分BWP上重叠的物理下行控制信道PDCCH监听时机中,网络设备配置M个控制资源集CORESET,且所述M个CORESET关联的PDCCH候选中存在重复的PDCCH,所述M的取值为大于或等于1的整数。
可以看出,本申请实施例中,在活跃下行BWP上重叠的PDCCH监听时机中,网络设备向终端配置的M个CORESET关联的PDCCH候选中存在重复的PDCCH。因此,终端可以在该M个CORESET中监听PDCCH,从而实现在关联PDCCH重复的CORESETs中监听PDCCH,提升PDCCH的可靠性,进而保证系统通信的灵活性、稳定性和可靠性。
第三方面,本申请实施例提供一种信道监听装置,所述装置包括处理单元,所述处理单元用于:
若在活跃下行带宽部分BWP上重叠的物理下行控制信道PDCCH监听时机中存在M个控制资源集CORESET,且所述M个CORESET关联的PDCCH候选中存在重复的PDCCH,则在所述M个CORESET中监听PDCCH,所述M的取值为大于或等于1的整数。
第四方面,本申请实施例提供一种监听装置,所述装置包括处理单元,所述处理单元用于:
在活跃下行带宽部分BWP上重叠的物理下行控制信道PDCCH监听时机中,配置M个控制资源集CORESET,且所述M个CORESET关联的PDCCH候选中存在重复的PDCCH,所述M的取值为大于或等于1的整数。
第五方面,本申请实施例提供一种终端,包括处理器、存储器、通信接口以及一个或多个程序,其中,所述一个或多个程序被存储在所述存储器中,并且被配置由所述处理器执行,所述一个或多个程序包括用于执行本申请实施例第一方面中的步骤的指令。
第六方面,本申请实施例提供一种网络设备,包括处理器、存储器、通信接口以及一个或多个程序,其中,所述一个或多个程序被存储在所述存储器中,并且被配置由所述处理器执行,所述一个或多个程序包括用于执行本申请实施例第二方面中的步骤的指令。
第七方面,本申请实施例提供一种计算机可读存储介质,其中,所述计算机可读存储介质存储用于电子数据交换的计算机程序,其中,所述计算机程序使得计算机执行如本申请实施例第一方面或第二方面中所描述的部分或全部步骤。
第八方面,本申请实施例提供一种计算机程序,其中,所述计算机程序可操作来使计算机执行如本申请实施例第一方面或第二方面中所描述的部分或全部步骤。该计算机程序可以为一个软件安装包。
附图说明
为了更清楚地说明本申请实施例中的技术方案,下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本申请的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1是本申请实施例提供的一种无线通信系统的架构示意图;
图2是本申请实施例提供的一种信道监听方法的流程示意图;
图3是本申请实施例提供的又一种信道监听方法的流程示意图;
图4是本申请实施例提供的一种信道监听装置的功能单元组成框图;
图5是本申请实施例提供的又一种信道监听装置的功能单元组成框图;
图6是本申请实施例提供的一种终端的结构示意图;
图7是本申请实施例提供的一种网络设备的结构示意图。
具体实施方式
为了本技术领域人员更好理解本申请的技术方案,下面结合本申请实施例中的附图,对本申请实施例中的技术方案进行描述。显然所描述的实施例是本申请一部分实施例,而不是全部的实施例。针对本申请中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本申请保护的范围。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别不同对象,而不是用于描述特定顺序。此外,术语“包括”和“具有”以及它们任何变形,意图在于覆盖不排他的包含。例如,包含了一系列步骤或单元的过程、方法、软件、产品或设备没有限定于已列出的步骤或单元,而是还包括没有列出的步骤或单元,或还包括对于这些过程、方法、产品或设备固有的其他步骤或单元。
在本文中提及“实施例”意味着,结合实施例描述的特定特征、结构或特性可以包含在本申请的至少一个实施例中。在说明书中的各个位置出现该短语并不一定均是指相同的实施例,也不是与其它实施例互斥的独立的或备选的实施例。本领域技术人员显式地和隐式地理解的是,本文所描述的实施例可以与其它实施例相结合。
需要说明的是,本申请实施例中出现的“连接”是指直接连接或者间接连接等各种连接方式,以实现设备间的通信,对此不做任何限定。本申请实施例中出现的“网络”与“系统”表达的是同一概念,通信系统即为通信网络。
本申请实施例的技术方案可以应用于各种无线通信系统,例如:全球移动通讯(Global System of Mobile communication,GSM)系统、码分多址(Code Division Multiple Access,CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access,WCDMA)系统、通用分组无线业务(General Packet Radio Service,GPRS)、长期演进(Long Term Evolution,LTE)系统、先进的长期演进(Advanced Long Term Evolution,LTE-A)系统、新无线(New Radio,NR)系统、NR系统的演进系统、非授权频谱上的LTE(LTE-based Access to Unlicensed Spectrum,LTE-U)系统、非授权频谱上的NR(NR-based Access to Unlicensed Spectrum,NR-U)系统、非地面通信网络(Non-Terrestrial Networks,NTN)系统、通用移动通信系统(Universal Mobile Telecommunication System,UMTS)、无线局域网(Wireless Local Area Networks,WLAN)、无线保真(Wireless Fidelity,WiFi)、第6代通信(6th-Generation,6G)系统或者其他通信系统等。
需要说明的是,传统的无线通信系统所支持的连接数有限,且易于实现。然而,随着通信技术的发展,无线通信系统不仅可以支持传统的无线通信系统,还可以支持如设备到设备(device to device,D2D)通信、机器到机器(machine to machine,M2M)通信、机器类型通信(machine type communication,MTC)、车辆间(vehicle to vehicle,V2V)通信、车联网(vehicle to everything,V2X)通信、窄带物联网(narrow band internet of things,NB-IoT)通信等,因此本申请实施例的技术方案也可以应用于上述无线通信系统。
可选地,本申请实施例的无线通信系统可以应用于波束赋形(beamforming)、载波聚合(carrier  aggregation,CA)、双连接(dual connectivity,DC)或者独立(standalone,SA)部署场景等。
可选地,本申请实施例的无线通信系统可以应用于非授权频谱。其中,非授权频谱也可以认为是共享频谱。或者,本实施例中的无线通信系统也可以应用于授权频谱。其中,授权频谱也可以认为是非共享频谱。
由于本申请实施例可能结合终端、网络设备描述各个实施例,因此下面将对涉及的终端、网络设备进行具体描述。
具体的,终端可以是用户设备(user equipment,UE)、远程/远端终端(remote UE)、中继设备(relay UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、移动设备、用户终端、智能终端、无线通信设备、用户代理或用户装置。需要说明的是,中继设备是能够为其他终端(包括远程终端)提供中继转发服务的终端。另外,终端还可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol,SIP)电话、无线本地环路(wireless local loop,WLL)站、个人数字助理(personal digital assistant,PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、下一代通信系统(例如NR通信系统)中的终端或者未来演进的公用陆地移动通信网络(public land mobile network,PLMN)中的终端等,对此不作具体限定。
进一步的,终端可以部署在陆地上,包括室内或室外、手持、穿戴或车载;可以部署在水面上(如轮船等);还可以部署在空中(如飞机、气球和卫星等)。
进一步的,终端可以是手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality,VR)终端设备、增强现实(augmented reality,AR)终端设备、工业控制(industrial control)中的无线终端设备、无人自动驾驶中的无线终端设备、远程医疗(remote medical)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备或者智慧家庭(smart home)中的无线终端设备等。
进一步的,终端可以包括具有收发功能的装置,例如芯片系统。其中,芯片系统可以包括芯片,还可以包括其它分立器件。
具体的,网络设备可以是用于与终端之间进行通信的设备,其负责空口侧的无线资源管理(radio resource management,RRM)、服务质量(quality of service,QoS)管理、数据压缩和加密、数据收发等。其中,网络设备可以是通信系统中的基站(base station,BS)或者部署于无线接入网(radio access network,RAN)以用于提供无线通信功能的设备。例如,GSM或CDMA通信系统中的基站(base transceiver station,BTS)、WCDMA通信系统中的节点B(node B,NB)、LTE通信系统中的演进型节点B(evolutional node B,eNB或eNodeB)、NR通信系统中的下一代演进型的节点B(next generation evolved node B,ng-eNB)、NR通信系统中的下一代节点B(next generation node B,gNB)、双链接架构中的主节点(master node,MN)、双链接架构中的第二节点或辅节点(secondarynode,SN)等,对此不作具体限制。
进一步的,网络设备还可以是核心网(core network,CN)中的其他设备,如访问和移动性管理功能(access and mobility management function,AMF)、用户计划功能(user plan function,UPF)等;还可以是无线局域网(wireless local area network,WLAN)中的接入点(access point,AP)、中继站、未来演进的PLMN网络中的通信设备、NTN网络中的通信设备等。
进一步的,网络设备可以包括具有为终端提供无线通信功能的装置,例如芯片系统。示例的,芯片系统可以包括芯片,还可以包括其它分立器件。
进一步的,网络设备可以与互联网协议(Internet Protocol,IP)网络进行通信。例如,因特网(internet)、私有的IP网或者其他数据网等。
需要说明的是,在一些网络部署中,网络设备可以是一个独立的节点以实现上述基站的所有功能,其可以包括集中式单元(centralized unit,CU)和分布式单元(distributed unit,DU),如gNB-CU和gNB-DU;还可以包括有源天线单元(active antenna unit,AAU)。其中,CU可以实现网络设备的部分功能,而DU也可以实现网络设备的部分功能。比如,CU负责处理非实时协议和服务,实现无线资源控制(radio resource control,RRC)层、服务数据适配(service data adaptation protocol,SDAP)层、分组数据汇聚(packet data convergence protocol,PDCP)层的功能。DU负责处理物理层协议和实时服务,实现无线链路控制(radio link control,RLC)层、媒体接入控制(medium access control,MAC)层和物理(physical,PHY)层的功能。另外,AAU可以实现部分物理层处理功能、射频处理及有源天线的相关功能。由于RRC层的信息最终会变成PHY层的信息,或者由PHY层的信息转变而来,因此,在该网络部署下,高层信令(如RRC层信令)可以认为是由DU发送的,或者由DU和AAU共同发送的。可以理解的是,网络设备可以包括CU、DU、AAU中的至少一个。另外,可以将CU划分为接入网(radio access network,RAN)中的网络设备,也可以将CU划分为核心网中的网络设备,对此不做具体限定。
进一步的,网络设备可以具有移动特性,例如网络设备可以为移动的设备。可选地,网络设备可以为卫星、气球站。例如,卫星可以为低地球轨道(low earth orbit,LEO)卫星、中地球轨道(medium earth orbit,MEO)卫星、地球同步轨道(geostationary earth orbit,GEO)卫星、高椭圆轨道(high elliptical orbit,HEO)卫星等。可选地,网络设备还可以为设置在陆地、水域等位置的基站。
进一步的,网络设备可以为小区提供服务,而该小区内的终端可以通过传输资源(如频谱资源)与网络设备进行通信。其中,该小区可以包括宏小区(macro cell)、小小区(small cell)、城市小区(metro cell)、微小区(micro cell)、微微小区(pico cell)和毫微微小区(femto cell)等。
结合上述描述,下面对本申请实施例的无线通信系统做一个示例性说明。
示例性的,本申请实施例的无线通信系统,请参阅图1。无线通信系统10可以包括终端110和网络设备120,而网络设备120可以是与终端110执行通信的设备。同时,网络设备120可以为特定的地理区域提供通信覆盖,并且可以与位于该覆盖区域内的终端110进行通信。
可选地,无线通信系统10还可以包括多个网络设备,并且每个网络设备的覆盖范围内可以包括一定数量的终端,对此不作具体限定。
可选地,无线通信系统10还可以包括网络控制器、移动管理实体等其他网络实体,对此不作具体限定。
可选地,无线通信系统10中的网络设备与终端之间的通信可以为无线通信或者有线通信,对此不作具体限制。
在对本申请实施例提供的信道监听方法进行详细介绍之前,再对本申请实施例所涉及的相关内容进行介绍。
1、带宽部分(bandwidth part,BWP)和重叠的PDCCH监听时机(overlapping PDCCH monitoring occasion)
BWP是小区总带宽的一个子集带宽,从而使得终端接收和发送的带宽不需要与小区总带宽一样大。其中,下行BWP(DL BWP)中可以包含至少一个关联搜索空间的控制资源集(control resource set,CORESET)。
重叠的PDCCH监听时机,可以理解为,PDCCH监听时机有重叠。
2、聚合等级(aggregation level)和控制信道单元(control channel element,CCE)
PDCCH的资源单元是CCE,并且1个CCE包含9个资源单元组(resource element group,REG)。其中,CCE是逻辑上的资源单位,且对应PRB上的9个REG。
一个PDCCH可以由n个连续的CCE组成。其中,n称作聚合等级,有4种聚合等级:{1,2,4,8}。若PDCCH对应的聚合等级为8,则表示一个PDCCH由8个连续的CCE组成。
3、搜索空间(search space)和控制资源集(control resource set,CORESET)
在5G NR系统中,由于系统的带宽较大以及终端解调能力的差异性,为了提高资源利用率、降低盲检复杂度,因此PDCCH在频域上可以不再占据整个频段。另外,为了增加系统灵活性,适配不同的场景,PDCCH在时域的起始位置也可配。因此,在5G NR系统中,通常将PDCCH在频域上占据的频段以及时域占用的OFDM符号数等信息封装在CORESET中,而将PDCCH起始OFDM符号、PDCCH监听周期以及其关联的CORESET等信息封装在搜索空间中。
搜索空间的类型可以包括公共搜索空间(common search space,CSS)和用户特定搜索空间(UE-specific search space,USS)。
需要说明的是,一个搜索空间会关联一个CORESET,如由高层参数controlResourceSetId指示或配置,并且一个搜索空间还可以关联多个PDCCH候选(PDCCH candidates),如由高层参数nrofCandidates指示或配置。因此,通过搜索空间的方式可以建立一个CORESET与多个PDCCH候选之间的关联关系。
另外,在某个重叠的PDCCH监听时机中,PDCCH候选所关联的CORESET可以配置有至少一个传输配置指示(transmission configuration indication,TCI)状态(state),并且高层可以通过TCI状态来配置QCL,而TCI状态可能会关联QCL-typeD。因此,PDCCH候选所关联的CORESET的TCI状态可能关联有QCL-typeD。
4、准共址(Quasi Co-Location,QCL)
为保证信号的正确接收和解调,标准协议引入具有QCL关系的参考信号概念,比如信道状态信息参考信号(channel state information reference signal,CSI-RS)、同步信号块(synchronization signal block,SSB),从而终端可以根据CSI-RS估计大尺度特征参数。其中,大尺度特征参数包括时延扩展、多普勒扩展、多普勒频移、平均增益、平均时延、空域信息等中的至少之一。例如,在LTE通信系统的版本11(Release 11)中,标准协议引入天线端口QCL。天线端口QCL可以表示天线端口发送出的信号会经过 相同的大尺度衰落,从而具有相同的大尺度特征参数。例如,当天线端口A和天线端口B之间满足QCL关系时,通过在天线端口A上的信号估计得到的大尺度特征参数同样适合于天线端口B上的信号。
另外,在5G NR系统中,终端和网络设备可能会配置多天线面板的大规模阵列结构,而不同的天线面板形成的波束的大尺度特性也会不同。此时,大尺度特性参数除了包括上述描述的时延扩展、多普勒扩展、多普勒频移、平均增益和平均时延之外,还包括接收到达角(angle of arival,AOA)、到达角扩展(angle of arival spread,AAS)、发射离开角(angle of departure,AOD)、离开角扩展(angle of departure spread,ADS)和空间相关性(spatialcorrelation)等。
5、天线端口准共址
在高层参数PDSCH-Config中可以为终端配置最多M个TCI状态,以用于根据检测到的PDCCH中的DCI来解码PDSCH,M取决于终端能力。其中,每个TCI状态包含用于配置一个或两个下行链路参考信号(如CSI-RS和/或SSB)与PDSCH的解调参考信号(demodulation reference symbol,DM-RS)端口、PDCCH的DM-RS端口或CSI-RS资源的CSI-RS端口之间的QCL关系的参数。QCL关系可以由用于第一个下行链路参考信号的高层参数qcl-Type1和用于第二个下行链路参考信号的qcl-Type2(如果配置第二个下行链路参考信号)来配置。对于有两个下行链路参考信号的情况,无论是否为同一种参考信号,该两个下行链路参考信号关联的QCL类型不应相同。其中,每个下行链路参考信号关联的QCL类型由QCL-Info中的高层参数qcl-Type,并且可以包括:
QCL类型A(QCL-typeA):{多普勒频移,多普勒扩展,平均时延,延时扩展};
QCL类型B(QCL-typeB):{多普勒频移,多普勒扩展};
QCL类型C(QCL-typeC):{多普勒频移,平均时延};
QCL类型D(QCL-typeD):{空间接收参数};等等。
其中,空间接收参数可以包括以下至少之一:AOA、平均AOA、AOA扩展、AOD、平均AOD、AOD扩展、接收天线空间相关性、发送天线空间相关性、发送波束、接收波束、资源标识等。此外,当QCL类型为QCL-TypeD时,TCI状态可以用于指示波束。同时,每个TCI状态可以给出(包含)1个或2个QCL类型参数。如果TCI状态包含2个QCL类型参数时,该QCL类型中会包含QCL-TypeD。也就是说,TCI状态可能会关联QCL-typeD。
另外,TCI状态可以由网络侧下发的激活命令(如MAC控制单元CE)激活以及由DCI中的TCI字段指示。例如,当TCI状态用于PDSCH的QCL类型指示时,网络设备可以先通过MAC CE激活2 N个激活TCI状态,再通过DCI中的N比特的TCI字段从该2 N个激活TCI状态中指示一个TCI状态。当N=3时,如果DCI中的TCI字段取值为‘000’,则该TCI指示由MAC CE激活的第一个TCI状态。另外,相对于该TCI状态给出的QCL类型参数,该TCI状态的参考信号与PDSCH的DM-RS端口是QCL的。
6、QCL-typeD属性相同
如何判断QCL-typeD属性是否相同,可以有:
→为了确定CORESET,一个SSB被认为具有与CSI-RS不同的QCL-typeD属性;
→为了确定CORESET,第一小区中与1个SSB关联的第一CSI-RS和第二小区中与该SSB关联的第二CSI-RS具有相同的QCL-typeD属性;等等。
例如,CORESET#1的TCI state对应的QCL-TypeD的参考信号是第一CSI-RS,CORESET#2的TCI state对应的QCL-TypeD的参考信号也是第一CSI-RS,则CORESET#1与CORESET#2之间具有相同的QCL-typeD属性。
结合上述描述,本申请实施例提供一种信道监听方法的流程示意图,请参阅图2,该方法包括:
S210、若在活跃下行BWP上重叠的PDCCH监听时机中存在M个CORESET,且该M个CORESET关联的PDCCH候选中存在重复的PDCCH,则终端在该M个CORESET中监听PDCCH,M的取值为大于或等于1的整数。
需要说明的是,网络可以通过高层参数(如controlResourceSetId)为每个搜索空间配置一个CORESET,即一个搜索空间可能关联一个CORESET。同时,网络还可以通过高层参数(如nrofCandidates)为每个搜索空间配置多个PDCCH候选,即一个搜索空间还可能关联多个PDCCH候选。因此,通过搜索空间的方式可以建立CORESET与PDCCH候选之间的关联关系,即一个CORESET关联多个PDCCH候选。
通过将不同的搜索空间各自关联的PDCCH候选之间建立映射关系,如一对一的映射关系,网络可以在不同的搜索空间各自关联的PDCCH候选中配置重复的PDCCH,从而实现PDCCH重复(PDCCH repetition),进而提升PDCCH的可靠性。
表1
Figure PCTCN2022091921-appb-000001
例如,如表1所示,当USS包括USS#1和USS#2时,若USS#1对应的聚合等级为4,则USS#1关联有2个PDCCH候选。同时,若USS#2对应的聚合等级为4,则USS#2关联有2个PDCCH候选。其中,若聚合等级为4,USS#1关联的第1个PDCCH候选只与USS#2关联的第1个PDCCH候选具有映射关系,而USS#1关联的第2个PDCCH候选只与USS#2关联的第2个PDCCH候选具有映射关系。因此,通过网络隐式或者显示地配置PDCCH重复,USS#1关联的第1个PDCCH候选可能与USS#2关联的第1个PDCCH候选相互重复(或相同)。也就是说,USS#1关联的第1个PDCCH候选可能与USS#2关联的第1个PDCCH候选之间具有相同的PDCCH内容(如DCI内容),即存在重复的PDCCH。同理,USS#1关联的第2个PDCCH候选可能与USS#2关联的第2个PDCCH候选相互重复(或相同)。可见,通过USS#1关联的CORESET所关联的PDCCH候选和USS#2关联的CORESET所关联的PDCCH候选中存在重复的PDCCH。
具体的,本申请实施例中的PDCCH重复,可以理解为,至少两个搜索空间(或不同的搜索空间)各自关联的PDCCH候选所传输的PDCCH内容相同(如PDCCH候选承载的DCI的内容相同)。
具体的,该M个CORESET关联的PDCCH候选中存在重复的PDCCH,可以理解为,在该M个CORESET关联的PDCCH候选中,存在所承载的PDCCH内容相同的至少两个PDCCH候选。
具体的,该M个CORESET关联的PDCCH候选中存在重复的PDCCH,可以理解为,在该M个CORESET关联的PDCCH候选中,存在被隐式地或者显示地配置为PDCCH重复的PDCCH候选。
也就是说,重复的PDCCH所关联的CORESET可能存在于不同的PDCCH监听时机中。例如,两个重复的PDCCH中的一个PDCCH所关联的CORESET属于该M个CORESET中的一个,但另一个PDCCH所关联的CORESET可能不属于该M个CORESET中的一个。也就是说,该两个重复的PDCCH所关联的CORESET可能存在于不同的PDCCH监听时机中。
具体的,关联PDCCH重复的搜索空间,可以理解为,若某个搜索空间关联的多个PDCCH候选与某些搜索空间关联的多个PDCCH候选之间存在重复的PDCCH,则该个搜索空间和该些搜索空间统称为关联PDCCH重复的搜索空间。
例如,若CSS#1关联的多个PDCCH候选和CSS#2关联的多个PDCCH候选之间存在重复的PDCCH,则CSS#1和CSS#2统称为关联PDCCH重复的搜索空间。
具体的,搜索空间与搜索空间关联,可以理解为,在关联PDCCH重复的搜索空间中的各个搜索空间之间具有关联关系。
例如,若CSS#1关联的多个PDCCH候选与CSS#2关联的多个PDCCH候选之间存在重复的PDCCH(或PDCCH重复),则CSS#1关联CSS#2。同理,若USS#1关联的多个PDCCH候选与USS#2关联的多个PDCCH候选之间存在重复的PDCCH,则USS#1关联USS#2。
具体的,关联PDCCH重复的CORESET,可以理解为,若某个CORESET关联的多个PDCCH候选与某些CORESET关联的多个PDCCH候选之间存在重复的PDCCH,则该个CORESET和该些CORESET统称为关联PDCCH重复的CORESET。
例如,若CORESET#1关联的多个PDCCH候选和CORESET#2关联的多个PDCCH候选之间存在重复的PDCCH,则CORESET#1和CORESET#2统称为关联PDCCH重复的CORESET。
具体的,CORESET与CORESET关联,可以理解为,关联PDCCH重复的CORESET中的各个CORESET之间具有关联关系。例如,若CORESET#1关联的多个PDCCH候选和CORESET#2关联的多个PDCCH候选之间存在重复的PDCCH,则CORESET#1关联CORESET#2。
综上所述,本申请实施例考虑如下:若在活跃下行BWP上重叠的PDCCH监听时机中存在M个CORESET,且该M个CORESET关联的PDCCH候选中存在重复的PDCCH,则在该M个CORESET中进行PDCCH的监听,从而实现在关联有PDCCH重复的CORESET中监听PDCCH,提升PDCCH的可靠性,进行保证通信系统的灵活性、稳定性和可靠性。
具体的,该M个CORESET中的所有CORESET的准共址QCL类型D属性相同;或者,该M个CORESET 中存在QCL类型D属性不相同的CORESET;或者,该M个CORESET中存在QCL类型D属性相同的CORESET。
需要说明的是,在某个活跃BWP上重叠的PDCCH监听时机中,PDCCH候选所关联的CORESET可以配置有至少一个TCI状态,并且高层可以通过TCI状态来配置QCL,而TCI状态可能会关联QCL-typeD。因此,PDCCH候选所关联的CORESET的TCI状态关联有QCL-typeD。其中,本申请实施例可以通过QCL-typeD对应的参考信号来判断QCL-typeD属性是否相同。
另外,重复的PDCCH之间可能会关联相同或者不同的CORESET,而不同的CORESET的QCL-typeD属性不同。因此,本申请实施例的终端既可以在具有不同的QCL-typeD属性的CORESET中监听PDCCH,也可以在具有相同的QCL-typeD属性的CORESET中监听PDCCH,从而有利于保证通信系统的灵活性、稳定性和可靠性。
综上所述,若在活跃下行BWP上重叠的PDCCH监听时机中存在M个CORESET,该M个CORESET关联的PDCCH候选中存在重复的PDCCH。同时,该M个CORESET中的所有CORESET的QCL-typeD属性相同(即该M个CORESET中的所有CORESET具有一个QCL-typeD属性);或者,该M个CORESET中存在QCL-typeD属性不相同的CORESET(即该M个CORESET中的CORESET具有多个QCL-typeD属性);或者,该M个CORESET中存在QCL-typeD属性相同的CORESET(即该M个CORESET中的CORESET具有多个QCL-typeD属性)。因此,终端在该M个CORESET中监听PDCCH可能存在以下情形:
1、终端可以仅在具有一个QCL-typeD属性的CORESETs中监听PDCCH,即“情形一”;
2、终端在具有多个QCL-typeD属性的CORESETs中监听PDCCH,即“情形二”。
下面本申请实施例对“情形一”和“情形二”进行具体说明。
情形一:
在一个可能的示例中,终端在该M个CORESET中监听PDCCH,可以包括:终端在第一参考CORESET和/或与第一参考CORESET具有相同QCL类型D属性的CORESET中监听PDCCH,第一参考CORESET为该M个CORESET中的一个CORESET。
具体的,第一参考CORESET可以为具有一个QCL-typeD属性的CORESET。
具体的,与第一参考CORESET具有相同QCL-typeD属性的CORESET可以包括:该M个CORESET中的一个或者多个。
需要说明的是,首先,由于一个CORESET可以关联1个TCI状态,并且每个TCI状态可能关联QCL-typeD,因此本申请实施例可以通过判断不同的CORESET的TCI状态对应的QCL-typeD属性之间是否相同的方式来选择相应的CORESET。基于此,与第一参考CORESET具有相同QCL-typeD属性的CORESET,可以理解为,本申请实施例可以将第一参考CORESET作为参考性的一个CORESET,再通过第一参考CORESET从该M个CORESET中确定出与第一参考CORESET具有相同QCL-typeD属性的CORESET以得到其他CORESETs,最终实现在该其他CORESETs中监听PDCCH。
其次,第一参考CORESET可以通过一定准则从该M个CORESET中确定出。同时,针对“情形一”,可以理解为,终端仅在具有一个QCL-typeD属性的CORESETs中监听PDCCH,该一个QCL-typeD属性为第一参考CORESET的QCL-typeD属性。
最后,终端监听PDCCH可以包括以下3种原则:在第一参考CORESET中监听PDCCH;在第一参考CORESET以及与第一参考CORESET具有相同QCL-typeD属性的CORESET中监听PDCCH;在与第一参考CORESET具有相同QCL-typeD属性的CORESET中监听PDCCH。
下面对其进行举例说明。
举例说明1:在某个活跃下行BWP上重叠的PDCCH监听时机中,存在下述CORESET(M=4的情况):CORESET#0(关联1个TCI state)、CORESET#1(关联1个TCI state)、CORESET#2(关联1个TCI state)、CORESET#3(关联1个TCI state);
→CORESET#1关联的多个PDCCH候选与CORESET#2关联的多个PDCCH候选之间存在重复的PDCCH,即CORESET#1关联CORESET#2;
→CORESET#1的TCI state对应的QCL-typeD属性与CORESET#0的TCI state对应的QCL-typeD属性相同;
→CORESET#1的TCI state对应的QCL-typeD属性与CORESET#3的TCI state对应的QCL-typeD属性相同;
→CORESET#2的TCI state对应的QCL-typeD属性与CORESET#0的TCI state对应的QCL-typeD属性不相同。
当通过一定的准则确定出第一参考CORESET为“CORESET#1”时,由于CORESET#1的TCI state 对应的QCL-typeD属性与CORESET#0和CORESET#3相同,而CORESET#1的TCI state对应的QCL-typeD属性与CORESET#2不相同,因此终端在“CORESET#0”、“CORESET#1”和“CORESET#3”中监听PDCCH。
结合上述描述,下面本申请实施例将对从该M个CORESET中确定第一参考CORESET的准则进行具体说明。
准则1-1:
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第一CORESET中存在关联CSS的CORESET,则第一参考CORESET具体为:第一CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于第一CORESET且关联最小索引CSS的CORESET;其中,第一CORESET包括:在M个CORESET中的关联PDCCH重复的CORESET。
需要说明的是,首先,由于一个搜索空间可以关联一个CORESET,而搜索空间的类型可以包括CSS和USS,因此每个CORESET可以关联(或包含)CSS和/或USS。
其次,在活跃下行BWP上重叠的PDCCH监听时机中,该M个CORESET中的每个CORESET可能关联(或属于)一个小区,并且各小区有其对应的索引(index),即小区索引。因此,本申请实施例可以按照最小索引原则从各小区中选择出最小索引的小区。同理,各搜索空间(CSS和/或USS)也有其对应的索引,因此本申请实施例也可以按照最小索引原则从关联搜索空间的CORESET中选择出关联最小索引搜索空间的CORESET。
例如,在某个活跃下行BWP上重叠的PDCCH监听时机中,存在4个CORESET,该4个CORESETE关联的小区包括小区1和小区2。其中,小区1关联有CORESET#1_1(关联1个TCI state,关联CSS#1)和CORESET#1_2(关联1个TCI state,关联CSS#2);小区2关联有CORESET#2_1(关联1个TCI state,关联USS#1)和CORESET#2_2(关联1个TCI state,关联CSS#3)。同时,小区1的索引小于小区2的索引,CSS#1的索引小于CSS#2的索引。
再次,在活跃下行BWP上重叠的PDCCH监听时机中,由于在该M个CORESET中可能存在关联PDCCH重复的CORESET,因此本申请实施例考虑将该M个CORESET中的关联PDCCH重复的CORESET作为第一CORESET。也就是说,第一CORESET中的各CORESET关联重复的PDCCH。
例如,在“举例说明1”中,在某个活跃下行BWP上重叠的PDCCH监听时机中,存在4个CORESET,且CORESET#1关联CORESET#2。因此,第一CORESET包括CORESET#1和CORESET#2。
又例如,在“举例说明1”中,在某个活跃下行BWP上重叠的PDCCH监听时机中,存在4个CORESET,且CORESET#1关联了重复的PDCCH。因此,第一CORESET包括CORESET#1。
最后,在第一CORESET中可能存在有关联CSS的CORESET,也可能不存在关联CSS的CORESET。因此,若第一CORESET中存在关联CSS的CORESET,则将第一CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于第一CORESET且关联最小索引CSS的CORESET作为第一参考CORESET。也就是说,先从第一CORESET中确定出关联CSS的CORESET以得到至少一个CORESET,再确定该至少一个CORESET各自所属的小区以得到至少一个小区,紧接从该至少一个小区中确定出最小索引的小区,最终从该最小索引的小区中确定出属于第一CORESET且关联最小索引CSS的CORESET以得到第一参考CORESET。
可见,通过本示例所述的“准则1-1”,本申请实施例可以准确、快速在活跃下行BWP上重叠的PDCCH监听时机中确定出一个关联PDCCH重叠、关联最小小区索引以及关联最小CSS索引的COSESET(即第一参考CORESET),从而实现在关联PDCCH重复的CORESETs中监听PDCCH,进而保证系统通信的灵活性、稳定性和可靠性。
准则1-2:
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第一CORESET中不存在关联CSS的CORESET,则第一参考CORESET具体为:第一CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于第一CORESET且关联最小索引USS的CORESET。
其中,第一CORESET包括:在M个CORESET中的关联PDCCH重复的CORESET。
需要说明的是,结合上述同理可知,USS也有其对应的索引,因此本申请实施例也可以按照索引最小原则从关联(包含)USS的多个CORESET中确定出关联最小索引USS的CORESET。
另外,若第一CORESET中不存在关联CSS的CORESET,则将第一CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于第一CORESET且关联最小索引USS的CORESET作为第一参考CORESET。也就是说,先从第一CORESET中确定出关联USS的CORESET以得到至少一个CORESET,再确定该至少一个CORESET各自所属的小区以得到至少一个小区,紧接从该至少一个小区中确定出最 小索引的小区,最终从该最小索引的小区中确定出属于第一CORESET且关联最小索引USS的CORESET以得到第一参考CORESET。
可见,通过本示例的“准则1-2”,本申请实施例可以准确、快速在活跃下行BWP上重叠的PDCCH监听时机中确定出一个关联PDCCH重叠、关联最小小区索引以及关联最小USS索引的COSESET(即第一参考CORESET),从而实现在关联PDCCH重复的CORESETs中监听PDCCH,进而保证系统通信的灵活性、稳定性和可靠性。
下面本申请实施例对“准则1-1”和“准则1-2”做一个举例说明。
举例说明2:在某个活跃下行BWP上重叠的PDCCH监听时机中,存在下述CORESETs(M=6的情况):
小区1:CORESET#0(关联1个TCI state,关联CSS#0)、CORESET#2(关联1个TCI state,关联CSS#1)、CORESET#3(1个TCI state,关联CSS#4)、CORESET#4(2个TCI state,关联USS#1);
→CSS#1关联的多个PDCCH候选与CSS#4关联的多个PDCCH候选之间存在重复的PDCCH,即CSS#1关联CSS#4(或CORESET#2关联CORESET#3);
→小区1的CORESET#2的TCI state对应的QCL-typeD属性与小区1的CORESET#0的TCI state对应的QCL-typeD属性相同;
→小区1的CORESET#2的TCI state对应的QCL-typeD属性与小区1的CORESET#3的TCI state对应的QCL-typeD属性不相同;
→小区1的CORESET#4的TCI state对应的QCL-typeD属性与小区1的CORESET#2的TCI state对应的QCL-typeD属性相同;
小区2:CORESET#1(1个TCI state,关联USS#2)、CORESET#2(1个TCI state,关联CSS#3);
→小区2的CORESET#2的TCI state对应的QCL-typeD属性与小区2的CORESET#1的TCI state对应的QCL-typeD属性相同;
→小区2的CORESET#2的TCI state对应的QCL-typeD属性与小区1的CORESET#2的TCI state对应的QCL-typeD属性相同;
首先,在该活跃下行BWP上重叠的PDCCH监听时机中,上述CORESETs(M=6)关联的小区包括小区1和小区2。其中,小区1关联的CORESETs包括CORESET#0、CORESET#2、CORESET#3、CORESET#4,小区2关联的CORESETs包括CORESET#1、CORESET#2。小区1的CORESET#0关联1个TCI state,并且小区1的CORESET#0关联的搜索空间包含CSS#0,该CSS#0关联多个PDCCH候选,其他CORESETs依次可知。
其次,小区1的索引小于小区2的索引,CSS#0的索引小于CSS#1的索引,CSS#1的索引小于CSS#4的索引。
再次,上述CORESETs中存在重复的PDCCH,即小区1的CORESET#2和小区1的CORESET#3(即第一CORESET)。由于小区1的CORESET#2和小区1的CORESET#3都为关联CSS的CORESET,即第一CORESET中存在关联CSS的CORESET,因此通过“准则1-1”确定出第一参考CORESET为小区1的“CORESET#2”:
从第一CORESET中确定出关联CSS的CORESET,得到小区1的“CORESET#2”和小区1的“CORESET#3”;确定小区1的“CORESET#2”和小区1的CORESET#3”各自所属的小区,小区1;从小区1中确定出属于第一CORESET且关联最小索引CSS的CORESET,得到小区1的“CORESET#2”。
紧接,从上述CORESETs(M=6)中确定出与第一参考CORESET具有相同QCL-typeD属性的其他CORESETs,得到小区1的“CORESET#0”、小区2的“CORESET#4”、小区2的“CORESET#1”和小区2的“CORESET#2”。
最后,终端在小区1的“CORESET#2”、小区1的“CORESET#0”、小区1的“CORESET#4”、小区2的“CORESET#1”和小区2的“CORESET#2”中监听PDCCH,从而实现在关联PDCCH重复的CORESETs中监听PDCCH。
情形二:
在一个可能的示例中,终端在该M个CORESET中监听PDCCH,可以包括:终端在第二参考CORESET和/或与第二参考CORESET具有相同QCL类型D属性的CORESET中监听PDCCH,以及在第三参考CORESE和/或与第三参考CORESET具有相同QCL类型D属性的CORESET中监听PDCCH;其中,第二参考CORESET为该M个CORESET中的一个CORESET,第三参考CORESET为M个CORESET中的一个CORESET,第二参考CORESET的QCL类型D属性与第三参考CORESET的QCL类型D属性不相同。
具体的,第二参考CORESET可以为具有一个QCL-typeD属性的CORESET。
具体的,与第二参考CORESET具有相同QCL-typeD属性的CORESET可以包括:该M个CORESET 中的一个或者多个。
具体的,第三参考CORESET可以为具有一个QCL-typeD属性的CORESET。
具体的,与第三参考CORESET具有相同QCL-typeD属性的CORESET可以包括:该M个CORESET中的一个或者多个。
需要说明的是,首先,针对“情形二”,可以理解为,终端需要在具有多个QCL-typeD属性的CORESETs中监听PDCCH。其中,终端监听PDCCH可以包括以下多种原则:在第二参考CORESET以及第三参考CORESET中监听PDCCH;在与第二参考CORESET具有相同QCL类型D属性的CORESET以及第三CORESET中监听PDCCH;在第二参考CORESET以及与第三参考CORESET具有相同QCL类型D属性的CORESET中监听PDCCH;在与第二参考CORESET具有相同QCL类型D属性的CORESET以及与第三参考CORESET具有相同QCL类型D属性的CORESET;在第二参考CORESET以及第三参考CORESET中监听PDCCH;在第二参考CORESET、与第二参考CORESET具有相同QCL类型D属性的CORESET以及第三CORESET中监听PDCCH;第二参考CORESET、与第二参考CORESET具有相同QCL类型D属性的CORESET以及第三CORESET中监听PDCCH;等等。
其次,与第二参考CORESET具有相同QCL-typeD属性的CORESET,可以理解为,本申请实施例可以将第二参考CORESET作为参考性的一个CORESET,再通过第二参考CORESET从该M个CORESET中确定出与第二参考CORESET具有相同QCL-typeD属性的CORESET以得到其他CORESETs,最终实现在该其他CORESETs中监听PDCCH。同理,与第三参考CORESET具有相同QCL-typeD属性的CORESET,可以理解为,本申请实施例可以将第三参考CORESET作为参考性的一个CORESET,再通过第三参考CORESET从该M个CORESET中确定出与第三参考CORESET具有相同QCL-typeD属性的CORESET以得到其他CORESETs,最终实现在该其他CORESETs中监听PDCCH。
最后,第二参考CORESET可以通过一定准则从该M个CORESET中确定出。同理,第三参考CORESET可以通过一定准则从该M个CORESET中确定出。
结合上述描述,下面本申请实施例将对该M个CORESET中确定第二参考CORESET和第三参考CORESET的准则进行具体说明。
准则2-1-1:
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第一小区集中存在包含关联CSS的CORESET的小区,则第二参考CORESET可以具体为:第一小区集中包含关联CSS的CORESET的小区中的最小索引的小区中关联最小索引CSS的CORESET。
其中,第一小区集包括:该M个CORESET对应的小区。
需要说明的是,在活跃下行BWP上重叠的PDCCH监听时机中,由于该M个CORESET中的每个CORESET可能对应(或关联)一个小区,因此本申请实施例的第一小区集包括该M个CORESET中的每个CORESET各自对应的小区。
另外,若第一小区集中存在包括关联CSS的CORESET的小区,则将第一小区集中包含关联CSS的CORESET的小区中的最小索引的小区中关联最小索引CSS的CORESET作为第二参考CORESET。也就是说,先从第一小区集中确定出包含关联CSS的CORESET的至少一个小区,再从该至少一个小区中确定出最小索引的小区,最终从该最小索引的小区中确定出关联最小索引CSS的CORESET以得到第二参考CORESET。
可见,与上述“第一参考CORESET”为一个关联PDCCH重叠、关联最小小区索引以及关联最小CSS/USS索引的COSESET不同,‘准则2-1-1’中的第二参考CORESET可以为一个关联最小小区索引以及关联最小CSS索引的COSESET。同时,通过本示例的“准则2-1-1”,本申请实施例可以准确、快速在活跃下行BWP上重叠的PDCCH监听时机中确定一个关联最小小区索引以及关联最小CSS索引的COSESE(即第二参考CORESET),从而实现在关联PDCCH重复的CORESETs中监听PDCCH,进而保证系统通信的灵活性、稳定性和可靠性。
准则2-1-2:
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第一小区集中不存在包含关联CSS的CORESET的小区,则第二参考CORESET可以为:第一小区集中包含关联USS的CORESET的小区中的最小索引的小区中关联最小索引的USS的CORESET。
需要说明的是,结合上述同理可知,与上述“第一参考CORESET”为一个关联PDCCH重叠、关联最小小区索引以及关联最小CSS/USS索引的COSESET不同,‘准则2-1-2’中的第二参考CORESET可以为一个关联最小小区索引以及关联最小USS索引的COSESET。
另外,若第一小区集中不存在包含关联CSS的CORSET的小区,则将第一小区集中包含关联USS的 CORSET的小区中的最小索引的小区中关联最小索引USS的CORESET作为第二参考CORESET。也就是说,先从第一小区集中确定出包含关联USS的CORESET的至少一个小区,再从该至少一个小区中确定出最小索引的小区,最终从该最小索引的小区中确定出关联最小索引USS的CORESET以得到第二参考CORESET。
可见,通过本示例所述的“准则2-1-2”,本申请实施例可以准确、快速在活跃下行BWP上重叠的PDCCH监听时机中确定出一个关联最小小区索引以及关联最小USS索引的COSESET(即第二参考CORESET),从而实现在关联PDCCH重复的CORESETs中监听PDCCH,进而保证系统通信的灵活性、稳定性和可靠性。
下面本申请实施例对“准则2-1-1”和“准则2-1-2”做一个举例说明。
举例说明3:在某个活跃下行BWP上重叠的PDCCH监听时机中,存在下述CORESETs(M=6的情况):
小区1:CORESET#0(关联1个TCI state,关联CSS#0)、CORESET#2(关联1个TCI state,关联CSS#1)、CORESET#3(1个TCI state,关联CSS#4)、CORESET#4(2个TCI state,关联USS#1);
→CSS#1关联的多个PDCCH候选与CSS#4关联的多个PDCCH候选之间存在重复的PDCCH,即CSS#1关联CSS#4(或CORESET#2关联CORESET#3);
→小区1的CORESET#2的TCI state对应的QCL-typeD属性与小区1的CORESET#0的TCI state对应的QCL-typeD属性相同;
→小区1的CORESET#2的TCI state对应的QCL-typeD属性与小区1的CORESET#3的TCI state对应的QCL-typeD属性不相同;
→小区1的CORESET#4的TCI state对应的QCL-typeD属性与小区1的CORESET#2的TCI state对应的QCL-typeD属性相同;
小区2:CORESET#1(1个TCI state,关联USS#2)、CORESET#2(1个TCI state,关联CSS#3);
→小区2的CORESET#2的TCI state对应的QCL-typeD属性与小区2的CORESET#1的TCI state对应的QCL-typeD属性相同;
→小区2的CORESET#2的TCI state对应的QCL-typeD属性与小区1的CORESET#2的TCI state对应的QCL-typeD属性相同;
首先,在该活跃下行BWP上重叠的PDCCH监听时机中,上述CORESETs(M=6)关联的小区包括小区1和小区2,即第一小区集包括小区1和小区2。其中,小区1关联的CORESETs包括CORESET#0、CORESET#2、CORESET#3、CORESET#4,小区2关联的CORESETs包括CORESET#1、CORESET#2。
其次,小区1的索引小于小区2的索引,CSS#0的索引小于CSS#1的索引,CSS#1的索引小于CSS#4的索引。
再次,由于小区1和小区2都存在关联CSS的CORESET,因此第一小区集中存在包含关联CSS的CORESET的小区,从而通过“准则2-1-1”确定出第二参考CORESET为小区1的“CORESET#0”:
从第一小区集中确定出包含关联CSS的CORESET的小区,得到小区1和小区2;从小区1和小区2中确定出最小索引的小区,得到小区1;从小区1中确定出关联最小索引CSS的CORESET,得到小区1的“CORESET#0”。
紧接,从上述CORESETs(M=6)中确定与第二参考CORESET相同QCL-typeD属性的其他CORESETs,得到小区1的“CORESET#2”、小区1的“CORESET#4”、小区2的“CORESET#1”、小区2的“CORESET#2”。
最后,终端在小区1的“CORESET#0”、小区1的“CORESET#2”、小区1的“CORESET#4”、小区2的“CORESET#1”和小区2的“CORESET#2”中监听PDCCH,从而实现在关联PDCCH重复的CORESETs中监听PDCCH。
准则2-2-1:
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第二CORESET中存在关联CSS的CORESET,则第二参考CORESET具体为:第二CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于第二CORESET且关联最小索引CSS的CORESET;其中,第二CORESET包括:在M个CORESET中的不关联PDCCH重复的CORESET。
需要说明的是,在活跃下行BWP上重叠的PDCCH监听时机中,由于在该M个CORESET中可能存在不关联PDCCH重复的CORESET,因此本申请实施例考虑将该M个CORESET中的不关联PDCCH重复的CORESET作为第二CORESET。也就是说,第二CORESET中的各CORESET之间不存在重复的PDCCH。
例如,在“举例说明1”中,在某个活跃下行BWP上重叠的PDCCH监听时机中,存在4个CORESET,且CORESET#1关联CORESET#2。因此,第二CORESET包括CORESET#0和CORESET#3。
另外,在第二CORESET中可能存在有关联CSS的CORESET,也可能不存在关联CSS的CORESET。 因此,若第二CORESET中存在关联CSS的CORESET,则将第二CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于第二CORESET且关联最小索引CSS的CORESET作为第二参考CORESET。也就是说,先从第二CORESET中确定出关联CSS的CORESET以得到至少一个CORESET,再确定该至少一个CORESET各自所属的小区以得到至少一个小区,紧接从该至少一个小区中确定出最小索引的小区,最终从该最小索引的小区中确定出属于第二CORESET且关联最小索引CSS的CORESET以得到第二参考CORESET。
可见,与上述“准则2-1-1”和“准则2-1-2”中的“第二参考CORESET”为一个关联最小小区索引以及关联最小CSS/USS索引的COSESET不同,通过本示例的“准则2-2-1”,本申请实施例可以准确、快速在活跃下行BWP上重叠的PDCCH监听时机中确定出一个不关联PDCCH重叠、关联最小小区索引以及关联最小CSS索引的COSESET(即第二参考CORESET),从而实现在关联PDCCH重复的CORESETs中监听PDCCH,进而保证系统通信的灵活性、稳定性和可靠性。
准则2-2-2:
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第二CORESET中不存在关联CSS的CORESET,则第二参考CORESET具体为:第二CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于第二CORESET且关联最小索引USS的CORESET。
其中,第二CORESET包括:在M个CORESET中的不关联PDCCH重复的CORESET。
需要说明的是,若第二CORESET中不存在关联CSS的CORESET,则将第二CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于第二CORESET且关联最小索引USS的CORESET作为第二参考CORESET。也就是说,先从第二CORESET中确定出关联USS的CORESET以得到至少一个CORESET,再确定该至少一个CORESET各自所属的小区以得到至少一个小区,紧接从该至少一个小区中确定出最小索引的小区,最终从该最小索引的小区中确定出属于第二CORESET且关联最小索引USS的CORESET以得到第二参考CORESET。
可见,通过本示例的“准则2-2-2”,本申请实施例可以准确、快速在活跃下行BWP上重叠的PDCCH监听时机中确定出一个不关联PDCCH重叠、关联最小小区索引以及关联最小USS索引的COSESET(即第二参考CORESET),从而实现在关联PDCCH重复的CORESETs中监听PDCCH,进而保证系统通信的灵活性、稳定性和可靠性。
下面本申请实施例对“准则2-2-1”和“准则2-2-2”做一个举例说明。
举例说明4:在某个活跃下行BWP上重叠的PDCCH监听时机中,存在下述CORESETs(M=6的情况):
小区1:CORESET#0(关联1个TCI state,关联CSS#0)、CORESET#2(关联1个TCI state,关联CSS#1)、CORESET#3(1个TCI state,关联CSS#4)、CORESET#4(2个TCI state,关联USS#1);
→CSS#1关联的多个PDCCH候选与CSS#4关联的多个PDCCH候选之间存在重复的PDCCH,即CSS#1关联CSS#4(或CORESET#2关联CORESET#3);
→小区1的CORESET#2的TCI state对应的QCL-typeD属性与小区1的CORESET#0的TCI state对应的QCL-typeD属性相同;
→小区1的CORESET#2的TCI state对应的QCL-typeD属性与小区1的CORESET#3的TCI state对应的QCL-typeD属性不相同;
→小区1的CORESET#4的TCI state对应的QCL-typeD属性与小区1的CORESET#2的TCI state对应的QCL-typeD属性相同;
小区2:CORESET#1(1个TCI state,关联USS#2)、CORESET#2(1个TCI state,关联CSS#3);
→小区2的CORESET#2的TCI state对应的QCL-typeD属性与小区2的CORESET#1的TCI state对应的QCL-typeD属性相同;
→小区2的CORESET#2的TCI state对应的QCL-typeD属性与小区1的CORESET#2的TCI state对应的QCL-typeD属性相同;
首先,在该活跃下行BWP上重叠的PDCCH监听时机中,上述CORESETs(M=6)关联的小区包括小区1和小区2。其中,小区1关联的CORESETs包括CORESET#0、CORESET#2、CORESET#3、CORESET#4,小区2关联的CORESETs包括CORESET#1、CORESET#2。
其次,小区1的索引小于小区2的索引,CSS#0的索引小于CSS#1的索引,CSS#1的索引小于CSS#4的索引。
再次,上述CORESETs中存在重复的PDCCH,即小区1的CORESET#2和小区1的CORESET#3。因此,上述CORESETs(M=6)的不关联PDCCH重复的CORESET(即第二CORESET)包括:小区1的CORESET#0、小区1的CORESET#3、小区1的CORESET#4、小区2的CORESET#1、小区2的CORESET#2。由于第二 CORESET中存在关联CSS的CORESET,因此通过“准则2-2-1”确定出第二参考CORESET为小区1的“CORESET#0”。
紧接,从上述CORESETs(M=6)中确定与第二参考CORESET相同QCL-typeD属性的其他CORESETs,得到小区1的“CORESET#2”、小区1的“CORESET#4”、小区2的“CORESET#1”、小区2的“CORESET#2”。
最后,终端在小区1的“CORESET#0”、小区1的“CORESET#2”、小区1的“CORESET#4”、小区2的“CORESET#1”和小区2的“CORESET#2”中监听PDCCH,从而实现在关联PDCCH重复的CORESETs中监听PDCCH。
结合上述描述,下面本申请实施例对从该M个CORESET中确定出第三参考CORESET的准则进行具体说明。
准则2-x-y-1:(x为1或2,y为1或2)
在一个可能的示例中,若在该M个CORESET中的关联PDCCH重复的CORESET中,不存在与第二参考CORESET的QCL类型D属性相同的CORESET,则在所述第三CORESET存在关联CSS的CORESET的情况下,第三参考CORESET具体为:第三CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于第三CORESET且关联最小索引CSS的CORESET;其中,第三CORESET包括:在该M个CORESET中的关联PDCCH重复的CORESET。
需要说明的是,在活跃下行BWP上重叠的PDCCH监听时机中,由于在该M个CORESET中可能存在关联PDCCH重复的CORESET,因此本申请实施例考虑将该M个CORESET中的关联PDCCH重复的CORESET作为第三CORESET。也就是说,第三CORESET中的各CORESET关联重复的PDCCH。
另外,第三CORESET中可能存在与第二参考CORESET的QCL类型D属性相同的CORESET,也可能不存在与第二参考CORESET的QCL类型D属性相同的CORESET。因此,为了保证第二参考CORESET的QCL-typeD属性与第三参考CORESET的QCL-typeD属性不相同,需要对第三CORESET中是否存在与第二参考CORESET的QCL类型D属性相同的CORESET进行分析。同时,在第三CORESET中可能存在有关联CSS的CORESET,也可能不存在关联CSS的CORESET。因此,若第三CORESET中不存在与第二参考CORESET的QCL类型D属性相同的CORESET,并且第三CORESET中存在关联CSS的CORESET,则将第三CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于第三CORESET且关联最小索引CSS的CORESET作为第三参考CORESET。
可见,通过本示例的“准则2-x-y-1”,本申请实施例可以准确、快速在活跃下行BWP上重叠的PDCCH监听时机中确定出一个关联PDCCH重叠、与第二参考CORESET的QCL-typeD属性不相同、关联最小小区索引以及关联最小CSS索引的COSESET(即第三参考CORESET),从而实现在关联PDCCH重复的CORESETs中监听PDCCH,进而保证系统通信的灵活性、稳定性和可靠性。
准则2-x-y-2:(x为1或2,y为1或2)
在一个可能的示例中,若在该M个CORESET中的关联PDCCH重复的CORESET中,不存在与第二参考CORESET的QCL类型D属性相同的CORESET,则在第三CORESET不存在关联CSS的CORESET的情况下,第三参考CORESET具体为:第三CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于第三CORESET且关联最小索引USS的CORESET。
可见,通过本示例的“准则2-x-y-2”,本申请实施例可以准确、快速在活跃下行BWP上重叠的PDCCH监听时机中确定出一个关联PDCCH重叠、与第二参考CORESET的QCL-typeD属性不相同、关联最小小区索引以及关联最小USS索引的COSESET(即第三参考CORESET),从而实现在关联PDCCH重复的CORESETs中监听PDCCH,进而保证系统通信的灵活性、稳定性和可靠性。
准则2-x-y-3:(x为1或2,y为1或2)
在一个可能的示例中,若在该M个CORESET中的关联PDCCH重复的CORESET中,存在与第二参考CORESET的QCL类型D属性相同的CORESET,则在第四CORESET存在关联CSS的CORESET的情况下,第三参考CORESET具体为:第四CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于第四CORESET且关联最小索引CSS的CORESET;其中,第四CORESET包括:在该M个CORESET中的与第二参考CORESET的QCL类型D属性相同的CORESET所关联的CORESET中,与第二参考CORESET的QCL类型D属性不相同的CORESET;或者,第四CORESET包括:在该M个CORESET中的关联PDCCH重复的CORESET中,与第二参考CORESET的QCL类型D属性不相同的CORESET。
需要说明的是,在该M个CORESET中可能存在与第二参考CORESET的QCL类型D属性相同的CORESET所关联的CORESET。同时,在该M个CORESET中与第二参考CORESET的QCL类型D属性相同的CORESET所关联的CORESET中,可能存在与第二参考CORESET的QCL类型D属性不相同的CORESET。
举例说明5:在某个活跃下行BWP上重叠的PDCCH监听时机中,存在下述CORESET(M=4的情况):CORESET#0(关联1个TCI state)、CORESET#1(关联1个TCI state)、CORESET#2(关联1个TCI state)、CORESET#3(关联1个TCI state);
→CORESET#1关联的多个PDCCH候选与CORESET#2关联的多个PDCCH候选之间存在重复的PDCCH,即CORESET#1关联CORESET#2;
→CORESET#1的TCI state对应的QCL-typeD属性与CORESET#0的TCI state对应的QCL-typeD属性相同;
→CORESET#1的TCI state对应的QCL-typeD属性与CORESET#3的TCI state对应的QCL-typeD属性相同;
→CORESET#1的TCI state对应的QCL-typeD属性与CORESET#2的TCI state对应的QCL-typeD属性不相同。
其中,若第二参考CORESET为“CORESET#0”,则在上述CORESETs(M=4)中与第二参考CORESET的QCL-typeD属性相同的CORESET包括:CORESET#1和CORESET#3。
另外,由于CORESET#1关联CORESET#2,因此在上述CORESETs(M=4)中与第二参考CORESET的QCL-typeD属性相同的CORESET所关联的CORESET包括:CORESET#2。同时,由于CORESET#2的QCL-typeD属性与第二参考CORESET的QCL-typeD属性不相同,因此第四CORESET包括:CORESET#2。
可见,通过本示例的“准则2-x-y-3”,本申请实施例可以准确、快速在活跃下行BWP上重叠的PDCCH监听时机中确定出一个关联PDCCH重叠、与第二参考CORESET的QCL-typeD属性不相同、关联最小小区索引以及关联最小CSS索引的COSESET(即第三参考CORESET),从而实现在关联PDCCH重复的CORESETs中监听PDCCH,进而保证系统通信的灵活性、稳定性和可靠性。
准则2-x-y-4:(x为1或2,y为1或2)
在一个可能的示例中,若在该M个CORESET中的关联PDCCH重复的CORESET中,存在与第二参考CORESET的QCL类型D属性相同的CORESET,则在第四CORESET不存在关联CSS的CORESET的情况下,第三参考CORESET具体为:第四CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于第四CORESET且关联最小索引USS的CORESET。
其中,第四CORESET包括:在该M个CORESET中的与第二参考CORESET的QCL类型D属性相同的CORESET所关联的CORESET中,与第二参考CORESET的QCL类型D属性不相同的CORESET;或者,第四CORESET包括:在该M个CORESET中的关联PDCCH重复的CORESET中,与第二参考CORESET的QCL类型D属性不相同的CORESET。
可见,通过本示例的“准则2-x-y-4”,本申请实施例可以准确、快速在活跃下行BWP上重叠的PDCCH监听时机中确定出一个关联PDCCH重叠、与第二参考CORESET的QCL-typeD属性不相同、关联最小小区索引以及关联最小USS索引的COSESET(即第三参考CORESET),从而实现在关联PDCCH重复的CORESETs中监听PDCCH,进而保证系统通信的灵活性、稳定性和可靠性。
下面本申请实施例对“准则2-2-1”和“准则2-2-2”做一个举例说明。
举例说明6:在某个活跃下行BWP上重叠的PDCCH监听时机中,存在下述CORESETs(M=6的情况):
小区1:CORESET#0(关联1个TCI state,关联CSS#0)、CORESET#2(关联1个TCI state,关联CSS#1)、CORESET#3(1个TCI state,关联CSS#4)、CORESET#4(2个TCI state,关联USS#1);
→CSS#1关联的多个PDCCH候选与CSS#4关联的多个PDCCH候选之间存在重复的PDCCH,即CSS#1关联CSS#4(或CORESET#2关联CORESET#3);
→小区1的CORESET#2的TCI state对应的QCL-typeD属性与小区1的CORESET#0的TCI state对应的QCL-typeD属性相同;
→小区1的CORESET#2的TCI state对应的QCL-typeD属性与小区1的CORESET#3的TCI state对应的QCL-typeD属性不相同;
→小区1的CORESET#4的TCI state对应的QCL-typeD属性与小区1的CORESET#2的TCI state对应的QCL-typeD属性相同;
小区2:CORESET#1(1个TCI state,关联USS#2)、CORESET#2(1个TCI state,关联CSS#3);
→小区2的CORESET#2的TCI state对应的QCL-typeD属性与小区2的CORESET#1的TCI state对应的QCL-typeD属性相同;
→小区2的CORESET#2的TCI state对应的QCL-typeD属性与小区1的CORESET#3的TCI state对应的QCL-typeD属性相同;
首先,在该活跃下行BWP上重叠的PDCCH监听时机中,上述CORESETs(M=6)关联的小区包括 小区1和小区2。其中,小区1关联的CORESETs包括CORESET#0、CORESET#2、CORESET#3、CORESET#4,小区2关联的CORESETs包括CORESET#1、CORESET#2。小区1的索引小于小区2的索引,CSS#0的索引小于CSS#1的索引,CSS#1的索引小于CSS#4的索引。
其次,若第二参考CORESET为小区1的“CORESET#0”,则在上述CORESETs(M=6)中与第二参考CORESET的QCL-typeD属性相同的CORESET包括:小区1的“CORESET#2”、小区1的“CORESET#4”、小区2的“CORESET#1”、小区2的“CORESET#2”。
再次,由于小区1的“CORESET#2”和小区1的“CORESET#3”关联,因此,通过“准则2-x-y-3”可知,与第二参考CORESET的QCL-typeD属性相同的CORESET所关联的CORESET包括:小区1的“CORESET#3”。同时,由于小区1的“CORESET#3”的QCL-typeD属性与第二参考CORESET的QCL-typeD属性不相同,因此第四CORESET包括:小区1的“CORESET#3”。同时,由于第四CORESET中存在关联CSS的CORESET,因此确定出第三参考CORESET为小区1的“CORESET#3”。
紧接,从上述CORESETs(M=6)中确定与第二参考CORESET相同QCL-typeD属性的其他CORESETs,得到小区1的“CORESET#2”、小区1的“CORESET#4”;同理,从上述CORESETs(M=6)中确定与第三参考CORESET相同QCL-typeD属性的其他CORESETs,得到小区2的“CORESET#1”、小区2的“CORESET#2”。
最后,终端在小区1的“CORESET#0”、小区1的“CORESET#2”、小区1的“CORESET#3”、小区1的“CORESET#4”、小区2的“CORESET#1”和小区2的“CORESET#2”中监听PDCCH,从而实现在关联PDCCH重复的CORESETs中监听PDCCH。
结合上述描述,下面本申请实施例再对该M个CORESET中确定第二参考CORESET和第三参考CORESET的准则进行具体说明。
准则2-3-1:
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第五CORESET中存在关联CSS的CORESET,则第二参考CORESET具体为:第五CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于第五CORESET且关联最小索引CSS的CORESET;其中,第五CORESET包括:在该M个CORESET中的关联PDCCH重复的CORESET。
需要说明的是,“准则2-3-1”与“准则1-1”类似,对此不再赘述。
可见,与上述“准则2-2-1”和“准则2-2-2”中的“第二参考CORESET”为一个不关联PDCCH重叠、关联最小小区索引以及关联最小CSS/USS索引的COSESET不同,通过本示例的“准则2-3-1”,本申请实施例可以准确、快速在活跃下行BWP上重叠的PDCCH监听时机中确定出一个关联PDCCH重叠、关联最小小区索引以及关联最小CSS索引的COSESET(即第二参考CORESET),从而实现在关联PDCCH重复的CORESETs中监听PDCCH,进而保证系统通信的灵活性、稳定性和可靠性。
准则2-3-2:
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第五CORESET中不存在关联CSS的CORESET,则第二参考CORESET具体为:第五CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于第五CORESET且关联最小索引USS的CORESET。
其中,第五CORESET包括:在该M个CORESET中的关联PDCCH重复的CORESET。
需要说明的是,“准则2-3-2”与“准则1-2”类似,对此不再赘述。
可见,通过本示例的“准则2-3-2”,本申请实施例可以准确、快速在活跃下行BWP上重叠的PDCCH监听时机中确定出一个关联PDCCH重叠、关联最小小区索引以及关联最小USS索引的COSESET(即第二参考CORESET),从而实现在关联PDCCH重复的CORESETs中监听PDCCH,进而保证系统通信的灵活性、稳定性和可靠性。
结合上述描述,下面本申请实施例再对从该M个CORESET中确定出第三参考CORESET的准则进行具体说明。
准则2-3-z-1(z为1或2):
在一个可能的示例中,若第六CORESET中存在关联CSS的CORESET,则第三参考CORESET具体为:第六CORESET中关联CSS的CORESET所属小区中的最小索引的小区中属于第六CORESET且关联最小索引CSS的CORESET;其中,第六CORESET包括:在M个CORESET中的与第二参考CORESET的QCL类型D属性相同的CORESET所关联的CORESET中,与第二参考CORESET的QCL类型D属性不相同的CORESET;或者,第六CORESET包括:在M个CORESET中的关联PDCCH重复的CORESET中,与第二参考CORESET的QCL类型D属性不相同的CORESET。
可见,通过本示例的“准则2-3-z-1”,本申请实施例可以准确、快速在活跃下行BWP上重叠的PDCCH 监听时机中确定出一个关联PDCCH重叠、与第二参考CORESET的QCL-typeD属性不相同、关联最小小区索引以及关联最小CSS索引的COSESET(即第三参考CORESET),从而实现在关联PDCCH重复的CORESETs中监听PDCCH,进而保证系统通信的灵活性、稳定性和可靠性。
准则2-3-z-2(z为1或2):
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第六CORESET中不存在关联CSS的CORESET,则第三参考CORESET具体为:第六CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于第六CORESET且关联最小索引USS的CORESET。
其中,第六CORESET包括:在M个CORESET中的与第二参考CORESET的QCL类型D属性相同的CORESET所关联的CORESET中,与第二参考CORESET的QCL类型D属性不相同的CORESET;或者,第六CORESET包括:在M个CORESET中的关联PDCCH重复的CORESET中,与第二参考CORESET的QCL类型D属性不相同的CORESET。
可见,通过本示例的“准则2-3-z-2”,本申请实施例可以准确、快速在活跃下行BWP上重叠的PDCCH监听时机中确定出一个关联PDCCH重叠、与第二参考CORESET的QCL-typeD属性不相同、关联最小小区索引以及关联最小USS索引的COSESET(即第三参考CORESET),从而实现在关联PDCCH重复的CORESETs中监听PDCCH,进而保证系统通信的灵活性、稳定性和可靠性。
与上述实施例一致,本申请实施例提供又一种信道监听方法的流程示意图,请参阅图3,该方法包括:
S310、在活跃下行BWP上重叠的PDCCH监听时机中,网络设备配置M个CORESET,且该M个CORESET关联的PDCCH候选中存在重复的PDCCH,M的取值为大于或等于1的整数。
具体的,M个CORESET中的所有CORESET的准共址QCL类型D属性相同;或者,M个CORESET中存在QCL类型D属性不相同的CORESET;或者,M个CORESET中存在QCL类型D属性相同的CORESET。
具体的,M个CORESET包括第一参考CORESET和/或与第一参考CORESET具有相同准共址QCL类型D属性的CORESET,第一参考CORESET为M个CORESET中的一个CORESET;或者,M个CORESET包括第二参考CORESET和/或与第二参考CORESET具有相同QCL类型D属性的CORESET,以及第三参考CORESE和/或与第三参考CORESET具有相同QCL类型D属性的CORESET;其中,第二参考CORESET为M个CORESET中的一个CORESET,第三参考CORESET为M个CORESET中的一个CORESET,第二参考CORESET的QCL类型D属性与第三参考CORESET的QCL类型D属性不相同。
需要说明的是,本申请实施例对各个实施例的描述都各有侧重,因此图3所述实施例中没有详述的部分,可以详见图2所述实施例的相关描述,对此不再具体赘述。
可以看出,本申请实施例中,在活跃下行BWP上重叠的PDCCH监听时机中,网络设备向终端配置的M个CORESET关联的PDCCH候选中存在重复的PDCCH。因此,终端可以在该M个CORESET中监听PDCCH,从而实现在关联PDCCH重复的CORESETs中监听PDCCH,提升PDCCH的可靠性,进而保证系统通信的灵活性、稳定性和可靠性。
上述主要从方法侧的角度对本申请实施例的方案进行了介绍。可以理解的是,终端或网络设备为了实现上述功能,其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,本申请能够以硬件或硬件与计算机软件的结合形式来实现。某个功能究竟以硬件或计算机软件驱动硬件的方式来执行,取决于技术方案的特定应用和设计约束条件。本领域技术人员可以对每个特定的应用使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对终端或网络设备进行功能单元的划分。例如,可以对应各个功能划分各个功能单元,也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用软件程序模块的形式实现。需要说明的是,本申请实施例中对单元的划分是示意性的,只是一种逻辑功能划分,而实际实现时可以有另外的划分方式。
在采用集成的单元的情况下,图4提供了一种信道监听装置的功能单元组成框图。信道监听装置400包括:处理单元402和通信单元403。处理单元402用于对终端的动作进行控制管理。例如,处理单元402用于支持终端执行图2中的步骤以及用于本申请所描述的技术方案的其它过程。通信单元403用于支持终端与无线通信系统中的其他设备之间的通信。信道监听装置400还可以包括存储单元401,用于存储信道监听装置400所执行的程序代码和所传输的数据。
需要说明的是,信道监听装置400可以是芯片或者芯片模组。
其中,处理单元402可以是处理器或控制器,例如可以是中央处理器(central processing unit,CPU)、通用处理器、数字信号处理器(digital signal processor,DSP)、专用集成电路(application-specific integrated  circuit,ASIC)、现场可编程门阵列(field programmable gate array,FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框、模块和电路。处理单元402也可以是实现计算功能的组合,例如包含一个或多个微处理器组合、DSP和微处理器的组合等等。通信单元403可以是通信接口、收发器、收发电路等,存储单元401可以是存储器。当处理单元402为处理器,通信单元403为通信接口,存储单元401为存储器时,本申请实施例所涉及的信道监听装置400可以为图6所示的终端。
具体实现时,处理单元402用于执行如上述方法实施例中由终端执行的任一步骤,且在执行诸如发送等数据传输时,可选择的调用通信单元403来完成相应操作。下面进行详细说明。
处理单元402用于:若在活跃下行BWP上重叠的PDCCH监听时机中存在M个CORESET,且该M个CORESET关联的PDCCH候选中存在重复的PDCCH,则在该M个CORESET中监听PDCCH,M的取值为大于或等于1的整数。
需要说明的是,图4所述实施例中各个操作的具体实现可以详见上述图2所示的方法实施例中的描述,在此不再赘述。
可以看出,本申请实施例中,若在活跃下行BWP上重叠的PDCCH监听时机中存在M个CORESET,且该M个CORESET关联的PDCCH候选中存在重复的PDCCH,则信道监听装置在该M个CORESET中监听PDCCH,从而实现在关联PDCCH重复的CORESETs中监听PDCCH,提升PDCCH的可靠性,进而保证系统通信的灵活性、稳定性和可靠性。
在一个可能的示例中,M个CORESET中的所有CORESET的准共址QCL类型D属性相同;或者,M个CORESET中存在QCL类型D属性不相同的CORESET;或者,M个CORESET中存在QCL类型D属性相同的CORESET。
在一个可能的示例中,在M个CORESET中监听PDCCH方面,处理单元402具体用于:在第一参考CORESET和/或与第一参考CORESET具有相同准共址QCL类型D属性的CORESET中监听PDCCH,第一参考CORESET为M个CORESET中的一个CORESET;或者,在第二参考CORESET和/或与第二参考CORESET具有相同QCL类型D属性的CORESET中监听PDCCH,以及在第三参考CORESE和/或与第三参考CORESET具有相同QCL类型D属性的CORESET中监听PDCCH;其中,第二参考CORESET为M个CORESET中的一个CORESET,第三参考CORESET为M个CORESET中的一个CORESET,第二参考CORESET的QCL类型D属性与第三参考CORESET的QCL类型D属性不相同。
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第一CORESET中存在关联公共搜索空间CSS的CORESET,则第一参考CORESET具体为:第一CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于第一CORESET且关联最小索引CSS的CORESET;
其中,第一CORESET包括:在M个CORESET中的关联PDCCH重复的CORESET。
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第一CORESET中不存在关联CSS的CORESET,则第一参考CORESET具体为:第一CORESET中关联用户特定搜索空间USS的CORESET各自所属小区中的最小索引的小区中属于第一CORESET且关联最小索引USS的CORESET。
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第一小区集中存在包含关联CSS的CORESET的小区,则第二参考CORESET具体为:第一小区集中包含关联CSS的CORESET的小区中的最小索引的小区中关联最小索引CSS的CORESET;其中,第一小区集包括:M个CORESET对应的小区。
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第一小区集中不存在包含关联CSS的CORESET的小区,则第二参考CORESET具体为:第一小区集中包含关联USS的CORESET的小区中的最小索引的小区中关联最小索引USS的CORESET。
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第二CORESET中存在关联CSS的CORESET,则第二参考CORESET具体为:第二CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于第二CORESET且关联最小索引CSS的CORESET;其中,第二CORESET包括:在M个CORESET中的不关联PDCCH重复的CORESET。
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第二CORESET中不存在关联CSS的CORESET,则第二参考CORESET具体为:第二CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于第二CORESET且关联最小索引USS的CORESET。
在一个可能的示例中,若在M个CORESET中的关联PDCCH重复的CORESET中,不存在与第二参考CORESET的QCL类型D属性相同的CORESET,则在第三CORESET存在关联CSS的CORESET的情况下,第三参考CORESET具体为:第三CORESET中关联CSS的CORESET各自所属小区中的最小索引的 小区中属于第三CORESET且关联最小索引CSS的CORESET;其中,第三CORESET包括:在M个CORESET中的关联PDCCH重复的CORESET。
在一个可能的示例中,若在M个CORESET中的关联PDCCH重复的CORESET中,不存在与第二参考CORESET的QCL类型D属性相同的CORESET,则在第三CORESET不存在关联CSS的CORESET的情况下,第三参考CORESET具体为:第三CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于第三CORESET且关联最小索引USS的CORESET。
在一个可能的示例中,若在M个CORESET中的关联PDCCH重复的CORESET中,存在与第二参考CORESET的QCL类型D属性相同的CORESET,则在第四CORESET存在关联CSS的CORESET的情况下,第三参考CORESET具体为:第四CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于第四CORESET且关联最小索引CSS的CORESET;其中,第四CORESET包括:在M个CORESET中的与第二参考CORESET的QCL类型D属性相同的CORESET所关联的CORESET中,与第二参考CORESET的QCL类型D属性不相同的CORESET;或者,第四CORESET包括:在M个CORESET中的关联PDCCH重复的CORESET中,与第二参考CORESET的QCL类型D属性不相同的CORESET。
在一个可能的示例中,若在M个CORESET中的关联PDCCH重复的CORESET中,存在与第二参考CORESET的QCL类型D属性相同的CORESET,则在第四CORESET不存在关联CSS的CORESET的情况下,第三参考CORESET具体为:第四CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于第四CORESET且关联最小索引USS的CORESET。
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第五CORESET中存在关联CSS的CORESET,则第二参考CORESET具体为:第五CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于第五CORESET且关联最小索引CSS的CORESET;其中,第五CORESET包括:在M个CORESET中的关联PDCCH重复的CORESET。
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第五CORESET中不存在关联CSS的CORESET,则第二参考CORESET具体为:第五CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于第五CORESET且关联最小索引USS的CORESET。
在一个可能的示例中,若第六CORESET中存在关联CSS的CORESET,则第三参考CORESET具体为:第六CORESET中关联CSS的CORESET所属小区中的最小索引的小区中属于第六CORESET且关联最小索引CSS的CORESET;其中,第六CORESET包括:在M个CORESET中的与第二参考CORESET的QCL类型D属性相同的CORESET所关联的CORESET中,与第二参考CORESET的QCL类型D属性不相同的CORESET;或者,第六CORESET包括:在M个CORESET中的关联PDCCH重复的CORESET中,与第二参考CORESET的QCL类型D属性不相同的CORESET。
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第六CORESET中不存在关联CSS的CORESET,则第三参考CORESET具体为:第六CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于第六CORESET且关联最小索引USS的CORESET。
在采用集成的单元的情况下,图5提供了又一种信道监听装置的功能单元组成框图。信道监听装置500包括:处理单元502和通信单元503。处理单元502用于对网络设备的动作进行控制管理。例如,处理单元502用于支持网络设备执行图3中的步骤以及用于本申请所描述的技术方案的其它过程。通信单元503用于支持网络设备与无线通信系统中的其他设备之间的通信。信道监听装置500还可以包括存储单元501,用于存储信道监听装置500所执行的程序代码和所传输的数据。
需要说明的是,信道监听装置500可以是芯片或者芯片模组。
其中,处理单元502可以是处理器或控制器,例如可以是中央处理器(central processing unit,CPU)、通用处理器、数字信号处理器(digital signal processor,DSP)、专用集成电路(application-specific integrated circuit,ASIC)、现场可编程门阵列(field programmable gate array,FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框、模块和电路。处理单元502也可以是实现计算功能的组合,例如包含一个或多个微处理器组合、DSP和微处理器的组合等等。通信单元503可以是通信接口、收发器、收发电路等,存储单元501可以是存储器。当处理单元502为处理器,通信单元503为通信接口,存储单元501为存储器时,本申请实施例所涉及的信道监听装置500可以为图7所示的网络设备。
具体实现时,处理单元502用于执行如上述方法实施例中由网络设备执行的任一步骤,且在执行诸如发送等数据传输时,可选择的调用通信单元503来完成相应操作。下面进行详细说明。
处理单元502用于:在活跃下行BWP上重叠的PDCCH监听时机中,配置M个CORESET,且该M个CORESET关联的PDCCH候选中存在重复的PDCCH,M的取值为大于或等于1的整数。
需要说明的是,图5所述实施例中各个操作的具体实现可以详见上述图2和图3所示的方法实施例中的描述,在此不再赘述。
可以看出,本申请实施例中,在活跃下行BWP上重叠的PDCCH监听时机中,信道监听装置向终端配置的M个CORESET关联的PDCCH候选中存在重复的PDCCH。因此,终端可以在该M个CORESET中监听PDCCH,从而实现在关联PDCCH重复的CORESETs中监听PDCCH,提升PDCCH的可靠性,进而保证系统通信的灵活性、稳定性和可靠性。
在一个可能的示例中,M个CORESET中的所有CORESET的准共址QCL类型D属性相同;或者,M个CORESET中存在QCL类型D属性不相同的CORESET;或者,M个CORESET中存在QCL类型D属性相同的CORESET。
在一个可能的示例中,M个CORESET包括第一参考CORESET和/或与第一参考CORESET具有相同准共址QCL类型D属性的CORESET,第一参考CORESET为M个CORESET中的一个CORESET;或者,M个CORESET包括第二参考CORESET和/或与第二参考CORESET具有相同QCL类型D属性的CORESET,以及第三参考CORESE和/或与第三参考CORESET具有相同QCL类型D属性的CORESET;其中,第二参考CORESET为M个CORESET中的一个CORESET,第三参考CORESET为M个CORESET中的一个CORESET,第二参考CORESET的QCL类型D属性与第三参考CORESET的QCL类型D属性不相同。
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第一CORESET中存在关联公共搜索空间CSS的CORESET,则第一参考CORESET具体为:第一CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于第一CORESET且关联最小索引CSS的CORESET;其中,第一CORESET包括:在M个CORESET中的关联PDCCH重复的CORESET。
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第一CORESET中不存在关联CSS的CORESET,则第一参考CORESET具体为:第一CORESET中关联用户特定搜索空间USS的CORESET各自所属小区中的最小索引的小区中属于第一CORESET且关联最小索引USS的CORESET。
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第一小区集中存在包含关联CSS的CORESET的小区,则第二参考CORESET具体为:第一小区集中包含关联CSS的CORESET的小区中的最小索引的小区中关联最小索引CSS的CORESET;其中,第一小区集包括:M个CORESET对应的小区。
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第一小区集中不存在包含关联CSS的CORESET的小区,则第二参考CORESET具体为:第一小区集中包含关联USS的CORESET的小区中的最小索引的小区中关联最小索引USS的CORESET。
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第二CORESET中存在关联CSS的CORESET,则第二参考CORESET具体为:第二CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于第二CORESET且关联最小索引CSS的CORESET;其中,第二CORESET包括:在M个CORESET中的不关联PDCCH重复的CORESET。
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第二CORESET中不存在关联CSS的CORESET,则第二参考CORESET具体为:第二CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于第二CORESET且关联最小索引USS的CORESET。
在一个可能的示例中,若在M个CORESET中的关联PDCCH重复的CORESET中,不存在与第二参考CORESET的QCL类型D属性相同的CORESET,则在第三CORESET存在关联CSS的CORESET的情况下,第三参考CORESET具体为:第三CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于第三CORESET且关联最小索引CSS的CORESET;其中,第三CORESET包括:在M个CORESET中的关联PDCCH重复的CORESET。
在一个可能的示例中,若在M个CORESET中的关联PDCCH重复的CORESET中,不存在与第二参考CORESET的QCL类型D属性相同的CORESET,则在第三CORESET不存在关联CSS的CORESET的情况下,第三参考CORESET具体为:第三CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于第三CORESET且关联最小索引USS的CORESET。
在一个可能的示例中,若在M个CORESET中的关联PDCCH重复的CORESET中,存在与第二参考CORESET的QCL类型D属性相同的CORESET,则在第四CORESET存在关联CSS的CORESET的情况下,第三参考CORESET具体为:第四CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于第四CORESET且关联最小索引CSS的CORESET;其中,第四CORESET包括:在M个CORESET中的与第二参考CORESET的QCL类型D属性相同的CORESET所关联的CORESET中,与第二参考 CORESET的QCL类型D属性不相同的CORESET;或者,第四CORESET包括:在M个CORESET中的关联PDCCH重复的CORESET中,与第二参考CORESET的QCL类型D属性不相同的CORESET。
在一个可能的示例中,若在M个CORESET中的关联PDCCH重复的CORESET中,存在与第二参考CORESET的QCL类型D属性相同的CORESET,则在第四CORESET不存在关联CSS的CORESET的情况下,第三参考CORESET具体为:第四CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于第四CORESET且关联最小索引USS的CORESET。
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第五CORESET中存在关联CSS的CORESET,则第二参考CORESET具体为:第五CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于第五CORESET且关联最小索引CSS的CORESET;第五CORESET包括:在M个CORESET中的关联PDCCH重复的CORESET。
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第五CORESET中不存在关联CSS的CORESET,则第二参考CORESET具体为:第五CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于第五CORESET且关联最小索引USS的CORESET。
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第六CORESET中存在关联CSS的CORESET,则第三参考CORESET具体为:第六CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于第六CORESET且关联最小索引CSS的CORESET;其中,第六CORESET包括:在M个CORESET中的与第二参考CORESET的QCL类型D属性相同的CORESET所关联的CORESET中,与第二参考CORESET的QCL类型D属性不同的CORESET;或者,第六CORESET包括:在M个CORESET中的关联PDCCH重复的CORESET中,与第二参考CORESET的QCL类型D属性不相同的CORESET。
在一个可能的示例中,在活跃下行BWP上重叠的PDCCH监听时机中,若第六CORESET中不存在关联CSS的CORESET,则第三参考CORESET具体为:第六CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于第六CORESET且关联最小索引USS的CORESET。
请参阅图6,图6是本申请实施例提供的一种终端的结构示意图。其中,终端600包括处理器610、存储器620、通信接口630以及用于连接处理器610、存储器620、通信接口630的通信总线。
存储器620包括但不限于是随机存储记忆体(random access memory,RAM)、只读存储器(read-only memory,ROM)、可擦除可编程只读存储器(erasable programmable read-only memory,EPROM)或便携式只读存储器(compact disc read-only memory,CD-ROM),该存储器620用于存储终端600所执行的程序代码和所传输的数据。
通信接口630用于接收和发送数据。
处理器610可以是一个或多个CPU,在处理器610是一个CPU的情况下,该CPU可以是单核CPU,也可以是多核CPU。
终端600中的处理器610用于读取存储器620中存储的一个或多个程序621,执行以下操作:若在活跃下行BWP上重叠的PDCCH监听时机中存在M个CORESET,且该M个CORESET关联的PDCCH候选中存在重复的PDCCH,则在该M个CORESET中监听PDCCH,M的取值为大于或等于1的整数。
需要说明的是,各个操作的具体实现可以采用上述图2所示的方法实施例的相应描述,终端600可以用于执行本申请上述方法实施例的终端侧的方法,在此不再具体赘述。
可见,若在活跃下行BWP上重叠的PDCCH监听时机中存在M个CORESET,且该M个CORESET关联的PDCCH候选中存在重复的PDCCH,则在该M个CORESET中监听PDCCH,从而实现在关联PDCCH重复的CORESETs中监听PDCCH,提升PDCCH的可靠性,进而保证系统通信的灵活性、稳定性和可靠性。
请参阅图7,图7是本申请实施例提供的一种网络设备的结构示意图。其中,网络设备700包括处理器710、存储器720、通信接口730以及用于连接处理器710、存储器720、通信接口730的通信总线。
存储器720包括但不限于是随机存储记忆体(random access memory,RAM)、只读存储器(read-only memory,ROM)、可擦除可编程只读存储器(erasable programmable read-only memory,EPROM)或便携式只读存储器(compact disc read-only memory,CD-ROM),该存储器720用于存储网络设备700所执行的程序代码和所传输的数据。
通信接口730用于接收和发送数据。
处理器710可以是一个或多个CPU,在处理器710是一个CPU的情况下,该CPU可以是单核CPU,也可以是多核CPU。
网络设备700中的处理器710用于读取存储器720中存储的一个或多个程序721,执行以下操作:在活 跃下行BWP上重叠的PDCCH监听时机中,配置M个CORESET,且该M个CORESET关联的PDCCH候选中存在重复的PDCCH,M的取值为大于或等于1的整数。
需要说明的是,各个操作的具体实现可以采用上述图2和图3所示的方法实施例的相应描述,网络设备700可以用于执行本申请上述方法实施例的网络设备侧的方法,在此不再具体赘述。
可见,在活跃下行BWP上重叠的PDCCH监听时机中,网络设备向终端配置的M个CORESET关联的PDCCH候选中存在重复的PDCCH。因此,终端可以在该M个CORESET中监听PDCCH,从而实现在关联PDCCH重复的CORESETs中监听PDCCH,提升PDCCH的可靠性,进而保证系统通信的灵活性、稳定性和可靠性。
本申请实施例还提供了一种计算机可读存储介质,其中,所述计算机可读存储介质存储用于电子数据交换的计算机程序,其中,所述计算机程序使得计算机执行如上述方法实施例中终端或管理设备所描述的部分或全部步骤。
本申请实施例还提供了一种计算机程序产品,其中,所述计算机程序产品包括计算机程序,所述计算机程序可操作来使计算机执行如上述方法实施例中终端或管理设备所描述的部分或全部步骤。该计算机程序产品可以为一个软件安装包。
在上述实施例中,本申请实施例对各个实施例的描述都各有侧重,某个实施例中没有详述的部分,可以参见其他实施例的相关描述。
本申请实施例所描述的方法或者算法的步骤可以以硬件的方式来实现,也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成,软件模块可以被存放于RAM、闪存、ROM、可擦除可编程只读存储器(erasable programmable ROM,EPROM)、电可擦可编程只读存储器(electrically EPROM,EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器,从而使处理器能够从该存储介质读取信息,且可向该存储介质写入信息。当然,存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外,该ASIC可以位于终端或管理设备中。当然,处理器和存储介质也可以作为分立组件存在于终端或管理设备中。
本领域技术人员应该可以意识到,在上述一个或多个示例中,本申请实施例所描述的功能可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时,可以全部或部分地以计算机程序产品的形式实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行该计算机程序指令时,全部或部分地产生按照本申请实施例所述的流程或功能。该计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。该计算机指令可以存储在计算机可读存储介质中,或者从一个计算机可读存储介质向另一个计算机可读存储介质传输。例如,该计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line,DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。该计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。该可用介质可以是磁性介质(例如,软盘、硬盘、磁带)、光介质(例如,数字视频光盘(digital video disc,DVD))、或者半导体介质(例如,固态硬盘(solid state disk,SSD))等。
上述实施例中描述的各个装置、产品包含的各个模块/单元,其可以是软件模块/单元,也可以是硬件模块/单元,或者也可以部分是软件模块/单元,部分是硬件模块/单元。例如,对于应用于或集成于芯片的各个装置、产品,其包含的各个模块/单元可以都采用电路等硬件的方式实现,或者,至少部分模块/单元可以采用软件程序的方式实现,该软件程序运行于芯片内部集成的处理器,剩余的(如果有)部分模块/单元可以采用电路等硬件方式实现;对于应用于或集成于芯片模组的各个装置、产品,其包含的各个模块/单元可以都采用电路等硬件的方式实现,不同的模块/单元可以位于芯片模组的同一组件(例如芯片、电路模块等)或者不同组件中,或者,至少部分模块/单元可以采用软件程序的方式实现,该软件程序运行于芯片模组内部集成的处理器,剩余的(如果有)部分模块/单元可以采用电路等硬件方式实现;对于应用于或集成于终端的各个装置、产品,其包含的各个模块/单元可以都采用电路等硬件的方式实现,不同的模块/单元可以位于终端内同一组件(例如,芯片、电路模块等)或者不同组件中,或者,至少部分模块/单元可以采用软件程序的方式实现,该软件程序运行于终端内部集成的处理器,剩余的(如果有)部分模块/单元可以采用电路等硬件方式实现。
以上所述的具体实施方式,对本申请实施例的目的、技术方案和有益效果进行了进一步详细说明,所应理解的是,以上所述仅为本申请实施例的具体实施方式而已,并不用于限定本申请实施例的保护范围,凡在本申请实施例的技术方案的基础之上,所做的任何修改、等同替换、改进等,均应包括在本申 请实施例的保护范围之内。

Claims (40)

  1. 一种信道监听方法,其特征在于,包括:
    若在活跃下行带宽部分BWP上重叠的物理下行控制信道PDCCH监听时机中存在M个控制资源集CORESET,且所述M个CORESET关联的PDCCH候选中存在重复的PDCCH,则终端在所述M个CORESET中监听PDCCH,所述M的取值为大于或等于1的整数。
  2. 根据权利要求1所述的方法,其特征在于,所述M个CORESET中的所有CORESET的准共址QCL类型D属性相同;或者,
    所述M个CORESET中存在QCL类型D属性不相同的CORESET;或者,
    所述M个CORESET中存在QCL类型D属性相同的CORESET。
  3. 根据权利要求1或2所述的方法,其特征在于,所述终端在所述M个CORESET中监听PDCCH,包括:
    所述终端在第一参考CORESET和/或与所述第一参考CORESET具有相同准共址QCL类型D属性的CORESET中监听PDCCH,所述第一参考CORESET为所述M个CORESET中的一个CORESET;或者,
    所述终端在第二参考CORESET和/或与所述第二参考CORESET具有相同QCL类型D属性的CORESET中监听PDCCH,以及在第三参考CORESE和/或与所述第三参考CORESET具有相同QCL类型D属性的CORESET中监听PDCCH;
    其中,所述第二参考CORESET为所述M个CORESET中的一个CORESET,所述第三参考CORESET为所述M个CORESET中的一个CORESET,所述第二参考CORESET的QCL类型D属性与所述第三参考CORESET的QCL类型D属性不相同。
  4. 根据权利要求3所述的方法,其特征在于,在所述活跃下行BWP上重叠的PDCCH监听时机中,若第一CORESET中存在关联公共搜索空间CSS的CORESET,则所述第一参考CORESET具体为:
    所述第一CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于所述第一CORESET且关联最小索引CSS的CORESET;
    其中,所述第一CORESET包括:在所述M个CORESET中的关联PDCCH重复的CORESET。
  5. 根据权利要求3所述的方法,其特征在于,在所述活跃下行BWP上重叠的PDCCH监听时机中,若第一CORESET中不存在关联CSS的CORESET,则所述第一参考CORESET具体为:
    所述第一CORESET中关联用户特定搜索空间USS的CORESET各自所属小区中的最小索引的小区中属于所述第一CORESET且关联最小索引USS的CORESET。
  6. 根据权利要求3所述的方法,其特征在于,在所述活跃下行BWP上重叠的PDCCH监听时机中,若第一小区集中存在包含关联CSS的CORESET的小区,则所述第二参考CORESET具体为:
    所述第一小区集中包含关联CSS的CORESET的小区中的最小索引的小区中关联最小索引CSS的CORESET;
    其中,所述第一小区集包括:所述M个CORESET对应的小区。
  7. 根据权利要求3所述的方法,其特征在于,在所述活跃下行BWP上重叠的PDCCH监听时机中,若所述第一小区集中不存在包含关联CSS的CORESET的小区,则所述第二参考CORESET具体为:
    所述第一小区集中包含关联USS的CORESET的小区中的最小索引的小区中关联最小索引USS的CORESET。
  8. 根据权利要求3所述的方法,其特征在于,在所述活跃下行BWP上重叠的PDCCH监听时机中,若第二CORESET中存在关联CSS的CORESET,则所述第二参考CORESET具体为:
    所述第二CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于所述第二CORESET且关联最小索引CSS的CORESET;
    其中,所述第二CORESET包括:在所述M个CORESET中的不关联PDCCH重复的CORESET。
  9. 根据权利要求3所述的方法,其特征在于,在所述活跃下行BWP上重叠的PDCCH监听时机中,若所述第二CORESET中不存在关联CSS的CORESET,则所述第二参考CORESET具体为:
    所述第二CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于所述第二CORESET且关联最小索引USS的CORESET。
  10. 根据权利要求6-9任一项所述的方法,其特征在于,若在所述M个CORESET中的关联PDCCH重复的CORESET中,不存在与所述第二参考CORESET的QCL类型D属性相同的CORESET,则在所述第三CORESET存在关联CSS的CORESET的情况下,所述第三参考CORESET具体为:
    所述第三CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于所述第三CORESET且关联最小索引CSS的CORESET;
    其中,所述第三CORESET包括:在所述M个CORESET中的关联PDCCH重复的CORESET。
  11. 根据权利要求6-9任一项所述的方法,其特征在于,若在所述M个CORESET中的关联PDCCH重复的CORESET中,不存在与所述第二参考CORESET的QCL类型D属性相同的CORESET,则在所述第三CORESET不存在关联CSS的CORESET的情况下,所述第三参考CORESET具体为:
    所述第三CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于所述第三CORESET且关联最小索引USS的CORESET。
  12. 根据权利要求6-9任一项所述的方法,其特征在于,若在所述M个CORESET中的关联PDCCH重复的CORESET中,存在与所述第二参考CORESET的QCL类型D属性相同的CORESET,则在第四CORESET存在关联CSS的CORESET的情况下,所述第三参考CORESET具体为:
    所述第四CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于所述第四CORESET且关联最小索引CSS的CORESET;
    其中,所述第四CORESET包括:在所述M个CORESET中的与所述第二参考CORESET的QCL类型D属性相同的CORESET所关联的CORESET中,与所述第二参考CORESET的QCL类型D属性不相同的CORESET;或者,
    所述第四CORESET包括:在所述M个CORESET中的关联PDCCH重复的CORESET中,与所述第二参考CORESET的QCL类型D属性不相同的CORESET。
  13. 根据权利要求6-9任一项所述的方法,其特征在于,若在所述M个CORESET中的关联PDCCH重复的CORESET中,存在与所述第二参考CORESET的QCL类型D属性相同的CORESET,则在所述第四CORESET不存在关联CSS的CORESET的情况下,所述第三参考CORESET具体为:
    所述第四CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于所述第四CORESET且关联最小索引USS的CORESET。
  14. 根据权利要求3所述的方法,其特征在于,在所述活跃下行BWP上重叠的PDCCH监听时机中,若第五CORESET中存在关联CSS的CORESET,则所述第二参考CORESET具体为:
    所述第五CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于所述第五CORESET且关联最小索引CSS的CORESET;
    其中,所述第五CORESET包括:在所述M个CORESET中的关联PDCCH重复的CORESET。
  15. 根据权利要求3所述的方法,其特征在于,在所述活跃下行BWP上重叠的PDCCH监听时机中,若所述第五CORESET中不存在关联CSS的CORESET,则所述第二参考CORESET具体为:
    所述第五CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于所述第五CORESET且关联最小索引USS的CORESET。
  16. 根据权利要求14或15所述的方法,其特征在于,若第六CORESET中存在关联CSS的CORESET,则所述第三参考CORESET具体为:
    所述第六CORESET中关联CSS的CORESET所属小区中的最小索引的小区中属于所述第六CORESET且关联最小索引CSS的CORESET;
    其中,所述第六CORESET包括:在所述M个CORESET中的与所述第二参考CORESET的QCL类型D属性相同的CORESET所关联的CORESET中,与所述第二参考CORESET的QCL类型D属性不相同的CORESET;或者,
    所述第六CORESET包括:在所述M个CORESET中的关联PDCCH重复的CORESET中,与所述第二参考CORESET的QCL类型D属性不相同的CORESET。
  17. 根据权利要求14或15所述的方法,其特征在于,在所述活跃下行BWP上重叠的PDCCH监听时机中,若所述第六CORESET中不存在关联CSS的CORESET,则所述第三参考CORESET具体为:
    所述第六CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于所述第六CORESET且关联最小索引USS的CORESET。
  18. 一种信道监听方法,其特征在于,包括:
    在活跃下行带宽部分BWP上重叠的物理下行控制信道PDCCH监听时机中,网络设备配置M个控制资源集CORESET,且所述M个CORESET关联的PDCCH候选中存在重复的PDCCH,所述M的取值为大于或等于1的整数。
  19. 根据权利要求18所述的方法,其特征在于,所述M个CORESET中的所有CORESET的准共址QCL类型D属性相同;或者,
    所述M个CORESET中存在QCL类型D属性不相同的CORESET;或者,
    所述M个CORESET中存在QCL类型D属性相同的CORESET。
  20. 根据权利要求18或19所述的方法,其特征在于,所述M个CORESET包括第一参考CORESET和/或与所述第一参考CORESET具有相同准共址QCL类型D属性的CORESET,所述第一参考CORESET为所述M个CORESET中的一个CORESET;或者,
    所述M个CORESET包括第二参考CORESET和/或与所述第二参考CORESET具有相同QCL类型D属性的CORESET,以及第三参考CORESE和/或与所述第三参考CORESET具有相同QCL类型D属性的CORESET;
    其中,所述第二参考CORESET为所述M个CORESET中的一个CORESET,所述第三参考CORESET为所述M个CORESET中的一个CORESET,所述第二参考CORESET的QCL类型D属性与所述第三参考CORESET的QCL类型D属性不相同。
  21. 根据权利要求20所述的方法,其特征在于,在所述活跃下行BWP上重叠的PDCCH监听时机中,若第一CORESET中存在关联公共搜索空间CSS的CORESET,则所述第一参考CORESET具体为:
    所述第一CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于所述第一CORESET且关联最小索引CSS的CORESET;
    其中,所述第一CORESET包括:在所述M个CORESET中的关联PDCCH重复的CORESET。
  22. 根据权利要求20所述的方法,其特征在于,在所述活跃下行BWP上重叠的PDCCH监听时机中,若第一CORESET中不存在关联CSS的CORESET,则所述第一参考CORESET具体为:
    所述第一CORESET中关联用户特定搜索空间USS的CORESET各自所属小区中的最小索引的小区中属于所述第一CORESET且关联最小索引USS的CORESET。
  23. 根据权利要求20所述的方法,其特征在于,在所述活跃下行BWP上重叠的PDCCH监听时机中,若第一小区集中存在包含关联CSS的CORESET的小区,则所述第二参考CORESET具体为:
    所述第一小区集中包含关联CSS的CORESET的小区中的最小索引的小区中关联最小索引CSS的CORESET;
    其中,所述第一小区集包括:所述M个CORESET对应的小区。
  24. 根据权利要求20所述的方法,其特征在于,在所述活跃下行BWP上重叠的PDCCH监听时机中,若所述第一小区集中不存在包含关联CSS的CORESET的小区,则所述第二参考CORESET具体为:
    所述第一小区集中包含关联USS的CORESET的小区中的最小索引的小区中关联最小索引USS的CORESET。
  25. 根据权利要求20所述的方法,其特征在于,在所述活跃下行BWP上重叠的PDCCH监听时机中,若第二CORESET中存在关联CSS的CORESET,则所述第二参考CORESET具体为:
    所述第二CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于所述第二CORESET且关联最小索引CSS的CORESET;
    其中,所述第二CORESET包括:在所述M个CORESET中的不关联PDCCH重复的CORESET。
  26. 根据权利要求20所述的方法,其特征在于,在所述活跃下行BWP上重叠的PDCCH监听时机中,若所述第二CORESET中不存在关联CSS的CORESET,则所述第二参考CORESET具体为:
    所述第二CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于所述第二CORESET且关联最小索引USS的CORESET。
  27. 根据权利要求23-26任一项所述的方法,其特征在于,若在所述M个CORESET中的关联PDCCH重复的CORESET中,不存在与所述第二参考CORESET的QCL类型D属性相同的CORESET,则在第三CORESET存在关联CSS的CORESET的情况下,所述第三参考CORESET具体为:
    所述第三CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于所述第三CORESET且关联最小索引CSS的CORESET;
    其中,所述第三CORESET包括:在所述M个CORESET中的关联PDCCH重复的CORESET。
  28. 根据权利要求23-26任一项所述的方法,其特征在于,若在所述M个CORESET中的关联PDCCH重复的CORESET中,不存在与所述第二参考CORESET的QCL类型D属性相同的CORESET,则在所述第三CORESET不存在关联CSS的CORESET的情况下,所述第三参考CORESET具体为:
    所述第三CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于所述第三CORESET且关联最小索引USS的CORESET。
  29. 根据权利要求23-26任一项所述的方法,其特征在于,若在所述M个CORESET中的关联PDCCH重复的CORESET中,存在与所述第二参考CORESET的QCL类型D属性相同的CORESET,则在第四CORESET存在关联CSS的CORESET的情况下,所述第三参考CORESET具体为:
    所述第四CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于所述第四 CORESET且关联最小索引CSS的CORESET;
    其中,所述第四CORESET包括:在所述M个CORESET中的与所述第二参考CORESET的QCL类型D属性相同的CORESET所关联的CORESET中,与所述第二参考CORESET的QCL类型D属性不相同的CORESET;或者,
    所述第四CORESET包括:在所述M个CORESET中的关联PDCCH重复的CORESET中,与所述第二参考CORESET的QCL类型D属性不相同的CORESET。
  30. 根据权利要求23-26任一项所述的方法,其特征在于,若在所述M个CORESET中的关联PDCCH重复的CORESET中,存在与所述第二参考CORESET的QCL类型D属性相同的CORESET,则在所述第四CORESET不存在关联CSS的CORESET的情况下,所述第三参考CORESET具体为:
    所述第四CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于所述第四CORESET且关联最小索引USS的CORESET。
  31. 根据权利要求20所述的方法,其特征在于,在所述活跃下行BWP上重叠的PDCCH监听时机中,若第五CORESET中存在关联CSS的CORESET,则所述第二参考CORESET具体为:
    所述第五CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于所述第五CORESET且关联最小索引CSS的CORESET;
    所述第五CORESET包括:在所述M个CORESET中的关联PDCCH重复的CORESET。
  32. 根据权利要求20所述的方法,其特征在于,在所述活跃下行BWP上重叠的PDCCH监听时机中,若所述第五CORESET中不存在关联CSS的CORESET,则所述第二参考CORESET具体为:
    所述第五CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于所述第五CORESET且关联最小索引USS的CORESET。
  33. 根据权利要求31或32所述的方法,其特征在于,在所述活跃下行BWP上重叠的PDCCH监听时机中,若第六CORESET中存在关联CSS的CORESET,则所述第三参考CORESET具体为:
    所述第六CORESET中关联CSS的CORESET各自所属小区中的最小索引的小区中属于所述第六CORESET且关联最小索引CSS的CORESET;
    其中,所述第六CORESET包括:在所述M个CORESET中的与所述第二参考CORESET的QCL类型D属性相同的CORESET所关联的CORESET中,与所述第二参考CORESET的QCL类型D属性不同的CORESET;或者,
    所述第六CORESET包括:在所述M个CORESET中的关联PDCCH重复的CORESET中,与所述第二参考CORESET的QCL类型D属性不相同的CORESET。
  34. 根据权利要求31或32所述的方法,其特征在于,在所述活跃下行BWP上重叠的PDCCH监听时机中,若所述第六CORESET中不存在关联CSS的CORESET,则所述第三参考CORESET具体为:
    所述第六CORESET中关联USS的CORESET各自所属小区中的最小索引的小区中属于所述第六CORESET且关联最小索引USS的CORESET。
  35. 一种信道监听装置,其特征在于,所述装置包括处理单元,所述处理单元用于:
    若在活跃下行带宽部分BWP上重叠的物理下行控制信道PDCCH监听时机中存在M个控制资源集CORESET,且所述M个CORESET关联的PDCCH候选中存在重复的PDCCH,则在所述M个CORESET中监听PDCCH,所述M的取值为大于或等于1的整数。
  36. 一种信道监听装置,其特征在于,所述装置包括处理单元,所述处理单元用于:
    在活跃下行带宽部分BWP上重叠的物理下行控制信道PDCCH监听时机中,配置M个控制资源集CORESET,且所述M个CORESET关联的PDCCH候选中存在重复的PDCCH,所述M的取值为大于或等于1的整数。
  37. 一种终端,其特征在于,包括处理器、存储器、通信接口,以及一个或多个程序,所述一个或多个程序被存储在所述存储器中,并且被配置由所述处理器执行,所述程序包括用于执行如权利要求1-17任一项所述的方法中的步骤的指令。
  38. 一种网络设备,其特征在于,包括处理器、存储器、通信接口,以及一个或多个程序,所述一个或多个程序被存储在所述存储器中,并且被配置由所述处理器执行,所述程序包括用于执行如权利要求18-34任一项所述的方法中的步骤的指令。
  39. 一种计算机可读存储介质,其特征在于,其存储用于电子数据交换的计算机程序,其中,所述计算机程序使得计算机执行如权利要求1-34中任一项所述的方法。
  40. 一种芯片,包括处理器,其特征在于,所述处理器执行权利要求1-17或18-34中任一项所述方法的步骤。
PCT/CN2022/091921 2021-05-10 2022-05-10 信道监听方法与装置、终端和网络设备 WO2022237763A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP22806726.0A EP4340500A1 (en) 2021-05-10 2022-05-10 Channel monitoring method and apparatus, terminal, and network device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110508085.4A CN115334688A (zh) 2021-05-10 2021-05-10 信道监听方法与装置、终端和网络设备
CN202110508085.4 2021-05-10

Publications (1)

Publication Number Publication Date
WO2022237763A1 true WO2022237763A1 (zh) 2022-11-17

Family

ID=83912361

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/091921 WO2022237763A1 (zh) 2021-05-10 2022-05-10 信道监听方法与装置、终端和网络设备

Country Status (3)

Country Link
EP (1) EP4340500A1 (zh)
CN (1) CN115334688A (zh)
WO (1) WO2022237763A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110972515A (zh) * 2018-07-31 2020-04-07 Lg电子株式会社 在无线通信系统中监测终端的控制信号的方法及其终端
CN111800801A (zh) * 2019-08-16 2020-10-20 维沃移动通信有限公司 Pdcch的监听方法和设备
CN112543082A (zh) * 2019-09-20 2021-03-23 维沃移动通信有限公司 监听方法、发送方法、终端及网络侧设备
WO2021062612A1 (zh) * 2019-09-30 2021-04-08 华为技术有限公司 通信方法及装置
CN112771959A (zh) * 2019-06-27 2021-05-07 Oppo广东移动通信有限公司 资源集合监听方法、设备及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110972515A (zh) * 2018-07-31 2020-04-07 Lg电子株式会社 在无线通信系统中监测终端的控制信号的方法及其终端
CN112771959A (zh) * 2019-06-27 2021-05-07 Oppo广东移动通信有限公司 资源集合监听方法、设备及存储介质
CN111800801A (zh) * 2019-08-16 2020-10-20 维沃移动通信有限公司 Pdcch的监听方法和设备
CN112543082A (zh) * 2019-09-20 2021-03-23 维沃移动通信有限公司 监听方法、发送方法、终端及网络侧设备
WO2021062612A1 (zh) * 2019-09-30 2021-04-08 华为技术有限公司 通信方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
INTEL CORPORATION: "Corrections to multi TRP", 3GPP DRAFT; R1-2003742, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20200525 - 20200605, 16 May 2020 (2020-05-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051885514 *
NOKIA, NOKIA SHANGHAI BELL: "Clarification of QCL types for default QCL assumptions of CORESET", 3GPP DRAFT; R1-1911251 38213CRDRAFT CLARIFICATION ON DEFAULT QCL PARAMTERS, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Chongqing, China; 20191014 - 20191020, 4 October 2019 (2019-10-04), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051808368 *

Also Published As

Publication number Publication date
EP4340500A1 (en) 2024-03-20
CN115334688A (zh) 2022-11-11

Similar Documents

Publication Publication Date Title
US9681464B2 (en) Cooperative transmission within heterogeneous stations
WO2020029996A1 (zh) 检测dci的方法、配置pdcch的方法和通信装置
WO2022147720A1 (zh) 波束指示方法、装置及通信设备
WO2019136720A1 (zh) 信号传输的方法和设备
US20230063901A1 (en) Sidelink feedback method and terminal device
US11259362B2 (en) Method for repeatedly transmitting data and device
WO2018228537A1 (zh) 信息发送、接收方法及装置
WO2023273869A1 (zh) 信道状态信息报告的优先级确定方法与装置、相关设备
WO2021036910A1 (zh) 数据传输方法及装置
WO2021159497A1 (zh) 载波调度的方法及装置
WO2022213653A1 (zh) 频域资源位置确定方法与装置、终端和网络设备
WO2022237763A1 (zh) 信道监听方法与装置、终端和网络设备
WO2022141629A1 (zh) 资源确定方法、第一终端设备和第二终端设备
US20220303073A1 (en) Technologies for Reliable Physical Data Channel Reception in Wireless Communications
WO2021047479A1 (zh) 一种通信方法及装置
WO2022206914A1 (zh) 监听方法与装置、终端和网络设备
KR20220152184A (ko) 자원 지시 방법, 단말 장치 및 네트워크 장치
WO2022077346A1 (zh) 信道传输的方法、终端设备和网络设备
WO2023131319A1 (zh) 定时提前确定方法及相关装置
WO2024012561A1 (zh) 解调参考信号端口确定方法与装置、终端设备和网络设备
WO2024008096A1 (zh) 通信方法与装置、终端设备、网络设备和芯片
WO2024083029A1 (zh) 多播广播业务传输方法与装置、终端设备和网络设备
WO2024032230A1 (zh) 下行控制信道传输方法、装置及系统
WO2022021448A1 (zh) 检测控制信息的方法、传输控制信息的方法、终端设备和网络设备
WO2022206271A1 (zh) 一种确定资源的方法和装置

Legal Events

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

Ref document number: 22806726

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022806726

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2022806726

Country of ref document: EP

Effective date: 20231211