Implicit PRACH repetition indication

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive a plurality of synchronization signal block transmissions associated with a random access procedure. The UE may transmit a number of first random access messages, wherein the number of first random access messages is based on a random access channel format associated with the random access procedure, a configured number of uplink shared channel random access message repetitions, or both. The UE may monitor a second random access message based at least in part on the number of first random access messages.

Description

Technical Field

[0001] The following relates to wireless communication, including implicit PRACH repetition indication. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, and so on. These systems can be capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multi-access systems include fourth-generation (4G) systems (such as Long-Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ techniques such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multi-access communication system may include one or more base stations, each of which supports wireless communication for communication devices, which may be referred to as User Equipment (UE).

[0003] In some wireless communication systems, a wireless device may send repetitions of a random access message. However, such methods can be improved. Summary of the Invention

[0004] The described techniques relate to improved methods, systems, devices, and apparatuses that support implicit random access repetition indication. A User Equipment (UE) may receive a plurality of Synchronization Signal Block transmissions associated with a random access procedure. The UE may send a certain number of first random access messages, where the number of the first random access messages is based on a random access channel format associated with the random access procedure, a configured number of uplink shared channel random access message repetitions, or both. The UE may monitor a second random access message at least in part based on the number of the first random access messages.

[0005] A method for wireless communication at a User Equipment (UE) is described. The method may include: receiving a set of a plurality of Synchronization Signal Block transmissions associated with a random access procedure; sending a certain number of first random access messages, where the number of the first random access messages is based on a random access channel format associated with the random access procedure, a configured number of uplink shared channel random access message repetitions, or both; and monitoring a second random access message based on the number of the first random access messages.

[0006] Describes an apparatus for wireless communication at a UE. The apparatus may include: a processor; a memory coupled to the processor; and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive a set of multiple synchronization signal block transmissions associated with a random access procedure; transmit a number of first random access messages, where the number of first random access messages is based on a random access channel format associated with the random access procedure, a configured number of uplink shared channel random access message repetitions, or both; and monitor a second random access message based on the number of first random access messages.

[0007] Describes another apparatus for wireless communication at a UE. The apparatus may include: means for receiving a set of multiple synchronization signal block transmissions associated with a random access procedure; means for transmitting a number of first random access messages, where the number of first random access messages is based on a random access channel format associated with the random access procedure, a configured number of uplink shared channel random access message repetitions, or both; and means for monitoring a second random access message based on the number of first random access messages.

[0008] Describes a non-transitory computer-readable medium storing code for wireless communication at a UE. The code may include instructions executable by a processor to: receive a set of multiple synchronization signal block transmissions associated with a random access procedure; transmit a number of first random access messages, where the number of first random access messages is based on a random access channel format associated with the random access procedure, a configured number of uplink shared channel random access message repetitions, or both; and monitor a second random access message based on the number of first random access messages.

[0009] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the number of first random access messages may be based on the length of the random access channel format.

[0010] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the number of first random access messages may be equal to the configured number of uplink shared channel random access message repetitions.

[0011] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the number of first random access messages may be based on the number of uplink shared channel random access repetitions and the random access channel format.

[0012] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the number of the first random access messages may be less than the configured number of uplink shared channel random access repetitions based on the random access channel format.

[0013] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for performing the following actions: receiving control signaling indicating the configured number of uplink shared channel random access message repetitions.

[0014] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the control signaling includes a random access response uplink grant or downlink control information.

[0015] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the number of uplink shared channel random access message repetitions may be the default number of uplink shared channel random access message repetitions.

[0016] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the number of the first random access messages for initial access may be based on the configured number of uplink shared channel random access message repetitions associated with the initial access.

[0017] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the number of the first random access messages for retransmission may be based on the configured number of uplink shared channel random access message repetitions associated with initial access or retransmission.

[0018] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the number of the first random access messages for retransmission may be at least partially based on the configured number of uplink shared channel random access message repetitions, which may be the maximum number, minimum number, or statistical number associated with a first configured number of uplink shared channel random access message repetitions for initial access and a second configured number of uplink shared channel random access message repetitions for retransmission.

[0019] Disclosed is a method for wireless communication at a network node. The method may include: transmitting a set of multiple synchronization signal blocks associated with a random access procedure; receiving a number of first random access messages, wherein the number of the first random access messages is based on a random access channel format associated with the random access procedure, a configured number of uplink shared channel random access message repetitions, or both; and monitoring for a second random access message based on the number of the first random access messages.

[0020] Describes an apparatus for wireless communication at a network node. The apparatus may include: a processor; a memory coupled to the processor; and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: transmit a set of multiple synchronization signal blocks associated with a random access procedure; receive a number of first random access messages, where the number of first random access messages is based on a random access channel format associated with the random access procedure, a configured number of uplink shared channel random access message repetitions, or both; and transmit a second random access message based on the number of first random access messages.

[0021] Describes another apparatus for wireless communication at a network node. The apparatus may include: means for transmitting a set of multiple synchronization signal blocks associated with a random access procedure; means for transmitting a number of first random access messages, where the number of first random access messages is based on a random access channel format associated with the random access procedure, a configured number of uplink shared channel random access message repetitions, or both; and means for transmitting a second random access message based on the number of first random access messages.

[0022] Describes a non-transitory computer-readable medium storing code for wireless communication at a network node. The code may include instructions executable by a processor to: transmit a set of multiple synchronization signal blocks associated with a random access procedure; receive a number of first random access messages, where the number of first random access messages is based on a random access channel format associated with the random access procedure, a configured number of uplink shared channel random access message repetitions, or both; and transmit a second random access message based on the number of first random access messages.

[0023] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the number of first random access messages may be based on the length of the random access channel format.

[0024] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the number of first random access messages may be equal to the configured number of uplink shared channel random access message repetitions.

[0025] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the number of first random access messages may be based on the number of uplink shared channel random access repetitions and the random access channel format.

[0026] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the number of the first random access messages may be less than the configured number of uplink shared channel random access repetitions based on the random access channel format.

[0027] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for performing the following action: transmitting control signaling indicating the configured number of uplink shared channel random access message repetitions.

[0028] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the control signaling includes a random access response uplink grant or downlink control information.

[0029] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the number of uplink shared channel random access message repetitions may be a default number of uplink shared channel random access message repetitions.

[0030] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the number of the first random access messages for initial access may be based on the configured number of uplink shared channel random access message repetitions associated with the initial access.

[0031] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the number of the first random access messages for retransmission may be based on the configured number of uplink shared channel random access message repetitions associated with initial access or retransmission.

[0032] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the number of the first random access messages for retransmission may be at least partially based on the configured number of uplink shared channel random access message repetitions, and the configured number may be the maximum number, minimum number, or statistical number associated with a first configured number of uplink shared channel random access message repetitions for initial access and a second configured number of uplink shared channel random access message repetitions for retransmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 Illustrates an example of a wireless communication system supporting implicit PRACH repetition indication in accordance with one or more examples disclosed herein.

[0034] Figure 2A and Figure 2B Illustrates an example of a random access scheme supporting implicit PRACH repetition indication in accordance with one or more examples disclosed herein.

[0035] Figure 3 An example of a wireless communication system supporting implicit PRACH repetition indication according to one or more examples disclosed herein is illustrated.

[0036] Figure 4 An example of a process flow supporting implicit PRACH repetition indication according to one or more examples disclosed herein is illustrated.

[0037] Figure 5 and Figure 6 A block diagram of a device supporting implicit PRACH repetition indication according to one or more examples disclosed herein is illustrated.

[0038] Figure 7 A block diagram of a communication manager supporting implicit PRACH repetition indication according to one or more examples disclosed herein is illustrated.

[0039] Figure 8 A diagram of a system including a device supporting implicit PRACH repetition indication according to one or more examples disclosed herein is illustrated.

[0040] Figure 9 and Figure 10 A block diagram of a device supporting implicit PRACH repetition indication according to one or more examples disclosed herein is illustrated.

[0041] Figure 11 A block diagram of a communication manager supporting implicit PRACH repetition indication according to one or more examples disclosed herein is illustrated.

[0042] Figure 12 A diagram of a system including a device supporting implicit PRACH repetition indication according to one or more examples disclosed herein is illustrated.

[0043] Figure 13 and Figure 14 A flowchart showing a method supporting implicit PRACH repetition indication according to one or more examples disclosed herein is illustrated. Detailed Description

[0044] In wireless communication, a user equipment (UE) may participate in a random access process that may involve using multiple beams and selecting one or more beams from the multiple beams to be used in the random access process. In some examples, different beams may be used for different messages in the random access process or for repetitions of messages in the random access process. In some examples, the number of repetitions to be used may be signaled to the UE. However, in the absence of such signaling (e.g., because such signaling may be optional), previous approaches do not provide the UE with other indications of the number of repetitions to be sent for one or more messages in the random access process.

[0045] In the absence of receiving an explicit repetition indication, the UE may implicitly determine the number of random access message repetitions. For example, the UE may determine the number of random access message repetitions based on the random access format employed in the random access process (e.g., a random access channel (RACH) format). Additionally or alternatively, the UE may determine the number of random access message repetitions based on the number of repetitions of a message (e.g., another random access message, such as a physical uplink shared channel (PUSCH) random access message). In some examples, the UE may determine the number of random access message repetitions based on both the random access format and the number of repetitions of another message. In this way, the UE may determine the number of random access message repetitions for the random access process, thereby improving communication quality and reliability by using repetitions across multiple beams.

[0046] Aspects of the present disclosure are first described in the context of a wireless communication system. Then aspects of the present disclosure are described with reference to a wireless communication system and a process flow. Aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow chart diagrams related to implicit PRACH repetition indication.

[0047] Figure 1 An example of a wireless communication system 100 supporting implicit PRACH repetition indication in accordance with one or more examples disclosed herein is illustrated. The wireless communication system 100 may include one or more network nodes 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies including future systems and radio technologies not explicitly mentioned herein.

[0048] Network nodes 105 may be distributed throughout a geographical area to form a wireless communication system 100 and may include devices in different forms or with different capabilities. In various examples, network nodes 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, etc. In some examples, network nodes 105 and UEs 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network nodes 105 may support a coverage area 110 (e.g., a geographical coverage area) over which UEs 115 and network nodes 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area over which network nodes 105 and UEs 115 may support signal communication according to one or more radio access technologies (RATs).

[0049] UEs 115 may be distributed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile or stationary and mobile at different times. UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated herein. The UEs 115 described herein may be capable of supporting communication with various types of devices (such as other UEs 115 or network nodes 105 as shown Figure 1 ).

[0050] As described herein, a node (which may be referred to as a network node or a wireless node) of the wireless communication system 100 can be a network node 105 (e.g., any network node described herein), a UE 115 (e.g., any UE described herein), a network controller, a device, an apparatus, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node can be a UE 115. As another example, the node can be a network node 105. As yet another example, a first node can be configured to communicate with a second node or a third node. In one aspect of this example, the first node can be a UE 115, the second node can be a network node 105, and the third node can be a UE 115. In another aspect of this example, the first node can be a UE 115, the second node can be a network node 105, and the third node can be a network node 105. In other aspects of this example, the first node, the second node, and the third node can be different from these examples. Similarly, references to UE 115, network node 105, device, apparatus, computing system, etc. can include the disclosure of UE 115, network node 105, device, apparatus, computing system, etc. as nodes. For example, the disclosure that UE 115 is configured to receive information from network node 105 also discloses that a first node is configured to receive information from a second node.

[0051] In some examples, network node 105 can communicate with core network 130, or with each other, or both. For example, network node 105 can communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network node 105 can communicate with each other directly (e.g., directly between network nodes 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network node 105 can communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 can be or include one or more wired links (e.g., electrical link, optical fiber link), one or more wireless links (e.g., radio link, wireless optical link), etc. or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0052] One or more of the network nodes 105 described herein may include or may be referred to as a base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, Node B, evolved Node B (eNB), next-generation Node B or giga Node B (either of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home Node B, home evolved Node B, or other suitable terms). In some examples, the network node 105 (e.g., base station 140) may be implemented in an integrated (e.g., monolithic, stand-alone) base station architecture that may be configured to utilize a protocol stack physically or logically integrated within a single network node 105 (e.g., a single RAN node, such as base station 140).

[0053] In some examples, the network node 105 may be implemented in a disaggregated architecture (e.g., disaggregated base station architecture, disaggregated RAN architecture) that may be configured to utilize a protocol stack physically or logically distributed across two or more network nodes 105 (such as an integrated access backhaul (IAB) network, open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or virtualized RAN (vRAN) (e.g., cloud RAN (C-RAN))). For example, the network node 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., near real-time RIC (near RT RIC), non-real-time RIC (non RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, intelligent radio head, remote radio head (RRH), remote radio unit (RRU), or transmit receive point (TRP). One or more components of the network node 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network node 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network nodes 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0054] The functional split between the CU 160, DU 165, and RU 170 is flexible and can support different functions, depending on which functions are performed at the CU 160, DU 165, or RU 170 (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof). For example, a functional split of the protocol stack can be employed between the CU 160 and DU 165 such that the CU 160 can support one or more layers of the protocol stack and the DU 165 can support one or more different layers of the protocol stack. In some examples, the CU 160 can host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 can be connected to one or more DU 165s or RU 170s, and one or more DU 165s or RU 170s can host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and can each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack can be employed between the DU 165 and RU 170 such that the DU 165 can support one or more layers of the protocol stack and the RU 170 can support one or more different layers of the protocol stack. The DU 165 can support one or more different cells (e.g., via one or more RU 170s). In some cases, the functional split between the CU 160 and DU 165 or between the DU 165 and RU 170 can be within a protocol layer (e.g., some functions of a protocol layer can be performed by one of the CU 160, DU 165, or RU 170, while other functions of that protocol layer are performed by a different one of the CU 160, DU 165, or RU 170). The CU 160 can be further functionally split into a CU control plane (CU-CP) and a CU user plane (CU-UP) function. The CU 160 can be connected to one or more DU 165s via an intermediate transport communication link 162 (e.g., F1, F1-c, F1-u), and the DU 165 can be connected to one or more RU 170s via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the intermediate transport communication link 162 or the fronthaul communication link 168 can be implemented according to the interfaces (e.g., channels) between the layers of the protocol stack, the layers of which are supported by the corresponding network nodes 105 communicating via such communication links.

[0055] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to a core network 130). In some cases, in an IAB network, one or more network nodes 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a donor network node 105 (e.g., donor base station 140). One or more donor network nodes 105 (e.g., IAB donors) may communicate with one or more additional network nodes 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication link 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communications with the UE 115, or may share the same antennas (e.g., of an RU 170) of the IAB node 104 for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of a split RAN architecture (e.g., one or more IAB nodes 104 or components of an IAB node 104) may be configured to operate according to the techniques described herein.

