Physical random access channel transmission

By managing the overlap between uplink PRACH transmission and downlink transmission in a wireless communication system, using synchronization signal blocks and configuration parameters, the problem of network performance degradation in the prior art is solved, and communication efficiency and reliability are improved.

CN118985168APending Publication Date: 2024-11-19QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280094667.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-04-20
Publication Date
2024-11-19

AI Technical Summary

Technical Problem

In wireless communication systems, it is difficult for the prior art to effectively manage the overlap between the uplink physical random access channel (PRACH) and downlink transmission, resulting in a degradation of network performance.

Method used

User equipment (UE) and network entities receive or send uplink PRACH transmissions in specific time resources by receiving synchronization signal blocks (SSBs) associated with the Random Access Channel (RACH) process, and discard the uplink if necessary. The PRACH transmission is sent to receive or send downlink transmissions, and the configuration parameters are used to determine the number and timing of discarding PRACH transmissions.

Benefits of technology

Improve network performance, avoid conflicts between uplink and downlink transmissions, and improve the communication efficiency and reliability of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118985168A_ABST
    Figure CN118985168A_ABST
Patent Text Reader

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive one or more synchronization signal blocks (SSBs) associated with a random access channel (RACH) procedure, where the one or more SSBs are associated with uplink physical random access channel (PRACH) transmissions in a particular time resource. The UE may receive a downlink transmission in the particular time resource that at least partially overlaps the uplink PRACH transmission, where the uplink PRACH transmission is discarded to receive the downlink transmission in the particular time resource, and where whether a number of configured PRACH transmissions include a discarded PRACH transmission is based at least in part on a parameter. Numerous other aspects are described.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for physical random access channel transmissions. Background Art

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0003] A wireless network may include one or more base stations that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. A "downlink" (or "DL") refers to the communication link from a base station to a UE, and an "uplink" (or "UL") refers to the communication link from a UE to a base station.

[0004] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with a cyclic prefix (CP) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0005] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include receiving one or more synchronization signal blocks (SSBs) associated with a random access channel (RACH) process, wherein the one or more SSBs are associated with an uplink physical random access channel (PRACH) transmission in a specific time resource. The method may include receiving a downlink transmission in a specific time resource that at least partially overlaps with an uplink PRACH transmission, wherein the uplink PRACH transmission is discarded to receive the downlink transmission in the specific time resource, and whether the discarded PRACH transmission is included in a certain number of configured PRACH transmissions is based at least in part on a parameter.

[0006] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include sending one or more SSBs associated with a RACH procedure, wherein the one or more SSBs are associated with an uplink PRACH transmission in a specific time resource. The method may include sending a downlink transmission in the specific time resource that at least partially overlaps with the uplink PRACH transmission, wherein the uplink PRACH transmission is discarded, and wherein whether the discarded PRACH transmission is included in a certain number of configured PRACH transmissions is based at least in part on a parameter.

[0007] Some aspects described herein relate to a UE for wireless communication. The user equipment may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive one or more SSBs associated with a RACH process, wherein the one or more SSBs are associated with an uplink PRACH transmission in a specific time resource. The one or more processors may be configured to receive a downlink transmission in a specific time resource that at least partially overlaps with the uplink PRACH transmission, wherein the uplink PRACH transmission is discarded to receive the downlink transmission in the specific time resource, and whether the discarded PRACH transmission is included in a certain number of configured PRACH transmissions is based at least in part on a parameter.

[0008] Some aspects described herein relate to a network entity for wireless communication. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send one or more SSBs associated with a RACH process, wherein the one or more SSBs are associated with an uplink PRACH transmission in a specific time resource. The one or more processors may be configured to send a downlink transmission in a specific time resource that at least partially overlaps with an uplink PRACH transmission, wherein the uplink PRACH transmission is discarded, and whether the discarded PRACH transmission is included in a certain number of configured PRACH transmissions is based at least in part on a parameter.

[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication performed by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive one or more SSBs associated with a RACH process, wherein the one or more SSBs are associated with an uplink PRACH transmission in a specific time resource. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a downlink transmission in a specific time resource that at least partially overlaps with the uplink PRACH transmission, wherein the uplink PRACH transmission is discarded to receive the downlink transmission in the specific time resource, and whether the discarded PRACH transmission is included in a certain number of configured PRACH transmissions is based at least in part on a parameter.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network entity. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to send one or more SSBs associated with a RACH process, wherein the one or more SSBs are associated with an uplink PRACH transmission in a specific time resource. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to send a downlink transmission in a specific time resource that at least partially overlaps with an uplink PRACH transmission, wherein the uplink PRACH transmission is discarded, and whether the discarded PRACH transmission is included in a certain number of configured PRACH transmissions is based at least in part on a parameter.

[0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving one or more SSBs associated with a RACH process, wherein the one or more SSBs are associated with an uplink PRACH transmission in a specific time resource. The apparatus may include components for receiving a downlink transmission in a specific time resource that at least partially overlaps with the uplink PRACH transmission, wherein the uplink PRACH transmission is discarded to receive the downlink transmission in the specific time resource, and wherein whether the discarded PRACH transmission is included in a certain number of configured PRACH transmissions is based at least in part on a parameter.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting one or more SSBs associated with a RACH procedure, wherein the one or more SSBs are associated with an uplink PRACH transmission in a specific time resource. The apparatus may include means for transmitting a downlink transmission in a specific time resource that at least partially overlaps with an uplink PRACH transmission, wherein the uplink PRACH transmission is discarded, and wherein whether the discarded PRACH transmission is included in a certain number of configured PRACH transmissions is based at least in part on a parameter.

[0013] Aspects of the present invention generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices and / or processing systems as fully described herein with reference to and as illustrated in the accompanying drawings and description.

[0014] The features and technical advantages of 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 a 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 protection of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood from the following description. Each of the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.

[0015] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements, and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0017] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0018] Figure 2 is a diagram illustrating an example of communication between a base station and a user equipment (UE) in a wireless network according to the present disclosure.

[0019] Figure 3 is a diagram illustrating an example of an open radio access network (O-RAN) architecture according to the present disclosure.

[0020] Figure 4 is a diagram illustrating an example of physical channels and reference signals in a wireless network according to the present disclosure.

[0021] Figure 5 is a diagram illustrating an example of a two-step random access procedure according to the present disclosure.

[0022] Figure 6is a diagram illustrating an example of a four-step random access procedure according to the present disclosure.

[0023] Figure 7 is a diagram illustrating an example of a random access procedure using a multi-beam synchronization signal block according to the present disclosure.

[0024] Figure 8 is a diagram illustrating an example of a random access response monitoring window according to the present disclosure.

[0025] 9A to 9F is a diagram illustrating an example associated with physical random access channel transmission according to the present disclosure.

[0026] Figure 10 to Figure 11 is a diagram illustrating an example process associated with physical random access channel transmission according to the present disclosure.

