SRS Positioning BWP in RRC inactive or idle positioning

Abstract

A method, apparatus, and computer-readable storage medium for wireless communications are provided. An example method may include transmitting, to a network entity, a capability for transmission of one or more positioning SRSs outside an initial UL BWP during an idle or inactive state of the UE. The example method may further include receiving, from the network entity, a configuration for transmission of one or more positioning SRSs outside the initial UL BWP during an idle or inactive state. The example method may further include transmitting, based on the configuration, the one or more positioning SRSs outside the initial UL BWP to the network entity.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of and priority to U.S. Provisional Patent Application No. 63 / 266,627, entitled "SRS Positioning BWP in RRC Inactive OR Idle Positioning," filed on January 10, 2022, and U.S. Non-Provisional Patent Application No. 17 / 804,528, entitled "SRS POSITIONING BWP IN RRC INACTIVE OR IDLE POSITIONING," filed on May 27, 2022, which are assigned to the assignee of this application and are expressly incorporated by reference in their entireties herein.

[0002] The present disclosure relates generally to communication systems, and more particularly, to wireless communication systems using positioning sounding reference signals (SRS) outside of an initial uplink (UL) bandwidth portion (BWP). [Background technology]

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

[0004] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that allows different wireless devices to communicate at a city, country, region, or even global level. An exemplary telecommunications standard is 5G New Radio (NR). 5G NR is part of the continuing mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., for the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements are needed in 5G NR technology that may also be applicable to other multiple access technologies and the telecommunications standards that employ those technologies. Summary of the Invention

[0005] SUMMARY OF THE DISCLOSURE The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, nor is it intended to identify key or critical elements of all aspects or to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0006] In one aspect of the disclosure, a method, a computer-readable medium, and an apparatus in a user equipment (UE) are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to transmit, to a network entity, a capability for transmission of one or more positioning SRSs outside the initial UL BWP during an idle or inactive state of the UE. The memory and the at least one processor coupled to the memory may be further configured to receive, from the network entity, a configuration for transmission of one or more positioning SRSs outside the initial UL BWP during an idle or inactive state, the configuration including a set of constraints on transmission of the one or more positioning SRSs. The memory and the at least one processor coupled to the memory may be further configured to transmit, to the network entity, one or more positioning SRSs outside the initial UL BWP based on the configuration, the one or more positioning SRSs being transmitted during the idle or inactive state.

[0007] In one aspect of the disclosure, a method, a computer-readable medium, and an apparatus in a base station are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to receive, from the UE, a capability for transmission of one or more positioning SRSs outside the initial UL BWP during an idle or inactive state of the UE. The memory and the at least one processor coupled to the memory may be further configured to transmit a configuration for transmission of one or more positioning SRSs outside the initial UL BWP during an idle or inactive state, the configuration including a set of constraints on transmission of the one or more positioning SRSs. The memory and the at least one processor coupled to the memory may be further configured to receive, from the UE based on the configuration, one or more positioning SRSs outside the initial UL BWP, the one or more positioning SRSs being received during the idle or inactive state.

[0008] To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of the various aspects may be employed and the description is intended to include all such aspects and their equivalents. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 illustrates an example of a wireless communication system and access network. [Figure 2A] FIG. 2 illustrates an example of a first frame in accordance with various aspects of the present disclosure. [Figure 2B] FIG. 1 illustrates an example of a DL channel in a subframe in accordance with various aspects of the present disclosure. [Figure 2C] FIG. 2 illustrates an example of a second frame, according to various aspects of the present disclosure. [Figure 2D] FIG. 1 illustrates an example of a UL channel in a subframe in accordance with various aspects of the present disclosure. [Diagram 3] FIG. 1 illustrates an example of a base station and user equipment (UE) in an access network. [Figure 4A] FIG. 1 is a signal flow diagram for connecting a UE to a transmission / reception point (TRP). [Figure 4B] FIG. 1 is a signal flow diagram for connecting a UE to a transmission / reception point (TRP). [Diagram 5] FIG. 1 is a timing diagram illustrating an example of a time gap (buffer period) between the transmission of an SRS transmission and the transmission of another message. [Figure 6] FIG. 1 is a timing diagram illustrating an example of a time gap (buffer period) between the transmission of an SRS transmission and the transmission of another message. [Figure 7]FIG. 1 is a timing diagram illustrating an example of a timing conflict between an SRS transmission and a subsequently transmitted message. [Figure 8] FIG. 1 is a timing diagram illustrating an example of a timing conflict between an SRS transmission and a subsequently transmitted message. [Figure 9] FIG. 1 illustrates an example spectrum management and configuration. [Figure 10] FIG. 1 illustrates an exemplary resource including a BWP. [Figure 11] FIG. 1 illustrates an example spectrum management and configuration using SRS for positioning. [Figure 12] FIG. 1 illustrates an example spectrum management and configuration using SRS for positioning. [Figure 13] A diagram showing communication between a UE and a network entity. [Figure 14] FIG. 1 is a flow diagram of a method of wireless communication. [Figure 15] FIG. 1 is a flow diagram of a method of wireless communication. [Figure 16] FIG. 2 illustrates an example of a hardware implementation of an exemplary device. [Figure 17] FIG. 2 illustrates an example of a hardware implementation for an exemplary apparatus. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] The detailed description set forth below in conjunction with the accompanying drawings describes various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The Detailed Description includes specific details intended to provide a thorough understanding of the various concepts. However, it will be apparent to one 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 such concepts.

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

[0012] As an example, the elements, or any portion of the elements, or any combination of the elements, may be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout this disclosure. One or more processors in a processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

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

[0014] Although aspects and implementations are described in this application by illustrating some examples, those skilled in the art will understand that additional implementations and use cases may arise in many different configurations and scenarios. The innovations described herein may be realized across many different platform types, devices, systems, shapes, sizes, and packaging configurations. For example, implementations and / or applications may arise with integrated chip implementations and other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). Some examples may or may not be specifically targeted to a use case or application, but a wide variety of applicability of the described innovations may arise. Implementations may range from chip-level or modular components to non-modular, non-chip-level implementations, and even aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementation and practice of the claimed and described aspects. For example, transmitting and receiving wireless signals necessarily involves a number of components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processor(s), interleavers, summers / analog summers, etc.). It is contemplated that the innovations described herein may be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed configurations, aggregated or disaggregated components, end-user devices, etc.

[0015] FIG. 1 illustrates an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes base stations 102, UEs 104, an Evolved Packet Core (EPC) 160, and another core network 190 (e.g., 5G Core (5GC)). The base stations 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). The macro cells include base stations. The small cells include femto cells, pico cells, and micro cells.

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

[0017] The base stations 102 may wirelessly communicate with the UE 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be known as a heterogeneous network. A heterogeneous network may also include home evolved Node Bs (eNBs) (HeNBs) that may provide service to restricted groups known as closed subscriber groups (CSGs). A communication link 120 between the base station 102 and the UE 104 may include uplink (UL) (also referred to as reverse link) transmissions from the UE 104 to the base station 102 and / or downlink (DL) (also referred to as forward link) transmissions from the base station 102 to the UE 104. The communication link 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be over one or more carriers. The base station 102 / UE 104 may use spectrum with a bandwidth of up to YMHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) per carrier, allocated in a carrier aggregation of up to YxMHz (x component carriers) in total, used for transmission in each direction. The carriers may be adjacent or non-adjacent to each other. The carrier allocation may be asymmetric for DL ​​and UL (e.g., more or fewer carriers may be allocated for DL ​​than UL). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell), and the secondary component carrier may be referred to as a secondary cell (SCell).

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

[0019] The wireless communication system may further include a Wi-Fi access point (AP) 150 that communicates with Wi-Fi stations (STAs) 152 via communication links 154, such as in the 5 GHz unlicensed frequency spectrum. When communicating in the unlicensed frequency spectrum, the STAs 152 / AP 150 may perform a clear channel assessment (CCA) prior to communication to determine if a channel is available.

[0020] The small cell 102' may operate in a licensed and / or unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102' may employ NR and use the same unlicensed frequency spectrum (e.g., 5 GHz, etc.) used by the Wi-Fi AP 150. By employing NR in the unlicensed frequency spectrum, the small cell 102' may enhance coverage to and / or increase capacity of the access network.

[0021] The electromagnetic spectrum is often subdivided into various classes, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is higher than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and papers. A similar nomenclature issue may arise with respect to FR2, which is often referred to (interchangeably) as the "millimeter wave" band in documents and papers, even though it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunications Union (ITU).

[0022] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified operating bands for these mid-band frequencies as a frequency range designation FR3 (7.125 GHz to 24.25 GHz). Frequency bands that fall within FR3 may inherit FR1 and / or FR2 characteristics, and thus, in effect, extend the features of FR1 and / or FR2 to the mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0023] With the above aspects in mind, it should be understood that unless otherwise specified, terms such as "sub-6 GHz" as used herein may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, it should be understood that unless otherwise specified, terms such as "millimeter wave" as used herein may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0024] The base station 102, whether a small cell 102′ or a large cell (e.g., a macro base station), may include and / or be referred to as an eNB, g Node B (gNB), or another type of base station. Some base stations, such as the gNB 180, may operate at millimeter wave and / or quasi-millimeter wave frequencies in the conventional sub-6 GHz spectrum in communication with the UE 104. When the gNB 180 operates at millimeter wave or quasi-millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. The base station 180 may utilize beamforming 182 with the UE 104 to compensate for path loss and short distances. The base station 180 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming.

[0025] The base station 180 may transmit a beamformed signal to the UE 104 in one or more transmit directions 182′. The UE 104 may receive the beamformed signal from the base station 180 in one or more receive directions 182″. The UE 104 may also transmit a beamformed signal to the base station 180 in one or more transmit directions. The base station 180 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 180 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 180 / UE 104. The transmit and receive directions for the base station 180 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.

[0026] The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may communicate with a Home Subscriber Server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are forwarded through the Serving Gateway 166, which is itself connected to the PDN Gateway 172. The PDN Gateway 172 provides IP address allocation for the UE as well as other functions. The PDN Gateway 172 and the BM-SC 170 are connected to IP services 176, which may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), PS streaming services, and / or other IP services. The BM-SC 170 may provide functionality for provisioning and delivery of MBMS user services. The BM-SC 170 may act as an entry point for content providers' MBMS transmissions and may be used to authorize and initiate MBMS bearer services in the public land mobile network (PLMN) and may be used to schedule MBMS transmissions.The MBMS Gateway 168 can be used to distribute MBMS traffic to base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and can be responsible for session management (start / stop) and collection of eMBMS related charging information.

[0027] The core network 190 may include an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may communicate with a Unified Data Management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. In general, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are forwarded through the UPF 195. The UPF 195 provides IP address allocation for the UE as well as other functions. The UPF 195 is connected to IP Services 197. The IP services 197 may include the Internet, an intranet, IP Multimedia Subsystem (IMS), Packet Switch (PS) Streaming (PSS) services, and / or other IP services.