[0056] For example, the access network (AN) or RAN may include communication between access nodes (e.g., IAB donors), IAB nodes 104, and one or more UEs 115. The IAB donor may facilitate the connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and a RU 170), in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and the IAB node 104 may communicate via the F1 interface according to a protocol that defines signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, the CU 160 may communicate with the core network via an interface (which may be an example of a part of the backhaul link), and may communicate with other CUs 160 (e.g., CUs 160 associated with alternative IAB donors) via the Xn-C interface (which may be an example of a part of the backhaul link).

[0057] The IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UEs 115, wireless self-backhaul capabilities, etc.). The DU 165 may act as a distributed scheduling node towards the child nodes associated with the IAB node 104, and the IAB-MT may act as a scheduled node towards the parent node associated with the IAB node 104. That is, the IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., the IAB donor may relay transmissions for the UE through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, the IAB node 104 may also be referred to as a parent node or a child node of other IAB nodes 104. Thus, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104, and the DU interface (e.g., the DU 165) may provide a Uu interface for the parent IAB node 104 to signal to the child IAB node 104 or the UE 115.

[0058] For example, the IAB node 104 may be referred to as a parent node that supports communication for a sub-IAB node or as a sub-node associated with an IAB donor or both. The IAB donor may include a CU 160 having a wired or wireless connection to the core network 130 (e.g., a backhaul communication link 120) and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB donor may relay transmissions to the UE 115 via the IAB node 104, or may signal transmissions directly to the UE 115, or both. The CU 160 of the IAB donor may signal communication link establishment to the IAB node 104 via the F1 interface, and the IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to the UE 115) via the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling over the NR Uu interface to the MT of the IAB node 104. Communication with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communication with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104.

[0059] In cases where the techniques described herein are applied in the context of a split RAN architecture, one or more components of the split RAN architecture may be configured to support implicit PRACH repetition indication as described herein. For example, some operations described as being performed by the UE 115 or the network node 105 (e.g., the base station 140) may additionally or alternatively be performed by one or more components of the split RAN architecture (e.g., the IAB node 104, the DU 165, the CU 160, the RU 170, the RIC 175, the SMO 180).

[0060] The UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device or some other suitable term, where "device" may also be referred to as a unit, a station, a terminal, or a client, etc. The UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, the UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0061] The UE 115 described herein may be capable of communicating with various types of devices (such as other UEs 115 that may sometimes act as relays, as well as network nodes 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc.), as Figure 1as shown

[0062] UE 115 and network node 105 may communicate wirelessly with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion (e.g., bandwidth part (BWP)) of an RF spectrum band operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operation, user data, or other signaling. The wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. According to a carrier aggregation configuration, UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between network node 105 and other devices may refer to communication between a device and any part (e.g., entity, sub-entity) of network node 105. For example, the terms "transmit", "receive", or "communicate" when referring to network node 105 may refer to any part of network node 105 of the RAN (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network nodes 105).

[0063] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling for coordinating the operation of other carriers. A carrier may be associated with a frequency channel (e.g., evolved universal mobile telecommunications system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN)) and may be identified according to a channel raster for discovery by UE 115. A carrier may operate in independent mode, in which case initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in non-independent mode, in which case the connection is anchored using a different carrier (e.g., different carriers of the same or different radio access technologies).

[0064] The communication link 125 shown in the wireless communication system 100 may include a downlink transmission (e.g., forward link transmission) from network node 105 to UE 115, an uplink transmission (e.g., return link transmission) from UE 115 to network node 105, or both, etc. A carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink communication and uplink communication (e.g., in TDD mode).

[0065] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or the wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., the network node 105, the UE 115, or both) may have a hardware configuration that supports communication using a specific carrier bandwidth or may be capable of being configured to support communication using one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network node 105 or a UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., a subband, a BWP) or all of the carrier bandwidth.

[0066] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using a multi-carrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing an MCM technique, a resource element may refer to the resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively large number of resource elements (e.g., during the transmission duration) and a relatively high-order modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and space resources (e.g., spatial layers or beams), and the use of multiple space resources may increase the data rate or data integrity for communication with the UE 115.

[0067] One or more parameter sets may be supported for a carrier, and the parameter set may include a subcarrier spacing (Δf) and a cyclic prefix. A carrier may be divided into one or more BWPs having the same or different parameter sets. In some examples, the UE 115 may be configured with multiple BWPs. In some examples, a single BWP of a carrier may be active at a given time, and the communication of the UE 115 may be restricted to one or more active BWPs.

[0068] The time interval for the network node 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may refer to, for example, the sampling period T s = 1 / (Δfmax ·N f ) seconds, where Δf max may represent the supported subcarrier spacing, and N f may represent the supported discrete Fourier transform (DFT) size. The time intervals of the communication resources may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0069] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, a time slot may be further divided into a plurality of mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f ones) sampling periods. The duration of the symbol period may depend on the subcarrier spacing or the operating frequency band.

[0070] A subframe, time slot, mini-slot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0071] According to various techniques, carriers can be used to multiplex physical channels for communication. For example, one or more of time-division multiplexing (TDM) techniques, frequency-division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region of a physical control channel (e.g., a control resource set (CORESET)) can be defined by a set of symbol periods and can extend across the system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) can be configured for a group of UEs 115. For example, one or more of the UEs 115 can monitor or search the control region for control information according to one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with the coded information for a control information format with a given payload size. The search space set can include a common search space set configured to transmit control information to multiple UEs 115 and a UE-specific search space set for transmitting control information to a specific UE 115.

[0072] The network node 105 can provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells or any combination thereof). The term "cell" can refer to a logical communication entity used to communicate with the network node 105 (e.g., using a carrier) and can be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other identifier) used to distinguish adjacent cells. In some examples, a cell can also refer to a coverage area 110 or a part of the coverage area 110 (e.g., a sector) on which the logical communication entity operates. Depending on various factors (such as the capabilities of the network node 105), the scope of such cells can range from a smaller area (e.g., a structure, a subset of a structure) to a larger area. For example, a cell can be or can include a building, a subset of a building, or an external space between or overlapping the coverage area 110, etc.