[0027] Figure 12 to Figure 13 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0028] Various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Rather, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of protection of the present disclosure will be fully conveyed to those skilled in the art. It should be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method implemented using other structures, functions, or structures and functions in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present invention.

[0029] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0030] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0031] Figure 1 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be or may include elements of a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The base station 110 is an entity that communicates with the UE 120. The base station 110 (sometimes referred to as a BS) may include, for example, an NR base station, an LTE base station, a NodeB, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), the term "cell" can refer to the coverage area of ​​a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.

[0032] The base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown in , BS 110a may be a macro base station for macro cell 102a, BS 110b may be a pico base station for pico cell 102b, and BS 110c may be a femto base station for femto cell 102c. A base station may support one or more (eg, three) cells.

[0033] In some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move according to the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 can be interconnected with each other and / or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.

[0034] The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a base station 110 or a UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a base station 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown in FIG, BS 110d (eg, a relay base station) can communicate with BS 110a (eg, a macro base station) and UE 120d to facilitate communication between BS 110a and UE 120d. Base station 110 that relays communication may be referred to as a relay station, relay base station, relay, or the like.

[0035] The wireless network 100 may be a heterogeneous network that includes different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0036] A network controller 130 may be coupled to or in communication with a set of base stations 110 and may provide coordination and control for the base stations 110. The network controller 130 may communicate with the base stations 110 via backhaul communication links. The base stations 110 may communicate directly with each other or indirectly via wireless or wired backhaul communication links.

[0037] UE 120 may be distributed throughout wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via a wireless medium.

[0038] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0039] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0040] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more side link channels (e.g., without using base station 110 as an intermediary to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0041] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as a "below 6 GHz" band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as a "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as a "millimeter wave" band by the International Telecommunication Union (ITU).

[0042] The 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.125GHz-24.25GHz). The frequency bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore 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 operation to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designation FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0043] In view of the above examples, unless otherwise specifically stated, it should be understood that the term "below 6 GHz", etc., if used herein, can be broadly referred to as frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that the term "millimeter wave", etc., if used herein, can be broadly referred to as frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0044] In some aspects, the UE 120 may include a communications manager 140. As described in greater detail elsewhere herein, the communications manager 140 may receive one or more synchronization signal blocks (SSBs) associated with a random access channel (RACH) procedure, wherein the one or more SSBs are associated with an uplink physical random access channel (PRACH) transmission in a particular time resource; and receive a downlink transmission in the particular time resource that at least partially overlaps with the uplink PRACH transmission, wherein the uplink PRACH transmission is discarded to receive the downlink transmission in the particular time resource, and wherein whether the discarded PRACH transmission is included in a number of configured PRACH transmissions is based at least in part on a parameter. Additionally or alternatively, the communications manager 140 may perform one or more other operations described herein.

[0045] In some aspects, a network entity (e.g., base station 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may transmit one or more SSBs associated with a RACH procedure, wherein the one or more SSBs are associated with an uplink PRACH transmission in a specific time resource. And transmit a downlink transmission in the specific time resource that at least partially overlaps with the uplink PRACH transmission, wherein the uplink PRACH transmission is discarded, and wherein whether the discarded PRACH transmission is included in a certain number of configured PRACH transmissions is based at least in part on a parameter. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0046] As indicated above, Figure 1 Other examples can be found in the Figure 1 The examples described are different.

[0047] Figure 22 is a diagram illustrating an example 200 of base station 110 communicating with UE 120 in wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

[0048] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0049] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the base station 110 and / or other base stations 110, and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0050] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.

[0051] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0052] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, reference FIG. 9A to FIG. 13 ) or any aspects of any of the methods described herein.

[0053] At the base station 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 where applicable, and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the base station 110 may include a modulator and a demodulator. In some examples, the base station 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to FIG. 9A to FIG. 13 ) or any aspects of any of the methods described herein.

[0054] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other components of the may perform one or more techniques associated with PRACH transmission, as described in more detail elsewhere herein. In some aspects, the network entity described herein is a base station 110, is included in a base station 110, or includes Figure 2 One or more components of the base station 110 are shown. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component in can perform or direct e.g. Fig.10 The process of 1000 Fig.11 1100 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of base station 110 and / or UE 120, may cause the one or more processors, UE 120, and / or base station 110 to perform or direct, for example, Fig.10 The process of 1000 Fig.11 The process 1100 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0055] In some aspects, the UE 120 includes means for receiving one or more SSBs associated with a RACH process, wherein the one or more SSBs are associated with an uplink PRACH transmission in a specific time resource; and / or means for receiving a downlink transmission in a specific time resource that at least partially overlaps with the uplink PRACH transmission, wherein the uplink PRACH transmission is discarded to receive the downlink transmission in the specific time resource, and wherein whether the discarded PRACH transmission is included in a certain number of configured PRACH transmissions is based at least in part on a parameter. Means for the UE 120 to perform operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0056] In some aspects, a network entity (e.g., a base station 110) includes means for transmitting one or more SSBs associated with a RACH process, wherein the one or more SSBs are associated with an uplink PRACH transmission in a specific time resource; and / or means for transmitting a downlink transmission in a specific time resource that at least partially overlaps with the uplink PRACH transmission, wherein the uplink PRACH transmission is discarded, and wherein whether the discarded PRACH transmission is included in a certain number of configured PRACH transmissions is based at least in part on a parameter. In some aspects, means for a network entity to perform operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0057] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0058] As indicated above, Figure 2 Other examples can be found in the Figure 2 The examples described are different.

[0059] Figure 3 3 is a diagram illustrating an example 300 of an open radio access network (O-RAN) architecture according to the present disclosure. Figure 3 As shown, the O-RAN architecture may include a central unit (CU) 310 that communicates with a core network 320 via a backhaul link. In addition, the CU 310 may communicate with one or more distributed units (DUs) 330 via corresponding midhaul links. The DUs 330 may each communicate with one or more radio units (RUs) 340 via corresponding fronthaul links, and the RUs 340 may each communicate with a corresponding UE 120 via a radio frequency (RF) access link. The DU 330 and the RU 340 may also be referred to as O-RAN DU (O-DU) 330 and O-RAN RU (O-RU) 340, respectively.

[0060] The DU 330 and the RU 340 may be implemented according to a functional split architecture, wherein the functionality of a base station 110 (e.g., an eNB or gNB) is provided by the DU 330 and one or more RUs 340 that communicate via a fronthaul link. Thus, as described herein, the base station 110 may include a DU 330 and one or more RUs 340, which may be co-located or geographically distributed. In some aspects, the DU 330 and the associated RU 340 may communicate via the fronthaul link to exchange real-time control plane information via a lower layer split (LLS) control plane (LLS-C) interface, non-real-time management information via an LLS management plane (LLS-M) interface, and / or user plane information via an LLS user plane (LLS-U) interface.

