Sounding Reference Signal (SRS) Transmission Based on SRS Transmit Antenna Port Switching

Abstract

The present application relates to devices and components, including devices, systems, and methods, for performing SRS transmission when a UE supports SRS Tx antenna port switching. In one example, a determination is made as to whether a scheduled SRS transmission will impact scheduled DL reception, subject to SRS Tx antenna port switching. If so, SRS transmission and / or DL ​​reception is modified. In a further example, a UE may support SRS TA capability along with SRS Tx antenna port switching capability. In this example, SRS TA may be applied to scheduled SRS transmission.

Description

[Background technology]

[0001] Fifth generation mobile networks (5G) are wireless standards that aim to improve data transmission speeds, reliability, availability, etc. The standard, which is still under development, includes many details regarding users of sounding reference signals (SRS). The RS is a reference signal transmitted by a UE to a base station on an uplink channel, allowing the base station to determine information about the uplink channel, such as the combined effects of multipath fading, scattering, and Doppler, among other types of information. [Brief explanation of the drawings]

[0002] [Figure 1] 1 illustrates an example of a network environment according to some embodiments.

[0003] [Figure 2] 1 illustrates an example of sounding reference signal (SRS) transmit antenna port switching according to some embodiments.

[0004] [Figure 3] 1 illustrates an example of controlling SRS transmission to avoid impacting downlink (DL) reception, or vice versa, according to some embodiments.

[0005] [Figure 4] 10 illustrates another example of controlling SRS transmission to avoid impacting DL reception when a non-zero timing advance (TA) is applied to an uplink frame, or vice versa, according to some embodiments.

[0006] [Figure 5] 10 illustrates yet another example of controlling SRS transmission to avoid impacting DL reception when a non-zero TA is applied to an uplink frame, or vice versa, according to some embodiments.

[0007] [Figure 6] 1 illustrates an example of using SRS TA to time SRS transmissions according to some embodiments.

[0008] [Figure 7] 10 illustrates another example of using SRS TA to time SRS transmissions, according to some embodiments.

[0009] [Figure 8] 1 illustrates an example of a sequence diagram between a user equipment (UE) and a network for controlling SRS transmission to avoid impacting DL reception, or vice versa, according to some embodiments.

[0010] [Figure 9] 1 illustrates an example of an operational flow / algorithm structure for controlling SRS transmission and / or DL reception, according to some embodiments.

[0011] [Figure 10] 10 illustrates another example of an operational flow / algorithm structure for controlling SRS transmission and / or DL reception, according to some embodiments.

[0012] [Figure 11] 1 illustrates an example of a sequence diagram between a UE and a network for timing SRS transmissions based on SRS TA, according to some embodiments.

[0013] [Figure 12] 1 illustrates an example operational flow / algorithm structure for timing SRS transmissions based on SRS TA, according to some embodiments.

[0014] [Figure 13] 10 illustrates another example of an operational flow / algorithm structure for timing SRS transmissions based on SRS TA, according to some embodiments.

[0015] [Figure 14] 1 illustrates an example of a receiving component, according to some embodiments.

[0016] [Figure 15] 1 illustrates an example of a UE, according to some embodiments.

[0017] [Figure 16] 1 illustrates an example of a base station, according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0018] The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular structures, architectures, interfaces, techniques, etc., in order to provide a thorough understanding of various aspects of various embodiments. However, it will be apparent to one skilled in the art having the benefit of this disclosure that various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In some instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For purposes of this disclosure, "A or B" means (A), (B), or (A and B).

[0019] Generally, a user equipment (UE) may support a sounding reference signal (SRS) transmit (Tx) antenna port switching capability, where the UE can switch between different antenna ports for SRS transmission. This capability may impact the UE's transmit and / or receive capabilities. For example, if the UE's uplink (UL) and downlink (DL) chains share radio frequency (RF) components, DL reception may be affected due to the required RF coordination between transmit and receive. A guard period may also be used around the SRS symbol. This guard period has a length of at least one symbol, during which UL transmission is not possible. Here, if the SRS symbol is the last symbol in a slot, the associated guard period extends into an adjacent slot, thereby preventing the use of at least the first symbol in the adjacent slot. Similarly, if the SRS symbol is the eighth symbol of a slot (which can only be one of the last six symbols of the slot), the associated guard period extends into the seventh symbol of the slot, thereby preventing the use of at least the seventh symbol of the slot.

[0020] Embodiments of the present disclosure improve transmission and / or reception capabilities when SRS Tx antenna port switching is supported. Such embodiments can be implemented in the UE, the base station communicating with the UE, or distributed between the UE and the base station. In a first example, SRS transmission can be suspended or rescheduled when DL reception is affected. This can be when the DL carries high-priority traffic or control information. Alternatively, DL reception can be suspended or rescheduled. In a second example, SRS timing advance (TA) can be used. The UE can advance or delay SRS transmission to avoid guard periods falling into adjacent slots or the seventh symbol of a slot.

[0021] The following is a glossary of terms that may be used in this disclosure.

[0022] As used herein, the term “circuitry” refers to, is a part of, or includes a hardware component configured to provide a described functionality, such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or memory (shared, dedicated, or group), an application-specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-volume PLD (HCPLD), a structured ASIC, a programmable system-on-chip (SoC)), a digital signal processor (DSP), or the like. In some embodiments, a circuitry can execute one or more software or firmware programs to provide at least a portion of the described functionality. The term “circuitry” can also refer to the combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with program code used to perform the functions of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0023] As used herein, the term "processor circuitry" refers to, is a part of, or includes circuitry capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transferring digital data. The term "processor circuitry" may refer to an application processor, a baseband processor, a central processing unit (CPU), a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device that can execute or otherwise operate computer-executable instructions such as program code, software modules, or functional processes.

[0024] As used herein, the term "interface circuitry" refers to, is a part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term "interface circuitry" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, or the like.

[0025] As used herein, the term "user equipment" or "UE" refers to a device having wireless communication capabilities and may represent a remote user of network resources in a communication network. The term "user equipment" or "UE" may be considered synonymous with and may be referred to as client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0026] The term "base station," as used herein, refers to a device having wireless communication capabilities that is a network element of a communication network (or, more simply, a network) and may be configured as an access node in the communication network. UE access to the communication network may be managed at least in part by a base station, whereby a UE connects with a base station to access the communication network. Depending on the radio access technology (RAT), a base station may be referred to as a gNodeB (gNB), an eNodeB (eNB), an access point, etc.

[0027] As used herein, the term "computer system" refers to any type of interconnected electronic device, computing device, or component thereof. Additionally, the term "computer system" or "system" can refer to various components of a computer that are communicatively coupled to each other. Furthermore, the term "computer system" or "system" can refer to multiple computing devices or multiple computing systems that are communicatively coupled to each other and configured to share computing or networking resources.

[0028] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component in a computing environment, or a physical or virtual component in a particular device, such as a computer device, a mechanical device, memory space, processor / CPU time, processor / CPU usage, processor and accelerator load, hardware time or usage, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory usage, storage, network, database and application, workload unit, etc. "Hardware resources" may refer to computational, storage, or network resources provided by physical hardware element(s). "Virtualized resources" may refer to computational, storage, or network resources provided by a virtualization infrastructure to applications, devices, systems, etc. The terms "network resources" or "communication resources" may refer to resources accessible by a computer device / system via a communication network. The term "system resources" may refer to any kind of shared entity for providing services and may include computing resources or network resources. A system resource can be thought of as a set of coherent functions, network data objects, or services that reside on a single host or multiple hosts and are accessible through a clearly identifiable server.

[0029] As used herein, the term "channel" refers to any tangible or intangible transmission medium used to communicate data or data streams. The term "channel" may be synonymous with or equivalent to "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term indicating a path or medium over which data is communicated. Additionally, as used herein, the term "link" refers to a connection between two devices for the purpose of transmitting and receiving information.

[0030] As used herein, the terms "instantiate," "instantiation," and the like refer to the creation of an instance. An "instance" also refers to a specific occurrence of an object that may occur, for example, during the execution of program code.

[0031] The term "connected" may mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other via a communication channel, link, interface, or reference point.

[0032] As used herein, the term "network element" refers to a physical or virtualized device or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered or referred to as synonymous with networked computer, network hardware, network equipment, network node, virtualized network function, etc.

[0033] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to an information element or an individual piece of content in a data element that contains content. An information element may contain one or more further information elements.

[0034] 1 illustrates a network environment 100 according to some embodiments. The network environment 100 may include a UE 104 and a gNB 108. The gNB 108 may be a base station providing a radio access cell, e.g., a 3rd Generation Partnership Project (3GPP®) New Radio (NR) cell, through which the UE 104 can communicate with the gNB 108. The UE 104 and the gNB 108 can communicate over an air interface that conforms to 3GPP technical specifications, such as those defining fifth-generation (5G) NR system standards.

[0035] The gNB 108 can transmit information (e.g., data and control signaling) in the downlink direction by mapping logical channels onto transport channels and mapping the transport channels onto physical channels. Logical channels can transfer data between the Radio Link Control (RLC) layer and the Medium Access Control (MAC) layer, transport channels can transfer data between the MAC layer and the PHY layer, and physical channels can transfer information over the air interface. Physical channels can include a Physical Broadcast Channel (PBCH), a Physical Downlink Control Channel (PDCCH), and a Physical Downlink Shared Channel (PDSCH).

[0036] The PBCH may be used to broadcast system information that the UE 104 can use for initial access to the serving cell. The PBCH may be transmitted along with a physical synchronization signal (PSS) and a secondary synchronization signal (SSS) in a synchronization signal (SS) / PBCH block. The SS / PBCH block (SSB) may be used by the UE 104 during cell search procedures (including cell selection and reselection) and for beam selection.

[0037] The PDSCH may be used to transport end-user application data, signaling radio bearer (SRB) messages, system information messages (eg, other than MIBs), and paging messages.

[0038] The PDCCH can transport downlink control information (DCI) used by the scheduler of the gNB 108 to allocate both uplink and downlink resources. DCI can also be used to provide uplink power control commands, configure slot formats, or indicate that preemption has occurred.

[0039] The gNB 108 may also transmit various reference signals to the UE 104. The reference signals may include demodulation reference signals (DMRS) for the PBCH, PDCCH, and PDSCH. The UE 104 may compare the received version of the DMRS with the transmitted known DMRS sequence to estimate the effect of the propagation channel. The UE 104 may then apply the inverse of the propagation channel during the demodulation process of the corresponding physical channel transmission.

[0040] Reference signals may also include channel state information reference signals (CSI-RS), which may be a multipurpose downlink transmission that may be used for CSI reporting, beam management, connected mode mobility, radio link failure detection, beam failure detection and recovery, and fine-tuning of time and frequency synchronization.

