Method and apparatus for synchronization of RACH and SDT in SSB-less DL BWP

Abstract

A method, apparatus, and computer-readable medium are provided for synchronization for RACH and SDT. An exemplary method may include receiving a configuration for a first DL and UL BWP pair including information indicating at least one of a CORESET, an SS set, and a set of UL resource occasions for an RA procedure or an SDT procedure. The exemplary method may further include initiating at least one of an RA procedure or an SDT procedure in the first DL and UL BWP pair. The exemplary method may further include performing time or frequency synchronization during the RA procedure or the SDT procedure using an SSB of a serving cell configured in the second DL BWP or a DL reference signal of a serving cell configured in the second DL BWP.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of PCT Application No. PCT / CN / 2021 / 135467, entitled "SYNCHRONIZATION FOR RACH AND SDT IN SSB-LESS DL BWP," filed on December 3, 2021, the entire contents of which are expressly incorporated by reference into this specification.

[0002]

[0002] The present disclosure relates generally to communication systems, and more specifically to wireless communication systems having a downlink (DL) bandwidth part (BWP) without a synchronization signal block (SSB) for random access (RA) or small data transmission (SDT) procedures. [Background technology]

[0003]

[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]

[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]

[0005] 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 does it identify key or critical elements of all aspects, nor does it 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]

[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 receive a configuration for a first downlink (DL) and uplink (UL) bandwidth portion (BWP) pair, the configuration including information indicating at least one of a control resource set (CORESET), a search space (SS) set, and a set of UL resource occasions for a random access (RA) procedure or a small data transmission (SDT) procedure. The memory and the at least one processor coupled to the memory may be further configured to initiate at least one of an RA procedure or an SDT procedure in the first DL and UL BWP pair. The memory and at least one processor coupled to the memory may be further configured to perform time synchronization or frequency synchronization during an RA procedure or an SDT procedure using a synchronization signal block (SSB) of a serving cell configured in the second DL BWP or a DL reference signal of a serving cell configured in the second DL BWP (e.g., in a first DL BWP of the first DL and UL BWP pair).

[0007] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus in a base station (e.g., a network node) are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and at least one processor coupled to the memory may be configured to send a configuration to a UE in a radio resource control (RRC) idle, inactive, or connected state for a random access procedure or an SDT procedure in a first downlink and uplink BWP pair, the configuration including information indicating at least one of a CORESET for the random access procedure or the SDT procedure, an SS set (such as a common SS (CSS) or a UE specific SS (USS) set), a set of uplink resource occasions, and an SSB or DL ​​reference signal in a second DL BWP, wherein the first DL BWP of the first DL and UL BWP pair does not include an SSB, and a quasi-colocation (QCL) source, spatial relationship configuration, and synchronization for the UE during the random access procedure or the SDT procedure are based on the SSB or DL ​​reference signal transmitted by the serving cell in the second DL BWP. The memory and at least one processor coupled to the memory may be further configured to receive from the UE an early indication of one or more of a device type, a first request for a first on-demand transmission of an SSB or DL ​​reference signal, or assistance information for adaptive scheduling in at least one of a random access message or an SDT message from the UE in a first UL BWP of the first DL and UL BWP pair.

[0008]

[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 only 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]

[0009] FIG. 1 illustrates an example of a wireless communication system and access network. [Figure 2A]

[0010] FIG. 2 illustrates an example of a first frame in accordance with various aspects of the present disclosure. [Figure 2B]

[0011] FIG. 1 illustrates an example of a DL channel in a subframe in accordance with various aspects of the present disclosure. [Figure 2C]

[0012] FIG. 2 illustrates an example of a second frame, according to various aspects of the present disclosure. [Figure 2D]

[0013] FIG. 1 illustrates an example of a UL channel in a subframe in accordance with various aspects of the present disclosure. [Diagram 3]

[0014] FIG. 1 illustrates an example of a base station and user equipment (UE) in an access network. [Figure 4]

[0015] A diagram showing an example resource having multiple BWPs configured within a frequency span of a carrier bandwidth. [Diagram 5]

[0016] A diagram showing an initial downlink BWP. [Figure 6]

[0017] FIG. 1 illustrates a four-step random access procedure (four-step RACH). [Figure 7]

[0018] FIG. 1 illustrates a two-step random access procedure (two-step RACH). [Figure 8]

[0019] FIG. 2 illustrates an exemplary timeline associated with a 4-step RACH. [Figure 9A]

[0020] FIG. 2 illustrates an example timeline associated with a retune timer. [Figure 9B] FIG. 2 illustrates an example timeline associated with a retune timer. [Figure 10]

[0021] FIG. 2 illustrates an exemplary timeline associated with retuning. [Figure 11]

[0022] FIG. 2 illustrates an exemplary timeline associated with retuning. [Figure 12]

[0023] FIG. 2 illustrates an exemplary timeline associated with retuning. [Figure 13]

[0024] FIG. 2 illustrates an example timeline associated with a two-step RACH. [Figure 14]

[0025] FIG. 2 illustrates an exemplary timeline associated with a 4-step RACH. [Figure 15]

[0026] 1 is a flow chart of a method of wireless communication. [Figure 16]

[0027] 1 is a flow chart of a method of wireless communication. [Figure 17]

[0028] FIG. 2 illustrates an example of a hardware implementation for an exemplary device. [Figure 18]

[0029] FIG. 2 illustrates an example of a hardware implementation for an exemplary device. [Figure 19]

[0030] FIG. 1 illustrates an example of a wireless communication system and access network. [Figure 20]

[0031] FIG. 2 illustrates an example of a hardware implementation for a network entity. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010]

[0032] The Detailed Description of the Invention described below in conjunction with the accompanying drawings illustrates various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The Detailed Description of the Invention includes specific details intended to provide a thorough understanding of the various concepts. However, 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]

[0033] Several aspects of a telecommunications system are presented with reference to various apparatus and methods that are described in the Detailed Description below 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 on the particular application and design constraints imposed on the overall system.

[0012]

[0034] 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, executables, threads of execution, procedures, functions, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0013]

[0035] Thus, in one or more exemplary aspects, implementations, and / or use cases, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded on a computer-readable medium as one or more instructions or code. 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, such computer-readable media may comprise 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 used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0014]

[0036] Although aspects, implementations, and / or use cases are described in this application by way of example for some embodiments, additional or different aspects, implementations, and / or use cases may occur in many different configurations and scenarios. The aspects, implementations, and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging configurations. For example, the aspects, implementations, and / or use cases may occur via 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.). Although some embodiments may or may not be specifically targeted to a use case or application, a wide variety of combination applicability of the described embodiments may occur. The aspects, implementations, and / or use cases 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 of the techniques herein. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for the implementation and practice of the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, summers / analog summers, etc.). The techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed configurations, aggregated or separated components, end-user devices, etc., of various sizes, shapes, and configurations.

[0015]

[0037] The deployment of a communication system such as a 5G NR system can be configured in multiple ways with various components or parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of the network, a radio access network (RAN) node, a core network node, a network element, or a network equipment such as a base station (BS), or one or more units (or one or more components) performing a base station function can be implemented in an aggregated or separated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit receive point (TRP), or cell) can be implemented as an aggregated base station (also known as a standalone BS or monolithic BS) or a separated base station.

[0016]

[0038] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A separated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU or alternatively geographically or virtually distributed across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0017]

[0039] Base station operation or network design may take into account the aggregated nature of base station functions. For example, a separated base station may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as the network configuration supported by the O-RAN alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functions across two or more units in different physical locations, as well as distributing functions virtually for at least one unit, which may allow flexibility in network design. Various units of a disaggregated base station, or a disaggregated RAN architecture, may be configured for wired or wireless communication with at least one other unit.

[0018]

[0040] 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.

[0019]

[0041] A base station 102 configured for 4G LTE (collectively referred to as Evolved Universal 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.

[0020]

[0042] The base stations 102 may wirelessly communicate with the UEs 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). The 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 technologies, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be through one or more carriers. The base station 102 / UE 104 may use spectrum with a bandwidth of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) per carrier, allocated in carrier aggregation with up to a total of Yx MHz (x component carriers) 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 for 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).

[0021]

[0043] 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.

[0022]

[0044] 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.

[0023]

[0045] The small cell 102' may operate in an unlicensed spectrum and / or an 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 increase coverage to and / or capacity of the access network.

[0024]

[0046] The electromagnetic spectrum is often divided into various classes, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified with 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. Similar nomenclature issues 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).

[0025]

[0047] 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 may 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 (71 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0026]

[0048] With the above aspects in mind, unless otherwise indicated, as used herein, terms such as "sub-6 GHz" may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, as used herein, unless otherwise indicated, terms such as "millimeter wave" 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.

[0027]

[0049] 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 millimeter wave base station 180 may utilize beamforming 182 for 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.

[0028]

[0050] 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.

[0029]

[0051] 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.

[0030]

[0052] 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.

[0031]

[0053] 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.

[0032]

[0054] Referring again to FIG. 1 , in some aspects, the UE 104 may include a synchronization component 198. In some aspects, the synchronization component 198 may be configured to receive a configuration for a first DL and UL BWP pair including information indicating at least one of a CORESET, an SS set, and a set of UL resource occasions for a RA or SDT procedure. In some aspects, the synchronization component 198 may be further configured to initiate at least one of an RA or SDT procedure in the first DL and UL BWP pair. In some aspects, the synchronization component 198 may be further configured to perform time or frequency synchronization using an SSB of a serving cell configured in the second DL BWP or a DL reference signal of a serving cell configured in the second DL BWP (e.g., in the first DL BWP of the first DL and UL BWP pair) during a RA or SDT procedure.

[0033]

[0055] In some aspects, the base station 180 may include a synchronization component 199. In some aspects, the synchronization component 199 may be configured to transmit a configuration for a random access procedure or an SDT procedure in a first downlink and uplink BWP pair, the configuration including information indicating at least one of a CORESET, an SS set, a set of uplink resource occasions for the random access procedure or SDT procedure, and an SSB or DL ​​reference signal in a second DL BWP, to a UE in an RRC idle, inactive, or connected state, where the first DL BWP of the first DL and UL BWP pair does not include an SSB, and the QCL source, spatial relationship configuration, and synchronization for the UE during the random access procedure or SDT procedure is based on the SSB or DL ​​reference signal transmitted by the serving cell in the second DL BWP. In some aspects, the synchronization component 199 may be further configured to receive an early indication from the UE of one or more of a device type, a first request for a first on-demand transmission of an SSB or DL ​​reference signal, or other assistance information for adaptive scheduling in at least one of a random access message or an SDT message from the UE in a first UL BWP of the first DL and UL BWP pair.

[0034]

[0056] 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, GSM, and other wireless technologies.

[0035]

[0057] As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, be, or be included in (e.g., may be a component of) a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote / radio unit (RU) (which may be referred to as a remote radio unit, RRU), and / or another processing entity configured to perform any of the techniques described herein. For example, a network node may be a UE. As another example, a network node may be a base station or a network entity. As another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first network node, the second network node, and the third network node may be different for these examples. Similarly, references to a UE, a base station, an apparatus, a device, a computing system, etc. may include disclosure of a UE, a base station, an apparatus, a device, a computing system, etc. that are network nodes. For example, a disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with this disclosure, when a specific example is expanded in accordance with this disclosure (e.g., also discloses that a UE is configured to receive information from a base station and that a first network node is configured to receive information from a second network node), the broader example of the narrower example may be interpreted in a converse, but broad, open-ended manner.In the above examples also disclosing that the UE is configured to receive information from a base station and the first network node is configured to receive information from a second network node, the first network node may refer to a first UE, a first base station, a first apparatus, a first device, a first computing system, a first set of one or more components, a first processing entity, etc. configured to receive information, and the second network node may refer to a second UE, a second base station, a second apparatus, a second device, a second computing system, a second set of one or more components, a second processing entity, etc.

[0036]

[0058] As described herein, communication of information (e.g., any information, signal, etc.) may be described in various manners using different terms. A disclosure of one communication term includes a disclosure of other communication terms. For example, a first network node may be described as configured to transmit information to a second network node. In this example, consistent with the present disclosure, a disclosure that a first network node is configured to transmit information to a second network node includes a disclosure that the first network node is configured to provide, send, output, communicate, or transmit information to the second network node. Similarly, in this example, consistent with the present disclosure, a disclosure that a first network node is configured to transmit information to a second network node includes a disclosure that the second network node is configured to receive, obtain, or decode information provided, sent, output, communicated, or transmitted by the first network node.

[0037]

[0059] 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, subframe 4 is configured with slot format 28 (mostly DL), where D is DL, U is UL, and F is flexible for DL / UL use, and subframe 3 is 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, UL, and flexible symbols. The UE is configured with the slot format through a received slot format indicator (SFI) (dynamically through DL control information (DCI) or semi-statically / statically through Radio Resource Control (RRC) signaling). Note that the following description also applies to 5G NR frame configurations that are TDD.

[0038]

[0060] 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 a number logic, which defines the subcarrier spacing (SCS), which effectively defines the symbol length / period equal to 1 / SCS.

[0039] [Table 1]

[0040]

[0061] For normal CP (14 symbols / slot), the different number logics μ0-4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, number logic 2 allows 4 slots per subframe. Thus, for normal CP and number logic μ, 14 symbols / slot and 2 μ There are slots / subframes. The subcarrier spacing is 2 μ *15kHz, where μ is a number logic 0-4. Therefore, number logic μ=0 has a subcarrier spacing of 15kHz and number logic μ=4 has a subcarrier spacing of 240kHz. 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 number logic μ=2 with 4 slots per subframe. The slot duration is 0.25ms, the subcarrier spacing is 60kHz, and the symbol duration is about 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 number logic and CP (normal or extended).

[0041]

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

[0042]

[0063] 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).

[0043]

[0064] 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.

[0044]

[0065] 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 configuration, 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.

[0045]

[0066] 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.

[0046]

[0067] 3 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, internet protocol (IP) packets 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.

[0047]

[0068] 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 can 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 can be used to determine the coding and modulation schemes as well as for spatial processing. The channel estimates can be derived from a reference signal and / or channel condition feedback transmitted by the UE 350. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx can modulate a radio frequency (RF) carrier with the respective spatial stream for transmission.

[0048]

[0069] At the UE 350, each receiver 354Rx receives a signal through its respective antenna 352. Each receiver 354Rx recovers the information modulated onto the 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.

[0049]

[0070] 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 performs demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0050]

[0071] 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.

[0051]

[0072] 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 354Tx. Each transmitter 354Tx may modulate an RF carrier with a respective spatial stream for transmission.

[0052]

[0073] 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 318Rx receives a signal through its corresponding antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides the information to the RX processor 370.

[0053]

[0074] 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 performs demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0054]

[0075] 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 synchronization component 198 of FIG.

[0055]

[0076] 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 synchronization component 199 of FIG.

[0056]

[0077] In addition to normal devices, wireless communication may also be supported on devices with reduced capabilities (also reduced capability devices). Examples of normal devices include premium smartphones, V2X devices, URLLC devices, eMBB devices, etc., among others. Reduced capability devices may include wearables (e.g., smart watches, augmented reality glasses, virtual reality glasses, health and medical monitoring devices, etc.), industrial wireless sensor networks (IWSNs) (e.g., pressure sensors, humidity sensors, motion sensors, thermal sensors, accelerometers, actuators, etc.), surveillance cameras, low-end smartphones, etc. For example, an NR communication system may support both normal devices and reduced capability devices. Reduced capability devices may be referred to as NR light devices, low-tier devices, lower tier devices, etc. Reduced capability UEs may communicate based on various types of wireless communication. For example, smart wearables may transmit or receive communications based on low power wide area (LPWA) / mMTC, mitigated IoT devices may transmit or receive communications based on URLLC, sensors / cameras may transmit or receive communications based on eMBB, etc.