[0061] Thus, the DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340. For example, the DU 330 may host a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (e.g., forward error correction (FEC) encoding and decoding, scrambling, and / or modulation and demodulation) based at least in part on the lower layer functional split. Higher layer control functions (such as packet data convergence protocol (PDCP), radio resource control (RRC), and / or service data adaptation protocol (SDAP)) may be hosted by the CU 310. Based at least in part on the lower layer functional split, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions and low PHY layer functions (e.g., fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, and / or PRACH extraction and filtering). Thus, in the O-RAN architecture, the RU 340 handles all over-the-air (OTA) communications with the UE 120, and the real-time and non-real-time aspects of the control plane and user plane communications with the RU 340 are controlled by the corresponding DU 330, which enables the DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture.

[0062] As indicated above, Figure 3 Other examples can be found in the Figure 3 The examples described are different.

[0063] Figure 4 4 is a diagram illustrating an example 400 of physical channels and reference signals in a wireless network according to the present disclosure. Figure 4 As shown, the downlink channel and the downlink reference signal may carry information from the network entity 402 to the UE 120 , and the uplink channel and the uplink reference signal may carry information from the UE 120 to the network entity 402 .

[0064] As shown, the downlink channel may include a physical downlink control channel (PDCCH) carrying downlink control information (DCI), a physical downlink shared channel (PDSCH) carrying downlink data, or a physical broadcast channel (PBCH) carrying system information, etc. PDSCH communication may be scheduled by PDCCH communication. As further shown, the uplink channel may include a physical uplink control channel (PUCCH) carrying uplink control information (UCI), a physical uplink shared channel (PUSCH) carrying uplink data, or a PRACH for initial network access, etc. UE 120 may send an acknowledgement (ACK) or negative acknowledgement (NACK) feedback (e.g., ACK / NACK feedback or ACK / NACK information) in the UCI on the PUCCH and / or PUSCH.

[0065] As further shown, the downlink reference signal may include an SSB, a channel state information (CSI) reference signal (CSI-RS), a DMRS, a positioning reference signal (PRS), or a phase tracking reference signal (PTRS), etc. As also shown, the uplink reference signal may include a sounding reference signal (SRS), a DMRS, or a PTRS, etc.

[0066] The SSB may carry information used for initial network acquisition and synchronization, such as PSS, SSS, PBCH, and PBCH DMRS. The SSB is sometimes referred to as a synchronization signal / PBCH (SS / PBCH) block. The network entity 402 may send multiple SSBs on multiple corresponding beams, and the SSB may be used for beam selection.

[0067] The CSI-RS may carry information for downlink channel estimation (e.g., downlink CSI acquisition), which may be used for scheduling, link adaptation, or beam management, among other things. The network entity 402 may configure a set of CSI-RS for the UE 120, and the UE 120 may measure the configured set of CSI-RS. Based at least in part on these measurements, the UE 120 may perform channel estimation and may report channel estimation parameters such as CQI, precoding matrix indicator (PMI), CSI-RS resource indicator (CRI), layer indicator (LI), rank indicator (RI), or RSRP, among other things, to the network entity 402 (e.g., in a CSI report). The network entity 402 may use the CSI report to select transmission parameters for downlink communication to the UE 120, such as the number of transmission layers (e.g., rank), precoding matrix (e.g., precoder), MCS, or a refined downlink beam (e.g., using a beam refinement process or a beam management process), among other things.

[0068] DMRS can carry information used to estimate the radio channel to demodulate the associated physical channel (e.g., PDCCH, PDSCH, PBCH, PUCCH, or PUSCH). The design and mapping of DMRS can be specific to the physical channel that the DMRS is used to estimate. DMRS is UE-specific, can be beamformed, can be restricted to scheduled resources (e.g., instead of being sent over a wideband), and can be sent only when necessary. As shown, DMRS is used for both downlink and uplink communications.

[0069] PTRS can carry information for compensating for oscillator phase noise. Typically, phase noise increases with the increase of the oscillator carrier frequency. Therefore, PTRS can be used at high carrier frequencies (such as millimeter wave frequencies) to mitigate phase noise. PTRS can be used to track the phase of the local oscillator and to achieve suppression of phase noise and common phase error (CPE). As shown, PTRS is used for both downlink communications (e.g., on PDSCH) and uplink communications (e.g., on PUSCH).

[0070] The PRS may carry information for implementing timing or ranging measurements of the UE 120 based on signals sent by the network entity 402 to improve observed time difference of arrival (OTDOA) positioning performance. For example, the PRS may be a pseudo-random quadrature phase shift keying (QPSK) sequence mapped in a diagonal pattern with a frequency offset and a time offset to avoid conflicts with cell-specific reference signals and control channels (e.g., PDCCH). In general, the PRS may be designed to improve the detectability of the UE 120, which may require detecting downlink signals from multiple neighboring base stations in order to perform OTDOA-based positioning. Thus, the UE 120 may receive PRS from multiple cells (e.g., a reference cell and one or more neighboring cells), and may report a reference signal time difference (RSTD) based on OTDOA measurements associated with the PRS received from the multiple cells. The network entity 402 may then calculate the position of the UE 120 based on the RSTD measurements reported by the UE 120.

[0071] The SRS may carry information for uplink channel estimation, which may be used for scheduling, link adaptation, pre-decoder selection, or beam management, among others. The network entity 402 may configure one or more SRS resource sets for the UE 120, and the UE 120 may send the SRS on the configured SRS resource sets. The SRS resource sets may have configured usages, such as uplink CSI acquisition, downlink CSI acquisition for reciprocity-based operation, uplink beam management, and the like. The network entity 402 may measure the SRS, may perform channel estimation based at least in part on these measurements, and may use the SRS measurements to configure communications with the UE 120.

[0072] As indicated above, Figure 4 Other examples can be found in the Figure 4 The examples described are different.

[0073] Figure 5 5 is a diagram illustrating an example 500 of a two-step random access procedure according to the present disclosure. Figure 5 As shown, the network entity 502 and the UE 120 may communicate with each other to perform a two-step random access procedure.

[0074] As indicated by reference numeral 505, the network entity 502 may send one or more SSBs and random access configuration information, and the UE 120 may receive the one or more SSBs and random access configuration information. The random access configuration information may be sent in system information (e.g., one or more SIBs) and / or SSBs and / or indicated by the system information and / or SSBs, such as for contention-based random access. Additionally or alternatively, the random access configuration information may be sent in an RRC message and / or a PDCCH command message that triggers a RACH procedure, such as for contention-free random access. The random access configuration information may include one or more parameters to be used in a two-step random access procedure, such as one or more parameters for sending a random access message (RAM) and / or receiving a random access response (RAR) to a RAM.