[0028] A base station may include and / or be referred to as a gNB, Node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit / receive point (TRP), or some other suitable terminology. The base station 102 provides an access point to the EPC 160 or core network 190 for the UE 104. Examples of the UE 104 include a cellular phone, a smartphone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small cooking appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). The UEs 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, handsets, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device constellation configuration. One or more of these devices may collectively access the network and / or may individually access the network.

[0029] Referring again to FIG. 1, in some aspects, the UE 104 may include an SRS component 198. In some aspects, the SRS component 198 may be configured to transmit to a network entity a capability for transmission of one or more positioning SRS outside of an initial UL BWP during an idle or inactive state of the UE. In some aspects, the SRS component 198 may be further configured to receive a configuration for transmission of one or more positioning SRS outside of an initial UL BWP during an idle or inactive state from the network entity, the configuration including a set of constraints on the transmission of the one or more positioning SRS. In some aspects, the SRS component 198 may be further configured to transmit one or more positioning SRS outside of an initial UL BWP to a network entity based on the configuration, the one or more positioning SRS being transmitted during an idle or inactive state.

[0030] In some aspects, the base station 180 may include an SRS component 199. In some aspects, the SRS component 199 may be configured to receive from the UE a capability for transmission of one or more positioning SRS outside the initial UL BWP during an idle or inactive state of the UE. In some aspects, the SRS component 199 may be further configured to transmit a configuration for transmission of one or more positioning SRS outside the initial UL BWP during an idle or inactive state, the configuration including a set of constraints on the transmission of the one or more positioning SRS. In some aspects, the SRS component 199 may be further configured to receive from the UE one or more positioning SRS outside the initial UL BWP based on the configuration, the one or more positioning SRS being received during an idle or inactive state.

[0031] The following description may focus on 5G NR, however, the concepts described herein may be applicable to other similar domains, such as LTE, LTE-A, CDMA, Wideband CDMA (WCDMA), Global System for Mobile Communications (GSM), and other wireless technologies.

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

[0033] 2A-2D show a frame structure, and aspects of the present disclosure may be applicable to other wireless communication technologies, which may have different frame structures and / or different channels. A frame (10 ms) may be divided into 10 subframes (1 ms) of equal size. Each subframe may include one or more time slots. A subframe may also include a minislot, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each slot may include 14 symbols, and for extended CP, each slot may include 12 symbols. The symbols on the DL may be CP orthogonal frequency division multiplexing (CP-OFDM) symbols. The symbols on the UL can be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also called single carrier frequency division multiple access (SC-FDMA) symbols) (for power limited scenarios, i.e. limited to single stream transmission). The number of slots in a subframe is based on the CP and numerology, which defines the subcarrier spacing (SCS), which effectively defines the symbol length / period equal to 1 / SCS.

[0034] [Table 1]

[0035] For the normal CP (14 symbols / slot), the different numerologies μ0-4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For the extended CP, numerology 2 allows 4 slots per subframe. Thus, for the normal CP and numerology μ, 14 symbols / slot and 2 μ There are slots / subframes. The subcarrier spacing is 2 μ * may be equal to 15 kHz, where μ is numerology 0 to 4. Thus, numerology μ=0 has a subcarrier spacing of 15 kHz, and numerology μ=4 has a subcarrier spacing of 240 kHz. The symbol length / period is inversely proportional to the subcarrier spacing. Figures 2A-2D provide an example of a normal CP with 14 symbols per slot, and numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a set of frames, there may be one or more different Bandwidth Parts (BWPs) (see Figure 2B), which are frequency division multiplexed. Each BWP may have a specific numerology and CP (normal or extended).

[0036] A resource grid may be used to represent the frame structure. Each time slot contains resource blocks (RBs) (also called physical RBs (PRBs)), spanning 12 consecutive subcarriers. The resource grid is divided into resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0037] As shown in Figure 2A, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include demodulation RS (DM-RS) (shown as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

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

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

[0040] 2D shows an example of various UL channels within a subframe of a frame. The PUCCH may be arranged as shown in one configuration. The PUCCH carries uplink control information (UCI) such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCIs.

[0041] 3 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functions. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 is responsible for RRC layer functions associated with broadcasting system information (e.g., MIBs, SIBs), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), mobility between radio access technologies (RATs), and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with forwarding higher layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and mapping of logical channels to transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), MAC SDUs from TBs, and MAC SDUs from TBs. It provides the MAC layer functions associated with demultiplexing of SDUs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

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

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

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

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

[0046] Channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select an appropriate coding and modulation scheme as well as to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters (e.g., TXs within the receiver 354). Each transmitter (e.g., TXs within the receiver 354) may modulate an RF carrier with a respective spatial stream for transmission.

[0047] The UL transmissions are processed at the base station 310 in a manner similar to that described with respect to the receiver functions at the UE 350. Each receiver (e.g., RX in transmitter 318) receives a signal through its respective antenna 320. Each receiver (e.g., RX in transmitter 318) recovers the information modulated onto the RF carrier and provides the information to the RX processor 370.

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

[0049] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to implement aspects associated with the SRS component 198 of FIG.

[0050] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to implement aspects associated with the SRS component 199 of FIG.

[0051] A collection of resource elements used for transmission of SRS is called an "SRS resource". The collection of resource elements may span multiple PRBs in the frequency domain and N (e.g., one or more) consecutive symbol(s) in a slot in the time domain. Within a given OFDM symbol, the SRS resource occupies consecutive RBs. An SRS resource is described by at least the following parameters: SRS resource identifier (ID), sequence ID, comb size-N, resource element offset in the frequency domain, starting slot and starting symbol, number of symbols per SRS resource (i.e., duration of the SRS resource), and quasi-collocation (QCL) information. Currently, one antenna port is supported. The comb size indicates the number of subcarriers in each symbol carrying the SRS.

[0052] An "SRS resource set" may be a set of SRS resources used for transmission of an SRS signal, where each SRS resource has an SRS resource ID. In addition, SRS resources in an SRS resource set are associated with the same UE. An SRS resource set is identified by an SRS resource set ID. An SRS resource ID in an SRS resource set is associated with a single beam (and / or beam ID) transmitted from the UE. That is, each SRS resource in an SRS resource set may be transmitted on a different beam.

[0053] An "SRS occasion" may be one instance of a periodically repeating time window (e.g., a group of one or more contiguous slots) during which an SRS is expected to be transmitted. An SRS occasion may also be referred to as an "SRS instance," an "SRS positioning occasion," a "positioning occasion," or simply an "opportunity."

[0054] A "BWP associated with a positioning SRS" or a "BWP associated with a positioning SRS" may be a defined BWP associated with a positioning SRS, or may be a virtual BWP implicitly defined (e.g., by inheritance) based on the location and bandwidth parameters, SCS, or cyclic prefix (CP) configured for the SRS.

[0055] It should be noted that the terms "positioning sounding reference signal" and "positioning SRS" sometimes refer to specific reference signals used for positioning in LTE systems. Although the discussion herein refers to sounding reference signals and SRS, the discussion may apply to other types of positioning signals. The term "positioning SRS" may refer to and be used interchangeably with the term "positioning SRS."

[0056] With reference to FIG. 4A and with further reference to FIGS. 1-3, a TRP 401 (e.g., of a base station 120) and a UE 402 (e.g., a UE 104) may be configured to communicate with each other according to a signal flow 400 to establish an RRC connection of the UE 402 to a communication network including the TRP 401 (e.g., including the base station 102 / 180 shown in FIG. 1). A wireless device may include multiple TRPs. Each TRP may include a different RF module with a shared hardware and / or software controller. Each TRP may have separate RF and digital processing. Each TRP may also perform separate baseband processing. Each TRP may include a different antenna panel or a different set of antenna elements of the wireless device. The TRPs of a wireless device may be physically separated. The spacing between the TRPs may vary based on the size of the vehicle and / or the number of TRPs associated with the vehicle. Each of the TRPs may experience the channel differently (e.g., may experience different channel quality) due to different physical locations, distance between the TRPs, different line-of-sight (LOS) characteristics (e.g., LOS channels compared to non-LOS (NLOS) channels), blocking / obstructions, interference from other transmissions, among other reasons. In some aspects, the signal flow 400 may occur while the UE 402 is in an unconnected state, in which the UE 402 is not connected from the communication network of the TRP 401. In the unconnected state, the UE 402 is not connected or synchronized to the communication network, does not have an active BWP (bandwidth portion), and cannot transmit information to or receive information from the communication network using unicast transmission. Examples of unconnected states include RRC idle, RRC inactive, and discontinuous reception (DRX) states, e.g., in a long DRX cycle or off duration of the DRX mode. The UE may be configured by the base station for a mode that saves power. In the DRX mode, the UE may be configured with periodic on and off durations. The UE may monitor the PDCCH during the on duration to identify whether it has downlink (DL) / uplink (UL) data.If the UE determines that it may have DL / UL data, it may remain awake for another amount of time, which may be defined based on an inactivity timer. If the UE identifies that it does not have DL / UL data, it may go to sleep and enter an off duration. During the off duration, the UE may, for example, skip monitoring the PDCCH. Signal flow 400 is a four-step process using a Random Access Channel (RACH) to connect the TRP 401 and the UE 402. Once connected, the UE 402 and the TRP 401 may exchange unicast messages. Signal flow 400 may be followed to transition from an unconnected state of the UE 402 (i.e., the UE 402 is outside of a connected state with a communication network, e.g., via and including the TRP 401) to a connected state. For example, signal flow 400 may be followed when the UE 402 is powered on or wakes up from sleep, or when transitioning from an RRC idle state or an RRC inactive state (in either of which the UE 402 is not connected) to an RRC connected state.

[0057] In step 410 of the signal flow 400, the TRP 401 may transmit synchronization information in an SSB message and a SIB1 message that includes the synchronization information. The TRP 401 broadcasts the SSB and the SIB1 message. The UE 402 may receive the SSB and identify the SIB1 message based on the SSB. The UE 402 may receive the SIB1 message from the TRP 401.

