Method and apparatus for PDCCH monitoring for multi-cell scheduling

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method includes receiving information of a plurality of cell sets and information of a user equipment (UE)-specific search space (USS) set for receiving PDCCH candidates on a scheduling cell. The USS set has a USS set identification and is associated with a downlink control information (DCI) format for scheduling over more than one cell. The method further includes determining a set of cells from the plurality of sets of cells associated with the USS set and a reference cell from the set of cells. The size of the DCI format is counted among a plurality of sizes of the DCI format for scheduling on the reference cell, and is not counted among a plurality of sizes of the DCI format for scheduling on cells other than the reference cell from the set of cells.

Description

Technical Field

[0001] The present disclosure relates to wireless communication systems. More particularly, the present disclosure relates to physical downlink control channel (PDCCH) monitoring for multi-cell scheduling. Background Art

[0002] 5G mobile communication technology defines a wide frequency band so that high transmission rates and new services are possible, and can be realized not only in "below 6 GHz" frequency bands such as 3.5 GHz, but also in "above 6 GHz" frequency bands called millimeter waves (mmWave) including 28 GHz and 39 GHz. In addition, it has been considered to implement 6G mobile communication technology (called super 5G system) in terahertz (THz) frequency bands (e.g., 95 GHz to 3 THz frequency bands) in order to achieve a transmission rate fifty times faster than 5G mobile communication technology and an ultra-low latency one-tenth of 5G mobile communication technology.

[0003] At the beginning of the development of 5G mobile communication technology, in order to support services and meet performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC) and massive machine-type communication (mMTC), there is ongoing standardization on the following items: beamforming and massive MIMO for mitigating radio wave path loss and increasing radio wave transmission distance in millimeter waves, parameter sets supporting dynamic operations for efficient utilization of millimeter wave resources and time slot formats (e.g., operating multiple subcarrier spacings), initial access technology for supporting multi-beam transmission and broadband, definition and operation of BWP (bandwidth part), new channel coding methods (such as LDPC (low-density parity check) codes for large-scale data transmission and polar codes for highly reliable transmission of control information), L2 preprocessing, and network slicing for providing dedicated networks dedicated to specific services.

[0004] Currently, in view of the services to be supported by 5G mobile communication technology, discussions are ongoing on improvements and performance enhancements of initial 5G mobile communication technology, and there is already physical layer standardization on technologies such as the following: V2X (Vehicle to Everything), for assisting driving determination of autonomous vehicles based on information about the location and status of the vehicle sent by the vehicle and for enhancing user convenience; NR-U (New Radio Unlicensed), for system operation that is intended to comply with various regulatory-related requirements in unlicensed bands; NR UE power saving; Non-Terrestrial Network (NTN), which is UE satellite direct communication for providing coverage in areas where communication with terrestrial networks is unavailable; and positioning.

[0005] In addition, in the air interface architecture / protocol, there is already ongoing standardization on technologies such as the Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner, mobility enhancements including conditional switching and DAPS (Dual Active Protocol Stack) switching, and two-step random access (two-step RACH for NR) for simplifying the random access procedure. There is also ongoing standardization on a 5G baseline architecture (e.g., a service-based architecture or service-based interface) for combining network function virtualization (NFV) and software defined network (SDN) technologies, and a system architecture / service for mobile edge computing (MEC) for receiving services based on UE location.

[0006] With the commercialization of 5G mobile communication systems, the already exponentially growing number of connected devices will be connected to the communication network, and it is accordingly expected that enhanced functions and performance of the 5G mobile communication system and integrated operations of the connected devices will be necessary. To this end, new research related to extended reality (XR) is arranged to effectively support AR (augmented reality), VR (virtual reality), MR (mixed reality), etc., to improve 5G performance and reduce complexity by utilizing artificial intelligence (AI) and machine learning (ML), AI service support, meta-service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a foundation for developing not only new waveforms for providing coverage in the terahertz band for 6G mobile communication technology, multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas, and massive antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional spatial multiplexing technology using OAM (orbital angular momentum), and RIS (reconfigurable smart surface), but also full-duplex technology for improving the frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technology for achieving system optimization by utilizing satellites and AI (artificial intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for achieving services at a complexity level that exceeds the operational capability limits of UEs by utilizing ultra-high performance communication and computing resources. Summary of the invention

[0008] Technical issues

[0009] Currently, there is a need to enhance multi-cell scheduling in wireless communication systems.

[0010] Solution to the problem

[0011] The present disclosure relates to an apparatus and method for PDCCH monitoring for multi-cell scheduling.

[0012] In one embodiment, a method includes receiving first information of multiple cell sets and second information of a first user equipment (UE) specific search space (USS) set for receiving a first physical downlink control channel (PDCCH) candidate on a scheduling cell, wherein the first USS set has a first USS set identifier and is associated with a first downlink control information (DCI) format for scheduling on more than one cell; and determining a first cell set associated with the first USS set from the multiple cell sets and a first reference cell from the first cell set, wherein a first size of the first DCI format is counted in multiple sizes of DCI formats for scheduling on the first reference cell and is not counted in multiple sizes of DCI formats for scheduling on cells other than the first reference cell from the first cell set, and wherein, when the scheduling cell is included in the first cell set and the first USS set is the only USS set with the first USS identifier among USS sets on cells in the first cell set, the first reference cell is the scheduling cell.

[0013] In another embodiment, a user equipment (UE) is provided. The user equipment includes a transceiver configured to receive first information of multiple cell sets and second information of a first USS set for receiving a first PDCCH candidate on a scheduling cell. The first USS set has a first USS set identifier and is associated with a first DCI format for scheduling on more than one cell. The UE also includes a processor operably connected to the transceiver. The processor is configured to determine a first cell set associated with a first USS set in multiple cell sets and a first reference cell in the first cell set. The first size of the first DCI format is counted in multiple sizes of a DCI format for scheduling on a first reference cell, and is not counted in multiple sizes of a DCI format for scheduling on a cell other than the first reference cell in the first cell set. When the scheduling cell is included in the first cell set and the first USS set is the only USS set with a first USS identifier among the USS sets on the cells in the first cell set, the first reference cell is the scheduling cell.

[0014] In yet another embodiment, a base station is provided. The base station includes a transceiver configured to send first information of multiple cell sets and second information of a first USS set for sending a first PDCCH on a scheduling cell. The first USS set has a first USS set identifier and is associated with a first DCI format for scheduling on more than one cell. The BS includes a processor operably connected to the transceiver. The processor is configured to determine a first cell set associated with a first USS set in multiple cell sets and a reference cell in the first cell set. The first size of the first DCI format is counted in multiple sizes of a DCI format for scheduling on a reference cell and is not counted in multiple sizes of a DCI format for scheduling on a cell other than the reference cell in the first cell set. When the scheduling cell is included in the first cell set and the first USS set is the only USS set with a first USS identifier among the USS sets on the cells in the first cell set, the reference cell is the scheduling cell.

[0015] Other technical features may be apparent to those skilled in the art from the following drawings, description and appended claims.

[0016] Before the following detailed description, it may be advantageous to set forth the definitions of certain words and phrases used throughout this patent document. The term "coupling" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not these elements are in physical contact with each other. The terms "send", "receive" and "communication" and their derivatives cover both direct and indirect communication. The terms "include" and "comprise" and their derivatives mean including but not limited to. The term "or" is inclusive, meaning and / or. The phrase "associated with ... " and its derivatives mean including, included in ..., interconnected with ..., including, included in ..., connected to or connected with ..., coupled to or coupled with ..., can communicate with ..., collaborate with ..., interlace, juxtapose, be close to, be bound to or bound with ..., have, have the nature of ..., have to or with ... relationship, etc. The term "controller" means any device, system or part thereof that controls at least one operation. Such a controller can be implemented in hardware or a combination of hardware and software and / or firmware. The function associated with any particular controller can be centralized or distributed, whether local or remote. When used with a list of items, the phrase "at least one of" means that different combinations of one or more of the listed items can be used, and only one of the items in the list may be required. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.

[0017] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" indicate one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data or a portion thereof suitable for implementation in a suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disk (CD), a digital video disc (DVD) or any other type of memory. "Non-transitory" computer-readable media excludes wired, wireless, optical or other communication links that transmit temporary electrical signals or other signals. Non-transitory computer-readable media include media that can permanently store data and media that can store data and rewrite it later, such as rewritable optical disks or erasable memory devices.

[0018] Definitions for certain other words and phrases are provided throughout this patent document. Those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.

[0019] Advantageous Effects of the Invention

[0020] According to various embodiments of the present disclosure, it is possible to effectively enhance UE and process handover in a wireless communication system. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, wherein like reference numerals represent like parts:

[0022] Figure 1 illustrates an example wireless network according to an embodiment of the present disclosure;

[0023] Figure 2 An example gNodeB (gNB) according to an embodiment of the present disclosure is shown;

[0024] Figure 3 An example user equipment (UE) according to an embodiment of the present disclosure is shown;

[0025] Figure 4 illustrates example wireless transmit and receive paths according to an embodiment of the present disclosure;

[0026] Figure 5 illustrates example wireless transmit and receive paths according to an embodiment of the present disclosure;

[0027] Figure 6 An example transmitter structure using orthogonal frequency division multiplexing (OFDM) according to an embodiment of the present disclosure is shown;

[0028] Figure 7 shows an example receiver structure using OFDM according to an embodiment of the present disclosure;

[0029] Figure 8 An example encoding process for a downlink control information (DCI) format according to an embodiment of the present disclosure is shown;

[0030] Fig. 9 An example decoding process for a DCI format according to an embodiment of the present disclosure is shown;

[0031] Fig.10 An example method for distinguishing a multi-cell scheduling DCI format from a single-cell scheduling DCI format according to an embodiment of the present disclosure is shown;

[0032] Fig.11 An example method for monitoring a PDCCH in a set of search spaces for multi-cell scheduling according to an embodiment of the present disclosure is shown;

[0033] Fig.12 An example method for search space linking for multi-cell scheduling according to an embodiment of the present disclosure is shown;

[0034] Fig.13 An example method for counting PDCCH candidates for multi-cell scheduling operation when a search space set is associated with a multi-cell scheduling DCI format according to an embodiment of the present disclosure is shown;

[0035] Fig.14 An example method for counting PDCCH candidates for multi-cell scheduling operation when a search space set is configured for both single-cell scheduling and multi-cell scheduling DCI formats according to an embodiment of the present disclosure is shown;

[0036] Fig.15 An example method of overbooking and dropping a search space set for multi-cell scheduling operation according to an embodiment of the present disclosure is shown; and

[0037] Fig.16 An example method of search space set oversubscription and dropping for multi-cell scheduling operation when the search space set is additionally configured with a priority level parameter according to an embodiment of the present disclosure is shown.

[0038] Fig.17 A block diagram of a terminal (or user equipment (UE)) according to an embodiment of the present disclosure is shown.

[0039] Fig.18 A block diagram of a base station according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0040] Fifth generation (5G) or New Radio (NR) mobile communications are gathering increasing momentum recently with all the global technical activities from industry and academia regarding various candidate technologies. Candidate enabling factors for 5G / NR mobile communications include massive antenna technology from traditional cellular bands up to high frequencies to provide beamforming gain and support increased capacity, new waveforms (e.g., new radio access technologies (RATs)) to flexibly accommodate various services / applications with different requirements, new multiple access schemes to support massive connectivity, etc.

[0041] Discussed below Figures 1 to 16 The various embodiments used to describe the principles of the present disclosure in this patent document are for illustration only and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will appreciate that the principles of the present disclosure can be implemented in any appropriately arranged system or device.

[0042] The following documents and standard descriptions are incorporated by reference into the present disclosure as if fully set forth herein: 3GPP TS 38.211 v17.2.0, “NR; Physical channels and modulation;” 3GPP TS 38.212 v17.2.0, “E-UTRA, NR,” Multiplexing and Channel coding; 3GPP TS 38.213 v17.2.0; “NR, Physical Layer Procedures for Control”; 3GPP TS 38.214 v17.2.0; “NR, Physical Layer Procedures for Data”; 3GPP TS 38.321 v17.1.0, “NR; Medium Access Control (MAC) protocol specification”; 3GPP TS 38.331 v17.1.0, “NR; Radio Resource Control (RRC) Protocol Specification;” 3GPP TS 38.300v17.1.0, "NR; NR and NG-RAN OverallDescription; Stage 2;" 3GPP TR 38.306v17.1.0, "NR; User Equipment (UE) radio accesscapabilities".

[0043] Wireless communication has been one of the most successful innovations in modern history. Recently, the number of subscribers to wireless communication services exceeded 5 billion and continues to grow rapidly. Due to the increasing popularity of smartphones and other mobile data devices (such as tablets, "notepad" computers, netbooks, e-book readers and machine-type devices) among consumers and enterprises, the demand for wireless data services is increasing rapidly. In order to meet the high growth of mobile data services and support new applications and deployments, improvements in radio interface efficiency and coverage are critical.

[0044] In order to meet the demand for wireless data services that have increased since the deployment of 4G communication systems and to realize various vertical applications, 5G / NR communication systems have been developed and are currently being deployed. 5G / NR communication systems are considered to be implemented in higher frequency (millimeter wave) bands (e.g., 28 GHz or 60 GHz bands) to achieve higher data rates, or in lower frequency bands (such as 6 GHz) to achieve robust coverage and mobility support. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology are discussed in 5G / NR communication systems.

[0045] In addition, in the 5G / NR communication system, system network improvements are being developed based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, collaborative communications, coordinated multi-point (CoMP), and receiving-end interference cancellation.

[0046] The discussion of 5G systems and frequency bands associated therewith is for reference because certain embodiments of the present disclosure may be implemented in 5G systems. However, the present disclosure is not limited to 5G systems or frequency bands associated therewith, and embodiments of the present disclosure may be utilized in conjunction with any frequency band. For example, aspects of the present disclosure may also be applied to 5G communication systems, 6G, or even later deployments that may use terahertz (THz) frequency bands.

[0047] The following Figure 1-Figure 3 Various embodiments are described that may be implemented using Orthogonal Frequency Division Multiplexing (OFDM) or Orthogonal Frequency Division Multiple Access (OFDMA) communication techniques in a wireless communication system. Figure 1-Figure 3 The description is not meant to imply physical or architectural limitations to the manner in which different embodiments may be implemented. Different embodiments of the present disclosure may be implemented in any suitably arranged communications system.

[0048] Figure 1 An example wireless network 100 is shown in accordance with the present disclosure. Figure 1The embodiment of the wireless network 100 shown in FIG. 1 is for illustration only. Other embodiments of the wireless network 100 can be used without departing from the scope of the present disclosure.

[0049] Wireless network 100 includes gNodeB (gNB) 101, gNB 102, and gNB 103. gNB 101 communicates with gNB 102 and gNB 103. gNB 101 also communicates with at least one Internet Protocol (IP) network 130, such as the Internet, a private IP network, or other data network.

[0050] Depending on the type of network, other well-known terms may be used instead of "gNodeB" or "gNB", such as "base station" or "access point". For convenience, the terms "gNodeB" and "gNB" are used in this patent document to indicate network infrastructure components that provide wireless access to remote terminals. In addition, depending on the type of network, other well-known terms may be used instead of "user equipment" or "UE", such as "mobile station", "subscriber station", "remote terminal", "wireless terminal" or "user device". For convenience, the terms "user equipment" and "UE" are used in this patent document to indicate a remote wireless device that wirelessly accesses a gNB, whether the UE is a mobile device (such as a mobile phone or smartphone) or is generally considered to be a fixed device (such as a desktop computer or vending machine). The UE may also be a car, truck, van, drone, or any similar machine or a device in such a machine.

[0051] gNB 102 provides wireless broadband access to network 130 for a first plurality of user equipment (UE) within coverage area 120 of gNB 102. The first plurality of UEs includes UE 111, which may be located in a small business (SB); UE 112, which may be located in an enterprise (E); UE 113, which may be located in a WiFi hotspot (HS); UE 114, which may be located in a first residence (R); UE 115, which may be located in a second residence (R); and UE 116, which may be a mobile device (M) such as a cellular phone, a wireless laptop computer, a wireless PDA, etc. gNB 103 provides wireless broadband access to network 130 for a second plurality of UEs within coverage area 125 of gNB 103. The second plurality of UEs includes UE 115, UE 116, UE 117, and UE 118. In some embodiments, one or more of gNBs 101-103 may communicate with each other and with UEs 111-118 using 5G, Long Term Evolution (LTE), LTE-A, WiMAX, or other advanced wireless communication technologies. In some embodiments, multiple UEs (e.g., UE 117, UE 118, and UE 119) may communicate directly with each other via device-to-device communication. In some embodiments, a UE (e.g., UE 119) is outside the coverage area of ​​the network, but may communicate with other UEs (e.g., UE 118) within or outside the coverage area of ​​the network.

[0052] The dashed lines illustrate the approximate extents of coverage areas 120 and 125, which are shown as approximately circular for purposes of illustration and explanation only. It should be clearly understood that coverage areas associated with a gNB, such as coverage areas 120 and 125, may have other shapes, including irregular shapes, depending on the configuration of the gNB and variations in the radio environment associated with natural and man-made obstacles.

[0053] As described in more detail below, one or more of BS101, BS102, and BS103 include a 2D antenna array as described in embodiments of the present disclosure. In some embodiments, one or more of BS101, BS102, and BS103 supports codebook design and structure for systems with 2D antenna arrays.

[0054] although Figure 1 An example of a wireless network 100 is shown, but may be Figure 1Various changes may be made. For example, wireless network 100 can include any number of gNBs and any number of UEs in any suitable arrangement. In addition, gNB 101 can communicate directly with any number of UEs and provide those UEs with wireless broadband access to network 130. Similarly, each gNB 102-103 can communicate directly with network 130 and provide UEs with direct wireless broadband access to network 130. In addition, gNBs 101, 102, and / or 103 can provide access to other or additional external networks, such as an external telephone network or other type of data network.

[0055] As described in more detail below, one or more of the UEs 111-116 include circuitry, programming, or a combination thereof for supporting PDCCH monitoring for multi-cell scheduling. In certain embodiments, one or more of the gNBs 101-103 include circuitry, programming, or a combination thereof for supporting PDCCH monitoring for multi-cell scheduling.

[0056] Figure 2 An example gNB 102 according to the present disclosure is shown. Figure 2 The embodiment of the gNB 102 shown in FIG. is for illustration only, and Figure 1 Other gNBs may have the same or similar configuration. However, gNBs have a variety of configurations, and Figure 2 The scope of the present disclosure is not limited to any particular implementation of the gNB. Note that gNB 101 and gNB 103 may include the same or similar structure as gNB 102.

[0057] like Figure 2 As shown, the gNB 102 includes multiple antennas 205a-205n, multiple transceivers 210a-210n, a controller / processor 225, a memory 230, and a backhaul or network interface 235.

[0058] The transceivers 210a-210n receive incoming RF signals from the antennas 205a-205n, such as signals transmitted by UEs in the network 100. The transceivers 210a-210n downconvert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are processed by receive (RX) processing circuits in the transceivers 210a-210n and / or the controller / processor 225, which generate processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. The controller / processor 225 may further process the baseband signals.

[0059] Transmit (TX) processing circuitry in the transceivers 210a-210n and / or the controller / processor 225 receives analog or digital data (such as voice data, web data, email, or interactive video game data) from the controller / processor 225. The TX processing circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to generate processed baseband or IF signals. The transceivers 210a-210n up-convert the baseband or IF signals to RF signals that are transmitted via the antennas 205a-205n.

[0060] The controller / processor 225 may include one or more processors or other processing devices that control the overall operation of the gNB 102. For example, the controller / processor 225 may control the reception of UL channel signals and the transmission of DL channel signals by the transceivers 210a-210n in accordance with well-known principles. The controller / processor 225 may also support additional functionality, such as more advanced wireless communication functionality. For example, the controller / processor 225 may support beamforming or directional routing operations, in which outgoing / incoming signals from / to multiple antennas 205a-205n are weighted differently to effectively steer the outgoing signals in a desired direction. As another example, the controller / processor 225 may support methods for PDCCH monitoring for multi-cell scheduling. Any of a variety of other functions may be supported by the controller / processor 225 in the gNB 102.

[0061] Controller / processor 225 may also execute programs and other processes, such as an OS, that reside in memory 230. Controller / processor 225 may move data into or out of memory 230 as required by the executing process.

[0062] The controller / processor 225 is also coupled to a backhaul or network interface 235. The backhaul or network interface 235 allows the gNB 102 to communicate with other devices or systems via a backhaul connection or via a network. The interface 235 is capable of supporting communication via any suitable wired or wireless connection (or multiple). For example, when the gNB 102 is implemented as part of a cellular communication system (such as a cellular communication system supporting 5G / NR, LTE, or LTE-A), the interface 235 may allow the gNB 102 to communicate with other gNBs via a wired or wireless backhaul connection. When the gNB 102 is implemented as an access point, the interface 235 may allow the gNB 102 to communicate via a wired or wireless local area network or via a wired or wireless connection to a larger network (such as the Internet). The interface 235 includes any suitable structure that supports communication via a wired or wireless connection, such as Ethernet or a transceiver.

[0063] Memory 230 is coupled to controller / processor 225. A portion of memory 230 may include RAM, and another portion of memory 230 may include flash memory or other ROM.

[0064] although Figure 2 An example of gNB 102 is shown, but the Figure 2 For example, gNB 102 may include any number of Figure 2 In addition, Figure 2 The various components in can be combined, further subdivided, or omitted, and additional components can be added according to specific needs.

[0065] Figure 3 An example UE 116 is shown in accordance with an embodiment of the present disclosure. Figure 3 The embodiment of UE 116 shown in FIG. 1 is for illustration only, and Figure 1 UEs 111-115 can have the same or similar configurations. However, UEs have a variety of configurations, and Figure 3 The scope of the present disclosure is not limited to any particular implementation of the UE.

[0066] like Figure 3 As shown, UE 116 includes antenna 305, transceiver 310, and microphone 320. UE 116 also includes speaker 330, processor 340, input / output (I / O) interface (IF) 345, input 350, display 355, and memory 360. Memory 360 includes operating system (OS) 361 and one or more applications 362.

[0067] Transceiver 310 receives incoming RF signals from antenna 305 transmitted by a gNB of network 100. Transceiver 310 downconverts the incoming RF signals to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is processed by RX processing circuitry in transceiver 310 and / or processor 340, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. The RX processing circuitry transmits the processed baseband signal to speaker 330 (such as for voice data) or is processed by processor 340 (such as for web browsing data).

[0068] The TX processing circuitry in the transceiver 310 and / or processor 340 receives analog or digital voice data from the microphone 320 or other outgoing baseband data (such as web data, email, or interactive video game data) from the processor 340. The TX processing circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The transceiver 310 up-converts the baseband or IF signal to an RF signal that is transmitted via the antenna 305.

[0069] The processor 340 may include one or more processors or other processing devices and execute the OS 361 stored in the memory 360 to control the overall operation of the UE 116. For example, the processor 340 may control the reception of DL channel signals and the transmission of UL channel signals by the transceiver 310 according to well-known principles. In some embodiments, the processor 340 includes at least one microprocessor or microcontroller.

[0070] The processor 340 may also execute other processes and programs resident in the memory 360, such as processes for supporting PDCCH monitoring for multi-cell scheduling. The processor 340 may move data into or out of the memory 360 as required by the executed processes. In some embodiments, the processor 340 is configured to execute the application 362 based on the OS 361 or in response to a signal received from the gNB or operator. The processor 340 is also coupled to the I / O interface 345, which provides the UE 116 with the ability to connect to other devices such as laptops and handheld computers. The I / O interface 345 is the communication path between these accessories and the processor 340.

[0071] Processor 340 is also coupled to input 350 (which includes, for example, a touch screen, keyboard, etc.) and display 355. An operator of UE 116 can use input 350 to enter data into UE 116. Display 355 may be a liquid crystal display, light emitting diode display, or other display that can render text and / or at least limited graphics (such as from a website).

[0072] Memory 360 is coupled to processor 340. A portion of memory 360 may include random access memory (RAM), and another portion of memory 360 may include flash memory or other read-only memory (ROM).

[0073] although Figure 3 An example of UE 116 is shown, but the Figure 3 Make various changes. For example, Figure 3 The various components in can be combined, further subdivided, or omitted, and additional components can be added as required. As a specific example, processor 340 can be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). In another example, transceiver 310 can include any number of transceivers and signal processing chains and can be connected to any number of antennas. In addition, although Figure 3 The UE 116 is shown configured as a mobile phone or smart phone, but the UE can be configured to operate as other types of mobile or stationary devices.

[0074] Figure 4 and Figure 5 An example wireless transmission and reception path according to the present disclosure is shown. In the following description, Figure 4 The transmission path 400 of may be described as being implemented in a gNB (such as gNB 102), while Figure 5 The receive path 500 may be described as being implemented in a UE, such as UE 116. However, it will be appreciated that the receive path 500 may be implemented in a gNB and the transmit path 400 may be implemented in a UE. Furthermore, it will be appreciated that in the case of device-to-device communication, the receive path 500 may be implemented in one UE and the transmit path 400 may be implemented in another UE. In some embodiments, the receive path 500 is configured to support PDCCH monitoring for multi-cell scheduling as described in embodiments of the present disclosure.