[0041] Reference signals and information from physical channels may be mapped to resources in a resource grid. One resource grid exists for a given antenna port, subcarrier spacing configuration, and transmission direction (e.g., downlink or uplink). The basic unit of the NR downlink resource grid may be a resource element, which may be defined by one subcarrier in the frequency domain and one orthogonal frequency division multiplexing (OFDM) symbol in the time domain. Twelve consecutive subcarriers in the frequency domain may constitute a physical resource block (PRB). A resource element group (REG) may include one PRB in the frequency domain and one OFDM symbol in the time domain, for example, 12 resource elements. A control channel element (CCE) may represent a group of resources used to transmit the PDCCH. One CCE may be mapped to several REGs, for example, six REGs.

[0042] Transmissions using different antenna ports may experience different wireless channels. However, in some situations, different antenna ports may share common wireless channel characteristics. For example, different antenna ports may have similar Doppler shift, Doppler spread, mean delay, delay spread, or spatial receiver parameters (e.g., characteristics related to the angle of arrival of the downlink received signal at the UE). Antenna ports that share one or more of these large-scale wireless channel characteristics may be said to be quasi-collocated (QCL) with each other. 3GPP defines four types of QCLs to indicate which specific channel characteristics are shared. For example, in QCL Type A, the antenna ports share Doppler shift, Doppler spread, mean delay, and delay spread. In QCL Type B, the antenna ports share Doppler shift and Doppler spread. In QCL Type C, the antenna ports share Doppler shift and mean delay. In QCL Type D, the antenna ports share spatial receiver parameters.

[0043] The gNB 108 may provide transmission configuration indicator (TCI) status information to the UE 104 to indicate the QCL relationship between the antenna port used for reference signals (e.g., synchronization signals / PBCH or CSI-RS) and downlink data or control signaling, e.g., PDSCH or PDCCH. The gNB 108 can use a combination of RRC signaling, MAC control element signaling, and DCI to inform the UE 104 of these QCL relationships.

[0044] The UE 104 can transmit data and control information to the gNB 108 using a physical uplink channel. Different types of physical uplink channels are possible, including, for example, a physical uplink control channel (PUCCH) and a physical uplink shared channel (PUSCH). The PUCCH carries control information such as uplink control information (UCI) from the UE 104 to the gNB 108, while the PUSCH carries data traffic (e.g., end user application data) and can carry UCI. Reference signals can also be transmitted from the UE 104 to the gNB 108 to derive information about the UL from the UE 104 to the gNB 108. Such reference signals include, for example, an SRS.

[0045] The UE 104 and the gNB 108 may perform beam management operations to identify and maintain desired beams for transmission in the uplink and downlink directions. Beam management may apply to both the PDSCH and PDCCH in the downlink direction and the PUSCH and PUCCH in the uplink direction.

[0046] In one example, communications with the gNB 108 and / or base stations may use channels within the Frequency Range 1 (FR1) band (between 40 megahertz (MHz) and 7,125 MHz) and / or the Frequency Range 2 (FR2) band (between 24,250 MHz and 52,600 MHz). The FR1 band includes licensed and unlicensed bands. The NR unlicensed band (NR-U) includes frequency spectrum shared with other types of radio access technologies (RATs) (e.g., LTE-LAA, WiFi, etc.). A listen-before-talk (LBT) procedure may be used to avoid or minimize collisions between different RATs in NR-U, whereby devices should apply a clear channel assessment (CCA) check before using a channel.

[0047] 1, the network environment 100 may further include a base station 112 to which the UE 104 may also connect. The base station 112 supports the same RAT as the gNB 108 (e.g., the base station 112 is also a gNB). Additionally or alternatively, the base station 112 supports a different RAT (e.g., a Long Term Evolution (LTE) eNB).

[0048] In one example, the UE 104 supports carrier aggregation (CA), which allows the UE 104 to simultaneously connect and exchange data with the gNB 108 and / or base station 112 via multiple component carriers (CCs). CCs can belong to the same frequency band, in which case they are referred to as intra-band CCs. Intra-band CCs can be adjacent or non-adjacent. CCs can also belong to different frequency bands, in which case they are referred to as inter-band CCs. A serving cell can be configured for the UE 104 to use a CC. The serving cell can be a primary cell (PCell), a primary secondary cell (PSCell), or a secondary cell (SCell). Multiple SCells can be activated via an SCell activation procedure, where the component carriers of these serving cells can be intra-band contiguous, intra-band non-contiguous, or inter-band. The serving cells can be collocated or non-collocated.

[0049] Additionally, the UE 104 may support SRS Tx antenna port switching. This type of capability may affect SRS transmission on the same UL carrier (e.g., UL CC) or reception on a DL carrier (e.g., DL CC). The UL CC and DL CC may be one of a set of band combinations supported by the UE 104.

[0050] FIG. 2 illustrates an example of SRS transmit antenna port switching 200, according to some embodiments. In the figure, multiple slots within a frame may be used for transmission on a UL CC. While FIG. 2 shows eight slots numbered "0" through "7," a different number of slots is possible. A transmission may include SRS transmission in "Slot 1" and "Slot 5," etc. Again, FIG. 2 shows SRS transmission in these two specific slots, each using a specific SRS resource set. However, a different number of SRS transmissions, a different number of slots, or other slots may be used for SRS transmission, and / or different SRS resource sets per slot are possible. Also shown are resource grids for "Slot 1" and "Slot 5," each showing the SRS resource set with a dark, solid rectangle. While FIG. 2 illustrates the two slots as using a similar pattern for SRS resource sets, different patterns may be used. Generally, along the time domain, the SRS is encoded within an OFDMA symbol, which may only be one of the last six symbols of a slot.

[0051] In one example, the UE uses the 1T2R capability of SRS Tx antenna port switching. As described further below, other SRS Tx antenna port switching capabilities are possible. 1T2R capability corresponds to the UE using the same SRS port (e.g., SRS port "0") to transmit a first SRS resource set and a second SRS resource set while switching between two different antenna ports (e.g., "antenna port 0" and "antenna port 1") for transmission of these two SRS resource sets. In the example of FIG. 2, "antenna port 0" is used for SRS transmission in "slot 1." For SRS transmission in "slot 5," the antenna port is switched to "antenna port 1."

[0052] 3GPP TS 38.306 V16.3.0(2020-12) refers to SRS Tx antenna port switching as "srs-TxSwitch, srs-TxSwitch-v1610." It defines this capability as whether the UE supports SRS for DL CSI acquisition, as defined in Section 6.2.1.2 of TS 38.214. The capability signaling includes the following parameters: -supportedSRS-TxPortSwitch indicates the SRS Tx port switching pattern supported by the UE and is mandatory in capability signaling. An indicated UE antenna switching capability of 'xTyR' corresponds to the UE capable of SRS transmission on 'x' antenna ports across 'y' antennas, where 'y' corresponds to all or a subset of the UE receive antennas, and 2T4R is two pairs of antennas. supportedSRS-TxPortSwitch-v1610 is optional to report and indicates the downgrade configuration of the SRS transmit port switching pattern. If the UE uses supportedSRS-TxPortSwitch-v1610 to signal support for the downgrade configuration of the SRS Tx port switching pattern, the UE shall report a value for this based on what is reported in supportedSRS-TxPortSwitch as follows: supportedSRS-TxPortSwitch supportedSRS-TxPortSwitch-v1610 t1r2 t1r1-t1r2 t1r4 t1r1-t1r2-t1r4 t2r4 t1r1-t1r2-t2r2-t2r4 t4r4 t1r1-t2r2-t4r4 t1r4-t2r4 t1r1-t1r2-t2r2-t1r4-t2r4-t2r4 -txSwitchImpactToRx indicates the entry number of the first listed band with UL (see NOTE) in the band combination that affects this DL, and is mandatory for capability signaling. -txSwitchWithAnotherBand is the entry number of the first listed band that has a UL (see NOTE) in the band combination that switches with this UL, and is mandatory for capability signaling. For txSwitchImpactToRx and txSwitchWithAnotherBand, a value of 1 means the first entry, a value of 2 means the second entry, etc. All DLs and ULs that switch together point to the same entry number. The entry number is the band entry number in the band combination. The UE is restricted not to include fallback band combinations for the purpose of indicating different SRS antenna switching capabilities.

[0053] SRS Tx antenna port switching may require a period of time to adjust the RF chain for SRS transmission on the UL CC. This adjustment may impact reception on the DL CC when the UL and DL share RF components of the RF chain. This impact may be signaled from the UE to the network. In particular, 3GPP TS 38.306 V16.3.0(2020-12) describes using the above-mentioned "txSwitchImpactToRx" as an indication of this impact. Nevertheless, there is no definition of a process for mitigating the impact other than indicating that the DL CC is affected. An embodiment of such a process is described with reference to the following figure.

[0054] FIG. 3 illustrates an example of controlling SRS transmission 300 to avoid impacting DL reception, or vice versa, according to some embodiments. As shown, DL CC 310 can be used for DL reception, whereby a UE receives traffic, reference signals, and / or control information encoded within the symbols of slots of DL CC 310. UL CC 320 can be used for UL transmission, whereby a UE transmits traffic, reference signals, and / or control information encoded within the symbols of slots of UL CC 320. The DL CC 310 and UL CC 320 can be supported band combinations. Each slot is depicted as a rectangle and listed with a corresponding number (e.g., "DL0" refers to "slot 0" on DL CC 310, and "UL0" refers to "slot 0" on UL CC 320). Downlink slots can belong to a downlink frame, while uplink slots can extend into an uplink frame. In the example of FIG. 3, the TA between the uplink frame and the downlink frame is 0.

[0055] In one example, a UE can transmit an SRS in an uplink slot while supporting SRS Tx antenna port switching capability. In the example of FIG. 3, a first SRS (e.g., a first SRS symbol) is transmitted on "UL1" and a second SRS (e.g., a second SRS symbol) is transmitted on "UL2." A guard period (denoted as "GP" in the figure) is used before and after each SRS (e.g., occupying at least one symbol before and at least one symbol after the SRS symbol). 3GPP TS38.214 V16.4.0(2020-12) defines a guard period as "a guard period of Y symbols during which a UE does not transmit other signals when a set of SRS resources is transmitted in the same slot." The guard period is between the set of SRS resources. The value of Y is shown in Table 1 and depends on the CC numerology. [Table 1]

