Method and apparatus for enabling single DCI scheduling of multiple cells

Abstract

The invention relates to a method and apparatus for implementing single DCI scheduling of multiple cells. A method implemented in a WTRU includes receiving a first message including first configuration information indicating a fixed size format of DCI and a plurality of cell identifiers, where each of the plurality of cell identifiers is associated with a cell combination of a plurality of cells and includes second configuration information indicating SRS resources associated with the plurality of cells, the sending module is used for sending SRS to a cell subset of a plurality of cells; receiving DCI having first information indicating a cell identifier of the plurality of cell identifiers in a fixed size format, and including second information indicating a cell subset of the plurality of cells associated with the SRS resource; determining a cell combination of the plurality of cells associated with a cell identifier based on the received DCI; and transmitting the communication via the cell combination, and transmitting the SRS to the subset of cells.

Description

[0001] This application is a divisional application of a Chinese invention patent application with an application date of February 10, 2023, application number 202380023619.1, and invention name “Method and device for implementing single downlink control information (DCI) scheduling for multiple cells”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 309,100 filed on February 11, 2022, U.S. Provisional Patent Application No. 63 / 327,452 filed on April 5, 2022, and U.S. Provisional Patent Application No. 63 / 410,435 filed on September 27, 2022, each of which is incorporated herein by reference. Technical Field

[0004] The present disclosure relates to methods and apparatus for implementing single DCI scheduling for multiple cells. Background Art

[0005] The present disclosure relates to methods and apparatus for implementing single DCI scheduling of multiple cells.Supporting scheduling of multiple cells with a single DCI may have the potential to reduce overhead, but at the same time may result in a large size DCI if all bit fields are multiplied by the number of scheduled cells.

[0006] A single DCI needs to be designed to schedule multiple cells while keeping the overhead on the control channel low. Summary of the invention

[0007] This document provides a method and apparatus for implementing single DCI scheduling for multiple cells.

[0008] In one embodiment, a method implemented in a wireless transmit / receive unit (WTRU) may include receiving configuration information including a plurality of identifiers, each of the plurality of identifiers being associated with a cell set of a plurality of cell sets. The method may also include receiving downlink control information DCI, the downlink control information being masked with a first identifier included in the received configuration information, wherein the first identifier is used to expose the DCI during said reception of the DCI. The method may also include determining a cell set associated with the DCI, the cell set including at least a first cell and a second cell; and communicating via the cell set including the at least first cell and the second cell using an information element associated with the received DCI.

[0009] The information element may indicate a first communication parameter associated with the first cell and a second communication parameter associated with the second cell.

[0010] The received DCI may include a modulation and coding scheme (MCS) bit field. The method may also include determining an MCS value for the first communication parameter and an MCS value for the second communication parameter based on the MCS bit field. The MCS bit field may point to at least one MCS value of an MCS table of the WTRU.

[0011] The first and second communication parameters may include a first modulation and coding scheme and a second modulation and coding scheme, respectively, for communicating via the respective first and second cells.

[0012] An identifier of the plurality of identifiers may be used to scramble a cyclic redundancy check of the DCI.

[0013] The plurality of identifiers may be a plurality of Radio Network Temporary Identifiers RNTIs.

[0014] The WTRU configuration of the association of each of the plurality of identifiers with a cell set of the plurality of cell sets may be a semi-static configuration.The WTRU may be semi-statically configured using radio resource control signaling.

[0015] In one embodiment, a method implemented in a wireless transmit / receive unit (WTRU) may include receiving, by the WTRU, a single downlink control information (DCI). The method may also include determining, by the WTRU, scheduling of multiple cells based on the single DCI; and performing wireless communication by the WTRU based on the determination.

[0016] Determining the scheduling may include determining multiple cells based on the cell on which the WTRU receives a single DCI. Determining the scheduling may include determining multiple cells based on a radio network temporary identifier (RNTI) of a cyclic redundancy check (CRC) used to scramble the single DCI. Determining the scheduling may include determining multiple cells based on the format of the single DCI. Determining the scheduling may include determining multiple cells based on a bit field identifying one or more target cells. Determining the scheduling may include determining multiple cells based on a DCI / medium access control-control element (MAC) CE indicating scheduling information and one or more target cells. Determining the scheduling may include determining the number of scheduled cells using a counter downlink assignment index (DAI) in a single DCI and a total (DAI) value in a single DCI.

[0017] The difference between the counter DAI and the total DAI value in a single DCI may indicate the number of scheduled cells.

[0018] Determining the scheduling may include determining to transmit or receive at least one of one or more channel state information reference signals (CSI-RS) or one or more sounding reference signals (SRS) on one or more cells among the plurality of cells based on at least one bit contained in the single DCI.

[0019] The number of blind decoding attempts for a single DCI scheduling multiple cells may depend on the number of target cells for the DCI.

[0020] If the bit field is not present in a single DCI, the WTRU may assume a semi-static configuration for a certain transmission parameter.

[0021] The method may also include receiving, by the WTRU, separate DCIs from the single DCI; and determining, by the WTRU, power control parameters for the plurality of cells based on the separate DCIs, wherein performing wireless communications is further based on the determined power control parameters.

[0022] The method may also include determining, by the WTRU, a target cell based on the single DCI; and determining, by the WTRU, transmission parameters based on the determined target cell, wherein performing wireless communication includes exchanging information, by the WTRU, with the determined target cell using the determined transmission parameters.

[0023] The WTRU may be configured with a bit field set that is always present in a single DCI and another bit field set that is associated with a target cell. The bit field set that is always present may not be dependent on the target cell. Multiple bit field sets may be configured and associated with a target cell.

[0024] Depending on the determined target cell, the WTRU may determine that at least one of the multiple sets of bit fields is present in a single DCI. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] A more detailed understanding can be obtained from the following detailed description, which is given by way of example in conjunction with its accompanying drawings. As with the detailed description, the figures in such drawings are exemplary. Therefore, the drawings and specific embodiments should not be considered limiting, and other equally effective examples are possible and contemplated. In addition, like reference numerals ("ref.") in the accompanying drawings ("Figures") indicate similar elements, and wherein:

[0026] Figure 1A is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented;

[0027] Figure 1B It is shown that according to one embodiment, Figure 1A A system diagram of an example wireless transmit / receive unit (WTRU) for use within the illustrated communication system;

[0028] Figure 1C It is shown that according to one embodiment, Figure 1A a system diagram of an example Radio Access Network (RAN) and an example Core Network (CN) used within the illustrated communication system;

[0029] Figure 1D It is shown that according to one embodiment, Figure 1A A system diagram of another example RAN and another example CN used within the illustrated communication system;

[0030] Figure 2A is a flow chart illustrating a method for implementing single downlink control information (DCI) scheduling of multiple cells;

[0031] Figure 2B is a flow chart illustrating a method for implementing individual DCI power control for multiple cells;

[0032] Figure 3 is a diagram depicting a single DCI schedule for multiple cells; and

[0033] Figure 4 is a flow chart illustrating a WTRU determination of transmission parameters based on a determined target cell.

[0034] Figure 5 is a flow chart illustrating a method implemented in a WTRU for implementing single downlink control information scheduling for multiple cells. DETAILED DESCRIPTION

[0035] In the following detailed description, many specific details are listed to provide a thorough understanding of the embodiments and / or examples disclosed herein. However, it should be understood that such embodiments and examples can be practiced without some or all of the specific details listed herein. In other cases, well-known methods, processes, components, and circuits are not described in detail to avoid blurring the following description. In addition, embodiments and examples not specifically described herein can be practiced in place of embodiments and other examples explicitly, implicitly, and / or inherently described, disclosed, or otherwise provided (collectively referred to as "provided") herein, or practiced in combination with these embodiments and examples.

[0036] Figure 1A1 is a diagram illustrating an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through sharing of system resources (including wireless bandwidth). For example, the communication system 100 may employ one or more channel access methods such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero tail unique word DFT spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), etc.

[0037] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, Internet 110 and other networks 112, but it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to send and / or receive wireless signals and may include user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated process chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0038] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device that is configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an eNode B, a Home Node B, a Home eNode B, a gNB, an NR Node B, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it should be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0039] The base station 114a may be part of the RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, etc. The base station 114a and / or the base station 114b may be configured to send and / or receive wireless signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be in a licensed spectrum, an unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage of wireless services to a specific geographic area, which may be relatively fixed or may change over time. The cell may be further divided into cell sectors. For example, a cell associated with the base station 114a may be divided into three sectors. Therefore, in one embodiment, the base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In one embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to send and / or receive signals in a desired spatial direction.

[0040] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0041] More specifically, as noted above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 116. WCDMA may include communication protocols such as High Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed ​​Downlink Packet Access (HSDPA) and / or High Speed ​​Uplink Packet Access (HSUPA).

[0042] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA) that may establish the air interface 116 using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-A Pro).

[0043] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access, which may establish the air interface 116 using New Radio (NR).

[0044] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may together implement LTE radio access and NR radio access, for example using dual connectivity (DC) principles. Thus, the air interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions transmitted to / from multiple types of base stations (e.g., eNBs and gNBs).

[0045] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0046] Figure 1A The base station 114b in the example may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a picocell base station or a femtocell base station. As Figure 1A As shown, base station 114b may have a direct connection to Internet 110. Therefore, base station 114b may not need to access Internet 110 via CN 106 / 115.

[0047] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not described in detail in the text, the CN 106 / 115 may be configured to provide voice, data, applications and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Figure 1AAlthough not shown in the figure, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may utilize NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) that employs GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0048] The CN 106 / 115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired communication networks and / or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 / 113 or a different RAT.

