Scheduling enhancements for wireless communication systems - Patents.com
Patent Information
- Application Number
- JP2023548829
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2022-03-18
- Filing Date
- 2022-03-22
- Publication Date
- 2025-03-25
- Estimated Expiration
- 2042-03-22
AI Technical Summary
Existing wireless communication systems face challenges in efficiently managing dynamic spectrum sharing and cross-carrier scheduling, leading to limitations in PDCCH reception and control channel management, particularly in scenarios involving multiple scheduling cells and dynamic bandwidth part changes.
A method for receiving a physical downlink control channel (PDCCH) that involves determining the number of non-overlapping control channel elements (CCEs) and canceling PDCCH receptions when the number exceeds a predetermined threshold, allowing for flexible and efficient PDCCH monitoring across multiple scheduling cells without the need for RRC reconfiguration.
This approach enhances scheduling efficiency and flexibility in dynamic spectrum sharing and cross-carrier scheduling, enabling seamless transitions between scheduling cells and reducing control signaling overhead, particularly in scenarios involving LTE and NR radio access technologies.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates generally to wireless communication systems, and more particularly to scheduling enhancements for wireless communication systems, including scheduling for dynamic spectrum sharing and cross-carrier scheduling enhancements. [Background technology]
[0002] 5G mobile communications technology defines a wide frequency band to enable faster transmission speeds and new services, and can be implemented not only in bands "below 6 GHz" such as 3.5 GHz, but also in bands "above 6 GHz" known as millimeter wave (mmWave) such as 28 GHz and 39 GHz. In addition, in the case of 6G mobile communication technology (called the Beyond 5G system), implementation in the terahertz band (e.g., 95 GHz to 3 THz band) is being considered to achieve transmission speeds 50 times faster and ultra-low latency that is one-tenth of that of 5G mobile communication technology.
[0003] In the early stages of 5G mobile communications technology, standardization was underway on beamforming and massive MIMO to mitigate path loss and increase radio wave transmission distance in mmWave, dynamic operation of various numerologies (such as operation of multiple subcarrier intervals) and slot formats for efficient use of ultra-high frequency resources, initial access technology to support multiple beams and wideband, definition and operation of BWP (BandWidth Part), new channel coding methods such as LDPC (Low Density Parity Check) code for large-volume data transmission and Polar Code for reliable transmission of control information, L2 pre-processing, and network slicing to provide dedicated networks specialized for specific services, with the goal of meeting service support and performance requirements for enhanced Mobile Broadband (eMBB), Ultra Reliable & Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC).
[0004] Considering the services that 5G mobile communications technology was intended to support, discussions are currently underway to improve the initial 5G mobile communications technology and its performance. Physical layer standardization is underway for technologies such as Vehicle-to-Everything (V2X), which assists autonomous vehicles in making driving decisions based on their own position and status information transmitted by the vehicle to increase user convenience, New Radio Unlicensed (NR-U), which aims to operate systems in unlicensed spectrum in accordance with various regulatory requirements, NR UE Power Saving, Non-Terrestrial Network (NTN), which is direct communication between UE and satellite to ensure coverage in areas where communication with terrestrial networks is not possible, and positioning.
[0005] In addition, standardization is also underway in the field of radio interface architecture / protocol for technologies such as the Industrial Internet of Things (IIoT), which supports new services through linkage and integration with other industries; Integrated Access and Backhaul (IAB), which provides nodes for expanding network service areas by integrating wireless backhaul links and access links; mobility improvement including conditional handover and Dual Active Protocol Stack (DAPS) handover; and 2-step random access (2-step RACH for NR), which simplifies random access procedures. In addition, standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., Service based Architecture, Service based Interface) for combining Network Functions Virtualization (NFV) and Software Defined Network (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the UE's location.
[0006] When such 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, which will require enhanced functionality and performance of the 5G mobile communication systems and integrated operation of connected devices. To this end, new research will be conducted on 5G performance improvement and complexity reduction using extended reality (XR) to efficiently support AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality), AI (Artificial Intelligence) and Machine Learning (ML), AI service support, metaverse service support, drone communications, etc.
[0007] In addition, the development of such 5G mobile communication systems can be the basis for the development of new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multiple antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas, and large scale antennas, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), and Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, AI-based communication technology that utilizes satellites and artificial intelligence (AI) from the design stage and internalizes end-to-end AI support functions to realize system optimization, and next-generation distributed computing technology that utilizes ultra-high performance communication and computing resources to realize services of a complexity that exceeds the limits of UE computing capabilities. Summary of the Invention [Problem to be solved by the invention]
[0008] The present invention has been made in consideration of the problems in the conventional communication systems described above, and an object of the present invention is to provide a wireless communication system including scheduling for dynamic spectrum sharing and improved cross-carrier scheduling. [Means for solving the problem]
[0009] According to one aspect of the present invention, a method for receiving a physical downlink control channel (PDCCH) includes the steps of receiving first information for a first search space set for scheduling for the first cell from a first cell and receiving second information for a second search space set for scheduling for the first cell from a second cell; determining a first number of PDCCH receptions via a first number of non-overlapping control channel elements (CCEs) on the first cell in a first slot based on the first search space set; identifying at least one of the first number of PDCCH receptions exceeding a predetermined number of PDCCH receptions and a first number of the non-overlapping CCEs exceeding a predetermined number of non-overlapping CCEs; and canceling PDCCH receptions corresponding only to a third search space set in the first search space set. Effect of the Invention
[0010] The method for receiving a PDCCH according to the present invention provides an improved communication method for scheduling and cross-carrier scheduling for dynamic spectrum sharing. [Brief description of the drawings]
[0011] For a more complete understanding of the present invention, and the advantages thereof, reference is now made to the following description taken in conjunction with the accompanying drawings, in which like reference characters indicate like parts and in which: [Figure 1] 1 illustrates an exemplary wireless network in accordance with an embodiment of the present invention. [Diagram 2] FIG. 2 illustrates an exemplary BS according to an embodiment of the present invention. [Diagram 3] FIG. 2 illustrates an exemplary UE according to an embodiment of the present invention. [Figure 4] FIG. 2 illustrates an exemplary wireless transmit and receive path according to an embodiment of the present invention. [Diagram 5] FIG. 2 illustrates an exemplary wireless transmit and receive path according to an embodiment of the present invention. [Figure 6] 4 is a flow chart illustrating an exemplary method for scheduling unicast Physical Downlink Shared Channel (PDSCH) reception and Multicast and Broadcast Service (MBS) PDSCH reception from two scheduling cells on a scheduled cell according to an embodiment of the present invention. [Figure 7] 4 is a flowchart illustrating an exemplary method for switching from a first scheduled cell to a second scheduled cell according to an embodiment of the present invention. [Figure 8] 1 is a flowchart illustrating an exemplary method for cross-bandwidth portion (BWP) configuration of a linked search space set for cross-carrier scheduling according to an embodiment of the present invention. [Figure 9] 1 is a flowchart illustrating an example method for PDCCH overbooking and dropping when monitored PDCCH candidates and non-overlapping control channel elements (CCEs) for scheduled cells are counted individually in each scheduled cell according to an embodiment of the present invention. [Figure 10] 4 is a flowchart illustrating an example method for PDCCH overbooking and dropping for a primary cell scheduled by both a primary cell and a special secondary cell (sSCell) in accordance with an embodiment of the present invention. [Figure 11] 1 is a flowchart illustrating an example method for PDCCH overbooking and search space set dropping when monitored PDCCH candidates and non-overlapping CCEs for a scheduled cell are counted jointly across two scheduling cells according to an embodiment of the present invention. [Figure 12]11 is a flowchart illustrating an exemplary method for a search space set dropping procedure when the scheduled cell is a primary cell and the scheduling cell is both the primary cell and an sSCell according to an embodiment of the invention. [Figure 13] FIG. 2 is a diagram showing the structure of a UE according to an embodiment of the present invention; [Figure 14] FIG. 2 is a diagram showing the structure of a base station according to an embodiment of the present invention; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0012] [Best form] The present invention relates to scheduling enhancements for wireless communication systems, including scheduling for dynamic spectrum sharing and cross-carrier scheduling enhancements. In one embodiment, a method for receiving a physical downlink control channel (PDCCH) is provided. The method includes receiving first information for a first search space set for scheduling from a first cell to the first cell and second information for a second search space set for scheduling from a second cell to the first cell. The method includes determining a first number of PDCCH receptions via a first number of non-overlapping control channel elements (CCEs) on a first cell in a first slot based on a first search space set, and identifying at least one of: the first number of PDCCH receptions exceeding a predetermined number of PDCCH receptions; and a first number of non-overlapping CCEs exceeding a predetermined number of non-overlapping CCEs. The method further includes canceling PDCCH reception corresponding only to a third search space set in the first search space set.
[0013] In another embodiment, a user equipment (UE) is provided. The UE includes a transceiver configured to receive first information for a first search space set for scheduling for the first cell from the first cell and to receive second information for a second search space set for scheduling for the first cell from the second cell. The UE further includes a processor operably coupled to the transceiver. The processor is configured to determine a first number of PDCCH receptions via a first number of non-overlapping control channel elements (CCEs) on the first cell in the first slot based on the first search space set, and to identify at least one of the first number of PDCCH receptions exceeding a predetermined number of PDCCH receptions and the first number of non-overlapping CCEs exceeding a predetermined number of non-overlapping CCEs. The transceiver is further configured to cancel PDCCH reception corresponding only to a third search space set in the first search space set.
[0014] In yet another embodiment, a base station (BS) is provided. The BS includes a transceiver configured to transmit first information for a first search space set for scheduling from a first cell to the first cell, transmit second information for a second search space set for scheduling from the second cell to the first cell, transmit a scaling factor α for scaling a maximum number of PDCCHs (physical downlink control channels) and a maximum number of non-overlapping CCEs on the first cell in a first slot based on the first search space set, and transmit the PDCCH on the first cell or the PDCCH on the second cell in the first slot.
[0015] Other technical features will be readily apparent to those skilled in the art from the following drawings, descriptions and claims. Before proceeding with the detailed description below, it may be helpful to set out definitions of certain words and phrases that will be used throughout this patent specification. The term "couple" and its derivatives refer to direct or indirect communication between two or more elements, whether or not the two or more elements are in physical contact with one another. The terms "transmit," "receive," and "communicate," as well as their derivatives, include both direct and indirect communication. The terms "include" and "comprise," as well as their derivatives, mean inclusion without limitation. The term "or" is inclusive, meaning and / or. The phrase "associated with" and its derivatives means include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, have a relationship to or with, and the like.
[0016] The term "controller" means a device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and / or firmware. The functionality associated with any particular controller may be centralized or distributed, either locally or remotely. The phrase "at least one," when used in conjunction with a list of items, means that different combinations of one or more of the listed items may be used. For example, "at least one of A, B, and C" includes one of A, B, and C, or combinations of A and B, A and C, B and C, and A, B, and C.
[0017] Additionally, various functions described below may be implemented or supported by one or more computer programs, each of which is formed of computer readable program code and embodied in a computer readable medium. The terms “application” and “program” refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof configured for implementation in suitable computer-readable program code. The phrase "computer readable program code" encompasses types of computer code, including source code, object code, and executable code.
[0018] The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as read only memory (ROM), random access memory (RAM), a hard disk drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory. "Non-transitory" computer-readable media excludes communications links conveying wired, wireless, optical, transitory electrical or other signals. Non-transitory computer readable media includes media in which data is stored permanently and media in which data is stored and later overwritten, such as a re-recordable optical disk or erasable memory device.
[0019] Definitions for other specific words and phrases are provided throughout this patent specification. Those of skill in the art should understand that in many, if not most, cases, such definitions will apply to both conventional and future uses of words and phrases so defined.
[0020] [Mode for carrying out the invention] This application claims priority under 35 USC § 119(e) to U.S. Provisional Patent Application No. 63 / 164,331, filed March 22, 2021, and U.S. Provisional Patent Application No. 63 / 164,340, filed March 22, 2021. The entire contents of the above provisional patent application are incorporated herein by reference.
[0021] The following description of Figures 1 to 12 and various embodiments used to explain the principles of the present invention in this patent specification are merely illustrative and should not be construed in any manner as limiting the scope of the present invention. Those skilled in the art will understand that the principles of the present invention may be implemented in any suitably arranged system or device.
[0022] The following documents, namely 3GPP TS 38.211 Rel-16 v16.4.0,“NR;Physical channels and modulation”(“REF1”);3GPP TS 38.212 Rel-16 v16.4.0,“NR;Multiplexing and channel coding”(“REF2”);3GPP TS 38.213 Rel-16 v16.4.0,“NR;Physical layer procedures for control”(“REF3”);3GPP TS 38.214 Rel-16 v16.4.0,“NR;Physical layer procedures for data”(“REF4”);3GPP TS 38.321 Rel-16 v16.3.0,“NR;Medium Access Control (MAC) protocol specification”(“REF5”);3GPP TS 38.331 Rel-16 v16.3.1,“NR;Radio "3GPP TS 38.300 Rel-16 v16.4.0, "NR; NR and NG-RAN Overall Description; Stage 2" ("REF7"); and 3GPP TS 38.133 Rel-16 v16.4.0, "NR; NR Requirements for support of radio resource management" ("REF8") are hereby incorporated by reference into the subject matter of the present invention as if fully set forth herein.
[0023] Since the construction of the 4G communication system, efforts have been made to develop improved 5G or pre-5G / NR communication systems to meet the increasing demand for wireless data traffic. For this reason, 5G or pre-5G communication systems are also called “Beyond 4G networks” or “Post LTE (long term evolution) systems.” 5G communication systems are expected to be implemented in higher frequency (mmWave) bands, such as the 28 GHz or 60 GHz bands, to achieve higher data transmission rates, or in lower frequency bands, such as 6 GHz, to enable robust coverage and mobility support.
[0024] In order to reduce radio wave propagation loss and increase transmission distance, beamforming, MIMO (Massive Multiple-Input Multiple-Output), FD-MIMO (Full Dimensional MIMO), array antennas, analog beamforming, and large-scale antenna technologies are discussed in 5G communication systems. In addition, in the 5G communication system, developments are being carried out to improve the system network based on advanced small cells, cloud radio access networks (RANs), ultra-high density networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, cooperative communications, CoMP (Coordinated Multi-Points), and receive interference cancellation. The discussion of 5G systems and associated frequency bands is for reference only as certain embodiments of the present invention may be implemented in 5G systems. However, the present invention is not limited to 5G systems or associated frequency bands, and embodiments of the present invention may be utilized in connection with any frequency band. For example, aspects of the present invention may also be applied to the deployment of 5G communication systems, 6G or even subsequent releases that may use the terahertz (THz) band.
[0025] Depending on the network type, the term "base station (BS)" may refer to a component (or collection of components) configured to provide wireless access to a network, such as a transmission point (TP), a transmit-receive point (TRP), an enhanced base station (eNodeB or eNB), a gNB, a macrocell, a femtocell, a WiFi access point (AP), a satellite, or other wireless enabled device. The base station can provide wireless access via one or more wireless communication protocols, such as 5G 3GPP® New Radio Interface / Access (NR), LTE, LTE-advanced (LTE-A), High Speed Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc.
[0026] The terms “BS,” “gNB,” and “TRP” are used interchangeably in this disclosure to denote network infrastructure components that provide wireless access to remote terminals. Also, depending on the network type, the term "user terminal (UE)" may refer to any component such as a mobile station, a subscriber station, a remote terminal, a wireless terminal, a receiving point, a vehicle, or user equipment. For example, the UE may be a mobile phone, a smartphone, a monitoring device, an alarm device, a fleet management device, an asset tracking device, an automobile, a desktop computer, an entertainment device, an infotainment device, a vending machine, an electricity meter, a water meter, a gas meter, a security device, a sensor device, a home appliance, and the like.
[0027] 1 to 3 below illustrate various embodiments implemented in a wireless communication system and using orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication techniques. The illustrations of Figures 1-3 are not meant to imply physical or architectural limitations to the manner in which different embodiments may be implemented. The different embodiments of the present invention may be implemented in any suitably arranged communications system.
[0028] FIG. 1 illustrates an exemplary wireless network 100 in accordance with an embodiment of the present invention. The wireless network embodiment shown in FIG. 1 is for illustration only. Other embodiments for the wireless network 100 may be used without departing from the scope of the invention. As shown in FIG. 1, the wireless network 100 includes a base station (hereinafter, BS) 101 (e.g., a gNB), a BS 102, and a BS 103. BS101 communicates with BS102 and BS103. The BS 101 also communicates with at least one network 130, such as the Internet, a dedicated Internet Protocol (IP) network, or other data network.
[0029] BS 102 provides wireless broadband access to network 130 for a first plurality of user equipment (UE) within a coverage area 120 of BS 102 . The first plurality of UEs includes UE 111 which may be located in a small or medium-sized business (SB), UE 112 which may be located in a large enterprise (E), UE 113 which may be located in a Wi-Fi hotspot (HS), UE 114 which may be located in a first residential area (R), UE 115 which may be located in a second residential area (R), and UE 116 which may be a mobile device (M) such as a mobile phone, a wireless laptop, a wireless PDA, etc. The BS 103 provides wireless broadband access to the network 130 for a second plurality of UEs within the coverage area 125 of the BS 103 .
[0030] The second plurality of UEs includes UE 115 and UE 116. In some embodiments, one or more of the BSs (101-103) can communicate with each other and with the UEs (111-116) using 5G / NR, long term evolution (LTE), long term evolution-advanced (LTE-A), WiMAX, WiFi, or other wireless communication technologies. The dotted lines indicate the general extent of the coverage areas (120, 125), which are shown as generally circular for purposes of illustration and explanation only. It should be clearly understood that the coverage areas associated with a BS, e.g., coverage areas (120, 125), may have other shapes, including irregular shapes, depending on the configuration of the BS and the changing radio environment associated with natural and man-made obstacles.
[0031] As will be described in more detail below, one or more of the UEs (111-116) may include circuitry, programming, or a combination thereof for dynamic spectrum sharing and scheduling for enhanced cross-carrier scheduling. In certain embodiments, one or more of the BSs (101-103) include circuitry, programming, or a combination thereof for dynamic spectrum sharing and scheduling for enhanced cross-carrier scheduling.
[0032] Although FIG. 1 illustrates an example of a wireless network, various changes may be made to FIG. For example, a wireless network may include any number of BSs and any number of UEs in any suitable arrangement. BS 10 may also communicate directly with any number of UEs to provide them with wireless broadband access to network 130 . Similarly, each BS (102, 103) can communicate directly with network 130 to provide UEs with direct wireless broadband access to network 130. The BSs (101, 102, and / or 103) may also provide access to other or additional external networks, such as an external telephone network or other types of data networks.
[0033] FIG. 2 illustrates an exemplary gNB 102 in accordance with an embodiment of the present invention. The embodiment of BS 102 shown in FIG. 2 is for illustration purposes only, and the BSs (101, 103) in FIG. 1 may have the same or a similar configuration. However, BSs come in a variety of configurations, and FIG. 2 does not limit the scope of the invention to any particular implementation for a BS. As shown in FIG. 2, the BS 102 includes multiple antennas (205a-205n), multiple radio frequency (RF) transceivers (210a-210n), a transmit (TX) processing circuit 215, and a receive (RX) processing circuit 220. BS 102 also includes a controller / processor 225 , a memory 230 , and a backhaul or network interface 235 . For example, the UE 116 may include more or fewer components than those described above. 14. Also, UE 116 corresponds to the UE in FIG.
[0034] The RF transceivers (210a-210n) receive incoming RF signals, such as signals transmitted by UEs in the network 100, from the antennas (205a-205n). The RF transceivers (210a to 210n) down-convert the received RF signals to generate IF or baseband signals. The IF or baseband signal is transmitted to RX processing circuitry 220 which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. The RX processing circuitry 220 sends the processed baseband signal to a controller / processor 225 for further processing.
[0035] The TX processing circuitry 215 receives analog or digital data (eg, voice data, web data, email, or interactive video game data) from the controller / processor 225. TX processing circuitry 215 encodes, multiplexes, and / or digitizes the outgoing baseband data and generates a processed baseband or IF signal. The RF transceivers (210a to 210n) receive transmission-processed baseband or IF signals from the TX processing circuit 215, and upconvert the baseband or IF signals to RF signals that are transmitted via the antennas (205a to 205n).
[0036] The controller / processor 225 includes one or more processors or other processing devices that control the overall operation of the BS 102 . For example, controller / processor 225 controls the reception of uplink channel signals and the transmission of downlink channel signals by RF transceivers (210a-210n), RX processing circuitry 220, and TX processing circuitry 215 in accordance with well-known principles. The controller / processor 225 may also support additional functionality, such as more advanced wireless communication capabilities. For example, the controller / processor 225 can support dynamic spectrum sharing and scheduling for improved cross-carrier scheduling. Any of a variety of other functions may be supported in BS 102 by controller / processor 225.
[0037] In some embodiments, the controller / processor 225 includes at least one microprocessor or microcontroller. The controller / processor 225 also executes programs and other processes that reside in the memory 230, such as an operating system. The controller / processor 225 moves data into or out of the memory 230 as required by an executing process. In some embodiments, the controller / processor 225 supports communications between the entities, such as Web real-time communications (RTC). For example, the controller / processor 225 moves data in and out of the memory 230 depending on the process being executed.
[0038] The controller / processor 225 is also coupled to a backhaul or network interface 235 . The backhaul or network interface 235 allows the BS 102 to communicate with other devices or systems over a backhaul connection or over a network. The network interface 235 may support communication via any suitable wired or wireless connection(s). For example, if BS102 is implemented as part of a cellular communications system (e.g., one that supports 5G / NR, LTE, or LTE-A), network interface 235 enables BS102 to communicate with other BSs via wired or wireless backhaul connections.
[0039] If the BS 102 is implemented as an access point, the network interface 235 allows the BS 102 to transmit over a wired or wireless local area network, or to a larger network (e.g., the Internet) over a wired or wireless connection. The network interface 235 includes any suitable structure supporting communication via a wired or wireless connection, for example, Ethernet or an RF transceiver. The memory 230 is coupled to the controller / processor 225 . A portion of the memory 230 may include RAM, and another portion of the memory 230 may include flash memory or other ROM.
[0040] Although FIG. 2 illustrates an example of BS 102, various modifications may be made to FIG. For example, BS 102 may include any number of each of the components shown in FIG. As one particular example, an access point may include multiple interfaces 235 and the controller / processor 225 may support a routing function for routing data between different network addresses. As another specific example, although shown as including a single instance of TX processing circuitry 215 and a single instance of RX processing circuitry 220, BS 102 may include multiple instances of each (e.g., one per RF transceiver). Also, the various components of FIG. 2 may be combined, further subdivided, or omitted, and additional components may be added according to particular needs.
[0041] FIG. 3 illustrates an exemplary UE 116 in accordance with an embodiment of the present invention. The embodiment of the UE 116 shown in FIG. 3 is for illustration purposes only, and the UEs (111-115) in FIG. 1 may have the same or similar configurations. However, UEs come in a variety of configurations, and FIG. 3 does not limit the scope of the invention to any particular implementation for a UE. For example, the UE 116 may include more or fewer components than those described above. 13. Also, UE 116 corresponds to the UE in FIG.
[0042] As shown in FIG. 3, the UE 116 includes an antenna 305, an RF transceiver 310, TX processing circuitry 315, a microphone 320, and receive (RX) processing circuitry 325. The UE 116 also includes a speaker 330 , a processor 340 , an input / output (I / O) interface (IF) 345 , an input device 350 , a display 355 , and a memory 360 . The memory 360 includes an operating system (OS) 361 and one or more applications 362 .
[0043] The RF transceiver 310 receives from the antenna 305 the received RF signals transmitted by the BSs of the network 100 . The RF transceiver 310 downconverts the received RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is transmitted to RX processing circuitry 325 which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. The RX processing circuitry 325 sends the processed baseband signal to a speaker 330 (eg, voice data) or to a processor 340 for further processing (eg, web browsing data).
[0044] TX processing circuitry 315 receives analog or digital voice data from a microphone 320 or other transmit baseband data (eg, web data, email, or interactive video game data) from a processor 340 . TX processing circuitry 315 encodes, multiplexes, and / or digitizes the transmit baseband data and generates a processed baseband or IF signal. The RF transceiver 310 receives transmit processed baseband or IF signals from the TX processing circuitry 315 and upconverts the baseband or IF signals to RF signals that are transmitted via the antenna 305 .
[0045] The processor 340 , which may include one or more processors or other processing devices, controls the overall operation of the UE 116 by executing an OS 361 stored in the memory 360 . For example, processor 340 controls the reception of forward channel signals and the transmission of reverse channel signals by RF transceiver 310, RX processing circuitry 325, and TX processing circuitry 315 in accordance with well-known principles. In some embodiments, processor 340 includes at least one microprocessor or microcontroller. The processor 340 also executes other processes and programs resident in the memory 360, such as processes for beam management. Processor 340 moves data into and out of memory 360 as required by executing processes.
[0046] In some embodiments, the processor 340 is configured to execute the application 362 based on the OS 361 or upon a signal received from the BS or an operator. The processor 340 is also coupled to an I / O interface 345 that provides the UE 116 with the ability to connect to other devices, such as laptop computers and handheld computers. The I / O interface 345 is a communication path between the peripherals and the processor 340 . The processor 340 is also coupled to an input device 350 . An operator of the UE 116 inputs data into the UE 116 using the input device 350 .
[0047] The input device 350 may be a keyboard, a touch screen, a mouse, a trackball, a voice input device, or any other device capable of acting as a user interface that allows a user to interact with the UE 116 . For example, the input device 350 may include voice recognition processing to allow a user to input voice commands. In other examples, the input device 350 may include a touch panel, a (digital) pen sensor, keys, or an ultrasonic input device. The touch panel can recognize touch input in at least one of a capacitive type, a pressure reducing type, an infrared type, and an ultrasonic type, for example.
[0048] The processor 340 is also coupled to a display 355 . Display 355 may be, for example, a liquid crystal display, light emitting diode display, or other display capable of rendering text and / or at least limited graphics from a website. The memory 360 is coupled to the processor 340 . A portion of memory 230 may include random access memory (RAM), and another portion of memory 230 may include flash memory or other read-only memory (ROM).
[0049] Although FIG. 3 illustrates an example of a UE 116, various modifications may be made to FIG. For example, the various components of FIG. 3 may be combined, further subdivided, or omitted, and additional components may be added according to particular needs. As one particular example, processor 340 may be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Also, although FIG. 3 illustrates the UE 116 configured as a mobile phone or smartphone, the UE may be configured to operate as other types of mobile or stationary devices.
[0050] 4 and 5 are diagrams illustrating exemplary wireless transmit and receive paths in accordance with the present invention. In the following description, the transmit path 400 of FIG. 4 is described as being implemented in a BS (such as BS 102), while the receive path 500 of FIG. 5 is described as being implemented in a UE (e.g., UE 116). However, it will be understood that the receive path 500 may be implemented in a BS and the transmit path 400 may be implemented in a UE. In some embodiments, the receive path 500 is configured to support dynamic spectrum sharing and scheduling for enhanced cross-carrier scheduling as described in embodiments of the present invention.
[0051] The transmit path 400 shown in FIG. 4 includes a channel coding and modulation block 405, a serial-to-parallel (S-to-P) block 410, a size-N Inverse Fast Fourier Transform (IFFT) block 415, a parallel-to-serial (P-to-S) block 420, an add cyclic prefix block 425, and an up-converter (UC) 430. The receive path 500 shown in FIG. 5 includes a down-converter (DC) 555, a remove cyclic prefix block 560, a serial-to-parallel (S-to-P) block 565, a size-N Fast Fourier Transform (FFT) block 570, a parallel-to-serial (P-to-S) block 575, and a channel decoding and demodulation block 580.
[0052] As shown in FIG. 4, the channel coding and modulation block 405 receives a set of information bits and applies coding (e.g., low-density parity check (LDPC) coding) and modulates the input bits (e.g., quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM)) to generate a series of frequency-domain modulation symbols. The serial-to-parallel block 410 converts (e.g., demultiplexes) the serially modulated symbols into parallel data to generate N parallel symbol streams, where N is the IFFT / FFT size used at the BS 102 and the UE 116. The size-N IFFT block 415 performs an IFFT operation on the N parallel symbol streams to generate a time-domain output signal.
[0053] The parallel-to-serial block 420 converts (eg, multiplexes) the parallel time-domain output symbols from the size-N IFFT block 415 to generate a serial time-domain signal. The add cyclic prefix block 425 inserts a cyclic prefix into the time domain signal. An upconverter 430 modulates (eg, upconverts) the output of the added cyclic prefix block 425 to an RF frequency for transmission over a wireless channel. The signal may also be baseband filtered before conversion to RF frequency. The RF signal transmitted from BS 102 passes through a wireless channel before reaching UE 116, where the reverse operations to those performed at BS 102 are carried out.
[0054] As shown in FIG. 5, downconverter 555 downconverts the received signal to a baseband frequency, and remove cyclic prefix block 560 removes the cyclic prefix to generate a serial time-domain baseband signal. The serial-to-parallel block 565 converts the time-domain baseband signal into a parallel time-domain signal. The size-N FFT block 570 performs an FFT algorithm to generate N parallel frequency domain signals. The parallel-to-serial block 575 converts the parallel frequency domain signals into a series of modulated data symbols. The channel decoding and demodulation block 580 demodulates and decodes the modulated symbols to recover the original input data stream.
[0055] Each of the BSs (101-103) may implement a transmit path 400, shown in FIG. 4, similar to the one shown for transmitting to the UEs (111-116) on the downlink, and a receive path 500, shown in FIG. 5, similar to the one shown for receiving from the UEs (111-116) on the uplink. Similarly, each of the UEs (111-116) implements a transmit path 400 for transmitting to the BSs (101-103) on the uplink, and implements a receive path 500 for receiving from the BSs (101-103) on the downlink.
[0056] Each of the components of Figures 4 and 5 may be implemented using hardware alone or using a combination of hardware and software / firmware. As a particular example, at least some of the components of FIGS. 4 and 5 may be implemented in software, while other components may be implemented by configurable hardware or a mixture of software and configurable hardware. For example, the FFT block 570 and the IFFT block 515 may be implemented as configurable software algorithms, where the value of size N may be modified depending on the implementation.
[0057] Also, although described as using FFT and IFFT, this is by way of example only and should not be construed as limiting the scope of the invention. Other types of transforms such as discrete Fourier transform (DFT) and inverse discrete Fourier transform (IDFT) functions may be used. It is understood that for the DFT and IDFT functions, the value of the N variable can be any integer (e.g., 1, 2, 3, 4, etc.), while for the FFT and IFFT functions, the value of the N variable can be any integer that is a power of 2 (i.e., 1, 2, 4, 8, 16, etc.).
[0058] Although Figures 4 and 5 show example wireless transmit and receive paths, various modifications to Figures 4 and 5 can be made. Also, various components in Figures 4 and 5 may be combined, further subdivided, or omitted, and additional components may be added according to particular needs. 4 and 5 are also intended to illustrate examples of the types of transmit and receive paths that may be used in a wireless network. Other suitable architectures may be used to support wireless communications in a wireless network.
[0059] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiments of the present invention consider enhancements to cross-carrier scheduling to achieve fast, efficient and flexible physical downlink control channel (PDCCH) monitoring. Cross-carrier scheduling is a core element of carrier aggregation (CA) operation to improve PDCCH capacity, coverage or reliability and simplify PDCCH monitoring by UEs. Cross-carrier scheduling (CCS) involves a single scheduling cell for each serving / scheduled cell provided by higher layer configuration.
[0060] but, (i) Dynamic use of resources available for PDCCH transmission in the scheduling cell; (ii) dynamic adaptation to the offered scheduled traffic; or (iii) For UE power reduction, it is advantageous to consider scenarios where a scheduled cell may be scheduled by one or more of multiple scheduling cells. One such scenario is dynamic spectrum sharing (DSS) for a primary cell between different radio access technologies such as LTE and NR, where the primary cell can be configured for both cross-carrier scheduling and self-carrier scheduling with a secondary cell (SCell), called a special SCell (sSCell).
[0061] It is noted that PDCCH monitoring to schedule the first number of scheduled cells from the second number of scheduling cells and to obtain control information not associated with scheduling depends on the corresponding UE capability for PDCCH monitoring as described in REF3. A UE (e.g., UE 116) has a capability for PDCCH monitoring that is defined by the maximum number of PDCCH candidates that the UE can decode and the maximum number of CCEs for which the UE can obtain distinct channel estimates (non-overlapping CCEs), which is predetermined in a system operating specification. The capability may be defined per slot or per combination (X,Y), where Y is the number of consecutive symbols that the UE monitors for the PDCCH, referred to as the span, and X is the number of symbols between the first symbols of two consecutive spans.
[0062] A UE (eg, UE 116) is configured to monitor the PDCCH with multiple common search space (CSS) sets and multiple UE specific search space (USS) sets. In addition to PDCCH monitoring for unicast traffic scheduling by the USS, PDCCH monitoring for multicast-broadcast traffic scheduling by the CSS may be considered under the enhanced cross-carrier scheduling operation. There are various other limitations to the legacy operation of cross-carrier scheduling.
[0063] For example, if a scheduling cell for a scheduled cell is deactivated or an active downlink (DL) bandwidth portion (BWP) (hereinafter, (DL BWP)) is changed to dormant (DL BWP), there is no PDCCH transmission in the scheduling cell, and the corresponding scheduled cell is also effectively deactivated or changed from active (DL BWP) to dormant (DL BWP), or higher layer reconfiguration is required for the scheduled cell to establish PDCCH monitoring for a new scheduling cell. Additionally, higher layer configuration of the search space set on the scheduling cell and the search space set on the corresponding scheduled cells linked to it can limit the ability to change the activity (DL BWP) on the scheduled cells, along with the requirement that the search space set must be active (DL BWP).
[0064] Therefore, the embodiment of the present invention takes into consideration the need to activate multiple scheduling cells for PDCCH monitoring by a CSS for multicast-broadcast traffic scheduling for a scheduled cell. Embodiments of the present invention also take into account another need to support fast scheduling cell switching for a UE, for example when the current scheduling cell is deactivated or changes from active (DL BWP) to dormant (DL BWP), in order to avoid RRC reconfiguration for the scheduling cell and for the UE to continue receiving / transmitting on the scheduled cell without interruption. An embodiment of the present invention additionally takes into account the need to enable flexible configuration and linking of search space sets on scheduling cells and search space sets on scheduled cells, thereby enabling a UE to benefit from dynamic BWP modifications for the scheduling cell(s) and all of the corresponding scheduled cell(s) without restrictions on PDCCH monitoring.
[0065] Therefore, embodiments of the present invention describe a method and apparatus for cross-carrier scheduling that enables fast, efficient and flexible PDCCH monitoring in a CA framework. The embodiment of the present invention also describes a method for scheduling multicast-broadcast PDSCH reception by a CSS set on a primary cell or sSCell. In an embodiment of the present invention, a mechanism for rapid replacement of a scheduling cell is additionally described by enabling a new scheduling cell to replace a scheduling cell that has been deactivated or changed from active (DL BWP) to dormant (DL BWP) without the need for RRC reconfiguration of the scheduling cell. Additionally, embodiments of the present invention describe an approach for configuration of a search space set of a scheduled cell that is linked to a search space set on multiple (DL BWPs) of a corresponding scheduling cell.
[0066] One motivation for enhanced cross-carrier scheduling is to reduce control signaling overhead or dynamic spectrum sharing for lower frequency bands, such as below 6 GHz (also referred to as FR1), to support coexistence of LTE and NR radio access technologies. In general, the present embodiments apply to any CA deployment including operation in frequency bands above 6 GHz, sidelink / V2X communications, multi-TRP / beam / panel, unlicensed / shared spectrum (NR-U), non-terrestrial networks (NTN), for airborne systems such as unmanned aerial vehicles (UAVs) such as drones, private or non-public networks (NPN), etc.
[0067] In the embodiment of the present invention, Multicast and Broadcast Service (MBS) PDSCH scheduling for a scheduled cell from two scheduling cells is described. This is illustrated in the following examples and embodiments, such as FIG. 6, discussed below. When a UE (e.g., UE 116) is configured with scheduling on the primary cell from two scheduling cells, including the primary cell and an sSCell, PDCCH reception with a CSS set that provides a downlink control information (DCI) format for scheduling unicast PDSCH (physical downlink shared channel) reception on the primary cell occurs only on the primary cell. PDCCH reception by a CSS set that provides a DCI format for scheduling "MBS PDSCH" reception on the primary cell is performed on the primary cell or on an sSCell.
[0068] For example, the DCI format for scheduling "MBS PDSCH" reception may include a carrier indicator field (CIF) having a value indicating the cell for the corresponding "MBS PDSCH" reception, or the "MBS PDSCH" reception may be performed only on the primary cell or only on the sSCell, or the DCI format for scheduling "MBS PDSCH" reception on the primary cell may be associated with a search space set of different indices than the DCI format for scheduling "MBS PDSCH" reception on the sSCell, or the DCI format for scheduling "MBS PDSCH" reception on the sSCell may be associated with a different RNTI for scrambling the CRC (cyclic redundancy check) of the DCI format.
[0069] In an embodiment of the present invention, a fast replacement of a deactivated scheduled cell with a corresponding scheduled cell is described. This is illustrated in the following examples and embodiments, such as FIG. 7, discussed below. A UE (eg, UE 116) is configured with a set of scheduling cells for the scheduled cells. Here, since only one subset of the set of scheduling cells is active for a scheduled cell at a time, when an active scheduling cell for a scheduled cell is deactivated (or changes from active (DL BWP) to dormant BWP), the UE monitors the PDCCH for the scheduled cell on other scheduling cells in the set of scheduling cells. For example, the UE monitors the PDCCH on the scheduling cell with the smallest index that is not deactivated or has a non-dormant BWP as an active (DL BWP) without any higher layer configuration or corresponding instruction by the gNB.
[0070] In the embodiment of the present invention, a cross-BWP configuration of a search space set for cross-carrier scheduling is described. This is illustrated in the following examples and embodiments, such as FIG. 8, discussed below. When a UE (e.g., UE 116) is configured with a first search space set on a first BWP of a scheduling cell and also configured with a second search space set on a second BWP of the scheduling cell, the UE is configured with a third search space set for a scheduled cell corresponding to the scheduling cell. In this example, the third search space set is linked to both the first search space set and the second search space set. In one implementation, the third search space set has the same search space set index as the first search space set, but a different search space set index than the second search space set.
[0071] As mentioned above, a UE (eg, UE 116) is configured to monitor the PDCCH with multiple CSS sets and multiple USS sets. Because a gNB (e.g., BS102) can schedule multiple UEs in one slot, it is not practical for the gNB to configure a search space set for each UE such that the corresponding UE's capability for PDCCH monitoring is not exceeded. This is especially so in the case of the primary cell, where the UE is most frequently scheduled and from which the UE typically receives control information, since the primary cell typically provides wide coverage and is not deactivated. For this reason, "PDCCH overbooking" is allowed for the primary cell, and the configuration of search space sets may exceed the UE's capability for PDCCH monitoring in the primary cell, and the UE must specify a priority of search space sets for PDCCH monitoring and discontinue PDCCH monitoring in lower priority search space sets to ensure that the allocation of PDCCH candidates and non-overlapping CCEs for the primary cell is not exceeded.
[0072] Although a UE procedure is properly defined to drop the search space set on the primary cell to satisfy the corresponding allocation of PDCCH candidates and non-overlapping CCEs when a scheduled cell has only one scheduling cell (in the case of a primary cell, the scheduling cell is the primary cell), a new UE procedure is defined when a scheduled cell such as a primary cell has multiple scheduling cells.
[0073] An embodiment of the present invention takes into account the need to define UE procedures for search space set dropping when a UE is configured with multiple scheduling cells for a scheduled cell such as a primary cell. Accordingly, various embodiments are disclosed for handling overbooking of PDCCH monitoring for a scheduled cell, such as a primary cell, when the scheduled cell is configured with multiple scheduling cells. Several approaches are described for counting PDCCH candidates and non-overlapping CCEs in a slot or span, including corresponding UE capability limits for monitored PDCCH candidates, and prioritizing search space sets among multiple scheduling cells for PDCCH monitoring and search space set dropping.
[0074] In an embodiment of the present invention, a procedure is described for search space set dropping for a scheduled cell having multiple simultaneous / active scheduling cells. For example, if a UE (e.g., UE 116) is instructed by a DCI format or other L1 / L2 signaling or by configuration from higher layers to simultaneously monitor the PDCCH for the serving cell on two or more scheduling cells, the UE applies a prioritization rule between the search space sets on two or more scheduling cells that overlap in the same slot. A search space set may include one or more CSS sets or one or more USS sets. The UE drops PDCCH monitoring for some search space sets on one or more scheduling cell(s) according to a priority assignment rule if the number of PDCCH candidates or the number of non-overlapping CCEs in a slot or span does not exceed the corresponding limit value(s). Hereinafter, for the sake of brevity, such an event will be referred to as PDCCH overbooking.
[0075] In an embodiment of the present invention, a procedure for search space set dropping for a scheduled cell is described when PDCCH candidates or non-overlapping CCEs for a scheduled cell are counted individually for each scheduled cell from multiple scheduling cells. This is illustrated in the following examples and embodiments, such as FIG. 9, described below. For example, a UE (e.g., UE 116) determines an overbooking event for a scheduled cell by individually determining the overbooking for the scheduled cell over a slot or span for any of the scheduled cells. Such an approach may be considered, for example, when the UE counts the number of PDCCH candidates or the number of non-overlapping CCEs for a scheduled cell individually for each scheduling cell.
[0076] In an embodiment of the present invention, a procedure is described for search space set dropping for a scheduled cell when counting PDCCH candidates or non-overlapping CCEs for a jointly scheduled cell across all scheduling cells. This is illustrated in the following examples and embodiments, such as FIGS. 10 and 11, described below. For example, a UE (e.g., UE 116) counts the number of PDCCH candidates or non-overlapping CCEs for a jointly scheduled cell across the scheduling cells for the scheduled cell, and determines an overbooking event for the scheduled cell if the counted number(s) exceeds a limit on the number of PDCCH candidates or non-overlapping CCEs for the scheduled cell.
[0077] In an embodiment of the present invention, a procedure for search space set dropping is described when a UE monitors the PDCCH on only one scheduling cell in a slot or span. This is illustrated in the following examples and embodiments, such as FIG. 12, discussed below. For example, if a UE (e.g., UE 116) is instructed (e.g., by higher layers) with a search space set that causes PDCCH monitoring for a scheduled cell on at most one scheduling cell in any slot or span, the UE applies the procedures for search space set dropping as if the scheduled cell had only one scheduling cell.
[0078] In the embodiment of the present invention, a procedure for each spatial set drop on the secondary cell that schedules the primary cell is described. For example, a UE (eg, UE 116) may be configured with scheduling on a cell such as the primary cell, by both a primary cell and an sSCell. The UE is configured with a PDCCH on an sSCell with a CSS set to, for example, a "Type-3 CSS" or a CSS used for scheduling multicast-broadcast PDSCH reception on the primary cell (simply referred to as "Type-4 CSS"). The UE determines a PDCCH overbooking event for the sSCell (eg, scheduled / serving cell) based on the CSS set and / or USS set configured on the sSCell. Therefore, the UE may thereby drop some search space sets in the sSCell.
[0079] As used throughout this specification, the terms "configuration" or "higher layer configuration" and variations thereof (e.g., "configured") are used to refer to one or more of the following: system information signaling, such as via a Master Information Block (MIB) or System Information Block (SIB) (e.g., SIB1), common or cell-specific higher layer / RRC signaling, or dedicated or UE-specific or BWP-specific higher layer / RRC signaling.
[0080] Throughout this specification, the term signal quality is used to refer to, for example, reference signal received power (RSRP), reference signal received quality (RSRQ), received signal strength indicator (RSSI), signal-to-noise ratio (SNR), or signal-to-noise and interference ratio (SINR), with or without filtering, such as L1 or L3 filtering, of a signal or channel, such as a synchronization signal (SS) physical broadcast channel (PBCH) block, a reference signal (RS) including a channel state information (CSI)-RS or a sounding reference signal (SRS).
[0081] Throughout this specification, the term dynamic Physical Uplink Shared Channel (PUSCH) transmission is used to denote a PUSCH transmission that is scheduled by a DCI format. The term Xn interface refers to the network interface between NG-RAN nodes. The F1 interface refers to the network interface between the "gNB CU" (central unit) and the "gNB DU" (distributed unit). The antenna ports are defined such that the channel over which symbols on an antenna port are conveyed can be inferred from the channels over which other symbols on the same antenna port are conveyed.
[0082] In a demodulation reference signal "(DM)-RS (DM-RS)" associated with a PDSCH, the channel on which a PDSCH symbol on one antenna port is conveyed can be inferred from the channel on which a DM-RS symbol on the same antenna port is conveyed only if the two symbols are in the same resource, in the same slot and in the same precoding resource block group (PRG) as the scheduled PDSCH. For the "DM-RS" associated with the PDCCH, the channel over which a PDCCH symbol on one antenna port is conveyed is inferred from the channel over which a "DM-RS" symbol on the same antenna port is conveyed only if the two symbols lie within resources for which the UE can assume that the same precoding is used.
[0083] In the "DM-RS" associated with the PBCH, the channel over which a PBCH symbol on one antenna port is conveyed is inferred from the channel over which a "DM-RS" symbol on the same antenna port is conveyed only if the two symbols are within an SS / PBCH block (SSB) transmitted in the same slot and have the same block index. Two antenna ports are considered to be quasi co-located (QCL) if the large-scale properties of the channel over which symbols on one antenna port are conveyed can be inferred from the channel over which symbols on the other antenna port are conveyed. The large-scale attributes include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters.
[0084] The UE assumes that SS / PBCH blocks transmitted with the same center frequency location and the same block index are quasi-collocated with respect to Doppler spread, Doppler shift, average gain, average delay, delay spread, and, if applicable, spatial Rx parameters. The UE may not assume quasi-co-location for any other SS / PBCH block transmissions. In the absence of a "CSI-RS" configuration, unless otherwise configured, the UE shall assume that the "PDSCH DM-RS" and SS / PBCH blocks are quasi-co-located with respect to Doppler shift, Doppler spread, mean delay, delay spread, and, if applicable, spatial Rx parameters. The UE assumes that the PDSCH DM-RSs in the same CDM group are quasi-collocated with respect to Doppler shift, Doppler spread, mean delay, delay spread and spatial Rx. The UE may also assume that the "DM-RS" port associated with the PDSCH is "QCL Type A, Type D" (if applicable) and the average gain and QCL. The UE may also assume that the "DM-RS" does not collide with the SS / PBCH blocks.
[0085] In a particular embodiment, a UE (e.g., UE 116) is configured with a list of up to M transmission configuration indication (TCI)-state configurations in an upper layer parameter "PDSCH-Config" for decoding a PDSCH according to a detected PDCCH having a DCI intended for the UE and a given serving cell. Here, M depends on the UE capability "maxNumberConfiguredTCIstatesPerCC". Each "TCI-State" includes parameters for setting the QCL relationship between one or two downlink reference signals and the "DM-RS" port of the PDSCH, the "DM-RS" port of the PDCCH, or the "CSI-RS" port of the "CSI-RS" resources. The quasi-collocation relationship is established by the higher layer parameters 'qcl-Type1' for the first 'DL RS' and 'qcl-Type2' for the second 'DL RS' (if configured).
[0086] For two "DL RS", whether the reference is the same "DL RS" or another "DL RS", the QCL types must not be the same. The quasi-collocation type corresponding to each "DL RS" is provided by the higher layer parameter "qcl-Type" of "QCL-Info" and may have one of the following values: The first value, denoted "QCL-TypeA", corresponds to {Doppler shift, Doppler spread, mean delay, delay spread}. The second value, labeled "QCL-TypeB", corresponds to {Doppler shift, Doppler spread}. The third value, labeled "QCL-TypeC", corresponds to {Doppler shift, mean delay}. The fourth value, labeled "QCL-TypeD", corresponds to the {spatial Rx parameter}.
[0087] The UE receives a MAC Control Element (MAC-CE) activation command for mapping up to N (eg, N=8) TCI states to codepoints of the DCI field "Transmission Configuration Indication". When HARQ (hybrid automatic repeat request) ACK (acknowledgement) information corresponding to the PDSCH carrying the 'MAC-CE' activation command is transmitted to slot n, the proposed mapping between the TCI state and the code point of the DCI field 'Transmission Configuration Indication' may be applied after the MAC-CE application time, for example, slot Starting from the first slot after TIFF2024511268000002.tif11146, where TIFF2024511268000003.tif11146 is the number of slots per subframe for the subcarrier spacing (SCS) setting μ.
[0088] A gNB (such as BS102) transmits multiple SSBs within a cell bandwidth or within the frequency span of a carrier. The PCI of SSBs transmitted at different frequency locations may have different PCIs. When an SSB is associated with a SIB such as an RMSI, the SSB is called a "CD-SSB" (Cell-Defining SSB). A primary cell (PCell) is associated with a CD-SSB that is located on the synchronization raster. From the UE's perspective, each serving cell is associated with at most a single SSB. For a UE (e.g., UE 116) in the "RRC_CONNECTED" state, the BWP configured for the UE by the serving cell may be overlapped in frequency with BWPs configured for other UEs by other cells within the carrier. "CORESET#0" refers to a control resource set used for PDCCH transmission for at least SIB1 scheduling. "CORESET#0" is configured by MIB or UE-dedicated RRC signaling.
[0089] Note that the System Information (SI) includes a MIB and multiple SIBs. The minimum SI includes the information required for initial access and for obtaining any other SI. The smallest SI consists of the MIB and the first SIB (SIB1). Here, the MIB contains the required physical layer information of the cell required to receive cell barring status information and additional system information (e.g., the "CORESET#0" setting, which the MIB broadcasts periodically over the BCH). SIB1 also defines the scheduling of other system information blocks and contains information required for initial access. SIB1 is also called RMSI (Remaining Minimum SI), and is periodically broadcast via "DL-SCH" or transmitted in a UE-dedicated manner to UEs in "RRC_CONNECTED" state via "DL-SCH". Other SIBs are either broadcast periodically on the DL-SCH, broadcast on demand on the DL-SCH (i.e. upon request of a UE in RRC_IDLE, RRC_INACTIVE or RRC_CONNECTED), or provided in a dedicated manner on the DL-SCH to a UE in RRC_CONNECTED state (i.e. upon request from a UE in RRC_CONNECTED (if configured by the network or when the UE has an active BWP with no common search space configured).
[0090] For a cell / frequency to be considered for camping by the UE, the UE does not need to obtain the contents of MIB / SIB1 for that cell / frequency from other cells / frequency layers. This does not exclude the case where the UE applies stored SI from previously visited cell(s). If the UE cannot determine the entire contents of the cell's MIB / SIB1 by receiving from the cell, the UE shall consider the cell barred. For bandwidth adaptation and BWP operation, the UE acquires SI only in active BWPs. The initial BWP may be, for example, 24, 48, or 96 RB in the frequency domain. The MIB is mapped to the Broadcast Control Channel (BCCH) and carried on the BCH, while all other SI messages are mapped to the BCCH and carried dynamically on the Downlink Shared Channel (DL-SCH).
[0091] In order for a UE to be allowed to camp in a cell, the UE must obtain MIB / SIB1 from that cell. There may be cells in the system that do not broadcast MIB / SIB1, so the UE cannot camp on such cells. DAPS (Dual Active Protocol Stack) handover refers to a handover procedure that maintains the source gNB connection until the source cell is released after receiving an RRC message for handover and after successful random access to the target gNB. A MAC entity is defined for each cell group, one for the master cell group (MCG) and one for the secondary cell group (SCG). When a UE is configured for DAPS handover, two MAC entities can be considered for the UE, one for the source cell (source MAC entity) and another one for the target cell (target MAC entity).
[0092] CA is also a framework for wider bandwidth operation, where a UE transmits and / or receives in parallel on multiple carriers / cells called component carriers (CCs). CA operation may include intra-band contiguous or non-contiguous CCs as well as inter-band CCs due to frequency allocation of CCs. The CA operation is visible at the PHY and MAC layers (L1 and L2) but is transparent to higher layers. In a CA, two or more CCs are aggregated. A UE may simultaneously receive or transmit on one or multiple CCs depending on its capabilities.
[0093] For example, a UE with a single timing advance capability for CA may simultaneously receive and / or transmit on multiple CCs corresponding to multiple serving cells (multiple serving cells grouped into one Timing Advance Group (TAG)) that share the same timing advance. In another example, a UE with multiple timing advance capability for CA may simultaneously receive and / or transmit on multiple CCs corresponding to multiple serving cells (multiple serving cells grouped into multiple TAGs) with different timing advances. "NG-RAN" ensures that each TAG contains at least one serving cell. In yet another example, a non-CA capable UE receives and transmits on a single CC that corresponds to only one serving cell (one serving cell with one TAG).
[0094] For CA operation, frame timing and system frame number (SFN) are aligned across aggregation-capable cells, or a slot multiple offset between PCell / PSCell (primary secondary cell) and SCell (secondary cell) is configured for the UE. For example, the maximum number of CCs configured for a UE is 16 for DL and 16 for UL (uplink). Together with a UL / DL carrier pair (Frequency Division Duplex (FDD) band) or a bidirectional carrier (Time Division Duplex (TDD) band), the UE configures a Supplementary Uplink (SUL). A SUL differs from an aggregated uplink in that a UE may be scheduled to transmit over either the supplemental uplink or the uplink of a supplemented carrier, but not both at the same time.
[0095] When CA is configured, the UE has only one RRC connection with the network. During RRC connection establishment / re-establishment / handover, one serving cell provides non-access stratum (NAS) mobility information, and during RRC connection re-establishment / handover, one serving cell provides security input. This is called a primary cell (PCell). Depending on the UE capabilities, a secondary cell (SCell) is configured to form a serving cell set together with the PCell. Therefore, a serving cell set configured for a UE includes one PCell and one or more SCells. The reconfiguration, addition and removal of SCells is performed by the RRC. During intra-NR handover and connection resumption from "RRC_INACTIVE", the network may also add, remove, maintain or reconfigure SCells for use with the target PCell. When adding a new SCell, dedicated RRC signaling is used to transmit all the necessary system information to the SCell, i.e. while in connected mode, the UE does not need to get broadcast system information directly from the SCell.
[0096] To enable bandwidth adaptation (BS) on the PCell, a gNB (e.g., BS 102) configures UL and DL BWPs (etc.) to a UE (e.g., UE 116). In the case of CA, to activate BA on the SCell, the gNB configures the UE with a minimum (DL BWP) (i.e., may not be UL). In the case of a PCell, the BWP used for initial access is configured via system information. In the case of SCell(s), after initial activation, the BWP to be used is configured via dedicated RRC signaling.
[0097] In paired spectrum, the DL and UL switch the BWP independently. In the unpaired spectrum, the DL and UL switch the BWP simultaneously. Switching between configured BWPs can occur via RRC signaling, DCI, an inactivity timer, or when a random access is initiated. If an inactivity timer is configured for a serving cell, the active BWP is switched to the default BWP configured by the network when the inactivity timer associated with that cell expires. There may be a maximum of one active BWP per cell, except when the serving cell is configured as SUL, in which case there may be a maximum of one for each UL carrier.
[0098] In a particular embodiment, when CA is configured, a Cell activation / deactivation mechanism is supported to enable reasonable UE battery consumption. When an SCell is deactivated, the UE does not need to receive the corresponding PDCCH or PDSCH, does not transmit on the corresponding uplink, and does not need to perform Channel Quality Indicator (CQI) measurements. Conversely, when a SCell is activated, the UE is expected to be able to receive the PDSCH and PDCCH (if the UE is configured to monitor the PDCCH from that SCell) and to perform CQI measurements.
[0099] The NG-RAN ensures that no SCells in a secondary PUCCH group (a SCell group associated with a PUCCH whose PUCCH signaling is "PUCCH SCell") are activated while a PUCCH (physical uplink control channel) SCell (a secondary cell configured for a PUCCH) is deactivated. The NG-RAN ensures that the SCell mapped to the PUCCH SCell is deactivated before the PUCCH SCell is modified or removed. When reconfiguring a serving cell set, the SCells that are added to the set are initially activated or deactivated, and the SCells that remain in the set (either unchanged or reconfigured) do not change their activation state (to activated or deactivated). During handover or connection resumption in "RRC_INACTIVE", the SCell is activated or deactivated.
[0100] In a particular embodiment, when a BA is configured, to enable reasonable UE battery consumption, only one "UL BWP" and one "DL BWP" for each uplink carrier or only one "DL / UL BWP" pair is activated at a time in the active serving cell, and all other BWPs configured by the UE are deactivated. With a deactivated BWP, the UE does not monitor the PDCCH and does not transmit via the PUCCH, the physical random access channel (PRACH) and the UL-SCH. In a particular embodiment, when CA is configured, one dormant BWP is configured for the SCell to enable fast SCell activation. If the active BWP of the activated SCell is a dormant BWP, the UE stops PDCCH monitoring on the SCell but continues to perform CSI measurement, AGC, and beam management (if configured). The DCI is used to control entering / exiting a dormant BWP for one or more SCell(s) or one or more SCell group(s). A dormant BWP is one of the dedicated BWPs of a UE that is configured by the network via dedicated RRC signaling. The SpCell and the "PUCCH SCell" are not set to the dormant BWP.
[0101] Cross-carrier scheduling using CIF allows the PDCCH of a serving cell to schedule resources (e.g., for data transmission and / or reception) on other serving cells, but has the following limitations in current standards: One example restriction includes that cross-carrier scheduling cannot be applied to the PCell (ie, the PCell can be scheduled via its own PDCCH). In some examples, the PCell may also be cross-scheduled with the SCell. In yet another exemplary restriction, when a SCell is configured as a PDCCH, the PDSCH and PUSCH of the corresponding cell are scheduled by the PDCCH on the SCell. In yet another exemplary restriction, if a SCell is not configured as a PDCCH, the PDSCH and PUSCH of the corresponding cell are scheduled by the PDCCH on another serving cell. In yet another example restriction, the scheduling PDCCH and the scheduled PDSCH / PUSCH can use the same or different numerologies.
[0102] Cross-carrier scheduling allows PDCCH monitoring and / or reception in several serving cells (called scheduling cells), while the received PDCCH corresponds to scheduling data transmission and / or reception etc. in all serving cells (called scheduled cells). The PDCCH is used to schedule DL transmissions via the PDSCH and UL transmissions via the PUSCH. For example, DCI on the PDCCH is (i) a downlink assignment including at least modulation and coding format, resource assignment, and hybrid-ARQ information associated with a DL-SCH; and (ii) An uplink scheduling grant including at least modulation and coding format, resource allocation and hybrid-ARQ information associated with the UL-SCH.
[0103] In addition to scheduling, the PDCCH is used for one of the following: (i) Activation and deactivation of PUSCH transmissions configured in the configured grants; (ii) Activation and deactivation of PDSCH semi-persistent transmission; (iii) informing one or more UEs of the slot format; (iv) notifying one or more UEs of the PRB(s) and OFDM symbol(s) for which the UE can assume a transmission is not intended for the UE; (v) sending transmit power control (TPC) commands for PUCCH and PUSCH; (vi) transmitting one or more TPC commands for SRS transmission by one or more UEs; (vii) UE active bandwidth fractional switching; (viii) initiation of a random access procedure; (ix) instructing the UE(s) to monitor the PDCCH during the next occurrence of discontinuous reception (DRX) on-duration; and / or (x) In an integrated access and backhaul (IAB) context, an indication of availability for the IAB-DU soft symbol.
[0104] In a particular embodiment, a UE (eg, UE 116) monitors a PDCCH candidate set at monitoring occasions configured in one or more configured "COntrol REsource SETs" (CORESETs) with corresponding search space configurations. The CORESET is set to a PRB set having a time duration of 1 to 3 OFDM symbols. Resource units (REG) and (CCE) are defined within a CORESET, with each CCE being set in a REG set. A control channel is formed by an aggregation of CCEs. Different code rates for the control channel are implemented by aggregating different numbers of CCEs. Interleaved and non-interleaved CCE-REG mapping is supported in CORESET.
[0105] Note that polar coding may be used for the PDCCH. Each resource element group carrying a PDCCH carries its own DMRS. QPSK modulation is used for the PDCCH. The UE monitors a set of PDCCH candidates in one or more CORESETs on the active (DL BWP) of each activated serving cell configured for PDCCH monitoring with a corresponding search space set, which means that the UE decodes each PDCCH candidate according to the monitored DCI format. If the UE is provided with "monitoringCapabilityConfig-r16" for the serving cell, the UE shall: (i) per slot if "monitoringCapabilityConfig-r16=r15monitoringcapability", or (ii) If "monitoringCapabilityConfig-r16=r16monitoringcapability", obtain an instruction to monitor the PDCCH on the serving cell for the maximum number of PDCCH candidates and non-overlapping CCEs per span.
[0106] If the UE is not provisioned with "monitoringCapabilityConfig-r16", the UE shall monitor the PDCCH on the serving cell every slot. The UE indicates capability of monitoring the PDCCH with one or more of the combinations (X,Y)=(2,2), (4,3) and (7,3) per SCS configuration for μ=0 and μ=1. The span is the number of consecutive symbols in a slot that the UE is configured to monitor for the PDCCH. Each PDCCH monitoring occasion is within one span. When the UE monitors the PDCCH on a cell with combination (X,Y), the UE monitors the PDCCH on the cell including the entire slot. Supports PDCCH monitoring occasions at any symbol of a slot with a minimum time separation of X symbols between the first symbols of two consecutive spans. The span starts at the first symbol where a PDCCH monitoring occasion starts and ends at the last symbol where a PDCCH monitoring occasion ends, with a maximum of Y symbols in the span.
[0107] If the UE indicates the capability of monitoring the PDCCH with multiple (X,Y) combinations and the configuration of the search space set for the UE for PDCCH monitoring on a cell results in a separation of each two consecutive PDCCH monitoring spans that is equal to or greater than the value of X for one or more of the multiple combinations (X,Y), the UE shall use the search space set defined in Table 10.1-2A and Table 10.1-3A. TIFF2024511268000004.tif11146 and The UE monitors the PDCCH on the cell with combination (X,Y) from one or more combinations (X,Y) associated with the highest maximum number of TIFF2024511268000005.tif12146.
[0108] The UE capability for PDCCH monitoring per slot or per span on the serving cell's activity (DL BWP) is defined by the maximum number of PDCCH candidates and non-overlapping CCEs that the UE can monitor per slot or per span, respectively, on the serving cell's activity (DL BWP). If the UE indicates carrier aggregation capability for more than four serving cells in "UE-NR-Capability", it shall include in "UE-NR-Capability" an indication for the maximum number of PDCCH candidates that the UE can monitor per slot when the UE is configured for carrier aggregation operation for more than four cells.
[0109] If the UE is not configured for "NR-DC" operation, the UE TIFF2024511268000006.tif12146 Determine the ability to monitor the maximum number of PDCCH candidates per slot corresponding to a downlink cell. In this example: TIFF2024511268000007.tif12146 is the number of downlink cells configured if the UE does not provide "pdcch-BlindDetectionCA", otherwise TIFF2024511268000008.tif12146 is the value of "pdcch-BlindDetectionCA".
[0110] If the UE indicates carrier aggregation capability for more than four serving cells in "UE-NR-Capability" and the UE is not provided with "monitoringCapabilityConfig-r16" for any downlink cell or the UE is provided with "monitoringCapabilityConfig-r16=r15monitoringcapability" for all downlink cells for which the UE monitors PDCCH, then the UE shall include an indication in "UE-NR-Capability" for the maximum number of PDCCH candidates and the maximum number of non-overlapping CCEs that can be monitored per slot when the UE is configured for carrier aggregation operation for more than four cells.
[0111] If the UE is not configured for "NR-DC" operation, the UE TIFF2024511268000009.tif12146 Determine the ability to monitor the maximum number of PDCCH candidates and the maximum number of non-overlapping CCEs per slot corresponding to the downlink cell, and in this example, TIFF2024511268000010.tif12146: If the UE does not provide "pdcch-BlindDetectionCA", TIFF2024511268000011.tif12146, where TIFF2024511268000012.tif12146 is the number of downlink cells configured, if not, TIFF2024511268000013.tif12146 is the value of "pdcch-BlindDetectionCA".
[0112] For each "DL BWP" configured for the UE in the serving cell, the UE shall determine if no "CORESETPoolIndex" has been provided by higher layer signaling that provides the following, or if "CORESETPoolIndex" is provided and the value of "CORESETPoolIndex" is the same for all CORESETs: P ≤ 3 CCORESET. Alternatively, the UE may provide the following by higher layer signaling if "CORESETPoolIndex" is not provided for the first CORESET or "CORESETPoolIndex" is provided for the first CORESET and has a value of "0" and for the second CORESET and has a value of "1". P ≤ 5 CORESET.
[0113] For each CORESET, the UE is provided with various parameters by the "ControlResourceSet". One exemplary parameter includes a CORESET index P, along with a "controlResourceSetId." Here, if "CORESETPoolIndex" is not provided, or if "CORESETPoolIndex" is provided and the value of "CORESETPoolIndex" is the same for all CORESETs, 0≦p<12. Alternatively, if "CORESETPoolIndex" is not provided for the first CORESET, or "CORESETPoolIndex" is provided for the first CORESET and has a value of "0" and is provided for the second CORESET and has a value of "1", 0 <p<16である。
[0114] In another example, the parameters include a DM-RS scrambling sequence initialization value according to pdcch-DMRS-ScramblingID. In another example, the parameters include the precoder granularity for the number of REGs in the frequency domain that the UE can assume using the same "DM-RS" precoder via "precoderGranularity". In another example, the parameters include a number of consecutive symbols provided by "duration." In another example, the parameters include a set of resource blocks provided by "frequencyDomainResources." In another example, the parameters include a "CCE-REG" mapping parameter provided by "cce-REG-MappingType."
[0115] In another example, the parameters include antenna port pseudo-colocation from a set of antenna port pseudo-colocations provided by "TCI-State" indicating pseudo-colocation information of "DM-RS" antenna ports for PDCCH reception in each CORESET. Here, if the UE has been provided with up to two cell lists for concurrent TCI state activation by 'concurrentTCI-UpdateList-r16' or 'concurrentTCI-UpdateListSecond-r16', the UE shall apply the antenna port quasi-co-location provided by 'TCI-States' with the same activated 'tci-StateID' value to the CORESET with index p at all configured 'DL BWP's' of all configured cells in the lists determined from the serving cell index provided by the 'MAC CE' command.
[0116] In yet another example, the parameters schedule PDSCH reception or indicate SPS (semi-persistent scheduling) PDSCH release via "tci-PresentInDCI" or "tci-PresentInDCI-ForDCIFormat1_2" and include an indication for the presence or absence of a TCI (transmission configuration indication) field for a DCI format other than DCI format (1_0) transmitted by the PDCCH in CORESET(p).
[0117] In a particular embodiment, when "precoderGranularity=allContiguousRBs", the UE (i) configuring a resource block set of CORESET that includes more than four subsets of resource blocks that are not contiguous in frequency; (ii) any RE of the CORESET overlaps with any RE determined from "LTE-CRS-ToMatchAround" or "LTE-CRS-PatternList-r16" or overlaps with any RE of the SS / PBCH block; or (iii) We do not expect both to happen.
[0118] For each CORESET in the "DL BWP" of the serving cell, each "frequencyDomainResources" provides a bitmap. For example, if a CORESET is not associated with any search space set in "freqMonitorLocation-r16", then the bit in the bitmap is set to the starting common RB location has TIFF2024511268000014.tif11146 TIFF2024511268000015.tif12146PRBs in "DL BWP" bandwidth, in ascending order of PRB index, have a one-to-one mapping with non-overlapping groups of 6 consecutive PRBs, where the first common RB in the first group of 6 PRBs is the common RB index if "rb-Offset-r16" is not provided. TIFF2024511268000016.tif10146 or the first common RB of the first group of 6 PRBs has the common RB index I have TIFF2024511268000017.tif10146, Where: TIFF2024511268000018.tif11146 is provided by "rb-Offset-r16".
[0119] In another example, if the CORESET is associated with at least one search space set set to "freqMonitorLocation-r16", then the first TIFF2024511268000019.tif9146 bits start common RB position has TIFF2024511268000020.tif10146[REF4] TIFF2024511268000021.tif12146PRBs of "DL BWP" bandwidth with a one-to-one mapping with non-overlapping groups of 6 consecutive PRBs in ascending order of PRB index in each RB set k. Here, the first common RB in the first group of 6 PRBs is In TIFF2024511268000022.tif12146, k is indicated by "freqMonitoringLocations-r16" if not provided for the search space set, otherwise k=0.
[0120] TIFF2024511268000023.tif11146 is the number of PRBs available in RB set 0 for “DL BWP” as described in Equation 1 below, TIFF2024511268000024.tif11146 is provided by "rb-Offset-r16" or, if "rb-Offset-r16" is not provided, The file is TIFF2024511268000025.tif10146.
number
[0121] For each CORESET other than the CORESET with index 0, one of two approaches is taken: In the first approach, if the UE has not been provided with an initial configuration of the TCI state(s) for the CORESET via "tci-StatesPDCCH-ToAddList" and "tci-StatesPDCCH-ToReleaseList", or has been provided with an initial configuration of more than one TCI state for the CORESET via "tci-StatesPDCCH-ToAddList" and "tci-StatesPDCCH-ToReleaseList" but has not received a "MAC CE" activation command for one of the TCI states listed in [REF5], the UE shall assume that the "DM-RS" antenna port associated with PDCCH reception is quasi-collocated with the SS / PBCH block identified by the UE during the initial access procedure.
[0122] In another approach, if the UE has been provided with the configuration of more than one TCI state via "tci-StatesPDCCH-ToAddList" and "tci-StatesPDCCH-ToReleaseList" for the CORESET as part of a reconfiguration involving the synchronization procedure described in [REF6], but has not received a "MAC CE" activation command for one of the TCI states described in [REF5], the UE shall assume that the "DM-RS" antenna port associated with PDCCH reception is quasi-co-located with the "CSI-RS" resource or SS / PBCH block identified by the UE during the random access procedure disclosed by the reconfiguration involving the synchronization procedure described in [REF6].
[0123] For a CORESET with index 0, the UE shall assume that the “DM-RS” antenna ports for PDCCH reception in the CORESET are quasi-co-located with: (i) one or more "DL RSs" established by a TCI state (where the TCI state is indicated by a "MAC CE" activation command for the CORESET, if present); or (ii) SS / PBCH blocks identified by the UE during the most recent random access procedure that was not initiated by a PDCCH command triggering a non-contention random access procedure, if no "MAC CE" activation command has been received since the most recent random access procedure indicating the TCI state for the CORESET.
[0124] For a CORESET other than the CORESET with index 0, if the UE is provided with a single TCI state for the CORESET or if the UE receives a "MAC CE" activation command for one of the TCI states provided for the CORESET, the UE shall assume that the "DM-RS" antenna ports associated with PDCCH reception in the CORESET are quasi-collocated with one or more "DL RS" configured by the TCI state. For the CORESET with index 0, the UE expects the SS / PBCH block to provide the “QCL-Type D” of the “CSI-RS” in the TCI state indicated by the “MAC CE” activation command for the CORESET.
[0125] In this example, if the UE receives a "MAC CE" activation command for one of the TCI states, the UE shall TIFF2024511268000027.tif10131, where k is the slot in which the UE transmits a PUCCH with "HARQ-ACK" information for the PDSCH providing the activation command, and μ is the SCS setting for the PUCCH. The active BWP is defined as the active BWP of the slot when the activate command is applied. For each "DL BWP" configured for the UE in the serving cell, the UE is provided with S≦10 search space sets by higher layers, where for each search space set from the S search space sets, the UE provides the following parameters by "SearchSpace": The parameters may include:
[0126] For example, the parameter includes a search space set index s (0 < s < 40) by "searchSpaceId". In other examples, the parameter includes the relationship between the search space set s by "controlResourceSetId" and "CORESET p". In other examples, the parameter is k by "monitoringSlotPeriodicityAndOffset" s The PDCCH monitoring period of the slot and o s The PDCCH monitoring offset of the slot. In other examples, the parameter includes the PDCCH monitoring pattern within the slot, indicating the first symbol(s) of the CORESET within the slot for PDCCH monitoring, by "monitoringSymbolsWithinSlot". In other examples, the parameter is T that indicates the number of slots in which the search space set s exists by "duration" s <ks The duration of the slot. In other examples, the parameter is the number of PDCCH candidates per CCE aggregation level L for each of CCE aggregation level 1, CCE aggregation level 2, CCE aggregation level 4, CCE aggregation level 8, and CCE aggregation level 16, by "aggregationLevel1", "aggregationLevel2", "aggregationLevel4", "aggregationLevel8", and "aggregationLevel16". TIFF2024511268000028.tif11131. In other examples, the parameter includes an indication that the search space set s is a CSS set or a USS set by searchSpaceType.
[0127] In other examples, when the search space set s is a USS set, the parameter includes one or more indications including the following. (i) An instruction by “dci-Format0-0-AndFormat1-0” to monitor PDCCH candidates for DCI format (0_0) and DCI format (1_0). (ii) For DCI format (2_0) and corresponding CCE aggregation level, an instruction via “dci-Format2-0” to monitor one or two PDCCH candidates or, if “freqMonitorLocation-r16” is provided for the search space set, to cause the UE to monitor one PDCCH candidate per RB set. (iii) An instruction by “dci-Format2-1” to monitor PDCCH candidates for DCI format (2_1). (iv) An instruction by “dci-Format2-2” to monitor PDCCH candidates for DCI format (2_2). (v) An instruction by “dci-Format2-3” to monitor PDCCH candidates for DCI format (2_3). (vi) An instruction by “dci-Format2-4” to monitor PDCCH candidates for DCI format (2_4). (vii) An instruction by “dci-Format2-6” to monitor PDCCH candidates for DCI format (2_6).
[0128] In another example, if the search space set s is a USS set, the parameters include an instruction in "dci-Formats" to monitor PDCCH candidates for DCI format, DCI format (0_0) and DCI format (1_0), or for DCI format (0_1) and DCI format (1_1), or an instruction in "dci-Formats-Rel16" to monitor PDCCH candidates for DCI format (0_0) and DCI format (1_0), or for DCI format (0_1) and DCI format (1_1), or for DCI format (0_2) and DCI format (1_2), or, if the UE indicates the capability, for DCI format (0_1), DCI format (1_1), DCI format (0_2) and DCI format (1_2), or for DCI format (3_0), or for DCI format (3_1), or for DCI format (3_0) and DCI format (3_1).
[0129] In yet another example, the parameters include a bitmap (if provided) from “freqMonitorLocation-r16” indicating the index of one or more RB sets for the search space set s, where “MSB k” of the bitmap corresponds to RB set (k-1) of the “DL BWP”. For an RB set k indicated by the bitmap, the first PRB of the frequency domain monitoring location limited within the RB set is Provided by TIFF2024511268000029.tif13131, where: TIFF2024511268000030.tif12131 is the index of the first common RB in RB set k [REF4], TIFF2024511268000031.tif11146 is provided by "rb-Offset-r16", or if "rb-Offset-r16" is not provided, The file is TIFF2024511268000032.tif10146.
[0130] For each RB set with a corresponding value of '1' in the bitmap, the frequency domain resource allocation pattern for the monitoring location is the first 'frequencyDomainResources' provided by the associated CORESET configuration. TIFF2024511268000033.tif is determined based on 9146 bits. If "monitoringSymbolsWithinSlot" instructs the UE to monitor the PDCCH with a subset of up to 3 consecutive symbols that is the same in all slots in which the UE monitors the PDCCH for all search space sets, then the UE is not expected to be configured with a "PDCCH SCS" other than 15 kHz if the subset contains at least one symbol following the third symbol.
[0131] In certain embodiments, the UE does not expect to be provided with the first symbol and multiple consecutive symbols for a CORESET that are PDCCH candidates that are mapped to symbols in different slots. In a particular embodiment, no two PDCCH monitoring occasions for activity (DL BWP) are anticipated in the same CORESET separated by a non-zero number of symbols less than the CORESET duration, for the same search space set or different search space sets.
[0132] The UE determines a PDCCH monitoring occasion for activation (DL BWP) from the PDCCH monitoring period, the PDCCH monitoring offset, and the PDCCH monitoring pattern in the slot. For a search space set s, In the case of TIFF2024511268000034.tif11131, the UE is the number n f Number in frame with It is determined that a PDCCH monitoring occasion(s) exists in slot [REF1] having TIFF2024511268000035.tif13131. The UE starts from slot T s Monitor the PDCCH candidates for the search space set s of consecutive slots and select the next k S -T S Do not monitor PDCCH candidates for the search space set s of consecutive slots.
[0133] The USS for a CCE aggregation level L ∈ {1, 2, 4, 8, 16} is defined by the PDCCH candidate set for the CCE aggregation level L. If the UE is configured with "CrossCarrierSchedulingConfig" for the serving cell, the carrier indicator field value corresponds to the value indicated by "CrossCarrierSchedulingConfig". For serving cell activity (DL BWP) for which the UE monitors PDCCH candidates in USS, if the UE has not configured a carrier indicator field, the UE monitors PDCCH candidates without the carrier indicator field. For serving cell activity (DL BWP) for which the UE monitors PDCCH candidates in USS, if the UE is configured with a carrier indicator field, the UE monitors the PDCCH candidates with the carrier indicator field.
[0134] In a particular embodiment, if the UE is configured to monitor PDCCH candidates in a carrier indicator field corresponding to the corresponding secondary cell of another serving cell, the UE is not expected to monitor PDCCH candidates in the secondary cell's activity (DL BWP). For serving cell activity (DL BWP) in which the UE monitors PDCCH candidates, the UE monitors at least PDCCH candidates for the same serving cell. For a search space set s associated with CORESET p, the carrier indicator field value n CI Slots for serving cell activity (DL BWP) corresponding to Candidate search space set in TIFF2024511268000036.tif13131 The CCE index for aggregation level L corresponding to TIFF2024511268000037.tif9131 is given in Equation 2 below.
number
[0135] In formula (2), for any CSS, The file is TIFF2024511268000039.tif11131. Also, in equation (2), in the case of USS, TIFF2024511268000040.tif14131, Y p,-1 =n RNTI For pmod3=0, Ap=39827, for pmod3=1, Ap=39829, for pmod3=2, Ap=39839 and D=65537. Also, in equation (2), i = 0, , L-1. Expression N in Equation (2) CCE,p is 0 to N per RB set (if any) in "CORESET p". CCE,p This is the number of CCEs numbered down to -1. Expression n in Eq. (2) CI is the carrier indicator field value if the UE has configured the carrier indicator field by "CrossCarrierSchedulingConfig" for the serving cell where the PDCCH is monitored, otherwise n for any CSS CI =0.
[0136] In equation (2), TIFF2024511268000041.tif12131, where TIFF2024511268000042.tif12131 is UE n CI where L is the number of PDCCH candidates that are configured to be monitored for aggregation level L of search space set s for the serving cell corresponding to For any CSS, Note that the file is TIFF2024511268000043.tif13130. In the case of USS, TIFF2024511268000044.tif12130 is a set of all n CCE aggregation levels L in the search space set s. CI For values This is the maximum value of TIFF2024511268000045.tif12131.
[0137] In equation (2), n RNTI The RNTI value used is the "C-RNTI" (cell-RNTI). The UE is expected to monitor PDCCH candidates for up to four sizes of DCI formats including up to three sizes of DCI formats CRC scrambled by "C-RNTI" per serving cell. The UE counts the number of sizes for DCI formats per serving cell based on the number of PDCCH candidates configured in each search space set for the corresponding active (DL BWP).
[0138] Serving Cell n CI Search space set S using CCE set in "CORESET p" with activity (DL BWP) for j Index for The PDCCH candidate with TIFF2024511268000046.tif13130 is included in the search space set S i j Index for If there is a PDCCH candidate with TIFF2024511268000047.tif13130, it is not counted for monitoring or serving cell n that uses the same CCE set. CI The activity against (DL BWP) is in "CORESET p", and the index TIFF2024511268000048.tif13130 ( TIFF2024511268000049.tif12130) If a PDCCH candidate exists, the PDCCH candidates have the same scrambling and the corresponding DCI formats for the PDCCH candidates have the same size, otherwise, PDCCH candidates with TIFF2024511268000050.tif13130 are counted as targets for monitoring.
[0139] Table 10.1-2 of [REF3] (reproduced below and denoted as Table 1) specifies the maximum number of monitored PDCCH candidates per slot for a UE in "DL BWP" with SCS setting μ for operation with a single serving cell. Provides TIFF2024511268000051.tif12130. In particular, Table 1 shows the maximum number of monitored PDCCH candidates per slot in “DL BWP” with SCS configuration μ ∈ {0,1,2,3} for a single serving cell. TIFF2024511268000052.tif12130 is listed. [Table 1]
[0140] Table 10.1-2A of [REF3] (reproduced below and denoted as Table 2) specifies the maximum number of monitored PDCCH candidates per span for a UE in "DL BWP" with SCS setting μ for operation with a single serving cell. Provides TIFF2024511268000054.tif11130. In particular, Table 2 shows the maximum number of PDCCH candidates monitored in a span for combination (X,Y) in “DL BWP” with SCS configuration μ ∈ {0,1} for a single serving cell. TIFF2024511268000055.tif11130 is listed. [Table 2]
[0141] Table 10.1-3 of [REF3] (reproduced below and denoted as Table 3) specifies the maximum number of non-overlapping CCEs in "DL BWP" with SCS setting μ that a UE is expected to monitor corresponding PDCCH candidates per slot for operation with a single serving cell. Provides TIFF2024511268000057.tif10131. Here, the CCEs for the PDCCH candidates are (i) they correspond to different CORESET indexes, or (ii) Non-overlapping occurs when the PDCCH candidates correspond to different first symbols for reception. In particular, Table 3 shows the maximum number of non-overlapping CCEs per slot in “DL BWP” with SCS configuration μ ∈ {0,1,2,3} for a single serving cell. TIFF2024511268000058.tif10131 is listed. [Table 3]
[0142] Table 10.1-3A of [REF3] (reproduced below and denoted as Table 4) specifies the maximum number of non-overlapping CCEs in "DL BWP" with SCS setting μ that a UE is expected to monitor corresponding PDCCH candidates per span for operation with a single serving cell. Provides TIFF2024511268000060.tif12131. In particular, Table 4 shows the maximum number of non-overlapping CCEs in a span for combination (X,Y) in “DL BWP” with SCS configuration μ ∈ {0,1} for a single serving cell. TIFF2024511268000061.tif12131 is listed. [Table 4]
[0143] The UE has a "DL BWP" with SCS configuration μ TIFF2024511268000063.tif13131 When set to downlink cell (where TIFF2024511268000064.tif17131), the UE is active in the scheduling cell (DL BWP) and per slot for each scheduled cell. TIFF2024511268000065.tif12131 or more non-overlapping CCE There is no need to monitor more PDCCH candidates than TIFF2024511268000066.tif10131.
[0144] The UE has a "DL BWP" with SCS configuration μ TIFF2024511268000067.tif13131 downlink cell (where TIFF2024511268000068.tif17131), if the "DL BWP" of the activated cell is the active (DL BWP) of the activated cell and the "DL BWP" of the deactivated cell is the "DL BWP" with the index provided by the "firstActiveDownlinkBWP-Id" for the deactivated cell, the UE shall select more PDCCH candidates (as described in equation (3)) or (as described in equation (4)) TIFF2024511268000069.tif13131 There is no need to monitor more non-overlapping CCEs per slot in the activity (DL BWP)(s) of the scheduling cell(s) from the downlink cell(s).
number
number
[0145] For each scheduled cell, the UE shall transmit the scheduled cell 100 Mbps per slot in active (DL BWP) with the SCS setting μ of the scheduled cell. TIFF2024511268000072.tif13130 or more non-overlapping CCE There is no need to monitor more PDCCH candidates than TIFF2024511268000073.tif13130. If the UE does not report "pdcch-BlindDetectionCA" or is not provided with "BDFactorR", then γ=R. Similarly, if the UE reports "pdcch-BlindDetectionCA", the UE is instructed to use γ=1 or γ=R by "BDFactorR".
[0146] In a particular embodiment, a UE (e.g., UE 116) uses the SCS configuration μ along with associated PDCCH candidates monitored in the active (DL BWP) of the scheduling cell(s). TIFF2024511268000074.tif11133 When set to downlink cell (here TIFF2024511268000075.tif12133), the UE does not need to monitor at least one of the following for scheduling cell activity (DL BWP):
[0147] That is, the UE is TIFF2024511268000076.tif12133 For downlink cells, per slot for each scheduled cell TIFF2024511268000077.tif11128 or more non-overlapping CCE There is no need to monitor more PDCCH candidates than TIFF2024511268000078.tif10128 in the activity of the scheduling cell (DL BWP).
[0148] In addition, the UE is TIFF2024511268000079.tif12133 per slot for each scheduled cell if it is from a downlink cell TIFF2024511268000080.tif12133 or more non-overlapping CCE There is no need to monitor more PDCCH candidates than TIFF2024511268000081.tif12133 in the activity of the scheduling cell (DL BWP).
[0149] In addition, the UE is TIFF2024511268000082.tif12133 For downlink cells, per slot for CORESETs with the same "CORESETPoolIndex" value for each scheduled cell More than TIFF2024511268000083.tif11129 non-overlapping CCE or There is no need to monitor more PDCCH candidates than TIFF2024511268000084.tif13129 in the activity of the scheduling cell (DL BWP).
[0150] (i) The UE was not provided with "monitoringCapabilityConfig-r16" or was not provided with "monitoringCapabilityConfig-r16=r15monitoringcapability" TIFF2024511268000085.tif12129When the UE is configured in the downlink cell, (ii) When the UE is configured with the SCS configuration μ to be an associated PDCCH candidate monitored in the activity (DL BWP) of the scheduling cell(s) (here TIFF2024511268000086.tif14129), and (iii) If the "DL BWP" of the activated cell is the active (DL BWP) of the activated cell and the "DL BWP" of the deactivated cell is the "DL BWP" with an index provided by the "firstActiveDownlinkBWP-Id" for the deactivated cell, the UE may select more PDCCH candidates than those listed in Equation (5) below or more than those listed in Equation (6) below. TIFF2024511268000087.tif12129 There is no need to monitor more than non-overlapping CCEs per slot for activity (DL BWP)(s) of the scheduling cell(s) from the downlink cell.
number
number
[0151] In a particular embodiment, for each scheduled cell, the UE TIFF2024511268000090.tif12133 Downlink cell to scheduling cell SCS setting μ Active (DL BWP) per slot TIFF2024511268000091.tif13130 or more non-overlapping CCE There is no need to monitor more PDCCH candidates than TIFF2024511268000092.tif13130.
[0152] In a particular embodiment, for each scheduled cell, the UE TIFF2024511268000093.tif12133 Downlink cell to scheduling cell SCS setting μ active (DL BWP) per slot TIFF2024511268000094.tif12146 or more non-overlapping CCE There is no need to monitor more PDCCH candidates than TIFF2024511268000095.tif12146.
[0153] In a particular embodiment, for each scheduled cell, the UE TIFF2024511268000096.tif12133 Downlink cell to scheduling cell SCS setting μ active (DL BWP) for CORESET with the same "CORESETPoolIndex" value per slot TIFF2024511268000097.tif12146 or more non-overlapping CCE There is no need to monitor more PDCCH candidates than TIFF2024511268000098.tif11146.
[0154] The UE was provided with "monitoringCapabilityConfig-r16=r16monitoringcapability" TIFF2024511268000099.tif11146 Downlink cell and associated PDCCH candidates monitored in the active (DL BWP) of the scheduling cell(s) using SCS configuration μ and combination (X,Y) for PDCCH monitoring TIFF2024511268000100.tif11146 Downlink cell TIFF2024511268000101.tif11146 (where If the UE is configured with only the firstActiveDownlinkBWP-Id field, and the "DL BWP" of the activated cell is the active (DL BWP) of the activated cell, and the "DL BWP" of the deactivated cell is the "DL BWP" with index provided by "firstActiveDownlinkBWP-Id" for the deactivated cell, the UE shall TIFF2024511268000103.tif12146 more PDCCH candidates (where TIFF2024511268000104.tif12146 is expressed by the following formula (7) or TIFF2024511268000105.tif12146 or more non-overlapping CCEs (where TIFF2024511268000106.tif12146 does not need to be monitored (as described in equation (8)).
[0155] TIFF2024511268000107.tif11146If the union of PDCCH monitoring occasions from a downlink cell to all scheduling cells results in a PDCCH monitoring with combination (X,Y) and the span of any pair in the set is within Y symbols (where the first X symbol starts with the first symbol with a PDCCH monitoring occasion and the next X symbol starts with the first symbol with a PDCCH monitoring occasion that is not included in the first X symbols), then TIFF2024511268000108.tif11146 Downlink cell to all scheduling cell(s) activity (DL BWP)(s) per span set TIFF2024511268000109.tif11146 Downlink cell to all scheduling cell(s) activity (DL BWP)(s) per span set There is no need to monitor more than TIFF2024511268000110.tif12146 non-overlapping CCEs.
[0156] Similarly, the UE may TIFF2024511268000111.tif11146 Per span set spanning downlink cell to all scheduling cell activations (DL BWP) (max. one span per scheduling cell for each span set, otherwise TIFF2024511268000112.tif11146 is the number of cells set in SCS setting j) There is no need to monitor more than TIFF2024511268000113.tif12146 non-overlapping CCEs.
[0157] If the UE configures "monitoringCapabilityConfig-r16=r15monitoringcapability" and "monitoringCapabilityConfig-r16=r16monitoringcapability" for all provided downlink cells, TIFF2024511268000114.tif11146 Replaced by TIFF2024511268000115.tif11146.
number
number
[0158] In a particular embodiment, for each scheduled cell, the UE uses the combination (X,Y) to TIFF2024511268000118.tif11146 Downlink cell with SCS setting μ of the scheduling cell active (DL BWP) per span TIFF2024511268000119.tif12146 or more non-overlapping CCE There is no need to monitor more PDCCH candidates than TIFF2024511268000120.tif12146.
[0159] In certain embodiments, a UE (e.g., UE 116) is not expected to be configured with a CSS set consisting of a corresponding total number of monitored PDCCH candidates and non-overlapping CCEs per slot or span, or a number per scheduled cell, that exceeds a corresponding maximum number per slot or span, respectively. In the case of same cell scheduling or cross-carrier scheduling, a UE (e.g., UE 116) does not expect the number of PDCCH candidates and the corresponding number of non-overlapping CCEs per slot or span of a secondary cell to be greater than the corresponding number that the UE can monitor in the secondary cell per slot or span, respectively. If the UE is provided with "PDCCHMonitoringCapabilityConfig=r16monitoringcapability" for the primary cell except for the first span of each slot, the UE shall not expect the number of PDCCH candidates and the corresponding number of non-overlapping CCEs per span in the primary cell to be greater than the corresponding number that the UE can monitor in the primary cell per span.
[0160] In the case of cross-carrier scheduling, the number of PDCCH candidates for monitoring and the number of non-overlapping CCEs per span or slot are counted separately for each scheduled cell. For every search space set in slot n or in the span of slot n, CSS Let S be a set of CSS sets with cardinality CSS and J USS Let S be a set of USS sets with cardinality USS Display as. S USS USS set position S j (0≦j <J USS ) in ascending order of search space set index. CSS Set S CSS(i) The number of PDCCH candidates counted for monitoring TIFF2024511268000121.tif11146(0≦i CSS ) and USS Set S CSS (j) The number of PDCCH candidates counted for monitoring is TIFF2024511268000122.tif11146(0≦j <J USS ) to display. For a CSS set, the UE TIFF2024511268000123.tif13146 Request non-overlapping CCE TIFF2024511268000124.tif14146Monitor PDCCH candidates.
[0161] The UE shall allocate PDCCH candidates for monitoring for the USS set for the primary cell that has activity (DL BWP) with SCS setting μ in the slot if it is not provided with "PDCCHMonitoringCapabilityConfig" for the primary cell or if it is provided with "PDCCHMonitoringCapabilityConfig=r15monitoringcapability" for the primary cell according to the following pseudocode, or in the first span of each slot if it is provided with "PDCCHMonitoringCapabilityConfig=r16monitoringcapability" for the primary cell.
[0162] In the case of a USS set for scheduling on a primary cell, if a UE is provided with a "CORESETPoolIndex" for the first CORESET or is provided with a "CORESETPoolIndex" having a value of "0" for the first CORESET and is provided with a "CORESETPoolIndex" having a value of "1" for the second CORESET, and satisfies either Equation (9) below or Equation 10 below, the following pseudocode (denoted in syntax (1) below) is applied only to the USS set associated with the first CORESET. The UE is not expected to monitor the PDCCH in the USS set without a PDCCH candidate assigned for monitoring.
[0163] In the following pseudo code, if the UE is provided with "PDCCHMonitoringCapabilityConfig=r16monitoringcapability" for the primary cell, TIFF2024511268000125.tif13129 and TIFF2024511268000126.tif11129 TIFF2024511268000127.tif10146 and Replace with TIFF2024511268000128.tif12146, TIFF2024511268000129.tif10146 and TIFF2024511268000130.tif11146 TIFF2024511268000131.tif12146 and Replace them with TIFF2024511268000132.tif12146 respectively.
number
number
[0164] In the Syntax (1) below, we define a search space set S USS Let V be the set of non-overlapping CCEs for (j). CCE (S USS (j)) and the search space set S USS (j) is a set of PDCCH candidates assigned for monitoring for the CSS set and all search space sets S USS (k) (0≦k≦j) CCE (S USS (j)) is the cardinality of C(V CCE (S USS (j))). TIFF2024511268000135.tif112146
[0165] UE, (i) configured for single cell operation or operation with carrier aggregation in the same frequency band; (ii) When monitoring PDCCH candidates in overlapping PDCCH monitoring occasions in multiple CORESETs with the same or different "QCL-Type D" attributes in the activity (DL BWP) of one or more cells, the UE monitors the PDCCH only in the CORESET. Also, in this example, the UE monitors the PDCCH in the activity (DL BWP) of one of the one or more cells only in any other CORESET from the multiple CORESETs that have the same “QCL-TypeD” attribute as the CORESET.
[0166] Here, CORESET corresponds to the CSS set with the lowest index in the cell with the lowest index that contains the CSS (if it exists), otherwise it corresponds to the USS set with the lowest index in the cell with the lowest index. The lowest USS set index is determined for all USS sets that have at least one PDCCH candidate with overlapping PDCCH monitoring occasions. For the purpose of determining the CORESET, the SS / PBCH block is considered to have “CSI-RS” and other “QCL-TypeD” attributes. To determine the CORESET, it is assumed that the first "CSI-RS" associated with the SS / PBCH block of a first cell and the second "CSI-RS" associated with the SS / PBCH block of a second cell have the same "QCL-TypeD" attribute. The allocation of non-overlapping CCEs and PDCCH candidates for PDCCH monitoring depends on all search space sets associated with multiple CORESETs for one or more cell activity (DL BWP)(s). The number of active TCI states is determined from a number of CORESETs.
[0167] In a particular embodiment, the UE: (i) configured for single cell operation or operation with carrier aggregation in the same frequency band; (ii) When monitoring PDCCH candidates in overlapping PDCCH monitoring occasions in multiple CORESETs, none of which has a TCI-state with "QCL-Type D", the UE shall monitor the PDCCH candidates in overlapping PDCCH monitoring occasions for search space sets associated with different CORESETs.
[0168] It is noted that embodiments of the present invention consider various scenarios in which a UE may be configured to monitor the PDCCH for a serving cell on more than one scheduling cell. The serving cell may be a primary cell or a secondary cell (SCell), such as a PCell or a PSCell or an SpCell. The two or more scheduling cells include a primary cell or a secondary cell. The scheduling operation or PDCCH monitoring refers to self-carrier scheduling or cross-carrier scheduling. In one example, the serving cell may be a primary cell, and the corresponding two scheduling cells include a primary cell for self-carrier scheduling and a secondary cell (SCell) for cross-carrier scheduling of the primary cell, and such a SCell is referred to as a scheduling / specialized SCell or "sSCell."
[0169] In another example, the serving cell is a first SCell, and the two corresponding scheduling cells are: (i) a primary cell for cross-carrier scheduling of the first SCell and a first SCell for self-carrier scheduling; (ii) a first SCell for self-carrier scheduling and a second SCell different from the first SCell for cross-carrier scheduling of the first SCell; (iii) all of a primary cell for cross-carrier scheduling of the first SCell and a second SCell different from the first SCell; or (iv) All second and third SCells different from the first SCell for cross-carrier scheduling of the first SCell.
[0170] In yet another example, a UE (eg, UE 116) may monitor PDCCHs on multiple scheduling cells at the same or different monitoring occasions (MOs). For example, a UE may be configured to monitor PDCCH on two scheduling cells in a MO including overlapping MO, where the first and second scheduling cells are for the same serving / scheduled cell. In another example, the UE is configured with a first set of "PDCCH MO" on a first scheduling cell and a second set of "PDCCH MO" on a second scheduling cell. Here, the first and second sets of "PDCCH MO" do not overlap in time, as would be the case if the first and second sets of "PDCCH MO" were in different slots or spans of different slots. In yet another example, the UE is configured with two scheduling cells, where any slot or span includes a "PDCCH MO" on at most one scheduling cell based on network instructions, such as DCI format or MAC-CE instructions.
[0171] Although CA is considered in the present invention, the embodiments may equally be applied to scenarios with multiple transmitting and receiving points (multi-TRPs) in one or more serving / scheduled / scheduling cells, where the same and / or different spatial configurations / relationships / beams are additionally used. In the embodiment of the present invention, MBS is described for a scheduled cell when there are two (simultaneous) scheduling cells. This is illustrated in the following examples and embodiments, such as FIG.
[0172] FIG. 6 is a flow chart illustrating an example method 600 for scheduling unicast PDSCH reception and "MBS PDSCH" reception from two scheduling cells on a scheduled cell in accordance with an embodiment of the present invention. The steps of the method 600 in FIG. 6 may be performed by any of the UEs (111-116) in FIG. 1 (eg, UE 116 in FIG. 3). The method 600 is merely illustrative and other embodiments may be used without departing from the scope of the invention.
[0173] In a particular embodiment, a UE (eg, UE 116) is configured with multiple scheduling cells for a scheduled cell. For example, the scheduled cell is a primary cell and has the primary cell and an sSCell as scheduling cells. The UE is also configured to monitor a PDCCH with a CSS set for scheduling PDSCH reception, such as that associated with multicast or broadcast traffic. For simplicity, the following description uses the term MBS. The DCI format for scheduling the "MBS PDSCH" is distinguished from the DCI format for scheduling the unicast PDSCH based on a corresponding indicator field in each DCI format, based on different sizes for each DCI format, or based on different RNTIs for scrambling the CRC in each DCI format.
[0174] For example, a DCI format that schedules unicast PDSCH reception has a CRC that is scrambled by the "C-RNTI," while a DCI format that schedules "MBS PDSCH" reception has a CRC that is scrambled by the "Group-RNTI" (G-RNTI). If the UE is configured for multiple MBS traffic types, the UE provides multiple "G-RNTIs" for each, or the DCI format indicates the traffic type. In a first implementation example, a UE (e.g., UE 116) is configured with a first search space set on multiple scheduling cells for monitoring a PDCCH that provides a DCI format for scheduling a unicast PDSCH on the scheduled cell and a second search space set only on a single scheduling cell for monitoring a PDCCH that provides a DCI format for scheduling an "MBS PDSCH" on the scheduled cell, e.g., the single scheduling cell and the scheduled cell is a primary cell or an SCell. The reason for the restriction on the second search space set is to maintain common operation for both unicast PDSCH and "MBS PDSCH", where scheduling of PDSCH reception using the CSS set is only done on a single scheduled cell from a single scheduling cell (e.g., the primary cell).
[0175] In a second implementation example, a UE (e.g., UE 116) is configured with a search space set on multiple scheduling cells, such as a primary cell or an sSCell, for monitoring a PDCCH that provides a DCI format for scheduling a unicast PDSCH or an "MBS PDSCH" on a scheduled cell, such as a primary cell or an sSCell. The only search space set associated with unicast PDSCH reception scheduling on the sSCell is the USS set. The only search space set associated with "MBS PDSCH" reception scheduling is the CSS set. In the first approach, "MBS PDSCH" reception is performed only on a scheduled cell, and the DCI format for scheduling "MBS PDSCH" reception does not include a carrier indicator field.
[0176] In the second approach, the "MBS PDSCH" reception is performed on an additional scheduled cell, and the DCI format for scheduling the "MBS PDSCH" reception includes a CIF to indicate the scheduled cell. The DCI format provided by the PDCCH reception by the CSS set that schedules the unicast PDSCH reception does not include the CIF, and the unicast PDSCH reception occurs only on the same scheduled cell as the scheduling cell (eg, only on the primary cell). In the third approach, different "G-RNTIs" or different DCI format sizes are associated with different scheduled cells for MBS PDSCH reception scheduled from the same scheduling cell.
[0177] Additionally, in any implementation example, a first CORESET associated with a search space set for a DCI format that schedules "MBS PDSCH" reception may be different from a second CORESET associated with a search space set for a DCI format that schedules unicast PDSCH reception. For example, the TCI state for PDCCH reception in a first CORESET may differ from the TCI state for PDCCH reception in a second CORESET because the TRP associated with "MBS PDSCH" reception may differ from the TRP associated with unicast PDSCH reception. A similar method may be used for the DCI format that activates the SPSPDSCH for MBS traffic, or may be used for the higher layer configuration of the SPSPDSCH for MBS traffic.
[0178] Method 600 shown in FIG. 6 illustrates an exemplary procedure for scheduling unicast PDSCH reception from two scheduling cells and "MBS PDSCH" reception on a scheduled cell in accordance with the present invention. At step 610, a UE (eg, UE 116) is configured with two scheduling cells for the scheduled cell. For example, the scheduling cell is a primary cell and an sSCell, and the scheduled cell is the primary cell. In step 620, the UE receives a PDCCH with a CSS set, where the PDCCH provides a DCI format for scheduling PDSCH reception. In step 630, the UE determines whether the PDSCH is an "MBS PDSCH." If the PDSCH is not an "MBS PDSCH" but a unicast PDSCH (determined in step 630), the scheduling cell is the primary cell, the scheduled cell is the primary cell, and the DCI format does not include CIF (step 640). If the PDSCH is an "MBS PDSCH" (determined in step 630), the scheduling cell is the primary cell or any scheduling cell such as an sSCell, if the DCI format includes a CIF, the scheduled cell is the primary cell or any cell such as an sSCell, otherwise the scheduled cell is the scheduling cell (step 650).
[0179] Although FIG. 6 illustrates a method 600, various modifications to FIG. 6 may be made. For example, although method 600 is depicted as a series of steps, various steps may overlap, occur in parallel, occur in other orders, or occur multiple times. In other instances, steps may be omitted or substituted with other steps. For example, the steps of method 600 may be performed in other orders.
[0180] The present invention also provides for the rapid replacement of a deactivated scheduling cell with the corresponding scheduled cell(s). This is illustrated in the following examples and embodiments, such as FIG. FIG. 7 is a flow chart illustrating an example method 700 for switching from a first scheduled cell to a second scheduled cell according to an embodiment of the present invention. The steps of the method 700 in FIG. 7 may be performed by any of the UEs (111-116) in FIG. 1 (eg, UE 116 in FIG. 3). The method 700 is merely illustrative and other embodiments may be used without departing from the scope of the invention.
[0181] In a particular embodiment, a UE (eg, UE 116) is configured with a set of scheduling cells for a scheduled cell. Here, since only one subset of the scheduling cell set is active at a time, if an active scheduling cell for a scheduled cell is deactivated or an active (DL BWP) is changed to a dormant BWP, the UE monitors the PDCCH for the scheduled cell on other scheduling cells in the scheduling cell set, e.g., monitors the PDCCH on the scheduling cell with the smallest index that is not deactivated or on the scheduling cell that has a non-dormant BWP as active (DL BWP) without higher layer reconfiguration or corresponding instruction by the serving gNB. Such a procedure is beneficial for smooth scheduling of the scheduled cell(s) while the scheduling cell is deactivated or changes from active (DL BWP) to dormant (DL BWP).
[0182] In one implementation, a UE (eg, UE 116) is configured with a scheduled cell having a first scheduling cell as a first priority scheduling cell and a second scheduling cell as a second priority scheduling cell. For example, the priority may be explicitly indicated by a separate field in the configuration of the scheduling cell, or may be implicitly determined by the index of the scheduling cell, e.g., a scheduling cell with a smaller index has a lower priority. For example, the UE may expect to perform PDCCH monitoring for a scheduled cell on the first scheduling cell if the first scheduling cell has activity (DL BWP) and is not activated and dormant (DL BWP). If the first scheduling cell is deactivated or the UE changes its activity (DL BWP) on the first scheduling cell to dormant (DL BWP), the UE expects the scheduled cell to be scheduled by the second scheduling cell and vice versa without any additional instructions from the network. A UE may also have an activated scheduling cell, such as a primary cell.
[0183] A change of the scheduling cell from the first scheduling cell to the second scheduling cell (and vice versa) is applied after a predefined time depending on the status of the second scheduling cell. When the second scheduling cell is activated and has an active (DL BWP) that is not dormant (DL BWP) for the UE, the time is the time required for the UE to determine the deactivation of the first scheduling cell or to determine a change from an active (DL BWP) to a dormant BWP. If the second scheduling cell is activated and has an active (DL BWP) that is dormant (DL BWP) for the UE, the time additionally includes the BWP switching delay. If the second scheduling cell is deactivated, the time may additionally include the time required for time-frequency tracking, AGC settling, CSI reporting, application time of MAC Control Element (CE) commands (if activation is performed by a "MAC CE"), etc.
[0184] For example, the UE receives a “MAC CE” command for deactivation of the first scheduling cell in the PDSCH in slot n or indicates a change from active (DL BWP) to dormant (DL BWP) for the first scheduling cell in slot n. (i) DCI format (2_6), (ii) DCI format (0_1), or (iii) When receiving a DCI format such as DCI format (1_1), the UE starts monitoring the PDCCH for the scheduled cell on the second scheduling cell in the first slot.
[0185] In the first example, the first slot is TIFF2024511268000136.tif11146 and subsequent slots, where μ is the SCS setting for the cell in which the UE received the PDSCH carrying the MAC-CE command. In the second example, the first slot is the slot that is the BWP switching time duration after slot n, as defined in REF8. In the third example, the first slot is the PDSCH / PUSCH preparation time after slot n. proc,1 Or T proc,2 This is the slot after the same time duration. In the fourth example, the first slot is the symbol N symbols after the last symbol of the PDCCH in slot n indicating dormancy for the first scheduling cell, where N is based on the UE capability for PDCCH processing, e.g., N=5 if μ=0, N=5.5 if μ=1, N=11 if μ=2, and otherwise, N=10 if μ=0, N=12 if μ=1, N=22 if μ=2, N=25 if μ=3, where μ corresponds to the SCS setting for the PDCCH. In yet another example, the first slot is a combination of the above time durations.
[0186] In one implementation example, when a SCell is deactivated by a "MAC CE" command, the UE receives a "MAC CE" command on a PDSCH in slot n to deactivate the first scheduling cell or indicates dormancy (DL BWP) for the first scheduling cell in slot n. (i) DCI format (2_6), (ii) DCI format (0_1), or (iii) From the slot where a DCI format such as format (1_1) is received, for a predetermined time duration, to the slot where the UE starts monitoring the PDCCH for the scheduled cell on the second scheduling cell.
[0187] In one example, the UE does not expect to receive a PDCCH for a scheduled cell on the first scheduling cell or the second scheduling cell. In another example, the UE continues to receive the PDCCH for the scheduled cell on the first scheduling cell. Thereafter, the UE continues to receive the PDCCH on the third scheduling cell for the scheduled cell, such as the primary cell. The UE monitors the PDCCH on a new scheduling cell, such as the second scheduling cell, after a predetermined time for scheduling of transmission or reception on the scheduled cell or for other indications corresponding to the scheduled cell. In another example, when a first scheduling cell for a scheduled cell is activated or changes from active (DL BWP) to dormant (DL BWP) to non-dormant (DL BWP), the UE expects to be scheduled for the cell scheduled by the first scheduling cell and monitors the PDCCH on the first scheduling cell after a predetermined time. Alternatively, the UE may be continuously scheduled to the cell scheduled by the second scheduling cell.
[0188] In another implementation example, the serving cell is configured with a first scheduling cell and a second scheduling cell, where the first or second scheduling cell is a scheduling cell for a scheduled cell at a time occasion, and a change between the first and second scheduling cells as the scheduling cell for the scheduled cell is indicated to the UE, which is also possible when the first and second scheduling cells are all activated and have respective non-dormant activity (DL BWP). For example, the instruction is given in DCI format. For example, the indication is for a group of scheduled cells. For example, the UE may be instructed to monitor the PDCCH for the scheduled cell on the first scheduling cell if the first scheduling cell is not overloaded due to PDCCH transmission, otherwise the UE is instructed to monitor the PDCCH for the scheduled cell on the second scheduling cell. A change in the scheduling cell due to deactivation or a change in activity (DL BWP) from non-dormant to dormant may additionally be applied. Such a mechanism allows dynamic load balancing of the PDCCH load among the scheduling cells.
[0189] In one example, if the scheduled cell for the UE is a primary cell and has the primary cell and a first sSCell as the scheduling cell, the UE is additionally configured with a second sSCell for cross-carrier scheduling on the primary cell. When the first sSCell is deactivated or the activation (DL BWP) is changed to a dormant BWP for the UE, the UE starts monitoring the PDCCH on the second sSCell for cross-carrier scheduling of the primary cell. In one example, when a first sSCell is deactivated or changes an active (DL BWP) to a dormant BWP, if a second sSCell is a deactivated SCell or has a dormant BWP as an active (DL BWP), the UE is configured to activate the second sSCell (if applicable) or change the active BWP of the second sSCell to a non-dormant BWP, in which case after a predetermined time, the UE starts monitoring the PDCCH on the second sSCell for cross-carrier scheduling of the primary cell.
[0190] In one example, when the UE monitors the PDCCH on the second sSCell for scheduling on the primary cell and the UE determines that the first sSCell is activated or changes the active (DL BWP) to a non-dormant BWP, the UE returns to the first sSCell for PDCCH monitoring for scheduling on the primary cell and stops monitoring the PDCCH on the second sSCell. In another option, the UE continues monitoring the PDCCH on the second sSCell until it receives an indication from the serving gNB, possibly including by timer expiration, to monitor the PDCCH on the first sSCell for scheduling on the primary cell, or until the second sSCell is deactivated or the active (DL BWP) is changed to a dormant BWP, after which the UE returns to the first sSCell for monitoring the PDCCH for scheduling on the primary cell. The same principle applies if the scheduled cell is not the primary cell.
[0191] FIG. 7 illustrates a method 700, which is a flow chart illustrating an exemplary procedure for switching from a first scheduling cell for a scheduled cell to a second scheduling cell for a scheduled cell in accordance with the present invention. At step 710, a UE (eg, UE 116) is configured with a scheduled cell having a first priority scheduling cell and a second priority scheduling cell. At step 720, the UE monitors the PDCCH for the scheduled cell on the first priority scheduling cell. At step 730, the UE receives an instruction to deactivate the first priority scheduling cell or to switch the active BWP to a dormant BWP for the first priority scheduling cell. For example, the indication is given in DCI format or by a "MAC-CE" command. At step 740, the UE begins monitoring the PDCCH for the scheduled cell on the second priority scheduling cell. PDCCH monitoring on the second priority scheduling cell is performed after a predetermined time.
[0192] Although FIG. 7 illustrates a method 700, various modifications to FIG. For example, although method 700 is depicted as a series of steps, various steps may overlap, occur in parallel, occur in other orders, or occur multiple times. In other instances, steps may be omitted or substituted with other steps. For example, the steps of method 700 may be performed in other orders.
[0193] In the embodiment of the present invention, a cross-BWP configuration of a search space set for cross-carrier scheduling is further described. This is illustrated in the following examples and embodiments, such as FIG. FIG. 8 is a flow chart illustrating an example method 800 for cross-BWP configuration of linked search space sets for cross-carrier scheduling in accordance with an embodiment of the present invention. The steps of the method 800 in FIG. 8 may be performed by any of the UEs (111-116) in FIG. 1 (eg, UE 116 in FIG. 3). The method 800 is merely illustrative and other embodiments may be used without departing from the scope of the invention.
[0194] In a particular embodiment, the UE is configured with a first search space set on a scheduled cell linked with a second search space set configured on a second BWP of the scheduling cell, where the first search space set and the second search space set have different indices from each other, and the second BWP is different from the first BWP of the scheduling cell to which the UE is configured with a third search space set having the same index as the first search space set. In one variant, the UE may be configured with a first search space set on a scheduled cell that is linked with all of the second search space set and the third search space set on the scheduling cell, where: (i) The second search space set is (a) set in the second BWP of the scheduling cell; (b) have indices that are different from each other compared to the indices of the first search space set; (ii) The third search space set is (a) set in the first BWP of the scheduling cell; (b) having the same index as the first search space set; (iii) the first BWP and the second BWP are different from each other. It should be noted that such a mechanism allows flexible PDCCH monitoring on the scheduling cell for the scheduled cell without any restriction on dynamic BWP switching on both the scheduled cell and the scheduling cell.
[0195] For example, if the active BWP for the scheduling cell is changed from a first BWP to a second BWP, the UE will continuously monitor the PDCCH for the scheduled cell on the first search space set. Such PDCCH monitoring may not be possible if there is no link between the first and second search space sets. The UE uses the search space set for PDCCH monitoring for the scheduled cell only when the scheduling cell and the 'DL BWP' with the search space set linked to the scheduled cell are all active. The search space set index is unique for each BWP of a serving cell. Additionally, the CORESET associated with the search space set is set to the same BWP as the search space set.
[0196] Syntax (2) below describes an exemplary RRC configuration for a cross-BWP link of multiple search space sets on a scheduling cell and a search space set on a scheduled cell. TIFF2024511268000137.tif156148
[0197] Method 800 shown in FIG. 8 illustrates an example procedure for cross-BWP configuration of linked search space sets for cross-carrier scheduling in accordance with the present invention. At step 810, a UE (eg, UE 116) receives configuration for cross-carrier scheduling of a scheduled cell from a scheduling cell. In step 820, the UE receives configuration for a link between a second search space set on a second (DL BWP) of the scheduling cell and a first search space set of the scheduled cell, where the first search space set and the second search space set have different indices from each other. In step 830, the UE receives configuration for a link between a third search space set on a first (DL BWP) of the scheduling cell and the first search space set of the scheduled cell, where the first search space set has the same index as the third search space set. In step 840, if the activity (DL BWP) of the scheduling cell is first (DL BWP), the UE monitors the first search space set of scheduled cells on the third search space set of scheduling cells. In step 850, if the activity (DL BWP) of the scheduling cell is changed to a second (DL BWP), the UE monitors the first search space set of scheduling cells on the second search space set of scheduling cells.
[0198] Although FIG. 8 illustrates a method 800, various modifications to FIG. 8 may be made. For example, although method 800 is depicted as a series of steps, various steps may overlap, occur in parallel, occur in other orders, or occur multiple times. In other instances, steps may be omitted or substituted with other steps. For example, the steps of method 800 may be performed in other orders.
[0199] The present invention also describes a UE procedure for search space set dropping for a scheduled cell having multiple scheduling cells in a slot or span. In a particular embodiment, when a UE is configured / instructed to monitor PDCCHs for a serving cell on multiple scheduling cells in the same slot or span, the UE applies a priority rule for PDCCH monitoring for a search space set on multiple scheduling cells. The search space set includes one or more Common Search Space (CSS) sets or one or more UE-specific search space (USS) sets. If the number of PDCCH candidates monitored in a slot or the number of non-overlapping CCEs monitored exceeds the corresponding limit value(s), the UE drops a search space set on one or more scheduling cells among the multiple scheduling cell(s) based on a priority assignment rule. Hereinafter, for the sake of brevity, such an event will be referred to as PDCCH overbooking.
[0200] To determine a PDCCH overbooking event in a slot or span for a scheduled cell, the UE counts the number of PDCCH candidates and the number of non-overlapping CCEs that the UE monitors in the slot or span for the scheduled cell. In the first approach, the UE counts the number of PDCCH candidates or the number of non-overlapping CCEs for each scheduled cell separately. In the second approach, the UE counts the number of PDCCH candidates or the number of non-overlapping CCEs jointly across all the scheduling cells for a scheduled cell. The overbooking procedure is described for each of the following approaches.
[0201] An embodiment of the present invention also describes a UE procedure for search space set dropping for a scheduled cell when counting the number of PDCCH candidates or the number of non-overlapping CCEs for a scheduled cell individually for each scheduling cell from multiple scheduling cells. This is illustrated in the following examples and embodiments, such as FIG. FIG. 9 is a flow chart illustrating an example method 900 for PDCCH overbooking and dropping when monitored PDCCH candidates and non-overlapping CCEs for scheduled cells are counted individually from each scheduled cell in accordance with an embodiment of the present invention. The steps of the method 900 in FIG. 9 may be performed by any of the UEs (111-116) in FIG. 1 (eg, UE 116 in FIG. 3). The method 900 is merely illustrative and other embodiments may be used without departing from the scope of the invention.
[0202] In a particular embodiment, a UE (eg, UE 116) determines an overbooking event for a scheduled cell over a slot or span individually for any scheduled cell. Such an approach is applied, for example, when a UE counts the number of PDCCH candidates or the number of non-overlapping CCEs for a scheduled cell individually for each of a plurality of scheduling cells. In one example, the UE counts the number of PDCCH candidates or non-overlapping CCEs in a slot or span on each scheduling cell for a cell scheduled by an SCS setting for PDCCH transmission on the scheduling cell, and compares the number with a corresponding limit value for PDCCH candidates or non-overlapping CCEs for a scheduled cell on the scheduling cell for the SCS setting.
[0203] The UE may determine an overbooking event for a scheduled cell on a slot or span basis for the scheduled cell. For example, the UE determines an overbooking event for a scheduled cell if the number of PDCCH candidates or non-overlapping CCEs in the first slot of a first scheduling cell for the scheduled cell exceeds a limit value for the number of PDCCH candidates or non-overlapping CCEs for PDCCH reception with a first SCS setting on the first scheduling cell. Alternatively, the UE determines an overbooking event for a scheduled cell if the number of PDCCH candidates or non-overlapping CCEs in a second slot of a second scheduling cell for the scheduled cell exceeds a limit value for the number of PDCCH candidates or non-overlapping CCEs for PDCCH reception with a second SCS setting on the second scheduling cell.
[0204] When a UE (e.g., UE 116) determines an overbooking event for a scheduled cell on the first scheduling cell or the second scheduling cell, the UE applies a separate prioritization rule between the search space sets for PDCCH monitoring on the corresponding first or second scheduling cell. The UE first allocates PDCCH candidates or non-overlapping CCEs to a CSS set (if any) for a scheduled cell on the corresponding first or second scheduling cell, and allocates the remaining PDCCH candidates or non-overlapping CCEs to the first USS set in ascending / descending order of USS set index. If the UE cannot monitor all PDCCH candidates in one of the second USS sets with the smallest or smaller index, it drops PDCCH monitoring for the second USS set with the larger index. For example, if a UE is configured with the primary cell as a scheduled cell with all self-carrier and cross-carrier scheduling from the sSCell, the UE makes overbooking decisions and potential search space set dropping (e.g., USS set dropping) separately on the primary cell and on the sSCell.
[0205] The UE also determines a limit on the number of PDCCH candidates or non-overlapping CCEs in a slot or span individually for each scheduling cell. For example, the limit value corresponds to a first SCS setting μ1 for a first scheduling cell and a second SCS setting μ2 for a second scheduling cell. TIFF2024511268000138.tif12148 or TIFF2024511268000139.tif14148 is a predetermined limit value for the number of PDCCH candidates, and similar content applies to a predetermined limit value for the number of non-overlapping CCEs. In another example, the limit value is TIFF2024511268000140.tif11147 or tif12147 (where parameters 0≦α≦1 and 0≦β≦1 may be provided by higher layers), and similar considerations apply to the predetermined limit on the number of non-overlapping CCEs.
[0206] In another example, the limit value is another scaled version of the predetermined limit value on the number of PDCCH candidates, where the scaling is TIFF2024511268000142.tif12147 or Similar considerations apply to any given limit on the number of non-overlapping CCEs, except that this applies only to the components of the limit, such as TIFF2024511268000143.tif12147. In another example, the limit value is TIFF2024511268000144.tif13147 (where μ * =min{μ1,μ2}), a predetermined maximum / total limit on the number of BDs or non-overlapping CCEs corresponding to the minimum (or maximum) SCS / numerology among the scheduling cells for a scheduled cell. In yet another example, the limit is Could be other variations of scaled max / total limits, such as TIFF2024511268000145.tif12147.
[0207] In certain embodiments, the SS set drop also applies to the CSS set. For example, as discussed above, the allocation scaling parameters for PDCCH candidates and non-overlapping CCEs are set to 0≦α≦1 and 0≦β≦1, thereby preventing the UE from monitoring all PDCCH candidates or non-overlapping CCEs for all CSS sets in a slot / span on the first or second scheduling cell of the scheduled cell. In this case, the UE applies SS set dropping for the CSS set. For example, the UE may assign PDCCH candidates or non-overlapping CCEs in a slot / span to CSS sets with lower indices starting from CSS index i=0 and continuing in ascending order of CSS set indices, dropping off at the CSS set with index i if the remaining PDCCH candidates or non-overlapping CCEs are less than the PDCCH candidates or non-overlapping CCEs for CSS set i, respectively. In this case, the UE drops PDCCH monitoring for all USS sets in CSS sets and slots / spans with index greater than or equal to i.
[0208] Method 900 shown in FIG. 9 illustrates an example procedure for PDCCH overbooking and dropping when monitored PDCCH candidates and non-overlapping CCEs for scheduled cells are counted individually on each scheduled cell. At step 910, a UE (eg, UE 116) is configured with two scheduling cells for the scheduled cell. At step 920, the UE determines limits on the number of PDCCH candidates and non-overlapping CCEs for PDCCH monitoring per slot / span for the scheduled cell on each of the two scheduling cells separately. For example, such individual allocation may be based on the respective scaling parameters 0≦α≦1 or 0≦β≦1 as described above. At step 930, the UE counts the number of PDCCH candidates and non-overlapping CCEs monitored in the slot / span for the scheduled cell on each of the two scheduling cells separately. In step 940, the UE determines a PDCCH overbooking event if the number of PDCCH candidates or non-overlapping CCEs counted in a slot / span for a scheduled cell on a scheduling cell exceeds a limit value for the corresponding PDCCH candidates or non-overlapping CCEs. In response to a PDCCH overbooking event, the UE may drop the USS set with a higher index for PDCCH monitoring associated with the scheduled cell on the scheduling cell in step 950 .
[0209] Although FIG. 9 illustrates a method 900, various modifications may be made to FIG. For example, although method 900 is depicted as a series of steps, various steps may overlap, occur in parallel, occur in other orders, or occur multiple times. In other instances, steps may be omitted or substituted with other steps. For example, the steps of method 900 may be performed in other orders.
[0210] An embodiment of the present invention also describes a UE procedure for search space set dropping for a scheduled cell when counting PDCCH candidates or non-overlapping CCEs for a jointly scheduled cell across all scheduling cells. This is illustrated in the following examples and embodiments such as FIGS. FIG. 10 is a flow chart illustrating an example method 1000 for PDCCH overbooking and dropping for a primary cell scheduled by both the primary cell and an sSCell in accordance with an embodiment of the present invention. FIG. 11 is a flowchart illustrating an example method 1100 for PDCCH overbooking and dropping search space sets when monitored PDCCH candidates and non-overlapping CCEs for a scheduled cell are jointly counted across two scheduling cells in accordance with an embodiment of the present invention. The steps of the method 1000 in FIG. 10 and the method 1100 in FIG. 11 are performed by any UE (eg, UE 116 in FIG. 3) among the UEs (111 to 116) in FIG. Method 1000 and method 1100 are merely illustrative and other embodiments may be used without departing from the scope of the invention.
[0211] In a second approach, a UE (e.g., UE 116) counts the number of PDCCH candidates or non-overlapping CCEs for a jointly scheduled cell across multiple scheduling cells for the scheduled cell, and determines an overbooking event for the scheduled cell if the counted number(s) exceeds a corresponding limit value for the number of PDCCH candidates or non-overlapping CCEs. If the UE is configured to monitor PDCCH on multiple scheduling cells having the same SCS configuration on the corresponding active (DL BWP) for a scheduled cell, the UE shall count the number of PDCCH candidates or non-overlapping CCEs for the scheduled cell in the slot / span across all scheduling cells and compare the counted number with the corresponding maximum / total limit value for the SCS configuration.
[0212] If the UE is configured to monitor PDCCH on two scheduled cells having different SCS settings in the corresponding active (DL BWP) for a scheduled cell, the UE counts the number of monitored PDCCH candidates or non-overlapping CCEs for the scheduled cell based on a slot / span determined by one of the following options: In one option (denoted as Option 1), the UE counts the number of monitored PDCCH candidates or non-overlapping CCEs for a scheduled cell by the slot / span corresponding to the scheduling cell with the smaller SCS setting. In another option (denoted as option 2), the UE counts the number of monitored PDCCH candidates or non-overlapping CCEs for scheduled cells by the slot / span corresponding to the scheduling cell with the larger SCS configuration. In another option (denoted as option 3), the UE counts the number of monitored PDCCH candidates or non-overlapping CCEs for a scheduled cell by the slot / span corresponding to the SCS setting for a reference cell, e.g., the scheduled cell, or a scheduling cell with a higher priority level, such as a primary cell, or a priority based on ascending / descending order of cell index. In yet another option (denoted as option 4), the UE counts the number of monitored PDCCH candidates or non-overlapping CCEs for scheduled cells by a reference slot / span corresponding to a reference SCS setting provided by higher layers or pre-determined in a system operational specification, such as an SCS setting of 15 kHz for FR1 and 120 kHz for FR2.
[0213] In one example, for the first option (described above), if multiple slots / spans of a second scheduling cell with a second SCS setting overlap with slots / spans of a first scheduling cell with a first SCS setting (the second SCS setting is larger than the first SCS setting), the UE counts all PDCCH candidates on the second scheduling cell in multiple slots / spans together with the number of PDCCH candidates on the first scheduling cell in the slot / span. A similar example is applied to count the number of non-overlapping CCEs. Similar examples(s) apply to any of the third or fourth options if the PDCCH candidates or non-overlapping CCEs on the first or second scheduling cell(s) have an SCS setting that is greater than the SCS setting for the reference cell as in the third option or greater than the reference SCS / numerology as in the fourth option.
[0214] In one example, for the second option (described above), a first slot / span of a first scheduling cell having a first SCS setting is partially overlapped with a second slot / span of a second scheduling cell having a second SCS setting, where the first SCS setting is smaller than the second SCS setting. This means that in a first implementation example, the UE counts PDCCH candidates on the first scheduling cell against the number of PDCCH candidates monitored for the scheduled cell in the second slot / span, and the corresponding limit value is for the second SCS setting and the second slot / span. In a second implementation example, the UE counts PDCCH candidates on the second scheduling cell against the number of PDCCH candidates monitored for the scheduled cell in the first slot / span, and the corresponding limit value is the limit value for the first SCS setting and the first slot / span. A similar example applies to calculate the number of non-overlapping CCEs for a scheduled cell. Similar examples(s) apply to any of the third or fourth options if the PDCCH candidates or non-overlapping CCEs on the first or second scheduling cell(s) have an SCS setting that is smaller than the SCS setting for the reference cell, as in the third option, or larger than the reference SCS / numerology, as in the fourth option.
[0215] For example, if two scheduling cells have two different SCS settings μ1 and μ2 for each activation (DL BWP), then BD 1 and B.D. 2 are the numbers of PDCCH candidates monitored in the first and second scheduling cells, respectively, and CCE 1 and CCE 2 Let β be the number of non-overlapping CCEs monitored in the first scheduling cell and the second scheduling cell, respectively. In a first example for counting allocations of PDCCH candidates / non-overlapping CCEs to a slot- or span-specific search space set, the UE counts PDCCH candidates / non-overlapping CCEs based on the SCS setting of the active (DL BWP) of the corresponding scheduling cell. For example, the UE may set BD per slot / span based on the SCS setting μ1. 1 and CCE 1 Count the number of BDs per slot / span based on the SCS setting μ2 2 and CCE 2 Count.
[0216] In a second example, the UE may allocate 100 BDs per slot / span based on a reference setting such as a minimum or maximum SCS setting of the scheduling cell, or based on a default SCS setting, e.g., determined in a system operation specification for each frequency range or set by higher layers. 1 and CCE 1 , and B.D. 2 and CCE 2 Count. For example, if μ1=15kHz and μ2=30kHz, the UE will set the BD per slot / span based on the SCS setting μ1=15kHz. 1 and CCE 1 After counting, BD per 2 slots / span using SCS setting μ1=30kHz 2 and CCE 2 (the ratio between the SCS of the second scheduling cell and the SCS of the first scheduling cell is 2), and the UE compares the counted PDCCH candidates and non-overlapping CCEs with the corresponding limit values for SCS setting μ1=15 kHz.
[0217] Based on Tables 10.1-2 and 10.1-3 of [REF3], since the UE capability for the total number of PDCCH candidates or non-overlapping CCEs for PDCCH monitoring for two slots for SCS setting μ2=30 kHz is greater than the corresponding UE capability for PDCCH monitoring for one slot for SCS setting μ1=15 kHz, the limit values for the number of PDCCH candidates and non-overlapping CCEs for the scheduled cell are determined based on the scheduling cell with the smaller SCS setting to apply the PDCCH overbooking procedure, thereby ensuring that the UE has PDCCH monitoring capability according to the search space set resulting from the PDCCH overbooking procedure.
[0218] In various examples, the UE operation for counting multiple PDCCH candidates jointly across two scheduling cells of a scheduled cell may include: (i) indicating a simple addition or linear combination of a first number of PDCCH candidates on a first scheduling cell and a second number of PDCCH candidates on a second scheduling cell; or (ii) A weighted combination of a first number of PDCCH candidates on a first scheduling cell and a second number of PDCCH candidates on a second scheduling cell, where the UE determines the weighting parameters based on scaling parameters 0≦α≦1 and 0≦β≦1, which are subsequently taken into account, relative to a limit on the number of PDCCH candidates or non-overlapping CCEs in a slot or span for the scheduled cells.
[0219] The UE determines a limit on the number of PDCCH candidates or non-overlapping CCEs in a slot or span for a scheduled cell and across multiple scheduling cells for a jointly scheduled cell. In a first example, the limit may be a predefined maximum / total limit on the number of PDCCH candidates based on the minimum or maximum SCS configuration of the scheduling cell, e.g. The file is TIFF2024511268000146.tif12148. For example, for two scheduling cells having corresponding first and second SCS configurations μ1≦μ2, the UE determines the maximum / total limit values for the number of PDCCH candidates per slot based on the corresponding per-slot maximum / total limit values for SCS configuration μ1. The UE applies the same approach to determine the maximum / total limit on the number of non-overlapping CCEs.
[0220] In a second example, the limit value may be a scaled version of a predefined maximum / total limit value on the number of PDCCH candidates, e.g. TIFF2024511268000147.tif13147, where the scaling parameters 0≦α≦1 and 0≦β≦1 are provided by higher layers or predetermined in the system operating specifications. The UE applies the same approach to determine the maximum / total limit on the number of non-overlapping CCEs.
[0221] In a third example, the limit may be another scaled version of a predefined maximum / total limit on the number of PDCCH candidates, where the scaling is TIFF2024511268000148.tif14142 or Applies to only a part or component of the limiting value, such as TIFF2024511268000149.tif12142. The UE applies the same approach to determine the maximum / total limit on the number of non-overlapping CCEs.
[0222] The UE (e.g., UE 116) determines a PDCCH overbooking event for a scheduled cell in a slot or span if the counted number of monitored PDCCH candidates or non-overlapping CCEs in a slot / span from the search space set exceeds a corresponding limit value in the slot or span calculated by the UE jointly across multiple scheduling cells. In this case, the UE applies a prioritization rule within the search space set for scheduled cells on all multiple scheduling cells, and when an overbooking event occurs, the UE drops the search space set. Priority assignment between search space sets on multiple scheduling cells for a scheduled cell may be determined based on one or more of a priority order between search space set types such as CSS sets and USS sets, a priority order between multiple scheduling cells, and a priority order between search space sets of the same type on the same scheduling cell.
[0223] For example, the UE may give higher priority to the CSS set compared to the USS set. In another example, the UE (i) a cell index, such as a primary cell, having a higher priority than a SCell, such as an sSCell; (ii) SCS setting for the active (DL BWP) of a scheduling cell such that a scheduling cell with a smaller (or larger) SCS setting has a higher priority than a scheduling cell with a larger (or smaller) SCS setting. (iii) the priority level between scheduling cells provided by higher layer configuration, or (iv) Based on the combination, giving the first scheduling cell a higher priority than the second scheduling cell. In yet another example, among search sets of the same type on the same scheduling cell, the UE gives higher priority to search space sets with smaller indices.
[0224] It is noted that there may be additional criteria for determining the priority order between search space sets in a slot or span, such as the number of PDCCH candidates in a search space set, the maximum CCE aggregation level for the PDCCH candidates corresponding to the search space set, the DCI format type / size for the search space set, or the TCI state for a CORESET associated with a search set, such as prioritization of search space sets associated with CORESETs having the same TCI state when a UE cannot receive simultaneously due to more than one TCI state. For example, a search set with a larger number of total PDCCH candidates has a higher priority than a search space set with a smaller number of total PDCCH candidates.
[0225] For example, a first search space set having non-'0' PDCCH candidates with a larger maximum CCE aggregation level, such as '16 CCE', has higher priority than a search space set having non-'0' PDCCH candidates with a smaller maximum CCE aggregation level, such as '4 CCE'. In another example, a search space set associated with a CORESET configured with a TCI state of “CSI-RS” has a higher (or lower) priority than a search space set associated with a CORESET configured with a TCI state of SSB. In yet another example, a search space set associated with a CORESET having a lower CORESET index and / or set to a BWP having a lower BWP index has a higher priority.
[0226] In one implementation example, when the UE considers only one or more of the three main factors described above for search space set prioritization, if the search space sets have the same priority, it uses one or more of the additional criteria described above to determine the priority order between the search space sets. For example, the selection or criteria of the above factors or combinations thereof may be predetermined in the specifications for the system operation. In yet another example, higher layer configuration provides an indication as to which of the above factors or criteria or combinations thereof may be used to determine the SS set priority level. In a further example, the SS set priority level may be set by a higher layer.
[0227] In the first approach, the UE applies the prioritization rules in three steps. In a first example, the UE first applies a priority order by search space set type, then by scheduling cell order index, and finally by search space set index. In another example, the UE applies the priority order first by search space set type, then by search space set index, and finally according to the scheduling cell index order. In a third example, the UE first applies the priority order according to the scheduling cell index order, then by search space set type, and finally by search space set index. The UE may also assign PDCCH candidates and non-overlapping CCEs to a CSS set, assuming that no priority assignment for the CSS set is required.
[0228] Then, for the USS sets, the UE gives a priority designation by USS set index, and if the USS sets have the same index, gives a priority designation by scheduling cell index, where the priority designation by scheduling cell index is defined in the system operation specification or provided by higher layers, such as prioritizing the USS set on the scheduling cell with the smallest (or largest) index. Alternatively, for a USS set, the UE may prioritize by scheduling cell index based on one of the previous approaches, and for the same scheduling cell index, prioritize by ascending order of USS set index.
[0229] In another example, the UE applies a prioritization rule in one or two steps by combining some or all of the three factors considered above. For example, the UE may first apply a priority order according to the search space set type, and then follow the combined priority order that includes all of the scheduling cell priority and the search space set index. For example, such a combined priority order may be set by higher layer signaling or determined from a specification formula, such as "combined priority level = scheduling cell priority + search space set index" or "combined priority level = scheduling cell priority * search space set index". The prioritization rules / order are either predetermined in the specification for the system operation or set by a higher layer.
[0230] The UE can expect that the total number of PDCCH candidates and the total number of non-overlapping CCEs due to the CSS set on all scheduled cells for a scheduled cell in a slot / span for the SCS setting as described above will not exceed the corresponding limit value for the scheduled cell. The UE then assigns the remaining PDCCH candidates or non-overlapping CCEs for the scheduled cell to a USS set on the scheduling cell for the scheduled cell, and if necessary, the UE applies the search space set dropping procedure for the USS set as described above. For example, if the scheduled cell is a primary cell and the corresponding scheduling cells are the primary cell and an sSCell, the PDCCH candidates / non-overlapping CCEs can be assigned to the CSS sets on the PCell and sSCell without CSS set dropping, and search space set dropping is applied to the USS sets on the primary cell or the sSCell. The decision on which USS set to drop is based on the priority between the search space sets, taking into account, for example, the scheduling cell index and the search space set index as described above.
[0231] Method 1000 shown in FIG. 10 illustrates an example procedure for PDCCH overbooking and dropping for a primary cell that is scheduled by both the primary cell and an sSCell. At step 1010, a UE (eg, UE 116) is configured to monitor the PDCCH for scheduling to the primary cell in both the primary cell and the sSCell. In step 1020, the UE determines a limit on the number of PDCCH candidates and non-overlapping CCEs in a slot / span for the primary cell based on the minimum SCS between the primary cell and the sSCell. In step 1030, the UE allocates PDCCH candidates and non-overlapping CCEs in slots / spans for the primary cell to a CSS set on the primary cell and the sSCell. In step 1040, the UE determines the number of remaining PDCCH candidates and non-overlapping CCEs in the primary cell and in the sSCell, up to the corresponding limit, in the slot / span to assign to the USS set for the primary cell. In step 1050, the UE determines a PDCCH overbooking event if the number of PDCCH candidates or non-overlapping CCEs in a slot / span for the primary cell across the entire USS set on the primary cell or sSCell exceeds the determined corresponding remaining number. In response to an overbooking event, according to the prioritization rules, the UE drops the USS set in the primary cell or sSCell having a lower priority in step 1060 . For example, the prioritization rule between the primary cell and the USS set of the sSCell may be based on the scheduling cell priority and the search space set index as described above.
[0232] In another example, PDCCH overbooking is applied to both the CSS set and the USS set. A prioritization rule may be applied between the CSS sets of multiple scheduling cells for a scheduled cell, and in case of a PDCCH overbooking event, the CSS set(s) with lower priority may be dropped. For example, if the scheduled cell is a primary cell and the corresponding scheduling cell is the primary cell and an sSCell, the UE drops the CSS set on the sSCell when an overbooking event occurs. The decision of which CSS or USS set to drop is based on the priority between the search space sets taking into account, for example, the scheduling cell index and the search space set index as described above. In another example, the UE drops the CSS set on the primary cell.
[0233] In another implementation example, a UE (e.g., UE 116) allocates PDCCH candidates and non-overlapping CCEs among multiple scheduling cells for a scheduled cell based on a priority assignment among the multiple scheduling cells, for example, using the methods described above. For example, the UE may assign PDCCH candidates and non-overlapping CCEs to a CSS set first, and then to a USS set on a scheduling cell with a higher priority, continuing by ascending order of scheduling cell priority. In one example, the UE expects that the number of PDCCH candidates or non-overlapping CCEs corresponding to the CSS set of the scheduling cell with the highest priority for the scheduled cell does not exceed the limit value of PDCCH candidates or non-overlapping CCEs for the scheduled cell. Then, the UE does not drop the CCS set on the scheduling cell with the highest priority, drops the USS set on the scheduling cell with the highest priority, or drops the CSS set or USS set on the scheduling cell with a priority lower than the highest. For example, if the scheduled cell for the UE is a primary cell and the corresponding scheduling cells are the primary cell and an sSCell, the UE first allocates PDCCH candidates and non-overlapping CCEs to a CSS set on the primary cell. Then, when a PDCCH overbooking event occurs, the UE drops the USS set on the primary cell or the CSS set or USS set on the sSCell. The decision as to which CSS or USS sets to drop is based on the priorities between the search space sets as described above.
[0234] In another implementation, a UE (eg, UE 116) allocates PDCCH candidates and non-overlapping CCEs among multiple scheduling cells for a scheduled cell by alternating allocations across search space sets on multiple serving cells. For example, if there are two scheduling cells for a scheduled cell, after allocating PDCCH candidates and non-overlapping CCEs to the CSS set, the UE allocates the PDCCH candidates and non-overlapping CCEs to the USS set with the lowest index on the first (or second) scheduling cell, then the UE allocates the PDCCH candidates and non-overlapping CCEs to the USS set with the lowest index on the second (or first) scheduling cell, then the UE allocates the PDCCH candidates and non-overlapping CCEs to the USS set with the next lowest index on the first (or second) scheduling cell, and so on. For example, a search space set with a higher priority is a CSS set with a lower index in a cell with a lower index that contains the CSS set (if any), otherwise a USS set with a lower index in a cell with a lower index that has at least one PDCCH candidate with overlapping PDCCH monitoring occasions / slots / spans.
[0235] Method 1100 shown in FIG. 11 illustrates an example procedure for PDCCH overbooking and dropping of search space sets when monitored PDCCH candidates and non-overlapping CCEs for a scheduled cell are counted jointly across two scheduling cells. At step 1110, a UE (eg, UE 116) is configured with two scheduling cells for the scheduled cell. In step 1120, the UE determines limit values for PDCCH candidates and non-overlapping CCEs for the scheduled cell per slot / span based on the minimum SCS configuration in the scheduling cell. In step 1130, the UE counts the number of monitored PDCCH candidates and non-overlapping CCEs for cells scheduled in slots / spans with minimum SCS jointly across the two scheduling cells. In step 1140, the UE determines a PDCCH overbooking event if the number of PDCCH candidates or non-overlapping CCEs for a scheduled cell counted in slots / spans across two scheduling cells exceeds a corresponding limit value. In response to the overbooking event, the prioritization rule causes the UE to drop the CSS or USS set with lower priority among the search space sets on the two scheduling cells in step 1150 .
[0236] Also, without expecting that the UE will determine an overbooking event for a CSS set in one or both of the scheduling cells, it may be possible to determine whether there is an overbooking event after allocating PDCCH candidates and non-overlapping CCEs to one or both of the scheduling cells. For example, the prioritization rule may be based on at least one of the priorities between two scheduling cells, or may be based on ascending order of search space set indexes while considering the scheduling cells, such as prioritizing the search space sets on the scheduling cell with the highest index or the scheduling cell with the lowest index, as described above.
[0237] Although FIG. 10 illustrates a method 1000 and FIG. 11 illustrates a method 1100, various modifications may be made to FIGS. For example, although methods 1000 and 1100 are depicted as a series of steps, various steps may overlap, occur in parallel, occur in other orders, or occur multiple times. In other instances, steps may be omitted or substituted with other steps. For example, the steps of methods 1000 and 1100 may be performed in other orders.
[0238] An embodiment of the present invention also describes a UE procedure for search space set dropping when the UE monitors the PDCCH for only one scheduling cell in a slot or span. This is illustrated in the following examples and embodiments, such as FIG. FIG. 12 is a flow chart illustrating an example method 1200 for a search space set dropping procedure when the scheduled cell is a primary cell and the scheduling cell is both a primary cell and an sSCell in accordance with an embodiment of the present invention. The steps of method 1200 of FIG. 12 may be performed by any UE (111-116) of FIG. 1, such as UE 116 of FIG. The method 1200 is merely illustrative and other embodiments may be used without departing from the scope of the invention.
[0239] In certain embodiments, a configuration is provided for a search space set on multiple scheduling cells that does not generate PDCCH monitoring occasions for multiple scheduling cells for cells scheduled in the same slot or span, thereby allowing the UE to coordinate procedures for determining PDCCH overbooking events. The UE may determine to monitor the PDCCH for a scheduled cell on only one scheduling cell in a slot, where the slot may be determined by the smallest SCS setting among the activity of multiple scheduling cells (DL BWP) based on: (i) configuration by higher layers of a search space set that causes PDCCH monitoring in slots or spans for only one of the multiple scheduling cells; or (ii) An indication via L1 / L2 signaling to generate a search space set with PDCCH monitoring in slots or spans for only one of the multiple scheduling cells. In one example, such a determination for only one scheduling cell in a slot applies to a period such as multiple consecutive slots. In another example, the UE alternates between multiple scheduling cells from one slot / span / MO to the next slot / span / MO.
[0240] In one implementation example, when a UE (e.g., UE 116) monitors a PDCCH for a cell scheduled by a USS set for only one scheduling cell in a slot out of two scheduling cells, the UE may: (i) a CSS set on a first scheduling cell, a CSS set on a second scheduling cell, and a USS set on the first scheduling cell; or (ii) determining a PDCCH overbooking event based only on the number of PDCCH candidates or non-overlapping CCEs corresponding to one of the CSS set on the first scheduling cell, the CSS set on the second scheduling cell, and the USS set on the second scheduling cell; For example, the UE does not drop the USS set in both the first and second scheduling cells in the same slot / span relative to the scheduled cell.
[0241] In another example, when the scheduled cell is a primary cell and the scheduling cell is the primary cell and an sSCell, the UE assigns the PDCCH candidates and non-overlapping CCEs in the slot / span to a CSS set on the primary cell and a CSS set on the sSCell, assigns the remaining PDCCH candidates and non-overlapping CCEs (if any) in the slot / span to a USS set with a lower index on the primary cell (or sSCell), and drops the USS set with a higher index on the primary cell (or sSCell) in the slot / span. In this case, the UE does not consider the USS set on the sSCell (or the primary cell) in the slot / span and does not need to specify the priority between the USS set on the primary cell and the USS set on the sSCell.
[0242] Method 1200 shown in FIG. 12 describes an exemplary procedure for a search space set dropping procedure when the scheduled cell is a primary cell and the scheduling cell is both the primary cell and an sSCell, where the USS set for the primary cell is configured only on the sSCell. At step 1210, a UE (eg, UE 116) is configured with a CSS set on both the primary cell and the sSCell, for a scheduled cell that is a primary cell, and a USS set only on the sSCell. In step 1220, the UE assigns PDCCH candidates and non-overlapping CCEs in a slot / span to a CSS set on the primary cell. In step 1230, the UE assigns the remaining PDCCH candidates and non-overlapping CCEs (if any) in the slot / span to the CSS set on the sSCell and then to the USS set on the sSCell in ascending order of the corresponding indexes. In response to a PDCCH overbooking event, the UE, in step 1240, drops the CSS set on the sSCell or the USS set on the sSCell that has a larger search space set index.
[0243] For example, the CSS set on a first scheduling cell, such as a primary cell, and the CSS set on a second scheduling cell, such as an sSCell, do not occur in any slot or span. The UE then: (i) a CSS set on the first scheduling cell, a USS set on the first scheduling cell, and a USS set on the first scheduling cell; or (ii) determining a PDCCH overbooking event based only on the number of non-overlapping CCEs or PDCCH candidates corresponding to one of the CSS set on the second scheduling cell, the USS set on the first scheduling cell, and the USS set on the second scheduling cell;
[0244] In another example, the UE may give higher priority to the USS set of the primary cell compared to the CSS set of the sSCell. In a further example, the UE may give a higher priority to the USS set of the sSCell compared to the CSS set of the primary cell. In a particular embodiment, when the scheduled cell is a primary cell and the scheduling cell is both the primary cell and an sSCell, the UE assigns PDCCH candidates and non-overlapping CCEs only to the CSS set on the primary cell (or sSCell), and assigns the remaining PDCCH candidates and non-overlapping CCEs (if any) to the USS set on the primary cell or the sSCell according to the search space set prioritization rules described above.
[0245] For example, a UE (eg, UE 116) may monitor a PDCCH for a cell scheduled in any slot according to the search space set of the first scheduling cell or according to the search space set of the second scheduling cell. Then, if applicable, the UE performs a procedure to drop the search space set as if there was only one scheduling cell (eg, the scheduled cell is the primary cell).
[0246] In another example, if the scheduled cell is a primary cell and the scheduling cell is the primary cell and an sSCell, the UE is configured only in the CSS set on the primary cell and in both the CSS set and the USS set on the sSCell. For example, a CSS set including "Type-0 / 0A / 1 / 2 PDCCH" and possibly "Type-3 PDCCH" or "Type-4 PDCCH" (CSS set for multicast service) is configured on the primary cell. For example, a CSS set including a "Type-3 PDCCH" or a "Type-4 PDCCH" is configured on the sSCell. PDCCH candidates and non-overlapping CCEs for all CSS sets of PCell / PSCell and sSCell are within the corresponding limit values in slot / span as described above. The UE allocates the remaining PDCCH candidates and non-overlapping CCEs to the USS set on the sSCell in ascending order of USS set index in the slot / span. If the UE determines an overbooking event for the primary cell, the UE may drop the USS set on the sSCell with a higher index.
[0247] In yet another example, if the scheduled cell for a UE is the primary cell and the scheduling cell is the primary cell and an sSCell, the UE is configured with only a CSS set on the primary cell and only a USS set on the sSCell. In this case, the UE assigns the PDCCH candidates and non-overlapping CCEs in a slot to a CSS set on the primary cell, and assigns the remaining PDCCH candidates and non-overlapping CCEs (if any) to a USS set on the sSCell in ascending order of search space set index. If the UE determines an overbooking event in a slot / span, the UE drops the USS set on the sSCell with a higher index. Such a PDCCH dropping method is applied at least when the UE counts multiple PDCCH candidates and non-overlapping CCEs jointly across the primary cell and sSCell as previously described. If the UE counts multiple PDCCH candidates and non-overlapping CCEs separately for the primary cell and sSCell, then either no overbooking event is expected for the primary cell or PDCCH overbooking and dropping of the search space set is applied to at least the USS set on the sSCell (e.g., when the scaling parameter(s) 0≦α≦1 or 0≦β≦1 is applied to the PDCCH candidate or non-overlapping CCE allocation).
[0248] Although FIG. 12 illustrates a method 1200, various modifications to FIG. For example, although method 1200 is depicted as a series of steps, various steps may overlap, occur in parallel, occur in other orders, or occur multiple times. In other instances, steps may be omitted or substituted with other steps. For example, the steps of the method 1200 may be performed in other orders.
[0249] The embodiments of the present invention further describe PDCCH overbooking and dropping for a secondary cell "sSCell" that schedules a PCell / PSCell. In a particular embodiment, a UE (eg, UE 116) is configured with a primary cell as the scheduled cell from the scheduling cell, which is a "sSCell." A UE is configured with a CSS set on the sSCell, such as a "Type-3 PDCCH CSS" set or a "Type-4 CSS" set (for multicast PDSCH scheduling), and needs to support overbooking on the sSCell since such a CSS set can be offloaded from the primary cell. The UE determines a PDCCH overbooking event on the sSCell based on the CSS set or USS set configured for the sSCell for scheduling on the primary cell. Therefore, the UE drops the search space set on the sSCell according to the priority specification rule.
[0250] In one example, for a UE, the sSCell allows only self-carrier scheduling (the UE cannot schedule on the sSCell from any other cell). The UE counts the number of PDCCH candidates and non-overlapping CCEs for the CSS set and USS set on the sSCell (scheduled cell) based on the SCS configuration for the activity (DL BWP) of the sSCell and the slot / span corresponding to the sSCell. The UE compares the number of PDCCH candidates and non-overlapping CCEs for the sSCell in a slot / span with the corresponding limit value in the slot / span for the SCS configuration of the active BWP of the sSCell.
[0251] The UE determines a PDCCH overbooking event if the number of PDCCH candidates or non-overlapping CCEs for the sSCell counted in a slot / span exceeds the corresponding limit value in the slot / span. Several approaches are considered. In the first approach, the UE counts all CSS sets on the sSCell in a slot / span as scheduled cells in the slot / span towards the number of monitored PDCCH candidates and non-overlapping CCEs for the sSCell. In a second approach, the UE splits multiple PDCCH candidates and multiple non-overlapping CCEs for a CSS set on the sSCell, or on any scheduling cell in general, among the scheduled cells for the sSCell, or for the scheduling cell in general.
[0252] for example, TIFF2024511268000150.tif1313The number of PDCCH candidates and the number of non-overlapping CCEs for the CSS set on the cell that is the scheduling cell for one scheduled cell are respectively TIFF2024511268000151.tif11142 and Display as TIFF2024511268000152.tif11142. Where: TIFF2024511268000153.tif13131 may be the same as or different from the number of downlinks / scheduled cells having a scheduling cell with SCS setting μ.
[0253] In this case, the first (or last) TIFF2024511268000154.tif11142 The scheduled cells are TIFF2024511268000155.tif13142 PDCCH candidates can be assigned, and the last (or first) TIFF2024511268000156.tif13142 The scheduled cells are TIFF2024511268000157.tif13131PDCCH candidates can be assigned.
[0254] Similarly, the first (or last) TIFF2024511268000158.tif11131The scheduled cells are TIFF2024511268000159.tif11131 Non-overlapping CCE can be assigned, and the last (or first) TIFF2024511268000160.tif13131 The scheduled cells are TIFF2024511268000161.tif12131 can be assigned a non-overlapping CCE, where: TIFF2024511268000162.tif11131 is the ceiling function, TIFF2024511268000163.tif11131 is the floor function and mod( ) is a modular function.
[0255] A simpler, sub-optimal alternative is to use TIFF2024511268000164.tif13142PDCCH candidates and TIFF2024511268000165.tif11131 It is considered that the PDCCH candidate is used for PDCCH monitoring for a CSS set on a scheduling cell. Of the corresponding PDCCH candidates and non-overlapping CCEs for the scheduled cell, only the remaining PDCCH candidates and non-overlapping CCEs of each scheduled cell that are considered for the CSS set on the scheduled cell are used for the USS set of the scheduled cell.
[0256] In the third approach, the CSS set on the scheduled cell corresponds to the scheduled cell based on the “target cell” parameter of the CSS set configuration, which determines the cells that the UE can consider as PDCCH candidates and non-overlapping CCEs for the CSS set should be counted. For example, the UE may use additional criteria to determine the search space set prioritization rules. For example, a (CSS set or) USS set on a sSCell shared / linked with the primary cell has a higher priority level compared to a (CSS set or) USS set on a sSCell that is not shared with the primary cell.
[0257] FIG. 13 shows a structure of a UE according to an embodiment of the present invention. As shown in FIG. 13, a UE in one embodiment includes a transceiver 1310, a memory 1320, and a processor 1330. The UE's transceiver 1310, memory 1320, and processor 1330 operate in accordance with the UE's communication method as described above. However, the components of the UE are not limited to this. For example, a UE may include more or fewer components than those described above. Additionally, the processor 1330, the transceiver 1310, and the memory 1320 are implemented on a single chip. Also, the processor 1330 may include at least one processor. 13 corresponds to the UE in FIG.
[0258] The transceiver 1310 collectively refers to a UE receiver and a UE transmitter and transmits signals to and receives signals from a base station or network entity. Signals transmitted to and from a base station or network entity may include control information and data. The transceiver 1310 may include an RF transmitter that upconverts and amplifies the frequency of transmitted signals and an RF receiver that low-noise amplifies and downconverts the frequency of received signals. However, this is merely an example of the transceiver 1310, and the components of the transceiver 1310 are not limited to an RF transmitter and an RF receiver. The transceiver 1310 also receives signals via a wireless channel and outputs them to the processor 1330, and transmits signals output from the processor 1330 via a wireless channel.
[0259] The memory 1320 stores programs and data necessary for the operation of the UE. Memory 1320 also stores control information or data included in signals obtained by the UE. The memory 1320 may be a storage medium or a combination of storage media, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a hard disk, a CD-ROM, a DVD, etc. The processor 1330 controls a series of processes that cause the UE to operate as described above. For example, the transceiver 1310 may receive data signals including control signals transmitted by a base station or a network entity, and the processor 1330 may determine the results of receiving the control signals and data signals transmitted by the base station or network entity.
[0260] FIG. 14 is a diagram illustrating a structure of a base station according to an embodiment of the present invention. As shown in FIG. 14, the base station in one embodiment includes a transceiver 1410, a memory 1420, and a processor 1430. The base station transceiver 1410, memory 1420, and processor 1430 operate in accordance with the base station communication method previously described. However, the components of the base station are not limited to these. For example, a base station may include more or fewer components than those described above. Additionally, the processor 1430, the transceiver 1410, and the memory 1420 are implemented on a single chip. Also, the processor 1430 may include at least one processor. 14 corresponds to the BS in FIG.
[0261] The transceiver 1410 collectively refers to a base station receiver and a base station transmitter, and transmits and receives signals to and from a terminal (UE) or a network entity. Signals transmitted to and from a terminal or a network entity may include control information and data. The transceiver 1410 may include an RF transmitter that upconverts and amplifies the frequency of transmitted signals, and an RF receiver that low-noise amplifies and downconverts the frequency of received signals. However, this is merely an example of the transceiver 1410, and the components of the transceiver 1410 are not limited to an RF transmitter and an RF receiver. The transceiver 1410 also receives signals via a wireless channel and outputs them to the processor 1430, and transmits signals output from the processor 1430 via the wireless channel.
[0262] Memory 1420 stores programs and data necessary for the operation of the base station. Memory 1420 also stores control information or data contained in signals obtained by the base station. The memory 1420 may be a storage medium such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a hard disk, a CD-ROM, a DVD, or a combination of storage media. The processor 1430 controls a series of processes that cause the base station to operate as described above. For example, the transceiver 1410 receives data signals including control signals transmitted by the UE, and the processor 1430 determines the reception results of the control signals and data signals transmitted by the UE.
[0263] In one embodiment, a method is provided. A method for receiving a physical downlink control channel (PDCCH) includes receiving first information for a first search space set for scheduling for the first cell from a first cell and receiving second information for a second search space set for scheduling for the first cell from a second cell; determining a first number of PDCCH receptions via a first number of non-overlapping control channel elements (CCEs) on the first cell in a first slot based on the first search space set; identifying at least one of: the first number of PDCCH receptions exceeding a predetermined number of PDCCH receptions; and a first number of non-overlapping CCEs exceeding a predetermined number of non-overlapping CCEs; and canceling PDCCH receptions corresponding only to a third search space set in the first search space set.
[0264] In one embodiment, the method includes receiving information on a third resource for PUCCH transmission to provide HARQ-ACK information in response to a PDSCH reception associated with a third RNTI from a first set of RNTIs and scheduled by a downlink control information (DCI) format; determining a second resource from the third resource for the second PUCCH to provide second HARQ-ACK information and the third HARQ-ACK information in response to a first PDSCH reception associated with the third RNTI from the first RNTI set; and transmitting the second PUCCH together with the second and third HARQ-ACK information using the second resource. In one embodiment, the first cell is a primary cell and the second cell is a secondary cell, the second cell having an active downlink bandwidth portion (DL BWP) that is activated and not dormant (DL BWP).
[0265] In one embodiment, the predetermined number of PDCCH receptions is TIFF2024511268000166.tif14146, and the number of non-overlapping CCEs is TIFF2024511268000167.tif12146, where α is a scaling factor, TIFF2024511268000168.tif11146 and TIFF2024511268000169.tif10146 are the total number of PDCCH receptions and the total number of non-overlapping CCEs in slots on the first cell, respectively. TIFF2024511268000170.tif11146 and TIFF2024511268000171.tif11146 are the maximum number of PDCCH receptions and the maximum number of non-overlapping CCEs in a slot on the first cell, respectively, and μ1 is the subcarrier spacing setting for the slot of the first cell.
[0266] In one embodiment, the method further includes receiving information indicative of the scaling factor α. In one embodiment, the third search space set is a UE specific search space (USS) set. In one embodiment, the first search space set includes a common search space (CSS) set associated with a first downlink control information (DCI) format, the first DCI format including cyclic redundancy check (CRC) bits scrambled by a group radio network temporary identifier (G-RNTI), and the first DCI format schedules multicast physical downlink shared channel (PDSCH) reception in the first cell. In one embodiment, the method further includes receiving third information for a fourth search space set for scheduling for the first cell from the third cell, determining that the second cell has an active downlink bandwidth portion (DL BWP) that is deactivated or dormant (DL BWP), and receiving a PDCCH with the fourth search space set for scheduling for the first cell.
[0267] In one embodiment, a user equipment (UE) is provided. The UE includes a transceiver configured to receive first information for a first search space set for scheduling for the first cell from a first cell and to receive second information for a second search space set for scheduling for the first cell from a second cell; and a processor operatively coupled to the transceiver, configured to determine a first number of PDCCH receptions via a first number of non-overlapping control channel elements (CCEs) on the first cell in the first slot based on the first search space set, and to identify at least one of: the first number of PDCCH receptions exceed a predetermined number of PDCCH receptions, and the first number of non-overlapping CCEs exceed a predetermined number of non-overlapping CCEs, wherein the transceiver is further configured to cancel PDCCH receptions corresponding only to a third search space set in the first search space set.
[0268] In one embodiment, where the first cell is a primary cell and the second cell is a secondary cell, the second cell has an active downlink bandwidth part (DL BWP) that is activated and not dormant (DL BWP). In one embodiment, PDCCH reception in a first cell has a first subcarrier spacing (SCS) setting, PDCCH reception in a second cell has a second SCS setting, and the first slot is the slot corresponding to the smaller of the first SCS and the second SCS.
[0269] In one embodiment, the predetermined number of PDCCH receptions is TIFF2024511268000172.tif14146, and the number of non-overlapping CCEs is TIFF2024511268000173.tif12146, α is the scaling factor, TIFF2024511268000174.tif11146 and TIFF2024511268000175.tif10146 are the total number of PDCCH receptions and the total number of non-overlapping CCEs in slots on the first cell, respectively. TIFF2024511268000176.tif11146 and TIFF2024511268000177.tif11146 are the maximum number of PDCCH receptions and the maximum number of non-overlapping CCEs in a slot on the first cell, respectively, and μ1 is the subcarrier spacing setting for the slot of the first cell.
[0270] In one embodiment, the transceiver is further configured to receive information indicative of the scaling factor α. In one embodiment, the third search space set is a UE specific search space (USS) set. In one embodiment, the first search space set includes a common search space (CSS) set associated with a first downlink control information (DCI) format, the first DCI format including cyclic redundancy check (CRC) bits scrambled by a group radio network temporary identifier (G-RNTI), and the first DCI format schedules multicast physical downlink shared channel (PDSCH) reception in the first cell.
[0271] In one embodiment, the first search space set includes a common search space (CSS) set associated with a first downlink control information (DCI) format, the first DCI format including cyclic redundancy check (CRC) bits scrambled by a group radio network temporary identifier (G-RNTI), and the first DCI format schedules multicast physical downlink shared channel (PDSCH) reception in the first cell. In one embodiment, the transceiver is further configured to receive third information for a fourth search space set for scheduling on the first cell from the third cell, determine whether the second cell has an active downlink bandwidth portion (DL BWP) that is deactivated or dormant (DL BWP), and receive a PDCCH according to the fourth search space set for scheduling on the first cell.
[0272] In one embodiment, a base station is provided. The base station includes a transceiver configured to transmit first information for a first search space set for scheduling from a first cell to the first cell, transmit second information for a second search space set for scheduling from a second cell to the first cell, transmit a scaling factor α for scaling a maximum number of PDCCHs (physical downlink control channels) and a maximum number of non-overlapping CCEs on the first cell in a first slot based on the first search space set, and transmit the PDCCH on the first cell or the PDCCH on the second cell in the first slot. In one embodiment, the first cell is a primary cell and the second cell is a secondary cell, the second cell having an active downlink bandwidth portion (DL BWP) that is activated and not dormant (DL BWP).
[0273] In one embodiment, the PDCCH reception on the first cell has a first subcarrier spacing (SCS) setting, the PDCCH reception on the second cell has a second SCS setting, and the first slot is the slot corresponding to the smaller of the first SCS and the second SCS. In one embodiment, the first search space set includes a common search space (CSS) set associated with a first downlink control information (DCI) format, the first DCI format including cyclic redundancy check (CRC) bits scrambled by a group radio network temporary identifier (G-RNTI), and the first DCI format schedules multicast physical downlink shared channel (PDSCH) reception in the first cell.
[0274] The above flow charts illustrate exemplary methods that may be implemented in accordance with the principles of the present invention, and various changes and modifications may be made to the methods illustrated in the flow charts. For example, while shown in the figures as a series of steps, various steps in each figure may overlap, occur in parallel, occur in other orders, or occur multiple times. In other instances, steps may be omitted or substituted with other steps.
[0275] Methods according to the embodiments described in the claims or detailed description of the present invention may be implemented in hardware, software, or a combination of hardware and software. When the electrical structures and methods are implemented in software, a computer-readable storage medium may be provided that stores one or more programs (software modules). One or more programs stored on the computer-readable storage medium are configured to be executable by one or more processors within the electronic device. The one or more programs contain instructions to carry out a method according to an embodiment of the invention as claimed or described in the detailed description.
[0276] The programs (e.g., software modules, software) may be stored in random access memory (RAM), non-volatile memory including flash memory, Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), magnetic disk storage, Compact Disc-ROM (CD-ROM), Digital Versatile Disc (DVD), other types of optical storage, or a magnetic cassette. Alternatively, the program may be stored in a memory system including a combination of some or all of the memory devices mentioned above. Also, each memory device may be included in multiple units. The program may also be stored in an attachable storage device accessible via a communications network such as the Internet, an intranet, a local area network (LAN), a wide LAN (WAN), or a storage area network (SAN), or a combination thereof. A storage device may be associated with an apparatus according to an embodiment of the present invention via an external port. Other storage devices on the communications network may also be associated with the device performing embodiments of the present invention.
[0277] In the above-described embodiments of the present invention, elements included in the present invention are expressed as singular or plural depending on the embodiment. However, for convenience of explanation, the singular or plural form is appropriately selected, and the present invention is not limited thereto. In this manner, elements expressed in the plural form may be set as a single element, and elements expressed in the singular form may be set as a plural element. Although the drawings show various examples of user terminals, various variations of the drawings are possible. For example, a user terminal may include any number of each component in any suitable arrangement. In general, the drawings do not limit the scope of the invention to any particular configuration or configurations. Moreover, although the drawings illustrate exemplary operating environments in which various user terminal features disclosed in this patent document may be used, such features may be used in any other suitable system.
[0278] Although the present invention has been described in exemplary embodiments, various changes and modifications may be suggested to those skilled in the art. It is intended that the present invention encompass such changes and modifications as fall within the scope of the appended claims. Nothing in the application should be construed as indicating any particular element, step or function as an essential element for inclusion in the claims. The scope of patented subject matter is defined by the claims. [Explanation of symbols]
[0279] 100 Wireless Network 101~103 Base station (BS) 111~116 User Equipment (UE) 120, 125 coverage area 130 Network 205a~ 205n, 305 antenna 210a~ 210n, 310 RF Transceiver 215, 315 Transmit (TX) processing circuit 220, 325 Receiver (RX) processing circuit 225, 340 Controller / Processor 230, 360 Memory 235 (Backhaul / ) Network Interface 330 Speaker 345 Input / Output (I / O) Interface (IF) 350 Input Device 355 Display 361 Operating System (OS) 362 Applications 405 Channel Coding and Modulation Block 410 Series-to-Parallel (S-to-P) Block 415 Size N Inverse Fast Fourier Transform Blocks 420 Parallel-Series (P-to-S) Block 425 Additional Cyclic Prefix Block 430 Upconverter 555 Down Converter 560 Remove Cyclic Prefix Block 565 Series-Parallel (S-to-P) Block 570 Size N Fast Fourier Transform Blocks 580 Channel Decoding and Demodulation Block
Claims
1. A method performed by a terminal (user equipment) in a wireless communication system, comprising: receiving setting information for an α value from a base station; receiving information for configuring scheduling from a primary cell to the primary cell and scheduling from a secondary cell to the primary cell from the base station; monitoring a physical downlink control channel (PDCCH) candidate for scheduling to the primary cell from the primary cell; The number of monitored PDCCH candidates per slot does not exceed a first value, The number of non-overlapping control channel elements (CCEs) monitored per slot does not exceed a second value, For the first value, the α value is multiplied by a minimum value between a maximum number of PDCCH candidates in a slot for a first subcarrier spacing (SCS) and a total number of PDCCH candidates in a slot for the first SCS; For the second value, the α value is multiplied by a minimum value between a maximum number of non-overlapping CCEs in a slot for the first SCS and a total number of non-overlapping CCEs per slot for the first SCS.
2. The method of claim 1, wherein the first SCS for the primary cell is less than or equal to the second SCS for the secondary cell.
3. The first value is Including, The second value is Including, includes a total number of PDCCH candidates in the slot on the primary cell, comprises a total number of non-overlapping CCEs in the slot on the primary cell, includes a maximum number of PDCCH candidates in the slot on the primary cell, contains the maximum number of non-overlapping CCEs in the slot on the primary cell, 2. The method of claim 1, wherein μ1 is the first SCS for a slot of the primary cell.
4. A terminal (user equipment) in a wireless communication system, A transceiver; a controller coupled to the transceiver; The controller: receiving setting information for an α value from a base station; receiving information for configuring scheduling for the primary cell from a primary cell and scheduling for the primary cell from a secondary cell from the base station; The PDCCH is configured to monitor a physical downlink control channel (PDCCH) candidate for scheduling from the primary cell to the primary cell; The number of monitored PDCCH candidates per slot does not exceed a first value, The number of non-overlapping control channel elements (CCEs) monitored per slot does not exceed a second value, For the first value, the α value is multiplied by a minimum value between a maximum number of PDCCH candidates in a slot for a first subcarrier spacing (SCS) and a total number of PDCCH candidates in a slot for the first SCS; For the second value, the α value is multiplied by the minimum value between the maximum number of non-overlapping CCEs in a slot for the first SCS and the total number of non-overlapping CCEs per slot for the first SCS.
5. The terminal described in Claim 4, characterized in that the first SCS for the primary cell is equal to or less than the second SCS for the secondary cell.
6. The first value is Including, The second value is Including, includes a total number of PDCCH candidates in the slot on the primary cell, comprises a total number of non-overlapping CCEs in the slot on the primary cell, includes a maximum number of PDCCH candidates in the slot on the primary cell, contains the maximum number of non-overlapping CCEs in the slot on the primary cell, The terminal of claim 4, wherein μ1 is the first SCS for a slot of the primary cell.
7. A method performed by a base station in a wireless communication system, comprising: transmitting configuration information for the α value to a terminal (user equipment: UE); transmitting, to the terminal, information for configuring scheduling from a primary cell to the primary cell and scheduling from a secondary cell to the primary cell; the number of PDCCH candidates per slot for scheduling from the primary cell to the primary cell does not exceed a first value; The number of non-overlapping control channel elements (CCEs) per slot for scheduling from the primary cell to the primary cell does not exceed a second value; For the first value, the α value is multiplied by a minimum value between a maximum number of PDCCH candidates in a slot for a first subcarrier spacing (SCS) and a total number of PDCCH candidates in a slot for the first SCS; For the second value, the α value is multiplied by a minimum value between a maximum number of non-overlapping CCEs in a slot for the first SCS and a total number of non-overlapping CCEs per slot for the first SCS.
8. The method of claim 7, wherein the first SCS for the primary cell is less than or equal to the second SCS for the secondary cell.
9. The first value is Including, The second value is Including, includes a total number of PDCCH candidates in the slot on the primary cell, comprises a total number of non-overlapping CCEs in the slot on the primary cell, includes a maximum number of PDCCH candidates in the slot on the primary cell, contains the maximum number of non-overlapping CCEs in the slot on the primary cell, 8. The method of claim 7, wherein μ1 is the first SCS for a slot of the primary cell.
10. A base station in a wireless communication system, comprising: A transceiver; a controller coupled to the transceiver; The controller: Transmitting configuration information for the α value to a terminal (user equipment: UE); The terminal is configured to transmit information for configuring scheduling from a primary cell to the primary cell and scheduling from a secondary cell to the primary cell, The number of physical downlink control channel (PDCCH) candidates per slot for scheduling from the primary cell to the primary cell does not exceed a first value; The number of non-overlapping control channel elements (CCEs) per slot for scheduling from the primary cell to the primary cell does not exceed a second value; For the first value, the α value is multiplied by a minimum value between a maximum number of PDCCH candidates in a slot for a first subcarrier spacing (SCS) and a total number of PDCCH candidates in a slot for the first SCS; The base station is characterized in that, for the second value, the α value is multiplied by a minimum value between a maximum number of non-overlapping CCEs in a slot for the first SCS and a total number of non-overlapping CCEs per slot for the first SCS.
11. The base station of claim 10, wherein the first SCS for the primary cell is equal to or less than the second SCS for the secondary cell.
12. The first value is Including, The second value is Including, includes a total number of PDCCH candidates in the slot on the primary cell, comprises a total number of non-overlapping CCEs in the slot on the primary cell, includes a maximum number of PDCCH candidates in the slot on the primary cell, contains the maximum number of non-overlapping CCEs in the slot on the primary cell, The base station of claim 10, wherein μ1 is the first SCS for a slot of the primary cell.