Apparatus for wireless communication

Abstract

The invention relates to an apparatus for wireless communication. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors configured to cause the UE to: transmit a first random access channel (RACH) message to a network entity; and monitoring the second RACH message in a set of resource candidates based at least in part on the first RACH message in the absence of downlink control information.

Description

[0001] This application is a divisional application of the Chinese invention patent application with application date of February 23, 2021 and application number 202180015054.3.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This patent application claims priority to U.S. Provisional Patent Application No. 62 / 980,670, filed on February 24, 2020, entitled “RANDOM ACCESS CHANNELMESSAGE WITHOUT A PHYSICAL DOWNLINK CONTROL CHANNEL,” and U.S. Non-Provisional Patent Application No. 17 / 181,981, filed on February 22, 2021, entitled “RANDOM ACCESS CHANNEL MESSAGE WITHOUT APHYSICAL DOWNLINK CONTROL CHANNEL,” which are expressly incorporated herein by reference. Background Art

[0004] Aspects of the present disclosure relate generally to wireless communications and techniques and apparatus for random access channel (RACH) communications.

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

[0006] A wireless communication network may include multiple base stations (BSs) that can support communication for multiple user equipment (UEs). User equipment (UEs) may communicate with a base station (BS) via a downlink and an uplink. A downlink (or forward link) refers to a communication link from a BS to a UE, and an uplink (or reverse link) refers to a communication link from a UE to a BS. As will be described in more detail herein, a BS may be referred to as a Node B, gNB, access point (AP), radio head, transmit receive point (TRP), new radio (NR) BS, 5G Node B, etc.

[0007] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user devices to communicate at a city, country, region, or even global level. New Radio (NR), which may also be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP). NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and better integrating with other open standards, which use orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink (DL), CP-OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), and support beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. However, as the demand for mobile broadband access continues to grow, further improvements in LTE and NR technologies are needed. Preferably, these improvements should be applicable to other multiple access technologies and telecommunication standards that adopt these technologies. Summary of the invention

[0008] In some aspects, a method of wireless communication performed by a user equipment (UE) may include: sending a first random access channel (RACH) message to a base station; and monitoring a second RACH message from the base station in a resource candidate set outside a physical downlink control channel (PDCCH) based at least in part on the sent first RACH message.

[0009] In some aspects, a method of wireless communication performed by a UE may include: sending a first RACH message to a base station; and in the absence of downlink control information, monitoring a second RACH message from the base station in a resource candidate set, the resource candidate set being based at least in part on the sent first RACH message.

[0010] In some aspects, a method of wireless communications performed by a base station may include receiving a first RACH message from a UE and sending a second RACH message in a set of resource candidates outside of a PDCCH based at least in part on receiving the first RACH message.

[0011] In some aspects, a UE for wireless communication may include a memory and one or more processors coupled to the memory. The memory and the one or more processors may be configured to send a first RACH message to a base station and monitor a second RACH message from the base station in a resource candidate set outside of a PDCCH based at least in part on the sent first RACH message.

[0012] In some aspects, a UE for wireless communication may include a memory and one or more processors coupled to the memory. The memory and the one or more processors may be configured to send a first RACH message to a base station and, in the absence of downlink control information, monitor a second RACH message from the base station in a resource candidate set, the resource candidate set being based at least in part on the sent first RACH message.

[0013] In some aspects, a base station for wireless communication may include a memory and one or more processors coupled to the memory. The memory and the one or more processors may be configured to receive a RACH message from a UE and send a second RACH message in a set of resource candidates outside of a PDCCH based at least in part on receiving a first RACH message.

[0014] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a UE, the one or more instructions may cause the one or more processors to send a first RACH message to a base station and, based at least in part on the sent first RACH message, monitor a resource candidate set outside of a PDCCH for a second RACH message from the base station.

[0015] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a UE, the one or more instructions may cause the one or more processors to send a first RACH message to a base station and, in the absence of downlink control information, monitor a resource candidate set for a second RACH message from the base station, the resource candidate set being based at least in part on the sent first RACH message.

[0016] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a base station, the one or more instructions may cause the one or more processors to receive a first RACH message from a UE and, based at least in part on receiving the first RACH message, send a second RACH message in a set of resource candidates outside of a PDCCH.

[0017] In some aspects, an apparatus for wireless communication may include means for sending a first RACH message to a base station and means for monitoring a set of resource candidates outside of a PDCCH for a second RACH message from the base station based at least in part on the sent first RACH message.

[0018] In some aspects, an apparatus for wireless communication may include components for sending a first RACH message to a base station, and components for monitoring a set of resource candidates for a second RACH message from the base station in the absence of downlink control information, the set of resource candidates being based at least in part on the sent first RACH message.

[0019] In some aspects, an apparatus for wireless communication may include means for receiving a first RACH message from a UE and means for sending a second RACH message in a set of resource candidates outside of a PDCCH based at least in part on receiving the first RACH message.

[0020] In some aspects, an apparatus for wireless communication at a user equipment (UE) may include: one or more memories; and one or more processors, coupled to the one or more memories, the one or more processors configured to cause the UE to: send a first random access channel (RACH) message to a network entity; and in the absence of downlink control information, monitor for a second RACH message in a resource candidate set based at least in part on the first RACH message.

[0021] In some aspects, an apparatus for wireless communication at a network entity may include: one or more memories; and one or more processors, coupled to the one or more memories, the one or more processors configured to cause the network entity to: receive a first random access channel (RACH) message from a user equipment (UE); and send a second RACH message in a set of resource candidates scheduled in the absence of downlink control information based at least in part on the first RACH message.

[0022] Aspects generally include methods, apparatuses, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems substantially as described with reference to and illustrated by the drawings and description.

[0023] The features and technical advantages of the examples according to the present disclosure have been outlined quite broadly above so that the following detailed description may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The features of the concepts disclosed herein, their organization and methods of operation, and related advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each of the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to be able to understand the above-mentioned features of the present disclosure in detail, a more specific description of the above brief summary may be made with reference to some aspects, some of which are shown in the accompanying drawings. However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and should not be considered as limiting the scope thereof, as the description may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0025] Figure 1 is a block diagram conceptually illustrating an example of a wireless communication network in accordance with various aspects of the present disclosure.

[0026] Figure 2 is a block diagram conceptually illustrating an example of a base station communicating with a UE in a wireless communication network according to various aspects of the present disclosure.

[0027] Figure 3 is a diagram illustrating an example of a downlink-centric timeslot or wireless communication structure according to various aspects of the present disclosure.

[0028] Figure 4 is a diagram illustrating an example of an uplink-centric time slot or wireless communication structure according to various aspects of the present disclosure.

[0029] Figure 5A and Figure 5B 2 are diagrams illustrating an example of a 4-step random access channel (RACH) procedure and an example of a 2-step RACH procedure, respectively.

[0030] Figure 6 An example in which a base station transmits a RACH message without a physical downlink control channel according to various aspects of the present disclosure is illustrated.

[0031] Figure 7 is a diagram illustrating an example process performed, for example, by a UE according to various aspects of the present disclosure.

[0032] Figure 8 is a diagram illustrating an example process performed, for example, by a base station, according to various aspects of the present disclosure.

[0033] Figure 9-11 is a block diagram of an example apparatus of a UE for wireless communication according to various aspects of the present disclosure.

[0034] Figure 12-14 is a block diagram of an example apparatus of a base station for wireless communications according to various aspects of the present disclosure. DETAILED DESCRIPTION

[0035] A user equipment (UE) may send a random access channel (RACH) message to a base station as part of a RACH procedure to initiate communication. The base station may respond with a second RACH message (e.g., msg2, msgB) that includes control information about a physical downlink control channel (PDCCH). However, if the UE coverage is poor for certain frequencies (e.g., mmWave 5G), or if the signal of the first RACH message is weak, the base station may be limited in how to boost the transmission of the second RACH message to improve coverage. The PDCCH may become a power bottleneck for RACH messages. In one or more examples, the base station can only use two or three symbols in the PDCCH because the PDCCH is limited to a core resource set (CORESET) and therefore the transmit power increase is limited to two or three symbols.

