Patent Description:
Long Term Evolution (LTE), fifth generation (<NUM>) new radio (NR), and other recently developed communication technologies allow wireless devices to communicate information at data rates (e.g., in terms of Gigabits per second, etc.) that are orders of magnitude greater than what was available just a few years ago. One of the methods used for increasing data rates involve transmitting radio frequency (RF) signals toward receiver devices using beam forming antennas rather than via omnidirectional antenna, thereby increasing the number of wireless devices that may be supported by a given base station while increasing transmission power directed at a particular wireless device.

Today's communication networks are also more secure, resilient to multipath fading, allow for lower network traffic latencies, provide better communication efficiencies (e.g., in terms of bits per second per unit of bandwidth used, etc.). These and other recent improvements have facilitated the emergence of the Internet of Things (IOT), large scale Machine to Machine (M2M) communication systems, autonomous vehicles, and other technologies that rely on consistent and secure communications. 3GPP draft RP-<NUM> describes aspects of new radio RF repeaters. <CIT> describes aspects of transmitting a random access preamble to a base station and receiving a random access response from the base station through reception beamforming.

Various aspects include methods for beam sweep configuration of a millimeter wave (MMW) repeater in a fifth generation (<NUM>) network during random access channel (RACH) procedures. In various aspects, the methods may be performed by a processor of a network device, such as a Next Generation NodeB (gNB), etc., and/or performed by a processor of an MMW repeater.

Various aspects may include receiving an RACH <NUM> message relayed by an MMW repeater, determining a beam sweep schedule for use by the MMW repeater in relaying a random access response (RAR) message in response to the RACH <NUM> message, the beam sweep schedule indicating a series of RAR messages to be sent successively and a different transmit (TX) beam sweep configuration to be used by the MMW repeater for each of the series of RAR messages, generating an RAR control message indicating the beam sweep schedule, sending the RAR control message to the MMW repeater, and sending the series of RAR messages to the MMW repeater.

Various aspects may further include receiving a message <NUM> relayed by the MMW repeater, wherein the message <NUM> is generated in response to at least one of the series of RAR messages, determining a suitable beam for communicating with a computing device based at least in part on the message <NUM>, and sending a cancelation message to the MMW repeater in response to determining that the suitable beam for communicating with the computing device, in which the cancelation message is configured to cause the MMW repeater to cancel any remaining RAR messages in the beam sweep schedule. In some aspects, the message <NUM> may be relayed by the MMW repeater according to one or more conditions indicated in the RAR control message.

Various aspects may further include determining a suitable beam for communicating with a computing device based at least in part on the message <NUM> and sending an indication of the suitable beam to the MMW repeater.

In some aspects, the different TX beam sweep configuration associated with a first of the series of RAR messages to be sent according to the beam sweep schedule may generate a same beam as used by the MMW repeater to receive the RACH <NUM> message or forward a synchronization signal block (SSB).

Various aspects may further include receiving an RACH <NUM> message relayed by an MMW repeater, determining a beam sweep schedule for use by the MMW repeater in relaying an RAR message in response to the RACH <NUM> message, wherein the beam sweep schedule indicates a series of RAR messages to be sent successively and a different TX beam sweep configuration to be used by the MMW repeater for each of the series of RAR messages, selecting an initial RAR message of the series of RAR messages to send, generating an initial RAR control message indicating the different TX beam sweep configuration associated with the selected initial RAR message, sending the initial RAR control message to the MMW repeater, and sending the selected initial RAR message to the MMW repeater.

Various aspects may further include determining whether a message <NUM> relayed by the MMW repeater in response to the initial RAR control message is successfully received, and determining a suitable beam for communicating with a UE computing device based at least in part on the message <NUM> in response to determining that the message <NUM> relayed by the MMW repeater in response to the initial RAR control message was successfully received.

Various aspects may further include sending an indication of the suitable beam to an MMW repeater and sending a message <NUM> to be relayed by the repeater to the computing device using the suitable beam.

Various aspects may further include, in response to determining that a message <NUM> relayed by the MMW repeater in response to the initial RAR control message was not successfully received, selecting a next RAR message of the series of RAR messages to send, generating a next RAR control message indicating the different TX beam sweep configuration associated with the selected next RAR message, sending the next RAR control message to the MMW repeater, and sending the selected next RAR message to the MMW repeater.

In some aspects, the different TX beam sweep configuration associated with the selected next RAR message may generate a narrower beam than a beam generated by the different TX beam sweep configuration associated with the selected initial RAR message. In some aspects, the different TX beam sweep configuration associated with a first of the series of RAR messages to be sent according to the beam sweep schedule may generate a same beam as used by the MMW repeater to receive the RACH <NUM> message or forward an SSB.

In some aspects, the different TX beam sweep configurations indicated in the beam sweep schedule may be determined based at least in part on an attribute of the RACH <NUM> message. In some aspects, the attribute of the RACH <NUM> message may be a received power of the RACH <NUM> message or a received timing of the RACH <NUM> message. In some aspects, the attribute of the RACH <NUM> message is determined by the gNB. In some aspects, the attribute of the RACH <NUM> message is indicated to the gNB by the MMW repeater.

Various aspects may further include receiving an RAR control message from a network device indicating a beam sweep schedule, wherein the beam sweep schedule indicates a series of RAR messages to be sent successively and a different TX beam sweep configuration to be used by the MMW repeater for each of the series of RAR messages, receiving the series of RAR messages from the gNB, and controlling one or more TX antennas of the MMW repeater according to the RAR control message to successively relay each of the series of RAR messages using that RAR message's respective different TX beam sweep configuration.

Various aspects may further include receiving a cancelation message from the network device, and canceling the relay of any remaining RAR messages in the beam sweep schedule in response to receiving the cancelation message. In some aspects, the different TX beam sweep configuration associated with a first of the series of RAR messages relayed according to the beam sweep schedule may generate a same beam as used by the MMW repeater to receive a RACH <NUM> message or forward an SSB. In some aspects, the network device may be a gNB.

Various aspects may further include receiving an indication of a suitable beam for communicating with a computing device and relaying a message <NUM> to the computing device using the suitable beam.

Various aspects may further include receiving an initial RAR control message indicating an initial TX beam sweep configuration associated with an initial RAR message, receiving the initial RAR message, controlling one or more TX antennas of the MMW repeater according to the initial RAR control message to relay the initial RAR message using the initial TX beam sweep configuration, receiving a next RAR control message indicating a next TX beam sweep configuration associated with a next RAR message, receiving the next RAR message, and controlling one or more TX antennas of the MMW repeater according to the next RAR control message to relay the next RAR message using the next TX beam sweep configuration. In some aspects, the next TX beam sweep configuration may generate a narrower beam than a beam generated by the initial TX beam sweep configuration. In some aspects, the beam generated by the initial TX beam sweep configuration may be a same beam as used by the MMW repeater to receive a RACH <NUM> message or forward an SSB. Various aspects may further include receiving an indication of a suitable beam for communicating with a computing device and relaying a message <NUM> to the computing device using the suitable beam.

Further aspects may include a computing device having a processing device configured to perform one or more operations of any of the methods summarized above. Further aspects may include a processing device configured to perform one or more operations of any of the methods summarized above. Further aspects may include a non-transitory processor-readable storage medium having stored thereon processor-executable instructions configured to cause a processor of a computing device to perform operations of any of the methods summarized above. Further aspects include a computing device having means for performing functions of any of the methods summarized above. Further aspects include a system on chip processing device for use in a computing device configured to perform one or more operations of any of the methods summarized above. Further aspects include a system in a package processing device that includes two systems on chip for use in a computing device and is configured to perform one or more operations of any of the methods summarized above.

Various embodiments will be described in detail with reference to the accompanying drawings. References made to particular examples and implementations are for illustrative purposes, and are not intended to limit the scope of the claims.

The term "computing device" is used herein to refer to any one or all of cellular telephones, smartphones, portable computing devices, personal or mobile multi-media players, laptop computers, tablet computers, smartbooks, ultrabooks, palmtop computers, wireless electronic mail receivers, multimedia Internet-enabled cellular telephones, cellular communication network devices, wireless router devices, wireless appliances, medical devices and equipment, biometric sensors/devices, wearable devices including smart watches, smart clothing, smart glasses, smart wrist bands, smart jewelry (e.g., smart rings, smart bracelets, etc.), entertainment devices (e.g., wireless gaming controllers, music and video players, satellite radios, etc.), wireless-network enabled Internet of Things (IoT) devices including smart meters/sensors, industrial manufacturing equipment, large and small machinery and appliances for home or enterprise use, wireless communication elements within autonomous and semiautonomous vehicles, wireless devices affixed to or incorporated into various mobile platforms, global positioning system devices, and similar electronic devices that include a memory, wireless communication components and a programmable processor.

