Marking symbols and verifying non-cell-defined synchronization signal blocks and random access channel opportunities

Abstract

The present disclosure provides systems, methods, and devices for wireless communication that support marking symbols and verification of non-cell-defined synchronization signal block (NCD-SSB) and random access channel (RACH) opportunities within a 5G new radio (NR) network. In a first aspect, a method of wireless communication includes a UE obtaining an uplink-downlink configuration for one or more slots, identifying an NCD-SSB configuration for an NCD-SSB transmission, and identifying a bandwidth configuration for a bandwidth portion (BWP) allocated to the UE and a configuration for a cell-defined synchronization signal block (CD-SSB) transmission. The UE may mark the flexible symbol as a downlink symbol in response to an NCD-SSB symbol or a CD-SSB symbol overlapping with the configured flexible symbol. Other aspects and features are also claimed and described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to co-pending U.S. patent application No. 18 / 447,794, filed on August 10, 2023, entitled “MARKING SYMBOLS AND VALIDATION OF NON-CELL-DEFINING SYNCHRONIZATION SIGNAL BLOCK AND RANDOMACCESS CHANNELOCCASIONS,” and co-pending U.S. provisional application No. 63 / 371,283, filed on August 12, 2022, entitled “MARKING SYMBOLS AND VALIDATION OF NON-CELL-DEFINING SYNCHRONIZATION SIGNAL BLOCK AND RANDOMACCESS CHANNEL OCCASIONS,” the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communication systems, and more particularly to 5G NR operations. Some features enable and provide improved communications, including marking symbols and validating non-cell defined synchronization signal blocks (NCD-SSBs) and random access channel (RACH) opportunities. Background Art

[0004] Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, messaging, broadcast, etc. These wireless networks may be multiple-access networks capable of supporting multiple users by sharing the available network resources. Such networks may be multiple-access networks capable of supporting communication for multiple users by sharing the available network resources.

[0005] A wireless communication network may include several components. These components may include wireless communication devices, such as network entities, base stations (e.g., base stations or node Bs) that may support communication for multiple user equipments (UEs). UEs may communicate with network entities via downlinks and uplinks. A downlink (or forward link) refers to a communication link from a network entity to a UE, and an uplink (or reverse link) refers to a communication link from a UE to a network entity.

[0006] A network entity may send data and control information to a UE on a downlink, or receive data and control information from a UE on an uplink. On the downlink, transmissions from a network entity may encounter interference caused by transmissions from neighboring network entities or other wireless radio frequency (RF) transmitters. On the uplink, transmissions from a UE may encounter interference from uplink transmissions from other UEs communicating with neighboring network entities or from other wireless RF transmitters. Such interference may degrade performance on both the downlink and uplink.

[0007] As the demand for mobile broadband access continues to grow, the potential for interference and congested networks grows with more UEs accessing long-range wireless communication networks and more short-range wireless systems deployed in communities. Research and development continues to advance wireless technologies to not only meet the growing demand for mobile broadband access, but also to improve and enhance the user experience with mobile communications. Summary of the invention

[0008] The following summarizes some aspects of the present disclosure to provide a basic understanding of the technology discussed. This summary is not an exhaustive overview of all expected features of the present disclosure, and is neither intended to identify key or important elements of all aspects of the present disclosure, nor to define the scope of any or all aspects of the present disclosure. Its sole purpose is to give some concepts of one or more aspects of the present disclosure in a summarized form as a prelude to more specific embodiments presented later.

[0009] In one aspect of the present disclosure, a method for wireless communication includes: obtaining a time division duplex (TDD) uplink-downlink symbol configuration, wherein the TDD uplink-downlink symbol configuration identifies a pattern of uplink symbols, downlink symbols, and flexible symbols on one or more time slots of a carrier bandwidth; receiving a bandwidth configuration identifying a reduced capacity (RedCap) specific bandwidth part (BWP) allocated to the UE within the carrier bandwidth and a configuration for cell definition synchronization signal block (CD-SSB) transmission; receiving a non-cell definition synchronization signal block (NCD-SSB) configuration identifying at least a frequency of a non-cell definition synchronization signal block (NCD-SSB) transmission and a time offset of the NCD-SSB transmission relative to the CD-SSB transmission; and marking the configured flexible symbol as a downlink symbol in response to one or more of the NCD-SSB symbols of the NCD-SSB transmission or the CD-SSB symbols of the CD-SSB transmission overlapping with a configured flexible symbol of the TDD uplink-downlink symbol configuration.

[0010] In an additional aspect of the present disclosure, a method for wireless communication includes: obtaining a TDD uplink-downlink symbol configuration, wherein the TDD uplink-downlink symbol configuration identifies a pattern of uplink symbols, downlink symbols, and flexible symbols on one or more time slots of a carrier bandwidth; receiving a bandwidth configuration identifying a RedCap-specific BWP allocated to the UE within the carrier bandwidth and a configuration for CD-SSB transmission; receiving an NCD-SSB configuration identifying at least a frequency of an NCD-SSB transmission and a time offset of the NCD-SSB transmission relative to the CD-SSB transmission; and validating the one or more NCD-SSB symbols as invalid in response to one or more NCD-SSB symbols of a plurality of NCD-SSB symbols scheduled according to the NCD-SSB configuration overlapping with one or more configured uplink symbols of the TDD uplink-downlink symbol configuration.

[0011] In an additional aspect of the present disclosure, a method for wireless communication includes: obtaining a PRACH configuration, wherein the PRACH configuration identifies multiple RACH opportunities within a RACH time slot; receiving a bandwidth configuration identifying a RedCap-specific BWP allocated to the UE within a carrier bandwidth and a configuration for CD-SSB transmission; receiving an NCD-SSB configuration identifying at least a frequency of an NCD-SSB transmission and a time offset of the NCD-SSB transmission relative to the CD-SSB transmission; and validating the RACH opportunity as invalid in response to a conflict between a RACH opportunity among the multiple RACH opportunities and one of the NCD-SSB symbols of the NCD-SSB transmission, or the CD-SSB symbol of the CD-SSB transmission, or a combination of the NCD-SSB symbol and the CD-SSB symbol.

[0012] In an additional aspect of the present disclosure, a UE includes: at least one processor; and a memory coupled to the at least one processor. The at least one processor is configured to: obtain a TDD uplink-downlink symbol configuration, wherein the TDD uplink-downlink symbol configuration identifies a pattern of uplink symbols, downlink symbols, and flexible symbols on one or more time slots of the carrier bandwidth; receive a bandwidth configuration identifying a RedCap-specific BWP allocated to the UE within the carrier bandwidth and a configuration for CD-SSB transmission; receive an NCD-SSB configuration identifying at least a frequency of NCD-SSB transmission and a time offset of the NCD-SSB transmission relative to the CD-SSB transmission; and in response to one or more of the NCD-SSB symbols of the NCD-SSB transmission or the CD-SSB symbols of the CD-SSB transmission overlapping with a configured flexible symbol of the TDD uplink-downlink symbol configuration, use the configured flexible symbol to be marked as a downlink symbol.

[0013] In an additional aspect of the present disclosure, a UE includes: at least one processor; and a memory coupled to the at least one processor. The at least one processor is configured to: obtain a TDD uplink-downlink symbol configuration, wherein the TDD uplink-downlink symbol configuration identifies a pattern of uplink symbols, downlink symbols, and flexible symbols on one or more time slots of a carrier bandwidth; receive a bandwidth configuration identifying a RedCap-specific BWP allocated to the UE within the carrier bandwidth and a configuration for CD-SSB transmission; receive an NCD-SSB configuration identifying at least a frequency of NCD-SSB transmission and a time offset of the NCD-SSB transmission relative to the CD-SSB transmission; and verify the one or more NCD-SSB symbols as invalid in response to one or more NCD-SSB symbols of a plurality of NCD-SSB symbols scheduled according to the NCD-SSB configuration overlapping with one or more configured uplink symbols of the TDD uplink-downlink symbol configuration.

[0014] In an additional aspect of the present disclosure, a UE includes: at least one processor; and a memory coupled to the at least one processor. The at least one processor is configured to: obtain a PRACH configuration, wherein the PRACH configuration identifies a plurality of RACH opportunities within a RACH time slot; receive a bandwidth configuration identifying a RedCap-specific BWP allocated to the UE within a carrier bandwidth and a configuration for CD-SSB transmission; receive an NCD-SSB configuration identifying at least a frequency of an NCD-SSB transmission and a time offset of the NCD-SSB transmission relative to the CD-SSB transmission; and verify the RACH opportunity as invalid in response to a conflict between a RACH opportunity in the plurality of RACH opportunities and an NCD-SSB symbol of the NCD-SSB transmission, a CD-SSB symbol of the CD-SSB transmission, or a combination of the NCD-SSB symbol and the CD-SSB symbol.

[0015] In additional aspects of the present disclosure, a UE includes: a component for obtaining a TDD uplink-downlink symbol configuration, wherein the TDD uplink-downlink symbol configuration identifies a pattern of uplink symbols, downlink symbols, and flexible symbols on one or more time slots of a carrier bandwidth; a component for receiving a bandwidth configuration identifying a RedCap-specific BWP allocated to the UE within the carrier bandwidth and a configuration for CD-SSB transmission; a component for receiving an NCD-SSB configuration identifying at least a frequency of an NCD-SSB transmission and a time offset of the NCD-SSB transmission relative to the CD-SSB transmission; and a component for marking a configured flexible symbol as a downlink symbol in response to one or more of the NCD-SSB symbols of the NCD-SSB transmission or the CD-SSB symbols of the CD-SSB transmission overlapping with a configured flexible symbol of the TDD uplink-downlink symbol configuration.

[0016] In additional aspects of the present disclosure, a UE includes: a component for obtaining a TDD uplink-downlink symbol configuration, wherein the TDD uplink-downlink symbol configuration identifies a pattern of uplink symbols, downlink symbols, and flexible symbols on one or more time slots of a carrier bandwidth; a component for receiving a bandwidth configuration identifying a RedCap-specific BWP allocated to the UE within the carrier bandwidth and a configuration for CD-SSB transmission; a component for receiving an NCD-SSB configuration identifying at least a frequency of an NCD-SSB transmission and a time offset of the NCD-SSB transmission relative to the CD-SSB transmission; and a component for validating one or more NCD-SSB symbols as invalid in response to one or more NCD-SSB symbols of a plurality of NCD-SSB symbols scheduled according to the NCD-SSB configuration overlapping with one or more configured uplink symbols of the TDD uplink-downlink symbol configuration.

[0017] In additional aspects of the present disclosure, a UE includes: a component for obtaining a PRACH configuration, wherein the PRACH configuration identifies multiple RACH opportunities within a RACH time slot; a component for receiving a bandwidth configuration identifying a RedCap-specific BWP allocated to the UE within a carrier bandwidth and a configuration for CD-SSB transmission; a component for receiving an NCD-SSB configuration identifying at least a frequency of an NCD-SSB transmission and a time offset of the NCD-SSB transmission relative to the CD-SSB transmission; and a component for validating the RACH opportunity as invalid in response to a conflict between a RACH opportunity among the multiple RACH opportunities and one of the NCD-SSB symbols of the NCD-SSB transmission, or the CD-SSB symbol of the CD-SSB transmission, or a combination of the NCD-SSB symbol and the CD-SSB symbol.

[0018] In an additional aspect of the present disclosure, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to perform operations. The operations include: obtaining a TDD uplink-downlink symbol configuration, wherein the TDD uplink-downlink symbol configuration identifies a pattern of uplink symbols, downlink symbols, and flexible symbols on one or more time slots of a carrier bandwidth; receiving a bandwidth configuration that identifies a RedCap-specific BWP allocated to the UE within the carrier bandwidth and a configuration for CD-SSB transmission; receiving an NCD-SSB configuration that at least identifies a frequency of an NCD-SSB transmission and a time offset of the NCD-SSB transmission relative to the CD-SSB transmission; and marking the configured flexible symbol as a downlink symbol in response to one or more of the NCD-SSB symbol of the NCD-SSB transmission or the CD-SSB symbol of the CD-SSB transmission overlapping with a configured flexible symbol of the TDD uplink-downlink symbol configuration.

[0019] In an additional aspect of the present disclosure, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to perform operations. The operations include: obtaining a TDD uplink-downlink symbol configuration, wherein the TDD uplink-downlink symbol configuration identifies a pattern of uplink symbols, downlink symbols, and flexible symbols on one or more time slots of a carrier bandwidth; receiving a bandwidth configuration that identifies a RedCap-specific BWP allocated to the UE within the carrier bandwidth and a configuration for CD-SSB transmission; receiving an NCD-SSB configuration that at least identifies a frequency of NCD-SSB transmission and a time offset of the NCD-SSB transmission relative to the CD-SSB transmission; and verifying that one or more NCD-SSB symbols of a plurality of NCD-SSB symbols scheduled according to the NCD-SSB configuration overlap with one or more configured uplink symbols of the TDD uplink-downlink symbol configuration as invalid.

[0020] In an additional aspect of the present disclosure, a non-transitory computer-readable medium stores instructions that, when executed by a processor (e.g., directly, indirectly, after preprocessing, without preprocessing), cause the processor to perform operations. The operations include: obtaining a PRACH configuration, wherein the PRACH configuration identifies multiple RACH opportunities within a RACH time slot; receiving a bandwidth configuration that identifies a RedCap-specific BWP allocated to a UE within a carrier bandwidth and a configuration for CD-SSB transmission; receiving an NCD-SSB configuration that identifies at least a frequency of an NCD-SSB transmission and a time offset of the NCD-SSB transmission relative to the CD-SSB transmission; and validating the RACH opportunity as invalid in response to a conflict between a RACH opportunity in the multiple RACH opportunities and one of an NCD-SSB symbol of the NCD-SSB transmission, a CD-SSB symbol of the CD-SSB transmission, or a combination of the NCD-SSB symbol and the CD-SSB symbol.

[0021] The features and technical advantages of the examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as the basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein (both their organization and methods of operation) and the associated advantages will be better understood according to the following description. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.

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

[0023] A further understanding of the nature and advantages of the present disclosure may be achieved by reference to the following drawings. In the drawings, similar components or features may have the same reference label. In addition, components of the same type may be distinguished by adding a dash and a second label to distinguish between similar components after the reference label. Where only the first reference label is used in the specification, the description applies to any one of the similar components having the same first reference label, regardless of the second reference label.

[0024] Figure 1 is a block diagram illustrating example details of an example wireless communication system supporting updated 5G NR operations associated with repeated control signaling configurations according to one or more aspects.

[0025] Figure 2 is a block diagram illustrating an example of a base station and a user equipment (UE) that mark symbols and verify non-cell defined synchronization signal blocks (NCD-SSBs) and random access channel (RACH) opportunities according to one or more aspects.

[0026] Figure 3is a diagram illustrating a 5G NR network configured to support marking of symbols and validation of NCD-SSB and RACH opportunities in accordance with various aspects of the present disclosure.

[0027] Figure 4 is a flow diagram of an example process for marking symbols in support of one or more aspects and validating NCD-SSB for RedCap UE operations.