[0058] From the SIB1 message, the UE 402 determines one or more transmission properties of a RACH preamble sequence to be transmitted in the first message MSG1 to the TRP 401 in step 411. The UE 402 may select a RACH preamble sequence and determine a RACH occasion (RO) (which may occur periodically, e.g., every 10 ms, 20 ms, 40 ms, 80 ms, 160 ms) according to the SSB-to-RO mapping for transmitting the RACH preamble. For example, the UE 402 may determine to transmit the RACH preamble at the next RACH occasion (in time). The RO is the time / frequency occasion for the UE 402 to transmit the RACH preamble. There may be different RACH preamble formats and correspondingly different RO sizes. The RACH preamble sequence may be selected from a set of RACH preamble sequences. In some aspects, the preamble format may be one or more of format 0, format 1, format 2, format 3, format A1, format A2, format A3, format B1, format B2, format B3, format B4, format C0, format C1, etc. Each of the preamble formats may be associated with a different cyclic prefix (CP) and a different preamble sequence. The preamble formats may be grouped into two categories: long preambles and short preambles. As an example, a long preamble may last longer than 1 ms in the time domain, and a short preamble may last shorter than 1 ms in the time domain. For example, the long preamble may be based on a sequence length of L=839. The long preamble may include preamble format 0, format 1, format 2, and format 3. As an example, the SCS associated with the long preamble may be 1.25 kHz or 5 kHz. The long preamble may be used for the FR1 frequency band. A long preamble with an SCS of 1.25 kHz may, as an example, occupy six resource blocks in the frequency domain.A long preamble with 5 kHz may occupy 24 resource blocks in the frequency domain, as an example. A short preamble may include preamble format A1, format A2, format A3, format B1, format B2, format B3, format B4, format C0, format C1. In some aspects, a short preamble may be based on a sequence length of L=139. In some aspects, an SCS associated with a short preamble may be 15 kHz, 30 kHz, 60 kHz, 120 kHz, etc. A short preamble may occupy 12 resource blocks in the frequency domain, as an example, regardless of the preamble numerology. In some aspects, the last part of each OFDM symbol in a short preamble may serve as a CP for the next OFDM symbol. In some aspects, the length of a preamble OFDM symbol may be equal to the length of a data OFDM symbol. In some aspects, multiple short preambles may be multiplexed in time within a single RO. The RACH preamble may be transmitted with an identifier such as a Random Access RNTI (RA-RNTI). Due to antenna reciprocity, the UE 402 may determine which receive (Rx) beam best received the synchronization signal (e.g., SSB) and select the corresponding transmit (Tx) beam for transmitting the RACH preamble. If reciprocity holds in the TRP 401, the UE 402 may transmit MSG1 once, otherwise it may repeat the MSG1 message for each of the TRP Tx beams. The UE 402 may be configured to transmit the first message MSG1 using a physical RACH (PRACH).

[0059] The TRP 401 may be configured to respond to the MSG1 message transmitted in stage 411 (also referred to as step 1) by transmitting a response or second message MSG2 in stage 412 (also referred to as step 2). The response message MSG2 may be a random access response (RAR) UL grant that the TRP 401 transmits using a Physical Downlink Shared Channel (PDSCH) with the selected beam. The second message MSG2 may acknowledge the reception of the first message MSG1 and provide some collision avoidance information. Based on the messages MSG1, MSG2, the TRP 401 and the UE 402 may establish a coarse beam alignment that can be used in stages 413, 414 discussed below.

[0060] The UE 402 may be configured to receive the response message MSG2 and respond in stage 413 (also referred to as step 3) by transmitting a third message MSG3 using resources scheduled by the TRP 401. Thus, the TRP 401 knows where to detect the third message MSG3 and which TRP Rx beam should be used to detect the third message MSG3. The UE 402 may be configured to transmit the third message MSG3 using a physical uplink shared channel (PUSCH) using the same beam or a different beam than the UE 402 used to transmit the first message MSG1.

[0061] In stage 414 (also referred to as step 4), TRP401 acknowledges receipt of the third message MSG3 by transmitting a fourth message MSG4 on the PDSCH using the TRP Tx beam determined in stage 413. At this point, UE402 may have identified synchronization between TRP401 and UE402, may have identified resources for transmission and reception, and may be connected to a communications network (via and including TRP401), i.e., is in a connected state (RRC connected state).

[0062] Also referring to FIG. 4B, TRP 451 (e.g., of base station 102 / 180) and UE 452 (e.g., UE 104) are configured to communicate with each other according to signal flow 450 to establish an RRC connection of UE 452 to a communication network including TRP 451. Signal flow 450 is a two-step process using RACH to connect TRP 451 and UE 452. Signal flow 450 is essentially a two-step version of the four-step signal flow 400 shown in FIG. 4A. In step 460, UE 452 receives SSB and SIB1. In step 461 (step 1 of the two-step process), UE 452 transmits an initial message MSGA after receiving SSB and SIB1. The initial message MSGA uses both PRACH and PUSCH. In step 462 (step 2 of a two-step process), TRP451 sends a response message MSGB to UE452 to connect UE452 to TRP451.

[0063] A situation may arise when a UE is in an unconnected state with respect to a communication network and is configured to transmit an SRS for positioning while performing a four-step or two-step PRACH process (e.g., as shown in FIG. 4A and FIG. 4B, respectively). A collision avoidance scenario is considered in which the UE is configured to transmit an SRS for positioning in an unconnected state using an initial UL BWP. The initial UL BWP in this situation may include a BWP used to transmit a PUSCH / PUCCH / SRS in a legacy scenario. The initial DL BWP may include a BWP used to receive a PDCCH for paging, etc. in the DL. However, when a UE is configured to transmit an SRS for positioning in an unconnected state using a BWP different from the initial UL BWP, thereby specifying retuning, it is not clear what qualifies as a "collision" in view of the fact that a period is required to retune both before and after the transmission of the SRS occurrence. The BWP in which the SRS is transmitted may be referred to herein as the SRS BWP.

[0064] Some aspects herein provide for establishing a time gap (or time window) that identifies collisions and establishes an action time to drop SRS transmission for collision avoidance when transmission of SRS during a disconnected state is configured outside of the initial UL BWP. Some aspects can leverage the established SRS switching time (e.g., an "SRS-SwitchingTimeNR" parameter or information element (IE)), and the UE performs a full RF retuning by switching between receiving and / or transmitting messages in the bandwidth of a first component carrier (CC) and transmitting SRS in a second CC. In some aspects, the SRS switching time may correspond to the UL BWP switching time, and the BWP switching delay may be determined by the slot length and the UE capability (e.g., Type 1 or Type 2). For example, for slot lengths of 1, 0.5, 0.25, and 0.125 ms, the BWP switching delays may be 1, 2, 3, and 6 slots in length for UEs with Type 1 capability, and 3, 5, 8, and 18 for UEs with Type 2 capability, respectively.

[0065] FIG. 5 is a timing diagram 500 illustrating a generalized scenario in which the TRP transmits a DL message 510 followed by the UE transmitting an SRS instance 520 and an UL message 530. The DL message 510 and / or the UL message 530 may be transmitted as part of a PRACH process, for example, while the UE is operating in an unconnected state (e.g., as shown in FIG. 4 and FIG. 5). Furthermore, the SRS instance 520 may be transmitted according to an SRS configuration, which may specify a particular SRS BWP, cyclic prefix (CP), and / or subcarrier spacing (SCS). As mentioned above, the SRS BWP may be different from the initial UL BWP used by the UE to transmit messages as part of the PRACH process. The first time gap 540 includes the length of time between the DL message 510 and the SRS instance 520, and the second time gap 550 includes the length of time between the SRS instance 520 and the UL message 530.

[0066] 6 is a timing diagram 600 similar to FIG. 5 in which the TRP transmits a first DL message 610 and the UE transmits an SRS instance 620. However, here, after the SRS instance 620, the TRP transmits a second DL message 630. A first time gap 640 includes the amount of time between the first DL message 610 and the SRS instance 620, and a second time gap 650 includes the amount of time between the SRS instance 620 and the second DL message 630.

[0067] Timing conflicts may occur between messages on either side of a time gap (e.g., 540, 550, 640, and 650) if the time gap is shorter than the minimum time gap required to avoid conflicts. In particular, the minimum time gap may be associated with RF tuning (if necessary) performed by the UE to transmit an SRS instance (e.g., 520 or 620) or a subsequent message (e.g., UL message 530 or second DL message 630). According to some aspects, if the initial BWP (e.g., in which DL messages 510, 610, and 630 and UL message 530 are transmitted) has the same center frequency as the SRS BWP (in which SRS instances 520 and 620 are transmitted), the minimum time gap may be relatively short, one OFDM symbol (its actual duration may vary depending on the SCS used). In other aspects, the minimum time gap may be larger or smaller.

[0068] For example, if the initial BWP and the SRS BWP have a common center frequency, the minimum time gap may be 1, 2, 3, or N symbols, where N is any number of symbols. According to some aspects, if a timing conflict occurs between a scheduled SRS instance and another message (e.g., the time gap between the SRS instance and the other message is less than the minimum time gap), the SRS instance may be dropped. Further, according to some aspects, all subsequent SRS instances of the SRS configuration may be dropped.

[0069] In some aspects, the UE may drop an SRS instance if it occurs in the same slot as a PRACH or is within N symbols of a PRACH. In other words, for SRS transmission in RRC_INACTIVE state, the UE does not transmit an SRS in the same slot as a PRACH or when the gap between the first or last symbol of a PRACH transmission in a first slot is separated by less than N symbols from the last or first symbol, respectively, of an SRS transmission in a second slot, where N=2 if μ=0 or μ=1, and N=4 if μ=2 or μ=3, and μ is the SCS setting of the initial UL BWP if the SRS is associated with the initial UL BWP, or the SRS setting if a separate SCS is provided.

[0070] In aspects where the SRS BWP used to transmit the SRS has a different center frequency than the initial BWP (e.g., a common center frequency is not possible), RF retuning may be specified by the UE, so that the minimum time gap between DL messages and SRS instances (e.g., time gaps 540, 640, and 650) may be relatively large (e.g., greater than one OFDM symbol). A similar minimum time gap with similar retuning may apply to the time gap between an SRS instance using the SRS BWP and a UL message using an initial UL BWP (different from the SRS BWP) (e.g., time gap 550). In such cases, the minimum time gap may be set as an SRS switching time (e.g., SRS-SwitchingTimeNR parameter), which may be selected from a set of enumerated values. In some aspects, a DL SRS switching time (e.g., a switching time between an SRS instance and a DL message, such as time gaps 540, 640, and 650) may be set to a first value and a UL SRS switching time (e.g., a switching time between an SRS instance and another UL message, such as time gap 550) may be set to a second value that may be the same as or different from the first value. According to some aspects, the SRS switching times (e.g., including the UL SRS switching time and / or the DL SRS switching time) may be set to a particular time value, such as 0 μs, 30 μs, 100 μs, 140 μs, 200 μs, 300 μs, 500 μs, or 800 μs.

[0071] According to some aspects, when a collision occurs during an unconnected state of the UE, an action time for the SRS may be established. The action time is the time at which the next collision may be identified for resolution. In other words, if the next collision is identified after the collision time, the collision may be unavoidable since transmissions (e.g., of an SRS instance) may already be pipelined. Figures 7 and 8 show how the action time for the SRS may be determined in an unconnected state.

