Indication of slot offset for sounding reference signal via trigger value

Abstract

In one aspect, a base station (BS) transmits a downlink control information (DCI) communication to a user equipment (UE), the DCI communication configured to trigger transmission of an aperiodic (AP) sounding reference signal (SRS). The UE determines, based at least in part on a DCI codepoint (i.e., an AP SRS resource trigger value) of the DCI communication, a slot offset from the DCI communication to a set of SRS resources for the AP SRS. The UE transmits the AP SRS on the set of SRS resources in accordance with the determined slot offset.

Description

[0001] Cross-reference to related applications

[0002] This patent application claims the benefit of Greek application No. 20200100542, filed on September 7, 2020, entitled “INDICATION OF SLOTOFFSET FOR A SOUNDING REFERENCE SIGNAL VIA TRIGGER VALUE”, which has been assigned to the assignee of this application and whose entire contents are expressly incorporated herein by reference. Technical Field

[0003] In summary, various aspects of this disclosure relate to the indication of slot offsets for the probe reference signal (SRS) via trigger values. Background Technology

[0004] Wireless communication systems have evolved through several generations, including first-generation analog radiotelephone service (1G), second-generation (2G) digital radiotelephone service (including temporary 2.5G networks), third-generation (3G) high-speed data, wireless services supporting the Internet, and fourth-generation (4G) services (e.g., LTE or WiMax). Currently, many different types of wireless communication systems exist in use, including cellular and Personal Communication Services (PCS) systems. Known examples of cellular systems include the Cellular Analog Improved Mobile Phone System (AMPS), and digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), and TDMA-based Global System for Mobile Access (GSM) variants.

[0005] The fifth-generation (5G) wireless standard (known as New Radio (NR)) achieves higher data transmission speeds, a greater number of connections, better coverage, and other improvements. According to the Next Generation Mobile Networks Alliance, the 5G standard is designed to provide tens of megabits per second of data to each of tens of thousands of users, with 1 gigabit per second provided to dozens of employees on an office floor. To support large-scale wireless deployments, it should support hundreds of thousands of simultaneous connections. Therefore, the spectral efficiency of 5G mobile communications should be significantly enhanced compared to the current 4G standard. Furthermore, signaling efficiency should be improved, and latency should be significantly reduced compared to existing standards. Summary of the Invention

[0006] The following is a brief overview relating to one or more aspects disclosed herein. Therefore, this overview should not be considered a general overview relating to all anticipated aspects, nor should it be considered as identifying key or important elements relating to all anticipated aspects, nor as depicting the scope associated with any particular aspect. Thus, the following overview has the sole purpose of providing, in a simplified form, certain concepts relating to one or more aspects related to the mechanisms disclosed herein, as a prelude to the detailed description that follows.

[0007] In one aspect, a method of operating a user equipment (UE) includes: receiving downlink control information (DCI) communication, the DCI communication being configured to trigger the transmission of an aperiodic (AP) sounding reference signal (SRS); determining a slot offset from the DCI communication to a set of SRS resources for the AP SRS based at least in part on the DCI code points of the DCI communication; and transmitting the AP SRS on the set of SRS resources according to the determined slot offset.

[0008] In some aspects, the method includes: receiving a configuration for an SRS resource set, the configuration including a mapping between a set of DCI code points for DCI communication and a set of time slot offsets for a time slot offset list, wherein the determination is based on the mapping.

[0009] In some respects, this configuration is received via Radio Resource Control (RRC) signaling.

[0010] In some aspects, the slot offset list supplements the slot offset field associated with the default slot offset in this configuration, or the slot offset list incorporates the slot offset field associated with the default slot offset.

[0011] In some aspects, the method includes receiving a command for modifying the configuration.

[0012] In some aspects, the command is used to instruct the UE to add one or more entries to the slot offset list or remove one or more entries from the slot offset list, or the command is used to instruct the UE to add at least one entry to the set of DCI code points or remove at least one entry from the set of DCI code points, or wherein the command is used to instruct the UE to modify the mapping between the set of DCI code points and the slot offset list, or a combination thereof.

[0013] In some respects, this command is used to instruct the UE to modify the configuration for a specific bandwidth portion (BWP) of a specific serving cell.

[0014] In some respects, this command corresponds to the Media Access Control Command Element (MAC-CE).

[0015] In some respects, the mapping is a 1:1 mapping between the set of DCI code points and the set of time slot offsets.

[0016] In some aspects, for at least one DCI code point, the mapping is a 1:N mapping that maps the DCI code point to a set of candidate time slot offsets.

[0017] In some aspects, the method includes: determining the availability of one or more candidate time slot offsets in a set of candidate time slot offsets, wherein transmission is performed on the earliest available time slot based on the determination.

[0018] In some respects, availability determination is based on conflict avoidance schemes, transmission prioritization schemes, or combinations thereof.

[0019] In some respects, the set of time slot offsets is smaller than the set of DCI code points.

[0020] In some respects, mapping maps a given time slot offset to multiple DCI code points.

[0021] In some aspects, the mapping maps a first time slot offset to a first DCI code point, and the mapping maps a second offset to a second DCI code point, wherein one or more of the first time slot offset and the second time slot offset are calculated via a function.

[0022] In one aspect, a method of operating a base station includes: sending downlink control information (DCI) communication to a user equipment (UE), the DCI communication being configured to trigger the transmission of an aperiodic (AP) probe reference signal (SRS) based on a slot offset indicated by a DCI code point via the DCI communication; and receiving an APSRS on a set of SRS resources according to the indicated slot offset.

[0023] In some aspects, the method includes: sending a configuration for an SRS resource set, the configuration including a mapping between a set of DCI code points for DCI communication and a set of time slot offsets for a time slot offset list.

[0024] In some respects, this configuration is transmitted via Radio Resource Control (RRC) signaling.

[0025] In some aspects, the slot offset list supplements the slot offset field associated with the default slot offset in this configuration, or the slot offset list incorporates the slot offset field associated with the default slot offset.

[0026] In some aspects, the method includes sending commands to modify the configuration.

[0027] In some aspects, the command is used to instruct the UE to add one or more entries to the slot offset list or remove one or more entries from the slot offset list, or the command is used to instruct the UE to add at least one entry to the set of DCI code points or remove at least one entry from the set of DCI code points, or wherein the command is used to instruct the UE to modify the mapping between the set of DCI code points and the slot offset list, or a combination thereof.

[0028] In some respects, this command is used to instruct the UE to modify the configuration for a specific bandwidth portion (BWP) of a specific serving cell.

[0029] In some respects, this command corresponds to the Media Access Control Command Element (MAC-CE).

[0030] In some respects, the mapping is a 1:1 mapping between the set of DCI code points and the set of time slot offsets.

[0031] In some aspects, for at least one DCI code point, the mapping is a 1:N mapping that maps the DCI code point to a set of candidate time slot offsets.

[0032] In some respects, AP SRS is received on candidate slot offsets from a set of candidate slot offsets.

[0033] In some respects, the set of time slot offsets is smaller than the set of DCI code points.

[0034] In some respects, mapping maps a given time slot offset to multiple DCI code points.

[0035] In some aspects, the mapping maps a first time slot offset to a first DCI code point, wherein the mapping maps a second offset to a second DCI code point, and wherein one or more of the first time slot offset and the second time slot offset are calculated via a function.

[0036] In one aspect, a user equipment (UE) includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive downlink control information (DCI) communication via the at least one transceiver, the DCI communication being configured to trigger the transmission of an aperiodic (AP) sounding reference signal (SRS); determine a slot offset from the DCI communication to a set of SRS resources for the AP SRS based at least in part on the DCI code points of the DCI communication; and transmit the AP SRS on the set of SRS resources via the at least one transceiver according to the determined slot offset.

[0037] In some aspects, at least one processor is further configured to receive, via at least one transceiver, a configuration for an SRS resource set, the configuration including a mapping between a set of DCI code points for DCI communication and a set of time slot offsets for a time slot offset list, wherein the determination is based on the mapping.

[0038] In some respects, this configuration is received via Radio Resource Control (RRC) signaling.

[0039] In some respects, the slot offset list supplements the slot offset field associated with the default slot offset in this configuration, or the slot offset list incorporates the slot offset field associated with the default slot offset.

[0040] In some aspects, at least one processor is also configured to receive commands for modifying the configuration via at least one transceiver.

[0041] In some aspects, the command is used to instruct the UE to add one or more entries to the slot offset list or remove one or more entries from the slot offset list, or the command is used to instruct the UE to add at least one entry to the set of DCI code points or remove at least one entry from the set of DCI code points, or wherein the command is used to instruct the UE to modify the mapping between the set of DCI code points and the slot offset list, or a combination thereof.

[0042] In some respects, this command is used to instruct the UE to modify the configuration for a specific bandwidth portion (BWP) of a specific serving cell.

[0043] In some respects, this command corresponds to the Media Access Control Command Element (MAC-CE).

[0044] In some respects, the mapping is a 1:1 mapping between the set of DCI code points and the set of time slot offsets.

[0045] In some aspects, for at least one DCI code point, the mapping is a 1:N mapping that maps the DCI code point to a set of candidate time slot offsets.

[0046] In some aspects, at least one processor is further configured to: determine the availability of one or more candidate time slot offsets in a set of candidate time slot offsets, wherein transmission is performed on the earliest available time slot based on the determination.

[0047] In some respects, availability determination is based on conflict avoidance schemes, transmission prioritization schemes, or combinations thereof.

[0048] In some respects, the set of time slot offsets is smaller than the set of DCI code points.

[0049] In some respects, mapping maps a given time slot offset to multiple DCI code points.

[0050] In some aspects, the mapping maps a first time slot offset to a first DCI code point, and the mapping maps a second offset to a second DCI code point, wherein one or more of the first time slot offset and the second time slot offset are calculated via a function.

[0051] In one aspect, a base station includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: transmit downlink control information (DCI) communication to a user equipment (UE) via the at least one transceiver, the DCI communication being configured to trigger the transmission of an aperiodic (AP) probe reference signal (SRS) based on a slot offset indicated by a DCI code point via the DCI communication; and receive the AP SRS on an SRS resource set via the at least one transceiver according to the indicated slot offset.

[0052] In some aspects, at least one processor is also configured to transmit, via at least one transceiver, a configuration for an SRS resource set, the configuration including a mapping between a set of DCI code points for DCI communication and a set of time slot offsets for a time slot offset list.

[0053] In some respects, this configuration is transmitted via Radio Resource Control (RRC) signaling.

[0054] In some aspects, the slot offset list supplements the slot offset field associated with the default slot offset in this configuration, or the slot offset list incorporates the slot offset field associated with the default slot offset.

[0055] In some aspects, at least one processor is also configured to send commands for modifying the configuration via at least one transceiver.

[0056] In some aspects, the command is used to instruct the UE to add one or more entries to the slot offset list or remove one or more entries from the slot offset list, or the command is used to instruct the UE to add at least one entry to the set of DCI code points or remove at least one entry from the set of DCI code points, or wherein the command is used to instruct the UE to modify the mapping between the set of DCI code points and the slot offset list, or a combination thereof.

[0057] In some respects, this command is used to instruct the UE to modify the configuration for a specific bandwidth portion (BWP) of a specific serving cell.

[0058] In some respects, this command corresponds to the Media Access Control Command Element (MAC-CE).

[0059] In some respects, the mapping is a 1:1 mapping between the set of DCI code points and the set of time slot offsets.

[0060] In some aspects, for at least one DCI code point, the mapping is a 1:N mapping that maps the DCI code point to a set of candidate time slot offsets.

[0061] In some respects, AP SRS is received on candidate slot offsets from a set of candidate slot offsets.

[0062] In some respects, the set of time slot offsets is smaller than the set of DCI code points.

[0063] In some respects, mapping maps a given time slot offset to multiple DCI code points.

[0064] In some aspects, the mapping maps a first time slot offset to a first DCI code point, wherein the mapping maps a second offset to a second DCI code point, and wherein one or more of the first time slot offset and the second time slot offset are calculated via a function.

[0065] In one aspect, a user equipment (UE) includes: a unit for receiving downlink control information (DCI) communication configured to trigger the transmission of an aperiodic (AP) sounding reference signal (SRS); a unit for determining a slot offset from the DCI communication to a set of SRS resources for the AP SRS, based at least in part on the DCI code points of the DCI communication; and a unit for transmitting the AP SRS on the set of SRS resources according to the determined slot offset.

[0066] In some aspects, the method includes: a unit for receiving a configuration for an SRS resource set, the configuration including a mapping between a set of DCI code points for DCI communication and a set of time slot offsets for a time slot offset list, wherein the determination is based on the mapping.

[0067] In some respects, this configuration is received via Radio Resource Control (RRC) signaling.

[0068] In some aspects, the slot offset list supplements the slot offset field associated with the default slot offset in this configuration, or the slot offset list incorporates the slot offset field associated with the default slot offset.

[0069] In some aspects, the method includes a unit for receiving a command for modifying the configuration.

[0070] In some aspects, the command is used to instruct the UE to add one or more entries to the slot offset list or remove one or more entries from the slot offset list, or the command is used to instruct the UE to add at least one entry to the set of DCI code points or remove at least one entry from the set of DCI code points, or wherein the command is used to instruct the UE to modify the mapping between the set of DCI code points and the slot offset list, or a combination thereof.

[0071] In some respects, this command is used to instruct the UE to modify the configuration for a specific bandwidth portion (BWP) of a specific serving cell.

[0072] In some respects, this command corresponds to the Media Access Control Command Element (MAC-CE).

[0073] In some respects, this mapping is a 1:1 mapping between the set of DCI code points and the set of time slot offsets.

[0074] In some aspects, for at least one DCI code point, the mapping is a 1:N mapping that maps the DCI code point to a set of candidate time slot offsets.

[0075] In some aspects, the method includes: a unit for determining the availability of one or more candidate time slot offsets in a set of candidate time slot offsets, wherein transmission is performed on the earliest available time slot based on the determination.

[0076] In some respects, availability determination is based on conflict avoidance schemes, transmission prioritization schemes, or combinations thereof.

[0077] In some respects, the set of time slot offsets is smaller than the set of DCI code points.

[0078] In some respects, mapping maps a given time slot offset to multiple DCI code points.

[0079] In some aspects, the mapping maps a first time slot offset to a first DCI code point, and the mapping maps a second offset to a second DCI code point, wherein one or more of the first time slot offset and the second time slot offset are calculated via a function.