[0036] In order to increase coverage and improve the reception of the second RACH message, the UE may monitor the second RACH message in time and frequency resources not limited to two or three symbols in the PDCCH. Receiving the second RACH message over a larger number of symbols (e.g., more than three symbols) improves the reception of the RACH message. According to various aspects described herein, the UE may monitor and receive the second RACH message in time and frequency resources other than the PDCCH, or in resources that are an alternative to resources including the PDCCH (resources in the downlink control information (DCI) in the PDCCH). The resources used for the UE to monitor the second RACH message may be based at least in part on the transmission of the first RACH message in the absence of DCI. That is, the resources used for the second message are based at least in part on the first RACH message, the DCI is not used to schedule the second RACH message, and the second RACH message is not received in the DCI. This provides improved coverage for the second RACH message because the UE can receive more symbols of the second RACH message when the DCI is not used.

[0037] In the RACH process, the data of the second RACH message on the physical downlink shared channel (PDSCH) is scheduled by the DCI carried in the PDCCH. Instead of scheduling the data on the PDSCH via the PDCCH, the base station can schedule the PDSCH via system information, such as the remaining minimum system information (RMSI). In other words, the UE can monitor the second RACH message in resources that are not scheduled via DCI (e.g., resources in the PDSCH). In some aspects, the second RACH message can be scheduled via the remaining minimum system information (RMSI) message or other system information.

[0038] Resources not scheduled via DCI may include resources in the DL data portion of a downlink (DL)-centric time slot. The DL data portion may sometimes be referred to as the payload of a DL-centric time slot. The DL data portion may include communication resources for communicating DL data from a scheduling entity (e.g., UE or BS) to a subordinate entity (e.g., UE). In some examples, the DL data portion may be a PDSCH. The data portion may be considered to be outside the PDCCH. If the UE is to receive a RACH message outside the PDCCH, in the absence of DCI outside the PDCCH, the UE may monitor the RACH message in a set of resource candidates (e.g., symbols, subcarriers) located in the data portion, such as in the PDSCH instead of in the PDCCH of the control portion. For example, the UE may monitor the RACH message in a resource candidate set that includes more than two or three symbols available for RACH messages in the control portion. The resource candidate set may also be scheduled in the absence of DCI, or by signaling that is not in the DCI.

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

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

[0041] It should be noted that although various aspects may be described herein using terms generally associated with 3G and / or 4G wireless technologies, various aspects of the present disclosure can be applied to other generation-based communication systems, such as 5G and later communication systems, including NR technologies.

[0042] Figure 1 1 is a schematic diagram illustrating a wireless network 100 in which aspects of the present disclosure may be practiced. The wireless network 100 may be an LTE network, a 5G or NR network, etc. The wireless network 100 may include a plurality of BSs 110 (shown as BSs 110a, BSs 110b, BSs 110c, and BSs 110d) and other network entities. A BS is an entity that communicates with a user equipment (UE) and may also be referred to as a base station, NR BS, Node B, gNB, 5G Node B (NB), access point, transmit receive point (TRP), etc. Each BS may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to a coverage area of ​​a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0043] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access to UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access to UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown, BS 110a may be a macro BS of macro cell 102a, BS 110b may be a pico BS of pico cell 102b, and BS 110c may be a femto BS of femto cell 102c. A BS may support one or more (e.g., three) cells. The terms "eNB", "base station", "NR BS", "gNB", "TRP", "AP", "Node B", "5G NB", and "cell" may be used interchangeably herein.

[0044] In some examples, the cells are not necessarily fixed, and the geographic area of ​​the cells may move according to the location of the mobile BS. In some examples, the BSs may be interconnected with each other and / or with one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as direct physical connections, virtual networks, etc., using any suitable transport network.

[0045] The wireless network 100 may also include a relay station. A relay station is an entity that can receive data transmissions from an upstream station (e.g., a BS or a UE) and deliver data transmissions to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions for other UEs. Figure 1 In the example shown, a relay station 110d may communicate with the macro BS 110a and the UE 120d to facilitate communication between the BS 110a and the UE 120d. A relay station may also be referred to as a relay BS, a relay base station, a relay, or the like.

[0046] The wireless network 100 may be a heterogeneous network including different types of BSs, such as a macro BS, a pico BS, a femto BS, a relay BS, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 5 to 40 watts), while a pico BS, a femto BS, and a relay BS may have a lower transmit power level (e.g., 0.1 to 2 watts).

[0047] The network controller 130 may be coupled to a group of BSs and may provide coordination and control for these BSs. The network controller 130 may communicate with the BSs via a backhaul. The BSs may also communicate with each other directly or indirectly via a wireless or wired backhaul.

[0048] UE 120 (e.g., 120a, 120b, 120c) can be dispersed in the wireless network 100, and each UE can be fixed or mobile. UE can also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. UE can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biosensor / device, a wearable device (smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing device, a global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium.

[0049] Some UEs may be considered machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which may communicate with a base station, another device (e.g., a remote device), or some other entity. For example, a wireless node may provide connectivity to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered customer premise equipment (CPE). UE 120 may be included in a housing that houses components of UE 120 such as a processor component, a memory component, etc.

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

[0051] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as a medium for communicating with each other) using one or more bypass channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocol (e.g., which may include vehicle-to-vehicle (V2V) protocol or vehicle-to-infrastructure (V2I) protocol) and / or mesh network. In some aspects, UE 120 may perform scheduling operations, resource selection operations, and / or other operations performed by base station 110 as described elsewhere herein.

[0052] The electromagnetic spectrum is often subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, the two initial operating bands are identified with the frequency range names FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that FR1 is often referred to (interchangeably) as the “below 6 GHz (Sub-6)” band in various documents and articles, even though a portion of FR1 is greater than 6 GHz. A similar naming issue sometimes occurs with FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, even though it is different from the extremely high frequency (EHF) band (30 GHz–300 GHz) which is identified as the “millimeter wave” (mmWave) band by the International Telecommunication Union (ITU).

[0053] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR research has identified operating bands for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz–24.25 GHz). Frequency bands that fall into FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus may effectively extend the characteristics of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations above 52.6 GHz. For example, the three higher operating bands are identified as the frequency range designations FR4a or FR4-1 (52.6 GHz–71 GHz), FR4 (52.6 GHz–114.25GHz), and FR5 (114.25 GHz–300 GHz). Each of these higher frequency bands falls within the EHF band.

[0054] In view of the above, unless otherwise stated, it should be understood that the term "below 6 GHz" and the like, if used herein, can broadly refer to frequencies below 6 GHz, which can be within FR1, or can include mid-band frequencies. In addition, unless otherwise stated, it should be understood that the term "millimeter wave" and the like, if used herein, can broadly refer to frequencies that can include mid-band frequencies, which can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band.

[0055] like Figure 1 As shown, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may send a first RACH message to a base station, and based at least in part on the sent first RACH message, monitor a second RACH message from the base station in a resource candidate set outside the PDCCH. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0056] Similarly, base station 110 may include communication manager 150. As described in more detail elsewhere herein, communication manager 150 may receive a first RACH message from a UE and, based at least in part on receiving the first RACH message, send a second RACH message in a resource candidate set outside of the PDCCH. Additionally or alternatively, communication manager 150 may perform one or more other operations described herein.

[0057] As mentioned above, Figure 1 are provided only as examples. Other examples may be related to Figure 1 Different than described.

[0058] Figure 2 A block diagram shows a design 200 of a base station 110 and a UE 120, which may be Figure 1 Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general T ≥ 1 and R ≥ 1.

