Method and apparatus for synchronization for rach and sdt in ssb-less dl bwp

Abstract

Methods, apparatus, and computer-readable media for RACH and SDT synchronization are provided. Example methods may include: receiving a configuration for a first DL and UL BWP pair, the configuration including information indicating at least one of a CORESET, an SS set, and a UL resource timing set for an RA procedure or an SDT procedure. Example methods may also include: initiating at least one of an RA procedure or an SDT procedure in the first DL and UL BWP pair. Example methods may also include: performing time or frequency synchronization during an RA procedure or an SDT procedure using an SSB of a service cell configured in a second DL BWP or a DL reference signal of a service cell configured in a second DL BWP.

Description

[Technical Field]

[0001] This patent application claims the benefit and priority of PCT application filed on December 3, 2021, entitled "SYNCHRONIZATION FOR RACH AND SDT IN SSB-LESS DL BWP" with serial number PCT / CN2021 / 135467, and PCT application filed on December 2, 2022, entitled "SYNCHRONIZATION FOR RACH AND SDT IN SSB-LESS DL BWP" with serial number PCT / CN2022 / 136114, both of which are expressly incorporated herein by reference in their entirety.

[0002] In general, the subject matter of this case concerns communication systems, and more specifically, wireless communication systems with downlink bandwidth portions (BWP) that do not have a synchronization signal block (SSB) for random access (RA) procedures or small data transfer (SDT) procedures. [Previous Technology]

[0003] Wireless communication systems are widely deployed to provide various telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiplexing access technologies that enable communication with multiple users by sharing available system resources. Examples of such multiplexing access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0004] These multiplexing access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, country, region, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Mobile Broadband Evolution (CMBE) released by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with 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 forms of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements to 5G NR technology. These improvements can also be applied to other multiplexing access technologies and telecommunications standards that adopt these technologies. [Summary of the Invention]

[0005] The following provides a brief overview of one or more states in order to offer a basic understanding of such states. This overview is not an exhaustive summary of all anticipated states, nor is it intended to identify key or important elements of all states, nor to describe the scope of any or all states. Its sole purpose is to present some concepts of one or more states in a simple form as a prelude to the more detailed descriptions that follow.

[0006] In one embodiment of this invention, methods, computer-readable media, and apparatus are provided for a user equipment (UE). 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: receive 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 UL resource timing set for a random access (RA) procedure or a small data transfer (SDT) procedure. The memory and at least one processor coupled to the memory may also be 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 also be configured to: perform time or frequency synchronization during the RA procedure or SDT procedure using a synchronization signal block (SSB) of a service cell configured in a second DL BWP or a DL reference signal of a service cell configured in the second DL BWP (e.g., or in the first DL BWP of the first DL and UL BWP pair).

[0007] In another embodiment of the present invention, methods, computer-readable media, and apparatus are provided at a base station (e.g., a network node). The apparatus may include 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 transmit to a UE in a Radio Resource Control (RRC) idle, inactive, or connected state 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 the following: a CORESET for the random access procedure or SDT procedure, a set of SSs (e.g., common SSs (CSS) or a UE-specific set of SSs (USS), an uplink resource timing set, 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 the quasi-co-location (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. The memory and at least one processor coupled to the memory can also be configured to: in the first UL BWP of the first DL and UL BWP pair, in at least one of the random access messages or SDT messages from the UE, receive an early indication from the UE for one or more of the following: device type, a first request for a first on-demand transmission of the SSB or DL ​​reference signal, or other auxiliary information for self-adjusting scheduling.

[0008] To achieve the foregoing and related purposes, one or more forms include the features fully described below and specifically pointed out in the claims. The following description and figures illustrate certain illustrative features of one or more forms in detail. However, these features indicate only some of the various methods by which the principles of the various forms may be adopted, and this specification is intended to include all such forms and their equivalents.

Implementation Method

[0034] The following description, in conjunction with the accompanying drawings, illustrates various configurations for specific implementations, and does not represent the only configurations that can implement the concepts described herein. For the purpose of providing a thorough understanding of the various concepts, the specific implementations include particular details. However, these concepts can be practiced without these particular details. In some instances, to avoid ambiguity regarding such concepts, well-known structures and components are shown in block diagram form.

[0035] Several forms of telecommunications systems are provided with reference to various devices and methods. These devices and methods are described in detail below and shown in the accompanying drawings in the specific implementations of various blocks, components, circuits, programs, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the entire system.

[0036] For example, an element, or any part thereof, or any combination thereof, can 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, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuitry, and other suitable hardware configured to perform the various functions described herein. One or more processors in the processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as instructions, instruction sets, code, code fragments, code, program, subprogram, software component, application, software application, software suite, routine, subroutine, object, executable file, executable thread, program, function, or any combination thereof.

[0037] Therefore, in one or more instance types, implementations, and / or use cases, the described functionality can be implemented using hardware, software, or any combination thereof. When implemented using software, the functionality can be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media includes computer storage media. Storage media can be any available medium that a computer can access. By way of example, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electronically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these 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.

[0038] Although the various forms, implementations, and / or use cases described herein are illustrated by way of examples, additional or different forms, implementations, and / or use cases may be implemented in many different arrangements and scenarios. The forms, implementations, and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, forms, implementations, and / or use cases may be implemented via integrated chip implementations and other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial devices, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a particular use case or application, a wide variety of applicability to the described examples may occur. The forms, implementations, and / or use cases may vary from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein. In some practical settings, devices incorporating the described states and features may also include additional components and features for implementing and practicing the claimed protected and described states. For example, the transmission and reception of wireless signals must include multiple components (e.g., hardware components, including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / converters, etc.) for analog and digital purposes. The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, clustered or fragmented components, end-user devices, etc., with different sizes, shapes, and configurations.

[0039] Communication systems (such as 5G NR systems) can be deployed in various ways using a variety of components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements, or network equipment, such as base stations (BS) or one or more units (or one or more components) performing base station functions, can be implemented using aggregated or decomposed architectures. For example, a BS (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit / receive point (TRP), or a cell, etc.) can be implemented as an aggregated base station (also known as a standalone BS or a single BS) or a decomposed base station.

[0040] Aggregated base stations can be configured to utilize radio protocol stacks that are physically or logically integrated within a single RAN node. Decomposed base stations can be configured to utilize protocol stacks that are physically or logically distributed between two or more units (such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some configurations, a CU can be implemented within a RAN node, and one or more DUs can be co-located with a CU, or alternatively, can be geographically or virtually distributed across one or more other RAN nodes. A DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0041] Base station operation or network design can consider the aggregation characteristics of base station functions. For example, a decomposed network can be utilized in Integrated Access Backload (IAB) networks, Open Radio Access Networks (O-RAN (such as network configurations sponsored by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). Decomposition can include distributing functions across two or more units in different physical locations, as well as virtually distributing functions to at least one unit, which allows for flexibility in network design. Individual units in a decomposed base station or decomposed RAN architecture can be configured to communicate with at least one other unit via wired or wireless means.

[0042] Figure 1 is a diagram illustrating 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 a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include macrocells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macrocells include base stations. Small cells include femtocells, picocells, and microcells.

[0043] A base station 102 configured for 4G LTE (collectively referred to as Evolutionary Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). A base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with core network 190 via a second backhaul link 184. Among other functions, base station 102 may also perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, motion control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of Non-Access Layer (NAS) messages, NAS node selection, synchronization, RAN sharing, Multimedia Broadcast Multicast Service (MBMS), user and device tracking, RAN Information Management (RIM), paging, location, and transmission of alarm messages. Base stations 102 can communicate with each other directly or indirectly (e.g., via EPC 160 or 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 can be wired or wireless.

[0044] Base station 102 can communicate wirelessly with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network including small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a Home Evolutionary Node B (eNB) (HeNB), which can provide services to a restricted group referred to as a Closed Subscriber Group (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also referred to as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also referred to as forward link) transmission from base station 102 to UE 104. Communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be via one or more carriers. Base station 102 / UE 104 may use a bandwidth of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) for each carrier allocated in a total of up to Y x MHz (x component carriers) for transmission in each direction. Carriers may or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). Component carriers may include primary component carriers and one or more auxiliary component carriers. The primary component carrier may be referred to as the main cell (PCell), and the auxiliary component carriers may be referred to as auxiliary cells (SCells).

[0045] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL WWAN spectrum. D2D communication link 158 can use one or more sideline channels, such as physical sideline broadcast channel (PSBCH), physical sideline discovery channel (PSDCH), physical sideline shared channel (PSSCH), and physical sideline control channel (PSCCH). D2D communication can be performed via various wireless D2D communication systems (e.g., WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR).

[0046] The wireless communication system may also include a Wi-Fi access point (AP) 150, which communicates with a Wi-Fi station (STA) 152 via a communication link 154, for example, in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform an idle channel assessment (CCA) before communicating to determine whether the channel is available.

[0047] The small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, the small cell 102' can employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) used by the Wi-Fi AP 150. The small cell 102' employing NR in unlicensed spectrum can improve access network coverage and / or increase access network capacity.

[0048] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency range names FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, in various documents and articles, FR1 is generally (interchangeably) referred to as the "below 6 GHz" band. Similar naming issues sometimes arise regarding FR2; although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) designated as the "millimeter wave" band by the International Telecommunication Union (ITU), FR2 is generally (interchangeably) referred to as the "millimeter wave" band in documents and articles.

[0049] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have designated the operating frequency bands of these mid-band frequencies as the frequency range name FR3 (7.125 GHz – 24.25 GHz). Frequency bands falling within FR3 can inherit the characteristics of FR1 and / or FR2, and thus can effectively extend the characteristics of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation above 52.6 GHz. For example, three higher operating frequency bands have been designated as the frequency range names FR2-2 (52.6 GHz – 71 GHz), FR4 (71 GHz – 114.25 GHz), and FR5 (114.25 MHz – 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0050] In view of the above, unless otherwise explicitly stated, the terms "below 6 GHz" etc. (if used herein) can broadly refer to frequencies less than 6 GHz, frequencies within FR1, or frequencies that may include intermediate frequency band frequencies. Furthermore, unless otherwise explicitly stated, the terms "millimeter wave" etc. (if used herein) can broadly refer to frequencies that may include intermediate frequency band frequencies, frequencies within FR2, FR4, FR2-2 and / or FR5, or frequencies within the EHF band.

[0051] Base station 102 (whether a small cell 102' or a large cell (e.g., a macro base station)) may include and / or may be referred to as an eNB, gNodeB (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in conventional sub-6 GHz spectrum, millimeter wave frequencies, and / or near-millimeter wave frequencies to communicate with UE 104. When gNB 180 operates in millimeter wave or near-millimeter wave frequencies, gNB 180 may be referred to as a millimeter wave base station. Millimeter wave base station 180 may utilize beamforming 182 with UE 104 to compensate for path loss and short range. Both base station 180 and UE 104 may include multiple antennas (e.g., antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming.

[0052] Base station 180 may transmit beamforming signals to UE 104 in one or more transmit directions 182''. UE 104 may receive beamforming signals from base station 180 in one or more receive directions 182''. UE 104 may also transmit beamforming signals to base station 180 in one or more transmit directions. Base station 180 may receive beamforming signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the optimal receive and transmit directions for each of base station 180 / UE 104. The transmit and receive directions for base station 180 may be the same or different. The transmit and receive directions for UE 104 may be the same or different.

[0053] EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a service 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. MME 162 can communicate with the Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signal transfer between UE 104 and EPC 160. Typically, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted via service gateway 166, which is itself connected to PDN gateway 172. PDN gateway 172 provides UE IP address allocation and other functions. PDN gateway 172 and BM-SC 170 are connected to IP service 176. IP service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. BM-SC 170 can provide functions for MBMS user service provisioning and delivery. BM-SC 170 can act as an entry point for MBMS transmissions to content providers, can be used to authorize and initiate MBMS bearer services in a Public Terrestrial Mobile Network (PLMN), and can be used to schedule MBMS transmissions. MBMS gateway 168 can be used to distribute MBMS transmissions to base stations 102 belonging to a Broadcast Specific Service Single Frequency Network (MBSFN) area, and can be responsible for communication period management (start / stop) and collection of billing information related to eMBMS.

[0054] The core network 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Term Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that handles signal transmission between UE 104 and the core network 190. Typically, AMF 192 provides QoS flow and term management. All user Internet Protocol (IP) packets are transmitted via UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP Service 197. IP Service 197 may include the Internet, intranet, IP Multimedia Subsystem (IMS), Packet Switched (PS) Streaming (PSS) service, and / or other IP services.

[0055] A base station may include and / or be referred to as a gNB, Node B, eNB, access point, base station transceiver, radio base station, radio transceiver, transceiver function, Basic Services Set (BSS), Extended Services Set (ESS), Transmitter Receiver Point (TRP), or some other suitable term. Base station 102 provides UE 104 with access to EPC 160 or core network 190. Examples of UE 104 include cellular phones, smartphones, conversation initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radio units, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, medical devices, implants, sensors / actuators, displays, or any other similar functional devices. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, user station, mobile unit, user unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile user station, access terminal, mobile terminal, radio terminal, remote terminal, handheld device, user agent, mobile service client, client, or some other suitable term. In some scenarios, the term UE may also be used for one or more accompanying devices, such as in a device cluster deployment. One or more of these devices may jointly access the network and / or individually access the network.

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

[0057] In some configurations, base station 180 may include synchronization component 199. In some configurations, synchronization component 199 may be configured to send 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. This configuration includes information indicating at least one of the following: a CORESET, SS set, uplink resource timing set, and an SSB or DL ​​reference signal in a second DL BWP for the random access procedure or SDT procedure, wherein 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 sent by the serving cell in the second DL BWP. In some configurations, the synchronization component 199 may also be configured to receive, in the first UL BWP of the first DL and UL BWP pair, an early indication from the UE for one or more of the following in at least one of the random access messages or SDT messages from the UE: device type, a first request for a first on-demand transmission of the SSB or DL ​​reference signal, or other auxiliary information for self-adjusting scheduling.

[0058] Although the following description may focus on 5G NR, the concepts described herein can be applied to other similar fields such as LTE, LTE-A, CDMA, GSM and other wireless technologies.

[0059] As described herein, a node (which may be referred to as a node, network node, network entity, or wireless node) may include, is, or is included (is a part of) the following devices: base station (e.g., any base station described herein), UE (e.g., any UE described herein), network controller, apparatus, device, computing system, integrated access and return (IAB) node, distributed unit (DU), central unit (CU), remote / radio unit (RU) (which may also be referred to as remote radio unit (RRU)), and / or another processing entity configured to perform any of the technologies 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 embodiment 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 variant of this instance, the first network node can be a UE, the second network node can be a base station, and the third network node can be a base station. In other variants of this instance, the first, second, and third network nodes can be different from these instances. Similarly, references to UE, base station, device, equipment, computing system, etc., can include disclosures that the UE, base station, device, equipment, computing system, etc., are network nodes. For example, disclosures that the UE is configured to receive information from a base station also disclose that the first network node is configured to receive information from a second network node. Consistent with the content of this application, once a specific instance is extended according to the content of this application (e.g., the UE is configured to receive information from a base station, and the first network node is also disclosed to be configured to receive information from a second network node), the wider instance of the narrower instance can be interpreted in a broadly open manner, in contrast. In the above example where the UE is configured to receive information from the base station, it is also disclosed that the first network node is configured to receive information from the second network node. The first network node may represent the first UE, the first base station, the first device, the first equipment, the first computing system, the first set of one or more components, the first processing entity, etc., configured to receive information; and the second network node may represent the second UE, the second base station, the second device, the second equipment, the second computing system, the second set of one or more components, the second processing entity, etc.

[0060] As described herein, different terms may be used in various contexts to describe the transmission of information (e.g., any information, signal, etc.). The disclosure of one communication term includes the disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this instance and consistent with the present invention, the disclosure of a first network node being configured to send information to a second network node includes the disclosure of a first network node being configured to provide, send, output, transmit, or transfer information to a second network node. Similarly, in this instance and consistent with the present invention, the disclosure of a first network node being configured to send information to a second network node includes the disclosure of a second network node being configured to receive, acquire, or decode information provided, sent, output, transmitted, or transferred by the first network node.

[0061] Figure 2A is Figure 200, showing an example of a first sub-frame within a 5G NR frame structure. Figure 2B is Figure 230, showing an example of a DL channel within a 5G NR sub-frame. Figure 2C is Figure 250, showing an example of a second sub-frame within a 5G NR frame structure. Figure 2D is Figure 280, showing an example of a UL channel within a 5G NR sub-frame. The 5G NR frame structure can be Frequency Division Duplex (FDD) or Time Division Duplex (TDD). In FDD, for a specific set of subcarriers (carrier system bandwidth), sub-frames within the subcarrier set are dedicated to either DL or UL. In TDD, for a specific set of subcarriers (carrier system bandwidth), sub-frames within the subcarrier set are dedicated to both DL and UL. In the examples provided by Figures 2A and 2C, it is assumed that the 5G NR frame structure is TDD, where subframe 4 is configured with slot format 28 (primarily DL), where D is DL, U is UL, and F is used flexibly between DL / UL, and subframe 3 is configured with slot format 1 (all UL). Although subframes 3 and 4 are shown with slot formats 1 and 28 respectively, 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. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured with a slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signal delivery). Note that the following description also applies to TDD 5G NR frame structures.

[0062] Figures 2A-2D illustrate the frame structure, and the various forms of the present invention can be applied to other wireless communication technologies, which may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized sub-frames (1 ms). Each sub-frame may include one or more time slots. Sub-frames may also include micro-time slots, which may include 7, 4, or 2 symbols. Depending on whether the Cyclic Prefix (CP) is normal or extended, each time slot may include 14 or 12 symbols. For normal CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. The symbols on the DL can be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL can be CP-OFDM symbols (for high-volume scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on CP and the digital scheme (numerology). The digital scheme defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration (which is equal to 1 / SCS). µ SCS Cyclic prefixes 0 15 ordinary 1 30 ordinary 2 60 Normal, Extended 3 120 ordinary 4 240 ordinary Table 1

[0063] For a standard CP (14 symbols / slot), different digital schemes µ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For an extended CP, digital scheme 2 allows 4 slots per subframe. Therefore, for both the standard CP and digital scheme µ, there are 14 symbols / slots and 2 µ slots / subframe. The subcarrier spacing can be equal to kHz, where µ is from digital scheme 0 to 4. Thus, digital scheme µ=0 has a subcarrier spacing of 15 kHz, and digital scheme µ=4 has a subcarrier spacing of 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A-2D provide examples of a standard CP with 14 symbols per slot and digital scheme µ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a set, there can be one or more different bandwidth portions (BWPs) of frequency division multiplexing (see Figure 2B). Each BWP can have a specific digital scheme and CP (normal or extended).

[0064] A resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) containing 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0065] 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) (indicated as R for a 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 (BRRS), and phase tracking RS (PT-RS).

[0066] Figure 2B illustrates examples of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries the DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE groups (REGs), each REG comprising 12 consecutive REs in the OFDM symbol of the RB. The PDCCH within a BWP can be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during PDCCH monitoring timing on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs can be located at higher and / or lower frequencies in the channel bandwidth. The primary synchronization signal (PSS) can be within symbol 2 of a specific subframe of the frame. The UE 104 uses the PSS to determine subframe / symbol timing and physical layer identification. The Auxiliary Synchronization Signal (SSS) can be located within symbol 4 of a specific subframe of the frame. The UE uses the SSS to determine the Physical Layer Cell Identifier Group Number and the radio frame timing. Based on the Physical Layer Identifier and the Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The Physical Broadcast Channel (PBCH) carrying the Main Information Block (MIB) can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known 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 information, broadcast system information not transmitted by the PBCH (such as the System Information Block (SIB)), and paging messages.

[0067] As shown in Figure 2C, some REs in the REs carry DM-RS (indicated as R for a particular configuration, but other DMRS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first one or two symbols before the PUSCH. The PUCCH DM-RS can 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 can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the comb structures. The base station can use the SRS for channel quality estimation to implement frequency-related scheduling on the UL.

[0068] Figure 2D shows examples of various UL channels within a sub-frame of a frame. The PUCCH can be positioned as indicated 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) feedback (i.e., one or more HARQ ACK bits indicating one or more ACK / negative ACK (NACK)). The PUCCH carries data and can also be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0069] Figure 3 is a block diagram of communication between base station 310 and UE 350 in the access network. In the DL, Internet Protocol (IP) packets are provided to controller / processor 375. Controller / processor 375 implements layer 3 and layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, and layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides: RRC layer functions associated with broadcasting system information (e.g., MIB, SIB), 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 reports; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with transmission of upper-layer packet data units (PDUs), error correction via ARQ, connection, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs to transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority processing, and logical channel priority allocation.

