Method for configuring uplink cancellation indication for supplemental uplink carrier

Abstract

Aspects are presented that enable a UE to determine an uplink cancellation indication (ULCI) for cancelling uplink communications in a supplemental uplink (SUL). The UE receives, from the base station, a first configuration associated with a first block of the ULCI and associated with at least one of a SUL carrier and a non-supplemental uplink (NUL) carrier in the cell. The base station configures a second configuration for the UE, the second configuration associated with a second block of the ULCI and associated with a SUL carrier in the cell, and the UE determines the second configuration. The UE monitors the ULCI based on the first configuration and the second configuration.

Description

[0001] This application is a divisional application of a patent application with an international application date of December 4, 2020, an international application number of PCT / US2020 / 063470, a Chinese national application date of December 4, 2020, an application number of 202080077825.7, and an invention name of "Method for configuring an uplink cancellation indication for a supplementary uplink carrier".

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims the benefit of U.S. Provisional Application No. 62 / 943,768, filed on December 4, 2019, entitled “METHODS TO CONFIGURE UPLINK CANCELLATION INDICATION FOR SUPPLEMENTARY UPLINK CARRIERS,” and U.S. Patent Application No. 17 / 111,389, filed on December 3, 2020, entitled “METHODS TO CONFIGURE UPLINK CANCELLATION INDICATION FOR SUPPLEMENTARY UPLINK CARRIERS,” both of which are expressly incorporated herein by reference in their entirety. background Technical Field

[0005] The present disclosure relates generally to communication systems, and more particularly to a wireless communication system between a user equipment (UE) and a base station (BS).

[0006] introduction

[0007] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0008] These multiple access technologies have been adopted in various telecommunication standards to provide common protocols that enable different wireless devices to communicate at city, country, region, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is a part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5GNR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Some aspects of 5G NR can be based on 4G Long Term Evolution (LTE) standards. There is a need for further improvements to 5G NR technology. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies.

[0009] Overview

[0010] A brief summary of one or more aspects is given below to provide a basic understanding of such aspects. This summary is not an exhaustive overview of all conceived aspects, and is neither intended to identify the key or critical elements of all aspects nor to define the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description that will be presented later.

[0011] After the base station schedules resources for use by a UE when transmitting or receiving, for example, periodic mobile broadband (eMBB) data, the base station may be aware of a more urgent, higher priority transmission from another UE. For example, the other transmission may be from another ultra-reliable low latency communication (URLLC) latency-sensitive device. In such cases, the base station may reclaim resources previously scheduled to a first, lower priority UE for use by a second, higher priority UE. Specifically, if the previously scheduled resources are for downlink transmission, the base station may send a downlink cancellation indication (DLCI) (or downlink preemption indication) to the first UE in a DLCI opportunity to cancel at least a portion of the downlink transmission to the UE. Similarly, if the previously scheduled resources are for uplink transmission, the base station may send an uplink cancellation indication (ULCI) (or uplink preemption indication) to the first UE in a ULCI opportunity to cancel at least a portion of the uplink transmission from the UE. The base station may then allocate those reclaimed resources to higher priority, latency-sensitive UEs.

[0012] Additionally, the UE may be configured with two uplink carriers in the same uplink serving cell, namely a supplementary uplink (SUL) carrier and a non-supplementary uplink (NUL) carrier, and the base station may semi-statically or dynamically schedule uplink transmissions on the NUL or the SUL. When the base station sends a ULCI to the UE to cancel a previously scheduled uplink transmission, the UE may determine whether to apply the ULCI to cancel the uplink transmission on the NUL or the SUL. For example, the base station may configure the UE to monitor separate blocks or fields in the ULCI, where each block corresponds to a SUL carrier and / or a NUL carrier carrying an uplink transmission to be punctured in a given cell. The portion of the uplink transmission to be canceled is based on various parameters configured for the UE (e.g., carrier, time domain resource granularity, symbol, etc.).

[0013] Currently, a UE may receive a NUL configuration for a ULCI in a serving cell, including a corresponding position of a field in a DCI for NUL (e.g., a NUL positioning parameter), a number of bits for applying the ULCI to the NUL (e.g., a NUL size parameter), and an indication of time-frequency resources for the ULCI in the NUL. The UE may also receive a corresponding position of a field in a DCI for a SUL (e.g., a SUL positioning parameter) for a ULCI in a serving cell. However, under the current configuration, the UE is not configured with a corresponding SUL CI payload size parameter and a SUL time-frequency resource for the ULCI. Therefore, a UE monitoring a block in the ULCI corresponding to the SUL may not be able to determine a subset of SUL resources in which the ULCI is to be applied, as compared to the NUL. Therefore, it would be desirable to enable the UE to determine a subset of SUL resources for applying the ULCI. The various aspects presented herein enable the UE to: determine a SUL configuration (including a SUL CI payload size parameter and time-frequency resources), and determine a subset of resources for canceling uplink communications in the SUL.

[0014] In one aspect of the present disclosure, a method, a computer-readable medium, and a device are provided. The device may be a UE. The device may receive a first configuration associated with a first block of uplink cancellation indications (ULCI) from a base station, wherein the first configuration is associated with at least one of a supplementary uplink (SUL) carrier or a non-supplementary uplink (NUL) carrier in a cellular cell. The device may determine a second configuration associated with a second block of the ULCI, wherein the second configuration is associated with the SUL carrier in the cellular cell. The device may monitor the ULCI based on the first configuration and the second configuration.

[0015] In another aspect of the present disclosure, a method, a computer-readable medium, and a device are provided. The device may be a base station. The device may transmit a first configuration associated with a first block of uplink cancellation indications (ULCIs) to a user equipment (UE), wherein the first configuration is associated with at least one of a supplementary uplink (SUL) carrier or a non-supplementary uplink (NUL) carrier in a cell. The device configures a second configuration associated with a second block of the ULCI for the UE, wherein the second configuration is associated with the SUL carrier in the cell.

[0016] To achieve the foregoing and related ends, the one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and drawings set forth in detail certain illustrative features of the one or more aspects. However, these features are merely indicative of several of the various ways in which the principles of the various aspects may be employed, and this description is intended to cover all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0019] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0020] Figure 2B is a diagram illustrating an example of DL channels within a subframe according to various aspects of the present disclosure.

[0021] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0022] Figure 2D is a diagram illustrating an example of UL channels within a subframe according to various aspects of the present disclosure.

[0023] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0024] Figure 4 is a diagram illustrating allocation of resources for uplink transmission of a UE based on an uplink grant received from a base station.

[0025] Figure 5 is a diagram of an example serving cell including NUL and SUL carriers for a UE.

[0026] Figure 6 is an example frame structure of a portion of downlink control information for ULCI.

[0027] Figure 7is a diagram of an example call flow between a UE and a base station.

[0028] Figure 8 It is a flow chart of a wireless communication method of UE.

[0029] Fig. 9 It is a flow chart of a wireless communication method of a base station.

[0030] Fig.10 is a diagram illustrating an example of a hardware implementation for an example device.

[0031] Fig.11 is a diagram illustrating an example of a hardware implementation for an example device. Detailed Description

[0033] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. This detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid diluting such concepts.

[0034] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0035] As an example, an element, or any part of an element, or any combination of elements may be implemented as a "processing system" including one or more processors. Examples of processors include: microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout this disclosure. One or more processors in a processing system may execute software. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether it is described in software, firmware, middleware, microcode, hardware description languages, or other terms.

[0036] Accordingly, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, these functions may be stored or encoded on a computer-readable medium as one or more instructions or codes. Computer-readable media include computer storage media. Storage media may be any available medium that can be accessed by a computer. As an example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, a combination of computer-readable media of the above types, or any other medium that may be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0037] Figure 1 1 is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.

[0038] Base stations 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with EPC 160 via a backhaul link 132 (e.g., an S1 interface). Base stations 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with core network 190 via a backhaul link 184. Base stations 102 may perform one or more of the following functions, among other functions: delivery of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of alert messages. The base stations 102 may communicate with each other directly or indirectly (eg, through the EPC 160 or the core network 190) via a backhaul link 134 (eg, an X2 interface). The backhaul link 134 may be wired or wireless.

