Indication of message repetition and demodulation reference signal bundling capability

Abstract

Aspects relate to wireless communication including providing a user equipment (UE) indication of a capability of the UE for demodulation reference signal (DMRS) bundling and / or joint channel estimation (JCE). In aspects, the capability indication includes at least using a physical random access channel (PRACH) to indicate a capability of the UE for repeated transmissions of a physical uplink shared channel (PUSCH) carrying a connection message and a count of available slots for repeated transmissions of the physical channel. Additionally, the UE can be configured to indicate the capability for JCE through a demodulation reference signal (DMRS) configuration or DMRS port.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority and interest in U.S. Application No. 17 / 711,862, filed April 1, 2022, with the U.S. Patent and Trademark Office, and U.S. Provisional Application No. 63 / 176,831, filed April 19, 2021, with the U.S. Patent and Trademark Office, the entire contents of which are incorporated herein by reference as fully set forth herein and for all applicable purposes. Technical Field

[0003] The techniques discussed below generally relate to wireless communication, and in particular to the ability of User Equipment (UE) to instruct repeating and demodulation reference signal (DMRS) bundles for Physical Uplink Shared Channel (PUSCH) messages or Joint Channel Estimation (JCE) for channel estimation.

[0004] introduction

[0005] Next-generation wireless communication systems (e.g., 5GS) may include a 5G core network and a 5G radio access network (RAN), such as a new radio (NR)-RAN. NR-RAN supports communication via one or more cells. For example, wireless communication equipment (such as user equipment (UE)) can access cells via network nodes or entities, which can be achieved, for example, by a base station or gB node (gNB).

[0006] For example, in a 5G NR-RAN system, when a UE first connects to the NR-RAN, an initial access procedure is performed. Specifically, depending on whether the initial access is contention-free (three messages) or contention-based (four messages), a Random Access Channel (RACH) procedure consisting of three or four messages transmitted between the UE and a network entity (such as a gB node (gNB)) is performed. The third message in this sequence is called "Message 3" or "Msg3" and is physically transmitted from the UE to the gNB using the Physical Uplink Shared Channel (PUSCH), and may include a Radio Resource Control (RRC) connection request. In 5G NR systems, repeated transmission of Msg3 (also known as Msg3 repetition or PUSCH repetition) has been introduced to extend the coverage of Msg3 transmission.

[0007] Furthermore, when multiple repetitive transmissions of Msg3 in a PUSCH are sent, the receivers of those messages will process the demodulation reference signal (DMRS) in those multiple PUSCH transmissions for joint channel estimation (JCE) in order to properly demodulate and decode the received signal. In such cases, the transmitter of the repetitive Msg3 transmission is typically restricted from maintaining phase continuity (such as maintaining the same frequency resource allocation, the same transmit power, and / or the same spatial transmission relationships, antenna ports) across multiple PUSCH transmissions, as well as precoding across all repetitive PUSCH transmissions. The ability to perform JCE across repetitive PUSCH transmissions for Msg3 provides additional gains beyond just PUSCH repetition. The ability to perform JCE across multiple Msg3 transmissions provides the UE with the capability to handle JCEs that might otherwise be limited by the PUSCH transmission; particularly the ability to maintain phase continuity across multiple PUSCH transmissions.

[0008] A brief overview of some examples

[0009] The following provides an overview of one or more aspects of this disclosure to provide a basic understanding of these aspects. This overview is not an exhaustive summary of all the features conceived in this disclosure, and is neither intended to identify key or decisive elements of all aspects of this disclosure, nor to define the scope of any or all aspects of this disclosure. Its sole purpose is to provide some concepts of one or more aspects of this disclosure in one form as a prelude to the more detailed description that follows.

[0010] According to a first example, a user equipment (UE) is disclosed, the UE including a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor is configured to configure Physical Random Access Channel (PRACH) resources according to a predetermined configuration to indicate that the UE can support: (1) repeated transmission of physical channels carrying connection messages, and (2) counting of available time slots for repeated transmission of physical channels. Additionally, the processor is configured to use the configured PRACH resources to transmit PRACH to network entities.

[0011] In other examples, a method for wireless communication in a user equipment (UE) is disclosed. The method includes configuring physical random access channel (PRACH) resources according to a predetermined configuration to provide a capability indication that the UE can support both repeated transmissions of the physical channel carrying connection messages and a count of available time slots for repeated transmissions of the physical channel. The method further includes transmitting the PRACH to a network entity using the configured PRACH resources.

[0012] In a further aspect, a base station or network entity is disclosed, including a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor is configured to process PRACH using Physical Random Access Channel (PRACH) resources received from a User Equipment (UE), wherein the PRACH resources are configured according to a predetermined configuration to provide a capability indication indicating that the UE can support: (1) repeated transmissions of the physical channel carrying a connection message, and (2) a count of available time slots for repeated transmissions of the physical channel. The processor is further configured to decode the PRACH to determine the capability indication, wherein the PRACH resources include a PRACH preamble or a PRACH timing including time and frequency resources, and the connection message includes a Message 3 (Msg3) message containing one or more of a radio resource connection request, a scheduling request, or a buffer state.

[0013] According to yet another example, a method for wireless communication in a base station is disclosed. The method includes: receiving a PRACH from a user equipment (UE) using physical random access channel (PRACH) resources, wherein the PRACH resources are configured according to a predetermined configuration to provide a capability indication indicating that the UE is capable of supporting: (1) repeated transmission of a physical channel carrying a connection message, and (2) a count of available time slots for repeated transmission of the physical channel. The method further includes decoding the PRACH to determine the capability indication, wherein the PRACH resources include a PRACH preamble or a PRACH timing including time and frequency resources, and the connection message includes a Message 3 (Msg3) message containing one or more of a radio resource connection request, a scheduling request, or a buffer state. Aspect 2: The method of aspect 1, wherein the PRACH resources include a PRACH preamble or a PRACH timing including time and frequency resources.

[0014] These and other aspects of this disclosure will become more fully understood upon reading the following detailed description. Other aspects, features, and examples of this disclosure will be apparent to those skilled in the art after reading the following description of specific exemplary aspects of this disclosure in conjunction with the accompanying drawings. Although features of this disclosure may be discussed below with respect to certain examples and drawings, all examples of this disclosure may include one or more of the advantageous features discussed herein. In other words, although one or more examples may be discussed having certain advantageous features, one or more such features may also be used according to the various examples of this disclosure discussed herein. Similarly, although the examples may be discussed below as examples of devices, systems, or methods, it should be understood that such examples can be implemented in a variety of devices, systems, and methods. Brief description of the attached diagram

[0016] Figure 1It is a schematic explanation based on some aspects of wireless communication systems.

[0017] Figure 2 It is a conceptual explanation based on examples of radio access networks from various aspects.

[0018] Figure 3 This is a schematic illustration of an example of utilizing radio resources in an air interface of orthogonal frequency division multiplexing (OFDM) based on some aspects.

[0019] Figure 4 The call flow diagram 400 illustrates an example of a four-step RACH procedure based on several aspects.

[0020] Figure 5 It is a timing diagram illustrating an example of signaling during the initial transmission and retransmission timings, based on some aspects.

[0021] Figure 6 An example of a timing diagram for a RACH procedure that utilizes enhanced coverage of Msg3 transmissions for repeated or repetitive transmissions of Msg3 is explained, based on several aspects.

[0022] Figure 7 An example of a PUSCH transmission slot with a demodulation reference signal (DMRS) used in channel estimation (CE) is explained according to some aspects, where the DMRS is used for CE in each corresponding slot.

[0023] Figure 8 The explanation describes time slots with demodulation reference signals (DMRS) used in channel estimation (CE) based on some aspects, where DMRS from multiple time slots are bundled for joint CE.

[0024] Figure 9A An example of counting repeated PUSCH transmissions in a Time Division Duplex (TDD) system is explained based on several aspects.

[0025] Figure 9B An example of counting repeated PUSCH transmissions in a frequency division duplex (FDD) system is explained based on several aspects.

[0026] Figure 10 The call flowchart explains how the UE indicates its capabilities to the base station based on certain aspects.

[0027] Figure 11 Another call flowchart explains the capabilities that the UE indicates to the base station based on certain aspects.

[0028] Figure 12 This is a block diagram illustrating an example of the hardware implementation of a user equipment (UE) using a processing system based on some aspects.

[0029] Figure 13 This is a flowchart illustrating examples of methods for communication in a UE, based on several aspects.

[0030] Figure 14 This is a block diagram illustrating an example of the hardware implementation of a network entity (such as a base station) using a processing system based on some aspects.

[0031] Figure 15 It is a flowchart explaining a method for communication in network entities based on some aspects.

[0032] Detailed description