[0070] The transmit (TX) processor 316 and the receive (RX) processor 370 implement Layer 1 functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection of the transmission channel, forward error correction (FEC) encoding / decoding of the transmission channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 processes the mapping to the signal cluster based on various modulation schemes (e.g., Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), M-Phase Phase Shift Keying (M-PSK), M-Order Quadrature Amplitude Modulation (M-QAM)). The encoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot signal) in the time and / or frequency domains, and subsequently combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM streams are spatially precoded to generate multiple spatial streams. Channel estimates from channel estimator 374 can be used to determine coding and modulation schemes and for spatial processing. The channel estimates can be derived based on a reference signal and / or channel status feedback transmitted by UE 350. Each spatial stream can then be provided to different antennas 320 via a separate transmitter 318Tx. Each transmitter 318Tx can modulate a radio frequency (RF) carrier using the corresponding spatial stream for transmission.

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

[0072] The controller / processor 359 can be associated with memory 360 storing code and data. Memory 360 may be referred to as computer-readable media. In UL, the controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transmission and logic channels to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0073] Similar to the functions described in conjunction with DL transmissions performed by base station 310, controller / processor 359 provides: RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reports; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with transmission of upper-layer PDUs, error correction via ARQ, connection, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transmission channels, multiplexing of MAC SDUs to TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority processing, and logical channel priority allocation.

[0074] The channel estimate derived by the channel estimator 358 from the reference signal or feedback transmitted by the base station 310 can be used by the TX processor 368 to select an appropriate coding and modulation scheme and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via corresponding transmitters 354Tx. Each transmitter 354Tx can use the corresponding spatial stream to modulate the RF carrier for transmission.

[0075] The UL transmission is processed at the base station 310 in a manner similar to that described in conjunction with the receiver function at the UE 350. Each receiver 318Rx receives the signal via its corresponding antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides the information to the RX processor 370.

[0076] The controller / processor 375 can be associated with memory 376 storing code and data. Memory 376 may be referred to as computer-readable media. In UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transmission and logic channels to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0077] At least one of the TX processor 368, RX processor 356 and controller / processor 359 can be configured to perform a state related to the synchronization component 198 of FIG1.

[0078] At least one of the TX processor 316, RX processor 370 and controller / processor 375 can be configured to perform a state related to the synchronization component 199 of FIG1.