[0039] Base stations 102 may communicate wirelessly with UEs 104. Each base station 102 may provide communication coverage for a corresponding geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved B node (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). A communication link 120 between a base station 102 and a UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from the UE 104 to the base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from the base station 102 to the UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. These communication links may be through one or more carriers. The base station 102 / UE 104 may use spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) bandwidth for each carrier allocated in the carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0040] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0041] The wireless communication system may further include a Wi-Fi access point (AP) 150 communicating with a Wi-Fi station (STA) 152 in the 5 GHz unlicensed spectrum via a communication link 154. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) prior to communication to determine whether the channel is available.

[0042] The small cell 102' may operate in a licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 102' may employ NR and use the same 5 GHz unlicensed spectrum as used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum may boost the coverage of the access network and / or increase the capacity of the access network.

[0043] Whether a small cell 102' or a large cell (e.g., a macro base station), the base station 102 may include an eNB, a gB node (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in traditional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near mmW frequencies to communicate with UE 104. When gNB 180 operates in mmW or near mmW frequencies, gNB 180 may be referred to as a mmW base station. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 mm and 10 mm. The radio waves in this band may be referred to as millimeter waves. Near mmW can be extended down to 3 GHz frequencies with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, which is also referred to as centimeter waves. Communications using mmW / near mmW radio frequency bands (e.g., 3 GHz–300 GHz) have extremely high path loss and short range. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short range.

[0044] Base station 180 may transmit beamformed signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 182". UE 104 may also transmit beamformed signals to base station 180 in one or more transmit directions. Base station 180 may receive beamformed signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of base station 180 / UE 104. The transmit direction and receive direction of base station 180 may be the same or may be different. The transmit direction and receive direction of UE 104 may be the same or may be different.

[0045] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may be in communication with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area that broadcasts a specific service, and may be responsible for session management (start / stop) and for collecting eMBMS-related charging information.

[0046] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. AMF 192 may be in communication with a unified data management (UDM) 196. AMF 192 is a control node that handles signaling between UE 104 and the core network 190. In general, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are delivered through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 is connected to IP services 197. IP services 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services.

[0047] A base station may also be referred to as a gNB, a Node B, an evolved Node B (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmission reception point (TRP), or some other suitable term. The base station 102 provides an access point to the EPC 160 or the core network 190 for the UE 104. Examples of UE 104 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet device, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a health care device, an implant, a sensor / actuator, a display, or any other similar functional device. Some UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

[0048] Referring again to 1, in certain aspects, the UE 104 may include a SUL determination component 198 configured to: receive a first configuration associated with a first block of uplink cancellation indications (ULCIs) from a base station, wherein the first configuration is associated with at least one of a supplementary uplink (SUL) carrier or a non-supplementary uplink (NUL) carrier in a cell; determine a second configuration associated with a second block of the ULCI, wherein the second configuration is associated with the SUL carrier in the cell; and monitor the ULCI based on the first configuration and the second configuration.

[0049] Referring again to 1, in certain aspects, the base station 180 may include a SUL configuration component 199 configured to: transmit a first configuration associated with a first block of uplink cancellation indications (ULCI) to a user equipment (UE), wherein the first configuration is associated with at least one of a supplementary uplink (SUL) carrier or a non-supplementary uplink (NUL) carrier in a cell; and configure a second configuration associated with a second block of the ULCI for the UE, wherein the second configuration is associated with the SUL carrier in the cell. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0050] Figure 2A200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. Figure 2C 250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D 280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure can be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within the subcarrier set are dedicated to DL or UL; or can be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within the subcarrier set are dedicated to both DL and UL. Figure 2A , 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (mostly DL) and subframe 3 is configured with slot format 1 (all UL), where D is DL, U is UL, and F is for flexible use between DL / UL. Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The UE is configured with the slot format (dynamically configured through DL control information (DCI) or semi-statically / statically configured through radio resource control (RRC) signaling) via the received slot format indicator (SFI). Note that the following description also applies to the 5G NR frame structure for TDD.

[0051] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include mini-slots, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. The symbols on the DL may be cyclic prefix (CP) orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power-limited scenarios; limited to single stream transmission). The number of time slots within a subframe is based on the time slot configuration and parameter design. For slot configuration 0, different parameter designs μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For slot configuration 1, different parameter designs 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Accordingly, for slot configuration 0 and parameter design μ, there are 14 symbols per slot and 2 per subframe. μ time slots. The subcarrier spacing and symbol length / duration vary depending on parameter design. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter design 0 to 4. Thus, parameter design μ=0 has a subcarrier spacing of 15kHz, while parameter design μ=4 has a subcarrier spacing of 240kHz. Figures 2A-2D An example of a slot configuration 0 with 14 symbols per slot and a parameter design μ=2 and 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency division multiplexed (see Figure 2B ). Each BWP may have a specific parameter design.

[0052] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also called a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a number of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0053] like Figure 2AAs illustrated in FIG, some REs carry reference (pilot) signals (RS) for UEs. RSs may include demodulation RSs (DM-RSs) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RSs) for channel estimation at the UE. RSs may also include beam measurement RSs (BRSs), beam refinement RSs (BRRSs), and phase tracking RSs (PT-RSs).

[0054] Figure 2B An example of various DL channels within a subframe of a frame is illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising 6 RE groups (REGs), each REG comprising 4 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identity. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth, and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as a system information block (SIB)), and paging messages.

[0055] As in Figure 2CAs explained in , some REs carry DM-RSs for channel estimation at the base station (indicated as R for one specific configuration, but other DM-RS configurations are possible). The UE may transmit DM-RSs for the physical uplink control channel (PUCCH) and DM-RSs for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the first or first two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether a short PUCCH or a long PUCCH is transmitted and on the specific PUCCH format used. The UE may transmit a sounding reference signal (SRS). The SRS may be transmitted in the last symbol of the subframe. The SRS may have a comb structure, and the UE may transmit the SRS on one of the comb teeth. The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0056] Figure 2D An example of various UL channels within a subframe of an illustration frame. The PUCCH may be located at a location as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and hybrid automatic repeat request (HARQ) acknowledgement (HARQ-ACK) information (ACK) / negative ACK (NACK) feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0057] Figure 33 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a media access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration of UE measurement reports; PDCP layer functionality associated with header compression / decompression, security (ciphering, cipher decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0058] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time domain and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine coding and modulation schemes and for spatial processing. The channel estimates may be derived from reference signals and / or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0059] At the UE 350, each receiver 354RX receives a signal through its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If there are multiple spatial streams destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then transforms the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the signal constellation point most likely transmitted by the base station 310. These soft decisions can be based on the channel estimates calculated by the channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted on the physical channel by the base station 310. These data and control signals are then provided to the controller / processor 359 which implements layer 3 and layer 2 functionality.

[0060] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, cipher interpretation, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0061] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto TBs, demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0062] Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by a TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0063] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

[0064] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, cipher decoding, header decompression, control signal processing to recover IP packets from the UE 350. The IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0065] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 The 198 combined aspects.

[0066] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 The 199 combines all aspects.

[0067] In some aspects of wireless communication, after a base station schedules resources for use by a UE when transmitting or receiving, for example, periodic mobile broadband (eMBB) data, the base station may be aware of a more urgent, higher priority transmission from another UE. For example, the other transmission may be from another ultra-reliable low latency communication (URLLC) latency-sensitive device. In such cases, the base station may reclaim resources previously scheduled to a first, lower priority UE for use by a second, higher priority UE. Specifically, if the previously scheduled resources are for downlink transmission, the base station may send a downlink cancellation indication (DLCI) (or downlink preemption indication) to the first UE in a DLCI opportunity to cancel at least a portion of the downlink transmission to the UE. Similarly, if the previously scheduled resources are for uplink transmission, the base station may send an uplink cancellation indication (ULCI) (or uplink preemption indication) to the first UE in a ULCI opportunity to cancel at least a portion of the uplink transmission from the UE. The base station may then allocate those reclaimed resources to higher priority, latency-sensitive UEs.