[0059] At the base station 110, the transmit processor 220 may receive data for one or more UEs from the data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for the UE based at least in part on the MCS selected for each UE, and provide data symbols for all UEs. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI), etc.) and control information (e.g., CQI requests, grants, upper layer signaling, etc.), and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS)) and synchronization signals (e.g., primary synchronization signals (PSS) and secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may, if applicable, perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, and may provide T output symbol streams to T modulators (MODs) 232 a to 232 t. Each modulator 232 may process a corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232 a to 232 t may be transmitted via T antennas 234 a to 234 t, respectively. According to various aspects described in more detail below, a synchronization signal can be generated with position coding to convey additional information.

[0060] At the UE 120, antennas 252a to 252r may receive downlink signals from the base station 110 and / or other base stations, and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. The MIMO detector 256 may obtain received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to the data sink 260, and provide decoded control information and system information to the controller / processor 280. The channel processor may determine a reference signal received power (RSRP), a received signal strength indicator (RSSI), a reference signal received quality (RSRQ), a channel quality indicator (CQI), etc. In some aspects, one or more components of UE 120 may be included in a housing.

[0061] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.). The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266, if applicable, further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to the base station 110. At the base station 110, uplink signals from the UE 120 and other UEs may be received by antennas 234, processed by demodulators 232, detected by MIMO detectors 236, if applicable, and further processed by a receive processor 238 to obtain decoded data and control information delivered by the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and communicate with the network controller 130 via the communication unit 244. The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292.

[0062] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other components of the base station 110 may perform one or more techniques associated with RACH messages without PDCCH, as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the can perform or direct e.g. Figure 8 The process of 800 Fig. 9 The operations of process 900 and / or other processes described herein may be performed. Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively. Scheduler 246 may schedule UEs for data transmission on the downlink and / or uplink.

[0063] In some aspects, the UE 120 may include components for sending a first RACH message to the base station, components for monitoring a second RACH message from the base station in a resource candidate set outside the PDCCH based at least in part on the sent first RACH message, components for monitoring a second RACH message from the base station in a resource candidate set based at least in part on the sent first RACH message in the absence of downlink control information, etc. Additionally or alternatively, the UE 120 may include components for performing one or more other operations described herein. In some aspects, such components may include the communication manager 140. Additionally or alternatively, such components may include in conjunction with Figure 2 One or more components of UE 120 are described.

[0064] In some aspects, the base station 110 may include components for receiving a first RACH message from the UE, components for sending a second RACH message in a resource candidate set outside the PDCCH based at least in part on receiving the first RACH message, etc. Additionally or alternatively, the base station 110 may include components for performing one or more other operations described herein. In some aspects, such components may include the communication manager 150. In some aspects, such components may include in conjunction with Figure 2 One or more components of base station 110 are described.

[0065] As mentioned above, Figure 2 are provided only as examples. Other examples may be related to Figure 2 Different than described.

[0066] Figure 3300 is a diagram illustrating an example of a downlink (DL)-centric time slot or wireless communication structure according to various aspects of the present disclosure. The DL-centric time slot may include a control portion 302. The control portion 302 may be present at an initial or beginning portion of the DL-centric time slot. The control portion 302 may include various scheduling information and / or control information corresponding to various portions of the DL-centric time slot. In some configurations, the control portion 302 may be a PDCCH, such as Figure 3 In some aspects, the control portion 302 may include legacy PDCCH information, shortened PDCCH (sPDCCH) information, a control format indicator (CFI) value (e.g., carried on a physical control format indicator channel (PCFICH)), one or more grants (e.g., downlink grant, uplink grant), etc. Downlink control information (DCI) may be received in the PDCCH. Control resource sets (CORESETs) may also be restricted to the PDCCH.

[0067] The UE may use the RACH procedure to synchronize with the base station and establish a radio resource control (RRC) connection to the base station. This may give the UE the ability to send data to and receive data from the base station. To start the RACH procedure, the UE may send a first RACH message to the base station to initiate communication with the base station. In response, the base station may send a second RACH message to the UE in a DCI, which will be in the PDCCH, such as Figure 3 As shown in the control part 302.

[0068] The DL-centric time slot may also include a DL data portion 304. The DL data portion 304 may sometimes be referred to as the payload of the DL-centric time slot. The DL data portion 304 may include communication resources for communicating DL data from a scheduling entity (e.g., a UE or a BS) to a subordinate entity (e.g., a UE). In some configurations, the DL data portion 304 may be a PDSCH. The data portion 304 may be considered to be outside the PDCCH. If the UE is to receive a RACH message outside the PDCCH, where there is a lack of DCI, the UE may monitor the RACH message in a set of resource candidates (e.g., symbols, subcarriers) located in the data portion 304, such as in a physical downlink shared channel (PDSCH), rather than in the PDCCH of the control portion 302. For example, the UE may monitor a second RACH message 310 in a resource candidate set 308, which includes more symbols than two or three symbols available for the second RACH message in the control portion 302. The resource candidate set 308 may also be scheduled in the absence of DCI or by signaling that is not in the DCI.

[0069] The DL-centric timeslot may also include an uplink (UL) short burst portion 306. The UL short burst portion 306 may sometimes be referred to as a UL burst, a UL burst portion, a common UL burst, a short burst, a UL short burst, a common UL short burst, a common UL short burst portion, and / or various other suitable terms. In some aspects, the UL short burst portion 306 may include one or more reference signals. Additionally or alternatively, the UL short burst portion 306 may include feedback information corresponding to various other portions of the DL-centric timeslot. For example, the UL short burst portion 306 may include feedback information corresponding to the control portion 302 and / or the data portion 304. Non-limiting examples of information that may be included in the UL short burst portion 306 include an acknowledgement (ACK) signal (e.g., a physical uplink control channel (PUCCH) ACK, a physical uplink shared channel (PUSCH) ACK, an immediate ACK), a negative acknowledgement (NACK) signal (e.g., a PUCCH NACK, a PUSCH NACK, an immediate NACK), a scheduling request (SR), a buffer status report (BSR), a hybrid automatic repeat request (HARQ) indicator, a channel state indication (CSI), a CQI, a sounding reference signal (SRS), a demodulation reference signal (DMRS), PUSCH data, and / or various other suitable types of information. The UL short burst portion 306 may include additional or alternative information, such as information related to a RACH procedure, a scheduling request, and various other suitable types of information.

[0070] like Figure 3 As shown, the end of the DL data portion 304 can be separated in time from the beginning of the UL short burst portion 306. This time separation may sometimes be referred to as a gap, a guard period, a guard interval, and / or various other suitable terms. This separation provides time for switching from DL communications (e.g., receiving operations of subordinate entities (e.g., UEs)) to UL communications (e.g., transmissions of subordinate entities (e.g., UEs)). The foregoing is an example of a DL-centric wireless communication structure, and alternative structures with similar features may exist without departing from the aspects described herein.

[0071] As mentioned above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 Different than described.

[0072] Figure 4 400 is a diagram illustrating an example of a UL-centric time slot or wireless communication structure according to various aspects of the present disclosure. The UL-centric time slot may include a control portion 402. The control portion 402 may be present at the initial or beginning portion of the UL-centric time slot. Figure 4The control portion 402 in the embodiment may be similar to the above reference Figure 4 The control portion 402 described above. The UL-centric timeslot may also include a UL long burst portion 404. The UL long burst portion 404 may sometimes be referred to as the payload of the UL-centric timeslot. The UL portion may refer to a communication resource used to communicate UL data from a subordinate entity (e.g., a UE) to a scheduling entity (e.g., a UE or a BS). In some configurations, the control portion 402 may be a PDCCH. In some aspects, the UE may receive a DCI in the control portion 402. If the UE is to receive a RACH message in the DCI, the UE may receive the RACH message in the control portion 402.

[0073] like Figure 4 As shown, the end of the control portion 402 can be separated in time from the beginning of the UL long burst portion 404. This time separation may sometimes be referred to as a gap, a guard period, a guard interval, and / or various other suitable terms. This separation provides time to switch from DL communication (e.g., receiving operation of the scheduling entity) to UL communication (e.g., transmission of the scheduling entity).

[0074] The UL-centric timeslot may also include a UL short burst portion 406 . Figure 4 The UL short burst portion 406 in the embodiment may be similar to that in the embodiment of the present invention. Figure 3 The UL short burst portion 306 described above may include the combination of Figure 3 The foregoing is one example of a UL-centric wireless communication structure, and there may be alternative structures with similar features without departing from the aspects described herein.

[0075] As mentioned above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 Different than described.