[0079] In addition to general devices, wireless communication can also be supported on devices with reduced capabilities (also known as degraded devices). Examples of general devices include advanced smartphones, V2X devices, URLLC devices, eMBB devices, etc. Other examples of degraded devices include wearable devices (e.g., smartwatches, 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, NR communication systems can support both general devices and degraded devices. Degraded devices can be referred to as NR lightweight devices, low-level devices, lower-level devices, etc. Degraded UEs can communicate based on various types of wireless communication. For example, smart wearable devices can transmit or receive communication based on low-power wide-area (LPWA) / mMTC, relaxed IoT devices can transmit or receive communication based on URLLC, sensors / cameras can transmit or receive communication based on eMBB, etc.

[0080] In some instances, a reduced-capability UE may have an uplink transmit power at least 10 dB lower than a typical UE. As another example, a reduced-capability UE may have reduced transmit or receive bandwidth compared to other UEs. For instance, compared to other UEs that may have bandwidths up to 100 MHz, a reduced-capability UE may have an operating bandwidth between 5 MHz and 20 MHz for transmitting and receiving. For example, in FR1, a reduced-capability UE may have a maximum bandwidth of 20 MHz during and after initial access. In FR2, a reduced-capability UE may have a maximum bandwidth of 100 MHz during and after initial access. As another example, a reduced-capability UE may have a reduced number of receive antennas compared to other UEs. For frequency bands where the UE is equipped with at least two antennas, the minimum number of receive branches for a reduced-capability UE may be one, and support for two receive branches may also be included. For a typical UE equipped with four receive antenna ports, a minimum of one receive branch can be supported. For example, a reduced-capability UE can support an additional two receive branches. In some configurations, the base station can know the number of receive branches at the UE. Compared to a typical UE that may have multiple antennas, a reduced-capability UE may only have a single receive antenna and may experience a lower equivalent receive signal-to-noise ratio (SNR). A reduced-capability UE with one receive branch can support one downlink MIMO layer. A reduced-capability UE with two receive branches can support two downlink MIMO layers. For a FR1 reduced-capability UE, a maximum modulation order of 256 QAM can be supported in the downlink. In some configurations, a reduced-capability UE can support half-duplex frequency division duplex (HD-FDD) type A duplex operation. A reduced-capability UE can 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 compared to other UEs.

[0081] For example, wearable devices may have downlink re-data rates, such as a reference rate of 5-50 Mbps on the downlink compared to an uplink rate of 2-5 Mbps. Latency and reliability may be based on eMBB. Battery life may be intended to last for several days (e.g., 1-2 weeks in one instance). Industrial sensors may have, for example, an uplink re-reference rate of approximately 2 Mbps, latency of less than 100 ms (with even lower latency for safety-related sensors (e.g., 5-10 ms)), 99.9% reliability, and may have a battery life intended to last for one year or more. Video surveillance equipment may have uplink retransmissions, for example, a reference rate of 2-4 Mbps for some transmissions and a reference rate of 7.5-25 Mbps for higher priority transmissions. Video surveillance equipment may have latency of less than 500 ms and 99%-99.9% reliability.

[0082] Expanding and deploying communications in a more efficient and cost-effective manner can be helpful. For example, for devices with reduced capabilities, peak throughput, latency, and / or reliability requirements can be relaxed or reduced. In some instances, priorities can be placed on reducing power consumption, complexity, production costs, and / or reducing system management burden. For example, industrial wireless sensors can have acceptable latency of up to approximately 100 ms. In some security-related applications, latency of up to 10 ms or up to 5 ms for industrial wireless sensors may be acceptable. Data rates can be lower and can include more uplink throughput than downlink throughput. As another example, video surveillance equipment can have acceptable latency of up to approximately 500 ms.

[0083] The carrier bandwidth can span a continuous set of PRBs, for example, common resource blocks from a given carrier for a given digital scheme. A base station can be configured with one or more bandwidth portions (BWPs) having a bandwidth span smaller than the carrier bandwidth. One or more of these BWPs can be configured for downlink communication and can be referred to as downlink (DL) BWPs. Figure 4 illustrates a resource map 400 showing multiple BWPs (e.g., BWP 1, BWP 2, and BWP 3) configured within a frequency span of the carrier bandwidth. At a time, one DL BWP can be active, and it may not be expected that the UE will receive PDSCH, PDCCH, CSI-RS, or TRS outside of the active BWP without a measurement gap or BWP handover gap. Each DL BWP can include at least one control resource set (CORESET). In Figure 4, a BWP can be a DL BWP and is shown having a CORESET within the BWP. In other instances, a BWP can be a UL BWP and may not include a CORESET configuration. One or more of these BWPs can be configured for uplink communication and can be referred to as uplink (UL) BWPs. One UL BWP can be active for the UE at a time, and the UE may not send PUSCH or PUCCH outside of the active BWP. The use of BWPs can reduce the bandwidth used by the UE for monitoring and / or transmission, which can help the UE save battery power.

[0084] A CORESET corresponds to a set of physical resources in time and frequency that the 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. For example, a CORESET may include multiple RBs in the frequency domain and 1, 2, or 3 consecutive symbols in the time domain. A resource element (RE) is a subcarrier element that indicates the frequency of a single symbol in time. Control channel elements (CCEs) include resource element groups (REGs) (e.g., 6 REGs), where a REG may correspond to one RB during an OFDM symbol (e.g., 12 REs). REGs within a CORESET may be numbered in ascending order in a time-priority manner, starting from 0 for the first OFDM symbol in the control resource set and the lowest-numbered resource block. A UE may be configured with multiple CORESETs, each associated with a CCE-to-REG mapping. A search space may include a set of CCEs (e.g., with different aggregation levels). For example, the search space may indicate the number of candidates to be decoded, in which the UE performs decoding. CORESET can include multiple search space sets.

[0085] In some configurations, UEs with different capability levels (such as a reduced-capability UE and a non-reduced-capability (or normal) UE) can share an initial DL BWP (e.g., BWP 1) and CORESET#0 (e.g., 402) for initial access. For example, the UE can monitor the resources of CORESET#0 to receive system information that enables the UE to perform initial access. Cell-defined SSBs (CD-SSBs) (e.g., 408) can be transmitted within the bandwidth supported by the reduced-capability UE. For example, BWP 1 can be the initial DL BWP, which can be configured for both reduced-capability and normal UEs. The UE can be configured with different BWPs as the active DL BWP, for example, after performing initial access. For example, in Figure 4, BWP 2 can be configured for the lower-capability UE, and the normal UE can be configured to have an active DL BWP 3. Figure 4 shows that BWP 1 may include SSB 408.

[0086] A cell providing access to a degraded UE can be configured with a separate initial BWP for the degraded UE. Figure 5 illustrates an example diagram 500 showing an initial downlink BWP 554, which can be configured within the carrier bandwidth 552 of the serving cell for the degraded UE to receive cell definition (CD) SSBs (CD-SSB), SIs, paging information, etc. In some cases, the initial downlink BWP 554 can be configured with resources for CD-SSB 555, CORESET#0 556, and another CORESET, as well as one or more SSs 558 for the UE to receive SIB1, other system information (OSI), or paging. A degraded UE in idle or inactive mode can reside on the initial downlink BWP 554, for example, reside on the serving cell's CORESET#0 556 to receive CD-SSBs, SIs, and paging. A degraded UE in idle or inactive mode can switch to a separate BWP to perform random access procedures, small data transfer (SDT) procedures, or initiate a transfer to connected mode. The UE can receive configurations for a BWP pair, such as a first BWP pair including a first downlink BWP 562 and a first uplink BWP 564 for random access or SDT procedures. In some configurations, the first downlink BWP 562 and the first uplink BWP 564 can be an initial DL BWP and an initial UL BWP. In some configurations, the term "first BWP pair" can refer to "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 initial transmissions (e.g., initial access) by the degraded UE. For example, the first uplink BWP 564 may include PUCCH resources and may include a physical random access channel (RACH) timing (RO) 566. The RAN may assume that a UE with reduced capabilities in an idle or inactive mode that performs random access procedures in a separate, such as the first BWP (e.g., sending random access messages in the first uplink BWP 564 and / or monitoring downlink responses in the first downlink BWP 562) does not monitor paging in CORESET0 556.

[0087] In some configurations, a single, for example, first BWP (e.g., 562) for a UE with reduced capabilities may include a CD-SSB and a specific CORESET (such as CORESET 0). In other configurations, a single, for example, first BWP (e.g., 562) for a UE with reduced capabilities may not include a CD-SSB (e.g., it may be configured to not have a CD-SSB, exclude a CD-SSB, etc., which may be referred to as an SSB-less BWP), and may not have a specific CORESET (such as resources for CORESET#0), or may not have a CORESET for receiving SIB1, OSI, or paging. Figure 5 illustrates a single, for example, first DL BWP 562 for performing random access procedures without a CD-SSB or CORESET#0.

[0088] In some configurations of FR1, a single, for example, first DL BWP (e.g., 562) that does not include CD-SSB and CORESET#0 (e.g., does not include the entire CORESET#0) can be configured to perform random access procedures instead of being used for paging in idle or inactive modes. A single, for example, first DL BWP (e.g., 562) may not contain SSB, CORESET#0, or SIB resources. For example, the network may assume that a degraded UE performing random access procedures in a single, for example, first downlink BWP (e.g., 562) is not monitoring paging in a BWP (e.g., 554) containing CORESET#0 556. If a BWP is configured for paging, a degraded UE may expect the BWP to contain a non-cell-defined SSB (NCD-SSB), but may not expect the BWP to include CORESET#0 / SIB. For an active DL BWP configured for a UE in connected mode using RRC configuration, and if the active DL BWP does not include the NCD-SSB or the entire CORESET#0, a de-capable UE may expect the active DL BWP to include the NCD-SSB, for example, but excluding CORESET#0 / SIB. In some cases, a de-capable UE may indicate that it does not require the NCD-SSB capability. For example, a de-capable UE may optionally support reference signal-based (e.g., CSI-RS) related operations for radio communication and may report this capability to the network.

[0089] If the network configures a separate RRC-configured DL BWP for a degraded UE to include the entire CORESET#0, the degraded UE can expect the separate BWP to include the CD-SSB. The network can choose to configure the CORESET#0 or SIB1 configured by the SSB or MIB within the corresponding DL BWP. When the initial DL BWP of the separate SIB configuration for the degraded UE includes the entire CORESET#0, the degraded UE can use the bandwidth and location of CORESET#0 for downlink reception during initial access. The NCD-SSB period can be different from the CD-SSB period. In some cases, the NCD-SSB period can be no less than the CD-SSB period.

[0090] In some configurations of FR2, a single, for example, first DL BWP (e.g., 562), excluding the CD-SSB or the entire CORESET#0, can be configured to perform random access procedures and not to paging in idle or inactive modes. A single, for example, first DL BWP (e.g., 562) may not contain SSB, CORESET#0, or SIB resources. For example, the network may assume that a degraded UE performing random access procedures in a single downlink BWP (e.g., 562) does not monitor paging in a BWP (e.g., 554) containing CORESET#0 556. If a single, for example, first DL BWP is configured for paging, a degraded UE may expect the single initial BWP to contain the NCD-SSB for the serving cell, but not the CORESET#0 or SIB resources.

[0091] For an active DL BWP configured for an RRC configuration of a UE in connected mode, and if the active DL BWP does not include a CD-SSB or the entire CORESET#0, a UE with reduced capabilities may expect the active DL BWP to include an NCD-SSB for the serving cell, but excluding CORESET#0 / SIB. In some cases, a UE with reduced capabilities may indicate that it does not require the capability of an NCD-SSB. For example, a UE with reduced capabilities may optionally support related operations for radio communication based on reference signals (such as CSI-RS) and may report this capability to the network.

[0092] For SSB and CORESET#0 multiplexing mode 1, if the individual initial DL BWP is configured via RRC to include the entire CORESET#0, then the degraded UE can expect the individual initial DL BWP to include the CD-SSB. The network can choose to configure the CORESET#0 or SIB1 configured by the SSB or MIB within the corresponding DL BWP. If the initial DL BWP configured by the individual SIB for the degraded UE includes the entire CORESET#0, then the degraded UE can use the bandwidth and location of CORESET#0 for downlink reception during initial access. The NCD-SSB period can be different from the CD-SSB period. In some cases, the NCD-SSB period can be no less than the CD-SSB period.

[0093] The UE can use random access procedures to communicate with the base station. For example, the UE can use random access procedures to request an RRC connection, re-establish an RRC connection, restore an RRC connection, etc. Random access procedures can include two different types: for example, when the UE is not synchronized with the base station, it can perform contention-based random access (CBRA); for example, when the UE was previously synchronized with base station 604, it can perform contention-free random access (CFRA). Both types of procedures include the transmission of random access preamble signals from the UE to the base station. In CBRA, the UE can, for example, randomly select a random access preamble signal sequence from a set of preamble signal sequences. When the UE randomly selects a preamble signal sequence, the base station can simultaneously receive other preamble signals based on the same preamble signal sequence from different UEs. Therefore, CBRA provides the base station with a way to resolve this contention between multiple UEs. In CFRA, the network can allocate a preamble signal sequence to the UE instead of the UE randomly selecting a preamble signal sequence. This helps avoid potential conflicts with preceding signals from another UE using the same sequence. Therefore, CFRA is called "contention-free" random access.

[0094] Figure 6 illustrates an example of a four-step random access procedure 600 between UE 602 and base station 604. UE 602 can initiate a random access message exchange by sending a first random access message 603 (e.g., Msg 1) including a preamble signal to base station 604. Before sending the first random access message 603, the UE can obtain random access parameters, such as preamble signal format parameters, time and frequency resources, root sequence for determining the random access preamble signal, and / or cyclic shift parameters, etc., from system information 601 from base station 604. The preamble signal can be sent using an identifier such as a random access RNTI (RA-RNTI). UE 602 can, for example, randomly select a random access preamble signal sequence from a set of preamble signal sequences. If UE 602 randomly selects a preamble signal sequence, base station 604 can simultaneously receive another preamble signal from different UEs. In some instances, a preamble sequence can be assigned to UE 602.

[0095] The base station responds to the first random access message 603 by sending a second random access message 605 (e.g., Msg 2) that uses PDSCH and includes a random access response (RAR). The RAR may include, for example, an identifier of a random access preamble signal sent by the UE, a timing advance (TA), an uplink grant for the UE to transmit data, a cellular radio network temporary identifier (C-RNTI) or other identifier, and / or a backoff indicator. Upon receiving the RAR 605, the UE 602 may, for example, use PUSCH to send a third random access message 607 (e.g., Msg 3) to the base station 604. The third random access message 607 may include an RRC connection request, an RRC connection re-establishment request, or an RRC connection restoration request, depending on the triggering of the random access procedure. Base station 604 can then complete the random access procedure by sending a fourth random access message 609 (e.g., Msg 4) to UE 602, such as using a PDCCH for scheduling and a PDSCH for that message. The fourth random access message 609 may include a random access response message, which includes timing advance information, contention resolution information, and / or RRC connection establishment information. UE 602 may, for example, use C-RNTI to monitor the PDCCH. If the PDCCH is successfully decoded, UE 602 can also decode the PDSCH. UE 602 can send a HARQ response for any data carried in the fourth random access message. If two UEs send the same preamble signal at 603, both UEs can receive a RAR that causes both UEs to send a third random access message 607. Base station 604 can resolve this conflict by being able to decode the third random access message from only one of the UEs and responding with a fourth random access message for that UE. Other UEs that do not receive the fourth random access message 609 can determine that the random access was unsuccessful and can retry the random access. Therefore, the fourth message can be called a contention resolution message. The fourth random access message 609 can complete the random access procedure. Therefore, UE 602 can then send uplink communications and / or receive downlink communications with base station 604 based on RAR 609.

[0096] To reduce latency or control signal transmission management burden, a single round-trip cycle between the UE and the base station can be implemented in a 2-step RACH procedure, as shown in Example 700 of Figure 7. The various states of Msg 1 and Msg 3 can be combined into a single message, for example, which may be referred to as message A. Before sending the first random access message 703, the UE 702 can obtain random access parameters from the base station 704 at 701, for example, in an SSB or RACH configuration (e.g., system information or RRC signal transmission), including preamble signal format parameters, time and frequency resources, parameters for determining the root sequence and / or cyclic shift of the random access preamble signal, etc. The UE 702 sends Msg A, which may include the random access preamble signal 703 and may also include PUSCH transmission 705 (e.g., data for Small Data Transmission (SDT)). The MsgA preamble signal can be separate from the four-step preamble signal, but it can be sent in the same random access timing (RO) as the preamble signal of the four-step RACH procedure, or it can be sent in a separate RO. PUSCH transmission can be sent in a PUSCH timing that may span multiple symbols and PRBs. After UE 702 sends Msg A (e.g., 703 and / or 705), UE 702 can wait for a response from base station 704. The variations of Msg 2 and Msg 4 in the four-step RACH of Figure 6 can be combined into a single message, which can be referred to as Msg B. Two-step RACH may be triggered for reasons similar to the four-step RACCH procedure. If UE 702 does not receive a response, UE 702 can retransmit MsgA or fall back to the four-step RACH procedure starting from Msg1. If base station 704 detects MsgA but fails to successfully decode the MsgA PUSCH, base station 704 can respond by allocating uplink retransmission resources for the PUSCH. UE 702 can return to the four-step RACH with Msg 3 based on the response from the base station and can retransmit the PUSCH from Msg A. If base station 704 successfully decodes Msg A and the corresponding PUSCH, base station 704 can reply using an indication of successful reception, for example, as a random access response to complete a two-step RACH procedure. Message B illustrated in Figure 7 may include Msg B PDCCH 707 and Msg B PDSCH 709 indicating successful reception (e.g., RAR). Msg B may include a random access response and a contention resolution message. The contention resolution message may be sent after the base station successfully decodes the PUSCH transmission. In some cases, Msg B PDSCH 709 may include data, for example, as part of an SDT. Subsequently, the UE can have effective timing advance (TA) and PUCCH resource timing.UE 702 can send PUCCH 710, which has ACK / NACK feedback for Msg B received from base station 704.

[0097] In some wireless communication systems, the initial transmission timing error of the UE may be less than or equal to the timing error limit value Te. For example, when the UE is configured in discontinuous reception (DRX) mode, such an initial transmission may occur after the UE has been inactive for a period of time (e.g., in a sleep state). The timing error limit value Te can be specified by the following table: Frequency range SSB signal SCS (kHz) SCS (kHz) of the uplink signal T e 1 15 15 12*64*T c 30 10*64*T c 60 10*64*T c 30 15 8*64*T c 30 8*64*T c 60 7*64*T c 2 120 60 3.5*64*T c 120 3.5*64*T c 240 60 3*64*T c 120 3*64*T c Table 2

[0098] As in the examples in Table 2, the timing error limit value Te can be defined based on the basic time unit Tc. In some cases, the timing error limit value Te can be applied to the first transmission in the DRX cycle of PUCCH, PUSCH, and SRS, or if the transmission is a PRACH transmission or a msgA transmission. For example, if at least one SSB is available at the UE during the last 160 ms, it is generally expected that the UE will meet the timing error limit value Te for the initial transmission. The reference point for the initial transmission timing control of the UE can be the downlink timing of the reference cell minus the downlink timing. The downlink timing can be defined as the time (in time) at which the first detected path is received from the reference cell for the corresponding downlink frame. The value NTA can be referred to as the timing advance between the downlink and uplink and can be provided to the UE via the timing advance command MAC-CE including TA. For PRACH, NTA can be 0. The value NTA offset can be referred to as the timing advance offset and can be provided to the UE via the information element (IE) n-TimingAdvanceOffset of the serving cell. For other channels (in Tc), it can be the difference between the UE transmission timing and the downlink timing immediately following the last timing advance of the application.

[0099] To meet timing error limits, the UE may measure the SSB of the serving cell at least once in the last N ms (e.g., the last 160 ms). In some cases, N may have a preset value of 160. In some cases, N may be any positive value. When the UE performs an RA procedure or SDT procedure in an initial / non-initial BWP (e.g., a single first DL and UL BWP pair (DL BWP 562 and UL BWP 564 in Figure 5) excluding the SSB, although the UE may be within the UL timing error limit for the first transmission for msg 1, msg A, or CG-PUSCH, subsequent UL (re)transmissions may extend beyond 160 ms after the last measurement of the SSB due to collisions, coverage limitations, and channel impairments. For example, Figure 8 is a diagram 800 showing the isochronism associated with a 4-step RACH. As shown in Figure 8, the UE (such as the UE illustrated in any of the diagrams in Figures 4-7) may receive SSB 802 (e.g., in the initial DL BWP 554). After receiving SSB 802, the UE can switch to a separate, for example, first BWP pair (e.g., 562 and 564) to perform a random access procedure. This separate, for example, first DL BWP does not include the SSB from the serving cell. The UE can transmit a first transmission for msg 1 804 in UL BWP 564. A random access response (RAR) window 806 can be scheduled for the UE to monitor the RAR from the serving cell on a separate, for example, first DL BWP 562 after transmitting the first transmission for msg 1 804 on UL BWP 564. A random backoff 808 may exist between RAR window 806 and another first transmission (e.g., retransmission) for msg 1 810. The time between the SSB and the retransmission of msg 1 810 can be TA. After retransmitting msg 1 810 on UL BWP 564, the UE can monitor msg 2 812 from the base station on DL BWP 562. After receiving msg 2 812 from the base station, the UE can correspondingly send msg 3 814 (e.g., on UL BWP 564) as a response. The time between the SSB and msg 3 814 can be TB. In a 4-step RACH procedure, TA and / or TB can be greater than 160 ms. In some cases, if the UE's initial / non-initial DL BWP does not contain an SSB or other DL RS (such as a TRS) for time / frequency tracking, and the RA / SDT procedure takes more than N ms to complete, the UE can retune and measure the SSB or other DL RS outside of the initial / non-initial DL BWP without an SSB configured for RA and SDT.For example, a UE can switch from DL BWP 562 or UL BWP 564 to measure the SSB or DL ​​RS on BWP 554. The UE can then return to DL BWP 562 or UL BWP 564 to continue the RA procedure or SDT procedure. The various forms provided herein offer synchronization procedures and signaling support for UEs configured with SSB-free initial / non-initial DL BWPs for RA or SDT. "SSB-free BWP" can refer to a DL BWP that does not include an SSB, for example, excluding the entire SSB sent by the serving cell.

[0100] In some cases, when an RRC-idle, inactive, or connected UE (which may be RedCap or non-RedCap) is configured with an SSB-free DL BWP for RA or SDT via System Information (SI) or RRC, the SSB-free DL BWP may be configured with a CORESET and / or SS set for RA (for 2-step or 4-step RACH) or SDT (e.g., RACH-based or configured permitted UL SDT, such as RA-SDT or CG-SDT). In some configurations, a UE may expect its UL BWP (e.g., having the same BWP identifier (ID) as a DL BWP without SSB) to include: 1) a valid PRACH timing (e.g., RO) for 4-step RACH and a valid PUCCH resource set for HARQ feedback for msg 4; 2) a valid msg A PRACH / PUSCH timing (msg A RO / PUSCH timing) for 2-step RACH and a valid PUCCH resource set for HARQ feedback for msg B; or 3) a valid SDT timing (e.g., RA-SDT or CG-SDT) and a valid PUCCH resource set for HARQ feedback for SDT. In some configurations, the network (such as a base station) may configure the spatial relation (e.g., spatial relation information) for RO, the msg A RO or PUSCH timing, the SDT timing, and the PUCCH resource set for the serving cell. In some configurations, spatial relationships can be associated with a cell-defined (CD-SSB) or non-cell-defined (NCD-SSB) of the serving cell, which can be transmitted outside of an SSB-free DL BWP configured for RA and SDT. In some configurations, spatial relationships can be associated with other DL RSs (e.g., CSI-RS) of the serving cell, which can be transmitted inside or outside an SSB-free DL BWP configured for RA. In some configurations, the CORESET and / or SS set used for RA or SDT procedures can be quasi-co-located (QCL) with the SSB or DL ​​RS used for spatial relationship configuration. In some configurations, the CORESET and / or SS set used for RA or SDT procedures can be QCL-based on QCL type D. In some configurations, the SSB or DL ​​RS configured as a QCL source for CORESET / SS for RA or SDT can also be used by the UE to perform time and / or frequency synchronization during RA or SDT procedures.

[0101] In some states, the QCL relation can indicate the relationship between signals with respect to one or more of the following: Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter set, etc. In some states, the QCL relation can be based on different QCL type parameters. Different types of QCL relations can exist, where QCL type A can include Doppler shift, Doppler spread, average delay, and delay spread; QCL type B can include Doppler shift and Doppler spread; QCL type C can include Doppler shift and average delay; and QCL type D can include spatial Rx parameters.