[0068] For example, Figure 4The explanation illustrates an example of a diagram 400 of allocation of resources for uplink transmission 402 for a UE based on an uplink grant 404 received from a base station. If the base station later learns that a latency-sensitive UE utilizes at least a portion 406 of the resources to be allocated for uplink transmission 402 for URLLC data or other higher priority data, the base station may transmit a ULCI 408 to the UE in a ULCI opportunity 410, indicating that the portion 406 previously granted for uplink transmission will be punctured for use by the latency-sensitive UE. As a result, the UE may cancel its uplink transmission during portion 406 for use by the other UE.

[0069] Additionally, a UE may be configured with two uplink carriers in the same uplink serving cell, a supplementary uplink (SUL) carrier and a non-supplementary uplink (NUL) carrier, and the base station may semi-statically or dynamically schedule uplink transmissions on the NUL or the SUL. Figure 5 An example serving cell 500 is illustrated in which a base station 502 can communicate with a UE 504 on a NUL carrier 506 and a SUL carrier 508. The NUL carrier 506 and the SUL carrier 508 can be located at different frequencies, for example, the NUL carrier 506 can be located at a higher frequency than the SUL carrier 508. The NUL carrier 506 and the SUL carrier 508 can have different ranges, such as Figure 5 . The base station 502 may send an uplink grant to the UE 504 on either the NUL or the SUL; the UE may not be able to transmit uplink communications on both the NUL and the SUL. For example, in a serving cell, the UE may be dynamically or semi-statically instructed by the base station to transmit PUSCH, SRS, PUCCH, or other uplink communications on either the NUL or the SUL.

[0070] When the base station sends a ULCI to the UE to cancel a previously scheduled uplink transmission, the UE may determine whether to apply the ULCI to cancel the uplink transmission on the NUL or SUL. For example, the base station may configure the UE to monitor separate blocks or fields in the ULCI, where each block corresponds to a SUL carrier and / or a NUL carrier carrying an uplink transmission to be punctured in a given cell. Moreover, the ULCI may include multiple blocks. The UE may be configured with the length of the ULCI in the DCI and may be configured to monitor a block corresponding to a SUL carrier, a block corresponding to a NUL carrier, or a block corresponding to both the SUL and NUL carriers. The UE may apply the ULCI (e.g., cancel at least a portion of the uplink transmission) on the corresponding carrier (e.g., SUL or NUL) indicated in each configured block.

[0071] Figure 6An example frame structure 600 of a DCI including a ULCI 602 is illustrated. The ULCI includes a plurality of blocks 604 that may be configured for a particular cell. Each block 604 may correspond to at least one bit associated with a time domain resource granularity (e.g., number of symbols), where a '0' may indicate not to cancel an uplink transmission and a '1' may indicate to direct an uplink transmission (e.g., apply ULCI) or vice versa. The blocks 604 may be configured to indicate which carrier (SUL or NUL) and the portion of the uplink transmission on which the resources / symbols are to be punctured or cancelled. In the example of Figure 6 In one example shown, the base station may configure at least one block of ULCI for the UE. Figure 6 In the embodiment of the present invention, the UE may be configured to receive the ULCI in block 2 606 and block 6 608 of the ULCI 606 structure, where block 2 606 may be configured to correspond to the NUL and block 6 608 may be configured to correspond to the SUL (or vice versa). Figure 6 Only a single example is illustrated; any block in the ULCI 602 may be configured (e.g., configured with 0 or 1), and any of the blocks may be configured to correspond to the NUL carrier or the SUL carrier of a given cell. For example, the UE may apply the ULCI to the NUL carrier or the SUL carrier based on which of the blocks 606, 608 receives the ULCI instruction to cancel the transmission. In another example, the UE may apply the ULCI received in a single block to both the NUL carrier and the SUL carrier.

[0072] When the UE receives an instruction to cancel uplink transmission in blocks 606 and / or 608, the UE may apply the ULCI to cancel at least a portion of the uplink transmission on the carrier (SUL and / or NUL) and the resources indicated in these blocks. The portion of the uplink transmission to be canceled is based on various parameters configured for the UE (e.g., carrier, time domain resource granularity, symbol, etc.). For example, if the UE is configured to receive a ULCI for a NUL carrier in block 606 and a ULCI for a SUL carrier in block 608 based on various parameters, the UE may cancel transmission on the NUL carrier when the ULCI instruction is received in block 606. When the ULCI instruction is received in block 608, the UE may cancel transmission on the SUL carrier.

[0073] As indicated above, for each serving cell, the UE may be configured with various parameters to apply the ULCI. In one example, the UE may be configured with the corresponding position of the field for NUL in the DCI. For example, the parameter may be a NUL positioning parameter in DCI format 2_4 (e.g., positioninDCI or another name). The UE may also be configured with the corresponding position of the field for NUL in the DCI. For example, the parameter may be a SUL positioning parameter (e.g., positioninDCI-forSUL or another name). Thus, in Figure 6 In the example of , the NUL positioning parameter may correspond to block 2 606, and the SUL positioning parameter may correspond to block 6 608. In another example, the UE may be configured to apply the number of bits of the ULCI. For example, the parameter may be a NUL size parameter (e.g., Cl-PayloadSize or another name). Figure 6 , for example, the NUL size parameter of block 2 606 can be 9 bits (or another number). In a further example, the UE can be configured with an indication of time-frequency resources for ULCI. For example, the parameter may be a NUL indication of time domain resources and frequency domain resources (e.g., timeFrequencyRegion or another name). The NUL indication may include, for example, a set of frequency domain resources on the serving cell, the number of consecutive codewords (excluding SS / PBCH blocks and DL codewords for receiving indicated by a time division duplex configuration [e.g., tdd-UL-DL-ConfigurationCommon or another name]), and the time domain granularity of each bit in the field (e.g., timeGranularityforCl or another name). Reference Figure 6And assuming a 9-bit NUL size parameter in this example, the NUL indication may indicate, for example, that block 2 606 has a 3-bit NUL time domain granularity, a 3-symbol NUL time duration, and a 3-subcarrier NUL frequency duration. In some aspects, if both the ULCI and the intra-UE priority indicator are configured for a given UE, an uplink cancellation priority field or parameter (e.g., uplinkCancellationPriority or another name) may configure uplink cancellation behavior. If the field or parameter is present, the ULCI may apply to UL transmissions that are indicated / configured as a low priority level. If the field or parameter is not present, the ULCI may apply to UL transmissions regardless of the priority level of the UL transmission. In some instances, the parameter may be configured for NUL. That is, a separate parameter for SUL (e.g., uplinkCancellationPriority-For-SUL or another name) may be configured to indicate uplink cancellation priority on the SUL. If this parameter is not configured for SUL, the UE may follow the same behavior as for NUL (ie, based on the existing RRC parameter uplinkCancellationPriority).

[0074] Based on the above, the UE may receive a NUL configuration (e.g., NUL positioning, size, and time-frequency resources) for the ULCI in the serving cell, and a SUL positioning for the ULCI in the serving cell. For example, a UE configured with the aforementioned example parameters may monitor block 2 606, and upon receiving block 2 606, may apply the ULCI across a NUL resource subset spanning a number of symbols (e.g., 3 symbols) and a number of subcarriers (e.g., 3 subcarriers) in the serving cell. However, under the current configuration, the UE may not be configured with a cancel indication (CI) payload size (e.g., field bit width) for the SUL, and the SUL time-frequency resources. Therefore, compared to the NUL, a UE monitoring block 6 608, for example, upon receiving block 6 608, may not be able to determine which SUL resource subset to apply the ULCI. The UE may also be unable to determine how many bits are included in the block corresponding to the SUL in the ULCI. Therefore, it is desirable to enable the UE to determine a SUL resource subset for applying the ULCI.

[0075] The various aspects presented herein enable the UE to: determine the SUL configuration (including SUL CI payload size parameters and time-frequency resources), determine a resource subset for canceling uplink communication in the SUL. For example, if the UE is configured with and receives the SUL positioning parameters described above from the base station, the UE may apply the various aspects described below to determine the SUL configuration for the ULCI for one or more aspects. Otherwise, if the UE is not configured with the SUL positioning parameters, the UE may refrain from determining the SUL parameters and monitoring the ULCI for the SUL.