[0049] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks via different wireless links). Figure 1A The illustrated WTRU 102c may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0050] Figure 1B is a system diagram illustrating an example WTRU 102. Figure 1B As shown, the WTRU 102 may include, among other things, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0051] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal decoding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0052] The send / receive element 122 may be configured to send a signal to a base station (e.g., base station 114a) or receive a signal from the base station via an air interface 116. For example, in one embodiment, the send / receive element 122 may be an antenna configured to send and / or receive an RF signal. In one embodiment, the send / receive element 122 may be a transmitter / detector configured to send and / or receive, for example, an IR, UV, or visible light signal. In another embodiment, the send / receive element 122 may be configured to send and / or receive both an RF signal and an optical signal. It should be understood that the send / receive element 122 may be configured to send and / or receive any combination of wireless signals.

[0053] Although the transmit / receive element 122 Figure 1B 102 as a single element, but the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0054] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and to demodulate signals received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. For example, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

[0055] The processor 118 of the WTRU 102 may be coupled to and may receive user input data from a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from and store data in any type of suitable memory, such as a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from and store data in a memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0056] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control power to the other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.

[0057] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method while remaining consistent with an embodiment.

[0058] The processor 118 may also be coupled to other peripherals 138, which may include one or more software modules and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth® module, frequency modulation (FM) radio unit, digital music player, media player, video game player module, Internet browser, virtual reality and / or augmented reality (VR / AR) device, activity tracker, etc. Peripheral device 138 may include one or more sensors, which may be one or more of the following: a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

[0059] The WTRU 102 may include a full-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with specific subframes for both uplink (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit 139 for reducing and / or substantially eliminating self-interference via signal processing performed by hardware (e.g., a choke) or via a processor (e.g., a separate processor (not shown) or via the processor 118). In one embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with specific subframes for both uplink (e.g., for transmission) or downlink (e.g., for reception)) may be concurrent and / or simultaneous.

[0060] Figure 1C 1 is a system diagram illustrating the RAN 104 and the CN 106 according to one embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0061] The RAN 104 may include evolved Node-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of evolved Node-Bs while being consistent with an embodiment. The evolved Node-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the evolved Node-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the evolved Node-B 160a, for example, may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.

[0062] Each of the evolved Node Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in uplink (UL) and / or downlink (DL), etc. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with one another via an X2 interface.

[0063] Figure 1C The illustrated CN 106 may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements is depicted as being part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0064] The MME 162 may be connected to each of the evolved Node-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, etc. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0065] The SGW 164 may be connected to each of the evolved Node-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring the user plane during inter-evolved Node-B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, and the like.

[0066] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0067] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include or may be in communication with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired networks and / or wireless networks owned and / or operated by other service providers.

[0068] Although the WTRU Figures 1A to 1D Although described as wireless terminals, it is contemplated that in certain representative embodiments such terminals may (eg, temporarily or permanently) employ a wired communications interface with a communications network.

[0069] In a representative embodiment, the other network 112 may be a WLAN.

[0070] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have access or an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic to and / or carries traffic away from the BSS. Traffic originating from outside the BSS and directed to the STA may arrive through the AP and may be delivered to the STA. Traffic originating from the STA and directed to a destination outside the BSS may be transmitted to the AP to be delivered to the corresponding destination. Traffic between STAs within the BSS may be transmitted through the AP, for example, where the source STA may transmit traffic to the AP, and the AP may deliver the traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. Point-to-point traffic may be transmitted between the source STA and the destination STA (e.g., directly between them) using direct link establishment (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunnel DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs within or using the IBSS (eg, all STAs in the STA) may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad-hoc" communication mode.

[0071] When using the 802.11ac infrastructure operating mode or a similar operating mode, the AP may send a beacon on a fixed channel (such as a primary channel). The primary channel may be a fixed width (e.g., a 20MHz wide bandwidth) or a width dynamically set via signaling. The primary channel may be an operating channel of the BSS and may be used by the STA to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access with collision avoidance (CSMA / CA) may be implemented, for example, in an 802.11 system. For CSMA / CA, a STA (e.g., each STA) (including the AP) may sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a specific STA, the specific STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0072] High throughput (HT) STAs may communicate using a 40 MHz wide channel, for example, via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0073] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz channels and / or 80MHz channels can be formed by combining continuous 20MHz channels. A 160MHz channel can be formed by combining 8 continuous 20MHz channels, or by combining two non-contiguous 80MHz channels (this can be referred to as an 80+80 configuration). For the 80+80 configuration, after channel coding, the data can pass through a segment parser that can divide the data into two streams. Each stream can be processed by inverse fast Fourier transform (IFFT) and time domain processing separately. These streams can be mapped to two 80MHz channels, and data can be sent by sending STA. At the receiver of the receiving STA, the above-mentioned operations for the 80+80 configuration can be reversed, and the combined data can be transmitted to the medium access control (MAC).

[0074] 802.11af and 802.11ah support operating modes below 1GHz. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah relative to those used in 802.11n and 802.11ac. 802.11af supports 5MHz, 10MHz, and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support meter type control / machine type communications, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support for (e.g., only support for) certain bandwidths and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., to maintain very long battery life).

[0075] WLAN systems that can support multiple channels and channel bandwidths (such as 802.11n, 802.11ac, 802.11af, and 802.11ah) include channels that can be designated as primary channels. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA (which supports the minimum bandwidth operating mode) from all STAs operating in the BSS. In the example of 802.11ah, for STAs (e.g., MTC-type devices) that support (e.g., only support) a 1MHz mode, the primary channel may be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy, for example, because a STA (which only supports a 1MHz operating mode) is transmitting to the AP, the entire available frequency band may be considered busy even if most of the frequency bands remain idle and may be available.

[0076] In the United States, the available frequency band for 802.11ah is 902MHz to 928MHz. In South Korea, the available frequency band is 917.5MHz to 923.5MHz. In Japan, the available frequency band is 916.5MHz to 927.5MHz. The total bandwidth available for 802.11ah is 6MHz to 26MHz, depending on the country code.

[0077] Figure 1D1 is a system diagram illustrating the RAN 113 and the CN 115 according to one embodiment. As noted above, the RAN 113 may employ NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.

[0078] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b may utilize beamforming to send signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a may, for example, use multiple antennas to send wireless signals to and / or receive wireless signals from the WTRU 102a. In one embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on an unlicensed spectrum, while the remaining component carriers may be on a licensed spectrum. In one embodiment, the gNBs 180a, 180b, 180c may implement coordinated multi-point (CoMP) technology. For example, the WTRU 102a may receive coordinated transmissions from the gNB 180a and gNB 180b (and / or gNB 180c).

[0079] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with scalable parameter sets. For example, OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or Transmission Time Intervals (TTIs) of varying or scalable lengths (e.g., containing varying numbers of OFDM symbols and / or varying absolute time lengths over time).

[0080] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c while also not accessing other RANs (e.g., such as the eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate / connect with the gNB 180a, 180b, 180c while also communicating / connecting with another RAN, such as the eNode-B 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNode-B 160a, 160b, 160c may act as a mobility anchor for the WTRUs 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.

[0081] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in uplink (UL) and / or downlink (DL), support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards a user plane function (UPF) 184a, 184b, routing of control plane information towards an access and mobility management function (AMF) 182a, 182b, etc. As shown in FIG. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.

[0082] Figure 1DThe illustrated CN 115 may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and possible data networks (DNs) 185a, 185b. Although each of the foregoing elements is depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0083] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, support of network slicing (e.g., handling of different PDU sessions with different requirements), selecting a specific SMF 183a, 183b, management of registration areas, termination of NAS signaling, mobility management, etc. The AMF 182a, 182b may use network slicing to customize CN support for the WTRU 102a, 102b, 102c based on the type of service utilized by the WTRU 102a, 102b, 102c. For example, different network slices may be established for different use cases, such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced mobile broadband (eMBB) access, services for machine type communication (MTC) access, etc. The AMF 182 a , 182 b may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro and / or non-3GPP access technologies, such as WiFi.

[0084] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 115 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 115 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b, and configure traffic routing through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

[0085] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, etc.

[0086] The CN 115 may facilitate communication with other networks. For example, the CN 115 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired networks and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to local data networks (DNs) 185a, 185b via the UPFs 184a, 184b via the N3 interfaces to the UPFs 184a, 184b and the N6 interfaces between the UPFs 184a, 184b and the DNs 185a, 185b.

[0087] Given that Figures 1A to 1D as well as Figures 1A to 1D Corresponding to the description of the present invention, one or more or all of the functions described herein with reference to one or more of the following may be performed by one or more simulation devices (not shown): WTRU102a to 102d, base station 114a to 114b, evolved Node B 160a to 160c, MME 162, SGW 164, PGW 166, gNB180a to 180c, AMF 182a to 182b, UPF 184a to 184b, SMF 183a to 183b, DN 185a to 185b and / or any other device described herein. The simulation device may be one or more devices configured to simulate one or more or all of the functions described herein. For example, the simulation device may be used to test other devices and / or simulate network and / or WTRU functions.

[0088] The simulation device may be designed to implement one or more tests of other devices in a laboratory environment and / or in an operator network environment. For example, one or more simulation devices may perform one or more functions or all functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network in order to test other devices within the communication network. One or more simulation devices may perform one or more functions or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The simulation device may be directly coupled to another device for testing purposes and / or may use over-the-air wireless communications to perform testing.

[0089] One or more simulation devices may perform one or more (including all) functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device may be used in a test lab and / or a test scenario in a non-deployed (e.g., testing) wired and / or wireless communication network to enable testing of one or more components. One or more simulation devices may be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (e.g., which may include one or more antennas) may be used by the simulation device to send and / or receive data.

