Resource for repeated joint channel estimation

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may send an indication of UE capabilities for the UE to maintain uplink continuity for Msg3 repetition. The UE may receive a configuration specifying resources indicating that Msg3 will be expected to repeat. The UE may transmit a physical random access channel (PRACH) message in a resource. These resources may include preamble resources dedicated to joint channel estimation for Msg3 repetition or dedicated to joint channel estimation for PRACH repetition. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Patent Application No. 17 / 810,061, filed on June 30, 2022, entitled “RESOURCES FOR JOINT CHANNEL ESTIMATION OF REPETITIONS” and assigned to the assignee of this application. The disclosure of the prior application is considered a part of this patent application and is incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for indicating resources for repeated joint channel estimation. Background Art

[0004] 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).

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

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

[0007] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include sending an indication of a UE capability of the UE to maintain uplink continuity of Msg3 repetitions. The method may include receiving a configuration specifying resources indicating that Msg3 repetitions are expected. The method may include sending a physical random access channel (PRACH) message in the resources.

[0008] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include receiving a PRACH message in a resource indicating that a Msg3 repetition is expected. The method may include receiving the Msg3 repetition. The method may include performing joint channel estimation based on the Msg3 repetition.

[0009] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include sending a capability indication of the UE's capability to maintain uplink continuity for contention-free random access (CFRA) uplink channel repetitions for joint channel estimation. The method may include sending the CFRA uplink channel repetitions.

[0010] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include receiving an indication of a UE capability to maintain uplink continuity of a CFRA uplink channel repetition for joint channel estimation. The method may include receiving the CFRA repetition. The method may include performing joint channel estimation based on the CFRA uplink repetition.

[0011] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory, one or more processors coupled to the memory, and instructions stored in the memory and executable by the one or more processors. These instructions may be executed by one or more processors to enable the UE to send an indication of the UE's ability to maintain uplink continuity of Msg3 repetitions. These instructions may be executed by one or more processors to enable the UE to receive a configuration of resources specifying an indication that Msg3 repetitions are expected. These instructions may be executed by one or more processors to enable PRACH messages to be sent in these resources.

[0012] Some aspects described herein relate to a network entity for wireless communication. The network entity may include a memory, one or more processors coupled to the memory, and instructions stored in the memory and executable by the one or more processors. These instructions may be executable by one or more processors to cause the network entity to receive a PRACH message in a resource indicating that Msg3 repetitions are expected. These instructions may be executable by one or more processors to cause the network entity to receive Msg3 repetitions. These instructions may be executable by one or more processors to cause the network entity to perform joint channel estimation based on Msg3 repetitions.

[0013] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory, one or more processors coupled to the memory, and instructions stored in the memory and executable by the one or more processors. These instructions may be executable by the one or more processors to cause the UE to send a capability indication of the UE's capability to maintain uplink continuity of CFRA uplink channel repetitions for joint channel estimation. These instructions may be executable by the one or more processors to cause the UE to send CFRA uplink channel repetitions.

[0014] Some aspects described herein relate to a network entity for wireless communication. The network entity may include a memory, one or more processors coupled to the memory, and instructions stored in the memory and executable by the one or more processors. These instructions may be executed by one or more processors to enable the network entity to receive an indication of the UE's ability to maintain uplink continuity of CFRA uplink channel repetitions for joint channel estimation. These instructions may be executed by one or more processors to enable the network entity to receive CFRA repetitions. These instructions may be executed by one or more processors to enable the network entity to perform joint channel estimation based on CFRA uplink repetitions.

[0015] Some aspects described herein relate to a non-transitory computer-readable medium storing one or more instructions for wireless communication performed by a UE. The one or more instructions, when executed by one or more processors of the UE, may cause the UE to send an indication of the UE's ability to maintain uplink continuity of Msg3 repetitions. The one or more instructions, when executed by one or more processors of the UE, may cause the UE to receive a configuration specifying resources indicating that Msg3 repetitions are expected. The one or more instructions, when executed by one or more processors of the UE, may cause the UE to send a PRACH message in these resources.

[0016] Some aspects described herein relate to a non-transitory computer-readable medium storing one or more instructions for wireless communication by a network entity. The one or more instructions, when executed by one or more processors of the network entity, may cause the network entity to receive a PRACH message in a resource indicating that Msg3 repetitions are expected. The one or more instructions, when executed by one or more processors of the network entity, may cause the network entity to receive Msg3 repetitions. The one or more instructions, when executed by one or more processors of the network entity, may cause the network entity to perform joint channel estimation based on Msg3 repetitions.

[0017] Some aspects described herein relate to a non-transitory computer-readable medium storing one or more instructions for wireless communication by a UE. The one or more instructions, when executed by one or more processors of the UE, may cause the UE to send a capability indication of the UE's capability to maintain uplink continuity of CFRA uplink channel repetition for joint channel estimation. The one or more instructions, when executed by one or more processors of the UE, may cause the UE to send a CFRA uplink channel repetition.

[0018] Some aspects described herein relate to a non-transitory computer-readable medium storing one or more instructions for wireless communication by a network entity. The one or more instructions, when executed by one or more processors of the network entity, may cause the network entity to receive an indication of a UE capability for maintaining uplink continuity of a CFRA uplink channel repetition for joint channel estimation. The one or more instructions, when executed by one or more processors of the network entity, may cause the network entity to receive the CFRA repetition. The one or more instructions, when executed by one or more processors of the network entity, may cause the network entity to perform joint channel estimation based on the CFRA uplink repetition.

[0019] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending an indication of the apparatus's ability to maintain uplink continuity for Msg3 repetitions. The apparatus may include means for receiving a configuration specifying resources indicating that Msg3 repetitions are expected. The apparatus may include means for sending a PRACH message in the resources.

[0020] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a PRACH message in a resource indicating that Msg3 repetitions are expected. The apparatus may include means for receiving Msg3 repetitions. The apparatus may include means for performing joint channel estimation based on Msg3 repetitions.

[0021] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a capability indication of the apparatus's ability to maintain uplink continuity of CFRA uplink channel repetitions for joint channel estimation. The apparatus may include means for sending CFRA uplink channel repetitions.

[0022] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving an indication of a capability of a UE to maintain uplink continuity of a CFRA uplink channel repetition for joint channel estimation. The apparatus may include means for receiving the CFRA repetition. The apparatus may include means for performing joint channel estimation based on the CFRA uplink repetition.

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

[0024] The features and technical advantages of the examples according to the present disclosure have been outlined quite extensively above in order to better understand the subsequent specific embodiments. Additional features and advantages will be described below. The disclosed concepts and specific examples can be easily used as a basis for modifying or designing other structures for the same purpose of achieving the present disclosure. Such equivalent constructions do not depart from the scope of protection of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.

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

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

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

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

