Timing advance for transmission of sounding reference signals

Abstract

Aspects relate to transmission of sounding reference signals (SRS). In some examples, a user equipment may select a timing advance to be used to transmit the SRS in a multiple transmit receive point (TRP) scenario. In some examples, the selection of the timing advance may be based on a usage associated with a set of SRS resources. In some examples, the selection of the timing advance may be based on a time domain configuration associated with a set of SRS resources.

Description

Technical Field

[0001]

[0013] The techniques discussed below relate generally to wireless communications, and more particularly, to selection of a timing advance value for sending a sounding reference signal. Background Art

[0002] A next generation wireless communication system (e.g., 5GS) may include a 5G core network and a 5G radio access network (RAN) (such as a new radio (NR)-RAN). NR-RAN supports communication via one or more cells. For example, a wireless communication device (such as a user equipment (UE)) may access a first cell of a first base station (BS) (such as a gNB) and / or access a second cell of a second base station. The base station may schedule access to the cell to support access by multiple UEs. For example, the base station may allocate different resources (e.g., time domain resources and frequency domain resources) for use by different UEs operating within the cell.

[0003] The UE may send a reference signal to the base station. For example, the UE may generate a sounding reference signal (SRS) based on a known sequence and send the SRS on resources allocated by the base station. The base station may then estimate the quality of an uplink channel from the UE based on the SRS and / or determine other information based on the SRS. The base station may use the channel estimate or other information, for example, to more efficiently allocate resources and / or specify transmission parameters for communicating on one or more channels. Summary of the invention

[0004] An overview of one or more aspects of the present disclosure is presented below to provide a basic understanding of these aspects. This summary is not an exhaustive overview of all expected features of the present disclosure, and is neither intended to identify key elements or important elements of all aspects of the present disclosure, nor is it intended to describe the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a form as a preface to a more detailed description presented later.

[0005] In some examples, a user equipment may include a transceiver, a memory, and a processor coupled to the transceiver and the memory. The processor and the memory may be configured to: receive, via the transceiver, a first configuration identifying a plurality of timing advance values. The processor and the memory may also be configured to: receive, via the transceiver, a second configuration of a first sounding reference signal (SRS) resource set. The processor and the memory may be further configured to: send, via the transceiver, a first timing advance value selected from a plurality of timing advance values ​​on a first SRS resource set based on a usage associated with the first SRS resource set or a time domain configuration associated with the first SRS resource set, a first SRS on a first SRS resource set.

[0006] In some examples, a method for wireless communication at a user equipment is disclosed. The method may include: receiving a first configuration identifying a plurality of timing advance values. The method may also include: receiving a second configuration of a first sounding reference signal (SRS) resource set. The method may also include: sending a first SRS on a first SRS resource set using a first timing advance value selected from a plurality of timing advance values ​​based on a usage associated with the first SRS resource set or a time domain configuration associated with the first SRS resource set.

[0007] In some examples, a user equipment may include a component for receiving a first configuration identifying a plurality of timing advance values. The user equipment may also include a component for receiving a second configuration of a first sounding reference signal (SRS) resource set. The user equipment may also include a component for sending a first SRS on a first SRS resource set using a first timing advance value selected from a plurality of timing advance values ​​based on a usage associated with the first SRS resource set or a time domain configuration associated with the first SRS resource set.

[0008] In some examples, a non-transitory computer-readable medium stores therein instructions that can be executed by one or more processors of a user equipment to receive a first configuration identifying a plurality of timing advance values. The computer-readable medium may also store therein instructions that can be executed by one or more processors of the user equipment to receive a second configuration of a first sounding reference signal (SRS) resource set. The computer-readable medium may further store therein instructions that can be executed by one or more processors of the user equipment to send a first SRS on a first SRS resource set using a first timing advance value selected from a plurality of timing advance values ​​based on a usage associated with the first SRS resource set or a time domain configuration associated with the first SRS resource set.

[0009] In some examples, a network entity may include a transceiver, a memory, and a processor coupled to the transceiver and the memory. The processor and the memory may be configured to: send a first configuration identifying multiple timing advance values ​​via the transceiver. The processor and the memory may also be configured to: send a second configuration of a first sounding reference signal (SRS) resource set via the transceiver. The processor and the memory may be further configured to: receive a first SRS on a first SRS resource set based on a first timing advance value among the multiple timing advance values ​​via the transceiver. In some examples, the first timing advance value is associated with a usage associated with the first SRS resource set or a time domain configuration associated with the first SRS resource set.

[0010] In some examples, a method for wireless communication at a network entity is disclosed. The method may include: sending a first configuration identifying a plurality of timing advance values. The method may also include: sending a second configuration of a first sounding reference signal (SRS) resource set. The method may also include: receiving a first SRS on a first SRS resource set based on a first timing advance value among the plurality of timing advance values. In some examples, the first timing advance value is associated with a usage associated with the first SRS resource set or a time domain configuration associated with the first SRS resource set.

[0011] In some examples, a network entity may include a component for sending a first configuration identifying a plurality of timing advance values. The network entity may also include a component for sending a second configuration of a first sounding reference signal (SRS) resource set. The network entity may also include a component for receiving a first SRS on a first SRS resource set based on a first timing advance value among the plurality of timing advance values. In some examples, the first timing advance value is associated with a usage associated with the first SRS resource set or a time domain configuration associated with the first SRS resource set.

[0012] In some examples, a non-transitory computer-readable medium stores therein instructions that can be executed by one or more processors of a network entity to send a first configuration identifying multiple timing advance values. The computer-readable medium may also store therein instructions that can be executed by one or more processors of the network entity to send a second configuration of a sounding reference signal (SRS) resource set. The computer-readable medium may further store therein instructions that can be executed by one or more processors of the network entity to receive a first SRS on a first SRS resource set based on a first timing advance value among multiple timing advance values. In some examples, the first timing advance value is associated with a usage associated with the first SRS resource set or a time domain configuration associated with the first SRS resource set.

[0013] After reading the detailed description below, these and other aspects of the present disclosure will become more fully understood. After reading the description of the specific example aspects of the present disclosure below in conjunction with the accompanying drawings, other aspects, features and examples of the present disclosure will be apparent to those of ordinary skill in the art. Although the features of the present disclosure may be discussed below with respect to certain examples and drawings, all examples of the present disclosure may include one or more of the advantageous features discussed herein. In other words, although one or more examples may be discussed as having certain advantageous features, one or more of such features may also be used according to the various examples of the present disclosure discussed herein. In a similar manner, although the example aspects may be discussed below as device, system or method examples, it should be understood that such example aspects may be implemented in various devices, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 is a schematic illustration of a wireless communication system according to some aspects.

[0015] Figure 2 is a conceptual illustration of an example radio access network in accordance with some aspects.

[0016] Figure 3 is a diagram providing a high-level illustration of one example of a configuration of a decomposed base station in accordance with some aspects.

[0017] Figure 4 is a schematic illustration of wireless resources in an air interface utilizing orthogonal frequency division multiplexing (OFDM) in accordance with some aspects.

[0018] Figure 5 is a schematic illustration of an example downlink control region of a time slot in accordance with some aspects.

[0019] Fig. 6A , Figure 6B and Figure 6C is a diagram illustrating an example uplink reference signal configuration according to some aspects.

[0020] Figure 7 is a signaling diagram illustrating an example of signaling for scheduling sounding reference signal (SRS) transmission in accordance with some aspects.

[0021] Figure 8 is an illustration of concepts of uplink timing and downlink timing according to some aspects.

[0022] Fig. 9 is a conceptual illustration of an example of timing advance signaling in accordance with some aspects.

[0023] Fig.10

[0013] A conceptual illustration of an example user equipment (UE) communicating with multiple transmit receive points (TRPs) in accordance with some aspects.

[0024] Fig.11 is an illustration of the concepts of uplink timing and downlink timing associated with multiple TRPs according to some aspects.

[0025] Fig.12 is a conceptual illustration of SRS resources according to some aspects.

[0026] Fig.13 is a flow chart illustrating an example timing advance selection method according to some aspects.

[0027] Fig.14 is a flow chart of another example timing advance selection method according to some aspects.

[0028] Fig.15 is a signaling diagram illustrating an example of signaling associated with timing advance selection in accordance with some aspects.

[0029] Fig.16 is a block diagram conceptually illustrating an example of a hardware implementation for user equipment employing a processing system in accordance with some aspects.

[0030] Fig.17 is a flow chart illustrating an example method of wireless communication involving transmitting SRS in accordance with some aspects.

[0031] Fig.18 is a block diagram conceptually illustrating an example of a hardware implementation for a network entity employing a processing system in accordance with some aspects.

[0032] Fig.19 is a flow chart illustrating an example method of wireless communications involving receiving SRS in accordance with some aspects. DETAILED DESCRIPTION

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

[0034] Although various aspects and examples are described in this application by illustrating some examples, it will be understood by those skilled in the art that additional specific implementations and use cases can be generated in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, various aspects and / or use can be generated via integrated chip examples and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, artificial intelligence (AI) enabled devices, etc.). Although some examples may or may not specifically point to use cases or applications, the applicability of a wide range of described innovations may occur. Specific implementations can range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed, or original equipment manufacturer (OEM) devices or systems in conjunction with one or more aspects of the described innovations. In some actual settings, the device incorporating the described aspects and features may also necessarily include additional components and features for the implementation and implementation of the claimed and described examples. For example, the transmission and reception of wireless signals necessarily include several components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be practiced in a variety of devices of different sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, disaggregated arrangements (e.g., base stations and / or UEs), end-user devices, etc.

[0035] Various aspects of the present disclosure relate to the transmission of a sounding reference signal (SRS).A network entity such as a base station may configure the transmission of an SRS by a user equipment (UE).

[0036] In some examples, the UE may select a timing advance to be used for sending SRS transmissions in a multiple transmit receive point (TRP) scenario. In some examples, the selection of the timing advance may be based on the type of usage associated with the SRS resource set. In some examples, the selection of the timing advance may be based on the type of time domain behavior associated with the SRS resource set.

[0037] The various concepts presented throughout this disclosure may be implemented across a wide variety of telecommunication systems, network architectures, and communication standards. Figure 1 , various aspects of the present disclosure are illustrated with reference to a wireless communication system 100 as an illustrative example and not as a limitation. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. By means of the wireless communication system 100, the UE 106 may be enabled to perform data communications with an external data network 110, such as (but not limited to) the Internet.

[0038] The RAN 104 may implement any suitable one or more wireless communication technologies to provide radio access to the UE 106. As an example, the RAN 104 may operate in accordance with the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification, commonly referred to as 5G. As another example, the RAN 104 may operate under a mix of 5G NR and an evolved universal terrestrial radio access network (eUTRAN) standard, commonly referred to as Long Term Evolution (LTE). 3GPP refers to such a hybrid RAN as the Next Generation RAN or NG-RAN. In another example, the RAN 104 may operate in accordance with both the LTE and 5G NR standards. Of course, many other examples may be utilized within the scope of the present disclosure.

[0039] As illustrated, RAN 104 includes multiple base stations 108. In a broad sense, a base station is a network element in a radio access network that is responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards or contexts, a base station may be referred to as a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a Node B (NB), an eNode B (eNB), a gNode B (gNB), a transmission and reception point (TRP) or some other suitable terminology by those skilled in the art. In some examples, a base station may include two or more TRPs that may be co-located or non-co-located. Each TRP may communicate on the same or different carrier frequencies in the same or different frequency bands. In an example where RAN 104 operates according to both LTE and 5G NR standards, one of the base stations 108 may be an LTE base station, and the other base station may be a 5G NR base station.

[0040] The radio access network 104 is further illustrated as supporting wireless communications for multiple mobile devices. The mobile device may be referred to as a user equipment (UE) 106 in the 3GPP standard, but may also be referred to as a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology by those skilled in the art. UE 106 may be a device that provides access to network services to a user. In an example where RAN 104 operates according to both LTE and 5G NR standards, UE 106 may be an evolved universal terrestrial radio access network-new radio dual connectivity (EN-DC) UE that is capable of simultaneously connecting to an LTE base station and an NR base station to receive data packets from both the LTE base station and the NR base station.

[0041] In this document, a mobile device does not necessarily have the ability to move and can be stationary. The term mobile device or mobile equipment refers to a wide variety of devices and technologies. A UE may include multiple hardware structural components whose size, shape, and arrangement facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. that are electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile devices, cellular (cell) phones, smart phones, session initiation protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smart books, tablet devices, personal digital assistants (PDAs), and a wide variety of embedded systems, for example, corresponding to the Internet of Things (IoT).

[0042] The mobile device may additionally be a car or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-rotor aircraft, a quadcopter, a remote control device, a consumer and / or wearable device (such as glasses, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, etc. The mobile device may additionally be a digital home or smart home device (such as home audio, video and / or multimedia equipment), an appliance, a vending machine, a smart lighting device, a home security system, a smart Meters, etc. The mobile device may additionally be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device that controls electrical power (e.g., a smart grid), lighting, water supply, etc., an industrial automation and enterprise device, a logistics controller, and / or agricultural equipment, etc. In addition, the mobile device may provide connected medical or telemedicine support, such as health care at a distance. Telemedicine devices may include telemedicine monitoring devices and telemedicine management devices, whose communications may be given priority or access priority over other types of information, for example, in terms of priority access for transmission of critical service data and / or associated QoS for transmission of critical service data.

[0043] The wireless communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmissions from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) over the air interface can be referred to as downlink (DL) transmissions. In some examples, the term downlink can refer to point-to-multipoint transmissions initiated at a base station (e.g., base station 108). Another way to describe this point-to-multipoint transmission scheme can be to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions. In some examples, the term uplink can refer to point-to-point transmissions originated at a UE (e.g., UE 106).

[0044] In some examples, access to the air interface may be scheduled, where a scheduling entity (e.g., a base station 108) of some other type of network entity allocates resources for communication among some or all devices and equipment within its service area or cell. Within the present disclosure, as discussed further below, a scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities (e.g., UEs). That is, for scheduled communications, multiple UEs 106 (which may be scheduled entities) may utilize resources allocated by a scheduling entity (e.g., a base station 108).

[0045] Base station 108 is not the only entity that can act as a scheduling entity. That is, in some examples, a UE can act as a scheduling entity, scheduling resources for one or more scheduled entities (e.g., one or more other UEs). For example, a UE can communicate with other UEs in a peer-to-peer or device-to-device manner and / or in a relay configuration.

[0046] like Figure 1 As illustrated, a scheduling entity (e.g., base station 108) may broadcast downlink traffic 112 to one or more scheduled entities (e.g., UE 106). Broadly speaking, a scheduling entity is a node or device responsible for scheduling traffic in a wireless communication network, including downlink traffic 112 and, in some examples, uplink traffic 116 and / or uplink control information 118 from one or more scheduled entities to the scheduling entity. On the other hand, a scheduled entity is a node or device that receives downlink control information 114, which includes, but is not limited to, scheduling information (e.g., grants), synchronization or timing information, or other control information from another entity in the wireless communication network, such as a scheduling entity.

[0047] In addition, uplink control information 118, downlink control information 114, downlink traffic 112 and / or uplink traffic 116 may be divided into frames, subframes, time slots and / or symbols by time. As used herein, a symbol may refer to a time unit in which each subcarrier carries one resource element (RE) in an orthogonal frequency division multiplexing (OFDM) waveform. In some examples, a time slot may carry 7 or 14 OFDM symbols. A subframe may refer to a duration of 1 millisecond (ms). Multiple subframes or time slots may be grouped together to form a single frame or radio frame. In the present disclosure, a frame may refer to a predetermined duration (e.g., 10ms) for wireless transmission, wherein each frame is composed of, for example, 10 subframes of 1ms each. Of course, these definitions are not required, and any suitable scheme for organizing waveforms may be utilized, and the various time divisions of waveforms may have any suitable duration.