[0072] 7 is a timing diagram 700 similar to those of FIGS. 5 and 6, illustrating a scenario in which a UE may be scheduled to follow the transmission of a first message 710 by the TRP along with the transmission of both an SRS instance 720 and a second message 730. Here, the first message 710 may correspond to any DL reception while the UE is in an unconnected state, such as SSB, SIB1, MSG2, or MSG4 of FIG. 4A, or SIB1 or MSGB of FIG. 4B, and the second message 730 may correspond to a response UL message, such as MSG1 or MSG3, or MSGA of FIG. 5. Because the SRS BWP may be different from the initial DL BWP in which the UE receives the first message 710, the UE may use a first switching period 740 to perform RF tuning so that it can transmit the SRS instance 720 via the SRS BWP. Similarly, because the initial UL BWP in which the UE transmits the second message 730 may be different from the SRS BWP, the UE may use the second switching period 750 to be able to transmit the second message 730 via the initial UL BWP. As shown, the second switching period 750 extends into the time in which the second message 730 should be transmitted, thereby creating a conflict. (A conflict may also occur when the second message 730 directly overlaps with the SRS instance 720 itself.) Because there may be a conflict between the SRS instance 720 and the second message 730, the UE may omit transmitting the SRS instance 720 and (optionally) all subsequent SRS instances in the SRS configuration (e.g., in accordance with the collision avoidance method described above). To ensure that the UE successfully drops the transmission of the SRS instance 720, the UE may identify the conflict at a time 760 prior to the start of the first switching period 740. FIG. 8 illustrates how a specific action time may be determined.

[0073] FIG. 8 is a timing diagram 800 illustrating a conflict similar to FIG. 7, illustrating a scenario in which a UE is scheduled to follow the transmission of a first message 810 by a TRP with the transmission of both an SRS instance 820 and a second message 830, the SRS instance 620 being preceded by a first switching period 840 and followed by a second switching duration 860. Point 850 marks the start of the first switching period 840 and indicates the point in time when, according to some aspects, the transmission of the SRS instance 820 is already pipelined and can no longer be cancelled. Thus, point 880 precedes the transmission of the SRS instance 820 by the switching duration 860 of the first switching period 840 and marks the time at which the UE may identify a conflict between the transmission of the SRS instance 820 and the second message 830 (and must cancel the transmission of the SRS instance 820). In many situations (e.g., PRACH process), the first message 810 may include Downlink Control Information (DCI) that schedules the transmission of the second message 830. Furthermore, it takes a period of time (defined as N2), shown as the decoding duration 870 in FIG. 8, for the UE to decode the first message 810. Thus, the UE can avoid the conflict (e.g., by canceling the transmission of the SRS instance 820) if the first message 810 is received before point 880, which is an action time that precedes the transmission of the SRS instance 820 by a duration 890 that includes the sum of the decoding duration 870 and the switching duration 860. According to some aspects, the duration 890 can be measured as the time interval between the last symbol of the first message 810 and the first symbol of the SRS instance 820.

[0074] More generally, for an SRS transmission by a UE in an unconnected state where the SRS transmission uses an SRS BWP having a different center frequency than the initial BWP in which the DL message is transmitted, aspects provided herein can use an action time during which a DL message scheduling a UL message should be transmitted so that the UE can determine whether a conflict exists. This action time can precede the transmission of the SRS instance by a duration that includes the sum of (i) the time it takes the UE to decode the DL message (e.g., the established N2 period) and (ii) an SRS switching time that precedes the transmission of the SRS instance. As discussed above, the SRS switching time can be a single symbol if the SRS BWP and the initial BWP have the same center frequency. If the SRS BWP and the initial BWP have different center frequencies, a longer switching time (e.g., a larger number of symbols) can be established. The use of this action time can be applied, for example, when the DL message includes a Physical Downlink Control Channel (PDCCH) that schedules a UL message including a PUCCH, or when the DL message includes a PDSCH that schedules a UL message including a PUSCH.

[0075] This can be implemented as follows for two specific situations: First, for an SRS in RRC_Inactive that is not associated with a UL BWP, the UE may apply prioritization / dropping between the SRS and msg3 transmissions considering DCI(s) whose time interval between the last symbol of the PDCCH and the first symbol of the SRS is at least N2+SRSSwitchingTime (e.g., as shown in FIG. 4A). Second, for an SRS in RRC_Inactive that is not associated with a UL BWP, the UE may apply prioritization / dropping between the SRS and PUCCH transmissions considering DCI(s) whose time interval between the last symbol of the PDCCH and the first symbol of the SRS is at least N2+SRSSwitchingTime.

[0076] In some wireless communication systems, several examples may be supported for positioning SRS transmission by an RRC inactive UE. A first example may be according to UE capabilities, where the UE may be configured with a positioning SRS associated with an initial UL BWP and may transmit in the initial UL BWP during an RRC inactive state using the same CP and SCS as configured for the initial UL BWP. A second example may be according to UE capabilities, where the UE may be configured with a positioning SRS and the following parameters are further configured for positioning SRS transmission during an RRC inactive state: frequency location and bandwidth, SCS, or CP length. The UE may not transmit a positioning SRS when it is expected (e.g., scheduled) to perform an UL transmission in an initial UL BWP in an RRC inactive state (which may be indicated as "RRC_INACTIVE"). In some aspects, a positioning SRS for a UE in an RRC inactive state may be configured using an SRS-PosResourceSet information element (IE) (e.g., an IE indicating an SRS positioning resource set). Aspects provided herein may provide signaling for an SRS for positioning configuration of an RRC inactive UE. In some aspects, the SRS-PosResourceSet IE may also include a slot-level periodicity and a slot-level offset, which represent higher layer parameters and may be represented by an IE periodicityAndOffset-p or an IE periodicityAndOffset-sp. In some aspects, for an SRS for positioning configured using the SRS-PosResourceSet IE, a reference RS associated with the RS may be a DL positioning reference signal (PRS) configured on the serving cell, an SS / PBCH block, or a DL PRS of a non-serving cell indicated by higher layer parameters.

[0077] Different types of BWP capabilities for connected UEs may be provided. For example, BWP operation may be without restriction on the BW of the BWP(s). The BW of the UE-specific RRC configured BWP may not include the BW of CORESET#0 (if CORESET#0 exists) and SSBs for the Primary Cell (PCell) or Primary Secondary Cell (PSCell) (if configured), and the BW of the UE-specific RRC configured BWP may not include SSBs for the SCell. For Type A BWP adaptation with the same numerology, the list of specifications may apply: 1) up to two UE-specific RRC configured DL BWPs per carrier, 2) up to two UE-specific RRC configured UL BWPs per carrier, 3) active BWP switching via downlink control information (DCI) and timer, 4) same numerology for all UE-specific RRC configured BWPs per carrier, 5) BW of UE-specific RRC configured BWP includes BW of CORESET#0 (if CORESET#0 exists) and SSB for PCell / PSCell (if configured), and BW of UE-specific RRC configured BWP includes SSB for SCell if SSB exists on SCell. For Type-B BWP adaptation with the same numerology, the list of specifications may apply: 1) up to 4 UE-specific RRC configured DL BWPs per carrier, 2) up to 4 UE-specific RRC configured UL BWPs per carrier, 3) active BWP switching by DCI and timer, 4) same numerology for all UE-specific RRC configured BWPs per carrier, and 5) BW of UE-specific RRC configured BWP includes BW of CORESET#0 (if CORESET#0 exists) and SSB for PCell / PSCell (if configured), and BW of UE-specific RRC configured BWP includes SSB for SCell if SSB exists on SCell.In case of BWP adaptation with different numerologies, the list of specifications may apply: 1) up to 4 UE-specific RRC configured DL BWPs per carrier, 2) up to 4 UE-specific RRC configured UL BWPs per carrier, 3) active BWP switching by DCI and timer, 4) multiple numerologies for UE-specific RRC configured BWPs per carrier, 5) same numerology between DL and UL per cell except for SUL at a given time, and 6) BW of UE-specific RRC configured BWP includes BW of CORESET#0 (if CORESET#0 exists) and SSB for PCell / PSCell (if configured), and BW of UE-specific RRC configured BWP includes SSB for SCell if SSB exists on SCell.

[0078] An example BWP information element (IE) may be provided below.

[0079]

number

[0080] The locationAndBandwidth parameter may indicate the frequency domain location and the bandwidth of this bandwidth portion. The value of the field may be interpreted as a Resource Indicator Value (RIV). The first PRB may be the PRB determined by the SCS of this BWP (indicated by the parameter subcarrierSpacing) and the offset corresponding to this subcarrier spacing (indicated by the offsetToCarrier parameter, which may be configured in the SCS-SpecificCarrier parameter indicating the carrier contained in the DL or UL frequency information such as FrequencyInfoDL / FrequencyInfoUL / FrequencyInfoUL-SIB / FrequencyInfoDL-SIB parameters in the serving cell configuration such as ServingCellConfigCommon / ServingCellConfigCommonSIB). In case of TDD, a BWP pair (UL BWP and DL BWP with the same bwp-Id) may have the same center frequency.

[0081] In some wireless communication systems, for a UE in RRC_INACTIVE state that can support DL PRS processing outside and inside the initial DL BWP, for DL ​​PRS processing outside the initial DL BWP, the SCS, CP type of the DL PRS may be the same or different as for the initial DL BWP. For DL ​​PRS processing inside the initial DL BWP, the SCS, CP type of the DL PRS may be the same as for the initial DL BWP. This may have potential impacts on DL positioning reference signal (PRS) reception performance for retuning time and expected relative timing difference (RSTD) assistance information. UE capabilities may be defined for DL ​​PRS processing in RRC_INACTIVE state.

[0082] In some wireless communication systems, for spatial relationship of SRS for positioning by RRC_INACTIVE UE, the validity criteria of path loss measurement (OLPC) may be reused to determine the validity of the spatial relationship for the configured RS. If the UE determines that it cannot meet the above validity criteria for the spatial relationship, the UE may stop transmitting the SRS resource for positioning. The RS for the spatial relationship is a periodic or semi-persistent RS. FIG. 9 is a diagram 900 illustrating an example spectrum management and configuration.

[0083] As shown in FIG. 9, within an operating band 902, there may be a spectrum 904 for an operator. Within the spectrum 904, a BWP 916 may start at a common RB and may include a set of contiguous RBs associated with a numerology (SCS and CP) on a carrier. The BWP 916 may extend from the start of a channel cell-specific channel bandwidth 912 to the RB start926. The carriers may be associated with a channel bandwidth 910. The channel bandwidth 910 may correspond to a cell-specific channel bandwidth 912. The cell-specific channel bandwidth 912 may occur after a number of RBs after a reference point 930 (point A). In some aspects, the reference point 930 may be a common reference point of the RB grid. In some aspects, the difference between the reference point 930 and the cell-specific channel bandwidth may be a cell-specific offset with respect to the carrier 922. The network may configure a UE-specific channel bandwidth 914 for the UE. The difference between the reference point 930 and the UE-specific channel bandwidth 914 may be a UE-specific offset with respect to the carrier 924. For each serving cell of the UE, the network may configure the UE with at least one UL BWP as an initial DL BWP. The network may configure the UE with one or more DL BWPs, such as up to four DL BWPs. In some aspects, one DL BWP may be active at a time. For each serving cell of the UE, the network may configure the UE with at least one UL BWP as the initial UL BWP. The network may configure the UE with one or more UL BWPs, such as up to four DL BWPs. In some aspects, one UL BWP may be active at a time. In some aspects, the UE may receive PDSCH, PDCCH, or CSI-RS in the active DL BWP. The UE may perform radio resource management (RRM) measurements outside the active DL BWP via measurement gaps. The UE may transmit PUSCH or PUCCH inside the active UL BWP. For an active serving cell, the UE may not transmit SRS outside the active UL BWP.