The term "system in a package" (SIP) may be used herein to refer to a single module or package that contains multiple resources, computational units, cores and/or processors on two or more IC chips, substrates, or SOCs. For example, a SIP may include a single substrate on which multiple IC chips or semiconductor dies are stacked in a vertical configuration. Similarly, the SIP may include one or more multi-chip modules (MCMs) on which multiple ICs or semiconductor dies are packaged into a unifying substrate. A SIP may also include multiple independent SOCs coupled together via high speed communication circuitry and packaged in close proximity, such as on a single motherboard or in a single computing device. The proximity of the SOCs facilitates high speed communications and the sharing of memory and resources.

The term "multicore processor" may be used herein to refer to a single integrated circuit (IC) chip or chip package that contains two or more independent processing cores (e.g., CPU core, Internet protocol (IP) core, graphics processor unit (GPU) core, etc.) configured to read and execute program instructions. A SOC may include multiple multicore processors, and each processor in an SOC may be referred to as a core. The term "multiprocessor" may be used herein to refer to a system or device that includes two or more processing units configured to read and execute program instructions.

The 3rd Generation Partnership Project (3GPP) defines various protocols that support transmissions in wireless networks, such as third generation wireless mobile communication technologies (<NUM>) (e.g., global system for mobile communications (GSM) evolution (EDGE) systems, etc.), fourth generation wireless mobile communication technologies (<NUM>) (e.g., long term evolution (LTE) systems, LTE-Advanced systems, etc.), fifth generation wireless mobile communication technologies (<NUM>) (<NUM> New Radio (NR) (<NUM> NR) systems, etc.), etc. All of the wireless signals associated with various 3GPP protocols face issues with radio signal blockage. However, signal blockage is an especially challenging problem faced in high frequency communications, such as <NUM> communications using millimeter wave (MMW) signals (e.g., MMW signals in mmWave spectrum bands, such as a <NUM>-<NUM> mmWave spectrum band, a <NUM>-<NUM> mmWave spectrum band, a <NUM>-<NUM> mmWave spectrum band, a <NUM>-<NUM> mmWave spectrum band, etc.).

MMW repeaters may be used in wireless networks to mitigate signal blockage for <NUM> communications using MMW signals (e.g., MMW signals in mmWave spectrum bands, such as a <NUM>-<NUM> mmWave spectrum band, a <NUM>-<NUM> mmWave spectrum band, a <NUM>-<NUM> mmWave spectrum band, a <NUM>-<NUM> mmWave spectrum band, etc.). MMW repeaters may provide protections against signal blockage, may extend MMW coverage, and may fill in MMW coverage holes in a wireless network.