[0075] like Figure 4 The transmit path 400 shown 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 upconverter (UC) 430. Figure 5 The receive path 500 shown includes a downconverter (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.

[0076] like Figure 4 As shown, the channel coding and modulation block 405 receives a set of information bits, applies coding (such as low density parity check (LDPC) coding), and modulates the input bits (such as using quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM)) to generate a sequence of frequency domain modulation symbols. The serial to parallel block 410 converts (such as demultiplexes) the serial modulation symbols into parallel data to generate N parallel symbol streams, where N is the IFFT / FFT size used in the gNB 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. The parallel to serial block 420 converts (such as 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. The up converter 430 modulates (such as upconverts) the output of the add cyclic prefix block 425 to an RF frequency for transmission via a wireless channel. The signal may also be filtered at baseband before conversion to RF frequency.

[0077] The RF signal transmitted from gNB 102 reaches UE 116 after passing through the wireless channel, and operations opposite to those at gNB 102 are performed at UE 116.

[0078] like Figure 5 As shown, the down converter 555 down-converts the received signal to the baseband frequency, and the cyclic prefix removal 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 FFT block 570 of size N 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 sequence of modulated data symbols. The channel decoding and demodulation block 580 demodulates and decodes the modulation symbols to recover the original input data stream.

[0079] Each of gNBs 101-103 may implement Figure 4 The transmission path 400 shown is similar to the transmission to UE 111-116 in the downlink, and can be implemented as follows: Figure 5 Receive path 500 is shown, which is similar to receiving from UE 111-116 in the uplink. Similarly, each of UE 111-116 can implement transmit path 400 for transmitting to BS 101-103 in the uplink and can implement receive path 500 for receiving from gNB 101-103 in the downlink.

[0080] Figure 4 and Figure 5 Each component in may be implemented using hardware or a combination of hardware and software / firmware. As a specific example, Figure 4 and Figure 5 At least some components in can be implemented in software, while other components can be implemented by configurable hardware or a mixture of software and configurable hardware. For example, FFT block 570 and IFFT block 415 can be implemented as configurable software algorithms, wherein the value of size N can be modified according to the implementation.

[0081] In addition, although described as using FFT and IFFT, this is for illustration only and should not be construed as limiting the scope of the present disclosure. Other types of transforms can be used, such as discrete Fourier transform (DFT) and inverse discrete Fourier transform (IDFT) functions. It will be appreciated that for DFT and IDFT functions, the value of variable N can be any integer (such as 1, 2, 3, 4, etc.), while for FFT and IFFT functions, the value of variable N can be any integer that is a power of two (such as 1, 2, 4, 8, 16, etc.).

[0082] although Figure 4 and Figure 5An example of a wireless transmit and receive path is shown, but the Figure 4 and Figure 5 Make various changes. For example, Figure 4 and Figure 5 The various components in may be combined, further subdivided, or omitted, and additional components may be added according to specific needs. Figure 4 and Figure 5 It is intended to illustrate examples of the types of transmit and receive paths that can be used in a wireless network. Any other suitable architecture can be used to support wireless communications in a wireless network.

[0083] Either DL transmission or UL transmission may be based on an OFDM waveform including a variation using DFT precoding, known as DFT-spread-OFDM, which is typically applicable to UL transmission.

[0084] In the following, a subframe (SF) refers to a transmission time unit of an LTE RAT, and a slot refers to a transmission time unit of an NR RAT. For example, the slot duration may be a multiple of the SF duration. NR may use a DL or UL slot structure that is different from the LTE SF structure. The differences may include a structure for sending a physical downlink control channel (PDCCH), a location and structure of a demodulation reference signal (DM-RS), a transmission duration, and the like. In addition, an eNB refers to a base station serving a UE operating with an LTE RAT, and a gNB refers to a base station serving a UE operating with an NR RAT. An exemplary embodiment considers the same parameter set for transmission with an LTE RAT and with an NR RAT, including a cyclic prefix (CP) length and a subcarrier spacing (SCS) configuration of an OFDM symbol. In this case, the OFDM symbol for the LTE RAT is the same as the OFDM symbol for the NR RAT, the subframe is the same as the slot, and for brevity, the term slot is subsequently used in the remainder of this disclosure.

[0085] The unit used for DL ​​signaling or UL signaling on a cell is called a time slot and may include one or more symbols. The bandwidth (BW) unit is called a resource block (RB). One RB includes multiple subcarriers (SCs). For example, a time slot may have a duration of one millisecond, and an RB may have a bandwidth of 180 kHz and include 12 SCs with an inter-SC spacing of 15 kHz. The subcarrier spacing (SCS) may be determined by the SCS configuration μ as 2 μ · 15kHz. The unit of one subcarrier on one symbol is called a resource element (RE). The unit of one RB on one symbol is called a physical RB (PRB).

[0086] DL signaling includes a physical downlink shared channel (PDSCH) conveying information content, a PDCCH conveying DL control information (DCI), and a reference signal (RS). The PDCCH may be sent over a variable number of slot symbols including one slot symbol and over a plurality of control channel elements (CCEs) in a predetermined set of a plurality of CCEs called a CCE aggregation level within a control resource set (CORESET), as described in 3GPP TS 36.211v17.1.0, "NR; Physical channels and modulation" and 3GPP TS 38.213v17.1.0 "NR; Physical Layer procedures for control".

[0087] Figure 6 An example transmitter structure 600 using OFDM is shown according to an embodiment of the present disclosure. Figure 6 The embodiment of a transmitter structure 600 using OFDM shown in FIG. 6 is for illustration only. Figure 6 One or more of the components shown in the may be implemented in dedicated circuits configured to perform the functions described, or one or more components may be implemented by one or more processors executing instructions to perform the functions described. Figure 6 The scope of the present disclosure is not limited to any particular implementation of transmitter structure 600 using OFDM.

[0088] like Figure 6 As shown, information bits (such as DCI bits or data bits 610) are encoded by an encoder 620, rate matched to the allocated time / frequency resources by a rate matcher 630, and modulated by a modulator 640. Subsequently, the modulated coded symbols and DMRS or CSI-RS 650 are mapped to SC 660 by an RE mapping unit 665, an inverse fast Fourier transform (IFFT) is performed by a filter 670, a cyclic prefix (CP) is added by a CP insertion unit 680, and the resulting signal is filtered by a filter 690 and transmitted by a radio frequency (RF) unit 695.

[0089] Figure 7 An example receiver structure 700 using OFDM is shown according to an embodiment of the present disclosure. Figure 7 The embodiment of a receiver structure 700 using OFDM shown in FIG. 7 is for illustration only. Figure 7 One or more of the components shown in the may be implemented in dedicated circuits configured to perform the functions described, or one or more components may be implemented by one or more processors executing instructions to perform the functions described. Figure 7 The scope of the present disclosure is not limited to any particular implementation of receiver structure 700 using OFDM.

[0090] like Figure 7 As shown, the received signal 710 is filtered by a filter 720, a CP removal unit removes the CP 730, a filter 740 applies a fast Fourier transform (FFT), an RE demapping unit 750 demaps the REs selected by a BW selector unit 755, received symbols are demodulated by a channel estimator and demodulator unit 760, a rate dematcher 770 restores rate matching, and a decoder 780 decodes the resulting bits to provide information bits 790.

[0091] DCI can serve multiple purposes. The DCI format includes an information element (IE) and is typically used to schedule PDSCH (DLDCI format) or PUSCH (UL DCI format) transmissions. The DCI format includes a cyclic redundancy check (CRC) bit so that the UE confirms correct detection. The DCI format type is identified by a radio network temporary identifier (RNTI) that scrambles the CRC bit. For a DCI format that schedules PDSCH or PUSCH for a single UE with an RRC connection to an eNB, the RNTI is a cell RNTI (C-RNTI) or another RNTI type, such as MCS-C-RNTI. For a DCI format that schedules a PDSCH that conveys system information (SI) to a group of UEs, the RNTI is an SI-RNTI. For a DCI format that schedules a PDSCH that provides a response to a random access (RA) from a group of UEs, the RNTI is an RA-RNTI. For a DCI format that schedules a PDSCH that provides contention resolution in Msg4 of a RA process, the RNTI is a temporary C-RNTI (TC-RNTI). For a DCI format that schedules a PDSCH that pages a group of UEs, the RNTI is a P-RNTI. For a DCI format that provides a transmit power control (TPC) command to a group of UEs, the RNTI is a TPC-RNTI, and so on. Each RNTI type is configured to the UE via higher layer signaling. The UE typically decodes at multiple candidate locations for potential PDCCH transmissions.

[0092] Figure 8 An example encoding process 800 for a DCI format according to an embodiment of the present disclosure is shown. Figure 8 The embodiment of the encoding process 800 for a DCI format shown in FIG. 8 is for illustration only. Figure 8 The scope of the present disclosure is not limited to any particular implementation of the encoding process 800 for a DCI format.

[0093] The gNB encodes and transmits each DCI format separately in the corresponding PDCCH. When applicable, the DCI format is intended to mask the CRC of the DCI format codeword for the RNTI of its UE so that the UE can identify the DCI format. For example, the CRC may include 24 bits and the RNTI may include 16 bits or 24 bits. A CRC calculation unit 820 is used to determine the CRC of the (non-encoded) DCI format bits 810, and an exclusive OR (XOR) operation unit 830 between the CRC bits and the RNTI bits 840 is used to mask the CRC. The XOR operation is defined as XOR (0, 0) = 0, XOR (0, 1) = 1, XOR (1, 0) = 1, XOR (1, 1) = 0. The masked CRC bits are appended to the DCI format information bits using a CRC append unit 850. The encoder 860 performs channel coding, such as polarization coding, and then the rate matcher 870 performs rate matching with the allocated resources. The interleaving and modulation unit 880 applies interleaving and modulation, such as QPSK, and an output control signal 890 is transmitted.

[0094] Fig. 9 An example decoding process 900 for a DCI format according to an embodiment of the present disclosure is shown. Fig. 9 The embodiment of the decoding process 900 for a DCI format shown in FIG. 9 is for illustration only. Fig. 9 The scope of the present disclosure is not limited to any particular implementation of the decoding process 900 for a DCI format.

[0095] The received control signal 910 is demodulated and deinterleaved by a demodulator and deinterleaver 920. The rate matching applied at the gNB transmitter is recovered by a rate matcher 930 and the resulting bits are decoded by a decoder 940. After decoding, a CRC extractor 950 extracts the CRC bits and provides DCI format information bits 960. The DCI format information bits are demasked 970 by an XOR operation with the RNTI 980 (when applicable) and a CRC check is performed by a unit 990. When the CRC check succeeds (checksum is zero), the DCI format information bits are considered valid. When the CRC check fails, the DCI format information bits are considered invalid.

[0096] When NR RAT is introduced in an existing LTE network, both LTE and NR need to coexist in the same or overlapping spectrum. Spectrum sharing is then required to support LTE and NR coexistence. The spectrum sharing mechanism may depend on a number of factors, including whether the LTE scheduler and the NR scheduler can perform co-scheduling and whether UEs capable of operating with NRRAT can also operate with LTE RAT. Co-scheduling is typically possible when the eNB scheduler for LTE and the gNB scheduler for NR are collocated, in which case even the same scheduler for LTE and NR can be possible, or connected via a backhaul with substantially negligible latency so that dynamic configuration can be exchanged over the corresponding interface. Non-co-scheduling is typically required when the conditions for co-scheduling cannot be met.

[0097] Various embodiments of the present disclosure consider PDCCH monitoring aspects for enhanced cross-carrier scheduling operations in a carrier aggregation (CA) framework to support joint scheduling of multiple cells.

[0098] In a conventional 5G NR system, downlink or uplink data transmission may be scheduled only on a single serving cell. In other words, the DCI format provides scheduling information parameters for PDSCH or PUSCH on a single serving cell. If the serving cell is a scheduling cell, the UE receives the DCI format for PDSCH / PUSCH in the PDCCH it receives on the corresponding scheduling cell. In the case of cross-carrier scheduling, based on the carrier indication field (CIF) in the DCI format, the UE can determine the serving cell on which the UE can receive PDSCH or send PUSCH.

[0099] The legacy NR system does not support joint scheduling of multiple PDSCHs or multiple PUSCHs on multiple cells by using a single / common control signaling (such as by using a single DCI format). For this operation, the UE receives multiple DCI formats, each of which can schedule one of multiple PDSCHs or PUSCHs. This operation achieves the expected results, but introduces signaling overhead proportional to the number of scheduled PDSCHs or PUSCHs. In various scenarios, it is possible that some scheduling parameters or corresponding UE operations are shared / common between multiple PDSCHs or PUSCHs on "co-scheduled" cells.

[0100] For example, a UE may use the same PUCCH resource to send a PUCCH providing HARQ-ACK feedback corresponding to multiple PDSCHs. Therefore, the indication for the same PUCCH resource (and the corresponding operation of PUCCH transmission) in the DCI format for scheduling PDSCH reception on multiple cells simultaneously may be repeated multiple times unnecessarily. In addition, in some scenarios, such as intra-band CA, physical channel conditions may be relevant, so various scheduling parameters such as for link adaptation, MIMO / beamforming operations, and possibly even resource allocation may be common and repeated between co-scheduled cells. This unnecessary overhead in control signaling can be significant, particularly when the number of co-scheduled cells is large, such as 4-8 cells. In addition, the CRC bits need to be repeated in each of the DCI formats for scheduling PDSCH or PUSCH on multiple cells, which causes significant signaling overhead, particularly for a large number of scheduled cells / DCI formats.

[0101] Similarly, the PDCCH monitoring aspect in the legacy 5G NR system is based on a single cell scheduling mechanism with a self-carrier or cross-carrier scheduling process. In order to detect a single cell scheduled DCI format, the UE needs to monitor the PDCCH according to a search space set associated with one or more control resource sets (CORESETs) to receive and decode DCI formats for multiple PDCCH candidates. There are predetermined limits on the number of PDCCH candidates and the number of non-overlapping control channel elements (CCEs) that the UE can monitor in a time slot, where the latter refers to the channel estimate of the resources associated with the PDCCH candidates in the time slot. In addition, the specification supports a search space set overbooking process, where the UE can discard certain user-specific search space sets on the primary cell (with the lowest priority, i.e., with the largest index) when the predetermined limits on the number of PDCCH candidates or the number of non-overlapping CCEs are exceeded.

[0102] For a UE supporting multi-cell scheduling, the DCI format received in the PDCCH provides (partially or completely) scheduling information for multiple serving cells and may additionally point to another PDSCH or PDCCH including the remaining scheduling information.

[0103] Various embodiments of the present disclosure recognize the need for multi-cell scheduling, wherein multiple cells can be jointly scheduled using reduced signaling overhead, such as by using only a single DCI format with a reasonable DCI format size, which may be the same as or slightly larger than the traditional DCI format size. Designing such multi-cell scheduling operations should take into account the number of co-scheduled cells and the relative similarity of channel / radio conditions between the co-scheduled cells. In addition, various embodiments of the present disclosure recognize the need to determine the search space design for multi-cell scheduling, such as how / where the UE can search for PDCCH candidates for multi-cell scheduling, and how the UE can distinguish multi-cell scheduling DCI formats from single-cell scheduling DCI formats. In addition, in view of multi-cell scheduling, the UE's restrictions on PDCCH monitoring need to be revisited. For example, the UE needs to determine how to count PDCCH candidates for multi-cell scheduling of different cells included in the co-scheduled cell set. In addition, various embodiments of the present disclosure recognize that in the presence of multi-cell scheduling operations, other PDCCH monitoring aspects need to be specified, such as search space overbooking and dynamic spectrum sharing "DSS" operations (i.e., scheduling on a cell such as a PCell from two scheduling cells (such as from a PCell and a special SCell or "sSCell")).

[0104] Furthermore, various embodiments of the present disclosure recognize the need for multi-cell scheduling, wherein multiple cells may be jointly scheduled using reduced signaling overhead, such as by using only a single DCI format having the same or slightly larger size than a DCI format used for single-cell scheduling. Furthermore, various embodiments of the present disclosure recognize the need to specify other PDCCH monitoring aspects in the presence of multi-cell scheduling operations, such as search space set overbooking and dynamic spectrum sharing "DSS" operations (i.e., scheduling on a cell such as a primary cell from two scheduling cells (such as from a primary cell and a special secondary cell or "sSCell")).

[0105] Therefore, various embodiments of the present disclosure provide methods and apparatus for PDCCH monitoring in the context of multi-cell scheduled operation with reduced signaling overhead, such as when a set of serving cells are jointly scheduled, referred to as "co-scheduled" cells.

[0106] In one case, the search space set for multi-cell scheduling is associated only with the DCI format for multi-cell scheduling on a set of cells for cooperative scheduling. Such a search space set may be referred to as a multi-cell search space (MSS) set. Such a search space set may correspond to a set-level n_CI value, which is separate from the existing n_CI value corresponding to the search space set for single-cell scheduling. By monitoring the search space set, the UE may detect a DCI format for scheduling on all scheduled cells or only a subset of scheduled cells in a set of cells for cooperative scheduling. Therefore, the detected DCI format may have a CIF value that is the same as or different from the n_CI value corresponding to the search space set for multi-cell scheduling. The search space set may be publicly configured on the scheduling cell and on all scheduled cells in the set of cells for cooperative scheduling, thereby linking. When the linked search space set on the scheduling cell and at least one scheduled cell in the set of cells for cooperative scheduling is configured on the corresponding active DL BWP of the scheduling cell and at least one scheduled cell, the UE may monitor the search space set for multi-cell scheduling. When the UE monitors a PDCCH candidate with L non-overlapping CCEs in a timeslot according to a search space set, for each cell in a set of K co-scheduled cells, the UE counts the PDCCH candidate as a fractional count 1 / K of the multiple monitored PDCCH candidates in the timeslot, and counts as a fractional count L / K of the multiple monitored non-overlapping CCEs in the timeslot. For example, the PDCCH candidates for a set of 4 co-scheduled cells are counted as 1 / 4 of the PDCCH candidates for each cell in the set of 4 co-scheduled cells. When resolving a search space set oversubscription event, the UE may assign a higher priority to the search space set for multi-cell scheduling to cover the search space set for single-cell scheduling that is configured earlier in time and may have a smaller search space set index.

[0107] In one case, the search space set for multi-cell scheduling is associated with a DCI format (or multiple) for both multi-cell scheduling on a set of cells for cooperative scheduling and single-cell scheduling on a first scheduled cell in the set of cells for cooperative scheduling. Such a search space set corresponds to an existing cell-level n_CI value corresponding to the first scheduled cell. For example, the search space set for single-cell scheduling on the first scheduled cell can be configured to additionally monitor the DCI format for multi-cell scheduling. By monitoring the search space set, the UE can detect a DCI format for single-cell scheduling on a first scheduled cell having the same CIF value as the n_CI value corresponding to the first scheduled cell, or can detect a DCI format for multi-cell scheduling on all scheduled cells or only a subset of scheduled cells in the set of cooperatively scheduled cells having a different set-level CIF value from the n_CI value corresponding to the first scheduled cell. The search space set is commonly configured on the scheduling cell and only the first scheduled cell, thereby linked, and when both are configured on the active DL BWP of the scheduling cell and the first scheduled cell, the UE monitors the linked search space set. When the UE monitors a PDCCH candidate with L non-overlapping CCEs in a time slot according to a search space set, the UE counts the PDCCH candidate as a full / single count of multiple monitored PDCCH candidates in the time slot only for the first scheduled cell, and counts as a full count of multiple monitored non-overlapping CCEs in the time slot L - for other cells in the co-scheduled cell set, there is no counting limit.

[0108] In one case, the search space set for multi-cell scheduling is associated only with the DCI format for multi-cell scheduling on a set of cells for collaborative scheduling. Such a search space set may be referred to as a multi-cell search space (MSS) set. Such a search space set may correspond to a set-level n_CI value that is separate from the existing n_CI value corresponding to the search space set for single-cell scheduling. By monitoring the search space set, the UE may detect the DCI format for multi-cell scheduling. If the same CORESET is shared by multiple MSS sets for different sets of cells for collaborative scheduling, the first n_CI / CIF value for the set of cells for collaborative scheduling may identify the DCI format accordingly, while the second n_CI / CIF value for the scheduled cell may identify the scheduled cell from the set of cells for collaborative scheduling. The first n_CI value and the second n_CI value may be separate fields in the DCI format and have different numbers of bits.

[0109] The MSS set may be commonly configured on all scheduled cells in the scheduling cell and the co-scheduled cell set, thereby forming a link. When the linked search space set on the scheduling cell and at least one scheduled cell in the co-scheduled cell set is configured on the corresponding active DL BWP of the scheduling cell and at least one scheduled cell, the UE may monitor the MSS set. When the UE monitors a PDCCH candidate with L non-overlapping CCEs in a time slot according to the MSS set, for each cell in the K co-scheduled cell sets, the UE counts the PDCCH candidate as a fractional count 1 / K of the multiple monitored PDCCH candidates in the time slot, and counts as a fractional count L / K of the multiple monitored non-overlapping CCEs in the time slot. For example, the geometric PDCCH candidates for 4 co-scheduled cells are counted as 1 / 4 of the PDCCH candidates for each cell in the set of 4 co-scheduled cells. When resolving a search space set oversubscription event, the UE may assign a higher priority to the MSS set than the search space set for single cell scheduling.

[0110] One motivation for multi-cell scheduling using a single DCI format is for enhanced cross-carrier scheduling operation of a larger number of cells (such as 4-8 cells) operating in an intra-band CA framework in frequency bands below 6 GHz or above 6 GHz (referred to as FR1 or FR2), respectively. In general, embodiments are applicable to any deployment, vertical or scenario, including inter-band CA, with eMBB, URLLC and IIoT and XR, mMTC and IoT, with sidelink / V2X communications, with multiple TRPs / beams / panels, in unlicensed / shared spectrum (NR-U), for non-terrestrial networks (NTN), for aerial systems such as unmanned aerial vehicles (UAVs) such as drones, for private or non-public networks (NPNs), for UEs with reduced capability (RedCap) operation, etc.

[0111] Embodiments of the present disclosure for supporting PDCCH monitoring enhancement in the context of multi-cell scheduling with reduced signaling overhead are summarized below and are more fully explained further below.

[0112] In one embodiment, the UE may be provided with multiple co-scheduled cell sets by higher layers. The term co-scheduled cell set was once referred to as a serving cell set, where the UE may schedule PDSCH reception or PUSCH transmission on two or more cells in the co-scheduled cell set via a single DCI format or by using a supplementary method such as described herein. In addition, a subset of the co-scheduled cell set may be indicated to the UE via a DCI format in the PDCCH or via a MAC CE in the PDSCH, where the cells of the subset may change across different PDCCH monitoring occasions, for example, as indicated by the corresponding DCI format.

[0113] In one embodiment, for a UE configured with a co-scheduled cell set, the DCI format for multi-cell scheduling may provide all or part of the information of the values ​​of the cell common field and the cell specific field for scheduling PDSCH reception or PUSCH transmission on the corresponding one or more cells in the co-scheduled cell set. When the DCI format provides part of the information, the UE may determine the remaining information from the RRC signaling or by using other supplementary methods.

[0114] In one embodiment, when the UE is configured with a co-scheduled cell set including a first cell, the UE may receive a PDCCH with a DCI format that schedules PDSCH reception or PUSCH transmission only on the first cell (single-cell scheduled DCI format). The UE may distinguish the single-cell scheduled DCI format from the multi-cell scheduled DCI format via various methods, such as the DCI format size, or the RNTI used to scramble the CRC of the DCI format for multi-cell scheduling, or by explicit indication by a field in the DCI format, or by a dedicated CORESET and associated search space set.

[0115] In one embodiment, when the UE is configured with multi-cell scheduling of a cell set for co-scheduling by scheduling a cell, the UE may determine the association between the search space set for multi-cell scheduling and the co-scheduling cell set based on a modified definition of the carrier indicator field value n_CI.

[0116] In one embodiment, for multi-cell scheduling of a cell set for collaborative scheduling, where the UE is configured with a first search space set on the corresponding scheduling cell, there may be some methods for search space configuration and linking to the collaboratively scheduled cell set, such as configuring the linked search space set on all collaboratively scheduled cells, or configuring the linked search space set only on a reference cell in the collaboratively scheduled cell set, or not configuring the linked search space set on any collaboratively scheduled cell.

[0117] In one embodiment, for a UE configured with one or more co-scheduled cell sets, the size of a multi-cell DCI format may be set-specific (where the set refers to the co-scheduled cell set), or set-size-specific (where the set size refers to the size of the co-scheduled cell set), or search space set-specific, or scheduling cell-specific, or UE-specific. In addition, the UE may have constraints / budgets on multiple DCI format sizes that the UE may monitor per serving cell, per timeslot, or across all timeslots, where the size of a DCI format for multi-cell scheduling may count against the UE constraint / budget based on a fractional count or a full count, or may be part of a separate UE constraint / budget for the size of the DCI format, or may not count at all.

[0118] In one embodiment, for a UE configured with multi-cell scheduling of a set of cells for coordinated scheduling, and compared to single-cell scheduling, the UE monitors the same total number of PDCCH candidates and non-overlapping CCEs on the corresponding scheduled cells, but the UE counts multiple PDCCH candidates and non-overlapping CCEs for each scheduled cell in the set of cells for coordinated scheduling differently based on the search space set for multi-cell scheduling. When monitoring PDCCH candidates according to the UE-specific search space set for multi-cell scheduling, the UE counts the PDCCH candidates as a fraction of the number of PDCCH candidates that the UE can monitor. For example, for a set of cells for coordinated scheduling including 4 cells, the UE counts the PDCCH candidates for 4-cell scheduling as 1 / 4 of the PDCCH candidates for each cell in the set of 4 configured cells. Note that this allocation also applies when no DCI is detected in the PDCCH candidates, or even when the UE detects a DCI format for a subset of cells configured for coordinated scheduling (such as only 2 cells out of 4 cells). Alternatively, the count can be included only for one scheduled cell in the set of cells for coordinated scheduling.

[0119] In one embodiment, when a primary cell (PCell) is among cells of a co-scheduled cell set and scheduling on cells in the co-scheduled cell set is from the PCell (which is a scheduling cell for the co-scheduled cell set), and when the UE is configured to monitor the PDCCH to detect a search space set of a multi-cell scheduling DCI format, and when the UE determines an oversubscription event for a search space set, the UE may assign a higher priority to the search space set and discard other (single cell scheduling) search space sets before discarding such (multi-cell scheduling) search space set. Such operation may be beneficial, for example, when a search space set for multi-cell scheduling is configured at a later point in time after some single cell scheduling search space sets corresponding to some cells in the co-scheduled cell set have been configured, and thus the gNB is forced to assign a larger search space set index to the multi-cell scheduling search space set than those single cell scheduling search space sets, rather than reconfiguring all search space sets.

[0120] In one embodiment, for a multi-cell scheduled UE configured with a set of cells for collaborative scheduling, when the UE is configured to monitor the PDCCH for the set of cells for collaborative scheduling on a first scheduling cell and a second scheduling cell, the UE allocates PDCCH candidates and non-overlapping CCEs for multi-cell scheduling based on the method described herein, so that for each cell in the set of cells for collaborative scheduling, the UE maintains an allocation of PDCCH candidates and non-overlapping CCEs across the first scheduling cell and the second scheduling cell similar to when there is a single scheduling cell for the set of cells for collaborative scheduling. The first scheduling cell may be a PCell, and the second scheduling cell may be a special scheduling SCell, referred to as an sSCell. In one example, the set of cells for collaborative scheduling includes a PCell. In another example, the set of cells for collaborative scheduling additionally includes an sSCell. Therefore, both multi-cell scheduling and DSS operation affect the PDCCH monitoring behavior for the UE, wherein the impact of multi-cell scheduling is addressed separately from the impact of DSS operation.

[0121] Throughout this disclosure, the term "configuration" or "higher layer configuration" and variations thereof (such as "configured", etc.) are used to indicate one or more of: system information signaling such as via a MIB or SIB (such as SIB1), common or cell-specific higher layer / RRC signaling, or dedicated or UE-specific or BWP-specific higher layer / RRC signaling.

[0122] Throughout this disclosure, the term signal quality is used to indicate, for example, RSRP or RSRQ or RSSI or SNR or SINR of a channel or signal such as a reference signal (RS) including SSB, CSI-RS or SRS with or without filtering such as L1 or L3 filtering.

[0123] Antenna ports are defined such that the channel on which a symbol on the antenna port is transmitted can be inferred from the channel on which another symbol on the same antenna port is transmitted.

[0124] For a DM-RS associated with a PDSCH, the channel on which a PDSCH symbol on one antenna port is transmitted can be inferred from the channel on which a DM-RS symbol on the same antenna port is transmitted only if both symbols are within the same resources as the scheduled PDSCH, in the same time slot, and in the same PRG.

[0125] For a DM-RS associated with a PDCCH, the channel on which a PDCCH symbol on one antenna port is transmitted can be inferred from the channel on which a DM-RS symbol on the same antenna port is transmitted only if both symbols are within resources for which the UE can assume that the same precoding is used.

[0126] For DM-RS associated with PBCH, the channel on which a PBCH symbol on one antenna port is transmitted can be inferred from the channel on which a DM-RS symbol on the same antenna port is transmitted only if both symbols are within an SS / PBCH block sent in the same time slot and have the same block index.

[0127] Two antenna ports are considered to be quasi co-located if the large-scale characteristics of the channel over which the symbols on one antenna port are transmitted can be inferred from the channel over which the symbols on the other antenna port are transmitted. The large-scale characteristics include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters.

[0128] The UE may assume that SS / PBCH blocks transmitted with the same block index at the same center frequency position are quasi-co-located with respect to Doppler spread, Doppler shift, average gain, average delay, delay spread, and Rx parameters when spatially applicable. The UE shall not assume quasi-co-location for any other SS / PBCH block transmissions.

[0129] In the absence of CSI-RS configuration, unless otherwise configured, the UE may assume that the PDSCH DM-RS and SS / PBCH blocks are quasi-co-located with respect to Doppler shift, Doppler spread, average delay, delay spread, and spatial Rx parameters when applicable. The UE may assume that the PDSCH DM-RS within the same CDM group are quasi-co-located with respect to Doppler shift, Doppler spread, average delay, delay spread, and spatial Rx. The UE may also assume that the DMRS ports associated with the PDSCH are QCL with QCL type A, type D (when applicable), and average gain. The UE may further assume that no DM-RS conflicts with SS / PBCH blocks.

[0130] The UE may be configured with a list of up to M TCI state configurations within the higher layer parameter PDSCH-Config to decode the PDSCH based on a detected PDCCH with DCI intended for the UE and a given serving cell, where M depends on the UE capability maxNumberConfiguredTCIstatesPerCC. Each TCI state contains parameters for configuring the quasi-co-location (QCL) relationship between one or two downlink reference signals and the DMRS ports of the PDSCH, the DMRS ports of the PDCCH, or the CSI-RS ports of the CSI-RS resources. The quasi-co-location relationship is configured by the higher layer parameters qcl-Type1 for the first DL RS and qcl-Type2 for the second DL RS (if configured). For the case of two DL RSs, the QCL type should not be the same regardless of whether the reference is to the same DL RS or different DL RSs. The quasi-co-location type corresponding to each DL RS is given by the higher layer parameter qcl-Type in QCL-Info and can take one of the following values:

[0131] - "QCL-TypeA": {Doppler shift, Doppler spread, average delay, delay spread},

[0132] - "QCL-TypeB": {Doppler shift, Doppler spread},

[0133] - "QCL-TypeC": {Doppler shift, average delay},

[0134] - "QCL-TypeD": {spatial Rx parameters}.

[0135] The UE receives a MAC-CE activation command to map up to N (e.g., N=8) TCI states to code points of the DCI field 'Transmission Configuration Indication'. When HARQ-ACK information corresponding to the PDSCH carrying the (MAC-CE) activation command is sent in time slot n, the mapping of the indication between the TCI state and the code point of the DCI field 'Transmission Configuration Indication' shall be applied after the MAC-CE application time, e.g., from the TCI state in time slot n to the code point of the DCI field 'Transmission Configuration Indication'. After that the first time slot begins, is the number of slots per subframe for subcarrier spacing (SCS) configuration μ.

[0136] Independently of the configuration of tci-PresentInDCI and tci-PresentDCI-1-2 in RRC connected mode, if the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL and at least one configured TCI state of the serving cell for the scheduled PDSCH contains a qcl-Type set to "typeD",

[0137] - The UE may assume that the DM-RS ports of the PDSCH of the serving cell are quasi-co-located with the RS with respect to the QCL parameters indicated by the PDCCH quasi-co-location for the CORESET associated with the monitoring search space with the lowest controlResourceSetId in the latest slot in which one or more CORESETs within the active BWP of the serving cell were monitored by the UE. In this case, if the qcl-Type of the PDSCH DM-RS set to "typeD" is different from the qcl-Type of the PDCCH DM-RS with which they overlap in at least one symbol, the UE is expected to receive the PDCCH associated with that CORESET with priority. This also applies to the intra-band CA case (when the PDSCH and the CORESET are in different component carriers).

[0138] - if the UE is configured with enableDefaultTCIStatePerCoresetPoolIndex and the UE is configured by a higher layer parameter PDCCH-Config containing two different values ​​for coresetPoolIndex in different ControlResourceSets,

[0139] - The UE may assume that in the latest slot monitored by the UE, the DM-RS ports of the PDSCH associated with the value of coresetPoolIndex of the serving cell in which one or more CORESETs are associated with the same value of coresetPoolIndex as the PDCCH scheduling this PDSCH within the active BWP of the serving cell are quasi-co-located with the RS with respect to the QCL parameters for the PDCCH quasi-co-location indication of the CORESET associated with the monitoring search space with the lowest controlResourceSetId among the CORESETs configured with the same value of coresetPoolIndex as the PDCCH scheduling this PDSCH. In this case, if the "QCL-TypeD" of the PDSCH DM-RS is different from the "QCL-TypeD" of the PDCCH DM-RS with which they overlap in at least one symbol and they are associated with the same coresetPoolIndex, the UE is expected to receive the PDCCH associated with this CORESET with priority. This also applies to the intra-band CA case (when the PDSCH and the CORESET are in different component carriers).

[0140] -If the UE is configured with enableTwoDefaultTCI-States and at least one TCI codepoint indicates two TCI states, the UE may assume that the DM-RS ports of the PDSCH or PDSCH transmission opportunity of the serving cell are quasi-co-located with the RS with respect to the QCL parameters associated with the TCI state corresponding to the lowest codepoint among the TCI codepoints containing two different TCI states. When the UE is configured by the higher layer parameter repetitionScheme set to "tdmschemA" or configured with the higher layer parameter repetitionNumber, and the offset between the reception of the DL DCI and the first PDSCH transmission opportunity is less than the threshold timeDurationForQCL, the mapping of TCI states to PDSCH transmission opportunities is determined according to clause 5.1.2.1 by replacing the indicated TCI state with the TCI state corresponding to the lowest codepoint among the TCI codepoints containing two different TCI states based on the activated TCI state in the time slot with the first PDSCH transmission opportunity. In this case, if the "QCL-TypeD" in the two TCI states corresponding to the lowest code point among the TCI code points containing two different TCI states is different from the "QCL-TypeD" of the PDCCH DM-RS with which they overlap in at least one symbol, the UE is expected to receive the PDCCH associated with the CORESET preferentially. This also applies to intra-band CA cases (when PDSCH and CORESET are in different component carriers).

[0141] - In all the above cases, if none of the configured TCI states of the serving cell for the scheduled PDSCH is configured with qcl-Type set to "typeD", the UE shall derive the other QCL assumptions from the indicated TCI state for its scheduled PDSCH, regardless of the time offset between the reception of the DL DCI and the corresponding PDSCH.

[0142] If the PDCCH carrying the scheduling DCI is received on one component carrier, and the PDSCH scheduled by this DCI is on another component carrier:

[0143] -timeDurationForQCL is determined based on the subcarrier spacing of the scheduled PDSCH. If μPDCCH < μPDSCH, then add additional timing delay to timeDurationForQCL where d is defined in 5.2.1.5.1a-1, otherwise d is zero;

[0144] - For both cases, when the UE is configured with enableDefaultBeamForCCS, and when the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL, and when the DL DCI does not have the TCI field present, the UE derives its QCL assumption for the scheduled PDSCH from the activated TCI state with the lowest ID applicable for the PDSCH in the active BWP of the scheduled cell.

[0145] For PUSCH scheduled by DCI format 0_0 on a cell, if the higher layer parameter enableDefaultBeamPL-ForPUSCH0-0 is set to "enabled", the UE is not configured with PUCCH resources on an active UL BWP, and the UE is in RRC connected mode, the UE shall send PUSCH according to the spatial relationship (if applicable) with reference to the RS configured with qcl-Type set to "typeD" corresponding to the QCL hypothesis of the CORESET with the lowest ID on the active DL BWP of the cell.

[0146] For PUSCH scheduled by DCI format 0_0 on a cell, if the higher layer parameter enableDefaultBeamPL-ForPUSCH0 is set to "enabled", the UE is configured with PUCCH resources on the active UL BWP (wherein all PUCCH resources are not configured with any spatial relationship and the UE is in RRC connected mode), then if a CORESET is configured on the cell, the UE shall send PUSCH according to the spatial relationship (if applicable) with reference to the RS configured with qcl-Type set to "typeD" corresponding to the QCL hypothesis of the CORESET with the lowest ID on the active DL BWP of the cell.

[0147] In Carrier Aggregation (CA), two or more Component Carriers (CCs) are aggregated. A UE can simultaneously receive or transmit on one or more CCs depending on its capabilities:

[0148] - A UE with single timing advance capability for CA can simultaneously receive and / or transmit on multiple CCs corresponding to multiple serving cells (multiple serving cells grouped in one TAG) sharing the same timing advance;

[0149] - A UE with multiple timing advance capability for CA can simultaneously receive and / or transmit on multiple CCs corresponding to multiple serving cells with different timing advances (multiple serving cells grouped in multiple TAGs). The NG-RAN ensures that each TAG contains at least one serving cell;

[0150] - A UE without CA capability may receive on a single CC and transmit on a single CC corresponding to only one serving cell (one serving cell in one TAG).

[0151] CA is supported for both contiguous CCs and non-contiguous CCs. When CA is deployed, frame timing and SFN are aligned across cells that may be aggregated, or an offset of multiple slots between PCell / PSCell and SCell is configured to the UE. The maximum number of configured CCs for a UE is 16 for DL ​​and 16 for UL.

[0152] When CA is configured, the UE has only one RRC connection with the network. One serving cell provides NAS mobility information upon RRC connection establishment / reestablishment / handover, and one serving cell provides security input upon RRC connection reestablishment / handover. This cell is called the primary cell (PCell). Depending on the UE capabilities, a secondary cell (SCell) can be configured to form a serving cell set together with the PCell. Therefore, the configured serving cell set for the UE includes one PCell and one or more SCells.

[0153] Reconfiguration, addition and removal of SCells can be performed by RRC. The network can also add, remove, keep or reconfigure SCells for use with the target PCell at intra-NR handover and during connection recovery from RRC_INACTIVE. When adding a new SCell, dedicated RRC signaling is used to send all required system information of the SCell, i.e., the UE does not need to obtain broadcast system information directly from the SCell while in connected mode.

[0154] In order to achieve reduced UE battery consumption when CA is configured, an activation / deactivation mechanism for cells is supported. When a SCell is deactivated, the UE does not need to receive the corresponding PDCCH or PDSCH, cannot transmit in the corresponding uplink, and does not need to perform CQI measurements. In contrast, when the SCell is active, the UE should receive PDSCH and PDCCH (if the UE is configured to monitor PDCCH from that SCell) and is expected to be able to perform CQI measurements. NG-RAN ensures that when a PUCCH SCell (a secondary cell configured with PUCCH) is deactivated, the SCells of the secondary PUCCH group (a group of SCells whose PUCCH signaling is associated with the PUCCH on the PUCCH SCell) should not be activated. NG-RAN ensures that the SCell mapped to the PUCCH SCell is deactivated before the PUCCH SCell is changed or removed.

[0155] When reconfiguring the serving cell set:

[0156] -The SCell added to the set is initially activated or deactivated;

[0157] - SCells that remain in the set (unchanged or reconfigured) do not change their activation state (activated or deactivated).

[0158] On handover or connection recovery from RRC_INACTIVE:

[0159] -SCell is activated or deactivated.

[0160] In order to achieve reduced UE battery consumption when BA is configured, only one UL BWP and one DL BWP or only one DL / UL BWP pair for each uplink carrier can be active at one time in the active serving cell, and all other BWPs with which the UE is configured are deactivated. On a deactivated BWP, the UE does not monitor PDCCH, does not transmit on PUCCH, PRACH and UL-SCH.

[0161] In order to achieve reduced UE battery consumption and reduced UE complexity when CA is configured, only one UL BWP and one DL BWP or only one DL / UL BWP pair for each uplink carrier can be active at one time in an active serving cell, and all other BWPs with which the UE is configured are deactivated. On a deactivated BWP, the UE does not monitor PDCCH, does not transmit on PUCCH, PRACH and UL-SCH.

[0162] To achieve fast SCell activation when CA is configured, a dormant BWP can be configured for the SCell. If the active BWP of the activated SCell is the dormant BWP, the UE stops monitoring PDCCH and sending SRS / PUSCH / PUCCH on the SCell, but continues to perform CSI measurements, AGC and beam management (if configured). DCI is used to control the dormant BWP entering / leaving one or more SCells or one or more SCell groups.

[0163] The dormant BWP is one of the dedicated BWPs of the UE configured by the network via dedicated RRC signaling. SpCell and PUCCH SCell cannot be configured with a dormant BWP.

[0164] Cross-carrier scheduling with carrier indicator field (CIF) allows the PDCCH of a serving cell to schedule resources on another serving cell, with the following restrictions:

[0165] - Cross-carrier scheduling is not applicable to PCell, i.e., PCell is scheduled via its own PDCCH;

[0166] -When a SCell is configured with a PDCCH, the PDSCH and PUSCH of the cell are scheduled by the PDCCH on the SCell;

[0167] -When a SCell is not configured with a PDCCH, the PDSCH and PUSCH of the SCell are scheduled by the PDCCH on another serving cell;

[0168] -Scheduled PDCCH and scheduled PDSCH / PUSCH may use the same or different parameter sets.

[0169] Cross-carrier scheduling using the Carrier Indicator Field (CIF) allows a DCI format provided by the PDCCH on a serving / scheduling cell to schedule resources on another serving / scheduling cell, with the following restrictions:

[0170] - When cross-carrier scheduling from SCell to PCell is not configured for the UE, the UE can schedule transmission or reception on the PCell only through the DCI format provided by PDCCH reception on the PCell;

[0171] -When cross-carrier scheduling from SCell to PCell is configured for the UE:

[0172] -The PDCCH on the SCell can provide the DCI format for scheduling PDSCH reception or PUSCH transmission from the UE on the PCell;

[0173] -The PDCCH on the PCell may provide a DCI format for scheduling PDSCH reception or PUSCH transmission from a UE on the PCell;

[0174] -Only one SCell can be configured for a UE for cross-carrier scheduling on the PCell.

[0175] -When an SCell is configured for a UE as a scheduling cell, PDSCH reception or PUSCH transmission from the UE is scheduled by a DCI format provided by PDCCH reception on the SCell;

[0176] - When an SCell is not configured for a UE as a scheduling cell, PDSCH reception or PUSCH transmission from the UE is scheduled by a DCI format provided by PDCCH reception on another serving cell;

[0177] - PDCCH reception on a scheduled cell may have the same or a different set of parameters as the associated PDSCH reception or PUSCH transmission on the scheduled cell.

[0178] Some of the above restrictions can be relaxed. For example, dynamic spectrum sharing (DSS) allows LTE and NR to share the same carrier. As the number of NR devices in the network increases, it is important to ensure sufficient scheduling capacity for NR UEs on the shared carrier. In the case of DSS operation, PDCCH enhancement for cross-carrier scheduling can be considered so that the PDCCH of a SCell called a special / scheduled SCell (sSCell) can schedule PDSCH or PUSCH on a P(S)Cell.

[0179] The physical downlink control channel (PDCCH) can be used to schedule DL transmission on the PDSCH and UL transmission on the PUSCH, where the downlink control information (DCI) on the PDCCH includes:

[0180] - Downlink allocation including at least modulation and coding format, resource allocation and hybrid ARQ information related to DL-SCH;

[0181] - An uplink scheduling grant containing at least the modulation and coding format, resource allocation and hybrid ARQ information related to the UL-SCH.

[0182] In addition to scheduling, PDCCH can be used for:

[0183] - Activation and deactivation of configured PUSCH transmissions with configured grants;

[0184] -Activation and deactivation of PDSCH semi-persistent transmission;

[0185] - Notify one or more UEs of the timeslot format;

[0186] - Notify one or more UEs that the UE may assume that no PRBs and OFDM symbols intended for the UE are transmitted;

[0187] - Transmission of TPC commands for PUCCH and PUSCH;

[0188] - Transmission of one or more TPC commands for SRS transmission by one or more UEs;

[0189] - Switching the active bandwidth portion of the UE;

[0190] -Initiate a random access procedure;

[0191] - instruct the UE to monitor the PDCCH during the next occurrence of the DRX on duration;

[0192] - In the IAB context, indicates the availability of soft symbols for the IAB-DU.

[0193] The UE monitors the PDCCH candidate set in the configured monitoring occasions in one or more configured CORESETs according to the corresponding search space configuration.

[0194] A CORESET includes a set of PRBs with a duration of 1 to 3 OFDM symbols. Resource unit resource element groups (REGs) and control channel elements (CCEs) are defined within a CORESET, where each CCE includes a set of REGs. A control channel is formed by the aggregation of CCEs. Different code rates for the control channel are achieved by aggregating different numbers of CCEs. Interleaved and non-interleaved CCE to REG mapping is supported in a CORESET.

[0195] Polarization coding is used for PDCCH. Each resource element group carrying PDCCH carries its own DMRS. QPSK modulation is used for PDCCH.

[0196] The UE monitors the set of PDCCH candidates in one or more CORESETs on the active DL BWP on each activated serving cell configured with PDCCH monitoring according to the corresponding search space set, where monitoring implies decoding each PDCCH candidate according to the monitored DCI format.

[0197] If the UE is provided with a monitoringCapabilityConfig for a serving cell, the UE obtains an indication to monitor PDCCH on the serving cell for the maximum number of PDCCH candidates and non-overlapping CCEs:

[0198] - if monitoringCapabilityConfig = r15monitoringcapability, then every time slot, or

[0199] -If monitoringCapabilityConfig=r16monitoringcapability, then every span.

[0200] If the UE is not provided with monitoringCapabilityConfig, the UE monitors PDCCH on the serving cell for the maximum number of PDCCH candidates and non-overlapping CCEs per slot.

[0201] The UE may indicate the ability to monitor the PDCCH according to one or more of the combinations (X, Y) = (2, 2), (4, 3) and (7, 3) according to the SCS configuration for μ = 0 and μ = 1. A span is a number of consecutive symbols in a time slot in which the UE is configured to monitor the PDCCH. Each PDCCH monitoring opportunity is within a span. If the UE monitors the PDCCH on a cell according to the combination (X, Y), the UE supports PDCCH monitoring opportunities in any symbol of a time slot having a minimum time interval of X symbols between the first symbols of two consecutive spans (including across time slots). The span starts at the first symbol at which the PDCCH monitoring opportunity begins and ends at the last symbol at which the PDCCH monitoring opportunity ends, where the number of symbols in the span is up to Y.

[0202] If the UE can support:

[0203] - a first set of serving cells, wherein the UE is not provided with a coresetPoolIndex or is provided with a coresetPoolIndex having a single value for all CORESETs on all DL BWPs for each scheduling cell in the first set of serving cells, and

[0204] - a second set of serving cells, wherein, on any DL BWP for each scheduling cell in the second set of serving cells, the UE is not provided with a coresetPoolIndex or is provided with a coresetPoolIndex having a value of 0 for the first CORESET and having a value of 1 for the second CORESET, and the UE determines the number of serving cells for the purpose of reporting PDCCH-BlindEventCA as Here, R is the value reported by the UE.

[0205] If the UE indicates in UE-NR-Capability a carrier aggregation capability of more than 4 serving cells and the UE is not provided with a monitoringCapabilityConfig for any downlink cell, or if the UE is provided with a monitoringCapabilityConfig=r15monitoringcapability for all downlink cells in which the UE monitors PDCCH, the UE includes in UE-NR-Capability an indication of the maximum number of PDCCH candidates and the maximum number of non-overlapping CCEs that the UE may monitor per timeslot when the UE is configured for carrier aggregation operation on more than 4 cells. When the UE is not configured for NR-DC operation, the UE determines to monitor the UE corresponding to The maximum number of PDCCH candidates per time slot and the maximum number of non-overlapping CCEs per downlink cell are as follows:

[0206] - yes If the UE does not provide pdcch-BlindDetectionCA, where: is the number of configured downlink serving cells.

[0207] -otherwise, It is the value of pdcch-BlindDetectionCA.

[0208] When the UE is configured for NR-DC operation, the UE determines to monitor the corresponding The maximum number of PDCCH candidates per time slot of the downlink cell and the maximum number of non-overlapping CCEs (where Provided by pdcch-BlindDetection for MCG), and determine the monitoring corresponding to the SCG The maximum number of PDCCH candidates per time slot of the downlink cell and the maximum number of non-overlapping CCEs (where When the UE is configured for carrier aggregation operation on more than 4 cells, or when the UE is configured for NR-DC operation for a cell group, the UE is not expected to monitor more than 4 cells per timeslot as shown in the example from The corresponding value of infers the maximum number of multiple PDCCH candidates or multiple non-overlapping CCEs.

[0209] If the UE indicates a carrier aggregation capability of more than two downlink cells in UE-NR-Capability-r16, the UE includes in UE-NR-Capability-r16 an indication of the maximum number of PDCCH candidates and the maximum number of non-overlapping CCEs that the UE may monitor per span when the UE is configured for carrier aggregation operation on more than two downlink cells with monitoringCapabilityConfig=r16monitoringcapability. When the UE is not configured for NR-DC operation and the UE is provided with monitoringCapabilityConfig=r16monitoringcapability for all downlink cells in which the UE monitors PDCCH, the UE determines to monitor the PDCCH corresponding to The maximum number of PDCCH candidates per span and the maximum number of non-overlapping CCEs per downlink cell are as follows:

[0210] - Is the number of configured downlink cells. If the UE does not provide pdcch-MonitoringCA,

[0211] -otherwise, It is the value of pdcch-MonitoringCA.

[0212] When the UE is configured for carrier aggregation operation on more than 2 cells, or when the UE is configured for NR-DC operation for a cell group, the UE is not expected to monitor more than 100 cells per span from The corresponding value of infers the maximum number of multiple PDCCH candidates or multiple non-overlapping CCEs.

[0213] If the UE indicates in UE-NR-Capability a carrier aggregation capability of more than one downlink cell with monitoringCapabilityConfig=r15monitoringcapability or more than one downlink cell with monitoringCapabilityConfig=r16monitoringcapability, the UE includes in UE-NR-Capability-r16 an indication of the maximum number of PDCCH candidates and the maximum number of non-overlapping CCEs that the UE can monitor for downlink cells with monitoringCapabilityConfig=r15monitoringcapability and for downlink cells with monitoringCapabilityConfig=r16monitoringcapability when the UE is configured for carrier aggregation operation on more than two downlink cells (wherein at least one downlink cell has monitoringCapabilityConfig=r15monitoringcapability and at least one downlink cell has monitoringCapabilityConfig=r16monitoringcapability). When the UE is not configured for NR-DC operation, the UE determines to monitor the PDCCH candidates corresponding to the downlink cells respectively. Downlink cell or The maximum number of PDCCH candidates per slot or per span and the maximum number of non-overlapping CCEs for each downlink cell, where:

[0214] - Is the number of configured downlink cells. If the UE does not provide pdcch-BlindDetectionCA1,

[0215] -otherwise,

[0216] - If the UE reports only one combination of (pdcch-BlindDetectionCA1, pdcch-BlindDetectionCA2), then is the value of pdcch-BlindDetectionCA1,

[0217] -otherwise, is the value of pdcch-BlindDetectionCA1 in the combination of (pdcch-BlindDetectionCA1, pdcch-BlindDetectionCA2) provided by pdcch-BlindDetectionCA-CombIndicator, and

[0218] - Is the number of configured downlink cells. If the UE does not provide PDCCH-BlinddDetectionCA2,

[0219] -otherwise,

[0220] - If the UE reports only one combination of (pdcch-BlindDetectionCA1, pdcch-BlindDetectionCA2), then is the value of pdcch-BlindDetectionCA2,

[0221] -otherwise, It is the value of pdcch-BlindDetectionCA2 in the combination of (pdcch-BlindDetectionCA1, pdcch-BlindDetectionCA2) provided by pdcch-BlindDetectionCA-CombIndicator.

[0222] The PDCCH candidate set for the UE to monitor is defined according to the PDCCH search space set. The search space set can be a CSS set or a USS set. The UE monitors PDCCH candidates in one or more of the following search space sets:

[0223] - Type0-PDCCH CSS set configured by pdcch-ConfigSIB1 in MIB or searchSpaceSIB1 in PDCCH-ConfigCommon or searchSpaceZero in PDCCH-ConfigCommon, for DCI format with CRC scrambled by SI-RNTI on the primary cell of the MCG,

[0224] - Type0A-PDCCH CSS set configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon, for DCI format with CRC scrambled by SI-RNTI on the primary cell of the MCG,

[0225] - Type1-PDCCH CSS set configured by ra-SearchSpace in PDCCH-ConfigCommon for DCI formats on the primary cell with CRC scrambled by RA-RNTI, MsgB-RNTI or TC-RNTI,

[0226] - Type2-PDCCH CSS set configured by pagingSearchSpace in PDCCH-ConfigCommon, for DCI format with CRC scrambled by P-RNTI on the primary cell of the MCG,

[0227] - Type3-PDCCH CSS set configured by SearchSpace in PDCCH-Config with searchSpaceType=common, for DCI formats with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI or CI-RNTI and (for primary cell only) C-RNTI, MCS-C-RNTI, CS-RNTI or PS-RNTI, and

[0228] -The USS set configured by SearchSpace in PDCCH-Config with searchSpaceType=ue-Specific, for DCI format with CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI, SL-RNTI, SL-CS-RNTI or SL semi-persistent scheduling V-RNTI.

[0229] If the UE:

[0230] - One or more search space sets are provided by one or more of searchSpaceZero, searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, ra-SearchSpace, or a CSS set is provided by PDCCH-Config, and is provided

[0231] -SI-RNTI, P-RNTI, RA-RNTI, MsgB-RNTI, SFI-RNTI, INT-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI or TPC-SRS-RNTI;

[0232] Then, for the RNTI in any of these RNTIs, the UE does not expect to process information in more than one DCI format with a CRC scrambled by the RNTI per time slot.

[0233] For each DL BWP configured for the UE in the serving cell, the UE may be provided by higher layer signaling with:

[0234] - P ≤ 3 CORESETs, if coresetPoolIndex is not provided, or if the value of coresetPoolIndex is the same for all CORESETs when coresetPoolIndex is provided,

[0235] - P ≤ 5 CORESETs, if coresetPoolIndex is not provided for the first CORESET, or is provided for the first CORESET and its value is 0, and is provided for the second CORESET and its value is 1.

[0236] For each CORESET, the UE is provided with the following by a ControlResourceSet:

[0237] - The CORESET index p via controlResourceSetId or via controlResourceSetId-v1610, where:

[0238] - If coresetPoolIndex is not provided, or if the value of coresetPoolIndex is the same for all CORESETs when coresetPoolIndex is provided, then 0 < p < 12;

[0239] - 0 < p < 16, if coresetPoolIndex is not provided for the first CORESET, or is provided for the first CORESET and its value is 0, and is provided for the second CORESET and its value is;

[0240] - The initialization value of the DM-RS scrambling sequence via pdcch-DMRS-ScramblingID;

[0241] - The precoder granularity of multiple REGs in the frequency domain, where the UE may assume the same DM-RS precoder via precoderGranularity;

[0242] - Multiple consecutive symbols provided by the duration;

[0243] - the set of resource blocks provided by frequencyDomainResources;

[0244] - CCE to REG mapping parameters provided by cce-REG-MappingType;

[0245] -Antenna port quasi co-location in the antenna port quasi co-location set provided by TCI-State, which indicates the quasi co-location information of the DM-RS antenna port for PDCCH reception in the corresponding CORESET;

[0246] - If the UE is provided with up to two cell lists for simultaneous TCI state activation by simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2, the UE applies the antenna port quasi-co-location provided by the TCI state with the same activated tci-StateID value to the CORESET with index p in all configured DL BWPs of all configured cells in the list determined from the serving cell index provided by the MAC CE command;

[0247] -Indication of the presence or absence of a transmission configuration indication (TCI) field for a DCI format other than DCI format 1_0, through tci-PresentInDCI or tci-PresentDCI-1-2, wherein the DCI format schedules PDSCH reception or indicates SPS PDSCH release or indicates SCell dormancy or indicates a request for Type-3 HARQ-ACK codebook reporting without scheduling PDSCH and is transmitted by PDCCH in CORESETp.

[0248] When precoderGranularity=allContiguousRB, the UE does not expect:

[0249] - configuring a set of resource blocks of a CORESET, which includes more than four resource block subsets that are not contiguous in frequency,

[0250] - Any RE of CORESET to overlap with any RE determined from lte-CRS-ToMatchAround or from LTE-CRS-PatternList, or overlap with any RE of SS / PBCH block.

[0251] For each CORESET in the DL BWP of the serving cell, the corresponding frequencyDomainResources provides a bitmap:

[0252] - If CORESET is not associated with any search space set configured with freqMonitorLocations, then of The bits of the bitmap have a one-to-one mapping with non-overlapping groups of 6 consecutive PRBs in ascending order of PRB indices in the DL BWP bandwidth of 6 PRBs, where if rb-Offset is not provided, the first common RB of the first group of 6 PRBs has a common RB index Or the first common RB of the first group of 6 PRBs has a common RB index in, Provided by rb-Offset,

[0253] - If CORESET is associated with at least one search space set configured with freqMonitorLocations, then of The PRB indices in each RB set k in the DL BWP bandwidth of PRBs are in ascending order, the first bits have a one-to-one mapping with non-overlapping groups of 6 consecutive PRBs, see REF 4, where the first common RB of the first group of 6 PRBs has a common RB index And k is indicated by freqMonitorLocations (if provided for the search space set); otherwise, k=0. is the number of available PRBs in RB set 0 for DLB WP, and provided by rb-Offset, or if rb-Offset is not provided, then If the UE is provided with the RB set in the DL BWP, the UE expects the RBs of the CORESET to be within the union of the PRBs in the RB set of the DL BWP.

[0254] For a CORESET other than the one with index 0,

[0255] - If the UE has not been provided with configuration of TCI states by tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList for CORESET, or has been provided with initial configuration of more than one TCI states for CORESET by tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList, but has not received a MAC CE activation command for one of the TCI states, as described in REF 5, the UE assumes that the DM-RS antenna ports associated with PDCCH reception are quasi-co-located with the SS / PBCH blocks identified by the UE during the initial access procedure;

[0256] - If the UE has been provided with configuration of more than one TCI state by tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList for CORESET as part of the reconfiguration procedure with synchronization procedure, as described in REF 6, but has not yet received a MAC CE activation command for one of the TCI states, as described in REF 5, the UE assumes that the DM-RS antenna port associated with PDCCH reception is quasi-co-located with the SS / PBCH block or CSI-RS resource identified by the UE during the random access procedure initiated by the reconfiguration with synchronization procedure, as described in REF 6.

[0257] For a CORESET with index 0, the UE assumes that the DM-RS antenna ports used for PDCCH reception in the CORESET are quasi-co-located with:

[0258] - one or more DL RSs configured by the TCI state indicated by the MAC CE activation command for the CORESET (if any), or

[0259] - SS / PBCH blocks identified by the UE during the most recent random access procedure not initiated by a PDCCH command triggering a contention-free random access procedure, if a MAC CE Activation Command indicating the TCI state for the CORESET was not received after the most recent random access procedure.

[0260] 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 provided TCI states for the CORESET, the UE assumes that the DM-RS antenna ports associated with PDCCH reception in the CORESET are quasi-co-located with one or more DL RS configured by the TCI state. For the CORESET with index 0, the UE expects that the CSI-RS configured with qcl-Type set to "typeD" in the TCI state indicated by the MAC CE activation command for the CORESET is provided by the SS / PBCH block:

[0261] - If the UE receives a MAC CE activation command for one of the TCI states, the UE The activation command is applied in the first time slot after k, where k is the time slot in which the UE shall send the PUCCH with HARQ-ACK information of the PDSCH providing the activation command, and μ is the SCS configuration of the PUCCH. The active BWP is defined as the active BWP in the time slot when the activation command is applied.

[0262] IE SearchSpace defines how / where to search for PDCCH candidates. Each search space is associated with one ControlResourceSet. For scheduled cells in case of cross-carrier scheduling, all optional fields except nrofCandidates are not present (regardless of their presence conditions). SearchSpace information element

[0263]

[0264]

[0265]

[0266]

[0267]

[0268] For each DL BWP configured for a UE in a serving cell, the UE is provided by higher layers with S≤10 search space sets, where for each of the S search space sets, the UE is provided by SearchSpace with the following items:

[0269] - The search space set index s provided by searchSpaceId, 0 <S<40,

[0270] - the association between the search space set S and CORESETp provided by controlResourceSetId or by controlResourceSetId-v1610,

[0271] -k provided by monitoringSlotPeriodicityAndOffset s The PDCCH monitoring periodicity and o s The PDCCH monitoring offset of the time slot is

[0272] - the PDCCH monitoring pattern within a slot provided by monitoringSymbolsWithinSlot, indicating the first symbol of the CORESET within the slot used for PDCCH monitoring,

[0273] -T provided by duration s <k s The duration of time slots indicates the number of time slots for which the search space set s exists.

[0274] - For CCE aggregation level 1, CCE aggregation level 2, CCE aggregation level 4, CCE aggregation level 8 and CCE aggregation level 16, multiple PDCCH candidates per CCE aggregation level provided by aggregationLevel1, aggregationLevel2, aggregationLevel4, aggregationLevel8 and aggregationLevel16 respectively

[0275] - an indication that the search space set s provided by searchSpaceType is a CSS set or a USS set,

[0276] - If the search space set s is a CSS set, then

[0277] - an indication provided by dci-Format0-0-AndFormat1-0 for monitoring PDCCH candidates of DCI format 0_0 and DCI format 1_0,

[0278] - an indication provided by dci-Format2-0 to monitor one or two PDCCH candidates for DCI format 2_0 and the corresponding CCE aggregation level, or an indication to monitor one PDCCH candidate per RB set (if the UE is provided with freqMonitorLocations for search space sets),

[0279] - an indication provided by dci-Format2-1 for monitoring PDCCH candidates of DCI format 2_1,

[0280] - an indication provided by dci-Format2-2 for monitoring PDCCH candidates of DCI format 2_2,

[0281] - an indication provided by dci-Format2-3 for monitoring PDCCH candidates of DCI format 2_3,

[0282] - an indication provided by dci-Format2-4 for monitoring PDCCH candidates of DCI format 2_4,

[0283] - an indication provided by dci-Format2-6 for monitoring PDCCH candidates of DCI format 2_6,

[0284] - if the search space set s is a USS set, an indication provided by dci-Formats for monitoring PDCCH candidates for DCI format 0_0 and DCI format 1_0, or DCI format 0_1 ​​and DCI format 1_1, or an indication provided by dci-FormatsExt for monitoring PDCCH candidates for DCI format 0_2 and DCI format 1_2, or DCI format 0_1, DCI format 1_1, DCI format 0_2 and DCI format 1_2, or DCI format 3_0, or DCI format 3_1, or DCI format 3_0 and DCI format 3_1,

[0285] - A bitmap provided by freqMonitorLocations (if provided) indicating the index of one or more RB sets of the search space set s, where the MSB k in the bitmap corresponds to RB set k-1 in the DL BWP. For RB set k indicated in the bitmap, the first PRB of the frequency domain monitoring locations within the RB set is restricted by Given, where is the index of the first common RB of RB set k, see REF 4, and provided by rb-Offset, or if rb-Offset is not provided, then For each RB set with a corresponding value of 1 in the bitmap, the frequency domain resource allocation pattern for the monitoring location is based on the first RB set in frequencyDomainResources provided by the associated CORESET configuration. bits to determine.

[0286] If monitoringSymbolsWithinSlot indicates to the UE to monitor PDCCH in a subset of up to the same three consecutive symbols in each slot in which the UE monitors PDCCH for all search space sets, then if the subset includes at least one symbol after the third symbol, the UE does not expect to be configured with a PDCCH SCS other than 15 kHz.

[0287] The UE does not expect to be provided with multiple consecutive symbols and the first symbol of the CORESET that result in PDCCH candidates being mapped to symbols of different slots.

[0288] The UE does not expect any two PDCCH monitoring occasions on an active DL BWP in the same CORESET, for the same search space set or for different search space sets, to be separated by a non-zero number of symbols that is less than the CORESET duration.

[0289] The UE determines the PDCCH monitoring opportunity on the active DLBWP from the PDCCH monitoring periodicity, PDCCH monitoring offset and PDCCH monitoring pattern in the time slot. For the search space set s, the UE determines that the PDCCH monitoring opportunity exists in the search space with number n. f The frames in the In the time slot (if UE in the slave time slot Starting T s monitor the PDCCH candidates of the search space set s in consecutive time slots, and in the next k s -T s The PDCCH candidates in the search space set s are not monitored in consecutive time slots.

[0290] The USSs at CCE aggregation level L∈{1,2,4,8,16} are defined by the PDCCH candidate set of CCE aggregation level L.

[0291] If the UE is configured with CrossCarrierSchedulingConfig for the serving cell, the CarrierIndicator field value corresponds to the value indicated by CrossCarrierSchedulingConfig.

[0292] For the active DL BWP of the serving cell on which the UE monitors PDCCH candidates in the USS, if the UE is not configured with the carrier indicator field, the UE monitors PDCCH candidates without the carrier indicator field. For the active DL BWP of the serving cell on which the UE monitors PDCCH candidates in the USS, if the UE is configured with the carrier indicator field, the UE monitors PDCCH candidates with the carrier indicator field.

[0293] If the UE is configured to monitor PDCCH candidates with a carrier indicator field corresponding to a secondary cell in another serving cell, the UE does not expect to monitor PDCCH candidates on the active DL BWP of the secondary cell.For the active DL BWP of the serving cell on which the UE monitors PDCCH candidates, the UE monitors PDCCH candidates for at least the same serving cell.

[0294] For the search space set s associated with CORESETp, the search space set s corresponding to the carrier indicator field value n CI The active DL BWP of the serving cell and the time slot PDCCH candidates in the search space set The corresponding CCE index of aggregation level L is given by:

[0295]

[0296] in,

[0297] For any CSS,

[0298] For USS, Y p,-1 =n RNTI ≠0, for pmod3=0, A p =39827, for pmod3 = 1, A p =39829, for pmod3 = 2, A p =39839, and D = 65537;

[0299] i=0,…,L-1;

[0300] N CCE,p It is from 0 to N in CORESETp CCE,p -1 the number of CCEs numbered, if any, for each RB set;

[0301] If the UE is configured with the Carrier Indicator field via the CrossCarrierSchedulingConfig for the serving cell on which the PDCCH is monitored, then n CI is the Carrier Indicator field value; otherwise, including for any CSS, n CI =0;

[0302] in, The UE is configured for CI The number of PDCCH candidates monitored by the aggregation level L of the search space set s of the corresponding serving cell;

[0303] For any CSS,

[0304] For USS, is the number of all configurations of CCE aggregation level L in the search space set s CI On the value Maximum value;

[0305] For n RNTI The RNTI value is C-RNTI.

[0306] The UE is expected to monitor PDCCH candidates of up to 4 sizes of DCI formats (including up to 3 sizes of DCI formats with CRC scrambled by C-RNTI) per serving cell (this rule is sometimes referred to as a "3+1" DCI format size budget). The UE counts multiple sizes of DCI formats per serving cell based on the number of PDCCH candidates configured in the corresponding search space set for the corresponding active DL BWP.

[0307] If for the search space set s i j There is an index PDCCH candidate, or if serving cell n uses the same CCE set CI In the CORESETp on the active DL BWP, there exists a PDCCH candidates and The PDCCH candidates have the same scrambling and the corresponding DCI formats for the PDCCH candidates have the same size, then for serving cell n CI The search space set s of the CCE set used in CORESETp on the active DL BWP j with index The PDCCH candidate with index is not counted for monitoring; otherwise, The PDCCH candidates are counted for monitoring.

[0308] The UE does not expect to configure a CSS set that results in exceeding the corresponding maximum number of monitored PDCCH candidates per slot or per span and the corresponding total number of non-overlapping CCEs or number per scheduled cells, respectively.

[0309] ​For same cell scheduling or for cross-carrier scheduling, the UE does not expect the number of PDCCH candidates per timeslot or per span and the number of corresponding non-overlapping CCEs on the secondary cell to be greater than the corresponding number per timeslot or per span that the UE can monitor on the secondary cell, respectively. If the UE is provided with monitoringCapabilityConfig=r16monitoringcapability for the primary cell, then except for the first span of each timeslot, the UE does not expect the number of PDCCH candidates per span and the number of corresponding non-overlapping CCEs on the primary cell to be greater than the corresponding number per span that the UE can monitor on the primary cell.

[0310] For cross-carrier scheduling, the number of PDCCH candidates for monitoring and the number of non-overlapping CCEs per span or per slot are counted individually for each scheduled cell.

[0311] For operation with a single serving cell, Table 1 provides the maximum number of PDCCH candidates to be monitored per slot for a UE in a DL BWP with SCS configuration μ.

[0312] Table 1: Maximum number of monitored PDCCH candidates per slot for DL ​​BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell

[0313]

[0314] For operation with a single serving cell, Table 2 provides the maximum number of PDCCH candidates to be monitored per span for a UE in a DL BWP with SCS configuration μ.

[0315] Table 2: Maximum number of monitored PDCCH candidates in the span of combination (X,Y) for DL ​​BWP with SCS configuration μ∈{0,1} for a single serving cell

[0316]

[0317]

[0318] For operation with a single serving cell, Table 3 provides the maximum number of non-overlapping CCEs for the DL BWP with SCS configuration μ that the UE is expected to monitor for the corresponding PDCCH candidate per slot.

[0319] CCEs for PDCCH candidates are non-overlapping if they correspond to:

[0320] - a different CORESET index, or

[0321] - Different first symbols are used for reception of corresponding PDCCH candidates.

[0322] Table 3: Maximum number of non-overlapping CCEs per slot for DL ​​BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell

[0323]

[0324] For operation with a single serving cell, Table 4 provides the maximum number of non-overlapping CCEs for the DL BWP with SCS configuration μ that the UE is expected to monitor for the corresponding PDCCH candidate per span.

[0325] Table 4: Maximum number of non-overlapping CCEs in the span of combination (X,Y) for DL ​​BWP with SCS configuration μ∈{0,1} for a single serving cell

[0326]

[0327] If the UE:

[0328] - pdcch-BlindDetectionCA is not reported or BDFactorR is not provided, then γ = R,

[0329] -Report pdcch-BlindDetectionCA, then the UE can be indicated by BDFactorR, γ=1 or γ=R.

[0330] If the UE is configured with a monitoringCapabilityConfig-r16 for which the UE is not provided or monitoringCapabilityConfig-r16=r15monitoringcapability is provided but CORESETPoolIndex is not provided downlink cells with associated PDCCH candidates monitored in the active DL BWP of the scheduling cell using SCS configuration μ, where The UE does not need to monitor the active DL BWP of the scheduling cell:

[0331] -When the dispatch cell comes from When there are more than 10 downlink cells, for each scheduled cell, there are more than 10 downlink cells per time slot. PDCCH candidates or more non-overlapping CCEs, or

[0332] -When the dispatch cell comes from When there are more than 10 downlink cells, for each scheduled cell, there are more than 10 downlink cells per time slot. PDCCH candidates or more non-overlapping CCEs,

[0333] -When the dispatch cell comes from When there are multiple downlink cells, for each scheduled cell, for a CORESET with the same coresetPoolIndex value, more than PDCCH candidates or more non-overlapping CCEs.

[0334] If the UE is configured with a downlink cell for which the UE is provided with both monitoringCapabilityConfig-r16=r15monitoringcapability and monitoringCapabilityConfig-r16=r16monitoringcapability, then quilt replace.

[0335] If the UE:

[0336] - configured with a UE for which monitoringCapabilityConfig is not provided or monitoringCapabilityConfig-r16=r15monitoringcapability is provided but coresetPoolIndex is not provided Downlink cells,

[0337] - has an associated PDCCH candidate monitored in the active DL BWP of the scheduling cell using SCS configuration μ, where, and

[0338] - 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 firstActiveDownlinkBWP-Id for the deactivated cell,

[0339] The UE does not need to The active DLBWP of the scheduling cell in the downlink cell monitors more than PDCCH candidates or more

[0340] non-overlapping CCEs. If the UE is configured with a downlink cell for which the UE is provided with both monitoringCapabilityConfig-r16=r15monitoringcapability and monitoringCapabilityConfig-r16=r16monitoringcapability, then quilt replace.

[0341] for For each scheduled cell in the downlink cells, the UE does not need to monitor more than 100 timeslots per time slot on the active DL BWP with SCS configuration μ of the scheduled cell. PDCCH candidates or more non-overlapping CCEs.

[0342] for For each scheduled cell in the downlink cells, the UE does not need to monitor on the active DL BWP with SCS configuration μ of the scheduled cell:

[0343] - More than per time slot PDCCH candidates or more non-overlapping CCEs,

[0344] - For a CORESET with the same coresetPoolIndex value, more than PDCCH candidates or more non-overlapping CCEs.

[0345] If the UE is configured with monitoringCapabilityConfig=r16monitoringcapability for which the UE is provided downlink cells, the associated PDCCH candidates monitored in the active DL BWP of the scheduling cell using the SCS configuration μ, and The combination (X,Y) is used for PDCCH monitoring in the downlink cell. downlink cells, of which, Then when the scheduling cell comes from When there are multiple downlink cells, the UE does not need to monitor more than 100 downlink cells per span for each scheduled cell on the active DL BWP of the scheduled cell. PDCCH candidates or more non-overlapping CCEs. If the UE is configured with a downlink cell for which the UE is provided with both monitoringCapabilityConfig=r15monitoringcapability and monitoringCapabilityConfig=r16monitoringcapability, then quilt replace.

[0346] If the UE only configures the monitoringCapabilityConfig=r16monitoringcapability for which the UE is provided downlink cells, associated PDCCH candidates monitored in the active DL BWP of the scheduling cell using SCS configuration μ, and The combination (X,Y) is used for PDCCH monitoring in the downlink cell. downlink cells, of which, 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 of the deactivated cell with the index provided by firstActiveDownlinkBWP-Id, then the UE does not need to monitor more than PDCCH candidates or more Non-overlapping CCEs

[0347] -if The union of the PDCCH monitoring opportunities on all scheduling cells in the downlink cells results in PDCCH monitoring according to the combination (X,Y), and any pair in the set spans within Y symbols, then within every X symbols per span set over active DL BWPs of all scheduled cells in downlink cells, wherein the first X symbols start at the first symbol with a PDCCH monitoring opportunity and the next X symbols start at the first symbol with a PDCCH monitoring opportunity that is not included in the first X symbols,

[0348] -Across The set of active DL BWPs per span of all scheduled cells in the downlink cell, where for each span set, there is at most one span per scheduled cell, otherwise,

[0349] -in, is the number of configured cells with associated PDCCH candidates monitored in the active DL BWP of the scheduling cell using SCS configuration j. If the UE is configured with downlink cells for which the UE is provided with both monitoringCapabilityConfig=r15monitoringcapability and monitoringCapabilityConfig=r16monitoringcapability, then quilt replace.

[0350] For the combination (X,Y) For each scheduled cell in the downlink cells, the UE does not need to monitor more than one downlink per span on the active DL BWP with SCS configuration μ of the scheduled cell. PDCCH candidates or more non-overlapping CCEs.

[0351] The UE does not expect to configure a CSS set that results in the corresponding total number of monitored PDCCH candidates per slot or per span and the number of non-overlapping CCEs or per scheduled cells exceeding the corresponding maximum number per slot or per span, respectively.

[0352] For same cell scheduling or for cross-carrier scheduling, the UE does not expect the number of PDCCH candidates and the corresponding number of non-overlapping CCEs per time slot or per span on the secondary cell to be greater than the corresponding number per time slot or per span that the UE can monitor on the secondary cell, respectively. If the UE is provided with monitoringCapabilityConfig=r16monitoringcapability for the primary cell, then except for the first span of each time slot, the UE does not expect the number of PDCCH candidates and the corresponding number of non-overlapping CCEs per span on the primary cell to be greater than the corresponding number per span that the UE can monitor on the primary cell.

[0353] For cross-carrier scheduling, the number of PDCCH candidates for monitoring and the number of non-overlapping CCEs per span or per slot are counted individually for each scheduled cell.

[0354] For all search space sets within time slot n or within a span in time slot n, use S css Indicates the cardinality is I css A collection of CSS collections, and with S uss Indicates the cardinality is J uss A collection of USS collections. j (0≤j<J uss ) in S ussThe positions in are in ascending order according to the search space set index. It is represented as: For CSS set S css (i) the number of PDCCH candidates counted to be monitored, and, For USS set S uss (j) The number of PDCCH candidates counted to be monitored.

[0355] For a CSS set, the UE needs to monitor a total of Non-overlapping CCEs PDCCH candidates.

[0356] According to the following pseudo code, if the UE is not provided with monitoringCapabilityConfig for the primary cell or if the UE is provided with monitoringCapabilityConfig=r15monitoringcapability for the primary cell, or, in the first span of each time slot, if the UE is provided with monitoringCapabilityConfig=r16monitoringcapability for the primary cell, the UE allocates PDCCH candidates for monitoring in the time slot to the USS set for the primary cell having an active DL BWP with SCS configuration μ. If, for the USS set for scheduling on the primary cell, the UE is not provided with coresetPoolIndex for the first CORESET, or is provided with a coresetPoolIndex with a value of 0 for the first CORESET and a coresetPoolIndex with a value of 1 for the second CORESET, and if or The following pseudo code applies only to the USS set associated with the first CORESET. The UE does not expect to monitor PDCCH in the USS set without an allocated PDCCH candidate for monitoring. In the following pseudo code, if the UE is provided with monitoringCapabilityConfig=r16monitoringcapability for the primary cell, then and Respectively and Instead, and and Respectively and replace.

[0357] By V CCE (S uss(j)) represents the search space set S uss (j) is a set of non-overlapping CCEs, and is given by Indicates V CCE (S uss (j)) where the PDCCH candidates for monitoring the CSS set and the PDCCH candidates for monitoring all search space sets S are considered. uss (k)(0≤k≤j) allocated PDCCH candidates are determined for the search space set S uss (j) Non-overlapping CCEs.

[0358] set up

[0359] set up

[0360] Set j = 0;

[0361] when and hour,

[0362] To be used for monitoring PDCCH candidates are allocated to the USS set S uss (j);

[0363]

[0364]

[0365] j=j+1;

[0366] End when.

[0367] If the UE:

[0368] - configured for single cell operation or for operation with carrier aggregation in the same frequency band, and

[0369] - monitoring PDCCH candidates in overlapping PDCCH monitoring occasions in multiple CORESETs that have been configured with the same or different qcl-Type set to the "typeD" attribute on the active DL BWP of one or more cells,

[0370] Then the UE monitors PDCCH on the active DL BWP of a cell in one or more cells only in the CORESET and in any other CORESET in the multiple CORESETs that has been configured with a qcl-Type set to the same "typeD" attribute as the CORESET:

[0371] - CORESET corresponds to the set of CSSs with the lowest index in the cell with the lowest index that contains the CSS (if any); otherwise, corresponds to the set of USSs with the lowest index in the cell with the lowest index,

[0372] - in overlapping PDCCH monitoring occasions, the lowest USS set index is determined over all USS sets with at least one PDCCH candidate,

[0373] - For the purpose of determining CORESET, SS / PBCH blocks are considered to have a different QCL "typeD" attribute than CSI-RS,

[0374] - for the purpose of determining CORESET, it is assumed that a first CSI-RS associated with a SS / PBCH block in a first cell and a second CSI-RS in a second cell also associated with a SS / PBCH block have the same QCL "typeD" attribute,

[0375] - Allocation of non-overlapping CCEs and PDCCH candidates for PDCCH monitoring is based on all search space sets associated with multiple CORESETs on the active DL BWP of one or more cells,

[0376] -The number of active TCI states is determined from multiple CORESETs.

[0377] If the UE:

[0378] - configured for single cell operation or for operation with carrier aggregation in the same frequency band, and

[0379] - monitoring PDCCH candidates in overlapping PDCCH monitoring occasions in multiple CORESETs, where none of the CORESETs has a TCI state configured with qcl-Type set to "typeD",

[0380] The UE is then required to monitor PDCCH candidates in overlapping PDCCH monitoring occasions for search space sets associated with different CORESETs.

[0381] For the scheduled cell and at any time, the UE is expected to have received a maximum of 16 PDCCHs, DCI format with CRC scrambled by C-RNTI, CS-RNTI or MCS-C-RNTI, for scheduling 16 PDSCH receptions for which the UE has not received any corresponding PDSCH symbols, and a maximum of 16 PDCCHs, DCI format with CRC scrambled by C-RNTI, CS-RNTI or MCS-C-RNTI, for scheduling 16 PUSCH transmissions for which the UE has not sent any corresponding PUSCH symbols.

[0382] If the UE is not provided with monitoringCapabilityConfig=r16monitoringcapability for any serving cell, and:

[0383] - Not configured for NR-DC operation and indicated by pdcch-BlindDetectionCA for The ability of a downlink cell to monitor PDCCH candidates and the UE is configured with Downlink cell or uplink cells, or

[0384] - configured with NR-DC operation and for Downlink cell or For a group of uplink cells, the UE is expected to have received the maximum PDCCH, used for

[0385] - Scheduling UEs for which they have not yet Any corresponding PDSCH symbol is received on the downlink cell DCI format received for each PDSCH with a CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI,

[0386] - Scheduling UEs for which they have not yet The uplink cell sends any corresponding PUSCH symbol The DCI format for PUSCH transmission with a CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI.

[0387] If the UE is provided with monitoringCapabilityConfig=r16monitoringcapability for all serving cells, and:

[0388] - Not configured for NR-DC operation and indicated by pdcch-MonitoringCA The ability of a downlink cell to monitor PDCCH candidates and the UE is configured with Downlink cell or uplink cells, or

[0389] - configured with NR-DC operation and for Downlink cell or For a group of uplink cells, the UE is expected to have received the maximum PDCCH, used for

[0390] - Scheduling UEs for which they have not yet Any corresponding PDSCH symbol is received on the downlink cell received DCI formats with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI,

[0391] -Scheduling UE has not yet been The uplink cell sends any corresponding PUSCH symbol The DCI format for PUSCH transmission with a CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI.

[0392] If the UE is provided with monitoringCapabilityConfig=r16monitoringcapability for at least one serving cell and is not provided with monitoringCapabilityConfig=r16monitoringcapability for at least one serving cell, and,

[0393] - is not configured for NR-DC operation and indicates Downlink cells and The ability of a downlink cell to monitor PDCCH candidates and the UE is configured with Downlink cell or uplink cells, or,

[0394] - configured with NR-DC operation and for Downlink cell or A cell group of uplink cells,

[0395] The UE is expected to have received respectively:

[0396] -most PDCCHs for scheduling UEs for which they have not yet received any corresponding PDSCH symbols on all serving cells for which monitoringCapabilityConfig=r16monitoringcapability is not provided DCI format received for each PDSCH with a CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI,

[0397] -most PDCCHs for scheduling UEs for which they have not yet sent any corresponding PUSCH symbols on all serving cells for which monitoringCapabilityConfig=r16monitoringcapability is not provided DCI format for PUSCH transmission with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI,

[0398] -most PDCCHs are used to schedule UEs for which they have not yet received any corresponding PDSCH symbols on all serving cells provided with monitoringCapabilityConfig=r16monitoringcapability DCI format for PDSCH reception with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI

[0399] -most PDCCHs for scheduling UEs for which they have not yet sent any corresponding PUSCH symbols on all serving cells provided with monitoringCapabilityConfig=r16monitoringcapability The DCI format for PUSCH transmission with a CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI.

[0400] If the UE:

[0401] - configured to monitor, in the CORESET with index zero on the active DL BWP, a first PDCCH candidate of DCI format 0_0 and DCI format 1_0 from the CSS set and a second PDCCH candidate of DCI format 0_0 and DCI format 1_0 from the USS set, and,

[0402] - the DCI format 0_0 / 1_0 associated with the first PDCCH candidate and the DCI format 0_0 / 1_0 associated with the second PDCCH candidate have the same size, and,

[0403] - the UE receives the first PDCCH candidate and the second PDCCH candidate on the same set of CCEs, and,

[0404] - the first PDCCH candidate and the second PDCCH candidate have the same scrambling, and,

[0405] - DCI format 0_0 / 1_0 for the first PDCCH candidate and DCI format 0_0 / 1_0 for the second PDCCH candidate have a CRC scrambled by C-RNTI or MCS-C-RNTI or CS-RNTI,

[0406] The UE then only decodes DCI format 0_0 / 1_0 associated with the first PDCCH candidate.

[0407] If the UE detects a DCI format with inconsistent information, the UE discards all information in the DCI format.

[0408] A UE configured with the bandwidth part indicator in a DCI format determines, in case the active DL BWP or active UL BWP changes, that the information in the DCI format is applicable to the new active DL BWP or UL BWP, respectively.

[0409] For unpaired spectrum operation, if the UE is not configured for serving cell c 2 If the PDCCH is in time with the serving cell c, 2 The UE may also overlap SRS transmissions on the serving cell (including any interruptions due to uplink or downlink RF retuning time [10, TS 38.133]) and if the UE cannot 1 and serving cell c 2 receiving and transmitting simultaneously on the serving cell c, the UE does not expect 1 Monitor PDCCH.

[0410] If the UE is provided with resourceBlocks and symbolsInResourceBlock in RateMatchPattern, or if the UE is additionally provided with periodicityAndPattern in RateMatchPattern, the UE may determine the set of RBs in the symbols of the slot that are not available for PDSCH reception, as described in [6, TS38.214]. If a PDCCH candidate in the slot is mapped to one or more REs that overlap with REs of any RB in the set of RBs in the symbols of the slot, the UE does not expect to monitor the PDCCH candidate.

[0411] The UE does not expect to be configured with dci-FormatsSL and dci-FormatsExt in the same USS.

[0412] In the downlink, the gNB can dynamically allocate resources to the UE via the C-RNTI on the PDCCH. The UE monitors the PDCCH to find possible allocations when its downlink reception is enabled (an activity managed by DRX when configured). When CA is configured, the same C-RNTI applies to all serving cells.

[0413] The gNB may preempt an ongoing PDSCH transmission of one UE with a latency critical transmission to another UE. The gNB may configure the UE to monitor for interrupted transmission indications using the INT-RNTI on the PDCCH. If a UE receives an interrupted transmission indication, the UE may assume that the resource elements included in the indication carry no information useful to the UE, even if some of these resource elements have been scheduled for the UE.

[0414] In addition, with semi-persistent scheduling (SPS), the gNB can allocate downlink resources for initial HARQ transmission to the UE: RRC defines the periodicity of the configured downlink allocation, and the PDCCH addressed to the CS-RNTI can signal and activate the configured downlink allocation, or deactivate it; that is, the PDCCH addressed to the CS-RNTI indicates that the downlink allocation can be implicitly reused according to the periodicity defined by RRC until deactivation. When needed, retransmissions are explicitly scheduled on the PDCCH.

[0415] If they overlap in time, the dynamically allocated downlink reception overrides the configured downlink allocation in the same serving cell. Otherwise, if activated, downlink reception according to the configured downlink allocation is assumed.

[0416] For a given BWP of a serving cell, a UE may be configured with up to 8 actively configured downlink allocations. When more than one is configured:

[0417] - the network decides which of these configured downlink allocations are active at once (including all of them); and,

[0418] - Each configured downlink allocation is activated individually using a DCI command, and deactivation of a configured downlink allocation is done using a DCI command, which may deactivate a single configured downlink allocation or deactivate multiple configured downlink allocations jointly.

[0419] PUSCH can be scheduled using DCI on PDCCH, or semi-statically configured grants can be provided through RRC, where two types of operations are supported:

[0420] - using DCI to trigger the first PUSCH, where subsequent PUSCH transmissions follow the RRC configuration and scheduling received on the DCI, or,

[0421] - PUSCH is triggered by data arriving at the UE's transmit buffer, and PUSCH transmission follows the RRC configuration.

[0422] In the uplink, the gNB can dynamically allocate resources to the UE via the C-RNTI on the PDCCH. The UE monitors the PDCCH to find possible grants for uplink transmission when its downlink reception is enabled (an activity managed by DRX when configured). When CA is not configured, the same C-RNTI applies to all serving cells.

[0423] The gNB may cancel a UE's PUSCH transmission, or a repetition of a PUSCH transmission, or an SRS transmission for another UE with a latency critical transmission. The gNB may configure the UE to monitor for a cancelled transmission indication using the CI-RNTI on the PDCCH. If a UE receives a cancelled transmission indication, the UE shall cancel PUSCH transmissions from the earliest symbol overlapping with the resources or SRS transmissions overlapping with the resources indicated by the cancellation.

[0424] Additionally, using the configured grant, the gNB can allocate uplink resources to the UE for initial HARQ transmission and HARQ retransmission. Two types of configured uplink grants are defined:

[0425] - With Type 1, RRC directly provides the configured uplink grant (including periodicity).

[0426] - With type 2, RRC defines the periodicity of the configured uplink grant, and the PDCCH addressed to the CS-RNTI can signal and activate the configured uplink grant, or deactivate it; that is, the PDCCH addressed to the CS-RNTI indicates that the uplink grant can be implicitly reused according to the periodicity defined by RRC until deactivation.

[0427] If the UE is not configured with enhanced intra-UE overlapping resource prioritization, then dynamically allocated uplink transmissions override the configured uplink grants in the same serving cell if they overlap in time. Otherwise, if activated, uplink transmissions according to the configured uplink grants are assumed.

[0428] If the UE is configured with enhanced intra-UE overlapping resource prioritization, in case a configured uplink grant transmission overlaps in time with a dynamically allocated uplink transmission or with another configured uplink grant transmission in the same serving cell, the UE prioritizes the transmission based on a comparison between the highest priority of the logical channels that have data to be transmitted and are multiplexed or capable of being multiplexed in the MAC PDU associated with the overlapping resources. Similarly, in case a configured uplink grant transmission or a dynamically allocated uplink transmission overlaps in time with a scheduling request transmission, the UE prioritizes the transmission based on a comparison between the priority of the logical channel that triggered the scheduling request and the highest priority of the logical channels that have data to be transmitted and are multiplexed or capable of being multiplexed in the MAC PDU associated with the overlapping resources. In case a MAC PDU associated with a reduced priority transmission has been generated, the UE keeps it stored to allow the gNB to schedule a retransmission. The UE may also be configured by the gNB to transmit the stored MAC PDU as a new transmission using subsequent resources configured with the same configured uplink grant when an explicit retransmission grant is not provided by the gNB.

[0429] Retransmissions other than repetitions are explicitly assigned via the PDCCH or via configuration of a retransmission timer.

[0430] For a given BWP of a serving cell, a UE may be configured with up to 12 active configured uplink grants. When more than one is configured, the network decides which of these configured uplink grants are active at once (including all uplink grants). Each configured uplink grant may be type 1 or type 2. For type 2, activation and deactivation of configured uplink grants are independent between serving cells. When more than one type 2 configured grant is configured, a DCI command is used to activate each configured grant individually, and a DCI command is used to complete deactivation of a type 2 configured grant, where the DCI command may deactivate a single configured grant configuration or jointly deactivate multiple configured grant configurations.

[0431] When SUL is configured, the network shall ensure that an uplink grant of an active configuration on the SUL does not overlap in time with an uplink grant of another active configuration on another UL configuration.

[0432] For both dynamic grants and configured grants, for a transport block, two or more repetitions may be in one slot, or across slot boundaries in consecutive available slots, where each repetition is in one slot. For both dynamic grants and configured grant type 2, the number of repetitions may also be dynamically indicated in L1 signaling. The dynamically indicated number of repetitions shall override the RRC configured number of repetitions, if both are present.

[0433] In multiple transmit / receive point (multi-TRP) operation, the serving cell can schedule UEs from two TRPs, thereby providing better PDSCH coverage, reliability and / or data rate.

[0434] There are two different modes of operation for multiple TRPs: single DCI and multiple DCI. For both modes, the control of uplink and downlink operations is done by both the physical layer and the MAC. In single DCI mode, the UE is scheduled by the same DCI for both TRPs, and in multiple DCI mode, the UE is scheduled by independent DCI from each TRP.

[0435] The downlink / uplink physical layer processing of the transport channel includes the following steps:

[0436] - Transport block CRC attachment;

[0437] - Code block segmentation and code block CRC attachment;

[0438] - Channel coding: LDPC coding;

[0439] - Physical layer hybrid ARQ processing;

[0440] -Rate matching;

[0441] - scrambling;

[0442] - Modulation: π / 2BPSK (only for uplink with transform precoding), QPSK, 16QAM, 64QAM and 256QAM;

[0443] - Layer mapping;

[0444] - (Uplink only) Transform precoding (enable / disable via configuration) and precoding;

[0445] -Mapping to allocated resources and antenna ports.

[0446] The UE may assume that there is at least one symbol with a demodulation reference signal on each layer where PDSCH is sent to the UE, and up to 3 additional DMRS may be configured by higher layers. Phase tracking RS may be sent on additional symbols to assist receiver phase tracking.

[0447] The UE sends at least one symbol with demodulation reference signal on each layer on each hop frequency where PUSCH is sent, and up to 3 additional DMRS may be configured by higher layers.Phase tracking RS may be sent on additional symbols to assist receiver phase tracking.

[0448] When scheduled by the UE to receive PDSCH via DCI, the time domain resource allocation field value m of the DCI provides a row index m+1 to the allocation table. The index row defines the slot offset K0, the start and length indicator SLIV, or directly defines the start symbol S and the allocation length L, and the PDSCH mapping type to be assumed in PDSCH reception.

[0449] Given the parameter value of the index row:

[0450] - The time slot allocated for PDSCH is Ks, where if the UE is configured with ca-SlotOffset for at least one of the scheduled cell and the scheduled cell, then otherwise, Where n is the time slot with scheduled DCI, K0 is based on the parameter set of PDSCH, and μ PDSCH and μ PDCCH are the subcarrier spacing configurations for PDSCH and PDCCH, and

[0451] - and μ offset,PDCCH They are and μ offset , which are respectively determined by the higher layer configuration ca-SlotOffset of the cell for receiving PDCCH, and μ offset,PDSCH They are and μ offset , which is determined by the higher layer configuration ca-SlotOffset of the cell used to receive PDSCH.

[0452] When the UE is scheduled to send a transport block without a CSI report, or when the UE is scheduled to send a transport block and a CSI report on the PUSCH via DCI, the "Time Domain Resource Allocation" field value m of the DCI provides a row index m+1 to the allocated table. The index row defines the slot offset K2, the start and length indicator SLIV, or directly defines the start symbol S and the allocation length L, the PUSCH mapping type / and the number of repetitions to be applied in the PUSCH transmission (if numberOrepetitions exists in the resource allocation table).

[0453] When a UE is scheduled to send a PUSCH without a transport block and with a CSI report via the "CSI Request" field on the DCI, the "Time Domain Resource Allocation" field value m of the DCI provides a row index m+1 to the allocated table. The index row defines the start and length indicator SLIV, or directly defines the start symbol S and the allocation length L, and the PUSCH mapping type and K2 value to be applied in the PUSCH transmission are determined as Among them, Y j (m+1) is Y j The (m+1)th entry of j ,j=0,...,N Rep -1 is the corresponding list entry for the higher level parameter

[0454] -reportSlotOffsetListDCI-0-2, if PUSCH is scheduled by DCI format 0_2 and reportSlotOffsetListDCI-0-2 is configured;

[0455] -reportSlotOffsetListDCI-0-1, if PUSCH is scheduled by DCI format 0_1 ​​and reportSlotOffsetListDCI-0-1 is configured;

[0456] - Otherwise, reportSlotOffsetList; in the case of N Rep The CSI-ReportConfig that triggers the CSI report setting.

[0457] - If the UE is configured with ca-SlotOffset for at least one of the scheduled cell and the scheduled cell, the time slot Ks in which the UE shall send the PUSCH is determined by K2 as K s = otherwise, Where n is the time slot with scheduled DCI, K 2 Based on the PUSCH parameter set, and μ PUSCH and μPDCCH They are the subcarrier spacing configurations of PUSCH and PDCCH,

[0458] - and μ offset,PDCCH They are and μ offset , which is determined by the ca-SlotOffset configured by higher layers for the cell receiving the PDCCH, and μ offset,PUSCH They are and μ offset , which is determined by the higher layer configuration ca-SlotOffset of the cell used to send PUSCH.

[0459] The information element ca-SlotOffset provides the slot offset between the primary cell (PCell / PSCell) and the SCell in the unaligned frame boundary of inter-band CA with slot alignment and partial SFN alignment. Based on this field, the UE determines the time offset of the SCell. The granularity of this field is determined by the reference SCS of the slot offset (i.e., the lowest SCS of the PCell / PSCell among all configured SCSs in the DL / UL SCS-SpecificCarrierList in ServingCellConfigCommon or ServingCellConfigCommonSIB and the maximum value among the lowest SCS of the serving cell among all configured SCSs in the DL / UL SCS-SpecificCarrierList in ServingCellConfigCommon or ServingCellConfigCommonSIB). The network configures at most a single non-zero offset duration (in ms) between CCs in the unaligned CA configuration (independent of the SCS). If this field is not present, the UE applies a value of 0. The slot offset value can only change with SCell release and addition. In this context, scs-SpecificCarrierList provides a set of carriers for different subcarrier spacings (parameter sets), which are defined relative to point A. The network configures scs-SpecificCarrier at least for each parameter set (SCS) used, for example, in BWP.

[0460] For carrier aggregation of cells with unaligned frame boundaries, the time slot offset between PCell / Pscell and SCell Determined by the higher layer parameter ca-SlotOffset of SCell. offsetDefined as the maximum value of the lowest subcarrier spacing configuration among the subcarrier spacing given by the higher layer parameter scs-SpecificCarrierList configured for PCell / PSCell and SCell respectively. satisfy

[0461] - When the lowest subcarrier spacing configuration among the subcarrier spacings configured for the cells is μ=2 for both cells or μ=3 for both cells, the start of the time slot 0 of the cell with the lower frequency at point A is aligned with the time slot 0 of the other cell. The beginning of coincidence, wherein if point A of the PCell / PSCell has a lower frequency than the frequency of point A of the SCell, then q=-1, otherwise q=1;

[0462] - Otherwise, the start of slot 0 of the cell with the lower subcarrier spacing of the lowest subcarrier spacing given by the higher layer parameter scs-SpecificCarrierList configured for both cells, or the start of slot 0 of the Pcell / PSCell (if both cells have the same lowest subcarrier spacing given by the higher layer parameter scs-SpecificCarrierList configured for both cells) with the other cell's slot The beginning of q coincides, where if the lowest subcarrier spacing configuration given by the scs-SpecificCarrierList of the PCell / PSCell is less than or equal to the lowest subcarrier spacing given by the scs-SpecificCarrierList of the SCell, then q=-1, otherwise q=1.

[0463] HARQ operation is supported for DL ​​reception. Asynchronous incremental redundancy HARQ is supported. The gNB provides HARQ-ACK feedback timing to the UE dynamically in the DCI or semi-statically in the RRC configuration. Retransmission of HARQ-ACK feedback is supported for operation with shared spectrum channel access by using an enhanced dynamic codebook and / or one-time trigger for HARQ-ACK transmission for all configured CCs and HARQ processes in the PUCCH group. The UE may be configured to receive codeblock group based transmissions, where retransmissions may be scheduled as a subset of all codeblocks carrying TBs.

[0464] HARQ operation is supported for UL transmissions. Asynchronous incremental redundancy HARQ is supported. The gNB schedules each uplink transmission and retransmission using an uplink grant on the DCI. For operation with shared spectrum channel access, the UE can also retransmit on a configured grant. The UE can be configured to send code block group based transmissions, where retransmissions can be scheduled as a subset of all code blocks carrying a transport block.

[0465] Up to two HARQ-ACK codebooks corresponding to the priority (high / low) can be constructed simultaneously. For each HARQ-ACK codebook, more than one PUCCH for HARQ-ACK transmission within a time slot is supported. Each PUCCH is confined to one subslot, and a subslot mode is configured per HARQ-ACK codebook.

[0466] The HARQ function ensures delivery between peer entities at Layer 1. When the physical layer is not configured for downlink / uplink spatial multiplexing, a single HARQ process supports one TB, and when the physical layer is configured for downlink / uplink spatial multiplexing, a single HARQ process supports one or more TBs.

[0467] In the case of CA, the multi-carrier nature of the physical layer is exposed only to the MAC layer for which one HARQ entity is required per serving cell. In both uplink and downlink, there is one independent HARQ entity per serving cell, and in the absence of spatial multiplexing, one transport block is generated per allocation / grant per serving cell. Each transport block and its potential HARQ retransmissions are mapped to a single serving cell.

[0468] The physical uplink control channel (PUCCH) carries uplink control information (UCI) from the UE to the gNB. UCI includes at least hybrid automatic request acknowledgement (HARQ-ACK) information, scheduling request (SR) and channel state information (CSI).

[0469] UCI can be sent on PUCCH or multiplexed in PUSCH. UCI multiplexing in PUSCH is supported when UCI and PUSCH transmissions coincide in time due to the transmission of UL-SCH transport blocks or due to triggering A-CSI transmission in the absence of UL-SCH transport blocks:

[0470] - Multiplexing UCI carrying HARQ-ACK feedback with 1 or 2 bits by puncturing PUSCH;

[0471] - In all other cases, UCI is multiplexed with rate matched PUSCH.

[0472] For operation with a configured grant with shared spectrum channel access, the CG-UCI (Configured Grant Uplink Control Information) is sent in the PUSCH scheduled by the configured uplink grant. For operation with shared spectrum channel access, multiplexing of the CG-UCI and PUCCH carrying HARQ-ACK feedback may be configured by the gNB. If not configured, the PUSCH scheduled by the configured grant is skipped when the PUCCH overlaps with the PUSCH scheduled by the configured grant within the PUCCH group and the PUCCH carries HARQ ACK feedback.

[0473] Throughout this disclosure, embodiments are described in terms of multiple PDSCHs or multiple PUSCHs being jointly scheduled on multiple serving cells, such as a subset / set of cells among one or more co-scheduled sets of cells.

[0474] Embodiments may be applied to various other scenarios, such as when a UE is jointly scheduled to receive / transmit multiple PDSCH / PUSCH:

[0475] - For example, in distributed MIMO operation, from / to multiple transmit-receive points (TRPs) or other communicating entities, such as multiple distributed units (DUs) or multiple remote radio heads (RRHs), where the TRPs / DUs / RRHs may be associated with one or more cells; or

[0476] - in multiple time units, such as multiple time slots or multiple transmission time intervals (TTIs); or

[0477] - on multiple BWPs associated with one or more cells / carriers / TRPs, including multiple BWPs for a single serving cell / carrier for a UE with the capability to receive / transmit on multiple active BWPs; or

[0478] - on one or more TRPs / cells, where the UE may receive / transmit more than one PDSCH / PUSCH on each co-scheduled TRP / cell; or

[0479] - for multiple transport blocks (TBs), or for multiple code words (CWs) corresponding to a single TB or multiple TBs; or

[0480] - For multiple semi-persistently scheduled PDSCHs (SPS PDSCH) or for multiple configured granted PUSCHs (CG PUSCH) jointly activated on one or more TRPs / cells.

[0481] Therefore, any reference to "co-scheduled cells" may be replaced by / with "co-scheduled TRP / DU / RRH", or "co-scheduled timeslot / TTI", or "co-scheduled BWP", or "co-scheduled PDSCH / PUSCH", or "co-scheduled TB / CW", or "co-scheduled SPS-PDSCH / CG-PUSCH", etc. Similarly, for other related terms such as "multi-cell scheduling", etc.

[0482] Various embodiments of the present disclosure contemplate receiving multiple PDSCHs or sending multiple PUSCHs on a corresponding cell, including carriers of the same cell, such as on an UL carrier (also referred to as a normal UL (NUL) carrier) or a supplementary UL (SUL) carrier. Embodiments are also applicable to situations where scheduling is used for a mix of PDSCHs and PUSCHs. For example, a UE may receive a first PDSCH on a corresponding first cell and may send a second PUSCH on a corresponding second cell, wherein the first PDSCH and the second PUSCH are jointly scheduled.

[0483] In one embodiment, the UE may be provided with multiple co-scheduled cell sets by a higher layer. The term co-scheduled cell set is used to refer to a serving cell set, wherein the UE may be scheduled for PDSCH reception or PUSCH transmission on two or more cells in the co-scheduled cell set through a single DCI format or by using a supplementary method such as described herein. For ease of presentation, this DCI format may be referred to as a multi-cell scheduling DCI (MC-DCI) format. The MC-DCI format may be a new DCI format, such as DCI format 0_3 for a co-scheduled PUSCH or 1_3 for a co-scheduled PDSCH. In addition, the UE may be indicated via a DCI format in the PDCCH (such as an MC-DCI format) or via a MAC CE in a PDSCH in a subset of a co-scheduled cell set, wherein the cell subset may change across different PDCCH monitoring opportunities (Mo). For example, a first MC-DCI format in a first MO may indicate a first co-scheduled cell set / subset, and a second DCI format in a second MO may indicate a second co-scheduled cell set / subset.

[0484] In one example, multi-cell scheduling may also include operations related to DL / UL transmission, such as reporting HARQ-ACK information, beam / CSI measurement or reporting, sending or receiving UL / DL reference signals, etc.

[0485] In one example, the UE may be configured by a higher layer (such as through a UE-specific RRC configuration) with multiple sets of co-scheduled cells. For example, the UE may be configured with a first set of cells, such as {cell #0, cell #1, cell #4, cell #7} and a second set {cell #2, cell #3, cell #5, cell #6}. Multiple sets of co-scheduled cells may be scheduled from the same scheduling cell or from different scheduling cells.

[0486] In one example, the co-scheduled cell set may include a primary cell (PCell / PSCell) and one or more SCells. In another example, the co-scheduled cell set may include only SCells. In one example, the scheduling cell may belong to the co-scheduled cell set. In another example, the UE does not expect the scheduling cell to belong to the co-scheduled cell set.

[0487] In one example, according to the specification of the system operation, the co-scheduled cell set is defined as a set including all scheduled cells with the same scheduling cell, and no additional higher layer configuration is required to indicate the co-scheduled cell set. Therefore, the DCI format or other supplementary methods for multi-cell scheduling can jointly schedule any number of scheduled cells with the same scheduling cell. For example, the MC-DCI format can include a bitmap to indicate which scheduled cells are jointly scheduled.

[0488] In another example, the co-scheduled cell set may have two or more scheduling cells. For example, the UE may receive a DCI format for scheduling multiple co-scheduled cells on the first scheduling cell in the first PDCCH monitoring opportunity or on the second scheduling cell in the second PDCCH monitoring opportunity. The UE may receive a first MC-DCI format in the first PDCCH monitoring opportunity on the first scheduling cell for scheduling the co-scheduled cell set, and may receive a second MC-DCI format in the second PDCCH monitoring opportunity on the second scheduling cell for scheduling the co-scheduled cell set. The DCI format may be associated with any search space set type (CSS or USS), or may be restricted to being associated with a USS set. For example, the DCI format may be associated with multicast scheduling and have a CRC scrambled by a G-RNTI and PDCCH candidates monitored according to a CSS set, or may be associated with unicast scheduling and have a CRC scrambled by a C-RNTI and PDCCH candidates monitored according to a USS set. Such PDCCH monitoring from two scheduling cells may be simultaneous, such as in the same span of symbols or in the same time slot, or may be non-overlapping, such as in different time slots (as configured by a higher layer, or as indicated in the PDCCH or via a MAC CE). The UE may or may not expect that both the first scheduling cell and the second scheduling cell may schedule transmission or reception on the same cell via PDCCH transmissions in the same time interval (such as a span or time slot). The UE may also monitor the PDCCH to detect a DCI format that provides scheduling only on one cell in a set of co-scheduled cells (single-cell scheduling DCI format). For example, the UE may be configured to monitor the PDCCH on the first scheduling cell for single-cell scheduling on the serving cell, and monitor the PDCCH on the second scheduling cell for multi-cell scheduling on a set of co-scheduled cells including the serving cell.

[0489] The UE may report one or more of the following as capabilities to the gNB: the maximum number of co-scheduled cell sets, or the maximum number of cells within a co-scheduled cell set, or the maximum total number of co-scheduled cells across different sets, or the maximum number of co-scheduled cells per PDCCH monitoring occasion. In an example, the capability may depend on the operating band or frequency range such as above or below 6 GHz.

[0490] Multi-cell scheduling may be an optional UE feature with capability signaling that may additionally be separate for PDSCH reception and PUSCH transmission. For example, a UE may report a capability of a maximum number of {2,4,8,16} co-scheduled cells for DL ​​and a maximum number of {2,4} co-scheduled cells for UL. A UE may be configured with multiple sets / subsets of co-scheduled cells such that the size of the set / subset does not exceed the corresponding value reported by the UE capability. For example, a UE may be configured with a separate set of co-scheduled cells for PDSCH reception compared to the set of co-scheduled cells for PUSCH transmission.

[0491] The UE may also be configured with multiple cells that do not belong to any of the co-scheduled cell sets. For example, the UE may be configured with cell #8 that does not belong to the first set or the second set of co-scheduled cells in the previous example.

[0492] In one example, restrictions may apply to co-scheduled cells and the UE may expect co-scheduled cells in the corresponding set:

[0493] - have the same parameter set (SCS configuration and CP); or

[0494] - have the same set of parameters for the corresponding active DL / UL BWP; or

[0495] - have the same duplex configuration, for example, all cells have FDD configuration, or all cells have TDD configuration, and in the case of TDD configuration, also have the same UL-DL configuration; or

[0496] - within the same frequency band (intra-band CA) or within the same frequency range (such as FR1 or FR2 or FR2-1 or FR2-2); or

[0497] - Have the same license type, for example, all cells are licensed, or all cells are unlicensed.

[0498] In one example, if the scheduling cell belongs to a co-scheduled cell set, the above restrictions may not apply to the scheduling cell. For example, the scheduling cell may have a different SCS configuration than (other) cells in the co-scheduled cell set. For example, the scheduling cell may be in FR1 and FDD bands, and jointly schedule a co-scheduled cell set in FR2 and TDD bands.

[0499] The serving cell may belong to only a single co-scheduled cell set, such that the co-scheduled cell set does not include any common cells, or may belong to multiple co-scheduled cell sets to achieve greater scheduling flexibility for the serving gNB. For example, the serving cell may belong to a first co-scheduled cell set and a second co-scheduled cell set, such as when the cells in the first co-scheduled cell set and the second co-scheduled cell set have common characteristics (such as a common parameter set, duplex configuration, operating frequency band / range, etc.). In addition, when the serving cell has a first common characteristic with a cell in the first co-scheduled cell set and a second common characteristic with a cell in the second co-scheduled cell set, the serving cell may belong to both the first co-scheduled cell set and the second co-scheduled cell set, wherein the first common characteristic may be different from the second common characteristic. When a first cell using paired spectrum operation (FDD) and a second cell using unpaired spectrum operation (TDD) are in the same co-scheduled cell set, and a DCI format schedules a first PDSCH reception on the first cell and a second PDSCH reception on the second cell, and the second PDSCH reception includes symbols that are UL symbols on the second cell (e.g., as determined based on a UL-DL configuration provided by a SIB or by UE-specific RRC signaling), the UE does not receive the second PDSCH on the UL symbols, or does not receive the second PDSCH on any symbols on the second cell. Alternatively, the UE may apply rate matching to the second PDSCH around the UL symbols on the second cell, so that the UE receives the second PDSCH at an adjusted rate in the other remaining symbols. Similar UE behavior may be applied when the first scheduled cell and the second scheduled cell use unpaired spectrum operation with different UL-DL configurations (such as on different frequency bands).

[0500] In a first method, the UE is expected to be provided with multi-cell scheduling for all cells in a co-scheduled cell set. For example, for a first co-scheduled cell set including cells {cell #0, cell #1, cell #4, cell #7}, the DCI format schedules PDSCH reception or PUSCH transmission on all four cells in the first co-scheduled cell set {cell #0, cell #1, cell #4, cell #7}. When the UE is configured with a first co-scheduled cell set and a second co-scheduled cell set, in one example, the UE expects that there are no service / scheduled cells configured in both the first set and the second set (i.e., there is no overlap between the first set and the second set). In another example, the first set and the second set may have common elements, i.e., both the first set and the second set may include a first service / scheduled cell. For example, the latter may be applied when both the first set and the second set correspond to the same scheduling cell. For example, the first cell may be a scheduling cell. In one example, the MC-DCI format needs to indicate a co-scheduled cell set in multiple co-scheduled cell sets. For example, the first MC-DCI may indicate a first co-scheduled cell set to jointly schedule all cells in the first co-scheduled cell set, and the second MC-DCI may indicate a second co-scheduled cell set to jointly schedule all cells in the second co-scheduled cell set.

[0501] In a second approach, the UE may be provided with multi-cell scheduling for a subset of the co-scheduled cell set. For example, the DCI format may schedule PDSCH reception or PUSCH transmission on only two cells (such as {cell #0, cell #4}) in the first cell set.

[0502] In the first option of the second method, the cell subset may be indicated by a MAC CE. Such a MAC CE command may include one or more of the following items: an indication for activating or deactivating / releasing a cell subset; an indication of the number of co-scheduled cell sets; or an indication of the number of co-scheduled cell subsets in a corresponding number of co-scheduled cell sets.

[0503] For example, a MAC CE activates a first subset of a co-scheduled cell set, and a subsequent DCI format for multi-cell scheduling is applied to the first subset of cells activated by the MAC CE. The UE may receive another MAC CE command that deactivates the first subset of co-scheduled cells, or activates a second subset of co-scheduled cells, where the second subset may be a subset of the same set of co-scheduled cells or a subset of a different set of co-scheduled cells. If the UE receives a MAC CE that deactivates the first subset of co-scheduled cells but does not activate the second subset of co-scheduled cells, then in one alternative, the UE does not expect to receive a DCI format for multi-cell scheduling, and the UE may not monitor the PDCCH according to the corresponding search space set until the UE receives a new MAC CE that activates the second subset of co-scheduled cells. In another alternative, the UE may receive a DCI format for multi-cell scheduling even before receiving a new MAC CE that activates the second subset of co-scheduled cells, but the UE expects to be provided with an indication of the co-scheduled cell subset for multi-cell scheduling through the DCI format or by using a supplementary method (such as those described herein).

[0504] In a second option of the second method, a subset of the set of co-scheduled cells may be provided by a DCI format in the PDCCH / PDSCH. The subset of cells may change between PDCCH monitoring occasions (MOs) for PDSCH / PUSCH scheduling, as indicated by the corresponding DCI format. For example, a first MC-DCI format in a first PDCCH MO indicates PDSCH or PUSCH scheduling on a first subset of cells, while a second MC-DCI format in a second PDCCH MO indicates PDSCH or PUSCH scheduling on a small second subset of cells.

[0505] In a first example, a DCI format for multi-cell scheduling provides an index for a subset of cells that are co-scheduled, such as a CIF value corresponding to a subset of one or more cells in a co-scheduled cell set. For example, UE-specific RRC signaling may indicate a first / second / third / fourth index and a corresponding first / second / third / fourth subset, the first / second / third / fourth subset including one or more cells in a co-scheduled cell set, wherein the subset may also include all cells in a co-scheduled cell set. Then, a 2-bit CIF field in the DCI format may provide a value indicating a scheduled cell subset. Such a CIF generally refers to a co-scheduled cell set, rather than a single scheduled cell, and may therefore be referred to as a "set-level" CIF (compared to the latter's "cell-level" CIF). A UE may be provided with a separate configuration of a first number of co-scheduled cell sets / subsets for PDSCH reception, compared to a second number of co-scheduled cell sets / subsets for PUSCH transmission. Therefore, a UE may be provided with a first index set of set-level CIFs for PDSCH reception, which is different from a second index set of set-level CIFs for PUSCH transmission. For example, a UE may be provided with 4 bits of an "aggregation level" CIF for PDSCH reception and 3 bits of an "aggregation level" CIF for PUSCH transmission.The aggregation level CIF may also be referred to as a cell aggregation indicator function value or a carrier aggregation indicator function value.

[0506] In one example, when a two-stage approach is used to jointly schedule a set / subset of co-scheduled cells, as described herein, when the first-stage DCI is on the first PDCCH on the first cell, and the second-stage DCI is on the first PDSCH on the second cell, and the first PDSCH schedules the second PDSCH / PUSCH, in one option, the UE still considers the scheduling cell for the second PDSCH / PUSCH to be the first cell, and defines the corresponding CIF association relative to the first cell and its configuration. In another option, the UE considers the scheduling cell for the second PDSCH / PUSCH to be the second cell, and defines the corresponding CIF association relative to the second cell and its configuration.

[0507] In a second example, the DCI format may include a 1-bit flag field to indicate whether the DCI format is for single-cell scheduling or for multi-cell scheduling, and in order for the UE to interpret the field of the DCI format accordingly, the field may also include a CIF field. Then, for single-cell scheduling, the CIF field can be interpreted as in the case of single-cell cross-carrier scheduling, and for multi-cell scheduling, the CIF field can be interpreted as indicating a subset of a set of cells for collaborative scheduling. In one example, instead of an explicit 1-bit flag for indicating single-cell scheduling or multi-cell scheduling, the UE can be configured with multiple sets / subsets of collaboratively scheduled cells, some of which include only one scheduled cell, while others include more than one scheduled cell. Therefore, the CIF value for single-cell scheduling can be separated from the CIF value for multi-cell scheduling. For example, CIF values ​​0, 1, 2, 3 correspond to scheduling individual cells, CIF values ​​4, 5, 6, 7 correspond to sets / subsets of collaboratively scheduled cells, and the function of the 1-bit flag can be absorbed in the CIF. Therefore, the UE can determine whether the DCI format is for single-cell scheduling or for multi-cell scheduling based on the CIF value.

[0508] In a third example, a DCI format for multi-cell scheduling provides multiple co-scheduled cells, and the indices of the co-scheduled cells are provided by an additional method, such as by an additional DCI format or by higher layer signaling as described herein.

[0509] In a fourth example, the CIF field in the DCI format for multi-cell scheduling can be a bitmap mapped to each cell or a subset of cells in a set of co-scheduled cells. For example, when the UE is configured with a maximum number of N scheduled cells (such as N=8 cells) associated with a scheduled cell, the UE can be configured with a bitmap having N bits, wherein the value of a bit in the bitmap "1" indicates scheduling on the corresponding cell, and the value of a bit in the bitmap "0" indicates no scheduling on the corresponding cell. For example, the bitmap can be in ascending or descending order of the cell index or (cell level) CIF value or cell index of the scheduled cell. For example, the leftmost bit (respectively, the rightmost bit) can correspond to a scheduled cell with a minimum cell index or cell level CIF, and the second left bit (respectively, the second right bit) can correspond to a scheduled cell with a second small cell index or cell level CIF, and so on. For example, if the UE is configured with a number of M scheduled cells (such as M=4 cells), which is less than the maximum supported number of N scheduled cells (such as N=8 cells), then in one option, the bitmap may include 8 bits, and the remaining rightmost (respectively, the remaining leftmost) MN bits (such as 8-4=4 bits) can be all zero or all one. In another option, the bitmap can include only M=4 bits.

[0510] In a third option of the second method, the UE can implicitly determine the index of the co-scheduled cell without explicit gNB indication. For example, the UE can determine the index of the co-scheduled cell based on PDCCH monitoring parameters, such as:

[0511] -CORESET index; or

[0512] - a search space set index, or a carrier indicator parameter n_CI corresponding to the search space set index; or

[0513] - The set of CCEs in a search space set or the first / last CCE in a search space set;

[0514] The UE receives a PDCCH providing a DCI format for multi-cell scheduling.

[0515] According to a third option, the UE can be configured with a mapping between a value of a PDCCH monitoring parameter (such as a search space set) and the number of co-scheduled cells or an index of a co-scheduled cell. In an example, a first value and a second value of a parameter n_CI in the search space set can indicate a first and a second co-scheduled cell subset, respectively. According to this example, the parameter n_CI can correspond to a single cell or can correspond to a group of cells, such as a co-scheduled cell subset / set.

[0516] In the fourth option, the UE can implicitly determine the set of co-scheduled cells based on other fields in the MC-DCI format without the need for an explicit CIF field. For example, when the UE is provided with a joint TDRA table for multi-cell scheduling, the index of the joint TDRA table can indicate the set / subset of co-scheduled cells. For example, an entry / row in the joint TDRA table configured by the RRC includes first TDRA information for a first cell and second TDRA information for a second cell, and so on, while the entry may not include information for a third cell. Therefore, when the MC-DCI format includes an indication of an entry / row of the joint TDRA table, it implies that the first and second cells are jointly scheduled by the MC-DCI format, while the third cell is not scheduled. In one example, in addition to TDRA, other DCI fields with joint indications, such as the FDRA field, may be used.

[0517] In another example, the UE expects the MC-DCI to include a number N TDRA fields corresponding to the maximum number N of supported / configured scheduling cells for scheduling cells, wherein a certain value of the TDRA field, such as all zeros or all ones, is reserved to indicate that there is no scheduling on the corresponding cell. Therefore, when the MC-DCI receives an MC-DCI format including M TDRA fields (of the N TDRA fields) with reserved values, the UE determines that the MC-DCI does not schedule the corresponding M cells and only jointly schedules NM cells. In one example, in addition to TDRA, other DCI fields with separate indications, such as the FDRA field, can be used.

[0518] In another example, when a HARQ process number (HPN) field or a redundant version field or a new data indicator field is provided separately for each scheduled cell in the MC-DCI format and a combination of those fields (such as all those fields) has the same value for the co-scheduled cell subset (such as HPN 15 (counting from 0 to 15 for a 4-bit HPN field), RV1 and NDI1), the co-scheduled cell subset can be assumed to be not scheduled by the MC-DCI format.

[0519] In another example, when an MCS field is provided separately for each scheduled cell in the MC-DCI format and the MCS field has a predetermined value (such as 0) for the co-scheduled cell subset, the co-scheduled cell subset can be assumed to be not scheduled by the MC-DCI format.

[0520] Reception or transmission on a corresponding subset of cells co-scheduled by a single DCI format or by using supplementary methods such as those described herein can indicate PDSCH or PUSCH that may or may not overlap in time. For example, the UE can be instructed to receive PDSCH or transmit PUSCH on the corresponding co-scheduled cells, where all reception / transmission are in the same time slot, or at least one reception / transmission is in a time slot different from the remaining time slots.

[0521] A UE configured for multi-cell scheduling can be provided with a first set of cell-common parameters and a second set of cell-specific parameters, wherein the values ​​of the cell-common parameters apply to scheduling on all co-scheduled cells, and the values ​​of the cell-specific parameters apply to scheduling on each corresponding co-scheduled cell. The UE can determine the cell-common and cell-specific scheduling information parameters based on the specifications of the system operation, or based on a higher layer configuration. For some cell-specific scheduling information parameters, the UE can be provided with a difference compared to a reference value, wherein the reference value can correspond to, for example, the first scheduled cell in a set of scheduled cells. For example, the reference value can correspond to the scheduled cell with the smallest cell index or the smallest (cell level) CIF value.

[0522] For a UE configured with multiple sets of co-scheduled cells, the DCI format for multi-cell scheduling can provide complete or partial information for cell-common or cell-specific scheduling parameters for multiple PDSCH receptions or multiple PUSCH transmissions on the corresponding multiple co-scheduled cells. When the DCI format for multi-cell scheduling provides partial information for scheduling parameters, the UE can determine the remaining information from UE-specific RRC signaling or through other supplementary methods.

[0523] In one embodiment, for a UE configured with a co-scheduled cell set, the DCI format for multi-cell scheduling can provide all or part of the information of the values ​​of the cell common field and the cell specific field for scheduling PDSCH reception or PUSCH transmission on the corresponding two or more cells in the co-scheduled cell set. When the DCI format provides part of the information, the UE can determine the remaining information from the RRC signaling or by using other supplementary methods.

[0524] In a first approach (referred to as a concatenated DCI format for multi-cell scheduling), a single DCI format may include information on all scheduling parameters for all co-scheduled PDSCH receptions or PUSCH transmissions, except for some information that may be provided by a higher layer or predetermined by a specification for system operation or implicitly determined by the UE. For example, the MC-DCI format can provide separate field values ​​for PDSCH reception or PUSCH transmission on each of multiple co-scheduled cells. The first value corresponds to the first cell, the second value corresponds to the second cell, and so on. Thus, the DCI format fields for multiple cells are concatenated, so that such a DCI format is referred to as a concatenated DCI format for multi-cell scheduling. The method can be beneficial, for example, for co-scheduling cells with different channel characteristics or configurations, such as for inter-band CA operation, or for co-scheduling PDSCH reception and PUSCH transmission. Some DCI fields can be common to cells and provided only once in the concatenated DCI format. In one example, the functionality of a field in a first DCI format that schedules PDSCH reception or PUSCH transmission on a single cell and provides information for multiple cells (such as the SCell sleep indicator field described in TS 38.213v17.1.0) can remain the same in a second DCI format that schedules PDSCH reception or PUSCH transmission on multiple cells, and the field can remain as in the first DCI format. Alternatively, such a field can be omitted from the second DCI format.

[0525] In a second method (referred to as multi-cell scheduling via multi-cell mapping), multi-cell mapping can be used to provide information for multi-cell scheduling of multiple PDSCH / PDCCHs on multiple corresponding cells to the UE, wherein a field in the DCI format can be interpreted to provide multiple values ​​for corresponding scheduling parameters of multiple co-scheduled cells. This interpretation can be based on a configured one-to-many mapping / table or based on multiple configuration offset values ​​for the corresponding cells applied to a reference value indicated by the DCI format. For example, the field can be an MCS field, wherein the value indicated in the DCI format can be used for PDSCH reception on a first cell, and the value for PDSCH reception on a second cell can be determined from the first value and the configuration offset value. The same MCS value can also be applicable to all PDSCH receptions or PUSCH transmissions. The method can be beneficial, for example, for co-scheduling cells having some similar physical channel characteristics or configurations, such as for intra-band CA operations.

[0526] In a third method (referred to as single-cell DCI pointing to PDSCH with multi-cell scheduling), information for multi-cell scheduling can be provided to a UE using a single-cell scheduling DCI format (i.e., a DCI format that schedules a first PDSCH on a first cell), wherein the first PDSCH includes scheduling information for receiving a second PDSCH (or multiple) or sending a second PUSCH (or multiple) on a subset of one or more co-scheduled cell sets. The method can be beneficial, for example, for co-scheduling a number (such as 4-8) of cells with different channel characteristics or configurations, such as for inter-band CA operation.

[0527] In the first option of the third method, the first PDSCH includes a MAC CE that provides scheduling information for multiple PDSCHs (or multiple) or PUSCHs (or multiple). Therefore, the MAC CE may include multiple modified DCIs (M-DCIs), wherein each M-DCI includes all or part of the scheduling information of the PDSCH / PUSCH from multiple PDSCHs (or multiple) / PUSCHs (or multiple).

[0528] In the second option of the third method, multi-cell scheduling information is multiplexed as M-DCI in the PDSCH. The UE receives a first PDSCH scheduled by a single-cell scheduling DCI format, and the UE receives additional scheduling information for one or more PDSCH(s) / PUSCH(s) on one or more corresponding co-scheduled cells(s). In addition to the reserved resources corresponding to the reference signal or other cell-level broadcast transmission, the UE allocates the coded modulation symbols for the M-DCI to the time / frequency resources within the first PDSCH, for example, in a frequency-first, time-second manner. The UE can start receiving the M-DCI in the first symbol of the first PDSCH, or in the first symbol after the first symbol with DM-RSRE in the first PDSCH. The M-DCI can be jointly encoded and include a single CRC.

[0529] In a second option, the physical layer processing of the M-DCI(s) included in the first PDSCH may be the same as the physical layer processing used for the DCI in the PDCCH, such as the DCI used to schedule the first PDSCH, or may be the same as the physical layer processing used for the data information / transport block in the first PDSCH. In this context, the physical layer processing indicates, for example, modulation, coding, scrambling, etc. Additionally, the UE may be able to adjust the M-DCI based on a scaling factor of the total (coded) payload size applied to the M-DCI. To determine a number of coded modulation symbols corresponding to multi-scheduling information (such as M-DCI) multiplexed in the first PDSCH scheduled by the single-cell scheduling DCI format. This scaling factor determines the effective channel coding rate of the M-DCI multiplexed on the first PDSCH to achieve flexible link adaptation and improved reliability of the M-DCI according to the physical channel conditions. Scaling factor The value of can be provided by higher layers, or can be indicated by a field in the DCI format in the PDCCH from a set of values ​​provided by higher layers, such as by indicating from four A 2-bit field indicating the value of a set of values.

[0530] In a fourth method (referred to as multi-stage PDCCH / DCI for multi-cell scheduling), a multi-stage DCI method (such as 2-stage DCI) can be used to provide a UE with information for multi-cell scheduling of multiple PDSCH / PUSCH on multiple corresponding cells, wherein, for example, the first-stage DCI format includes a set of cell common fields and the second-stage DCI format includes cell-specific fields. The UE receives the first-stage DCI format in the first PDCCH and receives the second-stage DCI format in the second PDCCH. The first PDCCH and the second PDCCH are linked. In one example, the first PDCCH and the second PDCCH are in the same search space set. This method can be beneficial, for example, for co-scheduling some cells having some common physical characteristics, such as time domain resource allocation or frequency domain resource allocation using the first-stage DCI format, and when the second PDCCH is received in the same time slot as the first PDCCH, it will not incur a delay or have (if the first-stage and second-stage DCI formats are combined into a single DCI format, this will result in) too large a DCI format size for receiving cell-specific parameters. The first stage DCI format can also indicate the time / frequency resources used to provide the PDCCH of the second stage DCI format, such as the index of the PDCCH candidate for the corresponding CCE aggregation level, so that the UE can interpret the content of the second stage DCI format or reduce the number of PDCCH receptions. The UE can determine the association between multiple linked multi-stage PDCCHs / DCIs (such as two PDCCHs / DCIs) providing multi-cell scheduling information based on the parameters of the linked DCI format (such as the size (or multiple) of the DCI format (or multiple) or the RNTI (or multiple) associated with the DCI format (or multiple)) or through explicit indications in some fields (or multiple) in the DCI format (or multiple) or based on PDCCH monitoring parameters (such as CORESET, search space, CCE or the monitoring opportunity in which the UE receives the first and second linked PDCCHs).

[0531] In one embodiment, when the UE is configured with a co-scheduled cell set including a first cell, the UE is capable of receiving a PDCCH with a DCI format that schedules PDSCH reception or PUSCH transmission only on the first cell (single-cell scheduled DCI format). The UE is capable of distinguishing the single-cell scheduled DCI format from the multi-cell scheduled DCI format via various methods, such as the DCI format size, or the RNTI used to scramble the CRC of the DCI format for multi-cell scheduling, or by an explicit indication of a field in the DCI format, or by a dedicated CORESET and associated search space set.

[0532] In a first example, the first DCI format size for multi-cell scheduling can be different from the second DCI format size for single-cell scheduling. The first DCI format size can be such that it can include a field identifying a set of co-scheduled cells (such as a set-level CIF) and possibly multiple fields, such as cell-common scheduling parameters, to enable the UE to decode the remaining scheduling information, or provide PDCCH candidates for the second stage DCI format.

[0533] In the second example, the same DCI format size is used for multi-cell scheduling and for single-cell scheduling, for example, to avoid increasing the number of DCI format sizes that the UE needs to decode in order to support multi-cell scheduling with a single DCI format. Therefore, various methods can be considered to identify whether a DCI format performs single-cell scheduling or multi-cell scheduling, as described below.

[0534] PDSCH reception or PUSCH transmission on any cell in the co-scheduled set of cells can be scheduled by a DCI format that does not schedule any other PDSCH reception or PUSCH transmission on any other cell in the co-scheduled set of cells, such as, as an example, by a DCI format that does not have multi-cell scheduling capability, or when there is no traffic associated with other cells. For example, for a UE configured for cross-carrier scheduling for a co-scheduled set of cells by a scheduling cell, the UE can receive a first PDCCH and a second PDCCH on the scheduling cell, the first PDCCH including a first DCI format for scheduling a single cell from a plurality of co-scheduled cells, and the second PDCCH including a second DCI format for scheduling all cells in the co-scheduled set of cells.

[0535] Herein, the DCI format for multi-cell scheduling can indicate, for example, one or more or a combination of the following items:

[0536] - a concatenated DCI format for multi-cell scheduling; or

[0537] -DCI format based on multi-cell mapping; or

[0538] - a set of the first DCI format or the second DCI format or the M-DCI in the first PDCCH or the M-DCI included in the first PDSCH scheduled by the first DCI / PDCCH; or

[0539] - a first DCI format in a first PDCCH or a second DCI format in a second PDCCH, wherein the first DCI / PDCCH and the second DCI / PDCCH are linked in a two-stage DCI operation;

[0540] Among others, the above terms and procedures are described herein.

[0541] In the first method, the UE can distinguish multi-cell scheduling from single-cell scheduling based on one or more dedicated DCI formats or DCI format sizes for multi-cell scheduling that are not used for single-cell scheduling. For example, the UE can be configured with DCI format 0_3 for sending multiple PUSCHs or DCI format 1_3 for receiving multiple PDSCHs on a set of co-scheduled cells. The dedicated size of the DCI format for multi-cell scheduling can also depend on the number of co-scheduled cells or the set of cell-common or cell-specific scheduling parameters for multi-cell scheduling. The dedicated DCI format size for sending multiple PUSCHs can be different from the dedicated DCI format size for receiving multiple PDSCHs on a set of co-scheduled cells.

[0542] In one example, when a UE is configured with a dedicated DCI format or DCI format size for multi-cell scheduling, the UE is expected to support a larger number of DCI format sizes than when the UE operates with only single-cell scheduling. For example, a UE that supports multi-cell scheduling (through a single DCI format) can be expected to support one or two additional DCI format sizes, or can indicate one or two additional DCI format sizes as a capability, compared to a UE that does not support multi-cell scheduling through a single DCI format. The UE counts the number of sizes for DCI formats per serving cell based on the number of configured PDCCH candidates in the corresponding search space set for the corresponding active DL BWP.

[0543] In order to avoid the UE requiring a larger number of DCI format sizes to support multi-cell scheduling and to avoid segmentation of multiple PDCCH candidates that the UE can monitor over an increased number of DCI format sizes, it is beneficial to provide additional means for distinguishing multi-cell scheduling from single-cell scheduling by means other than DCI format size. The DCI format for multi-cell scheduling can have the same size as the DCI format for single-cell scheduling.

[0544] In one example, an existing single-cell scheduling DCI format (such as one of the DCI formats supported in [TS 38.212, v17.1.0]) can be reused for multi-cell scheduling, for example, by reinterpreting existing fields or taking into account new / increased / configurable bit widths of existing fields or by adding new fields (or multiple). Herein, the UE determines the presence (or absence) of a reinterpreted / modified / new DCI field based on whether the CIF value indicates a single scheduled cell or a co-scheduled cell set / subset. Therefore, the reinterpreted / modified / new DCI field follows the multi-cell scheduling configuration provided for the co-scheduled cell set indicated by the (set level value of) the CIF field.

[0545] In another example, the size / bit width of one or more DCI fields for multi-cell scheduling (including their presence or absence) can be configured based on a higher-level configuration for the corresponding co-scheduled cell set or for any co-scheduled cell set / subset associated with the same scheduling cell.

[0546] In the second method, the UE can distinguish multi-cell scheduling based on a new / dedicated RNTI (such as M-RNTI) used to scramble the CRC of the DCI format for multi-cell scheduling. For example, such RNTI can be configured by UE-specific RRC signaling.

[0547] In a third method, the UE is able to distinguish multi-cell scheduling based on an explicit field or indication in the DCI format used for multi-cell scheduling. For example, the DCI format may include a 1-bit flag, where a value of "1" corresponds to multi-cell scheduling and a value of "0" corresponds to single-cell scheduling. In one example, there can be a restriction on the size of the DCI format used for multi-cell scheduling. For example, the UE does not expect the DCI format used for multi-cell scheduling to have the same size as the fallback DCI format (0_0 or 1_0) or the "compact" DCI format (0_2 or 1_2). Therefore, the 1-bit flag for indicating single-cell scheduling compared to multi-cell scheduling only exists in certain DCI formats, such as "normal" DCI formats 0_1 or 1_1.

[0548] In one example, the UE can distinguish multi-cell scheduling based on the verification process of the DCI format for single-cell scheduling. For example, when the value of one or more DCI fields in the DCI format for single-cell scheduling is set to a default / predetermined value, the UE determines that the DCI format is for multi-cell scheduling. In the example, for the case of multi-cell scheduling, one or more DCI fields corresponding to cell-specific scheduling parameters (such as HPN, RV, SRI, TCI state, AP, TDRA, FDRA or MCS) can be set to all zero or all one values.

[0549] In a fourth method, the UE can distinguish multi-cell scheduling based on a CORESET associated with a search space set that is configured to receive a PDCCH providing a DCI format for multi-cell scheduling. For example, the UE can be configured with a dedicated CORESET for multi-cell scheduling so that the search space set for multi-cell scheduling does not overlap with the search space set not used for multi-cell scheduling.

[0550] In one example, a combination of the above options can be used. For example, for multi-cell scheduling based on the first-stage DCI format and the second-stage DCI format, the UE determines the DCI format (in the first PDCCH) that is scrambled by the new / dedicated RNTI (such as M-RNTI) and also satisfies the aforementioned verification process as the first-stage DCI format, and the second-stage DCI format may be included in the PDSCH scheduled by the first-stage DCI format or in another PDCCH, as described herein.

[0551] Fig.10 An example method 1000 for distinguishing a multi-cell scheduling DCI format from a single-cell scheduling DCI format according to an embodiment of the present disclosure is shown. Fig.10 The embodiment of the method 1000 for distinguishing a multi-cell scheduling DCI format from a single-cell scheduling DCI format shown in FIG. 1 is for illustration only. Fig.10 The scope of the present disclosure is not limited to any particular implementation of the method 1000 for distinguishing a multi-cell scheduling DCI format from a single-cell scheduling DCI format.

[0552] like Fig.10 As shown, method 1000 begins at step 1010, wherein a UE (such as UE 116) is configured with a first DCI format or a first RNTI for single-cell scheduling, and a second DCI format or a second RNTI for multi-cell scheduling. At step 1020, the UE receives a PDCCH providing a DCI format. At step 1030, the UE decodes the DCI format based on the first size or the second size or based on the first RNTI or the second RNTI used to scramble the CRC. At step 1040, the UE determines whether the decoded DCI format has the first size or the second size, or has a CRC scrambled by the first RNTI or the second RNTI. At step 1050, when the DCI format has the first size or has a CRC scrambled by the first RNTI, the UE determines that the DCI format performs single-cell scheduling. At step 1060, when the DCI format has the second size or a CRC scrambled by the second RNTI, the UE determines that the DCI format performs multi-cell scheduling.

[0553] In one embodiment, when the cell scheduled by the UE is configured for multi-cell scheduling of a co-scheduled cell set, the UE is able to determine the association between the search space set used for multi-cell scheduling and a subset of the co-scheduled cell set based on a modified interpretation of the value n_CI of the CIF field in the DCI format performing multi-cell scheduling.

[0554] In a first approach, the UE can be configured with a search space set to monitor only the DCI format (MC-DCI format) used for multi-cell scheduling. This search space set dedicated to multi-cell scheduling can be called a multi-cell search space (MSS) set. As described, the MC-DCI format can also be used for scheduling on a single cell. The configuration of the MSS set is beneficial, for example, to allow the UE to monitor the PDCCH of the MC-DCI format more frequently (or less frequently) than the SC-DCI format, or to allocate PDCCH candidates that are more suitable for the MC-DCI format, such as more PDCCH candidates for a larger AL, which is more compatible with the larger size used for the MC-DCI format and may be unnecessary for the smaller size used for the SC-DCI format.

[0555] In one example, each of such search space sets can have a corresponding identifier, such as an n_CI value associated with a CIF field in a DCI format that performs multi-cell scheduling, so that there is a separate MSS set and corresponding n_CI value for each set / subset of co-scheduled cells. CI value.

[0556] In another example, the UE can be configured with a set of MSSs for a scheduled cell, which corresponds to a plurality of sets / subsets of co-scheduled cells and corresponding n associated with the scheduled cells. CI Therefore, the UE can receive PDCCH candidates and decode various DCI formats for multi-cell scheduling for different co-scheduled cell sets according to the PDCCH monitoring opportunity determined based on the MSS set configuration. The PDCCH candidates and associated non-overlapping CCEs can be different for different co-scheduled cell sets / subsets, corresponding to different n CI For example, the UE can calculate the value of n based on the formula CI Values ​​to determine PDCCH candidates corresponding to different co-scheduled cell sets / subsets from the same MSS set:

[0557]

[0558] n CI The association of the value with the co-scheduled cell set / subset can be provided by higher layer signaling, for example, within the MSS set configuration or in an RRC Information Element (IE) related / similar to cross-carrier scheduling, or in a separate RRC IE.

[0559] For example, the MSS set can be used to support scheduling of all co-scheduled cell sets / subsets and support all corresponding n associated with the scheduled cells. CIFor example, the UE can be configured with multiple MSS sets corresponding to the same co-scheduled cell set / subset. For example, the UE can be configured with multiple MSS sets corresponding to all co-scheduled cell sets / subsets associated with the scheduling cell.

[0560] In yet another example, the UE can be configured with multiple MSS sets for each scheduled cell, for example, to accommodate different PDCCH monitoring opportunities (such as different periodicities and time slot offsets) or to increase flexibility in configuration / association with different co-scheduled cell sets. For example, a first MSS set can correspond to a first number of co-scheduled cell sets / subsets associated with a scheduled cell, and a second MSS set can correspond to a second number of co-scheduled cell sets / subsets associated with a scheduled cell. The first number of co-scheduled cell sets / subsets can have no overlap or can have some overlap with the second co-scheduled cell set / subset. According to this example, the UE is provided with higher layer signaling indicating which n CI The value and the corresponding co-scheduled cell set / subset are associated with the first MSS set or the second MSS set. Such information can be provided, for example, within the configuration information of the first or second MSS set or in a separate RRC IE (such as RRC IE related / similar to cross-carrier scheduling).

[0561] An example of an information element SearchSpaceMultiCell is provided, where the UE can be configured to monitor only DCI formats for multi-cell scheduling. In this document, DCI formats 0_4 and 1_4 are considered to be DCI formats for uplink multi-cell scheduling and downlink multi-cell scheduling, respectively. In this example, the MSS set is associated with only one co-scheduled cell set indicated by coScheduledSetId. In this document, cif-set-InSchedulingCell indicates the CIF or n corresponding to the corresponding co-scheduled cell set. CI Values, for example, as provided in the MultiCellSchedulingConfig IE discussed further below.

[0562] Search Space Information Element - SearchSpaceMultiCell

[0563]

[0564]

[0565] Another example of an information element SearchSpaceMultiCell is provided, wherein an MSS set is associated with multiple co-scheduled cell sets / subsets, as indicated by coScheduledSetId. In one example, when coScheduledSetId is not present in the SearchSpaceMultiCell configuration of the MSS set, the MSS set is associated with all co-scheduled cell sets / subsets corresponding to the respective scheduled cells. In another example, when coScheduledSetId is not present in the SearchSpaceMultiCell configuration of the MSS set, the UE is able to determine the association of the MSS set with different co-scheduled cell sets / subsets based on an implicit method (such as a multi-cell extension of the UE procedure for search space linking), as described subsequently. In this document, cif-set-InSchedulingCell indicates a CIF or n corresponding to the corresponding co-scheduled cell set. CI Values, for example, as provided in the MultiCellSchedulingConfigIE discussed further below.

[0566] Search Space Information Element - SearchSpaceMultiCell

[0567]

[0568]

[0569]

[0570] In the second method, the UE is configured to monitor a set of search spaces of a PDCCH that provides a DCI format capable of performing both single-cell and multi-cell scheduling.

[0571] An example of an update to the SearchSpace information element is provided by the "SearchSpace information element", where a UE can be configured to monitor DCI formats for both multi-cell scheduling and single-cell scheduling.

[0572] SearchSpace Information Element

[0573]

[0574]

[0575]

[0576]

[0577] In one example, the search space set for the co-scheduled cell set can be a UE-specific search space (USS) set defined by an n_CI parameter, which is generalized to apply to a configured co-scheduled cell set instead of a single scheduled cell. For example, n_CI or CIF=0 can indicate self-carrier scheduling, n_CI or CIF in the set {1, 2, ..., 7} can indicate cross-carrier scheduling of a single scheduled cell, and n_CI or CIF in the set {8, 9, ..., 15} can indicate cross-carrier scheduling of one of eight co-scheduled cell subsets in the co-scheduled cell set. In one example, the existing CIF values ​​{0, 1, 2, ..., 7} are sufficient for both single-cell and multi-cell scheduling, and the UE can be provided by a higher layer with an association between the CIF value and a single cell or a co-scheduled cell set. For example, CIF values ​​{0, 1, 2, 3} can be associated with single-cell scheduling for four different scheduled cells, and CIF values ​​{4, 5, 6, 7} can be associated with multi-cell scheduling for four different co-scheduled cell sets. CIF association for a set (or multiple) of cells for cooperative scheduling can be provided through an extension of the cross-carrier scheduling information element (IE) or through a separate IE. In one example, the value range of CIF can be extended to, for example, {0, 1, ..., 15}, where the specific division of the extended value range between cell-level CIF values ​​and set-level CIF values ​​can depend on the gNB configuration. For example, the UE can be configured with {0, 1, ..., 4} for cell-level CIF values, and {5, 6, ..., 15} for set-level CIF values.

[0578] The search space for determining the CCE position of the PDCCH candidate can be provided as:

[0579]

[0580] Among them, all parameters are defined as in the case of single cell scheduling, and the value of the n_CI parameter is provided by the RRC configuration, as described above. In addition, the initial value Y p,-1 =n RNTI ≠0 can be based on C-RNTI or based on RNTI, such as M-RNTI, for multi-cell scheduling.

[0581] In one example, if the UE is configured to have only one co-scheduled cell set associated with the scheduling cell, such as when the co-scheduled cell set includes all scheduling cells corresponding to the scheduling cell, then n may be used. CI A single value, such as n CI=8. Such a value can be fixed in the specification of the system operation. For example, the DCI format can exclude the CIF value. For example, the DCI format can include a flag to indicate single-cell scheduling (e.g., flag value=0) or multi-cell scheduling (e.g., flag value=1), and when the flag indicates (value 0, thus) single-cell scheduling, the CIF is present in the DCI format, and when the flag indicates (value 1, thus) multi-cell scheduling, the DCI format does not include the CIF.

[0582] In one example, n CI Can be the same as the one used by the field in the DCI format to indicate a subset of scheduled cells. For example, for a set of 4 cells {cell #0, cell #1, cell #2, cell #3}, when there are four possible values ​​n indicating scheduling on {cell #0, cell #1}, {cell #2, cell #3}, {cell #0, cell #2} and {cell #0, cell #1, cell #2, cell #3} respectively CI =0, 1, 2, 3, it can be based on n CI =0, 1, 2, 3 to determine the search space for the corresponding PDCCH candidate.

[0583] In another example, if the UE can be configured to have multiple co-scheduled cell sets associated with the scheduling cell, there can be multiple co-scheduled cell sets associated with the scheduling cell and n CI Various options for mapping between values.

[0584] In the first option, the UE receives higher layer signaling, such as a dedicated RRC configuration, which provides the set of cells for co-scheduling. CI For example, n can be provided in the configuration information of the corresponding search space set for multi-cell scheduling or in an RRC information element (IE) related / similar to cross-carrier scheduling or in a separate RRC IE. CI Association of the value with the set / subset of co-scheduled cells.

[0585] An example is provided below, in which the MultiCellSchedulingConfig IE can be configured, for example, within the ServingCellConfig IE of the corresponding scheduling cell, so that no explicit indication of the scheduling cell is required. In addition, the individual / cell level CIF value corresponds to the corresponding value provided in the CrossCarrierSchedulingConfig IE for the corresponding serving / scheduled cell associated with the corresponding scheduling cell. The UE does not expect the individual / cell level CIF value configured for the serving / scheduled cell in the CrossCarrierSchedulingConfig IE to be reused as the set level CIF value for the co-scheduled cell set in the MultiCellSchedulingConfig IE. In this article, maxNrofCoScheduledSets indicates the maximum supported number of co-scheduled cell sets for any scheduling cell, and can be a constant predetermined in the system operation specification, such as 4 or 8 or 16. In addition, maxNrofCoScheduledCellsPerSet indicates the maximum number of serving cells that can be included in any co-scheduled cell set, and can be a constant predetermined in the specification of system operation, such as 4 or 8 or 16. For the RRC configuration IE, the information which cells belong to the co-scheduled cell set can be provided by, for example, a list of individual / cell level CIF values ​​corresponding to the cells included in the set, or in another example, by a bitmap including "1" for cells included in the set and "0" for cells not included in the co-scheduled cell set.

[0586] MultiCellSchedulingConfig Information Element

[0587]

[0588] In the second option, the UE determines the number of cells to be scheduled based on the number of cells n of each scheduled cell included in the set of co-scheduled cells. CI The value of n is used to determine the number of cells in the cooperative scheduling CI In one example, the value of n of the set of cells to be co-scheduled CI The value of can be based on n corresponding to the cells included in the co-scheduled cell set. CI In another example, the sum of the values ​​of n cells in the co-scheduled cell set is CI The value of can be defined as:

[0589] n CI (set) = n 0 +((∑ i∈set n CI(cell#i))mod L),

[0590] or

[0591] CIF(set)=n 0 +((∑ i∈set CIF(cell#i))mod L).

[0592] Among them, n 0 Can have such as n 0 =8 or n 0 =0, and L can have, for example, a value of L=8.

[0593] In the third option, the UE uses the number of reference scheduling cells in the coordinated scheduling cell set as n. CI The value of n is used to determine the number of cells in the cooperative scheduling CI In one example, the method is used when the same cell is not a reference cell for more than one co-scheduled cell set, and in another example, the method can be used even when two co-scheduled cell sets share the same reference cell. For example, the reference scheduling cell in the co-scheduled cell set can be:

[0594] - has a minimum or maximum n CI or a cell with a CIF value; or

[0595] - the cell with the smallest or largest size region index (Cell ID or ServCellIndex) value; or

[0596] - At least for the case where the scheduling cell is included in the set of co-scheduled cells, the scheduling cell, i.e. n CI =0;

[0597] - scheduled cells included in the set and explicitly indicated as reference cells by higher layer signaling;

[0598] - a scheduled cell included in the set and implicitly indicated as a reference cell, such as by configuring a corresponding search space on the DL BWP of the scheduled cell;

[0599] - A reference cell from the set / subset of serving cells for counting the DCI size budget including the sizes of the MC-DCI formats, such as a cell for which the sizes of the MC-DCI formats are counted into the “3+1” DCI size budget (and possibly not counted for other cells in the set of co-scheduled cells), e.g., a cell from the set / subset of co-scheduled cells that is configured with the smallest number of DCI format sizes.

[0600] According to a third option, the UE determines n of cells scheduled based on a reference from the set CI The same search space and corresponding PDCCH candidates are used for multi-cell scheduling and for single-cell scheduling when only the reference scheduled cell is scheduled by the scheduling cell. In this case, the UE can use other means to distinguish multi-cell scheduling from single-cell scheduling, such as the DCI format size or the RNTI used to scramble the CRC of the DCI format or an indication in the DCI format.

[0601] In one example, the search space set for multi-cell scheduling on the set of coordinated scheduled cells can be combined with multiple n CI The value is associated, such as when the UE monitors the first link search space set configured on the first cell, the first n corresponding to the first cell in the cooperatively scheduled cell set. CI value, and a second n corresponding to the second cell in the cooperatively scheduled cell set when the UE monitors the second link search space set configured on the second cell. CI value.

[0602] When multiple co-scheduled cell sets are associated with the same scheduling cell, the UE monitors the PDCCH of each co-scheduled cell set respectively, where each set can have a different n CI In one example, the DCI format can schedule only a subset of cells in the co-scheduled cell set. For example, the DCI format can co-schedule 2 cells from a set of 4 co-scheduled cells. The CIF value in the DCI format indicates the actual scheduled cell subset and does not indicate the co-scheduled cell set. For example, for a co-scheduled cell set including {cell #0, cell #1, cell #2, and cell #3}, n CI The value "00" can be associated with the scheduling of cell #0 and cell #1, n CI The value "01" can be associated with the scheduling of cell #0 and cell #2, n CI The value "10" can be associated with scheduling of cell #0 and cell #3, and n CI The value "00" can be associated with the scheduling of cell #0, cell #1, cell #2, and cell #3. In another example, the DCI format scheduling for multi-cell scheduling includes all serving cells in the co-scheduled cell set, so the CIF value in the DCI format and the n associated with the corresponding search space set are CI The values ​​are the same.

[0603] In one implementation, the UE can be indicated by the serving gNB the same n_CI value for multiple co-scheduled cell sets / subsets. For example, the UE can be indicated a first n_CI value for a first co-scheduled cell set / subset, and a second n_CI value for a second co-scheduled cell set / subset. In one example, the indication of the same or different n_CI values ​​for different co-scheduled cell sets / subsets can depend on the gNB implementation. In another example, there can be restrictions or conditions on whether the same or separate n_CI values ​​can be indicated. For example, the UE can be indicated the same n_CI value for a first co-scheduled cell set / subset when one or more of the following conditions are met:

[0604] - there is a co-scheduled cell set / subset from the first co-scheduled cell set / subset, which includes all other co-scheduled cell sets / subsets from the first co-scheduled cell set / subset; or,

[0605] - For any two co-scheduled cell sets / subsets from the first co-scheduled cell set / subset, there is at least one serving cell included in both sets / subsets.

[0606] For example, when the UE is configured with set 1 = {cell 1, cell 2}, and set 2 = {cell 3, cell 4}, and the UE is not configured with set 3 = {cell 1, cell 2, cell 3, cell 4} (or, alternatively, set 4 = {cell 1, cell 4} and set 5 = {cell 2, cell 3}), then separate n_CI values ​​can be indicated for set 1 and set 2; otherwise, the same n_CI can be indicated for all of set 1, set 2, and set 3 (or alternatively, the same n_CI value can be indicated for all of set 1, set 2, set 4, and set 5).

[0607] In another example, the UE can be instructed to have the same / shared n for a set / subset of cells that are co-scheduled with different numbers of cells. CI value, and a separate n for a set / subset of co-scheduled cells including the same number of cells CI For example, set 1 = {cell 1, cell 2} and set 2 = {cell 1, cell 2, cell 3, cell 4} can have a first n CI Values, such as n CI =5, and set 3 = {cell 3, cell 4} and set 4 = {cell 1, cell 2, cell 5, cell 6} may have a second n CI Values, such as n CI = 6. For example, the indication of the same or separate n_CI values ​​can be based on a combination of the set / subset size condition and the intersection condition described above.

[0608] In one example, different co-scheduled cell sets / subsets indicated with the same n_CI value can correspond to different sizes of a multi-cell scheduling DCI (MC-DCI) format. Different n_CI values ​​can correspond to the same size of an MC-DCI format for scheduling on more than one cell set. For example, the MC-DCI format can have a first size for a first co-scheduled cell set / subset and a second size for a second co-scheduled cell set / subset. For example, the size of the MC-DCI format can be based on the size of the co-scheduled cell set / subset associated with the n_CI value.

[0609] In one example, the UE can be configured with a first group of co-scheduled cells and a second group of co-scheduled cells. The UE can be indicated a first n_CI value for the first group of co-scheduled cells and all corresponding subsets of the first group of co-scheduled cells, and a second n_CI value for the second group of co-scheduled cells and all corresponding subsets of the second group of co-scheduled cells. For example, the first group includes cells {1, 2, 3, 4} and all subsets thereof, and the second group includes cells {5, 6, 7, 8} and all subsets thereof. For example, the UE can be provided with a separate configuration for co-scheduling on cells in the first and second groups of co-scheduled cells, such as for one or more of the following items: TDRA table (including a joint multi-cell TDRA table), MCS (including differential MCS), NZP CSI-RS triggering, rate matching indicator, TCI state, etc. For example, for the DCI field of the multi-cell scheduling DCI format for each of the first or second groups of co-scheduled cells, the UE can be indicated with the same value, such as a cell common value. For example, a first group of co-scheduled cells can correspond to a first frequency band or a first frequency range, such as FR1, and a second group of co-scheduled cells can correspond to a second frequency band or a second frequency range, such as FR2.

[0610] In one example, a UE can be provided with a first n_CI value for a first co-scheduled set / subset of cells associated with a first search space set (e.g., based on a search space linking process), and a second n_CI value for a second co-scheduled set / subset of cells associated with a second search space set. For example, when the co-scheduled set / subset of cells is associated with both the first search space set and the second search space set, the UE monitors the PDCCH according to the first search space set based on the first n_CI value and according to the second search space set based on the second n_CI value to detect an MC-DCI format for the co-scheduled set / subset of cells.

[0611] In one example, the UE may monitor the PDCCH based on a common search space (CSS) set for multi-cell scheduling. The UE can be configured to monitor the PDCCH to detect unicast DCI formats, such as DCI formats 0_0 or 1_0 that are repurposed for multi-cell scheduling. For example, such a unicast DCI format can be a first-stage DCI format for a two-stage scheduling mechanism, wherein the second-stage DCI is multiplexed in a PDSCH scheduled by the first-stage DCI or in another PDCCH, as described herein. In another example, the UE does not expect to be configured to monitor the PDCCH based on a CSS set for multi-cell scheduling.

[0612] In one example, the UE may monitor the PDCCH based on a common search space (CSS) set for multi-cell scheduling. The UE can be configured to monitor the PDCCH to detect unicast DCI formats, such as DCI formats 0_0 or 1_0 that are repurposed for multi-cell scheduling. For example, such a unicast DCI format can be a first-stage DCI format for a two-stage scheduling mechanism, wherein the second-stage DCI is multiplexed in a PDSCH scheduled by the first-stage DCI or in another PDCCH, as described herein. In another example, the UE does not expect to be configured to monitor the PDCCH based on a CSS set for multi-cell scheduling.

[0613] Fig.11 An example method 1100 for monitoring PDCCH in a set of search spaces for multi-cell scheduling according to an embodiment of the present disclosure is shown. The embodiment of the method 1100 for monitoring PDCCH in a set of search spaces for multi-cell scheduling is for illustration only. Fig.11 The scope of the present disclosure is not limited to any particular implementation of the method 1100 for monitoring a PDCCH in a set of search spaces for multi-cell scheduling.

[0614] like Fig.11 As shown, method 1100 begins at step 1110, where a UE (such as UE 116) is configured for a set of cells for cooperative scheduling. CI or CIF value. At step 1120, the UE is configured with a UE-specific search space (USS) set for monitoring the PDCCH to detect a DCI format for performing multi-cell scheduling on a set of co-scheduled cells. At step 1130, the UE uses the configured n CI The UE receives the PDCCH according to the USS set for multi-cell scheduling. At step 1140, the UE detects the DCI format for multi-cell scheduling in the PDCCH, which has a CIF value corresponding to a cell in the co-scheduled cell set. At step 1150, the UE receives the PDSCH or sends the PUSCH on the cell in the co-scheduled cell set.

[0615] In one example, no n is required CI or an indication of a CIF value to determine the association of a search space set with a co-scheduled cell set. For example, when the UE is configured with a search space set associated with a CORESET on a scheduling cell, the UE may determine PDCCH candidates based on the search space set for all co-scheduled cell sets / subsets associated with the scheduling cell. The UE determines the PDCCH candidates by applying the corresponding n in the PDCCH search space equation for the search space set. CI The method can be useful when the UE is not configured with a dedicated DCI format or dedicated DCI format size for multi-cell scheduling, such as when the same DCI format or the same DCI format size can be used for both single-cell scheduling and multi-cell scheduling. The same PDCCH candidate can be monitored for decoding SC-DCI format or MC-DCI format (using the same RNTI, such as C-RNTI) without any distinction between DCI formats, and thus without any impact on PDCCH candidate determination or search space set association. The method can also be useful when the size of the MC-DCI format does not depend on the subset of cells that are co-scheduled and is determined according to the co-scheduled cell set, and the UE can infer the co-scheduled cell based on a predetermined value of a field corresponding to an unscheduled cell in the co-scheduled cell set. For example, when a separate MCS field is used in the MC-DCI format for each cell in the co-scheduled cell set, a value of 0 can indicate that the cell is not scheduled by a given MC-DCI format.

[0616] For example, when the UE is configured with a search space set associated with a CORESET on a scheduling cell, and the search space configuration includes monitoring a DCI format for multi-cell scheduling (such as DCI format 0_3 or 1_3), the UE may determine PDCCH candidates based on the search space set for all sets / subsets of co-scheduled cells associated with the scheduling cell. The UE determines the PDCCH candidates by applying the corresponding n in the PDCCH search space equation for the search space set. CI The method can be beneficial when the UE is configured with a dedicated DCI format or dedicated DCI format size for multi-cell scheduling (different from that for single-cell scheduling). The UE can be configured by a higher layer or can be predetermined in the specification of the system operation to monitor a search space set including MC-DCI formats for all co-scheduled cell sets / subsets associated with the scheduling cell.

[0617] In one example, the UE implicitly determines the association between the search space set and the co-scheduled cell set / subset based on the search space set configuration / linkage or based on the active DL BWP of the co-scheduled cell on which the search space set is configured. For example, when the UE is configured:

[0618] - a first search space set associated with the CORESET on the scheduling cell, and

[0619] - a "linked" search space set on the set / subset of co-scheduled cells, wherein the linked search space set is associated with the first search space set,

[0620] The UE may determine the PDCCH candidates according to the first search space set of the cell set / subset for cooperative scheduling. Therefore, the UE applies the corresponding n in the PDCCH search space equation for the first search space set. CI The value (set level CIF) is used to determine the PDCCH candidates associated with the co-scheduled cell set / subset. For example, when the UE is configured:

[0621] - A set / subset of cells to be co-scheduled, including cell indexes {#2, #4, #5, #7}, set level CIF=6, and

[0622] - a first search space set on the scheduled cells corresponding to the set / subset of co-scheduled cells, and

[0623] - four linked search space sets (e.g., with the same search space set ID as the first search space set) on four cells in the co-scheduled cell set / subset (i.e., cells with indices #2, #4, #5, and #7), which are linked to the first search space set,

[0624] The UE performs the following operations according to the n corresponding to the co-scheduled cell set / subset with index {#2, #4, #5, #7}. CI The first (or linked) search space set (or sets) of PDCCH candidates are monitored using the value (set level CIF=6).

[0625] In one example, the UE monitors the PDCCH according to the first / linked search space set, regardless of whether the linked search space set is configured on the corresponding active DL BWP of the co-scheduled cell set / subset. In the above example, the UE monitors the first (or linked) search set (or multiple) of PDCCH candidates corresponding to the co-scheduled cell set / subset {#2, #4, #5, #7}, even if the linked search space sets on some cells (e.g., #4 and #5) are configured on DL BWPs that are not the active DL BWPs of serving cells #4 and #5, respectively. In one example, the UE monitors the PDCCH according to the first / linked search space set, even when all linked search space sets are configured on the corresponding active DL BWPs of cells in the co-scheduled cell set / subset that are not the corresponding active DL BWPs of the cells.

[0626] In one example, when the linked search space set is configured on the corresponding active DL BWP of a cell in the co-scheduled cell set / subset, the UE monitors the PDCCH according to the first / linked search space set. For example, when the first search space set is configured on the DL BWP that is not the active DL BWP of the scheduled cell or when at least one of the linked search space sets is configured on the corresponding DL BWP of the corresponding active DL BWP of the corresponding cell in the co-scheduled cell set / subset, the UE does not monitor the PDCCH according to the first / linked search space set for the co-scheduled cell set / subset. For example, when the corresponding linked search space set for one cell (say cell #4) is configured on the corresponding DL BWP of cell #4, the UE does not monitor the PDCCH according to the first / linked search set (or multiple) for PDCCH candidates corresponding to the co-scheduled cell set / subset {#2, #4, #5, #7}, even if the corresponding linked search space sets for cells #2, #5 and #7 are configured on the corresponding DL BWP.

[0627] In another example, the UE monitors a search space set on a scheduling cell for a co-scheduled cell set / subset, wherein, for the co-scheduled cell set / subset, a linked search space set is configured on a corresponding active DLBWP of the co-scheduled cell set / subset. For example, when a first linked search space set is configured on a corresponding active DL BWP of a first co-scheduled cell set / subset, the UE is able to determine an association of the search space set on the scheduling cell with the first co-scheduled cell set / subset, and when a second linked search space set is configured on a corresponding active DL BWP of a second co-scheduled cell set / subset, the UE is able to determine an association of the search space set on the scheduling cell with the second co-scheduled cell set / subset. Here, the first and second linked search space sets are linked to the search space set on the scheduling cell. In one example, the UE is able to provide a set level n corresponding to the first and second co-scheduled cell sets / subsets. CI or CIF value, so that the PDCCH candidates can be determined accordingly.

[0628] For example, when the UE is configured with four linked search space sets (e.g., having the same search space set ID) on cells #2, #4, #5, and #7 that are linked to the first search space set on the scheduling cells associated with cells #2, #4, #5, and #7, when the linked search space sets on cells #2 and #7 are configured on the corresponding active DL BWPs (and the linked search space sets on cells #4 and #5 are configured on the corresponding DL BWPs that are not active DL BWPs), the UE is configured according to the first set level n corresponding to the co-scheduled cells {#2, #7}. CI The UE may monitor the first (or linked) search space set (or sets) for PDCCH candidates according to the value (say, CIF=4) of the co-scheduled cells {#4, #7}. For example, when the linked search space set on cells #4 and #7 is configured on the corresponding active DL BWP (and the linked search space set on cells #2 and #5 is configured on the corresponding DLBWP that is not an active DL BWP), the UE may monitor the first (or linked) search space set (or sets) for PDCCH candidates according to the second set level n corresponding to the co-scheduled cells {#4, #7}. CI The UE is provided with a set level n corresponding to the first and second co-scheduled cell sets / subsets. CI Or CIF value (for example, CIF=4 or CIF=5).

[0629] In the above example, the configuration of the original search space set on the scheduling cell can indicate monitoring of multi-cell scheduling DCI formats when the UE is configured with dedicated DCI formats or dedicated DCI format sizes for multi-cell scheduling (different from those for single-cell scheduling).

[0630] In another example, the UE may not be configured with a dedicated DCI format (or dedicated DCI format size) for multi-cell scheduling that is different from that (those) for single-cell scheduling. Therefore, the UE may be configured with a dedicated DCI format (or dedicated DCI format size) for multi-cell scheduling that is different from that (those) for single-cell scheduling. CI The UE may determine a PDCCH candidate based on a search space set of values ​​to monitor a DCI format shared with single-cell scheduling. For example, the UE decodes the PDCCH candidate relative to an RNTI (such as an M-RNTI) that is configured to scramble the CRC of the DCI format (for single-cell scheduling) reused for multi-cell scheduling.

[0631] In yet another example, the UE may not be configured with a dedicated DCI format for multi-cell scheduling nor a dedicated RNTI for multi-cell scheduling, so both the DCI format and RNTI for multi-cell scheduling will be the same as those for single-cell scheduling (e.g., for multi-cell scheduling, an existing single-user DCI format such as 0_1 or 1_1 may include an additional DCI field or a DCI field with a different bit width based on the multi-cell scheduling configuration). In this case, when the UE determines the linked search space set (or multiple) corresponding to the co-scheduled cell set / subset (using any of the methods described throughout the present disclosure, such as extended search space linking or explicit configuration or predetermined rules), the UE is able to determine the set of linked search spaces corresponding to the co-scheduled cell set / subset based on the set level n corresponding to the co-scheduled cell set / subset. CI or CIF value to determine different individual PDCCH candidates for multi-cell scheduling. For example, the UE can determine the different individual PDCCH candidates for multi-cell scheduling based on the corresponding cell level n CI or CIF value to determine the first PDCCH candidate for single-cell scheduling on each cell in the cell set / subset for coordinated scheduling, and based on the corresponding set level n CI or CIF value to determine the second PDCCH candidate for multi-cell scheduling on the coordinated scheduled cell set / subset.

[0632] In one example, when the association of the search space set on the scheduling cell with the co-scheduled cell set is provided by explicit indication (such as by an IE in the search space set configuration), the UE applies the corresponding n in the PDCCH search space equation of the search space set. CI The PDCCH candidates associated with the co-scheduled cell set / subset are determined by using the value (set level CIF). The UE can be configured with one or more co-scheduled cell sets / subsets associated with the same search space set through explicit configuration.

[0633] When the UE is configured with a search space set associated with multiple co-scheduled cell sets / subsets, such as by an IE in the search space set configuration including first and second set-level CIF values, the UE can search the search space set based on a first n set-level CIF value equal to the first set-level CIF value corresponding to the first co-scheduled cell set / subset. CI The first PDCCH candidate is determined based on a second n value equal to a second set-level CIF value corresponding to a second co-scheduled cell set / subset. CI Herein, both the first and second PDCCH candidates are based on the same search space set (eg, used to determine a PDCCH monitoring opportunity, etc.).

[0634] In one example, when the association of the search space set on the scheduling cell with the co-scheduled cell set is provided by an explicit indication (such as by an IE in the search space set configuration), the UE performs the search according to the indication of the corresponding co-scheduled cell set / subset. CI The UE determines the PDCCH candidates based on the value (set-level CIF) regardless of whether zero or one or more linked search space sets (or multiple) are configured on zero or one or more cells in the co-scheduled cell set / subset, and regardless of whether any linked search space set is on the corresponding active DLBWP of the co-scheduled cell set / subset. In another example, when the UE is configured with one or more linked search space sets (or multiple) on one or more cells from the co-scheduled cell set / subset, and one or more of the linked search space sets are not configured on the corresponding active DL BWP of the co-scheduled cell set / subset, the UE does not determine the PDCCH candidates based on the indication corresponding to the co-scheduled cell set / subset. CI value (aggregation level CIF) to monitor PDCCH.

[0635] In another example, the UE applies the multi-cell extension of search space linking on top of an explicit configuration of the co-scheduled cell set / subset associated with the search space set. For example, when the association of the search space set on the scheduling cell with the co-scheduled cell set is provided by an explicit indication (such as by an IE in the search space set configuration), when the UE is not configured with one or more linked search space sets on one or more cells in the co-scheduled cell set / subset, or when one or more of the linked search space sets configured on one or more cells in the co-scheduled cell set / subset are configured on a corresponding DL BWP different from the corresponding active DL BWP, the UE does not apply the multi-cell extension of search space linking according to the indication corresponding to the co-scheduled cell set / subset. CI value (aggregation level CIF) to monitor PDCCH.

[0636] In one example, when the UE is configured with a search space set associated with multiple co-scheduled cell sets / subsets (such as through an IE in the search space set configuration including multiple set-level CIF values), the UE can select a search space set based on a reference n equal to one of the multiple set-level CIF values. CI The UE does not determine the PDCCH candidates based on other set-level CIF values ​​indicated for the search space set. CI The value can be equal to one of the following:

[0637] - the minimum collection level CIF value, or

[0638] - Maximum CIF value, or

[0639] - a CIF value corresponding to a co-scheduled cell set having a smallest size among a plurality of co-scheduled cells, or

[0640] - A CIF value corresponding to a co-scheduled cell set having a largest size among a plurality of co-scheduled cell sets.

[0641] The UE is capable of decoding a PDCCH candidate for monitoring a multi-cell scheduling DCI format associated with a plurality of set-level CIF values. For example, the UE is capable of determining a first size for the multi-cell scheduling DCI format based on a first set-level CIF value, and determining a second size for the multi-cell scheduling DCI format based on a second set-level CIF value.

[0642] In one example, even when the search space set is explicitly indicated with one or more associated sets (or multiple) of co-scheduled cells, the UE can implicitly determine the association between the search space set and the co-scheduled cell set / subset based on the linked search space set configured on the active DL BWP of the co-scheduled cells. For example, when the UE:

[0643] - A search space set is provided, wherein the search space set is configured by a higher layer (such as by an IE in the search space configuration) with the first set level n CI / CIF value associated, first collection level n CI / CIF value corresponds to the first co-scheduled cell set, and

[0644] - a first linked search space set on a set of cells provided with a first cooperative scheduling, wherein the first linked search space set is associated / linked with the first search space set;

[0645] - determining that a second linked search space set on a second cell is configured on a corresponding active DL BWP of the second cell, wherein the second cell is a subset of the first co-scheduled set of cells and the second search space set is a subset of the first linked search space set,

[0646] The UE is based on a second set level n corresponding to the second cell CI / CIF value, and determining the PDCCH candidate according to the first search space set (or according to the second link search space set).

[0647] For example, when the configuration of the search space set on the scheduling cell includes an association with a first set level / CIF=6 corresponding to a first co-scheduled cell set including cells {#2, #4, #5, #7}, and when the link search space sets on cells #2 and #7 are configured on the corresponding DL BWP (and the link search space sets on cells #4 and #5 are not configured on the corresponding DL BWP), the UE selects, based on, say, n corresponding to the co-scheduled cell subset {#2, #7}. CI / CIF=4, the PDCCH candidates are determined according to a search space set (or according to a linked search space set).

[0648] In one example, the UE can be configured to schedule the cell according to the cell level n corresponding to the single scheduled cell. CI / CIF values ​​to monitor PDCCH candidates, and the UE can be configured to monitor PDCCH candidates according to a DCI format (or multiple) used only for multi-cell scheduling or according to a DCI format (or multiple) shared for both single-cell scheduling and multi-cell scheduling (such as based on RNTI or based on an explicit indication / flag in the DCI). For example, the UE can be configured with one or more set-level CIF values ​​that can be used to decode the multi-cell scheduling DCI format (or multiple) through a higher layer configuration of the search space set. For example, the UE determines a first size of the MC-DCI format corresponding to the first set-level CIF value, and determines a second size of the MC-DCI format corresponding to the second set-level CIF value.

[0649] In one example, the search space set may include monitoring only one of the downlink MC-DCI format or the uplink MC-DCI format, but not both. For example, a search space set such as an MSS set may include monitoring only a downlink MC-DCI format such as 1_3, but not including monitoring an uplink MC-DCI format such as 0_3. In another example, a search space set such as an MSS set may include monitoring only an uplink MC-DCI format such as 0_3, but not including monitoring an uplink MC-DCI format such as 1_3. For example, due to the different DCI sizes and corresponding CCE AL values ​​required for the downlink MC-DCI format and the uplink MC-DCI format, this design can be beneficial.

[0650] In one embodiment, some methods for search space set configuration and linking to a co-scheduled set of cells are considered.

[0651] For single cell scheduling, the UE is configured with a first search space set on the scheduling cell and a second search space set on the scheduled cell, wherein the first search space set and the second search space set are linked by having the same search space index, and the second search space set does not include optional fields except nrofCandidates (regardless of their presence conditions in the SearchSpace IE). In addition, the UE applies the search space set for the scheduled cell only when both DL BWPs in which the linked search space set is configured in the scheduling cell and the scheduled cell are active.

[0652] In one example, for optional fields in the linked search space set in the scheduled cell, the UE uses the same values ​​corresponding to the fields provided in the linked (i.e., original) search space set in the scheduled cell. In another example, the UE can be provided with separate values ​​for some optional fields in the linked search space set in the scheduled cell, which are different from the values ​​for the corresponding fields in the linked search space set in the scheduled cell. For example, the PDCCH monitoring periodicity, offset, or duration can be different on the scheduled cell than on the scheduled cell.

[0653] In one example, the search space link can be based on an explicit configuration of the IE, which provides a search space set ID (or IDs) for linking a search space set (or sets). For example, the link search space sets on the scheduled cell and the scheduled cells (or cell) can have different search space set IDs. In one example, some IEs in the link search space set can be different from the original search space set, such as the number of monitored PDCCH candidates, or the set of DCI formats monitored in the link search space set. For example, the original search space set configured on the scheduled cell can include PDCCH monitoring according to a first DCI format, and the link search space set configured on the scheduled cell can include PDCCH monitoring according to a second DCI format. For example, the second DCI format can be a subset of the first DCI format. For example, the UE can be configured to monitor DCI formats for both single-cell scheduling and multi-cell scheduling on the original search space set, and the UE can be configured to monitor DCI formats for multi-cell scheduling (but not those for single-cell scheduling) on the link search space set.

[0654] For multi-cell scheduling, in an exemplary implementation, the same search space set for multi-cell scheduling can be provided on all cells in the set of co-scheduled cells. It is also possible that the search space set for multi-cell scheduling is provided only on the scheduled cell and not on any (other) co-scheduled cells.

[0655] In a first method, the UE can be configured with a first search space set on the corresponding scheduled cell and with N link search space sets on all N cells in the set of co-scheduled cells, where a search space set is configured on each of the N cells. For example, all N search space sets can have the same search space set index as the first search space set. For example, the first search space set can include all parameters and IEs for the configuration of the search space set, and the N link search space sets do not include optional fields, except for nrofCandidates (regardless of their presence conditions in the search space IE). For example, for the case of the MSS set dedicated to multi-cell scheduling, the first method is beneficial. In a variant, the UE can be configured with a first search space set on the corresponding scheduled cell and with M link search space sets on M cells from the set of co-scheduled cells including N cells, where 1 ≤ M < N, and where the "linked" search space sets are configured on each of the M cells.

[0656] For example, if a DL BWP in which a link search space set is configured in both the scheduling cell and the scheduled cell is active, the UE applies the link search space set for the scheduled cell in the co-scheduled cell set.

[0657] In another example, if a DL BWP in which a linked search space set is configured in the scheduling cell and in at least one cell in the co-scheduled cell set is active, the UE applies the linked search space set for the co-scheduled cell set. In this example, based on at least one cell with an active DL BWP, the UE is able to select the first search space set and all N linked search space sets with the same n. CI value, or it can be operated with different n for the first search space set and all N linked search space sets. CI For example, the link search space set for multi-cell scheduling on the co-scheduled cell set can be configured with the first n corresponding to the first cell when the UE monitors the active DL BWP of the first cell in the co-scheduled cell set. CI The value is associated with the second n corresponding to the second cell when the UE monitors the linked search space set configured on the active DL BWP of the second cell in the set of co-scheduled cells. CI Value associated.

[0658] In yet another example, if a DL BWP in which a linked search space set is configured in the scheduling cell and in all N cells in the co-scheduled cell set is active, the UE applies the linked search space set for the co-scheduled cell set. In this example, the UE is expected to use the same n for the first search space set and all N linked search space sets. CI Value to operate.

[0659] In the special case where the scheduling cell is in the set of N co-scheduled cells, no additional search space set is required on the scheduling cell, because the UE is already configured with the first search space set (with a complete search space configuration) on the scheduling cell. Then, only (N-1) search space sets need to be configured on the remaining cells in the set of co-scheduled cells.

[0660] In one example, when the search space set is used for multi-cell scheduling, the UE is expected to be configured with the same number of PDCCH candidates on each of the N linked search space sets of the cell set used for collaborative scheduling through the parameter nrofCandidates. In another example, when the search space can be used for both single-cell scheduling and multi-cell scheduling, the UE can be configured with a different number of PDCCH candidates through the corresponding parameter nrofCandidates on each of the N linked search space sets of the cell set used for collaborative scheduling. In one example, the UE can be configured with two separate values ​​of the parameter nrofCandidates for each AL, wherein the first nrofCandidates value of the AL provides the number of PDCCH candidates for single-cell scheduling of the AL, and the second nrofCandidates value of the AL provides the number of PDCCH candidates for multi-cell scheduling of the AL. In another example, when the UE is configured with a search space set associated with two or more co-scheduled cell sets / subsets, the UE can be configured with two or more values ​​for the parameter nrofCandidates for each CCE AL value, such that a first value of the parameter nrofCandidates for a given AL corresponds to a first co-scheduled cell set, and a second value of the parameter nrofCandidates for a given AL corresponds to a second co-scheduled cell set, and so on. In a variant, the first value of the parameter nrofCandidates for a given AL corresponds to a first co-scheduled cell set having a first size (i.e., a first number of cells), and the second value of the parameter nrofCandidates for a given AL corresponds to a second co-scheduled cell set having a second size (i.e., a second number of cells), and so on.

[0661] In the second method, the UE can be configured with a first search space set on the scheduling cell and a second link search space set only on a reference scheduling cell in the co-scheduled cell set. The UE does not expect to be configured with a link search space set on other cells in the co-scheduled cell set. Here, the reference cell in the co-scheduled cell set can indicate one or more examples described herein.

[0662] According to the second method, the UE applies the linked search space set for the scheduling cell only when the DL BWP in which the linked search space set is configured in both the scheduling cell and the reference cell is active.

[0663] In a variation of the second method, the reference scheduling cell can be any cell in the set of co-scheduled cells. This variation can be applicable, for example, when the UE is configured with a search space set to monitor the PDCCH to detect DCI formats for both single-cell scheduling and multi-cell scheduling. Then, the search space set configuration and linking can follow the existing rules for search space sets used only for single-cell scheduling.

[0664] In one example, the UE can be configured:

[0665] - a first search space set on a first cell in the set of co-scheduled cells, wherein the UE monitors the PDCCH to detect DCI formats for both single-cell scheduling on the first cell and multi-cell scheduling on the set of co-scheduled cells, and

[0666] - a second search space set on a second cell in the co-scheduled set of cells, wherein the UE monitors the PDCCH to detect DCI formats for both single cell scheduling on the second cell and multi-cell scheduling on the co-scheduled set of cells.

[0667] In one example, when the search space linking rule is based on the configuration of a linked search space set (e.g., having the same search space index) on only one cell in a co-scheduled cell set / subset, and when the UE is configured to monitor a search space set in a multi-cell scheduled DCI (MC-DCI) format on a first cell, the UE determines the PDCCH candidate based on the search space set for any co-scheduled cell set / subset including the first cell. In one example, the co-scheduled cell set / subset including the first cell can be associated with different n_CI values. In another example, the co-scheduled cell set / subset including the first cell can be associated with the same n_CI value.

[0668] In one implementation, the reference cell for search space linkage can be the same as the reference cell for counting PDCCH candidates and non-overlapping CCEs or for counting DCI size budget for MC-DCI.

[0669] In one example, for the first method or the second method, the linked search space sets can have a fully or partially separate configuration (including for optional IE or for search space index), and the linking of the search space sets can be explicitly indicated, such as by indicating an index of a first search space set on a scheduling cell, wherein a second search space set on a cell in a co-scheduled set of cells is linked to the first search space set. According to this example, the first search space set and the second search space set are dedicated to multi-cell scheduling or at least associated with a DCI format (or multiple) for multi-cell scheduling.

[0670] In the third method, search space set linkage is not used for multi-cell scheduling, and multi-cell scheduling is regarded as self-cell scheduling. The UE can be configured with only the first search space set on the corresponding scheduling cell, and the UE does not expect any other linked search space sets on any (other) cells in the co-scheduled cell set. Therefore, there is no constraint on the DL BWP of any cell in the co-scheduled cell set, and only the DL BWP of the scheduling cell on which the first search space set is configured needs to be active. For example, the UE monitors the PDCCH according to the search space set based on the following items: (i) the set level n associated with any co-scheduled cell set / subset corresponding to the same scheduling cell. CI or CIF value, or (i) the set level n associated with the first co-scheduled cell set / subset corresponding to the same scheduled cell CI Or CIF value, which is explicitly indicated by IE in the search space set configuration, for example. For example, in order to schedule on a subset of the cell set including {cell #0, cell #1, cell #2, cell #3}, the UE receives information of the search space set only on one scheduling cell, and the CIF values ​​"00", "10", "01", "11" in the MC-DCI format indicate scheduling on {cell #0, cell #1}, {cell #0, cell #2}, {cell #0, cell #3} and {cell #0, cell #1, cell #2, cell #3}, respectively. In one example, the CIF value is used to indicate the scheduled cell subset, and n CI The value is the same for all scheduled cell subsets, so that the same PDCCH candidate can be scheduled on any small subset indicated by the CIF value.

[0671] Fig.12 An example method 1200 for search space linking for multi-cell scheduling according to an embodiment of the present disclosure is shown. The embodiment of the method 1200 for search space linking for multi-cell scheduling is for illustration only. Fig.12 The scope of the present disclosure is not limited to any particular implementation of the method 1200 for search space linking for multi-cell scheduling.

[0672] like Fig.12As shown, method 1200 begins at step 1210, where a UE (such as UE 116) is configured with a co-scheduled cell set having the same scheduling cell. At step 1220, the UE is configured with a linked UE-specific search space (USS) set for multi-cell scheduling on the scheduling cell and on all cells in the co-scheduled cell set. At step 1230, the UE determines that the DL BWP on which the USS set for multi-cell scheduling is configured is active for the scheduling cell and for at least one cell in the co-scheduled cell set. At step 1240, the UE monitors the PDCCH according to the USS set for multi-cell scheduling on the co-scheduled cell set.

[0673] In one embodiment, for a UE configured with one or more co-scheduled cells, the size of a multi-cell DCI format can be set-specific (where the set indicates the set of co-scheduled cells), or set-size-specific (where the set size indicates the size of the set of co-scheduled cells), or search space set-specific, or scheduling cell-specific, or UE-specific. In addition, the UE can have a constraint / budget on the number of DCI format sizes that the UE can monitor per serving cell, per time slot, or across all time slots, where the size of the DCI format for multi-cell scheduling can be counted into the UE constraint / budget based on a fractional count or a full count, or can be part of a separate UE constraint / budget for the size of the DCI format, or can not be counted at all.

[0674] In a first implementation, the size of the multi-cell scheduling DCI format can be set-specific, i.e., can be based (only) on a co-scheduled cell set with an associated set-level CIF provided by a higher layer. For example, a first multi-cell scheduling DCI format corresponding to a first co-scheduled cell set (having a first number of cells) can have a first size, and a second multi-cell scheduling DCI format corresponding to a second co-scheduled cell set (having a second number of cells) can have a second size. For example, the first and second sizes depend on the configuration (such as presence, absence or bit width) of the DCI field provided for the first and second co-scheduled cell sets, respectively. Herein, the UE configures / determines the n number of cells configured / determined for the co-scheduled cell set in the search space set including monitoring the first DCI format. CIThe associated set-level CIF is determined based on the set-level CIF value indicated in the carrier indicator field value of the multi-cell scheduling DCI format, or based on the set-level CIF value indicated in the carrier indicator field value of the multi-cell scheduling DCI format. In one example, the UE determines the size of the first multi-cell scheduling DCI format associated with the first co-scheduled cell set, regardless of whether the UE is configured with a second multi-cell scheduling DCI format (or multiple) within the same (or different) search space set, or whether the first multi-cell scheduling DCI format is configured within the same (or different) search space set but associated with the second co-scheduled cell set.

[0675] In a second implementation, the size of the multi-cell scheduling DCI format can be set-size specific, i.e., can be based on the size of the co-scheduled cell set. For example, when the first and second co-scheduled cell sets have the same size (i.e., the same number of cells), the UE expects the same size of the multi-cell scheduling DCI format for both the first and second co-scheduled cell sets. In one example, when the UE monitors the multi-cell scheduling DCI format corresponding to the first and second co-scheduled cell sets in the same search space set, the same DCI format size applies. In another example, the same DCI format size applies regardless of whether the UE monitors the multi-cell scheduling DCI format corresponding to the first and second co-scheduled cell sets in the same search space set. For example, DCI format size alignment is applied across different search space sets (configured on the corresponding DL BWP of the corresponding co-scheduled cell sets).

[0676] In one example, the same size is achieved before / without any zero padding. In another example, the UE expects zero padding of a first DCI format with a smaller size so that the first DCI format has the same size as a second DCI format with an initially larger size. In one example, the DCI fields are individually size aligned. In another example, the zero padding is appended to the end of the DCI format with the smaller size.

[0677] In a third implementation, the size of the multi-cell scheduling DCI format can be search space set specific, i.e., can be based on the search space set in which the UE monitors the DCI format. For example, the UE can determine a first size of a multi-cell scheduling DCI format for monitoring in a first search space set, and a second size of a multi-cell scheduling DCI format for monitoring in a second search space set. For example, the DCI format size can depend not only on the higher layer configuration of the DCI field for the corresponding co-scheduled cell set, but also on the higher layer configuration of the DCI field for other co-scheduled cell sets for which its DCI format is monitored in the same search space set. For example, when the UE determines that the search space set is associated with multiple co-scheduled cell sets, the UE determines the same size for the multi-cell scheduling DCI format corresponding to the multiple co-scheduled cell sets, wherein the DCI size alignment can be achieved, for example, by zero padding. For example, the DCI field can be a size that is individually aligned, or zeros can be attached to the end of the DCI format (or multiple) with a smaller size (or multiples) so that their size becomes equal to the maximum size.

[0678] In a fourth implementation, the size of the multi-cell scheduling DCI format can be scheduling cell specific, that is, it can be based on the corresponding scheduling cell of the received DCI format. For example, the UE determines the same size of the multi-cell scheduling DCI format corresponding to multiple co-scheduled cell sets associated with the same scheduling cell. For example, regardless of the same or different sizes (or multiple) of multiple co-scheduled cell sets, or regardless of the same or different search space sets (or multiple) of the multi-cell scheduling DCI format in which the UE monitors multiple co-scheduled cell sets, the same size applies. For example, DCI size alignment can be achieved by zero padding. For example, the DCI field can be a separately aligned size, or zeros can be attached to the end of the DCI format (or multiple) with a smaller size (or multiple) so that their size becomes equal to the maximum size.

[0679] In a variation of the fourth implementation, the size of the multi-cell scheduling DCI format can be BWP-specific, ie, can be based on the DL BWP of the corresponding scheduling cell receiving the DCI format.

[0680] In a fifth implementation, the size of the multi-cell scheduling DCI format can be UE-specific. For example, the UE determines the same size for the multi-cell scheduling DCI format corresponding to a plurality of co-scheduled cell sets associated with the same or different scheduling cells (or multiples). For example, DCI size alignment can be achieved by zero padding. For example, the DCI field can be a size that is individually aligned, or zeros can be attached to the end of the DCI format (or multiples) with a smaller size (or multiples) so that their size becomes equal to the maximum size.

[0681] In one example, in addition to / instead of only the size of the multi-cell scheduling DCI format, the first, second, third, fourth, or fifth implementation manner described above can be applied to the multi-cell scheduling DCI format itself.

[0682] In one example, the size of the DCI format for multi-cell scheduling is fixed to a predetermined / configured value regardless of the number of cells included in the co-scheduled cell set / subset. For example, the predetermined / configured value of the size of the DCI format for multi-cell scheduling can be based on the maximum possible / allowed number of co-scheduled cells, such as 8 cells. For example, when the size of the DCI format for multi-cell scheduling is less than the predetermined / configured value, the UE can perform zero padding at the end of the DCI format or perform zero padding for each DCI field individually, so that the size of the DCI format after zero padding is equal to the predetermined / configured value.

[0683] In another example, the UE can be provided with a set size threshold and two values ​​of the size of the DCI format for multi-cell scheduling. Then, when the first DCI format schedules multiple PDSCH receptions or PUSCH transmissions on a first co-scheduled set of cells (associated with a first set level parameter of a corresponding search space set) having a first size less than or equal to the set size threshold, the first DCI format can have a size equal to the first value from the two values. When the second DCI format schedules multiple PDSCH receptions or PUSCH transmissions on a second co-scheduled set of cells (associated with a second set level parameter of a corresponding search space set) having a second size greater than the set size threshold, the first DCI format can have a size equal to the second value from the two values. For example, the set size threshold can be 4 cells, and the two values ​​of the DCI format size can be 96 bits and 124 bits (excluding CRC bits). For a co-scheduled cell set of no more than 4 cells, the DCI format size can be 96 bits, and for a co-scheduled cell set with 5-8 cells, the DCI format size can be 124 bits (excluding CRC bits). For example, the method can be extended to N values ​​of the size of the multi-cell scheduling DCI format and (N-1) set size thresholds. For example, the size of the multi-cell scheduling DCI format and the value of the set size threshold (or multiple) can be predetermined in the specification of the system operation, or can be provided by a higher layer configuration.

[0684] In 5G NR Rel-17 [TS 38.213v17.1.0], the UE is expected to monitor PDCCH candidates for up to 4 sizes of DCI formats per serving cell, including up to 3 sizes of DCI formats with CRC scrambled by C-RNTI. This rule is sometimes referred to as the "3+1" rule for the DCI size budget for the UE. The UE counts the number of sizes of DCI formats per serving cell based on the number of configured PDCCH candidates in the corresponding search space set for the corresponding active DLBWP.

[0685] When the UE is configured with one or more co-scheduled cell sets (or multiple) or the UE is configured to monitor the DCI format (or multiple) for multi-cell scheduling, there can be various options for modifying the "3+1" rule. Herein, the size of the multi-cell scheduling DCI format can be determined based on any one of the first / second / third / fourth / fifth options described above.

[0686] In the first option, the UE does not count the size of the multi-cell scheduling DCI format into the UE's "3+1" DCI size budget.

[0687] In a second option, the UE counts the size of the multi-cell scheduling DCI format into the UE's "3+1" DCI size budget for each cell in the co-scheduled cell set based on fractional counting or inverse scaling. For example, the size of the multi-cell scheduling DCI format corresponding to a co-scheduled cell set having M cells can be counted as a fractional count (such as 1 / M), counted into the UE's "3+1" DCI size budget for each of the M cells. For example, the fractional counting or inverse scaling can be based on a scaling factor predetermined in the system operating specification, or can be provided by a higher layer configuration. When a first multi-cell scheduling DCI format corresponds to a first co-scheduled cell set S1 having M1 cells, but the size of the first DCI format is aligned with the size of a second multi-cell scheduling DCI format corresponding to a second co-scheduled cell set S2 having M2 cells, for example by zero padding, in one option, the UE counts the (aligned) sizes of the first / second DCI formats as:

[0688] - Count 1 / M1 into the UE's "3+1" DCI size budget for each of the M1 (or M2) cells, or

[0689] - 1 / M2 is included in the UE's "3+1" DCI size budget for each of the M1 (or M2) cells, or

[0690] - 1 / min(M1,M2) is included in the UE's "3+1" DCI size budget for each of the M1 (or M2) cells, or

[0691] - 1 / max(M1,M2) is included in the UE's "3+1" DCI size budget for each of the M1 (or M2) cells, or

[0692] -1 / M * Included in UE for M * A "3+1" DCI size budget is set for each of the cells, where M * The cells include the union of M1 cells and M2 cells, that is, M * =|S 1 ∪S 2 |, or

[0693] -by Included in UE Cells (or M * A "3+1" DCI size budget is defined for each of the cells, where The cells include the intersection of M1 cells and M2 cells, that is,

[0694] In a third option, the UE counts the size of the multi-cell scheduling DCI format as a full count (ie, one size) without any scaling, into the UE's "3+1" DCI size budget for each cell in the co-scheduled set of cells.

[0695] In a fourth option, the UE counts the size of the multi-cell scheduling DCI format as a full count (i.e., one size) without any scaling, towards the UE's "3+1" DCI size budget for a reference cell in a set of co-scheduled cells. For example, the reference cell can indicate any of the examples described herein. In one example, the UE counts the size of the multi-cell scheduling DCI format as a full count (i.e., one size) without any scaling, towards the UE's "3+1" DCI size budget for a first cell in a set of co-scheduled cells, wherein for the set of co-scheduled cells, the UE does not expect / is not configured with more than the 3+1 DCI size of the first cell.

[0696] In one example, the UE is able to report capabilities corresponding to one or more of the first / second / third / fourth options described above.

[0697] When the UE is configured with one or more co-scheduled cell sets (or sets) or the UE is configured to monitor DCI format (or sets) for multi-cell scheduling, there can also be various alternatives for modifying the "3+1" rule itself.

[0698] In the first alternative, the "3+1" rule is not modified.

[0699] In a second alternative, the “3+1” rule can be modified to “3+1+1” or “3+1+2”, where the additional “1” or “2” corresponds to the UE budget for monitoring 1 or 2 sizes of multi-cell scheduling DCI format (or formats) separate from the existing DCI format in [TS 38.212v17.1.0].

[0700] In a third alternative, the “3+1” rule can be modified to “N+1”, where N>3 reflects the combined budget of the UE per serving cell for the size of multi-cell scheduling DCI formats or DCI formats with CRC scrambled by C-RNTI.

[0701] In a fourth alternative, the “3+1” rule can be modified to “3+M”, where M>1 reflects the combined budget of the UE per serving cell for the size of multi-cell scheduling DCI formats or DCI formats with CRC not scrambled by C-RNTI.

[0702] In the fifth alternative, the "3+1" rule (or any modified rule described in the above alternative) can be applied per time slot instead of across all time slots. Here, the time slot can be the time slot of the minimum SCS or maximum SCS among the SCS configurations of the co-scheduled cell set, or the time slot of the scheduling cell, or the reference time slot such as 15kHz in FR1 and 60kHz in FR2, or the time slot of the primary cell, or the time slot of the cell with the minimum CIF / cell index, or the time slot of the cell with the maximum CIF / cell index, etc.

[0703] In one example, the UE can report the capability for a modified UE's DCI size budget rule corresponding to one or more of the first / second / third / fourth alternatives described above. In one example, the UE can be provided by higher layers with information about which alternative to use as the modified "3+1" rule, where the "mode" parameter can indicate, for example, the previous four alternatives and any additional higher layer parameters (when applicable).

[0704] In a sixth alternative, the specification for system operation can exclude constraints / restrictions such as the "3+1" rule on the DCI size budget of the UE. For example, the UE is not limited to only the "3+1" DCI format described in [TS 38.213, v17.1.0].

[0705] In one embodiment, a UE configured for multi-cell scheduling of a set of cells that are co-scheduled monitors the same total number of PDCCH candidates and non-overlapping CCEs for the corresponding scheduled cells as when the UE is configured for single-cell scheduling, but when the search space set is used to monitor DCI formats for multi-cell scheduling, the UE counts the number of PDCCH candidates and non-overlapping CCEs for each scheduled cell in the set of cells that are co-scheduled differently. The UE applies a modified method, such as fractional counting, for PDCCH candidates and non-overlapping CCEs in the case of multi-cell scheduling, but applies the method as described in TS 38.213v16.5.0 for monitoring DCI format (or formats) for single-cell scheduling when counting PDCCH candidates and non-overlapping CCEs.

[0706] In the first case, when the UE monitors PDCCH candidates according to the search space set for monitoring multi-cell scheduled DCI formats, the UE counts each PDCCH candidate as a fraction of the maximum number of PDCCH candidates that the UE can monitor in the time slot or span of each scheduled cell in the co-scheduled cell set. For example, for a co-scheduled cell set including 4 cells, the UE counts the PDCCH candidates for 4-cell scheduling as 1 / 4 of the PDCCH candidates, or the fraction of PDCCH candidates provided by higher layers, for each scheduled cell from the set of 4 cells. Similar scaling can be applied to the number of non-overlapping CCEs. This allocation applies regardless of whether a DCI format is detected for the PDCCH candidate, or whether the detected DCI format co-schedules the entire set (such as all 4 cells) or only a subset of co-scheduled configured cells (such as only 2 cells from 4 cells). In this article, the time slot or span is the SCS configuration relative to the active DLBWP of the scheduled cell.

[0707] In one example, the scaling factor for such fractional counting or inverse scaling can be based on the inter-band CA to intra-band CA configuration. For example, the UE treats multiple co-scheduled cells (with intra-band CA configuration) in the same frequency band as a single cell. For example, for a set of 4 co-scheduled cells, where the first 2 cells are intra-band CA in the first frequency band and the last 2 cells are intra-band CA in the second frequency band, the UE counts the first two cells as one "valid" cell and the last two cells as another "valid" cell, so a total of two "valid" cells. Therefore, for each cell in the co-scheduled cell set, the UE counts the PDCCH candidates for such co-scheduled cell set as 1 / 2 (instead of 1 / 4). In another example, for a set of 4 co-scheduled cells, where all 4 cells are intra-band CA in the same frequency band, the UE counts the 4 cells as one "valid" cell, so a total of one "valid" cell. Therefore, for each cell in the co-scheduled cell set, the UE counts the PDCCH candidates for such co-scheduled cell set as 1 (instead of 1 / 4). Similar scaling can be applied to the number of non-overlapping CCEs.

[0708] In one example, the UE may select a search space based on n associated with the search space set. CI The scaling factor for fractional counting or inverse scaling is determined based on the cell-level or set-level CIF value. CI When the set level CIF of the value determines the PDCCH candidate, the UE and the corresponding CI The number of cells in the co-scheduled cell set of the set level CIF value is conversely counted for the PDCCH candidates (respectively, non-overlapping CCEs) monitored according to the multi-cell DCI format. The UE can use various explicit or implicit methods to determine such a set level n associated with the search space set. CI Values, as described in this article.

[0709] Herein, the multi-cell scheduling DCI format can be a DCI format dedicated to multi-cell scheduling, such as DCI format 0_3 or 1_3, or can be a DCI format that can be used for both single-cell scheduling and multi-cell scheduling, for example, based on an explicit indication / flag in the DCI format for distinguishing between single-cell and multi-cell scheduling.

[0710] In one example, the UE applies this inverse scaling or fractional counting when monitoring MC-DCI formats. In another example, the UE applies inverse scaling when monitoring PDCCH for DCI formats shared between single cell and multi-cell scheduling.

[0711] In another example, when monitoring a DCI format shared between single-cell and multi-cell scheduling, the UE does not apply inverse scaling; instead, the UE counts the PDCCH candidates (correspondingly, non-overlapping CCEs) used to monitor such a DCI format as a full count without any scaling of the reference cell and without counting other serving / co-scheduled cells. In this article, the reference cell in the co-scheduled cell set can indicate any example described herein.

[0712] In one example, the UE does not expect to be in communication with n corresponding to the co-scheduled cell set. CI Only DCI formats (or multiple DCI formats) used for single-cell scheduling are monitored in the search space set associated with the set-level CIF of the value. For example, when the UE:

[0713] - a search space set configured to be associated with a CORESET on a scheduling cell, wherein the search space set includes monitoring DCI formats for both single-cell scheduling and multi-cell scheduling, and

[0714] - According to the set level n corresponding to the set of cells to be co-scheduled CI / CIF value associated with the search space set to determine the PDCCH candidate,

[0715] The UE allocates a plurality of PDCCH candidates configured for a search space set to monitor a multi-cell scheduling DCI format (or formats), and does not monitor a DCI format (or formats) used only for single-cell scheduling.

[0716] Herein, the DCI format used only for single-cell scheduling indicates a DCI format not shared with multi-cell scheduling, such as fallback DCI format 0_0 or 1_0.

[0717] In one example, for a search space set associated with multiple co-scheduled cell sets, the UE can count PDCCH candidates (or non-overlapping CCEs) separately for each co-scheduled cell set, or can count PDCCH candidates (or non-overlapping CCEs) only once for a reference co-scheduled cell set. For example, the count of PDCCH candidates (or non-overlapping CCEs) can be based on fractional counting or count inverse scaling, taking into account the corresponding limit of each cell in the co-scheduled cell set. For example, when the UE is configured or determines that the search space set is associated with a first co-scheduled cell set having a first number of cells, and is also associated with a second co-scheduled cell set having a second number of cells, in one option, the UE counts the following items:

[0718] - The first PDCCH candidate (or non-overlapping CCE) corresponding to the first co-scheduled cell set, where reverse scaling is performed based on a first scaling factor, and the first scaling factor is further based on the size (i.e., the first quantity) of the first co-scheduled cell set, and

[0719] - The second PDCCH candidate (or non-overlapping CCE) corresponding to the second co-scheduled cell set, where reverse scaling is performed based on a second scaling factor, and the second scaling factor is further based on the size (i.e., the second quantity) of the second co-scheduled cell set.

[0720] For example, when the search space is associated with a first set of 4 co-scheduled cells and a second set of 8 co-scheduled cells, the UE counts the first PDCCH candidate corresponding to the first co-scheduled cell set as 1 / 4 of the PDCCH candidates for each of the 4 cells in the first set, and counts the second PDCCH candidate corresponding to the second co-scheduled cell set as 1 / 8 of the PDCCH candidates for each of the 8 cells in the second set.

[0721] For example, this option is beneficial when the UE determines the first PDCCH candidate based on the first set-level CIF value corresponding to the first co-scheduled cell set and determines the second PDCCH candidate based on the second set-level CIF value corresponding to the second co-scheduled cell set. For example, this option can be beneficial when the UE determines different sizes of the multi-cell scheduling DCI format corresponding to the first and second co-scheduled cell sets.

[0722] In one example, when the search space is associated with a co-scheduled cell set including N cells, and when M cells in the co-scheduled cell set are deactivated serving cells or have a corresponding active DL BWP as a dormant BWP, where 1 ≤ M < N, the UE counts the PDCCH candidate corresponding to the co-scheduled cell set as:

[0723] - 1 / (N - M) of the PDCCH candidates for each of the N cells; or

[0724] - (N - M) of the PDCCH candidates for each of the other (N - M) cells having active and non-dormant cells / BWPs, and for the PDCCH candidates of the M cells, count 0; or

[0725] - The PDCCH candidates for each of the N cells; or

[0726] - a PDCCH candidate for each of the other (NM) cells with activated and non-dormant cells / BWPs, and for the PDCCH candidates of the M cells, the count is 0; or

[0727] - Only PDCCH candidates for a single reference cell, and for PDCCH candidates for other cells, the count is 0.

[0728] Similarly, the UE counts the L non-overlapping CCEs corresponding to the PDCCH candidates as:

[0729] - L / (NM) of PDCCH candidates for each of the N cells; or

[0730] - L / (NM) for PDCCH candidates of each of the other (NM) cells with activated and non-dormant cells / BWPs, and for the PDCCH candidates of the M cells, the count is 0; or

[0731] - L PDCCH candidates for each of the N cells; or

[0732] - L PDCCH candidates for each of the other (NM) cells with activated and non-dormant cells / BWPs, and a count of 0 for the PDCCH candidates of the M cells; or

[0733] - Only L PDCCH candidates for a single reference cell, and the count is 0 for PDCCH candidates of other cells.

[0734] In one example, the UE is able to report the capability of which option the UE supports from the above options for BD / CCE counting in the presence of a deactivated cell or dormant BWP.

[0735] For example, when the UE is configured with a search space set associated with:

[0736] - A first co-scheduled cell set, comprising M cells and corresponding to a first set-level CIF value, such as n CI,1 ,and

[0737] - A second co-scheduled cell set, comprising N cells and corresponding to a second set level CIF value, such as n CI,2 ,

[0738] UE based on n CI,1 The search space set is used to determine the first PDCCH candidate, and the search space set is based on n CI,2The UE determines the second PDCCH candidate based on the search space set of the first coordinated scheduled cell set. Then, the UE counts the first PDCCH candidates based on a first predetermined or configured scaling factor corresponding to the M cells in the first coordinated scheduled cell set, and counts the second PDCCH candidates based on a second predetermined or configured scaling factor corresponding to the N cells in the second coordinated scheduled cell set. For example, the UE determines the first scaling factor to be 1 / M for the M cells in the first coordinated scheduled cell set, and determines the second scaling factor to be 1 / N for the N cells in the second coordinated scheduled cell set. For example, the UE determines the first scaling factor to be 1 for the first reference cell, determines the first scaling factor to be 0 for other cells from the M cells in the first coordinated scheduled cell set, and determines the second scaling factor to be 1 for the second reference cell, and determines the second scaling factor to be 0 for other cells from the N cells in the second coordinated scheduled cell set. The first reference cell can be the same as or different from the second reference cell.

[0739] In one example, higher layers can provide the UE with a first scaling factor value α for M cells in the first co-scheduled cell set. 1 and a second scaling factor value α for the N cells in the second cooperatively scheduled cell set 2 Therefore, the UE counts the candidate PDCCH from the first candidate PDCCH as α of the M cells in the cell set for the first coordinated scheduling. 1 candidate PDCCHs, and count the candidate PDCCHs from the second candidate PDCCH as α of the N cells in the cell set for the second coordinated scheduling. 2 candidate PDCCHs.

[0740] In one example, based on UE capabilities or higher layer configuration, the UE can count PDCCH candidates from the first candidate PDCCH as 1 or 2 (or 3) PDCCH candidates across the M cells in the first co-scheduled cell set. For example, the UE counts PDCCH candidates from the first PDCCH candidate as α for each of the M cells in the first co-scheduled cell set. 1 or 2α 1 or 3α 1 For example, the UE counts the PDCCH candidates from the second PDCCH candidate as α for each of the N cells from the second co-scheduled cell set. 2 or 2α 2 or 3α 2 PDCCH candidates.

[0741] In one example, the UE can be configured by higher layers with different values ​​for different cells in the co-scheduled set of cells for counting PDCCH candidates. These values ​​can be specific to a search space set or co-scheduled set of cells, or shared across different search space sets or co-scheduled sets of cells associated with / including a given cell.

[0742] A similar example can be applied to non-overlapping CCEs, where L non-overlapping CCEs corresponding to PDCCH candidates with CCE AL value equal to L are counted.

[0743] In another option, the UE counts both the first PDCCH candidate and the second PDCCH candidate into the corresponding limit of each co-scheduled cell based on fractional counting or inverse scaling using a shared scaling factor. For example, the shared scaling factor can be a reference scaling factor. For example, the reference scaling factor can be based on the minimum size or maximum size among the sizes of multiple co-scheduled cell sets. In the above example, both the first candidate PDCCH and the second candidate PDCCH are counted as 1 / 4 (or both are counted as 1 / 8), counted into the corresponding limit of each of the 4 cells from the first co-scheduled cell set or each of the 8 cells from the second co-scheduled cell set. Similar examples apply to non-overlapping CCEs.

[0744] In a variation of this option, the UE determines PDCCH candidates based only on a reference set of co-scheduled cells, and therefore, the fractional count or inverse scaling of the count of PDCCH candidates (or non-overlapping CCEs) is based on a reference scaling factor, which in turn is based on the size of the reference co-scheduled cell set (or based on a reference size of the co-scheduled cell set). For example, the reference co-scheduled cell set can be a co-scheduled cell set with the following items:

[0745] - the minimum collection level CIF value, or

[0746] - the maximum collection level CIF value, or

[0747] - the minimum size of a set of multiple co-scheduled cells, or

[0748] - the maximum size of a set of multiple co-scheduled cells, or

[0749] - CIF value provided by higher layers.

[0750] In another example, the reference co-scheduled cell set can be a set including reference cells (having minimum / maximum CIF values ​​or set sizes), wherein various examples for determining the reference cells are previously described herein.

[0751] In another example, when the UE is based on the cell level n corresponding to the single scheduled cell CI When monitoring PDCCH candidates in the search space set according to the value, in a first option, the UE counts the monitored PDCCH candidates (or non-overlapping CCEs) differently for the single-cell scheduling DCI format compared to the MC-DCI format (or multiple). For example, when monitoring PDCCH candidates (or non-overlapping CCEs) to decode the SC-DCI format, the UE counts the PDCCH candidates (or non-overlapping CCEs) as a full count without any scaling, counting the PDCCH candidates (or non-overlapping CCEs) used for decoding with cell level n. CI The UE may use a restriction of a single scheduled cell associated with a value. For example, when monitoring PDCCH candidates (or non-overlapping CCEs) to decode MC-DCI format (dedicated), the UE counts PDCCH candidates (or non-overlapping CCEs) using inverse scaling or fractional counting. Herein, fractional counting or inverse scaling is based on the size of the co-scheduled cell set, the corresponding set-level CIF value of the co-scheduled cell set being provided, such as by a higher layer configuration of the search space set.

[0752] In one example, when the UE is configured to:

[0753] - According to the cell level n corresponding to a single scheduled cell CI value to monitor the PDCCH candidates in the search space set, and

[0754] - monitor the multi-cell scheduling DCI format in the search space set, and

[0755] - Multiple set-level CIF values ​​corresponding to multiple sets of co-scheduled cells, used for decoding multi-cell scheduling DCI formats,

[0756] The UE counts the number of PDCCH candidates (or non-overlapping CCEs) based on fractional counting or inverse scaling, where the scaling factor is based on the size of the reference CIF value (or the size of the reference co-scheduled cell set). For example, the reference CIF value can be:

[0757] - minimum setting level CIF value, or

[0758] Maximum setting level CIF value, or

[0759] - a CIF value corresponding to a co-scheduled cell set having a smallest size among a plurality of co-scheduled cell sets, or

[0760] - A CIF value corresponding to a co-scheduled cell set having a largest size among a plurality of co-scheduled cell sets.

[0761] In another example, the reference CIF value can be a CIF value of a reference cell, where the reference cell can be based on the examples provided herein.

[0762] When the UE monitors PDCCH candidates in the search space set according to the cell level value corresponding to a single scheduled cell, in the second option, the UE counts the monitored PDCCH candidates (or non-overlapping CCEs) similarly for the single-cell scheduling DCI format and the MC-DCI format. For example, the UE counts the PDCCH candidates (or non-overlapping CCEs) as a full count without any scaling, counting the PDCCH candidates (or non-overlapping CCEs) used for the cell level n. CI The restriction of a single scheduling cell associated with the value is implemented regardless of whether the UE monitors PDCCH candidates (or non-overlapping CCEs) to decode the SC-DCI format or the MC-DCI format.

[0763] In one example, for example, due to the potential larger size of the MC-DCI format, the UE can count the PDCCH candidates for decoding the MC-DCI format as more than one PDCCH candidate. For example, the UE can count the PDCCH candidates for decoding the MC-DCI format based on a scaling factor, such as two PDCCH candidates. Similarly, the UE can count L non-overlapping CCEs for decoding according to the MC-DCI format by a scaling factor, such as 2*L non-overlapping CCEs. In another example, the scaling factor can be provided by a higher layer or by a specification of system operation. In another example, the UE can report the ability of the UE to count PDCCH candidates (or corresponding L non-overlapping CCEs) with or without a scaling factor. In one example, there can be different scaling factors (and corresponding different higher layer parameters, or corresponding different UE capabilities) for PDCCH candidates compared to non-overlapping CCEs.

[0764] In one example, the UE applies the above example rules for fractional counting or inverse scaling when counting PDCCH candidates or non-overlapping CCEs towards the corresponding number of per-scheduling cell limits. For example, the UE does not apply any fractional counting or inverse scaling when counting PDCCH candidates or non-overlapping CCEs towards the corresponding number of per-scheduling cell limits. For example, the UE counts PDCCH candidates for decoding the MC-DCI format for multi-cell scheduling as a full count of the maximum number of PDCCH candidates that the UE can monitor in the time slot of the scheduling cell (i.e., one PDCCH candidate without any inverse scaling). Similarly, the UE counts L non-overlapping CCEs for decoding the MC-DCI format for multi-cell scheduling as a full count, counting the maximum number of non-overlapping CCEs that the UE can monitor in the time slot of the scheduling cell (i.e., L non-overlapping CCEs without any inverse scaling).

[0765] In another example, similar to introducing multiple reference cells for counting the MC-DCI format size into the limitation of the DCI format size, multiple reference cells can be introduced for counting multiple PDCCH candidates and multiple non-overlapping CCEs for decoding the MC-DCI format. The reference cell can be the same as the cell used to count the MC-DCI format size. For example, the SCell in the co-scheduled cell set can be associated with the MC-DCI format (DCI format 1_3) for scheduling PDSCH reception and the MC-DCI format (DCI format 0_3) for scheduling PUSCH transmission, for example, through information based on UE-specific higher layer signaling. For example, the first SCell in the co-scheduled cell set can be associated with the MC-DCI format (DCI format 1_3) for scheduling PDSCH reception, for example, through information based on UE-specific higher layer signaling, and the second SCell in the co-scheduled cell set can be associated with the MC-DCI format (DCI format 0_3) for scheduling PUSCH transmission.

[0766] In the second case, when the UE monitors PDCCH candidates on the search space set associated with the first scheduled cell from the set of cells configured for cooperative scheduling, and also monitors PDCCH candidates of the DCI format for detecting single-cell scheduling associated with the first scheduled cell, the UE does not consider multi-cell scheduling for allocating PDCCH candidates. Therefore, the UE counts all PDCCH candidates associated with only the search space set into the PDCCH monitoring allocation for the first scheduled cell.

[0767] As described herein, the search space set for multi-cell scheduling can be:

[0768] - a set of search spaces associated with MC-DCI formats only, or

[0769] - a set of search spaces associated with both the MC-DCI format and the SC-DCI format, or

[0770] - A set of search spaces associated...

Claims

1. A method performed by a user equipment (UE), include: receiving first information of a plurality of cell sets and second information of a first user equipment (UE) specific search space (USS) set for receiving a first physical downlink control channel (PDCCH) candidate on a scheduling cell, wherein the first USS set has a first USS set identifier and is associated with a first downlink control information (DCI) format for scheduling on more than one cell; and Determine a first cell set associated with the first USS set from the multiple cell sets and a first reference cell from the first cell set, wherein a first size of the first DCI format is counted in multiple sizes of DCI formats used for scheduling on the first reference cell and is not counted in multiple sizes of DCI formats used for scheduling on cells other than the first reference cell from the first cell set, and wherein, when the scheduling cell is included in the first cell set and the first USS set is the only USS set having the first USS identifier among the USS sets on the cells in the first cell set, the first reference cell is the scheduling cell.

2. The method according to claim 1, in, The number of the first PDCCH candidates and the corresponding number of first non-overlapping control channel elements CCE for the first USS set are respectively counted in the number of PDCCH candidates and the corresponding number of non-overlapping CCEs for the first reference cell, and are not respectively counted in the number of PDCCH candidates and the corresponding number of non-overlapping CCEs for cells other than the first reference cell from the first cell set.

3. The method according to claim 1, further comprising: include: receiving third information of a second USS set on a cell in the cell set, wherein the second USS set has the first USS set identifier; and The first cell set is determined as the cell set, and the first reference cell is determined as the cell.

4. The method according to claim 1, further comprising: include: receiving third information of a second USS set for receiving a second PDCCH candidate on the first reference cell, fourth information for a first indicator value corresponding to the first cell set, and fifth information for a second indicator value corresponding to the first reference cell, wherein the second USS set is associated with a second DCI format for scheduling only on the first reference cell; and A first control channel element (CCE) for receiving the first PDCCH candidate is determined based on the first USS set and the first indicator value, and a second CCE for receiving a second PDCCH candidate is determined based on the second USS set and the second indicator value.

5. A user equipment (UE), include: a transceiver configured to receive first information of a plurality of cell sets and second information of a first UE-specific search space (USS) set for receiving a first physical downlink control channel (PDCCH) candidate on a scheduling cell, wherein the first USS set has a first USS set identifier and is associated with a first downlink control information (DCI) format for scheduling on more than one cell; and a processor operatively connected to the transceiver, the processor configured to determine: a first set of cells from the plurality of cell sets associated with the first set of USSs and a first reference cell from the first set of cells, wherein a first size of the first DCI format is counted in a plurality of sizes of DCI formats used for scheduling on the first reference cell and is not counted in a plurality of sizes of DCI formats used for scheduling on cells other than the first reference cell from the first set of cells, and When the scheduling cell is included in the first cell set, and when the first USS set is a unique USS set having the first USS identifier among USS sets on cells in the first cell set, the first reference cell is the scheduling cell.

6. The UE according to claim 5, in, The number of the first PDCCH candidates and the corresponding number of first non-overlapping control channel elements (CCEs) for the first USS set are counted in the number of PDCCH candidates and the corresponding number of non-overlapping CCEs for the first reference cell, respectively, and are not counted in the number of PDCCH candidates and the corresponding number of non-overlapping CCEs for cells from the first cell set other than the first reference cell, respectively.

7. The UE according to claim 5, in: The transceiver is further configured to receive third information of a second USS set on a cell in the cell set, wherein the second USS set has a first USS set identifier; and The processor is further configured to determine the first cell set as the cell set, and determine the first reference cell as the cell.

8. The UE according to claim 5, in, The transceiver is further configured to receive third information of a second USS set for receiving a second PDCCH candidate on the first reference cell, fourth information for a first indicator value corresponding to the first cell set, and fifth information for a second indicator value corresponding to the first reference cell, wherein the second USS set is associated with a second DCI format for scheduling only on the first reference cell; and The processor is further configured to determine a first control channel element (CCE) for receiving a first PDCCH candidate based on the first USS set and the first indicator value, and to determine a second CCE for receiving the second PDCCH candidate based on the second USS set and the second indicator value.

9. A method performed by a base station (BS), include: Sending first information of a plurality of cell sets and second information of a first user equipment (UE) specific search space (USS) set for sending a first physical downlink control channel (PDCCH) on a scheduling cell, wherein the first USS set has a first USS set identifier and is associated with a first downlink control information (DCI) format for scheduling on more than one cell; and Determine a first cell set associated with the first USS set from the multiple cell sets and a reference cell from the first cell set, wherein a size of a first DCI format is counted in multiple sizes of DCI formats used for scheduling on the first reference cell and is not counted in multiple sizes of DCI formats used for scheduling on cells other than the reference cell from the first cell set, and wherein, when the scheduling cell is included in the first cell set and the first USS set is the only USS set having the first USS identifier among the USS sets on the cells in the first cell set, the first reference cell is the scheduling cell.

10. The method according to claim 9, in, The first set of USSs is associated with a number of the first PDCCHs and a corresponding number of first non-overlapping control channel elements (CCEs), and wherein the number of the first PDCCHs and the corresponding number of the first non-overlapping CCEs are respectively counted in the number of PDCCHs and the corresponding number of non-overlapping CCEs used for the reference cell, and are not respectively counted in the number of PDCCHs and the corresponding number of non-overlapping CCEs used for cells other than the reference cell from the first cell set.

11. The method according to claim 9, further comprising: include: sending third information of a second USS set on a cell in the cell set, wherein the second USS set has the first USS set identifier; and The first cell set is determined as the cell set, and the reference cell is determined as the cell.

12. A base station (BS), include: a transceiver configured to transmit first information of a plurality of cell sets and second information of a first user equipment (UE) specific search space (USS) set for transmitting a first physical downlink control channel (PDCCH) on a scheduling cell, wherein the first USS set has a first USS set identifier and is associated with a first downlink control information (DCI) format for scheduling on more than one cell; and a processor operably connected to the transceiver, the processor configured to determine a first set of cells associated with the first set of USSs from the plurality of cell sets and a reference cell from the first set of cells, wherein a size of a first DCI format is counted in a plurality of sizes of DCI formats for scheduling on the reference cell and is not counted in a plurality of sizes of DCI formats for scheduling on cells from the first set of cells other than the reference cell, and When the scheduling cell is included in the first cell set, and the first USS set is a unique USS set having the first USS identifier among USS sets on cells in the first cell set, the reference cell is the scheduling cell.

13. The base station according to claim 12, in, The first set of USSs is associated with a number of the first PDCCHs and a corresponding number of first non-overlapping control channel elements (CCEs), and wherein the number of the first PDCCHs and the corresponding number of the first non-overlapping CCEs are respectively counted in the number of PDCCHs and the corresponding number of non-overlapping CCEs used for the reference cell, and are not respectively counted in the number of PDCCHs and the corresponding number of non-overlapping CCEs used for cells other than the reference cell from the first cell set.

14. The base station according to claim 12, in, The transceiver is further configured to transmit third information of a second USS set on a cell in the cell set, wherein the second USS set has the first USS set identifier; and The processor is further configured to determine the first cell set as the cell set, and determine the reference cell as the cell.

15. The base station according to claim 12, in, The transceiver is further configured to transmit third information of a second USS set for transmitting a second PDCCH on the reference cell, fourth information for a first indicator value corresponding to the first cell set, and fifth information for a second indicator value corresponding to the reference cell, wherein the second USS set is associated with a second DCI format for scheduling only on the reference cell; and The processor is further configured to determine a first CCE for sending a first PDCCH based on the first USS set and the first indicator value, and to determine a second CCE for sending the second PDCCH based on the second USS set and the second indicator value.

Images