[0029] Figure 3 is a diagram illustrating an example of a decomposed base station according to the present disclosure.

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

[0031] Figure 5 is a diagram illustrating an example of Msg3 repetition according to the present disclosure.

[0032] Figure 6 is a diagram illustrating an example of channel estimation according to the present disclosure.

[0033] Figure 7 is a diagram illustrating an example of a field indicating an amount of Msg3 repetition according to the present disclosure.

[0034] Figure 8 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0035] Fig. 9 is a diagram illustrating an example process performed, for example, by a network entity according to the present disclosure.

[0036] Fig.10 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0037] Fig.11 is a diagram illustrating an example process performed, for example, by a network entity according to the present disclosure.

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

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

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

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

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

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

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

[0045] In some aspects, the term "base station" (e.g., base station 110) or "network entity" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, and / or one or more components thereof. For example, in some aspects, a "base station" or "network entity" may refer to a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network entity" may refer to a device configured to perform one or more functions, such as those described herein in conjunction with base station 110. In some aspects, the term "base station" or "network entity" may refer to a plurality of devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographical location or in different geographical locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network entity" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network entity" may refer to one or more virtual base stations and / or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network entity" may refer to one of the base station functions but not the other. In this way, a single device may include more than one base station.

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

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

[0048] The network controller 130 may be coupled to or in communication with a set of network entities and may provide coordination and control for these network entities. The network controller 130 may communicate with the base station 110 via a backhaul communication link. The network entities may communicate with each other directly or indirectly via a wireless or wired backhaul communication link.

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

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

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

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

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

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

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

[0056] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may send an indication of the UE's capability to maintain uplink continuity for Msg3 repetitions. The communication manager 140 may receive a configuration specifying resources indicating that Msg3 repetitions are expected and send a physical random access channel (PRACH) message in these resources.

[0057] In some aspects, the communication manager 140 may send a capability indication of the UE's capability to maintain uplink continuity for contention-free random access (CFRA) uplink channel repetitions for joint channel estimation, and send the CFRA uplink channel repetitions. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0058] In some aspects, a network entity (e.g., base station 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive a PRACH message in a resource indicating that Msg3 repetitions are expected; receive the Msg3 repetitions and perform joint channel estimation based on the Msg3 repetitions.

[0059] In some aspects, the communication manager 150 may receive an indication of the UE's capability to maintain uplink continuity of CFRA uplink channel repetitions for joint channel estimation; receive the CFRA repetitions and perform joint channel estimation based on the CFRA uplink repetitions. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0060] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 Different than described.

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

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

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

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

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

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

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

[0068] A controller / processor of a network entity (e.g., controller / processor 240 of base station 110), controller / processor 280 of UE 120, and / or Figure 2 Any other component of the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or the like may perform one or more techniques associated with indicating resources for joint channel estimation for random access channel duplication, as described in more detail elsewhere herein. Figure 2 Any other component of the Figure 8 The process of 800 Fig. 9 The process of 900 Fig.10 The process of 1000 Fig.11 1100 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network entities and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of a network entity and / or UE 120, may cause the one or more processors, UE 120, and / or network entity to perform or direct, for example, Figure 8 The process of 800 Fig. 9 The process of 900 Fig.10 The process of 1000 Fig.11 The process 1100 and / or other processes described herein may include operations. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0069] In some aspects, the UE 120 includes means for sending an indication of the UE's capability to maintain uplink continuity for Msg3 repetitions; means for receiving a configuration specifying resources indicating that Msg3 repetitions are expected; and / or means for sending a PRACH message in these resources. Means for the UE 120 to perform operations described herein may include, for example, one or more of the communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0070] In some aspects, the UE 120 includes means for sending a capability indication of the UE capability to maintain uplink continuity of CFRA uplink channel repetition for joint channel estimation; and / or means for sending CFRA uplink channel repetition.

[0071] In some aspects, a network entity (e.g., base station 110) includes means for receiving a PRACH message in a resource indicating that Msg3 repetitions are expected; means for receiving Msg3 repetitions; and / or means for performing joint channel estimation based on Msg3 repetitions. In some aspects, means for a network entity to perform operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0072] In some aspects, the network entity includes means for receiving an indication of a UE capability to maintain uplink continuity for CFRA uplink channel repetitions for joint channel estimation; means for receiving CFRA repetitions; and / or means for performing joint channel estimation based on CFRA uplink repetitions.

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

[0074] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 Different than described.

[0075] Figure 3 is a diagram illustrating an example of a decomposed base station 300 according to the present disclosure.

[0076] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station, or one or more units (or one or more components) performing base station functionality) can be implemented in an aggregated architecture or a decomposed architecture. For example, a BS (such as a Node B, an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) can be implemented as an aggregated base station (also called an independent BS or a monolithic BS) or a decomposed base station.

[0077] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).

[0078] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0079] The decomposed base station 300 architecture may include one or more CUs 310 that may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed base station units (such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via corresponding midhaul links, such as an F1 interface. The DU 330 may communicate with one or more RUs 340 via corresponding fronthaul links. Fronthaul links, midhaul links, and backhaul links may generally be referred to as "communication links." The RU 340 may communicate with a corresponding UE 120 via one or more RF access links. In some aspects, a UE 120 may be served simultaneously by multiple RUs 340. The DU 330 and the RU 340 may also be referred to as "O-RAN DU (O-DU)" and "O-RAN RU (O-RU)", respectively. The network entity may include a CU, DU, RU, or any combination of CU, DU, and RU. The network entity may include a decomposed base station or one or more components of a decomposed base station, such as a CU, DU, RU, or any combination of CU, DU, and RU. The network entity may also include one or more of a TRP, a relay station, a passive device, an intelligent reflective surface (IRS), or other components that may provide a network interface or service for a UE, a mobile station, a sensor / actuator, or other wireless device.

[0080] Each of these units (e.g., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO framework 305) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, the unit may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or send signals or both to one or more of the other units on a wireless transmission medium.

[0081] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 310. CU 310 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). CU 310 may be implemented to communicate with DU 330 as needed for network control and signaling.

[0082] DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RU 340. In some aspects, DU 330 may host one or more of the following depending at least in part on a functional split such as that defined by 3GPP: a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.). In some aspects, DU 330 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 330 or with control functions hosted by CU 310.

[0083] The lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, PRACH extraction and filtering, etc.), or both, based at least in part on a functional partitioning (such as a lower layer functional partitioning). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0084] The SMO framework 305 may be configured to support RAN deployment and configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-cloud) 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0085] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0086] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

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