In NR, a <NUM> cell, such as a Next Generation NodeB (gNB), may periodically transmit synchronization signal blocks (SSBs) and system information (SI) (e.g., remaining minimum SI (RMSI), which is also referred to as a system information block (SIB) <NUM>. Such information may be transmitted by using beam-sweeping. Following each transmit operation, the <NUM> cell (e.g., a gNB) may perform one or more receive operations to listen for and receive random access channel (RACH) messages from a UE computing device, such as an RACH <NUM> message (also referred to as RACH message (MSG) <NUM> (RACH MSG <NUM>) or message <NUM> (MSG <NUM>) in NR access procedures). Such receive operations to listen for a RACH message from a UE computing device, such as a RACH <NUM> message (RACH message <NUM> or MSG <NUM>), may be referred to as a RACH occurrence (RO). A UE computing device receiving the SSBs and SI (e.g., RMSI) from the <NUM> cell (e.g., a gNB) may attempt random access with the <NUM> cell (e.g., a gNB) by sending a RACH <NUM> message (RACH message <NUM> or MSG <NUM>). In response to the <NUM> cell (e.g., a gNB) successfully receiving an RACH <NUM> message (RACH message <NUM> or MSG <NUM>) from a UE computing device, the <NUM> cell (e.g., a gNB) may send a random access response (RAR) message, such as an RACH <NUM> message (also referred to as an MSG <NUM> in NR access procedures), to the UE computing device. Further transmit and receive operations between the <NUM> cell (e.g., a gNB) and the UE computing device may be performed (e.g., transmit and reception of MSG <NUM>, MSG <NUM>, etc.) to enable wireless network access for the UE computing device via the <NUM> cell (e.g., a gNB).

In network configurations in which one or more repeaters, such as one or more MMW repeaters, are connected to a <NUM> cell (e.g., a gNB), the one or more repeaters, may be configured to relay the various synchronization signals (e.g., SSBs, SI, etc.) and messages (e.g., RACH MSG <NUM>, RACH MSG <NUM> (RAR message), MSG <NUM>, MSG <NUM>, etc.) used in the NR access procedure between the UE computing device and the <NUM> cell (e.g., a gNB). As examples, the MMW repeater may relay an RACH MSG <NUM> from a UE computing device to a gNB, the MMW repeater may relay an RAR message from the gNB to the UE computing device, the MMW repeater may relay the MSG <NUM> from the UE computing device to the gNB, and/or the MMW repeater may relay an MSG <NUM> indicating a suitable beam for communicating between the UE and gNB from the gNB to the UE computing device.

Various embodiments may enable MMW repeaters to support access procedures for UE computing devices in NR. Various embodiments include methods, systems, and devices for beam sweep configuration of an MMW repeater in a <NUM> network during RACH procedures, such as RACH procedures to exchange RAR messages, MSG <NUM>, and MSG <NUM> between gNBs and UE computing devices via an MMW repeater. Various embodiments may enable a gNB to provide an MMW repeater with one or more transmit (TX) beam configurations for use in forwarding RACH message <NUM> (RAR messages) from the gNB to a UE computing device. In some embodiments, the configuration may be dynamically determined and indicated to the MMW repeater along with controls signals that instruct the MMW repeater to forward one or more RAR messages. The control signals may enable the gNB to control resources of the MMW repeater, such as TX power settings, TX beam form settings, etc. In some embodiments, the configuration may be semi-statically determined and indicated to the MMW repeater. In some embodiments, the configuration may be periodic and/or semi-persistent.

Various embodiments may include receiving a RACH message <NUM> from an MMW repeater at a gNB. The RACH message <NUM> may be relayed by the MMW repeater from a UE computing device. The UE computing device may have sent the RACH message <NUM> in response to an SSB sent by the gNB and relayed by the MMW repeater to the UE computing device. The MMW repeater may have relayed the SSB to the UE computing device using a beam form (e.g., a TX beam form), such as an omni-directional or pseudo-omni directional beam, and may have received an RACH message <NUM> in response from the UE computing device using a beam form (e.g., a receive (RX) beam form), such as the same omni-directional or pseudo-omni directional beam used to relay the SSB.

Various embodiments may include determining a beam sweep schedule for use by the MMW repeater in relaying a random access response (RAR) message in response to the RACH <NUM> message. In various embodiments, the beam sweep schedule may indicate a series of RAR messages to be sent successively and a different TX beam sweep configuration to be used by the MMW repeater for each of the series of RAR messages. Similarly, the beam sweep schedule may indicate a series of RX beam sweep configurations to be used by the MMW repeater to receive (or listen for) MSG <NUM> sent by a UE computing device in response to the RAR messages. In various embodiments, the TX beam sweep configuration for the RAR message relay may be the same as the RX beam sweep configuration to receive (or listen for) MSG <NUM>.

In various embodiments, the different TX beam sweep configurations indicated in the beam sweep schedule may be determined based at least in part on an attribute of the RACH <NUM> message. For example, the power of the RACH <NUM> message and/or the timing of the RACH <NUM> message may be used to determine the beam sweep schedule. The received power of the RACH <NUM> message may be calculated by the gNB based on the forwarded RACH message <NUM> or the received power of the RACH <NUM> message may be calculated by the MMW repeater and forwarded to the gNB by the MMW repeater, such as via a control interface.

In various embodiments, the received timing of the RACH <NUM> message may be calculated by the gNB based on the forwarded RACH message <NUM> or the received timing of the RACH <NUM> message may be calculated by the MMW repeater and forwarded to the gNB by the MMW repeater, such as via a control interface.

In various embodiments, RAR control messages may be sent from the gNB to the MMW repeater to indicate one or more beam sweep settings, TX power settings, RX power settings, and/or other MMW repeater settings. In various embodiments, an RAR control message may indicate the determined beam sweep schedule. Indicating the beam sweep schedule may enable the MMW repeater to use the beam sweep schedule to send multiple RAR messages in an RAR window. In various embodiments, an RAR control message may be sent from the gNB to the MMW relay via a control interface, such as via in-band and/or out-of-band interfaces. In some embodiments, an RAR control message may indicate a single beam sweep configuration. In some embodiments, an RAR control message may indicate multiple beam sweep configurations. In some embodiments, an RAR control message may indicate one or more conditions to control a relay of an MSG <NUM> by an MMW repeater. For example, a condition may be an indication to use the same beam to relay the MSG <NUM> as was used to transmit the RAR message that triggered the MSG <NUM>.

In various embodiments, a beam sweep schedule may operate as instructions to an MMW repeater to forward received RAR messages from the gNB using one or multiple TX beams. In some embodiments, the TX beam may be a finer beam (e.g., with a greater beam gain) than the RX beam the MMW repeater used to receive the RACH message <NUM> from a UE computing device and/or a finer beam (e.g., with a greater beam gain) than the TX beam the MMW repeater used to transmit an SSB that may have triggered the RACH message <NUM> transmission by the UE computing device. In some embodiments, the one or more TX beams may be beams that are quasi co-located (QCLed) with the RX beam the MMW repeater used to receive the RACH message <NUM> from a UE computing device and/or that are QCLed the TX beam the MMW repeater used to transmit an SSB that may have triggered the RACH message <NUM> transmission by the UE computing device. In various embodiments, the beam sweep schedule may also configure the MMW repeater's RX beam form for receiving (or listening for) MSG <NUM> to be the same as the TX beam form used to transmit the RAR message.

In various embodiments, based on a relayed MSG <NUM> from the MMW repeater, the gNB may determine a suitable beam for the gNB and MMW repeater to use to communicate with the UE computing device. The gNB may instruct the MMW repeater to use the suitable beam for forwarding an MSG <NUM> to the UE computing device. In some embodiments, the gNB may send an indication of the suitable beam to the MMW repeater. In some scenarios, multiple RAR messages and MSG <NUM> may be overlapping. As such, before all the RAR messages associated with a beam sweep schedule may have been sent, a suitable beam for UE computing device communications may have been determined by the gNB. In such scenarios, in various embodiments, the gNB may generate and send a cancelation message to the MMW repeater. The cancelation message may be configured to cause the MMW repeater to cancel any remaining RAR messages in the beam sweep schedule. In various embodiments, a gNB may send an MSG <NUM> to the MMW repeater and the MMW repeater may relay the MSG <NUM> to the UE computing device using the suitable beam.

In various embodiments, a gNB may send one or multiple RAR messages one by one (e.g., sequentially). In such embodiments, the gNB may generate an RAR control message for an initial RAR message according to a beam sweep schedule. The initial RAR control message may indicate the TX beam sweep configuration associated with a selected initial RAR message. In some embodiments, the TX beam sweep configuration for an initial RAR message may be the same beam the MMW repeater used to receive the RACH message <NUM> from a UE computing device (e.g., the initial TX beam may correspond to the RX beam on which the RACH message <NUM> was received by the MMW repeater) and/or may be the same beam the MMW repeater used to transmit an SSB that may have triggered the RACH message <NUM> transmission by the UE computing device (e.g., the initial TX beam may correspond to the TX beam on which the SSB was transmitted by the MMW repeater). The initial RAR message may also configure the MMW repeater's RX beam form for receiving (or listening for) MSG <NUM> to be the same as the TX beam form used to transmit the initial RAR message.

In various embodiments, the gNB may determine whether an MSG <NUM> is relayed by the MMW repeater. In response to determining, no MSG <NUM> has been relayed by the MMW repeater, the gNB may select a next RAR message of the series of RAR messages to send. The gNB may generate a next RAR control message indicating the TX beam sweep configuration associated with the next RAR message. The gNB may send the next RAR control message and the next RAR message to the MMW repeater. In some embodiments, the TX beam sweep configuration for the next RAR message may be a finer beam than that generated by the initial RAR control message. In response to determining that the MSG <NUM> is relayed by the MMW repeater, the gNB may determine a suitable beam for the gNB and MMW repeater to use to communicate with the UE computing device. The gNB may instruct the MMW repeater to use the suitable beam for forwarding an MSG <NUM> to the UE computing device. In various embodiments, the gNB may send an indication of the suitable beam for communicating with the UE computing device to the MMW repeater. In some embodiments, the suitable beam may be the beam used to relay the RAR message that resulted in the MSG <NUM> being received from the UE computing device. In various embodiments, the MMW repeater may receive an indication of a suitable beam for communicating with the UE computing device. The MMW repeater may relay an MSG <NUM> from the gNB to the UE computing device using the suitable beam. For example, the MMW repeater may control one or more antennas to send an MSG <NUM> received from the gNB to the UE computing device using the suitable beam.

<FIG> illustrates an example of a communications system <NUM> that is suitable for implementing various embodiments. The communications system <NUM> may be an <NUM> NR network, or any other suitable network such as an LTE network.

The communications system <NUM> may include a heterogeneous network architecture that includes a core network <NUM> and a variety of mobile devices (also referred to as user equipment (UE) computing devices) (illustrated as wireless device 120a-120e in <FIG>). The communications system <NUM> may also include a number of base stations (illustrated as the BS 110a, the BS 110b, the BS 110c, and the BS 110d) and other network entities. A base station is an entity that communicates with computing devices (mobile devices or UE computing devices), and also may be referred to as an NodeB, a Node B, an LTE evolved nodeB (eNB), an access point (AP), a radio head, a transmit receive point (TRP), a New Radio base station (NR BS), a <NUM> NodeB (NB), a Next Generation NodeB (gNB), or the like. Each base station may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" can refer to a coverage area of a base station, a base station subsystem serving this coverage area, or a combination thereof, depending on the context in which the term is used.

A base station 110a-110d may provide communication coverage for a macro cell, a pico cell, a femto cell, another type of cell, or a combination thereof. A macro cell may cover a relatively large geographic area (for example, several kilometers in radius) and may allow unrestricted access by mobile devices with service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by mobile devices with service subscription. A femto cell may cover a relatively small geographic area (for example, a home) and may allow restricted access by mobile devices having association with the femto cell (for example, mobile devices in a closed subscriber group (CSG)). A base station for a macro cell may be referred to as a macro BS. A base station for a pico cell may be referred to as a pico BS. A base station for a femto cell may be referred to as a femto BS or a home BS. In the example illustrated in <FIG>, a base station 110a may be a macro BS for a macro cell 102a, a base station 110b may be a pico BS for a pico cell 102b, and a base station 110c may be a femto BS for a femto cell 102c. A base station 110a-110d may support one or multiple (for example, three) cells.

In some examples, a cell may not be stationary, and the geographic area of the cell may move according to the location of a mobile base station. In some examples, the base stations 110a-110d may be interconnected to one another as well as to one or more other base stations or network nodes (not illustrated) in the communications system <NUM> through various types of backhaul interfaces, such as a direct physical connection, a virtual network, or a combination thereof using any suitable transport network.

The base station 110a-110d may communicate with the core network <NUM> over a wired or wireless communication link <NUM>. The computing device 120a-120e (UE computing device) may communicate with the base station 110a-110d over a wireless communication link <NUM>.

The communications system <NUM> also may include relay stations (e.g., relay BS 110d). A relay station is an entity that can receive a transmission of data from an upstream station (for example, a base station or a mobile device) and send a transmission of the data to a downstream station (for example, a wireless device or a base station). A relay station also may be a mobile device that can relay transmissions for other computing devices. In the example illustrated in <FIG>, a relay station 110d may communicate with macro the base station 110a and the computing device 120d in order to facilitate communication between the base station 110a and the computing device 120d. A relay station also may be referred to as a relay base station, a relay base station, a relay, a repeater, etc..

As a specific example, one type of relay BS 110d may be a millimeter wave (MMW) repeater. An MMW repeater (e.g., relay BS 110d) may relay MMW signals (e.g., MMW signals in mmWave spectrum bands, such as a <NUM>-<NUM> mmWave spectrum band, a <NUM>-<NUM> mmWave spectrum band, a <NUM>-<NUM> mmWave spectrum band, a <NUM>-<NUM> mmWave spectrum band, etc.) between MMW enabled devices, such as between a gNB (e.g., macro BS 110a) and a computing device 120d. An MMW repeater (e.g., relay BS 110d) may provide protection against blockage of an MMW cell, such as a gNB (e.g., macro BS 110a), extend the coverage of the MMW cell, such as a gNB (e.g., macro BS 110a), and/or fill in coverage holes of the MMW cell, such as a gNB (e.g., macro BS 110a).

An MMW repeater (e.g., relay BS 110d) may receive one or more signals on or more of its receiver (RX) antennas based on one or more RX beamforming configurations, amplify the power of the one or more received signals, and transmit the one or more amplified signals from one or more of its transmitter (TX) antennas based on one or more TX beamforming configurations. An MMW repeater (e.g., relay BS 110d) may also exchange one or more control signals with other network devices (e.g., macro BS 110a, network controller <NUM>, donor nodes, control nodes, servers, etc.) via one or more control interfaces. A control interface may be an out-of-band interface using a different radio technology, such as Bluetooth, Bluetooth Low Energy (LE), etc., and/or a different frequency (e.g., the frequencies designated for LTE narrowband internet of things (NB-IoT) (LTE NB-IoT). Additionally, or alternatively, a control interface may be an in-band interface using bandwidth of the same carrier frequency (e.g., bandwidth of MMW signals in a mmWave spectrum band).

In some configurations, an MMW repeater (e.g., relay BS 110d) may be a low power relay with less functionality than a gNB (e.g., macro BS 110a). For example, the MMW repeater (e.g., relay BS 110d) may receive analog signals on its RX antennas, amplify the power of the received analog signals, and transmit the amplified analog signals from its TX antennas. Such example reduced functionality MMW repeaters (e.g., relay BS 110d) may not include analog-to-digital converters or digital-to-analog converters in their signal paths. Such example reduced functionality MMW repeaters (e.g., relay BS 110d) may be referred to as Layer <NUM> (L1) and/or physical layer (PHY) repeaters.

In various embodiments, the RX beamforming configurations, TX beamforming configurations, and/or power amplification settings of the MMW repeater (e.g., relay BS 110d) may be controlled by a gNB (e.g., macro BS 110a) that the MMW repeater may be supporting and/or another network device (e.g., network controller <NUM>, donor nodes, control nodes, servers, etc.).

The computing devices (UE computing devices) 120a, 120b, 120c may be dispersed throughout communications system <NUM>, and each computing device may be stationary or mobile. A computing device also may be referred to as an access terminal, a UE, a terminal, a mobile station, a subscriber unit, a station, etc..

A macro base station 110a may communicate with the communication network <NUM> over a wired or wireless communication link <NUM>. The computing devices 120a, 120b, 120c may communicate with a base station 110a-110d over a wireless communication link <NUM>.

The wireless communication links <NUM>, <NUM> may include a plurality of carrier signals, frequencies, or frequency bands, each of which may include a plurality of logical channels. The wireless communication links <NUM> and <NUM> may utilize one or more radio access technologies (RATs). Examples of RATs that may be used in a wireless communication link include 3GPP LTE, <NUM>, <NUM>, <NUM> (e.g., NR), GSM, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMAX), Time Division Multiple Access (TDMA), and other mobile telephony communication technologies cellular RATs. Further examples of RATs that may be used in one or more of the various wireless communication links <NUM>, <NUM> within the communication system <NUM> include medium range protocols such as Wi-Fi, LTE-U, LTE-Direct, LAA, MuLTEfire, and relatively short range RATs such as ZigBee, Bluetooth, and Bluetooth Low Energy (LE).

For example, the spacing of the subcarriers may be <NUM> and the minimum resource allocation (called a "resource block") may be <NUM> subcarriers (or <NUM>). Consequently, the nominal Fast File Transfer (FFT) size may be equal to <NUM>, <NUM>, <NUM>, <NUM> or <NUM> for system bandwidth of <NUM>, <NUM>, <NUM>, <NUM> or <NUM> megahertz (MHz), respectively. For example, a subband may cover <NUM> (i.e., <NUM> resource blocks), and there may be <NUM>, <NUM>, <NUM>, <NUM> or <NUM> subbands for system bandwidth of <NUM>, <NUM>, <NUM>, <NUM> or <NUM>, respectively.

While descriptions of some embodiments may use terminology and examples associated with LTE technologies, various embodiments may be applicable to other wireless communications systems, such as a new radio (NR) or <NUM> network. NR may utilize OFDM with a cyclic prefix (CP) on the uplink (UL) and downlink (DL) and include support for half-duplex operation using time division duplex (TDD). A single component carrier bandwidth of <NUM> may be supported. NR resource blocks may span <NUM> sub-carriers with a subcarrier bandwidth of <NUM> over a <NUM> millisecond (ms) duration. Each radio frame may consist of <NUM> subframes with a length of <NUM>. Consequently, each subframe may have a length of <NUM>. Each subframe may indicate a link direction (i.e., DL or UL) for data transmission and the link direction for each subframe may be dynamically switched. Each subframe may include DL/UL data as well as DL/UL control data. Multiple Input Multiple Output (MIMO) transmissions with precoding may also be supported. MIMO configurations in the DL may support up to eight transmit antennas with multi-layer DL transmissions up to eight streams and up to two streams per computing device. Multi-layer transmissions with up to <NUM> streams per computing device may be supported. Aggregation of multiple cells may be supported with up to eight serving cells. Alternatively, NR may support a different air interface, other than an OFDM-based air interface.

Some mobile devices may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) mobile devices. MTC and eMTC mobile devices include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., that may communicate with a base station, another device (for example, remote device), or some other entity. A wireless node may provide, for example, connectivity for or to a network (for example, a wide area network such as Internet or a cellular network) via a wired or wireless communication link. Some mobile devices may be considered Internet-of-Things (IoT) devices or may be implemented as NB-IoT (narrowband internet of things) devices. A computing device 120a-e may be included inside a housing that houses components of the computing device, such as processor components, memory components, similar components, or a combination thereof.