[0102] In some configurations, when a UE in an RRC idle, inactive, or connected state (e.g., a degraded UE or a general UE) can be configured with an SSB-free DL BWP for RA or SDT procedures (such as RACH-based or configuration-permitted small UL data transfers), the UE can be configured with an SSB-free DL BWP (as part of a DL and UL pair) via SI or RRC signals, and the SSB-free DL BWP can be configured with a CORESET and / or SS set for RA (for 2-step or 4-step RACH) or SDT (e.g., RA-SDT or CG-SDT). The SDT can represent the exchange of DL / UL data from the control plane or user plane that is less than a size threshold, which can be included in paging messages, RAR messages, contention resolution messages, or random access messages for 4-step or 2-step RACH (as described in conjunction with Figure 7), or transmitted in permitted resources configured for a UE not transitioned to an RRC connected state. In some configurations, after the UE initiates a RA or SDT procedure in the DL or UL BWP, the UE can start a retuning timer for DL ​​BWP handover to measure the SSB or other DL RS outside the SSB-less DL BWP. The UE can monitor the SSB-less DL BWP (e.g., 562) to obtain a response to RA or SDT messages sent in the UL (e.g., 564). In some configurations, the retuning timer and timing advance (TA) timer for RA or SDT can be configured separately. In some configurations, the retuning timer configuration can be based at least on UL timing accuracy requirements and UE capabilities. In some configurations, if configured via SI or RRC, the retuning timer can also depend on the period / mode of the serving cell's CD-SSB / NCD-SSB / TRS / PRS / CSI-RS. In some configurations, the retuning timer tracks the time interval for the last measurement of an SSB (or other DL RS) sent by the serving cell outside of the SSB-free DL BWP used for RA / SDT. In some configurations, the network can additionally configure backoff parameters for msg 1, msg A, or SDT retransmissions. In some configurations, the backoff parameters can be no less than the UE's retuning delay and measurement interval. For example, before msg 1, msg A, or SDT retransmissions, the UE's isochronism may be sufficient to measure SSBs outside the BWP to resynchronize with the serving cell.In some configurations, when a retuning timer for RA / SDT (including RA-SDT and CG-SDT) expires, or a TA timer for RA / SDT (including RA / SDT and CG-CDT) expires, or TA authentication for CG-SDT (PUSCH / PUCCH / SRS transmission) fails, the UE may autonomously (e.g., without signal delivery from the base station) terminate its DL reception (e.g., on a standalone DL initiating BWP 562) or cancel its UL transmission in a BWP configured for RA and SDT (e.g., 564), where DL termination or UL cancellation can be performed entirely or partially by the UE. The UE may also switch or retun between BWPs to measure SSB or other DL RS, 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 the BWP to receive system information updates or Public Warning System (PWS) notifications. In some cases, the effective length of the isochronous line, DL termination (full or partial), UL cancellation (full or partial), and measurement gap for the UE used for BWP handover / retuning may depend at least on the UE type or capability, SI modification period, interruption time for paging reception, and the reference SCS of the active DL / UL BWP. In some cases, after completing measurements or SI / PWS reception on a DL BWP 554 other than an SSB-free DL BWP 562, the UE can retune back to DL / UL BWP 562 or 564 and resume the RA procedure or SDT procedure. The UE can also reset the retuning timer.

[0103] Figures 9A and 9B are diagrams 900 and 950 illustrating example isochrones associated with a retuning timer. As shown in Figure 9A, a UE (such as the UE described in conjunction with any of the diagrams in Figures 4-7) may receive SSB 902 (e.g., in the initial DL BWP 554). After receiving SSB 902, the UE may perform random access using, for example, a first DL and UL BWP pair. At 904, the UE may send an initial transmission of msg 1 (for a four-step RACH) or msg A (for a two-step RACH). After sending the initial transmission msg 1 or msg A 904, the UE may monitor DL ​​BWP 562 during RAR window 906. After the UE initiates RA or SDT in the UL BWP, and after the initial transmission of msg 1 or msg A 904, the UE may start its retuning timer Tre. The time between SSB 902 and the start of the retuning timer may be T0. Random backoff (908) may occur between the retransmission of RAR window 906 and msg 1 or msg A 910. After the retransmission of msg 1 or msg A 910 on UL BWP 564, the UE can monitor msg 2 or msg B 912 from the base station on DL BWP 562. If the retuning timer expires (e.g., T 0 + Tr > N ms) or the TA timer expires, the UE can cancel the next UL transmission (914) for RA or SDT on UL BWP 564 or the DL reception on DL BWP 562.

[0104] As shown in Figure 9B, a UE (such as the UE described in conjunction with any of the figures in Figures 4-7) may, for example, switch to DL BWP 554 to receive SSB 952 based on the expiration of a timer. The UE may receive the SSB to perform synchronization measurements. After receiving SSB 952, the UE may send an initial transmission of msg 1 or msg A 954 on UL BWP 564. The UE may monitor for responses from the base station on DL BWP 562 during RAR window 956 after receiving the initial transmission of msg 1 or msg A 954. After the UE initiates RA or SDT in UL BWP 564 and after the initial transmission of msg 1 or msg A 954, the UE may start its retuning timer Tre. The time between SSB 952 and the start of the retuning timer may be T0. Random backoff 958 may occur between RAR window 956 and the retransmission of msg 1 or msg A 960. After a retransmission of msg 1 or msg A 960 in UL BWP 564, the UE can monitor msg 2 or msg B from the base station in RAR window 962 in DL BWP 562. If the retuning timer expires (T 0 + Tr > N ms) or the TA timer expires, the UE can terminate PDCCH / RAR monitoring (e.g., in RAR window 962) in an SSB-free DL BWP 562 configured for RA or SDT to switch to DL BWP 554 to receive SSBs and perform synchronization with the serving cell. In some cases, the parameter Nms can be the number of milliseconds the UE can continue monitoring without measuring SSBs.

[0105] In some configurations, when an idle, inactive, or connected UE is configured with an SSB-free DL BWP (e.g., 562) for RA or SDT via SI / RRC, the SSB-free DL BWP can be configured with a CORESET / SS for RA (2-step or 4-step RACH) or SDT (RA-SDT or CG-SDT). In some configurations, after the UE initiates RA or SDT in the corresponding UL BWP (e.g., 564), the UE can start a retuning timer for DL ​​BWP handover / retuning to measure the SSB or other DL RS in the DL BWP 554 other than the SSB-free DL BWP 562. Furthermore, if the RF retuning timer and TA timer are still running before the UL transmission (i.e., msg 3 or msg A PUSCH / CG PUSCH / UCI), and TA verification is successful for the CG-PUSCH transmission, the UE can optionally report the retuning schedule in msg 3 or msg A PUSCH / GG PUSCH / UCI during the RA or SDT procedure (depending on the earlier expiration time of the retuning timer and TA timer). In some cases, the UE can initiate BWP retuning based on, for example, the retuning schedule reported to the base station in msg 3 or msg A PUSCH / CG PUSCH / UCI, and can switch to BWP 554 to perform synchronization after sending the reported value. In some cases, the UE's reporting of the retuning timer can be enabled / disabled by the network in SI / RRC. For example, the UE can receive an instruction to enable timer reporting from the base station before performing the RA or SDT procedure. When the UE initiates an RA or SDT procedure in a BWP pair (e.g., 562 and 564), the UE can report the timer value to the base station. Conversely, 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 can avoid reporting the timer value to the base station. In some cases, the UE's reporting of the retuning timer can be triggered by a condition or triggering event. For example, the UE can be configured with one or more conditions or triggering events. If a condition or triggering event occurs, the UE can send a report of the timer value. For example, the UE may expect to retune before the following times: msg B RAR window expires, msg 4 contention resolution timer expires, or TA timer expires, etc. In some scenarios, upon receiving a report of retuning from the UE, the base station can schedule subsequent DL channels (e.g., msg 4, msg B, DL feedback for SDT) or UL channels (e.g., PUCCH for HARQ feedback) for the UE with sufficient scheduling gaps to accommodate isochronous extensions caused by retuning and measurement.In some cases, after completing measurements outside of the SSB-free DL BWP, the UE can retune back to the original DL / UL BWP, resume the RA / SDT procedure, or reset the retuning timer.

[0106] Figure 10 is a diagram 1000 illustrating an example isochron with retuning. As shown in Figure 10, a UE (such as the UE described in conjunction with any of the diagrams in Figures 4-7) can receive SSB 1002. After receiving SSB 1002 on DL BWP 554, the UE can send an initial transmission of msg 1 1004 in UL BWP 564. After the UE initiates RA or SDT in UL BWP 564, and after the initial transmission of msg 1 1004, the UE can start its retuning timer Tre for DL ​​BWP handover / retuning to measure SSBs or other DL RSs outside of the SSB-free DL BWP. For example, after sending msg 1 or msg A in UL BWP 564, the UE can monitor DL ​​BWP 562 for responses from the base station. The timer can be related to the time it takes for the UE to switch from monitoring DL BWP 562 for responses to DL BWP 554 in order to receive SSBs. The time between the previous SSB 1002 reception and the start of the retuning timer can be T0. After the initial transmission of msg 1 1004, the UE can monitor msg 2 1006 on DL BWP 562. Based on one or more configured conditions or triggering events, the UE can be triggered to report a retuning schedule in msg 3 1008. For example, based on the defined parameter τ, if N - τ < T0 + Tr < N, the UE can be triggered to report a retuning schedule in msg 3 1008. In some cases, N can be a number of milliseconds such that if the UE does not measure the SSB in the last N milliseconds, the UE will no longer believe its timing is reliable. The retuning schedule can represent the time during which the UE will return from the UL and DL BWP pair (DL BWP 562 and UL BWP 564) to DL BWP 554 to perform synchronization via measuring the SSB or another DL reference signal. In some states, after sending msg 3 1008, the UE can begin retuning based on the retuning schedule reported in msg 3 1008 (e.g., switching to DL BWP 554). In some states, after completing the measurements for resynchronization, the UE can return to BWP (e.g., 562 and / or 564) to continue the RA procedure or SDT procedure. In some states, the time taken to return to BWP 554 for synchronization measurements may cause a delay in the transmission (e.g., reception) of msg 4 1010. In some states, PUCCH 1012 can be sent after transmitting message 4 1010.

[0107] Figure 11 is a diagram 1100 illustrating an example isochronous line associated with BWP retuning for synchronization measurement (e.g., retuning from a single initial BWP pair excluding the SSB or DL ​​reference signal to an initial DL BWP including both the SSB and DL reference signals). As shown in Figure 11, a UE (such as the UE described in conjunction with any of the figures in Figures 4-7) can receive SSB 1102 in an initial DL BWP (such as DL BWP 554). After receiving SSB 1102, the UE can send an initial transmission of msg 1 1104 to initiate an RA procedure or an SDT procedure. After the UE initiates an RA or SDT in a UL BWP (e.g., 564) using the initial transmission of msg 1 1104, the UE can monitor the associated DL BWP (e.g., DL BWP 562) in response to a reply from the base station. The UE can start its retuning timer Tre for DL ​​BWP handover / retuning to measure the SSB or other DL RS in a DL BWP other than the SSB-free DL BWP (e.g., 554) (e.g., 562). The time between SSB 1102 and the start of the retuning timer can be T0. After the initial transmission of msg 1 1104, the UE can monitor DL ​​BWP 562 to send msg 2 1106. Based on the occurrence of one or more conditions or triggering events (e.g., which may be configured by the base station), the UE can be triggered to report a retuning schedule in msg 3. For example, based on the parameter τ (which may be defined or otherwise known to the UE), if N - τ < T0 + Tre < N, the UE can be triggered to report a retuning schedule in msg 3 1108. In some states, after receiving msg 4 1110 in response to msg 3 1108, the UE can initiate retuning based on the retuning schedule reported in msg 3 1108 (e.g., retuning from DL BWP 562 to DL BWP 554 to measure SSB or other DL RS for synchronization). In some states, after completing the measurements for resynchronization, the UE can return to the previous BWP (e.g., 562 or 564) to continue the RA procedure or SDT procedure. In some states, the UE can send PUCCH 1112, which may be delayed due to retuning. The base station can know the timing of the delay for PUCCH 1112 based on receiving the retuning schedule report from the UE.

[0108] In some states, when an idle, inactive, or connected UE is configured with an SSB-free DL BWP (e.g., 562) for RA or SDT via SI / RRC, the SSB-free DL BWP 562 can be configured with a CORESET / SS for RA (2-step or 4-step RACH) or SDT (RA-SDT or CG-SDT). In some states, after the UE initiates RA or SDT in the corresponding UL BWP (e.g., 564), the UE can monitor the response in the DL BWP 562. The UE can also start a retuning timer for DL ​​BWP handover or retuning to measure SSBs or other DL RSs outside the SSB-free DL BWP. In some states, the UE can also request RAR window reconfiguration based on an early indication in msg 1 or msg A. In some states, the UE can start retuning after sending msg 1 or msg A including the request. In some scenarios, early indication of a request by the UE can be enabled / disabled by the network in SI or RRC. For example, before executing a RA or SDT procedure, the UE can 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 can include the request to the base station. Conversely, if the UE receives an indication that the request is disabled, or does not receive an indication that the request is enabled, the UE can avoid sending the request to the base station. In some scenarios, a UE's request to reconfigure a RAR window can be triggered by configured conditions or events. In response to the occurrence of one or more conditions or triggering events (which may have been previously configured for the UE), the UE can send a request. For example, the UE may expect to retune for resynchronization before the RAR window expires. In some configurations, when transmitting early indications of the UE in msg 1 or msg A (including msg 1 or msg A transmission in RA-SDT), the base station can delay the transmission of msg 2 or msg B by a configured time offset to accommodate isochronous extension of the UE due to retuning and measurement outside the SSB-free DL BWP. In some configurations, after completing measurement outside the SSB-free DL BWP, the UE can retune back to the original DL / UL BWP (e.g., 562 and 564), resume the RA / SDT procedure, and reset the retuning timer.

[0109] Figure 12 is a diagram 1200 illustrating an example isochronous line associated with a BWP pair retuned from a DL BWP having an SSB or other DL reference signal for synchronization to a DL BWP having an SSB or other DL reference signal for synchronization. As shown in Figure 12, a UE (such as the UE described in conjunction with any of the diagrams in Figures 4-7) can receive SSB 1202, for example, in DL BWP 554. After receiving SSB 1202, the UE can send an initial transmission of msg 1 or msg A 1204 in UL BWP 564. Subsequently, the UE can monitor responses from the base station on DL BWP 562. After the UE initiates RA or SDT in UL BWP 564, and after the initial transmission of msg 1 or msg A 1204, the UE can start its retuning timer TR for DL ​​BWP handover / retuning to measure SSBs or other DL RSs outside of the SSB-free DL BWP. The time between the reception of SSB 1202 and the start of the retuning timer can be T0. The UE can monitor for a response to msg 2 or msg B from the base station within msg 2 or msg B RAR window 1208 after the interval of msg 2 or msg B RAR window 1206. After random backoff 1210, the UE can be triggered to send a request to reconfigure the RAR window to delay the transmission of msg B or msg 4. The UE can send the request based on the occurrence of one or more conditions or triggering events (which can be configured by the base station for the UE). In some cases, the UE can send a retransmission of msg A or msg 1 with an early indication 1212 to the base station. Upon receiving a retransmission of msg A or msg 1 from a UE with an early indication 1212, the base station may delay msg B or msg 2 RAR window 1218 and delay the transmission of msg B or msg 2 1216 by a configured time offset 1214 to accommodate the isochronous extension of the UE due to retuning and measurement outside of the SSB DL BWP.

