System and method for physical uplink shared channel (PUSCH) opportunity verification for two-step random access channel (RACH)

Abstract

Wireless communication systems and methods are provided for verifying physical uplink shared channel (PUSCH) opportunities defined for a two-step random access channel (RACH) in the event of a conflict. For example, a user equipment (UE) can determine whether a conflict occurs between a PUSCH opportunity for a two-step RACH and any RACH opportunity allocated to a two-step RACH or a four-step RACH after receiving a RACH configuration or update from a network. Then, when a conflict occurs, the UE can exclude the PUSCH opportunity from a resource pool for the two-step RACH.

Description

[0001] Priority claim

[0002] This application is non-provisional and claims priority under 35 USC 119 to U.S. Provisional Application No. 62 / 914,757, filed on October 14, 2019, and U.S. Non-provisional Patent Application No. 17 / 068,585, filed on October 12, 2020, the entire contents of which are expressly incorporated herein by reference. Background Art

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). A wireless multiple-access communication system may include a number of base stations (BSs), each of which simultaneously supports communication for multiple communication devices, which may also be referred to as user equipment (UE).

[0004] In a wireless system, a base station may broadcast synchronization signals such as a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and an extended synchronization signal (ESS), a beam reference signal (BRS), and system information in multiple directional beams. In addition, the BS may transmit other reference signals such as a channel state information reference signal (CSI-RS) on the beam to enable the UE to measure the channel between the BS and the corresponding UE. The UE may perform initial cell acquisition by listening to the broadcast signal, and perform signal measurements based on the synchronization signal, BRS, and / or other signals. The UE may determine the received signal strength based on the received signal, and select a cell and a beam within the selected cell for performing an access procedure.

[0005] To perform an access procedure, the UE may initiate a random access channel (RACH) procedure by sending a random access preamble using the same subarray and beam direction as the selected beam, and monitor a random access response (RAR) within the RAR window. Conventionally, a four-step RACH procedure is used to configure a connection between a UE and a BS, for example, as defined in New Radio (NR) Release 15 and / or earlier releases of the NR release. In NR Release 16, a two-step RACH procedure is defined, in which MsgA transmitted from the UE to the BS combines Msg1 and Msg3 in the four-step RACH procedure, and MsgB transmitted from the BS to the UE combines Msg2 and Msg4 in the four-step RACH procedure. Since there are only 2 instead of 4 message exchanges, the two-step RACH procedure may be more advantageous in terms of delay reduction compared to the conventional four-step RACH procedure. Since UEs designed under NR Release 16 are expected to support both two-step RACH and four-step RACH, the existing specifications in NR Release 16 adopt some existing resource allocation tables designed for four-step RACH to define the transmission opportunities of MsgA in two-step RACH. In this case, the transmission opportunities allocated to four-step RACH may conflict with the transmission opportunities allocated to two-step RACH.

[0006] Therefore, in a wireless communication system, it is necessary to manage the transmission timing of UEs compatible with four-step RACH and two-step RACH. Summary of the invention

[0007] The following summarizes some aspects of the present disclosure to provide a basic understanding of the technology discussed. This summary is not a broad overview of all expected features of the present disclosure, and is neither intended to identify key or important elements of all aspects of the present disclosure, nor to define the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in summary form as a preface to a more detailed description presented later.

[0008] For example, in one aspect of the present disclosure, a method for wireless communication is provided. The method includes receiving, at a user equipment (UE) from a base station (BS), a first configuration of a first random access channel (RACH) opportunity or a first physical uplink shared channel (PUSCH) opportunity for a first RACH procedure, and a second configuration of a second RACH opportunity for a second RACH procedure. The method also includes determining whether the first PUSCH opportunity or the first RACH opportunity is valid. The method also includes, in response to determining that the first PUSCH opportunity or the first RACH opportunity is invalid, updating the RACH resource pool by excluding the first PUSCH opportunity or the first RACH opportunity from the RACH resource pool, and transmitting a first RACH message using an available PUSCH opportunity and an available RACH opportunity to the BS from the updated RACH resource pool.

[0009] In another aspect of the present disclosure, a UE for wireless communication is disclosed. The UE includes a transceiver configured to receive a first configuration of a first RACH opportunity or a first PUSCH opportunity for a first RACH procedure from a BS, and a second configuration of a second RACH opportunity for a second RACH procedure. The UE also includes a processor configured to determine whether the first PUSCH opportunity or the first RACH opportunity is valid, and in response to determining that the first PUSCH opportunity or the first RACH opportunity is invalid, update the RACH resource pool by excluding the first PUSCH opportunity or the first RACH opportunity from the RACH resource pool. The transceiver is also configured to transmit a first RACH message to the BS from the updated RACH resource pool using an available PUSCH opportunity and an available RACH opportunity.

[0010] In another aspect of the present disclosure, a processor-readable non-transitory storage medium is disclosed, which stores processor-executable instructions of a user equipment (UR) for wireless communication. These instructions can be executed by the processor to perform multiple operations, including receiving a first configuration of a first RACH opportunity or a first PUSCH opportunity for a first RACH procedure and a second configuration of a second RACH opportunity for a second RACH procedure from a BS at the UE, determining whether the first PUSCH opportunity or the first RACH opportunity is valid, updating the RACH resource pool by excluding the first PUSCH opportunity or the first RACH opportunity from the RACH resource pool in response to determining that the first PUSCH opportunity or the first RACH opportunity is invalid, and transmitting a first RACH message to the BS from the updated RACH resource pool using available PUSCH opportunities and available RACH opportunities.

[0011] In another aspect of the present disclosure, a system for performing wireless communications is disclosed. The system includes a component for receiving a first random access channel (RACH) opportunity or a first physical uplink shared channel (PUSCH) opportunity from a base station (BS) at a user equipment (UE) for a first RACH procedure, and a second configuration of a second RACH opportunity for a second RACH procedure. The system also includes a component for determining whether the first PUSCH opportunity or the first RACH opportunity is valid. The system also includes a component for updating a RACH resource pool by excluding the first PUSCH opportunity or the first RACH opportunity from the RACH resource pool in response to determining that the first PUSCH opportunity or the first RACH opportunity is invalid. The system also includes a component for transmitting a first RACH message to the BS from the updated RACH resource pool using an available PUSCH opportunity and an available RACH opportunity.

[0012] After reading the following description of specific exemplary aspects of the present invention in conjunction with the accompanying drawings, other aspects, features and aspects of the present invention will become apparent to those of ordinary skill in the art. Although features of the present invention may be discussed with respect to some of the following aspects and drawings, all aspects of the present invention may include one or more advantageous features discussed herein. In other words, although one or more aspects may be discussed as having some advantageous features, one or more of these features may also be used according to the various aspects of the present invention discussed herein. In a similar manner, although exemplary aspects may be discussed below as aspects of devices, systems or methods, it should be understood that such exemplary aspects may be implemented in various devices, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 A wireless communication network according to some aspects of the present disclosure is shown.

[0014] Figure 2 The present invention shows various aspects of the present disclosure. Figure 1 A random access scheme in a wireless communication network is shown.

[0015] Figure 3 It is shown that some aspects of the present disclosure can be Figure 1-2 A transmission scenario of a two-step RACH scheme between a UE and a BS implemented in a wireless communication network is shown.

[0016] Figure 4 is a block diagram of a user equipment (UE) according to some aspects of the present disclosure.

[0017] Figure 5 is a block diagram illustrating an exemplary base station (BS) according to some aspects of the present disclosure.

[0018] Figure 6 A diagram illustrating collisions between two-step RACH PUSCH opportunities and two-step or four-step RACH opportunities in accordance with some aspects of the present disclosure is shown.

[0019] Figure 7 A diagram illustrating aspects of managing transmission opportunities for two-step RACH PUSCH opportunities by associating PUSCH opportunities with RACH opportunities in accordance with some aspects of the present disclosure is shown.

[0020] Figure 8 A diagram is provided illustrating a scenario according to some embodiments of the present technique, where PUSCH opportunities only collide with RACH opportunities, which are associated with different SSBs, then PUSCH opportunities of two-step RACH are considered valid.

[0021] Fig. 9The logic flow executed by the UE according to some aspects of the present disclosure is shown, wherein the logic flow is related to Figure 6 The verification procedure described for the two-step RACH corresponds to that for the PUSCH opportunity.

[0022] Fig.10 The logic flow executed by the UE according to some aspects of the present disclosure is shown, wherein the logic flow is related to Figure 7 The verification procedure described for the two-step RACH corresponds to that for the PUSCH opportunity.

[0023] Fig.11 An alternative logic flow performed by a UE according to some aspects of the present disclosure is shown, wherein the alternative logic flow is similar to the Figure 7 The verification procedure described for the two-step RACH corresponds to that for the PUSCH opportunity. DETAILED DESCRIPTION

[0024] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein may be implemented. In order to provide a thorough understanding of the various concepts, the detailed description includes specific details. However, it is apparent to those skilled in the art that these concepts may be implemented without these specific details. In some cases, known structures and components are shown in block diagram form to avoid confusion with such concepts.

[0025] The present disclosure generally relates to wireless communication systems, also referred to as wireless communication networks. In various aspects, these techniques and devices can be used for wireless communication networks, such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, LTE networks, global mobile communication systems (GSM) networks, fifth generation (5G) or new radio (NR) networks, and other communication networks. As described herein, the terms "network" and "system" can be used interchangeably.