[0076] As previously described, the UE may send a RACH message to the base station to initiate communication with the base station. The RACH message may be the first message sent by the UE when the UE is powered on. The RACH message may be sent on the physical RACH (PRACH) and may be more generally referred to as a PRACH communication. The UE may use the RACH message to request an uplink allocation from the base station.

[0077] The first RACH message may include a PRACH sequence (also referred to as a PRACH preamble or a PRACH preamble sequence), which may be used to distinguish UEs. The UE may use the PRACH format to determine the PRACH sequence and / or transmission attributes of the PRACH sequence. The UE may receive an initial RACH configuration in a transmission from the base station and use the initial RACH configuration to send the first RACH message. The first RACH message may initiate a RACH procedure to obtain an uplink allocation.

[0078] Figure 5A and Figure 5B 5 are diagrams illustrating an example 500 of a 4-step RACH procedure and an example 502 of a 2-step RACH procedure, respectively. In each example, a UE is performing a RACH procedure with a base station.

[0079] In LTE and NR, a 4-step RACH procedure may be a RACH procedure with a handshake of four messages (msg1, msg2, msg3, msg4) between the UE and the base station. As an example of a first RACH message, the UE may send msg1 with a PRACH preamble to the base station on the PRACH. As an example of a second RACH message, the base station may send msg2 to the UE on the PDCCH and the PDSCH. msg2 may include a random access response. In a 4-step RACH procedure, the UE may monitor the second RACH message (e.g., msg2) in the DCI in the PDCCH. However, according to various aspects described herein, the UE may monitor the second RACH message in a resource candidate set in the absence of a DCI, the resource candidate set being based at least in part on the first RACH message sent. That is, according to one example, the resources for the second RACH message are based at least in part on the first RACH message sent, the DCI is not used to schedule the second RACH message, and the second RACH message is not received in the DCI. In some aspects, the second RACH message may be scheduled via an RMSI message or in other system information.

[0080] The UE may send msg3 on PUSCH. msg3 may include contention request and device information. The base station may send msg4 on PDCCH and PDSCH. msg4 may include contention resolution. Contention request and contention resolution involve resolving contention from multiple UEs that happen to use the same PRACH preamble.

[0081] In NR, the 2-step RACH procedure is another RACH procedure. In the 2-step procedure, the base station broadcasts system information and synchronization signal block (SSB) information to the UE. As an example of a first RACH message, the UE can send the PRACH preamble as part of a msgA message to the base station. msgA can also include a payload. The base station can process the preamble, detect the preamble, and process the payload. As an example of a second RACH message, the base station can send a response in msgB. msg1 and msg3 of the 4-step RACH can be considered to be folded into msgA, while msg2 and msg4 can be considered to be folded into msgB.

[0082] In a 2-step RACH procedure, the UE may monitor the second RACH message (e.g., msgB) in the DCI in the PDCCH. However, according to various aspects described herein, the UE may instead monitor the second RACH message in a resource candidate set in the absence of the DCI, the resource candidate set being based at least in part on the transmitted first RACH message. That is, the resources used for the second RACH message are based at least in part on the first RACH message, the DCI is not used to schedule the second RACH message, and the second RACH message is not received in the DCI. In some aspects, the second RACH message may be scheduled via an RMSI message or in other system information.

[0083] As mentioned above, Figure 5A and Figure 5B are provided as two examples of RACH procedures. Other examples may be related to Figure 5A-Figure 5B Different than described.

[0084] The UE may send a first RACH message to the base station to initiate communication. The base station may respond with a second RACH message (e.g., msg2, msgB) including information about the PDCCH. However, if the UE coverage or signal strength is below a threshold level for certain frequencies (e.g., mmWave 5G), the base station may be limited in how the base station boosts the transmission of the second RACH message. The PDCCH may become a bottleneck for RACH information. The base station can only use two or three symbols in the PDCCH because the PDCCH is limited to the CORESET, so the transmit power increase is limited to two or three symbols.

[0085] According to various aspects described herein, a UE may monitor and receive a second RACH message in time and frequency resources outside of a PDCCH. This may be referred to as a second RACH message without a PDCCH (e.g., msg2 without a PDCCH, msgB without a PDCCH) or a RACH message without a PDCCH. In one example, because the DCI is included in the PDCCH, the RACH message without a PDCCH may be a RACH message without a DCI. That is, the DCI may be missing from the RACH information without a PDCCH. By sending the second RACH message outside of the PDCCH, the UE may have a better chance of receiving the second RACH message because the UE may receive more symbols (e.g., up to 14 symbols) of the second RACH message.

[0086] In the RACH process, the data of the second RACH message on the PDSCH can usually be scheduled by the DCI carried in the PDCCH. Instead of scheduling the data on the PDSCH via the PDCCH, the base station can schedule the PDSCH via the information in the second RACH message, the information in the RMSI message, other system information, etc.

[0087] Figure 6 Illustrated is an example 600 of a base station sending a RACH message without a PDCCH according to various aspects of the present disclosure. Figure 6 Base stations (BSs) 610 (eg, Figure 1 and Figure 2 BS 110) and UE 620 (eg, Figure 1 and Figure 2 UE 120 depicted in FIG. 1 ).

[0088] As indicated by reference numeral 630, UE 620 may send a first RACH message as part of a RACH procedure (e.g., 4-step RACH, 2-step RACH). The first RACH message may include a PRACH preamble. UE 620 may send the first RACH message in a first format selected from a first format and a second format, wherein the first format indicates that BS 610 may send a responding second RACH message in an alternative resource other than PDCCH, and the second format indicates that the second RACH message may be sent in PDCCH as generally expected.

[0089] In some aspects, the UE 620 may determine to send a first RACH message in a first format based at least in part on a RACH type (e.g., 2-step, 4-step), a signal measurement, a RACH format, a RACH sequence set (e.g., a preamble sequence subset), a RACH time resource, a RACH opportunity, a subset of RACH opportunities, or a combination thereof. For example, the UE 620 may be configured to use a RACH format, and thus the first format may be a RACH format. The UE 620 may receive the RACH format in a configuration message from the BS 610, such as in an RMSI message or other system information. The BS 610 may determine to instruct the UE 620 to send a first RACH message in a first format based at least in part on a RACH type, a signal measurement, a RACH format, a RACH sequence set, a preamble sequence subset, a RACH opportunity or a subset of RACH opportunities, a RACH time resource, or a combination thereof.

[0090] In some aspects, the UE 620 may determine to send a first RACH message in a first format instead of a second format based at least in part on the results of the signal measurement. The UE 620 may measure the RSRP of the SSB broadcast and determine that the RSRP does not meet the RSRP threshold. As a result, the UE 620 may determine to use the first format, which may trigger a responsive second RACH message that can use more symbols and / or more transmit power in an alternative resource other than the PDCCH. The RSRP threshold may be a threshold of the PDCCH.

[0091] In some aspects, the UE 620 may determine to send the first RACH message in the first format based at least in part on a RACH type or a number of RACH sequences. For example, the UE 620 may determine that a particular RACH type, a subset of preamble sequences, and / or a threshold number of RACH sequences in a PRACH preamble may be necessary to identify the UE 620. Thus, the UE 620 may determine that the second RACH message may be better received in an alternate resource other than the PDCCH.

[0092] In some aspects, the UE 620 may determine to send the first RACH message in the first format based at least in part on any combination of the above factors. In some aspects, the BS 610 may configure the UE 620 with rules for selecting the first format over the second format (or any other format) and / or for monitoring alternative resources for the second RACH message.

[0093] As indicated by reference numeral 635, BS 610 may receive a first RACH message and determine how to send a second RACH message. For example, BS 610 may determine to send the second RACH message in an alternative resource other than PDCCH based at least in part on receiving the first RACH message in a first format. BS 610 may schedule the RACH message via an RMSI message or another system information message that does not involve downlink control information in the PDDCH. In some aspects, BS 610 may determine to send the second RACH message in an alternative resource based at least in part on other characteristics of the first RACH message, such as a RACH type, a signal measurement, a RACH format, a RACH sequence set, a subset of a preamble sequence of the first RACH message, a RACH time resource, a RACH opportunity, a subset of RACH opportunities, or a combination thereof.