[0076] The UE may determine the SUL configuration according to various aspects. In a first aspect, the base station may configure a separate time domain / frequency domain and number of bits for the SUL in a configuration separate from the time domain / frequency domain and number of bits for the NUL. For example, the base station may provide the UE with a SUL CI payload size parameter (e.g., Cl-PayloadSize-forSUL (Cl payload size for SUL) or another name) and a SUL indication of time-frequency resources (e.g., timefrequencyRegion-forSUL (time-frequency domain for SUL) or another name) as additional RRC parameters for SUL configuration. Therefore, referring to Figure 6 In addition to the NUL size parameter corresponding to block 2 606 received from the base station, the UE may also determine the SULCI payload size parameter corresponding to block 6 608 based on the RRC parameters received from the base station. Similarly, in addition to the RRC parameters corresponding to the NUL (e.g., block 2 606), the UE may also determine the SUL time-frequency resources corresponding to block 6 608 based on one or more RRC parameters received from the base station.

[0077] In this first aspect, additional RRC parameters for SUL configuration may be configured under the same parent RRC parameters (e.g., ci-ConfigurationPerServingCell or another name) for NUL configuration. For example, NUL configuration parameters (e.g., NUL positioning, size, and time-frequency resources) and SUL configuration parameters (e.g., SUL positioning and SUL CI payload size and time-frequency resources) may be provided to the UE under a common parent RRC parameter.

[0078] In a second aspect, the UE may not receive additional RRC parameters from the base station for the SUL. Instead, the UE may determine the SUL configuration parameters based at least in part on the NUL configuration parameters. In one example, the SUL and NUL may share the same number of bits. For example, the NUL field and the SUL field in the ULCI may be configured to have the same bit width, both of which may follow the existing NUL size parameter (e.g., Cl-PayloadSize or another name). Therefore, referring to Figure 6 , the UE can determine that the SUL CI payload size parameter (e.g., number of bits) corresponding to block 6608 is the same as the NUL size parameter configured for block 2 606.

[0079] In another example, the frequency domain resources covered by the ULCI for the SUL may be configured to correspond to the entire active uplink bandwidth part (BWP) configured for the UE in the SUL. Alternatively, the frequency domain resources for the SUL may be configured to correspond to the entire SUL bandwidth. Figure 6 , the UE may determine that the frequency domain resource set associated with block 608 for SUL corresponds to a configured BWP (e.g., an active BWP) or a configured SUL bandwidth for SUL. In contrast, frequency domain resources configured for NUL (e.g., as provided by parameter timeFrequencyRegion or another name) may not be used for SUL because NUL and SUL occupy different frequencies.

[0080] In yet another example, the time domain resources covered by the SUL may be configured to have a duration equal in time to that of the NUL. Figure 6 , the UE may determine that the duration of the SUL time domain resources configured for block 6 608 is equal to the duration of the NUL time domain resources configured for block 2 606. Additionally, the UE may determine the SUL time domain resources based on the UE's monitoring periodicity of the ULCI. For example, when the UE's monitoring periodicity of the ULCI is greater than or equal to one time slot (e.g., the UE monitors the ULCI in the SUL every one or more time slots), the duration of the SUL time domain resources may be equal to the monitoring periodicity. Therefore, in Figure 6 In the example of , if the UE monitors block 6 608 every two time slots, the duration of the SUL time domain resources may also be configured as two time slots. However, when the UE's monitoring periodicity for ULCI is less than one time slot, the number of symbols configured for ULCI (e.g., as provided by parameter timeFrequencyRegion or another name) may apply to both NUL and SUL if NUL and SUL are time-overlapped. For example, in Figure 6In the example of , if the UE monitors block 6 608 every five time slots, the duration of the SUL time domain resources (and NUL time domain resources) may also be configured as five time slots. The number of symbols may be based on a subcarrier spacing (SCS) (eg, in units of SCS) used for downlink transmissions.

[0081] In an additional example, the same time domain granularity may apply to both SUL and NUL. For example, the SUL time domain granularity may be configured to be the same as the configured NUL time domain granularity (e.g., timeGranularityforCl or another name). Figure 6 , the UE may determine that the SUL time domain granularity associated with block 6 608 and the NUL time domain granularity associated with block 2 606 are the same.

[0082] In a third aspect, the UE may determine the SUL configuration parameters based on whether an additional RRC parameter for ULCI in the SUL is received from the base station. For example, if each of the SUL CI payload size parameter (e.g., Cl-PayloadSize-forSUL or another name) and the SUL indication of the time-frequency resource (e.g., timeFrequencyRegion-forSUL or another name) is configured by the base station and received by the UE, the UE may determine the SUL configuration parameters according to the received RRC parameters, as described above (with respect to the first aspect). Otherwise, if the UE does not receive certain RRC parameters, the UE may determine the corresponding SUL configuration parameters according to the NUL configuration parameters, as described above (with respect to the second aspect). The RRC parameters may include, for example, frequency domain resources, number of bits, total duration, time domain granularity, and / or uplink cancellation priority.

[0083] Figure 7 An example call flow diagram 704 between UE 700 and base station 702 is illustrated. At block 706, the base station may Figure 6 The third aspect described is to configure rules for the UE to determine SUL configuration parameters for ULCI. For example, according to the above reference Figure 6 In the first aspect described, the base station may configure the UE to determine the SUL configuration according to a separate RRC parameter configured for the SUL carrier and transmitted to the UE. Figure 6 In the second aspect described, the base station may configure the UE to determine the SUL configuration parameters based on the NUL configuration parameters without configuring separate RRC parameters for ULCI in the SUL. After configuring these rules, the base station may transmit configuration rules 708 for the UE to use to determine the SUL configuration. Alternatively, the UE may be pre-configured with these rules.

[0084] At block 710, the base station may configure NUL configuration parameters associated with a block of ULCI. For example, the base station may configure the corresponding position of the field for NUL in DCI (e.g., NUL positioning parameter), the number of bits for applying ULCI (e.g., NUL size parameter), and the indication of time-frequency resources for ULCI (e.g., NUL indication for time domain and frequency domain resources) (including the set of frequency domain resources on the serving cell, the number of consecutive symbols, and the time domain granularity of each bit in the field) for the UE. The base station may then transmit the NUL configuration parameters 712 to the UE 702.

[0085] At block 714, the base station may configure SUL configuration parameters associated with another block of ULCI. For example, the base station may configure separate time / frequency domains (e.g., SUL indication of time-frequency resources) and number of bits for SUL (e.g., SUL CI payload size parameter) as additional RRC parameters separate from the time / frequency domain and number of bits for NUL. The base station may transmit the SUL configuration 716 including the additional RRC parameters to the UE 702.

[0086] Alternatively, the base station may not configure additional RRC parameters for the SUL. Instead, in block 714, the base station may configure one or more SUL configuration parameters based on the NUL configuration parameters. In one example, the NUL field and the SUL field in the ULCI may be configured to have the same bit width. In another example, the frequency domain resources covered by the ULCI for the SUL may be configured to correspond to the entire active uplink bandwidth part (BWP) configured in the SUL for the UE, or to the entire SUL bandwidth. In yet another example, the time domain resources covered by the SUL may be configured to have a duration that is equal in time to the duration of the NUL. In an additional example, the SUL time domain granularity may be configured to be the same as the configured NUL time domain granularity.

[0087] At block 718, after the UE 702 receives the NUL configuration 712 associated with one block of ULCI, the UE may determine the SUL configuration associated with another block of ULCI. At block 720, the UE may monitor the ULCI based on the NUL configuration 712 and the SUL configuration. The UE 702 may determine the SUL configuration based on the configuration rule 708 (e.g., preconfigured or provided by the base station 704) according to the first aspect or the second aspect described above. For example, if the UE receives a SUL configuration 716 including additional RRC parameters associated with the SUL, the UE may monitor the ULCI and apply the ULCI to the SUL based on those separate RRC parameters (e.g., SUL indication of time-frequency resources, and SUL CI payload size parameters). Alternatively, if the UE does not receive the SUL configuration 716, or does not receive some parameters in the SUL configuration 716, the UE may monitor the ULCI and apply the ULCI to the SUL based on the corresponding parameters in the NUL configuration 712. For example, the UE may determine that a SUL CI payload size parameter is the same as a NUL size parameter, determine that a set of frequency domain resources corresponds to a configured BWP for the SUL or a configured SUL bandwidth, determine that a duration of the SUL time domain resources is equal to a duration of the NUL time domain resources, or determine that a SUL time domain granularity is the same as a NUL time domain granularity.