[0026] OFDMA networks can implement radio technologies such as Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM, etc. UTRA, E-UTRA, and GSM are part of Universal Mobile Telecommunications System (UMTS). Specifically, Long Term Evolution (LTE) is a version of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents provided by an organization named "3rd Generation Partnership Project" (3GPP), and cdma2000 is described in documents provided by an organization named "3rd Generation Partnership Project 2" (3GPP2). These various radio technologies and standards are known or under development. For example, the 3rd Generation Partnership Project (3GPP) is a collaboration between telecommunications association groups to define globally applicable third generation (3G) mobile phone specifications. 3GPP Long Term Evolution (LTE) is a 3GPP project that aims to improve the UMTS mobile phone standard. 3GPP may define specifications for next generation mobile networks, mobile systems, and mobile devices.The present disclosure relates to the evolution of wireless technology from LTE, 4G, 5G, and NR, where the wireless spectrum is shared between networks using a set of new and different radio access technologies or radio air interfaces.

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

[0028] 5G NR can be implemented using an optimized OFDM-based waveform with scalable digital and transmission time intervals (TTI); with a common, flexible framework to effectively multiplex services and functions through dynamic, low-latency time division duplex (TDD) / frequency division duplex (FDD) designs; and adopt advanced wireless technologies such as massive multiple-input multiple-output (MIMO), robust millimeter wave (mmWave) transmission, advanced channel decoding, and device-centric mobility. The scalability of digital in 5G NR, as well as the extension of subcarrier spacing, can effectively solve the operation problems of different services across different spectrums and different deployments. For example, in various outdoor and macro coverage deployments of less than 3GHz FDD / TDD implementations, subcarrier spacing can appear at 15kHz, such as over 5, 10, 20MHz bandwidth (BW). For other various outdoor and small cell coverage deployments of TDD greater than 3GHz, subcarrier spacing may appear at 30kHz on 80 / 100MHz BW. For various other indoor broadband implementations, using TDD on the unlicensed portion of the 5G Hz band, the subcarrier spacing may appear at 60kHz over 160MHz BW. Finally, for various deployments using mmWave components for transmission under TDD at 28GHz, the subcarrier spacing may appear at 120kHz over 500MHz BW.

[0029] 5G NR’s scalable numbers facilitate scalable TTIs that meet various latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs to allow transmission to start on symbol boundaries. 5G NR also considers a self-contained integrated subframe design that includes uplink / downlink scheduling information, data, and acknowledgment in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, and adaptive uplink / downlink can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current traffic demands.

[0030] Various other aspects and features of the present disclosure are further described below. It is apparent that the teachings herein can be embodied in a variety of forms, and any specific structure, function, or both disclosed herein are representative and non-restrictive. Based on the teachings herein, it should be understood by those of ordinary skill in the art that an aspect disclosed herein can be implemented independently of any other aspect, and two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement a device or implement a method. In addition, such a device can be implemented, or other structures, functions, or structures and functions other than one or more aspects set forth herein can be used to implement such a method. For example, the method can be implemented as a part of a system, device, device, and / or implemented as instructions stored on a computer-readable medium for execution on a processor or computer. In addition, an aspect may include at least one element of a claim.

[0031] In a wireless system, when a UE wants to access a network, the UE may try to attach to or synchronize with a BS. In order to synchronize with the network, a RACH procedure is used. For example, traditionally, a UE uses a four-step RACH procedure to establish a synchronous connection with a BS. Specifically, in the system information block (SIB2), a BS such as a next-generation node B (gNB) periodically broadcasts several parameters such as a root sequence ID, a RACH configuration index, a power offset, and an initial power. In the contention-based RACH procedure, the UE randomly selects a preamble from 54 orthogonal zadoff-chu (ZC) sequences generated by cyclic shifts of the root sequence, which is transmitted as Msg 1 on a random access subframe in time and a resource block (RB) during the RA Radio Network Temporary Identifier (RA-RNTI) implicitly defined in frequency. The gNB responds with a Msg 2 Random Access Response (RAR), which contains an uplink resource grant, a temporary cell RNTI (C-RNTI), and a time advance (TA) when Msg 1 succeeds. In Msg 3, the UE transmits a Radio Resource Control (RRC) Connection Request including a randomly selected initial device identity after decoding the RB allocation from Msg 2. Multiple UEs may select the same preamble, RA-RNTI in Msg 1, and the corresponding C-RNTI in Msg 2 and transmit their own Msg 3 on uplink resources detected as conflicting by the gNB. In Msg 4, the gNB sends an RRC Connection Establishment with a permanent C-RNTI and an echo of the initial identity transmitted by the device in Msg 3. If the identities match, the RACH procedure is considered successful, otherwise the device retries the procedure after a backoff interval. The successful UE is ready to transmit uplink data.

[0032] In order to reduce the access delay of the four-step RACH access procedure, a two-step RACH procedure may be used, in which the UE combines Msg1 and Msg3 into an initial message, called "MsgA", and the BS sequentially responds with a combined message of the traditional Msg2 and Msg4, called "MsgB". According to aspects of the present disclosure, the two-step RACH procedure, such as regarding Figure 3 As further described, the random access preamble of MsgA is transmitted at the RACH opportunity, and the payload of MsgA is transmitted at the PUSCH opportunity. The RACH opportunity and / or PUSCH opportunity of the two-step RACH are defined by the network and transmitted to the UE via residual system information (RMSI), other system information (SI) or radio resource control (RRC) message.

[0033] Since UEs designed under NR Release 16 are expected to support both two-step RACH and four-step RACH, the existing specifications in NR Release 16 adopt some existing resource allocation tables designed for four-step RACH to define the transmission opportunities of MsgA in two-step RACH. In this case, the transmission opportunities allocated to four-step RACH may conflict with the transmission opportunities allocated to two-step RACH.

[0034] In view of the need to manage transmission opportunities, the embodiments described herein, such as Figure 6-11 As further described, a method is provided to verify the PUSCH opportunity defined by the two-step RACH when a conflict occurs. For example, after receiving a RACH configuration or update from the network, the UE can determine whether a conflict occurs between the PUSCH opportunity of the two-step RACH and any RACH opportunity allocated to the two-step RACH or the four-step RACH. Then, when a conflict occurs, the UE can exclude the PUSCH opportunity from the resource pool used for the two-step RACH.

[0035] Figure 1 A wireless communication network 100 is shown according to some aspects of the present disclosure. The network 100 may be a 5G network. The network 100 includes a plurality of base stations (BSs) 105 (labeled 105a, 105b, 105c, 105d, 105e, and 105f, respectively) and other network entities. The BS 105 may be a station that communicates with the UE 115, and may also be referred to as an evolved Node B (eNB), a next generation eNB (gNB), an access point, etc. Each BS 105 may provide communication coverage to a particular geographic area. In 3GPP, the term "cell" may refer to a particular geographic coverage area of ​​the BS 105 and / or a BS subsystem serving a coverage area, depending on the context in which the term is used.

[0036] The BS 105 may provide communication coverage to macro cells or small cells, such as pico cells or femto cells, and / or other types of cells. A macro cell typically covers a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access to UEs with a service subscription with a network provider. Small cells, such as pico cells, typically cover relatively smaller geographic areas and may allow unrestricted access to UEs with a service subscription with a network provider. Small cells, such as femto cells, typically also cover relatively smaller geographic areas (e.g., a home) and, in addition to unrestricted access, may also provide restricted access to UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.). A BS for a macro cell may be referred to as a macro BS. A BS for a small cell may be referred to as a small cell BS, a pico BS, a femto BS, or a home BS. In Figure 1 In the example shown, BS 105d and 105e may be conventional macro BSs, while BS 105a-105c may be macro BSs enabled with one of three-dimensional (3D), full-dimensional (FD), or massive MIMO. BS 105a-105c may utilize its higher-dimensional MIMO capabilities to utilize 3D beamforming in elevation and azimuth beamforming to increase coverage and capacity. BS 105f may be a small cell BS, which may be a home node or a portable access point. BS 105 may support one or more (e.g., two, three, four, etc.) cells.

[0037] Network 100 may support synchronous or asynchronous operation. For synchronous operation, the BSs may have similar frame timing, and transmissions from different BSs may be roughly aligned over time. For asynchronous operation, the BSs may have different frame timing, and transmissions from different BSs may not be aligned over time.

[0038] UE 115 can be dispersed throughout the wireless network 100, and each UE 115 can be stationary or mobile. UE 115 can also be referred to as a terminal, a mobile station, a subscriber unit, a station and / or the like. UE 115 can be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, etc. In one aspect, UE 115 can be a device including a universal integrated circuit card (UICC). On the other hand, UE can be a device that does not include UICC. In some aspects, UE 115 that does not include UICC can also be referred to as an IoT device or an Internet of Everything (IoE) device. UE 115a-115d is an example of a mobile smart phone type device that accesses the network 100. UE 115 can also be a machine specially configured for connecting communications, including machine type communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), etc. UE 115e-115k are examples of various machines configured for communication to access network 100. UE 115 may be able to communicate with any type of BS, whether macro BS, small cell, etc. Figure 1 , the lightning ball (e.g., communication link) indicates wireless transmission between UE 115 and serving BS 105, or desired transmission between BSs, and backhaul transmission between BSs, where serving BS 105 is a BS designated to serve UE 115 on the downlink and / or uplink.