[0057]

[0078] In some examples, a reduced capability UE may have an uplink transmit power that is at least 10 dB lower than a normal UE. As another example, a reduced capability UE may have a reduced transmit or receive bandwidth than other UEs. For example, a reduced capability UE may have an operating bandwidth of 5 MHz to 20 MHz for both transmit and receive, as opposed to other UEs that may have a bandwidth of up to 100 MHz. As an example, a reduced capability UE may have a maximum bandwidth of 20 MHz during and after initial access in FR1. In FR2, a reduced capability UE may have a maximum bandwidth of 100 MHz during and after initial access. As a further example, a reduced capability UE may have a reduced number of receive antennas compared to other UEs. For frequency bands in which a UE is equipped with at least two antennas, the minimum number of receive branches for a reduced capability UE may be one, and may also include support for two receive branches. For frequency bands in which a normal UE is equipped with four receive antenna ports, a minimum number of one receive branch may be supported, with additional support for, for example, two receive branches for a reduced capability UE. In some aspects, the base station may know the number of receive branches at the UE. For example, a reduced capability UE may have only a single receive antenna and may experience a lower equivalent receive signal to noise ratio (SNR) compared to a normal UE that may have multiple antennas. A reduced capability UE with one receive branch may support one downlink MIMO layer. A reduced capability UE with two receive branches may support two downlink MIMO layers. A maximum modulation order of 256QAM may be supported in the downlink for FR1 reduced capability UEs. In some aspects, a reduced capability UE may support half-duplex frequency division duplex (HD-FDD) Type A duplex operation. A reduced capability UE may support full-duplex FDD (FD-FDD) operation or full-duplex time division duplex (FD-TDD) operation. A reduced capability UE may also have reduced computational complexity than other UEs.

[0058]

[0079] As an example, a wearable may have a high data rate on the downlink, e.g., a reference rate of 5-50 Mbps on the downlink, compared to a rate of 2-5 Mbps on the uplink. The latency and reliability may be based on eMBB. The battery life may be intended to last multiple days, e.g., 1-2 weeks in one example. An industrial sensor may have a high uplink reference rate, e.g., about 2 Mbps, a latency of less than 100 ms with a smaller latency (e.g., 5-10 ms) for safety-related sensors, 99.9% reliability, and a battery life intended to last one or multiple years. A video surveillance device may have a high traffic on the uplink, e.g., a reference rate of 2-4 Mbps for some traffic, and a reference rate of 7.5-25 Mbps for higher priority traffic. The video surveillance device may have a latency of less than 500 ms with 99%-99.9% reliability.

[0059]

[0080] It may be useful for communications to be scalable and deployable in a more efficient and cost-effective manner. For example, it may be possible to relax or reduce peak throughput, latency, and / or reliability requirements for reduced capability devices. In some examples, reduced power consumption, complexity, production costs, and / or reduced system overhead may be prioritized. As an example, an industrial wireless sensor may have an acceptable latency of up to about 100 ms. In some safety-related applications, the latency of an industrial wireless sensor may be acceptable up to 10 ms or up to 5 ms. Data rates may be lower and may include more uplink traffic than downlink traffic. As another example, a video surveillance device may have an acceptable latency of up to about 500 ms.

[0060]

[0081] A carrier bandwidth may span, for example, a contiguous set of PRBs from a common resource block for a given numerology on a given carrier. A base station may configure one or more bandwidth portions (BWPs) having a bandwidth span smaller than the carrier bandwidth. One or more of the BWPs may be configured for downlink communication and may be referred to as a downlink (DL) BWP. FIG. 4 shows a resource diagram 400 illustrating multiple BWPs (e.g., BWP1, BWP2, and BWP3) configured within a frequency span of a carrier bandwidth. One DL BWP may be active at a time, and a UE may not be expected to receive PDSCH, PDCCH, CSI-RS, or TRS outside of an active BWP without a measurement gap or BWP switching gap. Each DL BWP may include at least one control resource set (CORESET). In FIG. 4, the BWP may be a DL BWP and is shown as having a CORESET within the BWP. In another example, the BWP may be a UL BWP and may not include a CORESET configuration. One or more of the BWPs may be configured for uplink communication and may be referred to as an uplink (UL) BWP. One UL BWP may be active for a UE at a time, and the UE may not transmit PUSCH or PUCCH outside of an active BWP. Use of the BWP may reduce the bandwidth monitored by the UE and / or used for transmission, which may help the UE conserve battery power.

[0061]

[0082] A CORESET corresponds to a set of physical resources in time and frequency that a UE uses to monitor the PDCCH / DCI. Each CORESET includes one or more resource blocks in the frequency domain and one or more symbols in the time domain. As an example, a CORESET may include multiple RBs in the frequency domain and one, two, or three consecutive symbols in the time domain. A resource element (RE) is a unit that indicates one subcarrier in frequency on a single symbol in time. A control channel element (CCE) includes a resource element group (REG), for example, six REGs, in which case a REG may correspond to one RB (e.g., 12 REs) in one OFDM symbol. REGs in a CORESET may be numbered in ascending order in a time-prioritized manner, starting from 0 for the first OFDM symbol and the lowest numbered resource block in the control resource set. A UE may be configured with multiple CORESETs, where each CORESET is associated with a CCE-to-REG mapping. A search space may include a set of CCEs, for example, at different aggregation levels. For example, a search space may indicate, for example, the number of candidates to be decoded for which a UE performs decoding. A CORESET may include multiple search space sets.

[0062]

[0083] In some aspects, UEs with different levels of capabilities, such as reduced capability UEs and non-reduced capability (or normal) UEs, may share an initial DL BWP (e.g., BWP1) and CORESET#0 (e.g., 402) for initial access. The UEs may, for example, monitor resources of CORESET#0 to receive system information that enables the UEs to perform initial access. A cell-defining SSB (CD-SSB), for example, 408, may be transmitted within a bandwidth supported by the reduced capability UEs. As an example, BWP1 may be an initial DL BWP, for example, configured for both reduced capability UEs and normal UEs. The UEs may be configured with a different BWP as an active DL BWP, for example, after performing initial access. For example, in FIG. 4, BWP2 may be configured for lower capability UEs, and active DL BWP3 may be configured for normal UEs. FIG. 4 shows that BWP1 may include SSB 408.

[0063]

[0084] A cell providing access to a reduced capability UE may configure a separate initial BWP for the reduced capability UE. FIG. 5 illustrates an example diagram 500 illustrating an initial downlink BWP 554 that may be configured within a serving cell's carrier bandwidth 552 for a reduced capability UE to receive cell-defining (CD) SSBs (CD-SSBs), SI, paging information, etc. In some aspects, the initial downlink BWP 554 may be configured with resources for CD-SSBs 555, CORESET#0 556, and another CORESET and one or more SSs 558 for the UE to receive SIB1, other system information (OSI), or paging. A reduced capability UE in idle or inactive mode may camp on the initial downlink BWP 554, e.g., CORESET#0 556 of the serving cell, to receive CD-SSBs, SI, and paging. An idle or inactive mode reduced capability UE may switch to a separate BWP to perform a random access procedure, a small data transmission (SDT) procedure, or to initiate a transition to a connected mode. The UE may receive a configuration for a BWP pair, e.g., a first BWP pair including a first downlink BWP 562 and a first uplink BWP 564 for a random access or SDT procedure. In some aspects, the first downlink BWP 562 and the first uplink BWP 564 may be an initial DL BWP and an initial UL BWP. In some aspects, the term "first BWP pair" may refer to an "initial BWP pair" or another type of BWP pair. The first downlink BWP 562 may include resources 560 configured for CORESET and USS / CSS for an initial transmission (e.g., initial access) by the reduced capability UE. The first uplink BWP 564 may include a PUCCH resource, for example, a physical random access channel (RACH) occasion (RACH occasion, RO) 566.The RAN may assume that an idle or inactive mode reduced capability UE that performs a random access procedure in a separate, e.g., first BWP (e.g., sending a random access message in the first uplink BWP 564 and / or monitoring a downlink response in the first downlink BWP 562) does not monitor paging in CORESET0 556.

[0064]

[0085] In some aspects, a separate, e.g., first BWP (e.g., 562) for reduced capability UEs may include CD-SSB and a specific CORESET, such as CORESET0. In other aspects, a separate, e.g., first BWP (e.g., 562) for reduced capability UEs may not include CD-SSB (e.g., configured without CD-SSB, e.g., not including CD-SSB, which may be referred to as SSB-less BWP), without a specific CORESET, such as resources for CORESET#0, or without a CORESET for receiving SIB1, OSI, or paging. FIG. 5 illustrates a separate, e.g., first DL BWP 562 for performing a random access procedure that does not include CD-SSB or CORESET#0.

[0065]

[0086] In some aspects in FR1, a separate, e.g., first DL BWP (e.g., 562, etc.) that does not include CD-SSB and CORESET#0 (e.g., does not include the entire CORESET#0) may be configured to perform a random access procedure and not configured for paging in idle or inactive mode. The separate, e.g., first DL BWP (e.g., 562) may not include SSB, CORESET#0, or SIB resources. For example, the network may assume that a reduced capability UE performing a random access procedure in a separate, e.g., first downlink BWP (e.g., 562) will not monitor paging in a BWP (e.g., 554) that includes CORESET#0 556. If the BWP is configured for paging, the reduced capability UE may assume that the BWP includes a non-cell defining SSB (NCD-SSB), but may not assume that the BWP includes CORESET#0 / SIB. In the case of an RRC configured active DL BWP configured for a UE in connected mode, and if the active DL BWP does not include CD-SSB or the entire CORESET#0, the reduced capability UE may assume that the active DL BWP includes, for example, NCD-SSB, rather than CORESET#0 / SIB. In some aspects, the reduced capability UE may indicate a capability that the UE does not require NCD-SSB. For example, the reduced capability UE may optionally support related operations for wireless communication based on a reference signal, such as CSI-RS, and may report the capability to the network.

[0066]

[0087] If the network configures a separate RRC configured DL BWP for the reduced capability UE to include the entire CORESET#0, the reduced capability UE may assume that the separate BWP includes the CD-SSB. The network may choose to configure the SSB or MIB configured CORESET#0 or SIB1 to be within the respective DL BWP. When a separate SIB configured initial DL BWP for the reduced capability UE includes the entire CORESET#0, the reduced capability UE may use the bandwidth and location of CORESET#0 for downlink reception during initial access. The NCD-SSB periodicity may be different from the periodicity of the CD-SSB. In some aspects, the periodicity of the NCD-SSB may not be smaller than the periodicity of the CD-SSB.

[0067]

[0088] In some aspects in FR2, a separate, e.g., first DL BWP (e.g., 562) that does not include CD-SSB or the entire CORESET#0 may be configured to perform a random access procedure and not configured for paging in idle or inactive mode. The separate, e.g., first DL BWP (e.g., 562) may not include SSB, CORESET#0, or SIB resources. For example, the network may assume that a reduced capability UE performing a random access procedure in a separate downlink BWP (e.g., 562) does not monitor paging in a BWP (e.g., 554) that includes CORESET#0 556. If a separate, e.g., first DL BWP is configured for paging, the reduced capability UE may assume that the separate initial BWP includes NCD-SSB for the serving cell but does not include CORESET#0 or SIB resources.

[0068]

[0089] In the case of an RRC configured active DL BWP configured for a UE in connected mode, and if the active DL BWP does not include CD-SSB or the entire CORESET#0, the reduced capability UE may assume that the active DL BWP includes, for example, an NCD-SSB for the serving cell, rather than CORESET#0 / SIB. In some aspects, a reduced capability UE may indicate a capability that the UE does not require an NCD-SSB. For example, a reduced capability UE may optionally support related operations for wireless communications based on a reference signal, such as CSI-RS, and may report the capability to the network.

[0069]

[0090] For multiplexing pattern 1 of SSB and CORESET#0, if a separate initial DL BWP is configured via RRC to include the entire CORESET#0, the reduced capability UE may assume that the separate initial DL BWP includes CD-SSB. The network may choose to configure SSB or MIB configured CORESET#0 or SIB1 to be within the respective DL BWP. If a separate SIB configured initial DL BWP for the reduced capability UE includes the entire CORESET#0, the reduced capability UE may use the bandwidth and location of CORESET#0 for downlink reception during initial access. The NCD-SSB periodicity may be different from the periodicity of the CD-SSB. In some aspects, the periodicity of the NCD-SSB may not be smaller than the periodicity of the CD-SSB.

[0070]

[0091] A UE may use a random access procedure to communicate with a base station. For example, a UE may use the random access procedure to request an RRC connection, re-establish an RRC connection, resume an RRC connection, etc. The random access procedure may include two different types of random access procedures, for example, a Contention-Based Random Access (CBRA) may be implemented when the UE is not synchronized with the base station, and a Contention-Free Random Access (CFRA) may be implemented when the UE was previously synchronized with the base station 604. Both types of procedures include the transmission of a random access preamble from the UE to the base station. In CBRA, the UE may randomly select a random access preamble sequence, for example, from a set of preamble sequences. Because the UE randomly selects a preamble sequence, the base station may simultaneously receive other preambles based on the same preamble sequence from different UEs. Thus, CBRA provides for the base station to resolve such contention between multiple UEs. In CFRA, the network can assign a preamble sequence to the UE, rather than the UE randomly selecting a preamble sequence. This can help to avoid potential collisions with preambles from other UEs using the same sequence. Hence, CFRA is referred to as "contention-free" random access.

[0071]

[0092] FIG. 6 illustrates an example aspect of a four-step random access procedure 600 between a UE 602 and a base station 604. The UE 602 may initiate a random access message exchange by transmitting a first random access message 603 (e.g., Msg1) including a preamble to the base station 604. Before transmitting the first random access message 603, the UE may obtain random access parameters including, for example, preamble format parameters, time and frequency resources, parameters for determining a root sequence and / or a cyclic shift for the random access preamble, etc., in system information 601 from the base station 604. The preamble may be transmitted with an identifier such as a Random Access RNTI (RA-RNTI). The UE 602 may randomly select a random access preamble sequence, for example, from a set of preamble sequences. When the UE 602 randomly selects a preamble sequence, the base station 604 may simultaneously receive another preamble from a different UE. In some examples, a preamble sequence may be assigned to the UE 602.

[0072]