[0033] The detailed description that follows, taken in conjunction with the accompanying drawings, is intended as a description of various configurations and is not intended to represent only the configurations in which the concepts described herein can be practiced. This detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0034] The electromagnetic spectrum is typically subdivided into various classes, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz–7.125GHz) and FR2 (24.25GHz–52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, FR1 is generally (interchangeably) referred to as the “sub-6GHz band” in various documents and articles. Similar naming issues sometimes arise with FR2; although different from the Very High Frequency (EHF) band (30GHz–300GHz) designated as the “millimeter wave” band by the International Telecommunication Union (ITU), FR2 is generally (interchangeably) referred to as the “millimeter wave” band in various documents and articles.

[0035] The frequencies between FR1 and FR2 are generally referred to as intermediate frequency (IF) bands. Recent 5G NR studies have designated the operating bands of these IF bands as the frequency range designation FR3 (7.125 GHz – 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 into the IF band. Additionally, higher frequency bands are currently being explored to extend 5G NR operation above 52.6 GHz. For example, three higher operating frequency bands have been designated as the frequency range designations FR4-a or FR4-1 (52.6 GHz – 71 GHz), FR4 (52.6 GHz – 114.25 GHz), and FR5 (114.25 GHz – 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0036] In light of the foregoing, unless otherwise stated, it should be understood that, as used herein, the term "sub-6GHz" and the like can broadly refer to frequencies less than 6GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise stated, it should be understood that, as used herein, the term "millimeter wave" and the like can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR4-a or FR4-1 and / or FR5, or within the EHF band.

[0037] According to some aspects of this application, indications of a UE's ability to maintain phase continuity for multiple PUSCH Msg3 repetitions are disclosed. In some examples, the UE is configured to provide an indication that the UE has the ability to count time slots used for PUSCH Msg3 repetitions and supports DMRS bundle and / or Joint Channel Estimation (JCE). A UE thus enabled can provide indications to the network (e.g., gNB) that the UE has these capabilities, so that the network will be aware that the UE can implement PUSCHMsg3 repetitions.

[0038] While aspects and examples are described herein by way of illustration of a few examples, those skilled in the art will understand that additional implementations and use cases may arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, the examples and / or devices may arise via integrated chip examples and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a particular use case or application, broad applicability of the described innovations can emerge. The scope of implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations. In some practical contexts, devices incorporating the described aspects and features may also necessarily include additional components and features for implementing and practicing the claimed and described examples. For example, the transmission and reception of wireless signals requires several components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be implemented in a wide variety of devices, chip-level components, systems, distributed deployments, end-user equipment, etc., of various sizes, shapes, and configurations.

[0039] The various concepts presented throughout this disclosure can be implemented across a wide range of telecommunications systems, network architectures, and communication standards. Now refer to... Figure 1 The various aspects of this disclosure are explained with reference to a wireless communication system 100, by way of illustrative example and not limitation. The wireless communication system 100 includes three interaction domains: a core network 102, a radio access network (RAN) 104, and at least one scheduled entity 106. The at least one scheduled entity 106 may be referred to as User Equipment (UE) 106 in the following discussion. The RAN 104 includes at least one scheduling entity 108. The at least one scheduling entity 108 may be referred to as Base Station (BS) 108 in the following discussion. Through the wireless communication system 100, the UE 106 is enabled to perform data communication with an external data network 110 (such as, but not limited to, the Internet).

[0040] RAN 104 can implement any suitable one or more wireless communication technologies to provide radio access to UE 106. As an example, RAN 104 can operate according to the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification (commonly referred to as 5G). As another example, RAN 104 can operate in a hybrid of 5G NR and the Evolved Universal Terrestrial Radio Access Network (eUTRAN) standard (commonly referred to as LTE). 3GPP refers to this hybrid RAN as Next Generation RAN, or NG-RAN. Of course, many other examples can be utilized within the scope of this disclosure.

[0041] As explained, RAN 104 includes multiple base stations 108. Broadly speaking, a base station is a network element in a radio access network responsible for radio transmissions to and from a UE in one or more cells. In different technologies, standards, or contexts, a base station may be referred to by those skilled in the art as a base transceiver station (BTS), radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), access point (AP), B-node (NB), evolved B-node (eNB), next-generation B-node (gNB), transmit-receive point (TRP), or some other suitable term. In some examples, a base station may include two or more co-located or non-co-located TRPs. TRPs may communicate on the same or different carrier frequencies within the same or different frequency bands.

[0042] Radio access network 104 is further described as supporting wireless communication for multiple mobile devices. In 3GPP standards, a mobile device may be referred to as User Equipment (UE), but may also be referred to by those skilled in the art as a mobile station (MS), subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal (AT), mobile terminal, radio terminal, remote terminal, handheld device, terminal, user agent, mobile client, client, or any other suitable term. A UE may be a device that provides users with access to network services.

[0043] In this document, a “mobile” device does not necessarily need to be mobile and may be stationary. The term mobile device or mobile equipment refers to a wide variety of devices and technologies. A UE may include several hardware structural components that are sized, shaped, and arranged to facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc., electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile devices, cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal computers (PCs), laptops, netbooks, smartbooks, tablets, personal digital assistants (PDAs), and a wide variety of embedded systems, such as those corresponding to the “Internet of Things” (IoT). Additionally, mobile devices can be automobiles or other transportation vehicles, remote sensors or actuators, robots or robotic equipment, satellite radios, Global Positioning System (GPS) devices, object tracking devices, drones, multi-rotor aircraft, quadcopters, remote control devices, consumer and / or wearable devices (such as glasses), wearable cameras, virtual reality devices, smartwatches, health or fitness trackers, digital audio players (e.g., MP3 players), cameras, game consoles, etc. Mobile devices can also be digital home or smart home devices, such as home audio, video and / or multimedia equipment, appliances, vending machines, smart lighting equipment, home security systems, smart meters, etc. Mobile devices can also be smart energy devices, security devices, solar panels or solar arrays, municipal infrastructure equipment controlling electricity, lighting, water, etc. (e.g., smart grids); industrial automation and enterprise equipment; logistics controllers; military defense equipment, vehicles, aircraft, ships, and weapons, etc. Furthermore, mobile devices can provide connected healthcare or telemedicine support, i.e., remote health care. Remote healthcare devices may include remote healthcare monitoring devices and remote healthcare supervision devices, whose communications may be given priority or preferential access over other types of information, for example, in the form of priority access for critical service data transmission and / or relevant QoS for critical service data transmission.

[0044] Wireless communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) can be referred to as downlink (DL) transmissions. In some examples, the term downlink can refer to point-to-multipoint transmissions originating at a scheduling entity (further described below; e.g., base station 108). Another way to describe this point-to-multipoint transmission scheme is to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions. In some examples, the term uplink can refer to point-to-point transmissions originating at a scheduled entity (further described below; e.g., UE 106).

[0045] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., base station 108) allocates resources for communication among some or all of the equipment and devices within its service area or cell. Within this disclosure, as further discussed below, the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communication, UE 106 (which may be a scheduled entity) may utilize the resources allocated by scheduling entity 108.

[0046] Base station 108 is not the only entity that can be used as a scheduling entity. That is, in some examples, a UE can be used as a scheduling entity to schedule resources for one or more scheduled entities (e.g., one or more other UEs).

[0047] like Figure 1 As explained, scheduling entity 108 may broadcast downlink traffic 112 to one or more scheduled entities 106. Broadly speaking, scheduling entity 108 is a node or device responsible for scheduling traffic (including downlink traffic 112 and, in some examples, uplink traffic 116 and / or uplink control information 118 from one or more scheduled entities 106 to scheduling entity 108) in a wireless communication network. On the other hand, scheduled entity 106 is a node or device that receives downlink control information 114 (including, but not limited to, scheduling information (e.g., permission), synchronization or timing information), or other control information) from another entity in the wireless communication network (such as scheduling entity 108).

[0048] Additionally, uplink and / or downlink control information and / or traffic information can be temporally divided into frames, subframes, time slots, and / or symbols. As used herein, a symbol may refer to a time unit in which one resource element (RE) is carried per subcarrier in an Orthogonal Frequency Division Multiplexing (OFDM) waveform. In some examples, a time slot may carry 7 or 14 OFDM symbols. A subframe may refer to a duration of 1 millisecond (ms). Multiple subframes or time slots may be grouped together to form a single frame or radio frame. Of course, these definitions are not mandatory, and any suitable scheme can be used to organize the waveform, and the various time divisions of the waveform can have any suitable duration.

[0049] Generally, base station 108 may include a backhaul interface for communicating with the backhaul section 120 of a wireless communication system. Backhaul 120 provides a link between base station 108 and core network 102. Furthermore, in some examples, the backhaul network provides interconnection between the respective base stations 108. Various types of backhaul interfaces can be employed, such as a direct physical connection using any suitable transport network, a virtual network, etc.

[0050] Core network 102 may be part of wireless communication system 100 and may be independent of the radio access technology used in RAN 104. In some examples, core network 102 may be configured according to 5G standards (e.g., 5GC). In other examples, core network 102 may be configured according to 4G evolved packet core (EPC) or any other suitable standard or configuration.

[0051] Now refer to Figure 2 The illustrative explanation of RAN 200 is provided as an example, not a limitation. In some examples, RAN 200 may be used in conjunction with the above description and in Figure 1 The same applies to RAN 104 as explained in the text. The geographical area covered by RAN 200 can be divided into cellular areas (cells), which can be uniquely identified by the user equipment (UE) based on an identifier broadcast from an access point or base station. Figure 2 Macrocells 202, 204, and 206, and small cell 208, are described, each of which may include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors within a cell are served by the same base station. Radio links within a sector may be identified by a single logical identifier belonging to that sector. In a cell divided into sectors, multiple sectors within the cell may be formed by an antenna array, where each antenna is responsible for communication with UEs in a portion of the cell.

[0052] It can be deployed using various base stations. For example, in Figure 2In the illustration, two base stations 210 and 212 are shown in cells 202 and 204; and a third base station 214 is shown as a remote radio head (RRH) 216 controlling cell 206. That is, the base stations may have integrated antennas, or they may be connected to the antenna or RRH via a feed cable. In the illustrated example, cells 202, 204, and 206 may be referred to as macrocells because base stations 210, 212, and 214 support cells with large sizes. Furthermore, base station 218 is shown in small cell 208 (e.g., microcell, picocell, femtocell, home base station, home B node, home evolved B node, g B node, etc.), which may overlap with one or more macrocells. In this example, cell 208 may be referred to as a small cell because base station 218 supports cells with relatively small sizes. Cell size settings can be determined based on system design and component constraints.

[0053] It will be understood that the radio access network 200 may include any number of radio base stations and cells. Furthermore, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, and / or 218 provide radio access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 may be associated with the components described above and in... Figure 1 The base station / scheduling entity 108 described in the Chinese explanation is the same.

[0054] Within RAN 200, a cellular cell may include UEs capable of communicating with one or more sectors of each cellular cell. Further, each base station 210, 212, 214, and 218 may be configured to provide access to the core network for all UEs within the respective cellular cell (e.g., as...). Figure 1 Access points (as explained above). For example, UEs 222 and 224 may communicate with base station 210; UEs 226 and 228 may communicate with base station 212; UEs 230 and 232 may communicate with base station 214 via RRH 216; and UE 234 may communicate with base station 218. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240 and / or 242 may communicate with the access points described above and in... Figure 1 The UE / scheduled entity 106 described in the text is the same.

[0055] In some examples, an unmanned aerial vehicle (UAV) 220 (which may be a drone or a quadcopter) can be a mobile network node and can be configured to act as a UE. For example, UAV 220 can operate within cell 202 by communicating with base station 210. In some examples, UAV 220 can be configured to act as a BS (e.g., serving UE 236). That is, in some examples, the cell may not be stationary, and the geographical area of ​​the cell may move depending on the location of the mobile base station (such as UAV 220).

[0056] In a radio access network 200, the ability of a UE to communicate independently of its location while on the move is referred to as mobility. The various physical channels between the UE and the radio access network are generally established, maintained, and released under the control of the Access and Mobility Management Function (AMF). The AMF (not in...) Figure 2 (As shown in the figure) may include a Security Context Management (SCMF) function that manages the security context for both control plane and user plane functionality, and a Security Anchor (SEAF) function that performs authentication.

[0057] Radio access network 200 can utilize DL-based mobility or UL-based mobility to achieve mobility and handover (i.e., the UE's connection is transferred from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity, or at any other time, the UE can monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Depending on the quality of these parameters, the UE can maintain communication with one or more neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE can perform a handover or handover from the serving cell to a neighboring (target) cell. For example, UE 224 (described as a vehicle, but any suitable form of UE can be used) can move from a geographic area corresponding to its serving cell 202 to a geographic area corresponding to a neighboring cell 206. When the signal strength or quality from neighboring cell 206 exceeds the signal strength or quality of serving cell 202 for a given amount of time, UE 224 may transmit a report message indicating this condition to its serving base station 210. In response, UE 224 may receive a handover command, and the UE may undergo a handover to cell 206.

[0058] In a network configured for UL-based mobility, UL reference signals from each UE can be used by the network to select a serving cell for each UE. In some examples, base stations 210, 212, and 214 / 216 can broadcast unified synchronization signals (e.g., unified primary synchronization signal (PSS), unified secondary synchronization signal (SSS), and unified physical broadcast channel (PBCH)). UEs 222, 224, 226, 228, 230, and 232 can receive unified synchronization signals, derive carrier frequencies and time slot timings from these synchronization signals, and transmit uplink pilot or reference signals in response to the derived timings. The uplink pilot signal transmitted by a UE (e.g., UE 224) can be received concurrently by two or more cells (e.g., base stations 210 and 214 / 216) within the radio access network 200. Each of these cells can measure the strength of the pilot signal, and the radio access network (e.g., one or more of base stations 210 and 214 / 216 and / or a central node within the core network) can determine the serving cell for UE 224. As UE 224 moves within the radio access network 200, the network can continue to monitor the uplink pilot signal transmitted by UE 224. When the signal strength or quality of the pilot signal measured by a neighboring cell exceeds the signal strength or quality measured by the serving cell, the network 200 can, with or without notification, switch UE 224 from the serving cell to the neighboring cell.

[0059] Although the synchronization signal transmitted by base stations 210, 212, and 214 / 216 can be uniform, it may not identify a specific cell, but rather a zoning that includes multiple cells operating on the same frequency and / or having the same timing. Using zoning in 5G networks or other next-generation communication networks enables uplink-based mobility frameworks and improves the efficiency of both the UE and the network because the number of mobility messages that need to be exchanged between the UE and the network can be reduced.

[0060] In various implementations, the air interface in the radio access network 200 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum typically provides exclusive use of a portion of the spectrum by a mobile network operator purchasing a license from a government regulatory agency. Unlicensed spectrum provides shared use of a portion of the spectrum without a government-granted license. While some technical rules generally still need to be followed to access unlicensed spectrum, access can be obtained by any operator or device. Shared spectrum may fall between licensed and unlicensed spectrum, where technical rules or restrictions may be required to access the spectrum, but the spectrum may still be shared by multiple operators and / or multiple RATs. For example, a licensee of a portion of licensed spectrum may provide Licensed Shared Access (LSA) to share that spectrum with other parties, for example, by utilizing conditions determined by the appropriate licensee.

[0061] The electromagnetic spectrum is typically subdivided into various classes, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz–7.125GHz) and FR2 (24.25GHz–52.6GHz). The frequencies between FR1 and FR2 are generally referred to as the mid-band frequencies. Although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the “sub-6GHz” band in various documents and articles. Similar naming issues sometimes arise regarding FR2; although different from the Very High Frequency (EHF) band (30GHz–300GHz) designated as the “millimeter wave” band by the International Telecommunication Union (ITU), FR2 is often (interchangeably) referred to as the “millimeter wave” band in various documents and articles.

