DCI field for multi-cell scheduling

By using a single DCI format and one-to-many mapping table for multi-cell scheduling in the 5G mobile communication system, the problem of large signaling overhead is solved, efficient multi-cell scheduling is achieved, and system performance is improved.

CN118985165APending Publication Date: 2024-11-19SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202380035466.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-04-07
Filing Date
2023-04-21
Publication Date
2024-11-19

AI Technical Summary

Technical Problem

The existing 5G mobile communication systems have large signaling overhead in multi-cell scheduling, especially when the number of cells jointly scheduled is large, resulting in significant control signaling overhead and affecting system performance.

Method used

Multi-cell scheduling is used to use a single DCI format, and signaling overhead is reduced through one-to-many mapping tables or configuration of offset parameters, and public and specific scheduling parameters are reasonably configured in the DCI format, which is suitable for different cells.

Benefits of technology

It realizes the scheduling flexibility while reducing signaling overhead, and is suitable for multiple co-scheduled cells, improving system performance and efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118985165A_ABST
    Figure CN118985165A_ABST
Patent Text Reader

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The present invention relates to an apparatus and a method for a downlink control information (DCI) field for multi-cell scheduling, and more particularly, to an apparatus and a method for a downlink control information (DCI) field for multi-cell scheduling. In one embodiment, a method includes receiving first information for a set of cells, and identifying a first time-domain resource allocation (TDRA) table having a one-to-one mapping with cells in the set of cells. The method further includes receiving second information of a second TDRA table for receiving a physical downlink shared channel (PDSCH) on a cell of the group of cells, a physical downlink control channel (PDCCH) that provides a downlink control information (DCI) format, the DCI format including a TDRA field indicating a first row of the second TDRA table, and receiving the second information of the second TDRA table for receiving, on a cell of the group of cells, a physical downlink control channel (PDCCH) that provides a downlink control information (DCI) format. The method further includes determining first time resources for reception of the first PDSCH on the first cell based on the first entries of the first row of the second TDRA table, respectively, and receiving the first PDSCH on the first cell in the first time resources, respectively.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates generally to wireless communication systems, and more particularly, to downlink control information (DCI) fields for multi-cell scheduling. Background Art

[0002] At the beginning of the development of 5G mobile communication technology, in order to support services and meet the performance requirements related to enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization on beamforming and massive MIMO for mitigating radio wave path loss and increasing radio wave transmission distance in mmWave, parameter sets to support dynamic operation for efficient utilization of mmWave resources and time slot formats (e.g., operating multiple subcarrier spacings), initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bandwidth Part) new channel coding methods such as LDPC (Low Density Parity Check) codes for large data transmission and polar codes for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing dedicated networks dedicated to specific services.

[0003] Currently, in view of the services that 5G mobile communication technology is to support, there are ongoing discussions on improvements and performance enhancements of initial 5G mobile communication technology, and there has been physical layer standardization on technologies such as V2X (Vehicle-to-everything) for assisting driving determination of autonomous vehicles based on information on 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 complies with various regulatory-related requirements in unlicensed bands, NR UE power saving, non-terrestrial network (NTN) as UE-satellite direct communication for providing coverage in areas where communication with terrestrial networks is unavailable, and positioning.

[0004] In addition, there has been ongoing standardization on air interface architecture / protocols such as 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 extension by supporting wireless backhaul links and access links in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access (NR's two-step RACH) for simplifying the random access procedure. There is also ongoing standardization on system architecture / services for 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE location.

[0005] As 5G mobile communication systems are commercialized, the number of connected devices, which has been growing exponentially, will be connected to the communication network, and it is accordingly expected that enhanced functions and performance of the 5G mobile communication systems and integrated operations of the connected devices will be necessary. To this end, new research related to extended reality (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, metaverse service support, and drone communication.

[0006] Furthermore, this development of 5G mobile communication systems will serve as the basis for the development of not only new waveforms for providing terahertz band coverage 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 terahertz band signal coverage, high-dimensional spatial multiplexing technologies using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for improving frequency efficiency and improving system networks for 6G mobile communication technology, AI-based communication technology for achieving system optimization using 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 limits of UE operating capabilities using ultra-high-performance communication and computing resources.

[0007] The fifth generation (5G) or new radio (NR) mobile communications has been gathering more and more momentum recently with all the global technical activities from industry and academia on various candidate technologies. Candidate enablers for 5G / NR mobile communications include massive antenna technologies from traditional cellular frequency bands to high frequencies to provide beamforming gain and support increased capacity, new waveforms (e.g., new radio access technology (RAT)) to flexibly accommodate various services / applications with different requirements, new multiple access schemes to support massive connections, etc. Summary of the invention

[0008] Technical issues

[0009] The present disclosure relates to a wireless communication system, and more particularly, to an apparatus and method for a DCI field for multi-cell scheduling in a wireless communication system.

[0010] Technical Solution

[0011] In one embodiment, a method performed by a user equipment (UE) includes: receiving first information of a set of cells, and identifying a first time domain resource allocation (TDRA) table having a one-to-one mapping with a cell in the set of cells. A row of a first TDRA table from the first TDRA table indicates a time resource for reception of a physical downlink shared channel (PDSCH) on a cell in the set of cells. The method also includes receiving second information of a second TDRA table for reception of a PDSCH on a cell in the set of cells, and receiving a physical downlink control channel (PDCCH) on a scheduling cell. The PDCCH provides a downlink control information (DCI) format. The DCI format schedules reception of a first PDSCH on a first cell in the set of cells, respectively. The DCI format includes a TDRA field indicating a first row of a second TDRA table. The first row includes a first entry having a one-to-one mapping with a first cell. An entry from the first entry indicates a row from the first TDRA table. The method also includes determining a first time resource for reception of a first PDSCH on a first cell based on a first entry of a first row of the second TDRA table, respectively, and receiving a first PDSCH on the first cell in the first time resource, respectively.

[0012] In another embodiment, a user equipment (UE) includes a transceiver and a processor, the processor being configured to receive first information of a cell set to identify a first TDRA table having a one-to-one mapping with a cell in the cell set. A row of a first TDRA table from the first TDRA table indicates a time resource for receiving a PDSCH channel on a cell in the group of cells, and receives a second TDRA table for receiving a PDSCH on a cell in the group of cells and second information for receiving a PDCCH on a scheduling cell. The PDCCH provides a DCI format. The DCI format schedules the reception of a first PDSCH on a first cell in the cell set, respectively. The DCI format includes a TDRA field indicating a first row of a second TDRA table. The first row includes a first entry having a one-to-one mapping with a first cell. The entry from the first entry indicates a row from the first TDRA table. The processor is also configured to determine a first time resource for receiving a first PDSCH on a first cell, respectively, based on a first entry of a first row of the second TDRA table. The processor is also configured to receive a first PDSCH on a first cell in a first time resource, respectively.

[0013] In another embodiment, a base station is provided. The base station includes a transceiver and a processor. The processor is configured to identify a first TDRA table having a one-to-one mapping with a cell in a cell set. A row of the first TDRA table from the first TDRA table indicates a time resource for transmitting a PDSCH on a cell in the cell set. And the processor is also configured to transmit second information of a second TDRA table for transmitting a PDSCH on a cell in the group of cells and a PDCCH on a scheduling cell. PDCCH provides a DCI format. The DCI format schedules the transmission of a first PDSCH on a first cell in a cell set, respectively. The DCI format includes a TDRA field indicating a first row of a second TDRA table. The first row includes a first entry having a one-to-one mapping with a first cell. The entry from the first entry indicates a row from the first TDRA table. The processor is also configured to determine a first time resource for the transmission of a first PDSCH on a first cell based on a first entry of a first row of a second TDRA table, respectively, and is configured to send a first PDSCH on a first cell in a first time resource, respectively.

[0014] In yet another embodiment, a method performed by a base station includes: sending first information of a cell set, and identifying a first time domain resource allocation (TDRA) table having a one-to-one mapping with a cell in the cell set. A row of a first TDRA table from the first TDRA table indicates a time resource for receiving a physical downlink shared channel (PDSCH) on a cell in the cell set. The method also includes sending second information of a second TDRA table, the second TDRA table being used for receiving a PDSCH on a cell in the cell set, and sending a physical downlink control channel (PDCCH) on a scheduling cell. The PDCCH provides a downlink control information (DCI) format. The DCI format schedules reception of a first PDSCH on a first cell in the cell set, respectively. The DCI format includes a TDRA field indicating a first row of a second TDRA table. The first row includes a first entry having a one-to-one mapping with a first cell. An entry from the first entry indicates a row from the first TDRA table. The method also includes determining a first time resource for receiving a first PDSCH on a first cell based on a first entry of a first row of the second TDRA table, respectively, and sending a first PDSCH on the first cell in the first time resource, respectively.

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

[0016] Beneficial Effects

[0017] Advantages and salient features of the invention will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses exemplary embodiments of the invention.

[0018] According to various embodiments of the present disclosure, a method and apparatus for a DCI field for multi-cell scheduling may be provided. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] 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:

[0020] FIG1 illustrates an example wireless network according to an embodiment of the present disclosure;

[0021] FIG2 illustrates an example gNodeB (gNB) according to an embodiment of the present disclosure;

[0022] FIG3 illustrates an example user equipment (UE) according to an embodiment of the present disclosure;

[0023] FIG4 shows a method for multi-cell scheduling for a UE according to an embodiment of the present disclosure, where the UE is configured with multiple sets of co-scheduled cells;

[0024] FIG5 illustrates a method for multi-cell scheduling based on reference values ​​and differential values ​​of cell-specific scheduling parameters according to an embodiment of the present disclosure;

[0025] FIG6 illustrates a method for multi-cell scheduling based on a DCI field with multi-cell mapping using a configured one-to-many mapping / table according to an embodiment of the present disclosure;

[0026] FIG. 7 illustrates a method for multi-cell scheduling based on a DCI field with a multi-cell mapping table according to an embodiment of the present disclosure;

[0027] FIG8 illustrates a method for multi-cell scheduling based on a DCI field with multi-cell mapping and a set of operating levels for co-scheduled cells according to an embodiment of the present disclosure; and

[0028] FIG. 9 illustrates a method for performing multi-cell scheduling based on a DCI field with multi-cell mapping using a plurality of configured adjustment parameters corresponding to a plurality of co-scheduled cells according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0029] Before carrying out the following inventive mode, 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, included in, 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, 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. The phrase "at least one of" when used with a list of items means that different combinations of one or more of the listed items can be used, and that 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.

[0030] In addition, the various functions described below may 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" refer to 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 disc (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 or other signals. Non-transitory computer-readable media include media in which data can be permanently stored and media in which data can be stored and later rewritten, such as rewritable optical discs or erasable memory devices.

[0031] 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.

[0032] FIG. 1 to FIG. 9 discussed below and the various embodiments used to describe the principles of the present disclosure in this patent document are illustrative 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 suitably arranged system or device.

[0033] The following documents and standard descriptions are hereby incorporated by reference into the present disclosure as if fully set forth herein: 3GPP TS 38.211 Rel-16 v17.1.0, “NR; Physical channels and modulation”; 3GPP TS 38.212 Rel-16 v17.1.0, “NR; Multiplexing and channel coding”; 3GPP TS 38.213 Rel-16 v17.1.0, “NR; Physical layer procedures for control”; 3GPP TS 38.214 Rel-16 v17.1.0, “NR; Physical layer procedures for data”; 3GPP TS 38.321 Rel-16 v17.0.0, “NR; Medium Access Control (MAC) protocol specification”; 3GPP TS 38.331 Rel-16 v17.0.0, “NR; Radio Resource Control (RRC) protocol specification"; 3GPP TS38.300 Rel-16 v17.0.0, "NR; NR and NG-RAN Overall Description; Stage 2".

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

[0035] 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 (e.g., 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.

[0036] In addition, in 5G / NR communication systems, system network improvements are being developed based on advanced small cells, cloud radio access networks (RANs), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communications, coordinated multi-points (CoMP), and receiving-side interference cancellation.

[0037] The discussion of 5G systems and frequency bands associated therewith is for reference, as 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 used in conjunction with any frequency band. For example, aspects of the present disclosure may also be applied to the deployment of 5G communication systems, 6G, or even later versions that may use terahertz (THz) frequency bands.

[0038] The following Figures 1-3 describe various embodiments implemented in a wireless communication system and using orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication technology. The description of Figures 1-3 is not meant to imply physical or architectural limitations on the manner in which different embodiments can be implemented. Different embodiments of the present disclosure can be implemented in any appropriately arranged communication system.

[0039] FIG1 illustrates an example wireless network 100 according to the present disclosure. The embodiment of the wireless network 100 shown in FIG1 is for illustration only. Other embodiments of the wireless network 100 may be used without departing from the scope of the present disclosure.

[0040] 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.

[0041] 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 refer to 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 refer to 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). A UE may also be a car, truck, van, drone, or any similar machine or a device in such a machine.

[0042] gNB 102 provides wireless broadband access to network 130 for a first plurality of user equipments (UEs) within coverage area 120 of gNB 102. The first plurality of UEs include 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 notebook, 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 include 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 the coverage area of ​​the network or other UEs outside the coverage area of ​​the network.

[0043] 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 gNBs, 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.

[0044] As described in more detail below, one or more of BS 101, BS 102, and BS 103 include a 2D antenna array as described in embodiments of the present disclosure. In some embodiments, one or more of BS 101, BS 102, and BS 103 support codebook design and structure for systems with 2D antenna arrays.

[0045] Although FIG1 shows one example of a wireless network 100, various changes may be made to FIG1. ​​For example, wireless network 100 may include any number of gNBs and any number of UEs in any suitable arrangement. In addition, gNB 101 may communicate directly with any number of UEs and provide those UEs with wireless broadband access to network 130. Similarly, each gNB 102-103 may communicate directly with network 130 and provide UEs with direct wireless broadband access to network 130. In addition, gNBs 101, 102, and / or 103 may provide access to other or additional external networks, such as an external telephone network or other type of data network.

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

[0047] FIG2 illustrates an example gNB 102 according to the present disclosure. The embodiment of gNB 102 shown in FIG2 is for illustration only, and other gNBs of FIG1 may have the same or similar configuration. However, gNBs have a variety of configurations, and FIG2 does not limit the scope of the present disclosure to any particular implementation of a gNB. Note that gNB 101 and gNB 103 may include the same or similar structure as gNB 102.

[0048] As shown in Figure 2, 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.

[0049] The transceivers 210a-210n receive incoming RF signals from the antennas 205a-205n, such as signals sent 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 also process the baseband signals.

[0050] Transmit (TX) processing circuitry in the transceivers 210a-210n and / or the controller / processor 225 receives analog or digital data (such as voice data, network 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 a processed baseband or IF signal. The transceivers 210a-210n up-convert the baseband or IF signal to an RF signal that is transmitted via the antennas 205a-205n.

[0051] 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 according to 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 direct the outgoing signals in a desired direction. As another example, the controller / processor 225 may support methods for supporting DCI fields for multi-cell scheduling. The controller / processor 225 may support any of a variety of other functions in the gNB 102.

[0052] The controller / processor 225 is also capable of executing programs and other processes, such as an OS (operating system), that reside in the memory 230. The controller / processor 225 can move data into or out of the memory 230 as required by the executing process.

[0053] 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 over a backhaul connection or over a network. The interface 235 may support communication over any suitable wired or wireless connection. 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 over 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 with a larger network (such as the Internet) over a wired or wireless local area network or over a wired or wireless connection. The interface 235 includes any suitable structure that supports communication over a wired or wireless connection, such as Ethernet or a transceiver.

[0054] 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.

[0055] Although FIG2 shows one example of a gNB 102, various changes may be made to FIG2. For example, the gNB 102 may include any number of each component shown in FIG2. In addition, various components in FIG2 may be combined, further subdivided, or omitted, and additional components may be added as needed.

[0056] FIG3 shows an example UE 116 according to an embodiment of the present disclosure. The embodiment of UE 116 shown in FIG3 is for illustration only, and UEs 111-115 of FIG1 may have the same or similar configurations. However, UEs have a variety of configurations, and FIG3 does not limit the scope of the present disclosure to any particular implementation of the UE.

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

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

[0059] The TX processing circuitry in the transceiver(s) 310 and / or processor 340 receives analog or digital voice data from the microphone 320, or receives other outgoing baseband data (such as network 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.

[0060] The processor 340 may include one or more processors or other processing devices and executes 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(s) 310 according to well-known principles. In some embodiments, the processor 340 includes at least one microprocessor or microcontroller.

[0061] The processor 340 is also capable of executing other processes and programs resident in the memory 360. The processor 340 can move data into or out of the memory 360 as needed for the execution process. 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.

[0062] Processor 340 is also coupled to input 350 including, for example, a touch screen, a keypad, etc., and display 355. An operator of UE 116 may use input 350 to enter data into UE 116. Display 355 may be a liquid crystal display, a light emitting diode display, or other display capable of presenting text and / or at least limited graphics, such as from a website.

[0063] 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).

[0064] Although FIG. 3 shows an example of UE 116, various changes may be made to FIG. 3. For example, various components in FIG. 3 may be combined, further subdivided, or omitted, and additional components may be added as required. As a specific example, processor 340 may be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). In another example, transceiver 310 may include any number of transceivers and signal processing chains, and may be connected to any number of antennas. In addition, although FIG. 3 shows UE 116 configured as a mobile phone or smart phone, the UE may be configured to operate as other types of mobile or fixed devices.

[0065] Various embodiments of the present disclosure consider enhancement of cross-carrier scheduling operations in a carrier aggregation (CA) framework to support joint scheduling of multiple cells.

[0066] In a conventional 5G NR system, downlink or uplink data transmission may be scheduled only for 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 scheduled cell, the UE receives the DCI format for PDSCH / PUSCH in the PDCCCH received by the UE on the corresponding scheduling cell. Based on the carrier indication field (CIF) in the DCI format, the UE is able to determine the serving cell on which the UE can receive PDSCH or send PUSCH.

[0067] However, legacy NR systems do not support co-scheduling multiple PDSCHs or multiple PUSCHs on multiple cells using a single / common control signaling (such as by using a single DCI format). For such operation, the UE receives multiple DCI formats, each of which can schedule one of multiple PDSCHs or PUSCHs. Such operation achieves the desired results, but may have high signaling overhead. In various scenarios, several scheduling parameters or corresponding UE operations may be shared / common between multiple PDSCHs or PUSCHs on a jointly scheduled cell (referred to as a co-scheduled cell).

[0068] For example, a UE may use the same PUCCH resource to send HARQ-ACK feedback corresponding to multiple PDSCHs. Therefore, indications for the same PUCCH resource (and corresponding operations for PUCCH transmission) 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 regarding link adaptation, MIMO / beamforming operations, and even possible resource allocation may be common and repeated between co-scheduled cells. This unnecessary overhead in control signaling may be significant, especially when the number of co-scheduled cells is large, such as 4-8 cells. Last but not least, the CRC field needs to be repeated multiple times, which causes significant signaling overhead, especially for a large number of co-scheduled cells.

[0069] Various embodiments of the present disclosure recognize the need for multi-cell scheduling, where multiple cells can be jointly scheduled using reduced signaling overhead, for example by using only a single DCI format. In addition, various embodiments of the present disclosure recognize the need to use a reasonable DCI format size to achieve multi-cell scheduling, which may be the same or slightly larger than a traditional DCI format size, while at the same time, reasonably maintaining scheduling flexibility compared to a scenario with multiple separate DCI formats for each cell. In addition, various embodiments of the present disclosure recognize that when designing a method for multi-cell scheduling, the number of co-scheduled cells and the relative similarity of channel / radio conditions between the co-scheduled cells need to be considered.