[0084] FIG. 10 is a diagram 1000 illustrating example resources including BWPs. BWP switching delays may depend on the SCS. When BWP switching occurs between BWPs with different SCS values, the switching delay specification may be determined based on the smaller SCS. As shown in FIG. 10, the UE may synchronize and acquire MIBs from the network at 1002. The UE may perform downlink synchronization and acquire PBCH at 1002. In some aspects, initial DL and UL BWPs may be used for at least initial access before a radio resource control (RRC) connection is established. The first BWP has index 0 and may be referred to as BWP#0. During the initial connection, the UE may perform cell search based on SSBs including PSS, SSS, and PBCH. To access the network, the UE may further acquire and read SIB1 at 1004, which carries information including the initial DL / UL BWP configuration. SIB1 may be transmitted on the PDSCH and may be scheduled by the downlink control information (DCI) on the PDCCH using the control resource set with index 0 (CORESET#0). Before the UE reads SIB1, the UE's initial DL BWP may have the same frequency range and numerology as that of CORESET#0. After reading SIB1, the UE may follow the initial DL / UL BWP configurations in SIB1 and may use those configurations to perform a random access procedure at 1006 to request the establishment of an RRC connection. The network may configure the frequency domain location and bandwidth of the initial DL BWP in SIB1 such that the initial DL BWP includes the entire CORESET#0 in the frequency domain. The first active DL and UL BWP 1008 may be configured for a special cell (SpCell) or a secondary cell (SCell). In a master cell group (MCG), SpCell refers to the primary cell (PCell) on which the UE performs a connection (re)establishment procedure. In a secondary cell group (SCG), an SpCell refers to a primary SCG cell (PSCell) to which a UE performs random access for RRC (re)configuration.The SCell provides additional radio resources over the SpCell in the cell group. The first active DL and UL BWPs are the active DL and UL BWPs upon RRC (re)configuration for the SpCell or activation of the SCell. In the case of the serving cell, the network may configure the UE with a BWP inactivity timer. Expiration of this timer may indicate, for example, that the UE has not had scheduled transmissions and receptions for some time on the currently active BWP. Thus, the UE may switch its active BWP to a default BWP to save power. A default DL BWP may be configured. If not configured, the UE uses the initial DL BWP as the default DL BWP. In the case of unpaired spectrum, when the UE switches its active DL BWP to a default DL BWP, the active UL BWP is switched accordingly, since the BWP switching in TDD may be common for both DL and UL.

[0085] In other words, the UE may perform downlink synchronization based on the 20-RB SSB and acquire the PBCH at 1002. Assuming that the CORESET#0 configured in the MIB has 24 RBs, the UE may assume that the initial DL BWP is 24 RBs wide and may proceed to acquire SIB1 at 1004, which may also configure 24 RBs for both the initial DL and UL BWPs. The UE may perform a random access procedure at 1006 using the initial DL and UL BWPs. After the random access, the UE may report that it is capable of supporting multiple BWPs. Using dedicated RRC signaling, the network may configure the UE with a first active DL / UL BWP 1008 (270 RBs each), a small DL / UL BWP#2 (52 RBs), and a BWP inactivity timer. The first active DL / UL BWP 1008 may become active and be used to schedule a large amount of data. The UE may then have no traffic demand and may have no scheduled transmissions. As a result, a BWP inactivity timer may expire, at which time the UE switches its active DL BWP to a default DL BWP (e.g., DL BWP#2) at 1010. In some aspects, when a BWP switch (e.g., from initial to first active or upon timer expiration) occurs between BWPs of different SCS values, the switch delay specification may be determined based on the smaller SCS.

[0086] FIG. 11 is a diagram 1100 illustrating an example spectrum management and configuration using SRS for positioning. As shown in FIG. 11, within an operating band 1102, there may be a spectrum 1104 for an operator. Within the spectrum 1104, a BWP 1116 may start at a common RB or may include a set of contiguous RBs associated with a numerology (SCS and CP) on a carrier. The BWP 1116 may extend from the start of a channel cell-specific channel bandwidth 1112 to the RB start1126. The carriers may be associated with a channel bandwidth 1110. The channel bandwidth 1110 may correspond to a cell-specific channel bandwidth 1112. The cell-specific channel bandwidth 1112 may occur after a number of RBs after a reference point 1130 (point A). In some aspects, the reference point 1130 may be a common reference point of the RB grid. In some aspects, the difference between the reference point 1130 and the cell-specific channel bandwidth may be a cell-specific offset with respect to the carrier 1122. The network may configure a UE-specific channel bandwidth 1114 for the UE. The difference between the reference point 1130 and the UE-specific channel bandwidth 1114 may be a UE-specific offset with respect to the carrier 1124. For each serving cell of the UE, the network may configure the UE with at least one UL BWP as an initial DL BWP. The network may configure the UE with one or more DL BWPs, such as up to four DL BWPs. In some aspects, one DL BWP may be active at a time. For each serving cell of the UE, the network may configure the UE with at least one UL BWP as the initial UL BWP. The network may configure the UE with one or more UL BWPs, such as up to four DL BWPs. In some aspects, one UL BWP may be active at a time. In some aspects, the UE may receive PDSCH, PDCCH, or CSI-RS in the active DL BWP. The UE may perform radio resource management (RRM) measurements outside the active DL BWP via measurement gaps. The UE may transmit PUSCH or PUCCH inside the active UL BWP. For an active serving cell, the UE may not transmit SRS outside the active UL BWP.In some aspects, the SRS for positioning (which may be referred to as a special SCS or SRS-POS dedicated) and / or associated BWP 1118 (which may be a defined BWP or a virtual BWP and may be referred to as an "SRS-POS dedicated BWP") may have a location and bandwidth, SCS, CP defined in the same manner as another BWP, such as an initial or non-initial BWP that is not for positioning (e.g., BWP 1116). The SRS for positioning and / or associated BWP may inherit the restrictions of another BWP. For example, the same OffsetToCarrier (e.g., UE-specific offset to carrier 1124) configured in the SRS-SpecificCarrier may be used for the SRS for positioning and / or associated BWP (e.g., SRS-POS dedicated BWP / special SRS) as well as any normal BWP (initial / non-initial). This may be a stronger constraint than the SRS may be in the same band as the initial BWP. In some aspects, the SRS-POS dedicated BWP and the initial BWP may be designated to be in the same carrier (e.g., associated with the channel bandwidth 1110). In some aspects, in TDD, the SRS for positioning and / or associated BWP (e.g., SRS-POS dedicated BWP / special SRS) 1118 may correspond to a UL BWP. In some aspects, the center frequencies of the initial DL BWP and the SRS and / or associated BWP (e.g., SRS-POS dedicated BWP / special SRS) may be different. In some aspects, in TDD, the DL BWP and the paired UL BWP may have different center frequencies.

[0087] In some aspects, based on other signaled UE capabilities, the UE may support at least one connected mode configuration in which the SRS for positioning and / or associated BWP (e.g., SRS-POS dedicated BWP / special SRS) may be the active BWP and switching between the active BWP and the initial BWP may be supported. In some aspects, as long as the UE supports retuning between the initial BWP and any other non-initial BWP in RRC connection, the UE may be able to retune between the initial BWP and the SRS-POS dedicated BWP in RRC inactivity with similar timing uncertainty.

[0088] In some aspects, referring to diagram 1300 of FIG. 13, the UE may transmit (e.g., in capability indication 1306) a UE capability that may further indicate that the UE 1302 supports the same SCS / CP (which may be part of the numerology) without supporting different SCS / CP between the SRS for positioning and / or associated BWP (e.g., SRS-POS dedicated BWP / special SRS) and the initial BWP (e.g., similar to the aforementioned type A / B BWP adaptation with the same numerology and BWP adaptation with a different numerology). This capability may be transmitted to the network entity 1304. In some aspects, the network entity 1304 may be a network node. In some aspects, the network node may be implemented as an aggregate base station, as a distributed base station, as an integrated access and backhaul (IAB) node, as a relay node, as a sidelink node, etc. In some aspects, the network entity 1304 may be implemented in an aggregated or monolithic base station architecture, or alternatively in a non-aggregated base station architecture, and may include one or more of a CU, a DU, a RU, a Near-RT RAN Intelligent Controller (RIC), or a Non-RT RIC. In some aspects, if the UE 1302 declares support for the same SCS / CP among all BWPs and declares support for the SRS for positioning and / or associated BWPs (e.g., SRS-POS dedicated BWP / special SRS) without declaring support for others in the transmitted UE capabilities, the SRS for positioning and / or associated BWPs (e.g., SRS-POS dedicated BWP / special SRS) may have the same SCS / CP as the initial BWP. In some aspects, a separate component may be supported for the SRS for positioning and / or associated BWPs (e.g., SRS-POS dedicated BWP / special SRS), which may then support separate SCS / CP.