[0075] As indicated by reference numeral 510, the UE 120 may send a RAM preamble, and the network entity 502 may receive the RAM preamble. As indicated by reference numeral 515, the UE 120 may send a RAM payload, and the network entity 502 may receive the RAM payload. As shown, as part of the initial (or first) step of the two-step random access procedure, the UE 120 may send a RAM preamble and a RAM payload to the network entity 502. The RAM may be referred to as "message A," "msgA," "first message," or "initial message" in the two-step random access procedure. In addition, the RAM preamble may be referred to as "message A preamble," "msgA preamble," "preamble," or "PRACH preamble," and the RAM payload may be referred to as "message A payload," "msgA payload," or "payload." The RAM may include some or all of the contents of message 1 (msg1) and message 3 (msg3) of the four-step random access procedure described in more detail elsewhere herein. For example, the RAM preamble may include some or all of the contents of message 1 (e.g., the PRACH preamble), and the RAM payload may include some or all of the contents of message 3 (e.g., the UE identifier, UCI, and / or PUSCH transmission).

[0076] As indicated by reference numeral 520, the network entity 502 may receive the RAM preamble transmitted by the UE 120. If the network entity 502 successfully receives and decodes the RAM preamble, the network entity 502 may then receive and decode the RAM payload.

[0077] As indicated by reference numeral 525, the network entity 502 may send a RAR (sometimes referred to as a RAR message). As shown, the network entity 502 may send a RAR message as part of the second step of the two-step random access procedure. The RAR message may be referred to as "message B", "msgB", or "second message" in the two-step random access procedure. The RAR message may include some or all of the contents of message 2 (msg2) and message 4 (msg4) of the four-step random access procedure, as described in more detail elsewhere herein. For example, the RAR message may include a detected PRACH preamble identifier, a detected UE identifier, a timing advance value, and / or contention resolution information.

[0078] As indicated by reference numeral 530, as part of the second step of the two-step random access procedure, the network entity 502 may send a PDCCH communication for the RAR. The PDCCH communication may schedule a PDSCH communication including the RAR. For example, the PDCCH communication may indicate a resource allocation for the PDSCH communication (e.g., in a DCI).

[0079] As part of the second step of the two-step random access procedure, the network entity 502 may send a PDSCH communication for the RAR as scheduled by the PDCCH communication, as indicated by reference numeral 535. The RAR may be included in a MAC protocol data unit (PDU) of the PDSCH communication. As indicated by reference numeral 540, if the UE 120 successfully receives the RAR, the UE 120 may send a hybrid automatic repeat request (HARQ) ACK.

[0080] As indicated above, Figure 5 Other examples can be found in the Figure 5 The examples described are different.

[0081] Figure 6 6 is a diagram illustrating an example 600 of a four-step random access procedure according to the present disclosure. Figure 6 As shown, the network entity 602 and the UE 120 may communicate with each other to perform a four-step random access procedure.

[0082] As indicated by reference numeral 605, the network entity 602 may send one or more SSBs and random access configuration information, and the UE 120 may receive one or more SSBs and random access configuration information. The random access configuration information may be sent in system information (e.g., one or more SIBs) and / or SSBs and / or indicated by the system information and / or SSBs, such as for contention-based random access. Additionally or alternatively, the random access configuration information may be sent in an RRC message and / or a PDCCH command message that triggers a RACH procedure, such as for contention-free random access. The random access configuration information may include one or more parameters to be used in the random access procedure, such as one or more parameters for sending a RAM and / or one or more parameters for receiving a RAR.

[0083] As indicated by reference numeral 610, UE 120 may send a RAM that may include a preamble (sometimes referred to as a random access preamble, a PRACH preamble, or a RAM preamble). The message including the preamble may be referred to as "message 1," "msg1," "MSG1," "first message," or "initial message" in the four-step random access procedure. The random access message may include a random access preamble identifier.

[0084] As indicated by reference numeral 615, the network entity 602 may send a RAR as a response to the preamble. A message including the RAR may be referred to as "message 2," "msg2," "MSG2," or "second message" in the four-step random access procedure. The RAR may indicate a detected random access preamble identifier (e.g., received from the UE 120 in msg1). Additionally or alternatively, the RAR may indicate a resource allocation to be used by the UE 120 to send message 3 (msg3).

[0085] As part of the second step of the four-step random access procedure, the network entity 602 may send a PDCCH communication for the RAR. The PDCCH communication may schedule a PDSCH communication including the RAR. For example, the PDCCH communication may indicate a resource allocation for the PDSCH communication. Also as part of the second step of the four-step random access procedure, the network entity 602 may send a PDSCH communication for the RAR as scheduled by the PDCCH communication. The RAR may be included in the MAC PDU of the PDSCH communication.

[0086] As indicated by reference numeral 620, UE 120 may send an RRC connection request message. The RRC connection request message may be referred to as "message 3," "msg3," "MSG3," or "third message" of the four-step random access procedure. The RRC connection request may include a UE identifier, UCI, and / or PUSCH communication (e.g., RRC connection request).

[0087] As indicated by reference numeral 625, the network entity 602 may send an RRC connection setup message. The RRC connection setup message may be referred to as "message 4," "msg4," "MSG4," or "fourth message" of the four-step random access procedure. The RRC connection setup message may include a detected UE identifier, a timing advance value, and / or contention resolution information. As indicated by reference numeral 630, if the UE 120 successfully receives the RRC connection setup message, the UE 120 may send a HARQ ACK.

[0088] As indicated above, Figure 6 Other examples can be found in the Figure 6 The examples described are different.

[0089] Figure 7 is a diagram illustrating an example 700 of a RACH procedure using multi-beam SSB according to the present disclosure.

[0090] like Figure 7As shown, in a RACH process, a network entity (e.g., network entity 502 or network entity 602) may send a set of SSB beams to a UE (e.g., UE 120). For example, as shown, the UE may receive a first SSB#0, a second SSB#1, a third SSB#2, and a fourth SSB#3. The UE may determine an SSB to RACH opportunity (RO) mapping based at least in part on a SIB received from the network entity. The UE may select an SSB and use resources associated with the SSB to send PRACH msg1. For example, the UE may select SSB#1 based at least in part on RSRP, and may select PRACH resources associated with SSB#1. Based at least in part on using uplink PRACH resources associated with SSB#1 to send msg1, the network entity may use beam#1 corresponding to SSB#1 to send a PDCCH or PDSCH msg2 of a RACH process. Similarly, the UE may use RACH resources associated with SSB#1 to transmit PUSCH msg3, and may use beam#1 associated with SSB#1 to receive PDCCH or PDSCH msg4. For example, the UE may use the same spatial filter as used to transmit the existing PRACH transmission msg1 to transmit msg3.

[0091] As indicated above, Figure 7 Other examples can be found in the Figure 7 The examples described are different.

[0092] Figure 8 is a diagram illustrating an example 800 of a RAR monitoring window according to the present disclosure.