[0090] In the following description, a method and apparatus for implementing a single DCI scheduling of multiple cells are proposed. For the case of multiple narrow carriers corresponding to a segmented spectrum, it is inefficient to use multiple DCIs sent in each narrow carrier in the narrow carrier. In order to enhance the control channel overhead in the case of segmented spectrum, NR Rel-18 will support a single DCI for scheduling multiple cells. Different cells may have different configurations and characteristics associated therewith. For example, there is a scenario where multiple cells exist, some of which operate under licensed operation and others operate under unlicensed operation. For unlicensed operation, a DCI for uplink transmission is used to indicate the channel access type, while for licensed operation, channel access type information is not required. Scheduling multiple cells with different characteristics using the same DCI will increase the high overhead in the DCI. The present disclosure describes in detail a technique for designing DCI to schedule multiple cells while maintaining low overhead for scheduling DCI. The WTRU may be configured with a DCI format that can schedule one or more cells. The WTRU may first determine a subset of the scheduled cells and then interpret the DCI accordingly. Another technique described herein involves a single DCI triggering the WTRU to send / receive configured grants / DL SPS on a first subset of cells and to send / receive dynamic grants on a second subset of cells.

[0091] For NR low FR1 bands (lower than 7.125 GHz), the available spectrum blocks tend to be more segmented and dispersed, and the bandwidth is narrower. In existing wireless systems, a single downlink control channel is used to schedule transmission (PUSCH) or reception (PDSCH) in a single carrier. For the case of multiple narrow carriers corresponding to the segmented spectrum, it is inefficient to use multiple DCIs sent in each of the narrow carriers (i.e., inefficient control channel overhead). In order to ensure that the segmented spectrum is utilized in a spectrum efficient manner, it is proposed to increase the control channel overhead in this case. A work item has been agreed in 3GPP to specify one or more solutions for multi-cell PUSCH / PDSCH scheduling (one PDSCH / PUSCH per cell) with a single DCI.

[0092] On the one hand, supporting scheduling of multiple cells with a single DCI has the potential to reduce overhead by using a single DCI for more than one cell (rather than one DCI per cell). On the other hand, a single DCI scheduling of multiple cells can result in a very large DCI if all bit fields are multiplied by the number of scheduled cells. Increasing the DCI size by adding all possible bit fields for each scheduled cell would defeat the goal of reducing control channel overhead. It may even require more control channel overhead to achieve a specific reliability. In fact, a large DCI size may require a large number of control channel elements (CCEs) and higher aggregation levels to meet specific reliability requirements. Problems that arise in this case include how to design a single DCI to schedule multiple cells while keeping low overhead on the control channel.

[0093] Different cells may have different configurations and characteristics associated with them. For example, different bandwidths require different sizes of the frequency domain resource allocation (FDRA) bit field in the scheduling DCI. Another example is a scenario with multiple cells, some of which operate under licensed operation and others under unlicensed operation. For unlicensed operation, the DCI for uplink transmission is used to indicate the channel access type, while for licensed operation, the channel access type information is not required. If the WTRU is not sure which cells to schedule before DCI reception, scheduling multiple cells with different configurations by using the same DCI can add high overhead in the DCI.

[0094] Techniques for designing DCI to schedule multiple cells while maintaining low overhead for scheduling the DCI are described below.

[0095] The WTRU may be configured with multiple cells / carriers (carrier aggregation) for data transmission and / or reception. The WTRU may be configured to receive a single DCI to schedule multiple cells using PDSCH or PUSCH transmissions. A group of cells that will be scheduled using a single DCI is referred to herein as a "target cell". Determining the target cell includes determining the number of cells and the cell ID of each cell belonging to the target cell.

[0096] In the following disclosure, dynamic scheduling refers to scheduling PDSCH or PUSCH. Configured grant refers to uplink configured grant or downlink semi-persistent scheduling.

[0097] refer to Figure 2A The exemplary method 200 implemented in a wireless transmit / receive unit (WTRU) may begin at step 202. Step 202 may include receiving, by the WTRU, a single downlink control information (DCI). Processing may proceed from step 202 to step 204.

[0098] Step 204 may include determining, by the WTRU, scheduling of multiple cells based on a single DCI. For example, determining the scheduling at step 204 may include determining the multiple cells based on the cell on which the WTRU receives the single DCI. Alternatively, determining the scheduling at step 204 may include determining the multiple cells based on a radio network temporary identifier (RNTI) of a cyclic redundancy check (CRC) used to scramble the single DCI. In another alternative form, determining the scheduling at step 204 may include determining the multiple cells based on the format of the single DCI. In yet another alternative, determining the scheduling at step 204 may include determining the multiple cells based on a bit field identifying one or more target cells. In another alternative form, determining the scheduling at step 204 may include determining the multiple cells based on a DCI / media access control-control element (MAC-CE) indicating scheduling information and one or more target cells. Advantageously, when performing wireless communication, the number of blind decoding attempts for a single DCI that schedules multiple cells may depend on the number of target cells for the DCI. If there is no bit field in the single DCI, the WTRU may assume a semi-static configuration for a certain transmission parameter. It should be understood that the determination at step 204 may include a combination of the above. From step 204 , processing may proceed to step 206 .

[0099] Step 206 may include performing, by the WTRU, wireless communications based on the determination. For example, at step 206, the WTRU may determine transmit parameters for a scheduled transmission on the determined target cell, and perform the transmission on the target cell according to the determined transmit parameters. Alternatively, at step 206, the WTRU may perform a configured grant transmission. In another alternative, at step 206, the WTRU may perform a configured grant and a dynamic grant transmission. It should be understood that the performance of the wireless communications at step 204 may include a combination of the above. After step 206, the process may end. Alternatively, the process may return from step 206 to an earlier point in the process, such as step 202 or step 204.

[0100] refer to Figure 2B The exemplary method 250 implemented in a wireless transmit / receive unit (WTRU) may begin at step 252. Step 252 may include receiving, by the WTRU, a single downlink control information (DCI). Processing may proceed from step 252 to step 254.

[0101] Step 254 may include receiving, by the WTRU, individual DCIs separate from the single DCI. Processing may proceed from step 254 to step 256.

[0102] Step 256 may include determining, by the WTRU, power control parameters for the plurality of cells based on the separate DCI. For example, the separate DCI may indicate a transmit power control TCP command for one or more of the plurality of cells and / or an open loop power control (OLPC) parameter set for one or more of the plurality of cells. Processing may proceed from step 256 to step 258.

[0103] Step 258 may include the WTRU performing the same Figure 2A The WTRU may determine the scheduling of multiple cells based on a single DCI in the same or similar manner as described in step 206 of step 250. Additionally, step 258 may include determining whether a cell is to be scheduled (using a single DCI) based on the indicated power control parameters of the cell. For example, a zero transmit power indicated for a cell may be interpreted by the WTRU as no transmissions being scheduled for that cell. The WTRU may then decode the single DCI scheduling multiple cells accordingly. Processing may proceed from step 258 to step 260.

[0104] As described above, step 260 may include the WTRU performing wireless communications based on the determinations performed at steps 256 and 258. Thus, step 260 may be performed in conjunction with Figure 2AIn addition, step 260 may include performing wireless communication further based on the power control parameters determined at step 256. For example, the WTRU may perform power scaling for multiple cells using one or more TPC commands and / or OLPC parameter sets indicated by separate DCIs.

[0105] In some embodiments, the WTRU may be configured to determine the target cell at step 204 prior to receiving a single DCI scheduling multiple cells. The gNB may transmit an explicit indication, or alternatively, the WTRU may implicitly determine the target cell based on another indication sent by the gNB.

[0106] In some embodiments, the WTRU may be configured to receive DCI to determine the target cell. This DCI may be received separately from a single DCI that schedules the target cell. For example, a DCI indicating the target cell may be received before a single DCI schedules the target cell. The WTRU may use the received information about the target cell (number of cells and cell ID) to decode the single DCI that schedules the target cell. Alternatively, a DCI indicating the target cell may be received after a single DCI schedules the target cell. The WTRU may first decode the single DCI and then interpret the decoded bits of the single DCI according to the indicated target cell. This DCI may be received as a set of general DCIs or WTRU-specific DCIs.

[0107] In some embodiments, the WTRU may be configured to receive a MAC CE indicating a target cell. Such a MAC CE may be received on a previous PDSCH transmission on one of the configured cells. Alternatively, the WTRU may be configured to receive a MAC CE in a predetermined cell.

[0108] In one embodiment, the DCI and / or MAC CE indicating the target cell may have a bitmap of size equal to the number of configured cells. The bit positions within the bitmap may correspond to the cell IDs. For example, the most significant bit (MSB) may correspond to the cell with the smallest cell ID, and the least significant bit (LSB) may correspond to the cell ID with the largest cell ID. Alternatively, the most significant bit (MSB) may correspond to the cell with the largest cell ID, and the least significant bit (LSB) may correspond to the cell ID with the smallest cell ID. When a bit is set to "1" (or set to 0), the WTRU may determine that the corresponding cell is among the target cells.

[0109] The WTRU may be indicated using radio resource control (RRC) signaling with the target cell. The target cell may be associated with the cell using RRC signaling. When a single DCI is received that schedules multiple cells on one of the configured cells, the WTRU may determine the target cell using the RRC association between the cell where the single DCI is received and the target cell. For example, the WTRU may be configured with 6 cells: cell 1, cell 2, cell 3, cell 4, cell 5, and cell 6. Cell 1 may be associated with cell 1, cell 2, and cell 3, and cell 4 may be associated with cell 4, cell 5, and cell 6. When the WTRU receives a single DCI that schedules multiple cells in cell 1, the WTRU may determine that the target cells are cell 1, cell 2, and cell 3. When the WTRU receives a single DCI that schedules multiple cells in cell 4, the WTRU may determine that the target cells are cell 4, cell 5, and cell 6. In another embodiment, the target cell associated with the cell may be broadcast using SIB information or RRC configured in the case of a handover.

