Management of uplink transmissions and srs transmissions on different carriers

Abstract

Aspects are provided that improve effectiveness of collision resolution between scheduled uplink transmissions and carrier-switched sounding reference signals (SRS). A UE receives a physical downlink control channel (PDCCH) from a base station. The PDCCH schedules an uplink transmission on a first carrier. The UE determines whether to drop one of the uplink transmission or a transmission of an SRS on a second carrier different from the first carrier based on a timing between a time of reception of the PDCCH and a scheduled time for transmitting the SRS on the second carrier. By taking the timing into account in the determination, a situation where the UE does not know that an uplink transmission will be scheduled at a time of a carrier-switched SRS can be eliminated.

Description

[0001] Cross-references to related applications

[0002] This application claims the right to Greek application filed on 4 September 2020 entitled “TIMELINES FOR SRSCARRIER SWITCHING” with serial number 20200100539, the disclosure of which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] In summary, this disclosure relates to wireless communication systems, and more specifically, to wireless communication systems between user equipment (UE) and base stations. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable 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.

[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the continuous evolution of mobile broadband released by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., in conjunction with the Internet of Things (IoT),) and others. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements to 5G NR technology. These improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0006] The following provides a brief overview of one or more aspects to offer a basic understanding of such aspects. This overview is not a comprehensive summary of all anticipated aspects, nor is it intended to identify key or important elements of all aspects, nor to depict 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 the more detailed descriptions that follow.

[0007] In one aspect of this disclosure, methods, computer-readable media, and apparatus are provided. The apparatus may be a UE (User Equipment). The apparatus receives a Physical Downlink Control Channel (PDCCH) from a base station, the PDCCH being scheduled for uplink transmission on a first carrier. The apparatus determines whether to discard either the uplink transmission or the SRS transmission based on a timing interval between the PDCCH reception time and a scheduling time for transmitting a Sounding Reference Signal (SRS) on a second carrier different from the first carrier.

[0008] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and drawings set forth certain illustrative features of one or more aspects in detail. However, these features indicate only some of the various ways in which the principles of these aspects may be employed, and this specification is intended to include all such aspects and their equivalents. Attached Figure Description

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

[0010] Figure 2A This is a schematic diagram illustrating an example of a first subframe according to various aspects of this disclosure.

[0011] Figure 2B This is a schematic diagram illustrating an example of a DL channel within a subframe according to various aspects of this disclosure.

[0012] Figure 2C This is a schematic diagram illustrating an example of a second subframe according to various aspects of this disclosure.

[0013] Figure 2D This is a schematic diagram illustrating an example of a UL channel within a subframe according to various aspects of this disclosure.

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

[0015] Figure 4 This is a schematic diagram illustrating an example of a timeline for carrier-switched SRS transmission relative to uplink transmission.

[0016] Figure 5 This is a schematic diagram illustrating another example of the timeline for carrier-switched SRS transmission relative to uplink transmission.

[0017] Figure 6 This is a schematic diagram illustrating another example of the timeline for carrier-switched SRS transmission relative to uplink transmission.

[0018] Figure 7 This is a schematic diagram illustrating an example of a timeline for carrier-switched SRS transmission relative to uplink transmission.

[0019] Figure 8 This is a schematic diagram illustrating another example of the timeline for carrier-switched SRS transmission relative to uplink transmission.

[0020] Figure 9 This is a schematic diagram illustrating another example of the timeline for carrier-switched SRS transmission relative to uplink transmission.

[0021] Figure 10 This is a schematic diagram illustrating another example of the timeline for carrier-switched SRS transmission relative to uplink transmission.

[0022] Figure 11 This is a schematic diagram illustrating another example of the timeline for carrier-switched SRS transmission relative to uplink transmission.

[0023] Figure 12 This is a schematic diagram illustrating an example of a timeline for carrier-switched SRS transmission relative to uplink transmission.

[0024] Figure 13 This is a schematic diagram illustrating another example of the timeline for carrier-switched SRS transmission relative to uplink transmission.

[0025] Figure 14 This is a schematic diagram illustrating another example of the timeline for carrier-switched SRS transmission relative to uplink transmission.

[0026] Figure 15 This is a schematic diagram illustrating another example of the timeline for carrier-switched SRS transmission relative to uplink transmission.

[0027] Figure 16 This is a schematic diagram illustrating another example of the timeline for carrier-switched SRS transmission relative to uplink transmission.

[0028] Figure 17 This is a schematic diagram illustrating the call flow between the UE and the base station.

[0029] Figure 18 This is a flowchart of a wireless communication method.

[0030] Figure 19 This is a schematic diagram illustrating an example of a hardware implementation for an example device. Detailed Implementation

[0031] The specific embodiments described below with reference to the accompanying drawings are intended as a description of various configurations and not as representing only the configurations in which the concepts described herein can be practiced. Specific details are included in the specific embodiments for the purpose of providing a comprehensive understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0032] SRS is an uplink reference signal that a UE can transmit to a base station to allow the base station to estimate uplink channel quality for frequency-dependent scheduling or to estimate timing for timing alignment. The base station can trigger the UE to transmit periodic or semi-persistent SRS in response to RRC signaling, or to transmit aperiodic SRS in response to a trigger in downlink control information (DCI). Typically, the UE can transmit SRS on the same carrier as the DCI or other downlink data. Such SRS can be called non-carrier-switching SRS. The UE can also transmit SRS on a different carrier than the uplink transmission scheduled by the DCI or other downlink data. Such SRS can be called carrier-switching SRS.

[0033] SRS carrier handover is generally not allowed to be performed concurrently with uplink transmissions on other carriers. In some cases, SRS carrier handover is not allowed to be performed concurrently with another carrier that serves as the source for SRS carrier handover. Therefore, a UE may not be transmitting on a different carrier (e.g., PUSCH, PUCCH, SRS, or PRACH) simultaneously with transmitting SRS on one carrier. As a result, conflicts may occur between such uplink transmissions and carrier-switched SRS. To handle these conflicts, the UE can apply various conflict resolution rules to determine whether uplink transmission on the source carrier takes precedence over carrier-switched SRS. Based on these rules, the UE can transmit or discard carrier-switched SRS to prevent conflicts with uplink transmissions.

[0034] However, the effectiveness of the conflict resolution rules depends on when the downlink data scheduled for uplink transmissions is received relative to the scheduling time for carrier-switching SRS. Typically, the UE decides whether to initiate carrier-switching SRS transmissions a specific amount of time before sending the scheduling time, for example, considering the carrier switching time. This specific amount of time before the UE sends the carrier-switching SRS can be called the SRS decision time. If the UE determines at the SRS decision time that the carrier-switching SRS will overlap with the scheduled uplink transmissions, the UE can discard the carrier-switching SRS to favor uplink transmissions (or vice versa) according to the conflict resolution rules. However, if the downlink data scheduled for uplink transmissions is received after the SRS decision time, the UE may not know that the uplink transmissions are scheduled or even being scheduled when it initiates carrier-switching SRS. As a result, the UE may not be able to discard the SRS to favor uplink transmissions according to the conflict resolution rules, and conflicts may occur between the carrier-switching SRS and the uplink transmissions.

[0035] To address this issue, aspects of this disclosure allow the UE to determine, based on the timing between the downlink data reception time and the SRS decision time, whether to discard the SRS according to some conflict resolution rules or the uplink transmission according to other conflict resolution rules. For example, if the UE receives the PDCCH no later than the SRS decision time, the UE can determine the uplink transmission scheduled by the PDCCH and apply one of the aforementioned conflict resolution rules accordingly. In this way, timing situations that could lead to conflicts as described above can be avoided.

[0036] Several aspects of a telecommunications system will now be described with reference to various apparatuses and methods. These apparatuses and methods will be described in detail below and illustrated in the accompanying drawings by way of various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented in hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0037] By way of example, elements, or any part of elements, or any combination of elements, can 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, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described herein. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, software should be broadly interpreted as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc.

[0038] Accordingly, in one or more example embodiments, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or code on a computer-readable medium. A computer-readable medium includes a computer storage medium. The storage medium may be any available medium accessible by a computer. By way of example, and not limitation, such a computer-readable medium 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, combinations of computer-readable media of the types described above, or any other medium capable of storing computer-executable code in the form of computer-accessible instructions or data structures.

[0039] Figure 1 This is a schematic 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 user equipment (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 macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells include base stations. Small cells include femtocells, picocells, and microcells.

[0040] Base station 102 configured for 4G Long Term Evolution (LTE) (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G New Radio (NR) (collectively referred to as Next Generation RAN (NG-RAN)) can interface with core network 190 via a second backhaul link 184. Among other functions, base station 102 can also perform one or more of the following functions: transmission 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), user and device tracking, RAN Information Management (RIM), paging, location, and delivery of warning messages. Base station 102 can communicate directly or indirectly with each other (e.g., via EPC 160 or core network 190) via third backhaul link 134 (e.g., X2 interface). First backhaul link 132, second backhaul link 184 and third backhaul link 134 can be wired or wireless.

[0041] Base station 102 can communicate wirelessly with UE 104. Each base station 102 in the base station 102 can provide communication coverage for a corresponding geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells can be referred to as a heterogeneous network. The heterogeneous network may also include a Home Evolved Node B (eNB) (HeNB), which can provide services to a restricted group referred to as a Closed Subscriber Group (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also referred to as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also referred to as forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be via one or more carriers. Base station 102 / UE 104 may use spectrum allocated in carrier aggregation for a total of up to Y x MHz (x component carriers) for transmission in each direction, with a bandwidth of up to Y MHz per carrier (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.). Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell), and the secondary component carrier may be referred to as the secondary cell (SCell).

[0042] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL WWAN spectrum. D2D communication link 158 can use one or more sidelink channels, such as the Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be achieved through a variety of wireless D2D communication systems, such as WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0043] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, an unlicensed spectrum of 5 GHz. When communicating in unlicensed spectrum, the STA 152 / AP 150 may perform a free channel assessment (CCA) before communication to determine whether the channel is available.

[0044] Small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell 102' can employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) as used by Wi-Fi AP 150. Small cell 102' employing NR in unlicensed spectrum can improve coverage of the access network and / or increase the capacity of the access network.

[0045] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, the two initial operating bands have been designated as frequency range names FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the "below 6GHz" band in various documents and articles. Similar naming issues sometimes arise regarding FR2; although different from the Extremely High Frequency (EHF) band (30GHz-300GHz) designated as the "millimeter wave" band by the International Telecommunication Union (ITU), FR2 is often (interchangeably) referred to as the "millimeter wave" band in documents and articles.

[0046] In light of the above, unless otherwise specifically stated, it should be understood that when the term "below 6 GHz" is used herein, it can broadly refer to frequencies that are less than 6 GHz, within FR1, or may include intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that when the term "millimeter wave" is used herein, it can broadly refer to frequencies that may include intermediate frequency band frequencies, within FR2, or within the EHF band.

[0047] Base station 102 (whether a small cell 102' or a large cell (e.g., a macro base station)) may include and / or be referred to as an eNB, gNodeB (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in conventional sub-6 GHz spectrum, millimeter wave frequencies, and / or near-millimeter wave frequencies to communicate with UE 104. When gNB 180 operates in millimeter wave or near-millimeter wave frequencies, gNB 180 may be referred to as a millimeter wave base station. Millimeter wave base station 180 may utilize beamforming 182 with UE 104 to compensate for extremely high path loss and short range. Base station 180 and UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming.

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

[0049] EPC 160 may include Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, MBMS Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and Packet Data Network (PDN) Gateway 172. MME 162 can communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Typically, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides IP address allocation and other functions to the UE. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP Service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. BM-SC 170 can provide functions for MBMS user service provisioning and delivery. The BM-SC 170 can be used as an entry point for MBMS transmissions to content providers, to permit and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and to schedule MBMS transmissions. The MBMS gateway 168 can be used to distribute MBMS services to base stations 102 belonging to areas of Multicast-Broadcast Single Frequency Networks (MBSFNs) that broadcast specific services, and can be responsible for session management (start / stop) and collecting billing information related to eMBMS.

[0050] Core network 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 can communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that processes signaling between UE 104 and core network 190. Typically, AMF 192 provides Quality of Service (QoS) streaming and session management. All user IP packets are transmitted via UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP service 197. IP service 197 may include the Internet, intranet, IMS, packet-switched (PS) streaming service, and / or other IP services.

[0051] Base stations may include and / or be referred to as gNB, Node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, Basic Services Set (BSS), Extended Services Set (ESS), Transmitter Receiver Point (TRP), or some other suitable term. Base station 102 provides access to EPC 160 or core network 190 for UE 104. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radio units, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some UE 104 devices may be referred to as IoT devices (e.g., parking meters, air pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, user station, mobile unit, user unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile user station, access terminal, mobile terminal, radio terminal, remote terminal, handheld device, user agent, mobile client, client, or any other appropriate term.

[0052] Refer again Figure 1 In some aspects, UE 104 may include a carrier switching component 198 configured to receive a PDCCH from a base station, the PDCCH being scheduled for uplink transmission on a first carrier. The carrier switching component 198 is also configured to determine, based on a timing between the PDCCH reception time and the scheduling time for transmitting an SRS on a second carrier different from the first carrier, whether to discard either the uplink transmission or the SRS transmission.

[0053] Although the following description may focus on 5G NR, the concepts and aspects described herein can be applied to other similar fields, such as LTE, improved LTE (LTE-A), Code Division Multiple Access (CDMA), Global System for Mobile Communications (GSM) or other wireless / radio access technologies.

[0054] Figure 2A This is a schematic diagram 200 showing an example of the first subframe within a 5G NR frame structure. Figure 2B This is a schematic diagram 230 showing an example of a DL channel within a 5G NR subframe. Figure 2C This is a schematic diagram 250 showing an example of a second subframe within a 5G NR frame structure. Figure 2DThis is a schematic diagram 280 illustrating an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD) (where, for a specific set of subcarriers (carrier system bandwidth), subframes within that set are dedicated to either DL or UL), or Time Division Duplex (TDD) (where, for a specific set of subcarriers (carrier system bandwidth), subframes within that set are dedicated to both DL and UL). In the process of... Figure 2A , 2C In the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (mostly DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 34 (mostly UL). Although subframes 3 and 4 are shown as having slot formats 34 and 28, respectively, any particular subframe can 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 mixture of DL, UL, and flexible symbols. The UE is configured to have a slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0055] Other wireless communication technologies can have different frame structures and / or different channels. For example, a 10-millisecond (ms) frame can be divided into 10 equal-sized subframes (1ms). Each subframe can include one or more time slots. Subframes can also include micro-time slots, which can include 7, 4, or 2 symbols. Each time slot can include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot can include 14 symbols, and for time slot configuration 1, each time slot can include 7 symbols. Symbols on the DL can be Cyclic Prefix (CP) Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Spread Spectrum OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe can be based on the time slot configuration and the numbering scheme. For slot configuration 0, different digital schemes μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For slot configuration 1, different digital schemes 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Correspondingly, for slot configuration 0 and digital scheme μ, there are 14 symbols / slot and 2...μ Each time slot / subframe. Subcarrier spacing and symbol length / duration are functions of the digital scheme. Subcarrier spacing can be equal to 2. μ *15 kHz, where μ is the digital scheme from 0 to 4. Therefore, digital scheme μ = 0 has a subcarrier spacing of 15 kHz, and digital scheme μ = 4 has a subcarrier spacing of 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A-2D Examples are provided for slot configuration 0 (14 symbols per slot) and digital scheme μ=2 (4 slots per subframe). 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, one or more distinct bandwidth portions (BWPs) of frequency division multiplexing can exist (see [link to relevant documentation]). Figure 2B Each BWP can have a specific digital scheme.

[0056] A resource grid can be used to represent frame structure. Each time slot includes a resource block (RB) (also known as a physical RB (PRB)), which consists of 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0057] As in Figure 2A As shown, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulated RS (DM-RS) for channel estimation at the UE (indicated as R for a specific configuration). x (Where 100x is the port number, but other DM-RS configurations are possible) and Channel State Information Reference Signal (CSI-RS). RS may also include Beam Measurement RS (BRS), Beam Refinement RS (BRRS), and Phase Tracking RS (PT-RS).

[0058] Figure 2BExamples of various DL channels within a subframe of a frame are shown. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs), each CCE comprising nine RE Groups (REGs), each REG comprising four consecutive REs within an OFDM symbol. The PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). Additional BWPs can span the channel bandwidth at larger and / or lower frequencies. The Primary Synchronization Signal (PSS) can be located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) can be located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and Physical Layer Cell Identifier 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 known as an SS block (SSB)). The MIB provides the number of RBs and the System Frame Number (SFN) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (e.g., System Information Block (SIB)), and paging messages.