In general, any number of communications systems and any number of wireless networks may be deployed in a given geographic area. Each communications system and wireless network may support a particular radio access technology (RAT) and may operate on one or more frequencies. A RAT also may be referred to as a radio technology, an air interface, etc. A frequency also may be referred to as a carrier, a frequency channel, etc. Each frequency may support a single RAT in a given geographic area in order to avoid interference between communications systems of different RATs.

In some implementations, two or more mobile devices 120a-e (for example, illustrated as the computing device 120a and the computing device 120e) may communicate directly using one or more sidelink channels <NUM> (for example, without using a base station 110a-<NUM>10d as an intermediary to communicate with one another). For example, the computing devices 120a-e may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or similar protocol), a mesh network, or similar networks, or combinations thereof. In this case, the computing device 120a-e may perform scheduling operations, resource selection operations, as well as other operations described elsewhere herein as being performed by the base station 110a.

Various embodiments may be implemented on a number of single processor and multiprocessor processing devices, including a system-on-chip (SOC) or system in a package (SIP), which may be use in a variety of computing devices. <FIG> illustrates an example processing device or SIP <NUM> architecture that may implement various embodiments and be used in computing devices (UE computing devices) implementing the various embodiments.

With reference to <FIG> and <FIG>, the illustrated example SIP <NUM> includes a two SOCs <NUM>, <NUM>, a clock <NUM>, and a voltage regulator <NUM>. In some embodiments, the first SOC <NUM> operate as central processing unit (CPU) of the computing device that carries out the instructions of software application programs by performing the arithmetic, logical, control and input/output (I/O) operations specified by the instructions. In some embodiments, the second SOC <NUM> may operate as a specialized processing unit. For example, the second SOC <NUM> may operate as a specialized <NUM> processing unit responsible for managing high volume, high speed (e.g., <NUM> Gbps, etc.), and/or very high frequency short wave length (e.g., <NUM> mmWave spectrum, etc.) communications.

The first SOC <NUM> may include a digital signal processor (DSP) <NUM>, a modem processor <NUM>, a graphics processor <NUM>, an application processor <NUM>, one or more coprocessors <NUM> (e.g., vector co-processor) connected to one or more of the processors, memory <NUM>, custom circuity <NUM>, system components and resources <NUM>, an interconnection/bus module <NUM>, one or more temperature sensors <NUM>, a thermal management unit <NUM>, and a thermal power envelope (TPE) component <NUM>. The second SOC <NUM> may include a <NUM> modem processor <NUM>, a power management unit <NUM>, an interconnection/bus module <NUM>, a plurality of mmWave transceivers <NUM>, memory <NUM>, and various additional processors <NUM>, such as an applications processor, packet processor, etc..

The first and second SOC <NUM>, <NUM> may include various system components, resources and custom circuitry for managing sensor data, analog-to-digital conversions, wireless data transmissions, and for performing other specialized operations, such as decoding data packets and processing encoded audio and video signals for rendering in a web browser. For example, the system components and resources <NUM> of the first SOC <NUM> may include power amplifiers, voltage regulators, oscillators, phase-locked loops, peripheral bridges, data controllers, memory controllers, system controllers, access ports, timers, and other similar components used to support the processors and software clients running on a computing device. The system components and resources <NUM> and/or custom circuitry <NUM> may also include circuitry to interface with peripheral devices, such as cameras, electronic displays, wireless communication devices, external memory chips, etc..

The first and second SOC <NUM>, <NUM> may communicate via interconnection/bus module <NUM>. The various processors <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, may be interconnected to one or more memory elements <NUM>, system components and resources <NUM>, and custom circuitry <NUM>, and a thermal management unit <NUM> via an interconnection/bus module <NUM>. Similarly, the processor <NUM> may be interconnected to the power management unit <NUM>, the mmWave transceivers <NUM>, memory <NUM>, and various additional processors <NUM> via the interconnection/bus module <NUM>. The interconnection/bus module <NUM>, <NUM>, <NUM> may include an array of reconfigurable logic gates and/or implement a bus architecture (e.g., CoreConnect, AMBA, etc.). Communications may be provided by advanced interconnects, such as high-performance networks-on chip (NoCs).

The first and/or second SOCs <NUM>, <NUM> may further include an input/output module (not illustrated) for communicating with resources external to the SOC, such as a clock <NUM> and a voltage regulator <NUM>. Resources external to the SOC (e.g., clock <NUM>, voltage regulator <NUM>) may be shared by two or more of the internal SOC processors/cores.