[0110] The WTRU may be configured to implicitly determine the target cell based on another indication received from the gNB. In one embodiment, the WTRU may be configured to determine the target cell based on the bandwidth acquired in the unlicensed spectrum. The WTRU may be configured to have wideband operation in an unlicensed band with multiple listen-before-talk (LBT) bandwidths (BWs). The WTRU may monitor the gNB indication regarding the acquired LBT BWs. After determining the acquired LBT BWs, the WTRU may determine that a cell with a frequency allocation belonging to one of the acquired LBT BWs will be the target cell for the PUSCH or PDSCH transmission. Alternatively, the WTRU may initiate the LBT procedure and acquire a set of LBT BWs. The WTRU may determine that a cell with a frequency allocation belonging to one of the acquired LBT BWs will be the target cell for the PUSCH or PDSCH transmission. For example, the WTRU may initiate its own LBT, acquire a set of LBT BWs, and share the channel occupancy time (COT) with the gNB. Such a COT may be used to schedule PUSCH or PDSCH transmissions.

[0111] In some embodiments, the WTRU may be configured to determine the target cell based on the active cell. For example, the WTRU may receive a MAC CE (and / or DCI) that activates and / or deactivates the configured cell set. The WTRU may then exclude the deactivated cell set from the target cell.

[0112] In another embodiment, the WTRU may be configured to update the target cell based on which cell is the primary cell (PCell). For example, the WTRU may determine the target cell associated with the PCell based on the broadcasted SIB information or the RRC configuration for handover. If the WTRU is reselecting the PCell, the WTRU may update the target cell accordingly.

[0113] In some embodiments, the WTRU may be configured to determine the number of scheduled cells based on an indicated value of a counter downlink allocation index (DAI) and / or an indicated total DAI value in a received DCI (i.e., a received single DCI that schedules multiple cells). In one example, the WTRU may be configured to determine the number of scheduled cells based on the difference between the indicated total DAI value and the counter DAI. For example, the WTRU may receive a single DCI that schedules multiple cells, where the total DAI bit field indicates the value of N1 and the counter DAI bit field indicates the value of N2. When N1>N2, the WTRU may determine that the number of scheduled cells with a single DCI is equal to N1-N2. Alternatively, the WTRU may be pre-configured with a table that may have values ​​for the number of cells, and the values ​​of N1-N2 may point to an index in the table. The WTRU may be configured to sort the HARQ-ACK feedback bits of the scheduled PDSCH using the order of the cell indexes that schedule the PDSCH.

[0114] At step 204, the WTRU may determine a target cell based on one or more characteristics of the scheduling DCI.

[0115] When performing the determination at step 204, the WTRU may be configured to monitor multiple DCI formats to schedule different target cells. Each DCI format may support scheduling a different number of cells and / or cell combinations. The DCI format may have a fixed size. In one embodiment, the specification of the DCI format may be designed to schedule N cells, and the WTRU may be further configured by the gNB to associate such a DCI format with N cells. For example, the RRC configuration may associate a DCI format with N cell IDs. The DCI format for scheduling N cells may be associated with different cell combinations and result in different DCI formats with the same number of scheduled cells (i.e., the number of target cells). For example, the WTRU may be configured with 6 cells: cell 1, cell 2, cell 3, cell 4, cell 5, and cell 6. As shown in Table 1, the first DCI format (format 2-a) may schedule cell 1 and cell 2, the second DCI format (format 2-b) may schedule cell 3 and cell 4, the third DCI format (format 2-c) may schedule cell 5 and cell 6, and the fourth DCI format (format 6-a) may schedule cell 1, cell 2, cell 3, cell 4, cell 5, and cell 6. Each DCI format associated with a cell combination (ie, target cell) may have different bit fields / contents.

[0116]

[0117] Table 1: Example of DCI format associated with cell combination

[0118] In one embodiment, the WTRU may be triggered to monitor a DCI format associated with a cell combination (i.e., a target cell) based on one or more previously received DCI formats. For example, when the WTRU receives a first DCI format and a second DCI format within the previous K time slots (e.g., K may be configured to the WTRU or the specification is fixed), the WTRU may begin monitoring a third DCI format for L time slots (e.g., K may be configured to the WTRU or the specification is fixed). In another example associated with Table 1, if the WTRU receives DCI formats 2-a, 2-b, and 2-c within the first K time slots, the WTRU may respond by beginning to monitor format 6-a for the next L time slots.

[0119] In some embodiments, the WTRU may be configured to stop monitoring a DCI format when a cell associated with the DCI format is deactivated. For example, the WTRU may receive a deactivation indication from the gNB for cell 1. The WTRU may respond by stopping monitoring for DCI format 2-a. The WTRU may fall back to monitoring a single DCI that schedules a single cell for cell 2 (e.g., after the cell associated with the DCI format is deactivated, after stopping monitoring, or in conjunction with stopping monitoring, etc.).

[0120] In some embodiments, the WTRU may be configured to have the same size for all DCI formats that will schedule multiple cells. The DCI formats that will schedule multiple cells may have a format identifier bit field to indicate which format is the DCI. At step 204, the WTRU may determine the target cell based on the DCI format indicated in the identifier bit field. For example, if the WTRU receives an identifier bit field pointing to format 2-c, the WTRU may determine that the target cells are cell 5 and cell 6 (as shown in Table 1).

[0121] In some embodiments, the WTRU may be configured to determine the target cell (a single DCI that schedules multiple cells) based on the RNTI used to scramble the CRC of the scheduled DCI at step 204. When the WTRU is configured with a DCI format that schedules multiple cells, the WTRU may be configured to monitor such a format and decode it using multiple RNTIs, where each RNTI corresponds to a cell combination. For example, the WTRU is configured with a fixed size DCI that may schedule one or more cells. When the WTRU attempts to decode the DCI, the WTRU may use different configured RNTIs, and upon successful decoding of the DCI, the used RNTI may indicate the target cell to the WTRU.

[0122] The WTRU may be configured with an association between an RNTI and a target cell. This configuration may be semi-statically configured using RRC signaling. For example, the WTRU may be configured with four cells that may be jointly scheduled using the same DCI. Cell 1 and cell 2 are associated with a first RNTI (e.g., X1-RNTI), cell 1 and cell 3 are associated with a second RNTI (e.g., X2-RNTI), cell 1 and cell 4 are associated with a third RNTI (e.g., X3-RNTI), cell 2 and cell 3 are associated with a fourth RNTI (e.g., X4-RNTI), cell 2 and cell 4 are associated with a fifth RNTI (e.g., X5-RNTI), and cell 3 and cell 4 are associated with a sixth RNTI (e.g., X6-RNTI). Upon successful decoding of the DCI using one of the configured RNTIs, the WTRU may determine the target cell using this association between the RNTI and the target cell. More generally, for N cells that may be jointly scheduled using a single DCI, the WTRU may be configured with M RNTIs that may scramble a single DCI, where M is less than or equal to The association between the subgroup of N cells (eg, target cells) and the M RNTIs may be semi-statically configured or the specification may be fixed (eg, in the form of a table).

[0123] In some embodiments, the WTRU may be configured to associate a group of cells with a search space set. When the WTRU receives a single DCI that schedules multiple cells, at step 204, the WTRU may determine the target cell based on the associated cell with the search space set on which the single DCI was received. For example, the WTRU may be configured with two search space sets {s1, s2} and 6 cells {cell 1, cell 2, cell 3, cell 4, cell 5, cell 6}. The search space set s1 may be associated with {cell 1, cell 2, cell 3}, and the search space s2 may be associated with {cell 4, cell 5, cell 6}. When a single DCI scheduling multiple cells is received on s1, the WTRU may determine that the target cell is {cell 1, cell 2, cell 3}. When a single DCI scheduling multiple cells is received on s2, the WTRU may determine that the target cell is {cell 4, cell 5, cell 6}. In addition to the DCI format, the search space set RRC configuration may include a group of cells (i.e., target cells). Alternatively, the search space set configuration may include only the target cell.

[0124] In some embodiments, the WTRU may be configured to monitor the same DCI format for all possible scheduled cells. This DCI may have a fixed size, regardless of the number of target cells. This DCI may contain an identifier bit field for the target cell. At step 204, the WTRU may determine the target cell to be scheduled based on the identifier bit field of the target cell in the DCI. The value of the target cell identifier may be mapped to the configured cell combination. For example, the WTRU may be configured with {cell 1, cell 2, cell 3, cell 4, cell 5, cell 6}. The RRC configuration may configure the WTRU to associate the value of the identifier bit field of the target cell with the target cell, as shown in Table 2:

[0125]

[0126] Table 2: Example of association between target cell identifier and target cell

[0127] In some embodiments, the target cell identifier bit field value may be mapped to different tables depending on the search space set on which a single DCI is received. For example, the WTRU may be configured with two search space sets, each search space set being associated with a different table, as shown in Tables 3 and 4.

[0128]

[0129] Table 3: Association of target cell identifiers with target cells when a single DCI is received in search space set 1

[0130]

[0131] Table 4: Association of target cell identifiers with target cells when a single DCI is received in search space set 2

[0132] In some embodiments, the WTRU may be configured to evenly distribute blind decoding efforts among all configured "single DCIs that schedule multiple cells". In another embodiment, for each "single DCI that schedules multiple cells", the WTRU may be configured with different blind decoding efforts. For example, for all configured cells, the WTRU may support a maximum number of DCI blind decoding attempts. Each DCI of a scheduling cell combination (target cell) may be configured with a different number of DCI blind decoding attempts. In an example embodiment, the number of blind decoding attempts for a single DCI that schedules multiple cells depends on the number of target cells for the DCI. For example, a first DCI format may be configured to schedule 2 cells, and a second DCI format may be configured to schedule 3 cells. In one example, the number of blind decoding attempts for the first DCI is equal to 2xNmax / (2+3), and the number of blind decoding attempts for the second DCI is equal to 3xNmax / (2+3), where Nmax is the maximum number of blind decoding attempts for the DCIs of all configured cells. The number of blind decoding attempts for each DCI format is equal to the scaled maximum number of blind decoding attempts for the DCIs of all configured cells. The scaling factor for each DCI format may depend on the number of cells scheduled simultaneously.