[0093] like Figure 8 As shown, after a PRACH transmission (e.g., msg1 of a four-step random access procedure), a UE (e.g., UE120) may have a RAR window for monitoring a RAR transmission (e.g., PDCCH or PDSCH msg2) from a network entity (e.g., network entity 502 or network entity 602). The RAR window may start at the first symbol of the earliest control resource set (CORESET), and the UE is configured to use the first symbol to receive a PDCCH for a type-1 PDCCH common search space (CSS) set (e.g., at least one symbol after the last symbol of an uplink PRACH opportunity corresponding to an uplink PRACH transmission). The subcarrier spacing (SCS) for the symbol duration of the RAR window corresponds to the SCS for the type-1 PDCCH CSS set. The length of the RAR window (e.g., in slots) is indicated by a parameter ra-ResponseWindow.

[0094] As indicated above, Figure 8 Other examples can be found in the Figure 8 The examples described are different.

[0095] PRACH coverage enhancement has enabled the use of multiple PRACH transmissions with the same beam for the RACH procedure. When there are multiple PRACH transmissions, some configured PRACH transmissions may overlap with the RAR monitoring windows corresponding to some other PRACH transmissions. In other words, a first PRACH transmission may trigger a RAR monitoring window (for receiving a downlink transmission) that overlaps with a PRACH opportunity (for sending a second PRACH transmission). In this case, the UE may not be able to receive a downlink transmission and send a PRACH transmission simultaneously.

[0096] Some aspects described herein enable dropping an uplink PRACH transmission when it collides with another transmission, such as an SSB transmission or a scheduled downlink transmission. In this case, based at least in part on parameters received from a network entity, the UE may determine whether to count dropped PRACH transmissions in a certain number of configured PRACH transmissions. In this manner, the UE avoids being unable to receive downlink transmissions due to attempting to send a PRACH transmission on the uplink concurrently with receiving a downlink transmission, thereby improving network performance.

[0097] As indicated above, Figure 8 Other examples can be found in the Figure 8 The examples described are different.

[0098] 9A to 9F is a diagram illustrating an example 900 of PRACH transmission according to the present disclosure. Fig. 9A As shown, example 900 includes UE 120 and network entity 902 (e.g., which may correspond to base station 110, CU 310, DU 330, RU 340, network entity 402, network entity 502, or network entity 602, etc.).

[0099] like Fig. 9A As further shown, and as indicated by reference numeral 910, UE 120 may receive an SSB transmission from network entity 902. For example, UE 120 may receive one or more SSBs that may be associated with a RACH procedure and associated with triggering an uplink PRACH transmission in specific uplink resources.

[0100] like Fig. 9AAs further shown, and as indicated by reference numeral 920 / 920', the UE 120 may discard uplink transmissions and receive downlink transmissions. For example, the UE 120 may determine that an uplink PRACH transmission triggered by one or more received SSBs is in a first time resource that overlaps at least partially with a second time resource for receiving downlink transmissions. In this case, the UE 120 may discard (e.g., abandon) the transmission of the uplink PRACH transmission and may receive the downlink transmission. In some aspects, the UE 120 may include the discarded PRACH transmission in a count of a certain number of configured PRACH transmissions. For example, the UE 120 may increment a parameter that tracks a certain number of configured PRACH transmissions to include the discarded uplink PRACH transmissions. Additionally or alternatively, the UE 120 may include the discarded PRACH transmission in a count of the number of configured PRACH transmissions. In some aspects, UE 120 may determine whether to include a discarded PRACH transmission in a count of the number of configured PRACH transmissions based at least in part on the received parameter. For example, prior to discarding an uplink PRACH transmission, UE 120 may receive configuration information from network entity 902 that includes a parameter indicating whether UE 120 is to include a subsequently discarded uplink PRACH transmission in a count of the number of configured PRACH transmissions.

[0101] In some aspects, UE 120 may determine to drop an uplink PRACH transmission based at least in part on an uplink PRACH transmission that occurs after the start of the RAR window. Fig. 9B As shown, the transmission of msg1 triggered by receiving one or more SSBs is scheduled within a certain period within the RAR window. In this case, the msg1 transmission is discarded to enable the reception of the downlink transmission (e.g., another one or more SSBs). In some aspects, UE 120 may determine to discard the uplink PRACH transmission based at least in part on the successful reception of msg2 by UE 120 before the uplink PRACH transmission. For example, Fig. 9C As shown, when msg1 is scheduled to be sent before receiving msg2, UE 120 can still send msg1 (even if msg1 is scheduled to be sent during the RAR window). Fig.9D As shown, if msg1 transmission is scheduled after successful reception of msg2, UE 120 may determine to drop the msg1 transmission to enable reception of other downlink transmissions.

[0102] In some aspects, UE 120 may determine to drop an uplink PRACH transmission based at least in part on an uplink PRACH transmission occurring within a threshold amount of symbols N before the start of the RAR window. Fig.9E As shown, when msg1 transmission is scheduled within a certain period of N symbols before the start of the RAR window, UE 120 may discard msg1 transmission. Similarly, in some aspects, UE 120 may determine to discard uplink PRACH transmission based at least in part on uplink PRACH transmission occurring within a threshold amount of symbols N after the start of the RAR window. For example, Fig.9F As shown, when msg1 transmission is scheduled within a certain period lasting N symbols from the beginning of the RAR window, UE 120 may discard msg1 transmission. In some aspects, UE 120 may determine the symbol duration (e.g., for N symbols) based at least in part on the subcarrier spacing of the uplink PRACH transmission. Additionally or alternatively, UE 120 may determine the symbol duration based at least in part on the effective uplink or downlink bandwidth portion on which UE 120 is communicating or the initial uplink or downlink bandwidth portion used by UE 120 for communication. Additionally or alternatively, UE 120 may receive configuration information from network entity 902 in system information (SI) or an RRC message indicating the subcarrier spacing to be used by UE 120 to determine the symbol length.

[0103] As indicated above, 9A to 9F are provided as examples. Other examples can be found in the 9A to 9F The examples described are different.

[0104] Fig.10 1 is a diagram illustrating an example process 1000 performed, for example, by a UE in accordance with the present disclosure. Example process 1000 is an example in which a UE (eg, UE 120) performs operations associated with a PRACH transmission.