[0110] In some configurations, when an idle, inactive, or connected UE is configured with an SSB-free DL BWP (e.g., 562) for RA or SDT via SI / RRC, the SSB-free DL BWP can be configured with CORESET / SS for RA (2-step or 4-step RACH) or SDT (RA-SDT or CG-SDT). In some configurations, after the UE initiates RA or SDT in the UL BWP (e.g., 564), the UE can start a retuning timer for DL ​​BWP handover or retuning to measure SSBs or other DL RSs outside the SSB-free DL BWP. The UE can monitor DL ​​BWP 562 for responses to uplink messages sent in UL BWP 564. In some configurations, the UE can also request RS transmission or RS configuration in DL BWP 562 based on early indications for SDT in msg 1, msg 3, msg A, PUCCH, PUSCH, or other messages. In some states, the UE may request a TRS that the UE can use for synchronization, or another DL RS. The transmission or configuration of the DL reference signal in DL BWP 562 may allow the UE to continue monitoring DL BWP 562 and avoid retuning to DL BWP 554 to perform synchronization. In some states, the UE's early indication may be enabled / disabled by the network, for example, via an indication or absence indication in SI or RRC signal transmission. In some states, the UE's request for on-demand TRS transmission may be triggered by the occurrence of one or more conditions or events. These conditions or triggering events may be configured by the base station for the UE. In some states, upon receiving the UE's request or early indication in msg 1, msg 3, msg A, PUCCH, CG-PUSCH, or other messages, the base station may respond using (e.g., in DCI) an ACK or NACK for msg 2, msg B, or a DL feedback for SDT. In some scenarios, if the base station responds with "ACK" (such as in DCI), the base station can acknowledge the UE's request for on-demand transmission or configuration of TRS. The UE can then monitor TRS in DL BWP 562. The UE can expect to receive TRS configuration in the MAC-CE associated with DCI. The UE can also expect to receive TRS in a DL BWP without SSB without retuning. If the base station responds with "NACK" in DCI, the base station can reject the UE's request for on-demand transmission or TRS configuration.The UE can accordingly return to the procedure based on readjusting the timer to measure the SSB or other DL RS outside of the SSB DL BWP. For example, if the timer expires, the UE can switch to DL BWP 554 to perform synchronization based on the SSB or other DL reference signal.

[0111] Figure 13 is a diagram 1300 illustrating an instance isochronous line associated with a 2-step RACH. As shown in Figure 13, after the base station sends a DL transmission 1302 to the UE, there may be a gap 1304 greater than or equal to the defined parameter N gap before msg A 1306. Message A 1306 may include a preamble signal and a payload. Between the preamble signal and the payload, there may be a gap greater than or equal to the defined parameter N. After the start of the msg B RAR window (which may be defined based on the first PDCCH symbol in the earliest SS used for msg B PDCCH), there may be a msg B 1308 sent from the base station to the UE. msg B 1308 may include msg B PDCCH and msg B PDSCH (based on a successful RAR). After the defined time 1310, the UE may send a PUCCH HARQ ACK / NACK 1312 to the base station.

[0112] Figure 14 is a diagram 1400 illustrating an instance isochronous line associated with a 4-step RACH. As shown in Figure 14, after the base station sends the DL channel or signal 1402 to the UE, and before msg 1 1406 can be sent, there may be a gap 1404 equal to the defined gap N. After msg 1 1406 and before the RAR window for msg 2 associated with msg 1 1406, there may be a gap to the defined gap N. After the start of the msg 2 RAR window (which may be defined based on the first PDCCH symbol in the Type 1 PDCCH SS for msg 2), there may be msg 2 1408 sent from the base station to the UE. msg 2 1408 may be associated with a PDCCH. After the defined time, msg 3 1410 can be sent from the UE to the base station. In response to msg 3 1410, the base station can send msg 4 1412 to the UE, which can be associated with the PDCCH. The PDCCH can schedule resources for PUCCH 1414. After a period of time, the UE can send PUCCH 1414 to the base station.

[0113] Figure 15 is a flowchart 1500 of a wireless communication method. The method can be performed by a UE (e.g., UE 104, UE 602, UE 702; device 1704).

[0114] At 1502, the UE may receive a configuration for a first DL and UL BWP pair, which includes information indicating at least one of a CORESET, an SS set, and a UL resource timing set 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, as described in conjunction with any of the figures in Figures 4-14, the UE may receive a configuration for a first DL and UL BWP pair, which includes information indicating at least one of a CORESET, an SS set, and a UL resource timing set for a RA procedure or an SDT procedure. In some states, 1502 may be performed by a synchronization component 198. In some states, the first DL BWP does not include the entire SSB transmitted by the serving cell, and the QCL and spatial relationship configuration in the first DL and UL BWP pair is based on the serving cell's SSB or DL ​​reference signal configured in the second DL BWP. In some configurations, the UL resource timing set in the first uplink BWP of the first DL and UL BWP pair is associated with (e.g., configured with) a spatial relationship configuration of the SSB with serving cell or the DL reference signal in the second DL BWP. This UL resource timing set includes one or more of the following: a RO for RA procedures, a PUSCH timing for RA procedures, an authorized SDT timing based on random access or configuration, an SRS timing, and a PUCCH timing associated with the RA procedure or SDT. In some configurations, the configuration for the first DL and UL BWP pair includes information indicating the following: a QCL source in the second DL BWP and used by the UE to perform RA procedures or SDT procedures in the first DL and UL BWP pair, a spatial relationship configuration, and a synchronized CD-SSB or NCD-SSB. In some configurations, the configuration for the first DL and UL BWP pair includes information indicating the following: CSI-RS, PRS, or TRS, sent by the serving cell in the second DL BWP, for spatial relationship configuration and synchronization of the RA procedure or SDT procedure for the UE in RRC idle, inactive, or connected states. In some configurations, the CORESET and SS sets configured in the first DL BWP for the RA procedure or SDT procedure have a QCL relationship with the SSB of the serving cell or the DL reference signal in the second DL BWP.

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

[0116] At 1506, the UE may perform time or frequency synchronization during the RA procedure or SDT procedure 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., or in the first DL BWP of the first DL and UL BWP pair). For example, the UE described in conjunction with any of the figures in Figures 4-14 may perform time or frequency synchronization during the RA procedure or SDT procedure 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., or in the first DL BWP of the first DL and UL BWP pair). In some cases, 1506 may be performed by the synchronization component 198 in Figure 17. In some configurations, performing time or frequency synchronization includes: pausing or canceling activity in the first DL BWP or first UL BWP of the first DL and UL BWP pair during the RA or SDT procedure; switching from the first DL BWP or first UL BWP to the second DL BWP to measure the SSB of the serving cell or the DL reference signal in the second DL BWP; returning from the second DL BWP to the first DL BWP or first UL BWP after measuring 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 reselection of uplink resource timing; or resuming the RA or SDT procedure in the first DL and UL BWP pair. In some configurations, the isochrona used for switching from the first DL BWP or first UL BWP to the second DL BWP is based on one or more of the following: capabilities supported by the UE, device type indicated by the UE, triggering event for BWP handover, or reference SCS associated with the first DL BWP, first UL BWP, and second DL BWP.

[0117] In some configurations, the UE may also start a first timer associated with a BWP handover for measuring SSB or DL ​​reference signals from the first DL BWP or first UL BWP to the second DL BWP after initiating an RA procedure or SDT procedure (e.g., to meet the UE's performance specifications, at least for synchronization, beam management, and link maintenance), wherein the first timer tracks the gap relative to the UE's latest measurement of the SSB or DL ​​reference signal of the serving cell. In some configurations, the UE may start a second timer associated with the RA procedure or SDT procedure after initiating an RA procedure or SDT procedure, the second timer being configured separately from the first timer, wherein the UE switches from the first DL BWP or first UL BWP to the second DL BWP to measure the SSB or DL ​​reference signal in response to the expiration of the first or second timer or the failure of the early timing verification of the SDT procedure. In some configurations, the UE may reset the first timer after completing the measurement of the SSB or DL ​​reference signal in the second DL BWP.

[0118] In some configurations, handover from the first DL BWP or the first UL BWP to the second DL BWP also includes: stopping downlink reception in the first DL BWP or uplink transmission in the first UL BWP. In some configurations, the UE may send the value of the first timer in a message during one or more valid uplink resource opportunities during the RA procedure or SDT procedure. In some configurations, the UE sends the value of the first timer in a message based on the continuation of the first and second timers or the successful timing advance verification of the SDT procedure. In some configurations, the handover from the first DL BWP or the first UL BWP to the second DL BWP is performed after the value of the first timer is sent or based on the BWP retuning schedule received from the serving cell in system information or dedicated RRC messages.

[0119] In some states, the UE may receive a signal transmission from the serving cell reporting the value of the first timer before sending a message, wherein the signal transmission is received in system information, dedicated RRC messages, MAC CE, or DCI. In some states, the UE may selectively send the value of the first timer in a message based on conditions or the occurrence of a triggering event that depends at least on the UE's capabilities, the type of RA procedure or SDT procedure, cell coverage, or frequency range. In some states, the UE may receive scheduling information for DL ​​reception or UL transmission, the scheduling information including a time offset in response to the value of the first timer reported by the UE, wherein the time offset provided by the serving cell is not less than the UE's BWP handover delay and measurement gap. In some states, the UE may send a request for RAR window adjustment in an uplink signal or channel (e.g., PRACH, PUSCH, PUCCH, or SRS) associated with the RA procedure or SDT procedure, based on the BWP handover delay and the UE's measurement gap in the second DL BWP. In some configurations, the handover from the first DL BWP or the first UL BWP to the second DL BWP is performed after a request is sent or based on a BWP retuning schedule received from the serving cell in system information or a dedicated RRC message. In some configurations, the UE may receive a signal transmission enabling a request from the UE for RAR window adjustment before sending a random access message, wherein the signal transmission is received from the serving cell in system information, a dedicated RRC message, a MAC CE, or a DCI. In some configurations, the UE selectively sends requests based on the occurrence of a condition or triggering event, which depends on at least one of the following: UE capability, type of RA procedure or SDT procedure, cell coverage, or frequency range. In some configurations, the UE may send 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 procedure or SDT procedure. In some states, the UE may receive an enable request signal from the serving cell before sending the request, wherein the signal is received in system information, a dedicated RRC message, MAC CE, or DCI. In some states, the UE sends the request based on the occurrence of a condition or triggering event. In some states, the UE may receive an acknowledgment for on-demand transmission of NCD-SSB, TRS, or other DL reference signals, wherein performing time or frequency synchronization includes measuring the NCD-SSB, TRS, or other DL reference signals in the first DL BWP after receiving the acknowledgment. In some states, the UE may receive a negative response rejecting the request from the UE.In some configurations, the UE can switch 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 a negative response.

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

[0121] At 1602, the base station may send 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 includes information indicating at least one of the following: CORESET, SS set, uplink resource timing set, and SSB or DL ​​reference signal in the second DL BWP for the random access procedure or SDT procedure, wherein 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 sent by the serving cell in the second DL BWP. For example, the base station described in conjunction with any of the figures in Figures 4-14 can 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. This configuration includes information indicating at least one of the following: a CORESET for the random access procedure or SDT procedure, an SS set, an uplink resource timing set, 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 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 sent by the serving cell in the second DL BWP. In some cases, 1602 can be performed by the synchronization component 1842 in Figure 18.

[0122] At 1604, the base station may receive, in the first UL BWP of the first DL and UL BWP pair, at least one of the random access messages or SDT messages from the UE, an early indication from the UE for one or more of the following: device type, a first request for a first on-demand transmission of the SSB or DL ​​reference signal, or other auxiliary information for self-adjusting scheduling. For example, the base station described in conjunction with any of the figures in Figures 4-14 may receive, in the first UL BWP of the first DL and UL BWP pair, at least one of the random access messages or SDT messages from the UE, an early indication from the UE for one or more of the following: device type, a first request for a first on-demand transmission of the SSB or DL ​​reference signal, or other auxiliary information for self-adjusting scheduling. In some cases, 1604 may be performed by the synchronization component 1842 in Figure 18. In some configurations, the base station may receive, in a random access message or SDT message, one of the following: the value of a timer for the SSB or downlink reference signal of the UE's measuring service cell associated with a BWP handover from the first DL BWP or the first UL BWP to the second DL BWP, or a second request for RAR window adjustment based on the BWP handover delay and the measurement gap for measuring the SSB or DL ​​reference signal in the second DL BWP. In some configurations, the base station may utilize a time offset to schedule downlink transmissions or uplink receptions with the UE, the time offset being relative to the BWP handover delay and measurement gap for the UE's handover from the first DL BWP or the first UL BWP to the second DL BWP to measure the SSB or DL ​​reference signal. In some configurations, the base station may receive, in a random access message in the first UL BWP, a second request for on-demand transmission of the NCD-SSB, TRS, or another DL reference signal in the first DL BWP. In some states, the base station may respond to a request by sending at least one of the following: 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.

[0123] FIG17 is FIG1700 illustrating an example of a hardware implementation for device 1704. Device 1704 may be a UE, a component of a UE, or may implement UE functions. In some embodiments, device 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). Cellular baseband processor 1724 may include on-chip memory 1724'. In some embodiments, device 1704 may also include one or more Subscriber Identity Module (SIM) cards 1720 and an application processor 1706 coupled to a Secure Digital Card (SD) card 1708 and a screen 1710. Application processor 1706 may include on-chip memory 1706'. In some embodiments, device 1704 may also 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., barometers / altimeters; motion sensors such as inertial management units (IMUs), gyroscopes, and / or accelerometers; light detection and ranging (LIDAR), radio-assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometers, audio, and / or other technologies for positioning), an additional memory module 1726, a power supply 1730, and / or a camera 1732. The Bluetooth module 1712, WLAN module 1714, and satellite system module 1716 may include an on-chip transceiver (TRX) / receiver (RX). The cellular baseband processor 1724 communicates with the UE 104 and / or the RU associated with the network entity 1702 via a transceiver 1722 and one or more antennas 1780. The cellular baseband processor 1724 and the application processor 1706 may each include computer-readable media / memory 1724' and 1726', respectively. An additional memory module 1726 may also be considered computer-readable media / memory. Each computer-readable media / memory 1724', 1706', and 1726 may be non-transitory. The cellular baseband processor 1724 and the application processor 1706 are each responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by the cellular baseband processor 1724 / application processor 1706, the software causes the cellular baseband processor 1724 / application processor 1706 to perform the various functions described herein. Computer-readable media / memory can 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 can be a component of the UE 350 and can include at least one of the TX processor 368, RX processor 356, and controller / processor 359 and / or memory 360.In one configuration, device 1704 may be a processor chip (modem and / or application) and includes only a cellular baseband processor 1724 and / or an application processor 1706. In another configuration, device 1704 may be the entire UE (e.g., see 350 in FIG3) and includes additional modules of device 1704.

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