[0070] Therefore, various embodiments of the present disclosure provide methods and apparatus for multi-cell scheduling with reduced signaling overhead. Various embodiments of the present disclosure describe methods for configuration or indication of a set of cells that are jointly scheduled (referred to as co-scheduled cells). Various embodiments of the present disclosure also explain various cell-common scheduling parameters having common values ​​applicable to all co-scheduled cells, and various cell-specific scheduling parameters having individual values ​​provided separately and applied to each co-scheduled cell.

[0071] Several methods for enhanced multi-cell scheduling are disclosed, which provide values ​​of scheduling parameters for multiple PDSCHs or multiple PUSCHs on multiple co-scheduled cells. One method considers concatenated DCI formats, where a small number of DCI formats are added to generate a DCI format for multi-cell scheduling. One method relies on multi-cell mapping, where some DCI fields in a DCI format can be interpreted as multiple values ​​for multiple co-scheduled cells based on a one-to-many configured mapping / table or a configured offset parameter.

[0072] One motivation for multi-cell scheduling using a single DCI format is for enhanced cross-carrier scheduling operation for 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 extended reality (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 operation with reduced capability (RedCap) UEs, etc.

[0073] Various embodiments of the present disclosure provide mechanisms for supporting multi-cell scheduling with reduced signaling overhead and are summarized below and further fully described below. Combinations of embodiments are also applicable, but for the sake of brevity, they are not described in detail.

[0074] In one embodiment, a set of one or more co-scheduled cell sets may be provided to the UE by a higher layer. The term co-scheduled cell set is used to refer to a set of serving cells, where the UE is able to schedule PDSCH reception or PUSCH transmission on two or more or all cells from the co-scheduled cell set by a single DCI format or by using complementary methods (such as those described herein). In one implementation, the DCI format for multi-cell scheduling schedules PDSCH or PUSCH on all serving cells from the co-scheduled cell set. It is also possible that PDSCH reception or PUSCH transmission on any cell from the co-scheduled cell set is scheduled by a DCI format that does not schedule any other PDSCH reception or PUSCH transmission on any other cell from the co-scheduled cell set, such as, for example, by a DCI format that does not have multi-cell scheduling capability or when there is no business associated with other cells at a given time. In addition, a subset of the co-scheduled cell set can 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 can change across different PDCCH monitoring opportunities, for example, as indicated by the corresponding DCI format or MAC CE.

[0075] In one embodiment, a first set of cell-common scheduling information parameters and a second set of cell-specific scheduling information parameters may be provided to a UE configured for multi-cell scheduling, wherein the values ​​of the first set of cell-common scheduling information parameters apply to all co-scheduled cells, and the values ​​of the second set of cell-specific scheduling information parameters apply to each corresponding co-scheduled cell. The UE may determine the cell-common and cell-specific scheduling information parameters based on the specification of system operation, or based on a higher-layer configuration. In one implementation, when the higher-layer configuration does not provide corresponding information for one or more scheduling parameters, the specification of system operation may provide a default structure for the cell-common and cell-specific scheduling parameters. For some cell-specific scheduling information parameters, a differential value compared to a reference value may be provided to the UE, wherein the reference value may correspond to, for example, the first scheduling cell from a group of scheduling cells.

[0076] 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, which is used to schedule PDSCH reception or PUSCH transmission on one or more corresponding cells from the co-scheduled cell set. When the DCI format provides partial information, the UE can determine the remaining information from the RRC signaling, or determine the remaining information by using other complementary methods.

[0077] In one embodiment, the DCI format for multi-cell scheduling can provide a separate field value for each of a plurality of co-scheduled cells. The first value corresponds to the first cell, the second value corresponds to the second cell, and so on. Therefore, the DCI format fields for multiple cells are cascaded, so that such a DCI format is referred to as a cascaded DCI format for multi-cell scheduling. This method may be beneficial, for example, for co-scheduled cells with different channel characteristics or configurations (such as for inter-band CA operation) or for co-scheduling PDSCH reception and PUSCH transmission.

[0078] In one embodiment, multi-cell mapping may be used to provide information to a UE for multi-cell scheduling of multiple PDSCH / PDCCHs on multiple corresponding cells, where a field in a DCI format may be interpreted as providing multiple values ​​of corresponding scheduling parameters for multiple co-scheduled cells. This interpretation may be based on a configured one-to-many mapping / table, or based on multiple configured offset values ​​for each cell applied to a reference value indicated by the DCI format. This approach may be beneficial, for example, for co-scheduled cells with several similar physical channel characteristics or configurations (such as for intra-band CA operation).

[0079] In one embodiment, for a UE configured with a set of co-scheduled cells, a set of "states" (or "code points") corresponding to a combination of cell sets from the group of co-scheduled cells may be provided to the UE. Thus, the multi-cell scheduling DCI format may indicate UE operation regarding scheduling parameters or DCI fields through an indication of a state. The UE may receive a configuration of such a state to be applied jointly to multiple scheduling parameters or DCI fields, or a different set of states may be provided to the UE separately for each scheduling parameter or DCI field. Furthermore, in addition to the cell combination, the state may also relate to parameters associated with the scheduling parameters or DCI fields.

[0080] In one embodiment, in a first implementation, for the rate matching mode applicable to multiple co-scheduled PDSCHs, the field of the connection individual rate matching indicator field in the multi-cell scheduling DCI format needs to be between 4 and 8 bits, depending on whether the serving cell from the set of co-scheduled cells is configured with one or two rate matching mode groups, for example, one or two bits for the first co-scheduled cell, and one or two bits for the second co-scheduled cell, and so on.

[0081] In one embodiment, in the second implementation, in order to trigger an aperiodic zero power CSI-RS resource set, a cell combination "state" may be configured to trigger an aperiodic zero power CSI-RS resource set that is considered unavailable for PDSCH reception of multiple co-scheduled PDSCHs. In this article, a state can correspond to only a cell combination, or can correspond to a combination of {aperiodic ZPCSI-RS resource set ID, serving cell ID} pairs.

[0082] Throughout this disclosure, the term "configuration" or "higher layer configuration" and variations thereof (such as "configured", etc.) are used to refer to one or more of: system information signaling, such as through 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.

[0083] Throughout this disclosure, the term signal quality is used to refer to, 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.

[0084] Antenna ports are defined so 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.

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

[0086] 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 the two symbols are within resources that the UE can assume uses the same precoding.

[0087] 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 the two symbols are located in SS / PBCH blocks sent in the same time slot and have the same block index.

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

[0089] 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 spatial Rx parameters when applicable. The UE shall not assume quasi-co-location of any other SS / PBCH block transmissions.

[0090] In the absence of CSI-RS configuration, and 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 QCLs with QCL Type A, Type D (when applicable), and average gain. The UE may also assume that no DM-RS conflicts with SS / PBCH blocks.

[0091] 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 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-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-type 1 for the first DL RS and qcl-type 2 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 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:

[0092] - 'QCL-Type-A': {Doppler shift, Doppler spread, average delay, delay spread}

[0093] - 'QCL-Type-B': {Doppler shift, Doppler spread}

[0094] - 'QCL-Type-C': {Doppler shift, average delay}

[0095] - 'QCL-Type D': {Spatial Rx parameters}

[0096] 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 slot n, the indicated mapping between TCI states and code points of the DCI field 'Transmission Configuration Indication' shall be applied after the MAC-CE application time, e.g. from slot n. The first time slot begins after It is used for subcarrier spacing (SCS) configuration The number of time slots per subframe.

[0097] Independent 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 reception of the corresponding PDSCH is less than the threshold timeDurationForQCL and at least one configured TCI state of the serving cell for scheduling the PDSCH contains a qcl type set to 'type d',

[0098] -The UE may assume that the DM-RS ports of the PDSCH of the serving cell are quasi-co-located with the RS relative to the QCL parameters used by the PDCCH quasi-co-location indication associated with the monitored search space with the lowest ControlResourceSetID in the latest slot where one or more CORESETs within the active BWP of the serving cell are monitored by the UE. In this case, if the qcl type is set to "Type D" of the PDSCH DM-RS is different from the "Type D" of the PDCCH DM-RS they overlap in at least one symbol, 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 CORESET are in different component carriers).

[0099] - 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,

[0100] - The UE may assume that the DM-RS ports of the PDSCH associated with the value of coresetPoolIndex of the serving cell are quasi-co-located with the RS with respect to the QCL parameters of the PDCCH quasi-co-location indication for the CORESET associated with the monitored search space with the lowest controlResourceSetId among the CORESETs configured with the same value of coresetPoolIndex as the PDCCH scheduling the PDSCH, and in the latest slot the UE monitors one or more CORESETs associated with the same coresetPoolIndex value as the PDCCH scheduling the PDSCH within the active BWP of the serving cell. In this case, if the "QCL-Type D" of the PDSCH DM-RS is different from the "QCL-Type D" of the PDCCH DM-RS 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).

[0101] - 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 port of the PDSCH or PDSCH transmission opportunity of the serving cell is 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 'tdmschemeA' or is 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, according to clause 5.1.2.1, the mapping of TCI states to PDSCH transmission opportunities is determined 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 timeslot with the first PDSCH transmission opportunity. In this case, if the 'QCL type' in the two TCI states corresponding to the lowest code point in the TCI code points containing two different TCI states is different from the 'QCL type' of the PDCCH DM-RS they overlap in at least one symbol, then the UE is expected to receive the PDCCH associated with the CORESET with priority. This also applies to the intra-band CA case (when PDSCH and CORESET are in different component carriers)

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

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

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

[0105] 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 TCI field is not present in the DL DCI, the UE derives its QCL assumption for scheduling PDSCH from the activated TCI state with the lowest ID applicable to PDSCH in the active BWP of the scheduling cell.

[0106] For PUSCH scheduled by DCI format 0_0 on a cell, and if the higher layer parameter enableDefaultBeamPL-ForPUSCH0-0 is set to 'enabled', the UE is not configured with PUCCH resources on the active UL BWP, and the UE is in RRC connected mode, if applicable, the UE shall transmit PUSCH according to the spatial relationship with reference to the RS configured with a QCL type set to 'Type D' corresponding to the QCL assumption of the CORESET with the lowest ID on the active DL BWP of the cell.

[0107] For PUSCH scheduled by DCI format 0_0 on the cell and if the higher layer parameter enableDefaultBeamPL-ForPUSCH0 is set to 'enabled', the UE is configured with PUCCH resources on the active UL BWP, where all PUCCH resources are not configured with any spatial relationship and the UE is in RRC connected mode, if applicable, the UE shall transmit PUSCH according to the spatial relationship with reference to the RS configured with a QCL type set to 'Type D', where in the case where CORESET is configured on the cell, the 'Type D' corresponds to the QCL assumption of the CORESET with the lowest ID on the active DL BWP of the cell.

[0108] In carrier aggregation (CA), two or more component carriers (CCs) are aggregated. The UE can simultaneously receive or transmit on one or more CCs depending on its capabilities:

[0109] - 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;

[0110] - 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;

[0111] - 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).

[0112] CA is supported for both contiguous CCs and non-contiguous CCs. When CA is deployed, frame timing and SFN are aligned between cells that can 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.

[0113] When CA is configured, the UE has only one RRC connection with the network. During RRC connection establishment / reestablishment / handover, one serving cell provides NAS mobility information, and during RRC connection establishment / handover, one serving cell provides security input. This cell is called the Primary Cell (PCell). Depending on the UE capabilities, Secondary Cells (SCells) can be configured to form a group of serving cells together with the PCell. Therefore, the set of serving cells configured for the UE includes one PCell and one or more SCells.

[0114] 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 for the SCell, i.e., the UE does not need to obtain broadcast system information directly from the SCell when in connected mode.

[0115] In order to achieve reasonable 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 shall 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 SCells mapped to the PUCCH SCell are deactivated before the PUCCH SCell is changed or removed.

[0116] When reconfiguring the group of serving cells:

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

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

[0119] On handover or connection recovery from RRC_INACTIVE:

[0120] -SCell is activated or deactivated.

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

[0122] To enable 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.

[0123] 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.

[0124] 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:

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

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

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

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

[0129] 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 NRUEs on the shared carrier. In the case of DSS operation, PDCCH enhancements for cross-carrier scheduling can be considered, including that the PDCCH of an SCell (called a special / scheduled SCell (sSCell)) can schedule PDSCH or PUSCH on a P(S) cell.

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

[0131] - A downlink assignment containing at least the modulation and coding format, resource allocation and hybrid ARQ information related to the DL-SCH;

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

[0133] In addition to scheduling, PDCCH can be used

[0134] - Activation and deactivation of configured PUSCH transmission with configuration grant;

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

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

[0137] - Notify one or more UEs of PRBs and OFDM symbols, where the UE may assume that no transmission is intended for the UE;

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

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

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

[0141] -Initiate a random access procedure;

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

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

[0144] The UE monitors a set of PDCCH candidates in configured monitoring occasions in one or more configured control resource sets (CORESETs) according to the corresponding search space configuration.

[0145] A CORESET includes a set of PRBs with a duration of 1 to 3 OFDM symbols. Resource Element Groups (REGs) and Control Channel Element (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.

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

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

[0148] 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.

[0149] The gNB may preempt an ongoing PDSCH transmission of one UE with a latency critical transmission of 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.

[0150] 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.

[0151] If the dynamically allocated downlink reception overlaps in time, the dynamically allocated downlink reception overrides the configured downlink assignment in the same serving cell. Otherwise, downlink reception according to the configured downlink assignment is assumed (if activated).

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

[0153] - the network decides which of these configured downlink allocations are active at the same time (including all of them); and

[0154] - 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 can deactivate a single configured downlink allocation or jointly deactivate multiple configured downlink allocations.

[0155] PUSCH can be scheduled using DCI on PDCCH, or a semi-statically configured grant can be provided via RRC, where two types of operation are supported:

[0156] - the first PUSCH is triggered by a DCI, wherein subsequent PUSCH transmission follows the RRC configuration and scheduling received on the DCI, or

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

[0158] 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 configured, the same C-RNTI applies to all serving cells.

[0159] The gNB may cancel a PUSCH transmission, or a repetition of a PUSCH transmission, or an SRS transmission of a UE 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 the UE receives a cancelled transmission indication, the UE shall cancel the PUSCH transmission or SRS transmission overlapping the resources indicated by the cancellation from the earliest symbol overlapping the resources.

[0160] In addition, using the configured grants, the gNB can allocate uplink resources to the UE for initial HARQ transmissions and HARQ retransmissions. Two types of configured uplink grants are defined:

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

[0162] -For 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.

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

[0164] If the UE is configured with enhanced intra-UE overlapping resource priority, 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 can be 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 can be multiplexed in the MAC PDU associated with the overlapping resources. In case a MAC PDU associated with the de-prioritized 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 by the same configured uplink grant when no explicit retransmission permission is provided by the gNB.

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

[0166] 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 the same time (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, each configured grant is activated individually using a DCI command, and deactivation of a type 2 configured grant is done using a DCI command, which may deactivate a single configured grant or jointly deactivate multiple configured grants.

[0167] When configuring SUL, 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.

[0168] 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, with each repetition being in one slot. For both dynamic grants and configured grant type 2, the number of repetitions can also be indicated dynamically in L1 signaling. The dynamically indicated number of repetitions shall override the RRC configured number of repetitions, if both are present.

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

[0170] There are two different modes of operation for multi-TRP: single DCI and multi-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 multi-DCI mode, the UE is scheduled by independent DCI from each TRP.

[0171] 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 enhanced dynamic codebook and / or one-time triggering of 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.

[0172] 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 may also perform retransmissions on a configured grant. The UE may be configured to send codeblock group based transmissions, where retransmissions may be scheduled as a subset of all codeblocks carrying a transport block.

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

[0174] 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.

[0175] In the case of CA, the multi-carrier nature of the physical layer is only exposed to the MAC layer where 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, each assignment / grant per serving cell generates one transport block. Each transport block and its potential HARQ retransmissions are mapped to a single serving cell.

[0176] 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).

[0177] Throughout this disclosure, embodiments are described in terms of multiple PDSCHs or multiple PUSCHs jointly scheduled on multiple serving cells, for example, from a subset / set of cells in one or more sets of co-scheduled cells.

[0178] The embodiments are general and can be applied to various other scenarios, such as when a UE is jointly scheduled to receive / transmit multiple PDSCH / PUSCH:

[0179] § From / to multiple transmission-reception points (TRPs) other communicating entities, such as multiple distributed units (DUs) or multiple remote radio heads (RRHs), e.g. in distributed MIMO operation, where the TRPs / DUs / RRHs may be associated with one or more cells; or

[0180] § In multiple time units, such as multiple time slots or multiple transmission time intervals (TTIs); or

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

[0182] § for multiple transport blocks (TBs), or for multiple codewords (CWs) corresponding to a single TB or multiple TBs; or

[0183] §For multiple semi-persistently scheduled PDSCHs (SPSPDSCH) or for multiple configured grant PUSCHs (CG PUSCH) co-activated on one or more TRPs / cells.

[0184] Therefore, any reference to "co-scheduled cells" can be replaced by "co-scheduled TRP / DU / RRH" or "co-scheduled timeslot / TTI" or "co-scheduled PDSCH / PUSCH" or "co-scheduled TB / CW" or "co-scheduled SPS-PDSCH / CG-PUSCH", etc. The same is true for other related terms, such as "multi-cell scheduling", etc.

[0185] Various embodiments contemplate the reception of multiple PDSCHs or the transmission of multiple PUSCHs on corresponding cells, including carriers of the same cell, such as on an UL carrier (also referred to as a normal UL (NUL) carrier) or a supplemental UL (SUL) carrier. The embodiments are also applicable to situations where scheduling is a mix of PDSCHs and PUSCHs. For example, a UE can receive a first PDSCH on a corresponding first cell and can send a second PUSCH on a corresponding second cell, where the first PDSCH and the second PUSCH are jointly scheduled.

[0186] In one embodiment, a set of one or more co-scheduled cell sets may be provided to the UE by a higher layer. The term co-scheduled cell set is used to refer to a set of serving cells, where the UE is able to schedule PDSCH reception or PUSCH transmission on two or more or all cells from the co-scheduled cell set by a single DCI format or by using complementary methods (such as those described herein). In one implementation, the DCI format for multi-cell scheduling schedules PDSCH or PUSCH on all serving cells from the co-scheduled cell set. It is also possible that PDSCH reception or PUSCH transmission on any cell from the co-scheduled cell set is scheduled by a DCI format that does not schedule any other PDSCH reception or PUSCH transmission on any other cell from the co-scheduled cell set, such as, for example, by a DCI format that does not have multi-cell scheduling capabilities or when there is no business associated with other cells at a given time. In addition, a subset of the co-scheduled cell set can 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 can change across different PDCCH monitoring opportunities, for example, as indicated by the corresponding DCI format or MAC CE.

[0187] In this document, operations with a cell or a set of cells refer to DL / UL transmissions on the cell, such as PDSCH reception or PUSCH transmission across cells. Operations may also include other UE processes or behaviors corresponding to DL / UL transmissions, such as reporting HARQ-ACK information, beam / CSI measurements or reports, transmission or reception or processing of UL / DL reference signals, etc.

[0188] In one example, the UE can be configured with multiple sets of co-scheduled cells through high-level signaling (such as through UE-specific RRC configuration). For example, the UE can 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 can be scheduled from the same scheduling cell or from different scheduling cells.

[0189] In one example, the co-scheduled cell set may include a 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.

[0190] In one example, according to the specification for system operation, the set of co-scheduled cells is defined as the set of all scheduling cells from the same scheduling cell, and no additional higher layer configuration is required for the set of co-scheduled cells. Therefore, the DCI format or other complementary methods for multi-cell scheduling can jointly schedule any number of scheduled cells with the same scheduling cell.

[0191] 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 DCI format may be a DCI format with a CRC scrambled with any RNTI, or a DCI format limited to a CRC scrambled with an RNTI (such as C-RNTI, CS-RNTI, or MCS-C-RNTI) provided by UE-specific RRC signaling. Such PDCCH monitoring from two scheduling cells can be simultaneous, for example in the same time slot, or can be non-overlapping, such as in different time slots (per high-level configuration, or indication in each PDCCH or via MAC CE). The UE may or may not expect both the first scheduling cell and the second scheduling cell to schedule transmission or reception on the same cell. The UE is also able to monitor the PDCCH to detect a DCI format that provides scheduling (single-cell scheduling DCI format) only on one cell from a set of co-scheduled cells. In addition, for single-cell scheduling, the UE may be configured to monitor the PDCCH for the first scheduling cell (only) on the first scheduling cell, and monitor the PDCCH for the second scheduling cell (only) on the second scheduling cell. In such a case, the scheduling by the two scheduling cells may only be applicable to multi-cell scheduling, but not to single-cell scheduling.

[0192] For example, based on the individual configuration of the scheduling cells of each co-scheduled cell set, different co-scheduled cell sets may have the same number of cells, or may have different numbers of cells.

[0193] The UE may report to the GNB one or more of the following that the UE may support as a capability (-IE): the maximum number of sets of co-scheduled cells, or the maximum number of cells within a set of co-scheduled cells, or the maximum total number of co-scheduled cells across different sets, or the maximum number of co-scheduled cells per PDCCH monitoring opportunity, as one or more capabilities, and the UE may support these cells as (multiple) capabilities. In one example, the UE capabilities for one or more of the following may depend on the operating band or frequency range: the number of sets of co-scheduled cells, or the number of cells within each set of co-scheduled cells, or the total number of co-scheduled cells, or the number of co-scheduled cells per PDCCH monitoring opportunity.

[0194] The UE can also be configured with multiple cells that do not belong to any group (or groups) of co-scheduled cells. For example, the UE can be configured with cell #8 that does not belong to the first set or the second set in the previous example.

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

[0196] § have the same parameter set (SCS configuration and CP); or

[0197] § have the same set of parameters for the respective active DL / UL BWPs; or

[0198] § have the same duplex configuration, for example, all cells have an FDD configuration, or all cells have a TDD configuration; or

[0199] § In the same frequency band (intra-band CA) or in the same frequency range (such as FR1 only or FR2 only).

[0200] The serving cell can belong to only a single set of co-scheduled cells, such that the set of co-scheduled cells does not include any common cells, or can belong to multiple sets of co-scheduled cells to achieve greater scheduling flexibility for the serving gNB. For example, when the cells in the first set of co-scheduled cells and the second set of co-scheduled cells have common characteristics (such as a common parameter set, duplex configuration, operating band / range, etc.), the serving cell can belong to the first set of co-scheduled cells and the second set of co-scheduled cells. In another example, when the serving cell has a first common characteristic with a cell in the first set of co-scheduled cells and a second common characteristic with a cell in the second set of co-scheduled cells, the serving cell may belong to the first set of co-scheduled cells and the second set of co-scheduled cells, wherein the first common characteristic may be different from the second common characteristic.

[0201] In the 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 the 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}.