[0073] Macro cells generally cover a relatively large geographical area (e.g., with a radius of several kilometers) and may allow unrestricted access for UEs 115 having a service subscription with the network provider supporting the macro cell. Small cells may be associated with lower power network nodes 105 (e.g., lower power base stations 140) (compared to macro cells), and small cells may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UEs 115 having a service subscription with the network provider, or may provide restricted access to UEs 115 associated with the small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). Network node 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

[0074] In some examples, a carrier may support multiple cells and may be configured with different cells according to different protocol types that may provide access for different types of devices (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)).

[0075] In some examples, network node 105 (e.g., base station 140, RU 170) may be movable and thus provide communication coverage for a mobile coverage area 110. In some examples, although different coverage areas 110 associated with different technologies may overlap, different coverage areas 110 may be supported by the same network node 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network nodes 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network nodes 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0076] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, network nodes 105 (e.g., base stations 140) may have similar frame timings, and transmissions from different network nodes 105 may be approximately aligned in time. For asynchronous operation, network nodes 105 may have different frame timings, and in some examples, transmissions from different network nodes 105 may not be aligned in time. The techniques described herein may be used for synchronous or asynchronous operation.

[0077] Some UEs 115 (such as MTC or IoT devices) can be low-cost or low-complexity devices and may permit automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technologies that allow devices to communicate with each other or a device to communicate with a network node 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or meters to measure or capture information and relay such information to a central server or application that uses the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wilderness survival monitoring, weather and geographical event monitoring, formation management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0078] Some UEs 115 may be configured to operate in power-saving modes, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception but not concurrent transmission and reception). In some examples, half-duplex communication can be performed with a reduced peak rate. Other energy-saving techniques for UEs 115 include: entering a power-saving deep sleep mode when not participating in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a guard band of a carrier, or outside a carrier.

[0079] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private communication or group communication and may be supported by one or more services (such as push-to-talk, video, or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0080] In some examples, UE 115 may be configured to communicate directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 performing D2D communication in a group may be within the coverage area 110 of a network node 105 (e.g., base station 140, RU 170), and the network node may support aspects of such D2D communication configured (e.g., scheduled) by the network node 105. In some examples, one or more UEs 115 in such a group may be outside the coverage area 110 of the network node 105, or may otherwise be unable or not configured to receive transmissions from the network node 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UEs 115 in the group. In some examples, the network node 105 may facilitate the scheduling of resources for D2D communication. In some other examples, D2D communication may be performed between UEs 115 without involving the network node 105.

[0081] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these. Vehicles may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information related to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units) using vehicle-to-network (V2N) communication, or communicate with the network via one or more network nodes (e.g., network node 105, base station 140, RU 170), or both.

[0082] The core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 can be an Evolved Packet Core (EPC) or a 5G Core (5GC), which may include at least one control plane entity for managing access and mobility (e.g., Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) and at least one user plane entity for routing packets or interconnecting to an external network (e.g., Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)). The control plane entity can manage Non-Access Stratum (NAS) functions, such as mobility, authentication, and bearer management of the UE 115 served by the network node 105 (e.g., base station 140) associated with the core network 130. User IP packets can be passed through the user plane entity, which can provide IP address allocation and other functions. The user plane entity can be connected to the IP services 150 of one or more network operators. The IP services 150 can include access to the Internet, intranet, IP Multimedia Subsystem (IMS), or packet switched streaming services.

[0083] The wireless communication system 100 can operate using one or more frequency bands that can be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the Ultra-High Frequency (UHF) region or the decimeter band, because the wavelength ranges from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but these waves can be sufficient to penetrate structures so that macrocells can serve UEs 115 located indoors. Compared to communication using smaller frequencies and longer waves in the High Frequency (HF) or Very High Frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers).

[0084] The wireless communication system 100 may also operate using the super high frequency (SHF) region (also known as the centimeter band) in the range of 3 GHz to 30 GHz or using the extremely high frequency (EHF) region of the spectrum (e.g., 30 GHz to 300 GHz) (also known as the millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communication between the UE 115 and the network node 105 (e.g., the base station 140, the RU 170), and the EHF antennas of the corresponding devices may be smaller and closer spaced than UHF antennas. In some examples, such techniques may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be affected by greater attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the use of frequency bands designated across these frequency regions may vary by country or regulatory body.

[0085] The wireless communication system 100 may utilize both licensed RF spectrum bands and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use an unlicensed band (such as the 5 GHz industrial, scientific, and medical (ISM) band) to employ licensed-assisted access (LAA), LTE-unlicensed (LTE-U) radio access technology, or NR technology. When operating using an unlicensed RF spectrum band, devices such as the network node 105 and the UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, the operation using the unlicensed band may be based on a carrier aggregation configuration (e.g., LAA) in combination with the operation using a licensed band component carrier. The operation using the unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, D2D transmissions, and so on.

[0086] The network node 105 (e.g., base station 140, RU 170) or the UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network node 105 or the UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly such as an antenna tower. In some examples, the antennas or antenna arrays associated with the network node 105 may be located at different geographical locations. The network node 105 may include an antenna array having a set of rows and columns of antenna ports that the network node 105 may use to support beamforming for communication with the UE 115. Similarly, the UE 115 may include one or more antenna arrays, which may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0087] The network node 105 or the UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques may be referred to as spatial multiplexing. The multiple signals may be transmitted, for example, by the transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), for which multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), for which multiple spatial layers are transmitted to multiple devices.

[0088] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., network node 105, UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining signals communicated via the antenna elements of an antenna array such that some signals propagating along a particular direction relative to the antenna array experience constructive interference while other signals experience destructive interference. Adjusting the signals communicated via the antenna elements can include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to the signals carried via the antenna elements associated with that device. The adjustments associated with each of these antenna elements can be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other orientation).

[0089] Network node 105 or UE 115 can use beam scanning techniques as part of a beamforming operation. For example, network node 105 (e.g., base station 140, RU 170) can use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) can be sent by network node 105 multiple times along different directions. For example, network node 105 can send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions can be used to identify (e.g., by the transmitting device such as network node 105, or by the receiving device such as UE115) the beam directions for later transmission or reception by network node 105.

[0090] A transmitting device (e.g., transmitting network node 105, transmitting UE 115) can send some signals, such as data signals associated with a particular receiving device, along a single beam direction (e.g., a direction associated with a receiving device such as receiving network node 105 or receiving UE 115). In some examples, the beam direction associated with a transmission along a single beam direction can be determined based on signals transmitted along one or more beam directions. For example, UE 115 can receive one or more of the signals sent by network node 105 along different directions and can report to network node 105 an indication of the signal received with the highest signal quality or other acceptable signal quality with respect to UE 115.

[0091] In some examples, transmissions performed by a device (e.g., by network node 105 or UE 115) may be carried out using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., transmitted from network node 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across the system bandwidth or one or more sub-bands. Network node 105 may transmit reference signals (e.g., cell-specific reference signal (CRS), channel state information reference signal (CSI-RS)), which may or may not be precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals transmitted by network node 105 (e.g., base station 140, RU 170) in one or more directions, UE 115 may use similar techniques for transmitting signals multiple times in different directions (e.g., for identifying beam directions for subsequent transmissions or receptions by UE 115), or for transmitting signals in a single direction (e.g., for transmitting data to a receiving device).

[0092] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a transmitting device (e.g., network node 105). For example, the receiving device may perform receiving according to multiple receiving directions by: receiving via different antenna sub-arrays, processing the received signals according to different antenna sub-arrays, receiving according to different sets of receiving beamforming weights (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing the received signals according to different sets of receiving beamforming weights applied to signals received at multiple antenna elements of an antenna array. Any of these operations may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). The single receiving configuration may be aligned along a beam direction determined based on listening according to different receiving configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0093] The wireless communication system 100 can be a packet-based network that operates according to a hierarchical protocol stack. In the user plane, the communication at the bearer or PDCP layer can be IP-based. The RLC layer can perform packet segmentation and reassembly for conveyance via logical channels. The MAC layer can perform priority handling and multiplexing of logical channels into transport channels. The MAC layer can also implement error detection techniques, error correction techniques, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer can provide the establishment, configuration, and maintenance of an RRC connection for radio bearers supporting user plane data between the UE 115 and the network node 105 or the core network 130. The PHY layer can map the transport channels to physical channels.

[0094] The UE 115 and the network node 105 can support the retransmission of data to increase the likelihood that the data is successfully received. Hybrid Automatic Repeat Request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data via a communication link (e.g., communication link 125, D2D communication link 135). HARQ can include a combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve the throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device can support same-slot HARQ feedback, in which case the device can provide HARQ feedback for data received via previous symbols in a particular slot during that slot. In some other examples, the device can provide HARQ feedback in a subsequent slot or according to some other time interval.

[0095] In some embodiments, the UE can determine the number of repetitions of a random access message to be sent during a random access procedure and can do so based on one or more implicit indications, associations, information, or any combination thereof. For example, the UE can determine the number of repetitions of a random access message to be sent based on the random access channel (RACH) format (e.g., during or in association with an initial access procedure), the number of PUSCH random access message repetitions (e.g., in cases where the UE has previously been connected to a cell and has obtained such information in a previous initial access scenario). The UE can send one or more repetitions of the random access message and can then monitor a second random access message (e.g., a random access response message). At least in this way, in scenarios where no explicit signaling indicating the number of repetitions of the random access message to be sent is received, the UE can determine and send the number of repetitions of the random access message.

[0096] FIG. 2 illustrates an example of a random access scheme 200 supporting implicit PRACH repetition indication according to one or more examples disclosed herein.

[0097] In some specific implementations, UE 115-a and network node 105-a may perform a random access procedure (e.g., a random access channel (RACH) procedure) in combination with a multi-beam operation scenario. In such a scenario, the mapping between the SSB and the RACH occasion (RO) may be configured (e.g., by network node 105-a, optionally in the system information block (SIB)). For example, beam 0 225-a may be associated with SSB#0 and beam 1 225-b may be associated with SSB#1.