[0059] As in Figure 2C As shown, some of the REs in the diagram carry DM-RS for channel estimation at the base station (indicated as R for a specific configuration, but other DM-RS configurations are possible). The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first one or two symbols preceding the PUSCH. The PUCCH DM-RS can be transmitted in different configurations depending on whether a short or long PUCCH is transmitted and the specific PUCCH format used. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the combs. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0060] Figure 2DExamples of various UL channels within a subframe of a frame are shown. The PUCCH can be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) / negative acknowledgment (NACK) feedback. The PUSCH carries data and may also be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0061] Figure 3 This is a block diagram illustrating communication between base station 310 and UE 350 in the access network. In the DL, IP packets from EPC160 can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Serving Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides: RRC layer functions associated with: broadcasting 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 for UE measurement reporting; PDCP layer functions associated with: header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with: transmission of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with: mapping between logical channels and transport channels, multiplexing of MAC SDUs to transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0062] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection of 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. TX processor 316 processes 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 phase shift keying (M-PSK), and M-order quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using 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 channel estimator 374 can be used to determine coding and modulation schemes and for spatial processing. The channel estimates can be derived from reference signals transmitted by UE 350 and / or channel condition feedback. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can use the corresponding spatial stream to modulate an RF carrier for transmission.

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

[0064] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport and logical channels 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 operation.

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

[0066] The channel estimate derived by the channel estimator 358 from the reference signal or feedback transmitted by the base station 310 can be used by the TX processor 368 to select appropriate coding and modulation schemes, as well as to facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via a separate transmitter 354TX. Each transmitter 354TX can use the corresponding spatial stream to modulate the RF carrier for transmission.

[0067] UL transmission at base station 310 is handled in a manner similar to that described for the receiver functions integrated at UE 350. Each receiver 318RX receives signals via its corresponding antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides the information to the RX processor 370.

[0068] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport channel and the logical channel to recover IP packets from the UE 350. 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 operation.

[0069] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to perform and Figure 1 All aspects related to the carrier switching component 198.

[0070] SRS is an uplink reference signal that a UE can transmit to a base station to allow the base station to estimate uplink channel quality for frequency-dependent scheduling or to estimate timing for timing alignment. In time-division duplex (TDD) systems, SRS can also assist the base station in downlink scheduling, where the downlink channel including the scheduling and the uplink channel including the SRS are the same. The base station can trigger the UE to transmit periodic or semi-persistent SRS in response to RRC signaling, or to transmit aperiodic SRS in response to triggering in DCI. The UE can receive DCI in PDCCH, and the UE can transmit SRS in the Physical Uplink Shared Channel (PUSCH).

[0071] Typically, a UE can transmit aperiodic SRS (e.g., non-carrier-switching SRS) on the same carrier as the DCI. For example, a UE can receive downlink DCI, group common DCI, or uplink-based DCI commands, where the DCI code point can trigger one or more SRS resource sets on the same carrier. For SRS in resource sets used for "codebook" or "antennaSwitching," the minimum time interval between the last symbol of the PDCCH triggering the aperiodic SRS transmission and the first symbol of the SRS resource can be N²+T. switch Where N2 represents the PUSCH preparation time, and T switch Indicates the duration of the uplink handover gap (if any). Otherwise, the minimum time interval between the last symbol of the PDCCH that triggers the aperiodic SRS transmission and the first symbol of the SRS resource can be N²+T. switch+14. The minimum time interval in OFDM symbols can be calculated based on the minimum subcarrier spacing between the PDCCH and the aperiodic SRS. Although this example refers to the minimum time interval as being based on N2, the minimum time interval is not limited to N2 and can be based on some other timing (e.g., a different number of symbols other than the number of symbols represented by the PUSCH preparation time).

[0072] The value of N2 can be calculated based on the worst-case carrier among the carriers involved in the carrier-switching SRS. Both the source and target component carriers can be cross-carrier scheduled. For example, the value of N2 can be calculated based on μ from Tables 1 and 2 for UE processing capability 1 and UE processing capability 2, respectively, where μ corresponds to the subcarrier interval of the downlink used to transmit PDCCH or the subcarrier interval of the uplink used to transmit PUSCH that results in the maximum UE PUSCH preparation time (T). proc,2 One of them. For example, the value of μ in any table corresponding to the digital scheme with the smallest subcarrier spacing (e.g., μ = 0) can be the worst-case carrier that results in the maximum PUSCH preparation time.

[0073] Table 1: PUSCH preparation time for PUSCH timing capability 1

[0074]

[0075]

[0076] Table 2: PUSCH preparation time for PUSCH timing capability 2

[0077] μ <![CDATA[PUSCH preparation time N2 [symbols]]]> 0 5 1 5.5 2 11 (for frequency range 1)

[0078] The UE can also transmit aperiodic SRS (e.g., carrier-switching SRS) on a carrier different from the carrier of the uplink transmission scheduled by the DCI. For example, if the UE receives a PDCCH scheduled for uplink transmission on one component carrier but on another, the UE can switch to a different component carrier to transmit SRS, or the UE can transmit SRS on the same component carrier as the component carrier of the PDCCH that triggered the SRS. For example, when the UE has a single power amplifier that moves between carriers, the UE can interrupt another carrier transmission to transmit SRS on a different carrier. If the UE detects a positive SRS request on the permission for the nth (n≥1) aperiodic SRS transmission on cell c, the UE may initiate an SRS transmission on the configured symbols and time slots, provided that the transmission is not earlier than the sum of: (a) the maximum duration between two durations spanned by N OFDM symbols of cell c and the digital scheme carrying the permission cell (e.g., corresponding to N2 in one example, or some other timing in another example), and (b) the uplink or downlink RF retuning time for switching carriers (referred to herein as switchingTime). The switching time can be defined by the switchingTimeUL and switchingTimeDL of the higher-layer parameter srs-SwitchingTimeNR.

[0079] SRS carrier handover is typically not permitted to be concurrent with uplink transmissions on other carriers. Therefore, a UE may not transmit SRS on one carrier while simultaneously transmitting another UE's transmissions (e.g., PUSCH, PUCCH, SRS, or PRACH) on a different carrier. This restriction can be based on UE capability information reported to the base station. For example, when a UE reports uplink component carrier parameters to the base station, it may indicate that it does not support simultaneous transmission of SRS on a supplementary uplink (SUL) carrier or a non-SUL carrier and PUSCH / PUCCH / SRS / PRACH on other UL carriers in the same cell (e.g., in parameters such as simultaneousTxSUL-NonSUL or another name). As a result, conflicts may occur between such uplink transmissions and carrier-switched SRS.

[0080] To handle these conflicts, the UE can apply various rules to determine whether to prioritize uplink transmissions on the source carrier over carrier-switched SRS. In one rule, if the UE is scheduled to transmit a PUSCH, a PUCCH carrying an ACK / NACK, or a positive scheduling request (SR), then the uplink transmission takes precedence over carrier-switched SRS, and the UE discards the carrier-switched SRS. In another rule, if the UE is scheduled to transmit a PUSCH or PUCCH carrying a Rank Indicator (RI) and / or a Channel State Information Resource Indicator (CRI), then the uplink transmission takes precedence over carrier-switched SRS, and the UE discards the carrier-switched SRS. In yet another rule, if the UE is scheduled to transmit a PUSCH carrying aperiodic Channel State Information (CSI), then the uplink transmission takes precedence over periodic or semi-persistent carrier-switched SRS, and the UE discards the carrier-switched SRS. In another rule, if the UE is scheduled to transmit a PUSCH carrying only an aperiodic CSI with a Channel Quality Indicator (CQI) or a Precoding Matrix Indicator (PMI), then an aperiodic carrier-switched SRS takes precedence over the uplink transmission, and the UE discards the uplink transmission. In another rule, if the UE is scheduled to transmit a PUSCH or PUCCH carrying only a periodic CSI with a CQI or PMI, then a carrier-switched SRS (whether periodic, semi-persistent, or aperiodic) takes precedence over the uplink transmission, and the UE discards the uplink transmission. In another rule, if the UE is scheduled to transmit a PUSCH without Uplink Control Information (UCI), then a carrier-switched SRS takes precedence over the uplink transmission, and the UE discards the uplink transmission. In another rule, if the UE is scheduled to transmit a Physical Random Access Channel (PRACH), then the uplink transmission takes precedence over a carrier-switched SRS, and the UE discards the carrier-switched SRS. In another rule, if the UE is scheduled to transmit a non-carrier-switching SRS, the carrier-switching SRS takes precedence over the uplink transmission, and the UE discards the uplink transmission. Therefore, the UE can transmit or discard carrier-switching SRS based on these conflict resolution rules to prevent conflicts with uplink transmissions. However, the effectiveness of such conflict resolution rules depends on when the PDCCH scheduling the uplink transmission is received relative to the scheduling time used for the carrier-switching SRS.

[0081] Figure 4Example 400 illustrates a timeline for carrier-switching SRS transmission relative to uplink transmission, which may prevent the effective application of rules. In this example, the UE receives PDCCH 402 from the base station at reception time 404. PDCCH 402 may include a DCI scheduling PDSCH 406, which includes downlink data, thereby enabling the UE to send HARQ-ACK 408 on the PUCCH in response to the PDSCH. Thus, the PDCCH from the base station can schedule HARQ-ACK from the UE. The UE also receives permission (not shown) from the base station to schedule carrier-switching SRS 410 (e.g., aperiodic SRS). In other examples, carrier-switching SRS may be periodic (e.g., RRC-configured) or semi-persistent (e.g., activated via PDSCH). Carrier-switching SRS 410 is scheduled to be transmitted on a different carrier than HARQ-ACK and therefore includes a switching time 412 (e.g., switchingTime) for retuning to this different carrier before the SRS. The carrier-switching SRS 410 also includes a switching time 414 for retuning back to the source carrier after the SRS.

[0082] In this example, carrier-switching SRS 410 overlaps with HARQ-ACK 408. For example, HARQ-ACK 408 can be scheduled to occur during at least one symbol within the handover time 414. In this case, the conflict resolution rule instructs the UE to discard carrier-switching SRS 410 to favor uplink transmission (HARQ-ACK 408). However, as described above, for carrier-switching SRS, SRS transmission begins on the configured symbols and time slots, provided that the transmission is no earlier than the sum of N2 (or some other timing) + switchingTime. Therefore, the UE begins carrier-switching SRS transmission at SRS decision time 416, which can be N2 symbols 418 before handover time 412, and thus N2 + switchingTime symbols before carrier-switching SRS 410. Because the SRS decision time 416 occurs before the PDCCH reception time 404, the UE may not know that HARQ-ACK will be scheduled when it starts carrier-switching SRS, and therefore the UE may fail to discard SRS according to the conflict resolution rules to facilitate uplink transmission. As a result, a conflict may occur between SRS and HARQ-ACK.

[0083] This disclosure addresses the problem by allowing the UE to determine, based on the timing between the PDCCH reception time and the SRS decision time, whether to discard the SRS according to some conflict resolution rules or the uplink transmission according to others. For example, if the UE receives the PDCCH at a time no later than N2+switchingTime symbols before the first symbol of the carrier-switching SRS, the UE can determine the uplink transmission scheduled by the PDCCH and apply one of the aforementioned conflict resolution rules accordingly. The following section discusses… Figure 5-16 Examples of various uplink transmission scenarios are provided. This approach avoids timing conflicts that could occur, such as those mentioned above. Figure 4 The situation described.

[0084] Figure 5 A timeline 500 is shown for an example of a carrier-switching SRS transmission relative to an uplink transmission (i.e., corresponding to a dynamically permitted HARQ-ACK). In this example, the UE receives PDCCH 502 from the base station at reception time 504. PDCCH 502 may include a DCI that schedules PDSCH 506, which includes downlink data, thereby enabling the UE to send a HARQ-ACK 508 on the PUCCH in response to the PDSCH. Thus, the PDCCH from the base station can schedule a HARQ-ACK from the UE. The UE also receives permission (not shown) from the base station to schedule carrier-switching SRS 510 (e.g., aperiodic SRS). In other examples, carrier-switching SRS may be periodic (e.g., RRC-configured) or semi-persistent (e.g., activated via PDSCH). The carrier-switching SRS 510 is scheduled to transmit on a different carrier than the HARQ-ACK, and therefore includes a switching time 512 (e.g., switchingTime) for retuning to this different carrier before the SRS. The carrier-switching SRS 510 also includes a switching time 514 for retuning back to the source carrier after the SRS. The SRS decision time 516 can be N2 symbols 518 (or some other timing) before the switching time 512, and is therefore N2 + switchingTime symbols before the carrier-switching SRS 510.