[0039] In operation, BS 105a-105c may use 3D beamforming and cooperative spatial techniques such as coordinated multipoint (CoMP) or multi-connectivity to serve UEs 115a and 115b. Macro BS 105d may perform backhaul communications with BS 105a-105c and small cell BS 105f. Macro BS 105d may also transmit multicast services subscribed and received by UEs 115c and 115d. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information, such as weather emergencies or alerts, such as yellow rainstorm alerts or gray alerts.

[0040] The BS 105 may also communicate with a core network. The core network may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. At least some of the BSs 105 (e.g., which may be examples of gNBs or access node controllers (ANCs)) may interface with the core network via a backhaul link (e.g., NG-C, NG-U, etc.) and may perform radio configuration and scheduling for communicating with the UE 115. In various examples, the BSs 105 may communicate with each other over a backhaul link (e.g., X1, X2, etc.) directly or indirectly (e.g., through the core network), where the backhaul link may be a wired or wireless communication link.

[0041] The network 100 may also support mission-critical communications through ultra-reliable and redundant links for mission-critical devices, such as UE 115e, which may be a drone. The redundant communication links with UE 115e may include links from macro BSs 105d and 105e, and links from small cell BSs 105f. Other machine-type devices, such as UE 115f (e.g., a thermometer), UE 115g (e.g., a smart meter), and UE 115h (e.g., a wearable device), may communicate through the network 100 either directly with BSs such as small cell BSs 105f and macro BSs 105e, or in a multi-hop configuration by communicating with another user device, and the other machine-type devices relay their information to the network, such as UE 115f transmitting temperature measurement information to a smart meter, and UE 115g, which then reports the information to the network through the small cell. The network 100 may also provide additional network efficiency through dynamic, low-latency TDD / FDD communications, such as in vehicle-to-vehicle (V2V).

[0042] In some implementations, the network 100 communicates using an OFDM-based waveform. An OFDM-based system can divide the system BW into multiple (K) orthogonal subcarriers, which are also commonly referred to as subcarriers, tones, bins, etc. Each subcarrier can be modulated with data. In some cases, the subcarrier spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system BW. The system BW can also be divided into subbands. In other instances, the subcarrier spacing and / or the duration of the TTI can be scalable.

[0043] BS 105 may allocate or schedule transmission resources (e.g., in the form of time-frequency resource blocks (RBs)) for downlink (DL) and uplink (UL) transmissions in network 100. DL refers to the transmission direction from BS 105 to UE 115, while UL refers to the transmission direction from UE 115 to BS 105. Communication may be in the form of radio frames. A radio frame may be divided into a plurality of subframes or time slots, for example, about 10. Each time slot may be further divided into mini time slots. In FDD mode, simultaneous UL and DL transmissions may occur in different frequency bands. For example, each subframe includes a UL subframe in a UL frequency band and a DL subframe in a DL frequency band. In TDD mode, UL and DL transmissions occur in different time periods using the same frequency band. For example, a subset of subframes (e.g., DL subframes) in a radio frame may be used for DL ​​transmission, and another subset of subframes (e.g., UL subframes) in a radio frame may be used for UL transmission.

[0044] DL subframes and UL subframes can be further divided into several areas. For example, each DL or UL subframe can have a predefined area for transmitting reference signals, control information and data. Reference signals are predetermined signals that facilitate communication between BS 105 and UE 115. For example, reference signals can have a specific pilot pattern or structure, wherein the pilot frequency modulation can span the operating BW or frequency band, each located at a predefined time and a predefined frequency. For example, BS 105 can transmit a cell-specific reference signal (CRS) and / or a channel state information-reference signal (CSI-RS) to enable UE 115 to estimate the DL channel. Similarly, UE 115 can transmit a sounding reference signal (SRS) to enable BS 105 to estimate the UL channel. Control information may include resource allocation and protocol control. Data may include protocol data and / or operational data. In some aspects, BS 105 and UE 115 can communicate using self-contained subframes. Self-contained subframes may include a portion for DL ​​communication and a portion for UL communication. Self-contained subframes may be centered on DL or centered on UL. A DL-centric subframe may include a longer duration for DL ​​communications than a duration for UL communications. A UL-centric subframe may include a longer duration for UL communications than a duration for UL communications.

[0045] In some aspects, the network 100 may be an NR network deployed on a licensed spectrum. The BS 105 may transmit synchronization signals (e.g., including a primary synchronization signal (PSS) and a secondary synchronization signal (SSS)) in the network 100 to facilitate synchronization. The BS 105 may broadcast system information associated with the network 100 (e.g., including a master information block (MIB), residual system information (RMSI), and other system information (OSI)) to facilitate initial network access. In some cases, the BS 105 may broadcast the PSS, SSS, and / or MIB in the form of a synchronization signal block (SSB) over a physical broadcast channel (PBCH), and may broadcast the RMSI and / or OSI over a physical downlink shared channel (PDSCH).

[0046] In some aspects, a UE 115 attempting to access the network 100 may perform an initial cell search by detecting the PSS from the BS 105. The PSS may enable synchronization of periodic timing and may indicate a physical layer identification value. The UE 115 may then receive the SSS. The SSS may enable radio frame synchronization and may provide a cell identification value, which may be combined with the physical layer identification value to identify the cell. The PSS and SSS may be located in the center portion of the carrier or at any suitable frequency within the carrier.

[0047] After receiving the PSS and SSS, the UE 115 may receive the MIB. The MIB may include system information for initial network access and scheduling information for RMSI and / or OSI. After decoding the MIB, the UE 115 may receive the RMSI and / or OSI. The RMSI and / or OSI may include radio resource control (RRC) information related to random access channel (RACH) procedures, paging, control resource sets (CORESET) for physical downlink control channel (PDCCH) monitoring, physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH), power control, and SRS.

[0048] After obtaining the MIB, RMSI and / or OSI, the UE 115 may perform a random access procedure to establish a connection with the BS 105. In some examples, the random access procedure may be a four-step random access procedure. For example, the UE 115 may transmit a random access preamble, and the BS 105 may respond with a random access response. The random access response (RAR) may include a detected random access preamble identifier (ID) corresponding to the random access preamble, time advance (TA) information, UL authorization, a temporary cell radio network temporary identifier (C-RNTI), and / or a backoff indicator. Upon receiving the random access response, the UE 115 may transmit a connection request to the BS 105, and the BS 105 may respond with a connection response. The connection response may indicate contention resolution. In some examples, the random access preamble, the RAR, the connection request, and the connection response may be referred to as message 1 (MSG1), message 2 (MSG2), message 3 (MSG3), and message 4 (MSG4), respectively. In some examples, the random access procedure may be a two-step random access procedure, where the UE 115 may transmit a random access preamble and a connection request in a single transmission, and the BS 105 may respond by transmitting a random access response and a connection response in a single transmission.

[0049] After the connection is established, the UE 115 and the BS 105 may enter a normal operation phase, in which operational data may be exchanged. For example, the BS 105 may schedule the UE 115 for UL and / or DL ​​communications. The BS 105 may transmit UL and / or DL ​​scheduling grants to the UE 115 via the PDCCH. The BS 105 may transmit DL communication signals to the UE 115 via the PDSCH according to the DL scheduling grant. The UE 115 may transmit UL communication signals to the BS 105 via the PDSCH and / or PUCCH according to the UL scheduling grant.

[0050] In some cases, BS 105 may use hybrid automatic request (HARQ) to transmit data with UE 115 to improve communication reliability. BS 105 may schedule UE 115 for PDSCH communication by transmitting DL grant in PDCCH. BS 105 may transmit DL data packets to UE 115 according to the scheduling in PDSCH. DL data packets may be transmitted in the form of transfer blocks (TBs). If UE 115 successfully receives the DL data packet, UE 115 may transmit HARQ ACK to BS 105. Conversely, if UE 115 fails to successfully receive the DL transmission, UE 115 may transmit HARQ NACK to BS 105. Upon receiving HARQ NACK from UE 115, BS 105 may retransmit the DL data packet to UE 115. The retransmission may include a decoded version of the DL data that is the same as the initial transmission. Alternatively, the retransmission may include a decoded version of the DL data that is different from the initial transmission. The UE 115 may apply soft combining to combine the coded data received from the initial transmission and the retransmission for decoding. The BS 105 and the UE 115 may also apply HARQ to UL communications using a substantially similar mechanism to DL HARQ.

[0051] In some aspects, the network 100 may operate on a system BW or a component carrier BW. The network 100 may divide the system BW into multiple BWPs (e.g., portions). The BS 105 may dynamically allocate the UE 115 to operate on a certain BWP (e.g., a certain portion of the system BW). The allocated BWP may be referred to as an active BWP. The UE 115 may monitor the active BWP for signaling information from the BS 105. The BS 105 may schedule the UE 115 for UL or DL ​​communication in the active BWP. In some aspects, the BS 105 may allocate a pair of BWPs within a component carrier to the UE 115 for UL and DL communication. For example, the BWP pair may include one BWP for UL communication and one BWP for DL ​​communication. The BS 105 may additionally configure the UE 115 with one or more CORESETs in the BWP. A CORESET may include a set of frequency resources spanning multiple symbols in time. The BS 105 may configure one or more search spaces for PDCCH monitoring for the UE 115 based on the CORESETS. UE 115 may perform blind decoding in the search space to search for DL ​​control information (eg, UL and / or DL ​​scheduling grants) from the BS. In an example, BS 105 may configure BWP, CORESETS, and / or PDCCH search space for UE 115 via RRC configuration.