[0125] As shown, the device 1704 / 1704' may include various components configured for various functions. In one configuration, the device 1704 (and particularly the cellular baseband processor 1724) may include units for receiving a configuration for a first DL and UL BWP pair, the configuration including information indicating at least one of a CORESET, an SS set, and a UL resource timing set for an RA procedure or an SDT procedure. The cellular baseband processor 1724 may also include units 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 also include units for performing time or frequency synchronization during an RA procedure or an SDT procedure using an SSB of a service cell configured in a second DL BWP or a DL reference signal of a service cell configured in a second DL BWP (e.g., in the first DL BWP of the first DL and UL BWP pair). The cellular baseband processor 1724 may also include units for pausing or canceling activity in the first DL BWP or first UL BWP of the first DL and UL BWP pair during RA or SDT procedures. The cellular baseband processor 1724 may also include units for switching from the first DL BWP or first UL BWP to a second DL BWP to measure the SSB of the service cell or the DL reference signal in the second DL BWP. The cellular baseband processor 1724 may also include units for returning from the second DL BWP to the first DL BWP or first UL BWP after measuring the SSB or DL ​​reference signal in the second DL BWP. The cellular baseband processor 1724 may also include units for using measurements obtained in the second DL BWP for time or frequency synchronization, power control, beam management, timing advance verification, or reselection of uplink resource timing. The cellular baseband processor 1724 may also include units for resuming the RA or SDT procedure in the first DL and UL BWP pair. The cellular baseband processor 1724 may also include a unit for the following operation: after initiating an RA procedure or SDT procedure, starting a first timer associated with a BWP handover for measuring an SSB or DL ​​reference signal from a first DL BWP or a first UL BWP to a second DL BWP, wherein the first timer tracks the gap between the latest measurements of the SSB or DL ​​reference signal of the UE to the serving cell.The cellular baseband processor 1724 may also include units for: after initiating an RA procedure or SDT procedure, starting a second timer associated with the RA procedure or SDT procedure, the second timer being configured separately from the first timer, wherein the UE switches from a first DL BWP or a first UL BWP to a second DL BWP to measure an SSB or DL ​​reference signal in response to the expiration of the first timer or the second timer or the failure of early timing verification of the SDT procedure. The cellular baseband processor 1724 may also include units for: after completing the measurement of the SSB or DL ​​reference signal in the second DL BWP, resetting the first timer. The cellular baseband processor 1724 may also include units for: stopping downlink reception in the first DL BWP or uplink transmission in the first UL BWP. The cellular baseband processor 1724 may also include units for: during the RA procedure or SDT procedure, at one or more valid uplink resource opportunities, transmitting the value of the first timer in a message. The cellular baseband processor 1724 may also include units for: receiving a signal transmission from the serving cell reporting the value of a first timer before transmitting a message, wherein the signal transmission is received in system information, dedicated RRC messages, MAC CE, or DCI. The cellular baseband processor 1724 may also include units for: receiving scheduling information for DL ​​reception or UL transmission, the scheduling information including a time offset in response to the value of the first timer reported by the UE, wherein the time offset provided by the serving cell is not less than the UE's BWP handover delay and measurement gap. The cellular baseband processor 1724 may also include units for: sending a request for RAR window adjustment in an uplink signal or channel associated with an RA procedure or SDT procedure, based on the BWP handover delay and the UE's measurement gap in a second DL BWP. The cellular baseband processor 1724 may also include units for: receiving a signal transmission enabling a request from the UE for RAR window adjustment before transmitting a random access message, wherein the signal transmission is received from the serving cell in system information, dedicated RRC messages, MAC CE, or DCI. The cellular baseband processor 1724 may also include units for: transmitting 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 associated with the RA procedure or SDT procedure. The cellular baseband processor 1724 may also include units for: receiving a signal transmission enabling the request from the serving cell before transmitting the request, wherein the signal transmission is received in system information, dedicated RRC messages, MAC CE, or DCI.The cellular baseband processor 1724 may also include units for receiving acknowledgments for on-demand transmissions of NCD-SSB, TRS, or other DL reference signals, wherein performing time or frequency synchronization includes measuring the NCD-SSB, TRS, or other DL reference signals in a first DL BWP after receiving the acknowledgment. The cellular baseband processor 1724 may also include units for receiving a negative response rejecting a request from the UE. The cellular baseband processor 1724 may also include units for switching from a first DL BWP or a first UL BWP to a second DL BWP to measure the SSB or reference signal in the second DL BWP after receiving a negative response. These units may be one or more components of the device 1704 configured to perform the functions stated via these units (e.g., component 198). As described above, the device 1704 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, these units may be a TX processor 368, an RX processor 356, and a controller / controller 359 configured to perform the functions stated by these units.

[0126] FIG18 is FIG1800 illustrating an example of the hardware implementation of device 1802. Device 1802 is a base station, a component of a base station, or can implement base station functions. In some embodiments, device 1704 may include baseband unit 1804. Baseband unit 1804 can communicate with UE 104 via cellular RF transceiver 1822. Baseband unit 1804 may include computer-readable media / memory. Baseband unit 1804 is responsible for general processing, including executing software stored on computer-readable media / memory. When executed by baseband unit 1804, the software causes baseband unit 1804 to perform the various functions described above. Computer-readable media / memory can also be used to store data manipulated by baseband unit 1804 when executing software. Baseband unit 1804 also includes receiving component 1830, communication manager 1832, and transmission component 1834. The communication manager 1832 includes one or more of the components shown. The components within the communication manager 1832 may be stored in computer-readable media / memory and / or configured as hardware within the baseband unit 1804. The baseband unit 1804 may be a component of the base station 310 and may include at least one of a TX processor 316, an RX processor 370, and a controller / processor 375, and / or memory 376.

[0127] The communication manager 1832 includes a synchronization component 1842, which can send 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 includes information indicating at least one of the following: a CORESET for the random access procedure or SDT procedure, an SS set, an uplink resource timing set, 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 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 sent by the serving cell in the second DL BWP, for example, as described in conjunction with 1602 in FIG16. The communication manager 1832 may also include a synchronization component 1842, which may receive, in the first UL BWP of the first DL and UL BWP pair, an early indication from the UE for one or more of the following in at least one of the random access messages or SDT messages from the UE: device type, a first request for a first on-demand transmission of the SSB or DL ​​reference signal, or other auxiliary information for self-adjusting scheduling, such as as described in conjunction with 1604 in FIG16.

[0128] The apparatus may include additional components for executing each block of the algorithm in the flowchart of FIG16. Therefore, each block of the flowchart of FIG16 may be executed by components, and the apparatus may include one or more of these components. These components may be one or more hardware components specifically configured to execute the stated program / algorithm, implemented by a processor configured to execute the stated program / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0129] As shown, device 1802 may include various components configured for various functions. In one configuration, device 1802 (and particularly baseband unit 1804) may include a unit for transmitting to a UE in an RRC idle, inactive, or connected state 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 the following: a CORESET, SS set, uplink resource timing set, and an SSB or DL ​​reference signal in a second DL BWP for the random access procedure or SDT procedure, wherein 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. The baseband unit 1804 may also include units for: receiving, in at least one of a random access message or an SDT message from the UE, an early indication from the UE for one or more of the following: device type, a first request for a first on-demand transmission of an SSB or DL ​​reference signal, or other auxiliary information for self-adjusting scheduling in the first UL BWP of the first DL and UL BWP pair. The baseband unit 1804 may also include units for: scheduling downlink transmissions or uplink receptions with the UE using a time offset for the BWP handover delay and measurement gap of the UE for switching from the first DL BWP or the first UL BWP to the second DL BWP to measure the SSB or DL ​​reference signal. The baseband unit 1804 may also include units for: receiving, in a random access message in the first UL BWP, a second request for an on-demand transmission of an NCD-SSB, TRS, or another DL reference signal in the first DL BWP. The baseband unit 1804 may also include units for: responding to a request by sending at least one of the following: an acknowledgment and reference signal configuration for one of the NCD-SSB, TRS, or other DL reference signals; or a response message rejecting a second request. These units may be one or more components of the device 1802 configured to perform the functions stated via these units. As described above, the device 1802 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, these units may be the TX processor 316, the RX processor 370, and the controller / processor 375 configured to perform the functions stated via these units.

[0130] Figure 19 is Figure 1900 illustrating an example of a wireless communication system and access network. The wireless communication system shown includes a decomposed base station architecture. The decomposed base station architecture may include one or more CUs 1910, wherein the CUs 1910 may communicate directly with the core network 1920 via a backhaul link, or indirectly with the core network 1920 via one or more decomposed base station units (e.g., 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 a corresponding midrange link such as an F1 interface. The DUs 1930 may communicate with one or more RUs 1940 via a corresponding fronthaul link. RU 1940 can communicate with the corresponding UE 1904 via one or more radio frequency (RF) access links. In some implementations, UE 1904 can be served by multiple RU 1940s simultaneously.

[0131] Each of these units (i.e., CU 1910, DU 1930, RU 1940, and near-RT RIC 1925, non-RT RIC 1915, and SMO framework 1905) may include or be coupled to one or more interfaces, which are configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of these 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 other units via transmission media. For example, these units may include wired interfaces configured to receive signals from or send signals to one or more other units via wired transmission media. In addition, these units may include a wireless interface, which may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals from or to one or more other units via a wireless transmission medium, or perform both operations.

[0132] In some configurations, the CU 1910 can host one or more higher-level control functions. These control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to transmit signals with other control functions hosted by the CU 1910. The CU 1910 can 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 combinations thereof. In some implementations, the CU 1910 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 1910 can be implemented to communicate with the DU 1930 for network control and signal transmission as needed.

[0133] DU 1930 may correspond to a logic unit that includes one or more base station functions for controlling the operation of one or more RU 1940s. In some configurations, DU 1930 may host one or more of the following, depending on functional partitioning (such as those defined by 3GPP): Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and one or more high-level physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, etc.). In some configurations, DU 1930 may further host one or more low-level PHY layers. Each layer (or module) may be implemented using an interface configured to transmit signals with other layers (and modules) hosted by DU 1930 or with control functions hosted by CU 1910.

[0134] Lower-level functions can be implemented via one or more RU 1940s. In some deployments, based on functional partitioning (such as lower-level functional partitioning), the RU 1940 controlled by the DU 1930 can correspond to a logical node for managed 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. In such architectures, the RU 1940 can be implemented to handle over-the-air (OTA) communication with one or more UE 1904s. In some implementations, the real-time and non-real-time modes of control and user plane communication with the RU 1940 can be controlled by the corresponding DU 1930. In some scenarios, this configuration allows the DU 1930 and CU 1910 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

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

[0136] The non-RT RIC 1915 can be configured to include logical functions that implement the following: non-real-time control and optimization of RAN elements and resources; artificial intelligence (AI) / machine learning (ML) workflows including model training and updates; or policy-based guidance of applications / features in the near-RT RIC 1925. The non-RT RIC 1915 can be coupled to or communicate with the near-RT RIC 1925 (e.g., via the A1 interface). The near-RT RIC 1925 can be configured to include logical functions that implement the following: near real-time control and optimization of RAN elements and resources via data collection and actions on interfaces (e.g., via the E2 interface) that connect one or more CU 1910s, one or more DU 1930s, or both, and O-eNBs to the near-RT RIC 1925.

[0137] In some implementations, in order to generate AI / ML models to be deployed in the near-RT RIC 1925, the non-RT RIC 1915 can receive parameters or external enrichment information from an external server. This information can be used by the near-RT RIC 1925 and can be received from non-network data sources or network functions at the SMO framework 1905 or the non-RT RIC 1915. In some instances, the non-RT RIC 1915 or near-RT RIC 1925 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 1915 can monitor long-term trends and patterns in performance and use AI / ML models to perform corrective actions via the SMO framework 1905 (such as reconfiguration via O1) or via the establishment of RAN management policies (such as A1 policies).

[0138] At least one of CU 1910, DU 1930, and RU 1940 may be referred to as base station 1902. Therefore, base station 1902 may include one or more of CU 1910, DU 1930, and RU 1940 (each component is indicated by dashed lines to show that each component may or may not be included in base station 1902). Base station 1902 provides UE 1904 with an access point to core network 1920. Base station 1902 may include macrocells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Small cells include femtocells, picocells, and microcells. A network including both small cells and macrocells may be referred to as a heterogeneous network. A heterogeneous network may also include a Home Evolutionary Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a Closed User Group (CSG). The communication link between RU 1940 and UE 1904 may include uplink (UL) transmission (also known as reverse link) from UE 1904 to RU 1940 and / or downlink (DL) transmission (also known as forward link) transmission from RU 1940 to UE 1904. The communication link may utilize multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be via one or more carriers. Base station 1902 / UE 1904 may use a spectrum with a bandwidth of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) for each carrier allocated in a total of Y x MHz (x component carriers) for transmission in each direction. These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric relative to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include a primary component carrier and one or more auxiliary component carriers. The primary component carrier may be referred to as the main cell (PCell), and the auxiliary component carriers may be referred to as auxiliary cells (SCells).

[0139] Some UEs 1904 can communicate with each other using a device-to-device (D2D) communication link 1958. The D2D communication link 1958 can use DL / UL Wireless Wide Area Network (WWAN) spectrum. The D2D communication link 1958 can use one or more sideline channels, such as the Physical Sideline Broadcast Channel (PSBCH), Physical Sideline Discovery Channel (PSDCH), Physical Sideline Shared Channel (PSSCH), and Physical Sideline Control Channel (PSCCH). D2D communication can be performed via various wireless D2D communication systems such as Bluetooth, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0140] The wireless communication system may also include a Wi-Fi AP 1950 that communicates with the UE 1904 (also known as a Wi-Fi station (STA)) via a communication link 1954 in, for example, the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the UE 1904 / AP 1950 may perform an idle channel assessment (CCA) before communication to determine whether the channel is available.

[0141] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency range names FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the "below 6 GHz" band in various documents and articles. Similar naming issues sometimes arise regarding FR2, although it differs from the Extremely High Frequency (EHF) band (30 GHz-300 GHz) defined as a "millimeter wave" band by the International Telecommunication Union (ITU), FR2 is often referred to (interchangeably) as the "millimeter wave" band in various documents and articles.

[0142] Frequencies between FR1 and FR2 are generally referred to as intermediate frequency (IF) bands. Recent 5G NR research has designated the operating bands of these IF bands as the frequency range name FR3 (7.125 GHz – 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, and thus can effectively extend the characteristics of FR1 and / or FR2 to the IF band. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation above 52.6 GHz. For example, three higher operating frequency bands have been designated as the frequency range names FR2-2 (52.6 GHz – 71 GHz), FR4 (71 GHz – 1914.25 GHz), and FR5 (114.25 MHz – 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0143] In view of the above, unless otherwise explicitly stated, the terms "below 6 GHz" etc. (if used herein) can broadly refer to frequencies that are less than 6 GHz, frequencies that are within FR1, or frequencies that may include the intermediate frequency band. Furthermore, unless otherwise explicitly stated, the terms "millimeter wave" etc. (if used herein) can broadly refer to frequencies that may include the intermediate frequency band, frequencies that are within FR2, FR4, FR2-2 and / or FR5, or frequencies that are within the EHF band.

[0144] Base station 1902 and UE 1904 may each include multiple antennas (such as antenna components, antenna panels, and / or antenna arrays) to facilitate beamforming. Base station 1902 may transmit beamforming signals 1982 to UE 1904 in one or more transmit directions. UE 1904 may receive beamforming signals from base station 1902 in one or more receive directions. UE 1904 may also transmit beamforming signals 1984 to base station 1902 in one or more transmit directions. Base station 1902 may receive beamforming signals from UE 1904 in one or more receive directions. Base station 1902 / UE 1904 may perform beam training to determine the optimal receive and transmit directions for each of base station 1902 / UE 1904. The transmit and receive directions of base station 1902 may be the same or different. The transmit and receive directions of UE 1904 may be the same or different.

[0145] Base station 1902 may include and / or be referred to as gNB, Node B, eNB, access point, base station transceiver, radio base station, radio transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), TRP, network node, network entity, network device, or some other suitable term. Base station 1902 may be implemented as an Integrated Access and Backhaul (IAB) node, a relay node, a sidelink node, an aggregated (single) base station with baseband units (BBU) (including CU and DU) and RU, or may be implemented as a decomposed base station including one or more of CU, DU, and / or RU.