[0028] Figure 5 is a diagram illustrating a 5G NR network configured to support marking of symbols and verification of NCD-SSB in accordance with various aspects of the present disclosure.

[0029] Figure 6 is a flow chart illustrating an example process for marking symbols and validating NCD-SSBs according to one or more aspects.

[0030] Fig. 7A is a diagram illustrating a 5G NR network configured to support marking of symbols and verification of NCD-SSB in accordance with various aspects of the present disclosure.

[0031] Figure 7B is a diagram illustrating an extended time period of a 5G NR network configured to support marking of symbols and verification of NCD-SSB according to various aspects of the present disclosure.

[0032] Figure 8 is a flow chart illustrating an example process 80 for marking symbols and validating NCD-SSBs in accordance with one or more aspects.

[0033] Fig. 9 is a diagram illustrating a 5G NR network configured to support validation of RACH opportunities in accordance with various aspects of the present disclosure.

[0034] Fig.10 is a diagram illustrating a 5G NR network configured to support validation of RACH opportunities in accordance with various aspects of the present disclosure.

[0035] Fig.11 is a block diagram illustrating an example UE configured to support marking of symbols and validation of NCD-SSB according to one or more aspects.

[0036] The same reference numbers and designations in different drawings indicate the same elements. DETAILED DESCRIPTION

[0037] The specific embodiments described below in conjunction with the accompanying drawings are intended as descriptions of various configurations and are not intended to limit the scope of the present disclosure. Instead, the specific embodiments include specific details for providing a thorough understanding of the subject matter of the present invention. It will be apparent to those skilled in the art that these specific details are not required in every case, and in some cases, structures and components are shown in block diagram form for clarity of presentation.

[0038] The present disclosure provides systems, devices, methods and computer-readable media that support marking symbols and verifying non-cell defined synchronization signal blocks (NCD-SSBs) and random access channels (RACH) timings. Specific implementations of the subject matter described in the present disclosure may be implemented to achieve one or more of the following potential advantages or benefits. In some aspects, the present disclosure provides techniques for marking symbols and verifying NCD-SSB and RACH timings. Various aspects provide the UE with the following capabilities: marking symbols and verifying NCD-SSB transmissions using NCD-SSB transmissions other than CD-SSB transmissions, and verifying RACH timings as valid using NCD-SSB transmissions other than CD-SSB transmissions. Because the RedCap-specific bandwidth part (BWP) may not include CD-SSB transmissions, the additional use of NCD-SSB symbols can assist the UE in beam mobility (e.g., radio link monitoring (RLM) / beam fault detection (BFD) / random access channel (RACH), etc.) and timing operations.

[0039] The present disclosure as a whole relates to providing or participating in authorized shared access between two or more wireless devices in one or more wireless communication systems (also referred to as wireless communication networks). In various specific implementations, the various techniques and devices can be used in wireless communication networks, such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, fifth generation (5G) or new radio (NR) networks (sometimes referred to as "5G NR" networks, systems or devices) and other communication networks. As described herein, the terms "network" and "system" can be used interchangeably.

[0040] A CDMA network may implement, for example, a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband CDMA (W-CDMA) and Low Chip Rate (LCR). CDMA2000 covers IS-2000, IS-95, and IS-856 standards.

[0041] For example, a TDMA network can implement radio technologies such as the Global System for Mobile Communications (GSM). The Third Generation Partnership Project (3GPP) defines the standards for the GSM EDGE (Enhanced Data Rate GSM Evolution) Radio Access Network (RAN) (also known as GERAN). GERAN is a GSM / EDGE radio component, together with a network connecting network entities (e.g., Ater interface and Abis interface) and network entity controllers (A interface, etc.). The radio access network represents a component of the GSM network, through which phone calls and packet data are routed from the public switched telephone network (PSTN) and the Internet to subscriber phones (also known as user terminals or user equipment (UE)) and from subscriber phones to the PSTN and the Internet. The network of a mobile phone operator may include one or more GERANs, which may be coupled with UTRAN in the case of a UMTS / GSM network. Additionally, the operator network may also include one or more LTE networks, or one or more other networks. Various network types may use different radio access technologies (RATs) and RANs.

[0042] OFDMA network can realize radio technology such as Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM, etc. UTRA, E-UTRA and GSM are part of Universal Mobile Telecommunications System (UMTS). Specifically, Long Term Evolution (LTE) is a UMTS version using E-UTRA. UTRA, E-UTRA, GSM, UMTS and LTE are described in documents provided by an organization named "3rd Generation Partnership Project" (3GPP), and cdma2000 is described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). These various radio technologies and standards are known or under development. For example, 3GPP is a collaboration between telecommunication association groups with the goal of defining a globally applicable third generation (3G) mobile phone specification. 3GPP LTE is a 3GPP plan with the goal of improving the UMTS mobile phone standard. 3GPP can define the specifications of next generation mobile networks, mobile systems and mobile devices. The present disclosure may describe certain aspects with reference to LTE, 4G or 5G NR technology; however, the description is not intended to be limited to a particular technology or application, and one or more aspects described with reference to one technology may be understood to be applicable to another technology. Additionally, one or more aspects of the present disclosure may relate to shared access to wireless spectrum between networks using different radio access technologies or radio air interfaces.

[0043] 5G networks are expected to have diverse deployments, diverse spectrum, and diverse services and devices that can be implemented using a unified air interface based on OFDM. To achieve these goals, in addition to developing new radio technologies for 5GNR networks, further enhancements to LTE and LTE-A are also being considered. 5GNR will be able to scale to provide coverage (1) to massive Internet of Things (IoT), with ultra-high density (e.g., about 1M nodes / km 2 ), ultra-low complexity (e.g., about 10s of bits / sec), ultra-low power consumption (e.g., about 10+ years of battery life), and deep coverage with the ability to reach challenging locations; (2) including mission-critical control with strong security to protect sensitive personal, financial, or classified information, ultra-high reliability (e.g., about 99.9999% reliability), ultra-low latency (e.g., about 1 millisecond (ms)), and users with a wide range of mobility or lack of mobility; and (3) providing services with enhanced mobile broadband (including extremely high capacity (e.g., about 10Tbps / km 2 ), coverage of extremely high data rates (e.g., multi-Gbps rates, 100+Mbps user experience rates), and deep awareness with advanced discovery and optimization).

[0044] Devices, networks, and systems may be configured to communicate via one or more portions of the electromagnetic spectrum. The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5GNR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Frequencies between FR1 and FR2 are typically referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is typically (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. Similar naming issues sometimes arise with respect to FR2, which is typically (interchangeably) referred to as the "millimeter wave" (mmW) band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "mmW" band by the International Telecommunication Union (ITU).

[0045] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.126GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, currently exploring higher frequency bands to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2x (52.6GHz-71GHz), FR4 (71GHz-114.25GHz) and FR5 (114.25GHz-275GHz). Each of these higher frequency bands falls within the EHF band.

[0046] In view of the above aspects, unless otherwise specifically stated, it should be understood that if the term "6 GHz or less" is used herein, it can be broadly referred to as a frequency that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "mmW" or the like is used herein, it can be broadly referred to as a frequency that may include mid-band frequencies, may be within FR2, FR2x, FR4 and / or FR5, or may be within the EHF band.

[0047] 5G NR devices, networks, and systems may be implemented using optimized OFDM-based waveform features. These features may include scalable parameter sets and transmit time intervals (TTIs); a common flexible framework that efficiently multiplexes services and features using dynamic, low-latency time division duplex (TDD) designs or frequency division duplex (FDD) designs; and advanced wireless technologies such as massive multiple-input multiple-output (MIMO), robust mmW transmission, advanced channel decoding, and device-centric mobility. The scalability of parameter sets in 5GNR and the scaling of subcarrier spacing can efficiently address the operation of various services across different spectrums and different deployments. For example, in various outdoor and macro coverage deployments of less than 3GHz FDD or TDD implementations, the subcarrier spacing may appear at 15kHz, such as over bandwidths of 1MHz, 5MHz, 10MHz, 20MHz, etc. For various other outdoor and small cell coverage deployments with TDD greater than 3GHz, the subcarrier spacing may appear at 30kHz over 80MHz / 100MHz bandwidth. For various other indoor broadband implementations, using TDD on the unlicensed portion of the 5GHz band, the subcarrier spacing may occur at 60kHz over a 160MHz bandwidth. Finally, for various deployments transmitting over mmW components at 28GHz TDD, the subcarrier spacing may occur at 120kHz over a 500MHz bandwidth.

[0048] 5G NR's scalable parameter set facilitates scalable TTI for diverse latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs allows transmission to start on symbol boundaries. 5G NR also anticipates a self-contained integrated subframe design in which uplink or downlink scheduling information, data, and acknowledgments are in the same subframe. Self-contained integrated subframes support communications in unlicensed or contention-based shared spectrum, and adaptive uplink or downlink can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current business needs.

[0049] For clarity, certain aspects of devices and techniques may be described below with reference to example 5G NR implementations or in a 5G-centric manner, and 5G terminology may be used as illustrative examples in portions of the description below; however, the description is not intended to be limited to 5G applications.

[0050] Furthermore, it should be understood that in operation, a wireless communication network adapted according to the concepts herein may operate using any combination of licensed or unlicensed spectrum depending on load and availability. It will therefore be apparent to one of ordinary skill in the art that the systems, devices, and methods described herein may be applied to other communication systems and applications beyond the specific examples provided.

[0051] Although various aspects and specific implementations are described in this application by the illustration of some examples, it will be understood by those skilled in the art that additional specific implementations and use cases may be generated in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, specific implementation or use can be implemented via integrated chip specific implementation or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail equipment or purchasing equipment, medical equipment, AI-enabled devices, etc.). Although some examples may or may not specifically point to use cases or applications, the applicability of various types of described innovations may occur. The scope of specific implementation can range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems containing one or more described aspects. In some practical environments, the equipment in combination with the various aspects and features described may also necessarily include additional components and features for implementing and practicing the various aspects claimed and described. It is intended that the innovations described herein may be implemented in a wide variety of embodiments of different sizes, shapes, and configurations, including both large and small devices, chip-level components, multi-component systems (e.g., radio frequency (RF) chains, communication interfaces, processors), distributed arrangements, end-user devices, etc.

[0052] Figure 1 An example of a wireless communication system 100 that supports scheduling requests for spatial multiplexing according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0053] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In 3GPP, the term "cell" may refer to the specific geographic coverage area of ​​a network entity (such as the network entity 105) or a network entity subsystem serving the coverage area, depending on the context in which the term is used. In various examples, the network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, etc. In some examples, the network entity 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0054] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1 . The UEs 115 described herein may be able to communicate with various types of devices (such as Figure 1 Communicate with other UEs 115 or network entities 105) as shown.

[0055] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as a network node. For example, disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from the second node.

[0056] In some examples, the network entities 105 may communicate with the core network 130, or with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130) via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, the network entities 105 may communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol), or any combination thereof. The backhaul communication link 120, the midhaul communication link 162, or the fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. The UE 115 may communicate with the core network 130 via the communication link 155.

[0057] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a transmit receive point (TRP), a node B, an evolved node B (eNB), a next generation node B, or a gigabit node B (any of which may be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a home node B, a home evolved node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0058] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, an intelligent radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0059] The functional split between CU 160, DU 165, and RU 175 is flexible, and different functionalities may be supported depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 175. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165, such that CU 160 may support one or more layers of a protocol stack, and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as Layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160.

[0060] Additionally or alternatively, a functional split of the protocol stack may be employed between DU 165 and RU 170, such that DU 165 may support one or more layers of the protocol stack and RU 170 may support one or more different layers of the protocol stack. DU 165 may support one or more different cells (e.g., via one or more RU 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer may be performed by a different one of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interfaces). In some examples, midhaul communication links 162 or fronthaul communication links 168 may be implemented according to interfaces (e.g., channels) between layers of a protocol stack supported by the corresponding network entities 105 communicating over these communication links.

[0061] In a wireless communication system (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to a core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0062] For example, an access network (AN) or RAN may include an access node (e.g., an IAB donor), communications between an IAB node 104, and one or more UEs 115. The IAB donor may facilitate a connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), wherein the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and the IAB node 104 may communicate via an F1 interface according to a protocol defining a signaling message (e.g., an F1 AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of part of a backhaul link) and may communicate with other CUs 160 (e.g., CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be an example of part of a backhaul link).

[0063] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). The DU 165 may act as a distributed scheduling node toward child nodes associated with the IAB node 104, and the IAB-MT may act as a scheduled node toward a parent node associated with the IAB node 104. That is, an IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., the IAB donor may relay for transmissions to UEs through one or more other IAB nodes 104). Additionally or alternatively, an IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104, depending on the relay chain or configuration of the AN. Thus, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104, and a DU interface (eg, DU 165) may provide a Uu interface for the parent IAB node 104 to signal the child IAB node 104 or the UE 115.

[0064] For example, the IAB node 104 may be referred to as a parent node that supports child IAB node communications, and may be referred to as a child IAB node associated with an IAB donor. The IAB donor may include a CU 160 having a wired or wireless connection (e.g., backhaul communication link 120) to the core network 130, and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB donor may relay transmission to the UE 115 through the IAB node 104, and may directly signal the UE 115 of the transmission. The CU 160 of the IAB donor may signal the IAB node 104 of the communication link establishment via the F1 interface, and the IAB node 104 may schedule the transmission (e.g., the transmission relayed from the IAB donor to the UE 115) through the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling on the NR Uu-interface of the MT to the IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0065] Where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support scheduling requests for spatial multiplexing as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0066] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects (such as appliances, or vehicles, meters, satellite radios, global positioning system (GPS) devices, global navigation satellite system (GNSS) devices, logistics controllers, unmanned aerial vehicles (UAVs), drones, smart energy or security devices, solar panels or solar arrays, etc.).

[0067] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. Figure 1 shown.

[0068] The UE 115 and the network entity 105 may communicate wirelessly with each other via one or more communication links 125 (e.g., access links) via one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a physical layer structure defined for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any part (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send", "receive", or "communicate" when referring to the network entity 105 may refer to any part of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0069] The signal waveform transmitted through the carrier may be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM technology, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate of the device may be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may improve the data rate or data integrity of communications with UE 115.

[0070] One or more parameter sets for a carrier may be supported, where the parameter set may include subcarrier spacing (Δf) and cyclic prefix. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications for a UE 115 may be constrained to one or more active BWPs.

[0071] The time interval for the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be referred to as a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames, each radio frame having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0072] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., this depends on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, the time slot may be further divided into multiple mini-time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N f ) sampling period. The duration of a symbol period may depend on the subcarrier spacing or the operating band.

[0073] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0074] Physical channels may be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels may be multiplexed on a downlink carrier, for example, using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region to obtain control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 and a UE-specific search space set for transmitting control information to a specific one of the UEs 115 .

[0075] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for a mobile one of the coverage areas 110. In some examples, a different one of the coverage areas 110 associated with different technologies may overlap, but may be supported by the same one of the network entities 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different ones of the network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for respective coverage areas 110 using the same or different radio access technologies.