[0202] In a second method, multi-cell scheduling for a subset of a co-scheduled cell set can be provided to the UE. For example, the DCI format can schedule PDSCH reception or PUSCH transmission only on two cells from the first cell set (such as {cell #0, cell #4}). For example, the UE can be configured with a set-level CIF corresponding to a co-scheduled cell set. For example, a first CIF value corresponding to a first co-scheduled cell set and a second CIF value corresponding to a second co-scheduled cell set can be provided to the UE. Therefore, the UE can determine whether the DCI format for multi-cell scheduling corresponds to the first set or the second set of co-scheduled cells based on whether the DCI format includes the first CIF value or the second CIF value. In one example, the setting-level CIF value is separated from the cell-level CIF value provided for single-cell scheduling of a single (or multiple) PDSCH or PUSCH on a single scheduled cell.

[0203] 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: an indication for activating or deactivating / releasing a cell subset; an indication of the number of co-scheduled cell sets; or an indication of multiple co-scheduled cell subsets from a corresponding number of co-scheduled cell sets.

[0204] For example, a MAC CE activates a first subset of a set of co-scheduled cells, and a subsequent DCI format for multi-cell scheduling is applied to the first subset of cells activated by the MAC CE. The UE is able to receive another MAC CE command to deactivate the first subset of co-scheduled cells or to activate a second subset of co-scheduled cells, where the second subset can be a subset of the same co-scheduled cell set 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 is able to 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 provide an indication of the subset of co-scheduled cells for multi-cell scheduling through the DCI format or by using a complementary method (such as those described herein).

[0205] In a second option for the second method, a subset of a set of co-scheduled cells can be provided by a DCI format in a PDCCH / PDSCH. A subset of cells can change between PDCCH monitoring occasions (MO) for PDSCH / PUSCH scheduling, as indicated by a corresponding DCI format. For example, a first DCI format in a first PDCCH M0 indicates scheduling on a first subset of cells, and a second DCI format in a second PDCCH M0 indicates scheduling on a second subset of cells. In one example, a DCI format for multi-cell scheduling provides an index of a co-scheduled cell or an index of a configuration of a subset of co-scheduled cells or a CIF value corresponding to a co-scheduled cell. For example, RRC signaling can indicate a first / second / third index from a set of co-scheduled cells and a corresponding first / second / third subset (or a first / second / third set of co-scheduled cells), a fourth index can correspond to all cells from a set of co-scheduled cells (or all sets of co-scheduled cells), and a 2-bit first field in a DCI format can provide an index value to indicate a scheduled cell. A 1-bit flag field may also be included to indicate whether the DCI format is for single-cell scheduling or for multi-cell scheduling so that the UE interprets the other fields of the DCI format accordingly. Then, for single-cell scheduling, in the case of cross-carrier scheduling, the first field may be interpreted as a CIF field. In another example, the DCI format for multi-cell scheduling provides multiple co-scheduled cells, and the index of the co-scheduled cells is provided by an additional method, such as by an additional DCI format or by higher layer signaling as described herein.

[0206] In a third option for the second method, the UE can determine the index of the cell for co-scheduling. For example, the UE can determine the index of the cell for co-scheduling based on PDCCH monitoring parameters, such as:

[0207] §CORESET index; or

[0208] § a search space set index or a carrier indicator parameter n_CI corresponding to the search space set index; or

[0209] § The set of CCEs in the search space set or the first / last CCE in the search space set;

[0210] The UE has received a DCI format for multi-cell scheduling.

[0211] According to a third option, the UE can be configured for 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 co-scheduled cells. In an example, a first value of a parameter n_CI in the search space set can indicate a first subset of co-scheduled cells, and a second value of a parameter n_CI in the search space set can indicate a second subset of co-scheduled cells. According to this example, the parameter n_CI can correspond to a single cell (legacy behavior) or can correspond to a set of cells, such as a subset / set of co-scheduled cells.

[0212] FIG. 4 illustrates a method 400 for multi-cell scheduling of a UE configured with multiple sets of co-scheduled cells according to an embodiment of the present disclosure. The embodiment of the method 400 for multi-cell scheduling of a UE configured with multiple sets of co-scheduled cells shown in FIG. 4 is for illustration only. FIG. 4 does not limit the scope of the present disclosure to any particular implementation of the method 400 for multi-cell scheduling of a UE configured with multiple sets of co-scheduled cells.

[0213] As shown in Figure 4, method 400 begins at step 410, where a UE (e.g., UE 116) is configured with multiple sets of co-scheduled cells. At step 420, the UE receives a DCI format that includes a field with a value that provides an indication of a set from multiple configured sets of co-scheduled cells. Alternatively or additionally, it is also possible to provide an indication via a higher layer configuration or a MAC CE command. At step 430, the UE receives the value of a scheduling parameter for multiple PDSCH / PUSCH on a cell in the indicated co-scheduled cell via the DCI format. At step 440, the UE receives multiple PDSCHs or sends multiple PUSCHs on the indicated co-scheduled cell based on the value of the received scheduling parameter.

[0214] It is worth noting that when a cell is configured to be in a co-scheduled cell set, the UE can still receive a DCI format that schedules PDSCH reception or PUSCH transmission only on the cell (single-cell scheduling DCI format). The UE can distinguish between a single-cell scheduling DCI format and a multi-cell scheduling DCI format via various methods (such as DCI format size or RNTI used to scramble the CRC of the DCI format for multi-cell scheduling) or by explicit indication of the corresponding field in the DCI format.

[0215] The set of DL / UL transmissions on the corresponding set / subset of cells jointly scheduled by a single DCI format, or by using complementary methods such as those described in the embodiments of this document, may refer to multiple PDSCHs or multiple PUSCHs that may or may not overlap in time. For example, the UE may be instructed to receive multiple PDSCHs or transmit multiple PUSCHs on multiple co-scheduled cells, where all receptions / transmissions are in the same time slot, or at least one reception / transmission is in a different time slot from the rest of the receptions / transmissions.

[0216] 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 be able to report a capability of a maximum number of {2, 4, 8, 16} co-scheduled cells for DL ​​and a capability of a maximum number of {2, 4} co-scheduled cells for UL.

[0217] In one embodiment, a first set of cell-common scheduling information parameters and a second set of cell-specific scheduling information parameters may be provided to a UE configured for multi-cell scheduling, wherein the values ​​of the first set of cell-common scheduling information parameters apply to all co-scheduled cells, and the values ​​of the second set of cell-specific scheduling information parameters apply to each corresponding co-scheduled cell. The UE may determine the cell-common and cell-specific scheduling information parameters based on the specification of system operation, or based on a higher-layer configuration. In one implementation, when the higher-layer configuration does not provide corresponding information for one or more scheduling parameters, the specification of system operation may provide a default structure for the cell-common and cell-specific scheduling parameters. For some cell-specific scheduling information parameters, a differential value compared to a reference value may be provided to the UE, wherein the reference value may correspond to, for example, a first scheduling cell from a group of scheduling cells.

[0218] For example, the classification of the cell-common scheduling information parameters and the cell-specific scheduling information parameters may be based on whether the channel / MIMO characteristics are relatively similar between the co-scheduled cells.

[0219] In one implementation, the UE is configured with multiple sets of co-scheduled cells. The UE is configured with a first set of cell-set common scheduling parameters and a second set of cell-specific scheduling parameters. The UE receives indications of multiple co-scheduled cells from multiple configured sets of co-scheduled cells. For each parameter from the first set of cell-set common scheduling parameters, the UE receives a single value applicable to multiple PDSCH / PUSCH on the indicated multiple co-scheduled cells. The UE receives multiple values ​​applicable to multiple PDSCH / PUSCH on the indicated multiple co-scheduled cells for each parameter from the second set of cell-specific scheduling parameters. The UE receives multiple PDSCHs or sends multiple PUSCHs on the indicated multiple co-scheduled cells based on the received values ​​of the cell-common scheduling parameters and the cell-specific scheduling parameters.

[0220] In one example, for a cell-specific scheduling parameter, a first value and one or more differential values ​​relative to the first value may be provided to the UE. Such operation may be beneficial to reduce signaling overhead. For example, a first value may be provided for a first cell in a co-scheduled cell. For example, the first value may be provided to the UE via high-layer signaling or in a DCI format for multi-cell scheduling, and the differential value may be provided to the UE in the same DCI format or by using various other methods such as those described herein.

[0221] FIG5 shows a method 500 for multi-cell scheduling based on reference values ​​and differential values ​​of cell-specific scheduling parameters according to an embodiment of the present disclosure. The embodiment of the method 500 for multi-cell scheduling based on reference values ​​and differential values ​​of cell-specific scheduling parameters shown in FIG5 is for illustration only. FIG5 does not limit the scope of the present disclosure to any specific implementation of the method 500 for multi-cell scheduling based on reference values ​​and differential values ​​of cell-specific scheduling parameters.

[0222] As shown in FIG. 5 , method 500 begins at step 510, where a UE (such as UE 116) is configured with multiple sets of co-scheduled cells. At step 520, the UE receives an indication for co-scheduling a first cell and a second cell from a plurality of configured sets of co-scheduled cells. At step 530, the UE receives a multi-cell scheduling DCI format that provides a first value of a cell-specific scheduling parameter corresponding to a first PDSCH / PUSCH on a first cell. At step 540, the UE receives a differential value of a cell-specific scheduling parameter corresponding to a second PDSCH / PUSCH on a second cell from a DCI format or through high-layer signaling. At step 550, the UE determines a second value of a cell-specific scheduling parameter corresponding to a second PDSCH / PUSCH on a second cell based on the first value and the differential value. At step 560, the UE receives a first PDSCH and a second PDSCH or sends a first PUSCH and a second PUSCH on a first co-scheduled cell and a second co-scheduled cell, respectively, based on the first value and the second value.

[0223] The following considers various scheduling information parameters corresponding to the DCI format described in TS 38.212.

[0224] In a first example, the link direction parameter (uplink or downlink) may be a cell-common scheduling parameter. For example, a UE may be scheduled to receive multiple PDSCHs on a set of co-scheduled cells, or a UE may be scheduled to send multiple PUSCHs on the set of co-scheduled cells. Therefore, for all co-scheduled cells, a cell-common value may be provided to the UE via a flag in the DCI format, such as 0 for UL and 1 for DL.

[0225] In one example, multi-cell scheduling may include a mix of PDSCH reception and PUSCH transmission. The link direction may then be a cell-specific scheduling parameter provided separately for each co-scheduled cell. In one example, the co-scheduled cells may be grouped based on the link direction such that the UE receives a first PDSCH on a first set of co-scheduled cells and sends a second PUSCH on a second set of co-scheduled cells. In this case, an indication that the DCI format schedules both PDSCH reception and PUSCH transmission may be provided to the UE, for example, via a corresponding field in the DCI format or via a corresponding C-RNTI. The number of cells with scheduled PDSCH reception or scheduled PUSCH transmission may be predetermined / configured, or may be indicated by a corresponding field in the DCI format so that the UE may interpret other fields in the DCI format accordingly.

[0226] In one example, a carrier indicator field (CIF) is capable of indicating a subset of co-scheduled cells from a co-scheduled cell set, wherein the mapping between the value of the CIF and the subset of co-scheduled cells is configured by UE-specific RRC signaling. One value of the CIF may correspond to all cells from the co-scheduled cell set. For example, a first CIF value may correspond to a first co-scheduled cell set, and a second CIF value may correspond to a second co-scheduled cell set. The indication may be by an index to the subset of co-scheduled cells or by a bitmap mapped to the subset of co-scheduled cells. In another example, each co-scheduled cell indicates a separate CIF value, wherein the indication may be a cell index or a single-cell CIF index, or by a bitmap mapped to each co-scheduled cell. In one example, when the DCI format applies to all cells in the co-scheduled cell set, the DCI format does not include a CIF.

[0227] In one example, when the UE is configured with N sets (or subsets) of co-scheduled cells corresponding to the scheduling cell, the DCI format for multi-cell scheduling can include a DCI format having This example may apply when the configured N sets (or subsets) of co-scheduled cells include a set (or subset) with a single serving cell so that single-cell scheduling is also supported, or when the UE does not expect a DCI format for multi-cell scheduling to schedule PDSCH or PUSCH on a single serving / scheduling cell.

[0228] In another example, a DCI format for multi-cell scheduling may include a DCI format having CIF in bits:

[0229] - the UE is configured with M scheduled cells and N sets (or subsets) of co-scheduled cells, where each set (or subset) includes at least two cells from the M scheduled cells (i.e. no set / subset has a single scheduled cell), and

[0230] -DCI format for multi-cell scheduling can schedule PDSCH or PUSCH on a single or multiple serving / scheduling cells.

[0231] In one example, the bandwidth part (BWP) indicator field may not be present in the DCI format for multi-cell scheduling. For example, BWP switching may be performed by scheduling a DCI format that schedules PDSCH reception or PUSCH transmission on a single cell only, or by higher layer (re)configuration, or based on a timer, etc. Therefore, the UE receives the co-scheduled PDSCH on the corresponding active DL BWP of the corresponding co-scheduled cell, or transmits the co-scheduled PUSCH on the corresponding active UL BWP of the corresponding co-scheduled cell. In another example, the BWP indicator may be a cell-common scheduling parameter. For example, the UE is provided with a parameter by the RRC, which indicates whether the BWP ID field is not present in the multi-cell scheduling DCI (multi-cell scheduling DCI, MC-DCI) format and needs to use the active DL / UL BWP of the co-scheduled cell, or whether the BWP ID field is present in the MC-DCI as a cell-common field. For example, when the RRC parameter indicates "BWP ID present", the configuration of the MC-DCI format can include a BWP ID field of size 2 bits, and when the RRC parameter indicates "BWP ID not present", the BWP ID field is not included (size 0 bits). For example, the RRC parameter may have a default value, such as 'BWP ID not present', and when the RRC parameter is not provided, the UE expects the MC-DCI to not include the BWP ID field. In one example, such RRC parameters are provided independent of any particular set of co-scheduled cells and are applicable to all sets of co-scheduled cells. In another instance, the UE is provided with separate RRC parameters for each set of co-scheduled cells, and a first MC-DCI format for scheduling on a first set of co-scheduled cells having an RRC parameter indicating 'BWP ID not present' does not include the BWP ID field, while a second MC-DCI format for scheduling on a second set of co-scheduled cells having an RRC parameter indicating 'BWP ID present' includes the BWP ID field. For example, the MC-DCI format includes a BWP ID field with a reserved value for the first cell set / MC-DCI format and with a valid value for the second cell set / MC-DCI format.In another example, one of the two options is defined in the specification and the RRC parameters are not used.

[0232] In one example, the frequency-domain resource allocation (FDRA) field or the time domain resource allocation (TDRA) can be a cell-common scheduling parameter. This can be applicable, for example, to intra-band CA with co-scheduled cells having the same SCS configuration. In one example, the UE applies the FDRA or TDRA field based on the corresponding configuration of the corresponding co-scheduled cell. For example, when the cell-common TDRA field indicates index 3, the UE receives the first PDSCH (or sends the first PUSCH) according to the parameters provided in the 3rd row of the first TDRA table configured for the first co-scheduled cell, and receives the second PDSCH (or sends the second PUSCH) according to the parameters provided in the 3rd row of the second TDRA table configured for the second co-scheduled cell.

[0233] In one example, a high-level parameter may be configured for the UE, which indicates whether the UE applies FDRA or TDRA in a cell-common manner. In another example, the UE may implicitly determine whether FDRA or TDRA is cell-common based on whether the multi-cell scheduling DCI format indicates a single FDRA / TDRA field or multiple separate FDRA / TDRA fields. In yet another example, when a cell-specific FDRA or TDRA configuration or a joint FDRA or TDRA configuration (described below) is not provided to the UE, the UE determines whether FDRA or TDRA is cell-common, and the serving cell is included in the co-scheduled cell set.

[0234] In one example, the FDRA may be cell-common by specification for system operation, and in this case, the FDRA indicated in the multi-cell scheduling DCI format is the FDRA corresponding to the scheduled cell (when applicable), or the FDRA corresponding to the co-scheduled cell with the smallest index or the smallest CIF or with the smallest SCS configuration, or some other predetermined or configured co-scheduled cell. In one example, a per-cell FDRA may still be provided to allow single-cell scheduling.

[0235] In one example, a first FDRA / TDRA value for a first cell from a set / subset of co-scheduled cells and a differential FDRA / TDRA value for a second cell from a set / subset of co-scheduled cells may be provided to the UE. The differential FDRA / TDRA value is an offset value relative to the first FDRA / TDRA value. The UE may determine the second FDRA / TDRA of the second cell based on the first FDRA / TDRA value and the offset value. The number of bits for providing the first FDRA / TDRA value or the differential FDRA / TDRA value may be predetermined for the DCI format, or may be provided by high-layer signaling of the DCI format.

[0236] In one example, the UE expects the same resource allocation type (such as FDRA type-1 (contiguous RBs) or FRDA type-0 (RBG-based allocation) to apply to all co-scheduled cells. Similarly, the UE expects the TDRA PDSCH / PUSCH mapping type (such as type A or type B) to apply to all co-scheduled cells. In another example, the UE may be configured by higher layers with FDRA or TDRA type for each cell from a set of co-scheduled cells separately.

[0237] In one example, the UE may be provided with the same FDRA type configuration for both single-cell scheduling and multi-cell scheduling, including configuration of dynamic switching between FDRA Type-0 and Type-1. For example, when the UE is configured with dynamic switching between FDRA Type-0 and Type-1 (respectively, only FDRA Type-0 or only FDRA Type-1) for single-cell scheduling of all serving cells from a co-scheduled cell set, the UE may be configured with dynamic switching between FDRA Type-0 and Type-1 (respectively, only FDRA Type-0 or only FDRA Type-1) for multi-cell scheduling. For example, when the UE is provided with only FDRA Type-0 or only FDRA Type-1 for at least one cell from a co-scheduled cell set, the UE is not expected to be configured with dynamic switching between FDRA Type-0 and Type-1.

[0238] In one example, the UE determines the FDRA type for multi-cell scheduling based on the FDRA type configuration for single-cell scheduling. For example, when all serving cells from a co-scheduled cell set are configured with only FDRA type-0 (respectively, only type-1) for single-cell scheduling, the UE determines FDRA type-0 (respectively, type-1) for multi-cell scheduling of the co-scheduled cell set. For example, when all serving cells from a co-scheduled cell set are configured with dynamic switching between FDRA type-0 and type-1 for single-cell scheduling, the UE determines that dynamic switching between FDRA type-0 and type-1 is applicable to multi-cell scheduling of the co-scheduled cell set.

[0239] In one example, the specification for system operation may provide restrictions for FDRA type for multi-cell scheduling. For example, when operating with multi-cell scheduling of PDSCH / PUSCH, the UE expects that the UE cannot be configured with dynamic switching between FDRA type-0 and FDRA type-1. For example, this may also be conditioned on the UE not supporting such dynamic switching on at least one cell from the co-scheduled cells. It is worth noting that when operating with single-cell scheduling of PDSCH / PUSCH, the UE may still be configured for such dynamic switching.

[0240] In one example, the UE is provided with the same RBG size for all co-scheduled cells. In one example, the UE does not expect to configure different SCS configurations for the co-scheduled cell set. In another example, the UE does not expect to receive a multi-cell scheduling DCI format when the active BWP of the co-scheduled cell set has a different SCS configuration.

[0241] In one example, separate FDRA types for single-cell scheduling and multi-cell scheduling may be provided to the UE. For example, the UE may be configured with an FDRA type for multi-cell scheduling regardless of the corresponding FDRA type for single-cell scheduling on a serving cell of a co-scheduled cell set. For example, when at least one serving cell from a co-scheduled cell set is configured with FDRA type-1 (correspondingly, FDRA type-0), the UE may be provided with FDRA type-0 (correspondingly, FDRA type-1) for multi-cell scheduling. For example, when at least one serving cell from a co-scheduled cell set is configured with only FDRA type-0 or only FDRA type-1, the UE may be configured with dynamic switching between FDRA type-0 and type-1.

[0242] In one example, the UE considers the FDRA configuration to be incompatible with single-cell scheduling and multi-cell scheduling of at least one serving cell from a co-scheduled cell set when the UE is configured as follows:

[0243] - FDRA Type-0 for multi-cell scheduling when at least one serving cell from the co-scheduled cell set is configured with FDRA Type-1, or

[0244] - FDRA type 1 for multi-cell scheduling when at least one serving cell from the co-scheduled cell set is configured with FDRA type 0, or

[0245] - When at least one serving cell from the co-scheduled cell set is configured with only FDRA type 0 or only FDRA type 1, dynamically switching between FDRA type 0 and type 1.

[0246] In one example, the UE does not desire to be provided with incompatible FDRA configurations for single-cell scheduling and multi-cell scheduling for any serving cell from a set of co-scheduled cells.

[0247] In another example, when the UE is provided with incompatible FDRA configurations for single-cell scheduling and multi-cell scheduling for at least one serving cell from a co-scheduled cell set, the UE interprets the FDRA field in the multi-cell scheduling DCI format:

[0248] - in the first option, based on the FDRA configuration provided for single-cell scheduling (i.e. the UE discards the FDRA configuration for multi-cell scheduling of at least one serving cell), or

[0249] - In the second option, based on the FDRA configuration provided for multi-cell scheduling, and the assumption of predetermined / default values ​​for any parameters missing in the cell-specific FDRA configuration for single-cell scheduling (eg RBG size, as described below).

[0250] For example, if the UE is configured as:

[0251] - FDRA type 0 only or dynamic switching between FDRA type 0 and type 1 for multi-cell scheduling on a set of co-scheduled cells, and

[0252] - only FDRA type-1 is used for single-cell scheduling of at least one serving cell from the set of serving cells (hence, there is no dedicated / cell-specific configuration of RBG size for at least one serving cell),

[0253] In a first option, the UE determines the (nominal or actual) RBG size of at least one serving cell based on a default / predetermined configuration of the nominal RBG size parameter (such as Configuration 1 in [TS 38.214v17.1.0]). In a second option, the UE expects to be provided with a configuration for the nominal RBG size parameter (e.g., as an IE with a FDRA type configuration for multi-cell scheduling) that the UE can apply commonly to at least one serving cell without a cell-specific RBG size configuration.

[0254] In one example, when the UE is configured with dynamic switching between FDRA Type 0 and FDRA Type 1, the UE expects a single cell common indication of the multi-cell scheduling DCI format indicating the FDRA type, as FDRA Type 0 or FDRA Type 1, for co-scheduled PDSCH / PUSCH on a co-scheduled cell set.

[0255] In one example, when a UE is provided with active BWPs on a set of co-scheduled cells having different sizes (in terms of number of RBs), the UE determines the number of bits of the FDRA field in the multi-cell scheduling DCI format based on the size of the largest corresponding size in the set of co-scheduled cells. Thus, the UE determines the FDRA for each PDSCH / PUSCH from the co-scheduled PDSCH / PUSCH based on the number of least significant bits (LSBs) of the FDRA field from the multi-cell scheduling DCI format, where assuming the FRDA type is configured / determined for multi-cell scheduling, the number of bits is equal to the cell-specific bit width of the FDRA field.

[0256] For example, when When is the size of the active DL bandwidth portion of the serving cell c from the set S of co-scheduled cells, the FDRA field in the DCI format for multi-cell scheduling of multiple PDSCHs on the set S of co-scheduled cells includes:

[0257] o If resource allocation type 0 is configured / determined for multi-cell scheduling of the group of co-scheduled cells only, then Bit, where is the total number of RBGs in the active downlink bandwidth portion of serving cell c, as defined in [TS38.214],

[0258] o When no cell-specific information for single-cell scheduling is provided to the UE When configuring, the UE determines as described above ;

[0259] oUE based on the FDRA field in the multi-cell scheduling DCI format The LSB determines the FDRA of the PDSCH from the co-scheduled PDSCH on serving cell c.

[0260] - bit if only resource allocation type 1 is configured / determined for multi-cell scheduling of a set of co-scheduled cells,

[0261] oUE based on the FDRA field in the multi-cell scheduling DCI format LSB to determine the FDRA of the PDSCH from the co-scheduled PDSCH on serving cell c; or

[0262] - If dynamic switching is determined between FDRA Type-0 and Type-1, these bits are configured / determined for multi-cell scheduling of the co-scheduled cell set.

[0263] o When no single cell scheduling is provided to the UE When cell-specific configuration is used, the UE determines ;

[0264] o The most significant bit (MSB) is used to indicate resource allocation type 0 or resource allocation type 1 for the co-scheduled PDSCH on all serving cells from the co-scheduled cell set, where a bit value of 0 indicates resource allocation type 0 and a bit value of 1 indicates resource allocation type 1.

[0265] o For FDRA resource allocation type 0, the UE shall allocate resources based on the FDRA field in the multi-cell scheduling DCI format. The LSB determines the FDRA of the PDSCH from the co-scheduled PDSCH on serving cell c.

[0266] o For FDRA resource allocation type 1, the UE shall allocate resources based on the FDRA field in the multi-cell scheduling DCI format. The LSB determines the FDRA of the PDSCH from the co-scheduled PDSCH on serving cell c.

[0267] When frequency hopping (FH) for PUSCH reception is not configured or disabled for a co-scheduled cell set, as described subsequently, the FDRA field is the same as described above for the co-scheduled PDSCH, except that Replaced by , except that “DL” / ”downlink” and “PDSCH” are replaced by “UL” / ”uplink” and “PUSCH”, respectively.

[0268] In one example, the FH flag may be a cell common field. For example, the UE expects to be configured with FH for cells in a co-scheduled cell set. For example, when the UE is configured with FH for PUSCH transmissions from at least a first cell of a co-scheduled cell set, and is not configured with FH for PUSCH transmissions from at least a second cell of the co-scheduled cell set, FH operation can be disabled for the co-scheduled PUSCH on the co-scheduled cells of the group. Therefore, the UE does not expect to be provided with an FH flag in the DCI format for multi-cell scheduling of the co-scheduled cells of the group, or the UE does not perform FH for the co-scheduled PUSCH on the co-scheduled cells of the group, including the co-scheduled PUSCH on the first cell.

[0269] In another example, the UE can be configured with an FH flag in a DCI format for multi-cell scheduling when at least one cell from a co-scheduled cell set is provided with an FH configuration for PUSCH transmission. For example, the UE determines that FH is enabled for PUSCH transmission on a first serving cell from a co-scheduled cell set configured with FH operation, and ignores the FH flag for PUSCH transmission on a second serving cell from a co-scheduled cell set not configured with FH operation.

[0270] For example, it is expected that the UE is provided with the same configuration of FH parameters for cells in a co-scheduled cell set, such as the same configuration for multiple offset values ​​provided by the higher-level parameter frequencyHoppingOffsetLists. In one example, the UE is not expected to be configured with a co-scheduled cell set including a first cell with two offset values ​​provided by the higher-level parameter frequencyHoppingOffsetLists and a second cell with four offset values ​​provided by the higher-level parameter frequencyHoppingOffsetLists.

[0271] In another example, when the higher layer parameter frequencyHoppingOffsetLists provides different numbers of offset values ​​for a first cell and a second cell from a co-scheduled cell set (e.g., 2 offset values ​​for the first cell and 4 offset values ​​for the second cell), in one option, the UE determines the FH mode for the first cell and the second cell based on different numbers of bits from the FDRA field in the DCI format for multi-cell scheduling. For example, the DCI format may use 2 bits from the FDRA field for FH indication, wherein the MSB (or LSB) of the 2 bits is used for the FH indication of the first cell, and both of the 2 bits are used for the FH indication of the second cell.

[0272] In another option, the DCI format will include only 1 bit from the FDRA field for FH indication, and the UE determines the FH mode for both the first cell and the second cell based on this bit. Accordingly, in the case of multi-cell scheduling of PUSCH, the UE uses only two of the 4 configured offset values ​​for the second cell, such as only the first two offset values, and discards the other two offset values. Note that when scheduling PUSCH on the second cell by a single-cell scheduling DCI format, the UE can operate with any of the four configured offset values.

[0273] For example, when the UE is configured with FH for a co-scheduled cell set and / or the UE determines to operate with FH, as described above, and when When is the size of the active UL bandwidth portion of the serving cell c from the co-scheduled cell set S, the FDRA field in the DCI format for multi-cell scheduling of multiple PUSCHs on the co-scheduled cell set S includes:

[0274] If only resource allocation type 0 is configured / determined for multi-cell scheduling of a co-scheduled cell set, then Bits, of which is the total number of RBGs in the active uplink bandwidth portion for serving cell c, as defined in [TS38.214],

[0275] When no UE is provided with When single-cell scheduling is configured in a cell-specific manner, the UE determines ;

[0276] oUE based on the FDRA field in the multi-cell scheduling DCI format The LSB determines the FDRA of the PUSCH from the co-scheduled PUSCH on serving cell c.

[0277] - If only resource allocation type 1 is configured / determined for multi-cell scheduling of a co-scheduled cell set, then Bit,

[0278] oUE determines the MSB:

[0279] § = 1 bit when all cells in the set S of co-scheduled cells are configured with two offset values ​​by the higher layer parameter frequencyHoppingOffsetLists, or when at least one cell in the set S of co-scheduled cells is configured with two offset values ​​and the UE expects the same number of FH indication bits for the set of co-scheduled cells according to the specification of the system operation, as described above. When the UE is configured with four offset values ​​for cell c, the UE determines the FH pattern for the co-scheduled PUSCH on cell c according to the first two configured offset values;

[0280] § = 2 bits when four offset values ​​are configured for at least one cell in the set S of co-scheduled cells via the higher layer parameter frequencyHoppingOffsetLists. When the UE is configured with two offset values ​​for cell c, the UE determines the FH mode of the co-scheduled PUSCH on cell c from the MSB of the FDRA field (and ignores the MSB bit of cell c);

[0281] oUE based on the FDRA field in the multi-cell scheduling DCI format - LSB to determine the FDRA of the PUSCH from the co-scheduled PUSCH on serving cell c (within the hopping range); or

[0282] - Bits If dynamic switching is determined between FDRA Type-0 and Type-1, these bits are configured / determined for multi-cell scheduling of the co-scheduled cell set.

[0283] When no single cell scheduling is provided to the UE When the cell-specific configuration is used, the UE determines as previously discussed ;

[0284] The MSB bit is used to indicate resource allocation type 0 or resource allocation type 1 for the co-scheduled PUSCH on all serving cells from the co-scheduled cell set, where a bit value of 0 indicates resource allocation type 0 and a bit value of 1 indicates resource allocation type 1.

[0285] o For FDRA resource allocation type 0, the UE shall allocate resources based on the FDRA field in the multi-cell scheduling DCI format. The LSB determines the FDRA of the PUSCH from the co-scheduled PUSCH on serving cell c.

[0286] o For FDRA resource allocation type 1, the UE shall allocate resources based on the FDRA field in the multi-cell scheduling DCI format. LSB to determine the FH indication MSB, as described above, and the FDRA for the PUSCH from the co-scheduled PUSCH on serving cell c (within the hop range).

[0287] In one implementation, the UE may replace for , used to determine the FDRA field of the co-scheduled PDSCH / PUSCH, where, , in one option, may be the union of all co-scheduled cell sets corresponding to the same scheduled cell. In another option, It may be the union of all co-scheduled cell sets configured for the UE (corresponding to the same or different scheduling cells).

[0288] In one example, a UE is provided with a joint TDRA table across serving cells from a set of co-scheduled cells. Here, a joint TDRA table may refer to a TDRA table including multiple parameter sets (e.g., multiple columns or multiple column sets) corresponding to multiple co-scheduled cells. For example, each parameter set / column / column set provides a time domain parameter set (such as SLIV, mapping type, K0 or K2, number of repetitions, etc.) for the corresponding co-scheduled cell. For example, each row of the joint TDRA table indicates a first time domain parameter set for a first co-scheduled cell and a second time domain parameter set for a second co-scheduled cell. Therefore, when the UE detects a multi-cell scheduling DCI format for a set of co-scheduled cells, the TDRA field in the DCI format indicates an index of a row of the joint TDRA table, which in turn indicates multiple TDRA values ​​for multiple corresponding co-scheduled cells. This method is an example of a multi-cell mapping method considered herein.

[0289] In one example, a joint TDRA table may provide multiple values ​​for a cell-specific first TDRA parameter and a single value for a cell-common second parameter. For example, a joint TDRA table for multi-cell scheduling may include multiple SLIVs corresponding to multiple service cells from a co-scheduled cell set, and include a single TDRA mapping type or a single PDSCH / PUSCH time slot scheduling offset value K0 / K2 applied to all service cells from the co-scheduled cell set. For example, the UE expects the same TDRA mapping type for the service cells of the co-scheduled cell set. For example, the UE expects a single K0 or a single K2 for a co-scheduled PDSCH or PUSCH on a co-scheduled cell set, for example, when the co-scheduled PDSCH or PUSCH has the same SCS configuration.

[0290] In one example, a joint TDRA table for multi-cell scheduling may include multiple SLIVs and multiple K0 / K2 values ​​corresponding to multiple serving cells from a co-scheduled cell set, and include a single TDRA mapping type. This configuration may be beneficial, for example, when a UE is provided with different SCS configurations for different serving cells from a co-scheduled cell set.

[0291] In one example, a UE may be configured with a joint TDRA table for a set of co-scheduled cells, where:

[0292] - at least one entry / row for which multiple TDRA parameter sets are provided, such as multiple SLIV values, and

[0293] - Some entries / rows for which a set of TDRA parameters is provided, such as a SLIV, a K0 / K2 parameter, etc.

[0294] When the DCI format for multi-cell scheduling indicates an entry / row of a joint TDRA table including only one TDRA parameter set (such as one SLIV, K0 / K2, etc.), the UE applies the provided TDRA parameter set to all co-scheduled PDSCHs or PUSCHs on the co-scheduled cell set.

[0295] When the DCI format for multi-cell scheduling indicates an entry / row of a joint TDRA table including multiple TDRA parameter sets (such as multiple SLIVs), the UE applies each of the multiple TDRA parameter sets provided to the corresponding co-scheduled PDSCH or PUSCH on the co-scheduled cell set, for example, the first SLIV is used for the first co-scheduled PSDCH / PUSCH, the second SLIV is used for the second co-scheduled PDSCH / PUSCH, and so on.

[0296] In one example, the UE may be configured with the same joint TDRA table for both co-scheduled PDSCH and co-scheduled PUSCH on a co-scheduled cell set. For example, the joint TDRA table may include K0 and K2 values, and the UE applies the provided K0 or K2 value, respectively, depending on whether the multi-cell scheduling is for PDSCH reception or for PUSCH transmission.

[0297] In another example, different joint TDRA tables may be provided to the UE for co-scheduled PDSCH and co-scheduled PUSCH on the same co-scheduled cell set. For example, a first TDRA table for co-scheduled PDSCH on a co-scheduled cell set and a second joint TDRA table for co-scheduled PUSCH on the co-scheduled cell set may be provided to the UE.

[0298] In one example, a joint TDRA table for each configured co-scheduled cell set may be provided to the UE. For example, a first joint TDRA table for a first co-scheduled cell set and a second joint TDRA table for a second co-scheduled cell set may be provided to the UE. In one example, the configuration of multiple joint TDRA tables is supported regardless of whether the first co-scheduled cell set and the second co-scheduled cell set share the same service cell (i.e., whether the first service cell belongs to both the first set and the second set). In another example, the configuration of multiple joint TDRA tables is supported only when the first set and the second set do not share any service cell (i.e., when there is no service cell that belongs to both the first set and the second set). In yet another example, when the first co-scheduled cell set and the second co-scheduled cell set share a service cell (i.e., there is at least one service cell that belongs to both the first set and the second set), the UE may be configured with a single / shared joint TDRA table corresponding to the union of the first co-scheduled cell set and the second co-scheduled cell set. Therefore, when the UE detects a DCI format for multi-cell scheduling of the first co-scheduled cell set, the TDRA field in the DCI format indicates an index of a row of the single / shared joint TDRA table, which in turn indicates a plurality of TDRA values ​​for a plurality of corresponding cells included in the first co-scheduled cell set. In this example, the UE discards the TDRA indicated by the single / shared joint TDRA table for other serving cells that are not included in the first co-scheduled cell set and belong only to the second co-scheduled cell set.

[0299] In one example, when the UE may be configured with a value of a time domain higher layer parameter (such as PDSCH-TimeDomainResourceAllocationList or PUSCH-TimeDomainResourceAllocationList (or its multi-cell variant)) indicating that no joint TDRA table is configured for multi-cell scheduled operation, in one option, the UE uses a cell-specific TDRA table. In a second option, the UE uses a default TDRA table provided in a specification for system operation, such as those for single-cell operation in [TS38.214 v17.1.0], and applies the table entries for each / all co-scheduled cells. In another example, the specification for system operation provides a new multi-cell default TDRA table based on multiple co-scheduled cells (e.g., a first default table for two co-scheduled cells, a second default table for three co-scheduled cells, etc.), and the UE applies the TDRA table entries based on the ordering of the co-scheduled cells, as described in various examples of the present disclosure, such as in ascending (or descending) order based on a cell index or a cell-specific CIF.

[0300] In one example, when the UE is configured with a first SCS for an active BWP of a first co-scheduled cell and a second SCS for an active BWP of a second co-scheduled cell, the UE receives the first PDSCH and the second PDSCH or transmits the first PUSCH and the second PUSCH by interpreting the TDRA / FDRA field of the multi-cell scheduling DCI format:

[0301] - In one option: for a first co-scheduled cell based on a first SCS configuration, and for a second co-scheduled cell based on a second SCS configuration;

[0302] - in the second option: for all serving cells included in the co-scheduled cell set, based on the minimum SCS configuration among the first and second SCS configurations (generally, based on the minimum SCS configuration among the SCS configurations for serving cells in the co-scheduled cell set);

[0303] - In the third option: for all serving cells included in the set of co-scheduled cells, based on the maximum SCS configuration among the first and second SCS configurations (generally, based on the maximum SCS configuration among the SCS configurations for serving cells in the set of co-scheduled cells).

[0304] In one example, multi-cell scheduling is supported only for a set of co-scheduled cells with the same SCS on corresponding active DL / UL BWPs.

[0305] In one example, multi-cell scheduling is restricted to a set of co-scheduled cells operating with the same TDD configuration.

[0306] In one example, other scheduling parameters related to resource allocation, such as VRB to PRB mapping, PRB bundling, rate matching, and ZP CSI-RS triggering, may follow a higher layer configuration, or may be provided as cell-common scheduling parameters for all co-scheduled cells. For example, VRB to PRB mapping may be cell-common, such as when a co-scheduled cell set is in an intra-band CA setting. In one example, some or all of those scheduling parameters may not be present in the DCI format for multi-cell scheduling, and may be provided to the UE by higher layer signaling, either jointly or individually, for each cell from a co-scheduled cell set. In another example, depending on the specification of the system operation, some parameters may be disabled (not applicable) for multi-cell scheduling operations, such as the absence of VRB to PRB mapping, or PRB bundling, or ZP CSI-RS triggering.

[0307] In one example, a modulation and coding scheme (MCS) parameter may be cell-common for a set of co-scheduled cells, or may be provided by a differential indication. In one example, a DCI format may provide a single MCS value applied to a set of co-scheduled cells, for example, for the case of intra-band CA operation. In another example, a DCI format may provide a first MCS for a first cell from the co-scheduled cells and a differential MCS value for the remaining cells of the co-scheduled cells. The UE may determine a second MCS value for a second cell from the co-scheduled cells by adding the differential value to the first value.

[0308] In one example, the DCI format provides a new data indicator (NDI) parameter and a redundancy version (RV) parameter for each co-scheduled cell, respectively. In one example, the UE may be configured to operate with a restricted subset of RVs for multi-cell scheduling. For example, the UE may be configured with two RV values, such as RV=0 or RV=2 (alternatively, RV=0 or RV=3), instead of four RV values ​​used in a single-cell scheduling DCI format, so that only one bit is sufficient to indicate the RV of each serving cell. For example, for a co-scheduled cell set including N serving cells, the UE can be configured with N bits for the RV DCI field in the corresponding multi-cell scheduling DCI format. In another example, according to the specification of the system operation, the UE expects that only new / initial transmissions of TBs are supported for multi-cell scheduling. In this case, the UE does not expect an indication of NDI or RV because all PDSCH / PUSCH on the co-scheduled cells will correspond to a switched NDI value or RV value of zero. The restriction may apply to all HARQ processes or a subset of HARQ processes. The subset of the HARQ process may be configured by a higher layer.

[0309] In one example, the UE can receive a cell common NDI value, such as an indication for all handovers, which is applied to the co-scheduled cells.

[0310] In one example, the HARQ process number (HPN) is a cell-specific parameter provided separately for each co-scheduled PDSCH / PUSCH through the multi-cell scheduling DCI format.

[0311] In one example, the UE may operate with a subset of the HARQ processes of each serving cell (of BWP) for multi-cell scheduling compared to single-cell scheduling. Therefore, a reduced number of bits may be used to indicate the HPN in the DCI format for multi-cell scheduling. For example, the UE operates with only N=4 or 8 HARQ processes per serving cell (of BWP) for multi-cell processing, instead of 16 or 32 HARQ processes that the UE operates for single-cell scheduling, so only 2 or 3 bits per co-scheduled cell are sufficient for the HPN field. For example, the UE may operate with only the first N=4 or 8 HARQ processes of each serving cell (of BWP) from a set of co-scheduled cells. In another example, a higher layer configuration provides the ID of the HARQ process of each serving cell (of BWP) that the UE operates for multi-cell scheduling. Therefore, the HARQ process number (HPN) field in the DCI format for multi-cell scheduling on a set of co-scheduled cells provides a code point to the ID of a sub-selected set of N=4 or 8 HARQ processes. For example, a code point '000' (or '00') of the HPN field for a co-scheduled cell corresponds to a first sub-selected HARQ process (or simply the first HARQ process) provided by a higher layer of the co-scheduled cell, a code point '001' (or '01') corresponds to a second sub-selected HARQ process (or simply the second HARQ process) provided by a higher layer of the co-scheduled cell, and so on. Note that HPN is a cell-specific field in the DCI format, which is indicated separately for each co-scheduled cell, but with a reduced number of bits.

[0312] In one example, the selection of a subset of HARQ processes for multi-cell scheduling may be provided by a MAC-CE command, and the codepoints in the DCI format correspond to the HARQ processes provided by the MAC-CE command. In one example, a single MAC-CE command may provide HARQ processes for multiple serving cells, such as a co-scheduled set of cells.

[0313] In one example, the UE does not expect to be configured with a multi-cell scheduling DCI format that includes scheduling information for a second transport block / codeword (such as one or more of MCS, NDI, RV, etc.). Therefore, all co-scheduled PDSCH / PUSCH include only one transport block / codeword. In another example, the multi-cell scheduling DCI format can include information of one or more second transport blocks / codewords in the co-scheduled PDSCH / PUSCH, where such information can be cell-specific. For example, such information can be included in the DCI format or can be provided by an auxiliary method, such as an additional PDSCH or PDCCH that can include a portion of the scheduling information for the co-scheduled cell (such as one or more of the cell-specific DCI fields). The UE determines whether there can / may be a second transport block / codeword for the PDSCH / PUSCH from the co-scheduled PDSCH / PUSCH based on a high-level configuration (such as through a maxNrofCodeWordsScheduledByDCI parameter for the corresponding serving cell). For example, when the UE is indicated by a higher layer that the co-scheduled cell set has N cells and reception on the set of N cells may include a maximum number of M TBs (where M>N) across the N cells, the UE expects to receive an MC-DCI format including (at least) M values ​​for some (cell-specific) fields (such as one or more of the NDI, HPN, RV, MCS, etc. fields). For example, when the co-scheduled cell set includes a first cell whose PDSCH reception can include up to two TBs, a second cell whose PDSCH reception can include only one TB, and a third cell whose PDSCH reception can include up to two TBs, the UE expects to receive (at least) 2+1+2=5 values ​​of the aforementioned fields. In one example, the UE expects to receive a MC-DCI format with some (cell-specific) fields. MC-DCI format of the value, such as one or more of NDI, HPN, RV, MCS, etc., wherein is the maximum value field, the number of TBs that can be received in the co-scheduled cell set across all configured co-scheduled cell sets. That is, when Indicates the number of TBs that can be provided by PDSCH reception on a cell from the co-scheduled cell set and the UE is configured with S sets of co-scheduled cells, the UE determines .

[0314] Alternatively, in, is the size of the maximum set of co-scheduled cells, i.e. the set of co-scheduled cells comprising the maximum number of cells, and is the maximum number of cells in the set of S co-scheduled cells, where the corresponding PDSCH reception can include up to two TBs. For example, if co-scheduling can be for cells {1,2,3,4}, {5,6,7,8}, {1,2,5,6} and {3,4,7,8}, and PDSCH reception with up to two TBs can be only on cell 1 and cell 2, then the MC-DCI format can be sized based on two cells where the corresponding PDSCH reception can have up to two TBs and 2 cells where the corresponding PDSCH reception can have only one TB. In one example, when the MC-DCI format can schedule PDSCH reception providing a total of M TBs, where , the MC-DCI format may include fields ( ) reserved values ​​that are appended to the M valid values ​​of the field. Therefore, the UE is able to determine the bit width of the field based on the maximum number of bits required for the field across different combinations of co-scheduled cells, and the UE is able to determine the bit width of each value corresponding to each scheduled cell based on the corresponding configuration of the cell. In one example, when the UE configures two TBs for each PDSCH of a cell from a cell co-scheduled by a multi-cell scheduling DCI format, the two values ​​of the cell-specific parameters corresponding to the two TBs can be adjacent in the DCI format, regardless of whether the DCI format schedules one TB or two TBs for the PDSCH on the cell. For example, when the DCI format schedules only one TB for the PDSCH on the cell, the DCI format includes a first MCS / NDI / HPN / RV value for the first TB, and the UE includes a second MCS / NDI / HPN / RV value for the second TB that is set to a reserved value. For example, the second MCS value may indicate I_MCS=26, and the second RV value may indicate RV=1. In another example, at least some of the second MCS / NDI / HPN / RV values ​​(such as a reserved second HPN value or a second NDI value) may be dropped from the DCI format or may be placed as part of the padding bits, similar to those for non-scheduled cells as described previously.

[0315] In one example, some HARQ related parameters may not be present in the DCI format for multi-cell scheduling. For example, multi-cell scheduling does not support code-block group (CBG) operation, and the UE does not expect to receive an indication of a code block group transmission indicator (CBGTI) or code block group flush indicator (CBGFI) parameter for a co-scheduled cell.

[0316] In one example, when a UE is configured with different TDD configurations or different SCSs on respective DL BWPs of respective co-scheduled cells, and the UE is provided with a cell-common PDSCHs-to-HARQ_Feedback timing value (K1) for multiple PDSCHs on the respective co-scheduled cells, the UE interprets the K1 value relative to a time slot for PUCCH transmission that overlaps with a time slot of the latest PDSCH reception on the cell from the co-scheduled cell. For example, if the DCI format schedules two PDSCH receptions on two respective cells, where with reference to the time slot of the PUCCH transmission, for the PUCCH transmission, the PDSCH reception on the first cell ends in time slot n and the PDSCH reception on the second cell ends in time slot n+1, the UE interprets the K1 value relative to time slot n+1.

[0317] In one example, the priority indicator may be a cell-common parameter in a DCI format for multi-cell scheduling, for example, because the UE does not expect PDSCHs with different priority levels to be co-scheduled by the same DCI format. In one example, the priority indicator may not be present in a DCI format for multi-cell scheduling. For example, in the case of multi-cell scheduling, the UE determines a reference / default priority level for co-scheduled PDSCHs, such as priority 0 (or priority 1).

[0318] In one example, some MIMO-related parameters (such as DM-RS sequence initialization) may not be present in the DCI format for multi-cell scheduling, but provided by a higher layer configuration. In one example, the DM-RS sequence initialization may be a cell common field, which is provided once in the DCI format for multi-cell scheduling, and its value is commonly applied to the corresponding co-scheduled PDSCH.

[0319] In one example, some parameters may be the same for single-cell and multi-cell scheduling. For example, the SRS request field in the DCI format can be used to provide the same indication for multi-cell scheduling as for single-cell scheduling on the primary cell.

[0320] In one example, the configuration of some fields supported in the DCI format for single-cell scheduling may not be supported in the DCI format for multi-cell scheduling, such as DCI fields related to unlicensed band operation or UE power saving operation. For example, the indication of SCell dormancy may not be supported in the DCI format for multi-cell scheduling. For example, the DCI format for multi-cell scheduling may not include one or more of the following DCI fields: ChannelAccess-CPext, minimum applicable scheduling offset indicator, PDCCH monitoring adaptation indication, invalid symbol pattern indicator, sidelink allocation index, etc.

[0321] In one example, when no serving cell in the set of co-scheduled cells is configured with a SUL carrier, in one option, the DCI format for multi-cell scheduling does not include the UL / SUL field. In another option, the UL / SUL indicator field is configured / present in the DCI format, but the field is reserved.

[0322] In another example, the UL / SUL indicator field may be disabled for a DCI format used for multi-cell scheduling. For example, the UE does not expect the UL / SUL indicator field in a multi-cell scheduling DCI format:

[0323] - In an example, when none of the serving cells in the co-scheduled cell set is configured with a SUL carrier;

[0324] - in another example, when the UE is not configured for SUL of at least one serving cell in the co-scheduled cell set (although SUL carriers may be configured for some other serving cells in the co-scheduled cell set), or

[0325] - In yet another example, even when the UE is configured to co-schedule the SUL carriers of all serving cells in the cell set (ie disabled based on the specification of the system operation).

[0326] In this document, when a field is disabled (for the UL / SUL indicator field, or generally for any DCI field), in one option, the field is not present in the DCI format for multi-cell scheduling, or in another option, the field is configured / present in the DCI format, but the field is retained.

[0327] In one example, when the UL / SUL indicator field is disabled (i.e., not present or retained) in a DCI format for multi-cell scheduling, the UE determines an uplink carrier for a PUSCH for a co-scheduled PUSCH on a cell of a co-scheduled cell set configured as a SUL carrier based on:

[0328] - the uplink carrier (UL or SUL) indicated by the last single-cell scheduling DCI sent by the PUSCH scheduling the cell, or

[0329] - the uplink carrier on which the UE sent the last PUSCH, or

[0330] - Reference to an uplink carrier, such as a UL carrier (or SUL carrier), which is predetermined in the specification of the system operation or provided by a higher layer configuration.

[0331] In the above example, the UE can determine the last DCI format or the last PUSCH based on the last / end symbol of the most recently received PDCCH or PUSCH. In this article, the symbol or time slot can be relative to the SCS configuration of the last DCI format / PDCCH or PUSCH, or the SCS configuration of the co-scheduled PUSCH, or the minimum (or maximum) SCS configuration among a set of co-scheduled cells, or a reference SCS configuration, etc.

[0332] In one example, the UE determines the last DCI format / PDCCH or PUSCH considering a time offset (e.g., T symbols / time slots, such as a DCI format / PDCCH processing time or a PUSCH processing time, etc.) For example, if the end symbol or time slot of the first DCI format / PDCCH or the first PUSCH is after a symbol or time slot of T symbols / time slots before the start symbol / time slot of the co-scheduled PUSCH or the start symbol / time slot of the DCI format for multi-cell scheduling, the UE does not consider the first DCI format / PDCCH or the first PUSCH when determining the last DCI format / PDCCH or PUSCH.

[0333] In one example, a DCI format for multi-cell scheduling may include a cell-common UL / SUL indicator field and is therefore applicable to all cells in a co-scheduled cell set. In one example, when a UE receives a DCI format for multi-cell scheduling with a cell-common UL / SUL indicator field and the UE is not configured for a SUL carrier of a serving cell from the co-scheduled cell set, the UE ignores the UL / SUL indicator field for PUSCH transmissions on the serving cell.

[0334] In one example, a DCI format for multi-cell scheduling of a set of co-scheduled cells can include an indication of a first subset of cells having PUSCH transmissions on a corresponding UL carrier or a second subset of cells having PUSCH transmissions on a corresponding SUL carrier. In this document, the first subset and the second subset are subsets of the set of co-scheduled cells. For example, the multi-cell scheduling DCI format can include a SUL indicator field (having, for example, 1-3 bits) indicating a code point corresponding to a subset of the set of co-scheduled cells, as configured in a higher layer. Therefore, for the cells included in the subset indicated by the code point of the SUL indicator field, the UE transmits a PUSCH on the corresponding SUL carrier, and for all remaining cells in the set of co-scheduled cells not included in the indicated subset, the UE transmits a PUSCH on the corresponding UL carrier.

[0335] In one example, the UL / SUL indication may be based on a bitmap whose number of bits is equal to the number of co-scheduled cells, wherein the MSB or LSB bits of the bitmap are mapped to the co-scheduled cells in a predetermined order, such as ascending order of (individual / cell-specific) CIF values ​​or ascending order of cell indexes, etc.

[0336] In one example, the CSI request field is provided only once in the multi-cell scheduling DCI format for the co-scheduled PUSCH, with the same bit width as in [TS 38.212 v16.8.0], where the UE process is as follows. In one example, CSI is multiplexed on only one PUSCH in the co-scheduled PUSCH on the co-scheduled cell set, where the PUSCH:

[0337] - in the first option, corresponds to the serving cell with the smallest (or largest) cell index among the co-scheduled cells; or

[0338] - in the second option, corresponds to the serving cell with the smallest (or largest) CIF in the co-scheduled cell set; or

[0339] - in the third option, corresponds to the earliest (or latest) starting PUSCH in the co-scheduled PUSCH set; or

[0340] - in the fourth option, corresponds to the earliest (or latest) ending PUSCH in the co-scheduled PUSCH set; or

[0341] - In the fifth option, corresponding to the first / first (or last) PUSCH that meets the CSI processing / multiplexing timeline in a set of co-scheduled PUSCHs or in a subset of co-scheduled PUSCHs that meet the CSI processing / multiplexing timeline.

[0342] - In the sixth option, it corresponds to a cell configured by a higher layer or indicated by a DCI format for multi-cell scheduling.

[0343] In this article, the earliest / latest start or earliest / latest end refers to the start or end symbol / time slot, where the symbol / time slot is about the SCS configuration of the scheduled cell, or the reference SCS configuration, or the minimum (or maximum) SCS configuration among a set of co-scheduled cells, etc.

[0344] In one example, when at least one co-scheduled cell is configured with a dynamic indication of a β offset value for UCI multiplexing, the DCI format for multi-cell scheduling of a PUSCH on a set of co-scheduled cells may include a β offset indicator field having the same bit width as in [TS 38.212 v17.1.0], such as 2 bits. For example, the UE multiplexes UCI on only one PUSCH of one or more co-scheduled PUSCHs on a set of co-scheduled cells, where the PUSCH may be determined based on one of the first / second / third / fourth / fifth / sixth options described above for the CSI request field.

[0345] In one example, the DCI format for multi-cell scheduling of PUSCH does not include the UL-SCH indicator field.For example, the UE does not expect PUSCH from the co-scheduled PUSCH to be transmitted only for transmission of CSI reports.

[0346] In another example, the DCI format for multi-cell scheduling of PUSCH can include a UL-SCH indicator field, and the UL-SCH indicator field is applied to only one of the co-scheduled PUSCHs. For example, the UE determines that the PUSCH only includes UCI based on one of the first / second / third / fourth / fifth / sixth options described above for the CSI request field.

[0347] In one embodiment, for a UE configured with multiple groups of co-scheduled cells, the DCI format for multi-cell scheduling can provide complete or partial scheduling 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 scheduling information, the UE can determine the remaining scheduling information from the UE-specific RRC signaling, or by using other complementary methods.

[0348] In one example, a DCI format for multi-cell scheduling may have the same size as a DCI format for single-cell scheduling. This may enable the total number of DCI format sizes to be maintained when supporting multi-cell scheduling and avoid segmentation of multiple PDCCH candidates that the UE may monitor over an increased number of DCI format sizes, thereby avoiding having a smaller number of PDCCH candidates per DCI format size. In another example, the UE does not expect to receive a DCI format for multi-cell scheduling that is the same as or has the same size as DCI format 1_0 or 0_0, because the distinction between single-cell scheduling and multi-cell scheduling may not be possible, because the additional field that provides such a distinction may not be included in DCI format 1_0 or 0_0.

[0349] In one embodiment, the DCI format for multi-cell scheduling can provide separate scheduling information by separate values ​​of the corresponding fields for each of the serving cells. The first value corresponds to the first cell, the second value corresponds to the second cell, and so on. Therefore, the DCI format fields for multiple cells are cascaded, so that such a DCI format is referred to as a cascaded DCI format for multi-cell scheduling. This method may be beneficial, for example, for co-scheduling cells with different channel characteristics or configurations (such as for inter-band CA operation).

[0350] In one example, the concatenated DCI format for multi-cell scheduling consists of multiple "field blocks", where each field block includes multiple values ​​corresponding to multiple co-scheduled cells.

[0351] In another example, a concatenated DCI format for multi-cell scheduling consists of multiple "DCI format blocks", where each DCI format block provides scheduling information for a corresponding cell from multiple co-scheduled cells.

[0352] Support of concatenated DCI formats for multi-cell scheduling may be limited to the number of co-scheduled cells, such as for up to 2 cells.

[0353] In one example, the cascaded DCI format for multi-cell scheduling may exclude certain scheduling parameters compared to the fields in the single-cell scheduling DCI format, where those parameters may be configured by higher layers. This higher layer configuration may be per co-scheduled cell, or a subset of per co-scheduled cells. For example, some resource allocation fields such as PRB to VRB mapping or PRB bundling may be provided by higher layer signaling, while other fields such as ZP CSI-RS triggering may only be provided by the single-cell scheduling DCI format.

[0354] In one example, a concatenated DCI format may include a set of cell common scheduling information parameters, where, for example, a block of cell common fields may be placed first in the DCI format, followed by a block of multiple cell specific fields in ascending order of cell index or CIF.

[0355] The set of cell-common scheduling information parameters may be predetermined in the specification of the system operation, or may be provided by high-layer signaling. For example, the cell-common parameters may generally include parameters that are not related to PDSCH reception, and in particular one or more of the following: a PUCCH resource indicator (PRI), a transmit power control (TPC) command for PUCCH, or a PDSCH-to-HARQ_feedback timing indicator (K1) field, or a downlink assignment information (DAI) field (when applicable). Thus, the UE determines to send HARQ feedback information corresponding to multiple PDSCHs of multiple co-scheduled cells in the same PUCCH resource as indicated by the common PRI, or using the same TPC command, or using the same K1 timeline as indicated by the K1 parameter (as indicated in the cell-common field of the concatenated DCI format). Another cell-common parameter may be the link direction of the co-scheduled cells to indicate that all cells are co-scheduled for DL ​​reception (i.e., multiple PDSCHs) or for UL transmission (i.e., multiple PUSCHs).

[0356] In one example, for a UE configured with a set of co-scheduled cells, the UE does not expect to be configured / indicated PUCCH repetition (at least associated with multi-TRP operation), such as for transmitting HARQ-ACK feedback information corresponding to the co-scheduled PDSCH on the set of co-scheduled cells. Therefore, the UE does not expect to be configured with a second TPC command in DCI format for multi-cell scheduling on the set of co-scheduled cells.

[0357] In another example, for a UE configured with a set of co-scheduled cells, the UE can be configured or indicated with PUCCH repetition (associated with multi-TRP operation), such as for transmitting HARQ-ACK feedback information corresponding to the co-scheduled PDSCH on the set of co-scheduled cells. Thus, the multi-cell scheduling DCI format for the set of co-scheduled cells can include a second TPC command provided in a cell-common manner. Thus, there is only one such field in the DCI format, e.g., 2 bits.

[0358] In one example, the values ​​of some cell-specific scheduling parameters may be provided by the specification of the system operation, or provided via higher layer signaling. Therefore, there may be no DCI field corresponding to such cell-specific scheduling parameters in the concatenated DCI format for multi-cell scheduling.

[0359] In one embodiment, multi-cell mapping may be used to provide information for multi-cell scheduling of multiple PDSCH / PDCCH on multiple corresponding cells to a UE, wherein a field in a DCI format may be interpreted as providing multiple values ​​of corresponding scheduling parameters for multiple co-scheduled cells. Such an interpretation may be based on a configured one-to-many mapping / table or based on multiple configured offset values ​​applied to a reference value indicated by the DCI format. A field in a DCI format that may be interpreted based on a multi-cell mapping may be referred to as a DCI field with a multi-cell mapping. This approach may be beneficial, for example, for co-scheduling cells having similar physical channel characteristics or configurations, such as for intra-band CA operations.

[0360] In one example, for any scheduling parameter corresponding to a DCI field with multi-cell mapping, a predetermined or configured mapping or table, also referred to as a "code point", may be provided to the UE so that the value of the DCI field may be mapped to multiple values ​​of the corresponding scheduling parameter. In another example, for any scheduling parameter corresponding to a DCI field with multi-cell mapping, the UE may be configured with one or more adjustment parameters, such as an offset value or a scaling factor, so that the UE may determine one or more additional values ​​based on an adjustment of a reference value indicated by the DCI field. In all approaches, each DCI field with multi-cell mapping may have a one-to-many interpretation, rather than a one-to-one interpretation.

[0361] FIG. 6 illustrates a method 600 for multi-cell scheduling based on a DCI field with a multi-cell mapping using a configured one-to-many mapping / table according to an embodiment of the present disclosure. The embodiment of the method 600 for multi-cell scheduling based on a DCI field with a multi-cell mapping using a configured one-to-many mapping / table shown in FIG. 6 is for illustration only. FIG. 6 does not limit the scope of the present disclosure to any particular implementation of the method 600 for multi-cell scheduling based on a DCI field with a multi-cell mapping using a configured one-to-many mapping / table.

[0362] As shown in FIG. 6 , method 600 begins at step 610, where a UE (such as UE 116) is configured with a set of co-scheduled cells. At step 620, the UE is configured with cell-specific scheduling parameters for the co-scheduled cells. At step 630, the UE is configured with a multi-cell mapping between a value of a DCI field and a first value and a second value of the cell-specific scheduling parameter. At step 640, the UE receives a DCI format having an indication for co-scheduling a first cell and a second cell from the set of co-scheduled cells. At step 650, the UE receives the value of the DCI field in a DCI format. At step 660, the UE determines, based on the value of the DCI field and the configured multi-cell mapping, a first value corresponding to a first PDSCH / PUSCH on a first cell and a second value corresponding to a second PDSCH / PUSCH on a second cell for the cell-specific scheduling parameter. At step 670, the UE receives a first PDSCH and a second PDSCH or sends a first PUSCH and a second PUSCH on a first co-scheduled cell and a second co-scheduled cell, respectively, based on the determined first value and second value of the cell-specific scheduling parameter.

[0363] In one example, for a DCI field with multi-cell mapping, the UE may be configured with a table having rows corresponding to possible values ​​of the DCI field and columns corresponding to different interpretations of the DCI field. For example, the first column may correspond to a first / baseline interpretation / value of the DCI field, the second column may correspond to a second interpretation / value of the DCI field, and so on. For example, if the MCS field is a DCI field with multi-cell mapping, the first column provides a first / baseline MCS value of a first / baseline MCS table of 32 possible values ​​corresponding to a 5-bit MCS field. In one example, the second column may correspond to a second MCS table, which may be separate from the first MCS table or may be obtained by a variation or permutation of an entry of the first MCS table.

[0364] For example, a DCI field with an MCS value of '00000' may refer to the first entry of the first MCS table, and a value of '00001' may refer to the second entry of the first MCS table. Then, for the case of a DCI field with multi-cell mapping, in one example, a value of '00000' may refer to the first entry of the first MCS table, and a value of '00001' may also refer to the first entry of the first MCS table. In another example, a value of '00000' may refer to the third entry of the first MCS table, and a value of '00001' may refer to the fourth entry of the second MCS table. In yet another example, a value of '00000' may refer to the first entry of the first MCS table, and a value of '00001' may refer to the first entry of the third MCS table.

[0365] The DCI field with multi-cell mapping may be, for example, one or more of the following: MCS, antenna port (AP), TCI state, SRI, TPMI, FDRA or TDRA, etc.

[0366] In one example, for a DCI field with multi-cell mapping, different interpretations of the DCI field value, such as different columns of a configuration table associated with the DCI field, correspond to different co-scheduled cells. For example, a table with two columns may be provided to a UE configured for 2-cell scheduling, and a table with four columns may be provided to a UE configured for 4-cell scheduling. The first column may correspond to a first co-scheduled cell, the second column may correspond to a second co-scheduled cell, and so on. In one example, when a UE is configured with a set of 4 co-scheduled cells and the UE is indicated for two PDSCH / PUSCHs on two of the 4 co-scheduled cells (such as a first PDSCH on a first cell and a second PDSCH on a fourth cell), the UE operates with the values ​​provided in the first and fourth columns of the configured table for the first PDSCH and the second PDSCH, respectively, where the values ​​are provided by mapping a single value of a field in the DCI format to the values ​​in the first and fourth columns of the configured table.

[0367] FIG. 7 illustrates a method 700 for multi-cell scheduling based on a DCI field with a multi-cell mapping table according to an embodiment of the present disclosure. The embodiment of the method 700 for multi-cell scheduling based on a DCI field with a multi-cell mapping table shown in FIG. 7 is for illustration only. FIG. 7 does not limit the scope of the present disclosure to any particular implementation of the method 700 for multi-cell scheduling based on a DCI field with a multi-cell mapping table.

[0368] As shown in FIG. 7 , the method begins at step 710, where a UE (such as UE 116) is configured with a co-scheduled set of cells. At step 720, the UE is configured with a multi-cell mapping table of cell-specific scheduling parameters for multi-cell scheduling. At step 730, the UE receives a DCI format having an indication for co-scheduling a first cell and a second cell from the co-scheduled set of cells. At step 740, the UE receives a value of a DCI field corresponding to the cell-specific scheduling parameter in the DCI format. At step 750, the UE determines a first value corresponding to a first PDSCH / PUSCH on a first cell for the cell-specific scheduling parameter based on the value received in the DCI field according to the value provided in the first column of the multi-cell mapping table. At step 760, the UE determines a second value corresponding to a second PDSCH / PUSCH on a second cell for the cell-specific scheduling parameter based on the value received in the DCI field according to the value provided in the second column of the multi-cell mapping table. At step 770, the UE receives the first PDSCH and the second PDSCH or sends the first PUSCH and the second PUSCH on the first co-scheduled cell and the second co-scheduled cell, respectively, based on the determined first value and second value of the cell-specific scheduling parameter.

[0369] In one example, for a DCI field with multi-cell mapping, different interpretations of the DCI field value, such as different columns of a configuration table associated with the DCI field, correspond to different operating levels compared to a reference level. For example, the first column in the configuration table refers to a reference operating level, where the UE can use a first value of a scheduling parameter corresponding to the DCI field, and the other columns refer to differential levels from the reference operating level. In another example, columns other than the first column may refer to absolute levels rather than differential levels.

[0370] According to the method, a UE can be provided with an operating level for each of the co-scheduled cells, and can determine from a configured table a column for a corresponding DCI field with a multi-cell mapping for each of the co-scheduled cells. Then, to interpret the DCI field with the multi-cell mapping, the UE applies a first value corresponding to a first operating level of the first co-scheduled cell from a first column of the configured table, and a second value corresponding to a second operating level of the second co-scheduled cell from a second column of the configured table. The first and second operating levels may be the same or different. For example, when the first operating level is the same as the second operating level, the UE applies the same value from the same column of the configured table to both the first co-scheduled cell and the second co-scheduled cell.

[0371] In one example, for a serving cell, an operating level corresponding to a DCI field with multi-cell mapping may change over time. For example, to interpret a DCI field with multi-cell mapping, the UE may apply a first value from a first column of a configured table corresponding to a first operating level for a first PDSCH / PUSCH on a cell in a first time slot, and apply a second value from a second column of a configured table corresponding to a second operating level for a second PDSCH / PUSCH on a cell in a second time slot.

[0372] In one example, the operation levels for different scheduling parameters can be provided to the UE separately for cells from the set of co-scheduled cells, such as different column indexes in different tables corresponding to different DCI fields with multi-cell mapping.

[0373] In another example, for cells from a set of co-scheduled cells, a common operating level for different scheduling parameters can be provided to the UE, such as the same column index in different tables corresponding to different DCI fields with multi-cell mapping.

[0374] In one example, the UE receives information of (one or more) operating levels corresponding to the DCI field with multi-cell mapping via high-layer signaling for each cell from a set of co-scheduled cells. Thus, when the DCI field with multi-cell mapping is reinterpreted for any / all PDSCH or PUSCH scheduled on the cell by the multi-cell scheduling DCI format, the UE applies the configured operating level.

[0375] In another example, the UE receives information of (one or more) operating levels corresponding to the DCI field with multi-cell mapping via a DCI format for multi-cell scheduling. Thus, the UE may receive a first multi-cell scheduling DCI format indicating a first operating level for a first PDSCH / PUSCH on a co-scheduled cell, and receive a second multi-cell scheduling DCI format indicating a second operating level for a second PDSCH / PUSCH on a co-scheduled cell.

[0376] In yet another example, the UE determines information of (one or more) operating levels corresponding to a DCI field with multi-cell mapping based on predetermined or configured UE measurements for scheduling PDSCH / PUSCH on cells from a set of co-scheduled cells. In this document, the UE measurement may refer to RSRP or SINR measurements of a channel or signal, etc., such as a reference signal associated with a scheduled PDSCH / PUSCH on a scheduled cell. In an example, the reference signal associated with the PDSCH / PUSCH may refer to an SSB or CSI-RS or SRS, etc., which is QCL with the PDSCH / PUSCH, such as QCL type-D, or is provided as a downlink or uplink, separate or joint TCI state of the PDSCH / PUSCH (part of it), or is provided as a reference or target spatial relationship corresponding to the PDSCH / PUSCH, or is provided as a default beam / spatial relationship for the PDSCH / PUSCH.

[0377] FIG8 illustrates a method 800 for multi-cell scheduling based on a DCI field with a multi-cell mapping and an operating level set for co-scheduled cells according to an embodiment of the present disclosure. The embodiment of the method 800 for multi-cell scheduling based on a DCI field with a multi-cell mapping and an operating level set for co-scheduled cells shown in FIG8 is for illustration only. FIG8 does not limit the scope of the present disclosure to any particular implementation of the method 800 for multi-cell scheduling based on a DCI field with a multi-cell mapping and an operating level set for co-scheduled cells.

[0378] As shown in FIG. 8 , the method begins at step 810, where a UE (such as UE 116) is configured with a set of co-scheduled cells. At step 820, the UE is configured with a mapping between a set of operating levels and a column of a multi-cell mapping table. At step 830, the UE is configured with a mapping between a set of operating levels and a column of a multi-cell mapping table. At step 840, the UE receives a DCI format having an indication for co-scheduling a first cell and a second cell from the set of co-scheduled cells. At step 850, the UE receives in the DCI format a value of a DCI field corresponding to a cell-specific scheduling parameter and an operating level of the second cell from the configured set of operating levels. At step 860, the UE determines, based on the value received in the DCI field, a first value corresponding to a first PDSCH / PUSCH on the first cell for the cell-specific scheduling parameter according to a value provided in a first column of the multi-cell mapping table. At step 870, the UE determines a column from the multi-cell mapping table for the second cell based on the operating level indicated in the DCI and the configured mapping. At step 880, the UE determines, based on the value received in the DCI field, a second value corresponding to the second PDSCH / PUSCH on the second cell for the cell-specific scheduling parameter according to the value provided in the determined column of the multi-cell mapping table. At step 890, the UE receives the first PDSCH and the second PDSCH or sends the first PUSCH and the second PUSCH on the first co-scheduled cell and the second co-scheduled cell, respectively, based on the determined first value and second value of the cell-specific scheduling parameter.

[0379] For example, the UE may be configured with a mapping between multiple RSRP ranges and a set of operating levels for a DCI field with multi-cell mapping, such as a set of column indices in a configured mapping / table for scheduling parameters corresponding to the DCI field with multi-cell mapping. For example, the UE may be configured with N (such as N=4) RSRP ranges corresponding to N (such as N=4) operating levels. Thus, a first RSRP range may be mapped to a first operating level or a first column index, a second RSRP range may be mapped to a second operating level or a second column index, and so on. In one example, the UE reports the determined RSRP range or the corresponding operating level or table column index to the serving gNB, for example via L1 signaling in PUSCH or PUCCH or via MAC CE.

[0380] In one example, the UE may be configured with one or more adjustment parameters, such as an offset value or a scaling factor, so that the UE may determine one or more additional values ​​of the scheduling parameter based on the adjustment of the reference value indicated by the corresponding DCI field. For example, the UE may apply the offset to the index of the value corresponding to the scheduling parameter, or may directly apply the offset to the value of the scheduling parameter. For example, when the UE is configured with set O {-2,-1,0,1,2}, and when the multi-cell scheduling DCI format indicates an MCS value corresponding to entry I=17 in the MCS table, the offset value O=2 means using the MCS value corresponding to entry I+O=17+2=19, and the offset value O=-1 means using the MCS value corresponding to entry I+O=17-1=16. For example, the multi-cell scheduling DCI (MC-DCI) format includes a first MCS field of size 5 bits for the first cell in a set of co-scheduled cells, and a second MCS field of size 2 bits (or 3 bits) (and third and fourth MCS fields, if applicable), each MCS field providing a differential value from the value of the first MCS field. A single MCS field may also be defined, in which the first 5 bits from the set of co-scheduled cells are used for the first cell, the next two bits are used for the second cell, the next two bits are used for the third cell, and so on. In this document, the first cell in the set of co-scheduled cells can be the first cell in the configuration of the set of co-scheduled cells, or the cell with the smallest (or largest) cell index from the set of co-scheduled cells. When the offset value is {-20,-10,0,10,20} and the multi-cell scheduling DCI format indicates the MCS value corresponding to the coding rate with parameter R*

[1024] =379 in the MCS table, the offset value O=10 means using the MCS value corresponding to the coding rate with parameter R*

[1024] =379+10=389, and the offset value O=-20 means using the MCS value corresponding to the coding rate with parameter R*

[1024] =379-20=359.

[0381] For example, when O {-2,-1,0,1} or O {-1,0,1,2}, 2 bits can be used for differential MCS, or when 0 {-4,-3,-2,-1,0,1,2,3} or O {-3,-2,-1,0,1,2,3,4}, 3 bits can be used for differential MCS. In the example of {-2,-1,0,1}, the values ​​'00', '01', '10' or '11' in the MC-DCI format refer to the differential values ​​0=-2, 0=-1, 0=0 or 0=1, respectively. In another example, the offset value set of the differential MCS may be defined in the specification of the system operation, or may be provided by RRC information. For example, a table / sequence with 4 entries (or 8 entries) is provided to the UE, and these 4 entries (or 8 entries) provide 4 (or 8) offset O values ​​of the differential MCS, and these 4 (or 8) offset O values ​​correspond to the field values ​​{00,01,10,11} (or values ​​{000,001,010,011,100,101,110,111}) of the corresponding differential MCS value in the MC-DCI format. For example, the same offset value set for the differential MCS for all sets of co-scheduled cells may be provided to the UE. For example, separate sets of offset values ​​for differential MCSs for different sets of co-scheduled cells may be provided to the UE.

[0382] For example, when the UE is configured to schedule PDSCH reception or PUSCH transmission with up to 2 TBs per PDSCH reception or per PUSCH transmission on a cell from a co-scheduled cell set, the MC-DCI format includes a first (differential) MCS value for a first TB of the PDSCH / PUSCH on the cell, and includes a second differential MCS value for a second TB of the PDSCH / PUSCH on the cell. For example, the MC-DCI format includes a field having a size of 2 bits (or 3 bits) that provides a differential MCS of each TB from the second TB. For example, for a set including {cell #1, cell #2, cell #3, cell #4}, where PDSCH reception or PUSCH transmission has only 1 TB on cell #1 and cell #4 and up to 2 TBs on cell #2 and cell #3, the MCS field of the MC-DCI format includes a reference MCS value of size 5 bits for the first TB of cell #1, and a differential MCS value of size 2 bits for each of the first / only TBs of cell #2, cell #3, and cell #4, and includes a differential MCS value of size 2 bits for each of the second TBs of cell #1 and cell #4. As previously described, for the purpose of size alignment, the MC-DCI format may also include several reserved values ​​for MCS indication. In one example, the second differential MCS value of the second TB is relative to the corresponding first (differential) MCS value of the first TB. In another example, the second differential MCS value of the second TB is relative to the MCS value provided for the first TB associated with the first cell from the co-scheduled cell set (i.e., the same reference MCS used to determine the first differential MCS value of the first TB). In another example, the MC-DCI format does not include an MCS value for the second TB, and the UE desires to use the same MCS for the first TB and the second TB for PDSCH reception or PUSCH transmission on the cell.

[0383] In one example, adjustment parameters for each scheduling parameter / field of a corresponding multi-cell scheduling DCI format may be provided to the UE separately. In another example, a single adjustment parameter for all scheduling parameters / fields of a corresponding multi-cell scheduling DCI format may be provided to the UE. In yet another example, the adjustment parameter may be provided for each higher layer configuration, or the adjustment parameter may be changed based on an indication of a multi-cell scheduling DCI format or a UE measurement of RSRP for a reference signal associated with a co-scheduled PDSCH / PUSCH. In another example, the UE is capable of receiving an indication of an operating level, which is mapped to multiple adjustment parameters for multiple scheduling parameters / fields of a corresponding multi-cell scheduling DCI format, wherein the mapping is provided by high-layer signaling.

[0384] The gNB may configure a mapping / table or adjust parameters for reinterpretation of DCI fields with a multi-cell mapping for multi-cell scheduling based on an estimated combination of parameter values ​​across a set of co-scheduled cells. For example, for cells with relatively similar physical channel characteristics, such as for intra-band CA operation, the gNB may configure or indicate the same or similar values ​​for various scheduling parameters, such as for FDRA, TDRA, or MCS. For enhanced operation, the gNB may determine changes in parameter values ​​between co-scheduled cells based on, among other things, their relative operating frequencies and spatial / MIMO channel conditions. For example, based on the CSI reports of the co-scheduled cells, the gNB may determine the MCS offset of the scheduled cell from the co-scheduled cell.

[0385] In one example, a DCI field with multi-cell mapping of a scheduling parameter in a DCI format for multi-cell scheduling may have the same size as a corresponding DCI field of the same scheduling parameter in a DCI format for single-cell scheduling.

[0386] In another example, a DCI field with multi-cell mapping may have a different size, e.g., larger than the corresponding size in the DCI format for single-cell scheduling. For example, a DCI field with multi-cell mapping for MCS may have 6 or 7 bits. Such operation may be beneficial, e.g., to support an extended mapping / table between possible values ​​of a DCI field with multi-cell mapping (as rows in a table) and configuration combinations of values ​​of corresponding scheduling parameters for co-scheduled cells (as columns in a table). In this document, an extended mapping / table refers to a table with extended rows so that more interpretations or combinations of values ​​of corresponding scheduling parameters for multi-cell scheduling can be provided to the UE.

[0387] In one example, for a single cell scheduling DCI format, a 5-bit MCS field is provided to the UE to indicate one of up to 32 MCS values ​​from the MCS table. For multi-cell scheduling DCI and 2 co-scheduled cells, an MCS field with only 5 bits (instead of 10 bits) may be provided to the UE to indicate a pair of MCS values ​​of up to 32 possible pairs (instead of a maximum of 32 × 32 = 1024 possible pairs) of MCS values ​​from the MCS table. Each MCS value for the first co-scheduled cell may be associated with only one MCS value for the second co-scheduled cell. For example, the MCS value for the second cell may be the same as the MCS value for the first cell, or may be offset by a configured value relative to the MCS value of the first cell, as previously described. In general, the offset between the MCS value of the first cell and the MCS value of the second cell may depend on the MCS value of the first cell. For example, the first MCS value of the first cell can have a first offset from the second MCS value of the second cell, and the third MCS value of the first cell can have a second offset from the fourth MCS value of the second cell, wherein the first offset is different from the second offset. In this document, both the first offset and the second offset are configured in the mapping / table. However, when the UE is configured / indicated a single adjustment parameter (such as a single offset value) instead of a general one-to-many mapping / table, the UE applies the same offset regardless of the MCS value of the first cell.

[0388] If the MCS field in the DCI format for multi-cell scheduling has a larger size than that in the DCI format for single-cell scheduling, such as 6 bits versus 5 bits, a pair of MCS values ​​out of up to 64 possible MCS value pairs can be indicated to the UE from the MCS table. This method provides a trade-off between additional DCI overhead (up to a maximum of 5 bits) and additional scheduling flexibility because each MCS value for the first co-scheduled cell can be linked to two or more MCS values ​​for the second co-scheduled cell. Therefore, for the first and second co-scheduled cells, the 64-row table will include multiple rows with shared / repeated values ​​in the first column but different values ​​in the second column. In this article, the first column can correspond to the first co-scheduled cell, and the second column can correspond to the second co-scheduled cell. In one example, in addition to the 5-bit MCS field, a 1-bit differential MCS field can be provided, wherein the differential MCS field value provides an offset value relative to the MCS field value. For example, a "0" value of the differential MCS field can be mapped to a 0 value of the offset, and a "1" value of the differential MCS field can be mapped to an offset value specified in system operation or provided by high-level signaling.

[0389] This DCI field of multi-cell mapping with a 2-column table can also be applied to multi-cell scheduling of more than 2 cells when more than one co-scheduled cell can be associated with a column from the 2 columns in the table, such as when more than one cell shares the same operating level.

[0390] In one example, a DCI field with multi-cell mapping may refer to two or more scheduling parameters. For example, a UE can be configured with a one-to-many mapping with paired entries so that the value indicated by the DCI field with multi-cell mapping can be reinterpreted as a pair of values ​​for a pair of parameters for each co-scheduled cell. For example, a pair of scheduling parameters may include FDRA and TDRA, or may include MCS and the number of antenna ports (APs).

[0391] FIG. 9 illustrates a method 900 for multi-cell scheduling based on a DCI field with a multi-cell mapping, using a plurality of configured adjustment parameters corresponding to a plurality of co-scheduled cells, according to an embodiment of the present disclosure. The embodiment of the method 900 for multi-cell scheduling based on a DCI field with a multi-cell mapping, using a plurality of configured adjustment parameters corresponding to a plurality of co-scheduled cells shown in FIG. 9 is for illustration only. FIG. 9 does not limit the scope of the present disclosure to any particular implementation of the method 900 for multi-cell scheduling based on a DCI field with a multi-cell mapping, using a plurality of configured adjustment parameters corresponding to a plurality of co-scheduled cells.

[0392] As shown in FIG. 9 , method 900 begins at step 910, where a UE (such as UE 116) is configured with a co-scheduled cell set. At step 920, the UE is configured with cell-specific scheduling parameters for multi-cell scheduling. At step 930, the UE is configured with adjustment parameters for the cell-specific scheduling parameters for each cell in the co-scheduled cell set. At step 940, the UE receives a DCI format having an indication for co-scheduling a first cell and a second cell from the co-scheduled cell set. At step 950, the UE receives a reference value for the cell-specific parameter in the DCI format. At step 960, the UE determines a first value corresponding to a first PDSCH / PUSCH on the first cell for the cell-specific parameter based on the reference value and the adjustment parameter configured for the first cell. At step 970, the UE determines a second value corresponding to a second PDSCH / PUSCH on the second cell for the cell-specific parameter based on the reference value and the adjustment parameter configured for the second cell. At step 980, the UE receives the first and second PDSCHs or sends the first and second PUSCHs on the first co-scheduled cell and the second co-scheduled cell, respectively, based on the determined first and second values ​​of the cell-specific scheduling parameters.

[0393] In one example, for a given scheduling parameter or DCI field (such as MCS, APs, TCI state, SRI, TPMI, FDRA or TDRA, etc.), a first multi-cell mapping or table for a first co-scheduled cell set and a second multi-cell mapping for a second co-scheduled cell set may be provided to the UE. In one example, configuration of multiple multi-cell mappings is supported regardless of whether the first co-scheduled cell set and the second co-scheduled cell set share the same serving cell (i.e., whether the first serving cell belongs to both the first set and the second set). In another example, configuration of multiple multi-cell mappings is supported only when the first set and the second set do not share any serving cell (i.e., when there is no serving cell belonging to both the first set and the second set). In yet another example, when the first co-scheduled cell set and the second co-scheduled cell set share a serving cell (i.e., there is at least one serving cell belonging to both the first group and the second group), the UE can be configured with a single / shared multi-cell mapping for a given scheduling parameter or DCI field corresponding to the union of the first co-scheduled cell set and the second co-scheduled cell set. Therefore, when the UE detects a DCI format for multi-cell scheduling of a first set of co-scheduled cells, the corresponding DCI field in the DCI format indicates an index / row of a single / shared multi-cell mapping or table, which in turn indicates a plurality of parameter values ​​for a plurality of corresponding cells included in the first set of co-scheduled cells. In this example, the UE discards parameter values ​​indicated by the single / shared multi-cell mapping or table for the remaining serving cells that are not included in the first set of co-scheduled cells and belong only to the second set of co-scheduled cells.

[0394] In one example, the various methods described in the above embodiments may be combined. For example:

[0395] § The UE determines the value of the first cell common scheduling information parameter set from the corresponding cell common DCI field; and

[0396] § the UE determines values ​​of a second set of cell-specific scheduling information parameters based on a reinterpretation of a corresponding set of DCI fields with multi-cell mapping for each co-scheduled cell; and

[0397] § The UE determines the values ​​of the remaining scheduling information parameters for each co-scheduled cell according to predetermined values ​​in the specification or based on higher layer configuration.

[0398] In one example, the specification for system operation may support multiple methods from the various methods described in the above embodiments. For example, the UE may be configured for multiple methods of multi-cell scheduling and determine a method from the multiple methods based on, for example, the number of co-scheduled cells or measurements of reference signals associated with multiple PDSCH / PUSCHs.

[0399] In one example, a DCI format for multi-cell scheduling or any scheduling information block or DCI field for multi-cell scheduling may have a configurable size, ie, bit width.

[0400] In one embodiment, for a UE configured with a co-scheduled cell set, a set of "states" (or "code points") corresponding to a combination of cell sets from the co-scheduled cell set may be provided to the UE. Thus, the multi-cell scheduling DCI format may indicate UE operation on a scheduling parameter or DCI field by an indication of a state. The UE may receive a configuration of such a state to be applied jointly to a plurality of scheduling parameters or DCI fields, or a different set of states may be provided to the UE separately for each scheduling parameter or DCI field. Furthermore, in addition to a cell combination, a state may also relate to a parameter associated with a scheduling parameter or DCI field.

[0401] In one example, each "state" may correspond to a subset of a set of co-scheduled cells. For example, when a UE is configured with a set of co-scheduled cells such as {cell #1, cell #2, cell #3, cell #4}, the UE may be configured with state #1 corresponding to {cell #1, cell #2}, state #2 corresponding to {cell #3, cell #4}, and state #3 corresponding to {cell #1, cell #2, cell #4}. The specification for system operation may introduce a limit on the maximum number of configured "states" for each set of co-scheduled cells, such as 2 or 4 states, so that only 1 or 2 bits are required to indicate the state.

[0402] The concept of cell combination status can be used for various scheduling parameters or DCI fields, such as for indication of rate matching mode, or for triggering aperiodic ZP CSI-RS, etc. Such application is described in detail below.

[0403] In one embodiment, in a first implementation, for rate matching modes applicable to multiple co-scheduled PDSCHs, the field of the connection-individual rate matching indicator field in the multi-cell scheduling DCI format requires between 4 and 8 bits, depending on whether the serving cell from the co-scheduled cell set is configured with one or two rate matching mode groups, for example, one or two bits for the first co-scheduled cell, and one or two bits for the second co-scheduled cell, and so on.

[0404] For example, a multi-cell scheduling DCI format based on "state" may indicate a first state for rate matching mode group 1, and a second state for rate matching mode group 2. For example, for rate matching mode group 1, the DCI format includes a first state ID for indicating the first state and a second state ID for indicating the second state. For example, a DCI field value '01' for rate matching indicator 1 indicates state ID#1, and a DCI field value '10' indicates state ID#2, and a DCI field value '11' indicates state ID#3. For example, in one option, a DCI field value '00' for a rate matching indicator may indicate state ID#0, and in another option, may indicate no rate matching. A similar indication mechanism may be applied to rate matching mode group 2. Therefore, the DCI format may include a total of 2+2=4 bits for rate matching mode indication, wherein 2 MSBs indicate a state for rate matching mode group 1, and 2 LSBs indicate a state for rate matching mode group 2. In another example, the number of bits may be more than 2, such as 3 or 4 bits, to accommodate the configuration and indication of more states.

[0405] In another example, the UE may be configured with multiple states, such as up to 8 states, and a higher layer configuration (or MAC-CE command) may indicate a table of 3 (or 4) states for the purpose of rate matching mode groups. In this case, the UE interprets the DCI format field of rate matching indicator 1 as follows:

[0406] - The DCI format field "01" indicates the first state ID provided in the state table;

[0407] - DCI format field "10" indicates a second state ID provided in the state table;

[0408] - The DCI format field "11" indicates the third state ID provided in the state table.

[0409] The DCI field value '00' may be extended in a similar manner, for example, to indicate no rate matching, or to indicate the (zeroth or) fourth state ID provided in the state table. This approach may be beneficial, for example, when the configured state applies to multiple scheduling parameters or DCI fields, so that each scheduling parameter or DCI field may use a different selection of the configured state.

[0410] If the UE receives a PDSCH on a cell from a co-scheduled cell set and the cell is included in a state corresponding to the MSB or LSB of the rate matching indicator field, the UE determines that the REs corresponding to the configured resources in rateMatchPatternGroup1 or rateMatchPatternGroup2 are not available for PDSCHs from multiple co-scheduled PDSCHs.

[0411] In the above example, the size of the rate matching indicator field in the multi-cell DCI format can be fixed to 4 bits, i.e., 2 bits for the first state and 2 bits for the second state, regardless of the indication of the rate matching mode. For example, when the multi-cell scheduling DCI format indicates state #3 for rate matching mode group 1, and state #1 for rate matching mode group 2, then:

[0412] -PDSCH#1 on cell#1 performs rate matching around rate matching pattern group 1 and rate matching pattern group 2 configured for cell#1;

[0413] -PDSCH#2 on cell#2 performs rate matching around rate matching pattern group 1 and rate matching pattern group 2 configured for cell#2;

[0414] -PDSCH#3 on cell#3 is not rate matched, and

[0415] -PDSCH#4 on cell#4 is rate matched only around rate matching pattern group 1 configured for cell#4.

[0416] In one example, when all serving cells in the co-scheduled cell set are configured with only one rate matching pattern group, the multi-cell scheduling DCI format can include only one state (i.e., 2 bits) for the rate matching indicator field. Therefore, if the UE receives a PDSCH on a cell from the co-scheduled cell set and the cell is included in the state corresponding to the rate matching indicator field, the UE determines that the REs corresponding to the configured resources in rateMatchPatternGroup1 are not available for PDSCH reception from multiple co-scheduled PDSCHs.

[0417] In the above example, if the multi-cell scheduling DCI format includes a rate matching indicator field indicating state #2, then:

[0418] -PDSCH#1 on cell#1 is not rate matched, and

[0419] -PDSCH#2 on cell#2 is not rate matched, and

[0420] -PDSCH#3 on cell#3 is rate matched around rate matching mode group 1 configured for cell#3;

[0421] -PDSCH#4 on cell#4 is rate matched around rate matching mode group 1 configured for cell#4.

[0422] In one example, for the case of multi-cell scheduling on a co-scheduled cell set, the UE desires to be configured / indicated only a cell-specific (rather than a BWP-specific) rate matching pattern group.

[0423] In another example, for the case of multi-cell scheduling on a co-scheduled cell set, the UE may be configured / indicated a cell-specific or BWP-specific rate matching pattern group. In an alternative, the same cell combination state is configured regardless of the (active) DL BWP of the serving cell included in the cell combination associated with the state. For example, the UE determines the rate matching pattern group from the active DL BWP of the cell associated with the indicated state. For example, when the BWP-specific rate matching pattern group is not provided to the UE on the active DL BWP of the serving cell from the cell combination associated with the indicated state, the UE determines that there is no rate matching pattern group to be applied to the PDSCH (from the co-scheduled PDSCH) received in the active DL BWP of the serving cell.

[0424] In yet another example, the UE may configure a separate set of cell combination states in a BWP-specific manner. For example, a first set of states corresponding to a first BWP combination and a second set of states corresponding to a second BWP combination of the co-scheduled cell set may be provided to the UE.

[0425] In this document, the BWP combination of the co-scheduled cell set includes a first BWP for a first serving cell and a second BWP for a second serving cell, etc., where the first cell and the second cell, etc. are from the co-scheduled cell set. For example, for a co-scheduled cell set with four serving cells, some examples of BWP combinations may be as follows:

[0426] - For example, BWP combination #1 = {BWP #1@cell #1, BWP #1@cell #2, BWP #1@cell #3, BWP #1@cell #4},

[0427] - For example, BWP combination #2 = {BWP #2@cell #1, BWP #1@cell #2, BWP #2@cell #3, BWP #1@cell #4},

[0428] -For example, BWP combination #2 = {BWP #1@Cell #1, BWP #2@Cell #2, BWP #2@Cell #3, BWP #1@Cell #4}, etc.

[0429] In one example, the first and second options below may be extended so that the triggering state may be applied to multiple sets of co-scheduled cells, for example when:

[0430] - the first co-scheduled cell set is a subset of the second co-scheduled cell set, or

[0431] - When the first co-scheduled cell set and the second co-scheduled cell set have shared cell members, that is, there is at least one serving cell included by both the first set and the second set.

[0432] In one embodiment, in the second implementation, in order to trigger an aperiodic zero power CSI-RS resource set, a cell combination "state" may be configured to trigger an aperiodic zero power CSI-RS resource set that is considered unavailable for PDSCH reception of multiple co-scheduled PDSCHs. In this document, a state can correspond to only a cell combination, or can correspond to a combination of a pair of {aperiodic ZP CSI-RS resource set ID, serving cell ID}.

[0433] In a first option for the second implementation, the multi-cell scheduling DCI format can include multiple subfields corresponding to multiple non-periodic ZP CSI-RS resource sets configured in the BWP of each co-scheduled cell, wherein each subfield indicates a cell combination state. For example, the DCI format field for ZP CSI-RS triggering can include:

[0434] - a first subfield comprising an index of a first state indicating a first cell from a set of co-scheduled cells for which aperiodic ZP CSI-RS resource set ID#1 is triggered, and

[0435] - a second subfield comprising an index of a second state, the second state indicating a second cell from the set of co-scheduled cells for which aperiodic ZP CSI-RS resource set ID#2 is triggered, and

[0436] - A third subfield comprising an index of a third state, the third state indicating a third cell from the set of co-scheduled cells for which aperiodic ZP CSI-RS resource set ID#3 is triggered.

[0437] Therefore, the UE determines that REs indicated by resources within aperiodic ZP CSI-RS resource set IDs #1 / #2 / #3 are unavailable for the co-scheduled PDSCH corresponding to the serving cells included in the first / second / third states, respectively.

[0438] In a first alternative, the configuration / application of the state for triggering the aperiodic ZP CSI-RS resource sets may be "cell-specific" (rather than BWP-specific) such that the same state is configured / applied regardless of the active DL BWP of the serving cells included in the cell combination state. Note that the configuration of the aperiodic ZP CSI-RS resource sets is BWP-specific and the declaration of unavailable REs is based on the aperiodic ZP CSI-RS resource sets configured in the active DL BWP of each serving cell (which is included in the cell combination state). In one example, if:

[0439] -UE receives multi-cell scheduling DCI format, and

[0440] - the first (respectively, second / third) subfield of the ZP CSI-RS triggering field in the DCI format indicates a state;

[0441] - the cell combination associated with said state comprises a serving cell, and

[0442] - aperiodic ZP CSI-RS resource set #1 (respectively, #2 / #3) is not provided to the UE on the active DL BWP of the serving cell,

[0443] The UE does not trigger the aperiodic ZP CSI-RS resource set #1 (respectively, #2 / #3) on the active DL BPW of the serving cell. Therefore, the UE determines that the REs indicated by the resources within the aperiodic ZP CSI-RS resource set ID #1 (respectively, #2 / #3) are available for receiving the PDSCH (from the co-scheduled PDSCH) received on the active DL BWP of the serving cell.

[0444] In a second alternative, the configuration / application of the state for triggering the non-periodic ZP CSI-RS resource set may be BWP-specific, such that different states are configured / applied based on the active DL BWP of the serving cells included in the co-scheduled cell set. For example, a first set of trigger states is provided for a first BWP combination of a first cell combination, and a second set of trigger states is provided for a second BWP combination of the first cell combination or a second cell combination, and so on. BWP combinations are previously described in the present disclosure.

[0445] A third alternative may be based on cell-specific configuration of the states, while the UE may provide multiple different tables of selected states in a BWP-specific manner via higher layer configuration (or MAC-CE activation), as also described below.

[0446] In one example, the number of states included in the DCI format for triggering ZP CSI-RS can be based on the maximum allowed number of aperiodic ZP CSI-RS resource sets supported in the specification for system operation, such as 3 states corresponding to a maximum of 3 aperiodic ZP CSI-RS resource sets per BWP. Thus, when 2 bits are sufficient to indicate the configured cell combination "state", the size of the ZP CSI-RS trigger field in the multi-cell scheduling DCI format can be fixed to 3x2=6 bits.

[0447] In another example, the number of states included in the DCI format for triggering the ZP CSI-RS can be based on the maximum configured number of aperiodic ZP CSI-RS resource sets across all serving cells belonging to the set of co-scheduled cells. For example, if all co-scheduled cells are configured with at most one (respectively, at most two) aperiodic ZP CSI-RS resource sets per BWP, the DCI format can include only one state / subfield (respectively, only two states / subfields) to indicate the cell combination for which the corresponding aperiodic ZP CSI-RS resource set is triggered.

[0448] In one example, the UE may be configured with N cell combination states, such as up to 3 or up to 7 states, to indicate multiple cell combinations. Therefore, for the DCI field for ZP CSI-RS triggering, each state / subfield corresponding to each aperiodic ZP CSI-RS resource set includes bits, such as 2 or 3 bits. For example, when up to 3 cell combination states are configured, the first (respectively, second / third) subfield of the DCI field for ZP CSI-RS triggering can include:

[0449] - a value of '01', indicating state ID #1 corresponding to the first cell, or

[0450] - a value of "10" to indicate state ID #2 corresponding to the second cell, or

[0451] - a value of "11" indicating a state ID #3 corresponding to the third cell,

[0452] The set of cells for which co-scheduling of aperiodic ZP CSI-RS resource set ID#1 (respectively, ID#2 / ID#3) is triggered.

[0453] For example, the value of '00' of the first (respectively, second / third) subfield of the DCI field for ZP CSI-RS triggering can be reserved to indicate that the aperiodic ZP CSI-RS resource set ID#1 (respectively, ID#2 / ID#3) is not triggered for any serving cell from the set of co-scheduled cells.

[0454] In another example, when the UE is configured with several states (such as up to 8 or 16 states), a table of selected states (such as up to 3 or up to 7 sub-selected states) may be provided to the UE via higher layer configuration (or MAC-CE command) for the purpose of triggering aperiodic ZP CSI-RS resource sets. For example, when up to 3 cell combination states are configured, the first (respectively, second / third) subfield of the DCI field for ZP CSI-RS triggering can include:

[0455] - a value "01" indicating a first state ID provided in the table of selected states corresponding to the first cell, or

[0456] - a value of "10" indicating that a second state ID is provided in the table of selected states corresponding to the second cell, or

[0457] - a value "11" for indicating a third state ID provided in the table of selected states corresponding to a third cell,

[0458] The set of co-scheduled cells from which aperiodic ZP CSI-RS resource set ID#1 (respectively, ID#2 / ID#3) is triggered. As described above, the value "00" is used to indicate no triggering.

[0459] This approach may be beneficial, for example, when the first table of selected states is configured for a rate matching mode group, as described above, and the second table of selected states is configured for triggering an aperiodic ZP CSI-RS resource set.

[0460] For example, the method may also be beneficial when the selected states are associated with different BWP combinations, where the BWP combinations are previously described in the present disclosure. For example, a first table of selected states corresponding to a first BWP combination of a set of co-scheduled cells and a second table of selected states corresponding to a second BWP combination of the set of co-scheduled cells may be provided to the UE, and so on. Thus, when the active BWP corresponding to a serving cell in the set of co-scheduled cells coincides with the first BWP combination of the set of co-scheduled cells, the UE interprets the DCI field for ZP CSI-RS triggering based on the first table of selected states.

[0461] In a second option for the second implementation, the UE can be configured with a set of ZP CSI-RS triggering states, where each ZP CSI-RS triggering state corresponds to a set of pairs of (aperiodic ZP CSI-RS resource set ID, serving cell ID). In this document, the aperiodic ZP CSI-RS resource set is configured on the corresponding serving cell provided by the configured pair, and the serving cell belongs to a set of co-scheduled cells. Therefore, the multi-cell scheduling DCI format indicates a triggering state from the configured triggering state set. Note that in the second option, the DCI format field for ZP CSI-RS triggering does not have a separate subfield as considered in the first option, because the information of the aperiodic ZP CSI-RS resource set is provided by the triggering state configuration.

[0462] For example, trigger states may include:

[0463] - a first aperiodic ZP CSI-RS resource set on a first serving cell, and

[0464] - A second aperiodic ZP CSI-RS resource set on a second serving cell, and so on,

[0465] The first serving cell and the second serving cell belong to the co-scheduled cell set. For example, the trigger state may be in the form of {(aperiodic ZP CSI-RS resource set ID#2@cell#1), (aperiodic ZP CSI-RS resource set ID#3@cell#2), (aperiodic ZP CSI-RS resource set ID#3@cell#3)}.

[0466] In one example, the configuration of the trigger state may be cell-specific, and the same set of trigger states applies to all BWPs of the corresponding serving cell from the co-scheduled cell set. In another example, the configuration of the trigger state may be BWP-specific. For example, a separate configuration of the trigger state is provided for each BWP or each BWP combination, where BWP combinations are described earlier in this disclosure.

[0467] In one example, the specification for system operation may introduce a limit on the maximum number of N-1 trigger states (e.g., where N=4 or 8 or 16 trigger states) for a set of co-scheduled cells or a BWP combination of co-scheduled cells. Thus, the DCI field for ZP CSI-RS triggering can have bits, for example, 2 or 3 or 4 bits. For example, a first value of the ZP CSI-RS trigger field (such as '01' (or '001')) indicates a first trigger state (i.e., a first list of (resource set ID, cell ID) pairs), and a second value (such as '10' (or '010')) indicates a second trigger state (i.e., a second list of (resource set ID, cell ID) pairs), and so on.

[0468] In one example, the value of '00' (or '000') of the ZP CSI-RS triggering field can be reserved to indicate that the aperiodic ZP CSI-RS resource set is not triggered on any co-scheduled PDSCH / cell.

[0469] In one example, the bit width of the DCI field for ZP CSI-RS triggering can be reduced by reducing the number of states corresponding to ZP CSI-RS triggering. For example, the (new) configuration of ZP CSI-RS for multi-cell scheduling can be a subset of the ZP CSI-RS configuration for single-cell scheduling. For example, the ZP CSI-RS states that can be triggered by the multi-cell scheduling DCI format can be a subset of the ZP CSI-RS states that can be triggered by the single-cell scheduling DCI format.

[0470] In one example, the first and second methods described above may be used for activation of a semi-persistent ZP CSI-RS resource set (such as by a MAC-CE command). For example, the MAC-CE command may be able to activate multiple semi-persistent ZP CSI-RS resource sets on multiple serving cells from a set of co-scheduled cells using a cell combination state or a multi-cell trigger state.

[0471] In one example, the first and second options below may be extended so that the triggering state may be applied to multiple sets of co-scheduled cells, for example when:

[0472] The first co-scheduled cell set is a subset of the second co-scheduled cell set, or

[0473] When the first co-scheduled cell set and the second co-scheduled cell set have shared cell members, that is, there is at least one serving cell included by both the first set and the second set.

[0474] The above flow charts illustrate example methods that can be implemented according to the principles of the present disclosure, and various changes can be made to the methods shown in the flow charts herein. For example, although shown as a series of steps, the various steps in each figure can overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, a step can be omitted or replaced by another step.

[0475] Although the drawings show different examples of user equipment, various changes may be made to the drawings. For example, the user equipment may include any number of each component in any suitable arrangement. Generally, the drawings do not limit the scope of the present disclosure to any particular configuration. In addition, although the drawings show operating environments in which various user equipment features disclosed in this patent document may be used, these features may be used in any other suitable system.

[0476] Although the present disclosure has been described with exemplary embodiments, various changes and modifications may be suggested to those skilled in the art. The present disclosure is intended to cover these changes and modifications that fall within the scope of the appended claims. The description in this application should not be interpreted as implying that any particular element, step or function is an essential element that must be included in the scope of the claims. The scope of the patent subject matter is defined by the claims.

Claims

1. A method performed by a user equipment (UE), include: receiving first information of a cell set; identifying a first time domain resource allocation (TDRA) table having a one-to-one mapping with cells in the set of cells, wherein a row of the first TDRA table from the first TDRA table indicates time resources for reception of a physical downlink shared channel (PDSCH) on the cells in the set of cells; receiving second information of a second TDRA table for reception of a PDSCH on a cell in the set of cells; The Physical Downlink Control Channel (PDCCH) is received on the scheduling cell, where: PDCCH provides the downlink control information (DCI) format, The DCI format schedules the reception of the first PDSCH on the first cell in the cell set, The DCI format includes a TDRA field indicating a first row of a second TDRA table, The first row includes a first entry that has a one-to-one mapping with a first cell, and The entry from the first entry indicates a row from the first TDRA table; determining, based on the first entry of the first row of the second TDRA table respectively, a first time resource for receiving a first PDSCH on the first cell; and A first PDSCH is received on a first cell in a first time resource respectively.

2. The method according to claim 1, further comprising: include: Sending an indication of the maximum number of cell sets scheduled from the scheduling cell, where: The DCI format includes a field indicating a cell set, The field consists of ceiling(log2(N_set)) bits, and N_set is the number of cell sets scheduled from the scheduling cell and is not greater than the maximum number of cell sets; and Receive third information of N_cell_combo cell combinations from the cell set, wherein: The first cell corresponds to the first cell combination from the number N_cell_combo cell combinations, The DCI format includes a field indicating a first cell combination, and The field consists of ceiling(log2(N_cell_combo)) bits.

3. The method according to claim 1, further comprising: include: receiving fourth information indicating parameters associated with a set of aperiodic zero power channel state information reference signal (ZP CSI-RS) resources on each cell from the set of cells; The fifth information of the receiving table, wherein: The DCI format includes a field indicating a row of a table including an entry having a one-to-one mapping with the first cell, and a value of an entry from the entries indicating an aperiodic ZP CSI-RS resource set from an aperiodic ZP CSI-RS resource set on a cell from the first cell; and determining, based on the entries of the rows of the table, first parameters for a first aperiodic ZP-CSI RS resource set, Receiving the first PDSCH further includes receiving the first PDSCH based on a first parameter.

4. The method according to claim 1, further comprising: include: receiving third information of a bandwidth part (BWP) for each cell from the set of cells; Identifying a BWP index of a corresponding first BWP of the first cell based on a BWP indicator field in the DCI format, Receiving the first PDSCH also includes receiving the first PDSCH on the corresponding first BWP.

5. The method according to claim 1, further comprising: include: receiving third information of a plurality of cell combinations from the cell set; The bit width of the fields in the DCI format is determined as bits, where: The field is associated with the transport block (TB) received for the PDSCH on a combination of cells from the set of cells, and is the maximum bit width of the field over multiple cell combinations; from bits, wherein M is a bit width corresponding to a TB received by the PDSCH on the first cell; and throw away The last of the bits ( -M) bits, The field is one of a Redundancy Version (RV) field, a New Data Indicator (NDI) field, and a Modulation and Coding Scheme (MCS) field.

6. A user equipment (UE), include: A transceiver, and a processor, wherein the processor is configured to: receiving first information of a cell set, identifying a first time domain resource allocation (TDRA) table having a one-to-one mapping with cells in the set of cells, wherein a row of the first TDRA table from the first TDRA table indicates a time resource for reception of a physical downlink shared channel (PDSCH) on the cells in the set of cells, receiving second information of a second TDRA table for reception of a PDSCH on a cell in the set of cells, The Physical Downlink Control Channel (PDCCH) is received on the scheduling cell, where: PDCCH provides the downlink control information (DCI) format, The DCI format schedules the reception of the first PDSCH on the first cell in the cell set, The DCI format includes a TDRA field indicating a first row of a second TDRA table, The first row includes a first entry having a one-to-one mapping with a first cell, The entry from the first entry indicates a row from the first TDRA table, Determine, based on the first entry of the first row of the second TDRA table, a first time resource for receiving a first PDSCH on the first cell; A first PDSCH is received on a first cell in a first time resource respectively.

7. The UE according to claim 6, in: The processor is further configured to send an indication of a maximum number of the set of cells to be scheduled from the scheduling cell, The DCI format includes a field indicating a set of cells. The field consists of ceiling(log2(N_set)) bits, and N_set is the number of cell sets scheduled from the scheduling cell and is not greater than the maximum number of cell sets, and in: The processor is further configured to receive third information of a number N_cell_combo of cell combinations from the cell set, The first cell corresponds to the first cell combination from the number N_cell_combo cell combinations, The DCI format includes a field indicating a first cell combination, and The field consists of ceiling(log2(N_cell_combo)) bits.

8. The UE according to claim 6, in: The processor is also configured to receive: fourth information indicating parameters associated with a non-periodic zero power channel state information reference signal (ZP CSI-RS) resource set on each cell from the set of cells, The fifth information of the table, where: The DCI format includes a field indicating a row of a table including an entry having a one-to-one mapping with the first cell, a value of an entry from the entries indicating an aperiodic ZP CSI-RS resource set from an aperiodic ZP CSI-RS resource set on a cell from the first cell, Determining, based on the entries of the rows of the table, first parameters for a first aperiodic ZP-CSI RS resource set; A first PDSCH is received based on the first parameter.

9. A base station, include: Transceiver; and The processor is configured as: Send the first information of the cell set, identifying a first time domain resource allocation (TDRA) table having a one-to-one mapping with cells in the set of cells, wherein a row of the first TDRA table from the first TDRA table indicates time resources for transmission of a physical downlink shared channel (PDSCH) on the cells in the set of cells, sending second information of a second TDRA table for transmission of a PDSCH on a cell in the cell set, The Physical Downlink Control Channel (PDCCH) is sent on the scheduling cell, where: PDCCH provides the downlink control information (DCI) format, The DCI format schedules the transmission of the first PDSCH on the first cell in the cell set respectively. The DCI format includes a TDRA field indicating a first row of a second TDRA table, The first row includes a first entry that has a one-to-one mapping with a first cell, and The entry from the first entry indicates a row from the first TDRA table, Determine, based on the first entry of the first row of the second TDRA table, a first time resource for transmission of a first PDSCH on the first cell; The first PDSCH is sent on the first cell in the first time resource respectively.

10. The base station according to claim 9, in: The processor is further configured to receive an indication of a maximum number of the set of cells to be scheduled from the scheduling cell, The DCI format includes a field indicating a cell set, The field consists of ceiling(log2(N_set)) bits, N_set is the number of cell sets scheduled from the scheduling cell and is not greater than the maximum number of cell sets, and in: The processor is further configured to send third information of a number N_cell_combo of cell combinations from the cell set, The first cell corresponds to the first cell combination from the number N_cell_combo cell combinations, The DCI format includes a field indicating a first cell combination, and The field consists of ceiling(log2(N_cell_combo)) bits.

11. The base station according to claim 9, in: The processor is also configured to send: fourth information indicating parameters associated with a set of aperiodic zero power channel state information reference signal (ZP CSI-RS) resources on each cell from the set of cells, and The fifth information of the table is The DCI format includes a field indicating a row of a table including an entry having a one-to-one mapping with the first cell, a value of an entry from the entries indicating an aperiodic ZP CSI-RS resource set from an aperiodic ZP CSI-RS resource set on a cell from the first cell, The processor is further configured to determine, based on the entry of the first row of the table, a first parameter for a first aperiodic ZP-CSI RS resource set; The processor is further configured to send a first PDSCH based on the first parameter.

12. The base station according to claim 9, in, The processor is also configured to: transmitting third information of a bandwidth part (BWP) of each cell from the set of cells, the BWP indicator field in the DCI format indicating a BWP index of a corresponding first BWP of a first cell, and The first PDSCH is sent on the corresponding first BWP.

13. The base station according to claim 9, in, The processor is also configured to: sending third information of a plurality of cell combinations from the cell set, The bit width of the fields in the DCI format is determined as bits, where the field is associated with a transport block (TB) for a PDSCH transmission on a combination of cells from a set of cells, and is the maximum bit width of the field over multiple cell combinations, from Determine the first M bits from the bits, where M is the bit width corresponding to the TB transmitted by the PDSCH on the first cell; throw away The last of the bits ( -M) bits; and The field is one of a Redundancy Version (RV) field, a New Data Indicator (NDI) field, and a Modulation and Coding Scheme (MCS) field.

14. A method performed by a base station, include: Sending first information of a cell set; identifying a first time domain resource allocation (TDRA) table having a one-to-one mapping with cells in the set of cells, wherein a row of the first TDRA table from the first TDRA table indicates time resources for transmission of a physical downlink shared channel (PDSCH) on the cells in the set of cells; Sending second information of a second TDRA table for transmission of a PDSCH on a cell in the cell set; The Physical Downlink Control Channel (PDCCH) is sent on the scheduling cell, where: PDCCH provides the downlink control information (DCI) format, The DCI format schedules the transmission of the first PDSCH on the first cell in the cell set respectively. The DCI format includes a TDRA field indicating a first row of a second TDRA table, The first row includes a first entry that has a one-to-one mapping with a first cell, and The entry from the first entry indicates a row from the first TDRA table, determining, based on the first entry of the first row of the second TDRA table respectively, a first time resource for transmission of a first PDSCH on the first cell; and The first PDSCH is sent on the first cell in the first time resource respectively.

15. The method according to claim 14, further comprising: include: Receiving an indication of a maximum number of a set of cells to be scheduled from a scheduling cell, wherein: The DCI format includes a field indicating a set of cells. The field consists of ceiling(log2(N_set)) bits, and N_set is the number of cell sets scheduled from the scheduling cell and is not greater than the maximum number of cell sets.

Citation Information

Cited By

  • Frequency-domain resource configuration method and apparatus, and terminal, network-side device and readable storage medium

    WO2026119016A1