[0088] Figure 8 800 is a flow chart of a method of wireless communication. The method may be performed by a UE or a component of a UE (e.g., UE 104, 350, 504, 702; device 1002). Optional aspects are illustrated in dashed lines. The method allows the UE to determine a SUL configuration that determines a subset of resources for canceling uplink communications in the SUL. The methods described herein may provide several benefits, such as improved communication signaling, resource utilization, and / or power savings.

[0089] At 802, the UE may receive a first configuration associated with a first block of ULCI from a base station, wherein the first configuration is associated with at least one of a SUL carrier or a NUL carrier in a cell. Figure 7 , UE 702 may receive NUL configuration 712 associated with a block of ULCI. In addition, 802 may be Fig.10 1040 execution.

[0090] At 804, the UE may determine a second configuration associated with a second block of the ULCI, wherein the second configuration is associated with the SUL carrier in the cell. Figure 7At block 718, after the UE 702 receives the NUL configuration 712 associated with one block of ULCI, the UE may determine the SUL configuration associated with another block of ULCI. Fig.10 1040 execution.

[0091] In a first aspect, the second configuration may be determined based on an RRC parameter received from the base station and associated with the SUL carrier. The first configuration may include a NUL size parameter indicating a first number of bits associated with a first block, and a NUL indication of a time-frequency resource associated with the first block. The second configuration may include a SUL CI payload size parameter indicating a second number of bits associated with a second block, and a SUL indication of a time-frequency resource associated with the second block. The SUL CI payload size parameter and the SUL indication may be RRC parameters separate from the NUL size parameter and the NUL indication. The first configuration and the second configuration may be configured under the same (parent) RRC parameters.

[0092] In a second aspect, a second configuration may be determined based on a first configuration received from a base station. In one example, the first configuration may include a NUL size parameter indicating a first number of bits associated with the first block, the second configuration may include a SUL CI payload size parameter indicating a second number of bits associated with the second block, and the SUL CI payload size parameter may be the same as the NUL size parameter. In another example, the second configuration may include a set of SUL frequency resources, and the SUL frequency resources may include one of a BWP on the SUL or a bandwidth of the SUL. In a further example, the first configuration may include a first indication of a NUL time domain resource associated with the first block, the second configuration may include a second indication of a SUL time domain resource associated with the second block, and the NUL duration of the NUL time domain resource may be the same as the SUL duration of the SUL time domain resource. When the ULCI monitoring periodicity of the UE is at least one time slot, the SUL duration may be equal to the ULCI monitoring periodicity; and when the ULCI monitoring periodicity is less than one time slot, the SUL duration may be equal to the configured number of symbols. In an additional example, the first configuration may include a NUL time domain granularity associated with the first block, the second configuration may include a SUL time domain granularity associated with the second block, and the NUL time domain resource granularity may be the same as the SUL time domain granularity. In another example, the first configuration may include a first indication of an uplink de-prioritization on the NUL associated with the first block, the second configuration may include a second indication of an uplink de-prioritization on the SUL associated with the second block, and the uplink de-prioritization on the NUL may be the same as the uplink de-prioritization on the SUL.

[0093] In a third aspect, when the base station configures the RRC parameters, the second configuration may be determined according to the RRC parameters associated with the SUL carrier, and when the RRC parameters are not configured, the second configuration may be determined based on the first configuration. The RRC parameters associated with the SUL carrier may include at least one of: a set of frequency domain resources, a number of bits, a total duration of time domain resources, or a time domain granularity.

[0094] At 806, the UE may monitor the ULCI based on the first configuration and the second configuration. The ULCI may be monitored based on the second configuration, the second configuration being based on a radio resource control (RRC) parameter received from the base station. For example, referring to Figure 7 At block 720, the UE may monitor the ULCI based on the NUL configuration 712 and the SUL configuration. Figure 6 In an example of , the UE may monitor block 2 606 based on the NUL positioning parameters received in NUL configuration 712, and apply the ULCI across the NUL resource subset based on other NUL configuration parameters upon receiving block 2 606. Similarly, the UE may monitor block 6 608 based on the SUL positioning parameters received in SUL configuration 716, and apply the ULCI across the SUL resource subset based on the determined SUL configuration parameters upon receiving block 6 608. Alternatively, if the UE does not receive the SUL positioning parameters, the UE may refrain from determining the SUL parameters and monitoring the ULCI for the SUL. In addition, 806 may be performed by Fig.10 1040 execution.

[0095] Fig. 9 900 is a flow chart of a method of wireless communication. The method may be performed by a base station or a component of a base station (e.g., base station 102 / 180, 310, 704, 502, 704; device 1102). Optional aspects are illustrated in dashed lines. The method allows the base station to configure the UE to determine a SUL configuration that determines a subset of resources for canceling uplink communications in the SUL. The methods described herein may provide several benefits, such as improved communication signaling, resource utilization, and / or power savings.

[0096] At 902, the base station transmits a first configuration associated with a first block of ULCI to a UE, wherein the first configuration is associated with at least one of a SUL carrier or a NUL carrier in a cell. Figure 7 , the base station 704 may transmit a NUL configuration 712 associated with a block of ULCI to the UE 702. In addition, 902 may be Fig.11 1140 is executed in.

[0097] At 904, the base station configures a second configuration associated with a second block of the ULCI for the UE, wherein the second configuration is associated with the SUL carrier in the cell. Figure 7 , at block 714, the base station configures SUL configuration parameters associated with another block of ULCI. In addition, 904 may be performed by Fig.11 1140 is executed in.

[0098] In a first aspect, a second configuration includes an RRC transmitted to a UE and associated with a SUL carrier. The first configuration may include a NUL size parameter indicating a first number of bits associated with a first block, and a NUL indication of a time-frequency resource associated with the first block. The second configuration may include a SUL CI payload size parameter indicating a second number of bits associated with a second block, and a SUL indication of a time-frequency resource associated with the second block. The SUL CI payload size parameter and the SUL indication may be RRC parameters separate from the NUL size parameter and the NUL indication. The first configuration and the second configuration may be configured under the same (parent) RRC parameters.

[0099] In a second aspect, the second configuration may be configured based on the first configuration transmitted to the UE. In one example, the first configuration may include a NUL size parameter indicating a first number of bits associated with the first block, the second configuration may include a SUL CI payload size parameter indicating a second number of bits associated with the second block, and the SUL CI payload size parameter may be the same as the NUL size parameter. In another example, the second configuration may include a set of SUL frequency resources, and the SUL frequency resources may include one of a BWP on the SUL or a bandwidth of the SUL. In a further example, the first configuration may include a first indication of a NUL time domain resource associated with the first block, the second configuration may include a second indication of a SUL time domain resource associated with the second block, and the NUL duration of the NUL time domain resource may be the same as the SUL duration of the SUL time domain resource. When the ULCI monitoring periodicity of the UE is at least one time slot, the SUL duration may be equal to the ULCI monitoring periodicity; and when the ULCI monitoring periodicity is less than one time slot, the SUL duration may be equal to the configured number of symbols. In an additional example, the first configuration may include a NUL time domain granularity associated with the first block, the second configuration may include a SUL time domain granularity associated with the second block, and the NUL time domain resource granularity may be the same as the SUL time domain granularity. In another example, the first configuration may include a first indication of an uplink de-prioritization on the NUL associated with the first block, the second configuration may include a second indication of an uplink de-prioritization on the SUL associated with the second block, and the uplink de-prioritization on the NUL may be the same as the uplink de-prioritization on the SUL.

[0100] In a third aspect, at 906, the base station may configure the UE to: determine the second configuration based on the RRC parameter when the base station configures the RRC parameter associated with the SUL carrier. At 908, the base station may configure the UE to determine the second configuration based on the first configuration when the RRC parameter is not configured. The RRC parameter associated with the SUL carrier may include at least one of: a set of frequency domain resources, a number of bits, a total duration of time domain resources, or a time domain granularity. For example, referring to Figure 7 At block 706, the base station may configure rules for the UE to determine SUL configuration parameters for the ULCI. After configuring these rules, the base station may transmit configuration rules 708 for the UE to determine the SUL configuration. Alternatively, the UE may be pre-configured with these rules. In addition, 906 may be performed by Fig.11 1140 in the implementation. 908 can also be performed by Fig.11 1140 is executed in.