[0085] In this example, the reception time 504 of the PDCCH 502 used to schedule HARQ-ACK 508 is before the SRS decision time 516 (more than zero symbols before it). Therefore, before the SRS transmission begins, the UE can determine that the PDCCH is scheduling an uplink transmission (HARQ-ACK 508) that overlaps with the carrier-switching SRS 510. For example, the UE can determine that... Figure 5The HARQ-ACK 508 shown in the example will be scheduled to occur during at least one symbol within the handover time 514. In such a case, the conflict resolution rule instructs the UE to discard the carrier-switching SRS 510 to favor uplink transmission (HARQ-ACK 508). For example, the UE may determine that for a carrier of the serving cell with a slot format including DL and UL symbols, not configured for PUSCH / PUCCH transmission, whenever an SRS transmission on that carrier of the serving cell (including any interruption due to uplink or downlink RF retuning time as defined by the higher-layer parameter srs-SwitchingTimeNR's switchingTimeUL and switchingTimeDL) and a PUSCH / PUCCH transmission carrying HARQ-ACK overlap exactly in the same symbol and this may cause uplink transmission to exceed the UE's indicated uplink carrier aggregation capability, the UE may not send an SRS. Therefore, at the SRS decision time 516, the UE may determine to discard the carrier-switching SRS 510 transmission, thereby avoiding conflict with uplink transmission.

[0086] Figure 6 A timeline 600 is shown for another example of carrier-switching SRS transmission relative to uplink transmission (i.e., semi-persistent scheduling (SPS) HARQ-ACK). In this example, the UE receives PDCCH 602 from the base station at reception time 604. PDCCH 602 may include a DCI that activates the SPS PDSCH and HARQ-ACK. For example, the PDCCH may include a DCI that schedules a semi-persistent PDSCH 606 ​​that includes downlink data, which in turn allows the UE to send a semi-persistent HARQ-ACK 608 on the PUCCH in response to each PDSCH. Thus, the PDCCH from the base station can schedule the SPS HARQ-ACK from the UE. The UE also receives permission (not shown) from the base station to schedule carrier-switching SRS 610 (e.g., aperiodic SRS). In other examples, carrier-switching SRS may be periodic (e.g., RRC configured) or semi-persistent (e.g., activated via PDSCH). The carrier-switching SRS 610 is scheduled to transmit on a different carrier than the SPS HARQ-ACK, and therefore includes a switching time 612 (e.g., switching Time) for retuning to this different carrier before the SRS. The carrier-switching SRS 610 also includes a switching time 614 for retuning back to the source carrier after the SRS. Although Figure 6 The switching time of 614 is shown as less than in Figure 4 and Figure 5The switching times 414 and 514 are used in the diagram, but this change is only for illustrative purposes, and it should be noted that the switching time 614 can usually be the same as the switching times 414 and 514. The SRS decision time 616 can be N2 symbols 618 (or some other timing) before the switching time 612, and is therefore N2+switchingTime symbols before the carrier-switching SRS 610.

[0087] In this example, the reception time 604 of the PDCCH 602 used to schedule SPS HARQ-ACK 608 is before the SRS decision time 616 (more than zero symbols before it). Therefore, before the SRS transmission begins, the UE can determine that the PDCCH is scheduling an uplink transmission (SPS HARQ-ACK 608) that overlaps with carrier-switching SRS 610. For example, the UE can determine that... Figure 6 The example shown illustrates a second SPS HARQ-ACK scheduled to occur during at least one symbol within handover time 612. In such a case, the conflict resolution rule instructs the UE to discard carrier-switching SRS 610 to favor uplink transmission (SPS HARQ-ACK 608). For example, the UE may determine that for a carrier of the serving cell with a slot format including DL and UL symbols, not configured for PUSCH / PUCCH transmission, whenever an SRS transmission on that carrier of the serving cell (including any interruption due to uplink or downlink RF retuning time as defined by the higher-layer parameter srs-SwitchingTimeNR) and a PUSCH / PUCCH transmission carrying HARQ-ACK overlap exactly in the same symbol and this may cause uplink transmission to exceed the UE's indicated uplink carrier aggregation capability, the UE may not send SRS. Therefore, at SRS decision time 616, the UE may determine to discard the carrier-switching SRS 610 transmission to avoid conflict with uplink transmission.

[0088] Figure 7 The timeline 700 is shown as another example of a carrier-switching SRS transmission relative to an uplink transmission (i.e., SPS release of HARQ-ACK). In this example, the UE receives PDCCH 702 from the base station at reception time 704. PDCCH 702 may include a DCI that deactivates or releases the SPS PDSCH and HARQ-ACK. For example, the PDCCH may include a DCI that releases... Figure 6The example illustrates a prior semi-persistent scheduling, which in turn allows the UE to respond to the PDCCH by sending a HARQ-ACK 706 on the PUCCH. Therefore, the PDCCH from the base station can schedule the SPS release of the HARQ-ACK from the UE. The UE also receives permission from the base station to schedule a carrier-switching SRS 708 (e.g., an aperiodic SRS) (not shown). In other examples, the carrier-switching SRS can be periodic (e.g., RRC-configured) or semi-persistent (e.g., activated via the PDSCH). The carrier-switching SRS 708 is scheduled to be transmitted on a different carrier than the SPS HARQ-ACK and therefore includes a switching time 710 (e.g., switchingTime) for retuning to this different carrier before the SRS. The carrier-switching SRS 708 also includes a switching time 712 for retuning back to the source carrier after the SRS. The SRS decision time 714 can be N2 symbols 716 (or some other timing) before the switching time 710, and therefore N2+switchingTime symbols before the carrier-switching SRS 708.

[0089] In this example, the reception time 704 of PDCCH 702, used to schedule SPS release HARQ-ACK 706, is before SRS decision time 714 (more than zero symbols before it). Therefore, before the start of SRS transmission, the UE can determine that the PDCCH is scheduling an uplink transmission (SPS release HARQ-ACK 706) that overlaps with carrier-switching SRS 708. For example, the UE can determine that... Figure 7The example shown indicates that the SPS release HARQ-ACK will be scheduled to occur during at least one symbol within the handover time 710. In such a case, the conflict resolution rule instructs the UE to discard the carrier handover type SRS 708 to favor uplink transmission (SPS release HARQ-ACK 706). For example, the UE may determine that for a carrier of the serving cell with a slot format including DL and UL symbols, not configured for PUSCH / PUCCH transmission, whenever an SRS transmission on that carrier of the serving cell (including any interruption due to uplink or downlink RF retuning time as defined by the higher-layer parameter srs-SwitchingTimeNR, switchingTimeUL, and switchingTimeDL) and a PUSCH / PUCCH transmission carrying HARQ-ACK overlap exactly in the same symbol and this may cause uplink transmission to exceed the uplink carrier aggregation capability indicated by the UE, the UE may not send SRS. Therefore, at SRS decision time 714, the UE can determine to discard the transmission of carrier-switching SRS 708, thereby avoiding conflicts with uplink transmissions.

[0090] Figure 8A timeline 800 is shown for another example of carrier-switching SRS transmission relative to uplink transmission (i.e., HARQ-ACK multiplexed on PUSCH). In this example, the UE receives a first PDCCH 802 from the base station at reception time 804 and a second PDCCH 803 from the base station at reception time 805. The first PDCCH 802 may include a DCI scheduling a PDSCH 806 containing downlink data, which in turn allows the UE to send a HARQ-ACK 808 on the PUCCH in response to the PDSCH. Thus, the first PDCCH from the base station can schedule a HARQ-ACK from the UE. Furthermore, the second PDCCH 803 can schedule a PUSCH 807 containing uplink data from the UE. The UE also receives permission (not shown) from the base station to schedule carrier-switching SRS 810 (e.g., aperiodic SRS). In other examples, carrier-switching SRS may be periodic (e.g., RRC configured) or semi-persistent (e.g., activated via PDSCH). The carrier-switching SRS 810 is scheduled to transmit on a different carrier than the HARQ-ACK, and therefore includes a switching time 812 (e.g., switchingTime) for retuning to this different carrier before the SRS. The carrier-switching SRS 810 also includes a switching time 814 for retuning back to the source carrier after the SRS. The SRS decision time 816 can be N2 symbols 818 (or some other timing) before the switching time 812, and is therefore N2+switchingTime symbols before the carrier-switching SRS 810.

[0091] In this example, the reception time 804 of the first PDCCH 802 used to schedule HARQ-ACK 808 and the reception time 805 of the second PDCCH 803 used to schedule PUSCH 807 are before the SRS decision time 816 (more than zero symbols before it). Therefore, before starting SRS transmission, the UE can determine that PUSCH 807 overlaps in time with HARQ-ACK 808 on the PUCCH, for example, at... Figure 8 As shown in the diagram. Therefore, the UE can determine that HARQ-ACK 808 will be multiplexed with PUSCH 807 (at 820). Accordingly, the UE can determine that the first PDCCH 802 is scheduling uplink transmissions (HARQ-ACK 808) that overlap with carrier-switching SRS 810. For example, the UE can determine that due to the multiplexing at 820, in Figure 8 The HARQ-ACK 808 shown in the example will be scheduled to occur during at least one symbol within the switching time 814, as in Figure 8As indicated in the document. In such cases, the conflict resolution rule instructs the UE to discard carrier-switching SRS 810 to facilitate uplink transmission (HARQ-ACK 808). For example, the UE may determine that for a carrier of the serving cell with a slot format including DL and UL symbols, not configured for PUSCH / PUCCH transmission, whenever an SRS transmission on that carrier of the serving cell (including any interruption due to uplink or downlink RF retuning time as defined by the higher-layer parameter srs-SwitchingTimeNR, switchingTimeUL, and switchingTimeDL) and a PUSCH / PUCCH transmission carrying HARQ-ACK overlap exactly in the same symbol and this may cause uplink transmission to exceed the uplink carrier aggregation capability indicated by the UE, the UE may not transmit SRS. Therefore, at SRS decision time 816, the UE may determine to discard the transmission of carrier-switching SRS 810, thereby avoiding conflict with uplink transmission.

[0092] Figure 9 A timeline 900 is shown for an example of carrier-switched SRS transmission relative to uplink transmission (i.e., periodic channel state information (P-CSI) on the PUSCH or SPS CSI on the PUCCH). In this example, the UE receives PDCCH 902 from the base station at reception time 904. PDCCH 902 may include a DCI that schedules PDSCH 906, which includes uplink data. The base station may have previously scheduled the UE to transmit P-CSI on PUCCH 907. P-CSI may include RI or CRI. The UE also receives permission (not shown) from the base station to schedule carrier-switched SRS 908 (e.g., aperiodic SRS). In other examples, carrier-switched SRS may be periodic (e.g., RRC configured) or semi-persistent (e.g., activated via PDSCH). Carrier-switched SRS 908 is scheduled to be transmitted on a different carrier than P-CSI and therefore includes a switching time 910 (e.g., switchingTime) for retuning to this different carrier before the SRS. The carrier-switching SRS 908 also includes a switching time 912 for retuning back to the source carrier after the SRS. The SRS decision time 914 may be N2 symbols 916 (or some other timing) before the switching time 910, and is therefore N2+switchingTime symbols before the carrier-switching SRS 908.

[0093] In this example, the reception time 904 of PDCCH 902, used to schedule PUSCH 906, is before the SRS decision time 914 (more than zero symbols before it). Therefore, before the SRS transmission begins, the UE can determine that PUSCH 906 overlaps in time with the P-CSI scheduled on PUCCH 907, for example, at... Figure 9 As shown in the diagram. Therefore, the UE can determine that the P-CSI on PUCCH 907 will be multiplexed with PUSCH 906 (at 918). Accordingly, the UE can determine that PDCCH 902 is scheduling uplink transmissions overlapping with carrier-switched SRS 908 (including PUSCH 906 with multiplexed P-CSI). For example, the UE can determine that due to the multiplexing at 918, in Figure 9 The P-CSI shown in the example will be scheduled to occur during at least one symbol within the switching time 912, as in Figure 9 As indicated in the document. In such cases, the conflict resolution rule instructs the UE to discard carrier-switching SRS 908 to facilitate uplink transmission (P-CSI). For example, the UE may determine that for a carrier of the serving cell with a slot format including DL and UL symbols, not configured for PUSCH / PUCCH transmission, whenever an SRS transmission on that carrier of the serving cell (including any interruption due to uplink or downlink RF retuning time as defined by the higher-layer parameter srs-SwitchingTimeNR, switchingTimeUL, and switchingTimeDL) and a PUSCH / PUCCH transmission carrying RI or CRI overlap exactly in the same symbol and this may cause uplink transmission to exceed the uplink carrier aggregation capability indicated by the UE, the UE may not transmit SRS. Therefore, at SRS decision time 914, the UE may determine to discard the transmission of carrier-switching SRS 908, thereby avoiding conflicts with uplink transmission.

[0094] Figure 10A timeline 1000 is shown for another example of carrier-switching SRS transmission relative to uplink transmission (i.e., semi-persistently scheduled CSI (SP-CSI)). In this example, the UE receives PDCCH 1002 from the base station at reception time 1004. PDCCH 1002 may include a DCI scheduling PDSCH 1005, which in turn may include a MAC-CE activating SP-CSI and causing the UE to send HARQ-ACK 1006 in response to the PDSCH. At action time 1007 after HARQ-ACK (e.g., 3 ms after sending HARQ-ACK), the UE may begin sending SP-CSI 1008, including RI or CRI. Thus, the PDCCH from the base station can schedule SP-CSI from the UE starting at action time 1007. The UE also receives permission (not shown) from the base station to schedule carrier-switching SRS 1010 (e.g., aperiodic SRS). In other examples, carrier-switching SRS can be periodic (e.g., RRC-configured) or semi-persistent (e.g., activated via PDSCH). Carrier-switching SRS 1010 is scheduled to transmit on a different carrier than SP-CSI and therefore includes a switching time 1012 (e.g., switchingTime) for retuning to this different carrier before the SRS. Carrier-switching SRS 1010 also includes a switching time 1014 for retuning back to the source carrier after the SRS. The SRS decision time 1016 can be N2 symbols 1018 (or some other timing) before the switching time 1012, and is therefore N2+switchingTime symbols before the carrier-switching SRS 1010.

[0095] In this example, action time 1007 precedes SRS decision time 1016 (within zero or more symbols prior to it). Therefore, before initiating SRS transmission, the UE can determine that the PDCCH is scheduling an uplink transmission (SP-CSI 1008) overlapping with carrier-switching SRS 1010. For example, the UE can determine that... Figure 10The SP-CSI 1008 shown in the example will be scheduled to occur during at least one symbol within the handover time 1014. In such a case, the conflict resolution rule instructs the UE to discard the carrier handover type SRS 1010 to facilitate uplink transmission (SP-CSI 1008). For example, the UE may determine that for a carrier of the serving cell with a slot format including DL and UL symbols, not configured for PUSCH / PUCCH transmission, whenever an SRS transmission on that carrier of the serving cell (including any interruption due to uplink or downlink RF retuning time as defined by the higher-layer parameter srs-SwitchingTimeNR, switchingTimeUL, and switchingTimeDL) and a PUSCH / PUCCH transmission carrying RI or CRI overlap exactly in the same symbol and this may cause uplink transmission to exceed the uplink carrier aggregation capability indicated by the UE, the UE may not transmit SRS. Therefore, at SRS decision time 1016, the UE can determine to discard the transmission of carrier-switching SRS1010, thereby avoiding conflicts with uplink transmissions.

[0096] Figure 11 The diagram illustrates a timeline 1100 for another example of carrier-switched SRS transmission relative to uplink transmission when the carrier-switched SRS is aperiodic, namely, aperiodic channel state information (A-CSI) on the PUSCH. In this example, the UE receives PDCCH 1102 from the base station at reception time 1104. PDCCH 1102 may include a DCI that schedules or triggers PUSCH 1106, which includes A-CSI (which includes RI or CRI). The UE also receives permission (not shown) from the base station to schedule carrier-switched SRS 1108 (e.g., aperiodic SRS). Carrier-switched SRS 1108 is scheduled to be transmitted on a different carrier than A-CSI and therefore includes a switching time 1110 (e.g., switchingTime) for retuning to this different carrier before the SRS. Carrier-switched SRS 1108 also includes a switching time 1112 for retuning back to the source carrier after the SRS. SRS decision time 1114 can be N2 symbols 1116 (or some other timing) before switching time 1110, and therefore N2+switchingTime symbols before carrier-switching SRS 1108.

[0097] In this example, the reception time 1104 of PDCCH 1102, used to schedule PUSCH 1106, is before the SRS decision time 1114 (more than zero symbols before it). Therefore, before the SRS transmission begins, the UE can determine that PDCCH 1102 is scheduling an uplink transmission (including PUSCH 1106 for A-CSI) that overlaps with carrier-switched SRS 1108. For example, the UE can determine that... Figure 11 The example shown indicates that A-CSI will be scheduled to occur during at least one symbol within carrier-switching SRS 1108 or handover time 1112. In such a case, the conflict resolution rule instructs the UE to discard carrier-switching SRS 1108 to favor uplink transmission (A-CSI). For example, the UE may determine that for a carrier of the serving cell with a slot format including DL and UL symbols, not configured for PUSCH / PUCCH transmission, whenever an SRS transmission on that carrier of the serving cell (including any interruption due to uplink or downlink RF retuning time as defined by the higher-layer parameter srs-SwitchingTimeNR, switchingTimeUL, and switchingTimeDL) and a PUSCH / PUCCH transmission carrying RI or CRI overlap exactly in the same symbol and this may cause uplink transmission to exceed the uplink carrier aggregation capability indicated by the UE, the UE may not transmit SRS. Therefore, at SRS decision time 1114, the UE can determine to discard the transmission of carrier-switching SRS1108, thereby avoiding conflicts with uplink transmissions.

[0098] Figure 12A timeline 1200 is shown for another example of a carrier-switched SRS transmission relative to an uplink transmission (i.e., PRACH). In this example, the UE receives PDCCH 1202 from the base station at reception time 1204. PDCCH 1202 may include a PDCCH command scheduling PRACH 1206. The UE also receives permission (not shown) from the base station to schedule carrier-switched SRS 1208 (e.g., aperiodic SRS). In other examples, carrier-switched SRS may be periodic (e.g., RRC-configured) or semi-persistent (e.g., activated via PDSCH). Carrier-switched SRS 1208 is scheduled to be transmitted on a different carrier than PRACH and therefore includes a switching time 1210 (e.g., switchingTime) for retuning to this different carrier before the SRS. Carrier-switched SRS 1208 also includes a switching time 1212 for retuning back to the source carrier after the SRS. SRS decision time 1214 can be N2 symbols 1216 (or some other timing) before switching time 1210, and therefore N2+switchingTime symbols before carrier-switching SRS 1208.

[0099] In this example, the reception time 1204 of PDCCH 1202, used to schedule PRACH 1206, is before the SRS decision time 1214 (within zero or more symbols prior to it). Therefore, before the SRS transmission begins, the UE can determine that PDCCH 1202 is scheduling an uplink transmission (PRACH 1206) that overlaps with carrier-switched SRS 1208. For example, the UE can determine that... Figure 12 The example shown indicates that the PRACH will be scheduled to occur during at least one symbol within the handover time 1212. In such a case, the conflict resolution rule instructs the UE to discard carrier-switching SRS 1208 to facilitate uplink transmission (PRACH). For example, the UE may determine that for a carrier of the serving cell with a slot format including DL and UL symbols, not configured for PUSCH / PUCCH transmission, whenever an SRS transmission on that carrier of the serving cell (including any interruptions due to uplink or downlink RF retuning times as defined by the higher-layer parameter srs-SwitchingTimeNR's switchingTimeUL and switchingTimeDL) and PRACH overlap exactly in the same symbol and this may cause uplink transmission to exceed the UE's indicated uplink carrier aggregation capability, the UE may not transmit SRS. Therefore, at SRS decision time 1214, the UE may determine to discard the transmission of carrier-switching SRS 1208, thereby avoiding conflicts with uplink transmission.

[0100] Figure 13 The diagram illustrates another example of a carrier-switching SRS transmission relative to an uplink transmission (i.e., A-CSI on the PUSCH) when the carrier-switching SRS is periodic or semi-persistent. In this example, the UE receives PDCCH 1302 from the base station at reception time 1304. PDCCH 1302 may include a DCI that schedules or triggers PUSCH 1306, which includes A-CSI. The UE is also configured with carrier-switching SRS 1308, which may be periodic (e.g., RRC-configured) or semi-persistent (e.g., activated via PDSCH). Carrier-switching SRS 1308 is scheduled to transmit on a different carrier than A-CSI and therefore includes a switching time 1310 (e.g., switchingTime) for retuning to this different carrier before the SRS. Carrier-switching SRS 1308 also includes a switching time 1112 for retuning back to the source carrier after the SRS. SRS decision time 1314 can be N2 symbols 1316 (or some other timing) before switching time 1310, and therefore N2+switchingTime symbols before carrier-switching SRS 1308.

[0101] In this example, the reception time 1304 of PDCCH 1302, used to schedule PUSCH 1306, is before the SRS decision time 1314 (zero or more symbols prior to it). Therefore, before the SRS transmission begins, the UE can determine that PDCCH 1302 is scheduling an uplink transmission (including PUSCH 1306 for A-CSI) that overlaps with carrier-switched SRS 1308. For example, the UE can determine that... Figure 13The example shown indicates that A-CSI will be scheduled to occur during at least one symbol within carrier-switching SRS 1308 or handover time 1312. In such a case, the conflict resolution rule instructs the UE to discard carrier-switching SRS 1308 to favor uplink transmission (A-CSI). For example, the UE may determine that for a carrier of the serving cell with a slot format including DL and UL symbols, not configured for PUSCH / PUCCH transmission, whenever periodic / semi-persistent SRS transmissions on that carrier of the serving cell (including any interruptions due to uplink or downlink RF retuning times as defined by the higher-layer parameter srs-SwitchingTimeNR, switchingTimeUL, and switchingTimeDL) and PUSCH transmissions carrying aperiodic CSI overlap exactly in the same symbol and this may cause uplink transmissions to exceed the uplink carrier aggregation capability indicated by the UE, the UE may not transmit periodic / semi-persistent SRS. Therefore, at SRS decision time 1314, the UE can determine to discard the transmission of carrier-switching SRS 1308, thereby avoiding conflicts with uplink transmissions.

[0102] Figure 14 The timeline 1400 illustrates other examples of carrier-switched SRS transmissions relative to uplink transmissions (including P-CSI (on PUCCH or PUSCH), non-carrier-switched SRS, or PUSCH without UCI) when the carrier-switched SRS is aperiodic. In this example, the UE receives PDCCH 1402 from the base station at reception time 1404. PDCCH 1402 schedules or triggers carrier-switched SRS 1406. Carrier-switched SRS can be aperiodic. The UE also receives a PDCCH (not shown) that may include DCIs scheduling uplink transmission 1408, such as PUSCH or PUCCH, including P-CSI with only CQI or PMI, non-carrier-switched SRS, or PUSCH without UCI. Carrier-switched SRS 1406 is scheduled to be transmitted on a different carrier than uplink transmission 1408. SRS decision time 1410 can be N2 symbols 1412 (or some other timing) prior to uplink transmission 1408.

[0103] In this example, the reception time 1404 of the PDCCH 1402 used to schedule carrier-switching SRS 1406 is before the SRS decision time 1410 (zero or more symbols prior to it). Therefore, before the SRS transmission begins, the UE can determine that the PDCCH (not shown) is scheduling an uplink transmission (uplink transmission 1408) that overlaps with carrier-switching SRS 1406. For example, the UE can determine that in Figure 14 The uplink transmission shown in the example will be scheduled to occur during at least one symbol of the handover time for carrier-switching SRS 1406. In such a case, the conflict resolution rule instructs the UE to discard uplink transmission 1408 (P-CSI with only CQI / PMI, non-carrier-switching SRS, or PUSCH without UCI) to favor carrier-switching SRS 1406. For example, the UE can determine that, for a carrier in a serving cell with a slot format including DL and UL symbols, not configured for PUSCH / PUCCH transmission, the UE may discard a PUCCH / PUSCH transmission carrying only periodic CSI including CQI / PMI, a PUSCH transmission without UCI, and / or an SRS transmission on another serving cell configured for PUSCH / PUCCH transmission whenever: the transmission and the SRS transmission on the serving cell (including any interruptions due to uplink or downlink RF retuning times as defined by switchingTimeUL and switchingTimeDL of the higher-layer parameter srs-SwitchingTimeNR) happen to overlap in the same symbol and this may cause uplink transmissions to exceed the uplink carrier aggregation capability indicated by the UE. Therefore, at SRS decision time 1410, the UE can determine to discard uplink transmission 1408 to avoid conflict with carrier-switching SRS.

[0104] Figure 15The diagram illustrates another example of a carrier-switching SRS transmission relative to an uplink transmission when the carrier-switching SRS is semi-persistent (i.e., P-CSI (on PUCCH or PUSCH), non-carrier-switching SRS, or PUSCH without UCI). In this example, the UE receives PDCCH 1502 from the base station at reception time 1504. PDCCH 1502 may include a DCI scheduling PDSCH 1505, which in turn may include MAC-CE. The MAC-CE activates a semi-persistently scheduled carrier-switching SRS 1506 starting at action time 1507, and causes the UE to send HARQ-ACK 1508 in response to the PDSCH. Action time 1507 may occur at a time interval after HARQ-ACK 1508 (e.g., 3 ms after sending HARQ-ACK). The UE also receives a PDCCH (not shown) that may include a DCI that schedules uplink transmission 1510, such as PUSCH or PUCCH, including P-CSI with only CQI or PMI, non-carrier-switched SRS, or PUSCH without UCI. Carrier-switched SRS 1506 is scheduled to be transmitted on a different carrier than uplink transmission 1510. The SRS decision time 1512 may be N2 symbols 1514 (or some other timing) prior to uplink transmission 1510.

[0105] In this example, action time 1507 precedes SRS decision time 1512 (zero or more symbols prior to it). Therefore, before initiating SRS transmission, the UE can determine that the PDCCH (not shown) is scheduling an uplink transmission (uplink transmission 1510) overlapping with carrier-switched SRS 1506. For example, the UE can determine that... Figure 15The uplink transmission shown in the example will be scheduled to occur during at least one symbol of the handover time for carrier-switching SRS1506. In such a case, the conflict resolution rules instruct the UE to discard uplink transmissions (P-CSI with only CQI / PMI, non-carrier-switching SRS, or PUSCH without UCI) to favor carrier-switching SRS1506. For example, the UE can determine that, for a carrier in a serving cell with a slot format including DL and UL symbols, not configured for PUSCH / PUCCH transmission, the UE may discard a PUCCH / PUSCH transmission carrying only periodic CSI including CQI / PMI, a PUSCH transmission without UCI, and / or an SRS transmission on another serving cell configured for PUSCH / PUCCH transmission whenever: the transmission and the SRS transmission on the serving cell (including any interruptions due to uplink or downlink RF retuning times as defined by switchingTimeUL and switchingTimeDL of the higher-layer parameter srs-SwitchingTimeNR) happen to overlap in the same symbol and this may cause uplink transmissions to exceed the uplink carrier aggregation capability indicated by the UE. Therefore, at SRS decision time 1512, the UE can determine to discard uplink transmission 1510 to avoid conflict with carrier-switching SRS.

[0106] Figure 16 The timeline 1600 is shown for another example of a carrier-switching SRS transmission relative to an uplink transmission (i.e., A-CSI (on the PUSCH)) when the carrier-switching SRS is aperiodic. In this example, the UE receives PDCCH 1602 from the base station at reception time 1604. PDCCH 1602 schedules or triggers carrier-switching SRS 1606. Carrier-switching SRS can be aperiodic. The UE also receives a PDCCH (not shown) that may include DCI, which schedules an uplink transmission 1608 on the PUSCH (e.g., A-CSI with only CQI or PMI). Carrier-switching SRS 1606 is scheduled to be transmitted on a different carrier than the uplink transmission 1608. The SRS decision time 1610 can be N2 symbols 1612 (or some other timing) preceding the uplink transmission 1608.

[0107] In this example, the reception time 1604 of the PDCCH 1602 used to schedule carrier-switching SRS 1606 is before the SRS decision time 1610 (zero or more symbols before it). Therefore, before the SRS transmission begins, the UE can determine that the PDCCH (not shown) is scheduling an uplink transmission (uplink transmission 1608) that overlaps with carrier-switching SRS 1606. For example, the UE can determine that in Figure 16 The example shown illustrates an uplink transmission that will be scheduled to occur during at least one symbol of the handover time for carrier-switching SRS1606. In this case, the conflict resolution rule instructs the UE to discard uplink transmissions (A-CSI with only CQI / PMI) to favor carrier-switching SRS1606. For example, the UE may determine that, for a carrier of the serving cell with a slot format including DL and UL symbols, not configured for PUSCH / PUCCH transmission, the UE may discard a PUSCH transmission carrying only aperiodic CSI including CQI / PMI whenever the following occurs: the transmission and the aperiodic SRS transmission on the serving cell (including any interruptions due to uplink or downlink RF retuning times as defined by switchingTimeUL and switchingTimeDL of the higher-layer parameter srs-SwitchingTimeNR) overlap exactly in the same symbol and this may cause the uplink transmission to exceed the uplink carrier aggregation capability indicated by the UE. Therefore, at SRS decision time 1610, the UE can decide to discard uplink transmission 1608, thereby avoiding conflict with carrier-switching SRS.

[0108] Figure 17 This is a schematic diagram 1700 illustrating an example of a call flow between UE 1702 and base station 1704. The UE can receive SRS configuration 1706 from the base station. SRS configuration 1706 can configure the UE to transmit carrier-switching SRS, which can be periodic, semi-persistent, or aperiodic (in response to triggering in permission). The UE can transmit carrier-switching SRS on an uplink component carrier different from the source carrier used to transmit uplink data (e.g., in response to PDCCH). The UE can determine the scheduling time for transmitting carrier-switching SRS based on the SRS configuration.

[0109] UE 1702 can then receive PDCCH 1708 from base station 1704. PDCCH 1708 can schedule or trigger uplink transmissions by the UE on the source carrier. For example, PDCCH 1708 can schedule HARQ-ACKs on the PUCCH in response to the PDSCH (as described above). Figure 5As described above, HARQ-ACK for semi-persistent scheduling on PUCCH (as mentioned above) Figure 6 (as described above), or in response to the HARQ-ACK released by the SPS in PDCCH 1708 (as mentioned above). Figure 7 (As described). UE1702 can also receive a second PDCCH 1710 from base station 1704 for another uplink transmission that schedules the UE, and the HARQ-ACK can be multiplexed with this other uplink transmission, such as the one described above. Figure 8 As described above. In another example, uplink transmissions could be SRs indicated by a higher layer of the UE. In yet another example, the PDCCH 1708 could schedule uplink data on the PUSCH multiplexed with P-CSI, including RI or CRI, such as the above-described... Figure 9 As described above. In another example, PDCCH 1708 can schedule the activation of CSI for semi-persistent scheduling including RI or CRI (as mentioned above). Figure 10 As described above), or PDCCH 1708 can trigger A-CSI carrying RI or CRI (such as the above regarding...). Figure 11 (As described above). In additional examples, PDCCH 1708 may include PDCCH commands that schedule PRACH transmissions, such as those mentioned above. Figure 12 As described above. In another example, PDCCH 1708 may include a DCI that triggers a PUSCH carrying A-CSI, such as the one mentioned above. Figure 13 As described. In another example, PDCCH 1708 can schedule uplink data including P-CSI (including CQI or PMI only) on PUCCH or PUSCH, uplink data on PUSCH without UCI, or non-carrier-switched SRS (such as those mentioned above). Figure 14 Or as described in 15), or PDCCH 1708 can trigger A-CSI on PUSCH that includes only CQI or PMI (such as the above regarding Figure 16 (As described).

[0110] Next, at 1712, UE 1702 determines the scheduled or triggered uplink transmission. For example, the UE may determine the uplink transmission as a HARQ-ACK corresponding to dynamic permission (as mentioned above). Figure 5 As described above, semi-persistent scheduling of HARQ-ACK (as mentioned above) Figure 6 As described above, HARQ-ACK in response to SPS release (as mentioned above) Figure 7 (as described above), or HARQ-ACK multiplexed with another uplink transmission (such as the one mentioned above). Figure 8(As described above). In another example, the UE may identify the uplink transmission as an SR indicated by a higher layer of the UE. In yet another example, the UE may identify the uplink transmission as a P-CSI multiplexed with uplink data on the PUSCH, including RI or CRI, as described above. Figure 9 As described above. In another example, the UE can determine the uplink transmission as a CSI with semi-persistent scheduling including RI or CRI (as described above regarding...). Figure 10 (as described above), or A-CSI carrying RI or CRI (as mentioned above). Figure 11 (As described). In additional examples, the UE may identify an uplink transmission as a PRACH transmission, as described above. Figure 12 As described above. In another example, the UE may identify the uplink transmission as A-CSI on the PUSCH, as described above regarding... Figure 13 As described. In another example, the UE can determine uplink transmissions as P-CSI on the PUCCH or PUSCH that only includes CQI or PMI, uplink data on the PUSCH that does not carry UCI, or non-carrier-switched SRS (as described above). Figure 14 Or as described in 15), or A-CSI on PUSCH that only includes CQI or PMI (as mentioned above). Figure 16 (As described).