[0052] In some aspects, the network 100 may operate in a shared or unlicensed frequency band, for example, at about 3.5 gigahertz (GHz), below 6 GHz or higher frequencies in the millimeter wave band. The network 100 may divide the frequency band into a plurality of channels, for example, each channel occupies about 20 megahertz (MHz). The BS 105 and the UE 115 may be operated by a plurality of network operation entities that share resources in a shared communication medium, and an LBT procedure may be employed to obtain a channel occupancy time (COT) in the shared medium for communication. The COT may be discontinuous in time and may refer to the amount of time that a wireless node can send a frame when it wins a wireless medium competition. Each COT may include a plurality of transmission time slots. The COT may also be referred to as a transmission opportunity (TXOP). The BS 105 or UE 115 may perform LBT in the frequency band before transmitting in the frequency band. LBT may be based on energy detection or signal detection. For energy detection, when the signal energy measured from the channel is greater than a certain signal energy threshold, the BS 105 or UE 115 may determine that the channel is busy or occupied. For signal detection, when a certain reserved signal (eg, a preamble signal sequence) is detected in a channel, the BS 105 or UE 115 may determine that the channel is busy or occupied.

[0053] Additionally, BS 105 may configure UE 115 with narrowband operation capability (eg, transmission and / or reception limited to a BW of 20 MHz or less) to perform BWP hopping for channel monitoring and communication. Mechanisms for performing BWP hopping are described in greater detail herein.

[0054] Figure 2 1 shows a random access scheme in a wireless communication network 200 according to various aspects of the present disclosure. The network 200 corresponds to a portion of the network 100. For the sake of simplicity of discussion, although Figure 2 One BS 204 and one UE 202 are shown, but it will be appreciated that aspects of the present disclosure may be extended to more UEs 202 and / or BSs 204. BS 204 corresponds to one of BSs 104. UE 202 corresponds to one of UEs 102. UE 202 and BS 204 may communicate with one another at any suitable frequency.

[0055] exist Figure 2, BS 204 transmits synchronization signals, BRSs, and system information on multiple directional beams 211 in multiple directions, as shown by dashed ellipse 220. In order to access network 200, UE 202 listens to synchronization signals and / or BRSs, and selects a beam for performing a random access procedure. For example, UE 202 can receive beams 211a, 211b, and 211c, and selects beam 211b for random access. UE 202 transmits a random access preamble through beam 221 in the beam direction of beam 211b, and monitors the RAR from BS 204. Upon detecting the random access preamble, BS 204 transmits the RAR on beam 211b in the same beam direction as the random access preamble was received. BS 204 transmits the RAR through beam 211b using the entire subframe. This may result in resource inefficiency when a large bandwidth is available. In addition, when BS 204 sends the RAR, UE 202 may have moved to a different location away from beam 211b, as shown by the dashed arrow. Therefore, UE 202 may not be able to receive the RAR from beam 211b. Another reason for the failure of the RAR may be due to beam correspondence. Although UE 202 can retry another random access attempt after waiting for a period of time (e.g., a backoff period), the retry will add additional delay. Therefore, sending a single random access preamble in a single beam direction for each random access attempt may not be robust enough to successfully complete the RACH procedure.

[0056] Figure 3 It is shown that some aspects of the present disclosure can be Figure 1-2 A transmission scenario of a two-step RACH scheme between a UE 202 and a BS 204 implemented in a wireless communication network is shown.

[0057] Figure 3Figure 300 in Figure 300 shows a two-step RACH procedure that reduces access delay in the control plane compared to the traditional four-step RACH. System information blocks (e.g., SIB2) and RRC signaling are transmitted from BS 204 to UE 202 at 315, and UE 202 decodes the system information and RRC signaling, which may contain resource allocation information for two-step RACH or four-step RACH at 320 related to RACH opportunities and / or PUSCH opportunities. UE 202 then transmits Msg A including four-step RACH Msg 1 and Msg 3, for example, including a random access preamble 340a transmitted on a RACH opportunity, followed by a payload 340b for a random access message transmitted over a PUSCH opportunity at 340 (connection request, device ID, buffer status report, etc.). UE 202 then monitors Msg B from BS 204 at 345, and BS 204 processes and decodes Msg A at 350. MsgB is transmitted from BS 204, which corresponds to Msg 2 and Msg 4 of the four-step RACH, such as RAR, timing advance, and finally completing the connection with an RRC response message at 355. Therefore, the two-step RACH can establish a connection between UE 202 and BS 204 so that UE 202 can start transmitting uplink data with reduced access delay, such as 2 message exchanges versus the traditional 4 message exchanges.

[0058] As shown at 340, the preamble 340a of MsgA is transmitted on the RACH opportunity, and the payload 340b of MsgA is transmitted on the PUSCH opportunity. The network defines the RACH opportunity and the PUSCH opportunity for the two-step RACH, and transmits the information related to the opportunity to the UE via RMSI, other system information, or RRC message. When UE 202 is compatible with both two-step RACH and four-step RACH, UE 202 can receive the opportunity allocation information related to the two-step RACH and the four-step RACH. The existing system can use the same PRACH configuration table defined for the four-step RACH to allocate RACH opportunities for the two-step RACH. Due to the limited number of rows in the table, the RACH opportunity of the two-step RACH may conflict with the RACH opportunity of the four-step RACH in time and frequency, even if they are originally separated (i.e., there is no preamble partition). The conflict may cause serious logical confusion, for example, the gNB may have to respond to the detected preamble with msg2 in the four-step RACH and msgB in the two-step RACH.

[0059] Existing protocols in 3GPP include some rules for the UE to invalidate two-step RACH opportunities, which are the same as the rules used to invalidate four-step RACH opportunities when conflicts occur, and can be found in Section 8.1 of TS 38.213. However, there is no existing agreement to manage the situation when a PUSCH opportunity defined for two-step RACH conflicts with other opportunities (e.g., a RACH opportunity defined for two-step RACH or a RACH opportunity defined for four-step RACH).

[0060] In view of the need to manage transmission opportunities, the embodiments described herein, such as Figure 6-11 As further described, a method is provided to verify the PUSCH timing defined by the two-step RACH when a conflict occurs. With careful PUSCH timing allocation, such a conflict may not always occur (i.e., the UE does not expect it). However, due to the time constraints of 3GPP, a complex / complete design of PUSCH timing allocation may not always be implemented. In some implementations, the PUSCH timing may need to be verified together with or separately from the corresponding RACH timing. For example, after receiving a RACH configuration or update from the network, the UE can determine whether a conflict occurs between the PUSCH timing of the two-step RACH and any RACH timing allocated to the two-step RACH or the four-step RACH. Then, when a conflict occurs, the UE can exclude the PUSCH timing from the resource pool used for the two-step RACH.

[0061] Figure 4 4 is a block diagram illustrating an exemplary UE 400 according to some aspects of the present disclosure. For example, UE 400 may be the Figure 1 115 discussed in the previous figure, or the UE 202 shown in other figures. As shown, the UE 400 may include a processor 402, a memory 404, a BWP frequency hopping module 408, a communication interface 409, a transceiver 410 including a modem subsystem 412 and a radio frequency (RF) unit 414, and one or more antennas 416. These elements may communicate with each other directly or indirectly, for example via one or more buses.