[0093] The base station responds to the first random access message 603 by transmitting a second random access message 605 (e.g., Msg2) including a random access response (RAR) using the PDSCH. The RAR may include, for example, an identifier of the random access preamble transmitted by the UE, a time advance (TA), an uplink grant for the UE to transmit data, a cell radio network temporary identifier (C-RNTI) or other identifier, and / or a backoff indicator. Upon receiving the RAR 605, the UE 602 may transmit a third random access message 607 (e.g., Msg3) to the base station 604 using the PUSCH, which may include, for example, an RRC connection request, an RRC connection re-establishment request, or an RRC connection resumption request, depending on a trigger to initiate the random access procedure. The base station 604 may then complete the random access procedure by sending a fourth random access message 609 (e.g., Msg4) to the UE 602, for example, using the PDCCH for scheduling and the PDSCH for messaging. The fourth random access message 609 may include a random access response message including timing advancement information, contention resolution information, and / or RRC connection setup information. The UE 602 may monitor the PDCCH, for example, using the C-RNTI. If the PDCCH is successfully decoded, the UE 602 may also decode the PDSCH. The UE 602 may send HARQ feedback for any data carried in the fourth random access message. If the two UEs sent the same preamble in 603, both UEs may receive a RAR inducing both UEs to send a third random access message 607. The base station 604 may resolve such a collision by being able to decode the third random access message from only one of the UEs and responding to that UE with a fourth random access message.The other UE that does not receive the fourth random access message 609 may determine that the random access was not successful and may retry the random access. Thus, the fourth message may be referred to as a contention resolution message. The fourth random access message 609 may complete the random access procedure. Thus, the UE 602 may then transmit uplink communication with the base station 604 based on the RAR 609 and / or receive downlink communication with the base station 604.

[0073]

[0094] To reduce latency or control signaling overhead, a single round trip cycle between the UE and the base station may be achieved in a two-step RACH process, as shown in example 700 of FIG. 7. Aspects of Msg1 and Msg3 may be combined into a single message, which may be referred to as MsgA, for example. Before transmitting the first random access message 703, the UE 702 may obtain random access parameters, including, for example, preamble format parameters, time and frequency resources, parameters for determining a root sequence and / or cyclic shift for the random access preamble, etc., from the base station 704 in, for example, SSB or RACH configuration (e.g., system information or RRC signaling). The UE 702 transmits MsgA, which may include the random access preamble 703 and may include a PUSCH transmission 705, such as, for example, data for small data transmission (SDT). The MsgA preamble may be separate from the four-step preamble, but may be transmitted in the same random access occasions (ROs) as the preamble of the four-step RACH procedure, or may be transmitted in a separate RO. The PUSCH transmission may be transmitted in a PUSCH occasion that may span multiple symbols and PRBs. After the UE 702 transmits MsgA (e.g., 703 and / or 705), the UE 702 may wait for a response from the base station 704. The aspects of Msg2 and Msg4 in the four-step RACH of FIG. 6 may be combined into a single message that may be referred to as MsgB. The two-step RACH may be triggered for similar reasons as the four-step RACH procedure. If the UE 702 does not receive a response, the UE 702 may retransmit MsgA or fall back to the four-step RACH procedure starting with Msg1. If the base station 704 detects MsgA but fails to successfully decode the MsgA PUSCH, the base station 704 may respond with an allocation of resources for uplink retransmission of the PUSCH. The UE 702 may fall back to a four-step RACH with transmission of Msg3 based on the response from the base station and may retransmit the PUSCH from MsgA.If the base station 704 successfully decodes MsgA and the corresponding PUSCH, the base station 704 may reply with an indication of successful reception, e.g., as a random access response completing the two-step RACH procedure. FIG. 7 shows that MsgB may include MsgB PDCCH 707 and MsgB PDSCH 709 indicating successful reception, e.g., RAR. MsgB may include a random access response and a contention resolution message. The contention resolution message may be transmitted after the base station successfully decodes the PUSCH transmission. In some aspects, MsgB PDSCH 709 may include data, e.g., as part of the SDT. The UE may then have a valid timing advance (TA) and PUCCH resource timing. The UE 702 may transmit a PUCCH 710 with ACK / NACK feedback for MsgB received from the base station 704.

[0074]

[0095] In some wireless communication systems, the UE's initial transmit timing error is limited by a timing error limit T e For example, such an initial transmission may occur after the UE has been inactive for some time, e.g., in a sleep state when configured in discontinuous reception (DRX) mode. e can be specified according to the following table:

[0075] [Table 2]

[0076]

[0096] As shown in the example in Table 2, the timing error limit T e is the basic timing unit T c In some aspects, the timing error limit T emay be applicable to the first transmission in a DRX cycle for PUCCH, PUSCH, and SRS, or if the transmission is a PRACH transmission or a msgA transmission. As an example, the UE will generally apply the timing error bound T e The reference point for the UE's initial transmission timing control is assumed to be (N TA +N TA offset )×T c The downlink timing may be defined as the time when the first detected path (in time) of the corresponding downlink frame is received from the reference cell. TA may be referred to as the timing advance between the downlink and the uplink, and T A In the case of PRACH, N TA can be 0. The value N TA offset n may be referred to as the timing advance offset and may be provided to the UE via an information element (IE), n-TimingAdvanceOffset, for the serving cell. TA +N TA offset )×T c (Unit T c ) may be the difference between the UE transmit timing and the downlink timing immediately after the last timing advance was applied.

[0077]

[0097] To meet the timing error bound, the UE may measure the serving cell's SSB at least once in the last N ms, such as the last 160 ms. In some aspects, N may have a default value of 160. In some aspects, N may be any positive value. When the UE performs a RA or SDT procedure in an initial / non-initial BWP that does not include an SSB (e.g., a separate, e.g., first DL and UL BWP pair (DL BWP 562 and UL BWP 564 in FIG. 5) etc.), the UE may be within the UL timing error bound for the first transmission of msg1, msgA, or CG-PUSCH, but subsequent UL (re)transmissions may extend beyond 160 ms after the last measurement of the SSB due to collisions, coverage limitations, and channel impairments. As an example, FIG. 8 is a diagram 800 illustrating a timeline associated with a four-step RACH. As shown in FIG. 8, a UE, such as the UE described in connection with any of FIGS. 4-7, may receive an SSB 802 (e.g., in an initial DL BWP 554). After receiving the SSB 802, the UE may change to a separate, e.g., first BWP pair (e.g., 562 and 564) to perform a random access procedure, where the separate, e.g., first DL BWP does not include an SSB from the serving cell. The UE may transmit a first transmission for msg1 804 in the UL BWP 564. A random access response (RAR) window 806 may be scheduled for the UE to monitor an RAR from the serving cell on the separate, e.g., first DL BWP 562 after transmitting the first transmission for msg1 804 on the UL BWP 564. There may be a random backoff 808 between the RAR window 806 and another first transmission (e.g., retransmission) of msg1 810. The time between SSB and the retransmission of msg1 810 is T A After retransmitting msg1 810 on the UL BWP 564, the UE may monitor for msg2 812 from the base station on the DL BWP 562. After receiving msg2 812 from the base station, the UE may accordingly transmit msg3 814 in response (e.g., on the UL BWP 564). The time between the SSB and msg3 814 may be T BIn the four-step RACH procedure, T A and / or T B may be greater than 160 ms. In some aspects, if the UE's initial / non-initial DL BWP does not include SSB or other DL RS (such as TRS) for time / frequency tracking and the RA / SDT procedure takes more than N ms to finish, the UE may retune and measure SSB or other DL RS outside the SSB-less initial / non-initial DL BWP configured with SS for RA and SDT. For example, the UE may switch from DL BWP 562 or UL BWP 564 to measure SSB or DL ​​RS on BWP 554. The UE may then switch back to DL BWP 562 or UL BWP 564 to continue the RA or SDT procedure. Aspects provided herein may provide synchronization procedures and signaling support for situations where the UE is configured with SSB-less initial / non-initial DL BWP for RA or SDT. An "SSB-less BWP" may refer to a DL BWP that does not include an SSB, e.g., does not include the entire SSB transmitted by the serving cell.

[0078]

[0098] In some aspects, when a UE in RRC idle, inactive, or connected state (which may be RedCap or non-RedCap) is configured with an SSB-less DL BWP for RA or SDT by system information (SI) or RRC, the SSB-less DL BWP may be configured with a CORESET and / or SS set for RA or SDT (e.g., UL SDT based on RACH or configured grant such as RA-SDT or CG-SDT) (for 2-step or 4-step RACH). In some aspects, a UE may assume that its UL BWP (e.g., with the same BWP identifier (ID) as the SSB-less DL BWP) includes 1) a valid PRACH occasion (e.g., RO) for a 4-step RACH and a valid PUCCH resource set for HARQ feedback of msg4, 2) a valid msgA PRACH / PUSCH occasion (msgA RO / PUSCH occasion) for a 2-step RACH and a valid PUCCH resource set for HARQ feedback of msgB, or 3) a valid SDT (e.g., RA-SDT or CG-SDT) occasion and a valid PUCCH resource set for HARQ feedback of SDT. In some aspects, spatial relationships (e.g., spatial relationship information) for the RO, msgA RO or PUSCH occasion, SDT occasion, and PUCCH resource set may be configured for a serving cell by a network, such as a base station. In some aspects, the spatial relationship may be associated with a cell-defined (CD-SSB) or non-cell defining (NCD)-SSB of the serving cell, which may be transmitted outside the SSB-less DL BWP configured for RA and SDT. In some aspects, the spatial relationship may be associated with other DL RS (e.g., CSI-RS) of the serving cell, which may be transmitted within or outside the SSB-less DL BWP configured for RA.In some aspects, the CORESET and / or SS set for an RA or SDT procedure may be quasi-co-located (QCLed) with an SSB or DL ​​RS used for spatial relationship setup. In some aspects, the CORESET and / or SS set for an RA or SDT procedure may be QCLed based on QCL type D. In some aspects, an SSB or DL ​​RS configured as a QCL source of the CORESET / SS for RA or SDT may also be used by the UE to perform time and / or frequency synchronization during the RA or SDT procedure.

[0079]

[0099] In some aspects, the QCL relationship may indicate a relationship between signals with respect to one or more of Doppler shift, Doppler spread, average delay, delay spread, a set of spatial Rx parameters, etc. In some aspects, the QCL relationship may be based on different QCL type parameters. There may be different types of QCL relationships, where QCL type A may include Doppler shift, Doppler spread, average delay, and delay spread. QCL type B may include Doppler shift and Doppler spread. QCL type C may include Doppler shift and average delay, and QCL type D may include spatial Rx parameters.

[0080]

[0100] In some aspects, when a UE (e.g., reduced capability UE or normal UE) in RRC idle, inactive, or connected state may be configured with an SSB-less DL BWP for RA or SDT procedures (such as small UL data transfer based on RACH or configured grant), the UE may be configured with an SSB-less DL BWP as part of a DL and UL pair by SI or RRC signaling, and the SSB-less DL BWP may be configured with CORESET and / or SS for RA or SDT (e.g., RA-SDT or CG-SDT) (for 2-step or 4-step RACH). SDT may refer to an exchange of DL / UL data from the control plane or user plane below a size threshold that may be included in a paging message, RAR message, contention resolution message, or random access message of a 4-step RACH or 2-step RACH as described in connection with FIG. 7, or may be transmitted in configured grant resources for the UE without transitioning to an RRC connected state. In some aspects, after the UE initiates an RA or SDT procedure in the DL or UL BWP, the UE may start a retuning timer for DL ​​BWP switching to measure SSB or other DL RS outside the SSB-less DL BWP. The UE may monitor the SSB-less DL BWP (e.g., 562) for a response to an RA or SDT message transmitted in the UL (e.g., 564). In some aspects, the retuning timer and the timing advance (TA) timer for RA or SDT may be set separately. In some aspects, the retuning timer setting may be based on at least the UL timing accuracy requirement and the UE capabilities. In some aspects, if set by the SI or RRC, the retuning timer may also depend on the periodicity / pattern of the CD-SSB / NCD-SSB / TRS / PRS / CSI-RS of the serving cell. In some aspects, the retuning timer tracks the time gap with respect to the last measurement occasion for SSB (or other DL RS) transmitted by the serving cell outside the SSB-less DL BWP for RA / SDT.In some aspects, the network may additionally configure a back-off parameter for msg1 or msgA or SDT retransmission. In some aspects, the back-off parameter may be equal to or greater than the UE's retuning delay and measurement gap. As an example, before the retransmission of msg1 or msgA or SDT, the UE's timeline may be sufficient to measure the SSB outside the BWP to resynchronize with the serving cell. In some aspects, when the retuning timer for RA / SDT (including RA-SDT and CG-SDT) expires, or when the TA timer for RA / SDT (including RA-SDT and CG-SDT) expires, or when the TA verification for (PUSCH / PUCCH / SRS transmission in) CG-SDT fails, the UE may terminate its DL reception (e.g., on a separate starting DL BWP 562) or cancel its UL transmission in the BWP (e.g., 564) configured for RA and SDT, where the DL termination or UL cancellation may be performed fully or partially by the UE. The UE may also switch or retune between BWPs to measure SSB or other DL RSs, for example, for time and / or frequency synchronization, or other Layer-1 or Layer-3 measurements required by power control, RA / SDT resource reselection, mobility, radio resource management (RRM), radio link monitoring (RLM), beam management (such as BFR and BFD). In some other cases, the UE may need to switch or retune BWPs to receive system information updates or notifications for a public warning system (PWS). In some aspects, the UE timelines for BWP switching / retuning, DL termination (full or partial), UL cancellation (full or partial), and effective length of measurement gaps may depend at least on the UE type or capability, SI modification period, interruption time for paging reception, and reference SCS of the active DL / UL BWP.In some aspects, after measurements or SI / PWS reception on the DL BWP 554 outside the SSB-less DL BWP 562 are made, the UE may retune back to the DL / UL BWP 562 or 564 and resume the RA or SDT procedure. The UE may also reset the retuning timer.

[0081]

[0101] 9A and 9B are diagrams 900 and 950 illustrating example timelines associated with retuning timers. As shown in FIG. 9A, a UE, such as the UE described in connection with any of FIGS. 4-7, may receive an SSB 902 (e.g., in an initial DL BWP 554). After receiving the SSB 902, the UE may use a separate, e.g., first DL and UL BWP pair for random access. The UE may transmit an initial transmission of msg1 (in the case of a four-step RACH) or msgA (in the case of a two-step RACH) at 904. After transmitting the initial transmission for msg1 or msgA 904, the UE may monitor the DL BWP 562 during a RAR window 906. After the UE starts an RA or SDT in the UL BWP and after the initial transmission for msg1 or msgA 904, the UE may start its retuning timer T r 9. The time between the SSB 902 and the start of the retuning timer may be T0. There may be a random backoff 908 between the RAR window 906 and the retransmission of msg1 or msgA 910. After sending a retransmission of msg1 or msgA 910 on the UL BWP 564, the UE may monitor for msg2 or msgB 912 from the base station on the DL BWP 562. The UE may wait until the retuning timer expires (e.g., T0+T r >N ms) or if the TA timer expires, the UE may cancel the next UL transmission 914 for RA or SDT on the UL BWP 564 or DL ​​reception on the DL BWP 562.

[0082]

[0102] As shown in FIG. 9B, a UE, such as the UE described in connection with any of FIGS. 4-7, may switch to the DL BWP 554 to receive the SSB 952, for example, based on the expiration of a timer. The UE may receive the SSB to perform synchronization measurements. After receiving the SSB 952, the UE may transmit an initial transmission for msg1 or msgA 954 on the UL BWP 564. The UE may monitor for a response from the base station on the DL BWP 562 during the RAR window 956 after receiving the initial transmission for msg1 or msgA 954. After the UE starts an RA or SDT in the UL BWP 564 and after the initial transmission for msg1 or msgA 954, the UE may start its retuning timer T r The time between the SSB 952 and the start of the retuning timer may be T0. There may be a random backoff 958 between the RAR window 956 and the retransmission of msg1 or msgA 960. After sending a retransmission of msg1 or msgA 960 in the UL BWP 564, the UE may monitor the RAR window 962 for msg2 or msgB from the base station in the DL BWP 562. The time between the SSB 952 and the start of the retuning timer may be T0. r >Nms) or if the TA timer expires, the UE may terminate PDCCH / RAR monitoring (e.g., in the RAR window 962) in the SSB-less DL BWP 562 configured for RA or SDT to switch to the DL BWP 554 to receive SSBs and perform synchronization with the serving cell. In some aspects, the parameter Nms may be a number of milliseconds that the UE may continue monitoring without measuring the SSB.