[0076] Some of the UEs 115 (such as MTC or IoT devices) may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that utilizes the information or presents the information to a person interacting with the application. Some of the UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based service charging.

[0077] Some of the UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not support concurrent transmission and reception). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for the UE 115 include entering a power saving deep sleep mode when not engaged in active communications, or operating over a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some of the UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a subcarrier or resource block (RB) set) within a carrier, within a guard band of a carrier, or outside a carrier.

[0078] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency and ultra-reliable low-latency may be used interchangeably herein.

[0079] In some examples, a UE 115 may be able to communicate directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P) or D2D or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication as configured or scheduled by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system in which each UE 115 transmits to each of the other UEs in the group of UEs 115. In some examples, network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105.

[0080] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these items. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, vehicles in the V2X system can communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0081] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered via a user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to an IP service 150 for one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0082] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to transmission using lower frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

[0083] The wireless communication system 100 may also operate in a super high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz (also known as a centimeter band) or in an extremely high frequency (EHF) region of a spectrum (e.g., from 30 GHz to 300 GHz) (also known as a millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between a UE 115 and a network entity 105 (e.g., a base station 140, a RU 170), and the EHF antenna of the corresponding device may be smaller and closer than the UHF antenna. In some examples, this may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be affected by greater atmospheric attenuation and shorter range than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may differ by country or regulatory agency.

[0084] The wireless communication system 100 may utilize both licensed RF spectrum bands and unlicensed RF spectrum bands. For example, the wireless communication system 100 may employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations in unlicensed bands may be based on a carrier aggregation configuration combined with component carriers operating in a licensed band (e.g., LAA). Operations in the unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0085] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels that can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, antennas or antenna arrays associated with the network entity 105 may be located in different geographical locations. The network entity 105 may have an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0086] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. Multiple signals may be sent, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO), in which multiple spatial layers are sent to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are sent to multiple devices.

[0087] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a sender device or a receiver device (e.g., network entity 105, UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the sender device and the receiver device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating at a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the sender device or the receiver device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the sender device or the receiver device or relative to some other orientation).

[0088] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmission along different beam directions may be used to identify the beam direction (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) for later transmission or reception by the network entity 105.

[0089] Some signals, such as data signals associated with a particular receiving device, may be sent by a sending device (e.g., a sending network entity 105, a sending UE 115) along a single beam direction (e.g., a direction associated with a receiving device (such as a receiving network entity 105 or a receiving UE 115)). In some examples, the beam direction associated with the transmission along the single beam direction may be determined based on signals sent along one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 along different directions and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0090] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more subbands. Network entity 105 may send a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may be precoded or unprecoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel codebook, a linear combination codebook, a port selection codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).

[0091] When receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105), the receiving device (e.g., UE 115) may perform receiving operations (e.g., directional listening) according to multiple receiving configurations. For example, the receiving device may perform reception according to multiple receiving directions by: receiving via different antenna subarrays, processing the received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing the received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0092] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate through logical channels. The MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also use error detection techniques, error correction techniques, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer for user plane data between a UE 115 and a network entity 105 or a core network 130. At the PHY layer, transport channels may be mapped to physical channels.

[0093] UE 115 and network entity 105 may support retransmission of data to increase the possibility of successfully receiving data. Hybrid automatic repeat request (HARQ) feedback is a technology for increasing the possibility of correctly receiving data through a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve the throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support simultaneous slot HARQ feedback, wherein the device may provide HARQ feedback in a specific time slot for data received in a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0094] Figure 2 1 is a block diagram illustrating an example of a base station 140 and a UE 115 according to one or more aspects. The base station 140 and the UE 115 may be Figure 1 For a restricted association scenario (as mentioned above), the network entity 105 may be a small cell base station, and the UE 115 may be a UE 115 operating in the service area of ​​the small cell base station. In order to access the small cell base station, the UE will be included in the accessible UE list of the small cell base station. The base station 140 may also be some other type of base station. Figure 2 As shown, a network entity 105, such as a base station 140, may be equipped with antennas 234a through 234t, and a UE 115 may be equipped with antennas 252a through 252r for facilitating wireless communications.

[0095] At the base station 140, the transmit processor 220 may receive data from the data source 212 and control information from the controller 240 (such as a processor). The control information may be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid ARQ (automatic repeat request) indicator channel (PHICH), a physical downlink control channel (PDCCH), an enhanced physical downlink control channel (EPDCCH), an MTC physical downlink control channel (MPDCCH), etc. The data may be for a physical downlink shared channel (PDSCH), etc. Additionally, the transmit processor 220 may process the data and control information (e.g., encode and symbol map them) respectively to obtain data symbols and control symbols. The transmit processor 220 may also generate reference symbols, such as for a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), and a cell-specific reference signal. The transmit (TX) MIMO processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, or reference symbols, if applicable, and may provide output symbol streams to modulators (MODs) 232a to 232t. For example, the spatial processing performed on the data symbols, control symbols, or reference symbols may include pre-coding. Each modulator 232 may process a corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Additionally or alternatively, each modulator 232 may process the output sample stream (e.g., analog-convert, amplify, filter, and up-convert it) to obtain a downlink signal. The downlink signals from modulators 232a to 232t may be transmitted via antennas 234a to 234t, respectively.

[0096] At the UE 115, antennas 252a to 252r may receive downlink signals from the base station 140 and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may condition the corresponding received signal (e.g., filter, amplify, downconvert, and digitize it) to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. The MIMO detector 256 may obtain received symbols from the demodulators 254a to 254r, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. The receive processor 258 may process the detected symbols (e.g., demodulate, deinterleave, and decode them), provide decoded data for the UE 115 to the data sink 260, and provide decoded control information to the controller 280 (e.g., a processor).

[0097] On the uplink, at the UE 115, the transmit processor 264 may receive and process data from the data source 262 (e.g., for a physical uplink shared channel (PUSCH)) and control information from the controller 280 (e.g., for a physical uplink control channel (PUCCH)). Additionally, the transmit processor 264 may also generate reference symbols for reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266 (if applicable), further processed by the modulators 254a to 254r (e.g., for SC-FDM, etc.), and transmitted to the network entity 105. At the network entity 105, the uplink signal from the UE 115 may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 115. Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to controller 240 .

[0098] Controllers 240 and 280 may direct the operation at base station 140 and UE 115, respectively. Controller 240 or other processors and modules at base station 140, or controller 280 or other processors and modules at UE 115 may perform or direct the execution of various processes for the techniques described herein, such as to perform or direct the execution of various processes for the techniques described herein. Figure 4 , Figure 6 or Figure 8 The execution shown or other processes for the techniques described herein. Memories 242 and 282 may store data and program codes for base station 140 and UE 115, respectively. Scheduler 244 may schedule UEs for data transmission on the downlink or uplink.

[0099] In some cases, the UE 115 and the network entity 105 (such as the base station 140) may operate in a shared radio spectrum band, which may include licensed or unlicensed (e.g., contention-based) spectrum. In the unlicensed frequency portion of the shared radio spectrum band, the UE 115 or the base station 140 may traditionally perform a medium sensing procedure to compete for access to the spectrum. For example, the UE 115 or the base station 140 may perform a listen-before-talk or listen-before-send (LBT) procedure (such as a clear channel assessment (CCA)) before communicating to determine whether the shared channel is available. In some specific implementations, the CCA may include an energy detection procedure to determine whether there are any other active transmissions. For example, the device may infer that a change in the received signal strength indicator (RSSI) of the power meter indicates that the channel is occupied. Specifically, the signal power concentrated in a certain bandwidth and exceeding a predetermined noise floor may indicate another wireless transmitter. CCA may also include detection of a specific sequence indicating the use of the channel. For example, another device may send a specific preamble before sending a data sequence. In some cases, the LBT procedure may include the wireless node adjusting its own backoff window based on the amount of energy detected on the channel or acknowledgement / negative acknowledgement (ACK / NACK) feedback for its own transmitted packets (as a manifestation of a collision).

[0100] Generally, four categories of LBT procedures have been proposed for sensing signals on a shared channel that may indicate that the channel is occupied. In the first category (CAT 1 LBT), no LBT or CCA is applied to detect occupancy of a shared channel. The second category (CAT 2 LBT) (which may also be referred to as shortened LBT, single LBT, 16-μs LBT, or 25-μs LBT) specifies that a node performs CCA to detect energy above a predetermined threshold or to detect a message or preamble occupying a shared channel. CAT 2 LBT performs CCA without using a random backoff operation, which results in its shortened length relative to the next category.

[0101] The third category (CAT 3LBT) performs CCA to detect energy or messages on a shared channel, but also uses random backoff and a fixed contention window. Therefore, when a node initiates CAT 3LBT, it performs a first CCA to detect occupancy of the shared channel. If the shared channel is idle for the duration of the first CCA, the node can continue to send. However, if the first CCA detects a signal occupying the shared channel, the node selects a random backoff based on a fixed contention window size and performs an extended CCA. If the shared channel is detected to be idle during the extended CCA and the random number has been decremented to 0, the node can start sending on the shared channel. Otherwise, the node decrements the random number and performs another extended CCA. The node will continue to perform extended CCAs until the random number reaches 0. If the random number reaches 0 and no one of the extended CCAs detects channel occupancy, the node can then send on the shared channel. If in any of the extended CCAs, the node detects channel occupancy, the node can reselect a new random backoff based on a fixed contention window size to start the countdown again.

[0102] The fourth category (CAT 4 LBT) (which may also be referred to as the full LBT procedure) performs CCA with energy or message detection using random backoff and variable contention window size. The sequence of CCA detection proceeds similarly to the process of CAT 3 LBT, except that the contention window size is variable for the CAT 4 LBT procedure.

[0103] Sensing for shared channel access may also be categorized into full or shortened types of LBT procedures. For example, full LBT procedures such as CAT 3 or CAT 4 LBT procedures (including extended channel clearance assessment (ECCA) over a non-trivial number of 9-μs time slots) may also be referred to as "Type 1 LBT". Shortened LBT procedures such as CAT 2 LBT procedures (which may include a one-time CCA for 16-μs or 25-μs) may also be referred to as "Type 2 LBT".

[0104] Using medium sensing procedures to compete for access to unlicensed shared spectrum can result in communication inefficiencies. This is particularly evident when multiple network operating entities (e.g., network operators) attempt to access shared resources. In the wireless communication system 100, the network entity 105 and the UE 115 may be operated by the same or different network operating entities. In some examples, a separate network entity 105 or UE 115 may be operated by more than one network operating entity. In other examples, each network entity 105 and UE 115 may be operated by a single network operating entity. Requiring each network entity 105 and UE 115 of different network operating entities to compete for shared resources can result in increased signaling overhead and communication latency.

[0105] In some cases, operation in an unlicensed band may be based on a carrier aggregation configuration in conjunction with component carriers operating in a licensed band (e.g., LAA). Operations in the unlicensed spectrum may include downlink transmissions, uplink transmissions, peer to peer transmissions, or a combination of these. Duplexing in the unlicensed spectrum may be based on frequency division duplexing (FDD), time division duplexing (TDD), or a combination of both.

[0106] The flexibility and scalability of 5G NR technology has made it possible to introduce enhancements in a timely manner to address new use cases, which can expand the 5G ecosystem and connect more and more devices to the network. An example of such an enhancement is 5G NR support for reduced capability (RedCap) devices. The introduction of reduced capability 5G NR devices can promote the expansion of the 5G NR device ecosystem to address new, unserved or underserved use cases.

[0107] Figure 3 is a diagram illustrating a 5G NR network 30 configured to support marking of symbols and verification of non-cell defined synchronization signal blocks (NCD-SSB) and random access channel (RACH) opportunities for RedCap UE operation in accordance with various aspects of the present disclosure. RedCap UEs defined in accordance with 3GPP Release 17 (Rel-17) can coexist with non-RedCap UEs in the same cell. According to current specifications, RedCap UEs can be configured according to a maximum radio frequency (RF) bandwidth (e.g., 20 MHz, 40 MHz, etc.), while the base carrier bandwidth of a 5G NR cell can be up to 100 MHz. The 5G NR network 30 includes operations between a RedCap UE 115 and a network entity 105 serving a given cell. The cell served by network entity 105 includes a carrier bandwidth (e.g., up to 100 MHz), which may include dedicated uplink and downlink bandwidth parts (BWPs) for serving non-RedCap UEs and RedCap-specific BWPs (such as RedCap-specific BWP 301) for serving RedCap UEs (such as UE 115).

[0108] Due to the frequency window of the RedCap-specific BWP (such as the RedCap-specific BWP 301), the basic RedCap UE may not be able to use the cell-defined SSB (CD-SSB) for beam mobility (e.g., radio link monitoring (RLM) / beam failure detection (BFD) / random access channel (RACH), etc.) and timing, because the CD-SSB may fall outside the RedCap-specific BWP, such as the CD-SSB within the carrier bandwidth 300 falls outside the RedCap-specific BWP 301. However, some RedCap UEs may have the ability to tune outside their limited bandwidth (such as outside the RedCap-specific BWP 301) during network-configured gaps and use CD-SSB. BWP-specific NCD-SSBs have been introduced, and when such NCD-SSBs are located within a configured dedicated and active RedCap-specific BWP (such as the NCD-SSBs are located within the RedCap-specific BWP 301), the RedCap UE may use the BWP-specific NCD-SSBs for related operations.

[0109] Within the current Rel-17 standard defining NCD-SSB, the UE assumes that the active BWP will include a synchronization signal block (SSB) that includes both synchronization signals (e.g., primary synchronization signal (PSS) and secondary synchronization signal (SSS)) and a physical block channel (PBCH), and does not include a control source set (CORESET) with index 0 (CORESET0), unless the UE indicates its capability to operate within an active BWP without receiving SSBs.

[0110] A RedCap UE may receive configuration for NCB-SSB transmission via an information element. The NCB-SSB information element may include a frequency range for NCD-SSB transmissions that indicates a location within a RedCap-specific BWP. The information element may also include the periodicity when it is more frequent than the periodicity of CD-SSB transmissions. When the periodicity is not included in the information element, the RedCap UE may apply the CD-SSB transmission periodicity. Additionally, the information element configuring the NCD-SSB transmission may include a time offset that identifies the time between the CD-SSB of the serving cell and the NCD-SSB. The time offset may be a 0 time. Furthermore, when the information element does not include an explicit time offset, the RedCap UE will assume that the offset relative to the CD-SSB is 0. The possibility of a non-zero time offset means that the serving cell CD-SSB and the RedCap-specific BWP NCD-SSB may be located at different times.

[0111] The 5G NR specification currently defines three types of symbols: downlink (D) symbols, uplink (U) symbols, and flexible (X) symbols. Downlink symbols are configured for downlink communications, uplink symbols are configured for uplink communications, and flexible symbols can adapt to downlink communications under certain conditions and can adapt to uplink communications under other conditions. A specific symbol sequence for a given one or more time slots may be provided via a configuration signal including an uplink-downlink symbol configuration. The network attempts to configure CD-SSB symbols outside of any configured uplink symbols from the uplink-downlink configuration. Therefore, in the case where the CD-SSB symbol may overlap with the configured uplink symbol, the CD-SSB symbol may be verified as invalid. The configured CD-SSB symbols are expected to be located in the downlink symbol, and if they overlap with the configured flexible symbol, the configured flexible symbol will be marked as a downlink symbol.