[0101] Fig.101 is a diagram 1000 illustrating an example of a hardware implementation of a device 1002. The device 1002 is a UE and includes a cellular baseband processor 1004 (also referred to as a modem) coupled to a cellular RF transceiver 1022 and one or more subscriber identity modules (SIM) cards 1020, an application processor 1010 coupled to a secure digital (SD) card 1006 and a screen 1008, a Bluetooth module 1012, a wireless local area network (WLAN) module 1014, a global positioning system (GPS) module 1016, and a power supply 1018. The cellular baseband processor 1004 communicates with the UE 104 and / or BS 102 / 180 through the cellular RF transceiver 1022. The cellular baseband processor 1004 may include a computer-readable medium / memory. The computer-readable medium / memory may be non-transitory. The cellular baseband processor 1004 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor 1004, causes the cellular baseband processor 1004 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1004 when executing the software. The cellular baseband processor 1004 further includes a receiving component 1030, a communication manager 1032, and a transmitting component 1034. The communication manager 1032 includes one or more of the illustrated components. The components within the communication manager 1032 may be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1004. The cellular baseband processor 1004 may be a component of the UE 350 and may include a memory 360 and / or at least one of the following: a TX processor 368, an RX processor 356, and a controller / processor 359. In one configuration, the device 1002 may be a modem chip and include only the baseband processor 1004, and in another configuration, the device 1002 may be the entire UE (e.g., see Figure 3 350) and includes the aforementioned additional modules of device 1002.

[0102] The communication manager 1032 includes a determining component 1040 configured to receive a first configuration associated with a first block of uplink cancellation indications (ULCIs) from a base station, wherein the first configuration is associated with at least one of a supplementary uplink (SUL) carrier or a non-supplementary uplink (NUL) carrier in a cell, e.g., as described in conjunction with Figure 8 The determining component 1040 is also configured to determine a second configuration associated with a second block of the ULCI, wherein the second configuration is associated with the SUL carrier in the cellular cell, for example, as described in conjunction with Figure 8 The determining component 1040 is further configured to monitor the ULCI based on the first configuration and the second configuration, for example, as combined with Figure 8 As described in 806.

[0103] The apparatus may include executing Figure 7 and 8 The additional components of each box of the algorithm in the preceding flowchart. Thus, Figure 7 and 8 Each block in the aforementioned flow chart may be performed by a component and the device may include one or more of these components. These components may be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0104] In one configuration, the device 1002, and in particular the cellular baseband processor 1004, includes: a means for receiving a first configuration associated with a first block of uplink cancellation indications (ULCI) from a base station, wherein the first configuration is associated with at least one of a supplementary uplink (SUL) carrier or a non-supplementary uplink (NUL) carrier in a cellular cell; a means for determining a second configuration associated with a second block of the ULCI, wherein the second configuration is associated with a SUL carrier in the cellular cell; and a means for monitoring the ULCI based on the first configuration and the second configuration. The aforementioned means may be one or more of the aforementioned components in the device 1002 configured to perform the functions recited by the aforementioned means. As described above, the device 1002 may include a TX processor 368, an RX processor 356, and a controller / processor 359. As such, in one configuration, the aforementioned means may be a TX processor 368, an RX processor 356, and a controller / processor 359 configured to perform the functions recited by the aforementioned means.

[0105] Fig.111100 is an example of a hardware implementation of an illustrated device 1102. The device 1102 is a base station (BS) and includes a baseband unit 1104. The baseband unit 1104 can communicate with the UE 104 through a cellular RF transceiver 1122. The baseband unit 1104 may include a computer-readable medium / memory. The baseband unit 1104 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the baseband unit 1104, enables the baseband unit 1104 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the baseband unit 1104 when executing the software. The baseband unit 1104 further includes a receiving component 1130, a communication manager 1132, and a transmission component 1134. The communication manager 1132 includes one or more of the illustrated components. The components within the communication manager 1132 may be stored in a computer-readable medium / memory and / or configured as hardware within the baseband unit 1104. The baseband unit 1104 may be a component of the BS 310 and may include a memory 376 and / or at least one of: the TX processor 316 , the RX processor 370 , and the controller / processor 375 .

[0106] The communication manager 1132 includes a determining component 1140 configured to transmit a first configuration associated with a first block of uplink cancellation indications (ULCIs) to a user equipment (UE), wherein the first configuration is associated with at least one of a supplementary uplink (SUL) carrier or a non-supplementary uplink (NUL) carrier in a cell, e.g., as described in conjunction with Fig. 9 The determining component 1140 is further configured to configure a second configuration associated with a second block of the ULCI for the UE, wherein the second configuration is associated with the SUL carrier in the cell. For example, as described in conjunction with Fig. 9 The determining component 1140 is also configured to configure the UE to: when the base station configures a radio resource control (RRC) parameter associated with the SUL carrier, determine a second configuration according to the RRC parameter, for example, as combined with Fig. 9 The determining component 1140 is also configured to configure the UE to determine the second configuration based on the first configuration when the RRC parameter is not configured, for example, as combined with Fig. 9 As described in 906.

[0107] The apparatus may include executing Figure 7 and 9 The additional components of each box of the algorithm in the preceding flowchart. Thus, Figure 7 and 9Each block in the aforementioned flow chart may be performed by a component and the device may include one or more of these components. These components may be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0108] In one configuration, the device 1102, and in particular the baseband unit 1104, includes: means for transmitting a first configuration associated with a first block of uplink cancellation indications (ULCI) to a user equipment (UE), wherein the first configuration is associated with at least one of a supplementary uplink (SUL) carrier or a non-supplementary uplink (NUL) carrier in a cell; means for configuring a second configuration associated with a second block of the ULCI for the UE, wherein the second configuration is associated with the SUL carrier in the cell; means for configuring the UE to determine the second configuration based on a radio resource control (RRC) parameter associated with the SUL carrier when the base station configures the RRC parameter; and means for configuring the UE to determine the second configuration based on the first configuration when the RRC parameter is not configured. The aforementioned means may be one or more of the aforementioned components in the device 1102 configured to perform the functions recited by the aforementioned means. As described above, the device 1102 may include a TX processor 316, an RX processor 370, and a controller / processor 375. As such, in one configuration, the aforementioned means may be the TX processor 316, the RX processor 370, and the controller / processor 375 configured to perform the functions recited by the aforementioned means.

[0109] It should be understood that the specific order or hierarchy of each box in the disclosed process / flowchart is an illustration of an example approach. It should be understood that the specific order or hierarchy of each box in these process / flowcharts can be rearranged based on design preferences. In addition, some boxes can be combined or omitted. The attached method claims present the elements of various boxes in an exemplary order and are not meant to be limited to the specific order or hierarchy presented.

[0110] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be easily understood by those skilled in the art, and the universal principles defined in this article can be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown in this article, but should be granted the full scope consistent with the claims in language, wherein the singular reference of the elements is not intended to represent "there is and only one", but "one or more", unless otherwise stated. The wording "exemplary" is used herein to mean "used as an example, instance or explanation". Any aspect described as "exemplary" herein does not have to be interpreted as being superior to or superior to other aspects. Unless otherwise stated, the term "some / certain" refers to one or more. Combinations such as "at least one of A, B or C", "one or more of A, B or C", "at least one of A, B and C", "one or more of A, B and C" and "A, B, C or any combination thereof" include any combination of A, B and / or C, and may include multiple A, multiple B or multiple C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are currently or hereafter known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is expressly recorded in the claims. The terms "module," "mechanism," "element," "device," and the like may not be a substitute for the term "means." Thus, no claim element should be interpreted as a means-plus-function unless the element is explicitly stated using the phrase "means for..."