[0089] In some aspects, the UE 1302 may transmit (e.g., in the capability indication 1306) a UE capability that may further indicate that the unrestricted SRS for positioning and / or associated BWP (e.g., SRS-POS dedicated BWP / special SRS) may or may not be supported (such as BWP without SSB / Coreset0). For example, similar to the above BWP operation without restriction on the BW of the BWP(s) that can be supported, the BW of the UE-specific RRC configured BWP may not include the BW of CORESET#0 (if CORESET#0 is present) and the SSB for the PCell / PSCell (if configured), and the BW of the UE-specific RRC configured BWP may not include the SSB for the SCell. In some aspects, the SRS for positioning and / or associated BWP (e.g., SRS-POS dedicated BWP / special SRS) may be on the same band as the band of the initial BWP. FIG. 12 is a diagram 1200 illustrating an example spectrum management and configuration using the SRS for positioning. As shown in FIG. 12, within an operating band 1202, there may be a spectrum 1204 for an operator. Within the spectrum 1204, a BWP 1216 may start at a common RB and may include a set of contiguous RBs associated with a numerology (SCS and CP) on a carrier. The BWP 1216 may extend from the start of a channel cell-specific channel bandwidth 1212 to the RB start1226. The carriers may be associated with a channel bandwidth 1210. The channel bandwidth 1210 may correspond to a cell-specific channel bandwidth 1212. The cell-specific channel bandwidth 1212 may occur after a number of RBs after a reference point 1230 (point A). In some aspects, the reference point 1230 may be a common reference point of the RB grid. In some aspects, the difference between the reference point 1230 and the cell-specific channel bandwidth may be a cell-specific offset with respect to the carrier 1222. The network may configure a UE-specific channel bandwidth 1214 for the UE. The difference between the reference point 1230 and the UE-specific channel bandwidth 1214 may be a UE-specific offset with respect to the carrier 1224. For each serving cell of the UE, the network may configure the UE with at least one UL BWP as an initial DL BWP. The network may configure the UE with one or more DL BWPs, such as up to four DL BWPs. In some aspects, one DL BWP may be active at a time. For each serving cell of the UE, the network may configure the UE with at least one UL BWP as an initial UL BWP. The network may configure the UE with one or more UL BWPs, such as up to four DL BWPs. In some aspects, one UL BWP may be active at a time. In some aspects, the UE may receive PDSCH, PDCCH, or CSI-RS in the active DL BWP. The UE may perform radio resource management (RRM) measurements outside the active DL BWP via measurement gaps. The UE may transmit PUSCH or PUCCH inside the active UL BWP. For an active serving cell, the UE may not transmit SRS outside the active UL BWP. The SRS for positioning and / or associated BWPs (e.g., SRS-POS dedicated BWP / special SRS) 1218 may be on the same band as the initial BWP (e.g., 1216).

[0090] In some aspects, the SRS for positioning and / or associated BWP (e.g., SRS-POS dedicated BWP / special SRS) may be such that the UE may support at least one connected mode configuration in which the SRS dedicated BWP is the active BWP and the UE may operate without a switching gap between the active BWP and the initial BWP based on other signaled UE capabilities. In some aspects, the UE may operate with a switching gap. In some aspects, the UE may report the supported SRS BW, CP, SCS per band for the SRS outside the initial BWP.

[0091] In some aspects, the UE 1302 may report, per band pair or group of bands, e.g., for a given band / group of bands that includes the initial BWP, which bands / group of bands may be used for SRS outside the initial BWP (e.g., capabilities in the capability indication 1306). In some aspects, the UE may report the capability of whether the SRS outside the initial BWP may be in the same band as the initial BWP but in a different component carrier (e.g., OffsetToCarrier may be different for such SRS compared to OffsetToCarrier of the initial BWP).

[0092] In some aspects, the UE 1302 may report (eg, in the capability indication 1306) the capability of whether the same center frequency is expected in TDD between the SRS outside the initial DL BWP and the initial UL BWP.

[0093] In some aspects, the UE 1302 may receive a configuration 1308 for transmission of one or more positioning SRS outside of the initial UL BWP while in an idle or inactive state. In some aspects, the configuration 1308 may include a set of constraints on the transmission of the one or more positioning SRS from the network entity 1304. In some aspects, the set of constraints may or may not be based on the capability indication 1306. In some aspects, the configuration 1308 may be received after the capability indication 1306 is transmitted. In some aspects, the UE 1302 may transmit one or more positioning SRS 1310 to the network entity 1304 based on the configuration 1308.

[0094] 14 is a flow diagram 1400 of a method of wireless communication. The method may be performed by a UE (e.g., the UE 104, the device 1602).

[0095] At 1402, the UE may transmit to a network entity a capability for transmission of one or more positioning SRS outside of an initial UL BWP during an idle or inactive state of the UE. For example, the UE 104 or UE 1302 may transmit to a network entity (e.g., 1304) a capability for transmission of one or more positioning SRS outside of an initial UL BWP during an idle or inactive state of the UE (e.g., 1306). In some aspects, 1302 may be implemented by the SRS component 1642 of FIG. 16. In some aspects, the capability may include the UE supporting at least one connected mode configuration, where a BWP associated with the one or more positioning SRS may be an active BWP, and the UE supports switching between a BWP associated with the one or more positioning SRS and the initial UL BWP. In some aspects, the capabilities may include the UE supporting retuning associated with switching between an initial UL BWP and a non-initial BWP, and the UE supporting retuning associated with switching between an initial UL BWP and a BWP associated with one or more positioning SRSs. In some aspects, the capabilities may include the UE supporting the same SCS and CP between the initial UL BWP and a BWP associated with one or more positioning SRSs without supporting a different SCS or CP between the initial UL BWP and a BWP associated with one or more positioning SRSs. In some aspects, the capabilities may include whether the UE supports one or more positioning SRSs having a bandwidth that does not include SSB or CORESET0. In some aspects, the BWP associated with the one or more positioning SRSs may be in the same frequency band as the initial UL BWP. In some aspects, the capabilities may include whether the BWP associated with the one or more positioning SRSs may be in a different carrier than the initial UL BWP. In some aspects, the capabilities may include the UE supporting switching between a BWP associated with one or more positioning SRS and an initial UL BWP with or without a switching gap.In some aspects, the capability to support SRS transmission outside the initial BWP may be reported per band, and the capability may include at least one supported SCS, at least one supported CP, or at least one supported SRS BW. In some aspects, the capability may include whether the same center frequency may be associated with the initial BWP and one or more positioning SRS. In some aspects, the network entity may be a TRP or a base station.

[0096] At 1404, the UE may receive from a network entity a configuration for transmission of one or more positioning SRSs outside of an initial UL BWP while in an idle or inactive state, the configuration including a set of constraints on the transmission of the one or more positioning SRSs. For example, the UE 104 or UE 1302 may receive from a network entity (e.g., 1304) a configuration for transmission of one or more positioning SRSs outside of an initial UL BWP while in an idle or inactive state (e.g., 1308), the configuration including a set of constraints on the transmission of the one or more positioning SRSs. In some aspects, 1404 may be implemented by the SRS component 1642 of FIG. 16. In some aspects, the set of constraints may include a first constraint that a BWP associated with the one or more positioning SRSs or a configuration of the one or more positioning SRSs is associated with at least one of a location and bandwidth parameter, an SCS, or a CP based on the initial UL BWP. In some aspects, the set of constraints may include a second constraint that the offset of the initial UL BWP to the carrier configuration is the same as the offset to the carrier used for the BWP associated with one or more positioning SRSs or a configuration of one or more positioning SRSs. In some aspects, a BWP associated with one or more positioning SRSs may be paired with the initial DL BWP.

[0097] At 1406, the UE may transmit one or more positioning SRSs outside the initial UL BWP to a network entity based on the configuration, where the one or more positioning SRSs are transmitted during an idle or inactive state. For example, the UE 104 or UE 1302 may transmit one or more positioning SRSs (e.g., 1310) outside the initial UL BWP to a network entity based on the configuration, where the one or more positioning SRSs are transmitted during an idle or inactive state. In some aspects, 1406 may be implemented by the SRS component 1642 of FIG. 16.

[0098] 15 is a flow diagram 1500 of a method of wireless communication. The method may be performed by a network entity (e.g., a base station 102 / 180, a network entity 1304, an apparatus 1702).

[0099] At 1502, a network entity may receive from the UE a capability for transmission of one or more positioning SRS outside of an initial UL BWP during an idle or inactive state of the UE. For example, a base station 102 / 180 or a network entity 1304 may receive from a UE (e.g., 1302) a capability (e.g., 1306) for transmission of one or more positioning SRS outside of an initial UL BWP during an idle or inactive state of the UE. In some aspects, 1502 may be implemented by the SRS component 1742 of FIG. 17. In some aspects, the capability may include the UE supporting at least one connected mode configuration, where a BWP associated with the one or more positioning SRS may be an active BWP, and the UE supports switching between a BWP associated with the one or more positioning SRS and the initial UL BWP. In some aspects, the capabilities may include the UE supporting retuning associated with switching between an initial UL BWP and a non-initial BWP, and the UE supporting retuning associated with switching between an initial UL BWP and a BWP associated with one or more positioning SRSs. In some aspects, the capabilities may include the UE supporting the same SCS and CP between the initial UL BWP and a BWP associated with one or more positioning SRSs without supporting a different SCS or CP between the initial UL BWP and a BWP associated with one or more positioning SRSs. In some aspects, the capabilities may include whether the UE supports one or more positioning SRSs having a bandwidth that does not include SSB or CORESET0. In some aspects, the BWP associated with the one or more positioning SRSs may be in the same frequency band as the initial UL BWP. In some aspects, the capabilities may include whether the BWP associated with the one or more positioning SRSs may be in a different carrier than the initial UL BWP. In some aspects, the capabilities may include the UE supporting switching between a BWP associated with one or more positioning SRS and an initial UL BWP with or without a switching gap.In some aspects, the capability to support SRS transmission outside the initial BWP may be reported per band, and the capability may include at least one supported SCS, at least one supported CP, or at least one supported SRS BW. In some aspects, the capability may include whether the same center frequency may be associated with the initial BWP and one or more positioning SRS. In some aspects, the network entity may be a TRP or a base station.

[0100] At 1504, the network entity may transmit a configuration (e.g., 1308) for transmission of one or more positioning SRS outside of the initial UL BWP during an idle or inactive state, which may include a set of constraints on the transmission of the one or more positioning SRS. For example, the base station 102 / 180 or the network entity 1304 may transmit a configuration for transmission of one or more positioning SRS outside of the initial UL BWP during an idle or inactive state, which may include a set of constraints on the transmission of the one or more positioning SRS. In some aspects, 1504 may be implemented by the SRS component 1742 of FIG. 17. In some aspects, the set of constraints may include a first constraint that the BWP associated with the one or more positioning SRS or the configuration of the one or more positioning SRS is associated with at least one of a location and bandwidth parameter, an SCS, or a CP based on the initial UL BWP. In some aspects, the set of constraints may include a second constraint that the offset of the initial UL BWP to the carrier configuration is the same as the offset to the carrier used for the BWP associated with one or more positioning SRSs or a configuration of one or more positioning SRSs. In some aspects, a BWP associated with one or more positioning SRSs may be paired with the initial DL BWP.

[0101] At 1506, the network entity may receive one or more positioning SRSs outside the initial UL BWP from the UE based on the configuration, where the one or more positioning SRSs may be received during an idle or inactive state. For example, the base station 102 / 180 or the network entity 1304 may receive one or more positioning SRSs (e.g., 1310) outside the initial UL BWP from the UE (e.g., 1302) based on the configuration, where the one or more positioning SRSs may be received during an idle or inactive state. In some aspects, 1506 may be implemented by the SRS component 1742 of FIG. 17.