[0112] Similarly, random access channel (RACH) opportunities are expected to fall within uplink symbols. If a configured RACH opportunity happens to overlap with a configured downlink symbol or SSB symbol, the RACH opportunity may be verified as invalid. When a configured RACH opportunity overlaps with a configured flexible symbol, the configured flexible symbol will be marked as an uplink symbol and the RACH opportunity is verified as valid.

[0113] The marking and verification of CD-SSB symbols has been provided in the Technical Specifications (TS), such as in Rel-17 TS 38.213. For operation on a single carrier in unpaired spectrum, Rel-17 TS 38.213 provides for indicating to the UE via an SSB configuration message (e.g., such as via the ssb-PositionsInBurst field in SIB1 or via the ssb-PositionsInBurst field in ServingCellConfigCommon) a set of symbols of a time slot for reception of SSB, or if no transmit configuration information (TCI) parameters are provided to the UE (e.g., such as via a DLorJoint-TCIState parameter or a followUnifiedTCIstate parameter, or via the ssb-PositionsInBurst field in an SSB-MTCAdditionalPCI parameter associated with a physical cell identifier (ID) with an active TCI state), the UE shall not transmit PUSCH, PUCCH or PRACH in the time slot, and the UE shall not transmit a sounding reference signal (SRS) in the set of symbols of the time slot, if the transmission would overlap with any symbol from the set of symbols. The UE does not desire the set of symbols of the time slot to be indicated as uplink by the uplink-downlink symbol configuration when provided to the UE.

[0114] Rel-17 TS 38.213 also specifies that when no uplink-downlink symbol configuration is provided to the UE, a PRACH opportunity in a physical random access channel (PRACH) slot is not located before an SSB (including a CD-SSB or NCD-SSB) in the PRACH slot and at least a predefined number of symbols (N) after the last SSB received symbol. 间隙 ), the PRACH opportunity may be valid. N may be provided in the table 间隙 The table may be stored by the UE or communicated to the UE by the network. The candidate SSB index of the SSB may correspond to the SSB index provided by the SSB configuration message. When the uplink-downlink symbol configuration is provided to the UE, the PRACH opportunity in the PRACH time slot falls within the configured uplink symbol or it is not located before the SSB (including CD-SSB or NCD-SSB) in the PRACH time slot and at least N after the last downlink symbol. 间隙 symbols and at least N after the last SSB symbol 间隙 In the case where the PRACH opportunity starts at a symbol, the PRACH opportunity may be valid, as described above. Similarly, in the context of the UE receiving an uplink-downlink symbol configuration, the candidate SSB index of the SSB may correspond to the SSB index provided by the SSB configuration message.

[0115] Various examples and aspects described herein support marking and validating NCD-SSB and RACH opportunities based on a combination of NCD-SSB configuration and CD-SSB configuration according to aspects of the present disclosure.

[0116] Figure 4 4 is a flow chart illustrating an example process 40 for marking symbols and verifying NCD-SSB according to one or more aspects. The operations of process 40 may be performed by a UE (such as the one described above with reference to Figure 1 and Figure 2 The UE 115 or reference Fig.11 The UE) is used to execute. Fig.11 4 is a block diagram illustrating an example UE configured to support marking of symbols and verification of NCD-SSB according to one or more aspects. For example, example operations (also referred to as "boxes") of process 40 may enable UE 115 to support marking of symbols and verification of NCD-SSB for RedCap UE operation.

[0117] As shown, the memory 282 may include a TDD uplink-downlink configuration 1101, a RedCap BWP configuration 1102, an SSB configuration 1103, and a RedCap BWP operation logic 1104. The TDD uplink-downlink configuration 1101 stores a configuration sequence of uplink symbols, downlink symbols, and flexible symbols for one or more time slots. The RedCap BWP configuration 1102 stores configuration information for the RedCap BWP for a frequency window within the carrier bandwidth. The SSB configuration 1103 stores configuration information for SSB transmission, including the frequency of CD-SSB transmission and the frequency of NCD-SSB transmission and any offset information reflecting the number of symbols between the CD-SSB transmission and the NCD-SSB transmission. The RedCap BWP operation logic 1104 may be configured to provide a UE (such as UE 115) with functionality for marking using CD-SSB symbols or NCD-SSB symbols and verifying NCD-SSB transmission. UE 115 may receive information from one or more network entities (such as Figure 1 to Figure 2 The network entity 105 or base station 140) receives a signal or sends a signal to the one or more network entities.

[0118] In block 400, a UE (such as UE 115) obtains a TDD uplink-downlink symbol configuration that identifies a pattern of uplink symbols, downlink symbols, and flexible symbols on one or more time slots of a carrier bandwidth. A UE (such as UE 115) may receive configuration information for an uplink-downlink symbol sequence for one or more upcoming time slots. UE 115 will receive such configuration information, for example, via antennas 252a to 252r and radio components 1100a to 1100r via radio resource control (RRC) signaling. UE 115 will store such configuration information in a memory 282 at a TDD uplink-downlink configuration 1101.

[0119] At block 401, the UE receives a bandwidth configuration identifying a BWP allocated to the UE within a carrier bandwidth, wherein the BWP is located within a frequency window of the carrier bandwidth. The UE 115 may be a RedCap UE or may be a UE with conventional bandwidth capabilities. The UE 115 may also receive a configuration signal, such as via RRC signaling, that allocates a BWP (which may be a RedCap specific BWP) within the carrier bandwidth of the network and configures the frequency of CD-SSB transmission. The BWP configuration is stored in the memory 282 at RedCap BWP configuration 1102, and the CD-SSB transmission configuration is stored in the memory 282 at SSB configuration 1103. The UE 115 will receive such configuration information, for example, via antennas 252a to 252r and radio components 1100a to 1100r via RRC signaling.

[0120] In block 402, the UE receives an NCD-SSB configuration that identifies at least the frequency of the NCD-SSB transmission and the time offset of the NCD-SSB transmission relative to the CD-SSB transmission. The additional configuration information received by the UE 115 may also include the configuration of the NCD-SSB transmission. Such configuration information includes parameters such as the transmission frequency and the time offset of the NCD-SSB transmission relative to the CD-SSB transmission. The UE 115 will receive such configuration information, for example, via radio resource control (RRC) signaling via the antennas 252a to 252r and the radio components 1100a to 1100r, and store it at the SSB configuration 1103.

[0121] In block 403, the UE marks the configured flexible symbol as a downlink symbol in response to one or more of the NCD-SSB symbol transmitted by the NCD-SSB or the CD-SSB symbol transmitted by the CD-SSB overlapping with the configured flexible symbol of the TDD uplink-downlink symbol configuration. When operating within a RedCap-specific BWP, a UE (such as UE 115) may execute RedCap BWP operation logic 1104 under the control of controller 280. When the instructions and codes forming the basis of the RedCap BWP operation logic 1104 are executed by the controller 280 (referred to herein as the "execution environment" of the RedCap BWP operation logic 1104), the functionality of the UE 115 for performing various aspects of the present disclosure is enabled and implemented. Specifically, the execution environment of the RedCap BWP operation logic 1104 allows the UE 115 to mark the configured flexible symbol as a downlink symbol when the NCD-SSB symbol or the CD-SSB symbol overlaps with the configured flexible symbol.

[0122] As reference Figure 4As described above, the present disclosure provides techniques for marking symbols and verifying NCD-SSB. Because RedCap-specific BWPs may not include CD-SSB transmissions, the additional use of NCD-SSB symbols can assist UEs in beam mobility (e.g., RLM / BFD / RACH, etc.) and timing operations.

[0123] Figure 5 1 is a diagram illustrating a 5G NR network 50 configured to support marking of symbols and verification of NCD-SSB according to various aspects of the present disclosure. A UE, such as 115UE, identifies a RedCap-specific BWP 501 for communication in a 5G NR network 40. The UE 115 may be a RedCap UE or may be a UE with conventional bandwidth capabilities. The UE 115 identifies the RedCap-specific BWP 501 as an initial access BWP via a public network configuration or as a dedicated BWP via dedicated configuration messaging. The RedCap-specific BWP 501 includes a portion of the bandwidth of a carrier bandwidth 500 of the 5G NR network 50. The UE 115 may also obtain a TDD uplink-downlink symbol configuration from the network entity 105, which identifies a sequence of symbols 502 to 509 and a configured symbol type (e.g., downlink (D), uplink (U), flexible (F)).

[0124] Although the UE 115 can perform RedCap type communications via the RedCap specific BWP 501, common control transmissions such as CD-SSB and CORESET#0 are mostly located within the carrier bandwidth 500 outside the RedCap specific BWP 501. Therefore, if the UE 115 is not able to tune outside the bandwidth of the RedCap specific BWP 501, it cannot use the CORESET and synchronization information to access and communicate via the 5G NR network 50. The UE 115 can also receive the configuration of the NCD-SSB to be transmitted within the RedCap specific BWP 501. Therefore, the UE 115 can receive mobility, synchronization, and access information through the effective NCD-SSB transmission within the RedCap specific BWP 501.

[0125] In a first optional implementation, the configured flexible symbols within the TDD uplink-downlink symbol configuration may be marked according to NCD-SSB symbols or CD-SSB symbols. Figure 5As illustrated, the CD-SSB symbol overlaps with symbol 502 and the first illustrated NCD-SSB symbol overlaps with symbol 504, both of which are configured as flexible symbols (F). In a first optional implementation, UE 115 includes the ability to tune outside the bandwidth of RedCap-specific BWP 501 during configured network gaps. Therefore, UE 115 may mark symbol 502 configured as a flexible symbol as a downlink symbol in response to identifying that symbol 502 overlaps with CD-SSB. Similarly, UE 115 may mark symbol 504 configured as a flexible symbol as a downlink symbol in response to identifying that symbol 504 overlaps with NCD-SSB.

[0126] In a second optional implementation, the configured flexible symbols within the TDD uplink-downlink symbol configuration may be marked according to the NCD-SSB symbol instead of the CD-SSB symbol. In the second optional implementation, the UE 115 may not have the ability to tune outside the bandwidth of the RedCap-specific BWP 501, and therefore may not be able to detect the CD-SSB overlapping with the symbol 502 because the UE is located in the carrier bandwidth 500 outside the bandwidth of the RedCap-specific BWP 501. The UE 115 maintains the symbol 502 as the configured flexible symbol. However, at symbol 504, the UE 115 will mark the symbol 504 (which is configured as a flexible symbol) as a downlink symbol in response to the NCD-SSB overlapping with the symbol 504.

[0127] In a third optional implementation, the UE 115 has the capability to tune outside of the RedCap specific BWP 501 to detect CD-SSB in the symbol 502. Thus, due to this capability, the UE 115 can use CD-SSB to mark overlapping symbols. Figure 5 As illustrated, in a third optional implementation, UE 115 will mark symbol 502 (which is configured as a flexible symbol) as a downlink symbol in response to the CD-SSB overlapping with symbol 502. Because UE 115 can detect and use CD-SSB outside of RedCap-specific BWP 501, UE 115 will not have to use NCD-SSB within RedCap-specific BWP 501.