[0062] The processor 402 may include a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof, configured to perform the operations described herein. The processor 402 may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0063] Memory 404 may include cache memory (e.g., cache memory of processor 402), random access memory (RAM), magnetoresistive RAM (MRAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage devices, hard drives, other forms of volatile and non-volatile memory, or a combination of different types of memory. In one aspect, memory 404 includes a non-transitory computer-readable medium. Memory 404 may store or have recorded thereon instructions 406. Instructions 406 may include instructions that, when executed by processor 402, cause processor 402 to perform the various aspects of the present disclosure (e.g., described herein with reference to UE 115) in conjunction with the present disclosure. Figure 3 Instructions 406 may also be referred to as program code. The program code may be used to cause the wireless communication device to perform the operations, for example, by causing one or more processors (such as processor 402) to control or command the wireless communication device to perform the operations. The terms "instructions" and "code" should be broadly interpreted to include any type of computer-readable statements. For example, the terms "instructions" and "code" may refer to one or more programs, routines, subroutines, functions, programs, etc. "Instructions" and "code" may include a single computer-readable statement or many computer-readable statements.

[0064] The RACH module 408 can communicate with the communication interface 409 to receive a message from another device or transmit a message to another device. Each of the RACH module 408 and the communication interface 409 can be implemented via hardware, software, or a combination thereof. For example, each of the RACH module 408 and the communication interface 409 can be implemented as a processor, circuit, and / or instruction 406 stored in the memory 404 and executed by the processor 402. In some examples, the RACH module 408 and the communication interface 409 can be integrated in the modem subsystem 412. For example, the RACH module 408 and the communication interface 409 can be implemented by a combination of software components (e.g., executed by a DSP or a general-purpose processor) and hardware components (e.g., logic gates and circuits) within the modem subsystem 412. In some examples, the UE may include one of the RACH module 408 and the communication interface 409. In other examples, the UE may include both the RACH module 408 and the communication interface 409.

[0065] The RACH module 408 and the communication interface 409 may be used in various aspects of the present disclosure, such as Figure 3 and 6-11. The RACH module 408 is configured to receive system information including a definition of a RACH opportunity and a PUSCH opportunity for starting a RACH procedure from a BS (e.g., 204). The RACH module 408 is also configured to enable or disable the RACH opportunity and / or the PUSCH opportunity before transmitting to the BS a MsgA including a random access preamble and a payload containing a connection request.

[0066] The communication interface 409 is configured to coordinate with the RACH module 408 to receive system information, MsgB and / or other DL scheduling grants from the BS, and / or communicate with the BS according to the UL and / or DL ​​scheduling grants. The communication interface 409 is also configured to transmit MsgA and / or other UL data to the BS.

[0067] As shown, the transceiver 410 may include a modem subsystem 412 and an RF unit 414. The transceiver 410 may be configured to communicate bidirectionally with other devices such as the BS 105. The modem subsystem 412 may be configured to modulate and / or encode data from the memory 404, the RACH module 408, and / or the communication interface 409 according to a modulation and coding scheme (MCS), such as a low-density parity check (LDPC) decoding scheme, a turbo decoding scheme, a convolutional decoding scheme, a digital beamforming scheme, etc. The RF unit 414 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) the modulated / coded data (e.g., PUCCH, PUSCH, channel reports, ACK / NACK) from the modem subsystem 412 (on outbound transmissions) or a transmission originating from another source such as the UE 115 or the BS 105. The RF unit 414 may also be configured to perform analog beamforming in conjunction with digital beamforming. Although shown as being integrated together in the transceiver 410, the modem subsystem 412 and the RF unit 414 may be separate devices that are coupled together at the UE 115 to enable the UE 115 to communicate with other devices.

[0068] The RF unit 414 can provide modulated and / or processed data, such as data packets (or more generally, data messages that may contain one or more data packets and other information) to the antenna 416 for transmission to one or more other devices. The antenna 416 can also receive data messages transmitted from other devices. The antenna 416 can provide received data messages for processing and / or demodulation at the transceiver 410. The transceiver 410 can provide the demodulated and decoded data (e.g., DL data blocks, PDSCH, PUSCH, BWP hopping configuration and / or instructions) to the RACH module 408 and / or the communication interface 409 for processing. The antenna 416 may include multiple antennas with similar or different designs to maintain multiple transmission links. The RF unit 414 can configure the antenna 416.

[0069] In one aspect, the UE 400 may include multiple transceivers 410 that implement different RATs (e.g., NR and LTE). In one aspect, the UE 400 may include a single transceiver 410 that implements multiple RATs (e.g., NR and LTE). In one aspect, the transceiver 410 may include various components, where different combinations of components may implement different RATs.

[0070] Figure 5 5 is a block diagram illustrating an exemplary BS 500 according to some aspects of the present disclosure. For example, BS 500 may be the Figure 1 105 discussed in the foregoing, or BS 204 shown in other figures. As shown, BS 500 may include a processor 502, a memory 504, a RACH module 508, a communication interface 509, a transceiver 510 including a modem subsystem 512 and an RF unit 514, and one or more antennas 516. These elements may communicate with each other directly or indirectly, for example via one or more buses.

[0071] The processor 502 may have various characteristics as a particular type of processor. For example, these may include a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof, configured to perform the operations described herein. The processor 502 may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0072] The memory 504 may include a cache memory (e.g., a cache memory of the processor 502), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, a solid-state storage device, one or more hard disk drives, a memristor-based array, other forms of volatile and nonvolatile memory, or a combination of different types of memory. In certain aspects, the memory 504 may include a non-transitory computer-readable medium. The memory 504 may store instructions 506. The instructions 506 may include instructions that, when executed by the processor 502, cause the processor 502 to perform the operations described herein, such as Figure 2-3 Instructions 506 may also be referred to as code, which may be broadly interpreted to include any type of computer-readable statements, such as those described above with respect to Figure 4 discussed.

[0073] The RACH module 508 can communicate with the communication interface 509 to receive a message from another device or transmit a message to another device. Each of the RACH module 508 and the communication interface 509 can be implemented via hardware, software, or a combination thereof. For example, each of the RACH module 508 and the communication interface 509 can be implemented as a processor, circuit, and / or instruction 506 stored in the memory 504 and executed by the processor 502. In some examples, the RACH module 508 and the communication interface 509 can be integrated in the modem subsystem 512. For example, the RACH module 508 and the communication interface 509 can be implemented by a combination of software components (e.g., executed by a DSP or a general-purpose processor) and hardware components (e.g., logic gates and circuits) within the modem subsystem 512. In some examples, the UE may include one of the RACH module 508 and the communication interface 509. In other examples, the UE may include both the RACH module 508 and the communication interface 509.

[0074] The RACH module 508 and the communication interface 509 may be used in various aspects of the present disclosure, such as Figure 3 and 6 -11. The RACH module 508 is configured to broadcast system information including definitions of RACH opportunities and PUSCH opportunities for initiating random access channel procedures. The RACH module 508 is also configured to receive MsgA, which includes a random access preamble received through a RACH opportunity and a payload containing a connection request received through a PUSCH opportunity.

[0075] The communication interface 509 is configured to coordinate with the RACH module 508 to broadcast system information, or transmit MsgB to the UE. The communication interface 509 is also configured to receive MsgA or other UL data from the UE.

[0076] As shown, the transceiver 510 may include a modem subsystem 512 and an RF unit 514. The transceiver 510 may be configured to communicate bidirectionally with other devices such as the UE 115 and / or 400 and / or another core network element. The modem subsystem 512 may be configured to modulate and / or encode data according to an MCS, such as an LDPC decoding scheme, a turbo decoding scheme, a convolutional decoding scheme, a digital beamforming scheme, etc. The RF unit 514 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) the modulated / encoded data (e.g., BWP hopping configuration and instructions, PDCCH, PDSCH) from the modem subsystem 512 (on outbound transmissions) or a transmission originating from another source such as the UE 115 and 400. The RF unit 514 may also be configured to perform analog beamforming in conjunction with digital beamforming. Although shown as being integrated together in transceiver 51v, modem subsystem 512 and / or RF unit 514 may be separate devices that are coupled together at BS 105 to enable BS 105 to communicate with other devices.

[0077] The RF unit 514 may provide modulated and / or processed data, such as data packets (or more generally, data messages that may contain one or more data packets and other information) to the antenna 516 for transmission to one or more other devices. This may include, for example, transmitting information to complete attachment to a network and communication with a resident UE 115 or 400 in accordance with various aspects of the present disclosure. The antenna 516 may also receive data information transmitted from other devices and provide received data messages for processing and / or demodulation at the transceiver 510. The transceiver 510 may provide the demodulated and decoded data (e.g., channel reports, PUSCH, PUCCH, HARQ ACK / NACK) to the RACH module 508 and / or the communication interface 509 for processing. The antenna 516 may include multiple antennas of similar or different designs in order to maintain multiple transmission links.

[0078] In one aspect, the BS 500 may include multiple transceivers 510 that implement different RATs (e.g., NR and LTE). In one aspect, the BS 500 may include a single transceiver 510 that implements multiple RATs (e.g., NR and LTE). In one aspect, the transceiver 510 may include various components, where different combinations of components may implement different RATs.

[0079] Figure 6A diagram showing collisions between two-step RACH PUSCH opportunities and two-step or four-step RACH opportunities according to some aspects of the present disclosure is shown. For example, a collision in time and frequency occurs between a two-step RACH PUSCH opportunity 602 and a two-step RACH RACH opportunity 603 or a four-step RACH RACH opportunity 605 when the two opportunities 602 and 603, or 602 and 605 overlap at least one OFDM symbol (in time) × one subcarrier spacing (in frequency). That is, when the overlapping area "A" has a non-zero area, as shown in the area marked "A".

[0080] In some embodiments, when a collision occurs, for two-step RACH, the PUSCH opportunity 602 is first verified with the downlink pattern in SSB and TDD, for example, following the procedure described in Section 8.1 of TS 38.213. The PUSCH opportunity 602 for two-step RACH is then verified with the four-step RACH opportunity 605 and the two-step RACH opportunity 603. If the PUSCH opportunity 602 collides with the RACH opportunity 603 or 605, it is invalid. In any association between SSB and two-step RACH opportunity / PUSCH opportunity pairs, invalid PUSCH opportunities are not considered, for example, being excluded from the RACH resource pool.

[0081] In some embodiments, for two-step RACH, PUSCH opportunity 602 can only be verified with downlink patterns in SSB and TDD, for example, following the procedure described in Section 8.1 of TS 38.213. In this case, the UE carefully designs the opportunity allocation and does not expect the PUSCH opportunity 602 of the two-step RACH to collide with the RACH opportunity 603 or 605 of the two-step RACH or 4-step RACH.

[0082] In some embodiments, when the overlap area A is greater than a threshold portion of area B (the total area of ​​RACH opportunity 603 or 604), such as 10%, 15%, etc., the PUSCH opportunity 602 is considered to conflict with the RACH opportunity 603 or 605. The threshold ratio may be defined by the network in a verification procedure directed to the UE and may be transmitted to the UE via system information or an RRC message.