[0098] As part of the random access procedure, network entity 105-b may periodically transmit one or more SSBs (e.g., SSB#0, SSB#1, SSB#2, and SSB#3) by cycling through a set of transmission beams 220 oriented in different directions. UE 115-a may measure the SSB transmissions to determine or select which transmission beam 225 UE 115-a can receive best (e.g., based on a metric such as the reference signal received power (RSRP) of the SSB transmission). Based on the indicated mapping between the SSB and the RO, UE 115-a may transmit one or more first random access messages (e.g., one or more repetitions of the first random access message 325) in the RO corresponding to the selected transmission beam (e.g., based on the mapping). UE 115-a may use the spatial filter associated with the selected SSB to transmit one or more repetitions of the first random access message (e.g., Msg1 230). In some examples, network node 105-a may receive the first random access message and may use the same beam to transmit the second random access message (such as Msg2 235). In response to transmitting the second random access message (e.g., Msg2 235), UE 115-a may use the same spatial filter as the spatial filter that UE 115-a used to transmit the first random access message 325 to transmit the third random access message (e.g., Msg3 240). In response to transmitting the third random access message (e.g., Msg3 240), network entity 105-a may send a fourth random access message (e.g., Msg4 245) to UE 115-a. UE 115-a may send an affirmative acknowledgment (ACK) 250 to network entity 105-a. The ACK 250 may indicate that UE 115-a and network entity 105-a have successfully completed the random access procedure.

[0099] Figure 2B An example of a random access scheme 200 that supports implicit PRACH repetition indication in accordance with one or more examples disclosed herein is also illustrated. Figure 2BDepicts an example scenario where various SSBs have been mapped to various ROs, and UE115-a transmits repetitions of Msg1 230 in different ROs associated with multiple SSBs (e.g., SSB#0 and SSB#1) and multiple associated transmission beams 225. For example, beam 0 225-a may be associated with SSB#0 and beam 1 225-b may be associated with SSB#1.

[0100] In some random access scenarios, UE 115-a may transmit one or more repetitions (e.g., Msg1#0, Msg1#1, Msg1#2, and Msg1#3) of a first random access message (e.g., Msg1 230). In some examples that do not employ the use of multiple beams, multiple repetitions may be transmitted over multiple associated periods 255. However, in some examples that employ the use of multiple beams (such as Figure 2B the scenario described herein), multiple repetitions may be transmitted within a single associated period 255. For example, as depicted, Msg1#0 and Msg1#2 may be transmitted in RO#1 associated with SSB#0 and beam 1 225-b, and Msg1#1 and Msg1#3 may be transmitted in RO#3 associated with SSB#1 and beam 1 225-b. In this way, in scenarios involving multiple beams and SBSs, UE 115-a may transmit multiple repetitions of a first random access message (e.g., Msg1 230).

[0101] Figure 3 Illustrates an example of a wireless communication system 300 that supports implicit PRACH repetition indication in accordance with one or more examples disclosed herein. The wireless communication system 300 may include a network node 105-b, which may be an example of one or more of the network nodes discussed with respect to other figures. The wireless communication system 300 may include a UE 115-b, which may be an example of the UE discussed with respect to other figures. In some examples, UE 115-b may be located in a geographic coverage area 110-a that may be associated with network node 105-b. Network node 105-b and UE 115-b may communicate via one or more downlink communication links 305-a and one or more uplink communication links 305-b.

[0102] In some implementations, the number of repetitions to be transmitted by UE 115-b may be configured (e.g., via cell-specific signaling) to UE 115-b as part of the configuration of a random access procedure. However, in some cases, such explicit signaling or indication may be optional. Thus, UE 115-b may implicitly determine the number of repetitions of a first random access message 325 to be transmitted by UE 115-b.

[0103] In some examples, UE 115-b may determine the number of first random access messages 325 for UE 115-b to send based on the length or type of random access format 345. For example, for a long random access format 345 (e.g., 0, …, 3), the number of repetitions may be a single repetition, while for a short random access format 345, the number may be two repetitions. For example, random access format 345-a may be an example of a short random access format that may include less data than a “long” random access format (such as random access format 345-b or random access format 345-c). Since the length of a subframe may be fixed (e.g., 1 ms), different random access formats 345 may correspond to different lengths of ROs. Thus, the number of ROs in a subframe may be different for different random access formats 345. For example, for a “short” RO format A1 (e.g., where the RO size is two symbols), there may be six ROs in a subframe. However, for format C1 (e.g., where the RO size is six symbols), there may be only two ROs in a subframe.

[0104] In some examples, UE 115-b may determine the number of first random access messages 325 for UE 115-b to send based on the configured number of uplink shared channel random access repetitions (e.g., Msg3 PUSCH repetitions). For example, the number of repetitions of the first random access message 325 may be equal to the configured number of uplink shared channel random access repetitions (e.g., Msg3 PUSCH repetitions). Such a number of uplink shared channel random access repetitions may be indicated in the second random access message 330. UE 115-b may determine the number of first random access messages 325 for UE 115-b to send for a subsequent random access procedure (e.g., due to a current random access procedure failure or when UE 115-b performs a random access procedure when exiting the idle mode), and may send that number of first random access messages 325 in that subsequent random access procedure.

[0105] In some examples, UE 115-b may determine the number of first random access messages 325 to be sent by UE 115-b based on both a random access format 345 and the configured number of uplink shared channel random access repetitions (e.g., Msg3 PUSCH repetitions). For example, for one or more random access formats (e.g., RACH formats such as a "short" format or a subset of the "short" format), the number of repetitions of the first random access message 325 may be equal to the configured number of uplink shared channel random access repetitions (e.g., Msg3 PUSCH repetitions), and for one or more other random access formats, the number may be equal to 1. In an example of a "short" random access format (e.g., random access format 345-a), the resources of the RO may be large enough to send a number of first random access messages 325 that may be equal to the configured number of uplink shared channel random access repetitions. However, in an example of a "long" random access format (e.g., random access format 345-c), the resources of the RO may not be large enough to send the same number of first random access messages 325 as the configured number of uplink shared channel random access repetitions, and another value (e.g., the number 1) may be used based on the size of the resources of the RO.

[0106] In some examples, the number of uplink shared channel random access repetitions may be one value from a set of possible values (e.g., a set of values such as {1, 2, 3, 4, 7, 9, 12, 16}). In some examples, one or more values (e.g., four values) may be configured in a system information block. In some examples, if such values are not configured in the system information block, a default set of values (e.g., {1, 2, 3, 4}) may be used.

[0107] In some examples, the number of uplink shared channel random access repetitions may be configured in control signaling 335. For example, the number of uplink shared channel random access repetitions (e.g., PUSCH repetitions 340) may be configured (e.g., by one or more most significant bits of a modulation and coding scheme field in a random access response uplink grant, which may be an example of control signaling) for initial access transmission. Additionally or alternatively, the number of uplink shared channel random access repetitions (e.g., PUSCH repetitions 340) may be configured (e.g., by one or more most significant bits of a modulation and coding scheme field in control signaling, such as downlink control information (DCI) of a format (such as format 0_0), optionally with a cyclic redundancy check (CRC) scrambled by a temporary cell radio network temporary identifier (TC-RNTI)) for retransmission of uplink shared channel random access messages.

[0108] In some examples where the number of repetitions of the first random access message 325 is based on the number of uplink shared channel random access repetitions, UE 115-b may determine the number of repetitions in the same or different ways for the initial access procedure and the retransmission procedure. For example, for the initial access procedure, the number of repetitions of the first random access message 325 may be based on the number of uplink shared channel random access repetitions configured for the initial transmission of the random access message (e.g., Msg3 PUSCH transmission). For example, the number of repetitions of the first random access message 325 may be the same as the number of uplink shared channel random access repetitions configured for the initial transmission of the random access message.

[0109] However, for the retransmission procedure (e.g., after the network node 105-b fails to receive a random access message such as Msg2 or Msg4), the number of repetitions of the first random access message 325 may be based on the number of uplink shared channel random access repetitions (e.g., Msg3 PUSCH repetitions) configured for the initial uplink shared channel random access repetitions (e.g., Msg3 PUSCH transmission repetitions), the number of uplink shared channel random access repetitions (e.g., Msg3 PUSCH repetitions) configured for the uplink shared channel random access repetition (e.g., Msg3 PUSCH) retransmission, or both. For example, the number of repetitions of the first random access message 325 may be based on the maximum value, minimum value, rounded value, average value, one or more statistical values, or any combination thereof of the number of uplink shared channel random access repetitions configured for the initial uplink shared channel random access repetitions and the number of uplink shared channel random access repetitions (e.g., Msg3 PUSCH repetitions) configured for the uplink shared channel random access repetition (e.g., Msg3 PUSCH) retransmission. For example, if the number of uplink shared channel random access repetitions configured for the initial uplink shared channel random access repetitions is one and the number of uplink shared channel random access repetitions configured for the uplink shared channel random access repetition retransmission is three, a repeated value of the number of repetitions of the first random access message 325 may be calculated. In this case, the maximum value would be three, the minimum value would be 1, and the average value would be 2. Different statistical values based on the number of uplink shared channel random access repetitions configured for the initial uplink shared channel random access repetitions and the number of uplink shared channel random access repetitions may be used, and such values are not limited to the examples provided herein.

[0110] After the UE 115-b has determined the number of repetitions of the first random access message 325 to be sent by the UE 115-b, the UE 115-b may send the repetitions of the first random access message 325 and monitor one or more subsequent random access messages from the network node 105-b. The UE 115-b and the network node 105-b may continue the random access signaling (e.g., using one or more beams) to establish further connectivity between the UE 115-b and the network node 105-b. At least in this way, the UE 115-b may implicitly determine the number of repetitions of the first random access message 325 to be sent by the UE 115-b (even in the absence of explicit signaling indicating such a number of repetitions).

[0111] Figure 4 An example of a process flow 400 supporting implicit PRACH repetition indication in accordance with one or more examples disclosed herein is illustrated. The process flow 400 may implement aspects of the present disclosure described herein. The elements described in the process flow 400 (e.g., network node 105-c and UE 115-c) may be examples of similarly named elements described herein.

[0112] In the following description of the process flow 400, operations between various entities or elements may be performed in a different order or at different times. Some operations may also be excluded from the process flow 400, or other operations may be added. Although the various entities or elements are shown performing the operations of the process flow 400, some aspects of some operations may also be performed by other entities or elements of the process flow 400 or by entities or elements not depicted in the process flow or any combination thereof.

[0113] At 420, the UE 115-b may receive a plurality of synchronization signal block transmissions associated with a random access procedure.

[0114] At 425, the UE 115-b may send a certain number of first random access messages, and the number of the first random access messages is based on a random access channel format associated with the random access procedure, a configured number of uplink shared channel random access message repetitions, or both. In some examples, the number of the first random access messages may be based on the length of the random access channel format. In some examples, the number of the first random access messages may be equal to the configured number of uplink shared channel random access message repetitions.

[0115] In some examples, this number of uplink shared channel random access message repetitions may be the default number of uplink shared channel random access message repetitions. In some examples, the first random access message of this number may be used for initial access, and this number may be based on this configured number of uplink shared channel random access message repetitions associated with this initial access. In some examples, the first random access message of this number may be used for retransmission, and this number may be based on this configured number of uplink shared channel random access message repetitions associated with initial access or retransmission. In some examples, the first random access message of this number may be used for retransmission, and this number may be based on this configured number of uplink shared channel random access message repetitions, which may be the maximum number, minimum number, or statistical number associated with a first configured number of uplink shared channel random access message repetitions for initial access and a second configured number of uplink shared channel random access message repetitions for retransmission.

[0116] In some examples, this number of the first random access messages may be based on this configured number of uplink shared channel random access repetitions and this random access channel format. In some examples, this number of the first random access messages may be less than this configured number of uplink shared channel random access repetitions based on this random access channel format.

[0117] At 430, UE 115-b may monitor a second random access message based on this number of the first random access messages.

[0118] At 435, UE 115-b may receive control signaling indicating this configured number of uplink shared channel random access message repetitions. For example, this control signaling may be Msg2 of a RACH procedure. In some examples, this control signaling may include a random access response uplink grant or downlink control information. In a subsequent random access procedure, UE 115-c may determine the number of random access message repetitions to be sent by UE 115-c based on this configured number of uplink shared channel random access message repetitions included in this control signaling. In some examples, this control signaling may be included in a second random access message (e.g., this second random access message that UE 115-c is monitoring).

[0119] At 440, UE 115-c may send one or more third random access messages, and the one or more third random access messages may be sent based on this control signaling or the second random access message. For example, one or more repetitions of this third random access message may be sent according to this configured number of uplink shared channel random access message repetitions included in this control signaling. In some examples, this third random access message may be Msg3 of a RACH procedure.

[0120] At 445, UE 115-c may receive a fourth random access message from network entity 105-c. In some examples, another random access message may be Msg4 of a RACH procedure.

[0121] At 450, UE 115-c may communicate (e.g., send, receive, or both) one or more data communications with network entity 105-c. For example, the fourth random access message may be the last message of a random access procedure, may establish communication of a connection between UE 115-c and network entity 105-c, and UE 115-c and network entity 105-c may communicate via the one or more data communications.

[0122] Figure 5 Block diagram 500 illustrates a device 505 that supports implicit PRACH repetition indication according to one or more examples disclosed herein. Device 505 may be an example of aspects of UE 115 as described herein. Device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Device 505 may also include: one or more processors; a memory coupled to the one or more processors; and instructions stored in the memory and executable by the one or more processors to enable the one or more processors to perform the random access repetition indication features discussed herein. Each of these components may communicate with each other (e.g., via one or more buses).

[0123] Receiver 510 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to implicit PRACH repetition indication). The information may be delivered to other components of device 505. Receiver 510 may utilize a single antenna or a set of multiple antennas.

[0124] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, transmitter 515 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to implicit PRACH repetition indication). In some examples, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may utilize a single antenna or a set of multiple antennas.

[0125] The communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof or their various components can be examples of components for performing various aspects of implicit PRACH repetition indication as described herein. For example, the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof can support methods for performing one or more of the functions described herein.

[0126] In some examples, the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof can be implemented in hardware (e.g., in a communication management circuit). The hardware can include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured to or otherwise supporting components for performing the functions described in this disclosure. In some examples, a processor and a memory coupled to the processor can be configured to perform one or more of the functions described herein (e.g., by the processor executing instructions stored in the memory).

[0127] Additionally or alternatively, in some examples, the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof can be implemented in code executed by a processor (e.g., implemented as communication management software or firmware). If implemented in code executed by a processor, the functions of the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof can be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices configured to or otherwise supporting components for performing the functions described in this disclosure.

[0128] In some examples, the communication manager 520 can be configured to use or otherwise cooperate with the receiver 510, the transmitter 515, or both to perform various operations (e.g., receive, obtain, monitor, output, transmit). For example, the communication manager 520 can receive information from the receiver 510, convey information to the transmitter 515, or integrate in combination with the receiver 510, the transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

[0129] Additionally or alternatively, according to examples as disclosed herein, communication manager 520 may support wireless communication at a UE. For example, communication manager 520 may be configured to or otherwise support components for receiving a set of multiple synchronization signal blocks transmissions associated with a random access procedure. Communication manager 520 may be configured to or otherwise support components for transmitting a number of first random access messages, where the number of first random access messages is based on a random access channel format associated with the random access procedure, a configured number of uplink shared channel random access message repetitions, or both. Communication manager 520 may be configured to or otherwise support components for detecting a second random access message based on the number of first random access messages.

[0130] By including or configuring communication manager 520 according to examples as described herein, device 505 (e.g., a processor that controls or otherwise is coupled to receiver 510, transmitter 515, communication manager 520, or a combination thereof) may support techniques for reducing processing, reducing power consumption, more efficiently utilizing communication resources, or any combination thereof.

[0131] Figure 6 Block diagram 600 illustrates a device 605 that supports implicit PRACH repetition indication according to one or more examples as disclosed herein. Device 605 may be an example of aspects of device 505 or UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0132] Receiver 610 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to implicit PRACH repetition indication). The information may be delivered to other components of device 605. Receiver 610 may utilize a single antenna or a set of multiple antennas.