[0146] The core network 1920 may include Access and Mobility Management Function (AMF) 1961, Communication Management Function (SMF) 1962, User Plane Function (UPF) 1963, Unified Data Management (UDM) 1964, one or more location servers 1968, and other functional entities. AMF 1961 is the control node that handles signal transmission between UE 1904 and the core network 1920. AMF 1961 supports registration management, connection management, mobility management, and other functions. SMF 1962 supports communication management and other functions. UPF 1963 supports packet routing, packet forwarding, and other functions. UDM 1964 supports authentication and Key Agreement (AKA) credential generation, user identity processing, access authorization, and subscription management. One or more location servers 1968 are shown as including Gateway Mobile Location Center (GMLC) 1965 and Location Management Function (LMF) 1966. However, typically, one or more location servers 1968 may include one or more location / positioning servers, which may include one or more of the following: GMLC 1965, LMF 1966, Location Determination Entity (PDE), Serving Mobile Location Center (SMLC), Mobile Location Center (MPC), etc. GMLC 1965 and LMF 1966 support UE positioning services. GMLC 1965 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. LMF 1966 receives measurement and auxiliary information from NG-RAN and UE 1904 via AMF 1961 to calculate the location of UE 1904. NG-RAN may utilize one or more positioning methods to determine the location of UE 1904. Positioning UE 1904 may involve signal measurement, location estimation, and optional speed calculation based on the measurements. Signal measurement may be performed by UE 1904 and / or serving base station 1902. The measured signal may be based on one or more of the following: Satellite Positioning System (SPS) 1970 (e.g., one or more of Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN) or other satellite position / location systems), LTE signal, Wireless Local Area Network (WLAN) signal, Bluetooth signal, Terrestrial Beacon System (TBS), sensor-based information (e.g., barometric sensor, motion sensor), NR Enhanced Cell ID (NR E-CID) method, NR signal (e.g., Multi-Round-Trip Time (Multi-RTT), DL Departure Angle (DL-AoD), DL Time Difference of Arrival (DL-TDOA), UL Time Difference of Arrival (UL-TDOA), and UL Angle of Arrival (UL-AoA) positioning) and / or other systems / signals / sensors.

[0147] Examples of UE 1904 include cellular phones, smartphones, conversation initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, medical devices, implants, sensors / actuators, displays, or any other similarly functional device. Some UEs in UE 1904 may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.). UE 1904 may also be referred to as a station, mobile station, user station, mobile unit, user cell, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile user station, access terminal, mobile terminal, radio terminal, remote terminal, handheld device, user agent, mobile service client, client, or some other suitable term. In some scenarios, the term UE can also be applied to one or more accompanying devices (such as in a device cluster deployment). One or more of these devices can access the network jointly and / or individually.

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

[0149] In some configurations, base station 102 may include synchronization component 1999. In some configurations, synchronization component 1999 may be configured to transmit to a UE in an RRC idle, inactive, or connected state 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 the following: a CORESET, SS set, uplink resource timing set, and an SSB or DL ​​reference signal in a second DL BWP for the random access procedure or SDT procedure, wherein 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 configurations, the synchronization component 1999 may also be configured to: in the first UL BWP of the first DL and UL BWP pair, receive, in at least one of the random access messages or SDT messages from the UE, an early indication from the UE for one or more of the following: device type, a first request for a first on-demand transmission of the SSB or DL ​​reference signal, or other auxiliary information for self-adjusting scheduling. Figure 20 is Figure 2000 illustrating an example of a hardware implementation of network entity 2002. Network entity 2002 may be a BS, a component of a BS, or may implement BS functionality. Network entity 2002 may include at least one of CU 2010, DU 2030, or RU 2040. For example, depending on the layer function processed by component 199, network entity 2002 may include: CU 2010; both CU 2010 and DU 2030; each of CU 2010, DU 2030, and RU 2040; DU 2030; both DU 2030 and RU 2040; or RU 2040. CU 2010 may include CU processor 2012. CU processor 2012 may include on-chip memory 2012'. In some configurations, CU 2010 may also include additional memory module 2014 and communication interface 2018. CU 2010 communicates with DU 2030 via a mid-range link (such as an F1 interface). DU 2030 may include DU processor 2032. DU processor 2032 may include on-chip memory 2032'. In some configurations, DU 2030 may also include an additional memory module 2034 and a communication interface 2038. DU 2030 communicates with RU 2040 via a frontend link. RU 2040 may include an RU processor 2042. RU processor 2042 may include on-chip memory 2042'. In some configurations, RU 2040 may also include an additional memory module 2044, one or more transceivers 2046, an antenna 2080, and a communication interface 2048.RU 2040 communicates with UE 104. On-chip memories 2012', 2032', 2042' and additional memory modules 2014, 2034, 2044 can each be considered as computer-readable media / memory. Each computer-readable media / memory can be non-transitory. Each of processors 2012, 2032, 2042 is responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by the corresponding processor, the software causes the processor to perform the various functions described herein. The computer-readable media / memory can also be used to store data manipulated by the processor while executing software.

[0150] In some configurations, the synchronization component 199 may be configured to 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. This configuration includes information indicating at least one of the following: a CORESET, SS set, uplink resource timing set, and an SSB or DL ​​reference signal in a second DL BWP for the random access procedure or SDT procedure, wherein 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 sent by the serving cell in the second DL BWP. In some configurations, synchronization component 199 may also be configured to receive, in at least one of the random access messages or SDT messages from the UE, an early indication from the UE regarding one or more of the following: device type, a first request for a first on-demand transmission of the SSB or DL ​​reference signal, or other auxiliary information for self-adjusting scheduling in the first UL BWP of the first DL and UL BWP pair. Synchronization component 199 may reside within one or more processors of one or more of CU 2010, DU 2030, and RU 2040. Synchronization component 199 may be one or more hardware components specifically configured to execute the stated program / algorithm, implemented by one or more processors configured to execute the stated program / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. Network entity 2002 may include various components configured for various functions. Network entity 2002 may include units for the following operations: transmitting to a UE in an RRC idle, inactive, or connected state 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 the following: a CORESET, SS set, uplink resource timing set, and an SSB or DL ​​reference signal in a second DL BWP for the random access procedure or SDT procedure, wherein 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. Network entity 2002 may also include a unit for the following operation: in the first UL BWP of the first DL and UL BWP pair, in at least one of the random access messages or SDT messages from the UE, receiving an early indication from the UE for one or more of the following: device type, a first request for a first on-demand transmission of the SSB or DL ​​reference signal, or other auxiliary information for self-adjusting scheduling.Network entity 2002 may also include units for scheduling downlink transmissions or uplink receptions with the UE using a time offset for the BWP handover delay and measurement gap for the UE to measure the SSB or DL ​​reference signal during a handover from the first DL BWP or the first UL BWP to the second DL BWP. Network entity 2002 may also include units for receiving a second request for on-demand transmission of an NCD-SSB, TRS, or another DL reference signal in the first DL BWP, within a random access message in the first UL BWP. Network entity 2002 may also include units for responding to the request by sending at least one of the following: 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. These units may be synchronization components 199 of network entity 2002 configured to perform the functions stated by these units. As described herein, network entity 2002 may include TX processor 316, RX processor 370, and controller / processor 375. Thus, in one configuration, these units may be TX processor 316, RX processor 370, and controller / processor 375 configured to perform the functions stated via these units.

[0151] It should be understood that the specific order or hierarchy of the blocks in the disclosed program / flowchart is a description of the instance methods. It should be understood that the specific order or hierarchy of the blocks in the program / flowchart can be rearranged based on design preferences. Furthermore, some blocks can be combined or omitted. The appended method request provides the elements of various blocks in instance order, and is not limited to the specific order or hierarchy presented.

[0152] The foregoing description is provided to enable those skilled in the art to practice the various modes described herein. Various modifications to these modes will be apparent to those skilled in the art, and the overall principles defined herein can be applied to other modes. Therefore, the claims are not limited to the modes described herein, but are to be given the full scope consistent with the language of the claims. Unless specifically stated otherwise, references to singular elements do not mean "one and only one," but rather "one or more." Terms such as "if," "when," and "at" do not imply a direct temporal relationship or reaction. That is, these phrases (e.g., "when") do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply mean that an action will occur if a condition is met, without requiring a specific or immediate temporal constraint on the occurrence of that action. The word "exemplary" herein is used to mean "serving as an example, illustration, or description." Any mode described herein as "exemplary" is not necessarily to be construed as preferred or superior to other modes. Unless otherwise specified, the term "some" means 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 A, multiple B, or multiple C. In particular, 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 only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may contain one or more members of A, B, or C. A set should be interpreted as a collection of elements, where the elements are numbered one or more. Therefore, for a set X, X will include one or more elements. If the first device receives data from or sends data to the second device, the data may be received / sent directly between the first and second devices, or indirectly between the first and second devices via a set of devices. All structural and functional equivalents of the elements of various forms described herein are expressly incorporated herein by reference and are intended to be covered by the claims, and such structural and functional equivalents are known or will be known to those skilled in the art to which this invention pertains. Furthermore, the disclosure herein is not intended to be offered to the public, regardless of whether such disclosure is expressly stated in the claims. The terms "module," "device," "element," and "equipment," etc., are not substitutes for the term "unit."Therefore, no request element should be interpreted as a functional module unless the element is explicitly stated using the phrase "unit for...".

[0153] As used herein, the phrase “based on” should not be interpreted as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) should be interpreted as “based on at least A”, unless specifically stated differently.

[0154] The following examples are illustrative only and may be combined with, but not limited to, other examples or teachings described herein.

[0155] State 1 is a method for wireless communication at a UE, comprising: receiving configuration for a first DL and UL BWP pair, the configuration including information indicating at least one of a CORESET, an SS set, and a UL resource timing set for an 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, during the RA procedure or SDT procedure, performing time or frequency synchronization using an SSB of a serving cell configured in a second DL BWP or a DL reference signal of a serving cell configured in a second DL BWP.

[0156] State 2 is based on the method of State 1, wherein the first DL BWP does not include the entire SSB sent by the service 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 service cell configured in the second DL BWP.

[0157] State 3 is a method according to any of the states 1-2, wherein the set of UL resource timings in the first uplink BWP of the first DL and UL BWP pair is associated with (e.g., configured with) a spatial relationship configuration of the SSB with the service cell or the DL reference signal in the second DL BWP, and the set of UL resource timings includes one or more of the following: RO for RA procedure, PUSCH timing for RA procedure, SDT timing based on random access or configuration, SRS timing, and PUCCH timing associated with RA procedure or SDT.

[0158] State 4 is the method described according to any of the states 1-3, wherein the configuration for the first DL and UL BWP pair includes information indicating the following: a QCL source, spatial relationship configuration, and synchronization CD-SSB or NCD-SSB in the second DL BWP for (e.g., used as) the UE to perform RA or SDT procedures in the first DL and UL BWP pair. In some states, the spatial relationship configuration for the NCD-SSB and CD-SSB can be the same, because the NCD-SSB and CD-SSB can share the same ssb-positioninBurst information element (IE).

[0159] State 5 is the method described according to any of the states 1-4, wherein the configuration for the first DL and UL BWP pair includes information indicating the following: CSI-RS, PRS or TRS sent by the serving cell in the second DL BWP and used for spatial relationship configuration and synchronization of the RA procedure or SDT procedure of the UE in the RRC idle, inactive or connected state.

[0160] State 6 is the method according to any of the states 1-5, wherein the CORESET and SS set configured in the first DL BWP for the RA procedure or SDT procedure have a QCL relationship with the SSB of the service cell or the DL reference signal in the second DL BWP.

[0161] State 7 is the method according to any of the states 1-6, wherein performing time or frequency synchronization includes: pausing or stopping communication in the first DL BWP or first UL BWP of the first DL and UL BWP pair during the RA procedure or SDT procedure; switching from the first DL BWP or first UL BWP to the second DL BWP to measure the SSB of the service cell or the DL reference signal in the second DL BWP; after measuring the SSB or DL ​​reference signal in the second DL BWP, switching back from the second DL BWP to the first DL BWP or first UL BWP; using the measurements obtained in the second DL BWP for time or frequency synchronization, power control, beam management, timing advance verification, or reselection of uplink resource timing; and resuming or restarting communication in the first DL and UL BWP pair during the RA procedure or SDT procedure.

[0162] State 8 is the method according to any of the states 1-7, wherein the isochronous line for switching from the first DL BWP or the first UL BWP to the second DL BWP is based on one or more of the following: capabilities supported by the UE, device type indicated by the UE, triggering event for BWP switching, or reference SCS associated with the first DL BWP, the first UL BWP and the second DL BWP.

[0163] State 9 is the method described according to any of the states 1-8, and also includes: after initiating the RA procedure or SDT procedure, starting a first timer associated with a BWP handover from the first DL BWP or the first UL BWP to the second DL BWP for measuring the SSB or DL ​​reference signal, wherein the first timer tracks the gap relative to the latest measurement of the SSB or DL ​​reference signal of the UE to the serving cell; after initiating the RA procedure or SDT procedure, starting a second timer associated with the RA procedure or SDT procedure (e.g., which may correspond to the cg-SDT-TimeAlignmentTimerCommon information element or the TimeAlignmentTimer information element), the second timer being configured separately from the first timer, wherein the UE switches from the first DL BWP or the first UL BWP to the second DL BWP to measure the SSB or DL ​​reference signal in response to the expiration of the first timer or the second timer or the failure of the timing advance verification of the SDT procedure; and resetting the first timer after the measurement of the SSB or DL ​​reference signal is completed in the second DL BWP.

[0164] State 10 is the method according to any of the states 1-9, wherein switching from the first DL BWP or the first UL BWP to the second DL BWP also includes: stopping downlink reception in the first DL BWP or uplink transmission in the first UL BWP.

[0165] State 11 is the method according to any of the states 1-10, and also includes: during the RA procedure or SDT procedure, at one or more valid uplink resource opportunities, sending the value of the first timer in a message.

[0166] State 12 is the method according to any of the states 1-11, wherein the UE sends the value of the first timer in the message based on the first timer and the second timer continuing to execute or the successful timing verification of the SDT procedure.

[0167] State 13 is the method according to any of the states 1-12, wherein the switching from the first DL BWP or the first UL BWP to the second DL BWP is performed after the value of the first timer is sent or based on the BWP retuning schedule received from the service cell in system information or dedicated RRC message.

[0168] State 14 is the method according to any of the states 1-13, and also includes: receiving a signal transmission of a report of the value of enabling a first timer from the service cell before sending a message (e.g., which may correspond to the ue-TimerAndConstants information element), wherein the signal transmission is received in system information (e.g., in SIB 1), dedicated RRC message, MAC CE or DCI.

[0169] State 15 is the method according to any of the states 1-14, wherein the UE selectively sends the value of the first timer in the message based on conditions or the occurrence of a triggering event that depend at least on the UE capability, the type of RA procedure or SDT procedure, cell coverage or frequency range.

[0170] State 16 is the method according to any of the states 1-15, and also includes: receiving scheduling information for DL ​​reception or UL transmission, the scheduling information including a time offset in response to the value of a first timer reported by the UE, wherein the time offset provided by the serving cell is not less than the BWP handover delay and the measurement gap of the UE.

[0171] State 17 is the method described according to any of the states 1-16, and also includes: sending a request for RAR window adjustment in an uplink signal or channel associated with the RA procedure or SDT procedure based on the BWP handover delay and the measurement gap of the UE in the second DL BWP.

[0172] State 18 is the method according to any of the states 1-17, wherein the switching from the first DL BWP or the first UL BWP to the second DL BWP is performed after the request is sent or based on the BWP retuning schedule received from the service cell in system information or dedicated RRC messages.

[0173] State 19 is the method according to any of the states 1-18, and also includes: receiving a signal transmission enabling a request from the UE for RAR window adjustment before sending a random access message, wherein the signal transmission is received from the serving cell in system information, dedicated RRC message, MAC CE or DCI.

[0174] State 20 is the method according to any of the states 1-19, wherein the UE selectively sends a request based on the occurrence of a condition or triggering event, the condition or triggering event depending on at least one of the following: UE capability, type of RA procedure or SDT procedure, cell coverage or frequency range.

[0175] State 21 is the method according to any of the states 1-20, and also includes: sending 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 associated with the RA procedure or SDT procedure.

[0176] State 22 is the method according to any of the states 1-21, and also includes: receiving a signal transmission of an enable request from the service cell before sending the request, wherein the signal transmission is received in system information, dedicated RRC message, MAC CE or DCI.

[0177] State 23 is the method described according to any of the states 1-22, wherein the UE sends a request based on the occurrence of a condition or triggering event.

[0178] State 24 is the method according to any of the states 1-23, and also includes: acknowledgment of on-demand transmission of NCD-SSB, TRS or other DL reference signals, wherein performing time or frequency synchronization includes: measuring the NCD-SSB, TRS or other DL reference signals in the first DL BWP after receiving the acknowledgment.