[0062] In light of the foregoing, unless otherwise stated, it should be understood that, as used herein, the term "sub-6GHz" and the like can broadly refer to frequencies less than 6GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise stated, it should be understood that, as used herein, the term "millimeter wave" and the like can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, or within the EHF band.

[0063] The air interface in the radio access network 200 can utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication between individual devices. For example, the 5G NR specification utilizes Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP) to provide multiple access for UL transmissions from UEs 222 and 224 to base station 210, and to provide multiplexing for DL ​​transmissions from base station 210 to one or more UEs 222 and 224. Additionally, for UL transmissions, the 5G NR specification provides support for Discrete Fourier Transform Extended OFDM (DFT-s-OFDM) with CP (also known as Single-Carrier FDMA (SC-FDMA)). However, within the scope of this disclosure, multiplexing and multiple access are not limited to the above schemes and can be provided using Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Sparse Code Multiple Access (SCMA), Resource Extended Multiple Access (RSMA), or other suitable multiple access schemes. Furthermore, the multiplexing of DL transmissions from base station 210 to UEs 222 and 224 can be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), OFDM, sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0064] The air interface in the radio access network 200 can further utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link where both endpoints can communicate with each other in both directions. Full-duplex means that both endpoints can communicate with each other simultaneously. Half-duplex means that only one endpoint can send information to the other endpoint at a time. Half-duplex simulation is typically implemented for wireless links using Time Division Duplex (TDD). In TDD, transmissions in different directions on a given channel are separated using time division multiplexing. That is, at some times, the channel is dedicated to transmissions in one direction, and at other times, the channel is dedicated to transmissions in the other direction, where the direction can change very rapidly, for example, several times per time slot. In wireless links, full-duplex channels generally rely on physical isolation between the transmitter and receiver, and appropriate interference cancellation techniques. Full-duplex simulation is typically implemented for wireless links using Frequency Division Duplex (FDD) or Space Division Duplex (SDD). In FDD, transmissions in different directions operate at different carrier frequencies. In SDD, transmissions in different directions on a given channel are separated from each other using spatial division multiplexing (SDM). In other examples, full-duplex communication can be implemented in unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur in different subbands of the carrier bandwidth. This type of full-duplex communication can be called subband full-duplex (SBFD), also known as flexible duplex.

[0065] In a further aspect of RAN 200, sidelink signal 237 can be used between UEs without relying on scheduling or control information from a base station. For example, two or more UEs (e.g., UEs 226 and 228 (or UEs 240 and 242)) can communicate with each other using peer-to-peer (P2P) or sidelink signal 227 (or 244) without relaying the communication through a base station (e.g., base station 212). In a further example, UE 238 is described as communicating with UEs 240 and 242. Here, UE 238 can act as a scheduling entity or a primary sidelink device, and UEs 240 and 242 can act as scheduled entities or non-primary (e.g., secondary) sidelink devices. In yet another example, a UE can act as a scheduling entity in a device-to-device (D2D), peer-to-peer (P2P), or vehicle-to-vehicle (V2V) network, and / or a mesh network. In the mesh network example, UEs 240 and 242 may optionally communicate directly with each other in addition to communicating with UE 238 (e.g., acting as a scheduling entity). Thus, in a wireless communication system with scheduled access to time-frequency resources and with cellular, P2P, or mesh configurations, the scheduling entity and one or more scheduled entities can utilize the scheduled resources to communicate. In some examples, sidelink signal 227 (or 244) includes sidelink traffic (e.g., a physical sidelink shared channel) and sidelink control (e.g., a physical sidelink control channel).

[0066] In some examples, two or more UEs (e.g., UEs 226 and 228) within the coverage area of ​​serving base station 212 can communicate with base station 212 using cellular signals and communicate with each other using direct link signals (e.g., sidelink signal 227) without relaying the communication through the base station. In examples of V2X networks within the coverage area of ​​base station 212, base station 212 and / or one or both of UEs 226 and 228 can be used as a scheduling entity to schedule sidelink communication between UEs 226 and 228.

[0067] Various aspects of this disclosure will be described with reference to OFDM waveforms, examples of which are shown in Figure 3 The following is an illustrative explanation. Those skilled in the art will understand that various aspects of this disclosure can be applied to SC-FDMA waveforms in substantially the same manner as described below. That is, while some examples of this disclosure may focus on OFDM links for clarity, it should be understood that the same principles can also be applied to SC-FDMA waveforms.

[0068] Now refer to Figure 3The diagram illustrates an expanded view of example DL subframe (SF) 302A, showing the OFDM resource grid 304. However, as those skilled in the art will readily appreciate, the physical layer (PHY) transport architecture for any particular application can vary from the example described herein depending on any number of factors. Here, time is in the horizontal direction in units of OFDM symbols, while frequency is in the vertical direction in units of subcarriers. 5G NR supports scalable parameter designs, where different parameter designs can be used for different radio spectrums, different bandwidths, etc. For example, subcarrier spacing (SCS) of 15kHz, 30kHz, 60kHz, etc., can be used in different scenarios.

[0069] Resource grid 304 can be used to schematically represent time-frequency resources for a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple antenna ports available, there can be corresponding multiple resource grids 304 available for communication. Resource grid 304 is divided into multiple resource elements (REs) 306. An RE (which is 1 subcarrier × 1 symbol) is the smallest discrete part of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation used in a particular implementation, each RE may represent one or more information bits. In some examples, an RE block may be referred to as a physical resource block (PRB) or more simply as a resource block (RB) 308, which contains any suitable number of coherent subcarriers in the frequency domain. In one example, an RB may include 12 subcarriers, the number of which is independent of the parameter design used. In some examples, depending on the parameter design, an RB may include any suitable number of coherent OFDM symbols in the time domain. Within this disclosure, it is assumed that a single RB (such as RB 308) corresponds exactly to a single communication direction (transmission or reception for a given device).

[0070] Scheduling of downlink, uplink, or sidelink transmissions for a UE (e.g., a scheduled entity) typically involves scheduling one or more resource elements 306 within one or more subbands or bandwidth portions (BWPs). Each BWP may include two or more adjacent or coherent RBs. Thus, the UE generally utilizes only a subset of the resource grid 304. In some examples, an RB may be the smallest resource unit that can be allocated to the UE. Therefore, the more RBs scheduled for the UE and the higher the modulation scheme selected for the air interface, the higher the data rate of the UE. RBs can be scheduled by base stations (e.g., gNB, eNB, RSU, etc.) or can be self-scheduled by the UE implementing D2D sidelink communication.

[0071] In this explanation, RB 308 is shown to occupy less than the entire bandwidth of subframe 302A, where some subcarriers above and below RB 308 are explained. In a given implementation, subframe 302A may have a bandwidth corresponding to any number of one or more RB 308s. Furthermore, in this explanation, RB 308 is shown to occupy less than the entire duration of subframe 302A, but this is merely one possible example.

[0072] Each 1ms subframe 302A may include one or more adjacent time slots. As an illustrative example, in... Figure 3 In the example shown, a subframe 302B includes four time slots 310. In some examples, time slots may be defined based on a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include mini-time slots with shorter durations (e.g., one or two OFDM symbols). In some cases, these mini-time slots may occupy resources scheduled for ongoing time slot transmissions for the same or different UEs. Any number of resource blocks may be utilized within a subframe or time slot.

[0073] An expanded view of one of the time slots 310 illustrates time slot 310, which includes a control area 312 and a data area 314. Generally, the control area 312 may carry a control channel (e.g., a PDCCH), while the data area 314 may carry a data channel (e.g., a Physical Downlink Shared Channel (PDSCH) or a Physical Uplink Shared Channel (PUSCH)). Of course, a time slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. Figure 3 The structure described herein is merely an example, and different time slot structures can be used, and one or more can be included for each of the control and data regions.

[0074] Although not in Figure 3 The explanation is as follows: Each RE 306 within RB 308 can be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 306 within RB 308 can also carry pilot or reference signals, including but not limited to demodulation reference signals (DMRS), control reference signals (CRS), or probe reference signals (SRS). These pilot or reference signals can be used by the receiver equipment to perform channel estimation for the corresponding channels, which enables coherent demodulation / detection of the control and / or data channels within RB 308.

[0075] In some examples, time slot 310 can be used for broadcast or unicast communication. In V2X or D2D networks, broadcast communication can refer to point-to-multipoint transmission from one device (e.g., a vehicle, base station (e.g., RSU, gNB, eNB, etc.), UE, or other similar device) to other devices. Unicast communication can refer to point-to-point transmission from one device to a single other device.

[0076] In one example, the control area 312 of time slot 310 may include a physical downlink control channel (PDCCH) comprising downlink control information (DCI) transmitted by a base station (e.g., gNB, eNB, RSU, etc.) to one or more UEs in a group of UEs, which may include one or more sidelink devices (e.g., V2X / D2D devices). In some examples, the DCI may include synchronization information to synchronize communications performed by multiple sidelink devices on the sidelink channel. Furthermore, the DCI may include scheduling information indicating one or more resource blocks allocated to sidelink devices within control area 312 and / or data area 314 for sidelink communication. For example, the control area 312 of time slot may also include control information transmitted by sidelink devices on the sidelink channel, while the data area 314 of time slot 310 may include data transmitted by sidelink devices on the sidelink channel. In some examples, this control information may be transmitted within the physical sidelink control channel (PSCCH), and this data may be transmitted within the physical sidelink shared channel (PSSCH).