[0056] In the example of FIG. 3 , SRS transmissions in “UL1” and “UL2” can affect DL reception in “DL2” (as indicated by the hatched slots in the figure). In particular, considering the first SRS in “UL1,” its subsequent guard period falls in “UL2” (whereby the preceding guard period is in “UL1”). Given 0-TA, “UL2” is parallel to “DL2” in the time domain. Due to SRS Tx antenna port switching, the UE may adjust its RF chain in the subsequent guard period, thereby adjusting this RF chain for a period of time during DL reception in “DL2.” This period is shown as overlap 330. Because the RF chain is adjusted during overlap 330, symbols in “DL2” (e.g., received DL signal, demodulated DL signal, decoded DL signal, etc.) that would have been processed during this period are not processed successfully, thereby affecting DL reception in “DL2.”

[0057] Now, considering a second SRS in "UL2," this SRS completely overlaps with "DL2." This overlap is shown in FIG. 3 as overlap 340. Again, due to SRS Tx antenna port switching, the UE may adjust its RF chain for transmission of the second SRS, thereby adjusting this RF chain within overlap 340 "DL2." Because the RF chain is adjusted during overlap 340, symbols in "DL2" that would have been processed during this period (e.g., received DL signals, demodulated DL signals, decoded DL signals, etc.) are not processed successfully, thereby affecting DL reception in "DL2."

[0058] It is possible to mitigate the impact of SRS transmission on DL reception (in light of the SRS Tx antenna port switching capability). In particular, the UE is scheduled and / or configured to receive high-priority DL symbols / slots / occasions from the network (e.g., in "DL2"), transmit SRS (e.g., in "UL1" and "UL2"), and indicate that the SRS transmission will affect this DL reception. This scheduling or configuration may rely on downlink scheduling information from the network, such as RRC signaling, MAC CE, and / or DCI. DL reception (e.g., in "DL2") may be for high-priority downlink data, reference signals for Layer 1 or Layer 3 measurements, or system information. In particular, "DL2" may carry Ultra-Reliable and Low Latency Communication (URLLC) data, RS (e.g., SSB, CSI-RS) for L1 or L3 measurements, and / or system information for the DL channel. Scheduling of SRS transmission may use SRS scheduling information, which may be RRC signaling, MAC CE, and / or DCI. The SRS transmit impact can be indicated to the network by using "txSwitchImpactToRx".

[0059] The UE checks whether a DL symbol / slot / occasion overlaps with an SRS symbol(s) or SRS-related guard period(s). This check can be based on DL scheduling information, which informs the UE of the symbol / slot / occasion when DL reception is scheduled, and SRS scheduling information, which informs the UE of the symbol / slot / occasion when SRS transmission is scheduled. An overlap exists between an SRS symbol and DL reception, or between an associated guard period and DL reception, if their associated scheduled / configured timing occurs parallel in the time domain. This overlap can be a complete overlap (e.g., the timing of the SRS symbol transmission or the timing of the guard period can be scheduled within the timing of the DL reception) or a partial overlap (e.g., the overlap is a relatively short time length, and this overlap time length is equal to or greater than a predefined threshold time). Here, a guard period is used, and its time length may, but need not, be defined as a function of the symbol as in 3GPP TS38.214 V16.4.0(2020-12). For example, the guard period represents the transient period required for the UE to complete RF tuning for SRS Tx antenna port switching, which may be less than the length of a symbol, such as approximately 500 ms or some other value.

[0060] Similarly, the network may determine the overlap based on downlink scheduling information and SRS sounding information. However, in certain situations, the UE may apply TA with time synchronization that may not be known to the network. In such situations, the UE may determine the overlap more accurately.

[0061] Once overlap is determined (e.g., by the UE or the network), different approaches are possible to mitigate the impact of DL reception. In one approach, the UE can adjust the scheduled transmission (e.g., by using a different slot or symbol within the current slot), adjust the transmission itself (e.g., by shortening the guard period), and / or suspend the scheduled SRS transmission. Suspending can include any, combination, or all of muting the scheduled transmission of the SRS symbol (e.g., processing the SRS symbol but not transmitting it), canceling the scheduled transmission (e.g., partially processing and stopping this processing or avoiding the processing altogether), skipping the scheduled transmission (e.g., by applying a hopping pattern), repurposing the symbol (e.g., from being used to transmit SRS to transmitting non-SRS), or any other technique that alters the transmission of the SRS such that its impact on DL reception is avoided entirely or reduced to the shortest amount of time (or number of DL symbols) possible.

[0062] In another approach, the network can inform the UE to adjust the scheduled SRS transmission (in which case the network can provide updated SRS scheduling information), adjust the scheduled transmission itself (e.g., by signaling a shorter length of time to use as a guard period), or suspend (e.g., including muting, canceling, repurposing, or any other technique). Alternatively or additionally, the network can inform the UE to suspend (e.g., muting, canceling, skipping, repurposing, and / or any other technique that modifies DL reception such that the impact from the SRS transmission is avoided entirely or reduced to the shortest possible amount of time) or that DL reception be rescheduled (in which case the network can provide updated DL scheduling information). In this approach, the network may have received an indication of the overlap from the UE or may have determined the overlap itself based on the downlink scheduling information and the SRS scheduling information.

[0063] In both of the above approaches, if there is no overlap, SRS transmission does not affect DL reception. Therefore, no changes to SRS transmission and / or DL reception may be made. Furthermore, assuming there is overlap, no changes are made if the DL carries non-high priority traffic, reference signals, or control information.

[0064] As described herein above, the overlap may be partial. To determine whether such partial overlap should trigger a change to SRS transmission and / or DL reception, the duration of the overlap is compared to a predefined threshold time. This predefined threshold time may be stored in the UE's memory and may be specified by design or in a technical specification. For example, this predefined threshold time may represent the transient time required to complete RF adjustments to support SRS Tx antenna port switching. Additionally or alternatively, the threshold time may be signaled to the UE by the network, e.g., in an RRC configuration. Furthermore, the UE may signal the duration to the network (e.g., in UL information, without PUCCH or PUSCH), allowing the network to compare the duration with the predefined threshold time.

[0065] 4 illustrates another example of controlling SRS transmission 400 to avoid impacting DL reception when a non-zero TA is applied to an uplink frame, or vice versa, according to some embodiments. Control 400 may be similar or the same as control 300 of FIG. 3, whereby a UE or the network can determine overlap between SRS transmission and DL reception, and the UE can adjust SRS transmission and / or DL reception automatically or in response to information from the network. However, here, the illustrated overlap is partial. The reason for this partial overlap may be a non-zero TA.

[0066] In the example of FIG. 4, DL CC 410 can be used for DL reception, whereby the UE receives traffic, reference signals, and / or control information encoded in symbols of slots of DL CC 410. UL CC 420 can be used for UL transmission, whereby the UE transmits traffic, reference signals, and / or control information encoded in symbols of slots of UL CC 420. DL CC 410 and UL CC 420 can be supported band combinations. Each slot is depicted as a rectangle and listed with a corresponding number. Downlink slots can belong to a downlink frame, while uplink slots can extend into an uplink frame. In the example of FIG. 4, TA 412 is used to advance the uplink frame relative to the downlink frame, whereby the UE transmits UL symbols prior to receiving DL symbols based on a TA command (TAC) from the network for the amount of time the UE needs to advance the UL transmission.

[0067] In one example, a UE can transmit an SRS in an uplink slot while supporting SRS Tx antenna port switching capability. In the example of Figure 4, a first SRS (e.g., a first SRS symbol) is transmitted on "UL1" and a second SRS (e.g., a second SRS symbol) is transmitted on "UL2." A guard period (denoted as "GP" in the figure) is used before and after each SRS (e.g., occupying at least one symbol before and at least one symbol after the SRS symbol).

[0068] In the example of FIG. 4 , SRS transmissions in "UL1" and "UL2" can affect DL reception in "DL2" (as indicated by the hatched slots in the figure). In particular, considering a first SRS in "UL1," its subsequent guard period partially falls within "UL2" (whereby the preceding guard period is in "UL1"). The overlap time is shown as partial overlap 430. In comparison, a second SRS transmission in "UL2" completely overlaps with "DL2." This overlap is shown as full overlap 440 in FIG. 4. In both cases, because the RF chains are adjusted during the partial overlap 430 or full overlap 440, symbols in "DL2" (e.g., received DL signals, demodulated DL signals, decoded DL signals, etc.) that would have been processed during that time are not processed correctly, thereby affecting DL reception in "DL2."

[0069] The length of time of the overlap 430 is compared to a predefined threshold time to determine if the partial overlap 430 should trigger a change to SRS transmission and / or DL reception as a mitigation process. If the predefined time threshold is exceeded, the mitigation process is implemented.

[0070] FIG. 5 illustrates yet another example of controlling SRS transmission 500 to avoid impacting DL reception when a non-zero TA is applied to an uplink frame, or vice versa, according to some embodiments. Control 500 is similar to control 400 of FIG. 4. Similarities are not repeated herein for brevity. In FIG. 4, the length TA 412 was shorter than half a slot. As a result, a partial overlap 430 existed between the guard period following the SRS (e.g., SRS symbol) in an uplink slot and the DL slot following the uplink slot. In comparison, in FIG. 5, the length of TA 512 is longer than half a slot. Thus, a partial overlap 530 exists between the guard period preceding the SRS (e.g., SRS symbol) in an uplink slot and the DL slot that also precedes the uplink slot. Thus, the mitigation process (e.g., modifying either or both SRS transmission or DL reception) can be applied not only to the DL slot following a UL slot carrying an SRS (e.g., as in FIG. 4), but also to the DL slot preceding such a UL slot (e.g., as in FIG. 5).

[0071] 6 illustrates an example of using SRS TA to time SRS transmissions 600, according to some embodiments. SRS TA represents another mitigation process that can reduce or avoid the impact of SRS transmissions on subsequent slots on the same UL CC. This mitigation process can equally be applied to reduce or avoid the impact of SRS transmissions on DL reception on DL CCs.

[0072] In one example, an SRS TA represents a TA specific to SRS transmission. In particular, the SRS TA applies to advance (e.g., advance or delay) the transmission of an SRS symbol or set of SRS symbols scheduled in a slot, but does not apply to advance the transmission of non-SRS symbols in the same slot or other slots and / or the transmission of another SRS symbol or set of SRS symbols scheduled in another slot (e.g., in an adjacent slot).

[0073] Two adjacent slots, "Slot n" and "Slot n+1," which follows and is adjacent to Slot n, are shown in FIG. 6. Each of the two slots includes 14 symbols, listed by the corresponding symbol number (e.g., "Symbol 0" is the first symbol in the slot, "Symbol 7" is the eighth symbol in the slot, and "Symbol 13" is the last symbol in the slot). An SRS occasion represents the set of symbols in a slot that can be used to transmit one or more SRS symbols. This SRS occasion spans the last six symbols in the slot (e.g., starting with the ninth symbol and ending with the last, 14th symbol). The number of SRS symbols to transmit and the specific slot locations of such symbols can be configured by the network. Generally, the SRS Tx antenna switching capability can affect this number. For example, with 1T4R or 2T4R SRS Tx antenna switching capability, the network can schedule as many SRS symbols as possible in a slot, as this advanced capability can enable the network to determine a relatively large set of channel information. With the SRS Tx antenna switching capability, a guard period is applied before and after each SRS symbol. Thus, in a six-symbol SRS occasion, up to three SRS symbols may be transmitted, where pairs of SRS symbols are separated by guard periods, with the first guard period preceding the first SRS symbol and the last guard period following the last SRS symbol.