[0088] Figure 4 is a diagram illustrating an example of a four-step random access procedure according to the present disclosure. Figure 4 As shown in , a network entity (eg, base station 110) and a UE 120 may communicate with each other to perform a four-step random access procedure.

[0089] As shown by reference numeral 405, the base station 110 may send, and the UE 120 may receive, one or more synchronization signal blocks (SSBs) and random access configuration information. In some aspects, the random access configuration information may be sent and / or indicated by system information (e.g., one or more system information blocks (SIBs)) and / or SSBs, such as for contention-based random access. Additionally or alternatively, the random access configuration information may be sent in an RRC message and / or a physical downlink control channel (PDCCH) command message that triggers a random access channel (RACH) procedure, such as for CFRA. The random access configuration information may include one or more parameters to be used in the random access procedure, such as one or more parameters for sending a random access message (RAM) and / or one or more parameters for receiving a random access response (RAR).

[0090] As shown by reference numeral 410, UE 120 may send a RAM, which may include a preamble (sometimes referred to as a random access preamble, a PRACH preamble, or a RAM preamble). The message including the preamble may be referred to as message 1, Msg1, msg1, MSG1, a first message, or an initial message in a four-step RACH process. The random access message may include a random access preamble identifier.

[0091] As shown by reference numeral 415, the base station 110 may send a RAR as a response to the preamble. The message including the RAR may be referred to as message 2, Msg2, msg2, MSG2, or a second message in the four-step RACH process. In some aspects, the RAR may indicate a detected random access preamble identifier (e.g., received from the UE 120 in Msg1). Additionally or alternatively, the RAR may indicate a resource allocation to be used by the UE 120 to send message 3 (Msg3).

[0092] In some aspects, as part of a second step of the four-step RACH process, the base station 110 may send a PDCCH communication for the RAR. The PDCCH communication may schedule a physical downlink shared channel (PDSCH) communication including the RAR. For example, the PDCCH communication may indicate a resource allocation for the PDSCH communication (e.g., an uplink grant for the next message, a timing advance, a temporary cell radio network temporary identifier (TC-RNTI)). Also as part of the second step of the four-step RACH process, the base station 110 may send a PDSCH communication for the RAR as scheduled by the PDCCH communication. The RAR may be included in a medium access control (MAC) protocol data unit (PDU) of the PDSCH communication.

[0093] As shown by reference numeral 420, UE 120 may send an RRC connection request message. The RRC connection request message may be referred to as message 3, Msg3, msg3, MSG3, or a third message of the four-step RACH procedure. In some aspects, the RRC connection request may include a UE identifier, uplink control information (UCI), and / or physical uplink shared channel (PUSCH) communications (e.g., RRC connection request, scheduling request, and / or buffer status).

[0094] As shown by reference numeral 425, the base station 110 may send an RRC connection setup message. The RRC connection setup message may be referred to as message 4, Msg4, msg4, MSG4, or a fourth message of the four-step RACH procedure. In some aspects, the RRC connection setup message may include a detected UE identifier, a timing advance value, and / or contention resolution information. As shown by reference numeral 430, if the UE 120 successfully receives the RRC connection setup message, the UE 120 may send a hybrid automatic repeat request (HARQ) acknowledgement (ACK).

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

[0096] Figure 5 are diagrams illustrating examples 500 and 502 of Msg3 repetition according to the present disclosure.

[0097] The transmission of Msg3 for the RACH process may become bottlenecked due to the traffic conditions on the PUSCH. In addition, the UE 120 may expect to successfully receive both the RAR for the initial transmission and the TC-RNTI scrambled downlink control information (DCI) for the retransmission, and there may be high PDCCH overhead. If Msg3 is not successfully received, retransmission may occur and increase the initial access delay. In order to successfully deliver the Msg3 for the initial transmission, the UE 120 may repeat the transmission of Msg3. This may increase the probability of successfully delivering Msg3. Msg3 repetition may also be used for retransmission.

[0098] Example 500 illustrates an initial transmission of Msg2 by a network entity (e.g., base station 110, gNB). Msg2 may be a DCI 1_0 format scrambled with a random access RNTI (RA-RNTI). After the RAR, UE 120 may send a Msg3 repetition for the initial transmission. UE 120 may start a contention resolution timer. If the contention resolution timer expires without positive feedback (or if negative feedback is received), UE 120 may determine that the initial transmission was unsuccessful and a retransmission is to occur. Example 502 illustrates that the network entity may send a DCI format 0_0 with a cyclic redundancy check (CRC) scrambled with a TC-RNTI. The DCI may provide an uplink grant or otherwise specify resources for retransmission. UE 120 may send a Msg3 repetition for retransmission. Msg3 repetition may be a type A PUSCH repetition that carries the same transport block on an available slot while applying the same symbol allocation (starting symbol and transmission duration) in each slot.

[0099] UE 120 may request Msg3 repetitions via a separate PRACH resource based on channel conditions, such as RSRP measurements satisfying a threshold (e.g., a minimum RSRP). For example, if the RSRP measurement is equal to or less than a threshold, the RSRP measurement may satisfy the threshold. If UE 120 requests Msg3 repetitions, the network entity may determine whether to schedule Msg3 repetitions. Msg3 repetitions may include multiple Msg3 repetitions, such as 1, 2, 3, 4, 7, 8, 12, or 16 Msg3 repetitions. In some aspects, UE 120 may request Msg3 repetitions using a separate preamble set or frequency resource set dedicated to requesting Msg3 repetitions.

[0100] The network entity may indicate the amount of Msg3 repetitions to be used by UE 120 for initial transmission. For example, the network entity may send a value of a time domain resource allocation (TDRA) field indicating the amount of Msg3 repetitions to be used for initial transmission. The TDRA field may generally specify the time or frequency resources allocated for uplink transmission, but the TDRA field may be reused to indicate the amount of Msg3 repetitions. The TDRA field may be a column in the TDRA table. Candidate values ​​for the repetition factor may be selected from 1, 2, 3, 4, 7, 8, 12, or 16. Alternatively, the network entity may use the MCS information field to indicate the amount of Msg3 repetitions for initial transmission. That is, the MCS information field may generally indicate the MCS used for encoding and decoding. However, the MCS information field may be reused to indicate the amount of Msg3 repetitions. For example, the two most significant bits (MSB) of the MCS information field may be used to select a repetition factor from a SIB1 configuration set having four candidate values.

[0101] However, UE 120 may not know that a specific field is being used to indicate the amount of Msg3 repetitions for initial transmission or for retransmission. If UE 120 does not know which field or how the network entity indicates the amount of msg repetitions, UE 120 may not be able to successfully deliver the initial transmission or retransmission. This may degrade communications or cause UE 120 to consume additional processing resources and signaling resources with retransmissions.