[0111] Then, at 1714, UE 1702 determines whether to discard the uplink transmission or the carrier-switching SRS based on the timing between the reception of the PDCCH and the scheduling time for transmitting the carrier-switching SRS. The UE can also determine whether to discard the uplink transmission or the carrier-switching SRS based on another timing between the uplink transmission and the carrier-switching SRS. For example, the UE can determine to discard either the carrier-switching SRS or the uplink transmission based on the conflict resolution rules described above. The UE can then transmit either the carrier-switching SRS or the uplink transmission to base station 1704 (at 1716) based on the determination at 1714.

[0112] For example, if the UE determines that the uplink transmission is a HARQ-ACK corresponding to dynamic permission (see...) Figure 5 HARQ-ACK for semi-persistent scheduling (see) Figure 6 ) or in response to the SPS release of HARQ-ACK (see Figure 7If the UE determines to discard a carrier-switching SRS in response to identifying the following two conditions: (1) the PDCCH 1708 scheduled on the PUCCH in response to the HARQ-ACK of the PDCCH or PDSCH is received at least N2+switchingTime symbols before the scheduling time for transmitting the SRS, and (2) the HARQ-ACK overlaps with the scheduling time for transmitting the SRS or the carrier-switching time associated with the SRS, as stated above regarding Figure 5-7 As described.

[0113] In another example, if the UE determines that the uplink transmission is a HARQ-ACK multiplexed with another uplink transmission scheduled by the second PDCCH 1710 (see [link to example]). Figure 8 If the UE determines that the carrier-switching SRS is dropped in response to the identification of the following two items: (1) the PDCCH 1708 scheduled on the PUCCH in response to the HARQ-ACK of the PDSCH and the second PDCCH 1710 scheduled on the PUSCH multiplexed with the HARQ-ACK are received at least N2+switchingTime symbols before the scheduling time for transmitting the SRS, and (2) the multiplexed HARQ-ACK overlaps with the scheduling time for transmitting the SRS or the carrier-switching time associated with the SRS, as stated above regarding Figure 8 As described.

[0114] In another example, if the UE determines that the uplink transmission is an SR indicated by a higher layer of the UE, the UE can determine to discard a carrier-switching SRS in response to identifying that the SR overlaps with the scheduling time for transmitting the SRS or the carrier handover time associated with the SRS.

[0115] In another example, if the UE determines that the uplink transmission is a P-CSI multiplexed with uplink data on the PUSCH, including RI or CRI (see [link to P-CSI]). Figure 9 If the UE can determine to discard a carrier-switching SRS in response to identifying the following two items: (1) the PDCCH 1708 of the uplink data multiplexed with the P-CSI scheduled on the PUSCH is received at least N2+switchingTime symbols before the scheduling time for transmitting the SRS, and (2) the P-CSI overlaps with the scheduling time for transmitting the SRS or the carrier-switching time associated with the SRS, as stated above regarding Figure 9 As described.

[0116] In another example, if the UE determines that the uplink transmission is a CSI with semi-persistent scheduling including RI or CRI (see [reference]). Figure 10If the UE can determine to discard a carrier-switching SRS in response to identifying the following: (1) activation of SP-CSI by PDCCH 1708 scheduling at an action time at least N2+switchingTime symbols prior to the scheduling time for transmitting the SRS, and (2) the CSI of the semi-persistent scheduling overlapping with the scheduling time for transmitting the SRS or the carrier-switching time associated with the SRS, as stated above regarding Figure 10 As described, the action time can be based on the time required for the transmission of the HARQ-ACK associated with the channel carrying the activation command for SP-CSI (e.g., 3ms after the HARQ-ACK).

[0117] In an additional example, if the UE determines the uplink transmission to be an A-CSI carrying RI or CRI (see [reference]). Figure 11 If the UE can determine to discard a carrier-switching SRS in response to identifying the following two conditions: (1) the PDCCH 1708 that schedules or triggers the A-CSI is received at least N2+switchingTime symbols before the scheduling time for transmitting the SRS, and (2) the A-CSI overlaps with the scheduling time for transmitting the SRS or the carrier-switching time associated with the SRS, as stated above regarding Figure 11 As described.

[0118] In another example, if the UE determines the uplink transmission as a PRACH transmission (see...) Figure 12 If the UE can determine to discard a carrier-switching SRS in response to identifying the following two items: (1) the PDCCH 1708, which includes the PDCCH command for scheduling the PRACH transmission, is received at least N2+switchingTime symbols before the scheduling time for transmitting the SRS, and (2) the PRACH overlaps with the scheduling time for transmitting the SRS or the carrier-switching time associated with the SRS, as stated above regarding Figure 12 As described.

[0119] In another example, if the UE determines that the uplink transmission is A-CSI on the PUSCH (see...) Figure 13 If the UE can determine to discard a carrier-switching SRS in response to identifying the following two items: (1) the PDCCH 1708 that schedules or triggers the PUSCH carrying the A-CSI is received at least N2+switchingTime symbols before the scheduling time for transmitting the SRS, and (2) the A-CSI overlaps with the scheduling time for transmitting the SRS or the carrier-switching time associated with the SRS, as stated above regarding Figure 13 As described.

[0120] In another example, if the UE determines the uplink transmission to be a P-CS on the PUCCH or PUSCH that only includes CQI or PMI, uplink data on the PUSCH that does not carry UCI, or a non-carrier-switched SRS, and if the carrier-switched SRS is aperiodic (see [link to example]), Figure 14 If the UE determines to drop the uplink transmission in response to identifying the following two conditions: (1) the PDCCH 1708 for scheduling or triggering carrier-switching SRS is received at least N2 symbols before the scheduling time for transmitting the uplink transmission, and (2) the uplink transmission overlaps with the scheduling time for transmitting the SRS or the carrier-switching time associated with the SRS, as stated above regarding Figure 14 As described.

[0121] In another example, if the UE determines the uplink transmission to be P-CSI on PUCCH or PUSCH that only includes CQI or PMI, uplink data on PUSCH that does not carry UCI, or non-carrier-switched SRS, and if the carrier-switched SRS is semi-persistently scheduled (see [link to example]), Figure 15 If the UE determines to drop the uplink transmission in response to identifying the following two items: (1) activation of a semi-persistent carrier-switching SRS by the PDCCH 1708 scheduler at an action time starting at least N2 symbols prior to the scheduling time for transmitting the uplink transmission, and (2) the uplink transmission overlaps with the scheduling time for transmitting the SRS or the carrier-switching time associated with the SRS, as stated above regarding Figure 15 As described, the action time can be based on the time required for transmitting the HARQ-ACK associated with the channel carrying the activation command for the semi-persistent carrier switching type SRS (e.g., 3 ms after the HARQ-ACK).

[0122] In an additional example, if the UE determines the uplink transmission as an A-CSI on the PUSCH consisting only of CQI or PMI, and if the carrier-switching SRS is aperiodic (see...), Figure 16 If the UE determines to drop an uplink transmission in response to identifying the following two conditions: (1) the PDCCH 1708 for scheduling or triggering carrier-switching SRS is received at least N2 symbols before the scheduling time for transmitting A-CSI, and (2) the PUSCH transmission carrying A-CSI overlaps with the scheduling time for transmitting SRS or the carrier-switching time associated with SRS, as stated above regarding Figure 16 As described.

[0123] Figure 18This is a flowchart 1800 of a wireless communication method. This method can be performed by a UE (e.g., UE 104, 350, 1702; device 1902). Optional aspects are shown in dashed lines. This method allows the UE to effectively resolve conflicts between different types of uplink transmissions and carrier-switched SRS based on the timing between the reception of the PDCCH for scheduling uplink transmissions and the scheduling time for transmitting carrier-switched SRS.

[0124] At position 1802, the UE receives the PDCCH from the base station, and the PDCCH is scheduled for uplink transmission on the first carrier. For example, position 1802 can be... Figure 19 The PDCCH component 1940 is used for execution. For example, refer to... Figure 17 UE 1702 can receive DCI in PDCCH 1708 from base station 1704, which is scheduled for uplink transmission on uplink component carriers (e.g., source carriers) (as mentioned above). Figure 5-16 This describes one type of uplink transmission among various uplink transmissions.

[0125] At position 1804, the UE can receive a second PDCCH from the base station, where the second PDCCH schedules the PUSCH. For example, position 1804 can be... Figure 19 The PDCCH component 1940 is used for execution. For example, refer to... Figure 17 UE 1702 can receive DCI in the second PDCCH 1710 from base station 1704, which is scheduled uplink data on PUSCH.

[0126] At position 1805, the UE can receive a second PDCCH from the base station, which is scheduled for SRS on a second carrier. For example, position 1805 can be... Figure 19 The PDCCH component 1940 is used for execution. For example, refer to... Figure 14-17 UE 1702 can receive DCI in PDCCH 1402, 1502 or 1602 from base station 1704. The DCI is scheduled carrier switching type SRS1406, 1506 or 1606 respectively.

[0127] At 1806, the UE determines whether to discard either the uplink transmission or the SRS transmission based on the timing between the reception time on the PDCCH and the scheduling time for transmitting the SRS on a second carrier different from the first carrier. For example, 1806 can be determined by... Figure 19 The decision component 1944 is used to execute. For example, refer to... Figure 17At 1714, UE 1702 can determine whether to discard the uplink transmission (e.g., as mentioned above) in response to the recognition that the reception time of the DCI that schedules or triggers uplink transmission in PDCCH 1708 (e.g., the last symbol of the PDCCH) occurs at least a specific amount of time (e.g., N2 + switchingTime symbols) before the scheduling time for transmitting carrier-switching SRS (e.g., as configured in SRS configuration 1706 or another PDCCH). Figure 5-16 This refers to either any uplink transmission described in the uplink transmission description or carrier-switched SRS. Carrier-switched SRS can be configured for transmission on uplink component carriers that are different from the source carrier used for uplink transmission. The UE can also determine whether to discard either the uplink transmission or carrier-switched SRS based on the timing between the uplink transmission and SRS. For example, the UE can determine whether to discard the uplink transmission or carrier-switched SRS in response to overlap between the uplink transmission and carrier-switched SRS (including their handover time).

[0128] The timing can be based on a first digital scheme for a first cell carrying the scheduled SRS and a second digital scheme for a second cell including a second carrier. The timing can also include a handover time for switching from the first carrier to the second carrier to transmit the SRS. The timing can also be based on a digital scheme, wherein the digital scheme is a digital scheme with the minimum subcarrier spacing (SCS) among one or more cell schemes, said one or more cells including at least a cell receiving the PDCCH, a cell scheduling cross-carrier SRS, and a cell transmitting uplink transmissions. For example, the value of N2 above can be calculated based on the worst-case carrier between the carriers involved in carrier-switching SRS. Therefore, the timing can be based on the subcarrier spacing (e.g., a digital scheme) for the first or second carrier, and the subcarrier spacing can include a smaller SCS between the first and second carriers. Both the source component carrier and the target component carrier can be cross-carrier scheduled. For example, the value of N2 can be calculated based on μ from Tables 1 and 2, respectively, for UE processing capability 1 and UE processing capability 2, where μ corresponds to either the subcarrier spacing of the downlink used to transmit PDCCH or the subcarrier spacing of the uplink used to transmit PUSCH, which results in the maximum UE PUSCH preparation time (Tproc,2). For example, the value of μ in either table corresponding to the digital scheme with the smallest subcarrier spacing among various digital schemes (e.g., μ = 0) can be the worst-case carrier that results in the maximum PUSCH preparation time.

[0129] At point 1806, the decision regarding whether to use carrier-dropped SRS or uplink transmission likely depends on the uplink transmission. The UE can determine the uplink transmission as described above. Figure 5-16 One of the various uplink transmissions described herein, and the carrier-switched SRS or uplink transmission is discarded according to the conflict resolution rules described above.

[0130] Furthermore, the decision at 1806 regarding whether to use carrier-discarding SRS or uplink transmission can be based on the timing between the reception time of the second PDCCH received at 1805 and the scheduling time used for uplink transmission. For example, refer to... Figure 17 At 1714, UE 1702 may determine whether to discard the uplink transmission (e.g., as mentioned above) in response to the recognition that the reception time of the DCI for scheduling or triggering carrier-switching SRS in the second PDCCH (e.g., the last symbol of the second PDCCH) occurs at least a specific amount of time (e.g., N2 symbols) before the scheduling time for transmitting uplink transmissions (e.g., uplink transmissions 1408, 1510, or 1608). Figure 14-16 (Any uplink transmission described in those uplink transmissions) or carrier-switched SRS.

[0131] In one example, at 1808, the UE can determine that the uplink transmission is a HARQ-ACK on the PUCCH, where HARQ-ACK corresponds to dynamic permission, for example, as per [reference to...]. Figure 5 As described. For example, 1808 could be... Figure 19 The determination component 1942 performs this action. In such a case, the SRS can be dropped in response to an overlap between the HARQ-ACK and either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

[0132] In another example, at 1810, the UE can determine that the uplink transmission is an SPS HARQ-ACK on the PUCCH, where the PDCCH activates the SPS HARQ-ACK, for example, as regarding Figure 6 As described. For example, 1810 could be... Figure 19 The determination component 1942 performs this action. In such a case, the SRS can be discarded in response to an overlap between the SPS HARQ-ACK and either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

[0133] In another example, at 1812, the UE can determine that the uplink transmission is a HARQ-ACK on the PUCCH, where the PDCCH releases the SPS HARQ-ACK, for example, as regarding Figure 7 As described. For example, 1812 could be... Figure 19 The determination component 1942 performs this action. In such a case, the SRS can be dropped in response to an overlap between the HARQ-ACK and either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

[0134] In another example, at 1814, the UE can determine that the uplink transmission is a HARQ-ACK on the PUCCH, where the HARQ-ACK is multiplexed with a PUSCH scheduled by the second PDCCH at 1804, and the UE can further determine whether to discard either the uplink transmission or the SRS transmission based on the reception time of the second PDCCH, for example, as per [reference to...]. Figure 8 As described. For example, 1814 could be... Figure 19 The determination component 1942 performs this action. In such a case, the SRS can be discarded in response to an overlap between the PUSCH and either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

[0135] In another example, at point 1816, the UE can determine that the uplink transmission is SR. For example, point 1816 can be determined by... Figure 19 The determination component 1942 performs this action. In such a case, the SRS can be discarded in response to an overlap between the SR and either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

[0136] In another example, at 1818, the UE can determine that the uplink transmission is on a PUSCH multiplexed with a P-CSI that includes either RI or CRI on the PUCCH, for example, as per [reference to...]. Figure 9 As described. For example, 1818 could be... Figure 19 The determination component 1942 performs this action. In such a case, the SRS can be discarded in response to an overlap between the PUSCH and either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

[0137] In another example, at 1820, the UE can determine that the uplink transmission includes an SP-CSI having either an RI or a CRI, and the UE can further determine whether to discard either the uplink transmission or the SRS based on the timing between the action time associated with the SP-CSI and the scheduling time for sending the SRS, for example, as per [reference to...]. Figure 10As described. For example, 1820 could be... Figure 19 The determination component 1942 performs this action. In such a case, the SRS can be dropped in response to an overlap between the SP-CSI and the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS. The action time can be based at least on the time for transmitting the HARQ-ACK associated with the channel carrying the activation command for the SP-CSI.

[0138] In another example, at 1822, the UE can determine that the uplink transmission is on a PUSCH that includes one of the RI or CRI associated with A-CSI, for example, as per [reference to...]. Figure 11 As described. For example, 1822 could be... Figure 19 The determination component 1942 performs this action. In such a case, the SRS can be discarded in response to an overlap between the PUSCH and either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

[0139] In another example, at 1824, the UE can determine that the uplink transmission is on PRACH, for example, as per [reference to...]. Figure 12 As described. For example, 1824 could be... Figure 19 The determination component 1942 performs this action. In such a case, the SRS can be discarded in response to an overlap between the PRACH and the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

[0140] In another example, at 1826, the UE can determine that the uplink transmission includes A-CSI on the PUSCH, for example, as per [reference to...]. Figure 13 As described. For example, 1826 could be... Figure 19 The determination component 1942 performs this action. In such a case, the SRS can be discarded in response to the PUSCH overlapping with either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS, and the SRS being either a periodic SRS (P-SRS) or a semi-persistently scheduled SRS (SPS SRS).

[0141] In another example, at 1828, the UE can determine that the uplink transmission includes one of the following: a P-CSI on either the PUCCH or PUSCH that includes either CQI only or PMI only; a PUSCH without UCI; or a non-carrier-switched SRS, for example, as per [reference to...]. Figure 14 As described. For example, 1828 could be... Figure 19The determination component 1942 performs this action. In such a case, the uplink transmission can be discarded in response to an overlap between the uplink transmission and the scheduling time for transmitting the SRS or the carrier handover time associated with the SRS, and the SRS is an aperiodic SRS (A-SRS). In another example, also at 1828, the UE can determine that the uplink transmission includes one of the following: a P-CSI on one of the PUCCH or PUSCH including either CQI only or PMI only; a PUSCH without UCI; or a non-carrier handover type SRS, and the UE can further determine whether to discard the uplink transmission or the SRS transmission based on the timing between the action time associated with the SRS and the time for transmitting the uplink transmission, where the SRS is an SP-SRS, for example, as per [reference to...]. Figure 15 As described. In such a case, the uplink transmission can be dropped in response to an overlap between the uplink transmission and the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS. The action time can be based at least on the time used for transmitting the HARQ-ACK associated with the channel carrying the activation command for SP-SRS.

[0142] Finally, at 1830, the UE can determine that the uplink transmission includes an A-CSI on the PUSCH that includes either CQI only or PMI only, for example, as per the context... Figure 16 As described. For example, 1830 could be... Figure 19 The determination component 1942 performs this action. In such a case, the uplink transmission may be dropped in response to an overlap between the uplink transmission and the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS, and the SRS is A-SRS.

[0143] Figure 19This is a schematic diagram 1900 illustrating an example of a hardware implementation for device 1902. Device 1902 is a UE and includes: a cellular baseband processor 1904 (also referred to as a modem) coupled to a cellular RF transceiver 1922 and one or more Subscriber Identity Module (SIM) cards 1920; an application processor 1906 coupled to a Secure Digital Card (SD) card 1908 and a screen 1910; a Bluetooth module 1912; a Wireless Local Area Network (WLAN) module 1914; a Global Positioning System (GPS) module 1916; and a power supply 1918. The cellular baseband processor 1904 communicates with UE 104 and / or BS 102 / 180 via the cellular RF transceiver 1922. The cellular baseband processor 1904 may include computer-readable media / memory. The computer-readable media / memory may be non-transitory. The cellular baseband processor 1904 is responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by the cellular baseband processor 1904, the software causes the cellular baseband processor 1904 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1904 during software execution. The cellular baseband processor 1904 also includes a receiving component 1930, a communication manager 1932, and a transmitting component 1934. The communication manager 1932 includes one or more of the components shown. The components within the communication manager 1932 can be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1904. The cellular baseband processor 1904 can be a component of the UE 350 and can include at least one of the TX processor 368, the RX processor 356, and the controller / processor 359 and / or memory 360. In one configuration, the device 1902 can be a modem chip and only include the baseband processor 1904; in another configuration, the device 1902 can be the entire UE (e.g., see...). Figure 3 (350) and includes the aforementioned additional modules of device 1902.

[0144] Communication manager 1932 includes a PDCCH component 1940 configured to receive, for example, a PDCCH scheduled for uplink transmissions on a first carrier from a base station, as described in conjunction with 1802. PDCCH component 1940 may also be configured to receive a second PDCCH scheduled for PUSCH from a base station, as described in conjunction with 1804. PDCCH component 1940 may also be configured to receive a second PDCCH scheduled for SRS on a second carrier from a base station, as described in conjunction with 1805. Communication manager 1932 also includes a determining component 1942 that receives input from PDCCH component 1940 in the form of downlink data in the PDCCH and is configured to determine the uplink transmissions scheduled by the PDCCH.

[0145] In one example, determining component 1942 can be configured to determine that the uplink transmission is a HARQ-ACK on the PUCCH, where the HARQ-ACK corresponds to dynamic permission, for example, as described in conjunction with 1808. In another example, determining component 1942 can be configured to determine that the uplink transmission is an SPS HARQ-ACK on the PUCCH, where the PDCCH activates the SPSHARQ-ACK, for example, as described in conjunction with 1810. In another example, determining component 1942 can be configured to determine that the uplink transmission is a HARQ-ACK on the PUCCH, where the PDCCH releases the SPS HARQ-ACK, for example, as described in conjunction with 1812. In another example, determining component 1942 can be configured to determine that the uplink transmission is a HARQ-ACK on the PUCCH, where the HARQ-ACK is multiplexed with a PUSCH scheduled by a second PDCCH, for example, as described in conjunction with 1814. In another example, determining component 1942 can be configured to determine that the uplink transmission is an SR, for example, as described in conjunction with 1816.

[0146] In another example, determining component 1942 can be configured to determine that the uplink transmission is on a PUSCH multiplexed with a P-CSI that includes one of the RI or CRI on the PUCCH, for example, as described in conjunction with 1818. In another example, determining component 1942 can be configured to determine that the uplink transmission includes an SP-CSI having one of the RI or CRI, for example, as described in conjunction with 1820. In another example, determining component 1942 can be configured to determine that the uplink transmission is on a PUSCH that includes one of the RI or CRI associated with an A-CSI, for example, as described in conjunction with 1822. In another example, determining component 1942 can be configured to determine that the uplink transmission is on a PRACH, for example, as described in conjunction with 1824. In another example, determining component 1942 can be configured to determine that the uplink transmission includes an A-CSI on the PUSCH, for example, as described in conjunction with 1826.

[0147] In another example, determining component 1942 may be configured to determine that the uplink transmission includes one of the following: a P-CSI on one of the PUCCH or PUSCH including either CQI only or PMI only; a PUSCH without UCI; or a non-carrier-switched SRS, for example, as described in conjunction with 1828. In another example, determining component 1942 may be configured to determine that the uplink transmission includes an A-CSI on the PUSCH including either CQI only or PMI only, for example, as described in conjunction with 1830.

[0148] The communication manager 1932 also includes a decision component 1944, which receives input from the PDCCH component 1940 in the form of a PDCCH reception time, and from the decision component 1942 input including information about the scheduled uplink transmission. The decision component 1944 is configured to determine, for example, whether to discard an uplink transmission or an SRS transmission based on a timing between the PDCCH reception time and a scheduling time for transmitting an SRS on a second carrier different from the first carrier, as described in conjunction with 1806. The decision component 1944 can also be configured to further determine whether to discard an uplink transmission or an SRS transmission based on a reception time of a second PDCCH that schedules a PUSCH, as described in conjunction with 1814. The decision component 1944 can also be configured to determine whether to discard an uplink transmission or an SRS transmission based on a timing between the reception time of a second PDCCH that schedules an SRS transmission and a scheduling time for uplink transmission, as described in conjunction with 1806, 1828, and 1830. The decision component 1944 can also be configured to further determine whether to discard either the uplink transmission or the SRS based on timing between the action time associated with the uplink transmission and the scheduling time for transmitting the SRS, for example, as described in conjunction with 1820. The decision component 1944 can also be configured to further determine whether to discard either the uplink transmission or the SRS based on timing between the action time associated with the SRS and the time for transmitting the uplink transmission, for example, as described in conjunction with 1828. The decision component 1944 can also be configured to decide to discard the SRS in response to an overlap between the uplink transmission and the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS, for example, as described in conjunction with 1808, 1810, 1812, 1814, 1816, 1818, 1820, 1822, 1824, and 1826. The determining component 1944 can also be configured to decide to drop an uplink transmission in response to an overlap between an uplink transmission and a scheduling time for transmitting the SRS or a carrier switching time associated with the SRS, for example, as described in conjunction with 1828 and 1830.

[0149] The apparatus may include the function performed in the above-mentioned Figure 18 The flowchart shows the algorithm's additional components in each block of the algorithm. Therefore, in the above... Figure 18 Each block in the flowchart can be executed by a component, and the apparatus can include one or more of those components. A component can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0150] In one configuration, the apparatus 1902 (and in particular, the cellular baseband processor 1904) includes: a unit for receiving a PDCCH from a base station, the PDCCH being scheduled for uplink transmission on a first carrier; and a unit for determining whether to discard either the uplink transmission or the SRS transmission based on a timing between the PDCCH reception time and the scheduling time for transmitting an SRS on a second carrier different from the first carrier.

[0151] In one configuration, timing can be based on the subcarrier spacing used for the first carrier or the second carrier. In another configuration, the subcarrier spacing can include a smaller subcarrier spacing between the first carrier and the second carrier.

[0152] In one configuration, the receiving unit can be configured to receive a second PDCCH from a base station, the second PDCCH being scheduled for SRS on a second carrier. The determining unit can be configured to determine, based on a timing between the reception time of the second PDCCH and the scheduling time for uplink transmission, whether to discard either the uplink transmission or the SRS transmission.

[0153] In one configuration, timing may include a switching time for switching from a first carrier to a second carrier to transmit SRS.

[0154] In one configuration, device 1902 (and in particular, cellular baseband processor 1904) may include: a unit for determining that the uplink transmission is a HARQ-ACK on the PUCCH, wherein the HARQ-ACK corresponds to dynamic permission; and wherein the SRS is dropped in response to the HARQ-ACK overlapping with either the scheduling time for transmitting the SRS or the carrier handover time associated with the SRS.

[0155] In one configuration, device 1902 (and in particular, cellular baseband processor 1904) may include: a unit for determining that the uplink transmission is an SPS HARQ-ACK on the PUCCH, wherein the PDCCH activates the SPS HARQ-ACK; and wherein the SRS is dropped in response to an overlap between the SPS HARQ-ACK and either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

[0156] In one configuration, device 1902 (and in particular, cellular baseband processor 1904) may include: a unit for determining that the uplink transmission is a HARQ-ACK on the PUCCH, wherein the PDCCH releases the SPS HARQ-ACK; wherein the SRS is dropped in response to the HARQ-ACK overlapping with either the scheduling time for transmitting the SRS or the carrier handover time associated with the SRS.

[0157] In one configuration, device 1902 (and in particular, cellular baseband processor 1904) may include: a unit for receiving a second PDCCH from a base station, the second PDCCH scheduling a PUSCH; and a unit for determining whether an uplink transmission is a HARQ-ACK on the PUCCH, wherein the HARQ-ACK is multiplexed with the PUSCH; wherein determining whether to discard either an uplink transmission or a SRS transmission is based on the reception time of the second PDCCH; and wherein the SRS is discarded in response to an overlap between the PUSCH and either the scheduling time for transmitting the SRS or the carrier handover time associated with the SRS.

[0158] In one configuration, device 1902 (and in particular, cellular baseband processor 1904) may include: a unit for determining that the uplink transmission is an SR; and wherein the SRS is dropped in response to an overlap between the SR and either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

[0159] In one configuration, device 1902 (and in particular, cellular baseband processor 1904) may include: a unit for determining that the uplink transmission is on a PUSCH multiplexed with a P-CSI multiplexed with either RI or CRI on the PUCCH; wherein the SRS is dropped in response to the PUSCH overlapping with either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

[0160] In one configuration, device 1902 (and in particular, cellular baseband processor 1904) may include: a unit for determining whether an uplink transmission includes an SP-CSI having either an RI or a CRI; wherein determining whether to discard either the uplink transmission or the SRS transmission is based on timing between the action time associated with the SP-CSI and the scheduling time for transmitting the SRS; wherein the SRS is discarded in response to an overlap between the SP-CSI and either the scheduling time for transmitting the SRS or the carrier handover time associated with the SRS. The action time may be based at least on the time for transmitting a HARQ-ACK associated with the channel carrying an activation command for the SP-CSI.

[0161] In one configuration, device 1902 (and in particular, cellular baseband processor 1904) may include: a unit for determining that the uplink transmission is on a PUSCH that includes either an RI or a CRI associated with A-CSI; wherein the SRS is dropped in response to the PUSCH overlapping with either a scheduling time for transmitting the SRS or a carrier switching time associated with the SRS.

[0162] In one configuration, device 1902 (and in particular, cellular baseband processor 1904) may include: a unit for determining that the uplink transmission is on PRACH; wherein the SRS is dropped in response to an overlap between PRACH and either a scheduling time for transmitting the SRS or a carrier switching time associated with the SRS.

[0163] In one configuration, device 1902 (and in particular, cellular baseband processor 1904) may include: a unit for determining an uplink transmission including an A-CSI on the PUSCH; wherein the SRS is discarded in response to an overlap between the PUSCH and a scheduling time for transmitting the SRS or a carrier switching time associated with the SRS, and the SRS is either a P-SRS or an SPS SRS.

[0164] In one configuration, device 1902 (and in particular, cellular baseband processor 1904) may include: a unit for determining that an uplink transmission includes one of the following: a P-CSI on one of PUCCH or PUSCH including only CQI or only PMI; or a carrier-switched SRS; wherein the uplink transmission is dropped in response to an overlap between the uplink transmission and a scheduling time for transmitting the SRS or a carrier-switching time associated with the SRS and the SRS is an A-SRS.

[0165] In one configuration, device 1902 (and in particular, cellular baseband processor 1904) may include: a unit for determining whether an uplink transmission includes one of the following: P-CSI on one of PUCCH or PUSCH including either CQI only or PMI only; or non-carrier-switching SRS; wherein determining whether to discard either the uplink transmission or the SRS transmission is based on timing between the action time associated with the SRS and the time for transmitting the uplink transmission, wherein the SRS is SP-SRS; wherein the uplink transmission is discarded in response to an overlap between the uplink transmission and the scheduling time for transmitting the SRS or the carrier-switching time associated with the SRS. The action time may be at least based on the time for transmitting HARQ-ACK associated with the channel carrying an activation command for SP-SRS.

[0166] In one configuration, device 1902 (and in particular, cellular baseband processor 1904) may include: a unit for determining an uplink transmission including an A-CSI on the PUSCH, comprising either CQI only or PMI only; wherein the uplink transmission is dropped in response to an overlap between the uplink transmission and a scheduling time for transmitting SRS or a carrier switching time associated with the SRS and the SRS is A-SRS.

[0167] In one configuration, device 1902 (and in particular, cellular baseband processor 1904) may include: a unit for determining that an uplink transmission includes a PUSCH without UCI; wherein the uplink transmission is dropped in response to overlap with either a scheduling time for transmitting SRS or a carrier handover time associated with SRS.

[0168] In one configuration, timing can be based on a digital scheme. The digital scheme can be the digital scheme with the minimum SCS among one or more cell digital schemes. The one or more cells can include at least a cell in which PDCCH is received, a cell in which SRS is scheduled on a second carrier, or a cell in which uplink transmissions are transmitted on a first carrier.

[0169] The aforementioned unit may be one or more components of the device 1902 configured to perform the functions described therein. As described above, the device 1902 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the aforementioned unit may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions described therein.

[0170] Therefore, aspects of this disclosure improve the effectiveness of conflict resolution between uplink transmissions scheduled from the PDCCH and carrier-switching SRS. If the decision time for transmitting carrier-switching SRS occurs before the reception time for the PDCCH, the UE may not know that the uplink transmission will be scheduled when it begins carrier-switching SRS. This situation can lead to conflicts between SRS and uplink transmissions. To prevent these situations, the UE can determine whether to discard the SRS or the uplink transmission based on the timing between the reception time for the PDCCH and the SRS decision time. For example, if the UE receives the PDCCH no later than N2+switchingTime symbols before the first symbol of the carrier-switching SRS, the UE can determine the uplink transmission scheduled by the PDCCH and apply one of the conflict resolution rules described above accordingly. By taking timing into account in the application of conflict resolution rules, the aforementioned situations that may lead to conflicts can be eliminated.

[0171] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is illustrative of the example method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart may be rearranged based on design preferences. Furthermore, some blocks may be combined or omitted. The appended method claims give the elements of each block in the illustrative order, and do not imply limitation to the given specific order or hierarchy.

[0172] The foregoing description is provided to enable any person skilled in the art to implement the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be given the full scope consistent with the language of the claims, wherein, unless expressly stated otherwise, references to singular elements are not intended to mean “one and only one,” but rather “one or more.” Terms such as “if,” “when,” and “at the same time as,” should be interpreted as “under the condition of,” rather than implying an immediate temporal relationship or reaction. That is, these phrases (e.g., “when”) do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but only that an action will occur if the condition is met, without requiring a specific or immediate temporal constraint on the occurrence of the action. The term “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred over or superior to other aspects. Unless expressly stated otherwise, the term “some” refers to one or more. For example, 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 multiples of A, multiples of B, or multiples of 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 only A, only B, only C, 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 described throughout the various aspects of this disclosure that are known to or will be known later by one of ordinary skill in the art are expressly incorporated herein by reference and are intended to be included by the claims. Furthermore, the disclosure herein is not intended to be offered to the public, whether or not such disclosure is expressly recited in the claims. The terms “module,” “mechanism,” “element,” “device,” etc., are not necessarily substitutes for the term “unit.” Therefore, no claim can be made that an element should be interpreted as a functional unit unless the element is explicitly described using the phrase “unit for…”.

[0173] The following examples are merely illustrative and may be combined with, but not limited to, other embodiments or aspects of the teachings described herein.

[0174] Example 1 is a method for wireless communication at a user equipment (UE), comprising: receiving a physical downlink control channel (PDCCH) from a base station, the PDCCH being scheduled for uplink transmission on a first carrier; and determining, based on timing between the reception time of the PDCCH and the scheduling time for transmitting a sounding reference signal (SRS) on a second carrier different from the first carrier, whether to discard either the uplink transmission or the SRS transmission.

[0175] Example 2 is the method described in Example 1, wherein the timing is based on the subcarrier interval for the first carrier or the second carrier.

[0176] Example 3 is the method according to Example 2, wherein the subcarrier spacing includes a smaller subcarrier spacing between the first carrier and the second carrier.

[0177] Example 4 is the method according to any of Examples 1-3, further comprising: receiving a second PDCCH from a base station, the second PDCCH being scheduled for an SRS on a second carrier; and wherein determining whether to discard either an uplink transmission or an SRS transmission is based on timing between the reception time of the second PDCCH and the scheduling time for the uplink transmission.

[0178] Example 5 is the method according to Example 4, further comprising: determining that the uplink transmission includes one of the following: periodic channel state information (P-CSI) on one of the physical uplink control channel (PUCCH) or the physical uplink shared channel (PUSCH), including either channel quality indicator only (CQI) or precoding matrix indicator only (PMI); or non-carrier-switched SRS; wherein the uplink transmission is dropped in response to overlap between the uplink transmission and a scheduling time for transmitting the SRS or a carrier-switching time associated with the SRS, wherein the SRS is aperiodic SRS (A-SRS).

[0179] Example 6 is the method according to Example 4, further comprising: determining that the uplink transmission includes one of the following: periodic channel state information (P-CSI) on one of the physical uplink control channel (PUCCH) or the physical uplink shared channel (PUSCH), including either channel quality indicator only (CQI) or precoding matrix indicator only (PMI); or non-carrier-switching SRS; wherein determining whether to discard the uplink transmission or the transmission of the SRS is based on timing between the action time associated with the SRS and the scheduling time for the uplink transmission, wherein the SRS is a semi-persistent SPS (SP-SRS); wherein the uplink transmission is discarded in response to an overlap between the uplink transmission and the scheduling time for transmitting the SRS or the carrier-switching time associated with the SRS.

[0180] Example 7 is the method according to Example 6, wherein the action time is based at least on the time for transmitting the Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) (HARQ-ACK) associated with the channel carrying the activation command for SP-SRS.