[0094] As shown in reference numeral 640, BS 610 may send a second RACH message on an alternative resource other than PDCCH. These alternative resources may be part of a resource candidate set. The resource candidate set may be in the PDSCH. As shown in reference numeral 645, UE 620 may monitor the resource candidate set for the second RACH message, because the alternative resource may be one or more resources in the resource candidate set. UE 620 may perform blind detection on the resource candidate set to detect on which alternative resources the UE 620 may receive the second RACH message. UE 620 may also perform a cyclic redundancy check (CRC) on any data received on the alternative resource. The resource candidate set may be based at least in part on a RACH opportunity, which may be a time window for receiving a RACH message. In some aspects, UE 620 may receive the resource candidate set from BS 610 in an RMSI message or other system information.

[0095] UE 620 may normally receive control information in the PDCCH, such as DCI, for determining the location and / or scheduling of receiving data on the PDSCH, but if UE 620 is to monitor the second RACH message outside of the PDCCH, then UE 620 may have to have another way to receive the control information. In some aspects, UE 620 may receive the control information in the second RACH message, the RMSI message, or other system information.

[0096] In some aspects, the SSB may include resources that carry a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a physical broadcast channel (PBCH) 330, and the like. The SSB may also be referred to as a synchronization signal and a PBCH block. During the initial network access process, the UE may monitor and / or measure the SSB using different receive (Rx) beams. Based at least in part on the monitoring and / or measurement, the UE may indicate to the base station one or more SSBs with the best signal parameters (e.g., RSRP parameters, etc.). The base station and the UE may use one or more indicated SSBs to select one or more beams for communication between the base station and the UE (e.g., for RACH processes, etc.). In some aspects, the UE 620 may determine that the PDSCH is quasi-co-located with the SSB beam, and thus the UE 620 may use the SSB beam information to locate the PDSCH.

[0097] UE 620 may monitor and receive a second RACH message outside of the PDCCH, such as in a resource lacking DCI based on the first RACH message. The second RACH message may have been boosted by BS 610 to improve coverage beyond that available in the PDCCH. UE 620 may continue and complete the RACH procedure and successfully connect to BS 610 without wasting resources and increasing latency.

[0098] Figure 7 700 is a diagram illustrating an example process 700 performed, for example, by a UE according to various aspects of the present disclosure. The example process 700 is a diagram in which a UE (e.g., Figure 1 and Figure 2 UE 120 depicted in Figure 6 An example of UE 620, etc. depicted in FIG. 6A ) performing operations associated with a RACH message without a PDCCH.

[0099] like Figure 7 As shown, in some aspects, process 700 may include sending a first RACH message to a base station (block 710). For example, as described above, the UE (e.g., using receive processor 258, transmit processor 264, controller / processor 280, memory 282, etc.) may send a first RACH message to a base station.

[0100] like Figure 7As further shown in FIG. 7 , in some aspects, process 700 may include monitoring a set of resource candidates for a second RACH message from a base station in the absence of downlink control information, the set of resource candidates being based at least in part on the transmitted first RACH message (block 720). For example, as described above, the UE (e.g., using receive processor 258, transmit processor 264, controller / processor 280, memory 282, etc.) may monitor a set of resource candidates outside of a PDCCH for a second RACH message from a base station based at least in part on the transmitted first RACH message.

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

[0102] In a first aspect, monitoring the set of resource candidates for a second RACH message is based at least in part on one or more of a RACH type, a subset of a preamble sequence of the first RACH message, a RACH opportunity, or a subset of RACH opportunities.

[0103] In a second aspect, alone or in combination with the first aspect, process 700 includes receiving information identifying a candidate set of resources from a base station.

[0104] In a third aspect, alone or in combination with one or more of the first and second aspects, receiving information identifying the candidate set of resources includes receiving the information identifying the candidate set of resources in a remaining minimum system information message or another system information message.

[0105] In a fourth aspect, alone or in combination with one or more of the first to third aspects, monitoring the second RACH message includes performing blind detection on one or more resource candidates in the set of resource candidates.

[0106] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 700 includes determining control information for data on a physical downlink shared channel based at least in part on a second RACH message.

[0107] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the resource candidate set is at least partially based on a RACH opportunity.

[0108] In a seventh aspect, either alone or in combination with one or more of aspects 1 to 6, process 700 includes determining that a physical downlink shared channel is quasi-co-located with an SSB beam based at least in part on determining that a second RACH message from a base station is outside of a PDCCH.

[0109] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, monitoring the second RACH message includes performing a CRC on one or more resource candidates in the set of resource candidates.

[0110] although Figure 7 Example blocks of process 700 are shown, but in some aspects, process 700 may include more Figure 7 The blocks depicted in the process 700 may be more blocks, fewer blocks, different blocks, or differently arranged blocks. Additionally or alternatively, two or more blocks of process 700 may be performed in parallel.