[0128] Figure 6 60 is a flow chart illustrating an example process 60 for supporting marking of symbols and verification of NCD-SSB according to one or more aspects. The operations of process 60 may be performed by a UE (such as the one described above with reference to Figure 1 and Figure 2 The UE 115 or reference Fig.11For example, the example operations (also referred to as "boxes") of process 60 may enable UE 115 to support marking of symbols and verification of NCD-SSB.

[0129] In box 600, UE (such as UE 115) obtains TDD uplink-downlink symbol configuration, wherein the TDD uplink-downlink symbol configuration identifies the pattern of uplink symbols, downlink symbols and flexible symbols on one or more time slots of carrier bandwidth.UE 115 can be a RedCap UE or can be a UE with conventional bandwidth capabilities. As described above, UE (such as UE 115) can receive configuration information of uplink-downlink symbol sequences for one or more upcoming time slots.UE 115 will receive such configuration information via radio resource control (RRC) signaling via antenna 252a to 252r and radio part 1100a to 1100r, for example.UE 115 will store such configuration information in memory 282 at TDD uplink-downlink configuration 1101.

[0130] In block 601, the UE receives a bandwidth configuration identifying a RedCap-specific BWP allocated to the UE within a carrier bandwidth, wherein the RedCap-specific BWP is within a frequency window of the carrier bandwidth and is a configuration for CD-SSB transmission. Also as described above, the UE 115 may also receive a configuration signal, such as via RRC signaling, that allocates a RedCap-specific BWP within the carrier bandwidth of the network and configures the frequency of CD-SSB transmission. The RedCap-specific BWP configuration is stored in the memory 282 at RedCap BWP configuration 1102, and the CD-SSB transmission configuration is stored in the memory 282 at SSB configuration 1103. The UE 115 will receive such configuration information, for example, via radio resource control (RRC) signaling via antennas 252a to 252r and radio components 1100a to 1100r.

[0131] In block 602, the UE receives an NCD-SSB configuration that identifies at least the frequency of the NCD-SSB transmission and the time offset of the NCD-SSB transmission relative to the CD-SSB transmission. Also as described above, the additional configuration information received by the UE 115 may also include the configuration of the NCD-SSB transmission. Such configuration information includes parameters such as the transmission frequency and the time offset of the NCD-SSB transmission relative to the CD-SSB transmission. The UE 115 will receive such configuration information, for example, via RRC signaling via the antennas 252a to 252r and the radio components 1100a to 1100r, and store it at the SSB configuration 1103.

[0132] In block 603, the UE verifies one or more NCD-SSB symbols as invalid in response to one or more NCD-SSB symbols of a plurality of NCD-SSB symbols scheduled according to the NCD-SSB configuration overlapping one or more configured uplink symbols of the TDD uplink-downlink symbol configuration. The execution environment of the RedCap BWP operation logic 1104 allows the UE 115 to verify the one or more NCD-SSB symbols as invalid when the one or more NCD-SSB symbols overlap with the one or more configured uplink symbols.

[0133] As reference Figure 6 As described above, the present disclosure provides techniques for marking symbols and verifying NCD-SSB. Because RedCap-specific BWPs may not include CD-SSB transmissions, the additional use of NCD-SSB symbols can assist UEs in beam mobility (e.g., RLM / BFD / RACH, etc.) and timing operations.

[0134] Fig. 7A is a diagram illustrating a 5G NR network 70 configured to support marking of symbols and verification of NCD-SSB according to various aspects of the present disclosure. A UE, such as UE 115, obtains a configuration for a RedCap-specific BWP 701 for communication in the 5G NR network 70 within a carrier bandwidth 700. The UE 115 may be a RedCap UE or may be a UE with normal bandwidth capabilities. The RedCap-specific BWP 701 includes a portion of the bandwidth of the carrier bandwidth 700. The UE 115 may also obtain a TDD uplink-downlink symbol configuration from the network entity 105, which identifies a sequence of symbols 702 to 709 and a configured symbol type (e.g., downlink (D), uplink (U), flexible (F)).

[0135] As described above, the UE 115, which is a RedCap device, may have limited bandwidth capabilities that can be adapted using a dedicated BWP (RedCap-specific BWP 701). The UE 115 may or may not have the ability to tune into the remaining bandwidth of the carrier bandwidth 700 outside of the RedCap-specific BWP 701. For RedCap UEs that do not have such capabilities, they may not be able to detect and receive common control transmissions, such as CD-SSB and CORESET#0. The network may send NCD-SSB within the RedCap-specific BWP 701 via the network entity 105, which may be used for various tasks, such as beam mobility (e.g., RLM / BFD / RACH, etc.) and timing. The UE 115 may obtain the configuration of such NCD-SSB transmission within the RedCap-specific BWP 701 for mobility, synchronization, and access information.

[0136] In some cases, NCD-SSB is expected to overlap with a configured downlink symbol or a configured flexible symbol. However, UE (such as UE 115) will not expect NCD-SSB transmission to overlap with a configured uplink symbol. In fact, the NCD-SSB symbol overlapping with the configured uplink symbol can be verified as invalid in response to the NCD-SSB symbol overlapping with the configured uplink symbol. As illustrated in Figure 7, the NCD-SSB symbol overlaps with symbols 703, 705, 707 and 709. In these symbols, the TDD uplink-downlink symbol configuration has configured symbols 703 and 705 as uplink (U) symbols. Then, UE 115 can verify the NCD-SSB symbol overlapping with the configured uplink symbol in symbols 703 and 705 and potential other NCD-SSB as invalid.

[0137] In a first optional implementation, if any NCD-SSB symbol in a configured burst set of NCD-SSB transmission overlaps with a configured uplink symbol, the entire configuration of the burst set will be determined to be invalid by UE 115. For example, upon determining that the NCD-SSB symbol overlaps with the configured uplink symbol of symbol 703, UE 115 verifies the entire configured NCD-SSB burst set of NCD-SSB transmissions in all symbols including symbols 703, 705, 707, and 709 as invalid.

[0138] In a second optional specific implementation, UE 115 may verify that the NCD-SSB symbols in the NCD-SSB burst set that overlap with the configured uplink symbols are invalid, but the remaining NCD-SSB symbols in the burst set that do not overlap with the uplink symbols are kept valid. For example, as illustrated in the figure, the NCD-SSB burst set includes NCD-SSB symbols in symbols 703, 705, 707, and 709. UE 115 may verify that the NCD-SSB symbols that overlap with the configured uplink symbols of symbols 703 and 705 are invalid, but the NCD-SSB symbols that overlap with the configured downlink symbols of symbols 707 and 709 are valid.

[0139] It should be noted that the second optional implementation may be utilized by RedCap UEs that have the capability to tune outside of the RedCap specific BWP 701 to detect CD-SSB transmissions within the remaining bandwidth of the carrier bandwidth 700. Thus, the SSB indices of the NCB-SSB symbols that have been verified to be invalid may be replaced by corresponding SSB indices of CD-SSB symbols in the gap for the UE 115 to tune outside of the RedCap specific BWP 701, such as CD-SSB symbols that overlap with the configured downlink symbols of symbols 702 and 704. For the remaining SSB indices, the UE 115 will use valid NCD-SSB symbols that overlap with the configured downlink symbols of symbols 707 and 709.

[0140] Figure 7B is a diagram illustrating an extended time period of a 5G NR network 71 configured to support marking of symbols and verification of NCD-SSB in accordance with various aspects of the present disclosure. Figure 7B The time period of 5GNR network 71 includes Fig. 7A The depicted 5G NR network 70 operates over a longer time period. Figure 7B The depicted duration of the 5G NR network 71 includes a time period T1 (which covers Fig. 7A The illustrated operation) and operation over a time period T2 (which includes symbols 710 to 717). The TDD uplink-downlink symbol configuration received by UE 115 from network entity 105 includes a symbol type sequence over symbols 702 to 717. The NCD-SSB configuration defines a first burst set (burst set 1) of NCD-SSB transmission in time period T1 and a second burst set (burst set 2) of NCD-SSB transmission in timer period T2.

[0141] The overlap between the NCD-SSB symbols of a burst set and the configured uplink symbols may vary over time. For example, in burst set 1 of time period T1, the first NCD-SSB symbol set in burst set 1 overlaps the configured uplink symbols of symbols 703 and 705 and is therefore verified as invalid by UE 115, while the second NCD-SSB symbol set in burst set 1 is valid and overlaps the configured downlink symbols of symbols 707 and 709. In contrast, in burst set 2 of time period T2, the first NCD-SSB symbol set is valid and overlaps the configured downlink symbols of symbols 711 and 713, while the second NCD-SSB symbol set in burst set 2 overlaps the configured uplink symbols of symbols 715 and 717 and is therefore verified as invalid by UE 115. In time period T1, UE 115 will monitor CD-SSB symbols outside RedCap-specific BWP 701 corresponding to the first SSB index subset, and monitor NCD-SSB symbols within RedCap-specific BWP 701 corresponding to the second SSB index subset. Conversely, in time period T2, UE 115 will monitor NCD-SSB symbols within RedCap-specific BWP 701 corresponding to the first SSB index subset, and monitor CD-SSB symbols outside RedCap-specific BWP 701 corresponding to the second SSB index subset.

[0142] Figure 8 80 is a flow chart illustrating an example process 80 for marking symbols and verifying NCD-SSB according to one or more aspects. The operations of process 80 may be performed by a UE (such as the one described above with reference to FIG. Figure 1 and Figure 2 The UE 115 or reference Fig.11 For example, the example operations (also referred to as "boxes") of process 80 may enable UE 115 to support marking of symbols and verification of NCD-SSB.

[0143] As shown, the memory 282 may also include a RACH configuration 1105. The RACH configuration 1105 stores configurations for RACH slots and RACH opportunities within the RACH slots.

[0144] In block 800, a UE (such as UE 115) obtains a PRACH configuration, wherein the PRACH configuration identifies a plurality of RACH opportunities within a RACH time slot. UE 115 may be a RedCap UE or may be a UE with conventional bandwidth capabilities. As described above, a UE (such as UE 115) may receive configuration information for uplink-downlink symbol sequences for one or more upcoming time slots. UE 115 will receive such configuration information, for example, via antennas 252a to 252r and radio components 1100a to 1100r via radio resource control (RRC) signaling. UE 115 will store such configuration information in memory 282 at TDD uplink-downlink configuration 1101.

[0145] At block 801, the UE receives a bandwidth configuration identifying a BWP allocated to the UE within a carrier bandwidth, wherein the BWP is located within a frequency window of the carrier bandwidth. Also as described above, the UE 115 may also receive a configuration signal, such as via RRC signaling, that allocates a BWP (which may be a RedCap-specific BWP) within the carrier bandwidth of the network and configures the frequency of CD-SSB transmission. The BWP configuration is stored in the memory 282 at RedCap BWP configuration 1102, and the CD-SSB transmission configuration is stored in the memory 282 at SSB configuration 1103. The UE 115 will receive such configuration information, for example, via radio resource control (RRC) signaling via antennas 252a to 252r and radio components 1100a to 1100r.

[0146] In block 802, the UE receives an NCD-SSB configuration that identifies at least the frequency of the NCD-SSB transmission and the time offset of the NCD-SSB transmission relative to the CD-SSB transmission. Also as described above, the additional configuration information received by the UE 115 may also include the configuration of the NCD-SSB transmission. Such configuration information includes parameters such as the transmission frequency and the time offset of the NCD-SSB transmission relative to the CD-SSB transmission. The UE 115 will receive such configuration information, for example, via RRC signaling via the antennas 252a to 252r and the radio components 1100a to 1100r, and store it at the SSB configuration 1103.

[0147] In block 803, the UE verifies the RACH opportunity as invalid in response to a collision between a RACH opportunity in the plurality of RACH opportunities and one of an NCD-SSB symbol of an NCD-SSB transmission, a CD-SSB symbol of a CD-SSB transmission, or a combination of an NCD-SSB symbol and a CD-SSB symbol. The execution environment of the RedCap BWP operation logic 1104 allows the UE 115 to verify the RACH opportunity as invalid when one or more RACH opportunities collide with an NCD-SSB symbol, a CD-SSB symbol, or a combination of an NCD-SSB symbol and a CD-SSB symbol.

[0148] As reference Figure 8 As described above, the present disclosure provides techniques for marking verification of RACH opportunities. Because RedCap-specific BWPs may not include CD-SSB transmissions, the additional use of NCD-SSB symbols can assist UEs in beam mobility (e.g., RLM / BFD / RACH, etc.) and timing operations.

[0149] Fig. 9 is a diagram illustrating a 5G NR network 90 configured to support verification of RACH opportunities according to various aspects of the present disclosure. A UE, such as UE 115, obtains a configuration for a RedCap-specific BWP 901 for communication in a 5G NR network 90 within a carrier bandwidth 900. UE 115 may be a RedCap UE or may be a UE with conventional bandwidth capabilities. The RedCap-specific BWP 901 includes a portion of the bandwidth of the carrier bandwidth 900. As described above, UE 115, which is a RedCap device, may or may not have the ability to tune into the remaining bandwidth of the carrier bandwidth 900 outside of the RedCap-specific BWP 901. A RedCap UE that does not have such capabilities may not be able to detect CD-SSB and CORESET#0. Therefore, the network may send an NCD-SSB within the RedCap-specific BWP 901 via the network entity 105, which may be used for tasks such as beam mobility (e.g., RLM / BFD / RACH, etc.) and timing. The UE 115 may obtain configurations for such NCD-SSB transmissions within the RedCap-specific BWP 901 for mobility, synchronization, and access information. Additionally, the UE 115 receives configurations for multiple RACH opportunities (eg, RACH opportunities 902 to 905).

[0150] As previously described, valid RACH opportunities are considered uplink symbols, regardless of whether they overlap with configured uplink symbols or with configured flexible symbols. However, RACH opportunities that overlap with downlink symbols and SSB symbols will be verified as invalid. Because the RedCap-specific BWP 901 may include NCD-SSB transmissions but not CD-SSB transmissions, aspects of the present disclosure may provide for verification of RACH opportunities using NCD-SSB transmissions or CD-SSB transmissions, depending on the capabilities of the RedCap UE (such as UE 115).

[0151] In a first optional aspect, UE 115 is a UE with normal bandwidth capabilities or a RedCap UE capable of tuning outside of the RedCap specific BWP 901. With such capabilities, UE 115 can use CD-SSB symbols or NCD-SSB symbols to verify that the RACH opportunity is invalid. For example, UE 115 can tune outside of the RedCap specific BWP 901 to detect CD-SSB symbols overlapping with RACH opportunity 902. UE 115 also detects NCD-SSB symbol 906 overlapping with RACH opportunity 903. Then, due to the collision with CD-SSB symbol and NCD-SSB symbol 906, UE 115 can verify that RACH opportunities 902 and 903 are invalid. As previously described, when the RACH opportunity is located within a predetermined number of symbols (N) from the end of the last SSB symbol, the RACH opportunity is invalid. 间隙 ), the RACH opportunity may be further verified as invalid. Therefore, UE 115 may also verify RACH opportunity 904 as invalid because RACH opportunity 904 is located N from the end of NCD-SSB symbol 907. 间隙 within a symbol.

[0152] In a second optional aspect, the UE 115 cannot tune outside of the RedCap specific BWP 901. In such a scenario, the UE 115 may validate the RACH opportunity as invalid when the RACH opportunity collides with the NCD-SSB symbol instead of the CD-SSB symbol, wherein the RACH opportunity is not valid when the RACH opportunity overlaps with the NCD-SSB symbol or the RACH opportunity is N from the end of the NCD-SSB symbol. 间隙 For example, in a second optional aspect, UE 115 may verify RACH opportunities 903 and 904 as invalid because these opportunities conflict with NCD-SSB symbols 906 and 907, wherein the conflict includes RACH opportunity 903 overlapping with NCD-SSB symbol 906, and RACH opportunity 904 being located N from the end of NCD-SSB symbol 907. 间隙 Inside.

[0153] Fig.10 1000 is a diagram illustrating a 5G NR network 1000 configured to support validation of RACH opportunities in accordance with various aspects of the present disclosure. During initial access, a RedCap UE (such as UE 115) may obtain a public dedicated initial RedCap specific BWP 1002. UE 115 may be a RedCap UE or may be a UE with normal bandwidth capabilities. Due to the initial access, UE 115 may not be configured with NCD-SSB transmissions. In such cases, UE 115 may use CD-SSB transmissions within the carrier bandwidth 1001 outside of the public dedicated initial RedCap specific BWP 1002 to validate the public RACH opportunities 1003 and 1004 as valid. In the illustrated example, UE 115 will have the ability to tune outside of the public dedicated initial RedCap specific BWP 1002 to detect CD-SSB transmissions. For example, when the RACH opportunity 1003 is located N of the end of the CD-SSB symbol. 间隙 UE 115 may identify the conflict between the RACH opportunity and the CD-SSB symbol. Then, the UE may consider RACH opportunity 1004 to be valid.

[0154] After initial access, the UE may obtain a dedicated RedCap-specific BWP with configuration for NCD-SSB transmission. In such a scenario, the UE may use both CD-SSB transmission and NCD-SSB transmission when the UE is able to tune outside of the dedicated RedCap-specific BWP, or may use NCD-SSB transmission within the dedicated RedCap-specific BWP when the UE 115 does not have the ability to tune outside of its dedicated BWP. Fig. 9 , the RedCap-specific BWP 901 may be a dedicated RedCap-specific BWP, so if the UE 115 is a regular bandwidth capable UE or a RedCap UE capable of tuning outside of the RedCap-specific BWP 901, it will tune the dedicated RACH opportunities (such as described above with respect to Fig. 9 Alternatively, if the UE 115 is unable to tune outside of the RedCap specific BWP 901, the UE 115 will tune as described above for conflicts with NCD-SSB symbols 906 and 907. Fig. 9 The RACH opportunities 903 and 904 are verified to be invalid.

[0155] In one or more aspects, techniques for supporting marking of symbols and validating NCD-SSB and RACH opportunities may include additional aspects, such as any single aspect or any combination of aspects described below or in combination with one or more other processes or apparatus described elsewhere herein. In a first aspect, supporting marking of symbols and verifying NCD-SSB and RACH timing may include a UE configured to obtain a TDD uplink-downlink symbol configuration, wherein the TDD uplink-downlink symbol configuration identifies a pattern of uplink symbols, downlink symbols, and flexible symbols on one or more time slots of a carrier bandwidth; receiving a bandwidth configuration identifying a RedCap-specific BWP allocated to the UE within the carrier bandwidth and a configuration for CD-SSB transmission; receiving an NCD-SSB configuration identifying at least a frequency of an NCD-SSB transmission and a time offset of the NCD-SSB transmission relative to the CD-SSB transmission; and marking the configured flexible symbols as downlink symbols in response to one or more of the NCD-SSB symbols of the NCD-SSB transmission or the CD-SSB symbols of the CD-SSB transmission overlapping with the configured flexible symbols of the TDD uplink-downlink symbol configuration.

[0156] Additionally, the UE may perform or operate according to one or more aspects as described below. A first aspect may include a UE configured for wireless communication, the wireless communication including: obtaining a TDD uplink-downlink symbol configuration, wherein the TDD uplink-downlink symbol configuration identifies a pattern of uplink symbols, downlink symbols, and flexible symbols on one or more time slots of a carrier bandwidth; receiving a bandwidth configuration identifying a BWP allocated to the UE within the carrier bandwidth and a configuration for CD-SSB transmission; receiving an NCD-SSB configuration identifying at least a frequency of an NCD-SSB transmission and a time offset of the NCD-SSB transmission relative to the CD-SSB transmission; and marking the configured flexible symbol as a downlink symbol in response to one or more of the NCD-SSB symbol of the NCD-SSB transmission or the CD-SSB symbol of the CD-SSB transmission overlapping with a configured flexible symbol of the TDD uplink-downlink symbol configuration. Some specific implementations may include a processor coupled to a memory having computer code thereon, the computer code enabling functionality when executed by the processor. The processor may be configured to perform the operations described herein with respect to the apparatus. In some other implementations, the UE may include a non-transitory computer-readable medium having a program code recorded thereon, and the program code may be executable by a computer to cause the computer to perform the operations described herein with reference to the UE. In some implementations, the UE may include one or more components configured to perform the operations described herein. In some implementations, a method of wireless communication may include one or more operations described herein with reference to the UE.

[0157] In a second aspect, alone or in combination with the first aspect, wherein the marking comprises: marking the configured flexible symbol as the downlink symbol in response to the CD-SSB symbol or the NCD-SSB symbol overlapping with the configured flexible symbol.

[0158] In a third aspect, alone or in combination with one or more of the first aspect or the second aspect, the marking includes: marking the configured flexible symbol as the downlink symbol in response to the NCD-SSB symbol overlapping with the configured flexible symbol but not in response to the CD-SSB symbol overlapping with the configured flexible symbol.

[0159] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the marking includes: marking the configured flexible symbol as the downlink symbol in response to the CD-SSB symbol overlapping with the configured flexible symbol but not in response to the NCD-SSB symbol overlapping with the configured flexible symbol.

[0160] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, wherein the UE comprises a RedCap UE with reduced capacity, and wherein the RedCap UE is one of the following: capable of tuning outside of the RedCap-specific BWP, or not capable of tuning outside of the RedCap-specific BWP.

[0161] A sixth aspect of wireless communication performed by the UE may include: obtaining a TDD uplink-downlink symbol configuration, wherein the TDD uplink-downlink symbol configuration identifies a pattern of uplink symbols, downlink symbols, and flexible symbols on one or more time slots of a carrier bandwidth; receiving a bandwidth configuration identifying a RedCap-specific BWP allocated to the UE within the carrier bandwidth and a configuration for CD-SSB transmission; receiving an NCD-SSB configuration identifying at least a frequency of an NCD-SSB transmission and a time offset of the NCD-SSB transmission relative to the CD-SSB transmission; and validating the one or more NCD-SSB symbols as invalid in response to one or more NCD-SSB symbols of a plurality of NCD-SSB symbols scheduled according to the NCD-SSB configuration overlapping with one or more configured uplink symbols of the TDD uplink-downlink symbol configuration.

[0162] In a seventh aspect, alone or in combination with the sixth aspect, the verifying as invalid comprises: verifying the multiple NCD-SSB symbols as invalid in response to one of the multiple NCD-SSB symbols overlapping with one of the one or more configured uplink symbols.

[0163] In an eighth aspect, either alone or in combination with one or more of the sixth or seventh aspects, the wireless communication further comprises: verifying as valid one or more valid NCD-SSB symbols that do not overlap with the one or more configured uplink symbols, wherein the verification as invalid comprises: verifying as invalid the one or more NCD-SSB symbols in response to each of the one or more NCD-SSB symbols overlapping with the one or more configured uplink symbols.

[0164] In a ninth aspect, either alone or in combination with one or more of aspects 6 to 8, the wireless communication further comprises: monitoring the one or more valid NCD-SSB symbols for a first SSB index set; and monitoring one or more CD-SSB symbols outside the RedCap-specific BWP for a second SSB index set, wherein the second SSB index set corresponds to one or more SSB indices associated with the one or more NCD-SSB symbols that have been verified to be invalid.

[0165] In a tenth aspect, either alone or in combination with one or more of aspects six to nine, wherein the UE comprises a RedCap UE with reduced capacity, and wherein the RedCap UE is one of: capable of tuning outside of the RedCap-specific BWP, or not capable of tuning outside of the RedCap-specific BWP.

[0166] An eleventh aspect of wireless communication performed by a UE may include: obtaining a PRACH configuration, wherein the PRACH configuration identifies multiple RACH opportunities within a RACH time slot; receiving a bandwidth configuration identifying a BWP allocated to the UE within a carrier bandwidth and a configuration for CD-SSB transmission; receiving an NCD-SSB configuration identifying at least a frequency of an NCD-SSB transmission and a time offset of the NCD-SSB transmission relative to the CD-SSB transmission; and validating the RACH opportunity as invalid in response to a conflict between a RACH opportunity among the multiple RACH opportunities and an NCD-SSB symbol of the NCD-SSB transmission, a CD-SSB symbol of the CD-SSB transmission, or a combination of the NCD-SSB symbol and the CD-SSB symbol.

[0167] In a twelfth aspect, alone or in combination with the eleventh aspect, wherein the validating as invalid comprises: validating the RACH opportunity as invalid in response to the collision between the RACH opportunity and the NCD-SSB symbol.

[0168] In a thirteenth aspect, alone or in combination with one or more of the eleventh aspect or the twelfth aspect, wherein the BWP comprises a RedCap-specific initial BWP, and wherein the verification as invalid comprises one of: verifying the RACH opportunity as invalid in response to the conflict between the RACH opportunity and one of the NCD-SSB symbol or the CD-SSB symbol, wherein the UE is able to tune outside the BWP to detect the CD-SSB transmission, or verifying the RACH opportunity as invalid in response to the conflict between the RACH opportunity and the NCD-SSB symbol.

[0169] In a fourteenth aspect, alone or in combination with one or more of aspects eleven to thirteen, wherein the BWP comprises a RedCap-specific initial BWP and the RACH opportunity comprises a common RACH opportunity within the carrier bandwidth, and wherein the verification as invalid comprises: verifying the RACH opportunity as invalid in response to the conflict between the RACH opportunity and the CD-SSB symbol.

[0170] In a fifteenth aspect, alone or in combination with one or more of aspects eleven to fourteen, the conflict corresponds to one of the following: the RACH opportunity overlaps with the NCD-SSB symbol or the CD-SSB symbol, or the RACH opportunity overlaps with the spectrum within the BWP for a predefined number of symbols from the end of one or more of the NCD-SSB symbol or the CD-SSB symbol; or the RACH opportunity is located before the position of the NCD-SSB symbol or the CD-SSB symbol within the time slot.

[0171] In a sixteenth aspect, either alone or in combination with one or more of aspects eleven to fifteen, wherein the UE comprises a RedCap UE with reduced capacity, and wherein the RedCap UE is one of the following: capable of tuning outside the BWP, or not capable of tuning outside the BWP.

[0172] The seventeenth aspect may include a UE, which includes a memory that stores processor-readable code; and at least one processor, which is coupled to the memory, and the at least one processor is configured to execute the processor-readable code to enable the at least one processor to: obtain a TDD uplink-downlink symbol configuration, wherein the TDD uplink-downlink symbol configuration identifies a pattern of uplink symbols, downlink symbols, and flexible symbols on one or more time slots of a carrier bandwidth; receive a bandwidth configuration that identifies a BWP allocated to the UE within the carrier bandwidth and a configuration for CD-SSB transmission; receive an NCD-SSB configuration that at least identifies a frequency of an NCD-SSB transmission and a time offset of the NCD-SSB transmission relative to the CD-SSB transmission; and mark the configured flexible symbol as a downlink symbol in response to one or more of the NCD-SSB symbols of the NCD-SSB transmission or the CD-SSB symbols of the CD-SSB transmission overlapping with a configured flexible symbol of the TDD uplink-downlink symbol configuration.

[0173] In the eighteenth aspect, alone or in combination with the seventeenth aspect, the configuration of the at least one processor for marking includes the configuration of the at least one processor for performing the following operations: marking the flexible symbol of the configuration as the downlink symbol in response to the CD-SSB symbol or the NCD-SSB symbol overlapping with the flexible symbol of the configuration.

[0174] In a nineteenth aspect, alone or in combination with one or more of the seventeenth aspect or the eighteenth aspect, the configuration of the at least one processor for marking includes a configuration of the at least one processor for performing the following operations: marking the configured flexible symbol as the downlink symbol in response to the NCD-SSB symbol overlapping with the configured flexible symbol but not in response to the CD-SSB symbol overlapping with the configured flexible symbol.

[0175] In the twentieth aspect, alone or in combination with one or more of aspects seventeen to nineteen, the configuration of the at least one processor for marking includes the configuration of the at least one processor for performing the following operations: marking the flexible symbol of the configuration as the downlink symbol in response to the CD-SSB symbol overlapping with the flexible symbol of the configuration but not in response to the NCD-SSB symbol overlapping with the flexible symbol of the configuration.

[0176] In a twenty-first aspect, either alone or in combination with one or more of aspects seventeen to twentieth, wherein the UE comprises a RedCap UE with reduced capacity, and wherein the RedCap UE is one of the following: capable of tuning outside the BWP, or not capable of tuning outside the BWP.

[0177] A twenty-second aspect may include a UE comprising a memory storing processor-readable code; and at least one processor coupled to the memory, the at least one processor configured to execute the processor-readable code to enable the at least one processor to: obtain a TDD uplink-downlink symbol configuration, wherein the TDD uplink-downlink symbol configuration identifies a pattern of uplink symbols, downlink symbols, and flexible symbols on one or more time slots of a carrier bandwidth; receive a bandwidth configuration identifying a RedCap-specific BWP allocated to the UE within the carrier bandwidth and a configuration for CD-SSB transmission; receive an NCD-SSB configuration identifying at least a frequency of an NCD-SSB transmission and a time offset of the NCD-SSB transmission relative to the CD-SSB transmission; and verify the one or more NCD-SSB symbols as invalid in response to one or more NCD-SSB symbols of a plurality of NCD-SSB symbols scheduled according to the NCD-SSB configuration overlapping with one or more configured uplink symbols of the TDD uplink-downlink symbol configuration.

[0178] In the twenty-third aspect, alone or in combination with the twenty-second aspect, the configuration in which the at least one processor is used to verify as invalid includes the configuration in which the at least one processor is used to perform the following operations: verifying the multiple NCD-SSB symbols as invalid in response to one of the multiple NCD-SSB symbols overlapping with one of the one or more configured uplink symbols.

[0179] In aspect twenty-four, alone or in combination with one or more of aspect twenty-two or aspect twenty-three, the UE also includes a configuration of the at least one processor for verifying as valid one or more valid NCD-SSB symbols that do not overlap with the one or more configured uplink symbols, wherein the configuration of the at least one processor for verifying as invalid includes a configuration of the at least one processor for performing the following operation: verifying as invalid the one or more NCD-SSB symbols in response to each of the one or more NCD-SSB symbols overlapping with the one or more configured uplink symbols.

[0180] In aspect twenty-fifth, alone or in combination with one or more of aspects twenty-second to twenty-fourth, the UE also includes a configuration of the at least one processor for: monitoring the one or more valid NCD-SSB symbols for a first SSB index set; and monitoring one or more CD-SSB symbols outside the RedCap-specific BWP for a second SSB index set, wherein the second SSB index set corresponds to one or more SSB indices associated with the one or more NCD-SSB symbols that have been verified to be invalid.

[0181] In a twenty-sixth aspect, either alone or in combination with one or more of aspects twenty-second to twenty-fifth, wherein the UE comprises a RedCap UE with reduced capacity, and wherein the RedCap UE is one of the following: capable of tuning outside of the RedCap-specific BWP, or not capable of tuning outside of the RedCap-specific BWP.

[0182] The twenty-seventh aspect may include a UE, the UE including a memory storing a processor-readable code; and at least one processor coupled to the memory, the at least one processor configured to execute the processor-readable code to enable the at least one processor to: obtain a PRACH configuration, wherein the PRACH configuration identifies multiple RACH opportunities within a RACH time slot; receive a bandwidth configuration identifying a BWP allocated to the UE within a carrier bandwidth and a configuration for CD-SSB transmission; receive an NCD-SSB configuration identifying at least a frequency of an NCD-SSB transmission and a time offset of the NCD-SSB transmission relative to the CD-SSB transmission; and verify the RACH opportunity as invalid in response to a conflict between a RACH opportunity among the multiple RACH opportunities and an NCD-SSB symbol of the NCD-SSB transmission, a CD-SSB symbol of the CD-SSB transmission, or a combination of the NCD-SSB symbol and the CD-SSB symbol.

[0183] In a twenty-eighth aspect, alone or in combination with the twenty-seventh aspect, wherein the validating as invalid comprises: validating the RACH opportunity as invalid in response to the collision between the RACH opportunity and the NCD-SSB symbol.

[0184] In a twenty-ninth aspect, alone and in combination with aspect twenty-seven or aspect twenty-eight, wherein the BWP comprises a RedCap-specific initial BWP and the RACH opportunity comprises a dedicated RACH opportunity within the RedCap-specific initial BWP, and wherein the configuration of the at least one processor for validating as invalid comprises the configuration of the at least one processor for performing one of the following operations: validating the dedicated RACH opportunity as invalid in response to the conflict between the dedicated RACH opportunity and one of the NCD-SSB symbol or the CD-SSB symbol, wherein the UE is able to tune outside the BWP to detect the CD-SSB transmission, or validating the RACH opportunity as invalid in response to the conflict between the RACH opportunity and the NCD-SSB symbol.

[0185] In a thirtieth aspect, alone or in combination with one or more of aspects twenty-seven to twenty-ninth, wherein the BWP comprises a RedCap-specific initial BWP and the RACH opportunity comprises a common RACH opportunity within the carrier bandwidth, and wherein the configuration of the at least one processor for validating as invalid comprises the configuration of the at least one processor for performing the following operations: validating the RACH opportunity as invalid in response to the conflict between the RACH opportunity and the CD-SSB symbol.

[0186] In the thirty-first aspect, alone or in combination with one or more of aspects twenty-seven to thirtieth, the conflict corresponds to one of the following: the RACH opportunity overlaps with the NCD-SSB symbol or the CD-SSB symbol, or the RACH opportunity overlaps with the spectrum within the BWP for a predefined number of symbols from the end of one or more of the NCD-SSB symbol or the CD-SSB symbol; or the RACH opportunity is located before the position of the NCD-SSB symbol or the CD-SSB symbol within the time slot.

[0187] In aspect 32, either alone or in combination with one or more of aspects 27 to 31, wherein the UE comprises a RedCap UE with reduced capacity, and wherein the RedCap UE is one of the following: capable of tuning outside the BWP, or unable to tune outside the BWP.

[0188] A thirty-third aspect may include a UE configured for wireless communication, the UE comprising: a component for obtaining a TDD uplink-downlink symbol configuration, wherein the TDD uplink-downlink symbol configuration identifies a pattern of uplink symbols, downlink symbols, and flexible symbols on one or more time slots of a carrier bandwidth; a component for receiving a bandwidth configuration identifying a BWP allocated to the UE within the carrier bandwidth and a configuration for CD-SSB transmission; a component for receiving an NCD-SSB configuration identifying at least a frequency of an NCD-SSB transmission and a time offset of the NCD-SSB transmission relative to the CD-SSB transmission; and a component for marking a configured flexible symbol as a downlink symbol in response to one or more of the NCD-SSB symbols of the NCD-SSB transmission or the CD-SSB symbols of the CD-SSB transmission overlapping with a configured flexible symbol of the TDD uplink-downlink symbol configuration.

[0189] In a thirty-fourth aspect, alone or in combination with the thirty-third aspect, the means for marking includes means for marking the configured flexible symbol as the downlink symbol in response to the CD-SSB symbol or the NCD-SSB symbol overlapping with the configured flexible symbol.

[0190] In an aspect thirty-fifth, alone or in combination with one or more of aspects thirty-third or thirty-fourth, the component for marking includes a component for marking the configured flexible symbol as the downlink symbol in response to the NCD-SSB symbol overlapping with the configured flexible symbol but not in response to the CD-SSB symbol overlapping with the configured flexible symbol.

[0191] In an aspect thirty-six, alone or in combination with one or more of aspects thirty-three to thirty-five, the component for marking includes a component for marking the configured flexible symbol as the downlink symbol in response to the CD-SSB symbol overlapping with the configured flexible symbol but not in response to the NCD-SSB symbol overlapping with the configured flexible symbol.

[0192] In aspect thirty-seven, alone or in combination with one or more of aspects thirty-three to thirty-six, wherein the UE comprises a RedCap UE with reduced capacity, and wherein the RedCap UE is one of the following: capable of tuning outside the BWP, or unable to tune outside the BWP.

[0193] A thirty-eighth aspect may include a UE configured for wireless communication, the UE comprising: a component for obtaining a TDD uplink-downlink symbol configuration, wherein the TDD uplink-downlink symbol configuration identifies a pattern of uplink symbols, downlink symbols and flexible symbols on one or more time slots of a carrier bandwidth; a component for receiving a bandwidth configuration identifying a RedCap-specific BWP allocated to the UE within the carrier bandwidth and a configuration for CD-SSB transmission; a component for receiving an NCD-SSB configuration identifying at least a frequency of an NCD-SSB transmission and a time offset of the NCD-SSB transmission relative to the CD-SSB transmission; and a component for verifying one or more NCD-SSB symbols as invalid in response to one or more NCD-SSB symbols of a plurality of NCD-SSB symbols scheduled according to the NCD-SSB configuration overlapping with one or more configured uplink symbols of the TDD uplink-downlink symbol configuration.

[0194] In the thirty-ninth aspect, alone or in combination with the thirty-eighth aspect, the component for verifying as invalid includes: a component for verifying the multiple NCD-SSB symbols as invalid in response to one of the multiple NCD-SSB symbols overlapping with one of the one or more configured uplink symbols.

[0195] In the 40th aspect, alone or in combination with one or more of the 38th aspect or the 39th aspect, the UE also includes: a component for verifying that one or more valid NCD-SSB symbols that do not overlap with the one or more configured uplink symbols are valid, wherein the component for verifying as invalid includes a component for verifying the one or more NCD-SSB symbols as invalid in response to each NCD-SSB symbol of the one or more NCD-SSB symbols overlapping with the one or more configured uplink symbols.

[0196] In the forty-first aspect, alone or in combination with one or more of aspects 38 to 40, the UE also includes: a component for monitoring the one or more valid NCD-SSB symbols for a first SSB index set; and a component for monitoring one or more CD-SSB symbols outside the RedCap-specific BWP for a second SSB index set, wherein the second SSB index set corresponds to one or more SSB indices associated with the one or more NCD-SSB symbols that have been verified to be invalid.

[0197] In aspect 42, either alone or in combination with one or more of aspects 38 to 41, wherein the UE comprises a RedCap UE with reduced capacity, and wherein the RedCap UE is one of: capable of tuning outside of the RedCap-specific BWP, or not capable of tuning outside of the RedCap-specific BWP.

[0198] A forty-third aspect may include a UE configured for wireless communication, the UE comprising: a component for obtaining a PRACH configuration, wherein the PRACH configuration identifies multiple RACH opportunities within a RACH time slot; a component for receiving a bandwidth configuration identifying a BWP allocated to the UE within a carrier bandwidth and a configuration for CD-SSB transmission; a component for receiving an NCD-SSB configuration identifying at least a frequency of an NCD-SSB transmission and a time offset of the NCD-SSB transmission relative to the CD-SSB transmission; and a component for verifying the RACH opportunity as invalid in response to a conflict between a RACH opportunity among the multiple RACH opportunities and an NCD-SSB symbol of the NCD-SSB transmission, a CD-SSB symbol of the CD-SSB transmission, or a combination of the NCD-SSB symbol and the CD-SSB symbol.

[0199] In a forty-fourth aspect, alone or in combination with the forty-third aspect, the means for verifying as invalid comprises means for verifying the RACH opportunity as invalid in response to the conflict between the RACH opportunity and the NCD-SSB symbol.

[0200] In a forty-fifth aspect, alone or in combination with one or more of the forty-third aspect or the forty-fourth aspect, wherein the BWP comprises a RedCap-specific initial BWP and the RACH opportunity comprises a dedicated RACH opportunity within the RedCap-specific initial BWP, and wherein the means for verifying as invalid comprises any of the following: means for verifying the dedicated RACH opportunity as invalid in response to the conflict between the dedicated RACH opportunity and one of the NCD-SSB symbol or the CD-SSB symbol, wherein the UE is capable of tuning outside the BWP to detect the CD-SSB transmission, or means for verifying the RACH opportunity as invalid in response to the conflict between the RACH opportunity and the NCD-SSB symbol.

[0201] In a forty-sixth aspect, alone or in combination with one or more of aspects forty-three to forty-fifth aspects, wherein the BWP comprises a RedCap-specific initial BWP and the RACH opportunity comprises a common RACH opportunity within the carrier bandwidth, and wherein the means for validating as invalid comprises means for validating the RACH opportunity as invalid in response to the conflict between the CD-SSB symbols of the RACH opportunity.

[0202] In aspect 47, alone or in combination with one or more of aspects 43 to 46, the conflict corresponds to one of: the RACH opportunity overlaps with the NCD-SSB symbol or the CD-SSB symbol, or the RACH opportunity overlaps with the spectrum within the BWP for a predefined number of symbols from the end of one or more of the NCD-SSB symbol or the CD-SSB symbol; or the RACH opportunity is located before the position of the NCD-SSB symbol or the CD-SSB symbol within the time slot.

[0203] In a 48th aspect, either alone or in combination with one or more of aspects 43 to 47, wherein the UE comprises a RedCap UE with reduced capacity, and wherein the RedCap UE is one of the following: capable of tuning outside the BWP, or not capable of tuning outside the BWP.

[0204] The forty-ninth aspect may include a non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform operations including: obtaining a TDD uplink-downlink symbol configuration, wherein the TDD uplink-downlink symbol configuration identifies a pattern of uplink symbols, downlink symbols, and flexible symbols on one or more time slots of a carrier bandwidth; receiving a bandwidth configuration identifying a BWP allocated to the UE within the carrier bandwidth and a configuration for CD-SSB transmission; receiving an NCD-SSB configuration identifying at least a frequency of an NCD-SSB transmission and a time offset of the NCD-SSB transmission relative to the CD-SSB transmission; and marking a flexible symbol of the configuration as a downlink symbol in response to one or more of the NCD-SSB symbols of the NCD-SSB transmission or the CD-SSB symbols of the CD-SSB transmission overlapping with a configured flexible symbol of the TDD uplink-downlink symbol configuration.

[0205] In the fiftieth aspect, alone or in combination with the forty-ninth aspect, the instruction executed by the processor to cause the processor to mark includes an instruction executed by the processor to cause the processor to perform the following operations: marking the configured flexible symbol as the downlink symbol in response to the CD-SSB symbol or the NCD-SSB symbol overlapping with the configured flexible symbol.

[0206] In the fifty-first aspect, alone or in combination with one or more of the forty-ninth aspect or the fiftieth aspect, the instructions executed by the processor to cause the processor to perform the marking include instructions executed by the processor to cause the processor to perform the following operations: marking the configured flexible symbol as the downlink symbol in response to the NCD-SSB symbol overlapping with the configured flexible symbol but not in response to the CD-SSB symbol overlapping with the configured flexible symbol.

[0207] In aspect fifty-second, alone or in combination with one or more of aspects forty-ninth to fifty-second, the instructions executed by the processor to cause the processor to mark include instructions executed by the processor to cause the processor to perform the following operations: marking the configured flexible symbol as the downlink symbol in response to the CD-SSB symbol overlapping with the configured flexible symbol but not in response to the NCD-SSB symbol overlapping with the configured flexible symbol.

[0208] In a fifty-third aspect, either alone or in combination with one or more of aspects forty-ninth to fifty-second, wherein the UE comprises a RedCap UE with reduced capacity, and wherein the RedCap UE is one of the following: capable of tuning outside the BWP, or not capable of tuning outside the BWP.

[0209] The fifty-fourth aspect may include a non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform operations including: obtaining a TDD uplink-downlink symbol configuration, wherein the TDD uplink-downlink symbol configuration identifies a pattern of uplink symbols, downlink symbols, and flexible symbols on one or more time slots of a carrier bandwidth; receiving a bandwidth configuration identifying a RedCap-specific BWP allocated to the UE within the carrier bandwidth and a configuration for CD-SSB transmission; receiving an NCD-SSB configuration identifying at least a frequency of an NCD-SSB transmission and a time offset of the NCD-SSB transmission relative to the CD-SSB transmission; and validating the one or more NCD-SSB symbols as invalid in response to one or more NCD-SSB symbols of a plurality of NCD-SSB symbols scheduled according to the NCD-SSB configuration overlapping with one or more configured uplink symbols of the TDD uplink-downlink symbol configuration.

[0210] In the fifty-fifth aspect, alone or in combination with the fifty-fourth aspect, the instruction executed by the processor to cause the processor to verify as invalid includes an instruction executed by the processor to cause the processor to perform the following operations: verifying the multiple NCD-SSB symbols as invalid in response to one of the multiple NCD-SSB symbols overlapping with one of the one or more configured uplink symbols.

[0211] In the fifty-sixth aspect, alone or in combination with one or more of the fifty-fourth aspect or the fifty-fifth aspect, the non-transitory computer-readable medium also includes instructions executed by the processor to cause the processor to perform the following operations: verifying one or more valid NCD-SSB symbols that do not overlap with the one or more configured uplink symbols as valid, wherein the instructions executed by the processor to cause the processor to verify as invalid include instructions executed by the processor to cause the processor to perform the following operations: verifying the one or more NCD-SSB symbols as invalid in response to each NCD-SSB symbol of the one or more NCD-SSB symbols overlapping with the one or more configured uplink symbols.

[0212] In aspect fifty-seven, alone or in combination with one or more of aspects fifty-four to fifty-six, the non-transitory computer-readable medium further comprises instructions executed by the processor causing the processor to: monitor the one or more valid NCD-SSB symbols for a first SSB index set; and monitor one or more CD-SSB symbols outside the RedCap-specific BWP for a second SSB index set, wherein the second SSB index set corresponds to one or more SSB indices associated with the one or more NCD-SSB symbols that have been verified to be invalid.

[0213] In aspect fifty-eight, alone or in combination with one or more of aspects fifty-four to fifty-seven, wherein the UE comprises a RedCap UE with reduced capacity, and wherein the RedCap UE is one of: capable of tuning outside of the RedCap-specific BWP, or not capable of tuning outside of the RedCap-specific BWP.

[0214] The fifty-ninth aspect may include a non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform operations including: obtaining a PRACH configuration, wherein the PRACH configuration identifies multiple RACH opportunities within a RACH time slot; receiving a bandwidth configuration identifying a BWP allocated to the UE within a carrier bandwidth and a configuration for CD-SSB transmission; receiving an NCD-SSB configuration identifying at least a frequency of an NCD-SSB transmission and a time offset of the NCD-SSB transmission relative to the CD-SSB transmission; and validating the RACH opportunity as invalid in response to a conflict between a RACH opportunity among the multiple RACH opportunities and an NCD-SSB symbol of the NCD-SSB transmission, a CD-SSB symbol of the CD-SSB transmission, or a combination of the NCD-SSB symbol and the CD-SSB symbol.

[0215] In a sixtieth aspect, alone or in combination with the fifty-ninth aspect, wherein the validating as invalid comprises: validating the RACH opportunity as invalid in response to the conflict between the RACH opportunity and the NCD-SSB symbol.

[0216] In the sixty-first aspect, alone or in combination with one or more of the fifty-ninth aspect or the sixtieth aspect, wherein the BWP includes a RedCap-specific initial BWP and the RACH opportunity includes a dedicated RACH opportunity within the RedCap-specific initial BWP, and wherein the instruction executed by the processor to cause the processor to verify as invalid includes an instruction executed by the processor to cause the processor to perform one of the following operations: verifying the dedicated RACH opportunity as invalid in response to the conflict between the dedicated RACH opportunity and one of the NCD-SSB symbol or the CD-SSB symbol, wherein the UE is able to tune outside the BWP to detect the CD-SSB transmission, or verifying the RACH opportunity as invalid in response to the conflict between the RACH opportunity and the NCD-SSB symbol.

[0217] In a sixty-second aspect, alone or in combination with one or more of aspects fifty-ninth to sixty-first, wherein the BWP comprises a RedCap-specific initial BWP and the RACH opportunity comprises a common RACH opportunity within the carrier bandwidth, and wherein the instructions executed by the processor to cause the processor to verify as invalid include instructions executed by the processor to cause the processor to perform the following operations: verify the RACH opportunity as invalid in response to the conflict between the RACH opportunity and the CD-SSB symbol.

[0218] In a sixty-third aspect, alone or in combination with one or more of aspects fifty-ninth to sixty-second, wherein the conflict corresponds to one of the following: the RACH opportunity overlaps with the NCD-SSB symbol or the CD-SSB symbol, or the RACH opportunity overlaps with the spectrum within the BWP for a predefined number of symbols from the end of one or more of the NCD-SSB symbol or the CD-SSB symbol; or the RACH opportunity is located before the position of the NCD-SSB symbol or the CD-SSB symbol within the time slot.

[0219] In a sixty-fourth aspect, either alone or in combination with one or more of aspects fifty-ninth to sixty-third, wherein the UE comprises a RedCap UE with reduced capacity, and wherein the RedCap UE is one of the following: capable of tuning outside the BWP, or not capable of tuning outside the BWP.

[0220] It should be understood by those skilled in the art that any of a variety of different technologies and techniques may be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0221] This article is relative to Figures 1 to 11 The components, functional blocks and modules include processors, electronic devices, hardware devices, electronic components, logic circuits, memories, software codes, etc., or any combination thereof. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and / or functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms. In addition, the features discussed herein may be implemented via a dedicated processor circuit system, via executable instructions, or a combination thereof.

[0222] The technician will further understand that the various exemplary logic boxes, modules, circuits and algorithm steps described in conjunction with the disclosure of this article can be implemented as electronic hardware, computer software or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various exemplary components, blocks, modules, circuits and steps have been generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints proposed to the entire system. The technician can implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be interpreted as causing departure from the scope of the present disclosure. The technician will also easily recognize that the order or combination of components, methods or interactions described herein are only examples, and the components, methods or interactions of various aspects of the present disclosure can be combined or performed in a manner other than the manner illustrated and described herein.

[0223] The various illustrative logical components, logic blocks, modules, circuits, and algorithmic processes described in conjunction with the specific implementations disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. The interchangeability of hardware and software has been generally described in terms of functionality and is illustrated in the various illustrative components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0224] The hardware and data processing apparatus for implementing the various exemplary logics, logic blocks, modules and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed using a general purpose single-chip or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, a discrete hardware component or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller or state machine. In some specific implementations, a processor may be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration. In some specific implementations, a particular process and method may be performed by a circuit system specific to a given function.