[0083]

[0103] In some aspects, when a UE in RRC idle, inactive, or connected state is configured with an SSB-less DL BWP (e.g., 562) for RA or SDT by SI / RRC, the SSB-less DL BWP may be configured with CORESET / SS for RA (2-step or 4-step RACH) or SDT (RA-SDT or CG-SDT). In some aspects, after the UE starts RA or SDT in the corresponding UL BWP (e.g., 564), the UE may start a retuning timer for DL ​​BWP switching / retuning to measure SSB or other DL RS in DL BWP 554 outside the SSB-less DL BWP 562. In addition, the UE may optionally report a retuning schedule (depending on the earlier expiry time of the retuning timer and the TA timer) in msg3 or msgA PUSCH / CG PUSCH / UCI during the RA or SDT if both the RF retuning timer and the TA timer are still running before the UL transmission (i.e., msg3 or msgA PUSCH / CG PUSCH / UCI) and the TA verification is successful for the CG-PUSCH transmission. In some aspects, the UE may start BWP retuning based on the retuning schedule reported to the base station, for example, in msg3 or msgA PUSCH / CG PUSCH / UCI, and may switch to BWP 554 to perform synchronization after transmitting the reported value. In some aspects, the UE's reporting of the retuning timer may be enabled / disabled by the network in SI / RRC. For example, before performing a RA or SDT procedure, the UE may receive an indication from the base station to enable timer reporting. When the UE initiates an RA or SDT procedure in a BWP pair (e.g., 562 and 564), the UE may report the value of the timer to the base station. Alternatively, if the UE receives an indication that timer value reporting is disabled or does not receive an indication that timer value reporting is enabled, the UE may refrain from reporting the timer value to the base station. In some aspects, the UE's reporting for the retuning timer may be triggered by a condition or a trigger event.For example, the UE may be configured with one or more conditions or triggering events. If a condition or triggering event occurs, the UE may send a timer value report. For example, the UE may expect to retune before the msgB RAR window expires, before the msg4 contention resolution timer expires, before the TA timer expires, etc. In some aspects, upon receiving the UE's report of a retuning schedule, the base station may schedule the UE's subsequent DL channels (e.g., DL feedback for msg4, msgB, SDT) or UL channels (e.g., PUCCH for HARQ feedback) with a scheduling gap sufficient to accommodate the UE's timeline extension due to retuning and measurements. In some aspects, after measurements outside the SSB-less DL BWP are made, the UE may retune back to the original DL / UL BWP, restart the RA / SDT procedure, or reset the retune timer.

[0084]

[0104] FIG. 10 is a diagram 1000 illustrating an example timeline associated with retuning. As shown in FIG. 10, a UE, such as the UE described in connection with any of FIGS. 4-7, may receive an SSB 1002. After receiving the SSB 1002 on the DL BWP 554, the UE may transmit an initial transmission for msg1 1004 in the UL BWP 564. After the UE initiates an RA or SDT in the UL BWP 564 and after the initial transmission for msg1 1004, the UE may start a retuning timer T for DL ​​BWP switching / retuning to measure SSBs or other DL RSs outside the SSB-less DL BWP. rIt can be started. For example, after transmitting msg1 or msgA in UL BWP564, the UE may monitor DL BWP562 for a response from the base station. The timer may be related to the time from when the UE monitors DL BWP562 for the response to switch to DL BWP554 in order to receive the SSB. The time between the reception of the previous SSB 1002 and the start of the retuning timer may be T0. After transmitting the initial transmission for msg1 1004, the UE may monitor msg2 1006 on DL BWP562. Based on the occurrence of one or more set conditions or triggering events, the UE may be triggered to report a retuning schedule in msg3 1008. For example, based on the defined parameter τ, when N - τ < T0 + T r <N, the UE may be triggered to report a retuning schedule in msg3 1008. In some aspects, N may be the number of milliseconds when the UE no longer trusts the timing as reliable if it has not measured the SSB in the last N milliseconds. The retuning schedule may refer to the time for the UE to return from the UL and DL BWP pair (DL BWP562 and UL BWP564) to DL BWP554 to perform synchronization by measuring the SSB or another DL reference signal. In some aspects, after transmitting msg3 1008, the UE may start retuning (e.g., switch to DL BWP554) based on the retuning schedule reported in msg3 1008. In some aspects, after finishing the measurements for resynchronization, the UE may return to the BWP (e.g., 562 and / or 564) to continue the RA procedure or the SDT procedure. In some aspects, the time to return to BWP554 for synchronization measurements may lead to a delay in the delivery (e.g., reception) of msg4 1010. In some aspects, PUCCH1012 may be transmitted after msg4 1010 is delivered.

[0085]

[0105] FIG. 11 is a diagram 1100 illustrating an example timeline associated with BWP retuning for synchronization measurements (e.g., retuning from a separate initial BWP pair that does not include an SSB or DL ​​reference signal to an initial DL BWP that includes an SSB or DL ​​reference signal). As shown in FIG. 11, a UE, such as the UE described in connection with any of FIGS. 4-7, may receive an SSB 1102 in an initial DL BWP, such as DL BWP 554. After receiving the SSB 1102, the UE may transmit an initial transmission for msg1 1104 to initiate an RA or SDT procedure. After the UE initiates an RA or SDT in a UL BWP (e.g., 564) with the initial transmission for msg1 1104, the UE may monitor the associated DL BWP (e.g., DL BWP 562) for a reply from the base station. The UE may start a retuning timer T for DL ​​BWP switching / retuning to measure an SSB or other DL RS in a DL BWP (e.g., 554) outside the SSB-less DL BWP (e.g., 562). r The time between the SSB 1102 and the start of the retuning timer may be T0. After sending the initial transmission for msg1 1104, the UE may monitor the DL BWP 562 to transmit msg2 1106. Based on the occurrence of one or more conditions or triggering events (which may be set by the base station, for example), the UE may be triggered to report a retuning schedule in msg3. For example, based on a parameter τ (which may be defined or otherwise known to the UE), N-τ <T0+T rWhen N, the UE may be triggered to report a retuning schedule in msg3 1108. In some aspects, after receiving msg4 1110 in response to msg3 1108, the UE can start to return (e.g., from DL BWP562 to DL BWP554 for measuring SSB or other DL RS for synchronization) based on the retuning schedule reported in msg3 1108. In some aspects, after finishing the measurements for resynchronization, the UE can return to the previous BWP (e.g., 562 or 564) to continue the RA procedure or the SDT procedure. In some aspects, the UE can transmit PUCCH1112, which may be delayed due to retuning. The base station can recognize the delay timing for PUCCH1112 based on receiving the retuning schedule report from the UE.

[0086]

[0106] In some aspects, when a UE in RRC idle, inactive, or connected state is configured with an SSB-less DL BWP (e.g., 562) for RA or SDT by SI / RRC, the SSB-less DL BWP 562 may be configured with CORESET / SS for RA (2-step or 4-step RACH) or SDT (RA-SDT or CG-SDT). In some aspects, after the UE initiates RA or SDT in the corresponding UL BWP (e.g., 564), the UE may monitor for a response in the DL BWP 562. The UE may also start a retuning timer for DL ​​BWP switching or retuning to measure SSB or other DL RS outside the SSB-less DL BWP. In some aspects, the UE may also request an RAR window reconfiguration based on an early indication in msg1 or msgA. In some aspects, the UE may initiate retuning after sending msg1 or msgA containing the request. In some aspects, the UE's early indication of the request may be enabled / disabled by the network in SI or RRC. For example, before performing an RA or SDT procedure, the UE may receive an indication from the base station to enable the request. When the UE initiates an RA or SDT procedure in a BWP pair (e.g., 562 and 564), the UE may include a request to the base station. Alternatively, if the UE receives an indication that the request is disabled or does not receive an indication that the request is enabled, the UE may refrain from sending a request to the base station. In some aspects, the UE's request for RAR window reconfiguration may be triggered by a configured condition or event. In response to the occurrence of one or more conditions or trigger events that may have been previously configured for the UE, the UE may send a request. For example, the UE may expect to retune for resynchronization before the RAR window expires. In some aspects, upon transmission of the UE's early indication in msg1 or msgA (including msg1 or msgA transmission in RA-SDT), the base station may delay delivery of msg2 or msgB by a configured time offset to accommodate the UE's timeline extension due to retuning and measurements outside of the SSB-less DL BWP.In some aspects, after measurements outside the SSB-less DL BWP are made, the UE may retune back to the original DL / UL BWP (e.g., 562 and 564), restart the RA / SDT procedure, and reset the retune timer.

[0087]

[0107] FIG. 12 is a diagram 1200 illustrating an example timeline associated with retuning from a BWP pair having a DL BWP that does not include an SSB or other DL reference signal for synchronization to a DL BWP that includes an SSB or DL ​​reference signal for synchronization. As shown in FIG. 12, a UE, such as the UE described in connection with any of FIGS. 4-7, may receive an SSB 1202, for example, in the DL BWP 554. After receiving the SSB 1202, the UE may transmit an initial transmission for msg1 or msgA 1204 in the UL BWP 564. The UE may then monitor for a response from the base station on the DL BWP 562. After the UE initiates an RA or SDT in the UL BWP 564 and after the initial transmission for msg1 or msgA 1204, the UE may start a retuning timer T for DL ​​BWP switching / retuning to measure SSBs or other DL RSs outside the SSB-less DL BWP. r12. The time between receipt of SSB 1202 and the start of the retuning timer may be T0. After the gap for msg2 or msgB RAR window 1206, the UE may monitor for a msg2 or msgB response from the base station in msg2 or msgB RAR window 1208. After random backoff 1210, the UE may be triggered to send a request for RAR window reconfiguration to delay delivery of msgB or msg4. The UE may send the request based on the occurrence of one or more conditions or trigger events that may be configured for the UE by the base station. In some aspects, a msgA or msg1 retransmission with an early indication 1212 may be sent by the UE to the base station. Upon receipt of a msgA or msg1 retransmission with the UE's early indication 1212, the base station may delay delivery of the msgB or msg2 RAR window 1218 and msgB or msg2 1216 by a configured time offset 1214 to accommodate the UE's timeline extension due to retuning and measurements outside the SSB-less DL BWP.

[0088]

[0108] In some aspects, when a UE in RRC idle, inactive, or connected state is configured with an SSB-less DL BWP (e.g., 562) for RA or SDT by SI / RRC, the SSB-less DL BWP may be configured with CORESET / SS for RA (2-step or 4-step RACH) or SDT (RA-SDT or CG-SDT). In some aspects, after the UE starts RA or SDT in the UL BWP (e.g., 564), the UE may start a retuning timer for DL ​​BWP switching / retuning to measure SSB or other DL RS outside the SSB-less DL BWP. The UE may monitor the DL BWP 562 for a response to an uplink message transmitted in the UL BWP 564. In some aspects, the UE may also request RS transmission or RS configuration in the DL BWP 562 based on an earlier indication in msg1, msg3, msgA, PUCCH, PUSCH, or other messages for SDT. In some aspects, the UE may request a TRS or another DL RS that the UE may use for synchronization. Transmission or configuration of a DL reference signal in the DL BWP 562 may allow the UE to continue to monitor the DL BWP 562 and avoid retuning to the DL BWP 554 to perform synchronization. In some aspects, the UE's early indication may be enabled / disabled by the network, for example, through an indication or absence of an indication in SI or RRC signaling. In some aspects, the UE's request for on-demand TRS transmission may be triggered by the occurrence of one or more conditions or events. The conditions or triggering events may be configured by the base station for the UE. In some aspects, upon receiving the UE's request or early indication in msg1, msg3, msgA, PUCCH, CG-PUSCH, or other message, the base station may respond with an ACK or NACK (e.g., in a DCI) for DL ​​feedback for msg2, msgB, or SDT. In some aspects, the base station may acknowledge the UE's request for on-demand transmission or configuration of the TRS if the base station responds with an "ACK" such as a DCI.The UE may then monitor the TRS in the DL BWP 562. The UE may expect to receive the TRS configuration in the MAC-CE associated with the DCI. The UE may also expect to receive the TRS in the SSB-less DL BWP without retuning. If the base station responds with a "NACK" in the DCI, the base station may reject the UE's request for on-demand transmission or configuration of the TRS. Thus, the UE may fall back to a retuning timer based procedure to measure SSB or other DL RS outside the SSB-less DL BWP, e.g., if the timer expires, the UE may switch to the DL BWP 554 to perform synchronization based on the SSB or other DL reference signal.

[0089]

[0109] 13 is a diagram 1300 illustrating an example timeline associated with a two-step RACH. As shown in FIG. 13, after a base station sends a DL transmission 1302 to a UE, a defined parameter N is sent before msgA 1306, which may include a preamble and a payload. gap There may be a gap of N or more 1304 between the preamble and the payload. There may be a gap of N or more between the preamble and the payload. After the start of the msgB RAR window, which may be defined based on the first PDCCH symbol in the earliest SS for the msgB PDCCH, there may be a msgB 1308 transmitted from the base station to the UE. The msgB 1308 may include the msgB PDCCH and the msgB PDSCH (based on successful RAR). After a defined time 1310, the UE may send a PUCCH HARQ ACK / NACK 1312 to the base station.

[0090]

[0110] 14 is a diagram 1400 illustrating an example timeline associated with a four-step RACH. As shown in FIG. 14, after the base station transmits a DL channel or signal 1402 to the UE, there is a defined gap N before msg1 1406 can be transmitted. gapThere may be a gap 1404 equal to msg1 1406. After msg1 1406 and before the RAR window for msg2 associated with msg1 1406, there may be a gap for a defined gap N. After the start of the msg2 RAR window, which may be defined based on the first PDCCH symbol in the type-1 PDCCH SS for msg2, there may be msg2 1408 transmitted from the base station to the UE. msg2 1408 may be associated with a PDCCH. After a defined time, msg3 1410 may be transmitted from the UE to the base station. In response to msg3 1410, the base station may transmit msg4 1412 to the UE, which may be associated with a PDCCH. The PDCCH may schedule resources for a PUCCH 1414. After a certain amount of time, the UE may transmit the PUCCH 1414 to the base station.

[0091]

[0111] 15 is a flowchart 1500 of a method of wireless communication. The method may be performed by a UE (e.g., a UE 104, a UE 602, a UE 702, an apparatus 1704).

[0092]