[0080] In one aspect, a base station includes: a unit for transmitting downlink control information (DCI) communication to a user equipment (UE), the DCI communication being configured to trigger the transmission of an aperiodic (AP) probe reference signal (SRS) based on a slot offset indicated by a DCI code point via the DCI communication; and a unit for receiving the AP SRS on an SRS resource set according to the indicated slot offset.

[0081] In some aspects, the method includes: a unit for transmitting a configuration for an SRS resource set, the configuration including a mapping between a set of DCI code points for DCI communication and a set of time slot offsets for a time slot offset list.

[0082] In some respects, this configuration is transmitted via Radio Resource Control (RRC) signaling.

[0083] In some respects, the slot offset list supplements the slot offset field associated with the default slot offset in this configuration, or the slot offset list incorporates the slot offset field associated with the default slot offset.

[0084] In some aspects, the method includes: a unit for sending commands to modify the configuration.

[0085] In some aspects, the command is used to instruct the UE to add one or more entries to the slot offset list or remove one or more entries from the slot offset list, or the command is used to instruct the UE to add at least one entry to the set of DCI code points or remove at least one entry from the set of DCI code points, or wherein the command is used to instruct the UE to modify the mapping between the set of DCI code points and the slot offset list, or a combination thereof.

[0086] In some respects, this command is used to instruct the UE to modify the configuration for a specific bandwidth portion (BWP) of a specific serving cell.

[0087] In some respects, this command corresponds to the Media Access Control Command Element (MAC-CE).

[0088] In some respects, the mapping is a 1:1 mapping between the set of DCI code points and the set of gap offsets.

[0089] In some aspects, for at least one DCI code point, the mapping is a 1:N mapping that maps the DCI code point to a set of candidate time slot offsets.

[0090] In some respects, AP SRS is received on candidate slot offsets from a set of candidate slot offsets.

[0091] In some respects, the set of time slot offsets is smaller than the set of DCI code points.

[0092] In some respects, mapping maps a given time slot offset to multiple DCI code points.

[0093] In some aspects, the mapping maps a first time slot offset to a first DCI code point, wherein the mapping maps a second offset to a second DCI code point, and wherein one or more of the first time slot offset and the second time slot offset are calculated via a function.

[0094] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a user equipment (UE), cause the UE to: receive downlink control information (DCI) communications configured to trigger the transmission of an aperiodic (AP) sounding reference signal (SRS); determine, at least in part, a slot offset from the DCI communications to a set of SRS resources for the AP SRS based on the DCI code points of the DCI communications; and transmit the AP SRS on the set of SRS resources according to the determined slot offset.

[0095] In some aspects, one or more instructions also cause the UE to: receive a configuration for an SRS resource set, the configuration including a mapping between a set of DCI code points for DCI communication and a set of time slot offsets in a time slot offset list, wherein the determination is based on the mapping.

[0096] In some respects, this configuration is received via Radio Resource Control (RRC) signaling.

[0097] In some aspects, the slot offset list supplements the slot offset field associated with the default slot offset in this configuration, or the slot offset list incorporates the slot offset field associated with the default slot offset.

[0098] In some respects, one or more instructions also cause the UE to receive a command to modify the configuration.

[0099] In some aspects, the command is used to instruct the UE to add one or more entries to the slot offset list or remove one or more entries from the slot offset list, or the command is used to instruct the UE to add at least one entry to the set of DCI code points or remove at least one entry from the set of DCI code points, or wherein the command is used to instruct the UE to modify the mapping between the set of DCI code points and the slot offset list, or a combination thereof.

[0100] In some respects, this command is used to instruct the UE to modify the configuration for a specific bandwidth portion (BWP) of a specific serving cell.

[0101] In some respects, this command corresponds to the Media Access Control Command Element (MAC-CE).

[0102] In some respects, the mapping is a 1:1 mapping between the set of DCI code points and the set of time slot offsets.

[0103] In some aspects, for at least one DCI code point, the mapping is a 1:N mapping that maps the DCI code point to a set of candidate time slot offsets.

[0104] In some respects, one or more instructions also cause the UE to: determine the availability of one or more candidate time slot offsets in a set of candidate time slot offsets, wherein transmission is performed on the earliest available time slot based on the determination.

[0105] In some respects, availability determination is based on conflict avoidance schemes, transmission prioritization schemes, or combinations thereof.

[0106] In some respects, the set of time slot offsets is smaller than the set of DCI code points.

[0107] In some respects, mapping maps a given time slot offset to multiple DCI code points.

[0108] In some aspects, the mapping maps a first time slot offset to a first DCI code point, and the mapping maps a second offset to a second DCI code point, wherein one or more of the first time slot offset and the second time slot offset are calculated via a function.

[0109] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a base station, cause the base station to: send downlink control information (DCI) communications to a user equipment (UE), the DCI communications being configured to trigger the transmission of an aperiodic (AP) probe reference signal (SRS) based on a slot offset indicated by a DCI code point via the DCI communications; and receive an APSRS on a set of SRS resources according to the indicated slot offset.

[0110] In some aspects, one or more instructions also cause the base station to: send a configuration for the SRS resource set, which includes a mapping between a set of DCI code points for DCI communication and a set of time slot offsets in the time slot offset list.

[0111] In some respects, this configuration is transmitted via Radio Resource Control (RRC) signaling.

[0112] In some aspects, the slot offset list supplements the slot offset field associated with the default slot offset in this configuration, or the slot offset list incorporates the slot offset field associated with the default slot offset.

[0113] In some respects, one or more instructions also cause the base station to send a command to modify the configuration.

[0114] In some aspects, the command is used to instruct the UE to add one or more entries to the slot offset list or remove one or more entries from the slot offset list, or the command is used to instruct the UE to add at least one entry to the set of DCI code points or remove at least one entry from the set of DCI code points, or wherein the command is used to instruct the UE to modify the mapping between the set of DCI code points and the slot offset list, or a combination thereof.

[0115] In some respects, this command is used to instruct the UE to modify the configuration for a specific bandwidth portion (BWP) of a specific serving cell.

[0116] In some respects, this command corresponds to the Media Access Control Command Element (MAC-CE).

[0117] In some respects, this mapping is a 1:1 mapping between the set of DCI code points and the set of time slot offsets.

[0118] In some aspects, for at least one DCI code point, the mapping is a 1:N mapping that maps the DCI code point to a set of candidate time slot offsets.

[0119] In some respects, AP SRS is received on candidate slot offsets from a set of candidate slot offsets.

[0120] In some respects, the set of time slot offsets is smaller than the set of DCI code points.

[0121] In some respects, mapping maps a given time slot offset to multiple DCI code points.

[0122] In some aspects, the mapping maps a first time slot offset to a first DCI code point, wherein the mapping maps a second offset to a second DCI code point, and wherein one or more of the first time slot offset and the second time slot offset are calculated via a function.

[0123] Based on the accompanying drawings and detailed description, other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art. Attached Figure Description

[0124] The accompanying drawings are provided to aid in the description of various aspects of this disclosure, and are provided merely for illustrative purposes and not for limiting the scope thereof.

[0125] Figure 1 An exemplary wireless communication system is shown according to various aspects.

[0126] Figure 2A and Figure 2B An example wireless network architecture is shown, based on various aspects.

[0127] Figure 3 This is a block diagram illustrating an exemplary UE according to various aspects.

[0128] Figure 4A and Figure 4B This is a diagram illustrating an example of a frame structure and a channel within a frame structure according to various aspects of this disclosure.

[0129] Figure 5 This shows an example configuration for activating / deactivating MAC-CE using version 15 SP SRS.

[0130] Figure 6 An SRS resource mapping scheme according to one aspect of this disclosure is shown, wherein a set of SRS resources is mapped to a corresponding SRS resource.

[0131] Figure 7 Examples of AP SRS slot offset schemes according to various aspects of this disclosure are shown.

[0132] Figure 8 Exemplary methods of wireless communication according to various aspects of this disclosure are shown.

[0133] Figure 9 Exemplary methods of wireless communication according to various aspects of this disclosure are shown.

[0134] Figure 10 The MAC CE is shown in accordance with various aspects of this disclosure.

[0135] Figure 11 An example slot offset scheme with a set of candidate slot offsets is shown according to one aspect of this disclosure. Detailed Implementation

[0136] Aspects of this disclosure are provided in the following description and associated drawings, which relate to various examples provided for illustrative purposes. Alternative aspects may be devised without departing from the scope of this disclosure. Furthermore, well-known elements of this disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of this disclosure.

[0137] The terms “exemplary” and / or “example” are used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” and / or “example” is not necessarily to be construed as preferred or superior to other aspects. Similarly, the term “aspects of this disclosure” does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed.

[0138] Those skilled in the art will understand that the information and signals described below can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the description below can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof, depending in part on the specific application, in part on the desired design, in part on the corresponding technology, etc.

[0139] Furthermore, many aspects are described based on sequences of actions to be performed by elements of, for example, a computing device. It will be appreciated that the various actions described herein can be performed by specific circuitry (e.g., an application-specific integrated circuit (ASIC)), program instructions executed by one or more processors, or a combination of both. Additionally, the sequences of actions described herein can be considered to be fully embodied in any form of non-transitory computer-readable storage medium having a corresponding set of computer instructions stored therein, which, when executed, will cause or instruct the associated processor of the device to perform the functionality described herein. Therefore, various aspects of this disclosure can be embodied in several different forms, all of which are contemplated within the scope of the claimed subject matter. Furthermore, for each aspect described herein, the corresponding form of any such aspect can be described herein as, for example, "logic" "configured" to perform the described actions.

[0140] As used herein, unless otherwise stated, the terms “User Equipment” (UE) and “Base Station” are not intended to be specific to or otherwise limited to any particular Radio Access Technology (RAT). Generally, a UE can be any wireless communication device used by a user to communicate over a wireless communication network (e.g., mobile phone, router, tablet computer, laptop computer, tracking device, wearable device (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., car, motorcycle, bicycle, etc.), Internet of Things (IoT) device, etc.). A UE can be mobile or stationary (e.g., at certain times) and can communicate with a Radio Access Network (RAN). As used herein, the term “UE” can be interchangeably referred to as “Access Terminal” or “AT,” “Client Equipment,” “Wireless Equipment,” “Subscriber Equipment,” “Subscriber Terminal,” “Subscriber Station,” “User Terminal” or “UT,” “Mobile Terminal,” “Mobile Station,” or variations thereof. Typically, a UE can communicate with a core network via the RAN, and through the core network, a UE can connect to external networks such as the Internet and to other UEs. Of course, other mechanisms for connecting the UE to the core network and / or the Internet are also possible, such as through wired access networks, wireless local area network (WLAN) networks (e.g., based on IEEE 802.11, etc.).

[0141] Depending on the network in which the base station is deployed, the base station can operate according to one of several RATs communicating with the UE, and may be alternatively referred to as an Access Point (AP), Network Node, Node B, Evolved Node B (eNB), New Radio (NR) Node B (also referred to as gNB or gNodeB), etc. Furthermore, in some systems, the base station can provide purely edge node signaling functions, while in others it can provide additional control and / or network management functions. The communication link through which the UE can send signals to the base station is called an uplink (UL) channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). The communication link through which the base station can send signals to the UE is called a downlink (DL) or forward link channel (e.g., paging channel, control channel, broadcast channel, forward traffic channel, etc.). As used herein, the term Traffic Channel (TCH) can refer to either the UL / reverse or DL / forward traffic channel.

[0142] The term "base station" can refer to a single physical transmission point or multiple physical transmission points that may or may not be co-located. For example, when the term "base station" refers to a single physical transmission point, the physical transmission point can be the antenna of the base station corresponding to the cell of the base station. When the term "base station" refers to multiple co-located physical transmission points, the physical transmission points can be the antenna array of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). When the term "base station" refers to multiple non-co-located physical transmission points, the physical transmission points can be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a remote radio headend (RRH) (a remote base station connected to the serving base station). Alternatively, non-co-located physical transmission points can be the serving base station from which the UE receives measurement reports and neighboring base stations from which the UE is measuring its reference RF signal.

[0143] An “RF signal” refers to an electromagnetic wave of a given frequency that transmits information through the space between a transmitter and a receiver. As used herein, a transmitter may send a single “RF signal” or multiple “RF signals” to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple “RF signals” corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between the transmitter and receiver can be referred to as a “multipath” RF signal.

[0144] According to various aspects, Figure 1 An exemplary wireless communication system 100 is illustrated. The wireless communication system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 and various UEs 104. Base station 102 may include macro cell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, the macro cell base station may include an eNB in ​​which the wireless communication system 100 corresponds to an LTE network, or a gNB in ​​which the wireless communication system 100 corresponds to a 5G network, or a combination of both, and the small cell base station may include femtocells, picocells, microcells, etc.

[0145] Base station 102 can jointly form a RAN and interface with core network 170 (e.g., Evolved Packet Core (EPC) or Next Generation Core (NGC)) via backhaul link 122, and connect to one or more location servers 172 via core network 170. Among other functions, base station 102 can also perform one or more of the following functions: transmitting user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), user and device tracking, RAN information management (RIM), paging, location, and delivery of warning messages. Base stations 102 can communicate with each other directly or indirectly (e.g., via EPC / NGC) via backhaul link 134, which can be wired or wireless.

[0146] Base station 102 can communicate wirelessly with UE 104. Each base station in base station 102 can provide communication coverage for a corresponding geographic coverage area 110. In one aspect, one or more cells can be supported by base station 102 in each coverage area 110. A “cell” is a logical communication entity used to communicate with a base station (e.g., via some frequency resources, which are referred to as carrier frequency, component carrier, carrier, frequency band, etc.) and can be associated with an identifier (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID)) to distinguish cells operating via the same or different carrier frequencies. In some cases, different cells can be configured according to different protocol types that can provide access for different types of UEs (e.g., Machine Type Communication (MTC), Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB), or others). In some cases, the term “cell” can also refer to the geographic coverage area (e.g., sector) of a base station, with regard to the carrier frequency being detectable and used for communication within some portions of geographic coverage area 110.

[0147] While the geographic coverage areas 110 of adjacent macro cell base stations 102 may partially overlap (e.g., in handover areas), some geographic coverage areas 110 may significantly overlap with larger geographic coverage areas 110. For example, a small cell base station 102' may have a coverage area 110' that significantly overlaps with the coverage areas 110 of one or more macro cell base stations 102. A network that includes both small cell and macro cell base stations can be referred to as a heterogeneous network. A heterogeneous network may also include home eNBs (HeNBs) that can provide service to restricted groups known as closed subscriber groups (CSGs).