[0225] In one or more aspects, the functions described may be implemented in hardware, digital electronic circuitry, software, including the structures disclosed in this specification and their structural equivalents, or in any combination thereof. Specific implementations of the subject matter described in this specification may also be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on computer storage media for execution by data processing apparatus or for controlling the operation of data processing apparatus.

[0226] If implemented in software, the function may be stored as one or more instructions or codes on a computer-readable medium or sent via a computer-readable medium. The process of the method or algorithm disclosed herein may be implemented in a processor executable software module that may reside on a computer-readable medium. Computer-readable media include both computer storage media and communication media, and the communication media include any media that can be implemented to transfer a computer program from one place to another. The storage medium may be any available medium that a computer can access. As an example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to store the required program code in the form of an instruction or data structure and can be accessed by a computer. In addition, any connection may be appropriately referred to as a computer-readable medium. Disks and optical disks as used herein include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and blue-ray disks, wherein disks generally reproduce data magnetically, and optical disks reproduce data optically with lasers. The above combination should also be included in the scope of computer-readable media. Additionally, the operations of a method or algorithm may reside as a code and instruction set, or any combination of code and instruction sets, on a machine-readable medium or computer-readable medium, which may be incorporated into a computer program product.

[0227] Various modifications to the specific implementations described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to some other specific implementations without departing from the spirit or scope of the disclosure. Therefore, the claims are not intended to be limited to the specific implementations shown herein, but are to be consistent with the broadest scope consistent with the disclosure, the principles and novel features disclosed herein.