[0133] Transmitter 615 may provide components for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to implicit PRACH repetition indication). In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a set of multiple antennas.

[0134] Device 605 or its various components may be examples of components for performing aspects of implicit PRACH repetition indication as described herein. For example, communication manager 620 may include SSB component 625, first random access message component 630, second random access message component 635, or any combination thereof. Communication manager 620 may be an example of aspects of communication manager 520 as described herein. In some examples, communication manager 620 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise in cooperation with receiver 610, transmitter 615, or both. For example, communication manager 620 may receive information from receiver 610, convey information to transmitter 615, or integrate in combination with receiver 610, transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0135] According to examples disclosed herein, communication manager 620 may support wireless communication at a UE. SSB component 625 may be configured to or otherwise support components for receiving a set of multiple synchronization signal block transmissions associated with a random access procedure. First random access message component 630 may be configured to or otherwise support components for transmitting a number of first random access messages, where the number of first random access messages is based on a random access channel format associated with the random access procedure, a configured number of uplink shared channel random access message repetitions, or both. Second random access message component 635 may be configured to or otherwise support components for monitoring a second random access message based on the number of first random access messages.

[0136] In some cases, SSB component 525, first random access message component 530, and second random access message component may each be a processor (e.g., transceiver processor, or radio processor, or transmitter processor, or receiver processor) or at least part of a processor. The processor may be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate the features of SSB component 525, first random access message component 530, and second random access message component discussed herein. The transceiver processor may be collocated with and / or communicate with (e.g., direct the operation of) the transceiver of the device. The radio processor may be collocated with and / or communicate with (e.g., direct the operation of) the radio components of the device (e.g., NR radio components, LTE radio components, Wi-Fi radio components). The transmitter processor may be collocated with and / or communicate with (e.g., direct the operation of) the transmitter of the device. The receiver processor may be collocated with and / or communicate with (e.g., direct the operation of) the receiver of the device.

[0137] Figure 7 FIG. 700 is a block diagram illustrating a communication manager 720 that supports implicit PRACH repetition indication in accordance with one or more examples as disclosed herein. The communication manager 720 may be an example of aspects of the communication manager 520, the communication manager 620, or both as described herein. The communication manager 720 or its various components may be examples of components for performing aspects of the implicit PRACH repetition indication as described herein. For example, the communication manager 720 may include an SSB component 725, a first random access message component 730, a second random access message component 735, a random access channel format component 740, a UL-SCH random access message component 745, a control signaling component 750, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0138] Additionally or alternatively, in accordance with examples as disclosed herein, the communication manager 720 may support wireless communication at a UE. The SSB component 725 may be configured to or otherwise support components for receiving a set of multiple synchronization signal block transmissions associated with a random access procedure. The first random access message component 730 may be configured to or otherwise support components for transmitting a number of first random access messages, where the number of the first random access messages is based on a random access channel format associated with the random access procedure, a configured number of UL-SCH random access message repetitions, or both. The second random access message component 735 may be configured to or otherwise support components for monitoring a second random access message based on the number of the first random access messages.

[0139] In some examples, the number of the first random access messages is based on the length of the random access channel format.

[0140] In some examples, the number of the first random access messages is equal to the configured number of UL-SCH random access message repetitions.

[0141] In some examples, the number of the first random access messages is based on the configured number of UL-SCH random access repetitions and the random access channel format.

[0142] In some examples, the number of the first random access messages is less than the configured number of UL-SCH random access repetitions based on the random access channel format.

[0143] In some examples, the control signaling component 750 may be configured to or otherwise support components for receiving control signaling indicating the configured number of UL-SCH random access message repetitions.

[0144] In some examples, the control signaling includes a random access response uplink grant or downlink control information.

[0145] In some examples, the number of repetitions of the uplink shared channel random access message is the default number of repetitions of the uplink shared channel random access message.

[0146] In some examples, the number of the first random access messages for initial access is based on the configured number of repetitions of the uplink shared channel random access message associated with the initial access.

[0147] In some examples, the number of the first random access messages for retransmission is based on the configured number of repetitions of the uplink shared channel random access message associated with initial access or retransmission.

[0148] In some examples, the number of the first random access messages for retransmission is based on the configured number of repetitions of the uplink shared channel random access message, where the configured number is the maximum number, minimum number, or statistical number associated with a first configured number of repetitions of the uplink shared channel random access message for initial access and a second configured number of repetitions of the uplink shared channel random access message for retransmission.

[0149] In some cases, the SSB component 625, the first random access message component 630, the second random access message component 635, the random access channel format component 640, the uplink shared channel random access message component 645, and the control signaling component 650 may each be a processor (e.g., a transceiver processor, or a radio processor, or a transmitter processor, or a receiver processor) or at least a part of a processor. The processor may be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate the features of the SSB component 625, the first random access message component 630, the second random access message component 635, the random access channel format component 640, the uplink shared channel random access message component 645, and the control signaling component 650 discussed herein.

[0150] Figure 8FIG. illustrates a system 800 of a device 805 that supports implicit PRACH repetition indication according to one or more examples as disclosed herein. The device 805 may be an example of the device 505, the device 605, or the UE 115 as described herein, or include components thereof. The device 805 may communicate (e.g., wirelessly) with one or more network nodes 105, one or more UEs 115, or any combination thereof. The device 805 may include components for two-way voice and data communication, including components for sending and receiving communications, such as a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, code 835, and a processor 840. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) coupled via one or more buses (e.g., bus 845).