[0102] As indicated above, Figure 5 Some examples are provided. Other examples can be found in Figure 5 Different than described.

[0103] Figure 6 are diagrams illustrating examples 600 and 602 of channel estimation according to the present disclosure.

[0104] Example 600 shows three time slots of a transport block. A receiving UE (or receiving network entity) may perform channel estimation using the DMRS in each transport block. That is, channel estimation is performed separately for each time instance (e.g., time slot). Example 602 shows joint channel estimation using the DMRS of three transport blocks together. This may be referred to as "cross-time slot channel estimation", "DMRS bundling", or "joint channel estimation". Joint channel estimation may improve the accuracy of channel estimation because the estimation involves information across multiple time slots.

[0105] In some aspects, the network entity may utilize Msg3 repetitions to perform joint channel estimation. However, the ability of the network entity to perform joint channel estimation on Msg3 repetitions may depend on the UE capability to maintain uplink continuity (e.g., maintain phase continuity between Msg3 repetitions in different time slots). It is not yet specified how the UE 120 may indicate uplink continuity capability prior to Msg3 repetitions and how to provide the indication without consuming excessive overhead (signaling resources).

[0106] As indicated above, Figure 6 Some examples are provided. Other examples can be found in Figure 6 Different than described.

[0107] Figure 7 700 is a diagram illustrating an example of a field indicating the amount of Msg3 repetition according to the present disclosure. Figure 7 As shown, a base station (e.g., base station 110) and a UE (e.g., UE 120) may communicate with each other.

[0108] According to various aspects described herein, UE 720 may send an indication of UE capability of UE 720 for maintaining uplink (UL) continuity for Msg3 repetitions, as shown by reference numeral 725. The UE capability may indicate that UE 720 can maintain uplink continuity for Msg3 repetitions. The UE capability may be associated with a phase difference below a difference threshold or an average phase difference below a difference threshold between Msg3 repetitions. The UE capability may indicate that UE 720 cannot maintain uplink continuity for Msg3 repetitions. In some aspects, UE 720 may send an indication of UE capability of UE 720 for maintaining uplink continuity for PRACH repetitions or CFRA PUSCH repetitions.

[0109] UE 720 may receive a configuration specifying resources that may be used to indicate to network entity 710 that Msg3 repetitions are expected, as shown by reference numeral 730. The resources may include frequency resources for Msg3 repetitions separated from other frequency resources in an active bandwidth part (BWP). The resources may include preamble resources dedicated to joint channel estimation for Msg3 repetitions. For example, network entity 710 may configure separate frequency resources and / or a combination of preamble resources and PRACH repetitions to indicate Msg3 repetitions to UE 720.

[0110] As shown by reference numeral 735, UE 720 may send a PRACH message in a designated resource. The PRACH message may be a PRACH preamble. The PRACH message may include a PRACH repetition. The sending of the PRACH message in the designated resource may indicate a Msg3 repetition or a PRACH repetition. The sending of the PRACH message in the designated resource may indicate uplink continuity for the Msg3 repetition or for the PRACH repetition. For example, the designated resource may include a preamble resource dedicated to a joint channel estimation for the Msg3 repetition or a preamble resource dedicated to a joint channel estimation for the PRACH repetition. The sending of the PRACH message in the preamble resource may indicate uplink continuity for the Msg3 repetition or for the PRACH repetition. The network entity 710 may then anticipate and prepare for phase continuity across the Msg3 repetition or the PRACH repetition. For example, using the preamble resource may be efficient because otherwise the PRACH transmission may have to further divide the PRACH resources or the RACH opportunity.

[0111] As shown by reference numeral 740, UE 720 may send Msg3 repetitions. As shown by reference numeral 745, UE 720 may maintain uplink continuity during Msg3 repetitions based at least in part on UE capabilities. As shown by reference numeral 750, network entity 710 may perform joint channel estimation based on Msg3 repetitions. As shown by reference numeral 755, network entity 710 may communicate (send and / or receive communications) with UE 720 based at least in part on the results of the joint channel estimation (e.g., the joint channel estimation).

[0112] In some aspects, the combination of preamble resource selection (e.g., from a preconfigured subset) and PRACH repetition (for Msg3 repetition) may be used independently of any triggering criteria for PRACH repetition. In some aspects, the configuration may include an indication that the UE 720 will maintain uplink continuity for Msg3 repetition, PRACH repetition, or neither Msg3 repetition nor PRACH repetition, and the UE 720 may maintain or not maintain uplink continuity based on the indication, as shown by reference numeral 745.

[0113] In some aspects, the configuration may indicate a configured time domain window associated with Msg3 repetition, and the UE 720 may maintain uplink continuity during the configured time domain window. The time domain window may affect the pattern of inter-slot frequency hopping for Msg3 repetition. Therefore, the UE 720 may suppress frequency hopping during the configured time domain window. The network entity 710 may configure the time domain window to the UE 720 via an RRC message. The time domain window may be associated with a separate frequency resource and / or a separate combination of preamble resources and PRACH repetition for Msg3 repetition.

[0114] In some aspects, the network entity 710 may apply joint channel estimation to the reception of repetitions of CFRA PUSCH communications based at least in part on a prior configuration (by the network entity 710) and / or a capability indication by the UE 720. This may apply to the reception of PRACH repetitions in CFRA (in the case of PRACH repetitions). The application of joint channel estimation to the repetitions of CFRA PUSCH communications may be based at least in part on a prior configuration of a time domain window and / or the enabling of joint channel estimation to the repetitions of regular (non-random access) PUSCH communications. In some aspects, the time domain window for the joint channel estimation of the repetitions of CFRA PUSCH communications may be the same as the time domain window for regular PUSCH communications. In some aspects, the time domain window for the joint channel estimation of the repetitions of CFRA PUSCH communications may be different from the time domain window for regular PUSCH communications. The size of the time domain window for the joint channel estimation may be based at least in part on the time domain window for regular PUSCH communications. For example, the time domain window for joint channel estimation may be equal to the minimum of the time domain window for conventional PUSCH communication and a specified value or a preconfigured window size. The process for configuring UE 720 to maintain uplink continuity in association with repeated joint channel estimation of CFRA PUSCH communication may be similar to the process described for Msg3 repetition in example 700. By indicating the UE capability for maintaining uplink continuity for random access procedure repetitions (such as Msg3 repetitions) in designated resources, the network entity 710 may perform joint channel estimation for random access procedure repetitions and improve the accuracy of channel estimation without significantly increasing signaling overhead. Accurate channel estimation improves communication and saves processing resources and signaling resources.

[0115] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 Different than described.