[0105] like Fig.10 As shown, in some aspects, process 1000 may include receiving one or more SSBs associated with a RACH process, wherein the one or more SSBs are associated with an uplink PRACH transmission in a specific time resource (block 1010). For example, a UE (e.g., using Fig.12 The communication manager 140 and / or receiving component 1202 depicted in FIG. 1 may receive one or more SSBs associated with a RACH process, wherein the one or more SSBs are associated with an uplink PRACH transmission in a specific time resource, as described above.

[0106] like Fig.10As further shown, in some aspects, process 1000 may include receiving a downlink transmission at least partially overlapping an uplink PRACH transmission in a specific time resource, wherein the uplink PRACH transmission is discarded to receive the downlink transmission in the specific time resource, and wherein whether the discarded PRACH transmission is included in a certain number of configured PRACH transmissions is based at least in part on a parameter (block 1020). For example, a UE (e.g., using Fig.12 The communication manager 140 and / or receiving component 1202 depicted in the figure can receive a downlink transmission in a specific time resource that at least partially overlaps with an uplink PRACH transmission, wherein the uplink PRACH transmission is discarded to receive the downlink transmission in the specific time resource, and wherein whether the discarded PRACH transmission is included in a certain number of configured PRACH transmissions is based at least in part on parameters, as described above.

[0107] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0108] In a first aspect, process 1000 includes receiving configuration information identifying parameters.

[0109] In a second aspect, alone or in combination with the first aspect, the dropped PRACH transmissions are included in the number of configured PRACH transmissions.

[0110] In a third aspect, alone or in combination with one or more of the first and second aspects, the dropped PRACH transmissions are not included in the number of configured PRACH transmissions.

[0111] In a fourth aspect, alone or in combination with one or more of the first to third aspects, uplink PRACH transmissions are dropped based at least in part on specific time resources being within a random access response window.

[0112] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 1000 includes receiving RACH msg2, wherein uplink PRACH transmission is dropped based at least in part on specific time resources after successfully receiving RACH msg2.

[0113] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, uplink PRACH transmissions are dropped based at least in part on specific time resources being within a threshold duration of a start of a random access response window.

[0114] In a seventh aspect, either alone or in combination with one or more of aspects 1 to 6, the threshold duration is based at least in part on at least one of: the subcarrier spacing of an uplink PRACH transmission, the subcarrier spacing of an effective uplink bandwidth portion, the subcarrier spacing of a downlink bandwidth portion, or a received configuration.

[0115] although Fig.10 An example block diagram of process 1000 is shown, but in some aspects, process 1000 may include Fig.10 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1000. Additionally or alternatively, two or more blocks of the blocks of process 1000 may be performed in parallel.

[0116] Fig.11 1 is a diagram illustrating an example process 1100, for example, performed by a network entity according to the present disclosure. The example process 1100 is a process in which a network entity (e.g., base station 110, CU 310, DU 330, RU 340, network entity 402, network entity 502, or network entity 902, etc.) performs operations associated with PRACH transmission.

[0117] like Fig.11 As shown, in some aspects, process 1100 may include transmitting one or more SSBs associated with a RACH process, wherein the one or more SSBs are associated with an uplink PRACH transmission in a specific time resource (block 1110). For example, a base station (e.g., using Fig.13 The communication manager 150 and / or the transmitting component 1304 depicted in FIG. 1 may transmit one or more SSBs associated with a RACH process, wherein the one or more SSBs are associated with an uplink PRACH transmission in a specific time resource, as described above.

[0118] like Fig.11 As further shown, in some aspects, process 1100 may include transmitting a downlink transmission at least partially overlapping an uplink PRACH transmission in a particular time resource, wherein the uplink PRACH transmission is dropped, and wherein whether the dropped PRACH transmission is included in a certain number of configured PRACH transmissions is based at least in part on a parameter (block 1120). For example, a base station (e.g., using Fig.13 The communication manager 150 and / or transmitting component 1304 depicted in the figure can send a downlink transmission that at least partially overlaps with an uplink PRACH transmission in a specific time resource, wherein the uplink PRACH transmission is discarded, and wherein whether the discarded PRACH transmission is included in a certain number of configured PRACH transmissions is based at least in part on parameters, as described above.

[0119] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.

[0120] In a first aspect, process 1100 includes sending configuration information identifying parameters.

[0121] In a second aspect, alone or in combination with the first aspect, the dropped PRACH transmissions are included in the number of configured PRACH transmissions.

[0122] In a third aspect, alone or in combination with one or more of the first and second aspects, the dropped PRACH transmissions are not included in the number of configured PRACH transmissions.

[0123] In a fourth aspect, alone or in combination with one or more of the first to third aspects, uplink PRACH transmissions are dropped based at least in part on specific time resources being within a random access response window.

[0124] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 1100 includes sending RACH msg2, wherein uplink PRACH transmission is dropped based at least in part on specific time resources after successfully receiving RACH msg2.

[0125] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, uplink PRACH transmissions are dropped based at least in part on specific time resources being within a threshold duration of a start of a random access response window.

[0126] In a seventh aspect, either alone or in combination with one or more of aspects 1 to 6, the threshold duration is based at least in part on at least one of: the subcarrier spacing of an uplink PRACH transmission, the subcarrier spacing of an effective uplink bandwidth portion, the subcarrier spacing of a downlink bandwidth portion, or the transmitted configuration.

[0127] although Fig.11 An example block diagram of process 1100 is shown, but in some aspects, process 1100 may include Fig.11 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1100. Additionally or alternatively, two or more blocks in the blocks of process 1100 may be performed in parallel.

[0128] Fig.121 is a diagram of an example apparatus 1200 for wireless communication. Apparatus 1200 may be a UE, or a UE may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202 and a transmitting component 1204 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1200 may use receiving component 1202 and transmitting component 1204 to communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device). As further shown, apparatus 1200 may include a communication manager 140. Communication manager 140 may include a determining component 1208, among other things.

[0129] In some aspects, the apparatus 1200 may be configured to perform the 9A to 9F Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as Fig.10 In some aspects, the apparatus 1200 and / or Fig.12 One or more of the components shown may include a combination of Figure 2 Additionally or alternatively, Fig.12 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0130] The receiving component 1202 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the apparatus 1206. The receiving component 1202 may provide the received communications to one or more other components of the apparatus 1200. In some aspects, the receiving component 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the apparatus 1200. In some aspects, the receiving component 1202 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of a described UE.

[0131] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1206. In some aspects, one or more other components of the device 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1206. In some aspects, the transmitting component 1204 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 1204 can be co-located with the receive component 1202 in a transceiver.

[0132] The receiving component 1202 may receive one or more SSBs associated with a RACH process, wherein the one or more SSBs are associated with an uplink PRACH transmission in a specific time resource. The receiving component 1202 may receive a downlink transmission in a specific time resource that at least partially overlaps with the uplink PRACH transmission, wherein the uplink PRACH transmission is discarded to receive the downlink transmission in the specific time resource, and wherein whether the discarded PRACH transmission is included in a certain number of configured PRACH transmissions is based at least in part on a parameter. The receiving component 1202 may receive configuration information identifying the parameter. The receiving component 1202 may receive a RACH msg2, wherein the uplink PRACH transmission is discarded based at least in part on the specific time resource after successfully receiving the RACH msg2. The determining component 1208 may determine whether to discard the PRACH transmission.

[0133] Fig.12 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.12 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.12 Two or more components shown in may be implemented in a single component, or Fig.12 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig.12 A set (one or more) of components shown in the figure may perform the operations described as being performed by Fig.12 One or more functions performed by another set of components shown in FIG.

[0134] Fig.131 is a diagram of an example apparatus 1300 for wireless communication. Apparatus 1300 may be a network entity, or a network entity may include apparatus 1300. In some aspects, apparatus 1300 includes a receiving component 1302 and a transmitting component 1304 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1300 may use receiving component 1302 and transmitting component 1304 to communicate with another apparatus 1306 (such as a UE, a base station, or another wireless communication device). As further shown, apparatus 1300 may include a communication manager 150. Communication manager 150 may include a determining component 1308, among other things.

[0135] In some aspects, the apparatus 1300 may be configured to perform 9A to 9F Additionally or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as Fig.11 The process 1100. In some aspects, Fig.13 The apparatus 1300 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 Additionally or alternatively, Fig.13 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0136] The receiving component 1302 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the apparatus 1306. The receiving component 1302 may provide the received communications to one or more other components of the apparatus 1300. In some aspects, the receiving component 1302 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the apparatus 1300. In some aspects, the receiving component 1302 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described network entities.