[0151] The I / O controller 810 may manage input signals and output signals of the device 805. The I / O controller 810 may also manage peripheral devices not integrated into the device 805. In some cases, the I / O controller 810 may represent a physical connection or port to an external peripheral device. In some cases, the I / O controller 810 may utilize an operating system, such as or another known operating system. Additionally or alternatively, the I / O controller 810 may represent, or interact with, a modem, a keyboard, a mouse, a touch screen, or similar devices. In some cases, the I / O controller 810 may be implemented as part of a processor (such as the processor 840). In some cases, a user may interact with the device 805 via the I / O controller 810 or via hardware components controlled by the I / O controller 810.

[0152] In some cases, the device 805 may include a single antenna 825. However, in some other cases, the device 805 may have more than one antenna 825, which may be capable of concurrently sending or receiving multiple wireless transmissions. The transceiver 815 may communicate bidirectionally via one or more antennas 825, wired or wireless links as described herein. For example, the transceiver 815 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 815 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 825 for transmission; and demodulating packets received from one or more antennas 825. The transceiver 815, or the transceiver 815 and one or more antennas 825, may be an example of the transmitter 515, the transmitter 615, the receiver 510, the receiver 610, or any combination thereof, or components thereof, as described herein.

[0153] Memory 830 may include random access memory (RAM) and read-only memory (ROM). Memory 830 may store computer-readable, computer-executable code 835 including instructions that, when executed by processor 840, cause device 805 to perform the various functions described herein. Code 835 may be stored in a non-transitory computer-readable medium (such as system memory or another type of memory). In some cases, code 835 may not be directly executable by processor 840 but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 830 may contain a basic input / output system (BIOS), etc., which may control basic hardware or software operations, such as interactions with peripheral components or devices.

[0154] Processor 840 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 840. Processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 830) to cause device 805 to perform various functions (e.g., functions or tasks supporting implicit PRACH repetition indication). For example, device 805 or components of device 805 may include processor 840 and memory 830 coupled to or coupled with processor 840, and processor 840 and memory 830 are configured to perform the various functions described herein.

[0155] Additionally or alternatively, according to examples as disclosed herein, communication manager 820 may support wireless communication at the UE. For example, communication manager 820 may be configured to or otherwise support components for receiving a set of multiple synchronization signal block transmissions associated with a random access procedure. Communication manager 820 may be configured to or otherwise support components for transmitting a certain number of first random access messages, where the number of first random access messages is based on a random access channel format associated with the random access procedure, a configured number of uplink shared channel random access message repetitions, or both. Communication manager 820 may be configured to or otherwise support components for detecting a second random access message based on the number of first random access messages.

[0156] By including or configuring a communication manager 820 according to examples as described herein, device 805 may support techniques for improving communication reliability, reducing latency, improving the user experience associated with reduced processing, reducing power consumption, more efficiently utilizing communication resources, improving coordination between devices, extending battery life, improving utilization of processing capabilities, or any combination thereof.

[0157] In some examples, communication manager 820 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise in concert with transceiver 815, one or more antennas 825, or any combination thereof. Although communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to communication manager 820 may be supported or performed by processor 840, memory 830, code 835, or any combination thereof. For example, code 835 may include instructions executable by processor 840 to cause device 805 to perform aspects of implicit PRACH repetition indication as described herein, or processor 840 and memory 830 may otherwise be configured to perform or support such operations.

[0158] Figure 9 Block diagram 900 of a device 905 supporting implicit PRACH repetition indication in accordance with one or more examples disclosed herein is illustrated. Device 905 may be an example of aspects of a network node as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905 may also include: one or more processors; a memory coupled to the one or more processors; and instructions stored in the memory and executable by the one or more processors to enable the one or more processors to perform the random access repetition indication features discussed herein. Each of these components may communicate with each other (e.g., via one or more buses).

[0159] Receiver 910 may provide components for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be delivered to other components of device 905. In some examples, receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0160] Transmitter 915 may provide a component for outputting (e.g., transmitting, providing, conveying, delivering) information generated by other components of device 905. For example, transmitter 915 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 915 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 915 and receiver 910 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0161] Communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be examples of components for performing aspects of implicit PRACH repetition indication as described herein. For example, communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may support methods for performing one or more of the functions described herein.

[0162] In some examples, communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic, discrete hardware component, or any combination thereof configured to or otherwise supporting components for performing the functions described in this disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by the processor executing instructions stored in the memory).

[0163] Additionally or alternatively, in some examples, communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in code executed by a processor (e.g., implemented as communication management software or firmware). If implemented in code executed by a processor, the functions of communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured to or otherwise supporting components for performing the functions described in this disclosure.

[0164] In some examples, communication manager 920 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise in concert with receiver 910, transmitter 915, or both. For example, communication manager 920 may receive information from receiver 910, convey information to transmitter 915, or integrate in combination with receiver 910, transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0165] Additionally or alternatively, according to examples as disclosed herein, communication manager 920 may support wireless communication at a network node. For example, communication manager 920 may be configured to or otherwise support components for transmitting a plurality of synchronization signal blocks associated with a random access procedure. Communication manager 920 may be configured to or otherwise support components for receiving a number of first random access messages, where the number of first random access messages is based on a random access channel format associated with the random access procedure, a configured number of uplink shared channel random access message repetitions, or both. Communication manager 920 may be configured to or otherwise support components for transmitting a second random access message based on the number of first random access messages.

[0166] By including or configuring communication manager 920 according to examples as described herein, device 905 (e.g., a processor that controls or otherwise is coupled to receiver 910, transmitter 915, communication manager 920, or a combination thereof) may support techniques for reducing processing, reducing power consumption, more efficiently utilizing communication resources, or any combination thereof.

[0167] Figure 10 Block diagram 1000 illustrates device 1005 supporting implicit PRACH repetition indication according to one or more examples as disclosed herein. Device 1005 may be an example of aspects of device 905 or network node 105 as described herein. Device 1005 may include receiver 1010, transmitter 1015, and communication manager 1020. Device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0168] The receiver 1010 may provide components for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be delivered to other components of the device 1005. In some examples, the receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0169] The transmitter 1015 may provide components for outputting (e.g., transmitting, providing, conveying, delivering) information generated by other components of the device 1005. For example, the transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, the transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1015 and the receiver 1010 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0170] The device 1005 or its various components may be examples of components for performing aspects of the implicit PRACH repetition indication as described herein. For example, the communication manager 1020 may include an SSB component 1025, a first random access message component 1030, a second random access message component 1035, or any combination thereof. The communication manager 1020 may be an example of aspects of the communication manager 920 as described herein. In some examples, the communication manager 1020 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise in cooperation with the receiver 1010, the transmitter 1015, or both. For example, the communication manager 1020 may receive information from the receiver 1010, convey information to the transmitter 1015, or integrate in combination with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0171] According to examples as disclosed herein, communication manager 1020 may support wireless communication at a network node. The SSB component 1025 may be configured to or otherwise support components for transmitting a set of multiple synchronization signal blocks associated with a random access procedure. The first random access message component 1030 may be configured to or otherwise support components for receiving a certain number of first random access messages, where the number of the first random access messages is based on a random access channel format associated with the random access procedure, a configured number of uplink shared channel random access message repetitions, or both. The second random access message component 1035 may be configured to or otherwise support components for transmitting a second random access message based on the number of the first random access messages.

[0172] In some cases, the SSB component 925, the first random access message component 930, and the second random access message component may each be a processor (e.g., a transceiver processor, or a radio processor, or a transmitter processor, or a receiver processor) or at least part of a processor. The processor may be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate the features of the SSB component 925, the first random access message component 930, and the second random access message component discussed herein. The transceiver processor may be collocated with and / or communicate with (e.g., direct the operation of) a transceiver of the device. The radio processor may be collocated with and / or communicate with (e.g., direct the operation of) radio components of the device (e.g., NR radio components, LTE radio components, Wi-Fi radio components). The transmitter processor may be collocated with and / or communicate with (e.g., direct the operation of) a transmitter of the device. The receiver processor may be collocated with and / or communicate with (e.g., direct the operation of) a receiver of the device.

[0173] Figure 11 Block diagram 1100 illustrates a communication manager 1120 that supports implicit PRACH repetition indication according to one or more examples as disclosed herein. The communication manager 1120 may be an example of aspects of the communication manager 920, the communication manager 1020, or both as described herein. The communication manager 1120 or its various components may be examples of components for performing aspects of implicit PRACH repetition indication as described herein. For example, the communication manager 1120 may include an SSB component 1125, a first random access message component 1130, a second random access message component 1135, a random access channel format component 1140, an uplink shared channel random access message component 1145, a control signaling component 1150, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0174] Additionally or alternatively, according to examples as disclosed herein, communication manager 1120 may support wireless communication at a network node. The SSB component 1125 may be configured to or otherwise support components for transmitting a set of multiple synchronization signal blocks associated with a random access procedure. The first random access message component 1130 may be configured to or otherwise support components for receiving a number of first random access messages, where the number of the first random access messages is based on a random access channel format associated with the random access procedure, a configured number of uplink shared channel random access message repetitions, or both. The second random access message component 1135 may be configured to or otherwise support components for transmitting a second random access message based on the number of the first random access messages.

[0175] In some examples, the number of the first random access messages is based on the length of the random access channel format.

[0176] In some examples, the number of the first random access messages is equal to the configured number of uplink shared channel random access message repetitions.

[0177] In some examples, the number of the first random access messages is based on the configured number of uplink shared channel random access repetitions and the random access channel format.

[0178] In some examples, the number of the first random access messages is less than the configured number of uplink shared channel random access repetitions based on the random access channel format.

[0179] In some examples, the control signaling component 1150 may be configured to or otherwise support components for transmitting control signaling indicating the configured number of uplink shared channel random access message repetitions.

[0180] In some examples, the control signaling includes a random access response uplink grant or downlink control information.

[0181] In some examples, the number of uplink shared channel random access message repetitions is a default number of uplink shared channel random access message repetitions.

[0182] In some examples, the number of the first random access messages for initial access is based on the configured number of uplink shared channel random access message repetitions associated with the initial access.

[0183] In some examples, the number of the first random access messages for retransmission is based on the configured number of uplink shared channel random access message repetitions associated with initial access or retransmission.

[0184] In some examples, the number of the first random access messages for retransmission is based on the configured number of uplink shared channel random access message repetitions, which is the maximum number, minimum number, or statistical number associated with a first configured number of uplink shared channel random access message repetitions for initial access and a second configured number of uplink shared channel random access message repetitions for retransmission.