[0074] In the example of Figure 6, a specific distribution of SRS symbols in the first "slot n" is shown. This distribution includes three SRS symbols (indicated by the hatched squares located at "Symbol 9," "Symbol 11," and "Symbol 13" of "slot n"). A distribution of guard periods is also required and includes four guard periods. The first three guard periods are within "slot n" (indicated by the dotted squares located at "Symbol 8," "Symbol 10," and "Symbol 12" of "slot n"). The final guard period follows the last SRS symbol at "Symbol 13" of "slot n," and therefore, is within an adjacent slot (indicated by the dark solid square located at "Symbol 0" of "slot n+1").

[0075] Due to the above distribution of SRS symbols and required guard periods, the guard period of an SRS transmission in a UL slot (e.g., "slot n") can affect transmissions (SRS or non-SRS) in an adjacent UL slot (e.g., "slot n+1"). Specifically, the last guard of an SRS transmission in the first "slot n" falls in the first symbol in the adjacent "slot n+1." As a result, the UE cannot transmit a symbol in the first symbol of "slot n+1." Naturally, this impact on UL transmissions in adjacent slots depends on the length of the guard period. With longer guard periods (e.g., two symbols long), the impact can be more severe.

[0076] Furthermore, this effect is not limited to when three SRS symbols are scheduled for transmission in a slot. For example, this effect also occurs when only one SRS symbol is scheduled for transmission in the last symbol of "slot n."

[0077] Use of the SRS TA 610 can mitigate this effect. In particular, the UE advances the SRS symbol transmission via the SRS TA 610 (e.g., moves it forward as in FIG. 6 or delays it as in FIG. 7) so that the guard period does not extend into the first symbol of the adjacent "slot n+1." By doing so, this first symbol in "adjacent slot n+1" (shown by the horizontal dashed square in FIG. 6) is no longer affected by the last SRS symbol in "slot n" and becomes available for UL transmission.

[0078] In one example, the length of the SRS TA 610 is shorter than the guard period (e.g., half its length, or some other fraction or percentage). The first occurring guard period (e.g., the guard period located at symbol 8 of slot n) is replaced with or shortened to transition period 620. Similarly, the last occurring guard period (e.g., the guard period that would have been located at symbol 0 of slot n+1) is replaced with or shortened to transition period 630. The transition period (e.g., 620 or 630) is equal to or longer than the time required by the UE for RF adjustment to support SRS Tx antenna port switching and has a time length shorter than the time length of a typical guard period. When the SRS TA 610 is half the guard period, the transition periods 620 and 630 are equal to each other. Otherwise, the transition periods 620 and 630 are not equal, but their sum is equal to the time length of the guard period.

[0079] Different approaches are possible for defining the SRS TA 610. In one approach, the SRS TA 610 is predefined as the difference between the guard period for the UE to complete RF tuning and the actual transient period. This predefined time value can be stored in the UE's memory and can be specified by design or in a technical specification. In another approach, the network can configure the SRS TA 610 for the UE. This network-based approach can include one or more sub-approaches. In the first sub-approach, the network can configure a set of candidate SRS TAs for the UE. Upon determining that a scheduled SRS transmission in a slot will affect the next slot (or DL reception, as in the above figure), the network can inform the UE of a particular SRS TA from the set for the UE to use as the SRS TA 610. Here, the network can determine the impact based on SRS scheduling information scheduling the SRS transmission in "slot n" and other scheduling information (e.g., scheduling an UL transmission or DL reception in "slot n+1"). Additionally or alternatively, the UE can determine the impact based on SRS scheduling information, and other scheduling information can indicate the impact to the network (e.g., in UL control information). The initial configuration of the set of candidate SRS TAs can be via RRC signaling, MAC CE, and / or DCI. Subsequent indication of a particular SRS TA 610 can also be via RRC signaling, MAC CE, and / or DCI. In another sub-approach, the initial configuration can be skipped. Instead, the network can directly signal the SRS TA 610 (e.g., without an indication of the set of SRS TAs) to use in determining the impact (locally or based on an indication from the UE). Again, this indication can be via RRC signaling, MAC CE, and / or DCI.

[0080] In these various approaches, the SRS TA 610 can be defined to have a length of {+(x%*symbol length),-(x%*symbol length),0}, where "x" is a positive value (e.g., 50 for a 50 percent multiplier). A positive length (e.g., +(x%*symbol length)) is used to advance as in FIG. 6. A negative length (e.g., -(x%*symbol length)) is used to delay as in FIG. 7. A 0 length is used when there is no need to advance or delay the TA. The symbol length is based on the SRS subcarrier spacing (SCS), PUCCH SCS, or PUSCH SCS. Furthermore, when predefined for the UE or configured by the network, the SRS TA 610 can be set per SRS resource, per SRS resource set, per UE, per CC, per serving cell, or per SCS.

[0081] Different approaches for using the SRS TA 610 are possible. In one approach, the UE determines the applicable SRS TA 610 (whether from a predefined set of candidate SRS TAs or from a network-configured set of candidate SRS TAs). To do so, the UE may rely on a set of rules implemented in logic stored in the UE's memory and executed by the UE's processor. This logic may be specified by design or in a technical specification. The rules may take into account the location of the SRS symbols scheduled for transmission in the slot, the number of SRS symbols scheduled for transmission in the slot, and the priority of DL reception.

[0082] As an example of a symbol location rule, if an SRS symbol is adjacent to another symbol of a UL channel (e.g., a UL CC) in the same slot or an adjacent slot, the UE determines that the SRS TA is applicable. If the SRS symbol is before another symbol (e.g., "SRS symbol 13" in "slot n+1" is before "symbol 0" in "slot n+1"), the SRS TA is used to advance the SRS symbol transmission by "Y" milliseconds (e.g., "Y" is equal to the difference between the guard period and the transition period 620). Otherwise, the SRS symbol is after another symbol. In this case (as further shown in FIG. 7), the SRS TA is used to delay the SRS symbol transmission by "Y" milliseconds.

[0083] In one example of a symbol number rule, if this number is greater than a predefined threshold number (e.g., 2), the UE determines that the guard period is in effect and, therefore, SRS TA is applicable. The advance or delay depends on either the SRS symbol location or the guard period location. If the SRS symbol is the last symbol in a slot or SRS occasion (or, equivalently, the guard period is the first symbol in an adjacent slot), the transmission of the SRS symbol is advanced by 'Y' milliseconds. By comparison (as further shown in FIG. 7), if the SRS symbol is the ninth symbol in a slot or the first symbol in an SRS occasion (or, equivalently, the guard period is the eighth symbol in that same slot), the transmission of the SRS symbol is delayed by 'Y' milliseconds.

[0084] In one example of a DL reception rule, upon determining that a DL slot is affected (e.g., as shown in connection with Figures 3-5), the UE determines whether the SRS transmission is scheduled to occur before or after the DL reception. If before, the transmission of the SRS symbols is advanced by "Y" milliseconds. If not, the transmission of the SRS symbols is delayed by "Y" milliseconds. Similar UL transmission rules can be defined. In particular, if the guard period of an SRS symbol transmitted in a slot overlaps with an UL transmission using another slot, the SRS TA applies. The other slot may be an adjacent slot on the same UL CC or a different UL CC.

[0085] FIG. 7 shows another example 700 of using an SRS TA 710 to time an SRS transmission, according to some embodiments. The SRS TA 710 and setup is similar to the SRS 610 and setup of FIG. 6. The similarities will not be repeated here for the sake of brevity. In FIG. 7, rather than advancing the SRS transmission, this SRS transmission is delayed by the SRS TA 710 because the effect of the SRS transmission is on the portion of "slot n" outside of the SRS occasion for this slot.

[0086] In the particular example of FIG. 7 , the distribution of SRS symbols in the first "Slot n" includes three SRS symbols (indicated by the diagonally dashed squares located at "Symbol 8," "Symbol 10," and "Symbol 12" of "Slot n"). A distribution of guard periods is also required and includes four guard periods. All four guard periods are within "Slot n." The final three guard periods accompany the SRS occasion in "Slot n" (indicated by the dotted squares located at "Symbol 9," "Symbol 11," and "Symbol 13" of "Slot n"). However, the first guard period is outside the SRS occasion and is located at the eighth symbol (e.g., "Symbol 7" of "Slot n," indicated by the solid black square). Therefore, this guard period impacts the use of symbols in "Slot n" that are outside the SRS occasion; these symbols are available for non-SRS transmission. Depending on the actual length of the guard period, this effect may be at least one symbol (eg, at least "symbol 7" is not available for UL transmission).

[0087] Furthermore, this effect is not limited to when three SRS symbols are scheduled for transmission in a slot. For example, this effect also occurs when only one SRS symbol is scheduled for transmission in the first symbol of an SRS occasion (e.g., "symbol 8" of "slot n").

[0088] Use of the SRS TA 710 can mitigate this effect. In particular, the UE delays its SRS symbol transmission via the SRS TA 710 so that the guard period does not extend until the seventh symbol of "slot n." By doing so, this seventh symbol (shown in FIG. 7 by the horizontal dashed box) is no longer affected by the first SRS symbol in the SRS occasion of "slot n" and becomes available for UL transmission.

[0089] In one example, the length of SRS TA 710 is shorter than the guard period (e.g., half its length, or some other fraction or percentage). The first occurring guard period (e.g., the guard period that would have been located at "symbol 7" of "slot n") is replaced with or shortened to transition period 720. Similarly, the last occurring guard period (e.g., the guard period that would have been located at "symbol 13" of "slot n") is replaced with or shortened to transition period 730.

[0090] Referring back to Figures 3-7, a UE can signal its ability to support SRS TA to the network, which may be indicated along with or in conjunction with supporting the capability for SRS Tx antenna port switching. This indication can be transmitted in UE capability information. The UE capability information can indicate support or lack thereof, and optionally, a supported set of candidate TAs. Capabilities may also be indicated as available per SRS resource, per SRS resource set, per UE, per CC, per serving cell, or per SCS. Controls 300, 400, and 500 in Figures 3-5 and SRS TAs 610 and 710 in Figures 6-7 may be used in conjunction with or independently of each other. In one example, if a UE reports SRS TA capability to the network, and this SRS TA capability is not supported, the UE may default to using controls 300, 400, and 500 in Figures 3-5. In comparison, if the capability is supported, the controls 300, 400, 500 are used by default unless otherwise signaled by the network to use SRS TA, or alternatively, the SRS TA capability is used by default unless otherwise signaled by the network to use controls 300, 400, 500.