[0112] In 1502, the UE may receive a configuration for a first DL and UL BWP pair including information indicating at least one of a CORESET, an SS set, and a set of UL resource occasions for a RA procedure or an SDT procedure. The first DL and UL BWP pair may include a first DL BWP and a first UL BWP. For example, the UE described in connection with any of FIG. 4-FIG. 14 may receive a configuration for a first DL and UL BWP pair including information indicating at least one of a CORESET, an SS set, and a set of UL resource occasions for a RA procedure or an SDT procedure. In some aspects, 1502 may be implemented by the synchronization component 198. In some aspects, the first DL BWP does not include an entire SSB transmitted by a serving cell, and the QCL and spatial relationship configuration in the first DL and UL BWP pair is based on the SSB or DL ​​reference signal of the serving cell configured in the second DL BWP. In some aspects, a set of UL resource occasions in a first uplink BWP of a first DL and UL BWP pair is associated (e.g., configured) with a spatial relationship configuration with SSBs or DL ​​reference signals of a serving cell in a second DL BWP and includes one or more of: an RO for an RA procedure, a PUSCH occasion for an RA procedure, an SDT occasion based on a random access or configured grant, an SRS occasion, a PUCCH occasion associated with an RA procedure or an SDT. In some aspects, the configuration for the first DL and UL BWP pair includes information indicating a CD-SSB or an NCD-SSB to be used for a QCL source, a spatial relationship configuration, and synchronization for a UE in the second DL BWP and performing a RA procedure or an SDT procedure in the first DL and UL BWP pair. In some aspects, the configuration for the first DL and UL BWP pair includes information indicating the CSI-RS, PRS, or TRS to be sent by the serving cell in the second DL BWP and used for spatial relationship setup and synchronization for UEs in RRC idle, inactive, or connected states performing an RA or SDT procedure.In some aspects, the CORESET and SS set configured in the first DL BWP for a RA or SDT procedure have a QCL relationship to the SSB or DL ​​reference signal of the serving cell in the second DL BWP.

[0093]

[0113] At 1504, the UE may initiate at least one of an RA procedure or an SDT procedure in the first DL and UL BWP pair. For example, the UE described in connection with any of Figures 4-14 may initiate at least one of an RA procedure or an SDT procedure in the first DL and UL BWP pair. In some aspects, 1504 may be performed by synchronization component 198.

[0094]

[0114] In 1506, the UE may perform time or frequency synchronization using the SSB of the serving cell configured in the second DL BWP or the DL reference signal of the serving cell configured in the second DL BWP (e.g., in the first DL BWP of the first DL and UL BWP pair) during the RA or SDT procedure. For example, the UE described in connection with any of FIG. 4-FIG. 14 may perform time or frequency synchronization using the SSB of the serving cell configured in the second DL BWP or the DL reference signal of the serving cell configured in the second DL BWP (e.g., in the first DL BWP of the first DL and UL BWP pair) during the RA or SDT procedure. In some aspects, 1506 may be implemented by component 198 of FIG. 17. In some aspects, performing time or frequency synchronization includes pausing or canceling activity in a first DL BWP or a first UL BWP of the first DL and UL BWP pair during a RA or SDT procedure; switching from the first DL BWP or the first UL BWP to a second DL BWP to measure an SSB or DL ​​reference signal of a serving cell in the second DL BWP; switching back from the second DL BWP to the first DL BWP or the first UL BWP following the measurement of the SSB or DL ​​reference signal in the second DL BWP; using the measurements obtained in the second DL BWP for time or frequency synchronization, power control, beam management, timing advance validation, or uplink resource occasion reselection; and resuming the RA or SDT procedure in the first DL and UL BWP pair. In some aspects, a timeline for switching from the first DL BWP or the first UL BWP to the second DL BWP is based on one or more of capabilities supported by the UE, a device type indicated by the UE, a trigger event for BWP switching, or a reference SCS associated with the first DL BWP, the first UL BWP, and the second DL BWP.

[0095]

[0115] In some aspects, the UE may also start a first timer associated with a BWP switch from the first DL BWP or the first UL BWP to the second DL BWP for measuring SSB or DL ​​reference signals (e.g., to meet the UE's performance specifications for at least synchronization, beam management, and link maintenance), after initiating the RA or SDT procedure, the first timer tracking a gap to the UE's latest measurement of the SSB or DL ​​reference signals of the serving cell. In some aspects, the UE may start a second timer associated with the RA or SDT procedure, which is set separately from the first timer, after initiating the RA or SDT procedure, and the UE switches from the first DL BWP or the first UL BWP to the second DL BWP for measuring SSB or DL ​​reference signals in response to expiration of the first timer or the second timer or timing advance verification failure for the SDT procedure. In some aspects, the UE may reset the first timer after finishing measuring the SSB or DL ​​reference signals in the second DL BWP.

[0096]

[0116] In some aspects, switching from the first DL BWP or the first UL BWP to the second DL BWP further includes stopping downlink reception in the first DL BWP or uplink transmission in the first UL BWP. In some aspects, the UE can transmit the value of the first timer in a message during an RA procedure or an SDT procedure in one or more valid uplink resource occasions. In some aspects, the UE transmits the value of the first timer in a message based on the first timer and the second timer continuing to run or a successful timing advance verification for the SDT procedure. In some aspects, switching from the first DL BWP or the first UL BWP to the second DL BWP is performed following the transmission of the value of the first timer or based on a BWP retuning schedule received from the serving cell in system information or a dedicated RRC message.

[0097]

[0117] In some aspects, the UE may receive signaling from the serving cell prior to transmitting the message enabling reporting of the value of the first timer, the signaling being received in system information, a dedicated RRC message, a MAC CE, or a DCI. In some aspects, the UE selectively transmits the value of the first timer in the message based on the occurrence of a condition or trigger event that depends at least on the UE capability, the type of RA or SDT procedure, the cell coverage, or the frequency range. In some aspects, in response to the value of the first timer reported by the UE, the UE may receive scheduling information for DL ​​reception or UL transmission including a time offset, the time offset provided by the serving cell being equal to or greater than the UE's BWP switching delay and the measurement gap. In some aspects, the UE may transmit a request for an RAR window adjustment based on the UE's BWP switching delay and the measurement gap in the second DL BWP in an uplink signal or channel (e.g., PRACH, PUSCH, PUCCH, or SRS) associated with the RA or SDT procedure. In some aspects, switching from the first DL BWP or the first UL BWP to the second DL BWP is performed following transmission of a request or based on a BWP retuning schedule received from the serving cell in system information or a dedicated RRC message. In some aspects, the UE can receive signaling enabling a request for RAR window adjustment from the UE before transmitting the random access message, the signaling being received from the serving cell in system information, a dedicated RRC message, MAC CE, or DCI. In some aspects, the UE selectively transmits the request based on occurrence of a condition or trigger event that depends on at least one of the following: UE capabilities, type of RA or SDT procedure, cell coverage, or frequency range.In some aspects, the UE may transmit a request for on-demand transmission of NCD-SSB, TRS, or other DL reference signals in the first DL BWP in an uplink signal or channel (e.g., PRACH, PUSCH, PUCCH, or SRS) associated with an RA or SDT procedure. In some aspects, the UE may receive signaling enabling the request from a serving cell prior to transmitting the request, the signaling being received in system information, a dedicated RRC message, a MAC CE, or a DCI. In some aspects, the UE transmits the request based on the occurrence of a condition or trigger event. In some aspects, the UE may receive a positive response for the on-demand transmission of NCD-SSB, TRS, or other DL reference signals, and performing time or frequency synchronization includes measuring the NCD-SSB, TRS, or other DL reference signals in the first DL BWP after receiving the positive response. In some aspects, the UE may receive a negative response denying the request from the UE. In some aspects, after receiving a negative response, the UE may switch from the first DL BWP or the first UL BWP to the second DL BWP to measure an SSB or a reference signal in the second DL BWP.

[0098]

[0118] 16 is a flowchart 1600 of a method of wireless communication. The method may be performed by a base station (e.g., base station 102 / 180, base station 604, base station 704, device 1802).

[0099]

[0119] In 1602, the base station may send a configuration for a random access procedure or SDT procedure in a first downlink and uplink BWP pair to a UE in an RRC idle, inactive, or connected state, the configuration including information indicating at least one of a CORESET, an SS set, a set of uplink resource occasions for the random access procedure or SDT procedure, and an SSB or DL ​​reference signal in a second DL BWP, where the first DL BWP of the first DL and UL BWP pair does not include an SSB, and the QCL source, spatial relationship configuration, and synchronization for the UE during the random access procedure or SDT procedure are based on the SSB or DL ​​reference signal transmitted by the serving cell in the second DL BWP. For example, the base station described in connection with any of Figures 4-14 may transmit a configuration for a random access procedure or SDT procedure in a first downlink and uplink BWP pair, the configuration including information indicating at least one of a CORESET, an SS set, a set of uplink resource occasions for the random access procedure or SDT procedure, and an SSB or DL ​​reference signal in a second DL BWP, to a UE in an RRC idle, inactive, or connected state, where the first DL BWP of the first DL and UL BWP pair does not include an SSB, and the QCL source, spatial relationship configuration, and synchronization for the UE during the random access procedure or SDT procedure is based on the SSB or DL ​​reference signal transmitted by the serving cell in the second DL BWP. In some aspects, 1602 may be implemented by the synchronization component 1842 of Figure 18.

[0100]

[0120] In 1604, the base station may receive an early indication from the UE of one or more of a device type, a first request for a first on-demand transmission of an SSB or DL ​​reference signal, or other assistance information for adaptive scheduling in at least one of a random access message or an SDT message from the UE in a first UL BWP of a first DL and UL BWP pair. For example, the base station described in connection with any of FIG. 4-14 may receive an early indication from the UE of one or more of a device type, a first request for a first on-demand transmission of an SSB or DL ​​reference signal, or other assistance information for adaptive scheduling in at least one of a random access message or an SDT message from the UE in a first UL BWP of a first DL and UL BWP pair. In some aspects, 1604 may be implemented by the synchronization component 1842 of FIG. 18. In some aspects, the base station may receive in the random access message or SDT message one of: a value of a timer associated with a BWP switch from the first DL BWP or the first UL BWP to the second DL BWP for the UE to measure SSB or downlink reference signals of the serving cell; or a second request for a RAR window adjustment based on a BWP switch delay and a measurement gap for measuring SSB or DL ​​reference signals in the second DL BWP. In some aspects, the base station may schedule downlink transmission or uplink reception with the UE using a time offset for the UE's BWP switch delay and measurement gap to switch from the first DL BWP or the first UL BWP to the second DL BWP for measuring SSB or DL ​​reference signals. In some aspects, the base station may receive in the random access message in the first UL BWP a second request for on-demand transmission of NCD-SSB, TRS, or other DL reference signals in the first DL BWP.In some aspects, the base station can respond to the request with at least one of an acknowledgment and reference signal configuration for one of the NCD-SSB, TRS, or other DL reference signals, or a response message rejecting the second request.

[0101]

[0121] FIG. 17 is a diagram 1700 illustrating an example of a hardware implementation for an apparatus 1704. The apparatus 1704 may be a UE, may be a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1704 may include a cellular baseband processor 1724 (also referred to as a modem) coupled to one or more transceivers 1722 (e.g., cellular RF transceivers). The cellular baseband processor 1724 may include on-chip memory 1724′. In some aspects, the apparatus 1704 may further include an application processor 1706 coupled to one or more subscriber identity module (SIM) cards 1720, a secure digital (SD) card 1708, and a screen 1710. The application processor 1706 may include on-chip memory 1706′. In some aspects, the device 1704 may further include a Bluetooth module 1712, a WLAN module 1714, a satellite system module 1716 (e.g., a GNSS module), one or more sensor modules 1718 (e.g., barometric pressure sensors / altimeters, inertial management units (IMUs), gyroscopes, and / or motion sensors such as accelerometers, light detection and ranging (LIDAR), radio assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometers, audio, and / or other technologies used for positioning), additional memory modules 1726, a power source 1730, and / or a camera 1732. The Bluetooth module 1712, the WLAN module 1714, and the satellite system module 1716 may include on-chip transceivers (TRX) / receivers (RX).The cellular baseband processor 1724 communicates with the UE 104 and / or RUs associated with the network entity 1702 through the transceiver 1722 via one or more antennas 1780. The cellular baseband processor 1724 and the application processor 1706 may each include a computer-readable medium / memory 1724', 1706', respectively. The additional memory module 1726 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1724', 1706', 1726 may be non-transitory. The cellular baseband processor 1724 and the application processor 1706 are each responsible for general processing, including the execution of software stored in the computer-readable medium / memory. The software, when executed by the cellular baseband processor 1724 / application processor 1706, causes the cellular baseband processor 1724 / application processor 1706 to perform various functions described herein. The computer readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1724 / application processor 1706 when executing software. The cellular baseband processor 1724 / application processor 1706 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 1704 may be a processor chip (modem and / or application) and may include only the cellular baseband processor 1724 and / or the application processor 1706, and in another configuration, the device 1704 may be an entire UE (e.g., see 350 in FIG. 3) and may include additional modules of the device 1704.

[0102]

[0122] In some aspects, the synchronization component 198 may be configured to receive a configuration for the first DL and UL BWP pair including information indicating at least one of a CORESET, an SS set, and a set of UL resource occasions for an RA or SDT procedure. In some aspects, the synchronization component 198 may be further configured to initiate at least one of an RA or SDT procedure in the first DL and UL BWP pair. In some aspects, the synchronization component 198 may be further configured to perform time or frequency synchronization using an SSB of the serving cell configured in the second DL BWP or a DL reference signal of the serving cell configured in the second DL BWP (e.g., in the first DL BWP of the first DL and UL BWP pair) during the RA or SDT procedure.

[0103]

[0123] As shown, the apparatus 1704 may include various components configured for various functions. In one configuration, the apparatus 1704, particularly the cellular baseband processor 1724, may include means for receiving a configuration for a first DL and UL BWP pair including information indicating at least one of a CORESET, an SS set, and a set of UL resource occasions for an RA procedure or an SDT procedure. The cellular baseband processor 1724 may further include means for initiating at least one of an RA procedure or an SDT procedure in the first DL and UL BWP pair. The cellular baseband processor 1724 may further include means for performing time or frequency synchronization using an SSB of a serving cell configured in the second DL BWP or a DL reference signal of a serving cell configured in the second DL BWP (e.g., in the first DL BWP of the first DL and UL BWP pair) during the RA procedure or the SDT procedure. The cellular baseband processor 1724 may further include means for suspending or canceling activity in the first DL BWP or the first UL BWP of the first DL and UL BWP pair during an RA procedure or an SDT procedure. The cellular baseband processor 1724 may further include means for switching from the first DL BWP or the first UL BWP to the second DL BWP to measure an SSB or DL ​​reference signal of the serving cell in the second DL BWP. The cellular baseband processor 1724 may further include means for switching back from the second DL BWP to the first DL BWP or the first UL BWP following the measurement of the SSB or DL ​​reference signal in the second DL BWP. The cellular baseband processor 1724 may further include means for using measurements obtained in the second DL BWP for time or frequency synchronization, power control, beam management, timing advance validation, or uplink resource occasion reselection. The cellular baseband processor 1724 may further include means for resuming an RA procedure or an SDT procedure on the first DL and UL BWP pair.The cellular baseband processor 1724 may further include means for starting a first timer associated with a BWP switch from the first DL BWP or the first UL BWP to the second DL BWP for measuring the SSB or DL ​​reference signal, the first timer tracking a gap to the UE's latest measurement of the SSB or DL ​​reference signal of the serving cell, after starting the RA procedure or the SDT procedure. The cellular baseband processor 1724 may further include means for starting a second timer associated with the RA procedure or the SDT procedure, the second timer being set separately from the first timer, after starting the RA procedure or the SDT procedure, and the UE switches from the first DL BWP or the first UL BWP to the second DL BWP for measuring the SSB or DL ​​reference signal in response to expiration of the first timer or the second timer or timing advance verification failure for the SDT procedure. The cellular baseband processor 1724 may further include means for resetting the first timer after finishing the measurement of the SSB or DL ​​reference signal in the second DL BWP. The cellular baseband processor 1724 may further include means for stopping downlink reception in the first DL BWP or uplink transmission in the first UL BWP. The cellular baseband processor 1724 may further include means for transmitting the value of the first timer in a message during the RA procedure or the SDT procedure in one or more valid uplink resource occasions. The cellular baseband processor 1724 may further include means for receiving signaling enabling reporting of the value of the first timer from the serving cell before transmitting the message, the signaling being received in system information, a dedicated RRC message, a MAC CE, or a DCI. The cellular baseband processor 1724 may further include means for receiving scheduling information for DL ​​reception or UL transmission including a time offset in response to a value of the first timer reported by the UE, the time offset provided by the serving cell being equal to or greater than a BWP switching delay and a measurement gap of the UE.The cellular baseband processor 1724 may further include means for transmitting a request for an RAR window adjustment based on the UE's BWP switching delay and the measurement gap in the second DL BWP in an uplink signal or channel associated with the RA or SDT procedure. The cellular baseband processor 1724 may further include means for receiving signaling enabling the request for the RAR window adjustment from the UE before transmitting the random access message, the signaling being received from the serving cell in the system information, the dedicated RRC message, the MAC CE, or the DCI. The cellular baseband processor 1724 may further include means for transmitting a request for on-demand transmission of the NCD-SSB, TRS, or other DL reference signal in the first DL BWP in an uplink signal or channel associated with the RA or SDT procedure. The cellular baseband processor 1724 may further include means for receiving signaling enabling the request from the serving cell prior to transmitting the request, the signaling being received in system information, a dedicated RRC message, a MAC CE, or a DCI. The cellular baseband processor 1724 may further include means for receiving an acknowledgement for an on-demand transmission of the NCD-SSB, TRS, or other DL reference signal, and performing time or frequency synchronization includes measuring the NCD-SSB, TRS, or other DL reference signal in the first DL BWP after receiving the acknowledgement. The cellular baseband processor 1724 may further include means for receiving a negative acknowledgement rejecting the request from the UE. The cellular baseband processor 1724 may further include means for switching from the first DL BWP or the first UL BWP to the second DL BWP to measure the SSB or reference signal in the second DL BWP after receiving the negative acknowledgement. The means may be one or more of the components of the device 1704 (e.g., component 198) configured to perform the recited functions by the means. As described above, the device 1704 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 said means.

[0104]

[0124] FIG. 18 is a diagram 1800 illustrating an example of a hardware implementation for an apparatus 1802. The apparatus 1802 may be a base station, a component of a base station, or may implement base station functionality. In some aspects, the apparatus 1704 may include a baseband unit 1804. The baseband unit 1804 may communicate with the UE 104 via a cellular RF transceiver 1822. The baseband unit 1804 may include a computer-readable medium / memory. The baseband unit 1804 is responsible for overall processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the baseband unit 1804, causes the baseband unit 1804 to perform various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the baseband unit 1804 when executing the software. The baseband unit 1804 further includes a receiving component 1830, a communication manager 1832, and a transmitting component 1834. The communications manager 1832 includes one or more of the illustrated components. The components in the communications manager 1832 may be stored in a computer readable medium / memory and / or may be configured as hardware in the baseband unit 1804. The baseband unit 1804 may be a component of the base station 310 and may include the memory 376 and / or at least one of the TX processor 316, the RX processor 370, and the controller / processor 375.

[0105]

[0125] The communications manager 1832 may include a synchronization component 1842 that may send configuration to a UE in an RRC idle, inactive, or connected state, for a random access procedure or SDT procedure in a first downlink and uplink BWP pair, the configuration including information indicating at least one of a CORESET, an SS set, a set of uplink resource occasions for the random access procedure or SDT procedure, and an SSB or DL ​​reference signal in a second DL BWP, as described, for example, in connection with 1602 of FIG. 16, where the first DL BWP of the first DL and UL BWP pair does not include an SSB, and the QCL source, spatial relationship configuration, and synchronization for the UE during the random access procedure or SDT procedure is based on the SSB or DL ​​reference signal transmitted by the serving cell in the second DL BWP. The communications manager 1832 may further include a synchronization component 1842 that may receive an early indication from the UE of one or more of a device type, a first request for a first on-demand transmission of an SSB or DL ​​reference signal, or other assistance information for adaptive scheduling in at least one of a random access message or an SDT message from the UE in a first UL BWP of a first DL and UL BWP pair, e.g., as described in connection with 1604 of FIG. 16 .

[0106]

[0126] The apparatus may include additional components that implement each of the blocks of the algorithm in the flowchart of Figure 16. Thus, each block in the flowchart of Figure 16 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.

[0107]

[0127] As shown, the apparatus 1802 may include various components configured for various functions. In some aspects, the apparatus 1802, particularly the baseband unit 1804, may include means for transmitting a configuration for a random access procedure or SDT procedure in a first downlink and uplink BWP pair, the configuration including information indicating at least one of a CORESET, an SS set, a set of uplink resource occasions for the random access procedure or SDT procedure, and an SSB or DL ​​reference signal in a second DL BWP, to a UE in an RRC idle, inactive, or connected state, where the first DL BWP of the first DL and UL BWP pair does not include an SSB, and the QCL source, spatial relationship configuration, and synchronization for the UE during the random access procedure or SDT procedure are based on an SSB or DL ​​reference signal transmitted by a serving cell in the second DL BWP. The baseband unit 1804 may further include means for receiving an early indication from the UE of one or more of a device type, a first request for a first on-demand transmission of an SSB or DL ​​reference signal, or other assistance information for adaptive scheduling in at least one of a random access message or an SDT message from the UE in a first UL BWP of the first DL and UL BWP pair. The baseband unit 1804 may further include means for scheduling downlink transmission or uplink reception with the UE using a time offset for a BWP switching delay and a measurement gap for the UE to switch from the first DL BWP or the first UL BWP to a second DL BWP to measure the SSB or DL ​​reference signal. The baseband unit 1804 may further include means for receiving a second request in a random access message in the first UL BWP for an on-demand transmission of an NCD-SSB, a TRS, or other DL reference signal in the first DL BWP. The baseband unit 1804 may further include means for transmitting at least one of an acknowledgment and reference signal setting for one of the NCD-SSB, TRS, or other DL reference signals in response to the request, or a response message rejecting the second request.The means may be one or more of the components of the apparatus 1802 configured to perform the recited functions by the means. As described above, the apparatus 1802 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.

[0108]

[0128] FIG. 19 is a diagram 1900 illustrating an example of a wireless communication system and access network. The illustrated wireless communication system includes a non-aggregated base station architecture. The non-aggregated base station architecture may include one or more CUs 1910 that may communicate directly with a core network 1920 via a backhaul link or indirectly with the core network 1920 through one or more non-aggregated base station units (such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 1925 via an E2 link, or a non-real-time (non-RT) RIC 1915 associated with a Service Management and Orchestration (SMO) framework 1905, or both). The CUs 1910 may communicate with one or more DUs 1930 via respective midhaul links, such as an F1 interface. The DUs 1930 may communicate with one or more RUs 1940 via respective fronthaul links. The RUs 1940 may communicate with respective UEs 1904 via one or more radio frequency (RF) access links. In some implementations, a UE 1904 may be served by multiple RUs 1940 simultaneously.

[0109]

[0129] Each of the units, i.e., CU1910, DU1930, RU1940, as well as quasi-RT RIC1925, non-RT RIC1915, and SMO framework 1905, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) over a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the unit's communication interface, may be configured to communicate with one or more of the other units over a transmission medium. For example, a unit may include a wired interface configured to receive or transmit signals to one or more of the other units over a wired transmission medium. Additionally, a unit may include a wireless interface, which may include a receiver, transmitter, or transceiver (such as an RF transceiver), configured to receive and / or transmit signals to one or more of the other units over a wireless transmission medium.