[0048] Typically, base stations 108 may include a backhaul interface for communicating with a backhaul 120 of the wireless communication system. Backhaul 120 may provide a link between base stations 108 and core network 102. Additionally, in some examples, a backhaul network may provide interconnections between respective base stations 108. Various types of backhaul interfaces may be employed, such as a direct physical connection using any suitable transport network, a virtual network, and the like.

[0049] The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 may be configured according to 5G standards (e.g., 5GC). In other examples, the core network 102 may be configured according to 4G Evolved Packet Core (EPC) or any other suitable standard or configuration.

[0050] Reference now Figure 2 , by way of example and not limitation, a schematic illustration of a radio access network (RAN) 200 is provided. In some examples, the RAN 200 may be similar to the ones described above and in Figure 1 is the same as the RAN 104 illustrated in .

[0051] The geographic area covered by the RAN 200 may be divided into cellular regions (cells) that may be uniquely identified by user equipment (UE) based on an identity broadcast from an access point or base station. Figure 2 Cells 202, 204, 206, and 208 are illustrated, each of which may include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors within a cell are served by the same base station. A radio link within a sector may be identified by a single logical identifier belonging to the sector. In a cell divided into sectors, multiple sectors within a cell may be formed by multiple groups of antennas, each of which is responsible for communicating with a UE in a portion of the cell.

[0052] Various base station arrangements can be used. Figure 2 , two base stations 210 and 212 are shown in cells 202 and 204; and base station 214 is shown as controlling a remote radio head (RRH) 216 in cell 206. That is, the base station may have an integrated antenna, or may be connected to an antenna or RRH via a feeder cable. In the illustrated example, cells 202, 204, and 206 may be referred to as macro cells, because base stations 210, 212, and 214 support cells with larger sizes. In addition, base station 218 is shown in cell 208, which may overlap with one or more macro cells. In this example, cell 208 may be referred to as a small cell (e.g., a micro cell, a pico cell, a femto cell, a home base station, a home Node B, a home eNode B, etc.), because base station 218 supports a cell with a relatively small range. Cell size setting may be performed according to system design and component constraints.

[0053] It should be understood that the RAN 200 may include any number of wireless base stations and cells. In addition, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, 218 provide wireless access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 may be similar to those described above and in Figure 1 The base station / scheduling entity illustrated in is the same.

[0054] Figure 2 Also included is an unmanned aerial vehicle (UAV) 220, which may be a drone or a quadcopter. UAV 220 may be configured to act as a base station, or more specifically, a mobile base station. That is, in some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move depending on the location of a mobile base station (such as UAV 220).

[0055] Within the RAN 200, cells may include UEs that may communicate with one or more sectors of each cell. In addition, each base station 210, 212, 214, and 218 may be configured to provide a core network 102 (see FIG. 1 ) for all UEs in the respective cells. Figure 1 ) access point. For example, UEs 222 and 224 may communicate with base station 210; UEs 226 and 228 may communicate with base station 212; UEs 230 and 232 may communicate with base station 214 via RRH 216; and UE 234 may communicate with base station 218. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may communicate with the base stations described above and in Figure 1 In some examples, UAV 220 (e.g., a quadcopter) may be a mobile network node and may be configured to act as a UE. For example, UAV 220 may operate within cell 202 by communicating with base station 210.

[0056] In another aspect of RAN 200, sidelink signals may be used between UEs without having to rely on scheduling or control information from a base station. Sidelink communications may be utilized in a device-to-device (D2D) network, a peer-to-peer (P2P) network, a vehicle-to-vehicle (V2V) network, a vehicle-to-everything (V2X) network, and / or other suitable sidelink networks. For example, two or more UEs (e.g., UEs 238, 240, and 242) may communicate with each other using sidelink signals 237 without relaying the communication through a base station. In some examples, UEs 238, 240, and 242 may each act as a scheduling entity or a sender sidelink device and / or a scheduled entity or a receiver sidelink device to schedule resources and communicate sidelink signals 237 between them without relying on scheduling or control information from a base station. In other examples, two or more UEs (e.g., UEs 226 and 228) within the coverage area of ​​a base station (e.g., base station 212) may also communicate sidelink signals 227 via a direct link (sidelink) without routing the communication through base station 212. In this example, base station 212 may allocate resources to UEs 226 and 228 for sidelink communication.

[0057] In RAN 200, the ability for a UE to communicate while moving (independent of its location) is called mobility. This is usually done in an access and mobility management function (AMF, not shown). Figure 1 The AMF establishes, maintains and releases various physical channels between the UE and the radio access network under the control of the AMF (part of the core network 102 in the core network), where the AMF may include a security context management function (SCMF) that manages the security context of both control plane and user plane functionalities and a security anchor function (SEAF) that performs authentication.

[0058] RAN 200 may utilize DL-based mobility or UL-based mobility to implement mobility and handover (i.e., the transfer of a UE's connection from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity or at any other time, a UE may monitor various parameters of a signal from its serving cell and various parameters of neighboring cells. Based on the quality of these parameters, the UE may maintain communication with one or more neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE may perform a handover or handover from the serving cell to a neighboring (target) cell. For example, UE 224 (illustrated as a vehicle, but any suitable form of UE may be used) may move from a geographic area corresponding to its serving cell (e.g., cell 202) to a geographic area corresponding to a neighboring cell (e.g., cell 206). When the signal strength or quality from a neighboring cell exceeds the signal strength or quality of the serving cell for a given amount of time, UE 224 may send a report message indicating the condition to its serving base station (e.g., base station 210). In response, UE 224 may receive the handover command, and the UE may proceed with the handover to cell 206 .

[0059] In a network configured for UL-based mobility, the network may select a serving cell for each UE using a UL reference signal from each UE. In some examples, base stations 210, 212, and 214 / 216 may broadcast a unified synchronization signal (e.g., a unified primary synchronization signal (PSS), a unified secondary synchronization signal (SSS), and a unified physical broadcast channel (PBCH)). UEs 222, 224, 226, 228, 230, and 232 may receive a unified synchronization signal, derive carrier frequency and slot timing from the synchronization signal, and send an uplink pilot or reference signal in response to the derived timing. The uplink pilot signal sent by a UE (e.g., UE 224) may be received concurrently by two or more cells (e.g., base stations 210 and 214 / 216) within RAN 200. Each of the cells may measure the strength of the pilot signal, and the radio access network (e.g., one or more of the base stations 210 and 214 / 216 and / or a central node within the core network) may determine a serving cell for the UE 224. As the UE 224 moves through the RAN 200, the network may continue to monitor the uplink pilot signal sent by the UE 224. When the signal strength or quality of the pilot signal measured by the neighboring cell exceeds the signal strength or quality measured by the serving cell, the RAN 200 may hand over the UE 224 from the serving cell to the neighboring cell with or without notifying the UE 224.

[0060] Although the synchronization signals transmitted by base stations 210, 212 and 214 / 216 may be uniform, the synchronization signal may not identify a specific cell, but may identify a partition of multiple cells operating on the same frequency and / or using the same timing. Using partitions in a 5G network or other next generation communication network implements an uplink-based mobility framework and improves the efficiency of both the UE and the network, because the number of mobility messages that need to be exchanged between the UE and the network can be reduced.

[0061] In various specific implementations, the air interface in the RAN 200 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum typically provides exclusive use of a portion of the spectrum with the help of a mobile network operator purchasing a license from a government regulator. Unlicensed spectrum provides shared use of a portion of the spectrum without the need for a government-granted license. Although it is still generally necessary to comply with some technical rules to access the unlicensed spectrum, generally any operator or device can obtain access. Shared spectrum may fall between licensed spectrum and unlicensed spectrum, where access to the spectrum may require technical rules or restrictions, but the spectrum can still be shared by multiple operators and / or multiple radio access technologies (RATs). For example, a license holder of a portion of a licensed spectrum may provide licensed shared access (LSA) to share the spectrum with other parties (e.g., with appropriate licensee-determined conditions to obtain access).

[0062] The air interface in the RAN 200 may utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification provides multiple access for UL transmissions from UEs 222 and 224 to the base station 210, and multiplexing of DL transmissions from the base station 210 to one or more UEs 222 and 224 using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP). In addition, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also known as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and may be provided using time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource extension multiple access (RSMA) or other suitable multiple access schemes. In addition, multiplexing of DL transmissions from base station 210 to UEs 222 and 224 may be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0063] In addition, the air interface in the RAN 200 may utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link in which two endpoints can communicate with each other in two directions. Full-duplex means that two endpoints can communicate with each other at the same time. Half-duplex means that only one endpoint can transmit information to the other endpoint at a time. Half-duplex emulation is often implemented for wireless links using time division duplex (TDD). In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, at certain times, the channel is dedicated to transmissions in one direction, and at other times, the channel is dedicated to transmissions in another direction, where the direction can change very quickly, for example, several times per time slot. In wireless links, full-duplex channels generally rely on physical isolation of transmitters and receivers, and suitable interference cancellation techniques. Full-duplex emulation is often implemented for wireless links by utilizing frequency division duplex (FDD) or space division duplex (SDD). In FDD, transmissions in different directions operate at different carrier frequencies. In SDD, transmissions in different directions on a given channel are separated from each other using space division multiplexing (SDM). In other examples, full-duplex communication can be implemented in an unpaired spectrum (e.g., in a single carrier bandwidth), where transmissions in different directions occur in different sub-bands of the carrier bandwidth. This type of full-duplex communication may be referred to as sub-band full-duplex (SBFD), cross duplex (xDD), or flexible duplex.

[0064] Figure 3 A diagram illustrating an example disaggregated base station 300 architecture is shown. The disaggregated base station 300 architecture may include one or more central units (CUs) 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more distributed units (DUs) 330 via respective midhaul links, such as an F1 interface. The DU 330 may communicate with one or more radio units (RUs) 340 via respective fronthaul links. The RU 340 may communicate with respective UEs 350 via one or more radio frequency (RF) access links. In some implementations, a UE 350 may be served simultaneously by multiple RUs 340.

[0065] Each of the units (i.e., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO framework 305) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, the unit may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) configured to receive or send signals, or both, to one or more of the other units via a wireless transmission medium.

[0066] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 310 may be implemented to communicate with a distributed unit (DU) 330 for network control and signaling.

[0067] DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340. In some aspects, DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as those defined by the Third Generation Partnership Project (3GPP). In some aspects, DU 330 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 330 or with control functions hosted by CU 310.

[0068] The lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 350. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and the CU 310 in a cloud-based RAN architecture (such as a vRAN architecture).

[0069] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN such as an open eNB (O-eNB) 311 via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0070] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or communicate with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0071] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0072] Reference will be made to the OFDM waveform (an example of which is given in Figure 4 Various aspects of the present disclosure are described in detail with reference to Figure 1 (illustrated schematically in Figure 2). It should be understood by those skilled in the art that various aspects of the present disclosure can be applied to SC-FDMA waveforms in substantially the same manner as described herein below. That is, while some examples of the present disclosure may focus on OFDM links for clarity, it should be understood that the same principles can also be applied to SC-FDMA waveforms.

[0073] Reference now Figure 4 , illustrates an expanded view of an example subframe 402 showing an OFDM resource grid. However, as will be readily appreciated by those skilled in the art, the physical (PHY) layer transmission structure for any particular application may differ from the examples described herein, depending on any number of factors. Here, time is in units of OFDM symbols in the horizontal direction; and frequency is in units of subcarriers of a carrier in the vertical direction.

[0074] Resource grid 404 can be used to schematically represent the time-frequency resources for a given antenna port. In some examples, an antenna port is a logical entity for mapping a data stream to one or more antennas. Each antenna port can be associated with a reference signal (e.g., this can allow a receiver to distinguish data streams associated with different antenna ports in a received transmission). Antenna ports can be defined so that the channel on which a symbol on the antenna port is transmitted can be inferred from the channel on which another symbol on the same antenna port is transmitted. Therefore, a given antenna port can represent a specific channel model associated with a specific reference signal. In some examples, a given antenna port and a subcarrier spacing (SCS) can be associated with a corresponding resource grid (including REs as discussed above). Here, modulated data symbols from a multiple-input multiple-output (MIMO) layer can be combined and redistributed to each antenna port in the antenna port, and then pre-decoding is applied, and the pre-decoded data symbols are applied to the corresponding REs for generating and transmitting OFDM signals via one or more physical antenna elements. In some examples, the mapping of antenna ports to physical antennas can be based on beamforming (e.g., signals can be sent on certain antenna ports to form a desired beam). Thus, a given antenna port may correspond to a particular set of beamforming parameters (eg, signal phase and / or amplitude).

[0075] In a MIMO implementation with multiple available antenna ports, a corresponding number of resource grids 404 may be available for communication. Resource grid 404 is divided into multiple resource elements (REs) 406. RE (which is 1 subcarrier × 1 symbol) is the smallest discrete portion of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation utilized in a particular implementation, each RE may represent one or more bits of information. In some examples, a block of REs may be referred to as a physical resource block (PRB), or more simply a resource block (RB) 408, which contains any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB may include 12 subcarriers (a number independent of the parameter set used). In some examples, depending on the parameter set, an RB may include any suitable number of consecutive OFDM symbols in the time domain. Within the present disclosure, it is assumed that a single RB (such as RB 408) corresponds entirely to communication in a single direction (transmission or reception for a given device).

[0076] A collection of contiguous or discontinuous resource blocks may be referred to herein as a resource block group (RBG), a subband, or a bandwidth part (BWP). A collection of subbands or BWPs may span the entire bandwidth. Scheduling a scheduled entity (e.g., a UE) for downlink, uplink, or sidelink transmission typically involves scheduling one or more resource elements 406 within one or more subbands or bandwidth parts (BWPs). Thus, a UE typically utilizes only a subset of a resource grid 404. In some examples, an RB may be the smallest resource unit that may be allocated to a UE. Thus, the more RBs scheduled for a UE, and the higher the modulation scheme selected for the air interface, the higher the data rate for the UE. The RBs may be scheduled by a scheduling entity such as a base station (e.g., a gNB, an eNB, etc.), or may be self-scheduled by a UE implementing D2D sidelink communication.

[0077] In this illustration, RB 408 is shown as occupying less than the entire bandwidth of subframe 402, with some subcarriers illustrated above and below RB 408. In a given implementation, subframe 402 may have a bandwidth corresponding to any number of one or more RBs 408. Furthermore, in this illustration, RB 408 is shown as occupying less than the entire duration of subframe 402, but this is just one possible example.

[0078] Each 1 ms subframe 402 may consist of one or more adjacent time slots. Figure 4In the example shown, a subframe 402 includes four time slots 410 as an illustrative example. In some examples, a time slot may be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include micro-slots (sometimes referred to as shortened transmission time intervals (TTIs)) with shorter durations (e.g., one to three OFDM symbols). These micro-slots or shortened transmission time intervals (TTIs) may be transmitted in some cases by occupying resources that are scheduled for ongoing time slot transmissions for the same UE or different UEs. Any number of resource blocks may be utilized within a subframe or time slot.

[0079] The expanded view of one of the time slots 410 illustrates that the time slot 410 includes a control region 412 and a data region 414. In general, the control region 412 may carry control channels, and the data region 414 may carry data channels. Of course, a time slot may contain full DL, full UL, or at least one DL portion and at least one UL portion. Figure 4 The structure illustrated in is merely an example, and different time slot structures may be utilized and may include one or more of each of the control region and the data region.

[0080] Although not in Figure 4 4, but each RE 406 within an RB 408 may be scheduled to carry one or more physical channels, including a control channel, a shared channel, a data channel, etc. Other REs 406 within an RB 408 may also carry pilot signals or reference signals. These pilot signals or reference signals may allow a receiving device to perform channel estimation of the corresponding channel, which may enable coherent demodulation / detection of a control channel and / or a data channel within the RB 408.

[0081] In some examples, time slot 410 may be utilized for broadcast, multicast, groupcast, or unicast communications. For example, broadcast, multicast, or groupcast communications may refer to point-to-multipoint transmissions from one device (e.g., a base station, UE, or other similar device) to other devices. Here, broadcast communications are delivered to all devices, while multicast or groupcast communications are delivered to multiple intended receiving devices. Unicast communications may refer to point-to-point transmissions from one device to a single other device.

[0082] In an example of cellular communication on a cellular carrier via a Uu interface, for DL ​​transmission, a scheduling entity (e.g., a base station) may allocate one or more REs 406 (e.g., within a control region 412) to one or more scheduled entities (e.g., UEs) to carry DL control information including one or more DL control channels (such as a physical downlink control channel (PDCCH)). The PDCCH carries downlink control information (DCI), including but not limited to power control commands (e.g., one or more open-loop power control parameters and / or one or more closed-loop power control parameters), scheduling information, grants, and / or assignments of REs for DL ​​transmission and UL transmission. The PDCCH may further carry hybrid automatic repeat request (HARQ) feedback transmissions, such as acknowledgements (ACKs) or negative acknowledgements (NACKs). HARQ is a technique well known to those of ordinary skill in the art, wherein the integrity of packet transmissions may be checked for accuracy at the receiving side, for example, using any suitable integrity checking mechanism, such as a checksum or a cyclic redundancy check (CRC). If the integrity of the transmission is confirmed, an ACK may be sent, and if it is not confirmed, a NACK may be sent. In response to the NACK, the transmitting device may transmit a HARQ retransmission, which may implement chase combining, incremental redundancy, and the like.

[0083] The base station may further allocate one or more REs 406 (e.g., in the control region 412 or the data region 414) to carry other DL signals, such as a demodulation reference signal (DMRS); a phase tracking reference signal (PT-RS); a channel state information (CSI) reference signal (CSI-RS); and a synchronization signal block (SSB). The SSB may be broadcast at regular intervals based on a periodicity (e.g., 5ms, 10ms, 20ms, 30ms, 80ms, or 130ms). The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast control channel (PBCH). The UE may use the PSS and SSS to achieve radio frame, subframe, time slot, and symbol synchronization in the time domain, identify the center of the channel (system) bandwidth in the frequency domain, and identify the physical cell identity (PCI) of the cell.

[0084] The PBCH in the SSB may also include a master information block (MIB) containing various system information and parameters for decoding a system information block (SIB). The SIB may be, for example, SystemInformationType 1 (SIB1), which may include various additional (remaining) system information. The MIB and SIB1 together provide minimum system information (SI) for initial access. Examples of system information sent in the MIB may include, but are not limited to, subcarrier spacing (e.g., default downlink parameter set), system frame number, configuration of the PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), cell barring indicator, cell reselection indicator, grid offset, and search space for SIB1. Examples of remaining minimum system information (RMSI) sent in SIB1 may include, but are not limited to, random access search space, paging search space, downlink configuration information, and uplink configuration information. The base station may also send other system information (OSI).