[0185] In some cases, the SSB component 1025, the first random access message component 1030, the second random access message component 1035, the random access channel format component 1040, the uplink shared channel random access message component 1045, and the control signaling component 1050 may each be a processor (e.g., a transceiver processor, or a radio processor, or a transmitter processor, or a receiver processor) or at least part of a processor. The processor may be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate the features of the SSB component 1025, the first random access message component 1030, the second random access message component 1035, the random access channel format component 1040, the uplink shared channel random access message component 1045, and the control signaling component 1050 discussed herein.

[0186] Figure 12 FIG. illustrates a system 1200 of a device 1205 supporting implicit PRACH repetition indication according to one or more examples as disclosed herein. The device 1205 may be an example of the device 905, the device 1005, or a network node as described herein or include components of these devices. The device 1205 may include components for two-way voice and data communication, which include components for sending and receiving communications, such as a communication manager 1220, a transceiver 1210, an antenna 1215, a memory 1225, code 1230, and a processor 1235. These components may communicate electronically via one or more buses (e.g., bus 1240) or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) coupled.

[0187] The transceiver 1210 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1210 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1210 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1205 may include one or more antennas 1215, which may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1210 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1215, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1215, from a wired receiver); and demodulating the signal. In some implementations, the transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1215 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1215 configured to support various sending or outputting operations, or a combination thereof. In some implementations, the transceiver 1210 may include or be configured to be coupled to one or more processors or memory components, which are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1210, or the transceiver 1210 and one or more antennas 1215, or the transceiver 1210 and one or more antennas 1215 and one or more processors or memory components (e.g., processor 1235 or memory 1225 or both) may be included in a chip or chip assembly installed in the device 1205. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0188] The memory 1225 may include RAM and ROM. The memory 1225 may store computer-readable, computer-executable code 1230 including instructions that, when executed by the processor 1235, cause the device 1205 to perform the various functions described herein. The code 1230 may be stored in a non-transitory computer-readable medium (such as system memory or another type of memory). In some cases, the code 1230 may not be directly executable by the processor 1235 but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 1225 may also contain BIOS and the like, which may control basic hardware or software operations, such as interactions with peripheral components or devices.

[0189] Processor 1235 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1235. Processor 1235 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1225) to cause device 1205 to perform various functions (e.g., functions or tasks supporting implicit PRACH repetition indication). For example, device 1205 or components of device 1205 may include processor 1235 and memory 1225 coupled to processor 1235, and the processor 1235 and memory 1225 are configured to perform the various functions described herein. Processor 1235 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that may host functions for performing the functions of device 1205 (e.g., by executing code 1230). Processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1205 (such as within memory 1225). In some specific implementations, processor 1235 may be a component of a processing system. A processing system generally may refer to a system or series of machines or components that receive inputs and process those inputs to produce a set of outputs (which may be delivered to other systems or components of, for example, device 1205). For example, the processing system of device 1205 may refer to a system including various other components or sub-components of device 1205 (such as processor 1235, or transceiver 1210, or communication manager 1220, or a combination of other components or components of device 1205). The processing system of device 1205 may interface with other components of device 1205 and may process information (such as inputs or signals) received from other components or output information to other components. For example, a chip or modem of device 1205 may include a processing system and one or more interfaces for outputting information or for obtaining information or both. One or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information or the same interface configured to output information and obtain information, etc. In some specific implementations, one or more interfaces may refer to an interface between the processing system of a chip or modem and a transmitter such that device 1205 may transmit information output from the chip or modem. Additionally or alternatively, in some specific implementations, one or more interfaces may refer to an interface between the processing system of a chip or modem and a receiver such that device 1205 may obtain information or signal inputs, and the information may be delivered to the processing system.One of ordinary skill in the art will readily recognize that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.

[0190] In some examples, bus 1240 may support communication within a protocol layer of a protocol stack (e.g., within a protocol layer). In some examples, bus 1240 may support communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which communication may include communication performed within components of device 1205, or communication performed between different components that may be co-located or located at different locations within device 1205 (e.g., where device 1205 may refer to a system in which one or more of communication manager 1220, transceiver 1210, memory 1225, code 1230, and processor 1235 may be located in one component or divided among different components).

[0191] In some examples, communication manager 1220 may manage (e.g., via one or more wired or wireless backhaul links) aspects of communication with core network 130. For example, communication manager 1220 may manage the delivery of data communication for client devices such as one or more UEs 115. In some examples, communication manager 1220 may manage communication with other network nodes 105, and may include a controller or scheduler for coordinating with other network nodes 105 to control communication with UEs 115. In some examples, communication manager 1220 may support the X2 interface within the LTE / LTE-A wireless communication network technology to provide communication between network nodes 105.

[0192] Additionally or alternatively, according to examples as disclosed herein, communication manager 1220 may support wireless communication at a network node. For example, communication manager 1220 may be configured or otherwise support components for transmitting a set of multiple synchronization signal blocks associated with a random access procedure. Communication manager 1220 may be configured or otherwise support components for receiving a certain number of first random access messages, where the number of first random access messages is based on a random access channel format associated with the random access procedure, a configured number of uplink shared channel random access message repetitions, or both. Communication manager 1220 may be configured or otherwise support components for transmitting a second random access message based on the number of first random access messages.

[0193] By including or configuring communication manager 1220 according to examples as described herein, device 1205 may support techniques for improving communication reliability, reducing latency, improving the user experience associated with reduced processing, reducing power consumption, more efficiently utilizing communication resources, improving coordination between devices, extending battery life, improving utilization of processing capabilities, or any combination thereof.

[0194] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise in cooperation with the transceiver 1210, one or more antennas 1215 (e.g., where applicable), or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more of the functions described with reference to the communication manager 1220 may be supported or performed by the transceiver 1210, the processor 1235, the memory 1225, the code 1230, or any combination thereof. For example, the code 1230 may include instructions executable by the processor 1235 to cause the device 1205 to perform aspects of implicit PRACH repetition indication as described herein, or the processor 1235 and the memory 1225 may otherwise be configured to perform or support such operations.

[0195] Figure 13 A flowchart illustrating a method 1300 supporting implicit PRACH repetition indication in accordance with one or more examples disclosed herein is illustrated. Operations of the method 1300 may be implemented by a UE or components thereof as described herein. For example, operations of the method 1300 may be performed by the UE 115 as described with reference to Figures 1 to 8 In some examples, the UE may execute an instruction set to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0196] At 1305, the method may include: receiving a set of multiple synchronization signal block transmissions associated with a random access procedure. The operation of 1305 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operation of 1305 may be performed by the SSB component 725 as described with reference to Figure 7 In some examples, aspects of the operation of 1305 may be performed by the SSB component 725 as described with reference to

[0197] At 1310, the method may include: transmitting a certain number of first random access messages, where the number of the first random access messages is based on a random access channel format associated with the random access procedure, a configured number of uplink shared channel random access message repetitions, or both. The operation of 1310 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operation of 1310 may be performed by the first random access message component 730 as described with reference to Figure 7 In some examples, aspects of the operation of 1310 may be performed by the first random access message component 730 as described with reference to

[0198] At 1315, the method may include: monitoring for a second random access message based on the number of the first random access messages. The operation of 1315 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operation of 1315 may be performed by the Figure 7performed by the second random access message component 735 as described above.

[0199] Figure 14 Illustrates a flowchart of a method 1400 for supporting implicit PRACH repetition indication according to one or more examples disclosed herein. Operations of method 1400 may be implemented by a network node or its components as described herein. For example, operations of method 1400 may be performed by a network node as referred to Figures 1 to 4 and Figures 9 to 12 as described above. In some examples, the network node may execute an instruction set to control functional elements of the network node to perform the functions. Additionally or alternatively, the network node may use dedicated hardware to perform aspects of the described functions.

[0200] At 1405, the method may include: transmitting a set of multiple synchronization signal blocks associated with a random access procedure. The operation of 1405 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1405 may be performed by the SSB component 1125 as referred to Figure 11 as described above.

[0201] At 1410, the method may include: receiving a certain number of first random access messages, where the number of the first random access messages is based on a random access channel format associated with the random access procedure, a configured number of uplink shared channel random access message repetitions, or both. The operation of 1410 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1410 may be performed by the first random access message component 1130 as referred to Figure 11 as described above.

[0202] At 1415, the method may include: transmitting a second random access message based on the number of the first random access messages. The operation of 1415 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1415 may be performed by the second random access message component 1135 as referred to Figure 11 as described above.

[0203] An overview of aspects of the present disclosure is provided below:

[0204] Aspect 1: A method for wireless communication at a UE, the method including: receiving a set of multiple synchronization signal blocks associated with a random access procedure; transmitting a certain number of first random access messages, where the number of the first random access messages is at least partially based on a random access channel format associated with the random access procedure, a configured number of uplink shared channel random access message repetitions, or both; and monitoring a second random access message at least partially based on the number of the first random access messages.

[0205] Aspect 2: The method according to aspect 1, wherein the number of the first random access messages is at least partially based on the length of the random access channel format.

[0206] Aspect 3: The method according to any one of aspects 1 to 2, wherein the number of the first random access messages is equal to the configured number of repetitions of the uplink shared channel random access message.

[0207] Aspect 4: The method according to any one of aspects 1 to 3, wherein the number of the first random access messages is at least partially based on the configured number of repetitions of the uplink shared channel random access repetition and the random access channel format.

[0208] Aspect 5: The method according to any one of aspects 1 to 4, wherein the number of the first random access messages is less than the configured number of repetitions of the uplink shared channel random access repetition that is at least partially based on the random access channel format.

[0209] Aspect 6: The method according to any one of aspects 1 to 5, the method further comprising: receiving control signaling indicating the configured number of repetitions of the uplink shared channel random access message.

[0210] Aspect 7: The method according to aspect 6, wherein the control signaling includes a random access response uplink grant or downlink control information.

[0211] Aspect 8: The method according to any one of aspects 1 to 7, wherein the number of repetitions of the uplink shared channel random access message is the default number of repetitions of the uplink shared channel random access message.

[0212] Aspect 9: The method according to any one of aspects 1 to 8, wherein the number of the first random access messages for initial access is at least partially based on the configured number of repetitions of the uplink shared channel random access message associated with the initial access.

[0213] Aspect 10: The method according to any one of aspects 1 to 9, wherein the number of the first random access messages for retransmission is at least partially based on the configured number of repetitions of the uplink shared channel random access message associated with the initial access or retransmission.