[0111] The following examples are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0112] Aspect 1 is a method of wireless communication of a user equipment (UE). The method includes: receiving a first configuration associated with a first block of uplink cancellation indications (ULCI) from a base station, wherein the first configuration is associated with at least one of a supplementary uplink (SUL) carrier or a non-supplementary uplink (NUL) carrier in a cell; determining a second configuration associated with a second block of the ULCI, wherein the second configuration is associated with the SUL carrier in the cell; and monitoring the ULCI based on the first configuration and the second configuration.

[0113] Aspect 2 is the method of aspect 1, wherein the second configuration is determined according to a radio resource control (RRC) parameter received from the base station and associated with the SUL carrier.

[0114] Aspect 3 is a method of any one of Aspects 1 and 2, wherein the first configuration includes a NUL size parameter indicating a first number of bits associated with a first block, and a NUL indication of time-frequency resources associated with the first block; and wherein the second configuration includes a SUL cancellation indication (CI) size parameter indicating a second number of bits associated with a second block, and a SUL indication of time-frequency resources associated with the second block.

[0115] Aspect 4 is the method of any one of aspects 1 to 3, wherein the SUL CI payload size parameter and the SUL indication are RRC parameters separate from the NUL size parameter and the NUL indication.

[0116] Aspect 5 is the method of any one of aspects 1 to 4, wherein the first configuration and the second configuration are configured under the same RRC parameters.

[0117] Aspect 6 is the method of any one of aspects 1 to 5, wherein the second configuration is determined based on the first configuration received from the base station.

[0118] Aspect 7 is a method of any one of Aspects 1 to 6, wherein the first configuration includes a NUL size parameter indicating a first number of bits associated with the first block; wherein the second configuration includes a SUL cancel indication (CI) size parameter indicating a second number of bits associated with the second block; and wherein the SUL CI payload size parameter is the same as the NUL size parameter.

[0119] Aspect 8 is the method of any one of aspects 1 to 7, wherein the second configuration comprises a set of SUL frequency resources, and the SUL frequency resources comprise one of a bandwidth part (BWP) on the SUL or a bandwidth of the SUL.

[0120] Aspect 9 is a method of any one of Aspects 1 to 8, wherein the first configuration includes a first indication of a NUL time domain resource associated with the first block; wherein the second configuration includes a second indication of a SUL time domain resource associated with the second block; and wherein the NUL duration of the NUL time domain resource is the same as the SUL duration of the SUL time domain resource.

[0121] Aspect 10 is the method of any one of Aspects 1 to 9, wherein when the ULCI monitoring periodicity of the UE is at least one time slot, the SUL duration is equal to the ULCI monitoring periodicity; and wherein when the ULCI monitoring periodicity is less than one time slot, the SUL duration is equal to the configured number of codewords.

[0122] Aspect 11 is the method of any one of aspects 1 to 10, wherein the first configuration includes a NUL time domain granularity associated with the first block; wherein the second configuration includes a SUL time domain granularity associated with the second block; and wherein the NUL time domain granularity is the same as the SUL time domain granularity.

[0123] Aspect 12 is a method of any one of Aspects 1 to 11, wherein the first configuration includes a first indication of an uplink de-priority on the NUL associated with the first block; wherein the second configuration includes a second indication of an uplink de-priority on the SUL associated with the second block; and wherein the uplink de-priority on the NUL is the same as the uplink de-priority on the SUL.

[0124] Aspect 13 is a method of any one of Aspects 1 to 12, wherein when the base station configures a radio resource control (RRC) parameter associated with the SUL carrier, the second configuration is determined based on the RRC parameter; and wherein when the RRC parameter is not configured, the second configuration is determined based on the first configuration.

[0125] Aspect 14 is the method of any one of aspects 1 to 13, wherein the RRC parameter associated with the SUL carrier includes at least one of: a frequency domain resource set, a number of bits, a total duration of time domain resources, a time domain granularity, or an uplink de-prioritization.

[0126] Aspect 15 is the method of any one of aspects 1 to 14, wherein the ULCI is monitored based on a second configuration, the second configuration being based on a radio resource control (RRC) parameter received from the base station.

[0127] Aspect 16 is an apparatus for wireless communication, comprising means for implementing the method as in any one of aspects 1 to 15.

[0128] Aspect 17 is an apparatus for wireless communication, comprising: at least one processor coupled to a memory and configured to implement the method of any one of aspects 1 to 15.

[0129] Aspect 18 is a computer-readable medium storing a computer-executable code, wherein the code, when executed by a processor, causes the processor to implement the method of any one of aspects 1 to 15.

[0130] Aspect 19 is a method of wireless communication of a base station. The method includes: transmitting a first configuration associated with a first block of uplink cancellation indications (ULCI) to a user equipment (UE), wherein the first configuration is associated with at least one of a supplementary uplink (SUL) carrier or a non-supplementary uplink (NUL) carrier in a cell; and configuring a second configuration associated with a second block of the ULCI for the UE, wherein the second configuration is associated with the SUL carrier in the cell.

[0131] Aspect 20 is the method of aspect 19, wherein the second configuration includes a radio resource control (RRC) parameter transmitted to the UE and associated with the SUL carrier.

[0132] Aspect 21 is a method of any one of Aspects 19 and 20, wherein the first configuration includes a NUL size parameter indicating a first number of bits associated with a first block, and a NUL indication of time-frequency resources associated with the first block; and wherein the second configuration includes a SUL cancellation indication (CI) size parameter indicating a second number of bits associated with a second block, and a SUL indication of time-frequency resources associated with the second block.

[0133] Aspect 22 is the method of any one of aspects 19 to 21, wherein the SUL CI payload size parameter and the SUL indication are RRC parameters separate from the NUL size parameter and the NUL indication.

[0134] Aspect 23 is the method of any one of aspects 19 to 22, wherein the first configuration and the second configuration are configured under the same RRC parameters.

[0135] Aspect 24 is the method of any one of aspects 19 to 23, wherein the second configuration is configured based on the first configuration transmitted to the UE.

[0136] Aspect 25 is a method of any one of Aspects 19 to 24, wherein the first configuration includes a NUL size parameter indicating a first number of bits associated with the first block; wherein the second configuration includes a SUL cancel indication (CI) size parameter indicating a second number of bits associated with the second block; and wherein the SUL CI payload size parameter is the same as the NUL size parameter.

[0137] Aspect 26 is the method of any one of aspects 19 to 25, wherein the second configuration comprises a set of SUL frequency resources, and the SUL frequency resources comprise one of a bandwidth part (BWP) on the SUL or a bandwidth of the SUL.

[0138] Aspect 27 is a method of any one of Aspects 19 to 26, wherein the first configuration includes a first indication of a NUL time domain resource associated with the first block; wherein the second configuration includes a second indication of a SUL time domain resource associated with the second block; and wherein the NUL duration of the NUL time domain resource is the same as the SUL duration of the SUL time domain resource.

[0139] Aspect 28 is the method of any one of Aspects 19 to 27, wherein when the ULCI monitoring periodicity of the UE is at least one time slot, the SUL duration is equal to the ULCI monitoring periodicity; and wherein when the ULCI monitoring periodicity is less than one time slot, the SUL duration is equal to the configured number of codewords.

[0140] Aspect 29 is the method of any one of aspects 19 to 28, wherein the first configuration includes a NUL time domain granularity associated with the first block; wherein the second configuration includes a SUL time domain granularity associated with the second block; and wherein the NUL time domain granularity is the same as the SUL time domain granularity.

[0141] Aspect 30 is a method of any one of Aspects 19 to 29, wherein the first configuration includes a first indication of an uplink de-priority on the NUL associated with the first block; wherein the second configuration includes a second indication of an uplink de-priority on the SUL associated with the second block; and wherein the uplink de-priority on the NUL is the same as the uplink de-priority on the SUL.

[0142] Aspect 31 is a method of any one of Aspects 19 to 30, further comprising: configuring the UE to: determine a second configuration based on a radio resource control (RRC) parameter associated with the SUL carrier when the base station configures the RRC parameter; and configuring the UE to: determine the second configuration based on the first configuration when the RRC parameter is not configured.

[0143] Aspect 32 is the method of any one of aspects 19 to 31, wherein the RRC parameter associated with the SUL carrier includes at least one of: a frequency domain resource set, a number of bits, a total duration of time domain resources, a time domain granularity, or an uplink de-prioritization.