[0085] In UL transmission, the UE may utilize one or more REs 406 to carry UL control information (UCI) to the scheduling entity, and the UL control information (UCI) includes one or more UL control channels, such as a physical uplink control channel (PUCCH). The UCI may include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmission. Examples of uplink reference signals may include sounding reference signals (SRS) and uplink DMRS. In some examples, the UCI may include a scheduling request (SR), i.e., requesting the scheduling entity to schedule uplink transmission. In this article, in response to the SR sent on the UCI, the scheduling entity may send downlink control information (DCI), which may schedule resources for uplink packet transmission. The UCI may also include HARQ feedback, channel state feedback (CSF) (such as CSI report), or any other suitable UCI.

[0086] In addition to control information, one or more REs 406 (e.g., within the data region 414) may also be allocated for data traffic. Such data traffic may be carried on one or more traffic channels, such as for DL ​​transmissions, on a physical downlink shared channel (PDSCH); or for UL transmissions, on a physical uplink shared channel (PUSCH). In some examples, one or more REs 406 within the data region 414 may be configured to carry other signals, such as one or more SIBs and DMRS.

[0087] In an example of sidelink communication on a sidelink carrier via a proximity service (ProSe) PC5 interface, a control region 412 of a time slot 410 may include a physical sidelink control channel (PSCCH) including sidelink control information (SCI) sent by an initiator (transmitter) sidelink device (e.g., a transmitting (Tx) side V2X device or other Tx UE) toward a set of one or more other receiving sidelink devices (e.g., a receiving (Rx) side V2X device or some other Rx UE). A data region 414 of the time slot 410 may include a physical sidelink shared channel (PSSCH) including sidelink data traffic sent by the initiator (transmitter) sidelink device within resources reserved by the transmitting sidelink device on the sidelink carrier via the SCI. Other information may be further sent through various REs 406 within the time slot 410. For example, the HARQ feedback information may be sent from the receiving side link device to the transmitting side link device in a physical sidelink feedback channel (PSFCH) within time slot 410. Additionally, one or more reference signals may be sent within time slot 410, such as a sidelink SSB, a sidelink CSI-RS, a sidelink SRS, and / or a sidelink positioning reference signal (PRS).

[0088] These physical channels described above are typically multiplexed and mapped to transport channels for handling at the medium access control (MAC) layer. The transport channels carry blocks of information called transport blocks (TBs). Based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission, the transport block size (TBS), which may correspond to the number of information bits, may be a controlled parameter.

[0089] References Figures 1 to 4 The channels or carriers described are not necessarily all channels or carriers that may be utilized between a scheduling entity and a scheduled entity, and one of ordinary skill in the art will recognize that other channels or carriers may be utilized in addition to those illustrated, such as other traffic, control, and feedback channels.

[0090] As mentioned above, the base station may use the downlink control region of the time slot to transmit PDCCH information to the UE. In some examples, the PDCCH information may be a scheduled DCI that schedules downlink transmissions to the UE, a scheduled DCI that schedules uplink transmissions of the UE, or a scheduled DCI that schedules some other transmission. In some examples, the PDCCH information may be a non-scheduled DCI (e.g., a DCI that carries information but does not schedule transmissions). Figure 5 and FIG. 6 depict example resource configurations that may be used to carry such PDCCH information.

[0091] Figure 5is a schematic illustration of an example of a downlink (DL) control region 502 of a time slot according to some aspects. The DL control region 502 may correspond to, for example, Figure 4 The illustrated control region 412 of the time slot 410. As discussed above, the DL control region 502 may carry a PDCCH including one or more DCIs.

[0092] The DL control region 502 includes a plurality of CORESETs 504 indexed as CORESET#1-CORESET#N. Each CORESET 504 includes a plurality of subcarriers in the frequency domain and one or more symbols in the time domain. Figure 5 In the example of FIG. 5 , each CORESET 504 includes at least one control channel element (CCE) 506, the CORESET having both frequency and time dimensions, and being sized to span at least three OFDM symbols. A CORESET 504 having a size spanning two or more OFDM symbols may be beneficial for use on a relatively small system bandwidth (e.g., 5 MHz). However, a one-symbol CORESET may be used in some scenarios.

[0093] In some examples, the base station may be configured with a CORESET 504 for carrying group common control information or UE-specific control information, whereby the CORESET 504 may be used to send a PDCCH including the group common control information or UE-specific control information to one or more UEs. Each UE may be configured to monitor one or more CORESETs 504 to obtain UE-specific control information or group common control information (e.g., on a PDCCH).

[0094] In some examples, the PDCCH may be constructed from a variable number of CCEs depending on the PDCCH format (e.g., aggregation level). Each PDCCH format (e.g., aggregation level) supports a different DCI length. In some examples, PDCCH aggregation levels of 1, 2, 4, 8, and 16 corresponding to 1, 2, 4, 8, or 16 consecutive CCEs, respectively, may be supported.

[0095] A bandwidth part (BWP) may be defined within a carrier bandwidth (CBW). According to some aspects, a BWP is a set of contiguous physical resource blocks (PRBs) on a given carrier. A contiguous set of PRBs may correspond to a contiguous set of CCEs. In some examples, a BWP corresponds to a set of 64 PRBs representing 648 subcarriers (i.e., 12 RE / REGs x 6 REG / CCEs x 9 CCEs). A network entity may configure different sets of these CCEs as common CCEs or UE-specific CCEs.

[0096] In some examples, a CORESET may include 48 REGs in a set of eight CCEs. The eight CCEs may be grouped into a first DCI. The following relationship between a CORESET, a BWP, and a search space is made with reference to some examples of NR; however, the following are examples and are non-limiting, and other relationships between a CORESET, a BWP, and a search space (or their equivalents in other radio technologies, for example) are within the scope of the present disclosure. In some examples, for a given UE, a base station may configure up to five CORESETs in a BWP of a serving cell (e.g., a component carrier (CC)), including both a common CORESET and a UE-specific CORESET. In addition, a base station may configure up to four BWPs per serving cell, with one or more of the BWPs being active at a given time. The resource elements of a CORESET may be mapped to one or more CCEs.

[0097] As mentioned above, the UE may send a sounding reference signal, which the receiving device (e.g., a network entity in some examples) may use for various purposes, such as channel estimation, positioning, codebook generation, cross-link interference measurement, and beam selection. For example, for a channel estimation operation, the UE may send an SRS to the network entity over a specified bandwidth to enable the network entity to estimate the uplink channel over the bandwidth. In this way, the network entity may better schedule transmissions from the UE (e.g., the network entity may select a frequency band and transmission parameters for the UE to use for uplink transmissions).

[0098] In some aspects, the present disclosure relates to the transmission of a sounding reference signal (SRS). A network entity may send SRS configuration information to a UE, the SRS configuration information specifying SRS resources and other parameters to be used by the UE to transmit the SRS. For example, the network entity may configure one or more SRS resource sets for the UE. In some examples, the UE may use different resource sets for transmission on different symbols. A defined number of antenna ports may be used for each SRS resource.

[0099] In some examples, an antenna port is a logical entity for mapping a data stream to one or more antennas. Each antenna port may be associated with a reference signal (e.g., this may allow a receiver to distinguish data streams associated with different antenna ports in a received transmission). For example, logical antenna ports 1000-1999 may be used for SRS transmission in some networks. Antenna ports may be defined so that the channel on which a symbol on an antenna port is transmitted may be inferred from the channel on which another symbol on the same antenna port is transmitted. Thus, a given antenna port may represent a specific channel model associated with a particular reference signal. In some examples, a given antenna port and subcarrier spacing (SCS) may be associated with a corresponding resource grid (including REs as discussed above). Here, the modulated data symbols from the MIMO layer may be combined and redistributed to each antenna port in the antenna port, and then pre-decoding is applied, and the pre-decoded data symbols are applied to the corresponding REs for generating and transmitting OFDM signals via one or more physical antenna elements.

[0100] In some examples, the mapping of antenna ports to physical antennas may be based on beamforming (e.g., signals may be sent on certain antenna ports to form a desired beam). Thus, a given antenna port may correspond to a specific set of beamforming parameters (e.g., signal phase and / or amplitude).

[0101] As mentioned above, a network entity may configure multiple SRS resource sets for SRS transmission by a UE. Each SRS resource set may be configured to be periodic, aperiodic or semi-persistent, so that each of the SRS resources in the corresponding SRS resource set is periodic, aperiodic or semi-persistent, respectively. Each SRS resource includes a set of SRS resource parameters that configure the SRS resource. For example, the SRS resource parameters may include an antenna port set (e.g., an uplink beam), the number of consecutive symbols, time domain allocation, repetition, a transmit comb structure, bandwidth, and other suitable parameters. Each SRS may further be quasi-co-located (QCL) with another reference signal (such as an SSB, CSI-RS, or SRS). The corresponding SRS resource parameter set for each SRS resource in the SRS resources in a particular SRS resource set together forms the SRS resource set parameters of the SRS resource set. In addition, the SRS resource set itself may also include additional SRS resource set parameters.

[0102] The transmission of the uplink SRS may occur periodically (e.g., configured by the base station via radio resource control (RRC) signaling), semi-persistently (e.g., configured by the base station via RRC signaling and activated / deactivated via medium access control-control element (MAC-CE) signaling), or aperiodically (e.g., triggered by the base station via downlink control information (DCI)). The SRS resource set parameters of the aperiodic SRS resource set may include an aperiodic triggering state (e.g., code point) of the aperiodic SRS resource set (e.g., up to three triggering states may be possible in some cases, each triggering state being mapped to an aperiodic SRS resource set), a time slot including the DCI that triggers the aperiodic SRS resource and a time slot offset between SRS transmission (e.g., the SRS is transmitted k time slots after the time slot carrying the DCI containing the triggering state), and a CSI-RS resource identifier (CRI) associated with the aperiodic SRS resource set for pre-decoder estimation of the aperiodic SRS. As another example, the SRS configuration of a periodic SRS resource set or a semi-persistent SRS resource set may indicate the periodicity of SRS resources (eg, the periodicity of SRS transmission).

[0103] For sidelink SRS transmission, a sidelink SRS resource set, such as a set of symbols in a sidelink time slot or a full sidelink time slot, may be allocated for SL-SRS transmission. SL-SRS transmission may be independent of any data transmission and may be periodic, semi-persistent, or aperiodic. In an example in which SL-SRS transmission is periodic, a SL-SRS periodicity between consecutive SL-SRS transmissions of a transmitting device (e.g., a Tx sidelink device) may be defined. For example, SL-SRS periodicity may be defined via semi-persistent scheduling (SPS) signaling, radio resource control (RRC) signaling, medium access control (MAC) control element (MAC-CE), or other suitable signaling.

[0104] Fig. 6A , Figure 6B and Figure 6C is a diagram illustrating an example uplink reference signal configuration according to some aspects. FIG. 6A to FIG. 6C The uplink reference signal configuration shown in each of the figures in FIG. 5 may correspond to a single individual reference signal configuration, which may be combined with one or more other reference signal configurations to produce a combined reference signal configuration. FIG. 6A to FIG. 6CExample SRS configurations 600a-600c of SRS resource sets 602a-602c are illustrated according to some aspects, each SRS resource set including SRS resources 604a-604f. An SRS resource set may include one or more SRS resources. For example, SRS resource set 602a (SRS resource set 0) includes SRS resources 604a and 604b (SRS resource 0.0 and SRS resource 0.1), SRS resource set 602b (SRS resource set 1) includes SRS resource 604c (SRS resource 1.0), and SRS resource set 602c (SRS resource set 2) includes SRS resource sets 604d, 604e, and 604f (SRS resource 2.0, SRS resource 2.1, and SRS resource 2.2).

[0105] As in FIG. 6A to FIG. 6C As indicated in , multiple SRS resource sets 602a-602c for the UE may be configured. In addition, each SRS resource set 602a-602c may be configured as periodic, aperiodic, or semi-persistent, so that each of the SRS resources in the corresponding SRS resource set is periodic, aperiodic, or semi-persistent, respectively. For example, SRS resources 604a and 604b within SRS resource set 602a may be periodic SRS resources, SRS resource 604c within SRS resource set 602b may be aperiodic SRS resource, and SRS resources 604d-604f within SRS resource set 602c may be semi-persistent SRS resources.