[0091] 8 illustrates an example sequence diagram 800 between a UE 810 and a network 820 for controlling SRS transmission to avoid impacting DL reception, or vice versa, according to some embodiments. Communication between the UE 810 and the network 820 may be carried via one or more base stations of the network 820 and / or one or more component carriers of such base station(s).

[0092] In one example, sequence diagram 800 includes the UE 810 transmitting information about its SRS TA capabilities to the network 820. For example, this information can be transmitted in UE capability information and can indicate whether the UE supports SRS TA in conjunction with SRS Tx antenna port switching, as described above. As indicated by the dashed arrow, transmission of this information may be optional. If transmitted, the network 820 can determine whether the UE 810 supports SRS TA and, if so, configure a set of candidate SRS TAs for the UE 810. This set can be used separately or in conjunction with modifications to SRS transmission or DL reception, which modifications are further described in the next step of sequence diagram 800. If not supported, the modifications to SRS transmission or DL reception can be the default behavior that the network 820 expects the UE 810 to support.

[0093] The sequence diagram 800 also includes the network 820 transmitting DL scheduling information to the UE 810. This information indicates a set of symbols / slots / occasions for DL reception by the UE 810. In addition, this information may indicate a priority of DL reception (e.g., high priority for URLLC data, system information, or reference signals). In addition, the network 820 transmits SRS scheduling information to the UE 810. This information indicates a set of symbols / slots / occasions for transmission of SRS symbols by the UE 810.

[0094] In one example, as indicated by the dashed arrow as an optional step, the sequence diagram 800 further includes the UE 810 transmitting an overlap indication to the network 820. For example, the UE determines the overlap between the scheduled DL reception and the scheduled SRS transmission. The overlap may be complete or partial and may include overlap between the guard period and the scheduled DL reception. The indication may identify to the network the length of time or number of symbols of overlap between the SRS symbol and the DL reception or between the guard period of the SRS symbol and the DL reception. This determination is based on the DL scheduling information and the SRS scheduling information. If so, the UE 810 transmits an indication of overlap. In another example, no indication is transmitted. Instead, the UE 810 may automatically implement the change to the scheduled SRS transmission by, for example, rescheduling this transmission, changing parameters of the transmission (e.g., using a transition time for SRS Tx antenna port switching instead of a guard period, using SRS TA if supported, etc.), or suspending the SRS transmission. In yet another example, the UE 810 does not transmit an overlap indication, but instead the network 820 itself determines the overlap based on DL scheduling information and SRS scheduling information.

[0095] In a further example, as indicated by the dashed arrows as an optional step, the sequence diagram 800 also includes the network 820 transmitting information about changes to SRS transmission and / or DL reception. This information may be transmitted once the network 820 determines an overlap locally or based on receiving relevant information from the UE 810. In either case, the network 820 may inform the UE 810 whether to reschedule the SRS transmission, change parameters of the SRS transmission, or suspend the SRS transmission, and / or reschedule DL reception, change parameters of the DL reception (e.g., a DL symbol is no longer used, but the remaining SL symbols are unaffected), and / or suspend DL reception.

[0096] 9 illustrates an example of an operational flow / algorithm structure 900 for controlling SRS transmission and / or DL reception, according to some embodiments. A UE may implement the operational flow / algorithm structure 900 to avoid or reduce impact on DL reception when the impact is due to the UE's capability for SRS Tx antenna port switching. The operational flow / algorithm structure 900 may be executed or implemented by a UE, such as, for example, the UE 104, 810, 1500, or a component, such as, for example, the processor 1504. The UE may communicate with a network by being communicatively coupled to one or more base stations via one or more uplink CCs and one or more DL CCs.

[0097] The operational flow / algorithm structure 900 may include, at 902, transmitting UE capability information to the network indicating that the UE lacks the capability to apply SRS TA to SRS transmission. This operation may be optional. If this operation is performed, the UE informs the network that the UE does not support SRS TA along with the capability for SRS Tx antenna port switching, and the UE may default to mitigating any overlap between SRS transmission and DL reception by applying changes to either SRS transmission or DL reception or both (the changes to SRS transmission do not include SRS TA).

[0098] The operational flow / algorithm structure 900 may include, at 904, receiving downlink scheduling information from the network. This information indicates a set of symbols / slots / occasions for DL reception by the UE and may be sent via RRC signaling, MAC CE, and / or DCI.

[0099] The operational flow / algorithm structure 900 may include receiving SRS scheduling information from the network, at 906. This information indicates a set of symbols / slots / occasions for SRS transmission by the UE and may be transmitted via RRC signaling, MAC CE, and / or DCI.

[0100] The operational flow / algorithm structure 900 may include, at 908, determining an overlap between a downlink reception scheduled based on the downlink scheduling information and (i) an SRS transmission scheduled based on the SRS scheduling information, or (ii) a guard period associated with the SRS transmission. For example, if a TA (non-SRS TA) exists between the downlink frame and the uplink frame, and a scheduled SRS symbol transmission and an associated guard period applied to support SRS Tx antenna port switching exist in a slot of the uplink frame, the UE determines whether the SRS and / or guard period partially or fully overlap with the DL slot of the downlink frame (or a DL symbol within this slot). In the case of a full overlap, a mitigation process can be triggered to avoid or reduce the impact on DL reception. For a partial overlap, the time length can be compared to a predefined threshold time. If the time length is greater than the threshold time, a mitigation process can be triggered.

[0101] The operational flow / algorithm structure 900 may include, at 910, modifying SRS transmission or receiving an indication from the network of the modification to downlink reception UE based on the overlap. For example, the mitigation process is performed locally on the UE, and the UE automatically reschedules the SRS transmission (by sending an associated request to the network), modifies parameters of the SRS transmission, or suspends the SRS transmission. In another example, the mitigation process is distributed between the UE and the network. In this example, the UE sends an indication of the overlap to the network, and the network responds with information about modifying SRS transmission and / or DL reception.

[0102] 10 illustrates another example of an operational flow / algorithm structure 1000 for controlling SRS transmission and / or DL reception, according to some embodiments. A base station can implement the operational flow / algorithm structure 1000 to avoid or reduce an impact on DL reception when the impact is due to UE capability for SRS Tx antenna port switching. The operational flow / algorithm structure 900 may be executed or implemented by a base station, such as, for example, gNB 108, a base station of network 820, or gNB 1600, or a component thereof, such as, for example, processor 1604. The base station may be communicatively coupled to the UE via one or more uplink CCs and one or more DL CCs.

[0103] The operational flow / algorithm structure 1000 may include, at 1002, receiving UE capability information from a UE indicating that the UE lacks the capability to apply SRS timing advance (TA) to SRS transmissions. This operation may be optional. If this operation is performed, the UE capability information indicates that the UE does not support SRS TA along with the capability for SRS Tx antenna port switching, and the UE may default to mitigating any overlap between SRS transmission and DL reception by applying changes to either or both SRS transmission or DL reception (the changes to SRS transmission do not include SRS TA).

[0104] The operational flow / algorithm structure 1000 may further include transmitting downlink scheduling information to the UE, at 1004. This information indicates a set of symbols / slots / occasions for DL reception by the UE and may be sent via RRC signaling, MAC CE, and / or DCI.

[0105] The operational flow / algorithm structure 1000 may further include transmitting SRS scheduling information to the UE at 1006. This information indicates a set of symbols / slots / occasions for SRS transmission by the UE and may be transmitted via RRC signaling, MAC CE, and / or DCI.

[0106] The operational flow / algorithm structure 1000 may include, at 1008, receiving a first indication from the UE of an overlap. The overlap is between a downlink reception scheduled based on the downlink scheduling information and (i) an SRS transmission scheduled based on the SRS scheduling information, or (ii) a guard period associated with the SRS transmission. This operation may be optional, as the overlap may instead be determined by the base station (or network).

[0107] The operational flow / algorithm structure 1000 may include, at 1010, transmitting to the UE a second indication of a change to at least one of SRS transmission or downlink reception based on the first indication. In one example, this transmission is part of a mitigation process. The change may indicate that SRS transmission and / or DL reception is to be rescheduled, a change to parameters of SRS transmission and / or DL reception, and / or a suspension of SRS transmission and / or DL reception.

[0108] 11 shows an example of a sequence diagram 1100 between a UE 1110 and a network 1120 for timing SRS transmissions based on SRS TA, according to some embodiments, where the UE 1110 supports SRS TA capability. Communication between the UE 1110 and the network 1120 may be carried via one or more base stations of the network 1120 and / or one or more component carriers of such base station(s).

[0109] In one example, sequence diagram 1100 includes UE 1110 transmitting information about its SRS TA capabilities to network 1120. For example, this information may be transmitted in UE capability information and may indicate whether the UE supports SRS TA in conjunction with SRS Tx antenna port switching, as described above. Next, as indicated by the dashed arrow as an optional step, network 1120 may optionally configure a set of candidate SRS TAs for UE 1110 and transmit information about this set (e.g., the length, applicable SRS resources, applicable SRS resource sets, applicable CCs, applicable serving cells, applicable SCSs, etc.) for each of these candidate SRS TAs. This configuration information may be transmitted via RRC signaling.

[0110] Sequence diagram 1100 also includes network 1120 sending DL and / or UL scheduling information to UE 1110. This information indicates a set of symbols / slots / occasions for DL reception and / or UL by UE 810. Additionally, as part of this scheduling or separately, network 1120 may also send SRS scheduling information to UE 1110.

[0111] In one example, as an optional step, the UE transmits SRS TA applicability to the network, as indicated by the dashed arrow. Here, the UE is configured with multiple candidate SRS TAs and determines that DL reception (e.g., according to FIGS. 3-5) and / or UL transmission (transmission in a slot adjacent to a slot carrying an SRS symbol(s) according to FIG. 6 or in the same slot carrying an SRS symbol according to FIG. 7) will be affected by the SRS transmission. In this case, the UE can inform the network (e.g., via control information on the UL CC) that SRS TA needs to be applied. The UE 1110 informs the network of the overlap itself (e.g., the time length or number of symbols of overlap between the SRS symbol and DL reception, or between the guard period of the SRS symbol and DL reception or UL transmission). The UE 1110 then receives an indication of the specific SRS TA to use from the candidate SRS TAs from the network 1120 (e.g., via a MAC CE or DCI), as indicated by the final dashed arrow. In other situations, the network 1120 does not configure a set of candidate SRS TAs. Instead, upon receiving an indication of SRS TA applicability, the network informs the UE 1110 of the SRS TA to use. Alternatively, no SRS TA configuration may be performed, or if SRS TA configuration is performed, the UE 1110 may be pre-programmed to determine the particular SRS TA to use.