[0110]

[0130] In some aspects, the CU 1910 may host one or more upper layer control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), and the like. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by the CU 1910. The CU 1910 may be configured to handle user plane functions (i.e., Central Unit-User Plane (CU-UP)), control plane functions (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 1910 may be logically divided into one or more CU-UP units and one or more CU-CP units. The CU-UP units, when implemented in an O-RAN configuration, may communicate bidirectionally with the CU-CP units via an interface, such as an E1 interface. The CU 1910 may be implemented to communicate with the DU 1930, as needed, for network control and signaling.

[0111]

[0131] The DU 1930 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 1940. In some aspects, the DU 1930 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more upper physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, etc.) depending on a functional division such as that defined by 3GPP. In some aspects, the DU 1930 may further host one or more lower PHY layers. Each layer (or module) may be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 1930 or with a control function hosted by the CU 1910.

[0112]

[0132] The lower layer functions may be implemented by one or more RUs 1940. In some deployments, the RUs 1940 controlled by the DU 1930 may correspond to logical nodes hosting RF processing functions, or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based on a functional division, such as a lower layer functional division. In such an architecture, the RUs 1940 may be implemented to handle over-the-air (OTA) communications with one or more UEs 1904. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RUs 1940 may be controlled by the corresponding DUs 1930. In some scenarios, this configuration may enable the DUs 1930 and CUs 1910 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0113]

[0133] The SMO framework 1905 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 1905 may be configured to support deployment of dedicated physical resources for RAN coverage requirements that may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 1905 may be configured to interact with a cloud computing platform (such as an open cloud (O-cloud) 1990) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, a CU 1910, a DU 1930, a RU 1940, and a quasi-RT RIC 1925. In some implementations, the SMO framework 1905 may communicate with hardware aspects of a 4G RAN, such as an open eNB (O-eNB) 1911, via an O1 interface. Additionally, in some implementations, the SMO framework 1905 can communicate directly with one or more RUs 1940 via an O1 interface. The SMO framework 1905 can also include a non-RT RIC 1915 configured to support the functionality of the SMO framework 1905.

[0114]

[0134] The non-RT RIC 1915 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the quasi-RT RIC 1925. The non-RT RIC 1915 may be coupled to or in communication with the quasi-RT RIC 1925 (e.g., via an A1 interface). The quasi-RT RIC 1925 may be configured to include logic functions that enable near real-time control and optimization of RAN elements and resources through data collection and action via one or more CUs 1910, one or more DUs 1930, or both, and an interface connecting the O-eNB to the quasi-RT RIC 1925 (e.g., via an E2 interface).

[0115]

[0135] In some implementations, the non-RT RIC 1915 may receive parameters or external enrichment information from an external server to generate the AI / ML models deployed to the quasi-RT RIC 1925. Such information may be utilized by the quasi-RT RIC 1925 and may be received at the SMO framework 1905 or the non-RT RIC 1915 from non-network data sources or from network functions. In some examples, the non-RT RIC 1915 or the quasi-RT RIC 1925 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 1915 may employ the AI / ML models to monitor long-term trends and patterns in performance and implement corrective actions through the SMO framework 1905 (e.g., reconfiguration via O1) or through the creation of RAN management policies (e.g., A1 policies).

[0116]

[0136] At least one of the CU 1910, the DU 1930, and the RU 1940 may be referred to as a base station 1902. Thus, the base station 1902 may include one or more of the CU 1910, the DU 1930, and the RU 1940 (each component is shown with a dotted line to indicate that each component may or may not be included in the base station 1902). The base station 1902 provides an access point to a core network 1920 for the UE 1904. The base station 1902 may include a macro cell (high power cellular base station) and / or a small cell (low power cellular base station). Small cells include femto cells, pico cells, and micro cells. 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 serve restricted groups known as closed subscriber groups (CSGs). The communication link between the RU 1940 and the UE 1904 may include uplink (UL) (also referred to as reverse link) transmission from the UE 1904 to the RU 1940, and / or downlink (DL) (also referred to as forward link) transmission from the RU 1940 to the UE 1904. The communication link may use multiple-input multiple-output (MIMO) antenna technology including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be through one or more carriers. The base station 1902 / UE 1904 may use spectrum with a bandwidth of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) per carrier, allocated in carrier aggregation with up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be 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).

[0117]

[0137] Particular UEs 1904 may communicate with each other using device-to-device (D2D) communication links 1958. The D2D communication links 1958 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication links 1958 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 via various wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0118]

[0138] The wireless communication system may further include a Wi-Fi AP 1950 that communicates with the UE 1904 (also referred to as a Wi-Fi station (STA)) via a communication link 1954, such as in the 5 GHz unlicensed frequency spectrum. When communicating in the unlicensed frequency spectrum, the UE 1904 / AP 1950 may perform a clear channel assessment (CCA) before communicating to determine if a channel is available.

[0119]

[0139] The electromagnetic spectrum is often divided into various classes, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified with 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. Similar nomenclature issues 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).

[0120]

[0140] 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 (71 GHz to 1914.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0121]

[0141] With the above aspects in mind, unless otherwise indicated, as used herein, terms such as "sub-6 GHz" may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, as used herein, unless otherwise indicated, terms such as "millimeter wave" 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.

[0122]

[0142] The base station 1902 and the UE 1904 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. The base station 1902 may transmit a beamformed signal 1982 to the UE 1904 in one or more transmit directions. The UE 1904 may receive the beamformed signal from the base station 1902 in one or more receive directions. The UE 1904 may also transmit a beamformed signal 1984 to the base station 1902 in one or more transmit directions. The base station 1902 may receive the beamformed signal from the UE 1904 in one or more receive directions. The base station 1902 / UE 1904 may perform beam training to determine the best receive and transmit directions for each of the base stations 1902 / UE 1904. The transmit and receive directions for the base station 1902 may or may not be the same. The transmit and receive directions for the UE 1904 may or may not be the same.

[0123]

[0143] The base station 1902 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), TRP, network node, network entity, network equipment, or some other suitable terminology. The base station 1902 may be implemented as an aggregated (monolithic) base station having an integrated access and backhaul (IAB) node, a relay node, a sidelink node, a baseband unit (BBU) (including CU and DU) and a RU, or as a non-aggregated base station including one or more of a CU, DU, and / or RU.

[0124]