[0077] In DL transmission (e.g., via the Uu interface), the transmitting device (e.g., a scheduling entity) may allocate one or more REs 306 (e.g., within control area 312) to carry DL control information, including one or more DL control channels (such as Physical Broadcast Channel (PBCH) and / or PDCCH), to one or more scheduled entities. The transmitting device may further allocate one or more REs 306 to carry other DL signals (such as DMRS, Phase Tracking Reference Signal (PT-RS), Channel State Information-Reference Signal (CSI-RS), Primary Synchronization Signal (PSS), and Secondary Synchronization Signal (SSS).

[0078] Synchronization signals PSS and SSS, and in some examples PBCH and PBCH DMRS, can be transmitted in a synchronization signal block (SSB), which comprises three consecutive OFDM symbols numbered in ascending order from 0 to 3 via time indexing. In the frequency domain, the SSB can be extended over 240 adjacent subcarriers, where the subcarriers are numbered in ascending order from 0 to 239 via frequency indexing. Of course, this disclosure is not limited to this particular SSB configuration. Within the scope of this disclosure, other non-limiting examples may utilize more or fewer synchronization signals, may include one or more supplementary channels in addition to PBCH, may omit PBCH, and / or may use different numbers of symbols and / or discontinuous symbols for the SSB.

[0079] The SSB can be used to transmit System Information (SI) and / or provide a reference to SI transmitted via another channel. Examples of System Information may include, but are not limited to: subcarrier spacing, system frame number, Cell Global Identifier (CGI), Cell Strip Indicator, shared control resource set (coreset) list, shared search space list, search space for System Information Block 1 (SIB1), paging search space, random access search space, and uplink configuration information. Two specific examples of coresets include PDCCH CORESET 0 and CORESET 1.

[0080] The PDCCH can carry downlink control information (DCI), including but not limited to power control commands, scheduling information, grants, and / or RE assignments for DL ​​and UL transmissions. The physical (PHY) channel carries Hybrid Automatic Repeat Request (HARQ) feedback transmissions, such as ACK or NACK. HARQ is a technique well-known to those skilled in the art, where, for accuracy, any suitable integrity verification mechanism (such as a checksum or cyclic redundancy check (CRC)) can be used to verify the integrity of packet transmissions at the receiving side. If the integrity of the transmission is acknowledged, an ACK can be transmitted; otherwise, a NACK can be transmitted. In response to a NACK, the transmitting device can send a HARQ retransmission, which enables catch-up combining, incremental redundancy, etc.

[0081] In UL transmissions (e.g., via a Uu interface), the transmitting device (e.g., the scheduled entity) may utilize one or more RE 306s to carry UL control information to the scheduling entity. This UL control information includes one or more UL control channels, such as the Physical Uplink Control Channel (PUCCH). The UL control information may include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. For example, the UL control information may include DMRS or SRS. In some examples, the control information may include a scheduling request (SR), i.e., a request for the scheduling entity to schedule uplink transmissions. Here, in response to an SR transmitted on the control channel, the scheduling entity may transmit downlink control information, which can schedule resources for uplink packet transmissions. The UL control information may also include HARQ feedback, Channel State Feedback (CSF), or any other suitable UL control information.

[0082] In addition to control information, one or more REs 306 (e.g., within data area 314) may also be allocated for user data or traffic data. Such traffic may be carried on one or more traffic channels, such as on the PDSCH for DL ​​transmissions or on the PUSCH for UL transmissions. In some examples, one or more REs 306 within data area 314 may be configured to carry SIBs (e.g., SIB1) that enable access to system information for a given cell.

[0083] These physical channels are typically multiplexed and mapped to transport channels for processing by the Media Access Control (MAC) layer. The transport channel carries blocks of information, called transport blocks (TBs). The transport block size (TBS) (which may correspond to the number of information bits) can be a controlled parameter based on the modulation and coding scheme (MCS) and the number of redundancies (RBs) in a given transmission.

[0084] Referenced above Figures 1-3 The channels or carriers described are not necessarily all the channels or carriers available between the scheduling entity and the scheduled entity, and those skilled in the art will recognize that other channels or carriers, such as other traffic, control, and feedback channels, may be available in addition to those described.

[0085] As discussed earlier, the RACH procedure is implemented when the UE connects to a network (e.g., UE 106 connects to RAN 104). Figure 4The call flow diagram 400 illustrates an example of a contention-based four-step RACH procedure for this example. As shown, the RACH procedure involves messages transmitted between the UE 402 and a network entity (such as a base station or gNB 404). A first message Msg1 406 is sent via the Physical Random Access Channel (PRACH), which carries a PRACH preamble that can be one of several different available preamble configurations (e.g., 64 configurations for 5G NR).

[0086] In response to Msg1 406, the base station or gNB 404 responds to the PRACH preamble by generating and transmitting a second message, Msg2 408, via the PDCCH or PDSCH channel. Msg2 408 is a Random Access Response (RAR) in response to Msg1 406 and may include timing advance, uplink (UL) permission for subsequent message 3 (Msg3), temporary cell radio network temporary identifier (TC-RNTI), etc.

[0087] In response to Msg2 408, the UE responds by sending a third message (i.e., Msg3 410 on the PUSCH). Msg3 410 is typically a connection request and includes, in particular, an RRC connection request, a scheduling request, and the UE's buffer state, etc. As discussed earlier, for coverage enhancement in 5G NR systems, Msg3 is repeated through transmission on the PUSCH. Furthermore, for a Msg3 repetition system, the UE transmits the message repeatedly across multiple PUSCHes to maintain phase continuity.

[0088] Finally, for contention-based RACH procedures, the base station or gNB 406 transmits a fourth message, Msg4 412, on the PDCCH or PDSCH resources. Msg4 includes a contention resolution message. This message may use, for example, the TC-RNTI (or cell RNTI (C-RNTI)) on the PDCCH or the UE contention resolution identity (IE) on the PDSCH to assist the UE in resolving contention and determine whether the contention resolution was successful.

[0089] In some scenarios, Msg3 can be a bottleneck, where it is not received at the base station or gNB, and multiple retransmissions of Msg3 may be required to successfully deliver it to the base station or gNB. Note that in such scenarios, the UE needs to successfully receive both the RAR for the initial transmission (e.g., Msg2) and the TC-RNTIDCI for retransmissions, resulting in high PDCCH overhead. Additionally, retransmissions of Msg3 increase the initial access delay time of the RACH procedure.

[0090] Accordingly, Msg3 PUSCH repetition can be introduced to extend Msg3 coverage. In some cases, Msg3 repetition can be enabled only when retransmission is required, but in some examples, Msg3 repetition can be enabled for both the initial transmission and retransmission. It should be noted here that the difference between Msg3 repetition and retransmission is that message repetition is, of course, a configured scheme used to repeat the transmission of the same Msg3 a predetermined number of times (e.g., a configuration for sending multiple transmissions of Msg3 after Msg2, which is technically not a retransmission process in which the DCI with C-RNTI or TC-RNTI must be received and decoded before the retransmission of Msg3).

[0091] Figure 5 Examples of message passing sequences for the initial transmission and / or retransmission of Msg3 are explained. Box 502 explains the initial transmission sequence in which a DCI with a Random Access Radio Network Temporary Identifier (RA-RNTI) 504 is transmitted from the gNB to the UE, wherein the gNB uses the RA-RNTI to scramble the CRC of the PDCCH for transmission from the gNB to the UE carrying a RAR (e.g., Msg2) 506. Further, in response to RAR 506, the UE transmits Msg3 508 to the gNB via the PUSCH. In the retransmission case shown at box 510 (i.e., after the initial transmission process in box 502), the UE receives a DCI with a TC-RNTI from the gNB, as shown at 512, in one example, which is transmitted via the PDCCH resource. The UE then retransmits Msg3, as shown in box 514.

[0092] Figure 6 An example of the timing of a RACH procedure for repeated or retransmitted Msg3 using enhanced coverage for Msg3 transmission is explained. In this scenario, block 602 explains the initial transmission sequence, in which a DCI with RA-RNTI 604 is transmitted from the UE to the gNB and a RAR (e.g., Msg2) 606 is subsequently transmitted from the gNB to the UE. In some examples, the initial transmission procedure in block 602 may utilize Msg3 retransmission, and thus multiple or repeated Msg3 transmissions with the same configuration are explained by reference numerals 608a to 608n. In the retransmission case shown at block 610 (i.e., after the initial transmission procedure in block 602), the UE receives a DCI with TC-RNTI from the gNB, as shown at 612, in one example, which is transmitted via PDCCH resources. The UE then retransmits Msg3, as shown in block 614a. However, in this example, Msg3 repetition is also utilized, and thus multiple or repeated Msg3 transmissions are illustrated as shown in boxes 614a to 614n.

[0093] It should be noted that PUSCH repetitions are known to be classified into at least two types: Type A and Type B. In Type A, the same symbol allocation is applied to slots across repetitive PUSCH transmissions. In Type B, different symbol allocations within slots can be applied across repetitive PUSCH transmissions.

[0094] Another aspect to consider in Msg3 PUSCH repetition is joint channel estimation. In 5G NR, DMRS is used for channel estimation at the receiver receiving a signal with in-signal DMRS resources. For example, Figure 7 The general procedure for channel estimation (CE) is explained, in which several time slots 702a, 702b, and 702c are transmitted sequentially in time. Each time slot contains several symbols (e.g., 14 symbols with two control symbols and 12 symbols with data and / or DMRS). Figure 7 In the example, the receiver can use DMRS 704 in time slot 702a to perform channel estimation for decoding time slots 702a, 702b, and 702c.

[0095] However, in Joint Channel Estimation (JCE), iterative channel estimation is achieved by pooling DMRS frequency modulations over several time slots (such as time slots 702a, 702b, and 702c). As an explanation, Figure 8 The diagram illustrates how DMRS frequency modulation 804 from each of several time slots 802a, 802b, and 802c is jointly used for channel estimation. For example, receivers in each time slot jointly process DMRS from multiple repetitive PUSCH transmissions. This joint channel estimation technique becomes particularly useful in systems using millimeter waves and massive MIMO.

[0096] The JCE process can also be referred to as, or considered as, the bundle of DMRS in the time domain across one or more time slots (i.e., time-domain bundle of DMRS). When DMRS bundle is configured, the receiver (whether in the UE or the base station) can perform joint channel estimation based on DMRS received across multiple time slots 802a, 802b, 802c, rather than performing channel estimation separately for each individual time slot based on DMRS received in each individual time slot, for example, as... Figure 7 As shown.

[0097] When using DMRS bundles with Msg3 PUSCH repetition, specifically, it is important for the transmitter (i.e., the UE transmitter) to maintain phase continuity across multiple repetitive PUSCH transmissions. Phase continuity can be maintained through several means, including maintaining the same frequency resource allocation across repetitive transmissions, which... Figure 8As shown, each time slot 802a, 802b, and 802c uses the same time / frequency resources for data and DMRS. Other means of maintaining phase continuity include using the same transmit power, the same spatial transmission relationship, the same antenna port, and the same precoding at the transmitter.

[0098] Furthermore, in the example of UE transmission and PUSCH repetition transmission on the uplink (UL), specifically, the UE can be configured to count the number of UL slots available in a time-division duplex (TDD) allocation (e.g., set or dynamic UL / DL slot allocation), where there is a combination of downlink, special (or flexible), and uplink slots on a certain set number or slot pattern in the allocation (e.g., 16 slots for TDD allocation). The UE's ability to count UL slots or keep track of UL slots becomes important for maintaining phase continuity across multiple repetitive PUSCH transmissions. In a further aspect, when using PUSCH repetition type A, as discussed above, the UE is configured to repeat the transmission block (TB) across coherent slots, thereby applying the same symbol allocation in each slot. It should also be noted that although Figure 8 While the temporally consecutive time slots have been explained, there may be instances where TDD allocations have gaps between uplink time slots (such as downlink time slots or special time slots between uplink time slots in time). In these cases, the UE will still account for the number of UL time slots used for PUSCH retransmission, as will be explained below.

[0099] Figure 9A Example 900 illustrates the counting of repeated PUSCH transmissions in a Time Division Duplex (TDD) system. In this example, there are several uplink (U), downlink (D), or special (S) time slots allocated according to a certain allocation mode. Note that the special (S) time slots can be allocated as uplink, downlink, or flexible time slots. Figure 9A The specific example shows a repeating pattern of 10 time slots indicated by bracket 902, but this disclosure applies to many different patterns and allocations.

[0100] Figure 9A An example of counting PUSCH repeat transmissions is further illustrated. Each PUSCH repeat transmission in the repeat transmissions can be seen in time slots 904, 906, 908, 910, and 912. Note that time slot 906 in this example is a special time slot S allocated for UL transmissions. As follows... Figure 9AFor each of these time slots, the representation of the count (starting from time slot 0) is explained, which represents the count maintained in the UE for each PUSCH retransmission. This count (rather than counting sequentially across all time slots) is only for the UL time slots available for PUSCH retransmission. In a further aspect, the PUSCH retransmission type can be Type A, and the UE will repeat the same transport block (TB) across consecutive time slots, thus applying the same symbol allocation in each time slot.

[0101] Figure 9B Another example 920 of time slot allocation in a Frequency Division Duplex (FDD) system is explained. In this case, each time slot is available for uplink transmission because frequency resources, rather than time resources, are allocated / duplexed. Accordingly, for this particular example, a UE transmitting repeated PUSCH transmissions can simply count each time slot, as shown by counting from 0 to 15 below each uplink time slot, but is not limited to this.

[0102] Note that support for Msg3 PUSCH repetition, and further, the use of joint channel estimation across Msg3 PUSCH repetition, will depend on the capabilities of the UE, especially since the UE is required to maintain phase continuity across transmissions. Accordingly, it will be desirable to provide the UE with the ability to indicate to the UE that it supports repetition counting of available time slots and, accordingly, joint channel estimation / DMRS clustering across Msg3 PUSCH repetition. Based on the foregoing, this disclosure provides various UE configurations to enable the UE to send to the network (e.g., gNB) an indication of its ability to support Msg3 PUSCH repetition, including the ability to count and perform joint channel estimation or DMRS clustering of available UL time slots.

[0103] In the first option, the UE can configure and transmit PRACH using PRACH resources that indicate support for Msg3 PUSCH repetition (such as PRACH preambles or alternative PRACH timings (i.e., the time / frequency resources on which PRACH is transmitted)). Specifically, signaling on PRACH resources will indicate to the network that the UE supports Msg3 PUSCH repetition and the repetition count on the available time slots for PUSCH repetition. Further, this signaling may include an indication of DMRS bundle or joint channel estimation capabilities, where the transmitter in the UE is capable of maintaining phase continuity across multiple Msg3 PUSCH repetitions.

[0104] Figure 10The call flowchart 1000, which describes the first option described above, is explained below. As shown, the signaling explained in call flowchart 1000 is between the base station or gNB 1002 and the UE 1004. The process or procedure may include configuring PRACH resources (e.g., PRACH preamble or PRACH timing), as shown in box 1006. In some aspects, the procedure in box 1006 may include configuring PRACH resources according to a predetermined configuration to indicate that the UE 1004 is capable of supporting repeated transmissions of the physical channel carrying connection messages (e.g., Msg3PUSCH repetition), and being able to count the available time slots for repeated transmissions of the physical channel.

[0105] In a further aspect, the PRACH resources can be further configured to provide an indication of the UE 1004's ability to perform Joint Channel Estimation (JCE) and / or DMRS bundles. In a particular aspect, this indication can convey to the base station the repetition maintenance phase continuity that the UE can transmit across Msg3 PUSCH. In some other aspects, it is noted that the configuration of the PRACH resources in block 1006 may include selecting a set of PRACH resources, wherein the use of a particular selected set of PRACH resources is configured to provide to the base station 1002 an indication of the repetition of the transmission of the physical channel carrying connection messages by the UE 1004, and a count of the available time slots available for channel transmission. In yet another aspect, the ability of the UE 1004 to implement the procedures in block 1006 may be configured by RRC signaling (not shown) from the network, or alternatively, the UE 1004 may be pre-configured to implement the procedures in block 1006.

[0106] After configuring the PRACH resources in box 1006, UE 1004 uses the configured PRACH resources to transmit PRACH 1008 to the base station or gNB 1002. At base station 1002, the configured PRACH resources are decoded, which in turn conveys the capability indication to base station 1002. Accordingly, the base station will know that UE 1004 is capable of transmitting Msg3 PUSCH repeats and can also count the available UL timeslots for Msg3 PUSCH repeats.

[0107] Similar to combination Figure 4In the process discussed, base station 1002 will send a RAR message (Msg2) 1010 on the PDCCH or PDSCH. In response, UE 1004 will send a connection message (i.e., Msg3 on the PUSCH) to base station 1002. Specifically, if UE 1004 has the capability for Msg3 PUSCH repetition, it will perform retransmission (including transmission) of Msg3. Finally, in the case of a contention-based RACH procedure, base station 1002 will send a contention-resolving Msg4 via PDCCH or PDSCH resources, as shown in 1014.

[0108] In the second option, different capabilities related to Msg3 repetition can be communicated via two or more separate PRACHs, instead of configuring a single PRACH to indicate support for Msg3 repetition. In one example, the first capability can be transmitted using a first PRACH resource (PRACH resource 1), while the second capability can be transmitted using a second PRACH resource. Further, the UE can be configured to transmit a PRACH indicating support for Msg3 repetition via the first PRACH, including indications about the UE's support for repetition on available time slots and repetition counts. The second capability, i.e., the UE's support for DMRS bundle / JCE, can be transmitted via the second PRACH resource.

[0109] As an example of the second option Figure 11 The call flowchart 1100, which explains this option, is explained below. As shown, the signaling explained in call flowchart 1100 is between the base station or gNB 1102 and the UE 1104. The process or procedure may include configuring first and second PRACH resources, as shown in box 1106. The UE 1104 then transmits PRACH resources 1 and 2 to the base station 1102 1108. After receiving the first and second PRACH resources in the base station 1102, the base station 1102 is configured to decode both the first and second PRACH resources, which in turn conveys a capability indication to the base station 1102. Specifically, base station 1102 will know from the first PRACH resource that UE 1104 can send Msg3 PUSCH repeats, and will also be able to count the available UL timeslots for Msg3 PUSCH repeats, and UE 1104 can perform DMRS bundles for Msg3 repeats, so that UE 1104 will maintain phase continuity by transmitting across multiple PUSCH repeats.

[0110] Base station 1102 will send a RAR message (Msg2) 1110 on the PDCCH or PDSCH. In response, UE 1104 will send a connection message (i.e., Msg3 on the PUSCH) to base station 1102. Specifically, if UE 1104 has the capability for Msg3 PUSCH repetition, it will perform retransmission (including transmission) of Msg3. Finally, in the case of contention-based RACH, base station 1102 will send a contention-resolving Msg4 via PDCCH or PDSCH resources, as shown in 1114.

[0111] In the third option, the UE can be configured to use the DMRS uplink configuration for initial Msg3 PUSCH transmission or to indicate the capability of repeated joint channel estimation (JCE) for Msg3 PUSCH transmission via a DMRS transmission port. Regarding the indication via the DMRS transmission port, it should be noted that if there are N transmission ports that can be configured for PUSCH to carry Msg3, some of these ports can be dedicated to indicating JCE (i.e., the UE has JCE capability and will use this capability when transmitting the PUSCH, while the remaining ports of the N ports are used for UEs without JCE capability). It should also be noted that from the network side, the network will perform blind detection based on the transmission port assumption to determine whether the transmitting UE supports JCE.

[0112] In the example of DMRS configuration, the joint channel estimation capability indication can be made by the DMRS sequence via one or more scrambling identifiers or identifiers (IDs) used for UL DMRS scrambling initialization when the communication system utilizes a cyclic prefix OFDM (CP-OFDM) waveform (i.e., transform precoding disabled), or by the nPUSCH identifier parameter when the communication system uses a discrete Fourier transform extended OFDM (DFT-s-OFDM) waveform. The following example of DMRS uplink configuration parameters for CP-OFDM and DFT-s-OFDM waveforms is illustrated in an exemplary UE configuration:

[0113]

[0114] It should be noted further that the DMRS resources used to indicate the UE's capabilities for joint channel estimation can be applied to the first Msg3 repeat, or, on the other hand, to all configured repeats of the initial Msg3 PUSCH transmission.

[0115] On the one hand, it should be noted that the third option discussed above can be used in conjunction with the first option discussed earlier. That is, the configuration of PRACH resources is used to instruct the UE to support Msg3 PUSCH repetition and repetition counting on available uplink time slots, and to indicate the UE's support for joint channel estimation via the DMRS configuration for the initial Msg3 PUSCH transmission or the DMRS transmission port. Figure 10 For example, box 1016 is used to explain the additional instruction means.

[0116] Regarding the above options, note that the Msg3 repetition signaling is indicated for each UE (i.e., by each individual UE in the communication system or for each individual UE in the communication system) or for each frequency band (e.g., indicated for FR1 or FR2). Furthermore, when a UE indicates support for joint channel estimation for Msg3 PUSCH repetition, it may only support a limited number of cases. For example, if a UE indicates support for JCE, the UE may only support back-to-back PUSCH repetition transmissions (i.e., zero gaps between transmissions). Further, if a UE indicates its ability to support JCE, the UE may support non-back-to-back PUSCH repetition transmissions in addition to back-to-back PUSCH transmissions when there are non-zero gaps between transmissions but no other scheduled UL or DL ​​transmissions occur in the gaps. On another front, this capability indication may be signaled when the UE operates in frequency division duplex (FDD) mode in paired spectrum (e.g., a spectrum block in a lower frequency band and an associated spectrum block in a higher frequency band).

[0117] Figure 12 This is a block diagram conceptually illustrating an example hardware implementation of a user equipment (UE) 1200 employing a processing system 1214 according to some aspects of this disclosure. According to various aspects of this disclosure, elements, any part of elements, or any combination of elements can be implemented using a processing system 1204 including one or more processors 1214. In some implementations, the UE 1200 may correspond to... Figure 1 , 2 The UE or any of the scheduled entities shown in any of 4, 10, or 11.

[0118] UE 1200 can be implemented using a processing system 1214 that includes one or more processors 1204. Examples of processors 1204 include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. In various examples, UE 1200 can be configured to perform any or more of the functions described herein. That is, the processor 1200 utilized in UE 1204 can be used to implement any or more of the processes and procedures described below.

[0119] In this example, processing system 1214 can be implemented using a bus architecture generally represented by bus 1202. Depending on the specific application and overall design constraints of processing system 1214, bus 1202 may include any number of interconnect buses and bridges. Bus 1202 communicatively couples together various circuits including one or more processors (generally represented by processor 1204), memory 1205, and computer-readable media (generally represented by computer-readable media 1206). Bus 1202 may also link various other circuits, such as timing sources, peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further. Bus interface 1208 provides an interface between bus 1202 and transceiver 1210, and between bus 1202 and interface 1230. Transceiver 1210 provides a communication interface or means for communicating with various other devices over a wireless transmission medium. In some examples, the wireless communication device may include two or more transceivers 1210, each configured to communicate with a corresponding network type (e.g., terrestrial or non-terrestrial). At least one interface 1230 (e.g., a network interface and / or a user interface) provides a communication interface or means for communicating with various other devices and equipment (e.g., other devices housed within the same device as UE 1200 or other external devices) on an internal bus or via an external transmission medium (such as an Ethernet cable).

[0120] Processor 1204 is responsible for managing bus 1202 and general processing, including the execution of software stored on computer-readable medium 1206. When executed by processor 1204, the software causes processing system 1214 to perform various functions described below for any particular device. Computer-readable medium 1206 and memory 1205 may also be used to store data manipulated by processor 1204 during software execution.

[0121] One or more processors 1204 in the processing system can execute software. Software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. The software may reside on a computer-readable medium 1206.

[0122] Computer-readable medium 1206 may be a non-transient computer-readable medium. As examples, non-transient computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic tapes), optical disks (e.g., compact discs (CDs) or digital multi-purpose discs (DVDs)), smart cards, flash memory devices (e.g., cards, sticks, or key-type drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions accessible and readable by a computer. Computer-readable medium 1206 may reside in processing system 1214, be external to processing system 1214, or be distributed across multiple entities including processing system 1214. Computer-readable medium 1206 may be implemented in a computer program product. As an example, a computer program product may include a computer-readable medium in encapsulation material. Those skilled in the art will recognize how the functionality described throughout this disclosure is best implemented depending on the specific application and the overall design constraints imposed on the system as a whole.

[0123] UE 1200 can be configured to perform any one or more of the operations described herein (e.g., as combined above). Figures 4-11 The description and the following in combination Figure 13 (As described). In some aspects of this disclosure, such as the processor 1200 utilized in UE 1204, the processor 1200 may include circuitry configured for various functions.

[0124] In one aspect, processor 1204 may include communication and processing circuitry system 1241. Communication and processing circuitry system 1241 may include one or more hardware components providing physical structures for performing various processes related to wireless communication (e.g., signal reception and / or signal transmission) as described herein. Communication and processing circuitry system 1241 may further include one or more hardware components providing physical structures for performing various processes related to signal processing (e.g., processing received signals and / or processing signals for transmission) as described herein. In some examples, communication and processing circuitry system 1241 may include two or more transmit / receive chains. Communication and processing circuitry system 1241 may be further configured to execute communication and processing software 1251 included on computer-readable medium 1206 to implement one or more functions described herein.

[0125] Processor 1204 also includes PRACH configuration circuitry 1242, which is configured to configure PRACH resources to indicate Msg3 PUSCH repetition, as discussed herein. PRACH circuitry 1242 may include configuration of PRACH resources to indicate that the UE is capable of supporting: (1) repeated transmission of physical channels carrying connection messages, and (2) counting of available time slots for repeated transmission of physical channels, as discussed herein. Furthermore, PRACH configuration circuitry 1242 may be combined with communication and processing circuitry 1241 and / or transceiver 1210 to use the configured PRACH resources to initiate or cause the transmission of PRACH to network entities (such as base stations or gNBs). PRACH configuration circuitry 1242 may be further configured to execute PRACH configuration software 1252 included on computer-readable medium 1206 to implement one or more of the functions described herein.

[0126] In a further aspect, the PRACH configuration circuitry 1242 can configure PRACH resources to include a first PRACH resource and a second PRACH resource, wherein the first PRACH resource is used to indicate that the UE can support the repeated transmission of connection messages and the counting of available time slots for repeated transmission of uplink channels, while the second PRACH resource is used to indicate that the UE can maintain phase continuity across physical channels.

[0127] Processor 1204 also includes DMRS configuration circuitry 1243, configured to configure DMRS resources to instruct the UE to support joint channel estimation, such as phase continuity maintenance through repeated transmissions across multiple PUSCHs as discussed herein. According to other aspects, DMRS configuration circuitry 1243 may include functionality for configuring DMRS transmission ports to instruct the UE to support joint channel estimation. DMRS configuration circuitry 1243 may be further configured to perform DMRS configuration circuitry 1253 included on computer-readable medium 1206 to implement one or more of the functions described herein.

[0128] Figure 13 This is a flowchart illustrating an example wireless communication method 1300 implemented by a UE according to some aspects of this disclosure. As described herein, some or all of the described features may be omitted in a particular implementation within the scope of this disclosure, and some described features may not be required for implementing all examples. In some examples, method 1300 may be... Figure 12 The method is executed by UE 1200 as explained in the text. In some examples, method 1300 may be executed by any suitable equipment or apparatus for implementing the functions or algorithms described below.

[0129] At block 1302, the UE can configure physical random access channel (PRACH) resources according to a predetermined configuration to indicate that the UE can support: (1) repeated transmission of the physical channel carrying connection messages, and (2) counting of available time slots for repeated transmission of the physical channel. In one aspect, the processing of block 1302 can be implemented by means for configuring PRACH resources, which can be implemented by processor 1204 and, in a particular aspect, by PRACH configuration circuitry 1242 or its equivalent.

[0130] Further, at block 1304, the UE can transmit PRACH to a network entity using configured PRACH resources. In one aspect, note that PRACH resources include PRACH preambles or PRACH timings that include time and frequency resources. In another aspect, the process in block 1304 can be implemented by means for PRACH transmission, which may be implemented by processor 1204 and, in a particular aspect, by PRACH configuration circuitry 1242, communication and processing circuitry 1241, and / or transceiver 1210, or their equivalents.

[0131] Further, method 1300 may include configuring PRACH resources according to a predetermined configuration, including selecting a set of PRACH resources, wherein the specific selected set of PRACH resources is configured to provide an indication of the ability to perform repeated transmissions of the physical channel for carrying connection messages by the UE and a count of available time slots available for transmission on the physical channel. In some other aspects, configuring PRACH resources according to a predetermined configuration further indicates that the UE is able to maintain phase continuity across repeated transmissions of the physical channel carrying connection messages. In yet another aspect, the connection message includes a message 3 (Msg3) message and includes one or more of a radio resource connection request, a scheduling request, or a buffer state.

[0132] Additionally, method 1300 may include each repetition in a repetitive transmission of PUSCH having the same symbol allocation in each time slot in which the repetition is transmitted.

[0133] In other aspects, method 1300 may include PRACH resources including a first PRACH resource and a second PRACH resource, wherein the first PRACH resource is used to indicate that the UE can support the repeated transmission of connection messages and the counting of available time slots for repeated transmission of uplink channels, and the second PRACH resource is used to indicate that the UE can maintain phase continuity across physical channels.

[0134] Method 1300 may further include signaling a capability indication per UE; for example, each UE in a communication system signals its own capability indication. In other aspects, method 1300 may include signaling the capability indication for the frequency band of transmission for each physical channel. In various examples, the frequency band is FR1 or FR2.

[0135] Method 1300 may further include a capability indication being applied to back-to-back repeated transmissions of the physical channel, wherein there is no time gap between repeated transmissions. Additionally, the capability indication is further applied to non-back-to-back repeated transmissions of the physical channel, wherein a time gap occurs between transmissions, during which no other scheduled uplink or downlink transmission occurs. Furthermore, the capability indication is signaled when the UE operates in frequency division duplex (FDD) mode in the paired spectrum.

[0136] In other aspects, method 1300 may include configuring a demodulation reference signal (DMRS) configuration or DMRS transmission port at least for the initial transmission of the physical channel carrying the connection message, the DMRS configuration or DMRS transmission port indicating that the UE can maintain phase continuity across repetitions of the physical channel; and

[0137] Based on this configuration, at least the physical channel is transmitted to the network entity. In one example, the DMRS configuration includes a DMRS sequence having at least one scrambling identifier (ID) for a first type of waveform used in a communication system in which the UE can operate. Furthermore, the first type of waveform is a Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM) waveform, and the DMRS configuration includes a DMRS sequence identified by a parameter nPUSCH, which is configured to a specific value for a second type of waveform used in a communication system in which the UE can operate. Further, the second type of waveform is a Discrete Fourier Transform Extended OFDM (DFT-s-OFDM) waveform, where the DMRS indication is applied to the first repeated transmission of the initial uplink channel transmission. Additionally, the DMRS indication is applied to multiple repeated transmissions of the initial uplink channel transmission. Furthermore, the DMRS indication is applied to all repeated transmissions of the initial uplink channel transmission.