[0137] Transmit component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1306. In some aspects, one or more other components of device 1300 may generate communications and may provide the generated communications to transmit component 1304 for transmission to device 1306. In some aspects, transmit component 1304 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1306. In some aspects, transmit component 1304 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network entities. In some aspects, the transmit component 1304 can be co-located with the receive component 1302 in a transceiver.

[0138] The transmitting component 1304 may transmit one or more SSBs associated with a RACH procedure, wherein the one or more SSBs are associated with an uplink PRACH transmission in a specific time resource. The transmitting component 1304 may transmit a downlink transmission in a specific time resource that at least partially overlaps with an uplink PRACH transmission, wherein the uplink PRACH transmission is discarded, and wherein whether the discarded PRACH transmission is included in a certain number of configured PRACH transmissions is based at least in part on a parameter.

[0139] The transmitting component 1304 can transmit configuration information identifying the parameters. The transmitting component 1304 can transmit a RACH msg2, wherein the uplink PRACH transmission is discarded based at least in part on a specific time resource after successfully receiving the RACH msg2. The determining component 1308 can determine whether to transmit a downlink transmission concurrently with the scheduled uplink PRACH transmission and whether to cause the scheduled uplink PRACH transmission to be discarded.

[0140] Fig.13 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.13 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.13 Two or more components shown in may be implemented in a single component, or Fig.13 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig.13 A set (one or more) of components shown in the figure may perform the operations described as being performed by Fig.13 One or more functions performed by another set of components shown in FIG.

[0141] The following provides an overview of some aspects of the disclosure:

[0142] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving one or more synchronization signal blocks (SSBs) associated with a random access channel (RACH) process, wherein the one or more SSBs are associated with an uplink physical random access channel (PRACH) transmission in a specific time resource; and receiving a downlink transmission in the specific time resource that at least partially overlaps with the uplink PRACH transmission, wherein the uplink PRACH transmission is discarded to receive the downlink transmission in the specific time resource, and wherein whether the discarded PRACH transmission is included in a certain number of configured PRACH transmissions is at least partially based on a parameter.

[0143] Aspect 2: According to the method of aspect 1, the method further comprises: receiving configuration information identifying the parameter.

[0144] Aspect 3: The method according to any one of aspects 1 to 2, wherein the discarded PRACH transmission is included in the number of configured PRACH transmissions.

[0145] Aspect 4: The method according to any one of aspects 1 to 3, wherein the discarded PRACH transmission is not included in the number of configured PRACH transmissions.

[0146] Aspect 5: The method according to any one of aspects 1 to 4, wherein the uplink PRACH transmission is dropped based at least in part on the specific time resource being within a random access response window.

[0147] Aspect 6: According to any one of aspects 1 to 5, the method further includes: receiving a RACH message type 2 (msg2), wherein the uplink PRACH transmission is discarded after successfully receiving the RACH msg2 based at least in part on the specific time resource.

[0148] Aspect 7: The method according to any one of aspects 1 to 6, wherein the uplink PRACH transmission is dropped based at least in part on the specific time resource being within a threshold duration of the start of a random access response window.

[0149] Aspect 8: A method according to Aspect 7, wherein the threshold duration is based at least in part on at least one of: the subcarrier spacing sent by the uplink PRACH, the subcarrier spacing of the effective uplink bandwidth portion, the subcarrier spacing of the downlink bandwidth portion, or the received configuration.

[0150] Aspect 9: A method of wireless communication performed by a network entity, the method comprising: sending one or more synchronization signal blocks (SSBs) associated with a random access channel (RACH) process, wherein the one or more SSBs are associated with an uplink physical random access channel (PRACH) transmission in a specific time resource; and sending a downlink transmission in the specific time resource that at least partially overlaps with the uplink PRACH transmission, wherein the uplink PRACH transmission is discarded, and whether the discarded PRACH transmission is included in a certain number of configured PRACH transmissions is at least partially based on a parameter.

[0151] Aspect 10: According to the method of aspect 9, the method further comprises: sending configuration information identifying the parameter.

[0152] Aspect 11: The method according to any one of aspects 9 to 10, wherein the discarded PRACH transmission is included in the number of configured PRACH transmissions.

[0153] Aspect 12: The method according to any one of aspects 9 to 11, wherein the discarded PRACH transmission is not included in the number of configured PRACH transmissions.

[0154] Aspect 13: The method according to any one of aspects 9 to 12, wherein the uplink PRACH transmission is dropped based at least in part on the specific time resource being within a random access response window.

[0155] Aspect 14: According to any one of aspects 9 to 13, the method further comprises: sending a RACH message type 2 (msg2), wherein the uplink PRACH transmission is discarded after successfully receiving the RACH msg2 based at least in part on the specific time resource.

[0156] Aspect 15: The method according to any one of aspects 9 to 14, wherein the uplink PRACH transmission is dropped based at least in part on the specific time resource being within a threshold duration of the start of a random access response window.

[0157] Aspect 16: A method according to Aspect 15, wherein the threshold duration is based at least in part on at least one of: the subcarrier spacing of the uplink PRACH transmission, the subcarrier spacing of the effective uplink bandwidth portion, the subcarrier spacing of the downlink bandwidth portion, or the transmitted configuration.

[0158] Aspect 17: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 8.

[0159] Aspect 18: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 8.

[0160] Aspect 19: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 8.

[0161] Aspect 20: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 8.

[0162] Aspect 21: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 8.

[0163] Aspect 22: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 9 to 16.

[0164] Aspect 23: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 9 to 16.

[0165] Aspect 24: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 9 to 16.

[0166] Aspect 25: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 9 to 16.

[0167] Aspect 26: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 9 to 16.

[0168] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of these aspects.