[0112] 12 illustrates an example operational flow / algorithm structure 1200 for timing SRS transmissions based on SRS TA, according to some embodiments. A UE may implement the operational flow / algorithm structure 1200 to avoid or reduce impacts on DL reception and / or UL transmissions when the impacts are due to the UE's capability for SRS Tx antenna port switching. The operational flow / algorithm structure 1200 may be executed or implemented by a UE, such as, for example, the UE 104, 810, 1500, or a component, such as, for example, the processor 1504. The UE may communicate with a network by being communicatively coupled to one or more base stations via one or more uplink CCs and one or more DL CCs.

[0113] The operational flow / algorithm structure 1200 may include, at 1202, transmitting UE capability information to the network indicating that the UE supports the ability to apply SRS TA to SRS transmissions. This capability may be indicated as related to UE capability for SRS Tx antenna port switching.

[0114] The operational flow / algorithm structure 1200 may include receiving, from the network, information scheduling transmission of SRS symbols in slots, at 1204. This information may be SRS scheduling information indicating symbols / slots / occasions for SRS transmission by the UE, and may be sent via RRC signaling, MAC CE, and / or DCI.

[0115] The operational flow / algorithm structure 1200 may include, at 1206, determining an SRS TA applicable to the transmission of the SRS symbol based on the total number of SRS symbols in the slot, the symbol number of the SRS symbol in the slot, the timing of the guard period of the SRS symbol in the slot or in an adjacent slot, or the overlap of the guard period with downlink reception. For example, the UE applies one or more rules to determine that the SRS TA needs to be applied to mitigate the impact of the SRS transmission on UL transmission and / or DL reception. If the number of scheduled SRS symbols in the slot is greater than a predefined threshold number (e.g., 2), the UE determines that the SRS transmission will affect UL transmissions in symbols outside the SRS occasion of the slot (if the first SRS symbol is the ninth symbol) or UL transmissions using an adjacent slot (if the SRS symbol is the last symbol of the slot). Similarly, an SRS symbol is outside the SRS occasion if it is the first symbol in the SRS occasion or its guard period is the eighth symbol of the slot. If an SRS symbol is the last symbol in an SRS occasion, its guard period falls into at least the first symbol of an adjacent slot, and UL transmissions using this slot are affected. Alternatively or additionally, if there is partial or complete overlap between an SRS symbol or its guard period and a DL slot, DL reception is affected. The SRS TA can be determined to advance or delay SRS transmission according to Figures 6 and 7. The UE can determine the value of the SRS TA to use based on these rules or by indicating the impact on UL transmission and / or DL reception to the network, and the network responds with an indication of the particular SRS TA to use. As described herein above in sequence diagram 1100, the UE can be configured with and select from a set of candidate SRS TAs, or can further receive an indication from the network of the SRS TA to use from this candidate set.Alternatively, the UE may pre-store one or more SRS TA values and select the associated SRS TA to use based on a rule.

[0116] The operational flow / algorithm structure 1200 may further include transmitting SRS symbols based on the SRS TA, at 1208. For example, the timing of transmitting the SRS symbols may be advanced or delayed depending on the determination.

[0117] 13 illustrates another example of an operational flow / algorithm structure for timing SRS transmissions based on SRS TA, according to some embodiments. A base station can implement the operational flow / algorithm structure 1300 to avoid or reduce impacts on DL reception and / or UL transmissions when the impacts are due to UE capability for SRS Tx antenna port switching. The operational flow / algorithm structure 1300 may be executed or implemented by a base station, such as, for example, gNB 138, a base station of network 820, or gNB 1600, or a component thereof, such as, for example, processor 1604. The base station may be communicatively coupled to the UE via one or more uplink CCs and one or more DL CCs.

[0118] The operational flow / algorithm structure 1300 may include, at 1302, receiving UE capability information from a UE indicating that the UE supports the ability to apply SRA to SRS transmissions. This capability may be indicated as related to UE capability for SRS Tx antenna port switching.

[0119] The operational flow / algorithm structure 1300 may include, at 1304, transmitting, to the UE, first information configuring an SRS TA for the UE. The SRS TA is applicable to transmission from the UE of SRS symbols in the slot based on the total number of SRS symbols in the slot, the symbol numbers of the SRS symbols in the slot, the timing of guard periods of SRS symbols in the slot or in adjacent slots, or overlap of guard periods with DL reception. In one example, the first information is transmitted via RRC signaling to configure a set of candidate SRS TAs for the UE and to indicate the length, applicable SRS resources, applicable SRS resource sets, applicable CCs, applicable serving cells, applicable SCSs, etc. of each of these candidate SRS TAs.

[0120] The operational flow / algorithm structure 1300 may include, at 1306, transmitting second information to the UE scheduling transmission of SRS symbols. In an example, the second information includes SRS scheduling information. This information indicates a set of symbols / slots / occasions for SRS transmission by the UE and may be transmitted via RRC signaling, MAC CE, and / or DCI.

[0121] The operational flow / algorithm structure 1300 may include, at 1308, receiving SRS symbols from the UE based on the SRS TA and the second information. In one example, the UE advances or delays transmission of SRS symbols according to the SRS TA, whereby the base station receives the advanced or delayed SRS symbols. The UE may select an SRS TA from a set of candidate TAs based on rules stored in the UE. Additionally or alternatively, the UE may transmit information about the impact on UL transmission and / or DL reception, and the base station may transmit an indication of a particular SRS TA from the candidate set to use.

[0122] 14 illustrates a receiving component 1400 of a UE 104, according to some embodiments. The receiving component 1400 may include an antenna panel 1404 including several antenna elements. While the panel 1404 is shown with four antenna elements, other embodiments may include other numbers.

[0123] The antenna panel 1404 may be coupled to analog beamforming (BF) components, including several phase shifters 1408(1)-1408(4). The phase shifters 1408(1)-1408(4) may be coupled to a radio frequency (RF) chain 1412. The RF chain 1412 may amplify the received analog RF signals, downconvert the RF signals to baseband, and convert the analog baseband signals to digital baseband signals that can be provided to a baseband processor for further processing.

[0124] In various embodiments, control circuitry, which may be present in the baseband processor, may provide BF weights (e.g., W1 through W4), which may represent phase shift values, to the phase shifters 1408(1) through 1408(4) to provide receive beams at the antenna panel 1404. These BF weights may be determined based on channel-based beamforming.

[0125] 15 illustrates a UE 1500 according to some embodiments. The UE 1500 may be similar to and substantially interchangeable with the UE 154 of FIG.

[0126] Similar to that described above with respect to UE 154, UE 1500 may be any mobile or non-mobile computing device, such as, for example, a mobile phone, a computer, a tablet, an industrial wireless sensor (e.g., a microphone, a carbon dioxide sensor, a pressure sensor, a humidity sensor, a thermometer, a motion sensor, an accelerometer, a laser scanner, a fluid level sensor, an inventory sensor, a voltage / current meter, or an actuator, etc.), a video surveillance / monitoring device (e.g., a camera or video camera, etc.), a wearable device, or a relaxed-IoT device. In some embodiments, the UE may be a reduced-capacity UE or an NR-Light UE.

[0127] The UE 1500 may include a processor 1504, an RF interface circuit 1508, memory / storage 1512, a user interface 1516, sensors 1520, a driver circuit 1522, a power management integrated circuit (PMIC) 1524, and a battery 1528. The components of the UE 1500 may be implemented as an integrated circuit (IC), portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or combinations thereof. The block diagram of FIG. 15 is intended to illustrate a high-level view of some of the components of the UE 1500. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other embodiments.

[0128] The components of the UE 1500 may be coupled to various other components via one or more interconnects 1532, which may represent any type of interface, input / output, bus (local, system, or expansion), transmission line, trace, optical connection, etc. that may allow various circuit components (on a common or different chips or chipsets) to interact with one another.

[0129] The processor 1504 may include processor circuits such as, for example, a baseband processor circuit (BB) 1504A, a central processing unit circuit (CPU) 1504B, and a graphics processing unit circuit (GPU) 1504C. The processor 1504 may include any type of circuit or processor circuitry that executes or otherwise operates computer-executable instructions, such as program code, software modules, or functional processes from memory / storage 1512 to cause the UE 1500 to perform the operations described herein.

[0130] In some embodiments, the baseband processor circuit 1504A may access a communications protocol stack 1536 in the memory / storage 1512 to communicate over a 3GPP-compliant network. Generally, the baseband processor circuit 1504A may access the communications protocol stack to perform user plane functions at the PHY, MAC, RLC, PDCP, SDAP, and PDU layers, and control plane functions at the PHY, MAC, RLC, PDCP, RRC, and non-access "NAS" layers. In some embodiments, PHY layer operations may additionally / alternatively be performed by components of the RF interface circuit 1508.

[0131] The baseband processor circuit 1504A can generate or process baseband signals or waveforms that carry information in a 3GPP-compliant network. In some embodiments, waveforms for NR can be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.

[0132] The baseband processor circuit 1504A may also access group information 1524 from the memory / storage 1512 to determine search space groups in which several iterations of the PDCCH may be transmitted.

[0133] The memory / storage 1512 may include any type of volatile or non-volatile memory that may be distributed throughout the UE 1500. In some embodiments, some of the memory / storage 1512 may be located within the processor 1504 itself (e.g., L1 and L2 cache), while other memory / storage 1512 is external to the processor 1504 but accessible via a memory interface. The memory / storage 1512 may include any suitable volatile or non-volatile memory, such as, without limitation, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0134] The RF interface circuitry 1508 may include transceiver circuitry and a radio frequency front end module (RFEM) that enable the UE 1500 to communicate with other devices over a radio access network. The RF interface circuitry 1508 may include various elements disposed in the transmit or receive paths. These elements may include, for example, switches, mixers, amplifiers, filters, combiner circuits, control circuits, etc.

[0135] In the receive path, the RFEM may receive radiated signals from the air interface via antenna 1524, filter and amplify the signals (using a low noise amplifier), and provide the signals to a transceiver receiver that downconverts the RF signals to baseband signals that are provided to a baseband processor in processor 1504.

[0136] In the transmit path, the transmitter of the transceiver upconverts the baseband signal received from the baseband processor and provides an RF signal to the RFEM, which may amplify the RF signal with a power amplifier before radiating the signal over the air interface via the antenna 1524.

[0137] In various embodiments, the RF interface circuitry 1508 may be configured to transmit and receive signals in a manner compliant with an NR access technology.