[0228] Additionally, one of ordinary skill in the art will readily recognize that the terms "upper" and "lower" are sometimes used for ease of describing the drawings and indicate relative positions corresponding to the orientation of the drawings on a correctly oriented page, and may not reflect the correct orientation of any device as implemented.

[0229] Certain features described in this specification in the context of separate implementations may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented in multiple implementations, either individually or in any suitable subcombination. Furthermore, while features may be described above as functioning in certain combinations and even initially claimed as such, one or more features from a claimed combination may in some cases be removed from the combination, and a claimed combination may be directed to subcombinations or variations of subcombinations.

[0230] Similarly, although the operations are depicted in a specific order in the accompanying drawings, this should not be understood as requiring such operations to be performed in the specific order shown or in a sequential order, or to perform all illustrated operations to achieve the desired result. In addition, the accompanying drawings can schematically depict one or more example processes in the form of a flow chart. However, other operations that are not depicted can be combined in the schematically illustrated example process. For example, one or more additional operations can be performed before, after, at the same time, or between any illustrated operations. In some environments, multitasking and parallel processing are advantageous. In addition, the separation of various system components in the specific implementation described above should not be understood as requiring such separation in all specific implementations, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, some other specific implementations also fall within the scope of the appended claims. In some cases, the actions narrated in the claims can be performed in different orders and still achieve the desired result.