[0106] Each SRS resource 604a-604f includes a set of SRS resource parameters that configure the SRS resource. For example, the SRS resource parameters may include an antenna port set, the number of consecutive symbols (Nsymb), a time domain allocation (Ioffset), repetition, a transmit comb structure (kTC), a bandwidth (mSRS), and other suitable parameters. Each SRS may further be quasi-co-located (QCL) with another reference signal (such as SSB, CSI-RS, or SRS). Therefore, based on the quasi-co-located (QCL) association (e.g., with an SSB beam, a CSI-RS beam, or an SRS beam), the SRS resource may be sent using the same spatial domain filter (e.g., beam) as used to receive / send the indicated reference signal (e.g., SSB beam, CSI-RS beam, or SRS beam). Each SRS resource 604a-604f may be further indexed by a corresponding reference signal resource (ID). The reference signal resource ID may not only identify a specific beam and port, but also identify the resource on which the reference signal may be measured. For example, the reference signal resource ID may include an SRS resource indicator (SRI). FIG. 6A to FIG. 6CIn the example shown in , each SRS resource 604a-604f is indexed by a corresponding SRI (e.g., SRI-1, SRI-2, SRI-3, SRI-4, SRI-5, and SRI-6). Since each SRI identifies a corresponding beam, each SRI corresponds to a beam identifier (ID).

[0107] The corresponding SRS resource parameter set for each SRS resource in the SRS resources in a particular SRS resource set together forms the SRS resource set parameters of the SRS resource set. In addition, the SRS resource set itself may also include additional SRS resource set parameters. For example, the SRS resource set parameters of the aperiodic SRS resource set 602b may also include the aperiodic trigger state (e.g., code point) of the aperiodic SRS resource set 602b (e.g., up to three trigger states may be possible, each trigger state mapping to the aperiodic SRS resource set), the time slot including the DCI that triggers the aperiodic SRS resource and the time slot offset between the SRS transmission (e.g., the SRS is transmitted k time slots after the time slot carrying the DCI containing the trigger state), and the CRI associated with the aperiodic SRS resource set 602b for the pre-decoder estimation of the aperiodic SRS. As another example, the SRS configuration of the periodic SRS resource set 602a or the semi-persistent SRS resource set 602c may indicate the periodicity of the SRS resource (e.g., the periodicity of the SRS transmission). The corresponding SRS resource set parameters then collectively form an SRS configuration 600a-600c for the corresponding SRS resource set 602a-602c.

[0108] The network entity may semi-statically configure one or more SRS resource sets 602a-602c to the UE via, for example, radio resource control (RRC) signaling. In some examples, the network entity may send an RRC message including an RRC configuration (e.g., an RRC configuration information element (IE)) indicating an SRS configuration for a particular SRS resource set.

[0109] For example, the network entity may semi-statically configure one or more periodic SRS resource sets 602a to the UE, and the UE may use the one or more periodic SRS resource sets to generate a periodic SRS and send it to the network entity. As another example, the network entity may semi-statically configure one or more aperiodic SRS resource sets 602b and corresponding triggering states to the UE. The network entity may then use DCI to trigger the aperiodic SRS resource set 602b. As another example, the network entity may semi-statically configure one or more semi-persistent SRS resource sets 602c to the UE. The network entity may then use a medium access control (MAC) control unit (MAC-CE) to activate or deactivate the semi-persistent SRS resource set 602c.

[0110] Figure 7 7 is a signaling diagram 700 illustrating an example of scheduling SRS transmission in a wireless communication system including a scheduling entity (eg, a base station) 702 and a user equipment (UE) 704. In some examples, the scheduling entity 702 may correspond to Figure 1 , Figure 2 , Figure 3 , Figure 8 , Fig. 9 , Fig.15 and Fig.18 In some examples, the user equipment 704 may correspond to any of the base stations, CUs, DUs, RUs, or scheduling entities shown in any of the figures. Figure 1 , Figure 2 , Figure 3 , Figure 8 , Fig. 9 , Fig.15 and Fig.16 Any one of the UEs or scheduled entities shown in any of the figures.

[0111] exist Figure 7 At 706, the scheduling entity 702 selects resources for SRS transmission by the user equipment 704. For example, the scheduling entity 702 may allocate resources for different SRS resource sets at different BWPs in different cells. As another example, the scheduling entity 702 may allocate SL-SRS resources.

[0112] At 708, the scheduling entity 702 configures SRS transmission for the user equipment 704. For example, for uplink SRS transmission, the scheduling entity 702 (e.g., a base station) may transmit an RRC message or some other type of message to the user equipment 704, where the message specifies resources and other information that the user equipment 704 will use for SRS transmission.

[0113] For sidelink SRS transmission, the scheduling entity 702 (e.g., a scheduling sidelink UE or base station) may allocate resources for SL-SRS transmission from a user equipment 704 (e.g., a sidelink UE) to the scheduling entity 702 or another sidelink UE. In some examples, a resource set may be configured via an RRC message, and a DCI or other signaling may be used to activate SRS transmission (e.g., for non-periodic SRS resources). In some examples, the scheduling entity 702 may send an SL-SRS request indicating the allocated periodic, non-periodic, or semi-persistent SL-SRS resources. In some examples, the SL-SRS resources may be configured via an RRC message, and the SL-SRS request may be included in an SCI or MAC-CE to activate the SL-SRS resources (e.g., periodic SL-SRS resources).

[0114] At 710, the user equipment 704 identifies scheduled resources for SRS transmission. For example, for uplink SRS transmission, the user equipment 704 may identify periodic, aperiodic, or semi-persistent SRS resources within a corresponding SRS resource set. For sidelink SRS transmission, the user equipment 704 may identify periodic, aperiodic, or semi-persistent SL-SRS resources indicated in the SL-SRS request.

[0115] At optional 712 , in some examples, DCI or other signaling may be used to trigger or activate SRS transmission (eg, aperiodic SRS) at user equipment 704 .

[0116] At 714, the user equipment 704 transmits an SRS transmission on the scheduled resources. For example, for uplink SRS transmission, the user equipment 704 (e.g., UE) may transmit the SRS to the scheduling entity 702 (e.g., base station). For sidelink SRS transmission, the user equipment 704 (e.g., scheduled sidelink UE) may transmit the SRS to the scheduling entity 702 (e.g., sidelink UE) or to another sidelink UE (not in the scheduling entity 702). Figure 7 For triggered or activated SRS transmission, the user equipment 704 transmits SRS transmission according to the trigger or the activation (eg, indicated by MAC-CE, DCI, etc.).

[0117] At 716, the scheduling entity 702 processes the SRS transmission received at 714. For example, the scheduling entity 702 may estimate a channel between the scheduling entity 702 and the user equipment 704, estimate a positioning of the user equipment 704, generate a codebook for communication with the user equipment 704, estimate cross-link interference for communication with the user equipment 704, or select a beam for communication with the user equipment 704.

[0118] In some examples, the SRS transmission may be a subband transmission, where the SRS is transmitted on one or more subbands of the allocated SRS bandwidth. For example, the scheduling entity may configure the scheduled entity to use frequency hopping to transmit the SRS on different subbands. In some examples, the scheduling entity may configure a hopping scheme for each SRS resource set for the scheduled entity. For frequency hopping, the SRS bandwidth may refer to the total bandwidth that will be hopped across all hops (e.g., during a time slot, a set of time slots, a set of symbols, or some other time span). For example, an SRS bandwidth configuration set (C SRS ), which targets C SRS Different values ​​of specify different SRS hopping bandwidth values ​​for different RB groups (e.g., 4 RBs per hop, 8 RBs per hop, etc.). Therefore, the scheduling entity may transmit an SRS bandwidth configuration (e.g., a specific C SRSvalue) to configure the SRS transmission by the scheduled entity.

[0119] In various examples, the SRS transmission may be a codebook-based transmission or a non-codebook-based transmission. In some examples, for non-codebook-based SRS transmission, the UE may determine a pre-decoder matrix for SRS transmission based at least in part on a PUSCH pre-decoder. In some examples, for codebook-based SRS transmission, the UE may determine a pre-decoder matrix for SRS transmission based at least in part on a specified subset of a configured codebook. In some aspects, a codebook may map a set of values ​​(e.g., zero, one, etc.) to another set of values ​​(e.g., a set of complex values) for transmission. The UE may select a specific codebook subset to be used based on, for example, the number of antenna ports and / or the number of MIMO layers to be used for SRS transmission.

[0120] For uplink transmissions such as SRS transmissions, 5G NR uplink allows uplink intra-cell orthogonality so that uplink transmissions received from different devices within a cell do not interfere with each other. A feature for this uplink orthogonality is that the uplink slot boundaries for a given set of parameters are (approximately) time-aligned at the base station. To ensure this receiver-side time alignment, 5G NR includes a mechanism for sending a timing advance (TA) signal or indication.

[0121] Typically, a timing advance is a negative offset applied at a wireless device (e.g., UE) between the start of a downlink (DL) symbol (or subframe) and the start of a symbol in the uplink (UL) as observed by the device. By appropriately controlling the offset for each device, the network (e.g., base station or gNB) can control the timing of signals received at the base station or gNB from various devices (UEs) in the cell being served. Devices located far from the base station experience larger propagation delays and, therefore, should start their uplink transmissions slightly earlier than devices located closer to the base station, which have smaller propagation delays.

[0122] Figure 8 An example 800 of downlink timing and uplink timing is illustrated. In this example, a first UE (UE 1) is positioned closer to the gNB than a second UE (UE 2). Time-aligned downlink transmissions and uplink transmissions are illustrated relative to time t1 802 representing a subframe boundary at a network entity.