[0138] The antenna 1524 may include several antenna elements that convert electrical signals into radio waves to travel through the air and each converts received radio waves back into electrical signals. The antenna elements may be arranged in one or more antenna panels. The antenna 1524 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple-input, multiple-output communications. The antenna 1524 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. The antenna 1524 may have one or more panels designed for a specific frequency band, including the FR1 or FR2 bands.

[0139] User interface circuitry 1516 includes various input / output (I / O) devices designed to enable user interaction with UE 1500. User interface 1516 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting input, including, among others, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual means for displaying or otherwise communicating information, such as sensor readings, actuator position(s), or other similar information. The output device circuitry may include any number or combination of audio or visual displays, including, among other things, one or more simple visual outputs / indicators (e.g., binary status indicators such as light emitting diodes "LEDs" and multi-character visual outputs), or more complex outputs such as display devices or touch screens (e.g., liquid crystal displays "LCDs," LED displays, quantum dot displays, projectors, etc.), and output such as text, graphics, multimedia objects, etc. generated or created from operation of the UE 1500.

[0140] Sensors 1520 may include devices, modules, or subsystems intended to detect events or changes in the environment and transmit information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others, inertial measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems or nanoelectromechanical systems including 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless apertures); light detection and ranging sensors; proximity sensors (e.g., infrared detectors, etc.); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other similar audio capture devices; etc.

[0141] The driver circuit 1522 may include software and hardware elements that operate to control particular devices embedded in, attached to, or otherwise communicatively coupled to the UE 1500. The driver circuit 1522 may include individual drivers that enable other components to interact with or control various input / output (I / O) devices that may be present within or connected to the UE 1500. For example, the driver circuit 1522 may include a display driver for controlling and allowing access to a display device, a touchscreen driver for controlling and allowing access to a touchscreen interface, a sensor driver for obtaining sensor readings of the sensor circuit 1520 and controlling and allowing access to the sensor circuit 1520, a driver for obtaining actuator positions of or controlling and allowing access to electromechanical components, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0142] The PMIC 1524 may manage the power provided to various components of the UE 1500. In particular, with respect to the processor 1504, the PMIC 1524 may control power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0143] In some embodiments, the PMIC 1524 may control or otherwise be a part of various power-saving mechanisms of the UE 1500. For example, if the platform UE is in an RRC connected state and still connected to a RAN node because it expects to receive traffic soon, after a period of inactivity, the platform may enter a state known as discontinuous reception mode (DRX). While in this state, the UE 1500 may power down for short intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the UE 1500 may transition to an RRC_Idle state, in which it disconnects from the network and does not perform operations such as channel quality feedback or handover. The UE 1500 enters a very low power state, performs paging, wakes up periodically to listen to the network, and then powers down again. The UE 1500 cannot receive data in this state and must transition back to the original RRC_Connected state to receive data. In further power-saving modes, the device may be allowed to be unavailable to the network for periods longer than the paging interval (which can range from a few seconds to several hours). During this time, the device may not be able to reach the network at all and may be completely powered down. Any data sent during this time will be significantly delayed, but the delay is deemed acceptable.

[0144] The battery 1528 may provide power to the UE 1500, although in some examples the UE 1500 may be mounted and deployed in a fixed location or may have a power source coupled to a power grid. The battery 1528 may be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some implementations, such as in vehicle-based applications, the battery 1528 may be a typical automotive lead-acid battery.

[0145] 16 illustrates a gNB 1600 according to some embodiments. The gNB node 1600 may be similar to and substantially interchangeable with the gNB 148. A base station, such as the base station 162, may have the same or similar components as the gNB 1600.

[0146] The gNB 1600 may include a processor 1604, an RF interface circuit 1608, a core network (CN) interface circuit 1612, and a memory / storage circuit 1616.

[0147] The components of the gNB 1600 may be coupled to various other components via one or more interconnects 1628.

[0148] The processor 1604, RF interface circuitry 1608, memory / storage circuitry 1616 (including communication protocol stack 1610), antenna 1624, and interconnect 1628 may be similar to the like-named elements shown and described with respect to FIG.

[0149] The CN interface circuit 1612 may provide connectivity to a core network, e.g., a fifth-generation core network "5GC," using a 5GC-compliant network interface protocol, such as the Carrier Ethernet protocol or some other suitable protocol. Network connectivity may be provided to or from the gNB 1600 via optical fiber or wireless backhaul. The CN interface circuit 1612 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 1612 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0150] It is understood that use of personally identifiable information should comply with generally recognized privacy policies and practices that meet or exceed industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of authorized uses should be clearly indicated to users.

[0151] For one or more embodiments, at least one of the components depicted in one or more of the foregoing figures may be configured to perform one or more of the operations, techniques, processes, or methods as described in the example section below. For example, the baseband circuitry described above in connection with one or more of the foregoing figures may be configured to operate according to one or more of the examples described below. As another example, circuitry associated with a UE, a base station, a network element, etc., as described above in connection with one or more of the foregoing figures, may be configured to operate according to one or more of the examples described below in the example section. Example

[0152] Further exemplary embodiments are provided in the following sections.

[0153] Example 1 includes a method, implemented on a user equipment, that includes receiving downlink scheduling information from a network, receiving Sounding Reference Signal (SRS) scheduling information from the network for scheduling SRS transmissions, determining an overlap between the scheduled downlink reception and (i) the SRS transmission or (ii) a guard period associated with the SRS transmission based on the downlink scheduling information, and modifying the SRS transmission or receiving an indication of the modification to the downlink reception from the network based on the overlap.

[0154] Example 2 includes the method of Example 1, in which downlink reception is in a first slot, and SRS transmission is in a second slot that is scheduled based on the UE having SRS transmit antenna port switching capability and at least partially overlaps with the first slot.

[0155] Example 3 includes the method of Example 1 or 2, wherein the downlink reception is in a first slot, and the SRS transmission is scheduled based on the UE having SRS transmit antenna port switching capability and is in a second slot that does not overlap with the first slot, the overlap comprising a guard period that extends at least partially into the first slot.

[0156] Example 4 includes the method of any one of Examples 1 to 3, wherein the downlink reception and the SRS transmission are scheduled in different slots, the overlap is between the downlink reception and the guard period and has an overlap time length, and the overlap is determined based on the overlap time length being equal to or greater than a predefined threshold time.

[0157] Example 5 includes the method of any one of Examples 1 to 4, wherein downlink reception and SRS transmission are scheduled in different slots, with an overlap between downlink reception and a guard period, and the guard period is signaled to the network.

[0158] Example 6 includes the method of any one of Examples 1 to 5, wherein the downlink scheduling information schedules a set of downlink symbols, a set of downlink slots, or a set of downlink occasions; the downlink reception comprises high priority downlink data, a reference signal for Layer 1 or Layer 3 measurements, or system information; the SRS transmission comprises SRS symbols; and the overlap includes full or partial overlap of the SRS symbols with the downlink reception or full or partial overlap of the guard period with the downlink reception.

[0159] Example 7 includes the method of any one of Examples 1 to 6, wherein the downlink reception and the SRS transmission are scheduled in different slots, the overlap is between the downlink reception and the guard period, and has an overlap time length, and the method further includes indicating the overlap time length to the network and receiving an indication from the network about the change to the SRS transmission or the change to the downlink reception.

[0160] Example 8 includes the method of any one of Examples 1 to 7, wherein modifying the SRS transmission includes suspending the SRS transmission without an indication from the UE to the network about the overlap.

[0161] Example 9 includes the method of any one of Examples 1 to 8, further including indicating the overlap to the network and receiving an indication from the network about a change in SRS transmission, where the change includes rescheduling the SRS transmission or suspending the SRS transmission.

[0162] Example 10 includes the method of any one of Examples 1 to 9, further including indicating the overlap to a network and receiving an indication from the network about rescheduling of downlink reception or interruption of downlink reception.

[0163] Example 11 is the method according to any one of Examples 1 to 10, further comprising transmitting, to the network, UE capability information indicating that the UE lacks the capability to apply SRS timing advance (TA) to SRS transmission.

[0164] Example 12 includes a method, implemented by a base station, that includes transmitting downlink scheduling information to a user equipment (UE), transmitting sounding reference signal (SRS) scheduling information to the UE to schedule SRS transmissions, receiving a first indication of an overlap from the UE, where the overlap is between a downlink reception scheduled based on the downlink scheduling information and (i) the SRS transmission or (ii) a guard period associated with the SRS transmission, and transmitting a second indication of a change to at least one of the SRS transmission or the downlink reception to the UE based on the first indication.

[0165] Example 13 includes the method of example 12, wherein the second indication indicates rescheduling of the SRS transmission or suspension of the SRS transmission.

[0166] Example 14 includes the method according to any one of Examples 12 to 13, wherein the second indication indicates rescheduling of downlink reception or suspension of downlink reception.

[0167] Example 15 includes the method of any one of Examples 12 to 14, further including receiving UE capability information from the UE indicating that the UE lacks the capability to apply SRS timing advance (TA) to SRS transmission, and the second indication is sent to the UE based on the UE capability information.

[0168] Example 16 includes a method, implemented by a user equipment (UE), that includes: receiving, from a network, information scheduling transmission of Sounding Reference Signal (SRS) symbols in a slot; determining an SRS timing advance (TA) applicable to the transmission of the SRS symbols based on a total number of SRS symbols in the slot, symbol numbers of the SRS symbols in the slot, timing of guard periods of SRS symbols in the slot or adjacent slots, or overlap of guard periods with downlink reception; and transmitting the SRS symbols based on the SRS TA.

[0169] Example 17 includes the method of example 16, in which the SRS TA is not applied to transmission of non-SRS symbols in the slot.

[0170] Example 18 includes the method according to any one of Examples 16 to 17, wherein the SRS TA is not applied to transmission of other SRS symbols in adjacent slots.

[0171] Example 19 includes the method according to any one of Examples 16 to 18, wherein the SRS TA is applicable to transmitting the SRS symbol based on the total number of SRS symbols in a slot exceeding a threshold number.

[0172] Example 20 includes the method according to any one of Examples 16 to 19, in which the SRS TA is applicable to transmitting an SRS symbol based on a symbol number indicating that the SRS symbol is the first symbol or the last symbol of an SRS occasion within a slot.

[0173] Example 21 includes the method according to any one of Examples 16 to 20, wherein the SRS TA is applicable to transmitting an SRS symbol based on guard period timing indicating that the guard period is outside the SRS occasion in the slot.

[0174] Example 22 includes the method according to any one of Examples 16 to 21, wherein downlink reception and transmission of SRS symbols are scheduled in different slots, and the SRS TA is applicable to transmission of SRS symbols based on an overlap between downlink reception and a guard period, or between a guard period and an uplink transmission using another slot.