[0116] Figure 8 800 is a diagram illustrating an example process 800 performed, for example, by a UE according to the present disclosure. Example process 800 is an example in which a UE (e.g., UE 120, UE 720) performs operations associated with using resources to indicate a UE capability to maintain uplink continuity of random access channel repetitions for joint channel estimation.

[0117] like Figure 8 As shown, in some aspects, process 800 may include sending an indication of the UE's capability to maintain Msg3 repetition (block 810). For example, a UE (e.g., using Fig.12 The communications manager 1208 and / or sending component 1204 depicted in FIG. 1 may send an indication of the UE's capability to maintain uplink continuity for Msg3 repetitions, as described above.

[0118] like Figure 8 As further shown, in some aspects, process 800 may include receiving a configuration specifying resources indicating that Msg3 repetitions are expected (block 820). Fig.12 The communication manager 1208 and / or receiving component 1202 depicted in FIG. 1204 may receive a configuration specifying resources indicating that Msg3 repetitions are expected, as described above.

[0119] like Figure 8 As further shown, in some aspects, process 800 may include sending a PRACH message in a resource (block 830). For example, a UE (e.g., using Fig.12 The communication manager 1208 and / or the sending component 1204 depicted in can send a PRACH message in the resource as described above.

[0120] 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.

[0121] In a first aspect, process 800 includes performing Msg3 repetition.

[0122] In a second aspect, alone or in combination with the first aspect, the resources include frequency resources in an active BWP separate from other frequency resources.

[0123] In a third aspect, alone or in combination with one or more of the first and second aspects, the resources include preamble resources dedicated to joint channel estimation of Msg3 repetitions or dedicated to joint channel estimation of PRACH repetitions.

[0124] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 800 includes using PRACH repetitions in combination with preamble resources to indicate Msg3 repetitions.

[0125] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the configuration includes an indication that the UE will maintain uplink continuity for Msg3 repetition, PRACH repetition, or neither Msg3 repetition nor PRACH repetition, and process 800 includes maintaining uplink continuity based on the indication.

[0126] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, a configuration time domain window indicating association with Msg3 repetition is configured, and process 800 includes maintaining uplink continuity during the configured time domain window.

[0127] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, process 800 includes suppressing frequency hopping during configuration of the time domain window.

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

[0129] Fig. 9 900 is a diagram illustrating an example process 900 performed, for example, by a network entity according to the present disclosure. Example process 900 is an example in which a network entity (e.g., base station 110, network entity 710) performs operations associated with configuring resources for indicating a UE capability to maintain uplink continuity of random access channel repetitions for joint channel estimation.

[0130] like Fig. 9 As shown, in some aspects, process 900 may include receiving a PRACH message in a resource indicating that Msg3 repetitions are expected (block 910). For example, a network entity (e.g., using Fig.13 The communication manager 1308 and / or receiving component 1302 depicted in FIG. 1 may receive a PRACH message in a resource indicating that Msg3 repetitions are expected, as described above.

[0131] like Fig. 9 As further shown, in some aspects, process 900 may include receiving a Msg3 repetition (block 920). For example, a network entity (e.g., using Fig.13 The communication manager 1308 and / or receiving component 1302 depicted in FIG. 10A may receive a Msg3 repetition as described above.

[0132] like Fig. 9 As further shown, in some aspects, process 900 may include performing joint channel estimation based on Msg3 repetitions (block 930). Fig.13 The communication manager 1308 and / or channel estimation component 1310 depicted in FIG. 1 may perform joint channel estimation based on Msg3 repetitions, as described above.

[0133] Process 900 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.

[0134] In a first aspect, process 900 includes receiving an indication of a UE capability for maintaining uplink continuity of Msg3 repetitions for joint channel estimation, and sending a configuration of designated resources based at least in part on the UE capability.

[0135] In a second aspect, alone or in combination with the first aspect, the resources include frequency resources in the active bandwidth portion separate from other frequency resources.

[0136] In a third aspect, alone or in combination with one or more of the first and second aspects, process 900 includes determining that Msg3 repetition is to be expected based on usage of frequency resources in combination with PRACH repetition.

[0137] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the resources include preamble resources dedicated to joint channel estimation of Msg3 repetition.

[0138] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 900 includes receiving a PRACH repetition and performing a joint channel estimation based at least in part on the PRACH repetition.

[0139] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, process 900 includes sending a configuration indicating a configured time domain window associated with Msg3 repetition, and performing joint channel estimation includes performing joint channel estimation only within the configured time domain window.

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

[0141] Fig.10 1 is a diagram illustrating an example process 1000 performed, for example, by a UE according to the present disclosure. Example process 1000 is an example in which a UE (e.g., UE 120, UE 720) performs operations associated with using resources to indicate a UE capability to maintain uplink continuity of random access channel repetitions for joint channel estimation.

[0142] like Fig.10 As shown, in some aspects, process 1000 may include sending a capability indication of the UE's capability to maintain uplink continuity of CFRA uplink channel repetition for joint channel estimation (block 1010). For example, a UE (e.g., using Fig.12The communication manager 1208 and / or the sending component 1204 depicted in FIG. 1204 may send a capability indication to the UE of the UE's capability to maintain uplink continuity for CFRA uplink channel repetition for joint channel estimation, as described above.

[0143] like Fig.10 As further shown, in some aspects, process 1000 may include sending a CFRA uplink channel repetition (block 1020). For example, a UE (e.g., using Fig.12 The communications manager 1208 and / or the sending component 1204 depicted in FIG. 1204 may send a CFRA uplink channel repetition as described above.

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

[0145] In a first aspect, process 1000 includes receiving a configuration of a preamble for joint channel estimation dedicated to CFRA uplink channel repetition.

[0146] In a second aspect, alone or in combination with the first aspect, the configuration includes a continuity indication indicating that the UE is to maintain uplink continuity for CFRA uplink channel repetition or PRACH repetition, and the process 1000 includes maintaining uplink continuity based on the continuity indication.

[0147] In a third aspect, alone or in combination with one or more of the first and second aspects, process 1000 includes maintaining uplink continuity during a time domain window.

[0148] In a fourth aspect, alone or in combination with one or more of the first to third aspects, a time domain window for CFRA uplink repetitions matches a time domain window for other uplink channel communications.

[0149] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, a time domain window for CFRA uplink repetitions does not match a time domain window for other uplink channel communications.

[0150] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the size of the time domain window used for CFRA uplink repetition matches the smaller of the size of the time domain window used for other uplink channel communications or the configuration time domain window size.

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

[0152] Fig.11 1 is a diagram illustrating an example process 1100 performed, for example, by a network entity according to the present disclosure. Example process 1100 is an example in which a network entity (e.g., base station 110, network entity 710) performs operations associated with configuring resources for indicating a UE capability to maintain uplink continuity of random access channel repetitions for joint channel estimation.

[0153] like Fig.11 As shown, in some aspects, process 1100 may include receiving an indication of a UE capability for maintaining uplink continuity of a CFRA uplink channel repetition for joint channel estimation (block 1110). For example, a network entity (e.g., using Fig.13 The communications manager 1308 and / or receiving component 1302 depicted in FIG. 1 may receive an indication of the UE's capability to maintain uplink continuity for CFRA uplink channel repetition for joint channel estimation, as described above.

[0154] like Fig.11 As further shown, in some aspects, process 1100 may include receiving a CFRA repetition (block 1120). For example, a network entity (e.g., using Fig.13 The communication manager 1308 and / or receiving component 1302 depicted in FIG. 1 may receive CFRA repetitions as described above.

[0155] like Fig.11 As further shown, in some aspects, process 1100 may include performing joint channel estimation based on CFRA uplink repetitions (block 1130). For example, a network entity (e.g., using Fig.13 The communication manager 1308 and / or channel estimation component 1310 depicted in FIG. 1 may perform joint channel estimation based on CFRA uplink repetitions, as described above.

[0156] Process 1100 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.

[0157] In a first aspect, performing joint channel estimation includes performing joint channel estimation further based on a configuration for CFRA uplink channel repetition.

[0158] In a second aspect, alone or in combination with the first aspect, the CFRA uplink repetition comprises a PRACH repetition.

[0159] In a third aspect, alone or in combination with one or more of the first and second aspects, process 1100 includes sending a configuration indicating a time domain window for CFRA uplink repetition, and performing joint channel estimation includes performing joint channel estimation only during the time domain window.

[0160] In a fourth aspect, alone or in combination with one or more of the first to third aspects, a time domain window for CFRA uplink repetitions matches a time domain window for other uplink channel communications.

[0161] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, a time domain window for CFRA uplink repetitions does not match a time domain window for other uplink channel communications.

[0162] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the size of the time domain window used for CFRA uplink repetition matches the smaller of the size of the time domain window used for other uplink channel communications or the configuration time domain window size.

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

[0164] Fig.12 is a diagram of an example apparatus 1200 for wireless communication according to the present disclosure. Apparatus 1200 may be a UE (e.g., UE 120, UE 720), or a UE may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202 and a sending component 1204, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using receiving component 1202 and sending component 1204. As further shown, apparatus 1200 may include a communication manager 1208. Communication manager 1208 may control and / or otherwise manage one or more operations of receiving component 1202 and / or sending component 1204. In some aspects, communication manager 1208 may include a communication manager 1208 in conjunction with Figure 2 The communication manager 1208 may be or be similar to one or more antennas, modems, controllers / processors, memories, or combinations thereof of the UE. Figure 1 and Figure 2For example, in some aspects, the communication manager 1208 can be configured to perform one or more of the functions described as being performed by the communication manager 140. In some aspects, the communication manager 1208 can include a receiving component 1202 and / or a sending component 1204. The communication manager 1208 can include an indicating component 1210, among others.

[0165] In some aspects, the apparatus 1200 may be configured to perform Figures 1 to 7 Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as Figure 8 The process of 800 Fig.10 In some aspects, Fig.12 The device 1200 and / or one or more components shown may include a combination of Figure 2 One or more components of the UE. Additionally or alternatively, Fig.12 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

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

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

[0168] In some aspects, transmitting component 1204 can transmit an indication of UE capability for maintaining uplink continuity of Msg3 repetitions. Receiving component 1202 can receive a configuration specifying resources indicating that Msg3 repetitions are expected. Transmitting component 1204 can transmit a PRACH message in the resources.

[0169] The transmitting component 1204 can transmit the Msg3 repetitions. The indicating component 1210 can indicate the Msg3 repetitions using PRACH repetitions in combination with preamble resources. The transmitting component 1204 can suppress frequency hopping during the configured time domain window.

[0170] In some aspects, transmitting component 1204 may transmit a capability indication of the UE's capability to maintain uplink continuity of CFRA uplink channel repetitions for joint channel estimation.Transmitting component 1204 may transmit the CFRA uplink channel repetitions.

[0171] Receiving component 1202 can receive configuration of a preamble for joint channel estimation dedicated to CFRA uplink channel repetition. Transmitting component 1204 can maintain uplink continuity during a time domain window.

[0172] Fig.12 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.12 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.12 Two or more components shown may be implemented in a single component, or Fig.12 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.12 The component set (one or more components) shown may be described as being executable by Fig.12Another component shown may be a collection of components that perform one or more functions.

[0173] Fig.13 is a diagram of an example apparatus 1300 for wireless communication according to the present disclosure. Apparatus 1300 may be a network entity (e.g., base station 110, network entity 710), or a network entity may include apparatus 1300. In some aspects, apparatus 1300 includes a receiving component 1302 and a sending component 1304, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1300 may communicate with another apparatus 1306 (such as a UE, a base station, or another wireless communication device) using receiving component 1302 and sending component 1304. As further shown, apparatus 1300 may include a communication manager 1308. Communication manager 1308 may control and / or otherwise manage one or more operations of receiving component 1302 and / or sending component 1304. In some aspects, communication manager 1308 may include a communication manager 1308 in conjunction with Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the network entities described. The communication manager 1308 may be or be similar to Figure 1 and Figure 2 For example, in some aspects, the communication manager 1308 may be configured to perform one or more of the functions described as being performed by the communication manager 150. In some aspects, the communication manager 1308 may include a receiving component 1302 and / or a sending component 1304. The communication manager 1308 may include a channel estimation component 1310, among other things.

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

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

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

[0177] In some aspects, receiving component 1302 may receive a PRACH message in a resource indicating that Msg3 repetitions are expected. Receiving component 1302 may receive the Msg3 repetitions. Channel estimating component 1310 may perform joint channel estimation based on Msg3.

[0178] In some aspects, receiving component 1302 may receive an indication of UE capabilities for maintaining uplink continuity of Msg3 repetitions for joint channel estimation.Sending component 1304 may send a configuration of designated resources based at least in part on the UE capability information.

[0179] Channel estimation component 1310 can determine that Msg3 repetitions are to be expected based on the use of frequency resources in combination with PRACH repetitions. Receiving component 1302 can receive the PRACH repetitions. Channel estimation component 1310 can perform joint channel estimation based on the PRACH.

[0180] The transmitting component 1304 can transmit a configuration indicating a configured time domain window associated with the Msg3 repetition, and the channel estimating component 1310 can perform joint channel estimation only within the configured time domain window.

[0181] Receiving component 1302 can receive an indication of UE capability to maintain uplink continuity of CFRA uplink channel repetitions for joint channel estimation. Receiving component 1302 can receive CFRA repetitions. Channel estimation component 1310 can perform joint channel estimation based on the CFRA uplink repetitions.

[0182] Transmitting component 1304 can transmit a configuration indicating a time domain window for CFRA uplink repetition, and channel estimation component 1310 can perform joint channel estimation only during the time domain window.

[0183] Fig.13 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.13 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.13 Two or more components shown may be implemented in a single component, or Fig.13 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.13 The component set (one or more components) shown may be described as being executable by Fig.13 Another component shown may be a collection of components that perform one or more functions.

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

[0185] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: sending an indication of a UE capability of the UE for maintaining uplink continuity of Msg3 repetitions; receiving a configuration specifying resources indicating that Msg3 repetitions are expected; and sending a physical random access channel (PRACH) message in the resources.

[0186] Aspect 2: The method according to Aspect 1 further includes: sending the Msg3 repetition.

[0187] Aspect 3: The method according to aspect 1 or 2, wherein the resource comprises a frequency resource in an active bandwidth portion that is separated from other frequency resources.

[0188] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the resources include preamble resources dedicated to joint channel estimation of Msg3 repetition or dedicated to joint channel estimation of PRACH repetition.

[0189] Aspect 5: The method according to aspect 4 further includes: using PRACH repetition in combination with the preamble resource to indicate Msg3 repetition.

[0190] Aspect 6: A method according to any one of Aspects 1 to 5, wherein the configuration includes an indication that the UE will maintain uplink continuity for Msg3 repetition, PRACH repetition, or neither Msg3 repetition nor PRACH repetition, and wherein the method includes maintaining uplink continuity based on the indication.

[0191] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the configuration indicates a configured time domain window associated with Msg3 repetition, and wherein the method further comprises maintaining uplink continuity during the configured time domain window.

[0192] Aspect 8: The method according to Aspect 7 further includes: suppressing frequency hopping during the configuration time domain window.

[0193] Aspect 9: A method of wireless communication performed by a network entity, comprising: receiving a physical random access channel (PRACH) message in a resource indicating that a Msg3 repetition is expected; receiving the Msg3 repetition; and performing joint channel estimation based on the Msg3 repetition.

[0194] Aspect 10: The method according to Aspect 9 also includes: receiving an indication of a user equipment (UE) capability for maintaining uplink continuity of the Msg3 repetition to perform the joint channel estimation; and sending a configuration specifying the resources based at least in part on the UE capability.

[0195] Aspect 11: The method of aspect or 109, wherein the resources comprise frequency resources in an active bandwidth portion separate from other frequency resources.

[0196] Aspect 12: The method according to aspect 11 further comprises: determining that Msg3 repetition is expected based on using the frequency resources in combination with PRACH repetition.

[0197] Aspect 13: The method according to any one of Aspects 9 to 12, wherein the resources include preamble resources dedicated to joint channel estimation of Msg3 repetition.

[0198] Aspect 14: The method according to any one of aspects 9 to 13 further includes: receiving PRACH repetitions; and performing joint channel estimation based on the PRACH repetitions.

[0199] Aspect 15: The method according to any one of Aspects 9 to 14 further includes: sending a configuration indicating a configured time domain window associated with Msg3 repetition, and wherein performing joint channel estimation includes performing joint channel estimation only within the configured time domain window.

[0200] Aspect 16: A method of wireless communication performed by a user equipment (UE), comprising: sending a capability indication of the UE's ability to maintain uplink continuity for contention-free random access (CFRA) uplink channel repetitions for joint channel estimation; and sending the CFRA uplink channel repetitions.

[0201] Aspect 17: The method according to aspect 16 further comprises: receiving a configuration of a preamble code for joint channel estimation dedicated to CFRA uplink channel repetition.

[0202] Aspect 18: A method according to Aspect 17, wherein the configuration includes a continuity indication indicating that the UE will maintain uplink continuity for CFRA uplink channel repetition or physical random access channel (PRACH) repetition, and wherein the method includes maintaining uplink continuity based on the continuity indication.

[0203] Aspect 19: The method according to any one of aspects 16 to 18 further includes: receiving a configuration indicating a time domain window for CFRA uplink repetition, and wherein the method further includes maintaining uplink continuity during the time domain window.

[0204] Aspect 20: The method according to any one of aspects 16 to 19, wherein the time domain window used for CFRA uplink repetition matches the time domain window used for other uplink channel communications.

[0205] Aspect 21: The method according to any one of aspects 16 to 19, wherein the time domain window used for CFRA uplink repetition does not match the time domain window used for other uplink channel communications.

[0206] Aspect 22: The method according to aspect 19, wherein the size of the time domain window used for CFRA uplink repetition matches the smaller of the size of the time domain window used for other uplink channel communications or the configuration time domain window size.

[0207] Aspect 23: A method of wireless communication performed by a network entity, comprising: receiving an indication of a user equipment (UE) capability to maintain uplink continuity for contention-free random access (CFRA) uplink channel repetitions for joint channel estimation; receiving the CFRA repetitions; and performing joint channel estimation based on the CFRA uplink repetitions.

[0208] Aspect 24: The method according to aspect 23, wherein performing joint channel estimation comprises: performing joint channel estimation further based on the configuration for the CFRA uplink channel repetition.

[0209] Aspect 25: The method according to aspect 23 or 24, wherein the CFRA uplink repetition includes a physical random access channel (PRACH) repetition.

[0210] Aspect 26: The method according to any one of Aspects 23 to 25 further comprises: sending a configuration indicating a time domain window for CFRA uplink repetition, and wherein performing joint channel estimation comprises performing joint channel estimation only during the time domain window.

[0211] Aspect 27: The method according to any one of aspects 23 to 26, wherein the time domain window used for CFRA uplink repetition matches the time domain window used for other uplink channel communications.

[0212] Aspect 28: The method according to any one of aspects 23 to 26, wherein the time domain window used for CFRA uplink repetition does not match the time domain window used for other uplink channel communications.

[0213] Aspect 29: A method according to any one of aspects 23 to 28, wherein the size of the time domain window used for CFRA uplink repetition matches the smaller of the size of the time domain window used for other uplink channel communications or the configuration time domain window size.

[0214] Aspect 30: 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 to cause the apparatus to perform one or more of the methods described in Aspects 1 to 29.

[0215] Aspect 31: A device for wireless communication, comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the memory comprising instructions, the instructions being executable by the one or more processors to cause the device to perform one or more of the methods described in Aspects 1 to 29.

[0216] Aspect 32: A device for wireless communication, comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 29.

[0217] Aspect 33: An apparatus for wireless communication, comprising: at least one device for performing the method according to one or more of aspects 1 to 29.

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

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

[0220] 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.

[0221] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

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

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

[0224] Any element, action or instruction used herein should not be interpreted as key or necessary unless explicitly stated. Moreover, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms will be used. Moreover, as used herein, the terms "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to represent "based at least in part on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, comprising: Memory; and One or more processors, the one or more processors being coupled to the memory, the memory comprising instructions executable by the one or more processors to cause the UE to: sending an indication of the UE capability of the UE for maintaining uplink continuity of Msg3 repetitions; receiving a configuration specifying a resource indicating that Msg3 repetitions are to be expected; and A physical random access channel (PRACH) message is sent in the resource.

2. The UE according to claim 1, wherein the memory further comprises instructions executable by the one or more processors to enable the UE to send the Msg3 repetition.

3. The UE of claim 1, wherein the resources comprise frequency resources in an active bandwidth portion separated from other frequency resources.

4. The UE according to claim 1, wherein the resources include preamble resources dedicated to joint channel estimation of Msg3 repetition or dedicated to joint channel estimation of PRACH repetition.

5. The UE of claim 4, wherein the memory further comprises instructions executable by the one or more processors to cause the UE to indicate Msg3 repetition using PRACH repetition in combination with the preamble resources.

6. The UE of claim 1, wherein the configuration includes an indication that the UE will maintain uplink continuity for Msg3 repetition, PRACH repetition, or neither Msg3 repetition nor PRACH repetition, and wherein the memory also includes instructions executable by the one or more processors to enable the UE to maintain uplink continuity based on the indication.

7. The UE of claim 1, wherein the configuration indicates a configured time domain window associated with Msg3 repetition, and wherein the memory further comprises instructions executable by the one or more processors to enable the UE to maintain uplink continuity during the configured time domain window.

8. The UE of claim 7, wherein the memory further comprises instructions executable by the one or more processors to cause the UE to refrain from frequency hopping during the configured time domain window.

9. A network entity for wireless communication, comprising: Memory; and One or more processors, the one or more processors coupled to the memory, the memory comprising instructions executable by the one or more processors to cause the network entity to: receiving a physical random access channel (PRACH) message in a resource indicating that Msg3 repetitions are expected; Receive Msg3 repetition; and Joint channel estimation is performed based on the Msg3 repetition.

10. The network entity of claim 9, wherein the memory further comprises instructions executable by the one or more processors to cause the network entity to: receiving an indication of a user equipment (UE) capability for maintaining uplink continuity of the Msg3 repetitions for the joint channel estimation; and A configuration specifying the resources is sent based at least in part on the UE capabilities.

11. The network entity of claim 9, wherein the resources comprise frequency resources separate from other frequency resources in an active bandwidth portion.

12. The network entity of claim 11, wherein the memory further comprises instructions executable by the one or more processors to cause the network entity to determine that Msg3 repetitions are to be expected based on using the frequency resources in combination with PRACH repetitions.

13. The network entity of claim 9, wherein the resources include preamble resources dedicated to joint channel estimation of Msg3 repetition.

14. The network entity of claim 9, wherein the memory further comprises instructions executable by the one or more processors to cause the network entity to: receiving PRACH repetitions; and Joint channel estimation is performed based on the PRACH repetitions.

15. The network entity of claim 9, wherein the memory further comprises instructions executable by the one or more processors to cause the network entity to send an instruction indicating a configuration of a configured time domain window associated with Msg3 repetition, and wherein the memory further comprises instructions executable by the one or more processors to cause the network entity to perform joint channel estimation only within the configured time domain window.

16. A user equipment (UE) for wireless communication, comprising: Memory; and One or more processors, the one or more processors being coupled to the memory, the memory comprising instructions executable by the one or more processors to cause the UE to: sending a capability indication of the UE capability to maintain uplink continuity for contention-free random access (CFRA) uplink channel repetition for joint channel estimation; as well as The CFRA uplink channel is sent repeatedly.

17. The UE of claim 16, wherein the memory further comprises instructions executable by the one or more processors to cause the UE to receive configuration of a preamble for joint channel estimation dedicated to CFRA uplink channel repetition.

18. A UE according to claim 17, wherein the configuration includes a continuity indication indicating that the UE will maintain uplink continuity for CFRA uplink channel repetition or physical random access channel (PRACH) repetition, and wherein the memory also includes instructions that can be executed by the one or more processors to enable the UE to maintain uplink continuity based on the continuity indication.

19. The UE of claim 16, wherein the memory further comprises instructions executable by the one or more processors to cause the UE to receive a configuration indicating a time domain window for CFRA uplink repetition, and wherein the memory further comprises instructions executable by the one or more processors to cause the UE to maintain uplink continuity during the time domain window.

20. The UE of claim 19, wherein the time domain window for CFRA uplink repetition matches a time domain window for other uplink channel communications.

21. The UE of claim 19, wherein the time domain window used for CFRA uplink repetition does not match a time domain window used for other uplink channel communications.

22. The UE of claim 19, wherein a size of the time domain window for CFRA uplink repetition matches a smaller size of a time domain window for other uplink channel communications or a configured time domain window size.

23. A network entity for wireless communication, comprising: Memory; and One or more processors, the one or more processors coupled to the memory, the memory comprising instructions executable by the one or more processors to cause the network entity to: receiving an indication of a user equipment (UE) capability to maintain uplink continuity for contention free random access (CFRA) uplink channel repetition for joint channel estimation; receiving the CFRA repetition; as well as Joint channel estimation is performed based on the CFRA uplink repetitions.

24. The network entity of claim 23, wherein the memory further comprises instructions executable by the one or more processors to cause the UE to perform joint channel estimation further based on the configuration for the CFRA uplink channel repetition.

25. The network entity of claim 23, wherein the CFRA uplink repetitions comprise physical random access channel (PRACH) repetitions.

26. The network entity of claim 23, wherein the memory further comprises instructions executable by the one or more processors to cause the network entity to send a configuration indicating a time domain window for CFRA uplink repetition, and wherein the memory further comprises instructions executable by the one or more processors to cause the network entity to perform joint channel estimation only during the time domain window.

27. The network entity of claim 26, wherein the time domain window used for CFRA uplink repetitions matches a time domain window used for other uplink channel communications.

28. The network entity of claim 26, wherein the time domain window used for CFRA uplink repetitions does not match a time domain window used for other uplink channel communications.

29. The network entity of claim 26, wherein a size of the time domain window for CFRA uplink repetition matches the smaller of a size of a time domain window for other uplink channel communications or a configured time domain window size.

Images