[0231] As used herein, including in the claims, the term "or" used in a list of two or more items means that any of the listed items may be employed alone, or any combination of two or more of the listed items may be employed. For example, where a composition is described as containing components A, B, or C, the composition may contain A alone; B alone; C alone; A and B in combination; A and C in combination; B and C in combination; or A, B, and C in combination. In addition, as used herein, including in the claims, "or" as used in a list of items beginning with "at least one" indicates a separate list, so that, for example, a list of "at least one of A, B, or C" means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) or any combination of any of these. The term "substantially" is defined as to a large extent, but not necessarily entirely, what is specified (and includes what is specified; for example, substantially 90 degrees includes 90 degrees, and substantially parallel includes parallel), as understood by one of ordinary skill in the art. In any disclosed implementation, the term "substantially" may be replaced with "within [percent] of" a specified content, where the percentage includes 0.1%, 1%, 5%, or 10%.

[0232] The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Therefore, the disclosure is not intended to be limited to the examples and designs described herein, but to be consistent with the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method of wireless communication performed by a user equipment (UE), the method comprising: obtaining a time division duplex (TDD) uplink-downlink symbol configuration, wherein the TDD uplink-downlink symbol configuration identifies a pattern of uplink symbols, downlink symbols, and flexible symbols over one or more time slots of a carrier bandwidth; receiving a bandwidth configuration identifying a bandwidth part (BWP) allocated to the UE within the carrier bandwidth and a configuration for cell definition synchronization signal block (CD-SSB) transmission; receiving a non-cell defining synchronization signal block (NCD-SSB) configuration identifying at least a frequency of NCD-SSB transmissions and a time offset of said NCD-SSB transmissions relative to said CD-SSB transmissions; and In response to one or more of the NCD-SSB symbols sent by the NCD-SSB or the CD-SSB symbols sent by the CD-SSB overlapping with the configured flexible symbols of the TDD uplink-downlink symbol configuration, the configured flexible symbols are marked as downlink symbols.

2. The method of claim 1, wherein the NCD-SSB is associated with an active BWP of the UE.

3. The method of claim 1, wherein the BWP is a reduced capacity (RedCap) specific BWP.

4. The method according to claim 1, The markings include: The configured flexible symbol is marked as the downlink symbol in response to the CD-SSB symbol or the NCD-SSB symbol overlapping with the configured flexible symbol.

5. The method according to claim 1, The markings include: The configured flexible symbol is marked as the downlink symbol in response to the NCD-SSB symbol overlapping the configured flexible symbol but not in response to the CD-SSB symbol overlapping the configured flexible symbol.

6. The method according to claim 1, The markings include: The configured flexible symbol is marked as the downlink symbol in response to the CD-SSB symbol overlapping the configured flexible symbol but not in response to the NCD-SSB symbol overlapping the configured flexible symbol.

7. The method of claim 1, wherein the UE comprises a RedCap UE with reduced capacity, and wherein the RedCap UE is one of the following: can be tuned outside of the BWP, or Tuning outside of the BWP is not possible.

8. A method of wireless communication performed by a user equipment (UE), the method comprising: obtaining a physical random access channel (PRACH) configuration, wherein the PRACH configuration identifies a plurality of random access channel (RACH) opportunities within a RACH time slot; receiving a bandwidth configuration identifying a bandwidth part (BWP) allocated to the UE within a carrier bandwidth and a configuration for cell definition synchronization signal block (CD-SSB) transmission; receiving a non-cell defining synchronization signal block (NCD-SSB) configuration identifying at least a frequency of NCD-SSB transmissions and a time offset of said NCD-SSB transmissions relative to said CD-SSB transmissions; as well as The RACH opportunity is verified as invalid in response to a conflict between a RACH opportunity among the multiple RACH opportunities and an NCD-SSB symbol sent by the NCD-SSB, a CD-SSB symbol sent by the CD-SSB, or a combination of the NCD-SSB symbol and the CD-SSB symbol.

9. The method of claim 8, wherein the BWP is associated with an active BWP of the UE.

10. The method of claim 8, wherein the BWP is a Reduced Capacity (RedCap) specific BWP.

11. The method according to claim 8, wherein the verification as invalid comprises: The RACH opportunity is validated as invalid in response to the collision between the RACH opportunity and the NCD-SSB symbol.

12. The method according to claim 8, wherein the BWP comprises a reduced capacity (RedCap) specific initial BWP, and The invalid verification includes one of the following: validating the RACH opportunity as invalid in response to the collision between the RACH opportunity and one of the NCD-SSB symbol or the CD-SSB symbol, wherein the UE is capable of tuning outside of the BWP to detect the CD-SSB transmission, or The RACH opportunity is validated as invalid in response to the collision between the RACH opportunity and the NCD-SSB symbol.

13. The method according to claim 8, wherein the verification as invalid comprises: The RACH opportunity is validated as invalid in response to the collision between the RACH opportunity and the CD-SSB symbol.

14. The method of claim 8, wherein the conflict corresponds to one of the following: The RACH opportunity overlaps with the NCD-SSB symbol or the CD-SSB symbol, or The RACH opportunity overlaps with spectrum within the BWP for a predefined number of symbols from the end of one or more of the NCD-SSB symbol or the CD-SSB symbol; or The RACH opportunity is located before the position of the NCD-SSB symbol or the CD-SSB symbol in the time slot.

15. The method of claim 8, wherein the UE comprises a RedCap UE with reduced capacity, and wherein the RedCap UE is one of the following: can be tuned outside of the BWP, or Tuning outside of the BWP is not possible.

16. A user equipment (UE), the user equipment (UE) comprising: a memory storing processor readable code; and at least one processor, the at least one processor being coupled to the memory, the processor readable code being executable by the at least one processor to cause the UE to: Obtaining a time division duplex (TDD) uplink-downlink symbol configuration, wherein the TDD uplink-downlink symbol configuration identifies a pattern of uplink symbols, downlink symbols, and flexible symbols on one or more time slots of a carrier bandwidth; receiving a bandwidth configuration identifying a bandwidth part (BWP) allocated to the UE within the carrier bandwidth and a configuration for cell definition synchronization signal block (CD-SSB) transmission; receiving a non-cell defining synchronization signal block (NCD-SSB) configuration identifying at least a frequency of NCD-SSB transmissions and a time offset of said NCD-SSB transmissions relative to said CD-SSB transmissions; and In response to one or more of the NCD-SSB symbols sent by the NCD-SSB or the CD-SSB symbols sent by the CD-SSB overlapping with the configured flexible symbols of the TDD uplink-downlink symbol configuration, the configured flexible symbols are marked as downlink symbols.

17. The UE of claim 16, wherein the NCD-SSB is associated with an active BWP of the UE.

18. The UE of claim 16, wherein the BWP is a reduced capacity (RedCap) specific BWP.

19. The UE according to claim 16, wherein the processor-readable code capable of being executed by the at least one processor to enable the UE to mark is also capable of being executed by the at least one processor to enable the UE to: mark the configured flexible symbol as the downlink symbol in response to the CD-SSB symbol or the NCD-SSB symbol overlapping with the configured flexible symbol.

20. The UE of claim 16, wherein the processor-readable code executable by the at least one processor for marking comprises processor-readable code executable by the at least one processor for performing the following operations: marking the configured flexible symbol as the downlink symbol in response to the NCD-SSB symbol overlapping with the configured flexible symbol but not in response to the CD-SSB symbol overlapping with the configured flexible symbol.

21. The UE of claim 16, wherein the processor-readable code executable by the at least one processor for marking comprises a processor-readable code executable by the at least one processor for performing the following operations: marking the configured flexible symbol as the downlink symbol in response to the CD-SSB symbol overlapping with the configured flexible symbol but not in response to the NCD-SSB symbol overlapping with the configured flexible symbol.

22. The UE of claim 16, wherein the UE comprises a RedCap UE with reduced capacity, and wherein the RedCap UE is one of the following: can be tuned outside of the BWP, or Tuning outside of the BWP is not possible.

23. A user equipment (UE), the user equipment (UE) comprising: a memory storing processor readable code; and at least one processor, the at least one processor being coupled to the memory, the processor readable code being executable by the at least one processor to cause the UE to: obtaining a physical random access channel (PRACH) configuration, wherein the PRACH configuration identifies a plurality of random access channel (RACH) opportunities within a RACH time slot; receiving a bandwidth configuration identifying a bandwidth part (BWP) allocated to the UE within a carrier bandwidth and a configuration for cell definition synchronization signal block (CD-SSB) transmission; receiving a non-cell defining synchronization signal block (NCD-SSB) configuration identifying at least a frequency of NCD-SSB transmissions and a time offset of said NCD-SSB transmissions relative to said CD-SSB transmissions; as well as The RACH opportunity is verified as invalid in response to a conflict between a RACH opportunity among the multiple RACH opportunities and an NCD-SSB symbol sent by the NCD-SSB, a CD-SSB symbol sent by the CD-SSB, or a combination of the NCD-SSB symbol and the CD-SSB symbol.

24. The UE of claim 23, wherein the NCD-SSB is associated with an active BWP of the UE.

25. The UE of claim 23, wherein the BWP is a reduced capacity (RedCap) specific BWP.

26. The UE of claim 23, wherein the processor-readable code executable by the at least one processor to verify as invalid comprises processor-readable code executable by the at least one processor to perform the following operations: verifying the RACH opportunity as invalid in response to the conflict between the RACH opportunity and the NCD-SSB symbol.

27. The UE according to claim 23, wherein the BWP comprises a reduced capacity (RedCap) specific initial BWP, and Wherein the processor readable code executable by the at least one processor to verify as invalid comprises processor readable code executable by the at least one processor to perform one of the following operations: validating the RACH opportunity as invalid in response to the collision between the RACH opportunity and one of the NCD-SSB symbol or the CD-SSB symbol, wherein the UE is capable of tuning outside of the BWP to detect the CD-SSB transmission, or The RACH opportunity is validated as invalid in response to the collision between the RACH opportunity and the NCD-SSB symbol.

28. The UE of claim 23, wherein the processor-readable code executable by the at least one processor to verify as invalid comprises processor-readable code executable by the at least one processor to perform the following operations: verifying the RACH opportunity as invalid in response to the conflict between the RACH opportunity and the CD-SSB symbol.

29. The UE of claim 23, wherein the conflict corresponds to one of: The RACH opportunity overlaps with the NCD-SSB symbol or the CD-SSB symbol, or The RACH opportunity overlaps with spectrum within the BWP for a predefined number of symbols from the end of one or more of the NCD-SSB symbol or the CD-SSB symbol; or The RACH opportunity is located before the position of the NCD-SSB symbol or the CD-SSB symbol in the time slot.

30. The UE of claim 23, wherein the UE comprises a RedCap UE with reduced capacity, and wherein the RedCap UE is one of the following: can be tuned outside of the BWP, or Tuning outside of the BWP is not possible.

Images