[0144] The core network 1920 may include an access and mobility management function (AMF) 1961, a session management function (SMF) 1962, a user plane function (UPF) 1963, a unified data management (UDM) 1964, one or more location servers 1968, and other functional entities. The AMF 1961 is a control node that handles signaling between the UE 1904 and the core network 1920. The AMF 1961 supports registration management, connection management, mobility management, and other functions. The SMF 1962 supports session management and other functions. The UPF 1963 supports packet routing, packet forwarding, and other functions. The UDM 1964 supports authentication and key agreement (AKA) credential generation, user identity handling, access authorization, and subscription management. The one or more location servers 1968 are shown as including a Gateway Mobile Location Center (GMLC) 1965 and a Location Management Function (LMF) 1966. In general, however, the one or more location servers 1968 may include one or more location / positioning servers, which may include one or more of the GMLC 1965, the LMF 1966, a position determination entity (PDE), a serving mobile location center (SMLC), a mobile positioning center (MPC), etc. The GMLC 1965 and the LMF 1966 support UE location services. The GMLC 1965 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 1966 receives measurement and assistance information from the NG-RAN and the UE 1904 via the AMF 1961 to calculate the position of the UE 1904. The NG-RAN may use one or more positioning methods to determine the location of the UE 1904.Positioning the UE 1904 may include signal measurements, a position estimate, and an optional velocity calculation based on these measurements. The signal measurements may be performed by the UE 1904 and / or the serving base station 1902. The signals measured may include one or more of satellite positioning system (SPS) 1970 (e.g., one or more of Global Navigation Satellite System (GNSS), global position system (GPS), non-terrestrial network (NTN), or other satellite position / location systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, terrestrial beacon system (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR enhanced cell ID (NR E-CID) method, NR signals (e.g., multiple round trip time, multiple RTT), DL angle-of-departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle-of-arrival (UL-AR) (UL-AR). The positioning may be based on one or more of: UL-AoA (angle-of-arrival), UL-AoA (ultrasonic-based) positioning, and / or other systems / signals / sensors.

[0125]

[0145] Examples of UEs 1904 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 1904 may be referred to as IoT devices (e.g., a parking meter, a gas pump, a toaster, a vehicle, a heart monitor, etc.). The UEs 1904 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, 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.

[0126]

[0146] Referring again to FIG. 19, in some aspects, the UE 1904 may include a synchronization component 1998. In some aspects, the synchronization component 1998 may be configured to receive a configuration for a first DL and UL BWP pair including information indicating at least one of a CORESET, an SS set, and a set of UL resource occasions for an RA or SDT procedure. In some aspects, the synchronization component 1998 may be further configured to initiate at least one of an RA or SDT procedure in the first DL and UL BWP pair. In some aspects, the synchronization component 1998 may be further configured to perform time or frequency synchronization using an SSB of a serving cell configured in the second DL BWP or a DL reference signal of a serving cell configured in the second DL BWP (e.g., in the first DL BWP of the first DL and UL BWP pair) during an RA or SDT procedure.

[0127]

[0147] In some aspects, the base station 102 may include a synchronization component 1999. In some aspects, the synchronization component 1999 may be configured to transmit a configuration for a random access procedure or an SDT procedure in a first downlink and uplink BWP pair, the configuration including information indicating at least one of a CORESET, an SS set, a set of uplink resource occasions for the random access procedure or the SDT procedure, and an SSB or DL ​​reference signal in a second DL BWP, to a UE in an RRC idle, inactive, or connected state, where the first DL BWP of the first DL and UL BWP pair does not include an SSB, and the QCL source, spatial relationship configuration, and synchronization for the UE during the random access procedure or the SDT procedure is based on the SSB or DL ​​reference signal transmitted by the serving cell in the second DL BWP. In some aspects, the synchronization component 1999 may be further configured to receive an early indication from the UE of one or more of a device type, a first request for a first on-demand transmission of an SSB or DL ​​reference signal, or other assistance information for adaptive scheduling in at least one of a random access message or an SDT message from the UE in a first UL BWP of the first DL and UL BWP pair. FIG. 20 is a diagram 2000 illustrating an example of a hardware implementation for a network entity 2002. The network entity 2002 may be a BS, may be a component of a BS, or may implement a BS function. The network entity 2002 may include at least one of a CU 2010, a DU 2030, or a RU 2040. For example, depending on the layer functions processed by the components 199, the network entity 2002 may include a CU 2010, both the CU 2010 and the DU 2030, each of the CU 2010, the DU 2030, and the RU 2040, both the DU 2030, the DU 2030, and the RU 2040, or the RU 2040. The CU 2010 may include a CU processor 2012. The CU processor 2012 may include an on-chip memory 2012'. In some aspects, the CU 2010 may further include an additional memory module 2014 and a communication interface 2018.The CU 2010 communicates with the DU 2030 via a midhaul link, such as an F1 interface. The DU 2030 may include a DU processor 2032. The DU processor 2032 may include an on-chip memory 2032'. In some aspects, the DU 2030 may further include an additional memory module 2034 and a communication interface 2038. The DU 2030 communicates with the RU 2040 via a fronthaul link. The RU 2040 may include a RU processor 2042. The RU processor 2042 may include an on-chip memory 2042'. In some aspects, the RU 2040 may further include an additional memory module 2044, one or more transceivers 2046, an antenna 2080, and a communication interface 2048. The RU 2040 communicates with the UE 104. The on-chip memories 2012', 2032', 2042' and the additional memory modules 2014, 2034, 2044 may each be considered a computer readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of the processors 2012, 2032, 2042 is responsible for general processing, including the execution of software stored in the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform various functions described herein. The computer readable medium / memory may also be used to store data that is manipulated by the processor when executing the software.

[0128]

[0148] In some aspects, the synchronization component 199 may be configured to transmit a configuration for a random access procedure or an SDT procedure in a first downlink and uplink BWP pair to a UE in an RRC idle, inactive, or connected state, the configuration including information indicating at least one of a CORESET, an SS set, a set of uplink resource occasions for the random access procedure or SDT procedure, and an SSB or DL ​​reference signal in a second DL BWP, where the first DL BWP of the first DL and UL BWP pair does not include an SSB, and the QCL source, spatial relationship configuration, and synchronization for the UE during the random access procedure or SDT procedure are based on the SSB or DL ​​reference signal transmitted by the serving cell in the second DL BWP. In some aspects, the synchronization component 199 may be further configured to receive an early indication from the UE of one or more of a device type, a first request for a first on-demand transmission of an SSB or DL ​​reference signal, or other assistance information for adaptive scheduling in at least one of a random access message or an SDT message from the UE in a first UL BWP of a first DL and UL BWP pair. The synchronization component 199 may be within one or more processors of one or more of the CU 2010, DU 2030, and RU 2040. The synchronization component 199 may be one or more hardware components specifically configured to perform the described processes / algorithms, be implemented by one or more processors configured to perform the described processes / algorithms, be stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. The network entity 2002 may include various components configured for various functions.The network entity 2002 may include means for transmitting a configuration for a random access procedure or an SDT procedure in a first downlink and uplink BWP pair to a UE in an RRC idle, inactive, or connected state, the configuration including information indicating at least one of a CORESET, an SS set, a set of uplink resource occasions for the random access procedure or the SDT procedure, and an SSB or DL ​​reference signal in a second DL BWP, where a first DL BWP of the first DL and UL BWP pair does not include an SSB, and a QCL source, spatial relationship configuration, and synchronization for the UE during the random access procedure or the SDT procedure is based on an SSB or DL ​​reference signal transmitted by a serving cell in the second DL BWP. The network entity 2002 may further include means for receiving an early indication from the UE of one or more of a device type, a first request for a first on-demand transmission of an SSB or DL ​​reference signal, or other assistance information for adaptive scheduling in at least one of a random access message or an SDT message from the UE in a first UL BWP of the first DL and UL BWP pair. The network entity 2002 may further include means for scheduling downlink transmission or uplink reception with the UE using a time offset for a BWP switching delay and a measurement gap for the UE to switch from the first DL BWP or the first UL BWP to a second DL BWP to measure SSB or DL ​​reference signals. The network entity 2002 may further include means for receiving a second request in a random access message in the first UL BWP for on-demand transmission of the NCD-SSB, TRS, or other DL reference signals in the first DL BWP. The network entity 2002 may further include means for transmitting at least one of an acknowledgment and reference signal configuration for one of the NCD-SSB, TRS, or other DL reference signals, or a response message rejecting the second request in response to the request.The means may be the synchronization component 199 of the network entity 2002 configured to perform the functions recited by the means. As described herein, the network entity 2002 may include a TX processor 316, an RX processor 370, and a 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 functions recited by the means.

[0129]

[0149] It should be understood that the particular order or hierarchy of the blocks in the disclosed processes / flow charts is an example of an example approach. It should be understood that the particular order or hierarchy of the blocks in those processes / flow charts can be rearranged based on design preferences. 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 limited to the particular order or hierarchy presented.

[0130]

[0150] 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 limited to the aspects described herein, but are to be accorded the full scope consistent with the language of the claims. Reference to an element in the singular is not intended to mean "only one" unless so expressly stated, but rather "one or more." Terms such as "if," "when," and "while" do not imply an immediate temporal relationship or reaction. That is, these phrases, such as "when," do not imply an 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 any 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" is not necessarily to 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 members of A, B, or C. A set should be interpreted as a set of elements, the number of elements being one or more. Thus, for a set of X, X will include one or more elements. When a first device receives data from or transmits data to a second device, the data may be received / transmitted directly between the first device and the second device, or indirectly between the first device and the second device via a set of devices. All structural and functional equivalents to the elements of the various embodiments described throughout this disclosure that are known or later become known to those skilled in the art are expressly incorporated herein by reference and encompassed by the claims. Moreover, 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." Thus, no element of a claim should be construed as a means-plus-function unless the element is expressly recited using the phrase "means for."

[0131]

[0151] As used herein, the phrase "based on" should not be construed as a reference to a closed set of information, condition(s), factor(s), etc. In other words, the phrase "based on A" (where "A" can be information, condition, factor, etc.) is to be construed as "based on at least A," unless expressly stated otherwise.

[0132]

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

[0133]

[0153] Aspect 1 is a method of wireless communication in a UE, the method including: receiving a configuration for a first DL and UL BWP pair including information indicating at least one of a CORESET, an SS set, and a set of UL resource occasions for a RA procedure or an SDT procedure, the first DL and UL BWP pair including a first DL BWP and a first UL BWP; initiating at least one of an RA procedure or an SDT procedure in the first DL and UL BWP pair; and performing time or frequency synchronization during the RA procedure or the SDT procedure using an SSB of a serving cell configured in the second DL BWP or a DL reference signal of a serving cell configured in the second DL BWP.

[0134]

[0154] Aspect 2 is the method of aspect 1, in which the first DL BWP does not include the entire SSB transmitted by the serving cell, and the QCL and spatial relationship setting in the first DL and UL BWP pair is based on the SSB or DL ​​reference signal of the serving cell set in the second DL BWP.

[0135]

[0155] Example 3 is the method of example 1 or 2, wherein a set of UL resource occasions in a first uplink BWP of a first DL and UL BWP pair is associated (e.g., configured) with a spatial relationship configuration using an SSB or DL ​​reference signal of a serving cell in a second DL BWP, and includes one or more of an RO of an RA procedure, a PUSCH occasion of an RA procedure, an SDT occasion based on a random access or configured grant, an SRS occasion, or a PUCCH occasion associated with an RA procedure or an SDT.

[0136]

[0156] Example 4 is the method of any of Examples 1-3, wherein the configuration for the first DL and UL BWP pair includes information indicating a QCL source, a spatial relationship configuration, and a CD-SSB or an NCD-SSB to be used for synchronization (e.g., used as) for a UE that is in the second DL BWP and that performs a RA procedure or an SDT procedure in the first DL and UL BWP pair. In some aspects, the spatial relationship configuration for the NCD-SSB and the CD-SSB may be the same since the NCD-SSB and the CD-SSB may share the same ssb-positioninBurst information element (IE).

[0137]

[0157] Example 5 is the method of any of Examples 1 to 4, wherein the configuration for the first DL and UL BWP pair is sent by the serving cell in the second DL BWP and includes information indicating a CSI-RS, a PRS, or a TRS to be used for spatial relationship configuration and synchronization for a UE in an RRC idle, inactive, or connected state performing an RA procedure or an SDT procedure.

[0138]

[0158] Example 6 is any of the methods of Examples 1 to 5, in which the CORESET and SS set configured in the first DL BWP for the RA procedure or SDT procedure have a QCL relationship to the SSB or DL ​​reference signal of the serving cell in the second DL BWP.

[0139]

[0159] Example 7 is the method of any of Examples 1 to 6, wherein performing time or frequency synchronization includes suspending or stopping communication in a first DL BWP or a first UL BWP of the first DL and UL BWP pair during an RA procedure or an SDT procedure; switching from the first DL BWP or the first UL BWP to a second DL BWP to measure an SSB or DL ​​reference signal of a serving cell in the second DL BWP; switching back from the second DL BWP to the first DL BWP or the first UL BWP following the measurement of the SSB or DL ​​reference signal in the second DL BWP; using the measurements obtained in the second DL BWP for time or frequency synchronization, power control, beam management, timing advance verification, or uplink resource occasion reselection; and resuming or restarting communication during the RA procedure or SDT procedure in the first DL and UL BWP pair.

[0140]

[0160] Example 8 is the method of any of Examples 1-7, wherein the timeline for switching from the first DL BWP or the first UL BWP to the second DL BWP is based on one or more of capabilities supported by the UE, a device type indicated by the UE, a trigger event for BWP switching, or a reference SCS associated with the first DL BWP, the first UL BWP, and the second DL BWP.

[0141]

[0161] Aspect 9 includes starting a first timer associated with a BWP switch from a first DL BWP or a first UL BWP to a second DL BWP for measuring SSB or DL ​​reference signals, the first timer tracking a gap to the UE's latest measurement of the SSB or DL ​​reference signals of the serving cell, after starting an RA procedure or an SDT procedure; and starting a second timer associated with the RA procedure or the SDT procedure (e.g., may correspond to a cg-SDT-TimeAlignmentTimerCommon information element or a TimeAlignmentTimer information element), which is set separately from the first timer, after starting an RA procedure or an SDT procedure, where the UE switches from the first DL BWP or the first UL BWP to the second DL BWP for measuring SSB or DL ​​reference signals in response to expiration of the first timer or the second timer or a timing advance verification failure for the SDT procedure; The method according to any one of aspects 1 to 8, further comprising: resetting the first timer after completing measurement of the SSB or DL ​​reference signal in the BWP.

[0142]

[0162] Aspect 10 is the method of any of aspects 1 to 9, wherein switching from the first DL BWP or the first UL BWP to the second DL BWP further includes stopping downlink reception in the first DL BWP or uplink transmission in the first UL BWP.

[0143]

[0163] Example 11 is the method of any of Examples 1 to 10, further comprising transmitting a value of the first timer in a message during an RA procedure or an SDT procedure in one or more valid uplink resource occasions.

[0144]

[0164] Example 12 is a method according to any one of Examples 1 to 11, wherein the UE sends a value of the first timer in the message based on the first timer and the second timer continuing to run or successful timing advance verification for the SDT procedure.

[0145]

[0165] Example 13 is the method of any of Examples 1 to 12, wherein switching from the first DL BWP or the first UL BWP to the second DL BWP is performed following transmission of a value of the first timer or based on a BWP retuning schedule received from the serving cell in system information or a dedicated RRC message.

[0146]

[0166] Aspect 14 is a method according to any of aspects 1 to 13, further comprising receiving signaling from the serving cell prior to sending the message enabling reporting of a value of the first timer (which may, for example, correspond to a ue-TimerAndConstants information element), the signaling being received in system information, a dedicated RRC message, a MAC CE, or a DCI (for example, in SIB1).

[0147]

[0167] Aspect 15 is a method according to any one of aspects 1 to 14, wherein the UE selectively transmits a value of the first timer in the message based on the occurrence of a condition or trigger event that depends at least on UE capability, a type of RA procedure or SDT procedure, cell coverage, or a frequency range.

[0148]

[0168] Example 16 is the method of any of Examples 1 to 15, further comprising receiving scheduling information for DL ​​reception or UL transmission including a time offset in response to a value of the first timer reported by the UE, wherein the time offset provided by the serving cell is greater than or equal to a BWP switching delay and a measurement gap of the UE.

[0149]

[0169] Example 17 is the method of any of Examples 1 to 16, further comprising: transmitting a request for an RAR window adjustment based on a BWP switching delay and a measurement gap of the UE in the second DL BWP in an uplink signal or channel associated with the RA procedure or the SDT procedure.

[0150]

[0170] Example 18 is any of the methods of Examples 1 to 17, wherein switching from the first DL BWP or the first UL BWP to the second DL BWP is performed following transmission of a request or based on a BWP retuning schedule received from the serving cell in system information or a dedicated RRC message.

[0151]

[0171] Example 19 is the method of any of Examples 1 to 18, further comprising receiving signaling from the UE prior to sending the random access message enabling a request for RAR window adjustment, the signaling being received from the serving cell in system information, a dedicated RRC message, MAC CE, or DCI.

[0152]

[0172] Example 20 is any of the methods of Examples 1 to 19, in which the UE selectively transmits the request based on the occurrence of a condition or trigger event that depends on at least one of the following: UE capability, type of RA procedure or SDT procedure, cell coverage, or frequency range.

[0153]

[0173] Example 21 is the method of any of Examples 1 to 20, further comprising transmitting a request for on-demand transmission of an NCD-SSB, TRS, or other DL reference signal in the first DL BWP in an uplink signal or channel associated with an RA procedure or an SDT procedure.

[0154]

[0174] Example 22 is the method of any of Examples 1 to 21, further comprising receiving signaling enabling the request from the serving cell before sending the request, the signaling being received in system information, a dedicated RRC message, a MAC CE, or a DCI.

[0155]

[0175] Example 23 is the method of any one of Examples 1 to 22, wherein the UE sends the request based on the occurrence of a condition or a trigger event.

[0156]

[0176] Example 24 is the method of any of Examples 1 to 23, further including receiving an acknowledgment for the on-demand transmission of the NCD-SSB, TRS, or other DL reference signal, and performing time or frequency synchronization includes measuring the NCD-SSB, TRS, or other DL reference signal in the first DL BWP after receiving the acknowledgment.

[0157]

[0177] Example 25 is the method of any of Examples 1 to 24, further including receiving a negative response from the UE rejecting the request, and switching from the first DL BWP or the first UL BWP to the second DL BWP after receiving the negative response to measure an SSB or a reference signal in the second DL BWP.

[0158]

[0178] Aspect 26 is a wireless communication method in a base station (e.g., a network node), comprising: transmitting a configuration for a random access procedure or an SDT procedure in a first downlink and uplink BWP pair to a UE in an RRC idle, inactive, or connected state, the configuration including information indicating at least one of a CORESET, an SS set, a set of uplink resource occasions for the random access procedure or the SDT procedure, and an SSB or DL ​​reference signal in a second DL BWP, where the first DL BWP of the first DL and UL BWP pair does not include an SSB, and a QCL source, spatial relationship configuration, and synchronization for the UE during the random access procedure or the SDT procedure is based on an SSB or DL ​​reference signal transmitted by a serving cell in the second DL BWP; receiving from the UE, in at least one of a random access message or an SDT message from the UE in a first UL BWP of the first DL and UL BWP pair, an early indication of one or more of a device type, a first request for a first on-demand transmission of an SSB or DL ​​reference signal, or other assistance information for adaptive scheduling.

[0159]

[0179] Aspect 27 is the method of aspect 26, further including receiving in the random access message or the SDT message one of: a value of a timer associated with a BWP switch from the first DL BWP or the first UL BWP to the second DL BWP for the UE to measure an SSB or downlink reference signal of the serving cell; or a second request for an RAR window adjustment based on a BWP switch delay and a measurement gap for measuring an SSB or DL ​​reference signal in the second DL BWP; and the method further includes scheduling downlink transmission or uplink reception with the UE using a time offset for the UE's BWP switch delay and the measurement gap to switch from the first DL BWP or the first UL BWP to the second DL BWP for measuring the SSB or DL ​​reference signal.

[0160]

[0180] Example 28 is the method of example 26 or 27, further including receiving a second request in a random access message in the first UL BWP for on-demand transmission of an NCD-SSB, TRS, or other DL reference signal in the first DL BWP, and transmitting at least one of an acknowledgment and reference signal configuration for one of the NCD-SSB, TRS, or other DL reference signal, or a response message rejecting the second request in response to the request.

[0161]

[0181] Example 29 is an apparatus for wireless communication including at least one processor coupled to a memory and configured to perform the method of any of Examples 1-25.

[0162]

[0182]

[0041] Example 30 is an apparatus for wireless communication including at least one processor coupled to a memory and configured to perform the method of any of Examples 26-28.

[0163]

[0183] Aspect 31 is an apparatus for wireless communication, comprising means for implementing the method of any of aspects 1 to 25.

[0164]

[0184] Aspect 32 is an apparatus for wireless communication comprising means for performing the method of any of aspects 26 to 28.

[0165]

[0185] Aspect 33 is a computer-readable medium storing computer-executable code, which when executed by a processor causes the processor to perform the method of any of aspects 1-25.

[0166]

[0186] Aspect 34 is a computer readable medium storing computer executable code that, when executed by a processor, causes the processor to perform the method of any of aspects 26-28.

Claims

1. 1. An apparatus for wireless communication in a user equipment (UE), comprising: Memory and at least one processor coupled to the memory; wherein the at least one processor: receive a configuration for a first downlink (DL) and uplink (UL) bandwidth portion (BWP) pair, the first downlink (DL) and uplink (UL) bandwidth portion (BWP) pair including a first DL BWP and a first UL BWP, the configuration including information indicating at least one of a control resource set (CORESET), a search space (SS) set, and a set of UL resource occasions for a random access (RA) procedure or a small data transmission (SDT) procedure; initiating at least one of the RA procedure or the SDT procedure on the first DL and UL BWP pair; During the RA procedure or the SDT procedure, time synchronization or frequency synchronization is performed using a synchronization signal block (SSB) of a serving cell configured in a second DL BWP or a DL reference signal of the serving cell configured in the second DL BWP. The apparatus is configured to:

2. 2. The apparatus of claim 1, wherein the first DL BWP does not include an entire SSB transmitted by the serving cell, and a quasi-co-location (QCL) and spatial relationship configuration in the first DL and UL BWP pair is based on the SSB or the DL reference signal of the serving cell configured in the second DL BWP.

3. the set of UL resource occasions in a first uplink BWP of the first DL and UL BWP pair is associated with a spatial relationship configuration using the SSB or the DL reference signal of the serving cell in the second DL BWP; a Physical Random Access Channel (PRACH) Occasion (RO) of the RA procedure; a physical uplink shared channel (PUSCH) occasion for the RA procedure; Random access or configured grant-based SDT occasions; Sounding Reference Signal (SRS) occasions, or a physical uplink control channel (PUCCH) occasion associated with the RA procedure or the SDT procedure; The apparatus of claim 1 , comprising one or more of:

4. The configuration for the first DL and UL BWP pair includes information indicating cell-defined SSB (CD-SSB) or non-cell-defined SSB (NCD-SSB) used for a reference signal for quasi-co-location (QCL) source, spatial relationship establishment, and synchronization of the UE that is in the second DL BWP and performs the RA procedure or the SDT procedure on the first DL and UL BWP pair, or The configuration for the first DL and UL BWP pair includes information indicating a Channel State Information Reference Signal (CSI-RS), a Positioning Reference Signal (PRS), or a Tracking Reference Signal (TRS) that is sent by a serving cell in the second DL BWP and is used for spatial relationship configuration and synchronization of the UE in a Radio Resource Control (RRC) idle, inactive, or connected state that performs the RA procedure or the SDT procedure; or 2. The apparatus of claim 1, wherein the CORESET and the SS set configured in the first DL BWP for the RA procedure or the SDT procedure have a quasi-co-location (QCL) relationship to the SSB or the DL reference signal of the serving cell in the second DL BWP.

5. To perform the time synchronization or the frequency synchronization, the at least one processor: suspending or stopping communication in the first DL BWP or the first UL BWP of the first DL and UL BWP pair during the RA procedure or the SDT procedure; switching from the first DL BWP or the first UL BWP to the second DL BWP to measure the SSB or the DL reference signal of the serving cell in the second DL BWP; switching from the second DL BWP back to the first DL BWP or the first UL BWP following measurement of the SSB or the DL reference signal in the second DL BWP; using the measurements in the second DL BWP for the time synchronization or the frequency synchronization, power control, beam management, timing advance verification, or uplink resource occasion reselection; resuming or restarting communication during the RA procedure or the SDT procedure on the first DL and UL BWP pair; The apparatus of claim 1 , further configured to:

6. the at least one processor: After initiating the RA procedure or the SDT procedure, starting a first timer associated with a BWP switch from the first DL BWP or the first UL BWP to the second DL BWP for measuring the SSB or the DL reference signal, the first timer tracking a gap since the UE's latest measurement of the SSB or the DL reference signal of the serving cell; starting a second timer associated with the RA procedure or the SDT procedure, the second timer being set separately from the first timer, after initiating the RA procedure or the SDT procedure; and the UE switching from the first DL BWP or the first UL BWP to the second DL BWP to measure the SSB or the DL reference signal in response to expiration of the first timer or the second timer or a timing advance verification failure for the SDT procedure; resetting the first timer after completing measurement of the SSB or the DL reference signal in the second DL BWP; The apparatus of claim 5 further configured to:

7. the at least one processor: The apparatus of claim 6 , further configured to transmit, during the RA procedure or the SDT procedure, a value of the first timer in a message in one or more UL resource occasions.

8. the at least one processor is further configured to transmit the value of the first timer in the message based on determining that the first timer and the second timer are running; or To switch from the first DL BWP or the first UL BWP to the second DL BWP, the at least one processor is further configured to switch from the first DL BWP or the first UL BWP to the second DL BWP following transmission of the value of the first timer or based on a BWP retuning schedule received from the serving cell in system information or a dedicated Radio Resource Control (RRC) message; or the at least one processor is further configured to receive signaling from the serving cell before transmitting the message, the signaling enabling reporting of the value of the first timer, the signaling being received in system information, a dedicated radio resource control (RRC) message, a medium access control element (MAC CE), or a downlink control information (DCI); or the at least one processor is further configured to selectively transmit the value of the first timer in the message based on an occurrence of a condition or trigger event that depends at least on UE capability, a type of the RA procedure or the SDT procedure, cell coverage, or a frequency range; or 8. The apparatus of claim 7, wherein the at least one processor is further configured to receive, in response to the value of the first timer reported by the UE, scheduling information for DL ​​reception or UL transmission including a time offset, the time offset provided by the serving cell being equal to or greater than a BWP switching delay and a measurement gap of the UE.

9. the at least one processor:

6. The apparatus of claim 5, further configured to: transmit, in uplink signaling associated with the RA procedure or the SDT procedure, a request for a random access response (RAR) window adjustment based on a BWP switching delay and a measurement gap of the UE in the second DL BWP.

10. To switch from the first DL BWP or the first UL BWP to the second DL BWP, the at least one processor is further configured to switch from the first DL BWP or the first UL BWP to the second DL BWP following transmission of the request or based on a BWP retuning schedule received from the serving cell in system information or a dedicated Radio Resource Control (RRC) message; or The at least one processor is further configured to receive signaling from the UE before transmitting the random access message, the signaling enabling the request for the RAR window adjustment, the signaling being received from the serving cell in system information, a dedicated radio resource control (RRC) message, a medium access control element (MAC CE), or downlink control information (DCI); or 10. The apparatus of claim 9, wherein the at least one processor is further configured to selectively transmit the request based on an occurrence of a condition or trigger event that depends on at least one of UE capability, a type of the RA procedure or the SDT procedure, cell coverage, or a frequency range.

11. the at least one processor:

2. The apparatus of claim 1, further configured to transmit a request for on-demand transmission of a non-cell-defined SSB (NCD-SSB), a tracking reference signal (TRS), or other DL reference signal in the first DL BWP in an uplink signal associated with the RA procedure or the SDT procedure.

12. the at least one processor: receiving signaling from the serving cell prior to sending the request that enables the request, wherein the signaling is received in system information, a dedicated radio resource control (RRC) message, a medium access control element (MAC CE), or a downlink control information (DCI); or Sending said request based on the occurrence of a condition or trigger event; or receiving an acknowledgement for the on-demand transmission of the NCD-SSB, the TRS, or the other DL reference signal, wherein performing the time or frequency synchronization includes measuring the NCD-SSB, the TRS, or the other DL reference signal in the first DL BWP after receiving the acknowledgement; or receiving a negative response from the UE rejecting the request, and switching from the first DL BWP or the first UL BWP to the second DL BWP after receiving the negative response to measure the SSB or the reference signal in the second DL BWP; The apparatus of claim 11 , further configured to:

13. 1. An apparatus for wireless communication at a base station, comprising: Memory and at least one processor coupled to the memory; the at least one processor: transmit to a user equipment (UE) in a radio resource control (RRC) idle, inactive, or connected state a configuration for a random access procedure or a small data transmission (SDT) procedure in a first downlink (DL) and uplink (UL) bandwidth portion (BWP) pair, the configuration including information indicating at least one of a control resource set (CORESET) for the random access procedure or the SDT procedure, a search space (SS) set, a set of uplink resource occasions, and a synchronization signal block (SSB) or DL ​​reference signal in a second DL BWP, wherein a first DL BWP of the first DL and UL BWP pair does not include the SSB, and a quasi-co-location (QCL) source, spatial relationship configuration, and synchronization for the UE during the random access procedure or the SDT procedure are based on the SSB or the DL reference signal transmitted by a serving cell in the second DL BWP; receiving from the UE, in at least one of a random access message or an SDT message, in a first UL BWP of the first DL and UL BWP pair, an early indication of one or more of a device type, a first request for a first on-demand transmission of the SSB or the DL reference signal, or other assistance information for adaptive scheduling; The apparatus is configured to:

14. 1. A method of wireless communication in a user equipment (UE), comprising: receiving a configuration for a first downlink (DL) and uplink (UL) bandwidth portion (BWP) pair, the configuration including information indicating at least one of a control resource set (CORESET), a search space (SS) set, and a set of UL resource occasions for a random access (RA) procedure or a small data transmission (SDT) procedure; initiating at least one of the RA procedure or the SDT procedure on the first DL and UL BWP pair; performing time synchronization or frequency synchronization during the RA procedure or the SDT procedure using a synchronization signal block (SSB) of a serving cell configured in a second DL BWP or a DL reference signal of the serving cell configured in the second DL BWP or a first DL BWP of the first DL and UL BWP pair; A method comprising:

15. 1. A method of wireless communication in a base station, comprising: transmitting, to a user equipment (UE) in a radio resource control (RRC) idle, inactive, or connected state, configuration for a random access procedure or a small data transmission (SDT) procedure in a first downlink (DL) and uplink (UL) bandwidth portion (BWP) pair, the configuration including information indicating at least one of a control resource set (CORESET) for the random access procedure or the SDT procedure, a search space (SS) set, a set of uplink resource occasions, and a synchronization signal block (SSB) or DL ​​reference signal in a second DL BWP, wherein a first DL BWP of the first DL and UL BWP pair does not include the SSB, and a quasi-co-location (QCL) source, spatial relationship configuration, and synchronization for the UE during the random access procedure or the SDT procedure are based on the SSB or the DL reference signal transmitted by a serving cell in the second DL BWP; receiving, in a first UL BWP of the first DL and UL BWP pair, in at least one of a random access message or an SDT message from the UE, an early indication of one or more of a device type, a first request for a first on-demand transmission of the SSB or the DL reference signal, or other assistance information for adaptive scheduling; A method comprising:

Images