[0148] The communication link 120 between base station 102 and UE 104 may include downlink (UL) transmission from UE 104 to base station 102 (also referred to as the reverse link) and / or downlink (DL) transmission from base station 102 to UE 104 (also referred to as the forward link). The communication link 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may use one or more carrier frequencies. The allocation of carriers may be asymmetric relative to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL).

[0149] The wireless communication system 100 may further include a wireless local area network (WLAN) access point (AP) 150, which communicates with a WLAN station (STA) 152 via a communication link 154 in unlicensed spectrum (e.g., 5 GHz). When communicating in unlicensed spectrum, the WLAN STA 152 and / or WLAN AP 150 may perform a free channel assessment (CCA) before communication to determine whether a channel is available.

[0150] Small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell base station 102' can employ LTE or 5G technology and use the same 5 GHz unlicensed spectrum as used by WLAN AP 150. Small cell base station 102' employing LTE / 5G in unlicensed spectrum can improve coverage of the access network and / or increase the capacity of the access network. LTE in unlicensed spectrum can be referred to as LTE-Unlicensed (LTE-U), Licensed Assisted Access (LAA), or MulteFire.

[0151] The wireless communication system 100 may further include a millimeter-wave (mmW) base station 180, which can operate in mmW and / or near-mmW frequencies when communicating with the UE 182. Extremely high frequency (EHF) is a portion of the electromagnetic spectrum that contains RF frequencies. EHF has a range of 30 GHz to 300 GHz and wavelengths between 1 mm and 10 mm. Radio waves in this band can be referred to as millimeter waves. Near-mmW can extend down to frequencies of 3 GHz, where the wavelength is 100 mm. Ultra-high frequency (SHF) bands extend between 3 GHz and 30 GHz, and are also referred to as centimeter waves. Communication using mmW / near-mmW RF bands has high path loss and relatively short range. The mmW base station 180 and the UE 182 can utilize beamforming (transmit and / or receive) on the mmW communication link 184 to compensate for the extremely high path loss and short range. Furthermore, it will be understood that, in alternative configurations, one or more base stations 102 may also transmit using mmW or near-mmW and beamforming. Therefore, it will be understood that the foregoing description is merely illustrative and should not be construed as limiting any aspect of the disclosure herein.

[0152] Transmit beamforming is a technique for focusing RF signals in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). Using transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thus providing a faster (in terms of data rate) and stronger RF signal to the receiving device. To change the directivity of the RF signal during transmission, the network node can control the phase and relative amplitude of the RF signal at each of one or more transmitters broadcasting the RF signal. For example, the network node can use an antenna array (called a "phased array" or "antenna array") that creates a beam of RF waves that can be "guided" to point in different directions without actually moving the antennas. Specifically, RF currents from the transmitters are fed to individual antennas with the correct phase relationship, causing the radio waves from the individual antennas to be added together to increase radiation in the desired direction while cancellation is performed to suppress radiation in undesired directions.

[0153] Transmit beams can be quasi-co-located, meaning that the transmit beams appear to the same parameters to the receiver (e.g., the UE), regardless of whether the transmit antennas of the network nodes themselves are physically co-located. In NR, there are four types of quasi-co-located (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters about the second reference RF signal on the second beam can be derived from information about the source reference RF signal on the source beam. Therefore, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal transmitted on the same channel. If the source reference RF signal is of type QCL D, the receiver can use the source reference RF signal to estimate the spatial reception parameters of a second reference RF signal transmitted on the same channel.

[0154] In receive beamforming, a receiver uses a receive beam to amplify an RF signal detected on a given channel. For example, a receiver may increase a gain setting and / or adjust the phase setting of an antenna array in a specific direction to amplify the RF signal received from that direction (e.g., to increase the gain level of the RF signal received from that direction). Therefore, when a receiver is referred to as beamforming in a certain direction, it means that the beam gain in that direction is high relative to the beam gain along other directions, or that the beam gain in that direction is the highest compared to the beam gain of all other receive beams available to the receiver in that direction. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference-plus-noise ratio (SINR), etc.) of the RF signal received from that direction.

[0155] The receive beam can be spatially dependent. Spatial dependence means that the parameters of the transmit beam for the second reference signal can be derived from information about the receive beam for the first reference signal. For example, the UE can use a specific receive beam to receive a reference downlink reference signal (e.g., a synchronization signal block (SSB)) from a base station. The UE can then form a transmit beam based on the parameters of the receive beam to transmit an uplink reference signal (e.g., a sounding reference signal (SRS)) to that base station.

[0156] It should be noted that, depending on the entity forming the "downlink" beam, the "downlink" beam can be either a transmit beam or a receive beam. For example, if a base station is forming a downlink beam to send a reference signal to a UE, the downlink beam is a transmit beam. However, if a UE is forming a downlink beam, it is a receive beam used to receive downlink reference signals. Similarly, depending on the entity forming the "uplink" beam, the "uplink" beam can be either a transmit beam or a receive beam. For example, if a base station is forming an uplink beam, it is an uplink receive beam, and if a UE is forming an uplink beam, it is an uplink transmit beam.

[0157] In 5G, the spectrum in which radio nodes (e.g., base stations 102 / 180, UE 104 / 182) operate is divided into several frequency ranges: FR1 (from 450 MHz to 6000 MHz), FR2 (from 24250 MHz to 52600 MHz), FR3 (above 52600 MHz), and FR4 (between FR1 and FR2). In multi-carrier systems (such as 5G), one of the carrier frequencies is called the “primary carrier” or “anchor carrier” or “primary serving cell” or “PCell,” and the remaining carrier frequencies are called “secondary carriers” or “secondary serving cells” or “SCell.” In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by UE 104 / 182, and the cell in which UE 104 / 182 performs the initial Radio Resource Control (RRC) connection establishment procedure or initiates the RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels. A secondary carrier is a carrier operating on a second frequency (e.g., FR2). This second frequency can be configured once an RRC connection is established between UE 104 and the anchor carrier, and it can be used to provide additional radio resources. The secondary carrier may contain only the necessary signaling information and signals; for example, UE-specific information and signals may not be present in the secondary carrier because the primary uplink and downlink carriers are typically UE-specific. This means that different UEs 104 / 182 within a cell can have different downlink primary carriers. The same applies to the uplink primary carrier. The network can change the primary carrier of any UE 104 / 182 at any time. For example, this is done to balance the load on different carriers. Because a “serving cell” (whether PCell or SCell) corresponds to the carrier frequency / component carrier on which a base station is communicating, the terms “cell,” “serving cell,” “component carrier,” “carrier frequency,” etc., can be used interchangeably.

[0158] For example, still refer to Figure 1One of the frequencies utilized by the macro cell base station 102 can be an anchor carrier (or "PCell"), and other frequencies utilized by the macro cell base station 102 and / or the mmW base station 180 can be secondary carriers ("SCell"). Simultaneous transmission and / or reception on multiple carriers allows the UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, compared to that achieved by a single 20 MHz carrier, the aggregation of two 20 MHz carriers in a multi-carrier system would theoretically result in a doubling of the data rate (i.e., 40 MHz).

[0159] The wireless communication system 100 may further include one or more UEs (such as UE 190) that are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links. Figure 1 In the example, UE190 has a D2D P2P link 192 with one of UEs 104 connected to one of base stations 102 (e.g., through which UE 190 indirectly obtains cellular connectivity) and a D2D P2P link 194 with a WLAN STA 152 connected to a WLAN AP 150 (through which UE 190 indirectly obtains WLAN-based internet connectivity). In one example, D2D P2P link 192 and D2D P2P link 194 can be supported using any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth®, etc.

[0160] The wireless communication system 100 may further include a UE 164, which can communicate with the macro cell base station 102 via communication link 120 and / or with the mmW base station 180 via mmW communication link 184. For example, the macro cell base station 102 may support PCell and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164.

[0161] According to various aspects, Figure 2AAn example wireless network architecture 200 is illustrated. For example, the NGC 210 (also referred to as "5GC") can be functionally considered as a control plane function 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and a user plane function 212 (e.g., UE gateway functions, access to data networks, IP routing, etc.), which operate cooperatively to form the core network. A user plane interface (NG-U) 213 and a control plane interface (NG-C) 215 connect the gNB 222 to the NGC 210, and specifically, to the control plane function 214 and the user plane function 212. In another configuration, an eNB 224 can also be connected to the NGC 210 via NG-C 215 to the control plane function 214 and NG-U 213 to the user plane function 212. Furthermore, the eNB 224 can communicate directly with the gNB 222 via a backhaul connection 223. In some configurations, the new RAN 220 may have only one or more gNB 222s, while other configurations include one or more of both eNB 224 and gNB 222. The gNB 222 or eNB 224 can be used with UE 204 (e.g., in...). Figure 1 The location server 230 can communicate with the NGC 210 to provide location assistance to the UE 204. The location server 230 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively, each can correspond to a single server. The location server 230 can be configured to support one or more location services for the UE 204 that can be connected to the location server 230 via the core network, the NGC 210, and / or via the Internet (not shown). Furthermore, the location server 230 can be integrated into a component of the core network, or alternatively, can be located outside the core network.

[0162] According to various aspects, Figure 2BAnother example wireless network architecture 250 is shown. For example, NGC 260 (also referred to as "5GC") can be functionally considered as a control plane function provided by Access and Mobility Management Function (AMF) / User Plane Function (UPF) 264 and a user plane function provided by Session Management Function (SMF) 262, which cooperate to form the core network (i.e., NGC 260). User plane interface 263 and control plane interface 265 connect eNB 224 to NGC 260, and specifically to SMF 262 and AMF / UPF 264, respectively. In another configuration, gNB 222 can also connect to NGC 260 via control plane interface 265 to AMF / UPF 264 and user plane interface 263 to SMF 262. Furthermore, with or without a direct gNB connection to NGC 260, eNB 224 can communicate directly with gNB 222 via backhaul connection 223. In some configurations, the new RAN 220 may have only one or more gNB 222s, while other configurations include one or more of both eNB 224 and gNB 222. The gNB 222 or eNB 224 can be used with UE 204 (e.g., in...). Figure 1 The base station of the new RAN 220 communicates with the AMF side of the AMF / UPF 264 on the N2 interface and with the UPF side of the AMF / UPF 264 on the N3 interface.

[0163] The AMF's functions include registration management, connection management, reachability management, mobility management, lawful interception, transmission of Session Management (SM) messages between UE 204 and SMF 262, transparent proxy service for routing SM messages, access authentication and access authorization, transmission of Short Message Service (SMS) messages between UE 204 and the Short Message Service Function (SMSF) (not shown), and Security Anchor Functionality (SEAF). The AMF also interacts with the Authentication Server Function (AUSF) (not shown) and UE 204, and receives the intermediate key established as a result of the UE 204 authentication process. In the case of UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM)-based authentication, the AMF obtains security material from the AUSSF. The AMF's functions also include Security Context Management (SCM). The SCM receives a key from the SEAF, which it uses to derive a network-specific key. The functionality of AMF also includes location service management for management services, transmitting location service messages between UE 204 and Location Management Function (LMF) 270, transmitting location service messages between the new RAN 220 and LMF 270, EPS bearer identifier allocation for interoperability with Evolved Packet System (EPS), and UE 204 mobility event notification. Additionally, AMF supports functionality for non-3GPP access networks.

[0164] The functions of the UPF include: acting as an anchor point for intra / inter-RAT mobility (where applicable), acting as an external Protocol Data Unit (PDU) session point interconnected to a data network (not shown), providing packet routing and forwarding, packet verification, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, quality of service (QoS) processing for the user plane (e.g., UL / DL rate enforcement, reflective QoS flags in DL), UL traffic verification (service data flow (SDF) to QoS flow mapping), transport level packet flags in UL and DL, DL packet buffering and DL data notification triggering, and sending and forwarding one or more "end flags" to the source RAN node.

[0165] The functions of SMF 262 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, configuration of service bootstrapping at the UPF to route services to the correct destination, control of policy implementation and QoS, and downlink data notification. The interface on which SMF 262 communicates with the AMF side of AMF / UPF 264 is called the N11 interface.

[0166] Another optional aspect may include an LMF 270, which can communicate with the NGC 260 to provide location assistance to the UE 204. The LMF 270 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively, each may correspond to a single server. The LMF 270 may be configured to support one or more location services for the UE 204, which may connect to the LMF 270 via the core network, the NGC 260, and / or via the Internet (not shown).

[0167] Figure 3 Several sample components (represented by corresponding blocks) that can be incorporated into UE 302 (which may correspond to any UE described herein), base station 304 (which may correspond to any base station described herein), and network entity 306 (which may correspond to or embody any network function described herein, including location server 230 and LMF 270) to support file transfer operations as taught herein are illustrated. It will be understood that these components can be implemented in different types of devices in different implementations (e.g., in an ASIC, in a system-on-a-chip (SoC), etc.). The illustrated components can also be incorporated into other devices in a communication system. For example, other devices in the system may include components similar to those described to provide similar functionality. Additionally, a given device may contain one or more of the components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0168] UE 302 and base station 304 each include at least one wireless communication device (represented by communication devices 308 and 314 (and by communication device 320 if device 304 is a repeater)) for communicating with other nodes via at least one designated RAT. For example, communication devices 308 and 314 can communicate with each other on wireless communication link 360, which can correspond to... Figure 1The communication link 120 is described above. Each communication device 308 includes at least one transmitter (represented by transmitter 310) for transmitting and encoding signals (e.g., messages, indications, information, etc.) and at least one receiver (represented by receiver 312) for receiving and decoding signals (e.g., messages, indications, information, pilots, etc.). Similarly, each communication device 314 includes at least one transmitter (represented by transmitter 316) for transmitting signals (e.g., messages, indications, information, pilots, etc.) and at least one receiver (represented by receiver 318) for receiving signals (e.g., messages, indications, information, etc.). If base station 304 is a relay station, each communication device 320 may include at least one transmitter (represented by transmitter 322) for transmitting signals (e.g., messages, indications, information, pilots, etc.) and at least one receiver (represented by receiver 324) for receiving signals (e.g., messages, indications, information, etc.).

[0169] In some implementations, the transmitter and receiver may include integrated devices (e.g., transmitter and receiver circuitry embodied as a single communication device (often referred to as a "transceiver")), in some implementations may include separate transmitter and receiver devices, or in other implementations may be embodied in other ways. The wireless communication equipment of base station 304 (e.g., one of a plurality of wireless communication devices) may also include a network eavesdropping module (NLM) for performing various measurements, etc.