[0179] State 25 is the method described according to any of the states 1-24, and also includes: receiving a negative response to reject the request from the UE; and after receiving the negative response, 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.

[0180] State 26 is a method for radio communication at a base station (e.g., a network node), comprising: transmitting to a UE in an RRC idle, inactive, or connected state 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 the following: a CORESET, SS set, uplink resource timing set, and an SSB or DL ​​reference signal in a second DL BWP for the random access procedure or SDT procedure, wherein 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 service cell in the second DL BWP; and the first UL in the first DL and UL BWP pair In the BWP, in at least one of the random access messages or SDT messages from the UE, an early indication from the UE for one or more of the following: device type, a first request for a first on-demand transmission of an SSB or DL ​​reference signal, or other auxiliary information for self-adjusting scheduling is received.

[0181] State 27 is the method according to State 26, and also includes: receiving in a random access message or SDT message one of the following: the value of an SSB or downlink reference signal timer for the UE measuring service cell associated with a BWP handover from the first DL BWP or the first UL BWP to the second DL BWP, or a second request for RAR window adjustment based on the BWP handover delay and the measurement gap for measuring the SSB or DL ​​reference signal in the second DL BWP; the method also includes: scheduling downlink transmission or uplink reception with the UE using a time offset, the time offset being for the BWP handover delay and measurement gap for the UE to measure the SSB or DL ​​reference signal when handing over from the first DL BWP or the first UL BWP to the second DL BWP.

[0182] State 28 is the method according to any of states 26-27, and also includes: receiving, in a random access message in the first UL BWP, a second request for on-demand transmission of an NCD-SSB, TRS or another DL reference signal in the first DL BWP; and in response to the request, sending at least one of the following: 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.

[0183] State 29 is an apparatus for wireless communication, including information indicating at least one processor coupled to memory and configured to perform the method according to any of states 1 to 25.

[0184] State 30 is a device for wireless communication, including information indicating at least one processor coupled to memory and configured to perform the method according to any of states 26 to 28.

[0185] State 31 is an apparatus for wireless communication, including a unit for performing the method according to any of states 1 to 25.

[0186] State 32 is an apparatus for wireless communication, including a unit for performing the method according to any of states 26 to 28.

[0187] Format 33 is a computer-readable medium storing computer-executable code, wherein when executed by a processor, the code causes the processor to perform the method described according to any of formats 1 to 25.

[0188] Format 34 is a computer-readable medium storing computer-executable code, wherein when executed by a processor, the code causes the processor to perform the method described according to any of formats 26 to 28. [Simplified Explanation of the Diagram]

[0009] Figure 1 is a diagram illustrating an example of a wireless communication system and access network.

[0010] Figure 2A is a diagram showing an example of a first message frame of various states according to the content of this case.

[0011] Figure 2B is a diagram showing an example of a DL channel within a subframe of various states according to the content of this case.

[0012] Figure 2C is a diagram showing an example of a second message frame according to the various states of the case.

[0013] Figure 2D is a diagram showing an example of a UL channel within a subframe according to the various states of the present case.

[0014] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0015] Figure 4 is a diagram showing an instance resource with multiple BWPs configured within a frequency span of the carrier bandwidth.

[0016] Figure 5 is a diagram showing the initial downlink BWP.

[0017] Figure 6 is a diagram showing a four-step random access procedure (4-step RACH).

[0018] Figure 7 is a diagram showing a two-step random access procedure (2-step RACH).

[0019] Figure 8 is a graph showing the isochron of instances associated with the 4-step RACH.

[0020] Figures 9A and 9B are diagrams showing example isochrones associated with a retuning timer.

[0021] Figure 10 is a graph showing the instance isochrones associated with retuning.

[0022] Figure 11 is a graph showing the instance isochrones associated with retuning.

[0023] Figure 10 is a graph showing the instance isochrones associated with retuning.

[0024] Figure 11 is a graph showing the instance isochrones associated with retuning.

[0025] Figure 12 is a graph showing the instance isochrones associated with retuning.

[0026] Figure 13 is a graph showing the instance isochrones associated with the 2-step RACH.

[0027] Figure 14 is a graph showing the instance isochrones associated with the 4-step RACH.

[0028] Figure 15 is a flowchart of the wireless communication method.

[0029] Figure 16 is a flowchart of the wireless communication method.

[0030] Figure 17 is a diagram illustrating an example of a hardware implementation method for an instance device.

[0031] Figure 18 is a diagram illustrating an example of a hardware implementation method for an instance device.

[0032] Figure 19 is a diagram illustrating an example of a wireless communication system and access network.

[0033] Figure 20 is a diagram illustrating an example of a hardware implementation for a network entity. [Biomaterial Storage]

[0190] Domestic storage information (please note in order of storage institution, date, and number): None. International storage information (please note in order of storage country, institution, date, and number): None.

Claims

1. An apparatus for wireless communication at a user equipment (UE), comprising: One memory; and at least one processor coupled to the memory and 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 UL resource timing set for a random access (RA) procedure or a small data transfer (SDT) procedure, the first DL and UL BWP pair including a first DL BWP and a first UL BWP; initiate at least one of the RA procedure or the SDT procedure in the first DL and UL BWP pair; and, during the RA procedure or the SDT procedure, perform time or frequency synchronization 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, wherein the configuration for the first DL and UL BWP pair includes information indicating the following: in the second DL BWP and for the UE in the first DL and UL... BWP executes the RA procedure or the SDT procedure using a quasi-co-located (QCL) source, a spatial relation configuration, and a synchronization reference signal, either a cell-defined SSB (CD-SSB) or a non-cell-defined SSB (NCD-SSB).

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

3. The apparatus according to claim 1, wherein the UL resource timing set in a first uplink BWP of the first DL and UL BWP pair is associated with a spatial relationship configuration of the DL reference signal in the SSB or the second DL BWP having the service cell, the UL resource timing set including one or more of the following: a physical random access channel (PRACH) timing (RO) for the RA procedure, a physical uplink shared channel (PUSCH) timing for the RA procedure, an SDT timing permitted based on random access or a configuration, a probe reference signal (SRS) timing, or a physical uplink control channel (PUCCH) timing associated with the RA procedure or the SDT procedure.

4. The apparatus according to claim 1, wherein the configuration for the first DL and UL BWP pair includes information indicating the following: a channel state information reference signal (CSI-RS), a positioning reference signal (PRS), or a tracking reference signal (TRS) transmitted by the serving cell in the second DL BWP and used by the UE in a radio resource control (RRC) idle, inactive, or connected state for spatial relation configuration and synchronization of the RA procedure or the SDT procedure.

5. The apparatus according to claim 1, wherein the CORESET and the SS set configured in the first DL BWP for the RA program or the SDT program have a quasi-co-address (QCL) relationship with the SSB of the service cell or the DL reference signal of the second DL BWP.

6. The apparatus according to claim 1, wherein, in order to perform the time or frequency synchronization, the at least one processor is also configured to: suspend or stop communication in the first DL BWP or a first UL BWP of the first DL and UL BWP pair during the RA procedure or the SDT procedure; switch 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 the service cell or the second DL BWP; after measuring the SSB or the DL reference signal in the second DL BWP, switch back from the second DL BWP to the first DL BWP or the first UL BWP; use the measurement in the second DL BWP for the time or frequency synchronization, power control, beam management, timing advance verification, or reselection of uplink resource timing; and resume or restart communication in the first DL and UL BWP pair during the RA procedure or the SDT procedure.

7. The apparatus according to claim 6, wherein an isochronous line for switching from the first DL BWP or the first UL BWP to the second DL BWP is based on one or more of the following: a capability supported by the UE, a device type indicated by the UE, a triggering event for BWP handover, or a reference subcarrier spacing (SCS) associated with the first DL BWP, the first UL BWP, and the second DL BWP.

8. The apparatus according to claim 6, wherein the at least one processor is also configured to: after initiating the RA procedure or the SDT procedure, start a first timer associated with a BWP handover from the first DL BWP or the first UL BWP to the second DL BWP for measuring the SSB or the DL reference signal, wherein the first timer tracks a gap relative to the UE's latest measurement of the SSB or the DL reference signal of the serving cell; after initiating the RA procedure or the SDT procedure, start a second timer associated with the RA procedure or the SDT procedure, the second timer being configured separately from the first timer, wherein in response to the expiration of the first timer or the second timer or a certain time advance verification failure of the SDT procedure, the UE switches from the first DL BWP or the first UL BWP to the second DL BWP to measure the SSB or the DL reference signal; and after the measurement of the SSB or the DL reference signal is completed in the second DL BWP, reset the first timer.

9. The apparatus according to claim 8, wherein, in order to switch from the first DL BWP or the first UL BWP to the second DL BWP, the at least one processor is also configured to: stop downlink reception in the first DL BWP or uplink transmission in the first UL BWP.

10. The apparatus according to claim 8, wherein the at least one processor is also configured to: send a value of the first timer in a message during one or more UL resource times during the RA procedure or the SDT procedure.

11. According to the apparatus of request item 10, the at least one processor is also configured to send the value of the first timer in the message based on the determination that the first timer and the second timer are executing.

12. The apparatus according to claim 10, wherein, in order to switch from the first DL BWP or the first UL BWP to the second DL BWP, the at least one processor is also configured to: switch from the first DL BWP or the first UL BWP to the second DL BWP after transmitting the value of the first timer, or based on a BWP retuning schedule received from the service cell in system information or a dedicated radio resource control (RRC) message.

13. The apparatus according to claim 10, wherein the at least one processor is also configured to: receive, before sending the message, a signal transmission of a report activating the value of the first timer from the service cell, wherein the signal transmission is received in system information, a dedicated radio resource control (RRC) message, a media access control element (MAC CE) or downlink control information (DCI).

14. The apparatus according to request item 10, wherein the at least one processor is also configured to selectively send the value of the first timer in the message based on a condition or the occurrence of a triggering event that depends at least on a UE capability, a type of the RA procedure or the SDT procedure, a cell coverage or a frequency range.

15. The apparatus according to claim 10, wherein the at least one processor is also configured to: receive scheduling information for DL ​​reception or UL transmission, the scheduling information including a time offset in response to the value of the first timer reported by the UE, wherein the time offset provided by the serving cell is not less than a BWP handover delay and a measurement gap of the UE.

16. The apparatus according to request item 6, wherein the at least one processor is also configured to: send a request for adjustment of the Random Access Response (RAR) window in an uplink signal associated with the RA procedure or the SDT procedure, based on a BWP handover delay and a measurement gap of the UE in the second DL BWP.

17. The apparatus according to claim 16, wherein, in order to switch from the first DL BWP or the first UL BWP to the second DL BWP, the at least one processor is also configured to: switch from the first DL BWP or the first UL BWP to the second DL BWP after sending the request, or based on a BWP retuning schedule received from the service cell in system information or a dedicated radio resource control (RRC) message.

18. The apparatus according to request 16, wherein the at least one processor is also configured to: receive a signal transmission enabling the request for RAR window adjustment from the UE before sending a random access message, wherein the signal transmission is received from the serving cell in system information, a dedicated radio resource control (RRC) message, a media access control element (MAC CE) or downlink control information (DCI).

19. The apparatus according to request item 16, wherein the at least one processor is also configured to selectively send the request based on the occurrence of a condition or a triggering event, the condition or triggering event depending on at least one of the following: a UE capability, a type of the RA procedure or the SDT procedure, a cell coverage or a frequency range.

20. The apparatus according to claim 1, wherein the at least one processor is also configured to: transmit, in an uplink signal associated with the RA program or the SDT program, 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.

21. The apparatus according to request 20, wherein the at least one processor is also configured to: receive, before sending the request, a signal transmission enabling the request from the service cell, wherein the signal transmission is received in system information, a dedicated radio resource control (RRC) message, a media access control element (MAC CE), or downlink control information (DCI).

22. The apparatus according to request 20, wherein the at least one processor is also configured to send the request based on the occurrence of a condition or a triggering event.

23. The apparatus according to claim 20, wherein the at least one processor is also configured to: receive an acknowledgment of the on-demand transmission for the NCD-SSB, the TRS, or the other DL reference signal, wherein performing the time or frequency synchronization includes: After receiving the confirmation, measure the NCD-SSB, TRS, or other DL reference signal in the first DL BWP.

24. The apparatus according to request 20, wherein the at least one processor is also configured to: receive a negative response rejecting the request from the UE; and, after receiving the negative response, switch from the first DL BWP or the first UL BWP to the second DL BWP to measure the SSB or the reference signal in the second DL BWP.

25. An apparatus for wireless communication at a base station, comprising: One memory; and at least one processor coupled to the memory and configured to: 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 transfer (SDT) procedure in a first downlink (DL) and uplink (UL) bandwidth portion (BWP) pair, the configuration including information indicating at least one of the following: a control resource set (CORESET), a search space (SS) set, an uplink resource timing set, and a synchronization signal block (SSB) or DL ​​reference signal in a second DL BWP for the random access procedure or the SDT procedure, wherein a first DL BWP of the first DL and UL BWP pair does not include the SSB, and during the random access procedure or the SDT procedure, a quasi-co-location (QCL) source, a spatial relationship configuration, and synchronization for the UE are based on the SSB or the DL reference signal transmitted by a service cell in the second DL BWP; and a first UL in the first DL and UL BWP pair In the BWP, in at least one of a random access message or an SDT message from the UE, an early indication from the UE for one or more of the following: a device type, a first request for a first on-demand transmission for the SSB or the DL reference signal, or other auxiliary information for self-adjusting scheduling is received.

26. The apparatus according to claim 25, wherein the at least one processor is also configured to: receive in the random access message or the SDT message one of the following: a value of a timer for the UE to measure the SSB or the downlink reference signal of the serving cell in connection with a BWP handover from the first DL BWP or the first UL BWP to the second DL BWP, or a second request for a random access response (RAR) window adjustment based on a BWP handover delay and a measurement gap for measuring the SSB or the DL reference signal in the second DL BWP, wherein the at least one processor is also configured to: schedule downlink transmission or uplink reception with the UE using a time offset for the BWP handover delay and the measurement gap for the UE to measure the SSB or the DL reference signal during a handover from the first DL BWP or the first UL BWP to the second DL BWP.

27. The apparatus according to claim 25, wherein the at least one processor is also configured to: receive, in the random access message in the first UL BWP, a second request for on-demand transmission of a non-cell-defined SSB (NCD-SSB), a tracking reference signal (TRS), or another DL reference signal in the first DL BWP; and in response to the request, send at least one of the following: an acknowledgment and a reference signal configuration for one of the NCD-SSB, the TRS, or the other DL reference signal, or a response message rejecting the second request.

28. A method of wireless communication at a user equipment (UE), comprising the steps of: 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 UL resource timing set for a random access (RA) procedure or a small data transfer (SDT) procedure; initiating at least one of the RA procedure or the 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 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 in a first DL BWP of the first DL and UL BWP pair, wherein the configuration for the first DL and UL BWP pair includes information indicating the following: in the second DL BWP and for the UE in the first DL and UL BWP pair BWP executes the RA procedure or the SDT procedure using a quasi-co-located (QCL) source, a spatial relation configuration, and a synchronization reference signal, either a cell-defined SSB (CD-SSB) or a non-cell-defined SSB (NCD-SSB).

29. A method of wireless communication at a base station, comprising the steps of: transmitting 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 transfer (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), a search space (SS) set, an uplink resource timing set, and a synchronization signal block (SSB) or DL ​​reference signal in a second DL BWP for the random access procedure or the SDT procedure, wherein a first DL BWP of the first DL and UL BWP pair does not include the SSB, and during the random access procedure or the SDT procedure, a quasi-co-location (QCL) source, a spatial relationship configuration, and synchronization for the UE are based on the SSB or the DL reference signal transmitted by a serving cell in the second DL BWP; and a first UL in the first DL and UL BWP pair In the BWP, in at least one of a random access message or an SDT message from the UE, an early indication from the UE for one or more of the following: a device type, a first request for a first on-demand transmission for the SSB or the DL reference signal, or other auxiliary information for self-adjusting scheduling is received.

Images