[0083] Figure 7 A diagram illustrating aspects of managing transmission opportunities for two-step RACH PUSCH opportunities by associating PUSCH opportunities 711-713 with RACH opportunities 701-703 according to some aspects of the present disclosure. For two-step RACH opportunity / PUSCH opportunity association with SSB, the UE may independently associate SSB with valid two-step RACH opportunities and SSB with valid PUSCH opportunities. For example, if for Figure 6 For the conflict scenario described in , if the opportunities 701-703 and 711-713 are valid, the UE can associate SSB 705 with RACH opportunities 701-703, and independently associate SSB 705 with PUSCH opportunities 711-713. The RACH opportunities and PUSCH opportunities associated with the same SSB are then further associated using network-defined association rules. For example, here, because RACH opportunities 701-703 and PUSCH opportunities 711-713 are all associated with SSB 705. RACH opportunities 701, 702, 703 can be associated with PUSCH opportunities 711, 712, 713 in pairs, respectively.

[0084] If there is no association between the PUSCH opportunity and the RACH opportunity, an association may be established for a valid RACH opportunity or a valid PUSCH opportunity using a network-defined association rule, excluding the PUSCH opportunity or the RACH opportunity from the two-step RACH resource pool. For example, as shown by the solid line between the RACH opportunity 701 and the PUSCH opportunity 711, when both the RACH opportunity 701 and the PUSCH opportunity 711 are valid (e.g., do not conflict with other RACH or PUSCH opportunities) and are associated with the same SSB 705, then the RACH opportunity 701 and the PUSCH opportunity 711 are then considered to be a valid opportunity pair for MsgA transmission. For another example, if a PUSCH opportunity (e.g., 712) or a RACH opportunity (e.g., 703) is invalid, for example, invalid processing is performed using a downlink pattern in SSB 705 or TDD, or conflicts with another RACH opportunity, as indicated by the dotted lines between opportunities 702 and 712, and 703 and 713, respectively, the invalid PUSCH opportunity 712 or the invalid RACH opportunity 703 will be excluded from the RACH resource pool and therefore will not be used to form a transmission opportunity pair with the RACH opportunity 702 or the PUSCH opportunity 713, respectively.

[0085] In an alternative embodiment, the UE may first associate the two-step RACH opportunity with the PUSCH opportunity using an association rule from the network, rather than first determining whether the PUSCH or RACH opportunity is valid, e.g., forming opportunity pairs 701-712, 702-712, and 703-713. The UE may then run verification on the RACH opportunities 701-703 and the PUSCH opportunities 711-713, e.g., according to the Figure 6 If a RACH opportunity (eg, 703) or a PUSCH opportunity (eg, 712) is invalid, then the opportunity pair (eg, 702-712, 703-713) for two-step RACH is invalid and will be excluded from the RACH resource pool.

[0086] In this way, each SSB (eg, 705 ) is associated with a set of valid opportunity pairs, such as a pair formed by a RACH opportunity 701 and a PUSCH opportunity 711 .

[0087] Figure 8 A diagram is provided illustrating a scenario according to some embodiments of the present technology, where a PUSCH opportunity only collides with a RACH opportunity, and the RACH opportunity is associated with a different SSB, then the PUSCH opportunity for two-step RACH is considered valid. For example, even if the PUSCH opportunity 602 for two-step RACH is determined to be Figure 6 RACH opportunities 603 or 605 are shown to collide, but if the PUSCH opportunity 602 is associated with an SSB 802 that is different from SSB 801, and SSB 801 is associated with the colliding RACH opportunity 603 or 605, then the PUSCH opportunity 602 is still considered valid for MsgA transmission.

[0088] Fig. 9 The logic flow executed by the UE according to some aspects of the present disclosure is shown, wherein the logic flow is related to Figure 6 The steps of method 900 may be performed by a computing device (e.g., a processor, a processing circuit, and / or other suitable components) of a wireless communication device or other suitable components for performing the steps. For example, a wireless communication device such as UE 115, UE 202, or UE 400 may utilize one or more components, such as a processor 402, a memory 404, a RACH module 408, a communication interface 409, a transceiver 410, a modem 412, and one or more antennas 416 to perform the steps of method 900. As shown, method 900 includes a plurality of enumerated steps, but aspects of method 900 include additional steps before, after, and between the enumerated steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0089] At step 902, the UE may receive a configuration of a first RACH opportunity or a first PUSCH opportunity for a first RACH procedure. For example, the UE may receive a RACH / PUSCH opportunity for two-step RACH, for example, via RMSI, other system information, or an RRC message from a BS.

[0090] At step 904, the UE may receive a configuration of a second RACH opportunity for a second RACH procedure. For example, the UE may also receive a RACH / PUSCH opportunity for a four-step RACH.

[0091] The UE may verify the PUSCH timing using the downlink pattern in SSB and TDD at step 906. For example, the UE may verify the PUSCH timing of the two-step RACH using the downlink pattern in SSB or TDD according to Section 8.1 of TS38.213.

[0092] At step 910, the UE may optionally complete PUSCH opportunity verification because the UE does not expect the PUSCH opportunity of the two-step RACH to collide with any RACH opportunity.

[0093] Alternatively, at step 912, the UE may determine whether the first PUSCH opportunity (e.g., 602) collides with the first RACH opportunity (e.g., 603) or the second RACH opportunity (e.g., 605). For example, the UE may determine whether the first PUSCH opportunity completely overlaps with the first or second RACH opportunity and / or whether the overlapping area is greater than a threshold portion of the first or second RACH opportunity.

[0094] In step 914, if a conflict is found, method 900 proceeds to step 916 to determine that the first PUSCH opportunity is invalid, and then excludes the first PUSCH opportunity from the RACH resource pool in step 918. In step 920, the UE may transmit MsgA to the BS using available PUSCH opportunities and RACH opportunities selected from the updated RACH resource pool.

[0095] At step 914, if no collision is found, the method 900 proceeds to step 915 to transmit to BS MsgA using the first PUSCH opportunity (for payload) and the first RACH opportunity (for preamble).

[0096] Fig.10 The logic flow executed by the UE according to some aspects of the present disclosure is shown, wherein the logic flow is related to Figure 7 The steps of method 1000 may be performed by a computing device (e.g., a processor, a processing circuit, and / or other suitable components) of a wireless communication device or other suitable components for performing the steps. For example, a wireless communication device such as UE 115, UE 202, or UE 400 may utilize one or more components, such as a processor 402, a memory 404, a RACH module 408, a communication interface 409, a transceiver 410, a modem 412, and one or more antennas 416 to perform the steps of method 1000. As shown, method 1000 includes a plurality of enumerated steps, but aspects of method 1000 include additional steps before, after, and between the enumerated steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0097] In step 1001, from Fig. 9 Continuing with step 904 in the above, the UE determines that the first PUSCH timing and the first RACH timing are valid. For example, the UE may follow Fig. 9 The method 900 in the embodiment is effective for determining a PUSCH opportunity for a two-step RACH.

[0098] At step 1002, the UE may associate the first SSB with the first PUSCH opportunity. For example, the UE associates SSB 705 with Figure 7 The valid PUSCH opportunities 711 and 713 in are associated.

[0099] At step 1004, the UE may associate the second SSB with the first RACH opportunity. For example, the UE associates SSB 705 (or other SSBs) with Figure 7 The valid RACH opportunities 701 and 702 in are associated.

[0100] At step 1006, the UE determines whether the first SSB and the second SSB are the same. Figure 7 In the example shown, the same SSB 705 is used.

[0101] At step 1008, when the SSBs are the same, method 1000 proceeds to step 1012, where the first PUSCH opportunity is associated with the first RACH opportunity, for example, according to an association rule. Figure 7 As shown, both PUSCH opportunity 711 and RACH opportunity 701 are valid and associated with the same SSB, and are associated as a PUSCH-RACH opportunity pair according to the association rule. Method 1000 then proceeds to Fig. 9 Step 915 in .

[0102] At step 1008, if the valid PUSCH opportunity and the valid RACH opportunity are not associated with the same SSB, in other words, the valid PUSCH opportunity and the valid RACH opportunity cannot form a pair because they are not associated with the same SSB. The UE may exclude the first PUSCH opportunity or the first RACH opportunity from the RACH resource pool at step 1014. The method 1000 then proceeds to Fig. 9 Step 920 in .

[0103] Fig.11 An alternative logic flow performed by a UE according to some aspects of the present disclosure is shown, wherein the alternative logic flow is similar to the Figure 7The steps of method 1100 may be performed by a computing device (e.g., a processor, a processing circuit, and / or other suitable components) of a wireless communication device or other suitable components for performing the steps. For example, a wireless communication device such as UE 115, UE 202, or UE 400 may utilize one or more components, such as a processor 402, a memory 404, a RACH module 408, a communication interface 409, a transceiver 410, a modem 412, and one or more antennas 416 to perform the steps of method 1100. As shown, method 1100 includes a plurality of enumerated steps, but aspects of method 1100 include additional steps before, after, and between the enumerated steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0104] In step 1101, from Fig. 9 Continuing with step 904 in, the UE may associate the first PUSCH opportunity with the first RACH opportunity according to the association rule. For example, the UE may associate PUSCH opportunity 711 with RACH opportunity 701, PUSCH opportunity 712 with RACH opportunity 702, and PUSCH opportunity 713 with RACH opportunity 703 for two-step RACH.