[0181] Example 8 is the method according to Example 4, further comprising: determining uplink transmissions including aperiodic channel state information (A-CSI) on the physical uplink shared channel (PUSCH) including either channel quality indicator only (CQI) or precoding matrix indicator only (PMI); wherein the uplink transmission is dropped in response to overlap between the uplink transmission and a scheduling time for transmitting the SRS or a carrier handover time associated with the SRS, wherein the SRS is an aperiodic SRS (A-SRS).

[0182] Example 9 is the method according to Example 4, further comprising: determining that the uplink transmission includes a physical uplink shared channel (PUSCH) without uplink control information (UCI); wherein the uplink transmission is dropped in response to overlap with either a scheduling time for transmitting SRS or a carrier switching time associated with SRS.

[0183] Example 10 is the method according to any of the examples in Examples 1-9, wherein the timing includes a switching time for switching from a first carrier to a second carrier to transmit SRS.

[0184] Example 11 is a method according to any of Examples 1-3 or 10, further comprising: determining that the uplink transmission is a hybrid automatic repeat request (HARQ)-acknowledgment (ACK) (HARQ-ACK) on the physical uplink control channel (PUCCH), wherein the HARQ-ACK is any of the following: corresponding to dynamic permission; including a semi-persistent scheduling (SPS) HARQ-ACK (SPSHARQ-ACK), wherein the PDCCH activates the SPS HARQ-ACK; or in response to the PDCCH, wherein the PDCCH releases the SPSHARQ-ACK; and wherein the SRS is dropped in response to the HARQ-ACK overlapping with either the scheduling time for transmitting the SRS or the carrier handover time associated with the SRS.