[0214] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the number of the first random access messages for retransmission is at least partially based on the configured number of repetitions of the uplink shared channel random access message, and the configured number is the maximum number, minimum number, or statistical number associated with a first configured number of repetitions of the uplink shared channel random access message for initial access and a second configured number of repetitions of the uplink shared channel random access message for retransmission.

[0215] Aspect 12: A method for wireless communication at a network node, the method comprising: transmitting a plurality of synchronization signal blocks associated with a random access procedure; receiving a certain number of first random access messages, wherein the number of the first random access messages is at least partially based on a random access channel format associated with the random access procedure, a configured number of repetitions of the uplink shared channel random access message, or both; and transmitting a second random access message at least partially based on the number of the first random access messages.

[0216] Aspect 13: The method according to Aspect 12, wherein the number of the first random access messages is at least partially based on the length of the random access channel format.

[0217] Aspect 14: The method according to any one of Aspects 12 to 13, wherein the number of the first random access messages is equal to the configured number of repetitions of the uplink shared channel random access message.

[0218] Aspect 15: The method according to any one of Aspects 12 to 14, wherein the number of the first random access messages is at least partially based on the configured number of repetitions of the uplink shared channel random access repetition and the random access channel format.

[0219] Aspect 16: The method according to any one of Aspects 12 to 15, wherein the number of the first random access messages is less than the configured number of repetitions of the uplink shared channel random access repetition at least partially based on the random access channel format.

[0220] Aspect 17: The method according to any one of Aspects 12 to 16, the method further comprising: transmitting control signaling indicating the configured number of repetitions of the uplink shared channel random access message.

[0221] Aspect 18: The method according to Aspect 17, wherein the control signaling includes a random access response uplink grant or downlink control information.

[0222] Aspect 19: The method according to any one of Aspects 12 to 18, wherein the number of repetitions of the uplink shared channel random access message is the default number of repetitions of the uplink shared channel random access message.

[0223] Aspect 20: The method according to any one of Aspects 12 to 19, wherein the number of the first random access messages for initial access is at least partially based on the configured number of repetitions of the uplink shared channel random access message associated with the initial access.

[0224] Aspect 21: The method according to any one of Aspects 12 to 20, wherein the number of the first random access messages for retransmission is at least partially based on the configured number of repetitions of the uplink shared channel random access message associated with initial access or retransmission.

[0225] Aspect 22: The method according to any one of Aspects 12 to 21, wherein the number of the first random access messages for retransmission is at least partially based on the configured number of repetitions of the uplink shared channel random access message, and the configured number is the maximum number, minimum number, or statistical number associated with a first configured number of repetitions of the uplink shared channel random access message for initial access and a second configured number of repetitions of the uplink shared channel random access message for retransmission.

[0226] Aspect 23: An apparatus for wireless communication at a UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to any one of Aspects 1 to 11.

[0227] Aspect 24: An apparatus for wireless communication at a UE, the apparatus comprising: at least one component for performing the method according to any one of Aspects 1 to 11.

[0228] Aspect 25: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of Aspects 1 to 11.

[0229] Aspect 26: An apparatus for wireless communication at a network node, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to any one of Aspects 12 to 22.

[0230] Aspect 27: An apparatus for wireless communication at a network node, the apparatus comprising at least one component for performing the method according to any one of Aspects 12 to 22.

[0231] Aspect 28: A non-transitory computer-readable medium storing code for wireless communication at a network node, the code including instructions executable by a processor to perform the method according to any one of Aspects 12 to 22.

[0232] It should be noted that the methods described herein depict possible specific implementations, and the operations and steps may be rearranged or otherwise modified and other specific implementations are possible. Additionally, aspects from two or more methods may be combined.

[0233] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in much of the description, the techniques described herein are also applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communication systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0234] The information and signals described herein may be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

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

[0236] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these items. The features implementing the functions can also be physically located in different positions, including being distributed such that parts of the functions are implemented at different physical locations.

[0237] Computer-readable media includes both non-transitory computer storage media and communication media, which includes any medium that facilitates transfer of a computer program from one location to another. Non-transitory storage media can be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc read-only memory (CD-ROM) or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer or a general purpose or special purpose processor. Additionally, any connection is properly termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc. Discs can reproduce data optically, while disks can reproduce data magnetically. Combinations of the above are also included within the scope of computer-readable media.

[0238] As used herein (including in the claims), the "or" used in a list of items (e.g., a list of items accompanied by a phrase such as "at least one of" or "one or more of") indicates an inclusive listing such that, for example, the listing of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Additionally, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0239] The term "determine" encompasses a variety of actions and, thus, "determine" can include operations such as calculating, computing, processing, deriving, investigating, looking up (such as looking up in a table, database, or other data structure), and ascertaining. Additionally, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Additionally, "determine" can include parsing, obtaining, selecting, choosing, establishing, and other such like actions.

[0240] In the drawings, like reference numerals may be used to identify like components or features. Additionally, various components of the same type may be distinguished by following the reference numeral with a dash and a second numeral used to differentiate among like components. If only the first reference numeral is used in the specification, the description may apply to any one of the like components having the same first reference numeral, regardless of the second reference numeral or any subsequent reference numerals.

[0241] The description set forth herein with reference to the drawings describes example configurations and does not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration" and not "preferred" or "advantageous over other examples". The detailed description includes specific details for providing an understanding of the described techniques. However, the techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0242] The present disclosure is provided to enable a person of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to a person of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receive a plurality of synchronized signal block transmissions associated with a random access procedure; transmit a certain number of first random access messages, wherein the number of first random access messages is at least partially based on a random access channel format associated with the random access procedure, a configured number of uplink shared channel random access message repetitions, or both; and monitor a second random access message at least partially based on the number of first random access messages.

2. The apparatus of claim 1, wherein the number of first random access messages is at least partially based on the length of the random access channel format.

3. The apparatus of claim 1, wherein the number of first random access messages is equal to the configured number of uplink shared channel random access message repetitions.

4. The apparatus of claim 1, wherein the number of first random access messages is at least partially based on the configured number of uplink shared channel random access repetitions and the random access channel format.

5. The apparatus of claim 1, wherein the number of first random access messages is less than the configured number of uplink shared channel random access repetitions that is at least partially based on the random access channel format.

6. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: receive control signaling indicating the configured number of uplink shared channel random access message repetitions.

7. The apparatus of claim 6, wherein the control signaling comprises a random access response uplink grant or downlink control information.

8. The apparatus of claim 1, wherein the number of uplink shared channel random access message repetitions is a default number of uplink shared channel random access message repetitions.

9. The apparatus of claim 1, wherein the number of first random access messages for initial access is at least partially based on the configured number of uplink shared channel random access message repetitions associated with the initial access.

10. The apparatus of claim 1, wherein the number of first random access messages for retransmission is at least partially based on the configured number of uplink shared channel random access message repetitions associated with initial access or retransmission.

11. The apparatus of claim 1, wherein the number of first random access messages for retransmission is at least partially based on the configured number of uplink shared channel random access message repetitions, the configured number being the maximum number, minimum number, or statistical number associated with a first configured number of uplink shared channel random access message repetitions for initial access and a second configured number of uplink shared channel random access message repetitions for retransmission.

12. An apparatus for wireless communication at a network node, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: transmit a plurality of synchronization signal block transmissions associated with a random access procedure; receive a number of first random access messages, wherein the number of first random access messages is at least partially based on a random access channel format associated with the random access procedure, a configured number of uplink shared channel random access message repetitions, or both; and transmit a second random access message at least partially based on the number of first random access messages.

13. The apparatus according to claim 12, wherein the number of first random access messages is at least partially based on the length of the random access channel format.

14. The apparatus according to claim 12, wherein the number of first random access messages is equal to the configured number of uplink shared channel random access message repetitions.

15. The apparatus according to claim 12, wherein the number of first random access messages is at least partially based on the configured number of uplink shared channel random access repetitions and the random access channel format.

16. The apparatus according to claim 12, wherein the number of first random access messages is less than the configured number of uplink shared channel random access repetitions that is at least partially based on the random access channel format.

17. The apparatus according to claim 12, wherein the instructions are further executable by the processor to cause the apparatus to: transmit control signaling indicating the configured number of uplink shared channel random access message repetitions.

18. The apparatus according to claim 17, wherein the control signaling comprises a random access response uplink grant or downlink control information.

19. The apparatus according to claim 12, wherein the number of uplink shared channel random access message repetitions is a default number of uplink shared channel random access message repetitions.

20. The apparatus according to claim 12, wherein the number of first random access messages for initial access is at least partially based on the configured number of uplink shared channel random access message repetitions associated with the initial access.

21. The apparatus according to claim 12, wherein the number of first random access messages for retransmission is at least partially based on the configured number of uplink shared channel random access message repetitions associated with initial access or retransmission.

22. The apparatus according to claim 12, wherein the number of first random access messages for retransmission is at least partially based on the configured number of uplink shared channel random access message repetitions, which is the maximum number, minimum number, or statistical number associated with a first configured number of uplink shared channel random access message repetitions for initial access and a second configured number of uplink shared channel random access message repetitions for retransmission.

23. A method for wireless communication at a user equipment (UE), the method comprises: receiving multiple synchronization signal block transmissions associated with a random access procedure; transmitting a certain number of first random access messages, wherein the number of the first random access messages is at least partially based on a random access channel format associated with the random access procedure, a configured number of uplink shared channel random access message repetitions, or both; and monitoring a second random access message at least partially based on the number of the first random access messages.

24. The method according to claim 23, wherein the number of the first random access messages is at least partially based on the length of the random access channel format.

25. The method according to claim 23, wherein the number of the first random access messages is equal to the configured number of uplink shared channel random access message repetitions.

26. The method according to claim 23, wherein the number of the first random access messages is at least partially based on the configured number of uplink shared channel random access repetitions and the random access channel format.

27. A method for wireless communication at a network node, the method comprises: transmitting multiple synchronization signal block transmissions associated with a random access procedure; receiving a certain number of first random access messages, wherein the number of the first random access messages is at least partially based on a random access channel format associated with the random access procedure, a configured number of uplink shared channel random access message repetitions, or both; and transmitting a second random access message at least partially based on the number of the first random access messages.

28. The method according to claim 27, wherein the number of the first random access messages is at least partially based on the length of the random access channel format.

29. The method according to claim 27, wherein the number of the first random access messages is equal to the configured number of uplink shared channel random access message repetitions.

30. The method according to claim 27, wherein the number of the first random access messages is at least partially based on the configured number of uplink shared channel random access repetitions and the random access channel format.

Images