In addition to the example SIP <NUM> discussed above, various embodiments may be implemented in a wide variety of computing systems, which may include a single processor, multiple processors, multicore processors, or any combination thereof.

<FIG> illustrates an example of a software architecture <NUM> including a radio protocol stack for the user and control planes in wireless communications between a base station <NUM> (e.g., the base station 110a) and a computing device (UE computing device) <NUM> (e.g., the computing device 120a-120e, <NUM>). The wireless communications between the base station <NUM> (e.g., the base station 110a) and the computing device (UE computing device) <NUM> (e.g., the computing device 120a-120e, <NUM>) may be direct communications and/or may be communications via a relay, such as an MMW repeater (e.g., the relay BS 110d).

With reference to <FIG>, the computing device <NUM> may implement the software architecture <NUM> to communicate with the base station <NUM> of a communication system (e.g., <NUM>). In various embodiments, layers in software architecture <NUM> may form logical connections with corresponding layers in software of the base station <NUM>. The software architecture <NUM> may be distributed among one or more processors (e.g., the processors <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>). While illustrated with respect to one radio protocol stack, in a multi-SIM (subscriber identity module) computing device, the software architecture <NUM> may include multiple protocol stacks, each of which may be associated with a different SIM (e.g., two protocol stacks associated with two SIMs, respectively, in a dual-SIM wireless communication device). While described below with reference to LTE communication layers, the software architecture <NUM> may support any of variety of standards and protocols for wireless communications, and/or may include additional protocol stacks that support any of variety of standards and protocols wireless communications.

The software architecture <NUM> may include a Non-Access Stratum (NAS) <NUM> and an Access Stratum (AS) <NUM>. The NAS <NUM> may include functions and protocols to support packet filtering, security management, mobility control, session management, and traffic and signaling between a SIM(s) of the computing device (e.g., SIM(s) <NUM>) and its core network <NUM>. The AS <NUM> may include functions and protocols that support communication between a SIM(s) (e.g., SIM(s) <NUM>) and entities of supported access networks (e.g., a base station). In particular, the AS <NUM> may include at least three layers (Layer <NUM>, Layer <NUM>, and Layer <NUM>), each of which may contain various sub-layers.

In the user and control planes, Layer <NUM> (L1) of the AS <NUM> may be a physical layer (PHY) <NUM>, which may oversee functions that enable transmission and/or reception over the air interface. Examples of such physical layer <NUM> functions may include cyclic redundancy check (CRC) attachment, coding blocks, scrambling and descrambling, modulation and demodulation, signal measurements, MIMO, etc. The physical layer may include various logical channels, including the Physical Downlink Control Channel (PDCCH) and the Physical Downlink Shared Channel (PDSCH).

In the user and control planes, Layer <NUM> (L2) of the AS <NUM> may be responsible for the link between the computing device <NUM> and the base station <NUM> over the physical layer <NUM>. In the various embodiments, Layer <NUM> may include a media access control (MAC) sublayer <NUM>, a radio link control (RLC) sublayer <NUM>, and a packet data convergence protocol (PDCP) <NUM> sublayer, each of which form logical connections terminating at the base station <NUM>.

In the control plane, Layer <NUM> (L3) of the AS <NUM> may include a radio resource control (RRC) sublayer <NUM>. While not shown, the software architecture <NUM> may include additional Layer <NUM> sublayers, as well as various upper layers above Layer <NUM>. In various embodiments, the RRC sublayer <NUM> may provide functions including broadcasting system information, paging, and establishing and releasing an RRC signaling connection between the computing device <NUM> and the base station <NUM>.

In various embodiments, the PDCP sublayer <NUM> may provide uplink functions including multiplexing between different radio bearers and logical channels, sequence number addition, handover data handling, integrity protection, ciphering, and header compression. In the downlink, the PDCP sublayer <NUM> may provide functions that include in-sequence delivery of data packets, duplicate data packet detection, integrity validation, deciphering, and header decompression. In various embodiments, the PDCP sublayer <NUM> encode packets for transmission via lower layers and/or decode packets received from low layers and destined for higher layers.

In the uplink, MAC sublayer <NUM> may provide functions including multiplexing between logical and transport channels, random access procedure, logical channel priority, and hybrid-ARQ (HARQ) operations. In the downlink, the MAC layer functions may include channel mapping within a cell, demultiplexing, discontinuous reception (DRX), and HARQ operations.

While the software architecture <NUM> may provide functions to transmit data through physical media, the software architecture <NUM> may further include at least one host layer <NUM> to provide data transfer services to various applications in the computing device <NUM>. In some embodiments, application-specific functions provided by the at least one host layer <NUM> may provide an interface between the software architecture and the general purpose processor <NUM>.

In other embodiments, the software architecture <NUM> may include one or more higher logical layer (e.g., transport, session, presentation, application, etc.) that provide host layer functions. For example, in some embodiments, the software architecture <NUM> may include a network layer (e.g., IP layer) in which a logical connection terminates at a packet data network (PDN) gateway (PGW). In some embodiments, the software architecture <NUM> may include an application layer in which a logical connection terminates at another device (e.g., end user device, server, etc.). In some embodiments, the software architecture <NUM> may further include in the AS <NUM> a hardware interface <NUM> between the physical layer <NUM> and the communication hardware (e.g., one or more radio frequency (RF) transceivers).

Various embodiments may be implemented on a repeater (e.g., BS relay 110d), such as an MMW repeater. <FIG> illustrates a simplified architecture of an example MMW repeater <NUM> that may implement various embodiments.

With reference to <FIG>, the illustrated example MMW repeater <NUM> may include one or more RX antennas <NUM>, one or more mmWave receivers <NUM>, a repeater processor <NUM>, one or more amplifier units <NUM>, one or more mmWave transmitters <NUM>, one or more TX antennas <NUM>, a memory <NUM>, and one or more modem <NUM>, such as an LTE modem, <NUM> modem, etc..

The one or more RX antennas <NUM> may be connected to the one or more mmWave receivers <NUM> to receive MMW signals (e.g., MMW signals in mmWave spectrum bands, such as a <NUM>-<NUM> mmWave spectrum band, a <NUM>-<NUM> mmWave spectrum band, a <NUM>-<NUM> mmWave spectrum band, a <NUM>-<NUM> mmWave spectrum band, etc.). The one or more TX antennas <NUM> may be connected to the one or more mmWave transmitters <NUM> to send MMW signals (e.g., MMW signals in mmWave spectrum bands, such as a <NUM>-<NUM> mmWave spectrum band, a <NUM>-<NUM> mmWave spectrum band, a <NUM>-<NUM> mmWave spectrum band, a <NUM>-<NUM> mmWave spectrum band, etc.). The one or more TX antennas <NUM> and/or the one or more RX antennas <NUM> may be array type antennas, such as phased array antennas, configured to support beamforming and/or MIMO transmission/reception.

The one or more amplifier units <NUM> may amplify the power of MMW signals received via the one or more RX antennas and the one or more mmWave receivers <NUM> and transmit the one or more amplified MMW signals via the one or more mmWave transmitters <NUM> and one or more TX antennas <NUM>. In some configurations, the MMW repeater <NUM> may be a low power relay with less functionality than a gNB (e.g., macro BS 110a). For example, the MMW repeater <NUM> may receive analog signals on its RX antennas <NUM> and mmWave receivers <NUM>, amplify the power of the received analog signals via its amplifier units <NUM>, and transmit the amplified analog signals from its mmWave transmitters <NUM> and TX antennas <NUM>. Such reduced functionality MMW repeaters may not include analog-to-digital converters or digital-to-analog converters in their signal paths. Such example reduced functionality MMW repeaters may be referred to as Layer <NUM> (L1) and/or physical layer (PHY) repeaters.

A repeater processor <NUM> may be connected to the one or more RX antennas <NUM>, the one or more mmWave receivers <NUM>, the one or more amplifier units <NUM>, the one or more mmWave transmitters <NUM>, and/or the one or more TX antennas <NUM> to control the operations of the one or more RX antennas <NUM>, the one or more mmWave receivers <NUM>, the one or more amplifier units <NUM>, the one or more mmWave transmitters <NUM>, and/or the one or more TX antennas <NUM>. For example, the repeater processor <NUM> may control the one or more RX antennas and /or the one or more mmWave receivers <NUM> to receive analog MMW signals with one or more RX beamforming configurations. For example, the repeater processor <NUM> may control the one or more amplifier units to amplify analog MMW signals. For example, the repeater processor <NUM> may control the one or more mmWave transmitters <NUM> and/or the one or more TX antennas <NUM> to transmit amplified analog MMW signals with on one or more TX beamforming configurations. The repeater processor <NUM> may control the one or more RX antennas <NUM>, the one or more mmWave receivers <NUM>, the one or more amplifier units <NUM>, the one or more mmWave transmitters <NUM>, and/or the one or more TX antennas <NUM> to enable transmission and/or reception over the air interface thereby relaying Layer <NUM> (L1) services such as physical layer (PHY) services.