[0185] Example 12 is a method according to any of Examples 1-3 or 10, further comprising: receiving a second PDCCH from a base station, the second PDCCH scheduling a Physical Uplink Shared Channel (PUSCH); and determining that the uplink transmission is a Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) on a Physical Uplink Control Channel (PUCCH), wherein the HARQ-ACK is multiplexed with the PUSCH; wherein determining whether to discard either the uplink transmission or the transmission of the SRS is based on the reception time of the second PDCCH; wherein the SRS is discarded in response to an overlap between the PUSCH and a scheduling time for transmitting the SRS or a carrier handover time associated with the SRS.

[0186] Example 13 is a method according to any of Examples 1-3 or 10, further comprising: determining that the uplink transmission is either a scheduling request (SR) or a physical uplink shared channel (PUSCH) multiplexed with periodic channel state information (P-CSI) on a physical uplink control channel (PUCCH), the P-CSI including either a rank indicator (RI) or a channel state information reference signal resource indicator (CRI); and wherein the SRS is dropped in response to the uplink transmission overlapping with either a scheduling time for transmitting the SRS or a carrier handover time associated with the SRS.

[0187] Example 14 is a method according to any of Examples 1-3 or 10, further comprising: determining that the uplink transmission includes semi-persistently scheduled channel state information (SP-CSI), the SP-CSI including either a rank indicator (RI) or a channel state information reference signal resource indicator (CRI); wherein determining whether to discard either the uplink transmission or the SRS transmission is based on timing between the action time associated with the SP-CSI and the scheduling time for transmitting the SRS; wherein the SRS is discarded in response to an overlap between the SP-CSI and the scheduling time for transmitting the SRS or the carrier handover time associated with the SRS.