[0133] At step 204, the WTRU may implement two-level scheduling.

[0134] In some embodiments, the WTRU may be configured to receive a first DCI indicating some scheduling information and a subsequent DCI carrying the remaining scheduling information. For example, the first DCI may indicate the target cell (i.e., how many cells and which cells will be scheduled), and the second DCI may carry resource allocation information. The first DCI may use a bitmap with a configured cell size to indicate the target cell. The most significant bit (MSB) may correspond to the cell with the smallest cell ID and the least significant bit (LSB) may correspond to the cell ID with the largest cell ID. A value of 1 may correspond to a cell that is a target cell, while a value of 0 may correspond to a cell that is not a target cell. In another embodiment, the first DCI may indicate the target cell by triggering the transmission of channel state information (CSI) and / or sounding reference signal (SRS) for a subset of the configured cells. If the CSI or SRS transmission is triggered by the first DCI, the WTRU may determine that the cell is a target cell.

[0135] In some embodiments, the WTRU may be configured with two different DCI formats to monitor two-level scheduling. The first DCI format is used for a first DCI that may have a small size, and the second DCI format is used for a second DCI that may have a larger size. The WTRU may be configured to monitor the first DCI format and the second DCI format with different aggregation levels. For example, the first DCI format may be configured to have a low aggregation level, while the second DCI format may be configured to have a high aggregation level. For the first DCI format and the second DCI format, the WTRU may be configured with different search space sets. The first search space set may monitor the first DCI format with a large periodicity (e.g., the WTRU monitors the first search space set every 5ms). The second search space set may monitor the second DCI format with a small periodicity (e.g., the WTRU monitors the second search space set every 1ms).

[0136] The first DCI and the second DCI may have different configurations of one or more of the following: DCI format: for example, the first DCI is configured to be received in a first DCI format, while the second DCI is configured to be received in a second DCI format; control resource set (core set): for example, the first DCI may be configured to be received in a first core set, while the second DCI may be configured to be received in a core set; search space set: for example, the first DCI may be configured to be received in a first search space set, while the second DCI may be configured to be received in a second search space set; bandwidth part (BWP): for example, the first DCI may be configured to be received in a first BWP, while the second DCI may be configured to be received in a second BWP; cell: for example, the first DCI may be configured to be received in a first cell, while the second DCI may be configured to be received in a second cell; and transmit receive point (TRP): for example, the first DCI may be configured to be received in a first TRP, while the second DCI may be configured to be received in a second TRP.

[0137] In some embodiments, the WTRU may be configured with a valid time for the first DCI. Upon receiving the first DCI carrying some scheduling information, the WTRU may assume that the scheduling information is valid for the configured number of time slots (for example, the number of time slots may be semi-statically configured to the WTRU using RRC signaling, dynamically indicated using a bit field in the first DCI, or the specification is fixed). For example, the WTRU may receive a first DCI indicating a target cell. The WTRU may assume that the target cell information is valid for 10ms. The WTRU may be configured to back off after the valid time to assume certain scheduling information. For example, when the valid time expires, the WTRU may assume that the target cells are all configured cells. In another example, when the valid time expires, the WTRU may assume that the target cells are only primary cells (PCell) or pre-configured cells. For another example, when the valid time expires, the WTRU may assume that the target cell is a configured set of cells.

[0138] In some embodiments, the WTRU may be configured to report a positive acknowledgement or negative acknowledgement (ACK / NACK) of the reception of the first DCI. The WTRU may be configured with a physical uplink control channel (PUCCH) resource to report the ACK / NACK of the reception of the first DCI. The PUCCH resource may be semi-statically configured using RRC signaling, or dynamically indicated in the first DCI using a PUCCH resource indicator (PRI). In some embodiments, the WTRU may be configured to report the ACK / NACK of the reception of the first DCI and the hybrid automatic repeat request acknowledgement (HARQ-ACK) report sent by the scheduled PDSCH scheduled by both the first DCI and the second DCI. For example, the first DCI may indicate a target cell, and the second DCI may schedule a PDSCH on the target cell. The WTRU may report HARQ-ACK feedback for the scheduled PDSCH and ACK / NACK for the first DCI in the same PUCCH resource or PUSCH resource.

[0139] In some embodiments, the WTRU may be configured to receive a first DCI on one or more control channels and a second DCI on one or more data channels. The second DCI may be multiplexed with a PDSCH transmission on one of the scheduled cells. For example, the WTRU may be indicated by a first DCI of a target cell and schedule a PDSCH transmission on one of the cells (e.g., scheduling a PDSCH on a PCell). The PDSCH scheduled on the PCell may be multiplexed with a second DCI to carry additional scheduling information about the target cell.

[0140] In some embodiments, the first DCI may indicate some scheduling information of multiple cells, and may schedule the transmission timing, frequency domain timing and / or transmission parameters of the second DCI, and the second DCI may carry the remaining scheduling information of the multiple cells. Figure 3 As shown, the first DCI 300 may indicate the target cell and indicate the time slot position at which the WTRU should expect the second DCI 302. The time slot position may be offset relative to the time slot at which the first DCI 300 is received. In another example, the first DCI may indicate the target cell and indicate the search space set ID at which the WTRU should expect the second DCI. In another example, the first DCI may indicate the target cell and indicate the control channel element (CCE) at which the WTRU should expect the second DCI.

[0141] In some embodiments, the WTRU may be configured to receive a first DCI and a second DCI within the same search space set or within the same search space set and aggregation level (AL). The WTRU may first attempt to detect the first DCI, and in response to successfully decoding the first DCI, attempt to detect the second DCI. For example, within the same AL, some CCEs may be used for the first DCI, and the remaining CCEs may be used for the second DCI. The WTRU may blindly decode only the first CCE, and decode the remaining CCEs in response to detecting the first DCI.

[0142] The WTRU may be configured to receive a MAC CE indicating a set of cells to be scheduled for the next set of time slots (i.e., the target cells for the next set of time slots), and the MAC CE may be followed by a single DCI that schedules multiple cells. Part of the scheduling information may be carried by the MAC CE, while other scheduling information may be carried by a single DCI. Such a MAC CE may be received by the WTRU on a previous PDSCH scheduled on one of the configured cells, and may indicate the scheduled cells in one of two ways: a bitmap indicating which cell is scheduled and / or which cell the grant applies to. For example, the RRC may configure which subsets of cells the MAC CE may schedule, and then the MAC CE may indicate (1 or 0) which of these cells are scheduled. Alternatively, it may be all configured cells. The WTRU may omit deactivated cells; and cell indices of cascaded scheduled cells.

[0143] In some embodiments, the WTRU may activate a cell upon receiving a MAC CE indicating a scheduled cell. For example, the WTRU may be configured with cell x, and cell x may be deactivated. When the MAC CE indicates cell x as the target cell, the WTRU may activate the cell.

[0144] In some embodiments, the MAC CE may have two or more formats, and the format may be indicated by the gNB in ​​the MAC CE header. For example, a short format may be used, where the WTRU assumes that the number of scheduled cells is less than the configured number (e.g., 8 cells). The short format may indicate only the cell index, rather than a bitmap with the configured cell size. The short format may be of a fixed size. In another example, a long format may be used, where the WTRU assumes that the number of scheduled cells is greater than the first configured number and less than the second configured number. A bitmap may be used to indicate which cells are scheduled. The size of the long format may vary depending on the number of scheduled cells indicated.

[0145] In some embodiments, in response to receiving a PDSCH retransmission containing a multi-cell scheduling MAC CE, the WTRU may discard the grant or assignment, assuming that they are no longer valid. In another embodiment, the WTRU may assume that the grant and / or assignment is valid starting from an offset relative to the MAC CE reception time or relative to the time of sending the HARQ-ACK for the transport block (TB) with the MAC CE.

[0146] In some embodiments, the WTRU may be configured to receive a MAC CE that includes one or more of: a time offset until the start of the grant for each cell or all cells; a BWP associated with the scheduled grant, possibly for each cell; a HARQ process ID (PID) for each scheduled cell; other HARQ information (RV, new data indicator (NDI), transport block size (TBS), modulation and coding scheme (MCS)); whether the grant is for a supplemental uplink (SUL) or a normal uplink (NUL); a core set, a transmit configuration indicator (TCI) state, or a search space to monitor in the scheduled cells; and a logical channel (LCH) in the MAC subheader for identifying the MAC CE for scheduling multiple cells.

[0147] In some embodiments, the WTRU may assume that the grant or DL ​​assignment starts at least X ms after the end of the PDSCH containing the MAC CE.

[0148] At step 206, the WTRU may determine transmission parameters for the scheduled transmission on the determined target cell.

[0149] In some embodiments, the WTRU may be configured to use the same transmission parameters for each cell transmission in the scheduled cells. For example, a single DCI that schedules multiple cells may have a single time domain resource allocation (TDRA) bit field, and the WTRU may assume the same TDRA value for all scheduled transmissions. In another embodiment, the scheduled transmissions on different target cells may have different transmission parameters. A single DCI that schedules multiple cells may have a single bit field for each transmission parameter for all scheduled cells, but point to different values ​​for each cell. For example, a different modulation and decoding scheme table may be configured for each cell. The WTRU may use the MCS bit field value in a single DCI that schedules multiple cells to determine the MCS value of each cell based on the MCS table of each cell. In another embodiment, the WTRU may be configured to use the same transmission parameters for a subset of transmission parameters and different transmission parameters for another subset of transmission parameters.