The MMW repeater <NUM> may also exchange one or more control signals with other network devices (e.g., macro BS 110a, network controller <NUM>, donor nodes, control nodes, servers, etc.) via one or more control interfaces. A control interface may be an out-of-band interface using a different radio technology, such as Bluetooth, Bluetooth Low Energy (LE), etc., and/or a different frequency (e.g., the frequencies designated for LTE narrowband internet of things (NB-IoT) (LTE NB-IoT). For example, the control interface may be established via out-of-band communications established with the a gNB (e.g., macro BS 110a) using the modem <NUM>. Additionally, or alternatively, a control interface may be an in-band interface using bandwidth of the same carrier frequency (e.g., bandwidth of MMW signals in a mmWave spectrum band). For example, communications over a control channel via the one or more RX antennas <NUM>, the one or more mmWave receivers <NUM>, the one or more amplifier units <NUM>, the one or more mmWave transmitters <NUM>, and/or the one or more TX antennas <NUM> with a gNB (e.g., macro BS 110a) may be used to establish an in-band control interface.

Whether in-band and/or out-of-band, a control interface may be used by another network device (e.g., macro BS 110a, network controller <NUM>, donor node, control node, server, etc.) to control TX beamforming configurations, RX beamforming configurations, and/or power amplification configurations of the MMW repeater <NUM> by sending instruction (e.g., setting indications, etc.) to the repeater processor <NUM>. For example, a gNB (e.g., macro BS 110a) may send a message to the repeater processor <NUM> of the MMW repeater <NUM> via a control interface that instructions the repeater processor <NUM> of the MMW repeater <NUM> to control the one or more RX antennas <NUM>, the one or more mmWave receivers <NUM>, the one or more amplifier units <NUM>, the one or more mmWave transmitters <NUM>, and/or the one or more TX antennas <NUM> to achieve selected TX beamforming configurations, RX beamforming configurations, and/or power amplification configurations at the MMW repeater <NUM>.

<FIG> is a block diagram of an example beam sweep configuration of an MMW repeater, such as a relay BS 110d, by a gNB, such as macro BS 110a, in a <NUM> network for supporting RACH procedures using NR. With reference to <FIG>, the gNB may generate and send a RACH configuration message to the MMW repeater indicating a TX beam form <NUM> and a RX beam form <NUM> to use during RACH procedures. The RACH configuration message may be sent over a control interface, such as an in-band interface or an out-of-band interface, between the gNB and MMW repeater. The RACH configuration message may indicate the number "N" SSBs in use by the gNB, may indicate the periods of the SSBs, such as SS0, SS1, through SSN-<NUM>, etc., may indicate the number "N" of ROs in use by the gNB, and may indicate the periods of the ROs, such as RO0, RO1, through RON-<NUM>, etc.. The RACH configuration message may associate SSBs, such as SS0, SS1, through SSN-<NUM>, etc., with corresponding ROs, such as RO0, RO1, through RON-<NUM>, etc. The RACH configuration message may indicate the TX beam form the MMW repeater is to use during a specific SSB, such as TX beam form <NUM> during SSB SSN-<NUM>. The RACH configuration message may indicate the RX beam form the MMW repeater is to use during a specific RO, such as RX beam form <NUM> during RO RON-<NUM>.

During RACH procedures, the gNB may transmit SI using different TX beam forms <NUM>, <NUM>, and <NUM> during respective SSBs, SS0, SS1, SSN-<NUM>, etc., and may receive (or listen for) RACH messages, such as RACH message <NUM>, using different RX beam forms <NUM>, <NUM>, <NUM>, etc. The MMW repeater may relay SI from the gNB by transmitting any received SI from the gNB using TX beam form <NUM> during the SSB SSN-<NUM>, thereby relaying such SI using TX beam form <NUM> as specified in the RACH configuration message. Similarly, the MMW repeater may relay any RACH message <NUM> received from a UE computing device by using a RX beam <NUM> to receive (or listen for) any RACH message <NUM> during the RO RON-<NUM>.

In response to receiving a RACH message <NUM> relayed by the MMW repeater to the gNB, the gNB may generate an RAR message. The RAR message may be replayed to the UE computing device via the MMW repeater using a TX beam form, such as TX beam form <NUM> and/or one or more different TX beam forms. A UE computing device receiving the RAR message may send an MSG <NUM> that may be relayed by the MMW repeater using a RX beam form, such as RX beam form <NUM> and/or one or more different RX beam forms. In response to receiving an MSG <NUM> relayed by the MMW repeater, the gNB may determine a suitable beam for communication with the UE computing device and may relay an MSG <NUM> to the UE computing device via the MMW repeater using the suitable beam. In this manner, RACH procedures may establish communications between the gNB and a UE computing device via the MMW repeater.

<FIG> is a process flow diagram illustrating a method for beam sweep configuration of an MMW repeater according to an embodiment. With reference to <FIG>, the method <NUM> may be implemented by a processor of network device, such as a base station (e.g., the base station 110a (e.g., a gNB), <NUM>), network controller <NUM>, donor nodes, control nodes, servers, etc..

In block <NUM>, the processor may receive a RACH message <NUM> relayed from an MMW repeater. The RACH message <NUM> may be relayed by the MMW repeater from a UE computing device. The UE computing device may have sent the RACH message <NUM> in response to an SSB sent by the gNB and relayed by the MMW repeater to the UE computing device. The MMW repeater may have relayed the SSB to the UE computing device using a beam form (e.g., a TX beam form), such as an omni-directional or pseudo-omni directional beam, and may have received an RACH message <NUM> in response from the UE computing device using a beam form (e.g., a receive (RX) beam form), such as the same omni-directional or pseudo-omni directional beam used to relay the SSB.

In block <NUM>, the processor may determine a beam sweep schedule for use by the MMW repeater in relaying an RAR message in response to the RACH <NUM> message. In various embodiments, the beam sweep schedule may indicate a series of RAR messages to be sent successively and a different TX beam sweep configuration to be used by the MMW repeater for each of the series of RAR messages. Similarly, the beam sweep schedule may indicate a series of RX beam sweep configurations to be used by the MMW repeater to receive (or listen for) MSG <NUM> sent by a UE computing device in response to the RAR messages. In various embodiments, the TX beam sweep configuration for the RAR message relay may be the same as the RX beam sweep configuration to receive (or listen for) MSG <NUM>. In various embodiments, the different TX beam sweep configurations indicated in the beam sweep schedule may be determined based at least in part on an attribute of the RACH <NUM> message. For example, the power of the RACH <NUM> message and/or the timing of the RACH <NUM> message may be used to determine the beam sweep schedule. The received power of the RACH <NUM> message may be calculated by the gNB based on the forwarded RACH message <NUM> or the received power of the RACH <NUM> message may be calculated by the MMW repeater and forwarded to the gNB by the MMW repeater, such as via a control interface. The received timing of the RACH <NUM> message may be calculated by the gNB based on the forwarded RACH message <NUM> or the received timing of the RACH <NUM> message may be calculated by the MMW repeater and forwarded to the gNB by the MMW repeater, such as via a control interface.

In block <NUM>, the processor may generate an RAR control message indicating the beam sweep schedule. In various embodiments, RAR control messages may be sent from the gNB to the MMW repeater to indicate one or more beam sweep settings, TX power settings, RX power settings, and/or other MMW repeater settings. In various embodiments, an RAR control message may indicate the determined beam sweep schedule. Indicating the beam sweep schedule may enable the MMW repeater to use the beam sweep schedule to send multiple RAR messages in an RAR window. In some embodiments, an RAR control message may indicate one or more conditions to control a relay of an MSG <NUM> by an MMW repeater. For example, a condition may be an indication to use the same beam to relay the MSG <NUM> as was used to transmit the RAR message that triggered the MSG <NUM>.

In block <NUM>, the processor may send the RAR control message to the MMW repeater. In various embodiments, an RAR control message may be sent from the gNB to the MMW relay via a control interface, such as via in-band and/or out-of-band interfaces. In some embodiments, an RAR message may indicate a single beam sweep configuration.

In block <NUM>, the processor may send the series of RAR messages to the MMW repeater. In some embodiments, multiple RAR messages may be sent from the gNB at the same time and the MMW relay may sequentially send the RAR messages.

In determination block <NUM>, the processor may determine whether an MSG <NUM> is relayed by the MMW repeater. For example, the processor may determine whether an MSG <NUM> is successfully received from the MMW repeater.

In response to determining that an MSG <NUM> has not been relayed (i.e., determination block <NUM> = "No"), the processor may continue to monitor for relay of an MSG <NUM> in determination block <NUM>.

In response to determining that an MSG <NUM> is received (i.e., determination block <NUM> = "Yes"), the processor may determine a suitable beam for communicating with a UE computing device based at least in part on the MSG <NUM> in block <NUM>. In various embodiments, based on a relayed MSG <NUM> from the MMW repeater, the gNB may determine a suitable beam for the gNB and MMW repeater to use to communicate with the UE computing device. The gNB may instruct the MMW repeater to use the suitable beam for forwarding an MSG <NUM> to the UE computing device.

In block <NUM>, the processor may send a cancelation message to the MMW repeater. In some scenarios, multiple RAR messages and MSG <NUM> may be overlapping. As such, before all the RAR messages associated with a beam sweep schedule may have been sent, a suitable beam for UE computing device communications may have been determined by the gNB. In such scenarios, in various embodiments, the gNB may generate and send a cancelation message to the MMW repeater. The cancelation message may be configured to cause the MMW repeater to cancel any remaining RAR messages in the beam sweep schedule. In various embodiments, the cancelation message may be sent via a control interface, such as via in-band and/or out-of-band interfaces.

In block <NUM>, the processor may send an indication of the suitable beam to the MMW repeater. In various embodiments, the indication may be sent from the gNB to the MMW relay via a control interface, such as via in-band and/or out-of-band interfaces.

In block <NUM>, the processor may send an MSG <NUM> to the MMW repeater to be relayed to the UE computing device using the suitable beam. In various embodiments, a gNB may send an MSG <NUM> to the MMW repeater and the MMW repeater may relay the MSG <NUM> to the UE computing device using the suitable beam.

<FIG> is a process flow diagram illustrating a method for beam sweep configuration of an MMW repeater according to an embodiment. With reference to <FIG>, the method <NUM> may be implemented by a processor of a relay base station (e.g., the base station 110d, the MMW repeater <NUM>). In various embodiments, the operations of method <NUM> may be performed in conjunction with the operations of the method <NUM> as described.

In block <NUM>, the processor may receive an RAR control message from a network device (e.g., a gNB) indicating a beam sweep schedule. In various embodiments, the beam sweep schedule may indicate a series of RAR messages to be sent successively and a different TX beam sweep configuration to be used by the MMW repeater for each of the series of RAR messages. Similarly, the beam sweep schedule may indicate a series of RX beam sweep configurations to be used by the MMW repeater to receive (or listen for) MSG <NUM> sent by a UE computing device in response to the RAR messages. In various embodiments, RAR control messages may be sent from the gNB to the MMW repeater to indicate one or more beam sweep settings, TX power settings, RX power settings, and/or other MMW repeater settings. In various embodiments, an RAR control message may indicate the determined beam sweep schedule. Indicating the beam sweep schedule may enable the MMW repeater to use the beam sweep schedule to send multiple RAR messages in an RAR window.

In block <NUM>, the processor may receive a series of RAR messages from the network device (e.g., the gNB). In some embodiments, a network device, such as a gNB, may send multiple RAR messages at the same time to an MMW repeater.

In block <NUM>, the processor may control one or more TX antennas of the MMW repeater according to the RAR control message to successively relay each of the series of RAR messages using that RAR message's respective different TX beam sweep configuration. In various embodiments, a beam sweep schedule may operate as instructions to an MMW repeater to forward received RAR messages from the gNB using one or multiple TX beams. In some embodiments, the TX beam may be a finer beam (e.g., with a greater beam gain) than the RX beam the MMW repeater used to receive the RACH message <NUM> from a UE computing device and/or a finer beam (e.g., with a greater beam gain) than the TX beam the MMW repeater used to transmit an SSB that may have triggered the RACH message <NUM> transmission by the UE computing device. In some embodiments, the one or more TX beams may be beams that are quasi co-located (QCLed) with the RX beam the MMW repeater used to receive the RACH message <NUM> from a UE computing device and/or that are QCLed the TX beam the MMW repeater used to transmit an SSB that may have triggered the RACH message <NUM> transmission by the UE computing device. In various embodiments, the beam sweep schedule may also configure the MMW repeater's RX beam form for receiving (or listening for) MSG <NUM> to be the same as the TX beam form used to transmit the RAR message.

In determination block <NUM>, the processor may determine whether a cancelation message is received. In response to determining that a cancelation message is not received (i.e., determination block <NUM> = "No"), the processor may continue to control one or more TX antennas of the MMW repeater according to the RAR control message to successively relay each of the series of RAR messages using that RAR message's respective different TX beam sweep configuration in block <NUM>.

In response to determining that a cancelation message is received (i.e., determination block <NUM> = "Yes"), the processor may cancel the relay of any remaining RAR messages in the beam sweep schedule in block <NUM>. In this manner, resources may not be wasted on attempting relay of RAR messages and/or MSG <NUM> that may no longer be necessary to establish communications with the UE computing device.

In block <NUM>, the processor may receive an indication of a suitable beam for communicating with a UE computing device. In various embodiments, the indication may be received from the gNB via a control interface, such as via in-band and/or out-of-band interfaces.

In block <NUM>, the processor may relay an MSG <NUM> to the UE computing device using the suitable beam. In various embodiments, the MMW repeater may receive an indication of a suitable beam for communicating with the UE computing device. In response to receiving an MSG <NUM> from a gNB, the MMW repeater may relay the MSG <NUM> from the gNB to the UE computing device using the suitable beam. For example, the MMW repeater may control one or more antennas to send an MSG <NUM> received from the gNB to the UE computing device using the suitable beam.

In blocks <NUM> and <NUM>, the processor may perform operations of like numbered blocks of method <NUM> described with reference to <FIG> to receive a RACH message <NUM> and determine a beam sweep schedule.

In block <NUM>, the processor may select an initial RAR message of the series of RAR messages to send. In some embodiments, the beam sweep schedule may indicate a relative order of RAR messages, such that the initial RAR message may be the first RAR message in the beam sweep schedule.

In block <NUM>, the processor may generate an initial RAR control message indicating the different TX beam sweep configuration associated with the selected initial RAR message. In some embodiments, the TX beam sweep configuration for an initial RAR message may be the same beam the MMW repeater used to receive the RACH message <NUM> from a UE computing device (e.g., the initial TX beam may correspond to the RX beam on which the RACH message <NUM> was received by the MMW repeater) and/or may be the same beam the MMW repeater used to transmit an SSB that may have triggered the RACH message <NUM> transmission by the UE computing device (e.g., the initial TX beam may correspond to the TX beam on which the SSB was transmitted by the MMW repeater).

In block <NUM>, the processor may send the initial RAR control message to the MMW repeater. In various embodiments, an RAR control message may be sent from the gNB to the MMW relay via a control interface, such as via in-band and/or out-of-band interfaces.

In block <NUM>, the processor may send the selected initial RAR message to the MMW repeater.

In determination block <NUM>, the processor may determine whether an MSG <NUM> is relayed by the MMW repeater as described with reference to the like numbered block of the method <NUM> (<FIG>).

In response to determining that an MSG <NUM> has not been relayed (i.e., determination block <NUM> = "No"), the processor may select a next RAR message of the series of RAR messages to send in block <NUM>. In some embodiments, the beam sweep schedule may indicate a relative order of RAR messages, such that the next RAR message may be the RAR message in the beam sweep schedule following a last sent or transmitted RAR message by the gNB.

In block <NUM>, the processor may generate a next RAR control message indicating the different TX beam sweep configuration associated with the selected next RAR message. In some embodiments, the TX beam sweep configuration for the next RAR message may be a finer beam than that generated by the initial RAR control message.

In block <NUM>, the processor may send the next RAR control message to the MMW repeater. In various embodiments, an RAR control message may be sent from the gNB to the MMW relay via a control interface, such as via in-band and/or out-of-band interfaces.

In block <NUM>, the processor may send the selected next RAR message to the MMW repeater.

In determination block <NUM>, the processor may determine whether an MSG <NUM> is relayed by the MMW repeater as described with reference to the like numbered block of the method <NUM> (<FIG>). In response to determining that an MSG <NUM> has been relayed (i.e., determination block <NUM> = "Yes"), the processor may determine a suitable beam for communicating with a UE computing device based at least in part on the MSG <NUM> in block <NUM>.

In blocks <NUM> and <NUM>, the processor may perform operations of like numbered blocks of the method <NUM> described with reference to <FIG> to send an indication of the suitable beam and send an MSG <NUM> to the MMW repeater.

<FIG> is a process flow diagram illustrating a method for beam sweep configuration of an MMW repeater according to an embodiment. With reference to <FIG>, the method <NUM> may be implemented by a processor of a relay base station (e.g., the base station 110d, the MMW repeater <NUM>). In various embodiments, the operations of method <NUM> may be performed in conjunction with the operations of method <NUM>.

In block <NUM>, the processor may receive an initial RAR control message indicating an initial TX beam sweep configuration associated with an initial RAR message. The initial RAR control message may indicate the TX beam sweep configuration associated with a selected initial RAR message. In some embodiments, the TX beam sweep configuration for an initial RAR message may be the same beam the MMW repeater used to receive the RACH message <NUM> from a UE computing device (e.g., the initial TX beam may correspond to the RX beam on which the RACH message <NUM> was received by the MMW repeater) and/or may be the same beam the MMW repeater used to transmit an SSB that may have triggered the RACH message <NUM> transmission by the UE computing device (e.g., the initial TX beam may correspond to the TX beam on which the SSB was transmitted by the MMW repeater). The initial RAR message may also configure the MMW repeater's RX beam form for receiving (or listening for) MSG <NUM> to be the same as the TX beam form used to transmit the initial RAR message.

In block <NUM>, the processor may receive the initial RAR message.

In block <NUM>, the processor may control one or more TX antennas of the MMW repeater according to the initial RAR control message to relay the initial RAR control message using the initial TX beam sweep configuration.

In determination block <NUM>, the processor may determine whether an MSG <NUM> is received.

In response to determining that an MSG <NUM> is not received (i.e., determination block <NUM> = "No"), the processor may receive a next RAR control message indicating a next TX beam sweep configuration associated with a next RAR message in block <NUM>. In some embodiments, the TX beam sweep configuration for the next RAR message may be a finer beam than that generated by the initial RAR control message.

In block <NUM>, the processor may receive the next RAR message.

In block <NUM>, the processor may control one or more TX antennas of the MMW repeater according to the next RAR control message to relay the next RAR control message using the next TX beam sweep configuration.

In response to determining that an MSG <NUM> is received (i.e., determination block <NUM> = "Yes"), the processor may relay the MSG <NUM> to the network device (e.g., the gNB) in block <NUM>.

In blocks <NUM> and <NUM>, the processor may perform operations of like numbered blocks of the method <NUM> described with reference to <FIG> to receive an indication of the suitable beam and relay the MSG <NUM> from the network device (e.g., the gNB) to the UE computing device using the suitable beam.

Various embodiments may be implemented in a gNB as well as a variety of wireless network devices (e.g., base station 110a, <NUM>), an example of which is illustrated in <FIG> in the form of a server device <NUM> configured with processor-executable instructions to function as a gNB. Such network computing devices may include at least the components illustrated in <FIG>. With reference to <FIG>, the network computing device <NUM> may typically include a processor <NUM> coupled to volatile memory <NUM> and a large capacity nonvolatile memory, such as a disk drive <NUM>. The network computing device <NUM> may also include a peripheral memory access device such as a floppy disc drive, compact disc (CD) or digital video disc (DVD) drive <NUM> coupled to the processor <NUM>. The network computing device <NUM> may also include network access ports <NUM> (or interfaces) coupled to the processor <NUM> for establishing data connections with a network, such as the Internet and/or a local area network coupled to other system computers and servers. The network computing device <NUM> may include one or more antennas <NUM> for sending and receiving electromagnetic radiation that may be connected to a wireless communication link. The network computing device <NUM> may include additional access ports, such as USB, Firewire, Thunderbolt, and the like for coupling to peripherals, external memory, or other devices.

Various embodiments may be implemented on a variety of computing devices (e.g., the computing device 120a-120e, <NUM>, <NUM>), an example of which is illustrated in <FIG> in the form of a smartphone <NUM>. With reference to <FIG>, the smartphone <NUM> may include a first SOC <NUM> (e.g., a SOC-CPU) coupled to a second SOC <NUM> (e.g., a <NUM> capable SOC). The first and second SOCs <NUM>, <NUM> may be coupled to internal memory <NUM>, <NUM>, a display <NUM>, and to a speaker <NUM>. Additionally, the smartphone <NUM> may include an antenna <NUM> for sending and receiving electromagnetic radiation that may be connected to a wireless data link and/or cellular telephone transceiver <NUM> coupled to one or more processors in the first and/or second SOCs <NUM>, <NUM>. Smartphones <NUM> typically also include menu selection buttons or rocker switches <NUM> for receiving user inputs.

A typical smartphone <NUM> also includes a sound encoding/decoding (CODEC) circuit <NUM>, which digitizes sound received from a microphone into data packets suitable for wireless transmission and decodes received sound data packets to generate analog signals that are provided to the speaker to generate sound. Also, one or more of the processors in the first and second SOCs <NUM>, <NUM>, wireless transceiver <NUM> and CODEC <NUM> may include a digital signal processor (DSP) circuit (not shown separately).

The processors of the wireless network computing device <NUM> and the smart phone <NUM> may be any programmable microprocessor, microcomputer or multiple processor chip or chips that can be configured by software instructions (applications) to perform a variety of functions, including the functions of the various embodiments described below. In some mobile devices, multiple processors may be provided, such as one processor within an SOC <NUM> dedicated to wireless communication functions and one processor within an SOC <NUM> dedicated to running other applications. Typically, software applications may be stored in the memory before they are accessed and loaded into the processor. The processors may include internal memory sufficient to store the application software instructions.

As used in this application, the terms "component," "module," "system," and the like are intended to include a computer-related entity, such as, but not limited to, hardware, firmware, a combination of hardware and software, software, or software in execution, which are configured to perform particular operations or functions. For example, a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device may be referred to as a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one processor or core and/or distributed between two or more processors or cores. In addition, these components may execute from various non-transitory computer readable media having various instructions and/or data structures stored thereon. Components may communicate by way of local and/or remote processes, function or procedure calls, electronic signals, data packets, memory read/writes, and other known network, computer, processor, and/or process related communication methodologies.

A number of different cellular and mobile communication services and standards are available or contemplated in the future, all of which may implement and benefit from the various embodiments. Such services and standards include, e.g., third generation partnership project (3GPP), long term evolution (LTE) systems, third generation wireless mobile communication technology (<NUM>), fourth generation wireless mobile communication technology (<NUM>), fifth generation wireless mobile communication technology (<NUM>), global system for mobile communications (GSM), universal mobile telecommunications system (UMTS), 3GSM, general packet radio service (GPRS), code division multiple access (CDMA) systems (e.g., cdmaOne, CDMA1020TM), enhanced data rates for GSM evolution (EDGE), advanced mobile phone system (AMPS), digital AMPS (IS-<NUM>/TDMA), evolution-data optimized (EV-DO), digital enhanced cordless telecommunications (DECT), Worldwide Interoperability for Microwave Access (WiMAX), wireless local area network (WLAN), Wi-Fi Protected Access I & II (WPA, WPA2), and integrated digital enhanced network (iDEN). Each of these technologies involves, for example, the transmission and reception of voice, data, signaling, and/or content messages. It should be understood that any references to terminology and/or technical details related to an individual telecommunication standard or technology are for illustrative purposes only, and are not intended to limit the scope of the claims to a particular communication system or technology unless specifically recited in the claim language.

Various embodiments illustrated and described are provided merely as examples to illustrate various features of the claims. However, features shown and described with respect to any given embodiment are not necessarily limited to the associated embodiment and may be used or combined with other embodiments that are shown and described. Further, the claims are not intended to be limited by any one example embodiment.

The hardware used to implement various illustrative logics, logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A processor may also be implemented as a combination of receiver smart objects, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Alternatively, some operations or methods may be performed by circuitry that is specific to a given function.

In one or more embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions or code on a non-transitory computer-readable storage medium or non-transitory processor-readable storage medium. The operations of a method or algorithm disclosed herein may be embodied in a processor-executable software module or processor-executable instructions, which may reside on a non-transitory computer-readable or processor-readable storage medium. Non-transitory computer-readable or processor-readable storage media may be any storage media that may be accessed by a computer or a processor. By way of example but not limitation, such non-transitory computer-readable or processor-readable storage media may include RAM, ROM, EEPROM, FLASH memory, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage smart objects, or any other medium that may be used to store desired program code in the form of instructions or data structures and that may be accessed by a computer. Combinations of the above are also included within the scope of non-transitory computer-readable and processor-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and/or instructions on a non-transitory processor-readable storage medium and/or computer-readable storage medium, which may be incorporated into a computer program product.

Claim 1:
A method for beam sweep configuration of a millimeter wave, MMW, repeater during random access channel, RACH, procedures, characterized by comprising:
receiving (<NUM>), by a processor of a Next Generation NodeB, gNB, a RACH <NUM> message relayed by an MMW repeater;
determining (<NUM>), by the processor of the gNB, a beam sweep schedule for use by the MMW repeater in relaying a random access response, RAR, message in response to the RACH <NUM> message, wherein the beam sweep schedule indicates a series of RAR messages to be sent successively and a different transmit, TX, beam sweep configuration to be used by the MMW repeater for each of the series of RAR messages;
generating (<NUM>), by the processor of the gNB, an RAR control message indicating the beam sweep schedule;
sending (<NUM>), by the processor of the gNB, the RAR control message to the MMW repeater;
sending (<NUM>), by the processor of the gNB, the series of RAR messages to the MMW repeater;
receiving (<NUM>), by the processor of the gNB, a message <NUM> relayed by the MMW repeater, wherein the message <NUM> is generated by a computing device in response to at least one of the series of RAR messages;
determining (<NUM>), by the processor of the gNB, a suitable beam for communicating with the computing device based at least in part on the message <NUM>; and
sending (<NUM>), by the processor of the gNB, a cancelation message to the MMW repeater in response to determining the suitable beam for communicating with the computing device, wherein the cancelation message is configured to cause the MMW repeater to cancel any remaining RAR messages in the beam sweep schedule.