[0188] Example 15 is the method according to Example 14, wherein the action time is based at least on the time for transmitting the Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) (HARQ-ACK) associated with the channel carrying the activation command for SP-CSI.

[0189] Example 16 is a method according to any of Examples 1-3 or 10, further comprising: determining that uplink transmission is on a physical uplink shared channel (PUSCH) including either a rank indicator (RI) associated with aperiodic channel state information (A-CSI) or a channel state information reference signal resource indicator (CRI); wherein the SRS is dropped in response to the PUSCH overlapping with either a scheduling time for transmitting the SRS or a carrier switching time associated with the SRS.

[0190] Example 17 is the method according to any of Examples 1-3 or 10, further comprising: determining that the uplink transmission is on the Physical Random Access Channel (PRACH); wherein the SRS is dropped in response to an overlap between the PRACH and either a scheduling time for transmitting the SRS or a carrier handover time associated with the SRS.

[0191] Example 18 is a method according to any of Examples 1-3 or 10, further comprising: determining uplink transmissions including aperiodic channel state information (A-CSI) on a physical uplink shared channel (PUSCH); wherein the SRS is discarded in response to an overlap between the PUSCH and a scheduling time for transmitting the SRS or a carrier switching time associated with the SRS and the SRS being either a periodic SRS (P-SRS) or a semi-persistently scheduled SRS (SPS SRS).

[0192] Example 19 is an apparatus for wireless communication, comprising: a unit for receiving a physical downlink control channel (PDCCH) from a base station, the PDCCH being scheduled for uplink transmission on a first carrier; and a unit for determining whether to discard either the uplink transmission or the SRS transmission based on a timing between the reception time of the PDCCH and a scheduling time for transmitting a sounding reference signal (SRS) on a second carrier different from the first carrier.

[0193] Example 20 is an apparatus according to Example 19, wherein the timing is based on a subcarrier spacing for a first carrier or a second carrier.

[0194] Example 21 is an apparatus according to Example 20, wherein the subcarrier spacing includes a smaller subcarrier spacing between the first carrier and the second carrier.

[0195] Example 22 is an apparatus according to any of the examples 19-21, wherein the receiving unit is configured to receive a second PDCCH from a base station, the second PDCCH being scheduled for SRS on a second carrier; and wherein the determining unit is configured to determine, based on a timing between the reception time of the second PDCCH and the scheduling time for uplink transmission, whether to discard either the uplink transmission or the SRS transmission.

[0196] Example 23 is an apparatus according to any of the examples 19-22, wherein the timing includes a switching time for switching from a first carrier to a second carrier to transmit SRS.

[0197] Example 24 is an apparatus for wireless communication, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and operable thereon, which, when executed by the processor, cause the apparatus to: receive a physical downlink control channel (PDCCH) from a base station, the PDCCH being scheduled for uplink transmission on a first carrier; and determine, based on timing between the reception time of the PDCCH and the scheduling time for transmitting a sounding reference signal (SRS) on a second carrier different from the first carrier, whether to discard either the uplink transmission or the SRS transmission.

[0198] Example 25 is an apparatus according to Example 24, wherein the timing is based on a subcarrier spacing for a first carrier or a second carrier.

[0199] Example 26 is an apparatus according to Example 25, wherein the subcarrier spacing includes a smaller subcarrier spacing between the first carrier and the second carrier.

[0200] Example 27 is an apparatus according to any of Examples 24-26, wherein the instructions, when executed by the processor, further cause the apparatus to perform the following operations: receive a second PDCCH from a base station, the second PDCCH being scheduled for SRS on a second carrier; and wherein the instructions, when executed by the processor, further cause the apparatus to perform the following operations: determine, based on a timing between the reception time of the second PDCCH and the scheduling time for uplink transmission, whether to discard either the uplink transmission or the SRS transmission.

[0201] Example 28 is an apparatus according to any of the examples 24-27, wherein the timing includes a switching time for switching from a first carrier to a second carrier to transmit SRS.

[0202] Example 29 is an apparatus according to any of Examples 24-26 or 28, wherein the instructions, when executed by the processor, also cause the apparatus to: determine that the uplink transmission is a Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) on the Physical Uplink Control Channel (PUCCH), wherein the HARQ-ACK is any of the following: corresponding to dynamic permission; including a semi-persistent scheduling (SPS) HARQ-ACK (SPS HARQ-ACK), wherein the PDCCH activates the SPS HARQ-ACK; or in response to the PDCCH, wherein the PDCCH releases the SPS HARQ-ACK; and wherein the SRS is dropped in response to the HARQ-ACK overlapping with either the scheduling time for transmitting the SRS or the carrier handover time associated with the SRS.

[0203] Example 30 is a computer-readable medium storing computer-executable code that, when executed by a processor, causes the processor to: receive a physical downlink control channel (PDCCH) from a base station, the PDCCH being scheduled for uplink transmission on a first carrier; and determine, based on timing between the time of receiving the PDCCH and the time of scheduling for transmitting a sounding reference signal (SRS) on a second carrier different from the first carrier, whether to discard either the uplink transmission or the SRS transmission.

Claims

1. A method for wireless communication at a user equipment (UE), comprising: The UE receives a Physical Downlink Control Channel (PDCCH) from the base station at a reception time. The PDCCH is scheduled for uplink transmission on a first carrier. The reception time is prior to a decision time for transmitting a Sounding Reference Signal (SRS). The decision time for transmitting the SRS is the time when the UE decides whether to start transmitting the SRS. The decision time is the amount of time prior to the scheduling time for transmitting the SRS on a second carrier different from the first carrier. It is determined that the PDCCH is scheduling an uplink transmission that will overlap with the SRS scheduled transmission on a second carrier different from the first carrier; and Based on the determination that the PDCCH is scheduling an uplink transmission, which will overlap with the scheduled transmission of the SRS on a second carrier different from the first carrier, the PDCCH and conflict resolution rules are received from the base station at the reception time to determine whether to discard the uplink transmission or the transmission of the SRS on the second carrier different from the first carrier.

2. The method according to claim 1, wherein, The timing between the reception time and the scheduling time for transmitting the SRS is based on the subcarrier interval for the first carrier or the second carrier.

3. The method according to claim 2, wherein, The subcarrier spacing includes a smaller subcarrier spacing between the first carrier and the second carrier.

4. The method according to claim 1, further comprising: The base station receives a second PDCCH, the second PDCCH is scheduled on the second carrier, and the SRS is a carrier-switching SRS. and The determination of whether to discard the uplink transmission or the transmission of the carrier-switched SRS is based on the timing between the reception time of the second PDCCH and the scheduling time for the uplink transmission.

5. The method according to claim 4, further comprising: The uplink transmission is determined to include one of the following: Periodic channel state information (P-CSI) on either the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH), including either the Channel Quality Indicator (CQI) or the Precoding Matrix Indicator (PMI). or Non-carrier-switched SRS; The uplink transmission is dropped in response to overlap between the uplink transmission and the scheduling time for transmitting the carrier-switched SRS or the carrier switching time associated with the carrier-switched SRS, wherein the carrier-switched SRS is an aperiodic SRS (A-SRS).

6. The method according to claim 4, further comprising: The uplink transmission is determined to include one of the following: Periodic channel state information (P-CSI) on either the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH), including either the Channel Quality Indicator (CQI) or the Precoding Matrix Indicator (PMI). or Non-carrier-switched SRS; The determination of whether to discard the uplink transmission or the transmission of the carrier-switched SRS is based on timing between the action time associated with the carrier-switched SRS and the scheduling time for the uplink transmission, wherein the carrier-switched SRS is a semi-persistent SPS (SP-SRS). The uplink transmission is dropped in response to overlap with either the scheduling time for transmitting the carrier-switched SRS or the carrier switching time associated with the carrier-switched SRS.

7. The method according to claim 6, wherein, The action time is based at least on the time required for the transmission of the Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) (HARQ-ACK) associated with the channel carrying the activation command for the SP-SRS.

8. The method according to claim 4, further comprising: The uplink transmission includes aperiodic channel state information (A-CSI) on the physical uplink shared channel (PUSCH), comprising either a channel quality indicator only (CQI) or a precoding matrix indicator only (PMI). The uplink transmission is dropped in response to overlap with either the scheduling time for transmitting the carrier-switched SRS or the carrier switching time associated with the carrier-switched SRS, wherein the carrier-switched SRS is an aperiodic SRS (A-SRS).

9. The method according to claim 4, further comprising: The uplink transmission is determined to include a Physical Uplink Shared Channel (PUSCH) that does not carry uplink control information (UCI). The uplink transmission is dropped in response to overlap with either the scheduling time for transmitting the carrier-switched SRS or the carrier switching time associated with the carrier-switched SRS.

10. The method according to claim 1, wherein, The timing between the reception time and the scheduling time for transmitting the SRS includes a switching time for switching from the first carrier to the second carrier to transmit the SRS.

11. The method according to claim 1, further comprising: The uplink transmission is determined to be a Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) on the Physical Uplink Control Channel (PUCCH), wherein the HARQ-ACK is any of the following: Corresponding to dynamic permission, Including semi-persistent scheduling (SPS) HARQ-ACK (SPS HARQ-ACK), wherein the PDCCH activates the SPSHARQ-ACK, or It is in response to the PDCCH, wherein the PDCCH releases the SPS HARQ-ACK; and The SRS is dropped in response to the HARQ-ACK overlapping with either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

12. The method according to claim 1, further comprising: The second PDCCH is received from the base station, and the second PDCCH schedules the Physical Uplink Shared Channel (PUSCH). as well as It is determined that the uplink transmission is a hybrid automatic repeat request (HARQ)-acknowledgment (ACK) on the physical uplink control channel (PUCCH), wherein the HARQ-ACK is multiplexed with the PUSCH; The determination of whether to discard either the uplink transmission or the SRS transmission is based on the reception time of the second PDCCH. The SRS is dropped in response to the PUSCH overlapping with either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

13. The method according to claim 1, further comprising: Determine whether the uplink transmission is a scheduling request (SR) or a physical uplink shared channel (PUSCH) multiplexed with periodic channel state information (P-CSI) on the physical uplink control channel (PUCCH), wherein the P-CSI includes either a rank indicator (RI) or a channel state information reference signal resource indicator (CRI); and The SRS is dropped in response to an overlap between the uplink transmission and the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

14. The method according to claim 1, further comprising: The uplink transmission is determined to include semi-persistent scheduling channel state information (SP-CSI), wherein the SP-CSI includes either a rank indicator (RI) or a channel state information reference signal resource indicator (CRI). The determination of whether to discard either the uplink transmission or the SRS transmission is based on timing between the action time associated with the SP-CSI and the scheduling time for sending the SRS. The SRS is dropped in response to the SP-CSI overlapping with either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

15. The method according to claim 14, wherein, The action time is based at least on the time for transmitting the Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) (HARQ-ACK) associated with the channel carrying the activation command for the SP-CSI.

16. The method according to claim 1, further comprising: The uplink transmission is determined to be on a physical uplink shared channel (PUSCH) that includes either a rank indicator (RI) associated with aperiodic channel state information (A-CSI) or a channel state information reference signal resource indicator (CRI). The SRS is dropped in response to the PUSCH overlapping with either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

17. The method according to claim 1, further comprising: It is determined that the uplink transmission is on the Physical Random Access Channel (PRACH); The SRS is dropped in response to the PRACH overlapping with either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

18. The method according to claim 1, further comprising: The uplink transmission is determined to include aperiodic channel state information (A-CSI) on the Physical Uplink Shared Channel (PUSCH). The SRS is discarded in response to the PUSCH overlapping with either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS, and the SRS being either a periodic SRS (P-SRS) or a semi-persistently scheduled SRS (SPS SRS).

19. An apparatus for wireless communication, comprising: A unit for receiving a physical downlink control channel (PDCCH) from a base station at a reception time, the PDCCH being scheduled for uplink transmission on a first carrier, wherein the reception time is prior to a decision time for transmitting a sounding reference signal (SRS), wherein the decision time for transmitting the SRS is the time at which the device decides whether to begin transmitting the SRS, the decision time being the amount of time prior to a scheduling time for transmitting the SRS on a second carrier different from the first carrier; A unit for determining that the PDCCH is scheduling an uplink transmission that will overlap with the SRS scheduling transmission on a second carrier different from the first carrier; and A unit for determining, based on the determination that the PDCCH is scheduling an uplink transmission that will overlap with the scheduled transmission of the SRS on a second carrier different from the first carrier, to discard either the uplink transmission or the transmission of the SRS on the second carrier different from the first carrier, upon receiving the PDCCH and conflict resolution rules from the base station at the reception time.

20. The apparatus according to claim 19, wherein, The timing between the reception time and the scheduling time for transmitting the SRS is based on the subcarrier interval for the first carrier or the second carrier.

21. The apparatus according to claim 20, wherein, The subcarrier spacing includes a smaller subcarrier spacing between the first carrier and the second carrier.

22. The apparatus of claim 19, further comprising: A unit for receiving a second PDCCH from the base station, wherein the second PDCCH is scheduled on the SRS on the second carrier, and the SRS is a carrier-switching SRS; and The determination of whether to discard the uplink transmission or the transmission of the carrier-switched SRS is based on the timing between the reception time of the second PDCCH and the scheduling time for the uplink transmission.

23. The apparatus of claim 22, further comprising: A unit for determining that the uplink transmission includes one of the following: Periodic channel state information (P-CSI) on either the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH), including either the Channel Quality Indicator (CQI) or the Precoding Matrix Indicator (PMI). or Non-carrier-switched SRS; The uplink transmission is dropped in response to overlap between the uplink transmission and the scheduling time for transmitting the carrier-switched SRS or the carrier switching time associated with the carrier-switched SRS, wherein the carrier-switched SRS is an aperiodic SRS (A-SRS).

24. The apparatus of claim 22, further comprising: A unit for determining that the uplink transmission includes one of the following: Periodic channel state information (P-CSI) on either the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH), including either the Channel Quality Indicator (CQI) or the Precoding Matrix Indicator (PMI). or Non-carrier-switched SRS; The determination of whether to discard the uplink transmission or the transmission of the carrier-switched SRS is based on timing between the action time associated with the carrier-switched SRS and the scheduling time for the uplink transmission, wherein the carrier-switched SRS is a semi-persistent SPS (SP-SRS). The uplink transmission is dropped in response to overlap with either the scheduling time for transmitting the carrier-switched SRS or the carrier switching time associated with the carrier-switched SRS.

25. The apparatus according to claim 24, wherein, The action time is based at least on the time required for the transmission of the Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) (HARQ-ACK) associated with the channel carrying the activation command for the SP-SRS.

26. The apparatus of claim 22, further comprising: A unit for determining the uplink transmission including aperiodic channel state information (A-CSI) on the physical uplink shared channel (PUSCH) including either channel quality indicator only (CQI) or precoding matrix indicator only (PMI); The uplink transmission is dropped in response to overlap with either the scheduling time for transmitting the carrier-switched SRS or the carrier switching time associated with the carrier-switched SRS, wherein the carrier-switched SRS is an aperiodic SRS (A-SRS).

27. The apparatus of claim 22, further comprising: A unit for determining that the uplink transmission includes a Physical Uplink Shared Channel (PUSCH) without carrying uplink control information (UCI); The uplink transmission is dropped in response to overlap with either the scheduling time for transmitting the carrier-switched SRS or the carrier switching time associated with the carrier-switched SRS.

28. The apparatus according to claim 19, wherein, The timing between the reception time and the scheduling time for transmitting the SRS includes a switching time for switching from the first carrier to the second carrier to transmit the SRS.

29. The apparatus of claim 19, further comprising: The unit used to determine that the uplink transmission is a Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) on the Physical Uplink Control Channel (PUCCH), wherein the HARQ-ACK is any of the following: Corresponding to dynamic permission, Including semi-persistent scheduling (SPS) HARQ-ACK (SPS HARQ-ACK), wherein the PDCCH activates the SPSHARQ-ACK, or It is in response to the PDCCH, wherein the PDCCH releases the SPS HARQ-ACK; and The SRS is dropped in response to the HARQ-ACK overlapping with either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

30. The apparatus of claim 19, further comprising: A unit for receiving a second PDCCH from the base station, wherein the second PDCCH schedules the Physical Uplink Shared Channel (PUSCH); as well as The unit used to determine that the uplink transmission is a hybrid automatic repeat request (HARQ)-acknowledgment (ACK) on the physical uplink control channel (PUCCH), wherein the HARQ-ACK is multiplexed with the PUSCH; The determination of whether to discard either the uplink transmission or the SRS transmission is based on the reception time of the second PDCCH. The SRS is dropped in response to the PUSCH overlapping with either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

31. The apparatus of claim 19, further comprising: A unit for determining whether the uplink transmission is a scheduling request (SR) or a physical uplink shared channel (PUSCH) multiplexed with periodic channel state information (P-CSI) on the physical uplink control channel (PUCCH), wherein the P-CSI includes either a rank indicator (RI) or a channel state information reference signal resource indicator (CRI); and The SRS is dropped in response to an overlap between the uplink transmission and the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