[0123] As represented by downlink subframe 804 (designated as downlink subframe #n in this example), transmission of downlink subframes at the network entity begins at time t1 802. Downlink subframe 806 represents delayed reception of downlink subframe 804 at a first UE (UE 1). Subframe 806 is received at the first UE (UE 1) after a propagation delay δ1 808, as indicated.

[0124] In some aspects, it may be desirable to receive an uplink transmission at a network entity time that is aligned with a subframe boundary of the network entity. To this end, based on a timing advance command received from the network entity, the first UE (UE 1) will transmit an uplink subframe 810 at a time that is a propagation delay δ1 prior to the subframe boundary of the network entity. Uplink subframe 812 represents a delayed reception of uplink subframe 810 at the network entity. As indicated, the uplink subframe is received in a time-aligned manner with a subframe boundary of the network entity. For convenience, the transmission of the uplink subframe is depicted relative to time t1 802. However, it should be understood that in a half-duplex system, the relative subframe boundary for the uplink transmission will be later in time than time t1 802.

[0125] Figure 8 It is further illustrated that the propagation delay δ2 from the network entity to the second UE (UE 2) is less than the propagation delay δ1 due to the second UE (UE 2) being closer to the network entity than the first UE (UE 1). Downlink subframe 814 represents delayed reception of downlink subframe 804 at the second UE (UE 2). As indicated, subframe 814 is received at the second UE (UE 2) after a propagation delay δ2 816.

[0126] Based on the timing advance command received from the network entity, the second UE (UE 2) will transmit an uplink subframe 818 at a time that is a propagation delay δ2 prior to the subframe boundary of the network entity. Uplink subframe 820 represents the delayed reception of uplink subframe 818 at the network entity. As indicated, the uplink subframe is received in time alignment with the subframe boundary of the network entity. For convenience, the transmission of the uplink subframe is again depicted relative to time t1 802. However, it should be understood that in a half-duplex system, the relative subframe boundary for the uplink transmission will be later in time than time t1 802.

[0127] In some wireless communication systems, each serving cell (e.g., CC) may be associated with a timing advance group (TAG). In some aspects, a TAG may be used to associate multiple cells with the same UL timing advance value. Table 1 illustrates an example of a TAG configuration for a serving cell, where the serving cell is assigned a specific TAG identifier (TAG ID). In some examples, a serving cell may be configured with one of four possible TAG identifiers (TAG IDs).

[0128]

[0129] Table 1

[0130] MAC-CE or some other type of signaling may be used to indicate the TA command per TAG. For example, Fig. 9 The MAC-CE 902 is illustrated as including a TAG ID field 904 carrying an identifier of a particular TAG and a timing advance command field 906 carrying timing advance information associated with the particular TAG.

[0131] As mentioned above, the UE may communicate with the network via one or more Transmit Receiving Points (TRPs). Fig.10 A communication system 1000 is illustrated in which a user equipment (UE) 1002 communicates with at least one TRP 1004 and at least one TRP 1006 via a first link 1008 and a second link 1010, respectively. For example, a first transmit receive (TX / RX) chain 1012 of UE 1002 may communicate with a first TRP 1004 via a first link 1008 (e.g., uplink and downlink). Additionally, a second TX / RX chain 1014 of UE 1002 may communicate with a second TRP 1006 via a second link 1010 (e.g., uplink and downlink). In different implementations, TRP 1004 may be a single TRP or a set of TRPs. Similarly, TRP 1006 may be a single TRP or a set of TRPs. Additionally, TRPs 1004 and 1004 may be associated with the same cell or different cells.

[0132] In some aspects, a TRP may refer to a physical entity that incorporates RU functionality for a particular physical cell. In one or more aspects, the functionality may be similar to the RU functionality of a NodeB, eNodeB, gNodeB, radio network controller (RNC), base station (BS), radio base station (RBS), base station controller (BSC), base transceiver station (BTS), transceiver function (TF), radio transceiver, radio router, basic service set (BSS), extended service set (ESS), macro cell, macro node, home eNB (HeNB), or some other similar entity.

[0133] As discussed above, Fig.10 The TRPs 1004 and 1006 of the present invention may operate under the control of one or more network entities 1016. For example, the TRPs 1004 and 1006 may be controlled by a single DU. As another example, the TRP 1004 may be controlled by a first DU and the TRP 1006 may be controlled by a second DU. In addition, the TRPs 1004 and 1006 may be controlled by a single CU or different CUs.

[0134] In a multi-TRP scenario (e.g. Fig.10 UEs operating in the embodiment of the present invention may be scheduled in different ways in different implementations. In some examples, a single DCI is used to schedule uplink or downlink transmissions for a UE via a TRP. For example, the DCI may schedule a first set of MIMO layers on a first TRP and a second set of MIMO layers on a second TRP.

[0135] In other examples, for a multi-TRP scenario, multiple DCIs may be used. In such a multi-DCI scenario, a first DCI may be used to schedule uplink or downlink transmission for a UE via a first TRP, and a second DCI may be used to schedule uplink or downlink transmission for a UE via a second TRP.

[0136] In some wireless communication systems, multi-TRP scenarios can be supported by using a pool of control resource sets. Here, the control resource sets (e.g., 5 CORESETs) allocated for a given BWP and component carrier (CC) can be grouped into different groups according to the control resource set pool index (CORESETPoolIndex). For example, a first subset of control resource sets (e.g., 3 CORESETs) can be assigned to CORESETPoolIndex 0, and a second subset of control resource sets (e.g., 2 CORESETs) can be assigned to CORESETPoolIndex 1. Here, CORESETPoolIndex is effectively a TRP ID (e.g., CORESETPoolIndex0 can correspond to TRP 1 and CORESETPoolIndex 1 can correspond to TRP 2).

[0137] In some examples, channels / signals (e.g., PUCCH, PUSCH, SRS, etc.) may be associated with a CORESETPoolIndex value. For example, when a UE receives DCI on a CORESET associated with CORESETPoolIndex 0, the UE may determine that the DCI is from TRP 1. As another example, RRC configuration may be used to associate a specific channel with a specific CORESETPoolIndex value.

[0138] Therefore, in some examples, a multi-DCI based multi-TRP scenario can be configured for a BWP / CC by configuring two CORESETPoolIndex values ​​(values ​​0 and 1) for CORESET in the BWP / CC. In addition, in some examples, two TAs in one CC can be associated with two CORESETPoolIndex values, respectively. For example, because the propagation delay from the UE to different TRPs may be different, two TAs can be used. Therefore, the UE can be configured to use different TA values ​​for different TRPs.

[0139] Fig.11 Diagram 1100 illustrates an example of uplink (UL) timing and downlink (DL) timing between a UE and two TRPs (TRP 1 and TRP 2). A first message 1102 illustrates the DL timing at TRP 1 and TRP 2. As indicated, the DL timing for TRP 1 and TRP 2 may be synchronized in this example (while it may not be synchronized in other examples).

[0140] The second message 1104 illustrates the DL timing associated with TRP 1 at the UE. The propagation delay from TRP 1 to the UE is represented by line 1106. The third message 1108 illustrates the DL timing associated with TRP 2 at the UE. The propagation delay from TRP 2 to the UE is represented by line 1110. Here, it can be seen that these propagation delays are different.

[0141] With respect to uplink timing, the fourth message 1112 illustrates the UL timing associated with TRP 1 at the UE. Here, to ensure that the fourth message 1112 (UL message) is received at TRP 1 at the appropriate time, the UE may transmit the fourth message 1112 to TRP 1 some amount of time (represented by line 1114) before the second message 1104 (DL message). The fifth message 1116 illustrates the UL timing associated with TRP 2 at the UE. Here, to ensure that the fifth message 1116 (UL message) is received at TRP 2 at the appropriate time, the UE may transmit the fifth message 1116 to TRP 2 some amount of time (represented by line 1118) before the third message 1108 (DL message). Thus, it can be seen that the UE may use different timing advance values ​​when transmitting to different TRPs.

[0142] Given the relationship between TRP and CORESETPoolIndex values ​​discussed above, the UE may use different timing advance values ​​when transmitting channels / signals associated with different CORESETPoolIndex values. To address this issue, two frameworks are described herein.

[0143] The first framework (frame 1) uses two TAGs in the CC. A CC configured with two CORESETPoolIndex values ​​is configured with two TAG IDs, and the two TAs in the CC are associated with the two TAGs. In this case, an association between each UL signal / channel and a TAG ID (of the two TAG IDs) may be defined to determine the TA value used for transmission of the signal / channel.

[0144] The second framework (framework 2) uses one TAG in the CC. Here, each CC may be configured with one TAG ID. However, a CC configured with two CORESETPoolIndex values ​​may be configured to determine the second TA value relative to the first TA value. For example, the first TA may be associated with the one TAG, and the second TA is set equal to the first TA + ΔTA, where ΔTA may be determined based on UE measurements or based on network entity (e.g., gNB) signaling. Similarly, an association between each UL signal / channel and one of the two TA values ​​may be defined to determine the TA value used for the transmission of a particular signal / channel.

[0145] In some aspects, the present disclosure relates to techniques for determining an association between an SRS and one of the two configured TA values. The association may be defined in the context of framework 1 (two TAG-IDs configured for a CC) and / or framework 2 (one TAG and two TAs).

[0146] Before discussing these techniques, SRS resources and SRS resource sets (e.g., FIG. 6A to FIG. 6C The SRS resource is configured in an SRS resource set consisting of one or more SRS resources. This configuration mechanism simplifies activation (for semi-persistent SRS) and DCI triggering (for aperiodic SRS) since multiple resources can be activated / triggered simultaneously. The "resourceType" (RRC configuration per SRS resource set) can be configured as aperiodic, semi-persistent, or periodic, which determines the time domain behavior of the SRS.

[0147] The "usage" parameter of the SRS resource set may be configured as one of the following: {beamManagement, codebook, nonCodebook, antennaSwitching}. In some examples, the SRS resource set is configured via the srs-ResourceSetToAddModList parameter. For codebook-based (CB) UL, in some examples, the UE may be configured with only one SRS resource set with "usage" set to "codebook". For non-codebook-based (NCB) UL, in some examples, the UE may be configured with only one SRS resource set with "usage" set to "noncodebook".

[0148] In some examples, another (second) list of SRS resource sets may be configured via srs-ResourceSetToAddModListDCI-0-2 associated with DCI format 0_2. For "usage" set to "codebook" or "noncodebook", in some examples, only one SRS resource set may be configured in the second list. The SRS resources in the SRS resource set in the second list are a subset of the SRS resources in the SRS resource set in the first list.

[0149] In some examples, for the first list (srs-ResourceSetToAddModList) or the second list (srs-ResourceSetToAddModListDCI-0-2), for "usage" set to "codebook" or "noncodebook", two SRS resource sets may be configured in the list. The first SRS resource set is the resource set with a lower SRS resource set ID in the list (associated with the first TRP), and the second SRS resource set is the resource set with a higher SRS resource set ID in the list (associated with the second TRP). The first SRS resource set of the second list is a subset of the first SRS resource set of the first list, and the second SRS resource set of the second list is a subset of the second SRS resource set of the first list. In some aspects, the above examples apply to the context of multi-TRP PUSCH repetition based on a single DCI (e.g., for indicating SRS resources associated with PUSCH repetition).

[0150] In some examples, a similar framework may be used for multi-DCI based PUSCH operation. In the case of the first list or the second list, the first SRS resource set (with the lower ID) is associated with a CORESETPoolIndex value of 0 (first TRP), and the second SRS resource set (with the higher ID) is associated with a CORESETPoolIndex value of 1 (second TRP).

[0151] Fig.12 Figure 1200 illustrates an example of the above relationship between SRS resources in different lists. The first list associated with DCI format 0_1 ​​includes a first SRS resource set 1202 and a second SRS resource set 1204. The first SRS resource set 1202 has an SRS resource ID = 2, and the second SRS resource set 1204 has an SRS resource ID = 4. Therefore, the first SRS resource set 1202 (with a lower SRS resource ID) is associated with a CORESETPoolIndex value of 0, and the second SRS resource set 1204 (with a higher SRS resource ID) is associated with a CORESETPoolIndex value of 1.

[0152] The second list associated with DCI format 0_2 includes a third SRS resource set 1206 and a fourth SRS resource set 1208. The third SRS resource set 1206 has an SRS resource ID = 3, and the fourth SRS resource set 1208 has an SRS resource ID = 5. Therefore, the third SRS resource set 1206 (having a lower SRS resource ID) is associated with a CORESETPoolIndex value of 0, and the fourth SRS resource set 1208 (having a higher SRS resource ID) is associated with a CORESETPoolIndex value of 1.

[0153] In addition, if Fig.12 As shown, the SRS resources of the second list are a subset of the SRS resources of the first list. Here, the third SRS resource set 1206 (SRS resources 0 and 1) is a subset of the first SRS resource set 1202 (SRS resources 0, 1, 2, and 3). In addition, the fourth SRS resource set 1208 (SRS resource 4) is a subset of the second SRS resource set 1204 (SRS resources 4, 5, and 6).

[0154] In some aspects, the present disclosure relates to a scenario in which a UE is configured with two TA hypotheses (TA values) in a CC configured with two CORESETPoolIndex values, whereby the UE determines an association of each SRS resource set with one of the two TA hypotheses. In some examples, the UE may determine the association based on one or more of the examples described below. Once the UE determines the association (e.g., determines the TA value to be used for SRS transmission), the UE transmits the SRS resources in the configured SRS resource set using the corresponding TA value.

[0155] In a first example (Example 1), a TA is selected based on the usage of an SRS resource set and / or based on an SRS resource set ID. For "usage" set to "beamManagement" or "antennaSwitching", a fixed (e.g., default) TA of the two TAs may be used. In framework 1, where two TAGs are used, the fixed TAG may be the first configured TAG-ID for the CC (the first one in the order configured by RRC) or may be a TAG with a lower TAG-ID. In framework 2, where a single TAG is used, the fixed TA may be a TA associated with the TAG (and not a TA associated with a ΔTA).

[0156] For a "usage" set to "codebook" or "noncodebook", the association may depend on whether one or both SRS resource sets with the usage are configured in a given list (e.g., in a first list srs-ResourceSetToAddModList or in a second list srs-ResourceSetToAddModListDCI-0-2). If there is one SRS resource set in the list, a fixed (e.g., default) TA in the two TAs may be used, which may depend on framework 1 versus framework 2, similar to the other "usage" discussed above. If there are two SRS resource sets in the list, the SRS resource set with a lower ID may be associated with the first TA, and the SRS resource set with a higher ID may be associated with the second TA. In framework 1, the first TA / TAG may be the first configured TAG-ID for the CC (the first one in the order of RRC configuration) or may be a TA / TAG with a lower TAG-ID, and the second TA / TAG may be another TA / TAG. In framework 2, the first TA may be a TA associated with a TAG, and the second TA may be a TA obtained based on applying a ΔTA relative to the first TA. This rule is applicable to both lists of SRS resource sets separately.

[0157] In the second example (Example 2), the TA is selected based on the time domain behavior of the SRS resource set (e.g., whether the SRS resource set is periodic / semi-persistent / aperiodic). For periodic or semi-persistent SRS resource sets, a fixed (default) TA of the two TAs may be used, which may depend on Framework 1 versus Framework 2, similar to the discussion in Example 1. For aperiodic SRS resource sets (triggered by DCI), the TA may be a TA associated with the same CORESETPoolIndex value as the CORESETPoolIndex value of the CORESET in which the DCI is received. In Framework 1, the TA / TAG associated with the CORESETPoolIndex value of 0 may be the first configured TAG-ID for the CC (the first in the order of RRC configuration) or may be a TA / TAG with a lower TAG-ID, and the TA / TAG associated with the CORESETPoolIndex value of 1 may be another TA / TAG. In Framework 2, the TA associated with a CORESETPoolIndex value of 0 may be the TA associated with the TAG, and the TA associated with a CORESETPoolIndex value of 1 may be the TA obtained based on applying a ΔTA relative to the first TA.

[0158] Fig.13 1 is a flowchart illustrating a method 1300 of application example 1 according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for all example implementations. In some examples, method 1300 may be performed by Fig.16 In some examples, the method 1300 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0159] exist Fig.13 At block 1302, the UE is configured for multi-TRP, multi-DCI operation on the BWP / CC. In addition, two TAs are configured for the BWP / CC, and the UE is configured with an SRS resource set for SRS transmission.

[0160] At block 1304, the UE determines a usage of an SRS resource set. If at block 1304, the UE determines that the usage is beam management or antenna switching, then at block 1306, the UE may select a fixed (default) TA for SRS transmission. In some examples, the fixed TA is a TA associated with the TAG with the first (earliest) configured TAG ID. In some examples, the fixed TA is a TA associated with the TAG with the lowest TAG ID. In some examples, the fixed TA is a TA associated with a single TAG (i.e., the TA is not a delta TA).

[0161] If at block 1304 the UE determines that the usage is codebook or non-codebook, then at block 1308 the UE may determine whether the SRS list includes one or two SRS resource sets.

[0162] If at block 1308, the UE determines that the SRS list includes one SRS resource set, then at block 1310, the UE may select a fixed (default) TA for SRS transmission. In some examples, the fixed TA is the TA associated with the TAG with the first (earliest) configured TAG ID. In some examples, the fixed TA is the TA associated with the TAG with the lowest TAG ID. In some examples, the fixed TA is the TA associated with a single TAG (i.e., the TA is not a delta TA).

[0163] If at box 1308, the UE determines that the SRS list includes two SRS resource sets, then at box 1312, the UE may select a TA for SRS transmission based on the IDs of the SRS resource sets. In some examples, the lowest SRS resource set ID is associated with the first TA, and the highest SRS resource set ID is associated with the second TA. In some examples, the first TA / TAG is a TA / TAG associated with a TAG with a first (earliest) configured TAG ID, and the second TA / TAG is a TA / TAG associated with a TAG with a later configured TAG ID. In some examples, the first TA / TAG is a TA / TAG associated with a TAG with the lowest TAG ID, and the second TA / TAG is a TA / TAG associated with a TAG with the highest TAG ID. In some examples, the first TA is a TA associated with a single TAG, and the second TA is a ΔTA.

[0164] Fig.14 1400 is a flowchart illustrating method 1400 of application example 2 according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for all example implementations. In some examples, method 1400 may be performed by Fig.16In some examples, the method 1400 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0165] exist Fig.14 At block 1402 of , the UE is configured for multi-TRP, multi-DCI operation on the BWP / CC. In addition, two TAs are configured for the BWP / CC, and the UE is configured with an SRS resource set for SRS transmission.

[0166] At block 1404, the UE determines the time domain behavior of the SRS resource set. If at block 1404, the UE determines that the SRS resource set is configured as periodic or semi-persistent, then at block 1406, the UE may select a fixed (default) TA for SRS transmission. In some examples, the fixed TA is the TA associated with the TAG with the first (earliest) configured TAG ID. In some examples, the fixed TA is the TA associated with the TAG with the lowest TAG ID. In some examples, the fixed TA is the TA associated with a single TAG (i.e., the TA is not a delta TA).

[0167] If, at block 1404, the UE determines that the SRS resource set is configured as aperiodic, then at block 1408, the UE may select a TA for SRS transmission based on the CORESETPoolIndex value of the CORESET in which the DCI triggering the SRS transmission is received. In some examples, the TA / TAG associated with the CORESETPoolIndex value is the TA / TAG associated with the TAG with the first (earliest) configured TAG ID. In some examples, the TA / TAG associated with the CORESETPoolIndex value is the TA / TAG associated with the TAG with the lowest TAG ID. In some examples, the TA associated with the CORESETPoolIndex value is a TA associated with a single TAG (not a ΔTA).

[0168] Fig.15 is a signaling diagram 1500 illustrating an example of identifying a timing advance for SRS transmission in a wireless communication system including a network entity (eg, a base station) 1502 and a user equipment (UE) 1504. In some examples, the network entity 1502 may correspond to Figure 1 , Figure 2 , Figure 3 , Figure 7 , Figure 8 , Fig. 9 and Fig.18 In some examples, the user equipment 1504 may correspond to any of the base stations, CUs, DUs, RUs, or scheduling entities shown in any of the figures. Figure 1 , Figure 2 , Figure 3 , Figure 7 , Figure 8 , Fig. 9 and Fig.16 Any one of the UEs or scheduled entities shown in any of the figures.

[0169] exist Fig.15 At 1506, the network entity 1502 configures the user equipment 1504 for multi-TRP operation. For example, the network entity 1502 may configure the BWP, search space, and other resources for communication between the user equipment 1504 and two TRPs.

[0170] At 1508, the network entity 1502 defines a CORESET pool index value. For example, a first subset of CORESETs allocated for a CC for the user equipment 1504 may be associated with a CORESETPoolIndex value of 0, and a second subset of CORESETs allocated for a CC for the user equipment 1504 may be associated with a CORESETPoolIndex value of 1.

[0171] At 1510, the network entity 1502 configures the timing advance group. For example, the first TAG ID and the second TAG ID may be associated with a particular CC configured for the user equipment 1504. As another example, a single TAG ID may be associated with the CC.

[0172] At 1512, the network entity 1502 configures resources for SRS transmission by the user equipment 1504. For example, the network entity 1502 may allocate resources for different SRS resource sets at different BWPs under different cells. As another example, the network entity 1502 may allocate SL-SRS resources. For uplink SRS transmission, the network entity 1502 (e.g., a base station) may transmit an RRC message or some other type of message to the user equipment 1504, wherein the message specifies the resources and other information that the user equipment 1504 will use for SRS transmission.

[0173] At optional 1514 , in some examples, DCI or other signaling may be used to trigger or activate SRS transmission (eg, aperiodic SRS) at user equipment 1504 .

[0174] At 1516, the user equipment 1504 identifies a timing advance value to be used to send the SRS on the scheduled SRS resource. For example, the user equipment 1504 may use the above in conjunction with Fig.13 and Fig.14 One or more of the described operations may be used to identify a timing advance value.

[0175] At 1518, the user equipment 1504 sends an SRS transmission on the scheduled SRS resources using the timing advance value identified at 1516. For example, for uplink SRS transmissions, the user equipment 1504 (e.g., UE) may send the SRS to the network entity 1502 (e.g., base station). For sidelink SRS transmissions, the user equipment 1504 (e.g., scheduled sidelink UE) may send the SRS to the network entity 1502 (e.g., sidelink UE) or to another sidelink UE (not in the schedule). Fig.15 For triggered or activated SRS transmission, the user equipment 1504 transmits SRS transmission according to the trigger or the activation (eg, indicated by MAC-CE, DCI, etc.).

[0176] At 1520, the network entity 1502 processes the SRS transmission received at 1518. For example, the network entity 1502 may estimate a channel between the network entity 1502 and the user equipment 1504, estimate a positioning of the user equipment 1504, generate a codebook for communication with the user equipment 1504, estimate cross-link interference for communication with the user equipment 1504, or select a beam for communication with the user equipment 1504.

[0177] Fig.16 16 is a block diagram illustrating an example of a hardware implementation of a UE 1600 employing a processing system 1614. For example, the UE 1600 may be a device configured to communicate wirelessly with a network entity, such as Figures 1 to 15 In some implementations, UE 1600 may correspond to Figure 1 , Figure 2 , Figure 3 , Figure 7 , Figure 8 , Fig. 9 and Fig.15 Any one of the UEs or scheduled entities shown in any of the figures.

[0178] According to various aspects of the present disclosure, any combination of elements or any part of elements or elements can be implemented using processing system 1614. Processing system 1614 may include one or more processors 1604. Examples of processor 1604 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. In various examples, UE 1600 may be configured to perform any one or more of the functions described herein. That is, the processor 1604 as utilized in UE 1600 may be used to implement any one or more of the processes and procedures described herein.

[0179] In some examples, the processor 1604 may be implemented via a baseband or modem chip, and in other implementations, the processor 1604 may include multiple devices distinct from the baseband or modem chip (e.g., which in such scenarios may work together to implement the examples discussed herein). And as mentioned above, various hardware arrangements and components outside of the baseband modem processor may be used in implementations, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.

[0180] In this example, the processing system 1614 may be implemented using a bus architecture (generally represented by bus 1602). The bus 1602 may include any number of interconnecting buses and bridges, depending on the specific application of the processing system 1614 and the overall design constraints. The bus 1602 communicatively couples various circuits including one or more processors (generally represented by processor 1604), memory 1605, and computer-readable media (generally represented by computer-readable media 1606). The bus 1602 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further. The bus interface 1608 provides an interface between the bus 1602, the transceiver 1610, and the antenna array 1620, and between the bus 1602 and the interface 1630. The transceiver 1610 provides a communication interface or component for communicating with various other devices through a wireless transmission medium. The interface 1630 provides a communication interface or component for communicating with various other devices and equipment (e.g., other devices contained in the same device as the UE 1600 or other external devices) through an internal bus or an external transmission medium (such as an Ethernet cable). Depending on the nature of the device, the interface 1630 may include a user interface (e.g., a keypad, a display, a speaker, a microphone, a joystick). Of course, such a user interface is optional and may be omitted in some examples (such as IoT devices).

[0181] The processor 1604 is responsible for managing the bus 1602 and general processing, including executing software stored on the computer-readable medium 1606. The software, when executed by the processor 1604, causes the processing system 1614 to perform various functions described below for any particular device. The computer-readable medium 1606 and the memory 1605 can also be used to store data manipulated by the processor 1604 when executing the software. For example, the memory 1605 can store SRS information 1615 (e.g., SRS resource information) used by the processor 1604 for communication operations described herein.

[0182] One or more processors 1604 in the processing system may execute software. Software should be construed broadly to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software may reside on a computer readable medium 1606.

[0183] Computer readable medium 1606 may be a non-transitory computer readable medium. Non-transitory computer readable media include, for example, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact disks (CDs) or digital versatile disks (DVDs)), smart cards, flash memory devices (e.g., cards, sticks, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer readable medium 1606 may reside in processing system 1614, be located outside processing system 1614, or be distributed across multiple entities including processing system 1614. Computer readable medium 1606 may be embodied in a computer program product. For example, a computer program product may include a computer readable medium in a packaging material. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure, depending on the specific application and the overall design constraints imposed on the overall system.

[0184] UE 1600 may be configured to perform any one or more of the operations described herein (e.g., as described above in conjunction with Figures 1 to 15 As described and as follows Fig.17 In some aspects of the present disclosure, the processor 1604 as utilized in the UE 1600 may include circuits configured for various functions.

[0185] Processor 1604 may include communication and processing circuitry 1641. Communication and processing circuitry 1641 may be configured to communicate with a network entity, such as a gNB. Communication and processing circuitry 1641 may be configured to communicate with a base station and one or more other wireless communication devices via a common carrier shared between a cellular (e.g., Uu) interface and a sidelink (e.g., PC5) interface. Communication and processing circuitry 1641 may include one or more hardware components that provide a physical structure that performs various processes associated with wireless communication (e.g., signal reception and / or signal transmission) as described herein. Communication and processing circuitry 1641 may also include one or more hardware components that provide a physical structure that performs various processes associated with signal processing (e.g., processing received signals and / or processing signals for transmission) as described herein. In some examples, communication and processing circuitry 1641 may include two or more transmit / receive chains (e.g., one chain for communicating with a base station and another chain for communicating with a sidelink device). The communication and processing circuit 1641 may be further configured to execute communication and processing software 1651 included on the computer-readable medium 1606 to implement one or more functions described herein.

[0186] In some implementations where communication involves receiving information, the communication and processing circuit 1641 may obtain information from a component of the UE 1600 (e.g., from a transceiver 1610 that receives information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, the communication and processing circuit 1641 may output the information to another component of the processor 1604, to the memory 1605, or to the bus interface 1608. In some examples, the communication and processing circuit 1641 may receive one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuit 1641 may receive information via one or more channels. In some examples, the communication and processing circuit 1641 may receive one or more of a signal, a message, SCI, feedback, other information, or any combination thereof. In some examples, the communication and processing circuit 1641 may receive information via one or more of a PSCCH, a PSSCH, a PSFCH, some other type of channel, or any combination thereof. In some examples, communication and processing circuitry 1641 may include functionality for components for receiving. In some examples, communication and processing circuitry 1641 may include functionality for components for decoding.

[0187] In some implementations where communication involves transmitting (e.g., sending) information, the communication and processing circuit 1641 may obtain information (e.g., from another component of the processor 1604, the memory 1605, or the bus interface 1608), process (e.g., encode) the information, and output the processed information. For example, the communication and processing circuit 1641 may output the information to the transceiver 1610 (e.g., it sends the information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, the communication and processing circuit 1641 may transmit one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuit 1641 may transmit information via one or more channels. In some examples, the communication and processing circuit 1641 may transmit one or more of a signal, a message, SCI, feedback, other information, or any combination thereof. In some examples, the communication and processing circuit 1641 may transmit information via one or more of a PSCCH, a PSSCH, a PSFCH, some other type of channel, or any combination thereof. In some examples, the communication and processing circuitry 1641 may include functionality for components for transmitting (e.g., components for sending). In some examples, the communication and processing circuitry 1641 may include functionality for components for encoding. In some examples, the communication and processing circuitry 1641 may include functionality for components for sending SRS on SRS resources using the selected TA value.

[0188] The processor 1604 may include an SRS processing circuit 1642 configured to perform SRS processing related operations as discussed herein (e.g., as described above in conjunction with Figures 13 to 15 The SRS processing circuit 1642 may be configured to execute SRS processing software 1652 included on the computer-readable medium 1606 to implement one or more functions described herein.

[0189] The SRS processing circuit 1642 may include functionality for components configured to receive a set of SRS resources (e.g., as described above in conjunction with Figures 13 to 15 For example, the SRS processing circuit 1642 may receive an RRC message including the configuration from a network entity via a PDSCH.

[0190] The processor 1604 may include a TA processing circuit 1643 configured to perform TA processing related operations as discussed herein (e.g., as described above in conjunction with Figures 13 to 15 The TA processing circuit 1643 may be configured to execute TA processing software 1653 included on the computer-readable medium 1606 to implement one or more functions described herein.

[0191] TA processing circuit 1643 may include functionality for receiving components configured to identify a TA value (e.g., as described above in conjunction with Figures 13 to 15 For example, the TA processing circuit 1643 may receive an RRC message including the configuration from a network entity via a PDSCH.

[0192] Fig.17 is a flow chart illustrating an example method 1700 for a user equipment according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for all example implementations. In some examples, the method 1700 may be performed by Fig.16 In some examples, the method 1700 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0193] At block 1702, the user equipment may receive a first configuration identifying a plurality of timing advance values. In some examples, the TA processing circuit 1643 together with the communication and processing circuit 1641 and the transceiver 1610, such as Fig.16 As shown and described in , means for receiving a first configuration identifying a plurality of timing advance values ​​may be provided.

[0194] At block 1704, the user equipment may receive a second configuration of a first sounding reference signal (SRS) resource set. In some examples, the SRS processing circuit 1642, together with the communication and processing circuit 1641 and the transceiver 1610, may Fig.16 As shown and described in the accompanying drawings, components for receiving a first configuration of a first sounding reference signal (SRS) resource set may be provided.

[0195] At block 1706, the user equipment may transmit a first SRS on the first SRS resource set using a first timing advance value selected from a plurality of timing advance values ​​based on a usage associated with the first SRS resource set or a time domain configuration associated with the first SRS resource set. In some examples, the SRS processing circuit 1642 together with the communication and processing circuit 1641 and the transceiver 1610, such as Fig.16 As shown and described in , means may be provided for sending a first SRS on a first SRS resource set using a first timing advance value selected from a plurality of timing advance values ​​based on a usage associated with the first SRS resource set or a time domain configuration associated with the first SRS resource set.

[0196] In some examples, the user equipment may receive a third configuration including a first control resource pool value and a second control resource pool value, the first control resource pool value being associated with the first timing advance value, and the second control resource pool value being associated with a second timing advance value of the plurality of timing advance values. In some examples, the first control resource pool value is associated with the first transmission reception point. In some examples, the second control resource pool value is associated with the second transmission reception point.

[0197] In some examples, the first timing advance value may include a default timing advance value (e.g., associated with beam management SRS usage or antenna switching SRS usage). In some examples, the first timing advance value is associated with a first timing advance group (TAG). In some examples, a second timing advance value among multiple timing advance values ​​is associated with a second TAG configured after the first TAG. In some examples, the first timing advance value is associated with a first timing advance group (TAG) associated with a first TAG identifier. In some examples, a second timing advance value among multiple timing advance values ​​is associated with a second TAG associated with a second TAG identifier. In some examples, the first TAG identifier has an identifier value lower than the second TAG identifier. In some examples, the first timing advance value is associated with a first timing advance group (TAG). In some examples, the second timing advance value among multiple timing advance values ​​is defined based on an offset time value relative to the first timing advance value.

[0198] In some examples, the first SRS resource set is associated with codebook SRS use or non-codebook SRS use. In some examples, the first SRS resource set is included in a list of SRS resource sets that is limited to a single SRS resource set for codebook SRS use or non-codebook SRS use. In some examples, the first timing advance value may include a default timing advance value (e.g., associated with an SRS resource set list). In some examples, the first timing advance value is associated with a first timing advance group (TAG). In some examples, a second timing advance value among multiple timing advance values ​​is associated with a second TAG configured after the first TAG. In some examples, the first timing advance value is associated with a first timing advance group (TAG) associated with a first TAG identifier. In some examples, a second timing advance value among multiple timing advance values ​​is associated with a second TAG associated with a second TAG identifier. In some examples, the first TAG identifier has an identifier value lower than the second TAG identifier. In some examples, the first timing advance value is associated with a first timing advance group (TAG). In some examples, the second timing advance value among multiple timing advance values ​​is defined based on an offset time value relative to the first timing advance value.

[0199] In some examples, the first SRS resource set is associated with codebook SRS use or non-codebook SRS use. In some examples, the user equipment may select a first timing advance value based on a first identifier associated with the first SRS resource set. In some examples, the first SRS resource set is included in a list of SRS resource sets including a second SRS resource set. In some examples, the first SRS resource set is associated with a first timing advance value. In some examples, the second SRS resource set is associated with a second identifier and a second timing advance value in a plurality of timing advance values. In some examples, the first identifier has an identifier value lower than the second identifier. In some examples, the first timing advance value is associated with a first timing advance group (TAG). In some examples, the second timing advance value is associated with a second TAG configured after the first TAG. In some examples, the first timing advance value is associated with a first timing advance group (TAG) associated with the first TAG identifier. In some examples, the second timing advance value is associated with a second TAG associated with the second TAG identifier. In some examples, the first TAG identifier has an identifier value lower than the second TAG identifier. In some examples, the first timing advance value is associated with a first timing advance group (TAG).In some examples, a second timing advance value in the plurality of timing advance values ​​is defined based on an offset time value relative to the first timing advance value.

[0200] In some examples, the first timing advance value may include a default timing advance value (e.g., associated with a periodic SRS resource set or a semi-persistent SRS resource set). In some examples, the first timing advance value is associated with a first timing advance group (TAG). In some examples, a second timing advance value among multiple timing advance values ​​is associated with a second TAG configured after the first TAG. In some examples, the first timing advance value is associated with a first timing advance group (TAG) associated with a first TAG identifier. In some examples, a second timing advance value among multiple timing advance values ​​is associated with a second TAG associated with a second TAG identifier. In some examples, the first TAG identifier has an identifier value lower than the second TAG identifier. In some examples, the first timing advance value is associated with a first timing advance group (TAG). In some examples, the second timing advance value among multiple timing advance values ​​is defined based on an offset time value relative to the first timing advance value.

[0201] In some examples, a user equipment may receive a first downlink control information (DCI) scheduling a first SRS resource set as a non-periodic SRS resource set on a first control resource set. In some examples, the first control resource set is associated with a first control resource set pool value in a plurality of control resource set pool values. In some examples, a first timing advance value is associated with a first control resource set pool value. In some examples, the first timing advance value is associated with a first timing advance group (TAG). In some examples, a second timing advance value in a plurality of timing advance values ​​is associated with a second TAG configured after the first TAG. In some examples, the first timing advance value is associated with a first timing advance group (TAG) associated with a first TAG identifier. In some examples, a second timing advance value in a plurality of timing advance values ​​is associated with a second TAG associated with a second TAG identifier. In some examples, the first TAG identifier has an identifier value lower than the second TAG identifier. In some examples, the first timing advance value is associated with a first timing advance group (TAG). In some examples, a second timing advance value in a plurality of timing advance values ​​is defined based on an offset time value relative to the first timing advance value.

[0202] In one configuration, the UE 1600 includes: a component for receiving a first configuration identifying a plurality of timing advance values; a component for receiving a second configuration of a first sounding reference signal (SRS) resource set; and a component for transmitting a first SRS on the first SRS resource set using a first timing advance value selected from the plurality of timing advance values ​​based on a usage associated with the first SRS resource set or a time domain configuration associated with the first SRS resource set. In one aspect, the aforementioned components may be Fig.16 The processor 1604 shown in FIG. 1 is configured to perform the functions recited by the aforementioned components (eg, as discussed above). On the other hand, the aforementioned components may be a circuit or any device configured to perform the functions recited by the aforementioned components.

[0203] Of course, in the above examples, the circuits included in the processor 1604 are provided only as examples, and other components for performing the described functions may be included in various aspects of the present disclosure, including but not limited to instructions stored in the computer-readable medium 1606, or in Figure 1 , Figure 2 , Figure 3 , Figure 7 , Figure 8 , Fig. 9 , Fig.15 and Fig.16 One or more figures of the present invention are described and used as an example Fig.17 Any other suitable means or components of the described methods and / or algorithms.

[0204] Fig.18 18 is a conceptual diagram illustrating an example of a hardware implementation of a network entity 1800 employing a processing system 1814. In some implementations, the network entity 1800 may correspond to Figure 1 , Figure 2 , Figure 3 , Figure 7 , Figure 8 , Fig. 9 and Fig.15 Any of the base stations, CUs, DUs, RUs or scheduling entities shown in any of the figures.

[0205] According to various aspects of the present disclosure, the processing system 1814 may be used to implement an element or any portion of an element or any combination of elements. The processing system may include one or more processors 1804. The processing system 1814 may be substantially connected to Fig.16 1800, including a bus interface 1808, a bus 1802, a memory 1805, a processor 1804, a computer-readable medium 1806, a transceiver 1810, and an antenna array 1820. The memory 1805 may store SRS information 1815 (e.g., SRS resource information) used by the processor 1804 in cooperation with the transceiver 1810 to perform communication operations as described herein. In addition, the network entity 1800 may include an interface 1830 (e.g., a network interface) that provides a means for communicating with at least one other device within the core network and with at least one radio access network.

[0206] The network node 1800 may be configured to perform any one or more of the operations described herein (e.g., as described above in conjunction with Figures 1 to 15 Described and combined as follows Fig.19 In some aspects of the present disclosure, the processor 1804 as utilized in the network entity 1800 may include circuits configured for various functions.

[0207] Processor 1804 may be configured to generate, schedule, and modify resource assignments or grants of time-frequency resources (e.g., a set of one or more resource elements). For example, processor 1804 may schedule time-frequency resources within multiple time division duplex (TDD) and / or frequency division duplex (FDD) subframes, time slots, and / or mini-slots to carry user data traffic and / or control information to and / or from multiple scheduled entities. Processor 1804 may be configured to schedule resources for transmission of downlink signals. Processor 1804 may be further configured to schedule resources for transmission of uplink signals.

[0208] In some aspects of the present disclosure, the processor 1804 may include a communication and processing circuit 1841. The communication and processing circuit 1841 may be configured to communicate with user equipment. The communication and processing circuit 1841 may include one or more hardware components that provide a physical structure that performs various processes related to communication (e.g., signal reception and / or signal transmission) as described herein. The communication and processing circuit 1841 may also include one or more hardware components that provide a physical structure that performs various processes related to signal processing (e.g., processing received signals and / or processing signals for transmission) as described herein. The communication and processing circuit 1841 may be further configured to execute communication and processing software 1851 included on the computer-readable medium 1806 to implement one or more functions described herein.

[0209] The communication and processing circuit 1841 may be further configured to receive an indication from the UE. For example, the indication may be included in a MAC-CE carried in a Uu PUSCH or PSCCH, or in a Uu RRC message or SL RRC message, or in a dedicated Uu PUCCH or PUSCH. The communication and processing circuit 1841 may be further configured to receive a scheduling request for an uplink grant or a sidelink grant from the UE.

[0210] In some implementations where communication involves receiving information, the communication and processing circuit 1841 may obtain information from a component of the network entity 1800 (e.g., from a transceiver 1810 that receives information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, the communication and processing circuit 1841 may output the information to another component of the processor 1804, to the memory 1805, or to the bus interface 1808. In some examples, the communication and processing circuit 1841 may receive one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuit 1841 may receive information via one or more channels. In some examples, the communication and processing circuit 1841 may include functionality for components for receiving. In some examples, the communication and processing circuit 1841 may include functionality for components for decoding. In some examples, the communication and processing circuit 1841 may include functionality for components for receiving an SRS on an SRS resource based on a TA value.

[0211] In some implementations where communication involves transmitting (e.g., sending) information, the communication and processing circuitry 1841 may obtain information (e.g., from another component of the processor 1804, the memory 1805, or the bus interface 1808), process (e.g., encode) the information, and output the processed information. For example, the communication and processing circuitry 1841 may output the information to the transceiver 1810 (e.g., which transmits the information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, the communication and processing circuitry 1841 may transmit one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1841 may transmit information via one or more channels. In some examples, the communication and processing circuitry 1841 may include functionality for components for transmitting (e.g., components for sending). In some examples, the communication and processing circuitry 1841 may include functionality for components for encoding.

[0212] The processor 1804 may include an SRS processing circuit 1842 configured to perform SRS processing related operations as discussed herein (e.g., as described above in conjunction with Figures 13 to 15 The SRS processing circuit 1842 may be configured to execute SRS processing software 1852 included on the computer-readable medium 1806 to implement one or more functions described herein.

[0213] The SRS processing circuit 1842 may include functionality for components configured to transmit an SRS resource set (e.g., as described above in conjunction with Figures 13 to 15 For example, the SRS processing circuit 1842 may send an RRC message including the configuration to the UE via the PDSCH.

[0214] The processor 1804 may include a TA processing circuit 1843 configured to perform TA processing related operations as discussed herein (e.g., as described above in connection with Figures 13 to 15 The TA processing circuit 1843 may be configured to execute TA processing software 1853 included on the computer-readable medium 1806 to implement one or more functions described herein.

[0215] TA processing circuit 1843 may include functionality for components configured to send an identification TA value (e.g., as described above in conjunction with Figures 13 to 15 For example, the TA processing circuit 1843 may send an RRC message including the configuration to the UE via the PDSCH.

[0216] In some examples, the above is combined with Fig.18The network entity 1800 shown and described may be a decomposed base station. Fig.18 The network entity 1800 shown in the figure may include a CU and, optionally, one or more DU / RUs of a decomposed base station. Other DU / RUs associated with the network entity 1800 may be distributed throughout the network. In some examples, the DU / RU may correspond to a TRP associated with the network entity. In some examples, the CU and / or DU / RU of the decomposed base station (e.g., within the network entity 1800) may generate at least one configuration (e.g., including a TA value and / or an SRS resource set) and provide the at least one configuration to the user equipment, as well as receive an SRS from the user equipment and process the SRS.

[0217] Fig.19 is a flow chart illustrating an example method 1900 for a wireless communication system according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for all example implementations. In some examples, the method 1900 may be performed by Fig.18 In some examples, the method 1900 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0218] At block 1902, a network entity may send a first configuration identifying a plurality of timing advance values. In some examples, the TA processing circuit 1843 together with the communication and processing circuit 1841 and the transceiver 1810, such as Fig.18 As shown and described in , means for transmitting a first configuration identifying a plurality of timing advance values ​​may be provided.

[0219] At block 1904, the network entity may send a second configuration of the first sounding reference signal (SRS) resource set. In some examples, the SRS processing circuit 1842, together with the communication and processing circuit 1841 and the transceiver 1810, may Fig.18 As shown and described in the accompanying drawings, components for transmitting a first configuration of a first sounding reference signal (SRS) resource set may be provided.

[0220] At block 1906, the network entity may receive a first SRS on a first SRS resource set based on a first timing advance value in a plurality of timing advance values, the first timing advance value being associated with a usage associated with the first SRS resource set or a time domain configuration associated with the first SRS resource set. In some examples, the SRS processing circuit 1842, together with the communication and processing circuit 1841 and the transceiver 1810, Fig.18As shown and described in the foregoing, means may be provided for receiving a first SRS on a first set of SRS resources based on a first timing advance value among a plurality of timing advance values.

[0221] In some examples, the network entity may send a third configuration including a first control resource pool value and a second control resource pool value, the first control resource pool value being associated with the first timing advance value, and the second control resource pool value being associated with a second timing advance value of the plurality of timing advance values. In some examples, the first control resource pool value is associated with the first transmission reception point. In some examples, the second control resource pool value is associated with the second transmission reception point.

[0222] In some examples, the first timing advance value may include a default timing advance value (e.g., associated with beam management SRS usage or antenna switching SRS usage). In some examples, the first timing advance value is associated with a first timing advance group (TAG). In some examples, a second timing advance value among multiple timing advance values ​​is associated with a second TAG configured after the first TAG. In some examples, the first timing advance value is associated with a first timing advance group (TAG) associated with a first TAG identifier. In some examples, a second timing advance value among multiple timing advance values ​​is associated with a second TAG associated with a second TAG identifier. In some examples, the first TAG identifier has an identifier value lower than the second TAG identifier. In some examples, the first timing advance value is associated with a first timing advance group (TAG). In some examples, the second timing advance value among multiple timing advance values ​​is defined based on an offset time value relative to the first timing advance value.

[0223] In some examples, the first SRS resource set is associated with codebook SRS use or non-codebook SRS use. In some examples, the first SRS resource set is included in a list of SRS resource sets that is limited to a single SRS resource set for codebook SRS use or non-codebook SRS use. In some examples, the first timing advance value may include a default timing advance value (e.g., associated with an SRS resource set list). In some examples, the first timing advance value is associated with a first timing advance group (TAG). In some examples, a second timing advance value among multiple timing advance values ​​is associated with a second TAG configured after the first TAG. In some examples, the first timing advance value is associated with a first timing advance group (TAG) associated with a first TAG identifier. In some examples, a second timing advance value among multiple timing advance values ​​is associated with a second TAG associated with a second TAG identifier. In some examples, the first TAG identifier has an identifier value lower than the second TAG identifier. In some examples, the first timing advance value is associated with a first timing advance group (TAG). In some examples, the second timing advance value among multiple timing advance values ​​is defined based on an offset time value relative to the first timing advance value.

[0224] In some examples, the first SRS resource set is associated with codebook SRS use or non-codebook SRS use. In some examples, the network entity may select a first timing advance value based on a first identifier associated with the first SRS resource set. In some examples, the first SRS resource set is included in a list of SRS resource sets including a second SRS resource set. In some examples, the first SRS resource set is associated with a first timing advance value. In some examples, the second SRS resource set is associated with a second identifier and a second timing advance value among a plurality of timing advance values. In some examples, the first identifier has an identifier value lower than the second identifier. In some examples, the first timing advance value is associated with a first timing advance group (TAG). In some examples, the second timing advance value is associated with a second TAG configured after the first TAG. In some examples, the first timing advance value is associated with a first timing advance group (TAG) associated with the first TAG identifier. In some examples, the second timing advance value is associated with a second TAG associated with the second TAG identifier. In some examples, the first TAG identifier has an identifier value lower than the second TAG identifier. In some examples, the first timing advance value is associated with a first timing advance group (TAG).In some examples, a second timing advance value in the plurality of timing advance values ​​is defined based on an offset time value relative to the first timing advance value.

[0225] In some examples, the first timing advance value may include a default timing advance value (e.g., associated with a periodic SRS resource set or a semi-persistent SRS resource set). In some examples, the first timing advance value is associated with a first timing advance group (TAG). In some examples, a second timing advance value among multiple timing advance values ​​is associated with a second TAG configured after the first TAG. In some examples, the first timing advance value is associated with a first timing advance group (TAG) associated with a first TAG identifier. In some examples, a second timing advance value among multiple timing advance values ​​is associated with a second TAG associated with a second TAG identifier. In some examples, the first TAG identifier has an identifier value lower than the second TAG identifier. In some examples, the first timing advance value is associated with a first timing advance group (TAG). In some examples, the second timing advance value among multiple timing advance values ​​is defined based on an offset time value relative to the first timing advance value.

[0226] In some examples, the network entity may send a first downlink control information (DCI) on a first control resource set to schedule the first SRS resource set as a non-periodic SRS resource set. In some examples, the first control resource set is associated with a first control resource set pool value in a plurality of control resource set pool values. In some examples, the first timing advance value is associated with the first control resource set pool value. In some examples, the first timing advance value is associated with a first timing advance group (TAG). In some examples, a second timing advance value in a plurality of timing advance values ​​is associated with a second TAG configured after the first TAG. In some examples, the first timing advance value is associated with a first timing advance group (TAG) associated with a first TAG identifier. In some examples, a second timing advance value in a plurality of timing advance values ​​is associated with a second TAG associated with a second TAG identifier. In some examples, the first TAG identifier has an identifier value lower than the second TAG identifier. In some examples, the first timing advance value is associated with a first timing advance group (TAG). In some examples, a second timing advance value in a plurality of timing advance values ​​is defined based on an offset time value relative to the first timing advance value.

[0227] In one configuration, the network entity 1800 includes: a component for sending a first configuration identifying a plurality of timing advance values; a component for sending a second configuration of a first sounding reference signal (SRS) resource set; and a component for receiving a first SRS on a first SRS resource set based on a first timing advance value of the plurality of timing advance values, the first timing advance value being associated with a usage associated with the first SRS resource set or a time domain configuration associated with the first SRS resource set. In one aspect, the aforementioned components may be Fig.18The processor 1804 shown in FIG. 1 is configured to perform the functions recited by the aforementioned components (eg, as discussed above). On the other hand, the aforementioned components may be a circuit or any device configured to perform the functions recited by the aforementioned components.

[0228] Of course, in the above examples, the circuits included in the processor 1804 are provided only as examples, and other components for performing the described functions may be included in various aspects of the present disclosure, including but not limited to instructions stored in the computer-readable medium 1806, or in Figure 1 , Figure 2 , Figure 3 , Figure 7 , Figure 8 , Fig. 9 , Fig.15 and Fig.18 One or more figures of the present invention are described and used as an example Fig.19 Any other suitable means or components of the described methods and / or algorithms.

[0229] Fig.17 and Fig.19 The method shown in may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein. A summary of several aspects of the disclosure is provided below.

[0230] Aspect 1: A method for performing wireless communications at a user equipment, comprising: receiving a first configuration identifying multiple timing advance values; receiving a second configuration of a first sounding reference signal (SRS) resource set; and sending a first SRS on the first SRS resource set using a first timing advance value selected from the multiple timing advance values ​​based on a usage associated with the first SRS resource set or a time domain configuration associated with the first SRS resource set.

[0231] Aspect 2: The method according to Aspect 1 also includes: receiving a third configuration including a first control resource pool value and a second control resource pool value, wherein the first control resource pool value is associated with the first timing advance value, and the second control resource pool value is associated with the second timing advance value among the multiple timing advance values.

[0232] Aspect 3: A method according to aspect 2, wherein: the first control resource pool value is associated with a first transmission and reception point; and the second control resource pool value is associated with a second transmission and reception point.

[0233] Aspect 4: The method according to any one of Aspects 1 to 3, wherein: the first timing advance value comprises a default timing advance value associated with beam management SRS usage or antenna switching SRS usage.

[0234] Aspect 5: The method according to any one of aspects 1 to 3, wherein: the first SRS resource set is associated with codebook SRS usage or non-codebook SRS usage.

[0235] Aspect 6: The method according to aspect 5, wherein: the first SRS resource set is included in an SRS resource set list for which codebook SRS usage or non-codebook SRS usage is limited to a single SRS resource set; and the first timing advance value includes a default timing advance value.

[0236] Aspect 7: The method according to aspect 5 further includes: selecting the first timing advance value based on a first identifier associated with the first SRS resource set.

[0237] Aspect 8: A method according to Aspect 7, wherein: the first SRS resource set is included in an SRS resource set list including a second SRS resource set; the first SRS resource set is associated with the first timing advance value; the second SRS resource set is associated with a second identifier and a second timing advance value among the multiple timing advance values; and the first identifier has an identifier value lower than the second identifier.

[0238] Aspect 9: The method according to any one of Aspects 1 to 3, wherein: the first timing advance value includes a default timing advance value associated with a periodic SRS resource set or a semi-persistent SRS resource set.

[0239] Aspect 10: A method according to any one of Aspects 1 to 3, wherein: the method further includes: receiving first downlink control information (DCI) on a first control resource set to schedule the first SRS resource set as a non-periodic SRS resource set; the first control resource set is associated with a first control resource set pool value among multiple control resource set pool values; and the first timing advance value is associated with the first control resource set pool value.

[0240] Aspect 11: A method according to any one of Aspects 1 to 10, wherein: the first timing advance value is associated with a first timing advance group (TAG); and the second timing advance value among the multiple timing advance values ​​is associated with a second TAG configured after the first TAG.

[0241] Aspect 12: A method according to any one of Aspects 1 to 10, wherein: the first timing advance value is associated with a first timing advance group (TAG) associated with a first TAG identifier; a second timing advance value among the multiple timing advance values ​​is associated with a second TAG associated with a second TAG identifier; and the first TAG identifier has a lower identifier value than the second TAG identifier.

[0242] Aspect 13: A method according to any one of Aspects 1 to 10, wherein: the first timing advance value is associated with a first timing advance group (TAG); and a second timing advance value among the multiple timing advance values ​​is defined based on an offset time value relative to the first timing advance value.

[0243] Aspect 16: A method for wireless communication by a network entity, the method comprising: sending a first configuration identifying multiple timing advance values; sending a second configuration of a first sounding reference signal (SRS) resource set; and receiving a first SRS on the first SRS resource set based on a first timing advance value among the multiple timing advance values, the first timing advance value being associated with a usage associated with the first SRS resource set or a time domain configuration associated with the first SRS resource set.

[0244] Aspect 17: The method according to Aspect 16 also includes: sending a third configuration including a first control resource pool value and a second control resource pool value, wherein the first control resource pool value is associated with the first timing advance value, and the second control resource pool value is associated with the second timing advance value among the multiple timing advance values.

[0245] Aspect 18: The method according to Aspect 17, wherein: the first control resource pool value is associated with a first transmission and reception point; and the second control resource pool value is associated with a second transmission and reception point.

[0246] Aspect 19: A method according to any one of Aspects 16 to 18, wherein: the first timing advance value comprises a default timing advance value associated with beam management SRS usage or antenna switching SRS usage.

[0247] Aspect 20: The method according to any one of aspects 16 to 18, wherein: the first SRS resource set is associated with codebook SRS usage or non-codebook SRS usage.

[0248] Aspect 21: A method according to Aspect 20, wherein: the first SRS resource set is included in an SRS resource set list for which codebook SRS usage or non-codebook SRS usage is limited to a single SRS resource set; and the first timing advance value includes a default timing advance value.

[0249] Aspect 22: The method according to aspect 20 further includes: selecting the first timing advance value based on a first identifier associated with the first SRS resource set.

[0250] Aspect 23: A method according to Aspect 22, wherein: the first SRS resource set is included in an SRS resource set list including a second SRS resource set; the first SRS resource set is associated with the first timing advance value; the second SRS resource set is associated with a second identifier and a second timing advance value among the multiple timing advance values; and the first identifier has an identifier value lower than the second identifier.

[0251] Aspect 24: A method according to any one of Aspects 16 to 18, wherein: the first timing advance value comprises a default timing advance value associated with a periodic SRS resource set or a semi-persistent SRS resource set.

[0252] Aspect 25: A method according to any one of Aspects 16 to 18, wherein: the method further includes: sending first downlink control information (DCI) on a first control resource set to schedule the first SRS resource set as a non-periodic SRS resource set; the first control resource set is associated with a first control resource set pool value among multiple control resource set pool values; and the first timing advance value is associated with the first control resource set pool value.

[0253] Aspect 26: A method according to any one of Aspects 16 to 25, wherein: the first timing advance value is associated with a first timing advance group (TAG); and the second timing advance value among the multiple timing advance values ​​is associated with a second TAG configured after the first TAG.

[0254] Aspect 27: A method according to any one of Aspects 16 to 25, wherein: the first timing advance value is associated with a first timing advance group (TAG) associated with a first TAG identifier; a second timing advance value among the multiple timing advance values ​​is associated with a second TAG associated with a second TAG identifier; and the first TAG identifier has a lower identifier value than the second TAG identifier.

[0255] Aspect 28: A method according to any one of Aspects 16 to 25, wherein: the first timing advance value is associated with a first timing advance group (TAG); and a second timing advance value among the multiple timing advance values ​​is defined based on an offset time value relative to the first timing advance value.

[0256] Aspect 29: A user equipment comprising: a transceiver configured to communicate with a radio access network; a memory; and a processor coupled to the transceiver and the memory, wherein the processor and the memory are configured to perform any one or more of aspects 1 to 13.

[0257] Aspect 30: An apparatus configured for wireless communication, comprising at least one component for performing any one or more of aspects 1 to 13.

[0258] Aspect 31: A non-transitory computer-readable medium storing computer-executable code, comprising code for causing an apparatus to perform any one or more of aspects 1 to 13.

[0259] Aspect 32: A network entity comprising: a transceiver; a memory; and a processor, the processor being communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to perform any one or more of aspects 16 to 28.

[0260] Aspect 33: An apparatus configured for wireless communication, comprising at least one component for performing any one or more of aspects 16 to 28.

[0261] Aspect 34: A non-transitory computer-readable medium storing computer-executable code, comprising code for causing an apparatus to perform any one or more of aspects 16 to 28.

[0262] Several aspects of wireless communication networks have been presented with reference to example implementations. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures, and communication standards.

[0263] For example, various aspects may be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile (GSM). Various aspects may also be extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution-Data Optimized (EV-DO). Other examples may be implemented within systems employing Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

[0264] Within the present disclosure, the word "exemplary" is used to mean "serving as an example, instance, or illustration". Any specific implementation or aspect described herein as "exemplary" is not necessarily to be construed as superior or superior to other aspects of the present disclosure. Likewise, the term "aspect" does not require that all aspects of the present disclosure include the discussed features, advantages, or modes of operation. The term "coupled" is used herein to refer to a direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, objects A and C may still be considered to be coupled to each other, even if they are not in direct physical contact with each other. For example, a first object may be coupled to a second object, even if the first object has never been in direct physical contact with the second object. The terms "circuit" are used broadly, and they are intended to include both hardware implementations of electronic devices and conductors (where these electronic devices and conductors, when connected and configured, implement the execution of the functions described in the present disclosure, without limitation on the type of electronic circuits) and software implementations of information and instructions (where these information and instructions, when executed by a processor, implement the execution of the functions described in the present disclosure). As used herein, the term "determining" may include, for example, ascertaining, solving, selecting, choosing, establishing, calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, database or other data structure), etc. In addition, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc.

[0265] Figures 1 to 19 One or more of the illustrated components, steps, features and / or functions may be rearranged and / or combined into a single component, step, feature or function, or may be embodied in several components, steps or functions. Additional elements, components, steps and / or functions may also be added without departing from the novel features disclosed herein. Figure 1 , Figure 2 , Figure 3 , Figure 7 , Figure 8 , Fig. 9 , Fig.15 , Fig.16 and Fig.18 The apparatus, device and / or components illustrated in the examples may be configured to perform one or more of the methods, features or steps described herein. The novel algorithms described herein may also be effectively implemented in software and / or embedded in hardware.

[0266] It should be understood that the specific order or hierarchy of steps in the methods disclosed herein is illustrative of example processes. It should be understood that the specific order or hierarchy of steps in these methods may be rearranged based on design preferences. The attached method claims present elements of various steps in an example order, but are not intended to be limited to the specific order or hierarchy presented unless explicitly stated herein.

[0267] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the various aspects shown herein, but to conform to the full scope consistent with the text of the claims, wherein unless explicitly stated otherwise, reference to an element in the singular form is not intended to mean "one and only one", but "one or more". Unless otherwise specified, the term "some" refers to one or more. The phrase "at least one" of a list of items refers to any combination of those items, including a single member. As an example, "at least one of a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are currently or hereafter known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recorded in the claims.

Claims

1. A user equipment, comprising: Transceiver; Memory; and a processor coupled to the memory and the transceiver, wherein the processor and the memory are configured to: receiving, via the transceiver, a first configuration identifying a plurality of timing advance values, receiving, via the transceiver, a second configuration of a first sounding reference signal (SRS) resource set, and A first SRS is transmitted on the first SRS resource set using a first timing advance value selected from the plurality of timing advance values ​​based on a usage associated with the first SRS resource set or a time domain configuration associated with the first SRS resource set via the transceiver.

2. The user equipment of claim 1, wherein the processor and the memory are further configured to: A third configuration is received including a first control resource set pool value and a second control resource set pool value, the first control resource set pool value being associated with the first timing advance value, and the second control resource set pool value being associated with a second timing advance value of the plurality of timing advance values.

3. The user equipment according to claim 2, wherein: The first control resource set pool value is associated with a first transmission and reception point; and The second control resource set pool value is associated with a second sending and receiving point.

4. The user equipment according to claim 1, wherein: The first timing advance value includes a default timing advance value associated with beam management SRS usage or antenna switching SRS usage.

5. The user equipment according to claim 1, wherein: The first SRS resource set is associated with codebook SRS usage or non-codebook SRS usage.

6. The user equipment according to claim 5, wherein: The first SRS resource set is included in an SRS resource set list limited to a single SRS resource set for codebook SRS usage or non-codebook SRS usage; and The first timing advance value includes a default timing advance value.

7. The user equipment of claim 5, wherein the processor and the memory are further configured to: The first timing advance value is selected based on a first identifier associated with the first set of SRS resources.

8. The user equipment according to claim 7, wherein: The first SRS resource set is included in an SRS resource set list including a second SRS resource set; The first SRS resource set is associated with the first timing advance value; The second SRS resource set is associated with a second identifier and a second timing advance value of the plurality of timing advance values; and The first identifier has a lower identifier value than the second identifier.

9. The user equipment of claim 1, wherein: The first timing advance value comprises a default timing advance value associated with a periodic SRS resource set or a semi-persistent SRS resource set.

10. The user equipment of claim 1, wherein: The processor and the memory are further configured to: receive first downlink control information (DCI) scheduling the first SRS resource set as an aperiodic SRS resource set on a first control resource set; The first set of control resources is associated with a first set of control resource pool values ​​among a plurality of set of control resource pool values; and The first timing advance value is associated with the first control resource set pool value.

11. The user equipment of claim 1 , wherein: The first timing advance value is associated with a first timing advance group (TAG); and A second timing advance value among the plurality of timing advance values ​​is associated with a second TAG configured after the first TAG.

12. The user equipment of claim 1, wherein: The first timing advance value is associated with a first timing advance group (TAG) associated with a first TAG identifier; A second timing advance value among the plurality of timing advance values ​​is associated with a second TAG associated with a second TAG identifier; and The first TAG identifier has a lower identifier value than the second TAG identifier.

13. The user equipment of claim 1, wherein: The first timing advance value is associated with a first timing advance group (TAG); and A second timing advance value among the plurality of timing advance values ​​is defined based on an offset time value relative to the first timing advance value.

14. A method for wireless communication at a user equipment, comprising: receiving a first configuration identifying a plurality of timing advance values; receiving a second configuration of a first sounding reference signal (SRS) resource set; as well as A first SRS is transmitted on the first SRS resource set using a first timing advance value selected from the plurality of timing advance values ​​based on a usage associated with the first SRS resource set or a time domain configuration associated with the first SRS resource set.

15. A user equipment comprising: means for receiving a first configuration identifying a plurality of timing advance values; means for receiving a second configuration of a first set of sounding reference signal (SRS) resources; and Means for transmitting a first SRS on the first SRS resource set using a first timing advance value selected from the plurality of timing advance values ​​based on a usage associated with the first SRS resource set or a time domain configuration associated with the first SRS resource set.

16. A network entity, comprising: Transceiver; Memory; and a processor coupled to the memory and the transceiver, wherein the processor and the memory are configured to: transmitting, via the transceiver, a first configuration identifying a plurality of timing advance values, transmitting, via the transceiver, a second configuration of a first sounding reference signal (SRS) resource set, and A first SRS is received via the transceiver on the first SRS resource set based on a first timing advance value among the plurality of timing advance values, the first timing advance value being associated with a usage associated with the first SRS resource set or a time domain configuration associated with the first SRS resource set.

17. The network entity of claim 16, wherein the processor and the memory are further configured to: A third configuration is sent including a first control resource set pool value and a second control resource set pool value, wherein the first control resource set pool value is associated with the first timing advance value, and the second control resource set pool value is associated with a second timing advance value of the plurality of timing advance values.

18. The network entity according to claim 17, wherein: The first control resource set pool value is associated with a first transmission and reception point; and The second control resource set pool value is associated with a second sending and receiving point.

19. The network entity according to claim 16, wherein: The first timing advance value includes a default timing advance value associated with beam management SRS usage or antenna switching SRS usage.

20. The network entity according to claim 16, wherein: The first SRS resource set is associated with codebook SRS usage or non-codebook SRS usage.

21. The network entity according to claim 20, wherein: The first SRS resource set is included in an SRS resource set list limited to a single SRS resource set for codebook SRS usage or non-codebook SRS usage; and The first timing advance value includes a default timing advance value.

22. The network entity according to claim 20, wherein: The processor and the memory are further configured to select the first timing advance value based on a first identifier associated with the first SRS resource set.

23. The network entity according to claim 22, wherein: The first SRS resource set is included in an SRS resource set list including a second SRS resource set; The first SRS resource set is associated with the first timing advance value; The second SRS resource set is associated with a second identifier and a second timing advance value of the plurality of timing advance values; and The first identifier has a lower identifier value than the second identifier.

24. The network entity of claim 16, wherein: The first timing advance value comprises a default timing advance value associated with a periodic SRS resource set or a semi-persistent SRS resource set.

25. The network entity of claim 16, wherein: The processor and the memory are further configured to: send first downlink control information (DCI) scheduling the first SRS resource set as an aperiodic SRS resource set on a first control resource set; The first set of control resources is associated with a first set of control resource pool values ​​among a plurality of set of control resource pool values; and The first timing advance value is associated with the first control resource set pool value.

26. The network entity of claim 16, wherein: The first timing advance value is associated with a first timing advance group (TAG); and A second timing advance value among the plurality of timing advance values ​​is associated with a second TAG configured after the first TAG.

27. The network entity of claim 16, wherein: The first timing advance value is associated with a first timing advance group (TAG) associated with a first TAG identifier; A second timing advance value among the plurality of timing advance values ​​is associated with a second TAG associated with a second TAG identifier; and The first TAG identifier has a lower identifier value than the second TAG identifier.

28. The network entity of claim 16, wherein: The first timing advance value is associated with a first timing advance group (TAG); and A second timing advance value among the plurality of timing advance values ​​is defined based on an offset time value relative to the first timing advance value.

29. A method for wireless communication at a network entity, comprising: sending a first configuration identifying a plurality of timing advance values; sending a second configuration of a first sounding reference signal (SRS) resource set; as well as A first SRS is received on the first SRS resource set based on a first timing advance value among the plurality of timing advance values, the first timing advance value being associated with a usage associated with the first SRS resource set or a time domain configuration associated with the first SRS resource set.

30. A network entity, comprising: means for sending a first configuration identifying a plurality of timing advance values; means for transmitting a second configuration of a first set of sounding reference signal (SRS) resources; and Means for receiving a first SRS on the first SRS resource set based on a first timing advance value among the plurality of timing advance values, the first timing advance value being associated with a usage associated with the first SRS resource set or a time domain configuration associated with the first SRS resource set.

Images