[0175] Example 23 includes the method according to any one of Examples 16 to 22, wherein the SRS TA has a value equal to the product of the symbol length and a multiplier, and the symbol length is based on the SRS subcarrier spacing (SCS), the physical uplink control channel (PUCCH) SCS, or the physical uplink shared channel (PUSCH) SCS.

[0176] Example 24 includes the method according to any one of Examples 16 to 23, further including: determining that the total number of SRS symbols in the slot exceeds a threshold number; and advancing the transmission of SRS symbols by the value of SRS TA.

[0177] Example 25 includes the method of any one of Examples 16 to 24, further including determining whether the SRS symbol is either the first symbol or the last symbol of an SRS occasion in a slot, and advancing transmission of the SRS symbol by the value of the SRS TA if the SRS symbol is the last symbol, or delaying transmission of the SRS symbol by the value of the SRS TA if the SRS symbol is the first symbol.

[0178] Example 26 includes the method according to any one of Examples 16 to 25, further including determining that the guard period of the SRS symbol is either the eighth symbol of the slot or the first symbol of an adjacent slot, and advancing the transmission of the SRS symbol by the value of the SRS TA if the guard period is the first symbol of the adjacent slot, or delaying the transmission of the SRS symbol by the value of the SRS TA if the guard period is the eighth symbol of the slot.

[0179] Example 27 includes the method of any one of Examples 16 to 26, where downlink reception and transmission of the SRS symbols are scheduled in different slots, and the method further includes determining whether transmission of the SRS symbols is either before or after downlink reception, and advancing transmission of the SRS symbols by the value of the SRS TA if transmission of the SRS symbols is before downlink reception, or delaying transmission of the SRS symbols by the value of the SRS TA if transmission of the SRS symbols is after downlink reception.

[0180] Example 28 includes the method according to any one of Examples 16 to 27, further including: sending, to the network, UE capability information indicating that the UE supports the capability of applying timing advance to SRS transmission.

[0181] Example 29 includes the method according to any one of Examples 16 to 28, wherein the value of the SRS TA is stored in a memory of the UE before transmitting the UE capability information, and the value is predefined per SRS resource, per SRS resource set, per UE, per component carrier, per serving cell, or per subcarrier spacing.

[0182] Example 30 includes a method, implemented by a base station, including: transmitting, to a user equipment (UE), first information configuring a sounding reference signal (SRS) timing advance (TA) for the UE, the SRS TA being applicable to a transmission from the UE of an SRS symbol in the slot based on a total number of SRS symbols in the slot, symbol numbers of the SRS symbols in the slot, timing of guard periods of SRS symbols in the slot or in adjacent slots, or overlap of guard periods with downlink reception; transmitting, to the UE, second information scheduling transmission of the SRS symbols; and receiving, from the UE, the SRS symbols based on the SRS TA and the second information.

[0183] Example 31 includes the method of example 30, wherein the first information comprises a set of candidate SRS TAs, and the method further includes determining a total number of SRS symbols in a slot, a symbol number of an SRS symbol in a slot, a timing of a guard period of an SRS symbol, or an overlap of a guard period with downlink reception, and transmitting third information to the UE indicating an SRS TA from the set of candidate SRS TAs.

[0184] Example 32 includes the method of Example 31, in which the first information is transmitted in a radio resource control (RRC) configuration, a first medium access control (MAC) control element (CE), or a first downlink control information (DCI), and the third information is transmitted in a second MAC CE or a second DCI.

[0185] Example 33 includes the method of any one of Examples 30 to 32, further including receiving UE capability information from the UE indicating that the UE supports the ability to apply timing advance to SRS transmission, and the first information is transmitted based on the UE capability information.

[0186] Example 34 includes a UE including means for performing one or more elements of the method described or related to any one of Examples 1-11 and 16-28.

[0187] Example 35 includes one or more computer-readable media storing instructions that, when executed by a UE, cause the UE to perform operations of a method described in or related to any one of Examples 1 to 11 and 16 to 28.

[0188] Example 36 includes a UE including logic, modules, or circuitry for performing one or more elements of the method described or related to any one of Examples 1-11 and 16-28.

[0189] Example 37 includes a UE having one or more processors and one or more computer-readable media containing instructions that, when executed by the one or more processors, configure the UE to perform any one of Examples 1-11 and 16-28.

[0190] Example 38 includes a base station including means for performing one or more elements of the method described or related to any one of Examples 12-15 and 30-33.

[0191] Example 39 includes one or more computer-readable media storing instructions that, when executed by a base station, cause the base station to perform operations of a method described in or related to any one of Examples 12 to 15 and 30 to 33.

[0192] Example 40 includes a base station including logic, modules, or circuitry for performing one or more elements of the method described or related to any one of Examples 12-15 and 30-33.

[0193] Example 41 includes a base station comprising one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, configure the base station to perform any one of Examples 12-15 and 30-33.

[0194] Any of the above examples can be combined with any other example (or combination of examples) unless otherwise stated. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0195] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated, and it is intended that the following claims be interpreted to embrace all such variations and modifications.

Claims

1. 1. A method comprising: Informing a network of a user equipment (UE) capability to support sounding reference signal (SRS) antenna port switching and the impact of using the SRS antenna port switching on downlink reception; receiving data scheduling information from the network; receiving SRS scheduling information from the network for scheduling SRS transmissions; performing the SRS transmission using the SRS antenna port switching based on the effect and a determination that no collision exists between data communication and the SRS transmission, wherein the data communication is scheduled based on the data scheduling information; and A method comprising:

2. 10. The method of claim 1, wherein the data communication includes at least one of a synchronization signal physical broadcast channel block (SSB) signal or a channel state information reference signal (CSI-RS).

3. 3. The method of claim 1, wherein the data communication is in a first slot and the SRS transmission is in a second slot that is scheduled based on the capability of SRS antenna port switching and does not overlap with the first slot.

4. The method of any one of claims 1 to 3, further comprising determining whether the collision exists by determining whether the data communication overlaps with a guard period associated with the SRS transmission.

5. 5. The method of claim 1, further comprising transmitting UE capability information to the network indicating that the UE lacks the capability to apply SRS Timing Advance (TA) to the SRS transmission.

6. 5. The method of claim 1, further comprising: transmitting UE capability information to the network indicating that the UE supports applying SRS Timing Advance (TA) to SRS transmissions.

7. The method of any one of claims 1 to 6, further comprising indicating to the network whether the collision exists.

8. 8. The method of claim 1, wherein the data scheduling information schedules a set of downlink symbols, a set of downlink slots, or a set of downlink occasions, and the data communication comprises high priority downlink data, reference signals for Layer 1 or Layer 3 measurements, or system information.

9. 1. An apparatus comprising: one or more processors; one or more memories that store computer readable instructions; the computer-readable instructions, when executed by the one or more processors, cause the one or more processors to: Informing a network of a user equipment (UE) capability to support sounding reference signal (SRS) antenna port switching and the impact of using the SRS antenna port switching on downlink reception; receiving data scheduling information from the network; receiving SRS scheduling information from the network for scheduling SRS transmissions; performing the SRS transmission using the SRS antenna port switching based on the effect and a determination that no collision exists between data communication and the SRS transmission, wherein the data communication is scheduled based on the data scheduling information; and An apparatus configured to perform the above.

10. The execution of the computer readable instructions further causes the one or more processors to:

10. The apparatus of claim 9, configured to indicate to the network whether the UE supports applying SRS Timing Advance (TA) to the SRS transmission.

11. 11. The apparatus of claim 10, wherein the indicating whether the UE supports applying the SRS TA is based on the capability of the UE to support SRS antenna port switching.

12. 12. The apparatus of claim 10, wherein the SRS TA is applicable to transmission of an SRS symbol based on at least one of: a total number of SRS symbols in a slot exceeds a threshold number; a symbol number indicates that the SRS symbol is the first or last symbol of an SRS occasion in the slot; or a guard period indicates that the SRS symbol is outside the SRS occasion.

13. The apparatus of any one of claims 10 to 12, wherein the data communication and transmission of SRS symbols are scheduled in different slots, and the SRS TA is not applicable to the transmission of the SRS symbols.

14. 14. The apparatus of claim 10, wherein the SRS TA has a value equal to a product of a symbol length and a multiplier, and the symbol length is based on an SRS subcarrier spacing (SCS), a physical uplink control channel (PUCCH) SCS, or a physical uplink shared channel (PUSCH) SCS.

15. The execution of the computer readable instructions further causes the one or more processors to: determining that a total number of SRS symbols in a slot exceeds a threshold number; advancing the transmission of the SRS symbol by the value of the SRS TA; The apparatus according to any one of claims 10 to 14, configured to:

16. The execution of the computer readable instructions further causes the one or more processors to: determining that the SRS symbol is either the first symbol or the last symbol of an SRS occasion in a slot; If the SRS symbol is the last symbol, advance the transmission of the SRS symbol by the value of the SRS TA; or If the SRS symbol is the first symbol, delaying the transmission of the SRS symbol by the value of the SRS TA; The apparatus according to any one of claims 10 to 14, configured to:

17. The execution of the computer readable instructions further causes the one or more processors to: determining that the guard period of the SRS symbol is either the eighth symbol of the slot or the first symbol of an adjacent slot; If the guard period is the first symbol of the adjacent slot, then advance the transmission of the SRS symbol by the value of the SRS TA; or if the guard period is the eighth symbol of the slot, delaying the transmission of the SRS symbol by the value of the SRS TA; The apparatus according to any one of claims 10 to 14, configured to:

18. The data communication and transmission of SRS symbols are scheduled within different slots, and the execution of the computer-readable instructions further causes the one or more processors to: determining whether the transmission of the SRS symbol is before or after the data communication; if the transmission of the SRS symbol is before the data communication, advance the transmission of the SRS symbol by the value of the SRS TA; or delaying the transmission of the SRS symbol by the value of the SRS TA if the transmission of the SRS symbol is after the data communication; The apparatus according to any one of claims 10 to 14, configured to:

19. One or more computer-readable storage media storing instructions that, when executed on one or more processors, cause the one or more processors to: Informing a network of a user equipment (UE) capability to support sounding reference signal (SRS) antenna port switching and the impact of using the SRS antenna port switching on downlink reception; receiving data scheduling information from the network; receiving SRS scheduling information from the network for scheduling SRS transmissions; performing the SRS transmission using the SRS antenna port switching based on the effect and a determination that no collision exists between data communication and the SRS transmission, wherein the data communication is scheduled based on the data scheduling information; and One or more computer-readable storage media for causing operations to be performed, including:

20. The operation further comprises:

20. The one or more computer-readable storage media of claim 19, comprising transmitting UE capability information to the network indicating that the UE supports the ability to apply timing advance to SRS transmissions.

Images