32. The apparatus of claim 19, further comprising: A unit for determining the uplink transmission including semi-persistent scheduling channel state information (SP-CSI), wherein the SP-CSI includes either a rank indicator (RI) or a channel state information reference signal resource indicator (CRI). The determination of whether to discard either the uplink transmission or the SRS transmission is based on timing between the action time associated with the SP-CSI and the scheduling time for sending the SRS. The SRS is dropped in response to the SP-CSI overlapping with either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

33. The apparatus according to claim 32, wherein, The action time is based at least on the time for transmitting the Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) (HARQ-ACK) associated with the channel carrying the activation command for the SP-CSI.

34. The apparatus of claim 19, further comprising: The unit used to determine the uplink transmission on the physical uplink shared channel (PUSCH) including one of the rank indicator (RI) or channel state information reference signal resource indicator (CRI) associated with aperiodic channel state information (A-CSI). The SRS is dropped in response to the PUSCH overlapping with either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

35. The apparatus of claim 19, further comprising: Used to determine the unit of the uplink transmission on the Physical Random Access Channel (PRACH); The SRS is dropped in response to the PRACH overlapping with either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

36. The apparatus of claim 19, further comprising: A unit for determining the uplink transmission including aperiodic channel state information (A-CSI) on the physical uplink shared channel (PUSCH); The SRS is discarded in response to the PUSCH overlapping with either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS, and the SRS being either a periodic SRS (P-SRS) or a semi-persistently scheduled SRS (SPS SRS).

37. An apparatus for wireless communication at a user equipment (UE), comprising: processor; Memory coupled to the processor; as well as Instructions stored in the memory and operable therein, which, when executed by the processor, cause the device to perform the following operations: The UE receives a Physical Downlink Control Channel (PDCCH) from the base station at a reception time. The PDCCH is scheduled for uplink transmission on a first carrier. The reception time is prior to a decision time for transmitting a Sounding Reference Signal (SRS). The decision time for transmitting the SRS is the time when the UE decides whether to start transmitting the SRS. The decision time is the amount of time prior to the scheduling time for transmitting the SRS on a second carrier different from the first carrier. It is determined that the PDCCH is scheduling an uplink transmission that will overlap with the SRS scheduled transmission on a second carrier different from the first carrier; and Based on the determination that the PDCCH is scheduling an uplink transmission, which will overlap with the scheduled transmission of the SRS on a second carrier different from the first carrier, the PDCCH and conflict resolution rules are received from the base station at the reception time to determine whether to discard the uplink transmission or the transmission of the SRS on the second carrier different from the first carrier.

38. The apparatus according to claim 37, wherein, The timing between the reception time and the scheduling time for transmitting the SRS is based on the subcarrier interval for the first carrier or the second carrier.

39. The apparatus according to claim 38, wherein, The subcarrier spacing includes a smaller subcarrier spacing between the first carrier and the second carrier.

40. The apparatus according to claim 37, wherein, When executed by the processor, the instructions further cause the device to perform the following operations: The base station receives a second PDCCH, the second PDCCH is scheduled on the second carrier, and the SRS is a carrier-switching SRS. and The determination of whether to discard the uplink transmission or the transmission of the carrier-switched SRS is based on the timing between the reception time of the second PDCCH and the scheduling time for the uplink transmission.

41. The apparatus according to claim 40, wherein, When executed by the processor, the instructions further cause the device to perform the following operations: The uplink transmission is determined to include one of the following: Periodic channel state information (P-CSI) on either the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH), including either the Channel Quality Indicator (CQI) or the Precoding Matrix Indicator (PMI). or Non-carrier-switched SRS; The uplink transmission is dropped in response to overlap between the uplink transmission and the scheduling time for transmitting the carrier-switched SRS or the carrier switching time associated with the carrier-switched SRS, wherein the carrier-switched SRS is an aperiodic SRS (A-SRS).

42. The apparatus according to claim 40, wherein, When executed by the processor, the instructions further cause the device to perform the following operations: The uplink transmission is determined to include one of the following: Periodic channel state information (P-CSI) on either the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH), including either a Channel Quality Indicator (CQI) or a Precoding Matrix Indicator (PMI); or Non-carrier-switched SRS; The determination of whether to discard the uplink transmission or the transmission of the carrier-switched SRS is further based on timing between the action time associated with the carrier-switched SRS and the scheduling time for the uplink transmission, wherein the carrier-switched SRS is a semi-persistent SPS (SP-SRS). The uplink transmission is dropped in response to overlap with either the scheduling time for transmitting the carrier-switched SRS or the carrier switching time associated with the carrier-switched SRS.

43. The apparatus according to claim 42, wherein, The action time is based at least on the time required for the transmission of the Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) (HARQ-ACK) associated with the channel carrying the activation command for the SP-SRS.

44. The apparatus according to claim 40, wherein, When executed by the processor, the instructions further cause the device to perform the following operations: The uplink transmission includes aperiodic channel state information (A-CSI) on the physical uplink shared channel (PUSCH), comprising either a channel quality indicator only (CQI) or a precoding matrix indicator only (PMI). The uplink transmission is dropped in response to overlap with either the scheduling time for transmitting the carrier-switched SRS or the carrier switching time associated with the carrier-switched SRS, wherein the carrier-switched SRS is an aperiodic SRS (A-SRS).

45. The apparatus according to claim 40, wherein, When executed by the processor, the instructions further cause the device to perform the following operations: The uplink transmission is determined to include a Physical Uplink Shared Channel (PUSCH) that does not carry uplink control information (UCI). The uplink transmission is dropped in response to overlap with either the scheduling time for transmitting the carrier-switched SRS or the carrier switching time associated with the carrier-switched SRS.

46. ​​The apparatus according to claim 37, wherein, The timing between the reception time and the scheduling time for transmitting the SRS includes a switching time for switching from the first carrier to the second carrier to transmit the SRS.

47. The apparatus according to claim 37, wherein, When executed by the processor, the instructions further cause the device to perform the following operations: The uplink transmission is determined to be a Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) on the Physical Uplink Control Channel (PUCCH), wherein the HARQ-ACK is any of the following: Corresponding to dynamic permission, Including semi-persistent scheduling (SPS) HARQ-ACK (SPS HARQ-ACK), wherein the PDCCH activates the SPSHARQ-ACK, or It is in response to the PDCCH, wherein the PDCCH releases the SPS HARQ-ACK; and The SRS is dropped in response to the HARQ-ACK overlapping with either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

48. The apparatus according to claim 37, wherein, When executed by the processor, the instructions further cause the device to perform the following operations: Receives a second PDCCH from the base station, the second PDCCH scheduling the Physical Uplink Shared Channel (PUSCH); and It is determined that the uplink transmission is a hybrid automatic repeat request (HARQ)-acknowledgment (ACK) on the physical uplink control channel (PUCCH), wherein the HARQ-ACK is multiplexed with the PUSCH; The determination of whether to discard either the uplink transmission or the SRS transmission is based on the reception time of the second PDCCH. The SRS is dropped in response to the PUSCH overlapping with either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

49. The apparatus according to claim 37, wherein, When executed by the processor, the instructions further cause the device to perform the following operations: Determine whether the uplink transmission is a scheduling request (SR) or a physical uplink shared channel (PUSCH) multiplexed with periodic channel state information (P-CSI) on the physical uplink control channel (PUCCH), wherein the P-CSI includes either a rank indicator (RI) or a channel state information reference signal resource indicator (CRI); and The SRS is dropped in response to an overlap between the uplink transmission and the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

50. The apparatus according to claim 37, wherein, When executed by the processor, the instructions further cause the device to perform the following operations: The uplink transmission is determined to include semi-persistent scheduling channel state information (SP-CSI), wherein the SP-CSI includes either a rank indicator (RI) or a channel state information reference signal resource indicator (CRI). The determination of whether to discard either the uplink transmission or the SRS transmission is based on timing between the action time associated with the SP-CSI and the scheduling time for sending the SRS. The SRS is dropped in response to the SP-CSI overlapping with either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

51. The apparatus according to claim 50, wherein, The action time is based at least on the time for transmitting the Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) (HARQ-ACK) associated with the channel carrying the activation command for the SP-CSI.

52. The apparatus according to claim 37, wherein, When executed by the processor, the instructions further cause the device to perform the following operations: The uplink transmission is determined to be on a physical uplink shared channel (PUSCH) that includes either a rank indicator (RI) associated with aperiodic channel state information (A-CSI) or a channel state information reference signal resource indicator (CRI). The SRS is dropped in response to the PUSCH overlapping with either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

53. The apparatus according to claim 37, wherein, When executed by the processor, the instructions further cause the device to perform the following operations: It is determined that the uplink transmission is on the Physical Random Access Channel (PRACH); The SRS is dropped in response to the PRACH overlapping with either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

54. The apparatus according to claim 37, wherein, When executed by the processor, the instructions further cause the device to perform the following operations: The uplink transmission is determined to include aperiodic channel state information (A-CSI) on the Physical Uplink Shared Channel (PUSCH). The SRS is discarded in response to the PUSCH overlapping with either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS, and the SRS being either a periodic SRS (P-SRS) or a semi-persistently scheduled SRS (SPS SRS).

55. A computer-readable medium storing computer-executable code, which, when executed by a processor at a user equipment (UE), causes the processor to perform the following operations: At the reception time, the Physical Downlink Control Channel (PDCCH) is received from the base station. This PDCCH is scheduled for uplink transmission on the first carrier. The reception time is prior to the decision time for transmitting a probe reference signal (SRS), wherein the decision time for transmitting the SRS is the time when the UE decides whether to start transmitting the SRS, and the decision time is the amount of time prior to the scheduling time for transmitting the SRS on a second carrier different from the first carrier; It is determined that the PDCCH is scheduling an uplink transmission that will overlap with the SRS scheduled transmission on a second carrier different from the first carrier; and Based on the determination that the PDCCH is scheduling an uplink transmission, which will overlap with the scheduled transmission of the SRS on a second carrier different from the first carrier, the PDCCH and conflict resolution rules are received from the base station at the reception time to determine whether to discard the uplink transmission or the transmission of the SRS on the second carrier different from the first carrier.

56. The computer-readable medium according to claim 55, wherein, The timing between the reception time and the scheduling time for transmitting the SRS is based on the subcarrier interval for the first carrier or the second carrier.

57. The computer-readable medium according to claim 56, wherein, The subcarrier spacing includes a smaller subcarrier spacing between the first carrier and the second carrier.

58. The computer-readable medium according to claim 55, wherein, When the code is executed by the processor, it further causes the processor to perform the following operations: The base station receives a second PDCCH, the second PDCCH is scheduled on the second carrier, and the SRS is a carrier-switching SRS. and The determination of whether to discard the uplink transmission or the transmission of the carrier-switched SRS is based on the timing between the reception time of the second PDCCH and the scheduling time for the uplink transmission.

59. The computer-readable medium according to claim 58, wherein, When the code is executed by the processor, it further causes the processor to perform the following operations: The uplink transmission is determined to include one of the following: Periodic channel state information (P-CSI) on either the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH), including either the Channel Quality Indicator (CQI) or the Precoding Matrix Indicator (PMI). or Non-carrier-switched SRS; The uplink transmission is dropped in response to overlap between the uplink transmission and the scheduling time for transmitting the carrier-switched SRS or the carrier switching time associated with the carrier-switched SRS, wherein the carrier-switched SRS is an aperiodic SRS (A-SRS).

60. The computer-readable medium according to claim 58, wherein, When the code is executed by the processor, it further causes the processor to perform the following operations: The uplink transmission is determined to include one of the following: Periodic channel state information (P-CSI) on either the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH), including either the Channel Quality Indicator (CQI) or the Precoding Matrix Indicator (PMI). or Non-carrier-switched SRS; The determination of whether to discard the uplink transmission or the transmission of the carrier-switched SRS is based on timing between the action time associated with the carrier-switched SRS and the scheduling time for the uplink transmission, wherein the carrier-switched SRS is a semi-persistent SPS (SP-SRS). The uplink transmission is dropped in response to overlap with either the scheduling time for transmitting the carrier-switched SRS or the carrier switching time associated with the carrier-switched SRS.

61. The computer-readable medium of claim 60, wherein, The action time is based at least on the time required for the transmission of the Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) (HARQ-ACK) associated with the channel carrying the activation command for the SP-SRS.

62. The computer-readable medium according to claim 58, wherein, When the code is executed by the processor, it further causes the processor to perform the following operations: The uplink transmission includes aperiodic channel state information (A-CSI) on the physical uplink shared channel (PUSCH), comprising either a channel quality indicator only (CQI) or a precoding matrix indicator only (PMI). The uplink transmission is dropped in response to overlap with either the scheduling time for transmitting the carrier-switched SRS or the carrier switching time associated with the carrier-switched SRS, wherein the carrier-switched SRS is an aperiodic SRS (A-SRS).

63. The computer-readable medium according to claim 58, wherein, When the code is executed by the processor, it further causes the processor to perform the following operations: The uplink transmission is determined to include a Physical Uplink Shared Channel (PUSCH) that does not carry uplink control information (UCI). The uplink transmission is dropped in response to overlap with either the scheduling time for transmitting the carrier-switched SRS or the carrier switching time associated with the carrier-switched SRS.

64. The computer-readable medium according to claim 55, wherein, The timing between the reception time and the scheduling time for transmitting the SRS includes a switching time for switching from the first carrier to the second carrier to transmit the SRS.

65. The computer-readable medium according to claim 55, wherein, When the code is executed by the processor, it further causes the processor to perform the following operations: The uplink transmission is determined to be a Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) on the Physical Uplink Control Channel (PUCCH), wherein the HARQ-ACK is any of the following: Corresponding to dynamic permission, Including semi-persistent scheduling (SPS) HARQ-ACK (SPS HARQ-ACK), wherein the PDCCH activates the SPSHARQ-ACK, or It is in response to the PDCCH, wherein the PDCCH releases the SPS HARQ-ACK; and The SRS is dropped in response to the HARQ-ACK overlapping with either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

66. The computer-readable medium according to claim 55, wherein, When the code is executed by the processor, it further causes the processor to perform the following operations: Receives a second PDCCH from the base station, the second PDCCH scheduling the Physical Uplink Shared Channel (PUSCH); and It is determined that the uplink transmission is a hybrid automatic repeat request (HARQ)-acknowledgment (ACK) on the physical uplink control channel (PUCCH), wherein the HARQ-ACK is multiplexed with the PUSCH; The determination of whether to discard either the uplink transmission or the SRS transmission is based on the reception time of the second PDCCH. The SRS is dropped in response to the PUSCH overlapping with either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

67. The computer-readable medium of claim 55, wherein, When the code is executed by the processor, it further causes the processor to perform the following operations: Determine whether the uplink transmission is a scheduling request (SR) or a physical uplink shared channel (PUSCH) multiplexed with periodic channel state information (P-CSI) on the physical uplink control channel (PUCCH), wherein the P-CSI includes either a rank indicator (RI) or a channel state information reference signal resource indicator (CRI); and The SRS is dropped in response to an overlap between the uplink transmission and the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

68. The computer-readable medium according to claim 55, wherein, When the code is executed by the processor, it further causes the processor to perform the following operations: The uplink transmission is determined to include semi-persistent scheduling channel state information (SP-CSI), wherein the SP-CSI includes either a rank indicator (RI) or a channel state information reference signal resource indicator (CRI). The determination of whether to discard either the uplink transmission or the SRS transmission is based on timing between the action time associated with the SP-CSI and the scheduling time for sending the SRS. The SRS is dropped in response to the SP-CSI overlapping with either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

69. The computer-readable medium according to claim 68, wherein, The action time is based at least on the time for transmitting the Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) (HARQ-ACK) associated with the channel carrying the activation command for the SP-CSI.

70. The computer-readable medium according to claim 55, wherein, When the code is executed by the processor, it further causes the processor to perform the following operations: The uplink transmission is determined to be on a physical uplink shared channel (PUSCH) that includes either a rank indicator (RI) associated with aperiodic channel state information (A-CSI) or a channel state information reference signal resource indicator (CRI). The SRS is dropped in response to the PUSCH overlapping with either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

71. The computer-readable medium according to claim 55, wherein, When the code is executed by the processor, it further causes the processor to perform the following operations: It is determined that the uplink transmission is on the Physical Random Access Channel (PRACH); The SRS is dropped in response to the PRACH overlapping with either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS.

72. The computer-readable medium according to claim 55, wherein, When the code is executed by the processor, it further causes the processor to perform the following operations: The uplink transmission is determined to include aperiodic channel state information (A-CSI) on the Physical Uplink Shared Channel (PUSCH). The SRS is discarded in response to the PUSCH overlapping with either the scheduling time for transmitting the SRS or the carrier switching time associated with the SRS, and the SRS being either a periodic SRS (P-SRS) or a semi-persistently scheduled SRS (SPS SRS).

Images