[0138] Figure 14 This is a block diagram conceptually illustrating an example of a hardware implementation of a network node or entity 1400 employing a processing system 1414 according to some aspects of this disclosure. According to various aspects of this disclosure, elements, any part of elements, or any combination of elements can be implemented using a processing system 1414 including one or more processors 1404. In some implementations, network entity 1400 may correspond to... Figure 1 , 2 Any of the BS (e.g., gNB, eNBs, etc.) or scheduling entity shown in any of 4, 10, or 11. In a further aspect, network entity 1400 can be configured as a base station capable of operating within an Open RAN (O-RAN) environment, wherein the base station (e.g., 1400) is decomposed and comprises different parts, including distributed units (DUs), centralized units (CUs), and radio units (RUs). In yet another further aspect, the processing portion of the disclosed and explained network entity 1400 can be implemented within the RUs, DUs, and / or CUs, or within a portion of each.

[0139] Network entity 1400 may be implemented using a processing system 1414 including one or more processors 1404. Examples of processors 1404 include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. In various examples, network entity 1400 may be configured to perform any or more of the functions described herein. That is, the processor 1404 utilized in network entity 1400 may be used to implement any or more of the processes and procedures described herein.

[0140] In this example, processing system 1414 can be implemented using a bus architecture generally represented by bus 1402. Depending on the specific application and overall design constraints of processing system 1414, bus 1402 may include any number of interconnect buses and bridges. Bus 1402 communicatively couples together various circuits including one or more processors (generally represented by processor 1404), memory 1405, and computer-readable media (generally represented by computer-readable media 1406). Bus 1402 may also link various other circuits, such as timing sources, peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further. Bus interface 1408 provides an interface between bus 1402 and transceiver 1410, and between bus 1402 and interface 1430. Transceiver 1410 provides a communication interface or means for communicating with various other devices over a wireless transmission medium. In some examples, the wireless communication device may include two or more transceivers 1410, each configured to communicate with a corresponding network type (e.g., terrestrial or non-terrestrial). At least one interface 1430 (e.g., a network interface and / or a user interface) provides a communication interface or means for communicating with various other devices and equipment (e.g., other devices housed within the same device as network entity 1400 or other external devices) over an internal bus or external transmission medium (such as an Ethernet cable).