[0105] In step 1106, the UE may, for example, Fig. 9 The method 900 determines whether a first PUSCH opportunity and a first RACH opportunity are valid.

[0106] At step 1108, when the PUSCH or RACH opportunity is invalid, method 1100 proceeds to step 1112, where the UE determines that the PUSCH-RACH opportunity pair is invalid. Figure 7 As shown, when PUSCH opportunity 712 is invalid, PUSCH-RACH opportunity pair 712-702 is considered invalid. When RACH opportunity 703 is invalid, PUSCH-RACH opportunity pair 713-703 is considered invalid.

[0107] At step 1114, the UE may exclude invalid PUSCH-RACH pairs from the RACH resource pool, and then the method 1100 proceeds to Fig. 9 Step 920 in .

[0108] At step 1108, when both PUSCH and RACH opportunities are invalid, method 1100 proceeds to step 1113, where the PUSCH-RACH opportunity pair is associated with the SSB. For example, the valid PUSCH-RACH opportunity pair 711-701 is associated with SSB 705. Method 1100 then proceeds to step 1114. Fig. 9 Step 915 in .

[0109] In some embodiments, if an update is received from the network (e.g., BS 204) that may affect the RACH, including any changes in the two-step RACH opportunity to PUSCH opportunity association rules, SSB to RACH opportunity association rules, SSB to PUSCH opportunity association rules, SSB to MsgA opportunity association rules, SSB timing / scheduling, TDD uplink-downlink pattern, etc., such as Figure 6-11 As described in , the UE may revalidate the PUSCH opportunities for two-step RACH and follow the updated rules.

[0110] Information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above specification may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0111] The various illustrative blocks and modules described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0112] The functions described herein can be implemented by hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the function can be stored on a computer-readable medium or transmitted by a computer-readable medium as one or more instructions or codes. Other examples and implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described above can be implemented using software, hardware, firmware, hard wiring, or any combination thereof executed by a processor. The features of implementing the functions can also be physically located in various locations, including being distributed so that the parts of the functions are implemented at different physical locations. In addition, as used herein, including in the claims, the "or" used in a list of items (e.g., a list of items beginning with phrases such as "at least one" or "one or more") represents an inclusive list. Therefore, for example, a list of "at least one of A, B, or C" represents A or B or C or AB or AC or BC or ABC (i.e. A and B and C).

[0113] As some skilled in the art will now appreciate and depending on the specific application at hand, many modifications, substitutions and changes may be made to the materials, devices, configurations and methods of use of the apparatus of the present disclosure without departing from its spirit and scope. In view of this, the scope of the present disclosure should not be limited to the scope of the specific aspects shown and described herein, as they are merely some examples thereof, but should be fully commensurate with the scope of the claims hereinafter appended and their functional equivalents.

Claims

1. A method for wireless communication, comprising: Receiving, at a user equipment UE, a first configuration of a first random access channel RACH opportunity or a first physical uplink shared channel PUSCH opportunity for a first RACH procedure and a second configuration of a second RACH opportunity for a second RACH procedure; determining whether the first PUSCH opportunity is valid based at least in part on whether the first PUSCH opportunity conflicts with the first RACH opportunity or the second RACH opportunity, wherein the determining comprises: When the first PUSCH opportunity overlaps with the first RACH opportunity or the second RACH opportunity in time and frequency by a portion greater than a threshold ratio of the first RACH opportunity or the second RACH opportunity, determining that the first PUSCH opportunity is invalid; In response to determining that the first PUSCH opportunity is invalid, excluding the first PUSCH opportunity or the first PUSCH opportunity and the first RACH opportunity from a RACH resource pool for a two-step RACH procedure; and The first RACH message is transmitted using an available PUSCH opportunity and an available RACH opportunity.

2. The method according to claim 1, wherein: Determining whether the first PUSCH opportunity is valid includes: The first PUSCH opportunity is verified using SSB and a downlink pattern defined in time division duplex TDD mode.

3. The method according to claim 1, wherein: Determining whether the first PUSCH opportunity is valid also includes: In response to determining that an overlap area between the first PUSCH opportunity and the first RACH opportunity or the second RACH opportunity is less than the threshold ratio portion of the first RACH opportunity or the second RACH opportunity, determining that the first PUSCH opportunity is valid.

4. The method according to claim 1, further comprising: Determining that the first PUSCH opportunity is invalid; as well as When associating synchronization signal blocks SSB with PUSCH opportunities and RACH opportunities for the first RACH procedure, the first PUSCH opportunity is excluded.

5. The method according to claim 1, wherein: Determining whether the first PUSCH opportunity is valid includes determining whether the first PUSCH opportunity or the first RACH opportunity is valid, and the method further includes: Determining that the first PUSCH opportunity or the first RACH opportunity is valid; associating a first SSB with the first PUSCH opportunity; associating a second SSB with the first RACH opportunity; In response to determining that the first SSB and the second SSB are the same SSB, associating the first PUSCH opportunity with the first RACH opportunity according to an association rule defined by a network; In response to determining that the first SSB and the second SSB are different, excluding the first PUSCH opportunity or the first RACH opportunity from the RACH resource pool.

6. The method according to claim 1, wherein: Determining whether the first PUSCH opportunity is valid includes determining whether the first PUSCH opportunity or the first RACH opportunity is valid, and the method further includes: associating a first SSB with the first PUSCH opportunity; associating a second SSB with the first RACH opportunity; In response to determining that the first SSB and the second SSB are the same SSB, associating the first PUSCH opportunity with the RACH opportunity according to an association rule defined by a network; determining that the first PUSCH opportunity or the first RACH opportunity is invalid; and Reassociate the first SSB or the second SSB with a valid PUSCH opportunity and a valid RACH opportunity selected from the RACH resource pool.

7. The method according to claim 1, further comprising: receiving an update, wherein the update comprises a change in a RACH configuration parameter; as well as Re-verify the first RACH opportunity or the first PUSCH opportunity according to the change of the RACH configuration parameter.

8. The method according to claim 1, wherein: Determining whether the first PUSCH opportunity is valid includes: determining that the first PUSCH opportunity conflicts with the first RACH opportunity or the second RACH opportunity; determining that the first PUSCH opportunity is associated with a first SSB, and that the first RACH opportunity or the second RACH opportunity that collides with the first PUSCH is associated with a second SSB; and In response to determining that the first SSB is different from the second SSB, the first PUSCH opportunity is determined to be valid.

9. The method according to claim 1, wherein: The first RACH procedure is a two-step RACH procedure, and the second RACH procedure is a four-step RACH procedure.

10. A user equipment UE for wireless communication, comprising: The transceiver is configured as: receiving a first configuration of a first random access channel, RACH, opportunity or a first physical uplink shared channel, PUSCH, opportunity for a first RACH procedure and a second configuration of a second RACH opportunity for a second RACH procedure; The processor is configured as: determining whether the first PUSCH opportunity is valid based at least in part on whether the first PUSCH opportunity conflicts with the first RACH opportunity or the second RACH opportunity, wherein the determining comprises: When the first PUSCH opportunity overlaps with the first RACH opportunity or the second RACH opportunity in time and frequency by a portion greater than a threshold ratio of the first RACH opportunity or the second RACH opportunity, determining that the first PUSCH opportunity is invalid; In response to determining that the first PUSCH opportunity is invalid, excluding the first PUSCH opportunity or the first PUSCH opportunity and the first RACH opportunity from a RACH resource pool for a two-step RACH procedure; and The transceiver is configured to transmit a first RACH message using an available PUSCH opportunity and an available RACH opportunity.

11. The UE according to claim 10, wherein: The processor is configured to determine whether the first PUSCH opportunity is valid according to the following manner: The first PUSCH opportunity is verified using SSB and a downlink pattern defined in time division duplex TDD mode.

12. The UE according to claim 10, wherein: The processor is configured to determine whether the first PUSCH opportunity is valid according to the following manner: In response to determining that an overlap area between the first PUSCH opportunity and the first RACH opportunity or the second RACH opportunity is less than a threshold ratio portion of the first RACH opportunity or the second RACH opportunity, determining that the first PUSCH opportunity is valid.

13. The UE according to claim 10, wherein: The processor is further configured to: determining that the first PUSCH opportunity is invalid; and When associating synchronization signal blocks SSB with PUSCH opportunities and RACH opportunities for the first RACH procedure, the first PUSCH opportunity is excluded.

14. The UE according to claim 10, wherein: Determining whether the first PUSCH opportunity is valid includes determining whether the first PUSCH opportunity or the first RACH opportunity is valid, and the processor is further configured to: determine whether the first PUSCH opportunity or the first RACH opportunity is valid; associating a first SSB with the first PUSCH opportunity; associating a second SSB with the first RACH opportunity; In response to determining that the first SSB and the second SSB are the same SSB, associating the first PUSCH opportunity with the first RACH opportunity according to an association rule defined by a network; as well as In response to determining that the first SSB and the second SSB are different, excluding the first PUSCH opportunity or the first RACH opportunity from the RACH resource pool.