[0144] Aspect 33 is an apparatus for wireless communication, comprising means for implementing the method as in any one of aspects 19 to 32.

[0145] Aspect 34 is an apparatus for wireless communication, comprising: at least one processor coupled to a memory and configured to implement the method of any one of aspects 19 to 32.

[0146] Aspect 35 is a computer-readable medium storing a computer-executable code, wherein the code, when executed by a processor, causes the processor to implement the method of any one of aspects 19 to 32.

Claims

1. An apparatus for wireless communication at a user equipment UE, comprising: Memory; as well as at least one processor coupled to the memory and configured to: Receiving a first configuration associated with a first block of uplink cancellation indications (ULCI), wherein the first configuration is associated with at least one of a supplementary uplink (SUL) carrier or a non-supplementary uplink (NUL) carrier; and The ULCI is monitored based on the first configuration and a second configuration, wherein the second configuration is associated with a second block of the ULCI, wherein the second configuration is associated with the SUL carrier, and wherein the second configuration is based on a radio resource control (RRC) parameter associated with the SUL carrier when the RRC parameter is configured and the second configuration is based on the first configuration when the RRC parameter is not configured.

2. The device according to claim 1, wherein the first configuration includes a NUL size parameter indicating a first number of bits associated with the first block, and a NUL indication of time-frequency resources associated with the first block; and The second configuration includes a SUL cancel indication CI payload size parameter indicating a second number of bits associated with the second block, and a SUL indication of time-frequency resources associated with the second block.

3. The apparatus of claim 2, wherein the SUL CI payload size parameter and the SUL indication are separate RRC parameters from the NUL size parameter and the NUL indication.

4. The apparatus of claim 1, wherein the first configuration and the second configuration are configured under the same RRC parameters. The apparatus of claim 1 , wherein the second configuration is determined based on the received first configuration.

6. The device as claimed in claim 5, wherein the first configuration includes a NUL size parameter indicating a first number of bits associated with the first block; wherein the second configuration includes a SUL Cancel Indication CI Payload Size parameter indicating a second number of bits associated with the second block; and The SUL CI payload size parameter is the same as the NUL size parameter.

7. The apparatus of claim 5, wherein the second configuration comprises a set of SUL frequency resources, and the SUL frequency resources comprise one of a bandwidth part (BWP) on a SUL or a bandwidth of the SUL.

8. The device according to claim 5, wherein the first configuration includes a first indication of a NUL time domain resource associated with the first block; wherein the second configuration includes a second indication of SUL time domain resources associated with the second block; and The NUL duration of the NUL time domain resource is the same as the SUL duration of the SUL time domain resource.

9. The device according to claim 8, wherein when the ULCI monitoring periodicity of the UE is at least one time slot, the SUL duration is equal to the ULCI monitoring periodicity; and Wherein, when the ULCI monitoring periodicity is less than one time slot, the SUL duration is equal to the configured number of symbols.

10. The device according to claim 5, wherein the first configuration includes a NUL time domain granularity associated with the first block; wherein the second configuration includes a SUL time domain granularity associated with the second block; and The NUL time domain granularity is the same as the SUL time domain granularity.

11. The device according to claim 5, wherein the first configuration includes a first indication of uplink de-prioritization on a NUL associated with the first block; wherein the second configuration includes a second indication of uplink de-prioritization on the SUL associated with the second block; and The uplink de-priority on the NUL is the same as the uplink de-priority on the SUL.

12. The apparatus of claim 1, wherein the RRC parameter associated with the SUL carrier comprises at least one of: a frequency domain resource set, a number of bits, a total duration of time domain resources, a time domain granularity, or an uplink de-prioritization.

13. The apparatus of claim 12, wherein the set of frequency-domain resources corresponds to a portion of a bandwidth for a SUL configured for the UE.

14. The apparatus of claim 12, wherein the set of frequency-domain resources corresponds to an entire bandwidth for a SUL associated with the UE.

15. A method for wireless communication by a user equipment UE, comprising: Receiving a first configuration associated with a first block of uplink cancellation indications (ULCI), wherein the first configuration is associated with at least one of a supplementary uplink (SUL) carrier or a non-supplementary uplink (NUL) carrier; and The ULCI is monitored based on the first configuration and a second configuration, wherein the second configuration is associated with a second block of the ULCI, wherein the second configuration is associated with the SUL carrier, and wherein the second configuration is based on a radio resource control (RRC) parameter associated with the SUL carrier when the RRC parameter is configured and the second configuration is based on the first configuration when the RRC parameter is not configured.

16. An apparatus for wireless communication at a base station, comprising: Memory; as well as at least one processor coupled to the memory and configured to: transmitting a first configuration associated with a first block of uplink cancellation indications (ULCI) to a user equipment (UE), wherein the first configuration is associated with at least one of a supplementary uplink (SUL) carrier or a non-supplementary uplink (NUL) carrier; as well as configuring the UE to: determine a second configuration based on a radio resource control (RRC) parameter when the RRC parameter is configured, and to determine the second configuration based on the first configuration when the RRC parameter is not configured, wherein the second configuration is associated with a second block of the ULCI, and The second configuration is associated with the SUL carrier.

17. The device according to claim 16, wherein the first configuration includes a NUL size parameter indicating a first number of bits associated with the first block, and a NUL indication of time-frequency resources associated with the first block; and The second configuration includes a SUL cancel indication CI payload size parameter indicating a second number of bits associated with the second block, and a SUL indication of time-frequency resources associated with the second block.

18. The apparatus of claim 17, wherein the SUL CI payload size parameter and the SUL indication are separate RRC parameters from the NUL size parameter and the NUL indication.

19. The apparatus of claim 16, wherein the first configuration and the second configuration are configured under the RRC parameters.

20. The apparatus of claim 16, wherein the second configuration is configured based on the first configuration transmitted to the UE.

21. The device according to claim 20, wherein the first configuration includes a NUL size parameter indicating a first number of bits associated with the first block; wherein the second configuration includes a SUL Cancel Indication CI Payload Size parameter indicating a second number of bits associated with the second block; and The SUL CI payload size parameter is the same as the NUL size parameter.

22. The apparatus of claim 20, wherein the second configuration comprises a set of SUL frequency resources, and the SUL frequency resources comprise one of a bandwidth part (BWP) on a SUL or a bandwidth of the SUL.

23. The device according to claim 20, wherein the first configuration includes a first indication of a NUL time domain resource associated with the first block; wherein the second configuration includes a second indication of SUL time domain resources associated with the second block; and The NUL duration of the NUL time domain resource is the same as the SUL duration of the SUL time domain resource.

24. The device according to claim 23, wherein when the ULCI monitoring periodicity of the UE is at least one time slot, the SUL duration is equal to the ULCI monitoring periodicity; and Wherein, when the ULCI monitoring periodicity is less than one time slot, the SUL duration is equal to the configured number of symbols.

25. The device according to claim 20, wherein the first configuration includes a NUL time domain granularity associated with the first block; wherein the second configuration includes a SUL time domain granularity associated with the second block; and The NUL time domain granularity is the same as the SUL time domain granularity.

26. The device of claim 20, wherein the first configuration includes a first indication of uplink de-prioritization on a NUL associated with the first block; wherein the second configuration includes a second indication of uplink de-prioritization on the SUL associated with the second block; and The uplink de-priority on the NUL is the same as the uplink de-priority on the SUL.

27. The apparatus of claim 16, wherein the RRC parameter comprises at least one of: a frequency domain resource set, a number of bits, a total duration of a time domain resource, a time domain granularity, or an uplink de-prioritization.

28. A method for wireless communication by a base station, comprising: transmitting a first configuration associated with a first block of uplink cancellation indications (ULCI) to a user equipment (UE), wherein the first configuration is associated with at least one of a supplementary uplink (SUL) carrier or a non-supplementary uplink (NUL) carrier; as well as The UE is configured to determine a second configuration based on a radio resource control (RRC) parameter when the RRC parameter is configured, and to determine the second configuration based on the first configuration when the RRC parameter is not configured, wherein the second configuration is associated with a second block of the ULCI, and wherein the second configuration is associated with the SUL carrier.

Images