[0169] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "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, executable files, threads of execution, processes and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0170] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0171] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0172] Any element, action or instruction used herein should not be interpreted as critical or necessary unless explicitly described as such. In addition, as used herein, the article "one" is intended to include one or more entries, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more entries connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more entries, and can be used interchangeably with "one or more". If you only want to refer to an entry, the phrase "only one" or similar terms will be used. Moreover, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "based at least in part on", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) include: Memory; as well as one or more processors coupled to the memory and configured to: receiving one or more synchronization signal blocks (SSBs) associated with a random access channel (RACH) procedure, wherein the one or more SSBs are associated with an uplink physical random access channel (PRACH) transmission in a specific time resource; as well as Receiving a downlink transmission in the specific time resource that at least partially overlaps with the uplink PRACH transmission, wherein the uplink PRACH transmission is discarded to receive the downlink transmission in the specific time resource, and wherein whether the discarded PRACH transmission is included in a certain number of configured PRACH transmissions is at least partially based on a parameter.

2. The UE of claim 1, wherein the one or more processors are further configured to: Configuration information identifying the parameter is received.

3. The UE according to any one of claims 1 to 2, wherein the discarded PRACH transmission is included in the number of configured PRACH transmissions.

4. The UE according to any one of claims 1 to 3, wherein the discarded PRACH transmission is not included in the number of configured PRACH transmissions.

5. The UE according to any one of claims 1 to 4, wherein the uplink PRACH transmission is dropped based at least in part on the specific time resource being within a random access response window.

6. The UE according to any one of claims 1 to 5, wherein the one or more processors are further configured to: A RACH message type 2 (msg2) is received, wherein the uplink PRACH transmission is dropped based at least in part on the specific time resource after successfully receiving the RACH msg2.

7. The UE of any one of claims 1 to 6, wherein the uplink PRACH transmission is dropped based at least in part on the specific time resource being within a threshold duration of a start of a random access response window.

8. The UE according to any one of claims 1 to 7, wherein the threshold duration is based at least in part on at least one of: The subcarrier spacing of the uplink PRACH transmission, The subcarrier spacing of the effective uplink bandwidth portion, The subcarrier spacing of the downlink bandwidth portion, or The received configuration.

9. A network entity for wireless communication, the network entity include: Memory; as well as one or more processors coupled to the memory and configured to: transmitting one or more synchronization signal blocks (SSBs) associated with a random access channel (RACH) procedure, wherein the one or more SSBs are associated with an uplink physical random access channel (PRACH) transmission in a specific time resource; and A downlink transmission at least partially overlapping the uplink PRACH transmission is transmitted in the specific time resource, wherein the uplink PRACH transmission is dropped, and wherein whether the dropped PRACH transmission is included in a certain number of configured PRACH transmissions is based at least in part on a parameter.

10. The network entity of claim 9, wherein the one or more processors are further configured to: Configuration information identifying the parameters is sent.

11. The network entity according to any of claims 9 to 10, wherein the dropped PRACH transmission is included in the number of configured PRACH transmissions.

12. The network entity according to any one of claims 9 to 11, wherein the discarded PRACH transmission is not included in the number of configured PRACH transmissions.

13. The network entity of any one of claims 9 to 12, wherein the uplink PRACH transmission is dropped based at least in part on the specific time resource being within a random access response window.

14. The network entity according to any one of claims 9 to 13, wherein the one or more processors are further configured to: A RACH message type 2 (msg2) is transmitted, wherein the uplink PRACH transmission is dropped based at least in part on the specific time resource after successfully receiving the RACH msg2.

15. The network entity of any one of claims 9 to 14, wherein the uplink PRACH transmission is dropped based at least in part on the specific time resource being within a threshold duration of a start of a random access response window.

16. The network entity of claim 15, wherein the threshold duration is based at least in part on at least one of: The subcarrier spacing of the uplink PRACH transmission, The subcarrier spacing of the effective uplink bandwidth portion, The subcarrier spacing of the downlink bandwidth portion, or The configuration sent.

17. A method of wireless communication performed by a user equipment (UE), the method include: receiving one or more synchronization signal blocks (SSBs) associated with a random access channel (RACH) procedure, wherein the one or more SSBs are associated with an uplink physical random access channel (PRACH) transmission in a specific time resource; as well as Receiving a downlink transmission in the specific time resource that at least partially overlaps with the uplink PRACH transmission, wherein the uplink PRACH transmission is discarded to receive the downlink transmission in the specific time resource, and wherein whether the discarded PRACH transmission is included in a certain number of configured PRACH transmissions is at least partially based on a parameter.

18. The method according to claim 17, further comprising: include: Configuration information identifying the parameter is received.

19. The method according to any one of claims 17 to 18, wherein the discarded PRACH transmission is included in the number of configured PRACH transmissions.

20. The method according to any one of claims 17 to 19, wherein the discarded PRACH transmission is not included in the number of configured PRACH transmissions.

21. The method of any one of claims 17 to 20, wherein the uplink PRACH transmission is dropped based at least in part on the specific time resource being within a random access response window.

22. The method according to any one of claims 17 to 21, further comprising: include: A RACH message type 2 (msg2) is received, wherein the uplink PRACH transmission is dropped based at least in part on the specific time resource after successfully receiving the RACH msg2.

23. The method of any one of claims 17 to 22, wherein the uplink PRACH transmission is dropped based at least in part on the specific time resource being within a threshold duration of a start of a random access response window.

24. The method of claim 23, wherein the threshold duration is based at least in part on at least one of: The subcarrier spacing of the uplink PRACH transmission, The subcarrier spacing of the effective uplink bandwidth portion, The subcarrier spacing of the downlink bandwidth portion, or The received configuration.

25. A method of wireless communication performed by a network entity, the method include: transmitting one or more synchronization signal blocks (SSBs) associated with a random access channel (RACH) procedure, wherein the one or more SSBs are associated with an uplink physical random access channel (PRACH) transmission in a specific time resource; and A downlink transmission at least partially overlapping the uplink PRACH transmission is transmitted in the specific time resource, wherein the uplink PRACH transmission is dropped, and wherein whether the dropped PRACH transmission is included in a certain number of configured PRACH transmissions is based at least in part on a parameter.

26. The method according to claim 25, further comprising: include: Configuration information identifying the parameters is sent.

27. The method according to any one of claims 25 to 26, wherein the discarded PRACH transmission is included in the number of configured PRACH transmissions.

28. The method according to any one of claims 25 to 27, wherein the discarded PRACH transmission is not included in the number of configured PRACH transmissions.

29. The method of any one of claims 25 to 28, wherein the uplink PRACH transmission is dropped based at least in part on the specific time resource being within a random access response window.

30. The method according to any one of claims 25 to 29, further comprising: include: A RACH message type 2 (msg2) is transmitted, wherein the uplink PRACH transmission is dropped based at least in part on the specific time resource after successfully receiving the RACH msg2.