[0150] In some embodiments, when determining the transmission parameters of the scheduled cell, if the scheduled cell is not configured with a certain transmission parameter in a single DCI that schedules multiple cells, the WTRU may be configured to ignore the bit field corresponding to the transmission parameter. For example, for a single DCI that schedules two cells, one cell may belong to an unlicensed band and the other cell may belong to a licensed band. The single DCI may contain a bit field corresponding to a channel access priority type. When the unlicensed cell is within the target cell, the WTRU may use the channel access priority type bit field for the unlicensed cell, and if the unlicensed cell is not within the target cell, the WTRU may ignore the channel access priority type bit field.

[0151] In some embodiments, the WTRU may be configured with a single DCI that schedules multiple cells that does not include all transmission parameters for all cells. If the bit field is not present, the WTRU may assume a semi-static configuration for a certain transmission parameter. For example, a cell may support transmissions with different priorities, but a single DCI that schedules multiple cells may not include a priority indication. In this case, the WTRU may assume that the transmissions scheduled by the single DCI that schedules multiple cells are low priority transmissions.

[0152] In some embodiments, the WTRU may be configured to determine a bit field set present in a DCI that schedules multiple cells based on the identified target cell. A bit field set may be defined as a set of bit fields that will be present in the DCI. The DCI may be scheduling uplink transmissions (e.g., multiple PUSCHs) or downlink transmissions (e.g., multiple PDSCHs), and the target cell may be determined using the methods described previously. For example, Table 5 shows two different bit field sets. The WTRU may be configured with an association between a bit field set and a target cell. Each bit field in a bit field set may be configured as a common indication (e.g., the same value applies to the target cell), a joint indication (e.g., the same bit field value, but may point to different RRC configuration values), or a separate indication for a transmission parameter (e.g., a separate bit field). This configuration may be provided to the WTRU using RRC signaling. For example, a single DCI may schedule the WTRU to schedule four possible cells (i.e., cell 1, cell 2, cell 3, and cell 4). Target cells cell 1 and cell 2 may be associated with S1 (i.e., the first bit field set), and target cells cell 3 and cell 4 may be associated with S2 (i.e., the second bit field set). The WTRU may assume that there is a second bit field set (S2) in the DCI when it is determined that the target cells are cell 3 and cell 4. As shown in Table 5, the bit field set S2 has a joint indication of the frequency domain resource allocation (FDRA) (i.e., the same code point in the bit field but different frequency domain allocation) and the common time domain resource allocation (TDRA) (i.e., the same code point in the bit field and the same time domain allocation) for cell 3 and cell 4.

[0153]

[0154] In some embodiments, the WTRU may be configured with a single DCI that schedules multiple cells so that one set of bit fields is always present regardless of the determined target cell and a second set of bit fields that are dependent on the determined target cell. The set of bit fields that are always present may carry scheduling information that is independent of the target cell. For example, the set of bit fields that are always present may include TPC commands for a PUCCH bit field, a PUCCH resource indicator bit field, and a PDSCH to HARQ feedback timing indicator. When the WTRU identifies the target cell, the WTRU may assume that the DCI bit field includes a set of bit fields that are always present and a set of bit fields that are dependent on the target cell. For example, when the WTRU determines the target cell (e.g., cell 3 and cell 4 in the above example), the WTRU may assume that the DCI includes a set of bit fields that are always present and a set of bit fields S2.

[0155] refer to Figure 4, an example implementation is presented as a method 400, wherein at step 402, the WTRU is configured with multiple RNTIs, each of which is associated with a cell combination (i.e., a target cell). At step 404, the WTRU may monitor for DCI of a fixed size that may schedule one or more PUSCH / PDSCH in different cells, and at step 406, attempt to decode the DCI candidate using the configured cell combination RNTI. In response to a successful decoding at step 408, the WTRU may determine the scheduled cell / target cell based on the RNTI used to successfully decode the DCI at step 410. Then, at step 412, the WTRU may determine the transmit (or receive) parameters of the determined cell based on the determined cell. For example, the WTRU may use a bit field set associated with the target cell described above. Finally, at step 414, the WTRU may use the determined transmit parameters to exchange information (e.g., transmit (or receive) to (or from) the determined cell).

[0156] refer to Figure 5 , depicts an example of a flow chart showing a method 500 implemented in a WTRU for implementing single downlink control information scheduling for multiple cells. At step 510, the WTRU may be configured to receive configuration information including a plurality of identifiers, each of the plurality of identifiers being associated with a cell set of a plurality of cell sets. At step 520, the WTRU may be configured to receive downlink control information (DCI) masked with a first identifier included in the received configuration information, wherein the first identifier is used to expose the DCI during said reception of the DCI. At step 530, the WTRU may be configured to determine a cell set associated with the DCI, the cell set including at least a first cell and a second cell; and at step 540, the WTRU may be configured to communicate via the cell set including at least the first cell and the second cell using an information element associated with the received DCI.

[0157] In some embodiments, at step 206, the WTRU may perform a configured grant transmission. For example, the WTRU may be configured with a DCI format that may activate / deactivate one or more configured grants / DL semi-persistent scheduling (SPS) transmissions on a set of cells. The WTRU may be configured using an RRC configuration with multiple configured grants / DL SPSs on multiple cells, and such a DCI may activate / deactivate one or more configured grants / DL SPSs on a target cell. The WTRU may be configured with multiple RNTIs for monitoring a single DCI that triggers multiple configured grants / DL SPSs on different cells. In one embodiment, each RNTI may be associated with a cell combination. In response to receiving a single DCI that schedules multiple cells scrambled with a specific RNTI, the WTRU may trigger all configured grants / DL SPS transmissions on the target cell. In another embodiment, each RNTI may be associated with a configured grant / DL SPS set on one or more cells. In response to receiving a single DCI that schedules multiple cells scrambled with a specific RNTI, the WTRU may trigger the transmission of only the configured grants / DL SPS resources associated with the RNTI.

[0158] The WTRU may be configured with an RNTI associated with a configured grant / DL SPS as part of the RRC configuration of the configured grant / DL SPS. Alternatively, the WTRU may autonomously determine the radio network temporary identifier (RNTI) associated with the configured grant / DL SPS resource using a formula. For example, the WTRU may use the configured grant / DL SPS resource ID and the cell ID to determine the RNTI associated with the configured grant / DL SPS. An example formula may be: , where RNTI0, M1 and M2 can be configured individually or the specifications are fixed.

[0159] In some embodiments, after determining that the received single DCI is associated with a target cell for a configured grant / DL SPS, the WTRU may respond by determining whether to activate or deactivate the configured grant / DL SPS within the cell based on a bit field in the DCI. For example, the WTRU may determine whether one or more predefined DCI bit fields are set to certain special values ​​to determine which of the DL SPS / configured grants will be triggered or released.

[0160] In some embodiments, at step 206, the WTRU may perform transmission of configured grants and dynamic grants. For example, the WTRU may be configured with a DCI format that may activate transmission of one or more configured grants / DL SPS on a subset of cells and schedule dynamic grants on another subset of cells. The WTRU may be configured using an RRC configuration with multiple configured grants / DL SPS on multiple cells. Such a DCI may activate one or more of the configured grants / DL SPS on cells within a target cell and dynamically schedule grants on some cells within the target cell. The WTRU may be configured with multiple RNTIs for monitoring a single DCI that triggers a configured grant / DL SPS and for dynamic scheduling on multiple cells. In one embodiment, each RNTI may be associated with a configured grant / DL SPS on a first subset of cells and a dynamic grant on a second subset of cells. In response to receiving a single DCI that schedules multiple cells scrambled with a specific RNTI, the WTRU may enable / disable the sending of configured grants / DL SPS on a first subset of cells and send one or more dynamically scheduled grants on a second subset of cells associated with the RNTI used (target cell = first subset + second subset). The WTRU may determine whether to activate or deactivate the configured grants / DL SPS within a cell based on a bit field in the DCI. For example, the WTRU may determine whether a predefined DCI bit field is set to certain special values ​​to determine which of the DL SPS / configured grants will be triggered or released. The WTRU may be configured to ignore scheduling information for configured grants / DL SPS resources indicated in a single DCI that schedules multiple cells. The WTRU may use the scheduling information indicated in a single DCI that schedules multiple cells for dynamic grants.

[0161] In some embodiments, the WTRU may be configured to receive a separate DCI from a single DCI that schedules multiple cells. The separate DCI may indicate power control parameters for each cell. The separate DCI may indicate one or more of the following for each cell: a transmit power control (TPC) command. For example, the separate DCI may contain 2 bits per cell to indicate the TPC command value; an open-loop power control (OLPC) parameter set. For example, the separate DCI may contain N bits per cell to indicate an open-loop power control parameter set indication. Alternatively, the WTRU may be configured with a single bit field per cell to indicate the OLPC parameter set.

[0162] In some implementations, the WTRU may be configured to determine whether a cell is to be scheduled (using a single DCI) based on the power control parameters indicated for the cell. For example, a zero transmit power indicated for a cell may be interpreted by the WTRU as no transmission scheduled for that cell. The WTRU may then decode the single DCI that schedules multiple cells accordingly.