[0102] 16 is a diagram 1600 illustrating an example of a hardware implementation for a device 1602. The device 1602 may be a UE, may be a component of a UE, or may implement UE functionality. In some aspects, the device 1602 may include a cellular baseband processor 1604 (also referred to as a modem) coupled to a cellular RF transceiver 1622. In some aspects, the device 1602 may further include one or more subscriber identity module (SIM) cards 1620, an application processor 1606, a secure digital (SD) card 1608 and a screen 1610, a Bluetooth module 1612, a wireless local area network (WLAN) module 1614, a global navigation system (GNSS) module 1616, a power source 1618, or a memory 1624. The Bluetooth module 1612 may include a transceiver 1612A, and the WLAN module 1614 may include a transceiver 1614A. The GNSS module 1616 may include a GNSS receiver. In some aspects, the power source 1618 may include a battery. The cellular baseband processor 1604 communicates with the UE 104 and / or the BS 102 / 180 through a cellular RF transceiver 1622. The cellular baseband processor 1604 may include a computer readable medium / memory. The computer readable medium / memory may be non-transitory. The cellular baseband processor 1604 is responsible for general processing, including the execution of software stored on the computer readable medium / memory. The software, when executed by the cellular baseband processor 1604, causes the cellular baseband processor 1604 to perform various functions as described above. The computer readable medium / memory may also be used to store data that is manipulated by the cellular baseband processor 1604 when executing the software. The cellular baseband processor 1604 further includes a receiving component 1630, a communications manager 1632, and a transmitting component 1634. The communications manager 1632 includes one or more of the illustrated components.The components in the communications manager 1632 may be stored in a computer-readable medium / memory and / or configured as hardware in the cellular baseband processor 1604. The cellular baseband processor 1604 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1602 may be a modem chip and may include only the baseband processor 1604, while in another configuration, the device 1602 may be an entire UE (e.g., see 350 in FIG. 3) and may include additional modules of the device 1602.

[0103] The communications manager 1632 may include an SRS component 1642 configured to transmit capabilities to a network entity for transmission of one or more positioning SRS outside the initial UL BWP during an idle or inactive state of the UE, e.g., as described with respect to 1402 of FIG. 14. The SRS component 1642 may be further configured to receive a configuration for transmission of one or more positioning SRS outside the initial UL BWP during an idle or inactive state from the network entity, e.g., as described with respect to 1404 of FIG. 14. The SRS component 1642 may be further configured to transmit one or more positioning SRS outside the initial UL BWP to the network entity based on the configuration, e.g., as described with respect to 1406 of FIG. 14.

[0104] The apparatus may include additional components that implement each of the blocks of the algorithm in the flow diagram of Figure 14. Thus, each block in the flow diagram of Figure 14 may be implemented by a component, and the apparatus may include one or more of those components. Those components may be one or more hardware components specifically configured to perform the described process / algorithm, implemented by a processor configured to perform the described process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0105] As shown, the apparatus 1602 may include various components configured for various functions. In one configuration, the apparatus 1602, particularly the cellular baseband processor 1604, may include means for transmitting to a network entity a capability for transmission of one or more positioning SRSs outside the initial UL BWP during an idle or inactive state of the UE. The cellular baseband processor 1604 may further include means for receiving from the network entity a configuration for transmission of one or more positioning SRSs outside the initial UL BWP during an idle or inactive state, the configuration including a set of constraints on the transmission of the one or more positioning SRSs. The cellular baseband processor 1604 may further include means for transmitting one or more positioning SRSs outside the initial UL BWP to a network entity based on the configuration, the one or more positioning SRSs being transmitted during an idle or inactive state. The means may be one or more of the components of the apparatus 1602 configured to perform the enumerated functions by the means. As described above, the apparatus 1602 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, the means may be the TX processor 368, the RX processor 356, and the controller / processor 359, configured to perform the recited functions by the means.

[0106] FIG. 16 is a diagram 1700 illustrating an example of a hardware implementation for the device 1702. The device 1702 may be a network entity such as a base station, a component of a base station, or may implement base station functionality. In some aspects, the device 1702 may include a baseband unit 1704. The baseband unit 1704 may communicate with the UE 104 via a wide area network (WAN) RF transceiver 1722. The WAN RF transceiver 1722 may support various air interfaces and may support wireless communication using one or more RATs such as GSM, CDMA, WCDMA, LTE, High Rate Packet Data (HRPD), IEEE 802.11 WiFi (also referred to as Wi-Fi), BT, Worldwide Interoperability for Microwave Access (WiMAX), 5G NR, etc. The device 1702 may further include a memory 1724 and a processor 1726 coupled to the memory 1724. The baseband unit 1704 may include a computer-readable medium / memory. The baseband unit 1704 is responsible for overall processing, including the execution of software stored on a computer readable medium / memory. The software, when executed by the baseband unit 1704, causes the baseband unit 1704 to perform the various functions described above. The computer readable medium / memory may also be used to store data that is manipulated by the baseband unit 1704 when executing the software. The baseband unit 1704 further includes a receiving component 1730, a communications manager 1732, and a transmitting component 1734. The communications manager 1732 includes one or more of the illustrated components. The components in the communications manager 1732 may be stored in a computer readable medium / memory and / or may be configured as hardware in the baseband unit 1704. The baseband unit 1704 may be a component of the base station 310 and may include a memory 376 and / or at least one of a TX processor 316, a RX processor 370, and a controller / processor 375.

[0107] The communications manager 1732 may include an SRS component 1742 that may receive a capability from the UE for transmission of one or more positioning SRS outside the initial UL BWP during an idle or inactive state of the UE, e.g., as described with respect to 1602 of FIG. 15. The SRS component 1742 may also transmit a configuration for transmission of one or more positioning SRS outside the initial UL BWP during an idle or inactive state, the configuration including a set of constraints on transmission of the one or more positioning SRS, e.g., as described with respect to 1604 of FIG. 15. The SRS component 1742 may also receive one or more positioning SRS outside the initial UL BWP from the UE based on the configuration, the one or more positioning SRS being received during an idle or inactive state, e.g., as described with respect to 1606 of FIG.

[0108] The apparatus may include additional components that implement each of the blocks of the algorithm in the flow diagram of Figure 15. Thus, each block in the flow diagram of Figure 15 may be implemented by a component, and the apparatus may include one or more of those components. Those components may be one or more hardware components specifically configured to perform the described process / algorithm, implemented by a processor configured to perform the described process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0109] As shown, the apparatus 1702 may include various components configured for various functions. In one configuration, the apparatus 1702, particularly the baseband unit 1704, may include means for receiving from the UE a capability for transmission of one or more positioning SRSs outside the initial UL BWP during an idle or inactive state of the UE. The baseband unit 1704 may further include means for transmitting a configuration for transmission of one or more positioning SRSs outside the initial UL BWP during an idle or inactive state, the configuration including a set of constraints on the transmission of the one or more positioning SRSs. The baseband unit 1704 may further include means for receiving from the UE one or more positioning SRSs outside the initial UL BWP based on the configuration, the one or more positioning SRSs being received during the idle or inactive state. The means may be one or more of the components of the apparatus 1702 configured to perform the recited functions by the means. As described above, the apparatus 1702 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Thus, in one configuration, the means may be the TX processor 316, the RX processor 370, and the controller / processor 375, configured to perform the recited functions by the means.

[0110] It should be understood that the particular order or hierarchy of the blocks in the disclosed process / flow diagrams is an example of an example approach. Based on design preferences, it should be understood that the particular order or hierarchy of the blocks in the process / flow diagrams can be rearranged. Further, some blocks can be combined or omitted. The accompanying method claims present elements of the various blocks in an example order, and are not meant to be limited to the particular order or hierarchy presented.

[0111] 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 readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects set forth herein, but are to be accorded the widest scope consistent with the language of the claims, and references to elements in the singular shall mean "one or more" and not "one and only", unless otherwise expressly stated. Terms such as "if", "when", and "while" should be construed to mean "under the condition that", rather than implying an immediate temporal relationship or reaction. That is, these phrases, such as "when", do not imply immediate action in response to or during the occurrence of an action, but simply mean that an action will occur if a condition is met, but do not require a specific or immediate temporal constraint for the action to occur. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" should not necessarily be construed as preferred or advantageous over other aspects. Unless expressly stated otherwise, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple As, multiple Bs, or multiple Cs.Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, and any such combination may include one or more elements of A, B, or C. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are known or that later become known to those of skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be made public, regardless of whether such disclosure is expressly recited in the claims. Words such as "module," "mechanism," "element," "device," and the like may not be substitutes for the word "means." Therefore, no element of a claim should be construed as a means-plus-function unless the element is expressly recited using the phrase "means for."

[0112] The following aspects are exemplary only and can be combined with other aspects or teachings described herein without limitation.

[0113] Aspect 1 is for a method of wireless communication in a UE, the method including: a memory; transmitting, to a network entity, a capability for transmission of one or more positioning SRS outside an initial UL BWP during an idle or inactive state of the UE; receiving, from the network entity, a configuration for transmission of one or more positioning SRS outside an initial UL BWP during an idle or inactive state, the configuration including a set of constraints on transmission of the one or more positioning SRS; and transmitting, based on the configuration, to the network entity, one or more positioning SRS outside the initial UL BWP, the one or more positioning SRS being transmitted during the idle or inactive state.

[0114] Example 2 is the method of example 1, wherein the set of constraints includes a first constraint that a BWP associated with one or more positioning SRSs or a configuration of one or more positioning SRSs is associated with at least one of location and bandwidth parameters, an SCS, or a CP based on an initial UL BWP.

[0115] Example 3 is the method of any of Examples 1 or 2, wherein the set of constraints includes a second constraint that the offset of the initial UL BWP to a carrier configuration is the same as the offset to a carrier used for the BWP associated with one or more positioning SRSs or a configuration of one or more positioning SRSs.

[0116] Example 4 is the method of example 2, in which a BWP associated with one or more positioning SRSs is paired with an initial DL BWP.

[0117] Example 5 is the method of any of Examples 1 to 4, wherein the capabilities include the UE supporting at least one connected mode configuration in which a BWP associated with the one or more positioning SRSs is an active BWP and the UE supports switching between a BWP associated with the one or more positioning SRSs and an initial UL BWP.

[0118] Example 6 is the method of any of Examples 1 to 5, wherein the capabilities further include the UE supporting switching between an initial UL BWP and a BWP associated with one or more positioning SRSs.

[0119] Example 7 is the method of example 1, wherein the capability further includes the UE supporting the same SCS and CP between the initial UL BWP and a BWP associated with one or more positioning SRSs without supporting a different SCS or CP between the initial UL BWP and a BWP associated with one or more positioning SRSs.

[0120] Example 8 is the method of any of Examples 1 to 7, wherein the capabilities further include whether the UE supports one or more positioning SRSs having a bandwidth that does not include an SSB or CORESET0.

[0121] Example 9 is the method of any of Examples 1 to 8, wherein the BWP associated with the one or more positioning SRS is in the same frequency band as the initial UL BWP.

[0122] Example 10 is the method of any of Examples 1 to 9, wherein the capabilities further include whether a BWP associated with the one or more positioning SRS is in a different carrier than the initial UL BWP.