[0141] Processor 1404 is responsible for managing bus 1402 and general processing, including the execution of software stored on computer-readable medium 1406. When executed by processor 1404, the software causes processing system 1414 to perform various functions described below for any particular device. Computer-readable medium 1406 and memory 1405 may also be used to store data manipulated by processor 1404 during software execution.

[0142] One or more processors 1404 in the processing system can execute software. Software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. Software may reside on computer-readable media 1406.

[0143] Computer-readable medium 1406 may be a non-transient computer-readable medium. As examples, non-transient computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic tapes), optical disks (e.g., compact discs (CDs) or digital multi-purpose discs (DVDs)), smart cards, flash memory devices (e.g., cards, sticks, or key-type drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions accessible and readable by a computer. Computer-readable medium 1406 may reside in processing system 1414, be external to processing system 1414, or be distributed across multiple entities including processing system 1414. Computer-readable medium 1406 may be implemented in a computer program product. As an example, a computer program product may include a computer-readable medium in encapsulation material. Those skilled in the art will recognize how the functionality described throughout this disclosure is best implemented depending on the specific application and the overall design constraints imposed on the system as a whole.

[0144] Network entity 1400 can be configured to perform any one or more of the operations described herein (e.g., as combined above). Figures 4-11 The description and the following in combination Figure 15 (As described). In some aspects of this disclosure, such as the processor 1400 utilized in network entity 1404, circuitry may be configured for various functions.

[0145] Processor 1404 can be configured to generate, schedule, and modify resource assignments or grants to time-frequency resources (e.g., a set of one or more resource elements). For example, processor 1404 can schedule time-frequency resources within multiple time-division duplex (TDD) and / or frequency-division duplex (FDD) subframes, time slots, and / or mini-time slots to carry user data traffic and / or control information to and / or from multiple UEs.

[0146] Processor 1404 may be configured to schedule resources for the transmission of downlink reference signals (e.g., SSB or CSI-RS) or DCI (or SRS triggering) on ​​multiple downlink beams of a downlink beam sweep, based on the selected downlink beam sweep type and the number of selected downlink reference signal resources indicated in an uplink beam refinement request received from the UE. Processor 1404 may be further configured to schedule resources for uplink transmission of uplink reference signals (e.g., SRS) on multiple uplink beams of a downlink beam sweep, based on the selected beam sweep type and the number of selected uplink reference signal resources indicated in the request. Processor 1404 may be further configured to schedule resources that the UE can use to transmit the requested information. For example, uplink beam refinement request resources may include resources scheduled for the transmission of PUCCH, PUSCH, PRACH timing, or RRC messages. In some examples, processor 1404 may be configured to schedule PUSCH resources for uplink beam refinement requests in response to receiving a scheduling request from the UE.

[0147] Processor 1404 may be further configured to schedule resources for the transmission of uplink signals. In some examples, based on an indication of an uplink signal associated with one or more uplink transmit beams included in the request, resources may be associated with one or more uplink transmit beams and one or more corresponding receive beams applied to the uplink signal (e.g., based on an uplink BPL). In some examples, resources may be associated with an indication of the number of uplink transmit beams to be used for the uplink signal, the number of repetitions of each uplink transmit beam of the uplink signal, and a multiplexing scheme when more than one uplink transmit beam is used to transmit the uplink signal.

[0148] Processor 1404 may include communication and processing circuitry system 1441. Communication and processing circuitry system 1441 may include one or more hardware components providing a physical structure for performing various processes related to wireless communication (e.g., signal reception and / or signal transmission) as described herein. Communication and processing circuitry system 1441 may further include one or more hardware components providing a physical structure for performing various processes related to signal processing (e.g., processing received signals and / or processing signals for transmission) as described herein. In some examples, communication and processing circuitry system 1441 may include two or more transmit / receive chains. Communication and processing circuitry system 1441 may be further configured to execute communication and processing software 1451 included on computer-readable medium 1406 to implement one or more functions described herein.

[0149] In some other examples, the communication and processing circuitry system 1441 can be configured to convey higher-level information, such as RRC configuration information, to the UE. For example, the communication and processing circuitry system 1441 can convey RRC parameters to the UE, which are used in accordance with this document. Figures 4-11 The process disclosed in section 13 determines the PRACH resource or DMRS configuration.

[0150] Processor 1404 may further include PRACH decoding circuitry 1442, configured to process, receive, demodulate, interpret, and / or decode PRACH resources configured and transmitted by the UE (e.g., UE 1200). Circuitry 1442 may be configured to decode the received PRACH resources and establish, from the PRACH resources, that the transmitting UE supports Msg3 PUSCH repetition and repetition counting for available uplink time slots. Additionally, in some aspects, PRACH decoding circuitry 1442 may be configured to decode or interpret PRACH resources to determine whether the UE supports DMRS bundle / JCE. Furthermore, PRACH decoding circuitry 1442 may be configured to, in conjunction with this document… Figure 4-11 The PRACH decoding circuitry 1442 may be further configured to execute the PRACH decoding software 1452 included on the computer-readable medium 1406 to perform one or more of the functions described herein.

[0151] In some further examples, processor 1404 may further include DMRS configuration decoding circuitry 1443, configured to decode or interpret the UE's DMRS configuration to determine whether the UE supports joint channel estimation for Msg3 PUSCH repetition. In other aspects, DMRS configuration decoding circuitry 1443 may be configured to decode and / or interpret whether the UE has Msg3 PUSCH repetition joint channel estimation capability based on the DMRS transmission port as previously discussed. In yet another aspect, DMRS configuration decoding circuitry 1443 may determine or interpret whether the DMRS resource indication applies to the first repetition of Msg3 or to all configured repetitions of the initial Msg3 PUSCH transmission. DMRS configuration decoding circuitry 1443 may be further configured to execute DMRS configuration decoding software 1453 included on computer-readable medium 1406 to implement one or more of the functions described herein.

[0152] Figure 15This is a flowchart illustrating an example wireless communication method 1500 according to some aspects of this disclosure. As described herein, some or all of the described features may be omitted in a particular implementation within the scope of this disclosure, and some described features may not be required for implementing all examples. In some examples, method 1500 may be... Figure 14 The method is performed by the network entity 1400 described herein (e.g., a gNB or base station including a base station operable in an O-RAN environment). In some examples, method 1500 may be performed by any suitable equipment or apparatus for implementing the functions or algorithms described below.

[0153] At block 1502, method 1500 includes processing a Physical Random Access Channel (PRACH) resource received from the UE, wherein the PRACH resource is configured according to a predetermined configuration to provide an indication of the UE's ability to support: (1) repeated transmission of the physical channel carrying a connection message, and (2) counting of available time slots for repeated transmission of the physical channel. In one aspect, the process at block 1502 can be implemented by means for receiving the PRACH, which may be implemented by processor 1404 and, in certain aspects, by processing circuitry system 1441 and transceiver 1410 or their equivalents.

[0154] Additionally, method 1500 includes decoding (or interpreting) the received PRACH, as shown in block 1504. In one aspect, the process of block 1504 can be implemented by means for decoding or interpreting the PRACH, which can be implemented by processor 1404 and, in a particular aspect, by PRACH decoding circuitry system 1442 or its equivalent.

[0155] It should be further noted that this disclosure may include the following further aspects.

[0156] Aspect 1: A user equipment (UE) including a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory, wherein the processor is configured to: configure physical random access channel (PRACH) resources according to a predetermined configuration to indicate that the UE can support: repeated transmission of physical channels carrying connection messages and counting of available time slots for repeated transmission of physical channels; and transmit PRACH to a network entity using the configured PRACH resources.

[0157] Aspect 2: The UE as described in Aspect 1, wherein the PRACH resources include a PRACH preamble or a PRACH timing that includes time and frequency resources, and the physical channel includes the Physical Uplink Shared Channel (PUSCH).

[0158] Aspect 3: The UE as in Aspect 1 or Aspect 2, wherein the processor is further configured to: configure PRACH resources according to a predetermined configuration by selecting a PRACH resource set, wherein the selected PRACH resource set is configured to provide an indication of repeated transmissions of the physical channel for carrying connection messages by the UE and a count of available time slots available for transmission on the physical channel.

[0159] Aspect 4: UEs of any of Aspects 1 to 3, wherein the PRACH resource is further configured as a capability indicator that indicates that the UE is able to maintain phase continuity across repeated transmissions of physical channels carrying connection messages.

[0160] Aspect 5: The UE of aspect 4, wherein the UE is configured to apply capability indication to back-to-back repeated transmissions of the physical channel, wherein there is no time gap between repeated transmissions.

[0161] Aspect 6: UE as in Aspect 4 or 5, wherein the UE is configured to further apply capability indication to non-back-to-back repeated transmissions of the physical channel, wherein time gaps occur between transmissions, during which no other scheduled uplink or downlink transmissions occur.

[0162] Aspect 7: A UE such as any of Aspects 4 to 6, wherein the UE is configured to signal a capability indication when the UE is operating in frequency division duplex (FDD) mode in the paired spectrum.

[0163] Aspect 8: UEs of any of Aspects 1 to 7, wherein each repetition in the repeated transmission of the physical channel has the same symbol allocation in each time slot in which the repetition is transmitted.

[0164] Aspect 9: The UE of any of Aspects 1 to 8 further includes: PRACH resources including a first PRACH resource and a second PRACH resource, wherein the first PRACH resource is used to indicate that the UE can support the repeated transmission of connection messages and the counting of available time slots for repeated transmission of uplink channels, and the second PRACH resource is used to indicate that the UE can maintain phase continuity across physical channels.

[0165] Aspect 10: A UE as described in any of Aspects 1 to 9, wherein the processor is further configured to: configure a demodulation reference signal (DMRS) configuration or a DMRS transmission port, at least for the initial transmission of a physical channel carrying a connection message, the DMRS configuration or DMRS transmission port indicating that the UE can maintain phase continuity across repeated physical channels; and transmit at least the physical channel to a network entity based on the configuration.

[0166] Aspect 11: The UE of aspect 10, wherein the DMRS configuration includes: a first DMRS sequence having at least one scrambling identifier (ID) for a first type of waveform used in a communication system in which the UE can operate; and a second DMRS sequence having an identity parameter having specific values ​​configured for a second type of waveform used in the communication system.

[0167] Aspect 12: A method for wireless communication in a user equipment (UE), comprising: configuring physical random access channel (PRACH) resources according to a predetermined configuration to provide a capability indication indicating that the UE is capable of supporting: repeated transmission of a physical channel carrying a connection message and counting of available time slots for repeated transmission of the physical channel; and transmitting PRACH to a network entity using the configured PRACH resources.

[0168] Aspect 13: The method of aspect 12, wherein the PRACH resource includes a PRACH preamble or a PRACH timing that includes time and frequency resources.

[0169] Aspect 14: The method of aspect 12 or 13, wherein configuring PRACH resources according to a predetermined configuration includes selecting a set of PRACH resources, wherein the selected set of PRACH resources is configured to provide an indication of repeated transmissions of physical channels configured by the UE to carry connection messages and a count of available time slots available for transmission on the physical channels.

[0170] Aspect 15: The method of any of Aspects 12 to 13, wherein the PRACH resource configured according to a predetermined configuration is further configured to provide a capability indication for indicating that the UE is able to maintain phase continuity across repeated transmissions of physical channels carrying connection messages.

[0171] Aspect 16: The method of any of Aspects 12 to 15, wherein the physical channel includes the Physical Uplink Shared Channel (PUSCH).

[0172] Aspect 17: The method of any of Aspects 12 to 16, wherein each repetition in the repetition transmission of PUSCH has the same symbol allocation in each time slot in which the repetition is transmitted.

[0173] Aspect 18: The method of any of Aspects 12 to 17, wherein the PRACH resource further comprises: a first PRACH resource configured to indicate that the UE is capable of supporting repeated transmission of connection messages and counting of available time slots for repeated transmission of uplink channels; and a second PRACH resource configured to indicate that the UE is capable of maintaining phase continuity across physical channels.

[0174] Aspect 19: The method of any of Aspects 12 to 18, wherein the capability indicates that each UE, each UE in the wireless communication system, or each frequency band for transmission of the physical channel sends a signal notification.

[0175] Aspect 20: The method of any of Aspects 12 to 19, wherein the capability indication is applied to back-to-back repeated transmissions of the physical channel, wherein there is no time gap between repeated transmissions.

[0176] Aspect 21: The method of any of Aspects 12 to 20, wherein the capability indication is further applied to non-back-to-back repeated transmissions of the physical channel, wherein time gaps occur between transmissions, during which no other scheduled uplink or downlink transmissions occur.

[0177] Aspect 22: The method of any of Aspects 12 to 21 further includes: configuring a demodulation reference signal (DMRS) configuration or a DMRS transmission port at least for the initial transmission of a physical channel carrying a connection message, the DMRS configuration or DMRS transmission port indicating that the UE can repeatedly maintain phase continuity across the physical channel; and transmitting at least the physical channel to a network entity based on the configuration.

[0178] Aspect 23: The method of aspect 22, wherein the DMRS configuration includes: a first DMRS sequence having at least one scrambling identifier (ID) for a first type of waveform used in a communication system in which the UE can operate; and a second DMRS sequence having an identity parameter having specific values ​​configured for a second type of waveform used in the communication system.

[0179] Aspect 24: The method of either Aspect 22 or 23, wherein the DMRS indication is applied to one of the following: a first repeated transmission of the initial uplink channel transmission; a plurality of repeated transmissions of the initial uplink channel transmission; or all repeated transmissions of the initial uplink channel transmission.

[0180] Aspect 25: The method of any of Aspects 22 to 24 further includes: selectively applying a configured DMRS or DMRS port for timing of repeated transmissions of connection messages, wherein there is no time gap between repeated transmissions.

[0181] Aspect 26: The method of any of Aspects 22 to 25 further includes: selectively applying a configured DMRS or DMRS port for timing of repeated transmissions of connection messages, wherein time gaps occur between transmissions, during which no other scheduled uplink or downlink transmissions occur.

[0182] Aspect 27: A base station comprising: a processor configured to: process a Physical Random Access Channel (PRACH) using PRACH resources from a User Equipment (UE), wherein the PRACH resources are configured according to a predetermined configuration to provide a capability indication indicating that the UE is capable of supporting: repeated transmission of a physical channel carrying a connection message and counting of available time slots for repeated transmission of the physical channel; and decoding the PRACH to determine the capability indication; wherein the PRACH resources include a PRACH preamble or a PRACH timing including time and frequency resources, and the connection message includes a Message 3 (Msg3) message containing one or more of a radio resource connection request, a scheduling request, or a buffer state.

[0183] Aspect 28: A base station as described in Aspect 27, wherein the processor is further configured to: process at least a demodulation reference signal (DMRS) configuration or DMRS transmission port for the initial transmission of a physical channel carrying a connection message, the DMRS configuration or DMRS transmission port indicating that the UE is capable of repeatedly maintaining phase continuity across the physical channel; and decode the DMRS configuration or interpret the DMRS transmission port to determine that the UE is capable of repeatedly maintaining phase continuity across the physical channel.

[0184] Aspect 29: A method for conducting wireless communication in a base station, comprising: processing a PRACH using physical random access channel (PRACH) resources from a user equipment (UE), wherein the PRACH resources are configured according to a predetermined configuration to provide a capability indication indicating that the UE is capable of supporting: repeated transmission of a physical channel carrying a connection message and counting of available time slots for repeated transmission of the physical channel; and decoding the PRACH to determine the capability indication; wherein the PRACH resources include a PRACH preamble or a PRACH timing including time and frequency resources, and the connection message includes a Message 3 (Msg3) message containing one or more of a radio resource connection request, a scheduling request, or a buffer state.

[0185] Aspect 30: The method of aspect 29 further includes: processing a demodulation reference signal (DMRS) configuration or DMRS transmission port for at least the initial transmission of a physical channel carrying a connection message, the DMRS configuration or DMRS transmission port indicating that the UE is capable of repeatedly maintaining phase continuity across the physical channel; and decoding the DMRS configuration or interpreting the DMRS transmission port to determine that the UE is capable of repeatedly maintaining phase continuity across the physical channel.

[0186] Aspect 31: A device configured for wireless communication includes at least one means for performing a method as described in aspects 12 to 26 or any of aspects 29 and 30.

[0187] Aspect 32: A non-transient computer-readable medium storing computer-executable code, the computer-executable code including code for causing a device to perform a method such as that of aspects 12 to 26 or aspects 29 and 30.

[0188] Several aspects of wireless communication networks have been illustrated with reference to examples. As will be readily apparent to those skilled in the art, the various aspects described herein can be extended to other telecommunications systems, network architectures, and communication standards.

[0189] As examples, various aspects can be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile Communications (GSM). These aspects can also be extended to systems defined by 3GPP2, such as CDMA2000 and / or Evolved Data Optimized (EV-DO). Other examples can be implemented within systems employing IEEE standards IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunications standards, network architecture, and / or communication standards employed will depend on the specific application and the overall design constraints imposed on the system.

[0190] Within this disclosure, the term "exemplary" is used to mean "serving as an example, instance, or illustration." Any implementation or aspect described herein as "exemplary" is not necessarily to be construed as superior to or better than other aspects of this disclosure. Similarly, the term "aspect" does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed. The term "coupled" is used herein to refer to direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, then objects A and C can still be considered coupled to each other—even if they are not in direct physical contact. For example, a first object can be coupled to a second object, even if the first object never physically contacts the second object. The terms "circuit" and "circuit system" are used broadly and are intended to include both hardware implementations of electronic devices and conductors, and software implementations of information and instructions, which, when connected and configured, enable the performance of the functions described in this disclosure without limitation on the type of electronic circuit, and which, when executed by a processor, enable the performance of the functions described in this disclosure. As used herein, the term "determine" covers a wide variety of actions. For example, "determine" can include calculation, computation, processing, derivation, investigation, search (e.g., searching in a table, database, or other data structure), confirmation, parsing, selection, choosing, creation, receiving (e.g., receiving information), access (e.g., accessing data in memory), etc.

[0191] Figures 1-15 One or more of the components, steps, features and / or functions described herein may be rearranged and / or combined into a single component, step, feature or function, or implemented in several components, steps or functions. Additional elements, components, steps, and / or functions may also be added without departing from the novel features disclosed herein. Figures 1-15 The apparatus, device, and / or component described herein can be configured to perform one or more methods, features, or steps as described herein. The novel algorithms described herein can also be efficiently implemented in software and / or embedded in hardware.

[0192] It should be understood that the specific order or hierarchy of the steps in the disclosed methods is an illustration of the exemplary process. Based on design preferences, it will be understood that the specific order or hierarchy of the steps in these methods can be rearranged. The appended method claims present the elements of the various steps in an exemplary order and are not intended to be limited to the specific order or hierarchy presented, unless specifically stated herein.

[0193] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will readily be understood by those skilled in the art, and the universal principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be granted the full scope consistent with the language of the claims, wherein references to the singular form of an element are not intended to mean “one and only one”—unless specifically stated otherwise—but are intended to mean “one or more.” Unless specifically stated otherwise, the term “some / a” refers to one or more. The phrase “at least one of” referring to a list of items refers to any combination of these items, including a single member. As an example, “at least one of a, b, or c” is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the aspects described throughout this disclosure that are currently or hereafter known to a person skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be donated to the public, whether or not such disclosure is expressly stated in the claims.

Claims

1. A user equipment (UE), comprising: transceiver; Memory; as well as A processor communicatively coupled to the transceiver and the memory, wherein the processor is configured to: Configure the Physical Random Access Channel (PRACH) resources according to a predetermined configuration to indicate that the UE can support: Repeated transmission of physical channels carrying connection messages, and A count of the available time slots for the repeated transmissions used in the physical channel; as well as Use the configured PRACH resources to send PRACH to network entities. The PRACH resource is further configured as a capability indicator, which is used to indicate that the UE is able to maintain phase continuity across repeated transmissions of the physical channel carrying the connection message.

2. The UE as claimed in claim 1, wherein the PRACH resources include a PRACH preamble or a PRACH timing that includes time and frequency resources, and the physical channel includes a Physical Uplink Shared Channel (PUSCH).

3. The UE of claim 1, wherein the processor is further configured to: The PRACH resources are configured according to the predetermined configuration by selecting a PRACH resource set, wherein the selected PRACH resource set is configured to provide an indication of repeated transmissions of the physical channel for which the UE is configured to carry the connection message and a count of available time slots available for transmission on the physical channel.

4. The UE of claim 1, wherein the UE is configured to apply the capability indication to back-to-back repeated transmissions of the physical channel, wherein there is no time gap between the repeated transmissions.

5. The UE of claim 4, wherein the UE is configured to further apply the capability indication to non-back-to-back repeated transmissions of the physical channel, wherein time gaps occur between transmissions, and no other scheduled uplink or downlink transmissions occur during the time gaps.

6. The UE of claim 4, wherein the UE is configured to signal the capability indication when the UE is operating in frequency division duplex (FDD) mode in a paired spectrum.

7. The UE of claim 1, wherein each repetition in the repeated transmission of the physical channel has the same symbol allocation in each time slot in which the repetition is transmitted.

8. The UE of claim 1, further comprising: The PRACH resources include a first PRACH resource and a second PRACH resource, wherein the first PRACH resource is used to indicate that the UE can support the repeated transmission of the connection message and the counting of available time slots for repeated transmission of the uplink channel, and the second PRACH resource is used to indicate that the UE can maintain phase continuity across the physical channel.

9. The UE of claim 1, wherein the processor is further configured to: At least for the initial transmission of the physical channel carrying the connection message, a demodulation reference signal (DMRS) configuration or DMRS transmission port is configured, the DMRS configuration or DMRS transmission port indicating that the UE can maintain phase continuity across repetitions of the physical channel; and Based on the configuration, at least the physical channel is transmitted to the network entity.

10. The UE of claim 9, wherein the DMRS configuration includes: The first DMRS sequence has at least one scrambling identifier (ID) for a first type of waveform used in the communication system in which the UE can operate. as well as The second DMRS sequence has identity parameters with specific values ​​configured for use in the communication system for a second type of waveform.

11. A method for conducting wireless communication in a user equipment (UE), comprising: Configure the Physical Random Access Channel (PRACH) resources according to a predetermined configuration to provide a capability indication indicating that the UE can support: Repeated transmission of physical channels carrying connection messages, and A count of the available time slots for the repeated transmissions used in the physical channel; as well as Use the configured PRACH resources to send PRACH to network entities. The PRACH resource is further configured as a capability indicator, which is used to indicate that the UE is able to maintain phase continuity across repeated transmissions of the physical channel carrying the connection message.

12. The method of claim 11, wherein the PRACH resource includes a PRACH preamble or a PRACH timing that includes time and frequency resources.

13. The method of claim 11, wherein configuring the PRACH resources according to the predetermined configuration includes selecting a set of PRACH resources, wherein the selected set of PRACH resources is configured to provide an indication of repeated transmissions of the physical channel for which the UE is configured to carry the connection message and a count of available time slots available for transmission on the physical channel.

14. The method of claim 11, wherein the physical channel includes the Physical Uplink Shared Channel (PUSCH).

15. The method of claim 14, wherein each repetition in the repeated transmission of the PUSCH has the same symbol allocation in each time slot in which the repetition is transmitted.

16. The method of claim 11, wherein the PRACH resource further comprises: The first PRACH resource is configured to indicate that the UE is capable of supporting repeated transmission of the connection message, and to count the available time slots for repeated transmission of the uplink channel. as well as The second PRACH resource is configured to instruct the UE to maintain phase continuity across physical channels.

17. The method of claim 11, wherein the capability indication is signaled to each UE, by each UE in the wireless communication system, or for each frequency band of the transmission of the physical channel.

18. The method of claim 11, wherein the capability indication is applied to back-to-back repeated transmissions of the physical channel, wherein there is no time gap between the repeated transmissions.

19. The method of claim 18, wherein the capability indication is further applied to non-back-to-back repeated transmissions of the physical channel, wherein time gaps occur between transmissions, during which no other scheduled uplink or downlink transmissions occur.

20. The method of claim 11, further comprising: At least for the initial transmission of the physical channel carrying the connection message, a demodulation reference signal (DMRS) configuration or DMRS transmission port is configured, the DMRS configuration or DMRS transmission port indicating that the UE can maintain phase continuity across repetitions of the physical channel; as well as Based on the configuration, at least the physical channel is transmitted to the network entity.

21. The method of claim 20, wherein the DMRS configuration includes: The first DMRS sequence has at least one scrambling identifier (ID) for a first type of waveform used in the communication system in which the UE can operate. as well as The second DMRS sequence has identity parameters with specific values ​​configured for use in the communication system for a second type of waveform.

22. The method of claim 20, wherein the DMRS indication is applied to one of the following: The first repeated transmission of the initial uplink channel transmission; Multiple repeated transmissions of the initial uplink channel transmission; or All repeated transmissions of the initial uplink channel transmission.

23. The method of claim 20, further comprising: For the timing of the repeated transmission of the connection message, including the back-to-back repeated transmission of the connection message, a configured DMRS or DMRS port is selectively applied, wherein there is no time gap between the repeated transmissions.

24. The method of claim 20, further comprising: For the timing of repeated transmissions of the connection message, including non-back-to-back repeated transmissions of the connection message, a configured DMRS or DMRS port is selectively applied, wherein time gaps occur between transmissions, during which no other scheduled uplink or downlink transmissions occur.

25. A network entity, comprising: The processor is configured to: The PRACH is processed using Physical Random Access Channel (PRACH) resources from the User Equipment (UE), wherein the PRACH resources are configured according to a predetermined configuration to provide an indication of the UE's ability to support the following: Repeated transmission of physical channels carrying connection messages, and A count of the available time slots for the repeated transmissions used in the physical channel; as well as Decode the PRACH to determine the capability indication; The PRACH resources mentioned therein include PRACH preambles or PRACH timings that include time and frequency resources, and the connection messages include Message 3 (Msg3) messages that contain one or more of the following: radio resource connection requests, scheduling requests, or buffer states. The PRACH resource is further used to instruct the UE to maintain phase continuity across repeated transmissions of the physical channel carrying the connection message.

26. The network entity of claim 25, wherein the processor is further configured to: Processing at least a demodulation reference signal (DMRS) configuration or DMRS transmission port for the initial transmission of the physical channel carrying the connection message, the DMRS configuration or DMRS transmission port indicating that the UE can maintain phase continuity across repetitions of the physical channel; and Decode the DMRS configuration or interpret the DMRS transmission port to determine whether the UE can repeatedly maintain phase continuity across the physical channel.

27. A method for conducting wireless communication in a network entity, comprising: The PRACH is processed using Physical Random Access Channel (PRACH) resources from the User Equipment (UE), wherein the PRACH resources are configured according to a predetermined configuration to provide an indication of the UE's ability to support the following: Repeated transmission of physical channels carrying connection messages, and A count of the available time slots for the repeated transmissions used in the physical channel; as well as Decode the PRACH to determine the capability indication; The PRACH resources mentioned therein include PRACH preambles or PRACH timings that include time and frequency resources, and the connection messages include Message 3 (Msg3) messages that contain one or more of the following: radio resource connection requests, scheduling requests, or buffer states. The PRACH resource is further used to instruct the UE to maintain phase continuity across repeated transmissions of the physical channel carrying the connection message.

28. The method of claim 27, further comprising: Processing at least a demodulation reference signal (DMRS) configuration or DMRS transmission port for the initial transmission of the physical channel carrying the connection message, the DMRS configuration or DMRS transmission port indicating that the UE can maintain phase continuity across repetitions of the physical channel; as well as Decode the DMRS configuration or interpret the DMRS transmission port to determine whether the UE can repeatedly maintain phase continuity across the physical channel.

Images