[0111] Figure 8 8 is a diagram illustrating an example process 800 performed, for example, by a base station, according to various aspects of the present disclosure. Example process 800 is a base station (e.g., Figure 1 and Figure 2 BS 110, as depicted in Figure 6 An example of BS 610, etc. depicted in FIG. 6A performing operations associated with a RACH message without a PDCCH.

[0112] like Figure 8 As shown, in some aspects, process 800 may include receiving a first RACH message from a UE (block 810). For example, as described above, a base station (e.g., using transmit processor 220, receive processor 238, controller / processor 240, memory 242, etc.) may receive a first RACH message from a UE.

[0113] like Figure 8 As further shown in FIG. 8 , in some aspects, process 800 may include sending a second RACH message in a set of resource candidates outside of the PDCCH based at least in part on receiving the first RACH message (block 820). For example, as described above, the base station (e.g., using transmit processor 220, receive processor 238, controller / processor 240, memory 242, etc.) may send the second RACH message in a set of resource candidates outside of the PDCCH based at least in part on receiving the first RACH message.

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

[0115] In a first aspect, process 800 includes determining a RACH configuration that specifies a UE to send a first RACH message in a first format among a first format and a second format based at least in part on a RACH type, a signal measurement, a RACH format, a RACH sequence set, a RACH time resource, or a combination of two or more of the signal measurement, the RACH format, the RACH sequence set, or the RACH time resource; and sending the RACH configuration to the UE.

[0116] In a second aspect, alone or in combination with the first aspect, sending the RACH configuration includes sending the RACH configuration in a remaining minimum system information message or in another system information message.

[0117] In a third aspect, alone or in combination with one or more of the first and second aspects, process 800 includes sending information identifying a candidate set of resources to a UE.

[0118] In a fourth aspect, alone or in combination with one or more of the first to third aspects, sending information identifying the candidate set of resources includes sending the information identifying the candidate set of resources in a remaining minimum system information message or another system information message.

[0119] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the resource candidate set is based at least in part on a RACH opportunity.

[0120] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the second RACH message includes control information of data on a physical downlink shared channel.

[0121] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, sending a second RACH message in a resource candidate set outside the PDCCH is at least partially based on information in the first RACH message, wherein the information indicates one or more of a RACH message type, a subset of a preamble sequence of the first RACH message, a RACH opportunity, or a subset of RACH opportunities.

[0122] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, sending a second RACH message in a set of resource candidates outside of a PDCCH is based at least in part on determining that a signal measurement satisfies a threshold.

[0123] In a ninth aspect, either alone or in combination with one or more of aspects 1 to 8, process 800 includes sending a RACH configuration based at least in part on a RACH type associated with a first RACH message, a subset of a preamble sequence of the first RACH message, a RACH opportunity, or a subset of RACH opportunities, the RACH configuration indicating that a second RACH message is to be sent in a resource candidate set outside of a PDCCH.

[0124] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the resource candidate set is located in a PDSCH.

[0125] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the second RACH message is scheduled via a RMSI message or another system information message.

[0126] although Figure 8 Example blocks of process 800 are shown, but in some aspects, process 800 may include more Figure 8 The blocks depicted in the process 800 may be more blocks, fewer blocks, different blocks, or differently arranged blocks. Additionally or alternatively, two or more blocks of process 800 may be performed in parallel.

[0127] Fig. 9 is a block diagram of an example apparatus 900 for wireless communication according to various aspects of the present disclosure. The apparatus 900 may be, similar to, include, or be included in a UE (e.g., Figure 6 In some aspects, the apparatus 900 includes a receiving component 902, a communication manager 904, and a sending component 906, which can communicate with each other (e.g., via one or more buses). As shown, the apparatus 900 can communicate with another apparatus 908 (such as a client, a server, a UE, a base station, or another wireless communication device) using the receiving component 902 and the sending component 906.

[0128] In some aspects, the apparatus 900 may be configured to perform Figure 6 Additionally or alternatively, the apparatus 900 may be configured to perform one or more processes described herein, such as Figure 7 In some aspects, the apparatus 900 may include the above combined Figure 2 One or more components of a first UE are described.

[0129] The receiving component 902 may provide means for receiving communications, such as reference signals, control information, data communications, or combinations thereof, from the apparatus 908. The receiving component 902 may provide the received communications to one or more other components of the apparatus 900, such as the communications manager 904. In some aspects, the receiving component 902 may provide means for signal processing (e.g., filtering, amplifying, demodulating, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation, or decoding, etc.) the received communications, and may provide the processed signals to one or more other components. In some aspects, the receiving component 902 may include the above in combination with Figure 2 One or more antennas, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described first UE.

[0130] The transmission component 906 may provide means for transmitting communications (such as reference signals, control information, data communications, or combinations thereof) to the device 908. In some aspects, the communication manager 904 may generate communications and may communicate the generated communications to the transmission component 906 for transmission to the device 908. In some aspects, the transmission component 906 may provide means for performing signal processing (e.g., filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 908. In some aspects, the transmission component 906 may include the above in combination with Figure 2 One or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described first UE. In some aspects, the transmit component 906 can be co-located with the receive component 902 in a transceiver.

[0131] In some aspects, the communication manager 904 may provide means for sending a first RACH message to a base station, and means for monitoring a second RACH message from the base station in a resource candidate set in the absence of downlink control information, the resource candidate set being based at least in part on the sent first RACH message. In some aspects, the communication manager 904 may include the above in combination with Figure 2 A controller / processor, memory, or combination thereof of the first UE described. In some aspects, the communication manager 904 may include a receiving component 902, a sending component 906, etc. In some aspects, the components provided by the communication manager 904 may include components provided by the receiving component 902, the communication manager 904, etc., or be included therein.

[0132] In some aspects, the communication manager 904 and / or one or more components of the communication manager 904 may include hardware (e.g., in conjunction with Figure 2In some aspects, the communication manager 904 and / or one or more of its components may include the above combined Figure 2 A controller / processor, memory, or a combination thereof of the described UE 120 may be implemented therein.

[0133] In some aspects, the communication manager 904 and / or one or more components of the communication manager 904 may be implemented in code (e.g., as software or firmware stored in memory), such as in conjunction with Fig.11 For example, the communication manager 904 and / or the components (or parts of the components) of the communication manager 904 may be implemented as instructions or codes stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the functions or operations of the communication manager 904 and / or the components. If implemented in code, the functions of the communication manager 904 and / or the components may be implemented by the above combination. Figure 2 The described UE 120 may be executed by a controller / processor, a memory, a scheduler, a communication unit, or a combination thereof.

[0134] Fig. 9 The number and arrangement of components shown in FIG. 1 are provided as examples. Fig. 9 There may be additional components, fewer components, different components, or differently arranged components than those shown in . Fig. 9 Two or more components shown may be implemented in a single component, or Fig. 9 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig. 9 The component set (one or more) shown may be implemented as described by Fig. 9 Another component shown may be a collection of components that perform one or more functions.

[0135] Fig.10 1 is a diagram illustrating an example 1000 of a hardware implementation of an apparatus 1002 employing a processing system 1004. The apparatus 1002 may be, be similar to, include, or be included in Fig. 9 In the device 900 shown.

[0136] The processing system 1004 may be implemented with a bus architecture, generally represented by bus 1006. Bus 1006 may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of the processing system 1004. Bus 1006 links together various circuits including one or more processors and / or hardware components represented by processor 1008, illustrated components, and computer-readable media / memory 1010. Bus 1006 may also link various other circuits, such as timing sources, peripherals, voltage regulators, power management circuits, and the like.

[0137] The processing system 1004 can be coupled to a transceiver 1012. The transceiver 1012 is coupled to one or more antennas 1014. The transceiver 1012 provides a means for communicating with various other devices over a transmission medium. The transceiver 1012 receives signals from the one or more antennas 1014, extracts information from the received signals, and provides the extracted information to the processing system 1004, specifically, to the receiving component 1016. In addition, the transceiver 1012 receives information from the processing system 1004, specifically, from the transmitting component 1018, and generates a signal to be applied to the one or more antennas 1014 based at least in part on the received information.

[0138] Processor 1008 is coupled to computer readable medium / memory 1010. Processor 1008 is responsible for general processing, including running software stored on computer readable medium / memory 1010. When executed by processor 1008, the software causes processing system 1004 to perform various functions described herein in conjunction with the client. Computer readable medium / memory 1010 may also be used to store data manipulated by processor 1008 when running the software. Processing system 1004 may include Fig.10 The components shown and / or not shown may be software modules running in the processor 1008, software modules residing / stored in the computer-readable medium / memory 1010, one or more hardware modules coupled to the processor 1008, or some combination thereof.

[0139] In some aspects, the processing system 1004 may be a component of the UE 120 and may include the memory 282 and / or at least one of the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280. In some aspects, the apparatus 1002 for wireless communication provides a component for sending a first RACH message to a base station, and a component for monitoring a second RACH message from the base station in a resource candidate set in the absence of downlink control information, the resource candidate set being based at least in part on the sent first RACH message. The aforementioned components may be one or more of the aforementioned components of the processing system 1004 of the apparatus 1002 configured to perform the functions recited by the aforementioned components. As described elsewhere herein, the processing system 1004 may include the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280. In one configuration, the aforementioned components may be the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280 configured to perform the functions and / or operations described herein.

[0140] Fig.10are provided as examples. Other examples can be combined with Fig.10 Different than described.

[0141] Fig.11 1 is a diagram illustrating an example 1100 of an implementation of code and circuitry for an apparatus 1102 for wireless communication. The apparatus 1102 may be, similar to, include, or be included in Fig.10 The device 1002 and / or Fig. 9 The device 900 is shown in FIG. 1102. The device 1102 may include a processing system 1104, which may include a bus 1106 coupling one or more components, such as a processor 1108, a computer readable medium / memory 1110, a transceiver 1112, etc. As shown, the transceiver 1112 may be coupled to one or more antennas 1114.

[0142] like Fig.11 As further shown in FIG. 1 , the apparatus 1102 may include circuitry (circuitry 1116) for sending a first RACH message to a base station. For example, the apparatus 1102 may include circuitry 1116 for enabling the apparatus 1102 to send a first RACH message to a base station.

[0143] like Fig.11 As further shown in the figure, the apparatus 1102 may include a circuit (circuit 1118) for monitoring a second RACH message from a base station in a resource candidate set in the absence of downlink control information, the resource candidate set being based at least in part on the first RACH message transmitted. For example, the apparatus 1102 may include a circuit 1118 for enabling the apparatus 1102 to monitor a second RACH message from a base station in a resource candidate set in the absence of downlink control information, the resource candidate set being based at least in part on the first RACH message transmitted.

[0144] like Fig.11 As further shown in FIG. 1 , the apparatus 1102 may include code (code 1120) stored in the computer-readable medium 1110 for sending a first RACH message to the base station. For example, the apparatus 1102 may include code 1120, which, when executed by the processor 1108, may cause the transceiver 1112 to send the first RACH message to the base station.

[0145] like Fig.11As further shown in the figure, the apparatus 1102 may include code (code 1122) stored in the computer-readable medium 1110 for monitoring a second RACH message from a base station in a resource candidate set in the absence of downlink control information, the resource candidate set being based at least in part on the transmitted first RACH message. For example, the apparatus 1102 may include code 1124, which, when executed by the processor 1108, may cause the transceiver 1112 to monitor a second RACH message from a base station in a resource candidate set in the absence of downlink control information, the resource candidate set being based at least in part on the transmitted first RACH message.

[0146] Fig.11 is provided as an example. Other examples may be combined with Fig.11 Different than described.

[0147] Fig.12 1 is a block diagram of an example apparatus 1200 for wireless communication according to various aspects of the present disclosure. The apparatus 1200 may be, similar to, include, or be included in a base station (e.g., Figure 6 The base station 610 and / or Figure 1 and 2 In some aspects, the apparatus 1200 includes a receiving component 1202, a communication manager 1204, and a sending component 1206, which can communicate with each other (e.g., via one or more buses). As shown, the apparatus 1200 can communicate with another apparatus 1208 (such as a client, a server, a UE, a base station, or another wireless communication device) using the receiving component 1202 and the sending component 1206.

[0148] In some aspects, the apparatus 1200 may be configured to perform Figure 6 Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as Figure 8 In some aspects, the apparatus 1200 may include the above combined Figure 2 One or more components of a base station are described.

[0149] The receiving component 1202 may provide means for receiving communications, such as reference signals, control information, data communications, or combinations thereof, from the apparatus 1208. The receiving component 1202 may provide the received communications to one or more other components of the apparatus 1200, such as the communications manager 1204. In some aspects, the receiving component 1202 may provide means for performing signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications, and may provide the processed signals to one or more other components. In some aspects, the receiving component 1202 may include the above in combination with Figure 2 One or more antennas, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of a base station are described.

[0150] The transmission component 1206 may provide means for transmitting communications, such as reference signals, control information, data communications, or a combination thereof, to the device 1208. In some aspects, the communication manager 1204 may generate communications and may communicate the generated communications to the transmission component 1206 for transmission to the device 1208. In some aspects, the transmission component 1206 may provide means for performing signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1208. In some aspects, the transmission component 1206 may include the above in combination with Figure 2 One or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described base stations. In some aspects, the transmit component 1206 can be co-located with the receive component 1202 in a transceiver.

[0151] The communication manager 1204 may provide a component for receiving a first RACH message from the UE, and a component for sending a second RACH message in a resource candidate set outside the PDCCH based at least in part on receiving the first RACH message. In some aspects, the communication manager 1204 may include the above in combination with Figure 2 The controller / processor, memory, scheduler, communication unit, or combination thereof of the described base station. In some aspects, the communication manager 1204 may include a receiving component 1202, a sending component 1206, etc. In some aspects, the components provided by the communication manager 1204 may include or be included in the components provided by the receiving component 1202, the sending component 1204, etc.

[0152] In some aspects, the communications manager 1204 and / or one or more of its components may include hardware (e.g., in conjunction with Fig.14In some aspects, the communication manager 1204 and / or one or more of its components may include the above combined Figure 2 A controller / processor, memory, or a combination thereof of the described BS 110 may be implemented therein.

[0153] In some aspects, the communications manager 1204 and / or one or more of its components may be implemented in code (e.g., as software or firmware stored in memory), such as in conjunction with Fig.14 For example, the communication manager 1204 and / or the components (or parts of the components) of the communication manager 1204 may be implemented as instructions or codes stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the functions or operations of the communication manager 1204 and / or the components. If implemented in code, the functions of the communication manager 1204 and / or the components may be implemented by combining the above Figure 2 The described BS 110 may be executed by a controller / processor, a memory, a scheduler, a communication unit, or a combination thereof.

[0154] Fig.12 The number and arrangement of components shown in the FIG. are provided as examples. Fig.12 There may be additional components, fewer components, different components, or differently arranged components than those shown in . Fig.12 Two or more components shown in may be implemented in a single component, or Fig.12 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig.12 The component set (one or more) shown in the figure may be executed as described by Fig.12 One or more functions performed by another component collection shown in .

[0155] Fig.13 is a diagram illustrating an example 1300 of a hardware implementation of an apparatus 1302 employing a processing system 1304. The apparatus 1302 may be, be similar to, include, or be included in Fig.12 In the device 1200 shown.

[0156] The processing system 1304 may be implemented with a bus architecture, generally represented by bus 1306. Bus 1306 may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of the processing system 1304. Bus 1306 links together various circuits including one or more processors and / or hardware components (represented by processor 1308, components shown, and computer-readable media / memory 1310). Bus 1306 may also link various other circuits, such as timing sources, peripherals, voltage regulators, power management circuits, and the like.

[0157] The processing system 1304 can be coupled to a transceiver 1312. The transceiver 1312 is coupled to one or more antennas 1314. The transceiver 1312 provides components for communicating with various other devices over a transmission medium. The transceiver 1312 receives signals from the one or more antennas 1314, extracts information from the received signals, and provides the extracted information to the processing system 1304, specifically, to the receiving component 1316. In addition, the transceiver 1312 receives information from the processing system 1304, specifically, from the transmitting component 1318, and generates a signal to be applied to the one or more antennas 1314 based at least in part on the received information.

[0158] Processor 1308 is coupled to computer readable medium / memory 1310. Processor 1308 is responsible for general processing, including executing software stored on computer readable medium / memory 1310. When executed by processor 1308, the software causes processing system 1304 to perform various functions described herein in conjunction with the server. Computer readable medium / memory 1310 may also be used to store data that is manipulated by processor 1308 when executing the software. Processing system 1304 may include Fig.13 The components shown and / or not shown may be software modules running in the processor 1308, resident / stored in the computer-readable medium / memory 1310, one or more hardware modules coupled to the processor 1308, or some combination thereof.

[0159] In some aspects, the processing system 1304 may be a component of the UE 120 and may include at least one of the memory 282 and / or the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280. In some aspects, the apparatus 1302 for wireless communication provides a component for receiving a first RACH message from the UE, and a component for sending a second RACH message in a resource candidate set outside the PDCCH based at least in part on receiving the first RACH message. The aforementioned components may be one or more of the aforementioned components of the processing system 1304 of the apparatus 1302 configured to perform the functions recited by the aforementioned components. As described elsewhere herein, the processing system 1304 may include the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280. In one configuration, the aforementioned components may be the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280 configured to perform the functions and / or operations described herein.

[0160] Fig.13 are provided as examples. Other examples can be combined with Fig.13Different than described.

[0161] Fig.14 1400 is a diagram illustrating an example implementation of code and circuitry for an apparatus 1402 for wireless communication. The apparatus 1402 may be, similar to, include, or be included in Fig.11 The device 1102 and / or Fig.10 The device 1000 is shown in FIG. 1402. The device 1402 may include a processing system 1404, which may include a bus 1406 coupling one or more components, such as a processor 1408, a computer readable medium / memory 1410, a transceiver 1412, etc. As shown, the transceiver 1412 may be coupled to one or more antennas 1414.

[0162] like Fig.14 As further shown in FIG. 1 , the apparatus 1402 may include circuitry (circuitry 1416) for receiving a first RACH message from the UE. For example, the apparatus 1402 may include circuitry 1416 for enabling the apparatus 1402 to receive a first RACH message from the UE.

[0163] like Fig.14 As further shown in FIG. 1 , the apparatus 1402 may include circuitry (circuitry 1418) for receiving updates from the UE based at least in part on the federated learning configuration. For example, the apparatus 1402 may include circuitry 1418 for enabling the apparatus 1402 to receive updates from the UE based at least in part on the federated learning configuration.

[0164] like Fig.14 As further shown in FIG. 1 , the apparatus 1402 may include code (code 1420) stored in the computer-readable medium 1410 for receiving a first RACH message from the UE. For example, the apparatus 1402 may include code 1420, which, when executed by the processor 1408, may cause the transceiver 1412 to receive a first RACH message from the UE.

[0165] like Fig.14 As further shown in the figure, the apparatus 1402 may include code (code 1422) stored in the computer-readable medium 1410 for sending a second RACH message in a resource candidate set outside the PDCCH based at least in part on receiving the first RACH message. For example, the apparatus 1402 may include code 1422, which, when executed by the processor 1408, may cause the transceiver 1412 to send the second RACH message in a resource candidate set outside the PDCCH based at least in part on receiving the first RACH message.

[0166] Fig.14 are provided as examples. Other examples can be combined with Fig.14 Different than described.

[0167] The following provides an overview of various aspects of the present disclosure:

[0168] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: sending a first random access channel (RACH) message to a base station; and in the absence of downlink control information, monitoring a second RACH message from the base station in a resource candidate set, the resource candidate set being at least partially based on the sent first RACH message.

[0169] Aspect 2: The method of aspect 1, wherein monitoring the resource candidate set for the second RACH message is based at least in part on one or more of a RACH type, a subset of preamble sequences of the first RACH message, a RACH opportunity, or a subset of RACH opportunities.

[0170] Aspect 3: The method according to aspect 1 or 2 further includes receiving information identifying a candidate resource set from a base station.

[0171] Aspect 4: The method according to aspect 3, wherein receiving information identifying the candidate set of resources includes receiving the information identifying the candidate set of resources in a remaining minimum system information message or another system information message.

[0172] Aspect 5: The method according to any one of aspects 1-4, wherein monitoring the second RACH message comprises performing blind detection on one or more resource candidates in the resource candidate set.

[0173] Aspect 6: The method according to any one of aspects 1-5, wherein monitoring the second RACH message comprises performing a cyclic redundancy check on one or more resource candidates in the resource candidate set.

[0174] Aspect 7: The method according to any one of aspects 1-6, further comprising determining control information for data on a physical downlink shared channel based at least in part on the second RACH message.

[0175] Aspect 8: The method according to any one of aspects 1-7, wherein the resource candidate set is based at least in part on a RACH opportunity.

[0176] Aspect 9: The method according to any one of Aspects 1-8 further includes determining that a physical downlink shared channel is quasi-co-located with a synchronization signal and a physical broadcast channel block (SSB) beam based at least in part on determining that a second RACH message from a base station is outside a physical downlink control channel (PDCCH).

[0177] Aspect 10: The method according to any one of aspects 1-9, wherein the resource candidate set is located in a physical downlink shared channel.

[0178] Aspect 11: The method according to any one of aspects 1-10, wherein the second RACH message is scheduled via a RMSI message or another system information message.

[0179] Aspect 12: A wireless communication method performed by a base station, comprising: receiving a first random access channel (RACH) message from a user equipment (UE); and sending a second RACH message in a resource candidate set outside a physical downlink control channel (PDCCH) based at least in part on receiving the first RACH message.

[0180] Aspect 13: A method according to Aspect 12, wherein sending a second RACH message in a resource candidate set outside the PDCCH is at least partially based on information in the first RACH message, wherein the information indicates one or more of a RACH message type, a subset of a preamble sequence of the first RACH message, a RACH opportunity, or a subset of RACH opportunities.

[0181] Aspect 14: The method according to aspect 12 or 13, wherein the resource candidate set is located in a physical downlink shared channel.

[0182] Aspect 15: The method according to any one of aspects 12-14, further comprising the second RACH message being scheduled via a remaining minimum system information message or another system information message.

[0183] Aspect 16: The method according to any one of aspects 12-15, wherein sending the second RACH message in the set of resource candidates outside the PDCCH is based at least in part on determining that the signal measurement satisfies a threshold.

[0184] Aspect 17: The method according to any one of Aspects 12-16 also includes sending a RACH configuration based at least in part on a RACH type associated with the first RACH message, a subset of the preamble sequence of the first RACH message, a RACH timing or a subset of RACH timings, wherein the RACH configuration indicates that the second RACH message will be sent in a resource candidate set outside the PDCCH.

[0185] Aspect 18: The method according to aspect 17, wherein sending the RACH configuration includes sending the RACH configuration in a remaining minimum system information message or in another system information message.

[0186] Aspect 19: According to the method according to any one of aspects 12 to 18, the method further comprises sending information identifying a candidate resource set to a UE.

[0187] Aspect 20: The method according to Aspect 19, wherein sending the information identifying the candidate set of resources includes sending the information identifying the candidate set of resources in a remaining minimum system information message or another system information message.

[0188] Aspect 21: The method according to any one of aspects 12-20, wherein the set of resource candidates is based at least in part on a RACH opportunity.

[0189] Aspect 22: The method according to any one of aspects 12-21, wherein the second RACH message includes control information of data on a physical downlink shared channel.

[0190] Aspect 23: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor, the instructions causing the apparatus to perform one or more methods of Aspects 1-22.

[0191] Aspect 20: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the method of one or more aspects of aspects 1-22.

[0192] Aspect 21: An apparatus for wireless communication, comprising at least one component for performing the method of one or more of aspects 1-22.

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

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

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

[0196] As used herein, the term "component" is intended to be broadly interpreted as hardware, firmware, or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, or a combination of hardware and software.

[0197] Some aspects are described herein in conjunction with a threshold value. As used herein, satisfying a threshold value may refer to a value greater than a threshold value, greater than or equal to a threshold value, less than a threshold value, less than or equal to a threshold value, equal to a threshold value, not equal to a threshold value, etc.

[0198] Obviously, the systems and / or methods described herein can be implemented in various forms of hardware, firmware, or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit these aspects. Therefore, the operation and behavior of the systems and / or methods are described herein without reference to specific software code - it should be understood that software and hardware can be designed to implement the systems and / or methods based at least in part on the description herein.

[0199] Although particular combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the various aspects. In fact, many of these features can be combined in ways not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below may depend directly on one claim, the disclosure of the various aspects includes the combination of each dependent claim with every other claim in the claim set. A phrase referring to "at least one" of a list of items refers to any combination of those items, including single members. For example, "at least one of a, b, or c" is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc or any other order of a, b, and c).

[0200] Unless explicitly stated, any element, action or instruction used herein should not be interpreted as critical or essential. In addition, as used herein, "one" is intended to include one or more items and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items, etc.), and can be used interchangeably with "one or more". If only one item is intended, the phrase "only one item" or similar language is used. In addition, as used herein, terms such as "having" are intended to be open terms. In addition, unless otherwise explicitly stated, the phrase "based on" is intended to mean "based at least in part on".

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: one or more memories; as well as One or more processors, coupled to the one or more memories, the one or more processors configured to cause the UE to: sending a first random access channel (RACH) message to a network entity; as well as In the absence of downlink control information, monitoring a set of resource candidates based at least in part on the first RACH message for a second RACH message.

2. The device according to claim 1, wherein: To monitor the second RACH message, the one or more processors are configured to cause the UE to: The resource candidate set is monitored for the second RACH message based at least in part on one or more of a RACH type, a subset of a preamble sequence of the first RACH message, a RACH opportunity, or a subset of RACH opportunities.

3. The device according to claim 1, wherein: The resource candidate set is located in a physical downlink shared channel.

4. The device according to claim 1, wherein: The second RACH message is scheduled via the remaining minimum system information message or another system information message.

5. The device according to claim 1, wherein: The one or more processors are further configured to cause the UE to: Information identifying the candidate set of resources is received from the network entity.

6. An apparatus for wireless communication at a network entity, comprising: one or more memories; as well as One or more processors, coupled to the one or more memories, the one or more processors configured to cause the network entity to: receiving a first random access channel (RACH) message from a user equipment (UE); as well as Based at least in part on the first RACH message, a second RACH message is sent in a set of resource candidates scheduled in the absence of downlink control information.

7. The device according to claim 6, in, To send the second RACH message, the one or more processors are further configured to cause the network entity to: sending the second RACH message based at least in part on information in the first RACH message, and The information indicates one or more of a RACH message type, a preamble sequence subset of a first RACH message, a RACH opportunity, or a subset of a RACH opportunity.

8. The device according to claim 6, wherein: The resource candidate set is located in a physical downlink shared channel.

9. The device according to claim 6, wherein: The one or more processors are further configured to cause the network entity to: The second RACH message is scheduled via the remaining minimum system information message or another system information message.

10. The device according to claim 6, wherein: To send the second RACH message, the one or more processors are configured to cause the network entity to: Based at least in part on determining that a signal measurement satisfies a threshold, sending the second RACH message in the set of resource candidates.

Images