15. The UE according to claim 10, wherein: Determining whether the first PUSCH opportunity is valid includes determining whether the first PUSCH opportunity or the first RACH opportunity is valid, and the processor is further configured to: associating a first SSB with the first PUSCH opportunity; associating a second SSB with the first RACH opportunity; In response to determining that the first SSB and the second SSB are the same SSB, associating the first PUSCH opportunity with the RACH opportunity according to an association rule defined by a network; determining that the first PUSCH opportunity or the first RACH opportunity is invalid; as well as Reassociate the first SSB or the second SSB with a valid PUSCH opportunity and a valid RACH opportunity selected from the RACH resource pool.

16. The UE according to claim 10, wherein: The processor is further configured to: receiving an update, wherein the update comprises a change in a RACH configuration parameter; and Re-verify the first RACH opportunity or the first PUSCH opportunity according to the change of the RACH configuration parameter.

17. The UE according to claim 10, wherein: The processor is further configured to determine whether the first PUSCH opportunity is valid according to the following manner: determining that the first PUSCH opportunity conflicts with the first RACH opportunity or the second RACH opportunity; Determining that the first PUSCH opportunity is associated with a first SSB, and that the first RACH opportunity or the second RACH opportunity that collides with the first PUSCH is associated with a second SSB; as well as In response to determining that the first SSB is different from the second SSB, the first PUSCH opportunity is determined to be valid.

18. The UE according to claim 10, wherein: The first RACH procedure is a two-step RACH procedure, and the second RACH procedure is a four-step RACH procedure.

19. A processor-readable non-transitory storage medium storing processor-executable instructions of a user equipment (UE) for wireless communication, wherein the instructions are executable by the processor to perform the following operations: Receiving, at a user equipment UE, a first configuration of a first random access channel RACH opportunity or a first physical uplink shared channel PUSCH opportunity for a first RACH procedure and a second configuration of a second RACH opportunity for a second RACH procedure; determining whether the first PUSCH opportunity is valid based at least in part on whether the first PUSCH opportunity conflicts with the first RACH opportunity or the second RACH opportunity, wherein: Make sure to include: When the first PUSCH opportunity overlaps with the first RACH opportunity or the second RACH opportunity in time and frequency by a portion greater than a threshold ratio of the first RACH opportunity or the second RACH opportunity, determining that the first PUSCH opportunity is invalid; In response to determining that the first PUSCH opportunity is invalid, excluding the first PUSCH opportunity or the first PUSCH opportunity and the first RACH opportunity from a RACH resource pool for a two-step RACH procedure; and The first RACH message is transmitted using an available PUSCH opportunity and an available RACH opportunity.

20. The medium according to claim 19, wherein The operation of determining whether the first PUSCH opportunity is valid includes: The first PUSCH opportunity is verified using SSB and a downlink pattern defined in time division duplex TDD mode.

21. The medium of claim 19, wherein: The operation of determining whether the first PUSCH opportunity is valid also includes: In response to determining that an overlap area between the first PUSCH opportunity and the first RACH opportunity or the second RACH opportunity is less than a threshold ratio portion of the first RACH opportunity or the second RACH opportunity, determining that the first PUSCH opportunity is valid.

22. The medium of claim 19, wherein: The operations also include: determining that the first PUSCH opportunity is invalid; and When associating synchronization signal blocks SSB with PUSCH opportunities and RACH opportunities for the first RACH procedure, the first PUSCH opportunity is excluded.

23. The medium of claim 19, wherein: Determining whether the first PUSCH opportunity is valid includes determining whether the first PUSCH opportunity or the first RACH opportunity is valid, and the operation further includes: Determining that the first PUSCH opportunity or the first RACH opportunity is valid; associating a first SSB with the first PUSCH opportunity; associating a second SSB with the first RACH opportunity; In response to determining that the first SSB and the second SSB are the same SSB, associating the first PUSCH opportunity with the first RACH opportunity according to an association rule defined by a network; In response to determining that the first SSB and the second SSB are different, excluding the first PUSCH opportunity or the first RACH opportunity from the RACH resource pool.

24. The medium of claim 19, wherein: Determining whether the first PUSCH opportunity is valid includes determining whether the first PUSCH opportunity or the first RACH opportunity is valid, and the operation further includes: associating a first SSB with the first PUSCH opportunity; associating a second SSB with the first RACH opportunity; In response to determining that the first SSB and the second SSB are the same SSB, associating the first PUSCH opportunity with the RACH opportunity according to an association rule defined by a network; determining that the first PUSCH opportunity or the first RACH opportunity is invalid; and Reassociate the first SSB or the second SSB with a valid PUSCH opportunity and a valid RACH opportunity selected from the RACH resource pool.

25. The medium of claim 19, wherein: The operations also include: receiving an update, wherein the update comprises a change in a RACH configuration parameter; and Re-verify the first RACH opportunity or the first PUSCH opportunity according to the change of the RACH configuration parameter.

26. The medium of claim 19, wherein: The operation of determining whether the first PUSCH opportunity is valid includes: determining that the first PUSCH opportunity conflicts with the first RACH opportunity or the second RACH opportunity; determining that the first PUSCH opportunity is associated with a first SSB, and that the first RACH opportunity or the second RACH opportunity that collides with the first PUSCH is associated with a second SSB; and In response to determining that the first SSB is different from the second SSB, the first PUSCH opportunity is determined to be valid.

27. The medium of claim 19, wherein: The first RACH procedure is a two-step RACH procedure, and the second RACH procedure is a four-step RACH procedure.

28. A system for wireless communication, comprising: means for receiving, at a user equipment UE, a first configuration of a first random access channel RACH opportunity or a first physical uplink shared channel PUSCH opportunity for a first RACH procedure and a second configuration of a second RACH opportunity for a second RACH procedure; The means for determining whether the first PUSCH opportunity is valid based at least in part on whether the first PUSCH opportunity conflicts with the first RACH opportunity or the second RACH opportunity comprises: means for determining that the first PUSCH opportunity is invalid when the first PUSCH opportunity overlaps the first RACH opportunity or the second RACH opportunity in time and frequency by a portion greater than a threshold ratio of the first RACH opportunity or the second RACH opportunity; means for excluding the first PUSCH opportunity or the first PUSCH opportunity and the first RACH opportunity from a RACH resource pool for a two-step RACH procedure in response to determining that the first PUSCH opportunity is invalid; and Means for transmitting a first RACH message using available PUSCH opportunities and available RACH opportunities.

29. The system of claim 28, wherein: The component for determining whether the first PUSCH opportunity is valid includes: Means for validating the first PUSCH opportunity using SSB and a downlink pattern defined in a time division duplex (TDD) mode.

30. The system of claim 28, wherein: The component for determining whether the first PUSCH opportunity is valid further includes: means for determining that the first PUSCH opportunity is valid in response to determining that an overlap area between the first PUSCH opportunity and the first RACH opportunity or the second RACH opportunity is less than a threshold ratio portion of the first RACH opportunity or the second RACH opportunity.

31. The system of claim 28, further comprising: means for determining that the first PUSCH opportunity is invalid; as well as Means for excluding the first PUSCH opportunity when associating synchronization signal blocks (SSB) with PUSCH opportunities and RACH opportunities for the first RACH procedure.

32. The system of claim 28, wherein: The means for determining whether the first PUSCH opportunity is valid includes a means for determining whether the first PUSCH opportunity or the first RACH opportunity is valid, and further includes: A component configured to determine that the first PUSCH opportunity or the first RACH opportunity is valid; means for associating a first SSB with the first PUSCH opportunity; means for associating a second SSB with the first RACH opportunity; means for associating the first PUSCH opportunity with the first RACH opportunity according to a network-defined association rule in response to determining that the first SSB and the second SSB are the same SSB; and A means for excluding the first PUSCH opportunity or the first RACH opportunity from the RACH resource pool in response to determining that the first SSB and the second SSB are different.

33. The system of claim 28, wherein: The means for determining whether the first PUSCH opportunity is valid includes means for determining whether the first PUSCH opportunity or the first RACH opportunity is valid, and further includes: means for associating a first SSB with the first PUSCH opportunity; means for associating a second SSB with the first RACH opportunity; means for associating the first PUSCH opportunity with the RACH opportunity according to a network-defined association rule in response to determining that the first SSB and the second SSB are the same SSB; means for determining that the first PUSCH opportunity or the first RACH opportunity is invalid; and A component for reassociating the first SSB or the second SSB with a valid PUSCH opportunity and a valid RACH opportunity selected from the RACH resource pool.

34. The system of claim 28, further comprising: means for receiving an update, wherein the update comprises a change in a RACH configuration parameter; as well as A component is configured to re-verify the first RACH opportunity or the first PUSCH opportunity according to a change in a RACH configuration parameter.

35. The system of claim 28, wherein: The component for determining whether the first PUSCH opportunity is valid includes: A component configured to determine that the first PUSCH opportunity conflicts with the first RACH opportunity or the second RACH opportunity; means for determining that the first PUSCH opportunity is associated with a first SSB and that the first RACH opportunity or the second RACH opportunity colliding with the first PUSCH is associated with a second SSB; and Means for determining that the first PUSCH opportunity is valid in response to determining that the first SSB is different from the second SSB.

36. The system of claim 28, wherein: The first RACH procedure is a two-step RACH procedure, and the second RACH procedure is a four-step RACH procedure.

Images