[0163] In some solutions, when scaling power between scheduled cells for PUSCH transmissions, the WTRU may be configured to prioritize between the scheduled cells. For example, when a WTRU is scheduled with multiple PUSCH transmissions on different cells, the WTRU may allocate the available transmit power between the scheduled cells using some priority rule. The WTRU may be configured to prioritize between the scheduled cells during the power scaling process based on one or more of the following: the cell index of the scheduled cell, for example, the WTRU may assign a larger scaling factor (power scaling factor) to a cell with an index equal to 0. The WTRU may be configured to calculate a power scaling factor for each cell based on a formula, and the formula may take into account the cell index; the number of PRBs allocated for PUSCH transmission within the cell, for example, the WTRU may be configured to allocate a larger scaling factor to a cell having a larger number of scheduled PRBs for PUSCH transmission; the number of symbols allocated for PUSCH transmission within the cell, for example, the WTRU may be configured to allocate a larger scaling factor to a cell having a larger number of scheduled symbols for PUSCH transmission; the subcarrier spacing of the scheduled cells: the WTRU may be configured to prioritize / allocate a larger scaling factor to a cell having a larger subcarrier spacing, alternatively, the WTRU may be configured to prioritize / allocate a larger scaling factor to a cell having a smaller subcarrier spacing; the frequency position of the scheduled cells: the WTRU may be configured to prioritize the power allocation of the cells based on the frequency position of the scheduled cells, for example, the WTRU may be configured to allocate higher power to cells belonging to higher frequencies (for example, due to high path loss channels).

[0164] In some embodiments, the WTRU may be configured with CSI-RS and / or SRS on multiple cells, and subsets of CSI-RS / SRS may be jointly triggered to be received / sent on different cells using a single DCI. The WTRU may be configured with a mapping between CSI-RS / SRS resources on a subset of cells and a DCI format. This DCI format may trigger the sending / receiving of CSI-RS / SRS on a pre-configured subset of cells. In another solution, the WTRU may be configured with a bit field in the DCI that may indicate a subset of cells on which CSI-RS / SRS resources are triggered. For example, the value of such a bit field in the DCI may be mapped to a set of CSI / SRS resources on multiple cells. In another embodiment, the search space set and / or core set on which the DCI is received may be used as an indication of the set of CSI / SRS resources to be triggered. For example, a search space set may be associated with a group of cells. Upon receiving a DCI triggering CSI-RS reception on a search space set, the WTRU may use the configured association between the search space set and a set of cells to determine the set of cells on which the CSI RS will be transmitted. In another example, a bandwidth part (BWP) may be associated with a set of cells. Upon receiving a DCI triggering CSI-RS reception on a search space set on a BWP, the WTRU may respond by using the configured association between the BWP and the set of cells to determine the set of cells on which the CSI RS will be transmitted.

[0165] In some embodiments, the DCI that schedules multiple cells may have a single bit that triggers CSI-RS reception / SRS transmission. Based on the above method, the WTRU can determine the set of cells with CSI reception / SRS transmission, and the single bit can jointly trigger the reception / transmission of CSI-RS / SRS on the target cell. In another specific implementation, the DCI that schedules multiple cells may have a bitmap that can enable / disable CSI-RS reception / SRS transmission on the target cell. For example, in the case of semi-persistent CSI scheduling, the value "one" can enable CSI-RS reception, while the value "zero" can disable CSI-RS reception. The WTRU can be configured to determine the target cell on which to enable / disable semi-static CSI-RS based on the above method. Using the bitmap included in the DCI, the WTRU can further determine whether the CSI is enabled or disabled.

[0166] Although features and elements are provided above in specific combinations, it will be understood by those of ordinary skill in the art that each feature or element may be used alone or in any combination with other features and elements. The present disclosure is not limited to the specific embodiments described in this patent application, which are intended to be illustrative of various aspects. Many modifications and variations can be made without departing from the essence and scope of the present invention, as they will be apparent to those skilled in the art. Unless explicitly provided as such, any element, action or instruction used in the present application specification should not be understood as being essential or necessary to the present invention. According to the foregoing description, in addition to those listed herein, functionally equivalent methods and devices within the scope of the present disclosure will be apparent to those skilled in the art. Such modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is limited only to the terms of the appended claims and the full range of equivalent forms of such entitled claims. It should be understood that the present disclosure is not limited to a specific method or system.

[0167] For simplicity, the foregoing embodiments are discussed with respect to terminology and structure of infrared capable devices (i.e., infrared transmitters and receivers). However, the embodiments discussed are not limited to these systems, but may be applied to other systems using other forms of electromagnetic waves or non-electromagnetic waves (such as sound waves).

[0168] It should also be understood that the terminology used herein is for the purpose of describing specific embodiments only and is not intended to be limiting. As used herein, the term "video" or the term "image" may mean any of a snapshot, a single image, and / or a plurality of images displayed on a temporal basis. For example, when referred to herein, the term "user equipment" and its abbreviation "UE", the term "remote" and / or the term "head-mounted display" or its abbreviation "HMD" may mean or include (i) a wireless transmit and / or receive unit (WTRU); (ii) any of a plurality of embodiments of a WTRU; (iii) a wirelessly-enabled and / or wiredly-enabled (e.g., tetherable) device configured with (in particular) some or all of the structure and functionality of a WTRU; (iii) a wirelessly-enabled and / or wiredly-enabled device configured with less than all of the structure and functionality of a WTRU; or (iv), etc. This document is relative to Figures 1A to 1D Details of an example WTRU are provided that may represent any WTRU described herein. As another example, various disclosed embodiments herein above and below are described as utilizing a head mounted display. One skilled in the art will recognize that devices other than head mounted displays may be utilized, and some or all of the present disclosure and various disclosed embodiments may be modified accordingly without undue experimentation. Examples of such other devices may include drones or other devices configured to stream information to provide an adapted reality experience.

[0169] In addition, the methods provided herein may be implemented in a computer program, software, or firmware incorporated into a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (sent via a wired or wireless connection) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (such as internal hard disks and removable disks), magneto-optical media, and optical media (such as CD-ROM disks and digital versatile disks (DVDs)). A processor associated with the software may be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, MME, EPC, AMF, or any host computer.

[0170] Variations of the methods, devices, and systems provided above are possible without departing from the scope of the present invention. In view of the various embodiments that may be applied, it should be understood that the illustrated embodiments are merely examples and should not be considered to limit the scope of the following claims. For example, the embodiments provided herein include handheld devices that may include or be used with any suitable voltage source (such as a battery, etc.) that provides any suitable voltage.

[0171] In addition, in the embodiments provided above, processing platforms, computing systems, controllers, and other devices including processors are indicated. These devices may include at least one central processing unit ("CPU") and memory. According to the practice of those skilled in the art of computer programming, references to symbolic representations of actions and operations or instructions may be performed by various CPUs and memories. Such actions and operations or instructions may be referred to as being "executed," "computer executed," or "CPU executed."

[0172] Those of ordinary skill in the art will appreciate that the actions and symbolic representations of operations or instructions include manipulation of electrical signals by the CPU. The electrical system represents data bits, which may result in the ultimate transformation of electrical signals or reduction of electrical signals and the retention of data bits at memory locations in the memory system, thereby reconfiguring or otherwise changing the operation of the CPU and performing other processing of signals. The memory location that holds the data bit is a physical location that has a specific electrical, magnetic, optical, or organic property corresponding to or representing the data bit. It should be understood that the embodiments are not limited to the above-mentioned platforms or CPUs, and other platforms and CPUs may also support the provided methods.

[0173] The data bits may also be maintained on a computer-readable medium, including magnetic disks, optical disks, and any other volatile (e.g., random access memory ("RAM")) or non-volatile (e.g., read-only memory ("ROM")) mass storage system readable by the CPU. The computer-readable medium may include cooperating or interconnected computer-readable media that reside solely on the processing system or distributed across multiple interconnected processing systems that may be local or remote relative to the processing system. It should be understood that the embodiments are not limited to the above-mentioned memories, and other platforms and memories may also support the provided methods.

[0174] In an exemplary embodiment, any of the operations, processes, etc. described herein may be implemented as computer-readable instructions stored on a computer-readable medium. The computer-readable instructions may be executed by a processor of a mobile unit, a network element, and / or any other computing device.

[0175] There is little difference between hardware implementation and software implementation of various aspects of the system. The use of hardware or software is usually (but not always, because in some contexts, the choice between hardware and software may become important) a design choice that represents a trade-off between cost and efficiency. There may be various means of transportation (e.g., hardware, software, and / or firmware) that can implement the processes and / or systems and / or other technologies described herein, and the preferred means of transportation may vary with the context of the deployment process and / or system and / or other technologies. For example, if the implementer determines that speed and accuracy are most important, the implementer may choose a medium that is primarily hardware and / or firmware. If flexibility is most important, the implementer may choose a specific implementation that is primarily software. Alternatively, the implementer may choose some combination of hardware, software, and / or firmware.

[0176] The above detailed description has listed various embodiments of the device and / or process through the use of block diagrams, flow charts and / or examples. Where such block diagrams, flow charts and / or examples include one or more functions and / or operations, it should be understood by those skilled in the art that each function and / or operation within such block diagrams, flow charts or examples can be implemented individually and / or collectively by a wide range of hardware, software, firmware or almost any combination thereof. In one embodiment, several parts of the subject matter described herein can be implemented via application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs) and / or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein may be equivalently implemented in integrated circuits as a whole or in part as one or more computer programs running on one or more computers (e.g., one or more programs running on one or more computer systems), one or more programs running on one or more processors (e.g., one or more programs running on one or more microprocessors), firmware or almost any combination thereof, and according to the present disclosure, designing circuits and / or writing software and / or firmware codes will be completely within the technical scope of those skilled in the art. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein can be distributed as a program product in a variety of forms, and that the exemplary embodiments of the subject matter described herein apply regardless of the specific type of signal storage medium used to actually perform the distribution. Examples of signal storage media include, but are not limited to, the following: recordable type media (such as floppy disks, hard drives, CDs, DVDs, digital tapes, computer memory, etc.); and transmission type media (such as digital and / or analog communication media (e.g., fiber optic cables, waveguides, wired communication links, wireless communication links, etc.)).