[0170] Network entity 306 (and, if not a relay station, base station 304) includes at least one communication device (represented by communication device 326 and optionally 320) for communicating with other nodes. For example, communication device 326 may include a network interface configured to communicate via a wired or wireless backhaul 370 (which may correspond to...). Figure 1 The backhaul link 122 communicates with one or more network entities. In some aspects, the communication device 326 can be implemented as a transceiver configured to support wired or wireless signal-based communication, and the transmitter 328 and receiver 330 can be integrated units. This communication can involve, for example, sending and receiving: messages, parameters, or other types of information. Therefore, in Figure 3 In the example, communication device 326 is shown as including transmitter 328 and receiver 330. Alternatively, transmitter 328 and receiver 330 may be separate devices within communication device 326. Similarly, if base station 304 is not a relay station, communication device 320 may include a network interface configured to communicate with one or more network entities 306 via wired or wireless backhaul 370. Like communication device 326, communication device 320 is shown as including transmitter 322 and receiver 324.

[0171] Apparatus 302, 304, and 306 also include other components that can be used in conjunction with file transfer operations as disclosed herein. UE 302 includes a processing system 332 for providing functionality related to UE operations as described herein, and for providing other processing functionality. Base station 304 includes a processing system 334 for providing functionality related to base station operations as described herein, and for providing other processing functionality. Network entity 306 includes a processing system 336 for providing functionality related to network function operations as described herein, and for providing other processing functionality. Apparatus 302, 304, and 306 each include memory components 338, 340, and 342 (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Additionally, UE 302 includes a user interface 350 for providing instructions to a user (e.g., auditory and / or visual instructions) and / or for receiving user input (e.g., when the user drives sensing devices such as a keyboard, touchscreen, microphone, etc.). Although not shown, devices 304 and 306 may also include a user interface.

[0172] Referring more specifically to processing system 334, in the downlink, IP packets from network entity 306 can be provided to processing system 334. Processing system 334 can implement functionality for the Radio Resource Control (RRC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. Processing system 334 can provide: RRC layer functionality associated with: broadcasting system information (e.g., Master Information Block (MIB), System Information Block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with: header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with: transmission of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with: mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0173] Transmitter 316 and receiver 318 can implement Layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) can include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. Transmitter 316 processes the mapping to the signal constellation diagram based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to orthogonal frequency division multiplexing (OFDM) subcarriers, multiplexed with reference signals (e.g., pilots) in the time and / or frequency domains, and subsequently combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from the channel estimator can be used to determine coding and modulation schemes, as well as for spatial processing. Channel estimates can be derived based on reference signals transmitted by UE 302 and / or channel condition feedback. Each spatial stream can then be provided to one or more different antennas. Transmitter 316 can utilize the respective spatial streams to modulate an RF carrier for transmission.

[0174] At UE 302, receiver 312 receives signals through its corresponding antenna. Receiver 312 recovers the information modulated onto the RF carrier and provides this information to processing system 332. Transmitter 310 and receiver 312 implement Layer 1 functionality associated with various signal processing functions. Receiver 312 can perform spatial processing on the information to recover any spatial stream destined for UE 302. If multiple spatial streams are destined for UE 302, they can be combined by receiver 312 into a single OFDM symbol stream. Receiver 312 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most probable signal constellation points transmitted by base station 304. These soft decisions can be based on channel estimates calculated by a channel estimator. The soft decision is then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 304 on the physical channel. This data and control signals are then provided to processing system 332, which implements layer 3 and layer 2 functionality.

[0175] In UL, processing system 332 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets from the core network. Processing system 332 is also responsible for error detection.

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

[0177] Transmitter 310 can use a channel estimate derived by a channel estimator based on a reference signal or feedback transmitted by base station 304 to select an appropriate coding and modulation scheme and facilitate spatial processing. The spatial stream generated by transmitter 310 can be provided to different antennas. Transmitter 310 can utilize the corresponding spatial stream to modulate the RF carrier for transmission.

[0178] At base station 304, UL transmissions are processed in a manner similar to that described for the receiver functions incorporated at UE 302. Receiver 318 receives signals through its respective antenna. Receiver 318 recovers the information modulated onto the RF carrier and provides this information to processing system 334.

[0179] In the UL, processing system 334 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport and logical channels to recover IP packets from UE 302. IP packets from processing system 334 can then be provided to the core network. Processing system 334 is also responsible for error detection.

[0180] In one aspect, devices 302, 304, and 306 may each include probe reference signal (SRS) components 344, 348, and 349. It will be understood that the functionality of the various SRS components 344, 348, and 349 may differ based on the device in which that functionality is implemented. SRS components 344, 348, and 349 may be hardware circuitry that is part of or coupled to processing systems 332, 334, and 336, respectively, which, when executed, causes devices 302, 304, and 306 to perform the functionality described herein. Alternatively, SRS components 344, 348, and 349 may be memory modules stored in memory components 338, 340, and 342, respectively, which, when executed by processing systems 332, 334, and 336, cause devices 302, 304, and 306 to perform the functionality described herein.

[0181] For convenience, Figure 3 Devices 302, 304, and / or 306 are shown as including various components that can be configured according to the various examples described herein. However, it will be understood that the blocks shown may have different functionalities in different designs.

[0182] The various components of devices 302, 304 and 306 can communicate with each other on data buses 352, 354 and 356 respectively. Figure 3 Components can be implemented in various ways. In some implementations, Figure 3The components can be implemented in one or more circuits, such as one or more processors and / or one or more ASICs (which may include one or more processors). Here, each circuit may use and / or incorporate at least one memory component for storing information or executable code used by that circuit to provide such functionality. For example, some or all of the functionality represented by blocks 308, 332, 338, 344, and 350 can be implemented by the processor and memory components of UE 302 (e.g., by executing appropriate code and / or by properly configuring the processor components). Similarly, some or all of the functionality represented by blocks 314, 320, 334, 340, and 348 can be implemented by the processor and memory components of base station 304 (e.g., by executing appropriate code and / or by properly configuring the processor components). Furthermore, some or all of the functionality represented by blocks 326, 336, 342, and 349 can be implemented by the processor and memory components of network entity 306 (e.g., by executing appropriate code and / or by properly configuring the processor components). For simplicity, this document describes various operations, actions, and / or functions as being performed "by the UE," "by the base station," "by the positioning entity," etc. However, it will be understood that such operations, actions, and / or functions can actually be performed by specific components of the UE, base station, positioning entity, etc. (such as processing systems 332, 334, 336, communication devices 308, 314, 326, SRS components 344, 348, and 349, etc.) or combinations of components.

[0183] Figure 4A This is a schematic diagram 400 illustrating an example of a DL frame structure according to various aspects of this disclosure. Figure 4B This is a schematic diagram 430 illustrating an example of a channel within a DL frame structure according to various aspects of this disclosure. Other wireless communication technologies may have different frame structures and / or different channels.

[0184] LTE (and in some cases NR) utilizes OFDM on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR can also optionally use OFDM on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are often also referred to as tones, frequency bands, etc. Data can be used to modulate each subcarrier. Typically, modulation symbols are transmitted using OFDM in the frequency domain and SC-FDM in the time domain. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the subcarrier spacing can be 15 kHz and the minimum resource allocation (resource block) can be 12 subcarriers (or 180 kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, the nominal FFT size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into subbands. For example, a subband can cover 1.08 MHz (i.e., 6 resource blocks), and there can be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[0185] LTE supports a single digital scheme (numerology) (subcarrier spacing, symbol length, etc.). In contrast, NR can support multiple digital schemes; for example, subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz or greater can be available. Table 1, provided below, lists some of the different parameters used for different NR digital schemes.

[0186] exist Figure 4A and Figure 4B In the example, a 15 kHz digital scheme was used. Therefore, in the time domain, a frame (e.g., 10 ms) is divided into 10 equal-sized subframes, each 1 ms in size, and each subframe includes a time slot. Figure 4A and Figure 4B In this representation, time is shown horizontally (e.g., on the X-axis), where time increases from left to right, while frequency is shown vertically (e.g., on the Y-axis), where frequency increases (or decreases) from bottom to top.

[0187] A resource grid can be used to represent time slots, each time slot comprising one or more concurrent resource blocks (RBs) in the frequency domain (also known as physical RBs (PRBs)). The resource grid is further divided into multiple resource elements (REs). An RE can correspond to a symbol length in the time domain and a subcarrier in the frequency domain. Figure 4A and Figure 4B In the digital scheme, for a normal cyclic prefix, the RB can contain 12 consecutive subcarriers in the frequency domain and 7 consecutive symbols in the time domain (for DL, OFDM symbols; for UL, SC-FDMA symbols), for a total of 84 REs. For an extended cyclic prefix, the RB can contain 12 consecutive subcarriers in the frequency domain and 6 consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried through each RE depends on the modulation scheme.

[0188] like Figure 4A As shown, some REs in the REs carry DL reference (pilot) signals (DL-RS) for channel estimation at the UE. The DL-RS may include demodulation reference signals (DMRS) and channel state information reference signals (CSI-RS), with exemplary locations shown in [example location]. Figure 4A It is marked as "R".

[0189] Figure 4B Examples of various channels within a DL subframe of a frame are shown. The Physical Downlink Control Channel (PDCCH) carries DL Control Information (DCI) within one or more Control Channel Elements (CCEs). Each CCE includes nine RE Groups (REGs), and each REG includes four consecutive REs in an OFDM symbol. The DCI carries information about UL resource allocation (persistent and non-persistent) and a description of the DL data sent to the UE. Multiple (e.g., up to eight) DCIs can be configured in the PDCCH, and these DCIs can have one of several formats. For example, different DCI formats exist for UL scheduling, for non-MIMO DL scheduling, for MIMO DL scheduling, and for UL power control.

[0190] The UE uses the Primary Synchronization Signal (PSS) to determine subframe / symbol timing and physical layer identifiers. The UE uses the Secondary Synchronization Signal (SSS) to determine the physical layer cell identifier group number and radio frame timing. Based on the physical layer identifier and physical layer cell identifier group number, the UE can determine the PCI. Based on the PCI, the UE can determine the location of the aforementioned DL-RS. The Physical Broadcast Channel (PBCH) carrying the MIB can be logically grouped with the PSS and SSS to form an SSB (also known as SS / PBCH). The MIB provides the number of RBs and the System Frame Number (SFN) in the DL system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0191] SRS is an uplink-only signal transmitted by the UE to help the base station obtain Channel State Information (CSI) for each user. Channel State Information describes how the RF signal propagates from the UE to the base station and represents the combined effects of scattering, fading, and power attenuation with distance. This system uses SRS for resource scheduling, link adaptation, massive MIMO, beam management, and more.

[0192] In one extreme case, for example, for UL beam management purposes, SRS can be simply used at the gNB to obtain signal strength measurements. In another extreme case, SRS can be used at the gNB to obtain detailed amplitude and phase estimates based on frequency, time, and spatial variations. In NR, compared to LTE, channel sounding with SRS supports a more diverse set of use cases (e.g., downlink CSI acquisition for reciprocity-based gNB transmit beamforming (downlink MIMO); uplink CSI acquisition for link adaptation; and codebook-based / non-codebook-based precoding, uplink beam management, etc., for uplink MIMO).

[0193] SRS can be configured using various options. In some designs, the time / frequency mapping of SRS resources is defined by the following properties:

[0194] Duration N symb SRS —The duration of SRS resources can be one, two, or four consecutive OFDM symbols within a time slot, which is the opposite of LTE, which allows only a single OFDM symbol per time slot.

[0195] Start symbol position l0 — The start symbol of an SRS resource can be located anywhere within the last 6 OFDM symbols of the time slot, provided that the resource does not cross the end boundary of the time slot.

[0196] Repeat factor R —For SRS resources configured with frequency hopping, repetition is permitted before the next hopping occurs. R The same set of subcarriers detected in consecutive OFDM symbols (as used in this paper, "jump" specifically refers to frequency hopping). For example... R The values ​​are 1, 2, and 4, among which R ≤ N symb SRS .

[0197] Transmission comb spacer K TC and comb-like offset k TC—SRS resources can occupy resource elements (REs) in a frequency domain comb structure, where the comb spacing is 2 or 4 REs, as in LTE. This structure allows frequency domain multiplexing of different SRS resources for the same or different users on different combs, where different combs are offset from each other by an integer number of REs. The comb offset is defined relative to the PRB boundary and can take values ​​in the range 0, 1, ... K TC -1 values ​​in the RE. Therefore, for comb-shaped intervals K TC =2, there are 2 different combs that can be reused (if needed), and for the comb spacing K TC =4, there are 4 different available combs.

[0198] Period and slot offsets for periodic / semi-persistent (SP) SRS cases.

[0199] The probe bandwidth within the bandwidth portion (BWP).

[0200] In some designs, the Media Access Control (MAC) Command Element (CE) can be used to activate or deactivate the SRS. Figure 5 This shows a sample configuration for version 15 SP SRS Activation / Deactivation Media Access Control (MAC-CE) 500. (Regarding...) Figure 5 Version 15 MAC-CE 500 described in the document defines the corresponding fields as follows:

[0201] A / D: This field indicates whether the SP SRS resource set is activated or deactivated. Setting this field to 1 indicates activation; otherwise, it indicates deactivation.

[0202] Cell ID of SRS Resource Set: This field indicates the identifier of the serving cell, which contains the active / deactivated SPSRS resource set. If the C field is set to 0, this field also indicates the identifier of the serving cell containing all resources indicated by the Resource IDi field. This field is 5 bits long.

[0203] BWP ID of SRS resource set: This field indicates the UL BWP as the code point of the DCI bandwidth portion indicator field as specified in TS 38.212[9], which contains the active / deactivated SP SRS resource set. If the C field is set to 0, this field also indicates the identifier of the BWP containing all resources indicated by the resource IDi field. The length of this field is 2 bits;

[0204] C: This field indicates the presence of an octet containing the Resource Serving Cell ID and Resource BWP ID fields. If this field is set to 1, the octet containing the Resource Serving Cell ID and Resource BWP ID fields exists; otherwise, they do not exist.

[0205] SUL: This field indicates whether MAC-CE is applied to a NUL carrier or a SUL carrier configuration. This field is set to 1 to indicate that it is applied to a SUL carrier configuration, and to 0 to indicate that it is applied to a NUL carrier configuration.

[0206] SP SRS Resource Set ID: This field indicates the SP SRS resource set ID identified by SRS-ResourceSetId as specified in TS 38.331, which will be activated or deactivated. This field is 4 bits long;

[0207] Fi: This field indicates the type of resource used for spatial relationships of SRS resources within the SP SRS resource set indicated by the SP SRS resource set ID field. F0 refers to the first SRS resource within the resource set, F1 refers to the second SRS resource within the resource set, and so on. This field is set to 1 to indicate the use of the NZP CSI-RS resource index, and to 0 to indicate the use of either the SSB index or the SRS resource index. The field is 1 bit long. This field exists only when MACCE is activated (i.e., the A / D field is set to 1).

[0208] Resource IDi: This field contains the identifier of the resource used for spatial relation derivation of SRS resource i. Resource ID0 refers to the first SRS resource in the resource set, Resource ID1 refers to the second SRS in the resource set, and so on. If Fi is set to 0 and the first bit of this field is set to 1, the remainder of this field contains the SSB index as specified in TS 38.331. If Fi is set to 0 and the first bit of this field is set to 0, the remainder of this field contains the SRS-ResourceId as specified in TS 38.331. This field is 7 bits long. This field exists only when MAC-CE is used for activation (i.e., the A / D field is set to 1).

[0209] Resource Serving Cell IDi: This field indicates the identifier of the serving cell where the resource, used for spatial relation derivation of SRS resource i, is located. This field is 5 bits long.

[0210] Resource BWP IDi: This field indicates the code point of the UL BWP as the DCI bandwidth portion indicator field as specified in TS 38.212, on which the resource used for spatial relation derivation of SRS resource i is located. This field is 2 bits long.

[0211] exist Figure 5 Version 15 MAC-CE 500, as depicted, only allows spatial relation information to be updated for a single cell. In this case, the network is required to send a separate MAC CE for each component carrier (CC), resulting in high overhead and significant latency impacting network throughput. Recently, spatial relation information for SRS resources has been activated (or deactivated) by MAC-CE via explicit or implicit indication of the cell list, thus presumably applying spatial relation information to all cells in the cell list (e.g., with respect to...). Figure 5 In contrast to version 15 MAC-CE 500, which is described in the document, it is designed for single-cell operation by default. This approach offers various technical advantages, such as reduced overhead and reduced latency that impacts network throughput.

[0212] Figure 6 An SRS resource mapping scheme 600 according to one aspect of this disclosure is illustrated, wherein an SRS resource set is mapped to corresponding SRS resources. The SRS resource set includes a collection of SRS resources transmitted by a specific UE. As described above, the SRS resource set can be transmitted aperiodically (AP SRS, e.g., signaled by DCI), semi-persistently (SP-SRS), or periodically (P-SRS). The UE can be configured with multiple resources, which can be grouped into the SRS resource set according to use cases (e.g., antenna switching, codebook-based, non-codebook-based, or beam management).

[0213] In some designs, for AP SRS, two bits in the DL or UL DCI can be used to trigger a transmission to the SRS resource set. For example, each AP SRS resource set can be marked with 1, 2, or 3 (corresponding to code points 01, 10, and 11, respectively), and DCI code point 00 can indicate no AP SRS transmission. In some designs, each AP SRS resource set can be configured via RRC signaling with a “slotOffset” from 0 to 32, where slotOffset is the number of time slots between triggering the DCI and the actual transmission of that SRS-ResourceSet. If this field is absent, the UE does not apply an offset (value 0). Once the DCI selects an SRS resource set, the time slot offset is fixed.

[0214] Traditionally, AP SRS is triggered in association with a UE handover from one serving cell to another (without UL PUSCH and PUCCH) to transmit APSRS in the context of "AntennaSwitching". For example, DCI format 2_3 can be used to transmit a group of transmit power control (TPC) commands for SRS transmissions by one or more UEs. An SRS request can also be transmitted along with the TPC commands. DCI format 2_3 is an example of a group common (GC)-DCI comprising multiple blocks 1…n, where different blocks can target different UEs.

[0215] In some designs, SRS requests can be defined as follows:

[0216] In some designs, each SRS resource in the set has an associated symbol index (“startPosition”) containing the first symbol of the SRS resource. In some designs, an SRS resource can span multiple consecutive OFDM symbols. In some designs, such parameters are configured via RRC as follows:

[0217] SRS-Resource ::= SEQUENCE {

[0218] …

[0219] resourceMapping SEQUENCE {

[0220] startPosition INTEGER (0..5),

[0221] nrofSymbols ENUMERATED {n1, n2, n4},

[0222] repetitionFactor ENUMERATED {n1, n2, n4}

[0223] In one example, DCI format 0_1 ​​can be used for PUSCH scheduling within a cell. For instance, DCI format 0_1 ​​can be CRC scrambled using C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI, thus:

[0224] Identifier for DCI format – 1 bit

[0225] The value of this bit field is always set to 0, indicating the UL DCI format.

[0226] Carrier indicator – 0 or 3 bits, as defined in subclause 10.1 of [5, TS38.213].

[0227] SRS requests—as defined in Table 7.3.1.1.2-24—are requests made to cells that are not configured with SRS. ServingCellConfig In supplementaryUplink The UE is 2 bits; for the UE configured in the cell with ServingCellConfig In supplementaryUplink The UE field is 3 bits, where the first bit is a non-SUL / SUL indicator as defined in Table 7.3.1.1.1-1, and the second and third bits are defined by Table 7.3.1.1.2-24. According to subclause 6.1.1.2 of [6, TS 38.214], this bit field may also indicate the associated CSI-RS.

[0228] In another example, DCI format 1_1 can be used for PDSCH scheduling within a cell. For instance, DCI format 1_1 can be CRC scrambled using C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0229] Identifier for DCI format – 1 bit

[0230] The value of this bit field is always set to 1, indicating the DL DCI format.

[0231] Carrier indicator – 0 or 3 bits, as defined in subclause 10.1 of [5, TS38.213].

[0232] SRS Request – As defined in Table 7.3.1.1.2-24, 2 bits for a UE in a cell not configured with a supplementaryUplink in ServingCellConfig; 3 bits for a UE in a cell configured with a supplementaryUplink in ServingCellConfig, wherein the first bit is a non-SUL / SUL indicator as defined in Table 7.3.1.1.1-1, and the second and third bits are defined in Table 7.3.1.1.2-24. This bit field may also indicate the associated CSI-RS according to subclause 6.1.1.2 of [6, TS 38.214].

[0233] Figure 7 An example of an AP SRS slot offset scheme 700 according to various aspects of this disclosure is shown. Figure 7In this context, DL or UL permission 702 is received in association with DCI communication. A timeslot offset 704 is indicated, which maps to the starting point of the SRS resource set 706 used for AP SRS.

[0234] In some designs, dynamic AP SRS slot offset indication can be transmitted using a DCI. In some designs, each SRS resource set is configured with a list of slot offsets, where each code point in the DCI is associated with a specific offset value in the list. In other designs, a single slot offset list is configured for all SRS resource sets, where each code point in the DCI is associated with a specific offset value in the list. In some designs, existing fields in the DCI can be reused to indicate code points to indicate slot offsets. In other designs, new DCI fields are added to indicate slot offsets. However, such an approach is limited in terms of flexibility relative to assigning different slots to different SRS resource sets. For example, an SRS code point can trigger multiple SRS resource sets. Therefore, for each SRS resource set, the DCI code points and DCI fields used for each set are limited. Another option is to add extra bits to the DCI, which may degrade PDDCH reception due to DCI overhead.

[0235] Therefore, aspects of this disclosure relate to the indication of slot offsets for AP-SRS based on AP SRS resource trigger values. For example, a configuration for the SRS resource set (e.g., RRC) can specify a mapping between the set of AP SRS resource trigger values ​​for DCI communication and the set of slot offsets in the slot offset list. In some designs, the AP SRS resource trigger values ​​(e.g., DCI code points, such as 01, 10, or 11) can then be transmitted to indicate the mapped slot offset (or the set of candidate slot offsets). Such an approach has various technical advantages, such as allowing for a more flexible mechanism to indicate SRS slot offsets, reduced DCI overhead, and no need to reuse other bit fields.

[0236] Figure 8 An exemplary method 800 for wireless communication according to various aspects of this disclosure is shown. Method 800 can be performed by a UE (such as UE 302).

[0237] At 802, UE 302 (e.g., receiver 312, etc.) receives DCI communication configured to trigger AP-SRS transmission. In some designs, the DCI communication may include an AP SRS resource trigger value (e.g., a DCI code point set to 01, 10, or 11, where a DCI code point of 00 is used to indicate that AP SRS has not been triggered). References to AP SRS resource trigger values ​​and DCI code points are used interchangeably below.

[0238] At 804, UE 302 (e.g., processing system 332, SRS component 344, etc.) determines the slot offset from the DCI communication to the set of SRS resources used for AP SRS, at least in part, based on the AP SRS resource trigger value (e.g., DCI code point) of the DCI communication. The slot offset can be determined in various ways based on the AP SRS resource trigger value (e.g., DCI code point), and in some designs, it can constitute one of several candidate slot offsets for which the SRS transmission attempt is subject to conditions (e.g., collision avoidance schemes such as Listen-After-Speak (LBT)), preemption to facilitate the transmission of higher priority communications, etc.).

[0239] At 806, UE 302 (e.g., transmitter 314, etc.) transmits AP SRS on the SRS resource set according to the determined time slot offset.

[0240] Figure 9 An exemplary method 900 for wireless communication according to various aspects of this disclosure is shown. Method 900 can be performed by a BS (such as BS 304).

[0241] At 902, BS 304 (e.g., transmitter 316, etc.) sends DCI communication to the UE, which is configured to trigger AP-SRS transmission based on a slot offset indicated by an AP SRS resource trigger value (e.g., a DCI code point set to 01, 10, or 11, where a DCI code point of 00 is used to indicate that AP SRS has not been triggered) via the DCI communication. The slot offset can be indicated in various ways via the AP SRS resource trigger value (e.g., a DCI code point), and in some designs, it can constitute one of several candidate slot offsets for which the SRS transmission attempt is subject to conditions (e.g., collision avoidance schemes such as LBT, preemption to facilitate the transmission of higher priority communications, etc.).

[0242] At 904, BS 304 (e.g., transmitter 318, etc.) receives AP SRS on the SRS resource set according to the indicated time slot offset.

[0243] refer to Figure 8-9 In some designs, BS 304 can send a configuration for the SRS resource set to UE 302. This configuration includes a mapping between a set of AP SRS resource trigger values ​​(e.g., DCI code points) for DCI communication and a set of slot offsets from the slot offset list. The determination at 804 can then be based on this mapping. In some designs, this configuration is transmitted via RRC signaling.

[0244] To provide context for how DCI-to-SRS slot offsets are implemented in some systems, details related to traditional SRS will now be discussed. In some designs, the SRS resource set is configured via RRC, as follows:

[0245] SRS-ResourceSet ::= SEQUENCE {

[0246] srs-ResourceSetId SRS-ResourceSetId,

[0247] srs-ResourceIdList SEQUENCE (SIZE(1..maxNrofSRS-ResourcesPerSet))

[0248] OF SRS-ResourceId OPTIONAL, -- Cond Setup

[0249] resourceType CHOICE {

[0250] aperiodic SEQUENCE {

[0251] aperiodicSRS-ResourceTrigger INTEGER (1..maxNrofSRS-TriggerStates-1),

[0252] csi-RS NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook

[0253] slotOffset INTEGER (1..32) OPTIONAL, -- Need S ..., [[

[0255] aperiodicSRS-ResourceTriggerList-v1530 SEQUENCE (SIZE(1..maxNrofSRS-TriggerStates-2))

[0256] OF INTEGER (1..maxNrofSRS-TriggerStates-1) ]]

[0258]

[0259] maxNrofSRS-ResourceSets INTEGER ::= 16 -- The maximum number of SRS resource sets in BWP.

[0260] maxNrofSRS-ResourceSets-1 INTEGER ::= 15 -- Decrement the maximum number of SRS resource sets in BWP by 1.

[0261] maxNrofSRS-Resources INTEGER ::= 64 -- The maximum number of SRS resources.

[0262] maxNrofSRS-Resources-1 INTEGER ::= 63 -- Decrease the maximum number of SRS resources in the SRS resource set by 1.

[0263] maxNrofSRS-ResourcesPerSet INTEGER ::= 16 -- The maximum number of SRS resources in the SRS resource set.

[0264] maxNrofSRS-TriggerStates-1 INTEGER ::= 3 -- Maximum number of SRS trigger states minus 1 (i.e., maximum code points).

[0265] maxNrofSRS-TriggerStates-2 INTEGER ::= 2 -- Maximum number of SRS trigger states minus 2.

[0266] refer to Figure 8-9 In some designs, a new slot offset list RRC parameter (which can be represented as slotOffsetList or slotOffsetTriggerList) can be defined to supplement the existing slotOffset RRC parameter. In some designs, each entry in the new slot offset list RRC parameter can be associated with the corresponding DCI trigger code point entry at aperiodicSRS-ResourceTriggerList, for example:

[0267] SRS-ResourceSet ::= SEQUENCE {

[0268] …

[0269] slotOffset INTEGER (1..32) OPTIONAL, -- requires S

[0270] slotOffsetList SEQUENCE (SIZE(1..maxNrofSRS-TriggerStates-2))

[0271] OF INTEGER (1..32) OPTIONAL

[0272] …

[0273] In one example, DCI code point (or AP SRS resource trigger value) 01 is mapped to time slot offset 4, DCI code point (or AP SRS resource trigger value) 10 is mapped to time slot offset 8, and DCI code point (or AP SRS resource trigger value) 11 is mapped to time slot offset 10, as follows:

[0274] refer to Figure 8-9 In an alternative design, a new slot offset list (RRC parameter) can be defined via RRC (which can be represented as slotOffsetList or slotOffsetTriggerList) to replace the existing RRC slotOffset parameter, for example:

[0275] SRS-ResourceSet ::= SEQUENCE {

[0276] …

[0277] [[ slotOffset INTEGER (1..32) OPTIONAL, -- requires S ]]

[0278] slotOffsetList SEQUENCE (SIZE(1..maxNrofSRS-TriggerStates-2))

[0279] OF INTEGER (1..32) OPTIONAL

[0280] …

[0281] The double brackets indicate that the slotOffset RRC parameter is omitted.

[0282] In this scenario, the new slot offset list RRC parameter is associated with aperiodicSRS-ResourceTrigger and aperiodicSRS-ResourceTriggerList. For example, the first entry of the new slot offset list RRC parameter can be associated with aperiodicSRS-ResourceTrigger (e.g., DCI code point 01), and the remaining values ​​(e.g., DCI code points 10 and 11) can be associated with aperiodicSRS-ResourceTriggerList. In one example, DCI code point (or AP SRS resource trigger value) 01 is mapped to slot offset 4, DCI code point (or AP SRS resource trigger value) 10 is mapped to slot offset 8, and DCI code point (or AP SRS resource trigger value) 11 is mapped to slot offset 10, as follows:

[0283] Therefore, as shown in Tables 4-5, the slot offset list can supplement the slot offset field associated with the default slot offset in this configuration (e.g., Table 4), or the slot offset list can incorporate the slot offset field associated with the default slot offset (e.g., Table 5).

[0284] refer to Figure 8-9 In some designs, BS 304 can send commands to UE 302 to modify this configuration. For example, the command may instruct the UE to add or remove one or more entries from the slot offset list, or it may instruct the UE to add or remove one or more entries from the set of AP SRS resource trigger values ​​(e.g., DCI code points), or it may instruct the UE to modify the mapping between the set of AP SRS resource trigger values ​​(e.g., DCI code points) and the slot offset list, or a combination thereof. In some designs, the command may instruct the UE to modify the configuration for a specific bandwidth portion (BWP) for a specific serving cell. In a specific example, this command may correspond to MAC CE.

[0285] Figure 10 The MAC CE 1000 is shown according to various aspects of this disclosure. Figure 10In this configuration, aperiodicSRS-ResourceTriggerList_Entry_0 and slotOffsetList_Entry_0 are mapped to Entry_0 (e.g., AP SRS resource trigger values, such as DCI code point 10), and aperiodicSRS-ResourceTriggerList_Entry_1 and slotOffsetList_Entry_1 are mapped to Entry_1 (e.g., AP SRS resource trigger values, such as DCI code point 11). In some designs, DCI code point 01 can remain associated with the traditional slot offset 4 and therefore is not updated via MAC CE.

[0286] refer to Figure 8-9 In some designs, this configuration is based on a 1:1 mapping between the set of AP SRS resource trigger values ​​(e.g., DCI code points) and the set of time slot offsets, as illustrated in Table 4-5 above. In other designs, for at least one AP SRS resource trigger value (e.g., DCI code point), the mapping is a 1:N mapping of the AP SRS resource trigger value (e.g., DCI code point) to the set of candidate time slot offsets. For example, the UE can determine the availability of one or more candidate time slot offsets in the set of candidate time slot offsets and, based on this determination, ultimately perform SP-SRS transmission on the earliest available time slot. For example, the availability determination may be based on a conflict avoidance scheme, a transmission priority scheme, or a combination thereof.

[0287] For example, suppose the SRS trigger value (or code point) "01" is linked to a candidate (rather than just one) slot offset, and the UE will attempt SRS transmission until a valid (i.e., usable for AP SRS transmission) slot offset is reached. Specifically, "01" is associated with a set of candidate slot offsets, which includes slot offsets 4 and 6 (denoted as [4,6]). Figure 11 An example slot offset scheme 1100 with a set of candidate slot offsets [4, 6] according to one aspect of this disclosure is shown. Figure 11 In this scenario, the UE receives the SRS trigger value (e.g., DCI code point) "01" via the DCI in time slot 0, and the candidate time slot offsets [4, 6] are mapped to time slots 5 and 7. The UE will first begin SRS transmission in time slot 5 (i.e., time slot offset = 4). If time slot 5 is unavailable (e.g., due to a conflict with a higher priority channel or the time slot is unavailable, e.g., converted to DL), the UE will attempt to transmit AP SRS in time slot 7 (i.e., time slot offset = 6).

[0288] In one example, assume that DCI code point (or AP SRS resource trigger value) 01 is mapped to the set of candidate time slot offsets [4, 6], DCI code point (or AP SRS resource trigger value) 10 is mapped to the set of candidate time slot offsets [8, 12], and DCI code point (or AP SRS resource trigger value) 11 is mapped to the set of candidate time slot offsets [10, 14]. In this case, Tables 4 and 5 can be updated as shown in Tables 6 and 7, respectively, as follows:

[0289] refer to Figure 8-9 In some cases, the set of slot offsets may be smaller than the set of AP SRS resource trigger values ​​(e.g., DCI code points). For example, there may be only one configured slot offset, or the length of slotOffsetList may not match the length of the trigger list (e.g., there are more trigger values ​​than slot offsets). In such cases, each corresponding trigger value can be mapped to a slot offset according to various rules.

[0290] In one example, a given slot offset is mapped to multiple AP SRS resource trigger values ​​(e.g., DCI code points). For example, consider the case where only one slot offset value (or a set of candidate slot offset values) exists. In this case, the slot offset value (or the set of candidate slot offset values) can be applied to each trigger value (e.g., DCI code point). This is similar to conventional behavior, where the default slot offset is 4. In other designs, one or more of the first and second slot offsets are calculated as a function (e.g., an offset relative to a reference slot offset (denoted as Delta)).

[0291] In some designs, if Delta=4 (as in traditional time slot offset), offset_1 can be set to 0.

[0292] refer to Figure 8-9 In some designs, a given set of aperiodic SRS resources is transmitted in the (t+1)th available time slot, counted from the reference time slot, where t is indicated from either the DCI or the RRC (if only one value of t is configured in the RRC), and candidate values ​​for t include at least 0. In some designs, the reference time slot is the time slot with the triggering DCI. In other designs, the reference time slot is the time slot indicated by the conventional trigger offset.

[0293] refer to Figure 8-9In some designs, a list of t values ​​is configured in the RRC for each SRS resource set. In some designs, for DCI indications of t in one of the unicast DCI formats 0_1 / 0_2 / 1-1 / 1-2 or in the group common DCI format 2_3 for scheduling PDSCH or PUSCH or triggering only A-SRS without data, t is indicated by adding a new configurable DCI field. In other designs, for DCI indications of t in the DCI formats 0_1 / 0_2 / 1-1 / 1-2 for scheduling PDSCH or PUSCH, t is indicated without adding a DCI payload. In some designs, the size of the DCI payload does not change dynamically. In some designs, the number of RRC-configured t values ​​and the size of the DCI bit field per SRS resource set are specified.

[0294] refer to Figure 8-9 In some designs, for the DCI indication of "t" in the version 17 SRS trigger offset enhancement, both the DCI for scheduling PDSCH / PUSCH and the DCI 0_1 / 0_2 with no data and no CSI request are indicated by adding a new configurable DCI field (e.g., up to 2 bits). This only applies when multiple candidate values ​​for the configured t exist. In some designs, at least when configuring the new DCI field, there is no further enhancement to indicate "t" for DCI0_1 / 0_2 with no data and no CSI request.

[0295] In some designs, each SRS resource set can be configured with up to four "t" values.

[0296] As can be seen in the detailed description above, different features are grouped together in the examples. This manner of disclosure should not be construed as an intention to include more features than are expressly mentioned in each clause. Rather, aspects of this disclosure may include fewer features than those explicitly mentioned in the individual example clauses disclosed. Therefore, the following clauses should be regarded accordingly as included in the specification, wherein each clause may be considered as a separate example. Although each dependent clause may refer in the clause to a particular combination with one of the other clauses, the aspect of the dependent clause is not limited to that particular combination. It will be understood that other example clauses may also include combinations of aspects of a dependent clause with the subject matter of any other dependent or independent clauses, or combinations of any feature with other dependent and independent clauses. The aspects disclosed herein expressly include these combinations unless expressly stated or readily inferred that a particular combination is not expected (e.g., contradictory aspects, such as defining an element as both an insulator and a conductor). Furthermore, it is contemplated that aspects of a clause may be included in any other independent clause, even if that clause does not directly depend on the independent clause.

[0297] Implementation examples are described in the following numbered clauses:

[0298] Clause 1. A method of operating a user equipment (UE), comprising: receiving downlink control information (DCI) communication, the DCI communication being configured to trigger the transmission of an aperiodic (AP) sounding reference signal (SRS); determining a slot offset from the DCI communication to a set of SRS resources for the AP SRS based at least in part on the DCI code points of the DCI communication; and transmitting the AP SRS on the set of SRS resources according to the determined slot offset.

[0299] Clause 2. The method according to Clause 1 further includes: receiving a configuration for the SRS resource set, the configuration including a mapping between a set of DCI code points for the DCI communication and a set of time slot offsets in a time slot offset list, wherein the determination is based on the mapping.

[0300] Clause 3, the method described in Clause 2, wherein the configuration is received via Radio Resource Control (RRC) signaling.

[0301] Clause 4. The method according to any one of Clauses 2 to 3, wherein the slot offset list supplements the configured slot offset field associated with the default slot offset, or wherein the slot offset list incorporates the slot offset field associated with the default slot offset.

[0302] Clause 5. The method according to any one of Clauses 2 to 4 further includes: receiving a command for modifying the configuration.

[0303] Clause 6. The method according to Clause 5, wherein the command is used to command the UE to add one or more entries to the slot offset list or remove one or more entries from the slot offset list, or wherein the command is used to command the UE to add at least one entry to the set of DCI code points or remove at least one entry from the set of DCI code points, or wherein the command is used to command the UE to modify the mapping between the set of DCI code points and the slot offset list, or a combination thereof.

[0304] Clause 7. The method according to any one of Clauses 5 to 6, wherein the command is used to instruct the UE to modify the configuration for a specific bandwidth portion (BWP) of a specific serving cell.

[0305] Clause 8. The method according to any one of Clauses 5 to 7, wherein the command corresponds to a Media Access Control Command Element (MAC-CE).

[0306] Clause 9. The method according to any one of Clauses 2 to 8, wherein the mapping is a 1:1 mapping between the set of DCI code points and the set of time slot offsets.

[0307] Clause 10. The method according to any one of Clauses 2 to 9, wherein, for at least one DCI code point, the mapping is a 1:N mapping that maps the DCI code point to a set of candidate time slot offsets.

[0308] Clause 11. The method according to Clause 10 further includes: determining the availability of one or more candidate time slot offsets in the set of candidate time slot offsets, wherein the transmission is performed on the earliest available time slot based on the determination.

[0309] Clause 12. The method described in Clause 11, wherein the availability determination is based on a conflict avoidance scheme, a transmission priority scheme, or a combination thereof.

[0310] Clause 13. The method according to any one of Clauses 2 to 12, wherein the set of timeslot offsets is less than the set of DCI code points.

[0311] Clause 14. The method according to Clause 13, wherein the mapping maps a given time slot offset to a plurality of DCI code points.

[0312] Clause 15. The method according to any one of Clauses 13 to 14, wherein the mapping maps a first time slot offset to a first DCI code point, and wherein the mapping maps a second offset to a second DCI code point, wherein one or more of the first time slot offset and the second time slot offset are calculated via a function.

[0313] Clause 16. A method of operating a base station, comprising: sending downlink control information (DCI) communication to a user equipment (UE), the DCI communication being configured to trigger transmission of an aperiodic (AP) probe reference signal (SRS) based on a slot offset indicated by a DCI code point via the DCI communication; and receiving the AP SRS on an SRS resource set according to the indicated slot offset.

[0314] Clause 17. The method according to Clause 16 further includes: sending a configuration for the SRS resource set, the configuration including a mapping between a set of DCI code points for the DCI communication and a set of time slot offsets for the time slot offset list.

[0315] Clause 18, the method described in Clause 17, wherein the configuration is transmitted via Radio Resource Control (RRC) signaling.

[0316] Clause 19. The method according to any one of Clauses 17 to 18, wherein the slot offset list supplements the configured slot offset field associated with the default slot offset, or wherein the slot offset list incorporates the slot offset field associated with the default slot offset.

[0317] Clause 20, the method according to any one of Clauses 17 to 19, further includes: sending a command for modifying the configuration.

[0318] Clause 21. The method according to Clause 20, wherein the command is used to command the UE to add one or more entries to the slot offset list or remove one or more entries from the slot offset list, or wherein the command is used to command the UE to add at least one entry to the set of DCI code points or remove at least one entry from the set of DCI code points, or wherein the command is used to command the UE to modify the mapping between the set of DCI code points and the slot offset list, or a combination thereof.

[0319] Clause 22. The method according to any one of Clauses 20 to 21, wherein the command is used to instruct the UE to modify the configuration for a specific bandwidth portion (BWP) of a specific serving cell.

[0320] Clause 23. The method according to any one of Clauses 20 to 22, wherein the command corresponds to a Media Access Control Command Element (MAC-CE).

[0321] Clause 24. The method according to any one of Clauses 17 to 23, wherein the mapping is a 1:1 mapping between the set of DCI code points and the set of time slot offsets.

[0322] Clause 25. The method according to any one of Clauses 17 to 24, wherein, for at least one DCI code point, the mapping is a 1:N mapping that maps the DCI code point to a set of candidate time slot offsets.

[0323] Clause 26, the method according to Clause 25, wherein the AP SRS is received on a candidate slot offset from the set of candidate slot offsets.

[0324] Clause 27. The method according to any one of Clauses 17 to 26, wherein the set of timeslot offsets is less than the set of DCI code points.

[0325] Clause 28. The method according to Clause 27, wherein the mapping maps a given time slot offset to a plurality of DCI code points.

[0326] Clause 29. The method according to any one of Clauses 27 to 28, wherein the mapping maps a first time slot offset to a first DCI code point, wherein the mapping maps a second offset to a second DCI code point, and wherein one or more of the first time slot offset and the second time slot offset are calculated via a function.

[0327] Clause 30. A user equipment (UE) comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive downlink control information (DCI) communication via the at least one transceiver, the DCI communication being configured to trigger transmission of an aperiodic (AP) sounding reference signal (SRS); determine a slot offset from the DCI communication to a set of SRS resources for the AP SRS based at least in part on the DCI code points of the DCI communication; and transmit the AP SRS on the set of SRS resources via the at least one transceiver according to the determined slot offset.

[0328] Clause 31. The UE according to Clause 30, wherein the at least one processor is further configured to: receive, via the at least one transceiver, a configuration for the SRS resource set, the configuration including a mapping between a set of DCI code points for the DCI communication and a set of time slot offsets in a time slot offset list, wherein the determination is based on the mapping.

[0329] Clause 32, the UE as described in Clause 31, wherein the configuration is received via Radio Resource Control (RRC) signaling.

[0330] Clause 33. A UE pursuant to any one of Clauses 31 to 32, wherein the slot offset list supplements the configured slot offset field associated with the default slot offset, or wherein the slot offset list incorporates the slot offset field associated with the default slot offset.

[0331] Clause 34. The UE according to any one of Clauses 31 to 33, wherein the at least one processor is further configured to receive, via the at least one transceiver, a command for modifying the configuration.

[0332] Clause 35. The UE as described in Clause 34, wherein the command is used to command the UE to add one or more entries to the slot offset list or remove one or more entries from the slot offset list, or wherein the command is used to command the UE to add at least one entry to the set of DCI code points or remove at least one entry from the set of DCI code points, or wherein the command is used to command the UE to modify the mapping between the set of DCI code points and the slot offset list, or a combination thereof.

[0333] Clause 36. A UE pursuant to any one of Clauses 34 to 35, wherein the command is used to instruct the UE to modify the configuration for a specific bandwidth portion (BWP) of a specific serving cell.

[0334] Clause 37. A UE pursuant to any one of Clauses 34 to 36, wherein the command corresponds to a Media Access Control Command Element (MAC-CE).

[0335] Clause 38. A UE pursuant to any one of Clauses 31 to 37, wherein the mapping is a 1:1 mapping between the set of DCI code points and the set of time slot offsets.

[0336] Clause 39. A UE pursuant to any one of Clauses 31 to 38, wherein, for at least one DCI code point, the mapping is a 1:N mapping that maps the DCI code point to a set of candidate time slot offsets.

[0337] Clause 40, the UE according to Clause 39, wherein the at least one processor is further configured to: determine the availability of one or more candidate time slot offsets in the set of candidate time slot offsets, wherein the transmission is performed on the earliest available time slot based on the determination.

[0338] Clause 41. The UE as described in Clause 40, wherein the availability determination is based on a conflict avoidance scheme, a transmission priority scheme, or a combination thereof.

[0339] Clause 42. A UE pursuant to any one of Clauses 31 to 41, wherein the set of timeslot offsets is less than the set of DCI code points.

[0340] Clause 43, the UE as described in Clause 42, wherein the mapping maps a given time slot offset to a plurality of DCI code points.

[0341] Clause 44. A UE according to any one of Clauses 42 to 43, wherein the mapping maps a first time slot offset to a first DCI code point, and wherein the mapping maps a second offset to a second DCI code point, wherein one or more of the first time slot offset and the second time slot offset are calculated via a function.

[0342] Clause 45. A base station comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: transmit downlink control information (DCI) communication to a user equipment (UE) via the at least one transceiver, the DCI communication being configured to trigger transmission of an aperiodic (AP) probe reference signal (SRS) based on a slot offset indicated by a DCI code point indicated via the DCI communication; and receive the AP SRS on an SRS resource set via the at least one transceiver according to the indicated slot offset.

[0343] Clause 46. The base station according to Clause 45, wherein the at least one processor is further configured to: transmit via the at least one transceiver a configuration for the SRS resource set, the configuration including a mapping between a set of DCI code points for the DCI communication and a set of time slot offsets in a time slot offset list.

[0344] Clause 47. The base station as described in Clause 46, wherein the configuration is transmitted via Radio Resource Control (RRC) signaling.

[0345] Clause 48. A base station pursuant to any one of Clauses 46 to 47, wherein the slot offset list supplements the configured slot offset field associated with the default slot offset, or wherein the slot offset list incorporates the slot offset field associated with the default slot offset.

[0346] Clause 49. A base station according to any one of Clauses 46 to 48, wherein the at least one processor is further configured to: transmit a command for modifying the configuration via the at least one transceiver.

[0347] Clause 50. A base station as described in Clause 49, wherein the command is used to command the UE to add one or more entries to the time slot offset list or remove one or more entries from the time slot offset list, or wherein the command is used to command the UE to add at least one entry to the set of DCI code points or remove at least one entry from the set of DCI code points, or wherein the command is used to command the UE to modify the mapping between the set of DCI code points and the time slot offset list, or a combination thereof.

[0348] Clause 51. A base station pursuant to any one of Clauses 49 to 50, wherein the command is used to instruct the UE to modify the configuration for a specific bandwidth portion (BWP) of a specific serving cell.

[0349] Clause 52. A base station pursuant to any one of Clauses 49 to 51, wherein the command corresponds to a Media Access Control Command Element (MAC-CE).

[0350] Clause 53. A base station according to any one of Clauses 46 to 52, wherein the mapping is a 1:1 mapping between the set of DCI code points and the set of time slot offsets.

[0351] Clause 54. A base station pursuant to any one of Clauses 46 to 53, wherein, for at least one DCI code point, the mapping is a 1:N mapping that maps the DCI code point to a set of candidate time slot offsets.

[0352] Clause 55, the base station as described in Clause 54, wherein the AP SRS is received on a candidate time slot offset from the set of candidate time slot offsets.

[0353] Clause 56. A base station pursuant to any one of Clauses 46 to 55, wherein the set of timeslot offsets is less than the set of DCI code points.

[0354] Clause 57. A base station as described in Clause 56, wherein the mapping maps a given time slot offset to a plurality of DCI code points.

[0355] Clause 58. A base station according to any one of Clauses 56 to 57, wherein the mapping maps a first time slot offset to a first DCI code point, wherein the mapping maps a second offset to a second DCI code point, and wherein one or more of the first time slot offset and the second time slot offset are calculated via a function.

[0356] Clause 59. A user equipment (UE) comprising: a unit for receiving downlink control information (DCI) communication configured to trigger the transmission of an aperiodic (AP) sounding reference signal (SRS); a unit for determining a slot offset from the DCI communication to a set of SRS resources for the AP SRS, based at least in part on the DCI code points of the DCI communication; and a unit for transmitting the AP SRS on the set of SRS resources according to the determined slot offset.

[0357] Clause 60, the UE according to Clause 59, further includes: a unit for receiving a configuration for the SRS resource set, the configuration including a mapping between a set of DCI code points of the DCI communication and a set of time slot offsets of a time slot offset list, wherein the determination is based on the mapping.

[0358] Clause 61, the UE as described in Clause 60, wherein the configuration is received via Radio Resource Control (RRC) signaling.

[0359] Clause 62. A UE according to any one of Clauses 60 to 61, wherein the slot offset list supplements the configured slot offset field associated with the default slot offset, or wherein the slot offset list incorporates the slot offset field associated with the default slot offset.

[0360] Clause 63. The UE according to any one of Clauses 60 to 62 further includes: a unit for receiving a command for modifying the configuration.

[0361] Clause 64. The UE as described in Clause 63, wherein the command is used to command the UE to add one or more entries to the slot offset list or remove one or more entries from the slot offset list, or wherein the command is used to command the UE to add at least one entry to the set of DCI code points or remove at least one entry from the set of DCI code points, or wherein the command is used to command the UE to modify the mapping between the set of DCI code points and the slot offset list, or a combination thereof.

[0362] Clause 65. A UE pursuant to any one of Clauses 63 to 64, wherein the command is used to instruct the UE to modify the configuration for a specific bandwidth portion (BWP) of a specific serving cell.

[0363] Clause 66. A UE pursuant to any one of Clauses 63 to 65, wherein the command corresponds to a Media Access Control Command Element (MAC-CE).

[0364] Clause 67. A UE according to any one of Clauses 60 to 66, wherein the mapping is a 1:1 mapping between the set of DCI code points and the set of time slot offsets.

[0365] Clause 68. A UE pursuant to any one of Clauses 60 to 67, wherein, for at least one DCI code point, the mapping is a 1:N mapping that maps the DCI code point to a set of candidate time slot offsets.

[0366] Clause 69. The UE according to Clause 68 further includes: a unit for determining the availability of one or more candidate time slot offsets in the set of candidate time slot offsets, wherein the transmission is performed on the earliest available time slot based on the determination.

[0367] Clause 70, the UE as described in Clause 69, wherein the availability determination is based on a conflict avoidance scheme, or a transmission priority scheme, or a combination thereof.

[0368] Clause 71. A UE pursuant to any one of Clauses 60 to 70, wherein the set of timeslot offsets is less than the set of DCI code points.

[0369] Clause 72, the UE as described in Clause 71, wherein the mapping maps a given time slot offset to a plurality of DCI code points.

[0370] Clause 73. A UE according to any one of Clauses 71 to 72, wherein the mapping maps a first time slot offset to a first DCI code point, and wherein the mapping maps a second offset to a second DCI code point, wherein one or more of the first time slot offset and the second time slot offset are calculated via a function.

[0371] Clause 74. A base station comprising: a unit for transmitting downlink control information (DCI) communication to a user equipment (UE), the DCI communication being configured to trigger transmission of an aperiodic (AP) probe reference signal (SRS) based on a slot offset indicated by a DCI code point via the DCI communication; and a unit for receiving the AP SRS on an SRS resource set according to the indicated slot offset.

[0372] Clause 75. The base station according to Clause 74 further includes: a unit for transmitting a configuration for the SRS resource set, the configuration including a mapping between a set of DCI code points for the DCI communication and a set of time slot offsets in a time slot offset list.

[0373] Clause 76, the base station as described in Clause 75, wherein the configuration is transmitted via Radio Resource Control (RRC) signaling.

[0374] Clause 77. A base station pursuant to any one of Clauses 75 to 76, wherein the slot offset list supplements the configured slot offset field associated with the default slot offset, or wherein the slot offset list incorporates the slot offset field associated with the default slot offset.

[0375] Clause 78. The base station according to any one of Clauses 75 to 77 further includes: a unit for sending a command for modifying the configuration.

[0376] Clause 79. A base station according to Clause 78, wherein the command is used to command the UE to add one or more entries to the time slot offset list or remove one or more entries from the time slot offset list, or wherein the command is used to command the UE to add at least one entry to the set of DCI code points or remove at least one entry from the set of DCI code points, or wherein the command is used to command the UE to modify the mapping between the set of DCI code points and the time slot offset list, or a combination thereof.

[0377] Clause 80, a base station pursuant to any one of Clauses 78 to 79, wherein the command is used to instruct the UE to modify the configuration for a specific bandwidth portion (BWP) of a specific serving cell.

[0378] Clause 81. A base station pursuant to any one of Clauses 78 to 80, wherein the command corresponds to a Media Access Control Command Element (MAC-CE).

[0379] Clause 82. A base station according to any one of Clauses 75 to 81, wherein the mapping is a 1:1 mapping between the set of DCI code points and the set of time slot offsets.

[0380] Clause 83. A base station pursuant to any one of Clauses 75 to 82, wherein, for at least one DCI code point, the mapping is a 1:N mapping that maps the DCI code point to a set of candidate time slot offsets.

[0381] Clause 84, the base station as described in Clause 83, wherein the AP SRS is received on a candidate time slot offset from the set of candidate time slot offsets.

[0382] Clause 85. A base station pursuant to any one of Clauses 75 to 84, wherein the set of timeslot offsets is less than the set of DCI code points.

[0383] Clause 86, the base station as described in Clause 85, wherein the mapping maps a given time slot offset to a plurality of DCI code points.

[0384] Clause 87. A base station according to any one of Clauses 85 to 86, wherein the mapping maps a first time slot offset to a first DCI code point, wherein the mapping maps a second offset to a second DCI code point, and wherein one or more of the first time slot offset and the second time slot offset are calculated via a function.

[0385] Clause 88. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: receive downlink control information (DCI) communication configured to trigger the transmission of an aperiodic (AP) sounding reference signal (SRS); determine a slot offset from the DCI communication to a set of SRS resources for the AP SRS, based at least in part on the DCI code points of the DCI communication; and transmit the AP SRS on the set of SRS resources according to the determined slot offset.

[0386] Clause 89. A non-transitory computer-readable medium pursuant to Clause 88, wherein the one or more instructions further cause the UE to: receive a configuration for the SRS resource set, the configuration including a mapping between a set of DCI code points for the DCI communication and a set of time slot offsets in a time slot offset list, wherein the determination is based on the mapping.

[0387] Clause 90, a non-transitory computer-readable medium as described in Clause 89, wherein the configuration is received via Radio Resource Control (RRC) signaling.

[0388] Clause 91. A non-transitory computer-readable medium pursuant to any one of Clauses 89 to 90, wherein the slot offset list supplements the configured slot offset field associated with the default slot offset, or wherein the slot offset list incorporates the slot offset field associated with the default slot offset.

[0389] Clause 92. A non-transitory computer-readable medium according to any one of Clauses 89 to 91, wherein the one or more instructions further cause the UE to: receive a command for modifying the configuration.

[0390] Clause 93. A non-transitory computer-readable medium as described in Clause 92, wherein the command is used to instruct the UE to add one or more entries to the slot offset list or remove one or more entries from the slot offset list, or wherein the command is used to instruct the UE to add at least one entry to the set of DCI code points or remove at least one entry from the set of DCI code points, or wherein the command is used to instruct the UE to modify the mapping between the set of DCI code points and the slot offset list, or a combination thereof.

[0391] Clause 94. A non-transitory computer-readable medium pursuant to any one of Clauses 92 to 93, wherein the command is used to instruct the UE to modify the configuration for a specific bandwidth portion (BWP) of a specific serving cell.

[0392] Clause 95. A non-transitory computer-readable medium pursuant to any one of Clauses 92 to 94, wherein the command corresponds to a Media Access Control Command Element (MAC-CE).

[0393] Clause 96. A non-transitory computer-readable medium pursuant to any one of Clauses 89 to 95, wherein the mapping is a 1:1 mapping between the set of DCI code points and the set of time slot offsets.

[0394] Clause 97. A non-transitory computer-readable medium pursuant to any one of Clauses 89 to 96, wherein, for at least one DCI code point, the mapping is a 1:N mapping that maps the DCI code point to a set of candidate time slot offsets.

[0395] Clause 98, a non-transitory computer-readable medium pursuant to Clause 97, wherein the one or more instructions further cause the UE to: determine the availability of one or more candidate time slot offsets in the set of candidate time slot offsets, wherein the transmission is performed on the earliest available time slot based on the determination.

[0396] Clause 99. A non-transitory computer-readable medium as described in Clause 98, wherein the availability is determined based on a conflict avoidance scheme, a transmission prioritization scheme, or a combination thereof.

[0397] Clause 100, a non-transitory computer-readable medium pursuant to any one of Clauses 89 to 99, wherein the set of said time slot offsets is less than the set of said DCI code points.

[0398] Clause 101, a non-transitory computer-readable medium as described in Clause 100, wherein the mapping maps a given time slot offset to a plurality of DCI code points.

[0399] Clause 102. A non-transitory computer-readable medium according to any one of Clauses 100 to 101, wherein the mapping maps a first time slot offset to a first DCI code point, and wherein the mapping maps a second offset to a second DCI code point, wherein one or more of the first time slot offset and the second time slot offset are calculated via a function.

[0400] Clause 103. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a base station, cause the base station to: send downlink control information (DCI) communication to a user equipment (UE), the DCI communication being configured to trigger the transmission of an aperiodic (AP) probe reference signal (SRS) based on a slot offset indicated by a DCI code point via the DCI communication; and receive the AP SRS on an SRS resource set according to the indicated slot offset.

[0401] Clause 104, a non-transitory computer-readable medium pursuant to Clause 103, wherein the one or more instructions further cause the base station to: transmit a configuration for the SRS resource set, the configuration including a mapping between a set of DCI code points for the DCI communication and a set of time slot offsets in a time slot offset list.

[0402] Clause 105, a non-transitory computer-readable medium as described in Clause 104, wherein the configuration is transmitted via Radio Resource Control (RRC) signaling.

[0403] Clause 106. A non-transitory computer-readable medium pursuant to any one of Clauses 104 to 105, wherein the slot offset list supplements the configured slot offset field associated with the default slot offset, or wherein the slot offset list incorporates the slot offset field associated with the default slot offset.

[0404] Clause 107. A non-transitory computer-readable medium pursuant to any one of Clauses 104 to 106, wherein the one or more instructions further cause the base station to: send a command for modifying the configuration.

[0405] Clause 108. A non-transitory computer-readable medium as described in Clause 107, wherein the command is used to instruct the UE to add one or more entries to the slot offset list or remove one or more entries from the slot offset list, or wherein the command is used to instruct the UE to add at least one entry to the set of DCI code points or remove at least one entry from the set of DCI code points, or wherein the command is used to instruct the UE to modify the mapping between the set of DCI code points and the slot offset list, or a combination thereof.

[0406] Clause 109. A non-transitory computer-readable medium pursuant to any one of Clauses 107 to 108, wherein the command is used to instruct the UE to modify the configuration for a specific bandwidth portion (BWP) of a specific serving cell.

[0407] Clause 110. A non-transitory computer-readable medium pursuant to any one of Clauses 107 to 109, wherein the command corresponds to a Media Access Control Command Element (MAC-CE).

[0408] Clause 111. A non-transitory computer-readable medium according to any one of Clauses 104 to 110, wherein the mapping is a 1:1 mapping between the set of DCI code points and the set of time slot offsets.

[0409] Clause 112. A non-transitory computer-readable medium according to any one of Clauses 104 to 111, wherein, for at least one DCI code point, the mapping is a 1:N mapping that maps the DCI code point to a set of candidate time slot offsets.

[0410] Clause 113, a non-transitory computer-readable medium as described in Clause 112, wherein the AP SRS is received on a candidate slot offset from the set of candidate slot offsets.

[0411] Clause 114. A non-transitory computer-readable medium according to any one of Clauses 104 to 113, wherein the set of said time slot offsets is less than the set of said DCI code points.

[0412] Clause 115. A non-transitory computer-readable medium as described in Clause 114, wherein the mapping maps a given time slot offset to a plurality of DCI code points.

[0413] Clause 116. A non-transitory computer-readable medium according to any one of Clauses 114 to 115, wherein the mapping maps a first time slot offset to a first DCI code point, wherein the mapping maps a second offset to a second DCI code point, and wherein one or more of the first time slot offset and the second time slot offset are calculated via a function.

[0414] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the foregoing description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0415] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, circuits, and algorithmic steps described in connection with the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, the functionality of the various illustrative components, blocks, modules, circuits, and steps has been generally described above. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in alternative ways for each specific application, but such implementation decisions should not be construed as departing from the scope of this disclosure.

[0416] The various illustrative logic blocks, modules, and circuits described in conjunction with the aspects disclosed herein can be implemented or executed using a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware component, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0417] The methods, sequences, and / or algorithms described in conjunction with the aspects disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or a combination of both. The software module can reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium can be coupled to a processor, enabling the processor to read information from and write information to the storage medium. Alternatively, the storage medium can be a component of the processor. The processor and storage medium can reside in an ASIC. The ASIC can reside in a user terminal (e.g., a UE). Alternatively, the processor and storage medium can reside as discrete components in the user terminal.

[0418] In one or more exemplary aspects, the described functionality can be implemented using hardware, software, firmware, or any combination thereof. If implemented in software, the functionality can be stored on or transmitted via a computer-readable medium as one or more instructions or code. A computer-readable medium can include both computer storage media and communication media, wherein the communication medium includes any medium that facilitates the transfer of a computer program from one place to another. A storage medium can be any available medium that is accessible to a computer. By way of example, and not limitation, such a computer-readable medium can include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that is accessible to a computer. Furthermore, any connection is appropriately referred to as a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared, radio, and microwave), then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) is included in the definition of a medium. As used herein, disks and optical discs include compact optical discs (CDs), laser discs, optical discs, digital versatile optical discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically copy data magnetically, while optical discs use lasers to copy data optically. Combinations of the above should also be included within the scope of computer-readable media.

[0419] While the foregoing disclosure illustrates aspects of this disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of this disclosure as defined by the appended claims. The functions, steps, and / or actions of the method claims according to the aspects of the disclosure described herein do not need to be performed in any particular order. Furthermore, although elements of this disclosure may be described or claimed in the singular, plural forms are contemplated unless expressly stated to be limited to the singular.

Claims

1. A method of operating a user equipment (UE), comprising: receiving a configuration for a set of sounding reference signal (SRS) resources, the configuration comprising a mapping between a set of downlink control information (DCI) codepoints and a set of slot offsets in a list of slot offsets, wherein the mapping is a 1 : 1 mapping between the set of DCI codepoints and the set of slot offsets, or wherein the mapping is a 1 :N mapping for at least one DCI codepoint that maps the DCI codepoint to a set of candidate slot offsets, or wherein a number in the set of slot offsets is less than a number in the set of DCI codepoints; receiving a DCI communication, the DCI communication comprising a value configured to trigger transmission of an aperiodic sounding reference signal (AP SRS); determining, in dependence on the mapping, a slot offset from the DCI communication to a set of SRS resources for the AP SRS based at least in part on a DCI codepoint of the DCI communication; and transmitting the AP SRS on the set of SRS resources according to the determined slot offset. the configuration is received via radio resource control (RRC) signaling.

2. The method of claim 1, wherein, 3. The method of claim 1, the list of slot offsets supplements a slot offset field of the configuration associated with a default slot offset, or wherein wherein the list of slot offsets incorporates the slot offset field associated with the default slot offset.

4. The method of claim 1, further comprising: receiving a command to modify the configuration.

5. The method of claim 4, the command to instruct the UE to add or remove one or more entries to or from the list of slot offsets, or wherein wherein the command to instruct the UE to add or remove at least one entry to or from the set of DCI codepoints, or wherein the command to instruct the UE to modify the mapping between the set of DCI codepoints and the list of slot offsets, or a combination thereof. the command to instruct the UE to modify the configuration for a particular bandwidth part (BWP) of a particular serving cell.

6. The method of claim 4, wherein, the command corresponds to a medium access control command element (MAC-CE).

7. The method of claim 4, wherein, 8. The method of claim 1, wherein the mapping is a 1 :N mapping, the method further comprising: determining availability of one or more candidate slot offsets among the set of candidate slot offsets, wherein the transmitting is performed on an earliest available slot based on the determining. the availability determination is based on a collision avoidance scheme, or a transmission priority scheme, or a combination thereof.

9. The method of claim 8, wherein, in a case where a number in the set of slot offsets is less than a number in the set of DCI codepoints, the mapping maps a given slot offset to a plurality of DCI codepoints.

10. The method of claim 1, wherein, 11. The method of claim 1, the mapping maps a first slot offset to a first DCI codepoint, and wherein, wherein the mapping maps a second slot offset to a second DCI codepoint, ​ wherein one or more of the first slot offset and the second slot offset are computed via a function.

12. The method of claim 1, wherein, the value configured to trigger transmission of the AP SRS is different from the DCI codepoint used to determine the slot offset.

13. The method of claim 1, wherein, The set of slot offsets includes up to 4 slot offsets for each set of SRS resources.

14. A method of operating a base station, comprising: transmitting, to a user equipment (UE), a configuration for a set of sounding reference signal (SRS) resources, the configuration including a mapping between a set of downlink control information (DCI) codepoints and a set of slot offsets in a list of slot offsets, wherein the mapping is a 1 : 1 mapping between the set of DCI codepoints and the set of slot offsets, or wherein the mapping is a 1 :N mapping that maps a DCI codepoint to a set of candidate slot offsets for at least one DCI codepoint, or wherein a number in the set of slot offsets is less than in the set of DCI codepoints; transmitting, to the UE, a DCI communication including a value configured to trigger transmission of an aperiodic sounding reference signal (AP SRS), transmission of the AP SRS being based on a slot offset indicated via the DCI codepoint of the DCI communication in accordance with the mapping; and receiving the AP SRS on the set of SRS resources in accordance with the indicated slot offset.

15. The method of claim 14, wherein, The configuration is transmitted via radio resource control (RRC) signaling.

16. The method of claim 14, wherein, the list of slot offsets supplements a slot offset field of the configuration associated with a default slot offset, or wherein the list of slot offsets incorporates the slot offset field associated with the default slot offset.

17. The method of claim 14, further comprising: transmitting a command to modify the configuration.

18. The method of claim 14, wherein, the value configured to trigger transmission of the AP SRS is different from the DCI codepoint used to determine the slot offset.

19. The method of claim 14, wherein, The set of slot offsets includes up to 4 slot offsets for each set of SRS resources.

20. A user equipment (UE) for communication, comprising: a memory; and one or more processors coupled with the memory, the one or more processors configured to cause the UE to: receive a configuration for a set of sounding reference signal (SRS) resources, the configuration including a mapping between a set of downlink control information (DCI) codepoints and a set of slot offsets in a list of slot offsets, wherein the mapping is a 1 : 1 mapping between the set of DCI codepoints and the set of slot offsets, or wherein the mapping is a 1 :N mapping that maps a DCI codepoint to a set of candidate slot offsets for at least one DCI codepoint, or wherein a number in the set of slot offsets is less than in the set of DCI codepoints; receive a DCI communication including a value configured to trigger transmission of an aperiodic sounding reference signal (AP SRS); ​ determine, based at least in part on a DCI codepoint of the DCI communication, a slot offset from the DCI communication to a set of SRS resources for the AP SRS in accordance with the mapping; and transmit the AP SRS on the set of SRS resources in accordance with the determined slot offset.

21. The UE of claim 20, wherein, The configuration is received via radio resource control (RRC) signaling.

22. The UE of claim 20, wherein, the slot offset list supplements a slot offset field of the configuration associated with a default slot offset, or wherein the slot offset list incorporates the slot offset field associated with the default slot offset.

23. The UE of claim 20, wherein, The one or more processors are further configured to cause the UE to: receive a command to modify the configuration.

24. The UE of claim 23, wherein, the command to instruct the UE to add or remove one or more entries to or from the slot offset list, or wherein the command to instruct the UE to add or remove at least one entry to or from the set of DCI codepoints, or wherein the command to instruct the UE to modify a mapping between the set of DCI codepoints and the slot offset list, or combinations thereof.

25. The UE of claim 23, wherein, the command to instruct the UE to modify the configuration for a particular bandwidth part (BWP) of a particular serving cell.

26. The UE of claim 23, wherein, The command corresponds to a medium access control command element (MAC-CE).

27. The UE of claim 20, wherein, The mapping is a 1:N mapping, and wherein the one or more processors are further configured to cause the UE to: determine availability of one or more candidate slot offsets among the set of candidate slot offsets, wherein the transmission of the AP SRS on the set of SRS resources is based on the determination to perform on an earliest available slot.

28. The UE of claim 27, wherein, The availability determination is based on a collision avoidance scheme, or a transmission priority scheme, or combinations thereof.

29. The UE of claim 20, wherein, In a case where a number of the set of slot offsets is less than a number of the set of DCI codepoints, the mapping maps a given slot offset to multiple DCI codepoints.

30. The UE of claim 20, wherein the mapping maps a first slot offset to a first DCI codepoint, and wherein the mapping maps a second slot offset to a second DCI codepoint, wherein one or more of the first slot offset and the second slot offset are computed via a function.

31. The UE of claim 20, wherein, a value configured to trigger transmission of the AP SRS is different from the DCI codepoint used to determine a slot offset.

32. The UE of claim 20, wherein, The set of slot offsets includes up to 4 slot offsets for each set of SRS resources.

33. A base station, comprising: a memory; one or more processors coupled with the memory, wherein the one or more processors are configured to cause the base station to: transmitting, to a user equipment (UE), a configuration for a set of sounding reference signal (SRS) resources, the configuration including a mapping between a set of downlink control information (DCI) codepoints and a set of slot offsets in a list of slot offsets, wherein the mapping is a 1 : 1 mapping between the set of DCI codepoints and the set of slot offsets, or wherein the mapping is a 1 :N mapping for at least one DCI codepoint mapping the DCI codepoint to a group of candidate slot offsets, or wherein a number in the set of slot offsets is less than a number in the set of DCI codepoints; transmitting, to the UE, a DCI communication including a value configured to trigger transmission of an aperiodic sounding reference signal (AP SRS), the transmission of the AP SRS based on a slot offset indicated via a DCI codepoint of the DCI communication in accordance with the mapping; and receiving the AP SRS on the set of SRS resources in accordance with the indicated slot offset.

34. The base station of claim 33, wherein, the configuration is transmitted via radio resource control (RRC) signaling.

35. The base station of claim 33, wherein the list of slot offsets supplements a slot offset field of the configuration associated with a default slot offset, or wherein the list of slot offsets incorporates the slot offset field associated with the default slot offset.

36. The base station of claim 33, wherein, the one or more processors are further configured to cause the base station to: transmit a command to modify the configuration.

37. The base station of claim 33, wherein, the value configured to trigger the transmission of the AP SRS is different from the DCI codepoint used to determine the slot offset.

38. The base station of claim 33, wherein, the set of slot offsets includes up to 4 slot offsets for each set of SRS resources.

Images