[0123] Example 11 is the method of any of Examples 1 to 10, wherein the capabilities further include the UE supporting switching between a BWP associated with one or more positioning SRSs and an initial UL BWP with or without a switching gap.

[0124] Example 12 is a method according to any of Examples 1 to 11, in which a capability to support SRS transmission outside the initial BWP is reported for each band, the capability including at least one supported SCS, at least one supported CP, or at least one supported SRS BW.

[0125] Example 13 is the method of any of examples 1 to 12, wherein the capabilities further include whether a same center frequency is associated with the initial BWP and the one or more positioning SRSs.

[0126] Example 14 is the method of any one of Examples 1 to 13, wherein the network entity is a TRP or a base station.

[0127] Aspect 15 is a method for wireless communication in a network entity, comprising: receiving from a UE a capability for transmission of one or more positioning SRS outside an initial UL BWP during an idle or inactive state of the UE; transmitting a configuration for transmission of one or more positioning SRS outside an initial UL BWP during an idle or inactive state, the configuration including a set of constraints on transmission of the one or more positioning SRS; and receiving from the UE one or more positioning SRS outside the initial UL BWP based on the configuration, the one or more positioning SRS being received during the idle or inactive state.

[0128] Example 16 is the method of example 15, wherein the set of constraints includes a first constraint that a BWP associated with one or more positioning SRSs is associated with at least one of a location and bandwidth parameter, an SCS, or a CP based on an initial UL BWP.

[0129] Example 17 is the method of example 15 or 16, wherein the set of constraints includes a second constraint that an offset with respect to a carrier associated with the initial UL BWP is used for a BWP associated with the one or more positioning SRSs.

[0130] Example 18 is the method of any of Examples 15 to 17, wherein the BWP associated with the one or more positioning SRS corresponds to an initial UL BWP.

[0131] Example 19 is the method of any of examples 15 to 18, wherein the capabilities include the UE supporting at least one connected mode configuration in which a BWP associated with the one or more positioning SRSs is an active BWP and the UE supports switching between a BWP associated with the one or more positioning SRSs and an initial UL BWP.

[0132] Example 20 is the method of any of examples 15 to 19, wherein the capability further includes the UE supporting switching between an initial UL BWP and a BWP associated with one or more positioning SRSs.

[0133] Example 21 is the method of any of examples 15 to 20, wherein the capability further includes the UE supporting the same SCS and CP between the initial UL BWP and a BWP associated with one or more positioning SRSs without supporting a different SCS or CP between the initial UL BWP and a BWP associated with one or more positioning SRSs.

[0134] Example 22 is the method of any of examples 15 to 21, wherein the capabilities further include whether the UE supports one or more positioning SRSs without SSB or CORESET0.

[0135] Example 23 is the method of any of Examples 15 to 22, wherein a BWP associated with the one or more positioning SRSs is in the same band as the initial UL BWP.

[0136] Example 24 is the method of any one of examples 15 to 23, wherein a BWP associated with the one or more positioning SRSs is in a different carrier than the initial UL BWP.

[0137] Example 25 is the method of any of examples 15 to 24, wherein the capabilities further include the UE supporting switching between a BWP associated with one or more positioning SRSs and an initial UL BWP with or without a switching gap.

[0138] Example 26 is a method as described in any of examples 15 to 25, wherein the capability is associated with a band for an SRS outside the initial BWP, the band including at least one supported SCS, at least one supported CP, or at least one supported SRS BW.

[0139] Example 27 is the method of any of examples 15 to 26, wherein the capabilities further include whether a same center frequency is associated with the initial BWP and the one or more positioning SRSs.

[0140] Example 28 is the method of any one of Examples 15 to 27, wherein the network entity is a TRP or a base station.

[0141] Aspect 29 is an apparatus for wireless communication in a UE including a memory and at least one processor coupled to the memory and configured to perform a method according to any one of aspects 1 to 14 based at least in part on information stored in the memory. The apparatus may further include at least one of a transceiver or an antenna coupled to the at least one processor.

[0142]

[0036] Aspect 30 is an apparatus for wireless communication, comprising means for performing a method according to any one of aspects 1 to 14.

[0143] Aspect 31 is a non-transitory computer-readable medium comprising instructions that, when executed by an apparatus, cause the apparatus to perform a method according to any one of aspects 1 to 14.

[0144] Aspect 32 is an apparatus for wireless communication in a network entity, including a memory and at least one processor coupled to the memory and configured to perform a method according to any one of aspects 15 to 28 based at least in part on information stored in the memory. The apparatus may further include at least one of a transceiver or an antenna coupled to the at least one processor.

[0145]

[0036] Aspect 33 is an apparatus for wireless communication, comprising means for performing a method according to any one of aspects 15 to 28.

[0146] Aspect 34 is a non-transitory computer-readable medium comprising instructions that, when executed by an apparatus, cause the apparatus to perform a method according to any one of aspects 15 to 28.

Claims

1. 1. An apparatus for wireless communication in a user equipment (UE), comprising: Memory and A transceiver; at least one processor communicatively coupled to the memory and the transceiver, the at least one processor comprising: transmitting to a network entity a capability for transmission of one or more positioning sounding reference signals (SRS) outside an initial uplink (UL) bandwidth portion (BWP) during an idle or inactive state of the UE; receiving, from the network entity, a configuration for the transmission of the one or more positioning SRSs outside the initial UL BWP during the idle state or the inactive state, the configuration including a set of constraints on the transmission of the one or more positioning SRSs, the set of constraints including a first constraint that a BWP associated with the one or more positioning SRSs or the configuration of the one or more positioning SRSs is associated with at least one of a location and bandwidth parameter, a subcarrier spacing (SCS), or a cyclic prefix (CP) based on the initial UL BWP; transmitting, to the network entity based on the configuration, the one or more positioning SRS outside the initial UL BWP, wherein the one or more positioning SRS are configured to be transmitted during the idle state or the inactive state; An apparatus configured to:

2. 2. The apparatus of claim 1, wherein the set of constraints includes a second constraint that an offset to a carrier configuration of the initial UL BWP is the same as the offset to a carrier used for the one or more positioning SRSs or the BWP associated with the configuration of the one or more positioning SRSs.

3. The apparatus of claim 1 , wherein the BWP associated with the one or more positioning SRSs is paired with an initial downlink (DL) BWP.

4. 2. The apparatus of claim 1, wherein the capabilities include the UE supporting at least one connected mode configuration in which a BWP associated with the one or more positioning SRSs is an active BWP and the UE supports switching between the BWP associated with the one or more positioning SRSs and the initial UL BWP.

5. The apparatus of claim 1 , wherein the capabilities further include supporting the UE to switch between the initial UL BWP and the BWP associated with the one or more positioning SRSs.

6. 2. The apparatus of claim 1, wherein the capabilities further include the UE supporting the same subcarrier spacing (SCS) and cyclic prefix (CP) between the initial UL BWP and the BWPs associated with the one or more positioning SRSs without supporting different SCSs or CPs between the initial UL BWP and the BWPs associated with the one or more positioning SRSs.

7. 2. The apparatus of claim 1, wherein the capabilities further include whether the UE supports the one or more positioning SRSs having a bandwidth that does not include a synchronization signal block (SSB) or a control resource set 0 (CORESET0).

8. a BWP associated with the one or more positioning SRSs is within the same frequency band as the initial UL BWP; The apparatus of claim 1 , wherein the capabilities further include whether the BWP associated with the one or more positioning SRS is in a different carrier than the initial UL BWP.

9. 2. The apparatus of claim 1, wherein the capabilities further include the UE supporting switching between a BWP associated with the one or more positioning SRSs and the initial UL BWP with or without a switching gap.

10. 2. The apparatus of claim 1, wherein the capability to support SRS transmission outside an initial BWP is reported per band, and the capability includes at least one supported subcarrier spacing (SCS), at least one supported cyclic prefix (CP), or at least one supported SRS BW.

11. The apparatus of claim 1 , wherein the capabilities further include whether a same center frequency is associated with an initial BWP and the one or more positioning SRSs.

12. The apparatus of claim 1 , wherein the network entity is a transmission / reception point (TRP) or a base station.

13. 1. An apparatus for wireless communication in a network entity, comprising: Memory and A transceiver; at least one processor communicatively coupled to the memory and the transceiver, the at least one processor comprising: receiving capability for transmission of one or more positioning sounding reference signals (SRS) outside an initial uplink (UL) bandwidth portion (BWP) during an idle or inactive state of a user equipment (UE); transmitting a configuration for the transmission of the one or more positioning SRSs outside the initial UL BWP during the idle state or the inactive state, the configuration including a set of constraints on the transmission of the one or more positioning SRSs, the set of constraints including a first constraint that a BWP associated with the one or more positioning SRSs or the configuration of the one or more positioning SRSs is associated with at least one of a location and bandwidth parameter, a subcarrier spacing (SCS), or a cyclic prefix (CP) based on the initial UL BWP; receiving the one or more positioning SRSs outside the initial UL BWP based on the configuration, wherein the one or more positioning SRSs are configured to be received during the idle state or the inactive state; An apparatus configured to:

14. 1. A method of wireless communication in a user equipment (UE), comprising: transmitting to a network entity a capability for transmission of one or more positioning sounding reference signals (SRS) outside an initial uplink (UL) bandwidth portion (BWP) during an idle or inactive state of the UE; receiving, from the network entity, a configuration for the transmission of the one or more positioning SRSs outside the initial UL BWP during the idle state or the inactive state, the configuration including a set of constraints on the transmission of the one or more positioning SRSs, the set of constraints including a first constraint that a BWP associated with the one or more positioning SRSs or the configuration of the one or more positioning SRSs is associated with at least one of a location and bandwidth parameter, a subcarrier spacing (SCS), or a cyclic prefix (CP) based on the initial UL BWP; transmitting the one or more positioning SRSs outside the initial UL BWP to the network entity based on the configuration, wherein the one or more positioning SRSs are configured to be transmitted during the idle state or the inactive state; A method comprising:

15. 1. A method of wireless communication in a network entity, comprising: receiving capability for transmission of one or more positioning sounding reference signals (SRS) outside an initial uplink (UL) bandwidth portion (BWP) during an idle or inactive state of a user equipment (UE); transmitting a configuration for the transmission of the one or more positioning SRSs outside the initial UL BWP during the idle state or the inactive state, the configuration including a set of constraints on the transmission of the one or more positioning SRSs, the set of constraints including a first constraint that a BWP associated with the one or more positioning SRSs or the configuration of the one or more positioning SRSs is associated with at least one of a location and bandwidth parameter, a subcarrier spacing (SCS), or a cyclic prefix (CP) based on the initial UL BWP; receiving the one or more positioning SRSs outside the initial UL BWP based on the configuration, wherein the one or more positioning SRSs are configured to be received during the idle state or the inactive state; A method comprising:

Images