[0177] Those skilled in the art will recognize that it is common in the art to describe devices and / or processes in the manner listed herein, and thereafter use engineering practices to integrate such described devices and / or processes into a data processing system. That is, at least a portion of the devices and / or processes described herein can be integrated into a data processing system via a reasonable amount of experimentation. Those skilled in the art will recognize that a typical data processing system generally may include one or more of the following: a system unit housing; a video display device; a memory, such as a volatile memory and a non-volatile memory; a processor, such as a microprocessor and a digital signal processor; a computing entity, such as an operating system, a driver, a graphical user interface, and an application; one or more interactive devices, such as a touch pad or a screen; and / or a control system, including a feedback loop and a control motor (e.g., a feedback for sensing position and / or velocity, a control motor for moving and / or adjusting components and / or quantities). A typical data processing system may be implemented using any suitable commercially available components, such as those typically found in data computing / communication and / or network computing / communication systems.

[0178] The subject matter described herein sometimes illustrates different components included in or connected to different other components. It should be understood that such depicted architectures are merely examples, and in fact many other architectures that achieve the same functionality can be realized. In a conceptual sense, any arrangement of components that achieve the same functionality is effectively "associated" so that the desired functionality can be achieved. Therefore, any two components that are combined to achieve a specific functionality in this article can be considered to be "associated" with each other so that the desired functionality can be achieved, regardless of the architecture or intermediate components. Similarly, any two components so associated can also be considered to be "operably connected" or "operably coupled" to each other to achieve the desired functionality, and any two components that can be so associated can also be considered to be "operably coupled" to each other to achieve the desired functionality. Specific examples that can be operably coupled include, but are not limited to, components that can physically cooperate and / or physically interact and / or components that can wirelessly interact and / or wirelessly interact and / or components that can logically interact and / or components that can logically interact.

[0179] For substantially any plural and / or singular terms used herein, those skilled in the art may translate from the plural to the singular and / or from the singular to the plural, as appropriate, as appropriate to the context and / or application. For clarity, various singular / plural arrangements may be explicitly listed herein.

[0180] It will be understood by those skilled in the art that, in general, the terms used herein, and particularly in the appended claims (e.g., the bodies of the appended claims), are generally intended to be "open" terms (e.g., the term "including" should be interpreted as "including but not limited to", the term "having" should be interpreted as "having at least", the term "comprising" should be interpreted as "including but not limited to", etc.). It will also be understood by those skilled in the art that if a specific number of an introduced claim recitation is intended, such intent will be expressly stated in the claim, and in the absence of such a statement, such intent is absent. For example, where only one item is intended, the term "single" or similar language may be used. To aid understanding, the following appended claims and / or the description herein may include the use of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed as implying that any particular claim including such introduced claim recitation is limited to an embodiment including only one such recitation by the indefinite article "a" or "an" to introduce a claim recitation. This is true even when the same claim includes the introductory phrase "one or more" or "at least one" and an indefinite article such as "a" or "an" (e.g., "a" and / or "an" should be interpreted as meaning "at least one" or "one or more"). The same applies to the use of definite articles used to introduce claim expressions. In addition, even if a specific number of introduced claim expressions is explicitly stated, those skilled in the art will recognize that such statements should be interpreted as meaning at least the stated number (e.g., a bare statement of "two expressions" without other modifiers means at least two expressions or two or more expressions). In addition, in those instances where a convention similar to "at least one of A, B, and C, etc." is used, generally speaking, the meaning of such construction is that those skilled in the art will understand the convention (e.g., "a system having at least one of A, B, and C" will include, but is not limited to, a system having A alone, B alone, C alone, A and B at the same time, A and C at the same time, B and C at the same time, and / or A, B, and C at the same time, etc.). In those instances where a convention similar to "at least one of A, B, or C, etc." is used, generally speaking, the meaning of such construction is that one skilled in the art will understand the convention (e.g., "a system having at least one of A, B, or C" will include, but is not limited to, systems having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). One skilled in the art will also understand that, in fact, any discrete words and / or phrases presenting two or more alternative terms, whether in the specification, claims, or drawings, should be understood to contemplate the possibility of including one of the terms, any of the terms, or both of the terms.For example, the phrase "A or B" will be understood to include the possibilities of "A" or "B" or "A and B." Additionally, as used herein, the term "any of" followed by a listing of multiple items and / or multiple categories of items is intended to include "any of," "any combination," "any multiples," and / or "any combination of multiples" of the items and / or categories of items, either alone or in combination with other items and / or other categories of items. Additionally, as used herein, the term "set" is intended to include any number of items, including zero. Additionally, as used herein, the term "quantity" is intended to include any quantity, including zero. And, as used herein, the term "plurality" is intended to be synonymous with "multiple."

[0181] In addition, where features or aspects of the disclosure are described in terms of Markush groups, those skilled in the art will recognize that the disclosure is also described in terms of any individual member or subgroup of members of the Markush group.

[0182] As will be understood by those skilled in the art, for any and all purposes (such as for providing a written description), all ranges disclosed herein also encompass any and all possible subranges and combinations of their subranges. Any listed range can be easily identified as fully describing and enabling the same range to be divided into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed herein can be easily divided into a lower third, a middle third, and an upper third, etc. As will be understood by those skilled in the art, all languages ​​such as "up to", "at least", "greater than", "less than", etc. include the cited numbers and refer to ranges that can subsequently be divided into subranges as described above. Finally, as will be understood by those skilled in the art, ranges include each individual number. Thus, for example, a group having 1 to 3 units refers to a group having 1, 2, or 3 units. Similarly, a group having 1 to 5 units refers to a group having 1, 2, 3, 4, or 5 units, etc.

[0183] Furthermore, the claims should not be read as limited to the order or elements presented unless otherwise stated. Furthermore, use of the term "means for..." in any claim is intended to invoke 35 USC §112, ¶ 6 or parts-plus-function claim format, and any claim without the term "means for..." is not intended to be so.

[0184] Suitable processors include, by way of example, a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), an application specific standard product (ASSP), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), and / or a state machine.

[0185] The WTRU may be used in conjunction with a module, which may be implemented in hardware and / or software including the following components: Software Defined Radio (SDR) and other components such as a camera, video camera module, videophone, speakerphone, vibration device, speaker, microphone, TV transceiver, hands-free headset, keyboard, Bluetooth ® module, frequency modulation (FM) radio unit, near field communication (NFC) module, liquid crystal display (LCD) display unit, organic light emitting diode (OLED) display unit, digital music player, media player, video game player module, internet browser and / or any wireless local area network (WLAN) or ultra-wideband (UWB) module.

[0186] Although various embodiments have been described in terms of a communication system, it is contemplated that the system may be implemented in software on a microprocessor / general purpose computer (not shown). In certain embodiments, one or more of the functions of the various components may be implemented in software controlling a general purpose computer.

[0187] Furthermore, while the invention has been shown and described herein with reference to specific embodiments, the invention is not intended to be limited to the details shown. Rather, various modifications may be made to the details within the scope and range of equivalents of the claims without departing from the invention.

[0188] References

[0189] The following references may have been mentioned above and are incorporated herein by reference in their entirety.

[0190] [1]RP-213577, “New WID on Multi-carrier enhancements”.

Claims

1. A method implemented in a wireless transmit / receive unit (WTRU), the method comprising: receiving a first message, the first message comprising first configuration information indicating a fixed size format of downlink control information (DCI) and a plurality of cell identifiers, wherein each cell identifier of the plurality of cell identifiers is associated with a cell combination of a plurality of cells, and comprising second configuration information indicating sounding reference signal (SRS) resources associated with the plurality of cells for transmitting the SRS to a cell subset of the plurality of cells; receiving a DCI having the fixed size format, the DCI including first information indicating a cell identifier among the plurality of cell identifiers and including second information indicating a cell subset of the plurality of cells associated with the SRS resource; Based on the received DCI, determining a cell combination of the plurality of cells associated with the cell identifier; and Communications are sent via the combination of cells, and SRS is sent to the subset of cells. 2 . The method according to claim 1 , wherein the multiple cell identifiers are indicated in a first bit field of a fixed size of the DCI. 3 . The method of claim 1 , comprising monitoring one or more DCIs having a configured fixed size format. 4 . The method according to claim 1 , wherein the first configuration information indicates receiving one or more DCIs having the same fixed size format respectively for scheduling transmission to one or more cells. 5 . The method of claim 1 , wherein the subset of cells associated with the SRS resources is indicated in a second bit field of the DCI. 6 . The method of claim 5 , wherein the value of the second bit field indicates an SRS resource subset of the SRS resources associated with the cell subset.

7. A wireless transmit / receive unit (WTRU), the WTRU comprising a processor, a transmitter, a receiver and a memory and configured to: receiving a first message, the first message comprising first configuration information indicating a fixed size format of downlink control information (DCI) and a plurality of cell identifiers, wherein each cell identifier of the plurality of cell identifiers is associated with a cell combination of a plurality of cells, and comprising second configuration information indicating sounding reference signal (SRS) resources associated with the plurality of cells for transmitting the SRS to a cell subset of the plurality of cells; receiving a DCI having the fixed size format, the DCI including first information indicating a cell identifier among the plurality of cell identifiers and including second information indicating a cell subset of the plurality of cells associated with the SRS resource; Based on the received DCI, determining a cell combination of the plurality of cells associated with the cell identifier; and Communications are sent via the combination of cells, and SRS is sent to the subset of cells.

8. The WTRU of claim 7, wherein the plurality of cell identifiers are indicated in a first bit field of a fixed size of the DCI.

9. The WTRU of claim 7, the WTRU comprising monitoring one or more DCIs having a configured fixed size format.

10. The WTRU of claim 7, wherein the first configuration information indicates receiving one or more DCIs having the same fixed size format, respectively, for scheduling transmission to one or more cells.

11. The WTRU of claim 7, wherein the subset of cells associated with the SRS resources is indicated in a second bit field of the DCI.

12. The WTRU of claim 11, wherein the value of the second bit field indicates a subset of the SRS resources associated with the subset of cells.

Images