Information for wireless communication repeater devices

Abstract

The present disclosure relates to information for wireless communication repeater devices, wherein aspects relate to exchanging beam-related information for repeater devices. A network access node configures a repeater device to transmit synchronization signal blocks using different beams. The network access node determines a number of beams that the repeater device can use for its operation. A repeater device indicates how many beams it supports, how many antenna arrays it have, and a mapping of beam indices to antenna array indices. The repeater device indicates which beam pairs cannot be used for simultaneous transmission and / or reception and / or which beam groups can be used for simultaneous transmission and / or reception. The network access node determines, based on signal measurements and / or beam configuration feedback from the repeater device, which beam pairs cannot be used by the repeater device for simultaneous transmission and / or reception and / or which beam groups can be used by the repeater device for simultaneous transmission and / or reception.

Description

[0001] This application is a divisional application of a Chinese patent application with an application date of August 14, 2021, an application number of 202180057410.8, and an invention title of "Information for Wireless Communication Repeater Devices".

[0002] Cross - reference to related applications

[0003] This patent application claims priority to pending non - provisional patent application No. 17 / 402,375, filed on August 13, 2021, provisional patent application No. 63 / 065,915, filed on August 14, 2020, provisional patent application No. 63 / 067,790, filed on August 19, 2020, provisional patent application No. 63 / 070,194, filed on August 25, 2020, and provisional patent application No. 63 / 138,046, filed on January 15, 2021, all in the United States Patent and Trademark Office, all of which applications have been assigned to the assignee of this application and are hereby incorporated by reference in their entirety for all applicable purposes as if fully set forth hereinbelow. Technical field

[0004] The techniques discussed below generally relate to wireless communication and, in particular, to exchanging beam information, open - loop configuration, and identification of wireless communication repeater devices.

[0005] Introduction

[0006] Next - generation wireless communication systems (e.g., 5GS) may include a 5G core (e.g., 5GC) network and a 5G radio access network (RAN), such as a New Radio (NR) - RAN. The NR - RAN supports communication via one or more cells. For example, a wireless communication device (such as a user equipment (UE)) may access a first cell of a first network access node (such as a gNB) and / or access a second cell of a second network access node. In some instances, a repeater device may be located between the UE and the network access node. The repeater device may relay traffic and control between the UE and the network access node in both the uplink and downlink directions.

[0007] The network access node may schedule access to the cell to support access by multiple UEs. For example, the network access node may allocate different resources (e.g., time - domain and frequency - domain resources) for different UEs operating within the cell of the network access node.

[0008] In a 5G New Radio wireless communication network, resources can be shared between the access network and the backhaul network. For example, the radio spectrum can be used for access links (e.g., the link between a network access node and a UE) and backhaul links (e.g., the link between a network access node and the core network). In such an Integrated Access Backhaul (IAB) network, a shared radio carrier can be time-divided into multiple frames, sub-frames, and time slots. In some IAB network configurations, one or more time slots can be allocated for access communication, while other time slots can be allocated for backhaul communication.

[0009] Brief overview of some examples

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

[0011] In one example, a method of wireless communication at a repeater device in a wireless communication network is described. The method includes: receiving a first configuration specifying a first number of Synchronization Signal Blocks (SSBs) to be transmitted by the repeater device; selecting to transmit the SSBs using a second number of beams, where the second number of beams is less than or equal to the first number of SSBs; receiving at least one SSB transmission; and transmitting the at least one SSB transmission via the second number of beams.

[0012] In another example, a repeater device is described. The repeater device includes a relay unit, a memory, and a processor communicatively coupled to the relay unit and the memory. The processor and the memory are configured to: receive a first configuration specifying a first number of Synchronization Signal Blocks (SSBs) to be transmitted by the relay unit of the repeater device; select to transmit the SSBs using a second number of beams, where the second number of beams is less than or equal to the first number of SSBs; receive at least one SSB transmission; and transmit the at least one SSB transmission via the second number of beams.

[0013] According to another example, a method for wireless communication at a network access node in a wireless communication network is described. The method includes: generating a first configuration indicating a first number of synchronization signal blocks (SSBs) to be transmitted by a repeater device; transmitting the first configuration to the repeater device; determining that the repeater device is transmitting less than all of the first number of SSBs; generating a second configuration after determining that the repeater device is transmitting less than all of the first number of SSBs, the second configuration indicating a second number of SSBs to be transmitted by the repeater device; and transmitting the second configuration to the repeater device.

[0014] In yet another example, a network access node is described. The network access node includes a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor and the memory are configured to: generate a first configuration indicating a first number of synchronization signal blocks (SSBs) to be transmitted by a repeater device; transmit the first configuration to the repeater device via the transceiver; determine that the repeater device is transmitting less than all of the first number of SSBs; generate a second configuration after determining that the repeater device is transmitting less than all of the first number of SSBs, the second configuration indicating a second number of SSBs to be transmitted by the repeater device; and transmit the second configuration to the repeater device via the transceiver.

[0015] These and other aspects of the present disclosure will be more fully understood after reading the following detailed description. After reading the following description of specific exemplary aspects in conjunction with the accompanying drawings, other aspects, features, and examples of the present disclosure will be apparent to those of ordinary skill in the art. Although the features may be discussed below with respect to certain examples and drawings, all examples may include one or more of the advantageous features discussed herein. In other words, although one or more examples may be discussed as having certain advantageous features, one or more such features may be used in accordance with the various examples discussed herein. Similarly, although the examples may be discussed below as examples of devices, systems, or methods, it should be understood that such examples may be implemented in a variety of devices, systems, and methods. Brief Description of the Drawings

[0017] Figure 1 is a schematic illustration of a wireless communication system in accordance with some aspects of the present disclosure.

[0018] Figure 2 is a schematic illustration of an example of a radio access (RAN) network in accordance with some aspects of the present disclosure.

[0019] Figure 3 is a schematic illustration of wireless resources in an air interface utilizing orthogonal frequency division multiplexing (OFDM) in accordance with some aspects of the present disclosure.

[0020] Figure 4 FIG. is an illustration showing an example of a downlink channel within a 5G New Radio (NR) subframe in accordance with some aspects of the present disclosure.

[0021] Figure 5 FIG. is a block diagram showing an example of a wireless communication system supporting beamforming and / or multiple-input multiple-output (MIMO) communication in accordance with some aspects of the present disclosure.

[0022] Figure 6 FIG. is an illustration showing an example of communication using beamformed signals between a radio access network (RAN) node and a wireless communication device in accordance with some aspects of the present disclosure.

[0023] Figure 7 FIG. is a schematic diagram providing a high-level illustration of an example of a network configuration including an integrated access backhaul (IAB) network in accordance with some aspects of the present disclosure.

[0024] Figure 8 FIG. is an illustration showing an example of a wireless communication network having communication using beamformed signals between a network access node and four UEs in accordance with some aspects of the present disclosure.

[0025] Figure 9 FIG. is a schematic diagram showing an example of IAB node functionality within an IAB network in accordance with some aspects of the present disclosure.

[0026] Figure 10 FIG. is an illustration providing a high-level illustration of an example of a network configuration including an integrated access backhaul (IAB) network in accordance with some aspects of the present disclosure.

[0027] Figure 11 FIG. is an illustration showing an example of a radio protocol architecture in a control plane in accordance with some aspects of the present disclosure.

[0028] Figure 12 FIG. is a block diagram showing an example of a wireless communication network including a network access node, a repeater device, and a UE in accordance with some aspects of the present disclosure.

[0029] Figure 13 FIG. is a schematic diagram showing an example of components of a repeater device in accordance with some aspects of the present disclosure.

[0030] Figure 14 FIG. is a signaling diagram showing an example of repeater device signaling in accordance with some aspects of the present disclosure.

[0031] Figure 15 FIG. is a schematic illustration of an example path for a repeater device in accordance with some aspects of the present disclosure.

[0032] Figure 16Is a schematic example of the propagation of control and data associated with a DL transmission from a network access node to a UE via a repeater device, in accordance with some aspects of the present disclosure.

[0033] Figure 17 Is a block diagram illustrating exemplary couplings between various nodes of a wireless communication network including a repeater device, in accordance with some aspects of the present disclosure.

[0034] Figure 18 Is a schematic diagram of a MIMO repeater device, in accordance with some aspects of the present disclosure.

[0035] Figure 19 Is a schematic diagram of a bi-directional MIMO repeater device, in accordance with some aspects of the present disclosure.

[0036] Figure 20 Is a schematic diagram of a single input single output (SISO) repeater device, in accordance with some aspects of the present disclosure.

[0037] Figure 21 Is a schematic diagram illustrating an example of a hardware implementation of a repeater device employing a processing system, in accordance with some aspects of the present disclosure.

[0038] Figure 22 Is a flowchart illustrating an example process at a repeater device for communicating beam information in a wireless communication network, in accordance with some aspects of the present disclosure.

[0039] Figure 23 Is a flowchart illustrating an example process at a repeater device for communicating beam information in a wireless communication network, in accordance with some aspects of the present disclosure.

[0040] Figure 24 Is a flowchart illustrating an example process at a repeater device for communicating beam information in a wireless communication network, in accordance with some aspects of the present disclosure.

[0041] Figure 25 Is a schematic diagram illustrating an example of a hardware implementation of a network access node employing a processing system, in accordance with some aspects of the present disclosure.

[0042] Figure 26 Is a flowchart illustrating an example process at a network access node for communicating beam information in a wireless communication network, in accordance with some aspects of the present disclosure.

[0043] Figure 27 Is a flowchart illustrating an example process at a network access node for communicating beam information in a wireless communication network, in accordance with some aspects of the present disclosure.

[0044] Figure 28is a flowchart illustrating an example process at a network access node for communicating beam information in a wireless communication network in accordance with some aspects of the present disclosure.

[0045] Figure 29 is a diagram illustrating a wireless communication network for communicating via a beamformed signal between a network access node and a first UE via a first repeater device in accordance with some aspects of the present disclosure.

[0046] Figure 30A and 30B is a graph comparing the cumulative distribution function (CDF) on the vertical axis and the data rate on the horizontal axis (in bits per second per hertz (bits / s / Hz)) depending on whether "side control information" is provided to the repeater device in accordance with some aspects of the present disclosure.

[0047] Figure 31 is a call flow diagram illustrating an example of signaling in a wireless communication network including a network access node, a repeater device, and a UE in accordance with some aspects of the present disclosure.

[0048] Figure 32 is a schematic diagram illustrating an example of a hardware implementation of a repeater device employing a processing system in accordance with some aspects of the present disclosure.

[0049] Figure 33 is a flowchart illustrating an exemplary process at a repeater device in a wireless communication network in accordance with some aspects of the present disclosure.

[0050] Figure 34 is a flowchart illustrating an exemplary process at a repeater device in a wireless communication network in accordance with some aspects of the present disclosure.

[0051] Figure 35 is a schematic diagram illustrating an example of a hardware implementation of a network access node employing a processing system in accordance with some aspects of the present disclosure.

[0052] Figure 36 is a flowchart illustrating an exemplary process for a network access node in a wireless communication network in accordance with some aspects of the present disclosure.

[0053] Figure 37 is a call flow diagram illustrating signaling between a repeater device, a network access node, and a core network node in accordance with some aspects of the present disclosure.

[0054] Figure 38 is a flowchart illustrating an exemplary process at a network access node in a wireless communication network in accordance with some aspects of the present disclosure.

[0055] Figure 39Is a call flow diagram illustrating an example of an initial access procedure between a network access node and a repeater device according to some aspects of the present disclosure.

[0056] Figure 40 Is a call flow diagram illustrating an example of a dedicated RACH procedure in a wireless communication network including a network access node and a repeater device according to some aspects of the present disclosure.

[0057] Figure 41 Is a call flow diagram illustrating an example of initial UE message signaling in a wireless communication network including a network access node and a core network (CN) access and mobility management function (AMF) according to some aspects of the present disclosure.

[0058] Figure 42 Is a call flow diagram illustrating an example of radio capability signaling in a wireless communication network including a network access node and a CN (AMF) according to some aspects of the present disclosure.

[0059] Figure 43 Is a call flow diagram illustrating an example of a next generation (NG) setup procedure in a wireless communication network including a network access node and a CN (AMF) according to some aspects of the present disclosure.

[0060] Figure 44 Is a call flow diagram illustrating an example of signaling configuration information in a wireless communication network including a wireless communication device, a network access node, and a CN (AMF) according to some aspects of the present disclosure.

[0061] Figure 45 Is a schematic diagram illustrating an example of a hardware implementation of a wireless communication device employing a processing system according to some aspects of the present disclosure.

[0062] Figure 46 Is a flowchart illustrating an example of a process at a wireless communication device in a wireless communication network according to some aspects of the present disclosure.

[0063] Figure 47 Is a flowchart illustrating an example of a process at a wireless communication device in a wireless communication network according to some aspects of the present disclosure.

[0064] Figure 48 Is a schematic diagram illustrating an example of a hardware implementation of a network access node employing a processing system according to some aspects of the present disclosure.

[0065] Figure 49 Is a flowchart illustrating an example of a process at a network access node in a wireless communication network according to some aspects of the present disclosure.

[0066] Figure 50Is a flowchart illustrating an example process at a network access node in a wireless communication network in accordance with some aspects of the present disclosure.

[0067] Figure 51 Is a flowchart illustrating an example process at a network access node in a wireless communication network in accordance with some aspects of the present disclosure.

[0068] Figure 52 Is a flowchart illustrating an example process at a network access node in a wireless communication network in accordance with some aspects of the present disclosure.

[0069] Figure 53 Is a schematic diagram illustrating an example of a hardware implementation of a core network node employing a processing system in accordance with some aspects of the present disclosure.

[0070] Figure 54 Is a flowchart illustrating an example process at a core network node in a wireless communication network in accordance with some aspects of the present disclosure.

[0071] Figure 55 Is a flowchart illustrating an example process at a core network node in a wireless communication network in accordance with some aspects of the present disclosure. Detailed Description

[0073] The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. It will be apparent, however, to one of ordinary skill in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

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

[0075] Taking into account the above aspects, unless otherwise specifically stated, it should be understood that if used herein, terms such as "sub-6 GHz" can generally represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. Additionally, unless otherwise specifically stated, it should be understood that if used herein, terms such as "millimeter wave" can generally represent frequencies that can include mid-band frequencies, can be within FR2, or can be within the EHF band.

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

[0077] Aspects of the present disclosure relate to repeater devices. A radio frequency (RF) repeater device can be a non-regenerative type of relay node that amplifies and forwards all RF signals it receives. There are various configurations of RF repeater devices. For example, an RF repeater device can be configured based on the power characteristics and spectrum that the RF repeater device is designed to amplify. Other configurations that can include single-band and multi-band RF repeater devices can be established based on specifying particular requirements to be provided by the RF repeater device. For example, one RF repeater device can be installed on a tower where there are no obstacles on either side of the RF repeater device, while a second RF repeater device can be installed on the outer wall or corner of an office building. The former RF repeater device can operate satisfactorily with an omnidirectional beam, while the latter RF repeater device may require a fixed sector beam to operate satisfactorily. In most examples, RF repeater devices are always on and always amplify and forward the received RF signals. Additionally, an RF repeater device with full-duplex capabilities does not distinguish between resources scheduled for uplink or downlink. Accordingly, the main advantages of RF repeater devices are their low cost, their relative simplicity, their ease of deployment, and the fact that they do not add latency because they are essentially straight-through devices. RF repeater devices (distinguished from the intelligent repeater devices cited herein) are already the simplest and most cost-effective way to improve network coverage. However, RF repeater devices amplify both signals and noise equally and thus contribute to interference (pollution) in a wireless communication network.

[0078] An intelligent repeater device can obtain side control information via a control interface to a network access node (e.g., a scheduling entity, evolved Node B (eNB), g Node B (gNB), base station). However, this requires the intelligent repeater device to establish a communication link (e.g., a radio resource control (RRC) connection) with the network access node. The establishment of the RRC connection can be similar to the way a user equipment (UE) establishes an RRC connection with a network access node. Such establishment has at least two implications. First, the implementation of the intelligent repeater device becomes more complex compared to the implementation of an RF repeater device. In fact, the implementation of the intelligent repeater device may require a user equipment (UE) modem. Second, the operation of the intelligent repeater device is managed / configured by the network access node, which results in an increased processing and control signaling overhead at the network access node.

[0079] The present disclosure relates to enhancements to RF repeater devices (e.g., layer 1 repeater devices) that obtain relevant and useful side control information without establishing a link (e.g., an RRC connection) with a network access node. Aspects and features of the present disclosure may provide performance benefits that are the same as or similar to those enjoyed by intelligent repeater devices, but without the implications described above. However, according to some aspects, a network access node may identify the presence of a nearby open-loop repeater device and may provide some information to the open-loop repeater device. However, the amount of information and / or detail may be minimal compared to the amount of information and / or detail that the same network access node would give to an intelligent repeater device (to control the intelligent repeater device).

[0080] The various concepts presented throughout this disclosure may be implemented across a wide variety of telecommunications systems, network architectures, and communication standards. Now refer to Figure 1 , by way of illustrative example and not limitation, various aspects of the present disclosure are illustrated with reference to wireless communication system 100. Wireless communication system 100 includes three interacting domains: core network 102, radio access network (RAN) 104, and at least one scheduled entity 106. The at least one scheduled entity 106 may be referred to as user equipment (UE) 106 in the following discussion. RAN 104 includes at least one scheduling entity 108. The at least one scheduling entity 108 may be referred to as a network access node (BS) 108 in the following discussion. By means of wireless communication system 100, UE 106 can be enabled to perform data communication with an external data network 110 (such as, but not limited to, the Internet).

[0081] RAN 104 may implement any suitable one or more wireless communication technologies to provide radio access to UE 106. As an example, RAN 104 may operate according to the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification (commonly referred to as 5G). As another example, RAN 104 may operate under a hybrid of 5G NR and the evolved universal terrestrial radio access network (eUTRAN) standard (commonly referred to as Long Term Evolution (LTE)). 3GPP refers to this hybrid RAN as the next generation RAN, or NG-RAN. Of course, many other examples may be utilized within the scope of the present disclosure.

[0082] As illustrated, RAN 104 includes a plurality of network access nodes 108. Broadly speaking, a network access node is a network element in a radio access network that is responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards, or contexts, a network access node may be differently referred to by those skilled in the art as a base transceiver station (BTS), radio network access node, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), access point (AP), Node B (NB), evolved Node B (eNB), next-generation Node B (gNB), transmission reception point (TRP), or some other suitable term. In some examples, a network access node may include two or more co-located or non-co-located TRPs. Each TRP may communicate on the same or different carrier frequencies within the same or different frequency bands. In an example where RAN 104 operates according to both LTE and 5G NR standards, one of these network access nodes may be an LTE network access node, while another network access node may be a 5G NR network access node.

[0083] RAN 104 is further illustrated as supporting wireless communication for a plurality of mobile devices. A mobile device may be referred to as a user equipment (UE) in the 3GPP standard, but may also be referred to by those skilled in the art as a mobile station (MS), subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal (AT), mobile terminal, wireless terminal, remote terminal, handset, terminal, user agent, mobile client, client, or some other suitable term. A UE may be a device (e.g., a mobile device) that provides a user with access to network services.

[0084] Within this disclosure, a "mobile" device does not necessarily need to have the ability to move and may be stationary. The terms mobile device or mobile equipment generally refer to a wide variety of devices and technologies. A UE may include several hardware structure components sized, shaped, and arranged to facilitate communication; such components may include antennas, antenna arrays, RF chains, transmit chains, amplifiers, one or more processors, etc., that are electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile equipment, cellular (cell) phones, smartphones, session initiation protocol (SIP) phones, laptop devices, personal computers (PCs), notebooks, netbooks, smartbooks, tablet devices, personal digital assistants (PDAs), and a wide variety of embedded systems, e.g., corresponding to the "Internet of Things" (IoT).

[0085] Additionally, the mobile device can be an automobile or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a Global Positioning System (GPS) device, an object tracking device, a drone, a multi-axis aircraft, a quadcopter, a remote control device, a consumer and / or wearable device (such as glasses), a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, etc. Additionally, the mobile device can be a digital home or smart home device, such as a home audio, video, and / or multimedia device, an appliance, a vending machine, a smart lighting device, a home security system, a smart meter, etc. Additionally, the mobile device can be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device (e.g., a smart grid) that controls electricity, lighting, water, etc., an industrial automation and enterprise device, a logistics controller, and / or an agricultural equipment, etc. Further still, the mobile device can provide connected healthcare or telemedicine support, such as remote healthcare. Telehealth devices can include telehealth monitoring devices and telehealth regulatory devices, and their communication can be given preferential treatment or prioritized access over other types of information, for example, in the form of prioritized access for critical service data transmission and / or associated QoS for critical service data transmission.

[0086] The wireless communication between the RAN 104 and the UE 106 can be described as utilizing an air interface. Transmissions on the air interface from a network access node (e.g., network access node 108) to one or more UEs (e.g., similar to UE 106) can be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term downlink can refer to a point-to-multipoint transmission originating at a network access node (e.g., network access node 108). Another way to describe this scenario can be to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a network access node (e.g., network access node 108) can be referred to as uplink (UL) transmissions. According to further aspects of the present disclosure, the term uplink can refer to a point-to-point transmission originating at a UE (e.g., UE 106).

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

[0088] The network access node 108 is not the only entity that can serve as a scheduling entity. That is, in some examples, a UE can serve as a scheduling entity to schedule resources for one or more scheduled entities (e.g., one or more other UEs). For example, a UE can communicate directly with other UEs in a peer-to-peer or device-to-device manner and / or in a relay configuration.

[0089] As Figure 1 illustrated, the scheduling entity 108 can broadcast downlink traffic 112 to one or more scheduled entities (e.g., one or more UEs 106). Broadly speaking, the scheduling entity 108 is a node or device responsible for scheduling traffic in a wireless communication network, including downlink traffic 112 and in some examples also including uplink traffic 116 from one or more scheduled entities (e.g., one or more UEs 106) to the scheduling entity 108. On the other hand, a scheduled entity (e.g., UE 106) is a node or device that receives downlink control information 114 (including but not limited to scheduling information (e.g., grants), synchronization or timing information), or other control information from another entity in the wireless communication network, such as the scheduling entity 108. Additionally, the scheduled entity (e.g., UE 106) can transmit uplink control information 118 including one or more uplink control channels to the scheduling entity 108. The uplink control 118 information can include a variety of packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions.

[0090] Additionally, uplink and / or downlink control information and / or traffic information can be transmitted on waveforms that can be divided in time into frames, subframes, time slots, and / or symbols. As used herein, a symbol can refer to a time unit in an orthogonal frequency division multiplexing (OFDM) waveform that carries one resource element (RE) per subcarrier. A time slot can carry 7 or 14 OFDM symbols. A subframe can refer to a duration of 1 ms. Multiple subframes or time slots can be grouped together to form a single frame or radio frame. Within the present disclosure, a frame can refer to a predetermined duration for wireless transmission (e.g., 10 ms), where each frame includes, for example, 10 subframes each of 1 ms duration. Of course, these definitions are not required, and any suitable scheme can be utilized to organize the waveform, and the various time divisions of the waveform can have any suitable duration.

[0091] Generally, the network access node 108 can include a backhaul interface for communicating with the backhaul portion 120 of the wireless communication system 100. The backhaul portion 120 can provide a link between the network access node 108 and the core network 102. Additionally, in some examples, the backhaul network can provide an interconnection between the respective network access nodes 108. Any suitable transport network can be used to employ various types of backhaul interfaces, such as direct physical connections, virtual networks, and the like.

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

[0093] Now referring to Figure 2 , by way of illustrative example and not limitation, a schematic illustration of an example of a radio access network (RAN) 200 according to some aspects of the present disclosure is provided. In some examples, the RAN 200 can be the same as the RAN 104 described above and illustrated in Figure 1 .

[0094] The geographical area covered by the RAN 200 can be divided into several cellular areas (cells), which can be uniquely identified by the user equipment (UE) based on the identification broadcast over the geographical area from an access point or network access node. Figure 2 Cells 202, 204, 206, and 208 are illustrated, where each can include one or more sectors (not shown). A sector is a sub-region of a cell. All sectors within a cell are served by the same network access node. The radio link within a sector can be identified by a single logical identification belonging to that sector. In a cell divided into sectors, multiple sectors within the cell can be formed by an antenna group, where each antenna is responsible for communicating with UEs in a part of the cell.

[0095] Various network access node arrangements can be utilized. For example, in Figure 2In [the figure], two network access nodes (network access nodes 210 and 212) are shown in cells 202 and 204. A third network access node (network access node 214) is shown as controlling a remote radio head (RRH) 216 in cell 206. That is, a network access node may have an integrated antenna or may be connected to an antenna or RRH 216 by a feeder cable. In the illustrated example, cells 202, 204, and 206 may be referred to as macro cells because network access nodes 210, 212, and 214 support cells with large dimensions. Additionally, network access node 218 is shown in cell 208, and cell 208 may overlap with one or more macro cells. In this example, cell 208 may be referred to as a small cell (e.g., a micro cell, a pico cell, a femto cell, a home network access node, a home Node B, a home evolved Node B, etc.) because network access node 218 supports a cell with a relatively small dimension. Cell sizing may be done according to system design and component constraints.

[0096] It is to be understood that RAN 200 may include any number of radio network access nodes and cells. Additionally, relay nodes may be deployed to extend the size or coverage area of a given cell. Network access nodes 210, 212, 214, 218 provide a wireless access point to the core network for any number of mobile devices. In some examples, network access nodes 210, 212, 214, and / or 218 may be the same as or similar to the scheduling entity 108 described above and illustrated in Figure 1 [the figure].

[0097] Figure 2 Further included is an unmanned aerial vehicle (UAV) 220, which may be a drone or a quadcopter. UAV 220 may be configured to act as a network access node, or more specifically as a mobile network access node. That is, in some examples, a cell may not have to be stationary, and the geographical area of a cell may move according to the location of a mobile network access node such as UAV 220.

[0098] Within RAN 200, a cell may include UEs that may communicate with one or more sectors of each cell. Additionally, each network access node 210, 212, 214, 218, and 220 may be configured to provide a wireless access point to the core network 102 (see Figure 1) access points. For example, UEs 222 and 224 may be in communication with network access node 210, UEs 226 and 228 may be in communication with network access node 212, UEs 230 and 232 may be in communication with network access node 216 via RRH 216, UE 234 may be in communication with network access node 218, and UE 236 may be in communication with mobile network access node 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may be the same as or similar to the UE / scheduled entity 106 described above and illustrated in Figure 1 In some examples, UAV 220 (e.g., quadcopter) may be a mobile network node and may be configured to act as a UE. For example, UAV 220 may operate within cell 202 by communicating with network access node 210.

[0099] In a further aspect of RAN 200, sidelink signals may be used between UEs without relying on scheduling or control information from a network access node. Sidelink communication may be used in, for example, device-to-device (D2D) networks, peer-to-peer (P2P) networks, vehicle-to-vehicle (V2V) networks, vehicle-to-everything (V2X) networks, and / or other suitable sidelink networks. For example, two or more UEs (e.g., UEs 238, 240, and 242) may communicate with each other using sidelink signal 237 without relaying the communication through a network access node. In some examples, UEs 238, 240, and 242 may each act as a scheduling entity or transmitting sidelink device and / or a scheduled entity or receiving sidelink device to schedule resources and communicate sidelink signal 237 therebetween without relying on scheduling or control information from a network access node. In other examples, two or more UEs (e.g., UEs 226 and 228) within the coverage area of a network access node (e.g., network access node 212) may also communicate sidelink signal 227 over a direct link (sidelink) without communicating the communication through network access node 212. In this example, network access node 212 may allocate resources to UEs 226 and 228 for sidelink communication.

[0100] To achieve a low block error rate (BLER) on the air interface while still achieving a very high data rate, channel decoding may be used. That is, wireless communication generally may utilize a suitable error-correcting block code. In a typical block code, an information message or sequence is split into code blocks (CBs), and an encoder (e.g., CODEC) at the transmitting device then mathematically adds redundancy to the information message. This redundancy in the encoded information message can improve the reliability of the message, thus enabling any bit errors that may occur due to noise to be corrected.

[0101] Data decoding can be implemented in a variety of ways. In earlier 5G NR specifications, user data was encoded using quasi-cyclic low-density parity-check (LDPC) with two different base graphs: one base graph was used for large code blocks and / or high code rates, and the other base graph was used for other cases. Polar decoding based on nested sequences was used to decode control information and the physical broadcast channel (PBCH). For these channels, puncturing, shortening, and repetition were used for rate matching.

[0102] Aspects of the present disclosure can be implemented using any suitable channel code. Various implementations of network access nodes and UEs can include suitable hardware and capabilities (e.g., encoders, decoders, and / or CODECs) to communicate wirelessly using one or more of these channel codes.

[0103] In the RAN 200, the ability of a UE to communicate while moving, independent of its location, is referred to as mobility. The various physical channels between the UE and the RAN 200 are generally established, maintained, and released under the control of the access and mobility management function (AMF). In some scenarios, the AMF can include a security context management function (SCMF) and a security anchor function (SEAF) that performs authentication. The SCMF can manage the security context for both the control plane and user plane functionality, either wholly or in part.

[0104] In aspects of the present disclosure, the RAN 200 can implement mobility and handover (i.e., the transfer of a UE's connection from one radio channel to another) using DL-based mobility or UL-based mobility. In a network configured for DL-based mobility, during a call with a scheduling entity, or at any other time, the UE can monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Depending on the quality of these parameters, the UE can maintain communication with one or more neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE can perform a handover or switch from the serving cell to the neighboring (target) cell. For example, the UE 224 can move from the geographical area corresponding to its serving cell 202 to the geographical area corresponding to the neighbor cell 206. When the signal strength or quality from the neighbor cell 206 exceeds the signal strength or quality of its serving cell 202 for a given amount of time, the UE 224 can transmit a report message to its serving network access node 210 indicating this condition. In response, the UE 224 can receive a handover command, and the UE can undergo a handover to cell 206.

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

[0106] Although the synchronization signal transmitted by the network access nodes 210, 212 and 214 / 216 may be uniform, the synchronization signal may not identify a specific cell, but may identify a zone including multiple cells operating on the same frequency and / or having the same timing. The use of zones in a 5G network or other next generation communication network implements an uplink-based mobility framework and improves the efficiency of both the UE and the network because the number of mobility messages that need to be exchanged between the UE and the network can be reduced.

[0107] In various implementations, the air interface in RAN 200 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum generally provides exclusive use of a portion of the spectrum by a mobile network operator purchasing a license from a government regulatory agency. Unlicensed spectrum provides shared use of a portion of the spectrum without a government-granted license. Although some technical rules generally still need to be followed to access unlicensed spectrum, any operator or device may obtain access. Shared spectrum may fall between licensed and unlicensed spectrum, where technical rules or restrictions may be required to access the spectrum, but the spectrum may still be shared by multiple operators and / or multiple radio access technologies (RATs). For example, a license holder of a portion of licensed spectrum may provide licensed shared access (LSA) to share the spectrum with other parties, e.g., with access obtained using conditions determined by a suitable license holder.

[0108] Each device communicating in RAN 200 may utilize one or more multiplexing techniques and multiple access algorithms to enable simultaneous communication of the individual devices. For example, the 5G NR specification utilizes orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) to provide multiple access for UL transmissions from UEs 222 and 224 to network access node 210 and multiplexing for DL transmissions from network access node 210 to one or more UEs 222 and 224. Additionally, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also known as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource spreading multiple access (RSMA), or other suitable multiple access schemes may be utilized to provide access. Further, multiplexing of DL transmissions from network access node 210 to UEs 222 and 224 may be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0109] Each device in the RAN 200 may also utilize one or more duplexing algorithms. Duplexing refers to a point-to-point communication link where both endpoints can communicate with each other in two directions. Full duplex means that both endpoints can communicate with each other simultaneously. Half duplex means that only one endpoint can send information to the other endpoint at a time. Time division duplexing (TDD) is typically used to implement half duplex emulation for wireless links. In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, in some scenarios, the channel is dedicated to transmission in one direction, and at other times, the channel is dedicated to transmission in the other direction, where the direction can change very quickly, e.g., several times per time slot. In a wireless link, a full duplex channel generally relies on physical isolation of the transmitter and receiver, as well as suitable interference cancellation techniques. Full duplex emulation for wireless links is typically achieved by using frequency division duplexing (FDD) or space division duplexing (SDD). In FDD, transmissions in different directions can operate at different carrier frequencies (e.g., within paired spectra). In SDD, transmissions in different directions on a given channel are separated from each other using space division multiplexing (SDM). In other examples, full duplex communication can be achieved within unpaired spectra (e.g., within a single carrier bandwidth), where transmissions in different directions occur in different subbands of the carrier bandwidth. This type of full duplex communication may be referred to herein as subband full duplex (SBFD), and is also known as flexible duplexing.

[0110] Reference will be made to Figure 3 the orthogonal frequency division multiplexing (OFDM) waveform schematically illustrated in

[0111] Now reference is made to Figure 3 , which illustrates an expanded view of an exemplary subframe 304 showing the OFDM resource grid 302. However, as will be readily appreciated by those skilled in the art, the PHY transmission structure for any particular application may differ from the examples described herein depending on any number of factors. Here, time is in the horizontal direction in terms of OFDM symbols; and frequency is in the vertical direction in terms of the subcarriers of the carrier.

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

[0113] A set of contiguous or non-contiguous resource blocks can be referred to herein as a resource block group (RBG), a subband, or a bandwidth part (BWP). A collection of subbands or BWPs can span the entire bandwidth. Scheduling of a scheduled entity (e.g., a UE) for downlink, uplink, or sidelink transmission typically involves scheduling one or more resource elements 306 within one or more subbands or bandwidth parts (BWPs). Thus, a UE generally utilizes only a subset of the resource grid 304. In some examples, an RB can be the smallest resource unit that can be allocated to a UE. Thus, the more RBs scheduled for a UE and the higher the modulation scheme selected for the air interface, the higher the data rate of that UE. These RBs can be scheduled by a network access node (e.g., a gNB, an eNB, etc.), or can be self-scheduled by a UE implementing D2D sidelink communication.

[0114] In this illustration, RB 308 is shown as occupying less than the entire bandwidth of subframe 302, with some subcarriers shown above and below RB 308. In a given implementation, subframe 302 can have a bandwidth corresponding to any number of one or more RBs 308. Additionally, in this illustration, RB 308 is shown as occupying less than the entire duration of subframe 302, but this is merely one possible example.

[0115] Each 1 ms subframe 302 can include one or more adjacent time slots. As an illustrative example, in Figure 3In the example shown, a subframe 302 includes four time slots 310. In some examples, a time slot may be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, in the case of a nominal CP, a time slot may include 7 or 14 OFDM symbols. Additional examples may include mini-slots (sometimes referred to as shortened transmission time intervals (TTIs)) having a shorter duration (e.g., one to three OFDM symbols). In some cases, these mini-slots or shortened transmission time intervals (TTIs) may occupy resources scheduled for ongoing time slot transmissions for the same or different UEs to transmit. Any number of resource blocks may be utilized within a subframe or time slot.

[0116] An expanded view of a time slot 310 illustrates a time slot 310 including a control region 312 and a data region 314. Generally, the control region 312 may carry control channels, while the data region 314 may carry data channels. Of course, a time slot may include all DL, all UL, or at least one DL portion and at least one UL portion. Figure 3 The structures illustrated are merely exemplary in nature and different time slot structures may be utilized and may include one or more for each of the control region and the data region.

[0117] Although not illustrated in Figure 3 each individual RE 308 within an RB 306 may be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 306 within the RB 308 may also carry pilots or reference signals. These pilots or reference signals may be available for a receiving device to perform channel estimation of the corresponding channel, which may enable coherent demodulation / detection of the control and / or data channels within the RB 308.

[0118] In some examples, a time slot 310 may be used for broadcast, multicast, groupcast, or unicast communication. For example, broadcast, multicast, or groupcast communication may refer to a point-to-multipoint transmission from one device (e.g., a network access node, UE, or other similar device) to other devices. Here, broadcast communication is delivered to all devices, while multicast or groupcast communication is delivered to multiple target receiving devices. Unicast communication may refer to a point-to-point transmission from one device to a single other device.

[0119] In an example of cellular communication over a cellular carrier via the Uu interface, for DL transmission, a scheduling entity (e.g., a network access node) may allocate one or more resource elements (REs) 306 (e.g., within the control region 312) to carry DL control information including one or more DL control channels (such as the Physical Downlink Control Channel (PDCCH)) to one or more scheduled entities (e.g., UEs). The PDCCH carries downlink control information (DCI), including but not limited to power control commands for DL and UL transmission (e.g., one or more open-loop power control parameters and / or one or more closed-loop power control parameters), scheduling information, grants, and / or RE assignments. The PDCCH may further carry Hybrid Automatic Repeat reQuest (HARQ) feedback transmissions, such as an acknowledgement (ACK) or a negative acknowledgement (NACK). HARQ is a technique well known to those of ordinary skill in the art, where for accuracy, the integrity of the packet transmission may be verified at the receiving side using, for example, any suitable integrity check mechanism (such as a checksum or a Cyclic Redundancy Check (CRC)). If the integrity of the transmission is confirmed, an ACK may be transmitted, while if not, a NACK may be transmitted. In response to a NACK, the transmitting device may send a HARQ retransmission, which may enable Chase Combining, Incremental Redundancy, etc.

[0120] The network access node may further allocate one or more REs 306 (e.g., in the control region 312 or the data region 314) to carry other DL signals, such as Demodulation Reference Signals (DMRS); Phase Tracking Reference Signals (PT-RS); Channel State Information (CSI) Reference Signals (CSI-RS); and Synchronization Signal Blocks (SSB). The SSB may be broadcast at regular intervals based on a period (e.g., 5, 10, 20, 40, 80, or 160 milliseconds). The SSB includes a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Control Channel (PBCH). The UE may use the PSS and SSS to achieve radio frame, subframe, slot, and symbol synchronization in the time domain, identify the center of the channel (system) bandwidth in the frequency domain, and identify the physical cell identity (PCI) of the cell.

[0121] The PBCH in SSB may further include: a master information block (MIB), which includes various system information and parameters for decoding system information blocks (SIBs). The SIB may be, for example, System Information Type 1 (SIB1), which may include various additional system information. The MIB and SIB1 together provide the minimum system information (SI) for initial access. Examples of the system information transmitted in the MIB may include, but are not limited to: subcarrier spacing (e.g., default downlink parameter design), system frame number, configuration of the PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), cell barring indicator, cell reselection indicator, raster offset, and search space for SIB1. Examples of the remaining minimum system information (RMSI) transmitted in SIB1 may include, but are not limited to, random access search space, paging search space, downlink configuration information, and uplink configuration information. The network access node may also transmit other system information (OSI).

[0122] In UL transmission, the scheduled entity (e.g., UE) may utilize one or more REs 306 to carry UL control information (UCI) to the scheduling entity, and the UL control information includes one or more UL control channels, such as the physical uplink control channel (PUCCH). The UCI may include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. Examples of uplink reference signals may include sounding reference signals (SRS) and uplink DMRS. In some examples, the UCI may include a scheduling request (SR), i.e., a request for the scheduling entity to schedule an uplink transmission. Here, in response to the SR transmitted on the UCI, the scheduling entity may transmit downlink control information (DCI), which may schedule resources for uplink packet transmission. The UCI may also include HARQ feedback, channel state feedback (CSF) (such as CSI report), or any other suitable UCI.

[0123] In addition to control information, one or more REs 306 (e.g., within the data region 314) may also be allocated for data traffic. Such data traffic may be carried on one or more traffic channels, such as for DL transmission, it may be carried on the physical downlink shared channel (PDSCH); or for UL transmission, it may be carried on the physical uplink shared channel (PUSCH). In some examples, one or more REs 306 within the data region 314 may be configured to carry other signals, such as one or more SIBs and DMRS.

[0124] In an example of sidelink communication on a sidelink carrier via a proximity service (ProSe) PC5 interface, the control region 312 of slot 310 may include a physical sidelink control channel (PSCCH) that includes sidelink control information (SCI) transmitted by an initiating (transmitting) sidelink device (e.g., a Tx V2X device or other Tx UE) to a set of one or more other receiving sidelink devices (e.g., an Rx V2X device or other Rx UE). The data region 314 of slot 310 may include a physical sidelink shared channel (PSSCH) that includes sidelink data traffic transmitted by the initiating (transmitting) sidelink device within resources reserved on the sidelink carrier by the transmitting sidelink device via the SCI. Other information may further be transmitted on respective resource elements (REs) 306 within slot 310. For example, HARQ feedback information may be transmitted from a receiving sidelink device to a transmitting sidelink device in a physical sidelink feedback channel (PSFCH) within slot 310. Additionally, one or more reference signals, such as a sidelink SSB, a sidelink CSI-RS, a sidelink SRS, and / or a sidelink positioning reference signal (PRS), may be transmitted within slot 310.

[0125] These physical channels are generally multiplexed and mapped to transport channels for handling by the media access control (MAC) layer. A transport channel carries an information block, which is referred to as a transport block (TB). The transport block size (TBS) (which may correspond to the number of information bits) may be a controlled parameter based on a modulation and coding scheme (MCS) and the number of resource blocks (RBs) in a given transmission.

[0126] Figure 4 FIG. 400 is a diagram illustrating an example of a downlink (DL) channel within a 5G new radio (NR) subframe in accordance with some aspects of the present disclosure. In this example (e.g., for slot configuration 0), each slot may include 14 symbols. The first arrowed line indicates a subset of the system bandwidth resource blocks (RBs) 402 (e.g., Figure 3 a subset of the resource grid 304). In some examples, the symbols on the DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols.

[0127] The physical downlink control channel (PDCCH) 404 may carry DCI within one or more control channel elements (CCEs). Each CCE may include nine resource element groups (REGs), where each REG may include four consecutive resource elements (REs) in an OFDM symbol.

[0128] The primary synchronization signal (PSS) 406 is shown in symbol 2 of the subframe. The PSS 406 can be used by the UE to determine subframe and symbol timing and the physical layer identity. The secondary synchronization signal (SSS) 408 is shown in symbol 4 of the subframe. The SSS 408 can be used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the positions of the aforementioned DMRS. The physical broadcast channel (PBCH) 410 carrying the master information block (MIB) as discussed herein can be logically grouped with the PSS 406 and the SSS 408 to form the SS / PBCH block 412. The MIB can indicate the number of resource blocks (RBs) in the system bandwidth, the system frame number (SFN), and other information. As indicated by the second arrowed line, the length of the SS / PBCH block 412 is 20 RBs 414 in this example.

[0129] The physical downlink shared channel (PDSCH) 416 carries user data, broadcast system information not transmitted through the PBCH (such as system information blocks (SIBs)), and paging messages. Additionally, in some examples, the PDSCH 416 can carry DCI (e.g., control-related information).

[0130] The MIB in the PBCH can include system information (SI), along with parameters for decoding system information blocks (SIBs). In some examples, this SIB is the system information type 1 SIB (referred to as SIB1) that includes additional SI. Examples of SI transmitted in the MIB can include but are not limited to subcarrier spacing, system frame number, configuration of the PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), and the search space for SIB1. Examples of SI transmitted in SIB1 can include but are not limited to the random access search space, downlink configuration information, and uplink configuration information. The MIB and SIB1 together provide the minimum SI for initial access.

[0131] The initial access procedure of the UE for using the above information is briefly discussed below. As discussed above, the network access node can transmit synchronization signals (e.g., including PSS and SSS) in the network to enable the UE to synchronize with the network access node, and transmit SI (e.g., including MIB, RMSI, and OSI) to facilitate initial network access. The network access node can transmit the PSS, SSS, and / or MIB via the SSB on the PBCH, and can broadcast the RMSI and / or OSI on the PDSCH.

[0132] A UE attempting to access the RAN can perform an initial cell search by detecting the PSS from a network access node of the RAN (e.g., the PSS of a cell of the network access node). The PSS enables the UE to synchronize with the periodic timing of the network access node and can indicate the physical layer identity value assigned to the cell. The UE can also receive the SSS from the network access node, which enables the UE to synchronize with the cell at the radio frame level. The SSS can also provide a cell identity value, which the UE can combine with the physical layer identity value to identify the cell.

[0133] After receiving the PSS and SSS, the UE can receive SI from the network access node. The system information can be in the form of the MIB and SIBs discussed above. The system information includes necessary or critical information for the UE to access the network, such as downlink (DL) channel configuration information, uplink (UL) channel configuration information, access class information, and cell barring information, as well as other less critical information. The MIB can include SI for initial network access and scheduling information for RMSI and / or OSI. After decoding the MIB, the UE can receive RMSI and / or OSI.

[0134] The SI includes information that enables the UE to determine how to perform an initial access to the RAN (e.g., Figure 2 the RAN 200). In some examples, SIB2 includes random access configuration information (e.g., RACH configuration), which indicates the resources that the UE is to use to communicate with the RAN during initial access. The random access configuration information can indicate, for example, the resources allocated by the RAN for the PRACH procedure. For example, the RACH configuration can indicate the resources allocated by the network for the UE to transmit the PRACH preamble and receive the random access response. In some examples, the RACH configuration identifies a monitoring occasion (MO) that specifies a set of symbols (e.g., in a PRACH time slot) scheduled by the network access node for the PRACH procedure. The RACH configuration can also indicate the size of the random access response window during which the UE is to monitor for a response to the PRACH preamble. In some examples, the RACH configuration can further specify that the random access response window starts a specific number of subframes after the end of the PRACH preamble. After obtaining the MIB, RMSI, and / or OSI, the UE can thus perform a random access procedure for initial access to the RAN.

[0135] Figure 4 FIG. 400 is a diagram illustrating an example of DL channels within a 5G NR subframe. In this example (e.g., for slot configuration 0), each slot can include 14 symbols. The first arrowed line indicates a subset of the system bandwidth RBs 402 (e.g., Figure 3a subset of the resource grid 304). In some examples, the symbols on the DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols.

[0136] The physical downlink control channel (PDCCH) 404 may carry DCI within one or more control channel elements (CCEs). Each CCE may include nine resource element (RE) groups (REGs), where each REG may include four consecutive REs in an OFDM symbol.

[0137] The primary synchronization signal (PSS) 406 is shown in symbol 2 of the subframe. The PSS 406 may be used by the UE to determine subframe and symbol timing and the physical layer identity. The secondary synchronization signal (SSS) 408 is shown in symbol 4 of the subframe. The SSS 408 may be used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE may determine the physical cell identifier (PCI). Based on the PCI, the UE may determine the location of the aforementioned DMRS. The physical broadcast channel (PBCH) 410 carrying the master information block (MIB) as discussed herein may be logically grouped with the PSS 406 and the SSS 408 to form an SS / PBCH block 412. The MIB may indicate the number of RBs in the system bandwidth, the system frame number (SFN), and other information. As indicated by the second arrowed line, the length of the SS / PBCH block 412 is 20 RBs 414 in this example.

[0138] The physical downlink shared channel (PDSCH) 416 carries user data, broadcast system information not transmitted through the PBCH (such as system information blocks (SIBs)), and paging messages. Additionally, in some examples, the PDSCH 416 may carry DCI (e.g., control-related information).

[0139] Figure 5 is a block diagram illustrating an example of a wireless communication system supporting beamforming and / or multiple-input multiple-output (MIMO) communication in accordance with some aspects of the present disclosure. In some aspects of the present disclosure, a scheduling entity and / or a scheduled entity may be configured for beamforming and / or MIMO techniques. In a MIMO system, a transmitter 502 includes a plurality of transmit antennas 504 (e.g., N transmit antennas), and a receiver 506 includes a plurality of receive antennas 508 (e.g., M receive antennas). Thus, there are N×M signal paths 510 from the transmit antennas 504 to the receive antennas 508. Each of the transmitter 502 and the receiver 506 may be implemented, for example, in a scheduling entity, a scheduled entity, or any other suitable wireless communication device.

[0140] The use of such multi-antenna techniques enables a wireless communication system 500 to utilize the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing can be used to simultaneously transmit different data streams (also referred to as layers) on the same time-frequency resources. These data streams can be transmitted to a single UE to increase the data rate or to multiple UEs to increase the overall system capacity, the latter being referred to as multi-user MIMO (MU-MIMO). This is achieved by spatially pre-coding each data stream (i.e., multiplying these data streams by different weights and phase shifts) and then transmitting each spatially pre-coded stream on the downlink via multiple transmit antennas. The spatially pre-coded data streams arrive at the UE with different spatial signatures, which enable each UE to recover one or more data streams intended for that UE. On the uplink, each UE transmits a spatially pre-coded data stream, which enables the network access node to identify the source of each spatially pre-coded data stream.

[0141] The number of data streams or layers corresponds to the transmission rank. In general, the rank of a MIMO system (e.g., the wireless communication system 500 supporting MIMO) is limited by the lower of the number of transmit or receive antennas 504 or 508. Additionally, the channel conditions at the UE and other considerations (such as the available resources at the network access node) may also affect the transmission rank. For example, the rank assigned to a particular UE on the downlink (and thus, the number of data streams) can be determined based on a rank indicator (RI) transmitted from the UE to the network access node. The RI can be determined based on the antenna configuration (e.g., the number of transmit and receive antennas) and the measured signal-to-interference-plus-noise ratio (SINR) on each receive antenna. The RI can indicate, for example, the number of layers that can be supported under the current channel conditions. The network access node can use the RI along with resource information (e.g., the available resources and the amount of data to be scheduled for the UE) to assign a transmission rank to the UE.

[0142] In a time-division duplex (TDD) system, the UL and DL are reciprocal, where each uses different time slots of the same frequency bandwidth. Thus, in a TDD system, the network access node can assign the rank for DL MIMO transmission based on UL SINR measurements (e.g., based on sounding reference signals (SRS) or other pilot signals transmitted from the UE). Based on the assigned rank, the network access node can then transmit CSI-RS using a separate channel state information-reference signal (CSI-RS) sequence for each layer to provide multi-layer channel estimation. Based on this CSI-RS, the UE can measure the channel quality across the layers and resource blocks and feedback channel quality indicator (CQI) and rank indicator (RI) values to the network access node for use in updating the rank and assigning resource elements (REs) for future downlink transmissions.

[0143] In one example, asFigure 5 As shown, rank-2 spatial multiplexing transmission on a 2x2 MIMO antenna configuration will transmit one data stream from each of the transmit antennas 504. Each data stream arrives at each receive antenna 508 along a different signal path in the signal paths 510. The receiver 506 can then use the signals received from each of the receive antennas 508 to reconstruct these data streams.

[0144] Beamforming is a signal processing technique that can be used at the transmitter 502 or the receiver 506 to shape or direct an antenna beam (e.g., a transmit beam or a receive beam) along a spatial path between the transmitter 502 and the receiver 506. Beamforming can be achieved by combining signals communicated via the antennas 504 or 508 (e.g., antenna elements of an antenna array) such that some of these signals experience constructive interference while others experience destructive interference. To create the desired constructive / destructive interference, the transmitter 502 or the receiver 506 can apply amplitude and / or phase offsets to the signals transmitted or received from each of the antennas 502 or 506 associated with the transmitter 504 or the receiver 508.

[0145] In a 5G New Radio (NR) system, especially for systems above 6 GHz or mmWave systems, beamformed signals can be used for most downlink channels, including the Physical Downlink Control Channel (PDCCH) and the Physical Downlink Shared Channel (PDSCH). Additionally, broadcast control information (such as SSB, Slot Format Indicator (SFI), and paging information) can be transmitted in a beam sweeping manner so that all scheduled entities (UEs) in the coverage area of the Transmission and Reception Point (TRP) (e.g., gNB) can receive this broadcast control information. Additionally, for UEs configured with beamforming antenna arrays, beamformed signals can also be used for uplink channels (including the Physical Uplink Control Channel (PUCCH) and the Physical Uplink Shared Channel (PUSCH)). However, it should be understood that beamformed signals can also be used by enhanced mobile broadband (eMBB) gNBs for sub-6 GHz systems.

[0146] A network access node (e.g., gNB) can generally be capable of communicating with a UE using transmit beams (e.g., downlink transmit beams) with varying beam widths. For example, the network access node can be configured to utilize a wider beam when communicating with a moving UE and a narrower beam when communicating with a stationary UE. The UE can further be configured to utilize one or more downlink receive beams to receive signals from the network access node.

[0147] In some examples, to select one or more serving beams (e.g., one or more downlink transmit beams and one or more downlink receive beams) for communicating with a UE, the network access node may transmit reference signals, such as synchronization signal blocks (SSBs), tracking reference signals (TRSs), or channel state information reference signals (CSI-RSs), on each of a plurality of beams (e.g., on each of a plurality of downlink transmit beams) in a beam sweeping manner. The UE may measure the received signal strength of the reference signals on each beam (e.g., measure the RSRP on each of the plurality of downlink transmit beams) and transmit a beam measurement report to the network access node, the beam measurement report indicating the layer 1 RSRP (L-1RSRP) of each of the measured beams. Subsequently, the network access node may select one or more serving downlink beams (e.g., downlink transmit beams and downlink receive beams) for communicating with the UE based on the beam measurement report. The resulting selected downlink transmit beam and downlink receive beam may form a downlink beam pair link. In other examples, when the channel is reciprocal, the network access node may derive the (a) specific beam (e.g., the (a) specific downlink beam) for communicating with the UE based on the uplink measurement of one or more uplink reference signals, such as sounding reference signals (SRSs).

[0148] Similarly, uplink beams (e.g., the (a) uplink transmit beam(s) at the UE and the (a) uplink receive beam(s) at the network access node) may be selected by measuring the RSRP of the received uplink reference signals (e.g., SRSs) or downlink reference signals (e.g., SSBs or CSI-RSs) during uplink or downlink beam sweeping. For example, the network access node may determine the uplink beam through uplink beam management at the network access node measured via SRS beam sweeping or through downlink beam management at the UE measured via SSB / CSI-RS beam sweeping. The selected uplink beam may be indicated by the selected SRS resource (e.g., the time-frequency resource for the transmission of SRS) when implementing uplink beam management, or by the selected SSB / CSI-RS resource when implementing downlink beam management. For example, the selected SSB / CSI-RS resource may have a spatial relationship with the selected uplink transmit beam (e.g., the uplink transmit beam for PUCCH, SRS, and / or PUSCH). The resulting selected uplink transmit beam and uplink receive beam may form an uplink beam pair link.

[0149] Figure 6FIG. is an illustration depicting an example of communication between a radio access network (RAN) node (e.g., network access node 604) and a wireless communication device (e.g., UE 602) using beamformed signals, in accordance with some aspects of the present disclosure. The network access node 604 may correspond to Figure 1 , 2 , any one of the network access nodes (e.g., scheduling entity, gNB, base station) shown in 5 - 12, 14 - 17, 25, 29, 31, 37, and / or 39 - 44. The UE 602 may correspond to Figure 1 , 2 , any one of the UEs (e.g., scheduled entity, wireless communication device) shown in 5 - 12, 14 - 17, 29, 31, and / or 44.

[0150] In Figure 6 the example shown, the network access node 604 is configured to generate a plurality of beams 606a–606h, each beam associated with a different beam direction. Additionally, the UE 602 is configured to generate a plurality of beams 608a–608e, each beam associated with a different beam direction. The network access node 604 and the UE 602 may use a downlink beam management scheme and / or an uplink beam management scheme to select one or more of the beams 606a - 606h on the network access node 604 and one or more of the beams 608a - 608e on the UE 602 for communicating uplink and downlink signals therebetween.

[0151] In an example of a downlink beam management scheme for selecting a downlink beam, the network access node 604 may be configured to sweep or transmit on each of a plurality of downlink transmit beams 606a–606h during one or more synchronization time slots. For example, the network access node 604 may transmit a reference signal (such as an SSB or CSI-RS) on each beam in a different beam direction during a synchronization time slot. Transmission of the beam reference signal may occur periodically (e.g., as configured by the gNB via radio resource control (RRC) signaling), semi-persistently (e.g., as configured by the gNB via RRC signaling and activated / deactivated via media access control - control element (MAC-CE) signaling), or aperiodically (e.g., as triggered by the gNB via downlink control information (DCI)). It should be noted that although some beams are illustrated as being adjacent to each other, such an arrangement may be different in different aspects. For example, the downlink transmit beams 606a - 606h transmitted during the same symbol may not be adjacent to each other. In some examples, the network access node 604 may transmit more or fewer beams distributed in all directions (e.g., 360 degrees).

[0152] Additionally, UE 602 is configured to receive downlink beam reference signals on multiple downlink receiving beams 608a–608e. In some examples, UE 602 searches for and identifies each of the downlink transmission beams 606a–606h based on the beam reference signals. Subsequently, UE 602 performs beam measurements (e.g., RSRP, SINR, reference signal received quality (RSRQ), etc.) on the beam reference signals on each of the downlink receiving beams 608a - 608e to determine the corresponding beam quality of each of the downlink transmission beams 606a - 606h, as measured on each of the downlink receiving beams 608a - 608e.

[0153] UE 602 may generate and transmit a beam measurement report to network access node 604, including the corresponding beam index for each of the downlink transmission beams 606a - 606h and the beam measurements for each of the downlink transmission beams 606a - 606h on each of the downlink receiving beams 608a - 608e. Subsequently, network access node 604 may select one or more downlink transmission beams on which to transmit unicast downlink control information and / or user data traffic to UE 602. In some examples, the selected downlink transmission beam(s) has the highest gain from the beam measurement report. In some examples, UE 602 may further identify the downlink transmission beam(s) selected by the network access node from the beam measurements. The transmission of the beam measurement report may occur periodically (e.g., as configured by the gNB via RRC signaling), semi - persistently (e.g., as configured by the gNB via RRC signaling and activated / deactivated via MAC - CE signaling), or aperiodically (e.g., triggered by the gNB via DCI).

[0154] Network access node 604 or UE 602 may further select a corresponding downlink receiving beam on UE 602 for each selected serving downlink transmission beam to form a corresponding downlink beam pair link (BPL) for each selected serving downlink transmission beam. For example, UE 602 may use beam measurements to select a corresponding downlink receiving beam for each serving downlink transmission beam. In some examples, the selected downlink receiving beam to be paired with a particular downlink transmission beam may have the highest gain for that particular downlink transmission beam.

[0155] In one example, a single downlink transmit beam (e.g., beam 606d) on network access node 604 and a single downlink receive beam (e.g., beam 608c) on the UE can form a single downlink BPL for communication between network access node 602 and UE 602. In another example, multiple downlink transmit beams (e.g., beams 606c, 606d, and 606e) on network access node 604 and a single downlink receive beam (e.g., beam 608c) on UE 602 can form corresponding downlink BPLs for use in communication between network access node 604 and UE 602. In another example, multiple downlink transmit beams (e.g., beams 606c, 606d, and 606e) on network access node 604 and multiple downlink receive beams (e.g., beams 608c and 608d) on UE 602 can form corresponding downlink BPLs for use in communication between network access node 604 and UE 602. In this example, the first downlink BPL can include downlink transmit beam 606c and downlink receive beam 608c, the second downlink BPL can include downlink transmit beam 608d and downlink receive beam 608c, and the third downlink BPL can include downlink transmit beam 608e and downlink receive beam 608d.

[0156] When the channel is reciprocal, the downlink beam management schemes described above can also be used to select one or more uplink BPLs for uplink communication from UE 602 to network access node 604. For example, the downlink BPL formed by beam 606d and beam 608e can also serve as an uplink BPL. Here, beam 608c is used as the uplink transmit beam, and beam 606d is used as the uplink receive beam.

[0157] In an example of uplink beam management, UE 602 can be configured to sweep or transmit on each of multiple uplink transmit beams 608a - 608e. For example, UE 602 can transmit SRS on each beam in different beam directions. Additionally, network access node 604 can be configured to receive uplink beam reference signals on multiple uplink receive beams 606a - 606h. In some examples, network access node 604 searches for and identifies each of the uplink transmit beams 608a - 608e based on the beam reference signals. Subsequently, network access node 604 performs beam measurements (e.g., RSRP, SINR, etc.) on the beam reference signals on each of the uplink receive beams 606a - 606h to determine the corresponding beam quality of each of the uplink transmit beams 608a - 608e as measured on each of the receive beams 606a - 606h.

[0158] Subsequently, the network access node 604 may select one or more uplink transmit beams on which the UE 602 will transmit unicast downlink control information and / or user data traffic to the network access node 604. In some examples, the (selected) uplink transmit beams have the highest gain. The network access node 604 may further select a corresponding uplink receive beam with respect to the network access node 604 for each selected serving uplink transmit beam to form a corresponding uplink beam pair link (BPL) for each selected serving uplink transmit beam. For example, the network access node 604 may use beam measurements to select the corresponding uplink receive beam for each serving uplink transmit beam. In some examples, the selected uplink receive beam to be paired with a particular uplink transmit beam may have the highest gain for that particular uplink transmit beam.

[0159] The network access node 604 may then notify the UE 602 of the selected uplink transmit beams. For example, the network access node 604 may provide a sounding reference signal (SRS) resource identifier (ID) that identifies the SRS transmitted on the selected uplink transmit beams. In some examples, the network access node 604 may apply each selected uplink transmit beam (and the corresponding uplink receive beam) to an uplink signal (e.g., physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH), SRS, etc.) and transmit to the UE 602 the corresponding SRS resource ID associated with the selected uplink transmit beam applied to each uplink signal. When the channel is reciprocal, the uplink beam management scheme described above may also be used to select one or more downlink BPLs for downlink communication from the network access node 604 to the UE 602. For example, the uplink BPLs may also be used as downlink BPLs.

[0160] The channels or carriers described above with reference to Figures 1 to 6 are not necessarily all the channels or carriers available between the scheduling entity and the scheduled entity, and one of ordinary skill in the art will recognize that other channels or carriers, such as other traffic, control, and feedback channels, may be utilized in addition to those illustrated.

[0161] In some wireless communication networks, the functionality of the network access node and / or other components of the network may be distributed across multiple entities. Figure 7FIG. is a schematic diagram providing a high-level illustration of one example of an integrated access backhaul (IAB) network 702 in accordance with some aspects of the present disclosure. In this illustration, a wireless communication network 700 (including the IAB network 702) is coupled to a remote network 704 (such as a primary backhaul network or a mobile core network). In such an IAB network 702, wireless spectrum can be used for both access links and backhaul links. In some examples, the wireless spectrum can utilize millimeter wave (mmWave) or sub-6 GHz carrier frequencies.

[0162] The IAB network 702 can be similar to Figure 2 the RAN 200 shown in, because the IAB network 702 can be divided into several cells 706, 708, 710, 712, and 714, and each cell can be served by a corresponding IAB node 716, 718, 720, 722, and 724. Each of the IAB nodes 716 - 724 can be an access point, a network access node (BS), a base station (BS), an eNB, a gNB, or other nodes that utilize wireless spectrum (e.g., radio frequency (RF) spectrum) to support access for one or more UEs located within the cells 706 - 714 served by the IAB nodes 716 - 724.

[0163] In Figure 7 the example shown in, the IAB node 716 communicates with UEs 726 and 728 via wireless access links 730 and 732, the IAB node 718 communicates with the UE 734 via the wireless access link 736, and the IAB node 722 communicates with the UE 738 via the wireless access link 740. The IAB nodes 716 - 724 are further interconnected via one or more wireless backhaul links 742, 744, 746, 748, 750, and 752. Each of the wireless backhaul links 742 - 752 can utilize the same wireless spectrum (e.g., radio frequency (RF) spectrum) as the access links 730, 732, 736, 740 to backhaul access traffic to / from the remote network 704. This can be referred to as wireless self-backhaul. Such wireless self-backhaul can enable the rapid and easy deployment of highly dense small cell networks. That is, instead of requiring each new gNB deployment to be equipped with its own hard-wired backhaul connection, the wireless spectrum used for communication between the gNB and UEs can be used for backhaul communication between any number of IAB nodes to form the IAB network 702.

[0164] In Figure 7In the example shown, IAB node 716 communicates with IAB node 720 via wireless backhaul link 742, IAB node 720 communicates with IAB node 722 via wireless backhaul link 744, IAB node 722 communicates with IAB node 724 via wireless backhaul link 746, IAB node 724 communicates with IAB node 718 via wireless backhaul link 748, IAB node 718 communicates with IAB node 716 via wireless backhaul link 750, and IAB node 718 communicates with IAB node 720 via wireless backhaul link 752. As Figure 7 shown, each of IAB nodes 716 - 724 can be connected to two or more other IAB nodes via respective wireless backhaul links 742 - 752 to achieve robustness.

[0165] Some or all of IAB nodes 716 - 724 can also be connected via a wired backhaul link (e.g., optical fiber, coaxial cable, Ethernet, copper wire, etc.) and / or a microwave backhaul link. Thus, IAB network 702 can support both wired / microwave and wireless backhaul traffic. At least one of these IAB nodes can be a border IAB node, also referred to herein as an IAB donor node, which also provides a communication link 754 to remote network 704. IAB node 724 is an example of an IAB donor node. For example, IAB node 724 can include a wired (e.g., optical fiber, coaxial cable, Ethernet, copper wire), microwave, or other suitable communication link 754 to remote network 704.

[0166] To facilitate wireless communication between IAB nodes 716 - 724 and between IAB nodes 724 - 724 and UEs served by IAB nodes 716 - 724, each of IAB nodes 724 - 724 can be configured to operate as both a scheduling entity and a scheduled entity. Thus, an IAB node (e.g., IAB node 716) can utilize the same wireless spectrum to transmit access traffic to / from a UE and then backhaul that access traffic to / from remote network 704. For example, to backhaul access traffic to / from IAB node 718, IAB node 718 can communicate with IAB node 720 to transmit backhaul access traffic via wireless backhaul link 742, IAB node 720 can communicate with IAB node 722 to transmit backhaul access traffic via wireless backhaul link 744, and IAB node 722 can communicate with IAB node 724 to transmit backhaul access traffic via wireless backhaul link 746. In this example, IAB nodes 720 and 722 can each operate as both a scheduling entity and a scheduled entity to backhaul access traffic to / from IAB node 716. Thus, communication between IAB node pairs can be individually scheduled by one of the IAB nodes within that IAB node pair.

[0167] In other examples, an IAB node may schedule wireless backhaul communication between other IAB node pairs. For example, IAB node 724 may operate as a scheduling entity of IAB network 702, while IAB nodes 716, 720, and 722 each operate as scheduled entities to backhaul access traffic to / from IAB node 716. In this example, IAB node 724 may schedule wireless backhaul communication between each IAB node pair (e.g., between IAB node 716 and IAB node 720, between IAB node 720 and IAB node 722, and between IAB node 722 and IAB node 724). As another example, IAB node 722 may act as a scheduling entity to schedule wireless backhaul communication between IAB nodes 716 and 720 and also between IAB node 720 and IAB node 722. IAB node 722 may then operate as a scheduled entity to allow IAB node 724 to schedule wireless backhaul communication therebetween.

[0168] Figure 8 FIG. is an example diagram illustrating a wireless communication network 800 having communication between a network access node 802 and four UEs (first UE 810, second UE 814, third UE 822, fourth UE 826) using beamformed signals according to some aspects of the present disclosure. Network access node 802 may correspond to Figure 1 , 2 , any one of the network access nodes (e.g., a scheduling entity, gNB, base station) shown in any of 5 - 12, 14 - 17, 25, 29, 31, 37, and / or 39 - 44. The four UEs (first UE 810, second UE 814, third UE 822, fourth UE 826) may correspond to Figure 1 , 2 , any one of the UEs (e.g., a scheduled entity, wireless communication device) shown in any of 5 - 12, 14 - 17, 29, 31, and / or 44. The first RF repeater device 806 and the second RF repeater device 818 may correspond to Figures 7 - 21 , any one of the RF repeater devices of 29, 31, 32, 37, 39, and / or 40.

[0169] In Figure 8In the example shown, the network access node 802 may be configured to generate multiple beams 804a, 804b, each beam associated with a different beam direction. Only two beams in two directions are shown to avoid cluttering the drawing. The network access node 802 may transmit and / or receive on one or both of the multiple beams 804a, 804b. The corresponding beams among the multiple beams 804a, 804b may be directed to various angles (e.g., azimuth). The first UE 810 and / or the second UE 814 may each be at a certain distance from the network access node 802. Additionally or alternatively, there may be structures or obstacles (not shown) between the direct line of sight between the network access node 802 and the first UE 810 and / or between the network access node 802 and the second UE 814.

[0170] The first RF repeater device 806 may be located between the network access node 802 and the first UE 810 and / or between the network access node 802 and the second UE 814. The first RF repeater device 806 may have an omnidirectional beam 808 or may be customized to direct a wide beam (not shown) in one direction without the ability to steer the beam.

[0171] The first UE 810 may have an omnidirectional beam 812. The second UE 814 may have an antenna array (not shown) that allows the second UE 814 to perform beamforming and direct the beam in various directions (e.g., azimuth). Beamforming may allow the second UE 814 to form narrow directional beams 816 (one of the multiple directional beams shown to avoid cluttering the drawing) in multiple directions, and / or form wide directional beams (not shown) in multiple directions, and / or form an omnidirectional beam (not shown).

[0172] The first RF repeater device 806 may amplify and forward (e.g., convey) RF signals exchanged between the first UE 810, the second UE 814, and the network access node 802. The amplification and forwarding may be two-way. The two-way link between the network access node 802 and the first RF repeater device 806 may be referred to as the backhaul link. The two-way links between the first RF repeater device 806 and the first UE 810 and between the first RF repeater device 806 and the second UE 814 may each be referred to as access links.

[0173] The second RF repeater device 818 may be located between the network access node 802 and the third UE 822 and / or between the network access node 802 and the fourth UE 826. The second RF repeater device 818 may have an omnidirectional beam or may be customized to direct a wide beam (not shown) in one direction without the ability to steer the beam.

[0174] The third UE 822 may have an omnidirectional beam 824. The fourth UE 826 may have an antenna array (not shown) that allows the fourth UE 826 to perform beamforming and direct the beam in various directions (e.g., azimuth). Beamforming may allow the fourth UE 826 to form narrow directional beams 828 in multiple directions (one of the multiple directional beams shown to avoid cluttering the drawing), and / or form wide directional beams in multiple directions (not shown), and / or form an omnidirectional beam (not shown).

[0175] The second RF repeater device 818 may amplify and forward (e.g., convey) RF signals exchanged between the third UE 822, the fourth UE 826, and the network access node 802. The amplification and forwarding may be bidirectional. The bidirectional link between the network access node 802 and the second RF repeater device 818 may be referred to as the fronthaul link. The bidirectional links between the second RF repeater device 818 and the third UE 822 and between the second RF repeater device 818 and the fourth UE 826 may each be referred to as access links.

[0176] As described, the first RF repeater device 806 and the second RF repeater device 818 may each amplify and forward RF signals (e.g., analog signals in the physical (PHY) layer). The first RF repeater device 806 and the second RF repeater device 818 may be referred to herein as RF repeater devices, analog repeater devices, and / or layer 1 repeater devices. They may operate in the analog domain, receive RF signals via their respective omnidirectional beams 808, 820, pass the RF signals through their RF amplifier chains (not shown), and transmit (e.g., forward) the amplified RF signals via their respective omnidirectional beams 808, 820. One benefit of RF repeater devices (such as the first RF repeater device 806 and the second RF repeater device 818) may be low cost. RF repeater devices have analog RF chains and components and generally do not have a digital processing chain. They may not have the ability to steer antenna beams. These RF repeater devices may be used for coverage / capacity enhancement in, for example, 5G millimeter wave (mmWave) deployments. However, millimeter wave communication systems are vulnerable to blockage due to higher penetration loss and reduced diffraction. Densification of coverage may be useful in millimeter wave systems that may have a large number of nodes. Thus, RF repeater devices (such as the first RF repeater device 806 and the second RF repeater device 818) may provide a cost-effective solution for densification in millimeter wave systems.

[0177] Figure 9 is a schematic diagram illustrating an example of IAB node functionality within the IAB network 900 according to some aspects of the present disclosure. In Figure 9In the example shown, an IAB node is shown coupled to a core network 904 via a wired connection. This IAB node may be referred to herein as an IAB donor node 902, which may be, for example, an enhanced gNB including functionality for controlling the IAB network 900. In some examples, the IAB donor node 902 may include a central unit (CU) 906 and a distributed unit (DU) 908. The CU 906 may be configured to operate as a centralized network node (or central entity) within the IAB network 900. For example, the CU 906 may include radio resource control (RRC) layer functionality and packet data convergence protocol (PDCP) layer functionality to control / configure other nodes (e.g., IAB nodes and UEs) within the IAB network 900. In some aspects, RRC signaling may be used for various functions, including, for example, establishing and releasing user data bearers. In some examples, RRC signaling messages may be transmitted on signaling bearers (e.g., SRB1 and SRB2).

[0178] The DU 908 may be configured to operate as a scheduling entity to schedule scheduled entities (e.g., other IAB nodes and UEs) of the IAB donor node 902. For example, the DU 908 of the IAB donor node 902 may operate as a scheduling entity to schedule IAB nodes 910 and 912 and UEs 914 and 916. Thus, the DU 908 of the IAB donor node 902 may schedule communications with IAB nodes 910 and 912 via corresponding backhaul links and schedule communications with UEs 914 and 916 via corresponding access links. In some examples, the DU 908 may include radio link control (RLC), media access control (MAC), and physical (PHY) layer functionality to enable operation as a scheduling entity.

[0179] Each of the IAB nodes 910 and 912 may be configured to include a layer-2 (L2) relay node including a corresponding DU 920 and a mobile terminal (MT) unit 918, such that each L2 relay IAB node 910 and 912 can operate as both a scheduling entity and a scheduled entity. For example, the MT unit 918 within each of the L2 relay IAB nodes 910 and 912 is configured to operate as a scheduled entity that can be scheduled by the IAB donor node 902. Each MT unit 918 within the L2 relay IAB nodes 910 and 912 may facilitate communication with the IAB donor node 902 via a corresponding backhaul link. Additionally, the DU 920 within each of the L2 relay IAB nodes 910 and 912 may operate similar to the DU 908 within the IAB donor node 902 to act as a scheduling entity to schedule one or more corresponding scheduled entities (e.g., other IAB nodes and / or UEs) of the L2 relay IAB nodes 910 and 912.

[0180] For example, the DU 920 of the L2 relay IAB node 912 can act as a scheduling entity to schedule communication with the UE 922 via the access link, while the DU 920 of the L2 relay IAB node 910 can act as a scheduling entity to schedule communication with the MT units 918 of the L2 relay IAB nodes 926 and 926 and with the UE 928 via the respective backhaul links and via the access link. Each of the L2 relay IAB nodes 924 and 926 can further include a respective DU 920, which can act as a scheduling entity to communicate with the respective UEs 930 and 932. Thus, in Figure 9 the network topology illustrated in, since the IAB donor node 902 can be configured to control each other node in the IAB network, the IAB donor node 902 is the parent IAB node of the sub-IAB nodes 910, 912, 924, and 926. Additionally, the IAB node 910 can further be the parent IAB node of the sub-IAB nodes 924 and 926. For example, the CU 906 and DU 908 within the IAB donor node 902 can act as the parent IAB node of the sub-IAB nodes 910, 912, 924, and 926, while the DU 920 within the IAB node 910 can act as the parent IAB node of the sub-IAB nodes 924 and 926. The MT units 918 within the IAB nodes 910, 912, 924, and 926 can further act as sub-IAB nodes.

[0181] In a mobile IAB network, one or more of the L2 relay IAB nodes 910, 912, 924, and / or 926 may be moving within the IAB network 900. For example, an L2 relay IAB node (e.g., the IAB node 924) can be a mobile IAB node installed on a bus, train, taxi, platoon vehicle, or other movable object.

[0182] In some examples, the IAB node can operate in an Evolved Universal Terrestrial Radio Access Network - New Radio Dual Connectivity (EN-DC) mode to simultaneously connect to an LTE network access node and an NR network access node to receive data packets from both the LTE network access node and the NR network access node.

[0183] As mentioned above, the functionality of the network access node and / or other components of the network can be distributed across multiple entities. Figure 10FIG. is a high - level illustration providing an example of a network configuration including an integrated access backhaul (IAB) network in accordance with some aspects of the present disclosure. In this illustration, a network entity (such as network access node 1002 (e.g., BS, eNB, gNB)) may be coupled to a remote network 1004 (such as a primary backhaul network or a mobile core network). In a wireless communication network 1000, the radio spectrum may be used for the fronthaul link 1006 between the network access node 1002 and the repeater device 1008 and for the access link 1010 between the repeater device 1008 and the UE 1012. As described in the examples herein, a repeater device (such as repeater device 1008) may also be referred to as a repeater, a repeater device, etc. The fronthaul link 1006 and the access link 1010 may each operate over the Uu radio interface or some other suitable wireless communication interface. In some examples, the radio spectrum may utilize millimeter - wave (mmWave) frequencies and / or sub - 6GHz carrier frequencies.

[0184] The wireless communication network 1000 may include other network access nodes, UEs, and repeater devices (not shown). The network access node 1002 and other network access nodes may correspond to Figure 1 、 2 any one of the network access nodes (e.g., scheduling entity, gNB, base station) shown in any of 5 - 12, 14 - 17, 25, 29, 31, 37, and / or 39 - 44. The repeater device 1008 and other repeater devices may correspond to any repeater device described herein, such as, by way of example Figures 7 - 21 any one of the repeater devices of 29, 31, 32, 37, 39, and / or 40. The UE 1012 and other UEs may be similar to Figure 1 、 2 any one of the UEs (e.g., scheduled entity, wireless communication device) shown in any of 5 - 12, 14 - 17, 29, 31, and / or 44.

[0185] In Figure 10In the example, the network access node 1002 (e.g., a network access node) may be referred to as a donor node because the network access node 1002 provides a communication link to the remote network 1004. The donor node may include a wired (e.g., fiber optic, coaxial cable, Ethernet, copper wire), microwave, or another suitable link to the remote network 1004. The donor node may broadcast (e.g., send, transmit, broadcast, unicast, multicast) a set of repeater device - specific control information (e.g., configuration, configuration settings, configuration information) (hereinafter referred to as "repeater device control information") in different angular directions corresponding to different repeater devices. The respective repeater devices arranged in the respective different angular directions relative to the donor node may receive the respective sets of repeater device control information broadcast in the respective different angular directions occupied by the respective repeater devices. According to some aspects, the donor node may broadcast a set of different respective repeater device control information (e.g., configuration, configuration settings, configuration information) in two or more different respective directions relative to the network access node.

[0186] The network access node 1002 may be an enhanced gNB that includes functionality for controlling the wireless communication network 1000. In some examples (as Figure 10 shown), the network access node 1002 may include a Central Unit (CU) 1014 and a Distributed Unit (DU) 1016. The CU 1014 may be configured to operate as a centralized network node (or central entity) within the wireless communication network 1000. For example, the CU 1014 may include Radio Resource Control (RRC) layer functionality and Packet Data Convergence Protocol (PDCP) layer functionality to control / configure other nodes (e.g., repeater devices and UEs) within the wireless communication network 1000. In some aspects, RRC signaling may be used for various functions, including, for example, establishing and releasing user data bearers. In some examples, RRC signaling messages may be transmitted on signaling bearers (e.g., SRB1 and SRB2).

[0187] The DU 1016 may be configured to operate as a scheduling entity to schedule the scheduled entities (e.g., repeater devices and / or UEs) of the network access node 1002. For example, the DU 1016 may operate as a scheduling entity to schedule the repeater device 1008 and the UE 1012. In some examples, the DU 1016 may include Radio Link Control (RLC), Media Access Control (MAC), and Physical (PHY) layer functionality to enable operation as a scheduling entity.

[0188] The F1 interface (not shown) provides a mechanism for interconnecting the CU 1014 (e.g., PDCP layer and higher layers) and the DU 1016 (e.g., RLC layer and lower layers). In some aspects, the F1 interface may provide control plane and user plane functions (e.g., interface management, system information management, UE context management, RRC message passing, etc.). F1AP is the application protocol for the F1 interface, which defines the signaling procedures for this F1 interface in some examples. The F1 interface supports F1-C on the control plane and F1-U on the user plane.

[0189] To facilitate wireless communication between the network access node 1002 and a UE (e.g., UE 1012) served by the network access node 1002, the repeater device 1008 may be configured to operate as a scheduled entity. The repeater device 1008 may include a Mobile Terminal (MT) unit 1018 to implement the scheduled entity functionality. For example, the MT unit 1018 may include UE functionality that is connected to and scheduled by the network access node 1002.

[0190] The repeater device 1008 may also include a Repeat Unit 1020 (RU) that relays signals between the network access node 1002 and the UE 1012. Repeat units (such as repeat unit 1020) may also be referred to as relay units, remote units, etc. The functionality of the repeat unit 1020 and other repeater device functionality will be described in more detail below in conjunction with Figures 2 - 21 Sections 29, 31, 32, 37, 39, and / or 40.

[0191] Figure 11 FIG. 12 is a diagram illustrating an example of a radio protocol architecture 1100 in the control plane according to some aspects of the present disclosure. The radio protocol architecture 1100 may be the radio protocol architecture of a 5G wireless system. The radio protocol stack may be implemented in a device operating in a 5G wireless network. Figure 11 FIG. 14 depicts the control plane protocol stacks of the network access node 1102, the repeater device 1114, and the UE 1130. The network access node 1102 may correspond to Figure 1 any of the network access nodes (e.g., scheduling entity, gNB, base station) shown in 2 Sections 5 - 12, 14 - 17, 25, 29, 31, 37, and / or 39 - 44. The UE 1130 may correspond to Figure 1 any of the UEs (e.g., scheduled entity, wireless communication device) shown in 2 Sections 5 - 12, 14 - 17, 29, 31, and / or 44. The repeater device 1114 may correspond to Figures 7 - 21any one of the RF repeater devices of 29, 31, 32, 37, 39, and / or 40. As Figure 11 As illustrated in Figure 11 , the radio protocol architecture 1100 includes three layers: layer 1 (L1), layer 2 (L2), and layer 3 (L3). L1 1142 is the lowest layer, L2 1144 is above L1 1142, and L3 1146 is above L2 1144.

[0192] Regarding the repeater device 1114, the implementation of the protocol stack can be divided between the repeater unit (RU) 1118 in L1 1142 and the mobile terminal (MT) 1116 in L2 1144 and L3 1146. In L1 1142, the PHY layer 1120 of the RU 1118 can operate as a relay, which relays the modulated RF analog signal (e.g., digital content on an analog carrier) in the uplink and downlink directions between the physical (PHY) layer 1104 of the network access node 1102 and the PHY layer 1132 of the UE 1130.

[0193] There are at least two types of relay procedures that can be used by the repeater device 1114 to relay traffic (e.g., user data signals and control signals) between the network access node 1102 and the UE 1130 through the repeater device 1114. The first relay procedure can be referred to as a layer 1 relay procedure, which can be implemented by a layer 1 relay. The second relay procedure can be referred to as a layer 2 relay procedure. The layers referred to are an indication of the layers of the protocol stack that are used to organize the data flow within and between devices. An example of a protocol stack can be a 5G protocol stack, which has a physical layer as its lowest layer, also known as layer 1.

[0194] According to the aspects described herein, the repeater device 1114 can be configured as a layer 1 relay that operates according to the layer 1 relay procedure. When operating as a layer 1 relay, the repeater device 1114 can receive a signal as a modulated RF waveform at a receiver coupled to a receive antenna array, amplify the signal, and retransmit the signal from a transmitter coupled to a transmit antenna array. Therefore, layer 1 relay can be referred to as amplify-and-forward relay. Generally, layer 1 relay may not require a large amount of upper layer functionality to perform the amplify-and-forward type of function, and may be less complex and less costly compared to layer 2 relay.

[0195] A repeater device, such as repeater device 1114, may be configured to operate as a layer 2 repeater. When operating as a layer 2 repeater, repeater device 1114 may receive, at a receiver coupled to a receive antenna array, a signal as a modulated RF waveform, demodulate and decode the signal to obtain a digital representation of the signal, re-encode and re-modulate the signal, amplify it, and then forward the signal from a transmitter coupled to a transmit antenna array. Thus, a layer 2 repeater may be referred to as a decode-and-forward type repeater. Generally speaking, a layer 2 repeater is more complex than a layer 1 repeater and may require a larger amount of upper layer functionality (compared to a layer 1 repeater) to perform decode-and-forward type operations. Therefore, a layer 2 repeater may be more complex and costly than a layer 1 repeater.

[0196] According to some aspects of the present disclosure, repeater device 1114 may be configured as and referred to as an intelligent repeater device. The intelligent repeater device may apply some upper layer functionality to a layer 1 repeater, but may not provide the level of functionality that would otherwise be required when operating as a layer 2 repeater. For example, while the intelligent repeater device may not use a higher level of functionality to demodulate, decode, encode, and re-modulate a signal, the intelligent repeater device may use that higher level of functionality in conjunction with various Synchronization Signal Block (SSB) information and Transmission Configuration Indicator (TCI) states to listen to a channel, implement MIMO functionality, select various beams, and may adjust the transmit power of the modulated RF waveform that is being amplified and forwarded by the repeater unit 1118 of the intelligent repeater device.

[0197] In the control plane, the various layers of each of network access node 1102, repeater device 1114, and UE 1130 are similar and will be described once to avoid repetition. These layers include the PHY layers 1104, 1120, 1132 at L1 layer 1142; the Medium Access Control (MAC) layers 1106, 1122, 1134, Radio Link Control (RLC) layers 1108, 1124, 1136, and Packet Data Convergence Protocol (PDCP) layers 1110, 1126, 1138 at L2 layer 1144; and the RRC layers 1112, 1128, 1140 at L3 layer 1146.

[0198] The PHY layers 1104, 1120, and 1132 may be responsible for transmitting and receiving data over a physical channel (e.g., within a time slot). The MAC SDU may be placed in the MAC PDU for transmission to the PHY layers 1104, 1120, and 1132 over a transport channel. The PHY context may indicate the transmission format and radio resource configuration (e.g., bandwidth part (BWP), numerology, etc.). The functions of the PHY layers 1104, 1120, and 1132 may include, for example, error detection on the transport channel and indication to a higher layer, forward error correction coding / decoding of the transport channel, hybrid automatic repeat request (HARQ) soft combining, rate matching of the coded transport channel to the physical channel, mapping of the coded transport channel onto the physical channel, power weighting of the physical channel, modulation and demodulation of the physical channel, frequency and time synchronization, radio characteristic measurement and indication to a higher layer, MIMO antenna processing, transmit diversity, digital and analog beamforming, and RF processing.

[0199] The MAC layers 1106, 1122, and 1134 may provide services to upper layers and obtain services from the PHY layers 1104, 1120, and 1132. The PHY layers 1104, 1120, and 1132 provide transport channels to the MAC layers 1106, 1122, and 1134 to support services for data delivery over a radio interface. The MAC layers 1106, 1122, and 1134 provide logical channels to the RLC layers 1108, 1124, and 1136. The logical channels exist between the MAC and PHY layers, while the transport channels exist between the PHY and radio layers. Thus, the MAC layers 1106, 1122, and 1134 may be an interface between higher layer logical channels and PHY layer transport channels. The functions of the MAC layers 1106, 1122, and 1134 may include, for example, beam management random access procedures, mapping between logical and transport channels, and concatenating multiple MAC SDUs belonging to one logical channel into a transport block (TB).

[0200] The RLC layers 1108, 1124, and 1136 may provide segmentation and reassembly of upper layer data packets, error correction via automatic repeat request (ARQ), and sequence numbering independent of the PDCP sequence numbering. The RLC context may indicate whether to use an acknowledged mode (e.g., using a reordering timer) or an unacknowledged mode for the RLC layers 1108, 1124, and 1136.

[0201] The PDCP layers 1110, 1126, 1138 can provide packet sequence numbers, in-order delivery of packets, retransmission of PDCP protocol data units (PDUs), and transfer of upper layer data packets to the lower layer. The PDUs can include, for example, Internet Protocol (IP) packets, Ethernet frames, and other unstructured data (i.e., machine type communication (MTC), hereinafter collectively referred to as "packets"). The PDCP layers 1110, 1126, 1138 can also provide header compression of upper layer data packets to reduce radio transmission overhead, provide security by encrypting the data packets, and integrity protection of the data packets. The PDCP context can indicate whether PDCP duplication is used, for example, for unicast connections.

[0202] The RRC layers 1112, 1128, 1140 of the L3 layer 1146 can be responsible for establishing and configuring signaling radio bearers (SRBs) and data radio bearers (DRBs) between the network access node 1102 and the UE 1130 and / or between the network access node 1102 and the repeater device 1114, paging initiated by the 5G core network (5GC) or the next generation RAN (NG-RAN), and broadcasting system information related to the access stratum (AS) and the non-access stratum (NAS). The RRC layers 1112, 1128, 1140 can further be responsible for QoS management, mobility management (e.g., handover, cell selection, inter-RAT mobility), UE 1130 measurement and reporting, and security functions.

[0203] In the user plane (not shown), the radio protocol architectures of the network access node 1102, the repeater device 1114, and the UE 1130 are substantially similar for the L1 layer 1142 and the L2 layer 1144 and will not be repeated to avoid duplication. The user plane protocol stack does not include the RRC layers 1112, 1128, 1140. The user plane protocol stack does include, for example, a service data adaptation protocol (SDAP) layer (not shown) in the L3 layer 1146. The SDAP layer (not shown) can provide a mapping between 5G core (5GC) quality of service (QoS) flows and data radio bearers and perform QoS flow ID marking in both downlink packets and uplink packets.

[0204] Figure 12 is a block diagram illustrating an example of a wireless communication network 1200 including a network access node 1202, a repeater device 1204, and a UE 1206 according to some aspects of the present disclosure. The network access node 1202 can correspond to Figure 1 , 2 , any of the network access nodes (e.g., scheduling entity, gNB, base station) shown in any of 5-12, 14-17, 25, 29, 31, 37, and / or 39-44. The repeater device 1204 can correspond toFigures 7 - 21 any one of the RF repeater devices of 29, 31, 32, 37, 39, and / or 40. The UE 1206 may correspond to Figure 1 , 2 any UE among the UEs (e.g., scheduled entities, wireless communication devices) shown in any one of 5-12, 14-17, 29, 31, and / or 44.

[0205] Compared with other types of radio waves used for communication (e.g., sub-6 GHz communication), millimeter-wave communication has a higher frequency and a shorter wavelength. Therefore, millimeter-wave communication may have a shorter propagation distance and may be more easily blocked by obstacles compared to other types of radio waves. For example, wireless communication using sub-6 GHz radio waves may be able to penetrate the walls of a building or structure to provide coverage to an area on the opposite side of the wall from a network access node that communicates using sub-6 GHz radio waves. However, millimeter waves may not be able to penetrate the same wall (e.g., depending on the thickness of the wall, the material that makes up the wall, etc.). Therefore, repeater devices can be used to increase the coverage area of a network access node, extend the coverage to UEs that do not have a line of sight to the network access node (e.g., due to obstacles), and so on.

[0206] For example, an obstacle between a UE and a network access node may block or otherwise degrade the quality of the link between the network access node and the UE. However, a repeater device can be placed such that there are no obstacles or fewer obstacles between the repeater device and the UE and between the repeater device and the network access node. Therefore, communication between the network access node and the UE via the repeater device can have a higher quality compared to direct communication between the network access node and the UE.

[0207] In some examples, a repeater device can perform directional communication by using beamforming to communicate with a network access node via a first beam pair (e.g., a downlink beam pair) and communicate with a UE via a second beam pair (e.g., an access link beam pair). The term "beam pair" can refer to a transmit (Tx) beam used by a first device for transmission and a receive (Rx) beam used by a second device to receive information transmitted by the first device via the Tx beam.

[0208] Refer to Figure 12 , the repeater device 1204 includes an MT unit 1208 and an RU 1210, as described above in connection with Figure 10 and 11As discussed, the MT unit 1208 can communicate with the network access node 1202 via the fronthaul link. In some examples, the fronthaul link can implement a reduced-functionality Uu interface, which can be modified to support repeater device functionality. The fronthaul link can provide a control path 1212 between the MT unit 1208 and the network access node 1202 (e.g., the DU in the network access node 1202, not shown). In some examples, the control path 1212 can carry UL and DL signals to configure the repeater device 1204. The control path 1212 can be implemented using a relatively small bandwidth portion (BWP) within the band, where these BWPs are allocated for UL transmission and / or DL transmission between the network access node 1202 and the UE 1206. In some examples, the fronthaul link can operate in the FR2 frequency range.

[0209] The RU 1210 can provide relay (e.g., receive, amplify, and transmit) functionality to enable signals from the network access node 1202 to reach the UE 1206 and / or enable signals from the UE 1206 to reach the network access node 1202. In some examples, the RU 1210 can be an analog through device (e.g., without store-and-forward capabilities). In other examples, the RU 1210 can include store-and-forward functionality. Signals to and from the network access node 1202 can be carried as data on the fronthaul link 1216 and the access link 1218. The access link 1218 provides a data path for carrying analog UL signals and DL signals to and from the UE 1206. In some examples, the access link 1218 can operate in the FR2 frequency range.

[0210] The RU 1210 and the access link 1218 can be controlled by the network access node 1202 (e.g., the DU in the network access node 1202, not shown). For example, the network access node 1202 can schedule UL transmissions and DL transmissions on the access link 1218 (e.g., by transmitting control information to the UE 1206). In addition, the network access node 1202 can control the operation of the RU 1210 through the MT unit 1208. For example, the network access node 1202 can configure the MT unit 1208 via the control path 1212 described above to cause the MT unit 1208 to configure the RU 1210. To this end, the MT unit 1208 can generate control signaling carried by the control signaling path 1214 for controlling the operation of the RU 1210.

[0211] Figure 13 is a schematic diagram illustrating example components of a repeater device 1300 in accordance with some aspects of the present disclosure. The repeater device 1300 can correspond to Figures 7 - 21any one of the repeater devices of 29, 31, 32, 37, 39, and / or 40. In some examples, the repeater device 1300 can be a millimeter-wave repeater device that communicates via millimeter-wave transmission (e.g., rather than sub-6 GHz transmission).

[0212] The repeater device 1300 can include a Repeater Unit (RU) 1302, one or more antenna arrays (or antennas, antenna panels, etc.) (such as a Receive (Rx) array 1304 and a Transmit (Tx) array 1306), and an MT unit 1308, as discussed herein. The RU 1302 can include an amplifier 1310 that is configured to amplify a signal received via the Rx array 1304 and transmit the amplified signal via the Tx array 1306. The MT unit 1308 can include a baseband processor 1312 that is configured to process signals received from a network access node (not shown) on the control path as described above, control the operation of the RU 1302 as needed (e.g., via control signaling on the control signaling path 1314), and transmit signals to the network access node via this control path.

[0213] The antenna array (e.g., the RX array 1304, the Rx array 1306) can include a plurality of antenna elements that can be configured for beamforming. The antenna array can be referred to as a phased array because the phase values and / or phase offsets of the antenna elements can be configured to form beams, where different phase values and / or phase shifts are used for different beams (e.g., in different directions). In some aspects, the antenna array can be a fixed Receive (RX) antenna array that is only capable of receiving communications and not transmitting communications. In some aspects, the antenna array can be a fixed Transmit (TX) antenna array that is only capable of transmitting communications and not receiving communications. In some aspects, the antenna array can be configured to act as an RX antenna array and / or a TX antenna array (e.g., via TX / RX switching, MUX / DEMUX, etc.). The antenna array can be capable of communicating using millimeter-wave and / or other types of RF analog signals.

[0214] The amplifier 1310 can include one or more components that are configured to amplify an input signal and output an amplified signal. For example, the amplifier 1310 can include a power amplifier, a variable gain component, etc. In some aspects, the amplifier 1310 can have variable gain control. In some examples, the amplification level of the amplifier 1310 can be controlled by the baseband processor 1312 (e.g., under the guidance of the network access node).

[0215] The baseband processor 1312 may include one or more components capable of controlling one or more other components of the repeater device 1300. For example, the baseband processor 1312 may include a controller, a microcontroller, a processor, etc. In some aspects, the baseband processor 1312 may control the amplification or gain level applied to the input signal by the amplifier 1310. Additionally or alternatively, the baseband processor 1312 may control the antenna array by: controlling the beamforming configuration for the antenna array (e.g., one or more phase values for the antenna array, one or more phase offsets for the antenna array, one or more power parameters for the antenna array, one or more beamforming parameters for the antenna array, TX beamforming configuration, RX beamforming configuration, etc.), controlling whether the antenna array acts as a receive antenna array or a transmit antenna array (e.g., by configuring the interaction and / or connection between the antenna array and the switch), etc. Additionally or alternatively, the baseband processor 1312 may power on / off one or more components of the repeater device 1300 (e.g., when the network access node does not need to use the repeater device to serve the UE). In some aspects, the baseband processor 1312 may control the timing of one or more of the above configurations.

[0216] The baseband processor 1312 may include components capable of communicating with the network access node via a control path. In some aspects, the baseband processor 1312 may communicate with the network access node using one or more in-band radio frequencies (e.g., radio frequencies included within the operating frequency bandwidth of the antenna array). In such a case, the network access node may configure a BWP (e.g., in-band BWP) within the operating frequency bandwidth of the antenna array such that the BWP carries a control interface associated with the repeater device 1300.

[0217] In some examples, the baseband processor 1312 may include one or more components for digital signal processing (e.g., digital signal processors, baseband processors, digital-to-analog converters (DACs), analog-to-digital converters (ADCs), etc.). In this way, the baseband processor 1312 may demodulate, decode, and / or perform other types of processing on the control information received from the network access node.

[0218] Switches 1316, 1318, 1320, and 1322 may each include one or more components that enable the repeater device 1300 to relay signals received via the receive antenna array or transmit RF analog signals generated by the repeater device 1300 (e.g., generated by the MT unit 1308). For example, in one configuration, switches 1316, 1318, 1320, and 1322 may be configured to couple the RU 1302 to the receive array 1304 and the transmit array 1306. In another configuration, switches 1316, 1318, 1320, and 1322 may be configured to couple the MT unit 1308 to the receive array 1304 and the transmit array 1306. In some examples, the position of each of switches 1316, 1318, 1320, and 1322 may be controlled by the MT unit 1308.

[0219] The adder 1324 (e.g., multiplexer) may include functionality to combine the signal from the amplifier 1310 with the signal from the MT unit 1308. For example, signals for the data path may be provided on the frequency band of the BWP allocated for data transmission, while signals for the control path may be provided on the frequency band of the BWP allocated for control transmission. In some examples, a demultiplexer 1328 (e.g., to demultiplex the control path from the incoming signal) may be used.

[0220] Figure 14 is a signaling diagram illustrating an example of repeater device signaling 1400 in accordance with some aspects of the present disclosure. In some examples, the network access node 1402 may correspond to Figure 1 , 2 , any one of the network access nodes (e.g., scheduling entity, gNB, base station) shown in any of 5 - 12, 14 - 17, 25, 29, 31, 37, and / or 39 - 44. In some examples, the repeater device 1404 may correspond to Figures 7 - 21 , any one of the RF repeater devices of 29, 31, 32, 37, 39, and / or 40. In some examples, the UE 1406 may correspond to Figure 1 , 2 , any one of the UEs (e.g., scheduled entity, wireless communication device) shown in any of 5 - 12, 14 - 17, 29, 31, and / or 44.

[0221] In 1408, the network access node 1402 and the repeater device 1404 may perform an initial access procedure and establish an RRC connection. This communication may use a specified (e.g., configurable) BWP on the Uu link as discussed above. The initial BWP may be used as the default. In some examples, the Uu link may use a single component carrier (CC). The MT unit of the repeater device 1404 may perform procedures similar to those of a UE (e.g., access, radio link management (RLM), and beam management (BM)). These procedures may be simplified and / or modified versions of RF and radio resource management (RRM) procedures known to those skilled in the art.

[0222] The network access node 1402 and the repeater device 1404 may identify the beams they will use to communicate with each other. Additionally, in some examples, the network access node 1402 and the repeater device 1404 may exchange configuration information, capability information, and other information.

[0223] In 1410, the network access node 1402 and the repeater device 1404 may perform a RU integration procedure. For example, the network access node 1402 may learn the capabilities of the RU (not shown) of the repeater device 1404. Here, the repeater device 1404 (e.g., the MT (not shown) of the repeater device 1404) may identify itself as a repeater device and share its functionality. The shared information may include, for example, beam-related information and the latency required to implement the configuration.

[0224] In 1412, the network access node 1402 and the repeater device 1404 may perform radio link management and radio resource management procedures. For example, the network access node 1402 may specify beam information and allocate resources.

[0225] In 1414, the network access node 1402 and the repeater device 1404 may perform RU configuration procedures. Here, the network access node 1402 may send control messages to configure the operation of the RU. For example, the network access node 1402 may send configuration information for the RU of the repeater device 1404 to the MT of the repeater device 1404. Thus, in some examples, the RU configuration procedure may control the operation of the first RU 1404a for DL traffic (as indicated by line 1416) and control the operation of the second RU 1404b for UL traffic (as indicated by line 1418). The configuration may include, for example, beamforming configuration and TDD configuration (e.g., Rx&Tx (forward) beamforming) and / or time-domain resource allocation (e.g., resources used to adopt the indicated configuration). A RU-specific DCI format (scrambled by the RU-RNTI) may be defined to provide the required configuration. In addition to dynamic configuration (e.g., default mode), semi-persistent configuration and periodic configuration may also be supported. Configuration via MAC-CE or RRC (e.g., for semi-persistent / periodic mode) may also be supported.

[0226] In 1420, the network access node 1402 may transmit DL traffic for the UE 1406 and DL traffic for the MT (of the repeater device 1404) to the repeater device 1404. Subsequently, in 1422, the first RU 1404a may forward (e.g., relay) the DL traffic for the UE 1406 to the UE 1406. Here, the repeater device 1404 may demultiplex the DL traffic for the MT from the DL traffic from the network access node 1402. The DL traffic for the MT may or may not be multiplexed with the DL traffic for the UE 1406 on the same resources.

[0227] In 1424, the UE 1406 may transmit UL traffic to the repeater device 1404. In 1426, the second RU 1404b may forward (e.g., relay) the UL traffic from the UE 1406 together with the UL traffic from the MT (of the repeater device 1404) to the network access node 1402. Here, the repeater device 1404 may multiplex the UL traffic from the MT with the UL traffic transmitted to the network access node 1402. The UL traffic from the MT may or may not be multiplexed with the UL traffic from the UE 1406 on the same resources. The repeater device 1404 may relay signals to and from multiple UEs (e.g., including the UE 1406 and other UEs (not shown)).

[0228] Figure 15Schematic diagram of an example of a signaling path in a wireless communication network 1500 between a network access node 1502, a repeater device 1504, a first UE 1506, and a second UE 1508 according to some aspects of the present disclosure. In some examples, the network access node 1502 may correspond to Figure 1 , 2 , any one of the network access nodes (e.g., scheduling entity, gNB, base station) shown in 5-12, 14-17, 25, 29, 31, 37, and / or 39-44. In some examples, the repeater device 1504 may correspond to Figures 7 - 21 , any one of the RF repeater devices of 29, 31, 32, 37, 39, and / or 40. In some examples, the first UE 1506 and the second UE 1508 may correspond to Figure 1 , 2 , any one of the UEs (e.g., scheduled entity, wireless communication device) shown in 5-12, 14-17, 29, 31, and / or 44.

[0229] In Figure 15 's example, the repeater device 1504 has established a first beam pair 1510 (B1) to the first UE 1506 and a second beam pair 1512 (B2) to the second UE 1508. The network access node 1502 and the repeater device 1504 (e.g., the MT unit of the repeater device) may communicate via an in-band control path 1514 as discussed herein. Data transmitted to and / or received from the first UE 1506 via the first beam pair 1510 and data transmitted to and / or received from the second UE 1508 via the second beam pair 1512 may be sent on the data path 1516. In some examples, the data may be sent as analog RF communication in the FR2 spectrum.

[0230] Figure 16 Schematic example of the propagation of control and data associated with a DL transmission from a network access node to a UE via a repeater device according to some aspects of the present disclosure. According to some aspects of the present disclosure, similar timing may apply to UL transmissions from a UE to a network access node via a repeater device. In some examples, the network access node 802 may correspond to Figure 1 , 2 , any one of the network access nodes (e.g., scheduling entity, gNB, base station) shown in 5-12, 14-17, 25, 29, 31, 37, and / or 39-44. In some examples, the repeater device may correspond to Figures 7 - 21Any one of the RF repeater devices of 29, 31, 32, 37, 39, and / or 40. In some examples, the UE may correspond to Figure 1 , 2 Any UE among the UEs (e.g., scheduled entities, wireless communication devices) shown in any one of 5 - 12, 14 - 17, 29, 31, and / or 44.

[0231] The network access node may transmit repeater device control information (R control) 1602, which may be received by the repeater device after a period of time (as indicated by R control 1604). The objects associated with the network access node, the repeater device, and the UE may be laterally shifted to the right along the time axis due to propagation delay (e.g., the time it takes for an RF signal to propagate through the air medium from its source to its destination). As discussed herein, this repeater device control information may configure the repeater device for an upcoming DL transmission to the UE.

[0232] After waiting for a time period N equal to or greater than the amount of time it takes for the repeater device to process the repeater device control information (e.g., to configure the DLRU of the repeater device) R the network access node may transmit UE control information (UE control) 1608. This UE control information may be received by the repeater device after a period of time (as indicated by UE control 1610). The repeater device may forward the UE control information to the UE and the information may be received at the UE after a period of time (as indicated by UE control 1612).

[0233] Subsequently, the network access node may transmit UE data 1614, which is received by the repeater device after a period of time (as indicated by UE data 1610). Subsequently, the repeater device may forward the UE data to the UE and the UE data may be received at the UE after a period of time (as indicated by UE data 1618).

[0234] The channels, carriers, traffic, control, and protocol layers described above and illustrated in Figures 1 - 16 are not necessarily all the channels, carriers, traffic, control, and protocol layers that may be utilized between the network access node, the repeater device, and the UE, and one of ordinary skill in the art will recognize other channels, carriers, traffic, control, and protocol layers, as well as other aspects as described and illustrated above, that may be utilized as supplements to those described and illustrated above (such as other traffic, control, and feedback channels).

[0235] Figure 17FIG. is a block diagram illustrating an exemplary coupling between various nodes of a wireless communication network including a repeater device 1702 in accordance with some aspects of the present disclosure. As depicted, the repeater device 1702 can be used to repeat signals between different types of devices in different examples. These devices include, but are not limited to, network access nodes, integrated access and backhaul devices, other repeater devices, user equipment, and general wireless devices. A network access node 1701 (identified as BS1 in Figure 17 and a repeater device 1702 (identified as R in Figure 17 ) are presented in three configurations. The repeater device 1702 can be a smart repeater device as described herein. The repeater device 1702 can correspond to any of the RF repeater devices of Figures 7 - 21 , 29, 31, 32, 37, 39, and / or 40.

[0236] The network access node 1701 can correspond to any of the network access nodes (e.g., scheduling entity, gNB, base station) shown in any of Figure 1 , 2 , 5 - 12, 14 - 17, 25, 29, 31, 37, and / or 39 - 44.

[0237] In a first configuration 1700, the repeater device 1702 can be controlled by the network access node 1701. The repeater device 1702 can receive control signaling including control information associated with traffic relayed by the repeater device 1702 between the network access node 1701 (BS1) and the user equipment 1703 (UE 1). In the first configuration 1700, the network access node 1701 can be considered the first wireless communication device (WD1) and the user equipment 1703 can be considered the second wireless communication device (WD2). As used herein, the term "wireless communication device" generally can refer to a network access node, an integrated access and backhaul device, a repeater device, user equipment, an IoT device, a V2X device, or generally any device that communicates with another device using the wireless spectrum.

[0238] In the second configuration 1720, the repeater device 1702 may be controlled by the network access node 1701 (BS1). The repeater device 1702 may receive control signaling including control information associated with traffic relayed by the repeater device 1702 between the first wireless communication device 1704 (WD1) and the second wireless communication device 1705 (WD2) from the network access node 1701. In the second configuration 1720, the first wireless communication device 1704 may be a device other than a network access node (e.g., the network access node 1701), and the second wireless communication device 1705 (WD2) may be a device other than, for example, a UE (e.g., the user equipment 1703). In the second configuration, traffic (including user signaling and control signaling) may be relayed between the first wireless communication device 1704 and the second wireless communication device 1705 by the repeater device 1702. The network access node 1701 and the repeater device 1702 may exchange control information on the control signaling. The traffic between the first wireless communication device 1704 and the second wireless communication device 1705 may or may not be relayed (copied, dual-cast, multi-cast) to the network access node 1701.

[0239] In the third configuration 1730, the repeater device 1702 may be controlled by the network access node 1701 (BS1). The network access node 1701 may or may not be the first wireless communication device 1704 (WD1). For ease of reference, an alternative identification / location of the network access node 1701 is shown in dashed lines. The repeater device 1702 may receive control signaling including control information associated with traffic relayed by the repeater device 1702 between the first wireless communication device 1704 and the second wireless communication device 1705 from the network access node 1701. In the third configuration 1730, the first wireless communication device 1704 may be represented as at least one or more of the following: the network access node 1701, one or more wireless communication devices 1706, one or more network access nodes 1708, 1710, one or more integrated access and backhaul (IAB) nodes 1712, 1714, or one or more repeater devices 1716, 1718. The second wireless communication device 1705 may be represented as at least one or more of the following: one or more UEs 1703, one or more wireless communication devices 1707, one or more network access nodes 1709, 1711, one or more IAB nodes 1713, 1715, or one or more repeater devices 1717, 1719.

[0240] Beam information for a wireless communication repeater device

[0241] Aspects described herein may relate to exchanging beam-related information between a network access node and a repeater device. In some examples, beam information may not initially be communicated between the network access node and the repeater device (e.g., to simplify repeater device-related operations and / or reduce repeater device-related signaling). In some examples, the repeater device may send beam information to the network access node (e.g., to enable the network access node to better configure the repeater device). In some examples, the network access node may determine (e.g., estimate) beam information related to the repeater device (e.g., by monitoring signals associated with communication between the network access node and a UE via the repeater device).

[0242] According to some aspects, the network access node may select the number of synchronization signal blocks (SSBs) that the repeater device may transmit before receiving an indication from the repeater device as to how many beams the repeater device can support (e.g., transmit) (e.g., without first receiving such an indication). By not requiring the repeater device to indicate how many beams it can support, less signaling may be required between the network access node and the repeater device. Additionally, the network access node and the repeater device may not need to perform operations associated with transmitting and receiving specific signaling (since an RRC connection may not be established). As a result, power savings may be achieved at the network access node and the repeater device, and overall system throughput may be increased.

[0243] Figure 18 is a schematic diagram of a MIMO repeater device 1800 according to some aspects of the present disclosure. The MIMO repeater device 1800 may have a single input or multiple inputs. Input signals from one or more subarrays 1801 (e.g., a set of subarrays) selected by a set of switches 1802 may be combined (e.g., by an adder or a multiplexer 1804), amplified (e.g., by an amplifier 1806), and then divided (e.g., by a demultiplexer 1808) for transmission via a single output or multiple outputs (e.g., via the set of subarrays 1801) selected by the set of switches 1802. The MIMO repeater device 1800 may correspond to Figures 7 - 21 any one of the RF repeater devices of

[0244] Figure 19 is a schematic diagram of a two-way MIMO repeater device 1900 according to some aspects of the present disclosure. The two-way MIMO repeater device 1900 includes components that may be similar to Figure 18Two repeater device circuits of the MIMO repeater device 1800 (referred to as the first switch 1902 and the second switch 1904) (e.g., independent RF chains). The bi-directional MIMO repeater device 1900 may have a plurality of input terminals in a first direction, where input signals are combined, amplified, and then divided for transmission via a plurality of output terminals (e.g., as discussed above in connection with Figure 18 ). The bi-directional MIMO repeater device 1900 may have a plurality of input terminals in a second direction, where input signals are combined, amplified, and then divided for transmission via a plurality of output terminals (e.g., as discussed above in connection with Figure 18 ).

[0245] In the above example, different input and / or output devices may be employed by configuring corresponding sub-arrays 1901 of one or more antenna arrays. In some examples, the first switch 1902 may be used to configure a particular set of sub-arrays for transmission and the second switch 1904 may be used to configure a particular set of sub-arrays for reception. By sending connectivity information of the array to a network access node, the network access node may be able to configure the array for transmission and / or reception (e.g., configure the RU via the MT). The bi-directional MIMO repeater device 1900 may correspond to Figures 7 - 21 any one of the RF repeater devices of 29, 31, 32, 37, 39, and / or 40.

[0246] Figure 20 is a schematic diagram of a single-input single-output (SISO) repeater device 2000 according to some aspects of the present disclosure. The SISO repeater device 2000 may have a single input terminal (e.g., a first port), which is amplified by an amplifier 2002 and then transmitted via a single output terminal (e.g., a second port). In other examples, the SISO repeater device 2000 may have a plurality of input terminals and a plurality of output terminals (e.g., where only one input terminal / output terminal pair can be selected at any given time). In Figure 20 example, a single input terminal and a single output terminal are coupled to a plurality of antenna arrays. In Figure 20 example, some arrays (FH arrays) 2010, 2013, 2015, 2016 may be designated for backhaul link communication, while other arrays (AL arrays) 2011, 2012, 2014, 2017 may be designated for access link communication. In Figure 20In the example, multiple antenna arrays can be divided into four backhaul link arrays (FH arrays) 2010, 2013, 2015, 2016 and four access link arrays (AL arrays) 2011, 2012, 2014, 2017; however, for illustration rather than limitation, the number of antenna arrays and the ratio between the FH arrays and the AL arrays are provided. A single input terminal can be fed from a first switch 2004 coupled between an amplifier 2002 and the multiple antenna arrays 2010 - 2017 (e.g., in Figure 20 's example, the first switch 2004 can be a single-pole eight-throw switch). A single output terminal can feed a second switch 2006 coupled between the amplifier 2002 and the multiple antenna arrays 2010 - 2017 (e.g., in Figure 20 's example, the second switch 2006 can be a single-pole eight-throw switch). The first switch 2004 and the second switch 2006 can be multiplexer / demultiplexer circuits or other distribution circuits known to those skilled in the art, or be replaced by them. Here, different array pairs can be selected at a given time for communication on the backhaul link and communication on the access link. In Figure 20 's example, the output terminal of the first FH array 2016 is selected by the first switch 2004, amplified by the amplifier 2002, and output to the second AL array 2012 via the second switch 2006. The illustrated configuration is exemplary rather than restrictive. The SISO repeater device 2000 can correspond to Figures 7 - 21 any one of the RF repeater devices of

[0247] Figure 21 is a schematic diagram illustrating an example of a hardware implementation of a repeater device 2100 employing a processing system 2114 according to some aspects of the present disclosure. For example, the repeater device 2100 can be a device configured to wirelessly communicate with a network access node (e.g., a scheduling entity, a gNB, a base station), a user equipment (e.g., a UE, a scheduled entity, a wireless communication device), and / or a core network node, all as Figures 1 - 55 discussed in any one or more of Figures 1 - 55 's repeater devices or scheduled entities.

[0248] In accordance with various aspects of the present disclosure, an element, or any portion of an element, or any combination of elements can be implemented using processing system 2114. Processing system 2114 can include one or more processors 2104. Examples of processors 2104 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout the present disclosure. In various examples, repeater device 2100 can be configured to perform any one or more of the functions described herein. That is, the processor 2100 utilized in repeater device 2104 can be used to implement any one or more of the processes and procedures described herein (e.g., in Figures 22 - 24 , 33 - 34 and / or 46 - 47).

[0249] In some instances, processor 2104 can be implemented via a baseband or modem chip, while in other implementations, processor 2104 can include several devices different and distinct from the baseband or modem chip (e.g., devices that can work together in such scenarios to achieve the embodiments discussed herein). And as mentioned above, various hardware arrangements and components outside of the baseband modem processor can be used in implementations, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.

[0250] In this example, processing system 2114 can be implemented using a bus architecture generally represented by bus 2102. Depending on the specific application and overall design constraints of processing system 2114, bus 2102 can include any number of interconnecting buses and bridges. Bus 2102 communicatively couples various circuits including one or more processors (generally represented by processor 2104), memory 2105, and computer - readable medium (generally represented by computer - readable medium 2106). Bus 2102 can also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and thus will not be described further.

[0251] The bus interface 2108 can provide an interface between the bus 2102 and the transceiver 2110 (e.g., which can be alternatively implemented as an RU), and between the bus 2102 and the interface 2130. If implemented as an RU, the transceiver 2110 can represent transmit functionality and / or receive functionality. The transceiver 2110 can be further coupled to one or more antennas / antenna arrays 2120. The transceiver 2110 in combination with one or more antennas / antenna arrays 2120 can provide a communication interface or means for communicating with various other devices over a wireless transmission medium. In some examples, the repeater device 2100 can include two or more transceivers 2110 each configured to communicate with a respective network type (e.g., terrestrial or non-terrestrial). The interface 2130 can provide a communication interface or means for communicating with various other devices and equipment (e.g., other devices housed within the same equipment as the repeater device 2100 or other external devices) over an internal bus or an external transmission medium such as an Ethernet cable. Depending on the characteristics of the equipment, the interface 2130 can include a user interface (e.g., keypad, display, speaker, microphone, joystick, control features, etc.). Of course, such a user interface is optional and can be omitted in some examples such as IoT devices. Additionally, the bus interface 2108 can further provide an interface between the bus 2102 and the power supply 2128.

[0252] The processor 2104 is responsible for managing the bus 2102 and general processing, including the execution of software stored on the computer-readable medium 2106. The software, when executed by the processor 2104, causes the processing system 2114 to perform the various functions described below for any particular equipment. The computer-readable medium 2106 and / or the memory 2105 can also be used to store data manipulated by the processor 2104 when executing the software.

[0253] One or more processors 2104 in the processing system 2114 can execute the software. The software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, execution threads, procedures, functions, etc., regardless of whether it is referred to in terms of software, firmware, middleware, microcode, hardware description language, or other terms. The software can reside on the computer-readable medium 2106.

[0254] The computer-readable medium 2106 can be a non-transitory computer-readable medium. By way of example, non-transitory computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic tape), optical disks (e.g., compact disc (CD) or digital versatile disc (DVD)), smart cards, flash memory devices (e.g., cards, sticks, or key drives), random access memory (RAM), read only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. The computer-readable medium 2106 can reside within the processing system 2114, outside the processing system 2114, or be distributed across multiple entities including the processing system 2114. The computer-readable medium 2106 can be embodied in a computer program product or article. By way of example, a computer program product or article can include the computer-readable medium in a packaging material. In some examples, the computer-readable medium 2106 can be a part of the memory 2105. Those skilled in the art will recognize how best to implement the described functionality presented throughout this disclosure depending on the particular application and the overall design constraints imposed on the overall system.

[0255] The repeater device 2100 can be configured to perform any one or more of the operations described herein (e.g., as described in connection with Figures 22 - 24 , 33 - 34, and / or 46 - 47). In some aspects of the present disclosure, the processor 2104 as utilized in the repeater device 2100 can include circuitry configured for various functions.

[0256] For example, the processor 2104 may include communication and processing circuitry 2141. The communication and processing circuitry 2141 may be configured for various functions, including, for example, communicating with network access nodes (e.g., scheduling entities, gNBs, base stations), user equipment (e.g., UEs, scheduled entities, wireless communication devices), core network nodes (e.g., 5G core network nodes), and / or any other entities (such as, for example, local infrastructure or entities communicating with the repeater device 2100 via the Internet (such as network providers)). The communication and processing circuitry 2141 may include one or more hardware components providing physical structures for performing various processes related to wireless communication (e.g., signal reception and / or signal transmission) as described herein. The communication and processing circuitry 2141 may further include one or more hardware components providing physical structures for performing various processes related to signal processing (e.g., processing received signals and / or processing signals for transmission) as described herein. In some examples, the communication and processing circuitry 2141 may be configured to relay uplink traffic and uplink control messages (e.g., similar to Figure 1 the uplink traffic 116 and uplink control 118) and relay downlink traffic and downlink control messages (e.g., similar to downlink traffic 112 and downlink control 114) via the antenna / antenna array 2120 and transceiver 2110. In some examples, the communication and processing circuitry 2141 may include two or more transmit chains / receive chains. Each of the two or more transmit chains / receive chains may be configured to process signals of different RAT (or RAN) types. The communication and processing circuitry 2141 may further be configured to execute communication and processing software 2151 stored on the computer-readable medium 2106 to implement one or more functions described herein.

[0257] In some examples, the communication and processing circuitry 2141 may be configured to receive and process downlink beamformed signals at millimeter wave frequencies or sub-6 GHz frequencies via the transceiver 2110 and antenna array 2120. For example, the communication and processing circuitry 2141 may be configured to receive corresponding reference signals (e.g., SSB or CSI-RS) from a network access node on each of a plurality of downlink beams via at least one first antenna panel of the antenna array 2120 during downlink beam sweeping. The communication and processing circuitry 2141 may further be configured to transmit beam measurement reports to the network access node.

[0258] In some examples, the communication and processing circuitry 2141 may further be configured to generate and transmit an uplink beamformed signal at millimeter wave frequencies or sub-6 GHz frequencies via the transceiver 2110 and the antenna array 2120. For example, the communication and processing circuitry 2141 may be configured to transmit a respective reference signal (e.g., SRS or DMRS) on each of a plurality of uplink beams via at least one second antenna panel of the antenna array 2120 during an uplink beam sweep to a network access node.

[0259] The communication and processing circuitry 2141 may further be configured to control the antenna array 2120 and the transceiver 2110 to search for and identify a plurality of downlink transmit beams during a downlink beam sweep. The communication and processing circuitry 2141 may further be configured to obtain a plurality of beam measurements on each of a plurality of downlink receive beams for each of the identified downlink transmit beams via the antenna array 2120. The communication and processing circuitry 2141 may further be configured to use the communication and processing circuitry 2141 to generate a beam measurement report for transmission to a network access node.

[0260] The communication and processing circuitry 2141 may further be configured to identify one or more selected uplink beams based on beam measurements obtained from downlink beam reference signals. In some examples, the communication and processing circuitry 2141 may be configured to, for each of the serving downlink transmit beams, compare the respective RSRP (or other beam measurement) measured on each of the downlink receive beams to identify the serving downlink receive beam, and further use the serving downlink receive beam as the selected uplink transmit beam. Each serving downlink receive beam may have the highest measured RSRP (or other beam measurement) for one of the downlink transmit beams.

[0261] The communication and processing circuitry 2141 may be configured to generate one or more uplink transmit beams for transmission during an uplink beam sweep. Each uplink transmit beam may carry an uplink reference signal (e.g., SRS) for measurement by a network access node. The communication and processing circuitry 2141 may further be configured to identify the selected uplink transmit beam(s) selected by the network access node based on uplink beam measurements. For example, the communication and processing circuitry 2141 may be configured to receive an indication of the selected uplink transmit beam(s) from the network access node.

[0262] In some examples, the communication and processing circuitry 2141 may be configured to generate a scheduling request and transmit it (e.g., via UCI in the PUCCH) to a network access node to receive an uplink grant for the PUSCH. The communication and processing circuitry 2141 may further be configured to generate an uplink signal and interact with the transceiver 2110 to transmit the uplink signal. The uplink signal may include, for example, PUCCH, PUSCH, SRS, DMRS, or PRACH. The communication and processing circuitry 2141 may further be configured to interact with the transceiver 2110 to monitor and decode downlink signals. The downlink signals may include, for example, PDCCH, PDSCH, CSI-RS, or DMRS.

[0263] In some implementations in which communication involves receiving information, the communication and processing circuitry 2141 may obtain information from a component of the repeater device 2100 (e.g., from the transceiver 2110 that receives information via radio frequency signaling or some other type of signaling adapted to the applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, the communication and processing circuitry 2141 may output the information to another component of the processor 2104, to the memory 2105, or to the bus interface 2108. The information may include, for example, beam information 2115 that may be stored in the memory 2105. In some examples, the communication and processing circuitry 2141 may receive one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 2141 may receive information via one or more channels. In some examples, the communication and processing circuitry 2141 may include the functionality of means for receiving.

[0264] In some implementations in which communication involves sending (e.g., transmitting) information, the communication and processing circuitry 2141 may obtain information from (e.g., from another component of the processor 2104, the memory 2105, or the bus interface 2108), process (e.g., encode) the information, and output the processed information. For example, the communication and processing circuitry 2141 may output the information to the transceiver 2110 (e.g., to transmit the information via radio frequency signaling or some other type of signaling adapted to the applicable communication medium). In some examples, the communication and processing circuitry 2141 may send one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 2141 may send information via one or more channels. In some examples, the communication and processing circuitry 2141 may include the functionality of means for sending (e.g., means for transmitting).

[0265] The processor 2104 may include beam configuration circuitry 2142 configured to perform operations related to beam configuration as discussed herein. The beam configuration circuitry 2142 may further be configured to provide functionality for a device to receive a configuration. The beam configuration circuitry 2142 may further be configured to provide functionality for a device to select a number of beams to use. The beam configuration circuitry 2142 may further be configured to provide functionality for a device to determine a number of antenna arrays. The beam configuration circuitry 2142 may further be configured to provide functionality for a device to determine a mapping. The beam configuration circuitry 2142 may further be configured to provide functionality for a device to transmit a mapping. The beam configuration circuitry 2142 may further be configured to provide functionality for a device to generate an indication. The beam configuration circuitry 2142 may further be configured to provide functionality for a device to transmit an indication. The beam configuration circuitry 2142 may further be configured to execute beam configuration software 2152 included on a computer-readable medium 2106 to implement one or more functions described herein.

[0266] The processor 2104 may include beam processing circuitry 2143 configured to perform operations related to beam processing as discussed herein. The beam processing circuitry 2143 may further be configured to provide functionality for a device to receive an SSB transmission. The beam processing circuitry 2143 may further be configured to provide functionality for a device to transmit an SSB transmission. The beam processing circuitry 2143 may further be configured to execute beam processing software 2153 included on a computer-readable medium 2106 to implement one or more functions described herein.

[0267] Figure 22 is a flow chart illustrating an example process 2200 (e.g., method) at a repeater device for communicating beam information in a wireless communication network in accordance with some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some of the illustrated features may not be required to implement all embodiments. In some examples, process 2200 may be performed by Figure 21 the repeater device 2100 illustrated in. In some examples, process 2200 may be performed by any suitable apparatus or device for performing the functions or algorithms described below.

[0268] At block 2202, the repeater device may receive a first configuration specifying a first number of synchronization signal blocks (SSBs) to be transmitted by the repeater device. For example, as described above in connection with Figure 21The beam configuration circuitry 2142 shown and described, together with the communication and processing circuitry 2141 and the transceiver 2110, can receive SSB configurations from the gNB and can provide means for receiving a first configuration for receiving a first number of synchronization signal blocks (SSBs) specified to be transmitted by the repeater device.

[0269] In some examples, the first configuration can include SSB indices. In some examples, these SSB indices can be mapped to resources to be used by the repeater device for SSB transmission. In some examples, these SSB indices can be mapped to beam information to be used by the repeater device for subsequent transmissions. In some examples, the beam information can include spatial quasi-co-location information for the first number of SSBs.

[0270] At block 2204, the repeater device can select to use a second number of beams to transmit the SSBs, where the second number of beams can be less than or equal to the first number of SSBs. For example, as described above in connection with Figure 21 the beam configuration circuitry 2142 shown and described can determine that it cannot support K SSBs. According to another example, as described above in connection with Figure 21 the beam configuration circuitry 2142 shown and described can provide means for selecting to use a second number of beams to transmit the SSBs, where the second number of beams can be less than or equal to the first number of SSBs.

[0271] In some examples, selecting to use a second number of beams to transmit the SSBs can include determining the second number of beams based on how many beams the repeater device can generate. In some examples, selecting to use a second number of beams to transmit the SSBs can include identifying the beams that can be used by the repeater device to relay the SSBs; and determining the second number of beams based on the beams that can be used by the repeater device to relay the SSBs. In some examples, selecting to use a second number of beams to transmit the SSBs can include identifying the beams that have been successfully used by the repeater device to communicate with at least one user equipment; and determining the second number of beams based on the beams that have been successfully used by the repeater device to communicate with the at least one user equipment.

[0272] At block 2206, the wireless communication device can receive at least one SSB transmission. For example, as described above in connection with Figure 21 the beam processing circuitry 2142 shown and described, together with the communication and processing circuitry 2143 and the transceiver (e.g., RU) 2110, can receive the SSBs on the fronthaul link. Additionally, as described above in connection with Figure 21 the beam processing circuitry 2143 shown and described, together with the communication and processing circuitry 2141 and the transceiver (e.g., RU) 2110, can provide means for receiving at least one SSB transmission.

[0273] At block 2208, the repeater device may transmit the at least one SSB transmission via a second number of beams. The repeater device may transmit the at least one SSB transmission via a repeater unit (RU) of the repeater device. For example, the beam processing circuitry 2143, as shown and described above in conjunction with Figure 21 the communication and processing circuitry 2141 and the transceiver 2110 may forward an SSB on an access link or generate an SSB and transmit the SSB on the access link. Additionally, the beam processing circuitry 2143, as shown and described above in conjunction with Figure 21 the communication and processing circuitry 2141 and the transceiver 2110 may provide means for transmitting the at least one SSB transmission via a second number of beams.

[0274] In some examples, the at least one SSB transmission may include multiple SSB transmissions, and transmitting the at least one SSB transmission may include sequentially relaying the multiple SSB transmissions via a second number of beams. In some examples, the at least one SSB transmission may include SSB information, and transmitting the at least one SSB transmission may include generating multiple SSB transmissions from the SSB information and transmitting the multiple SSB transmissions via a second number of beams.

[0275] In some examples, process 2200 may further include generating an indication that the repeater device will use a second number of beams to transmit an SSB and transmitting the indication to a network access node. In some examples, process 2200 may further include receiving a second configuration after transmitting the indication, where the second configuration specifies a second number of SSBs to be used by the repeater device.

[0276] Figure 23 is a flow diagram of an example process 2300 (e.g., method) at a repeater device for communicating beam information in a wireless communication network in accordance with some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some of the illustrated features may not be required to implement all embodiments. In some examples, process 2300 may be performed by Figure 21 the repeater device 2100 illustrated in

[0277] At block 2302, the repeater device may determine the number of antenna arrays of the repeater device. For example, the beam configuration circuitry 2142, as shown and described above in conjunction with Figure 21 the communication and processing circuitry 2141 and the transceiver 2110 may access the capability information for the repeater device. Additionally, the beam configuration circuitry 2142, as shown and described above in conjunction with Figure 21The beam configuration circuitry 2142 shown and described can provide means for determining the number of antenna arrays of the repeater device.

[0278] At block 2304, the repeater device can determine a mapping of beam indices to array indices of these antenna arrays. For example, as described above in connection with Figure 21 the beam configuration circuitry 2142 shown and described can access the capability information and / or the current antenna array configuration for the repeater device. Additionally, as described above in connection with Figure 21 the beam configuration circuitry 2142 shown and described can provide means for determining a mapping of beam indices to array indices of these antenna arrays.

[0279] At block 2306, the repeater device can transmit an indication of the number of antenna arrays and the mapping of beam indices to array indices to the network access node. For example, as described above in connection with Figure 21 the beam configuration circuitry 2142 shown and described, together with the communication and processing circuitry 2141 and the transceiver 2110, can transmit the indication to the gNB via the backhaul link. Additionally, as described above in connection with Figure 21 the beam configuration circuitry 2142 shown and described, together with the communication and processing circuitry 2141 and the transceiver 2110, can provide means for transmitting an indication of the number of antenna arrays and the mapping of beam indices to array indices to the network access node.

[0280] In some examples, process 2300 may further include identifying at least one beam pair that cannot be used to relay transmissions between the network access node and the user equipment; and transmitting an indication of the at least one beam pair to the network access node. In some examples, relaying the transmission between the network access node and the user equipment may include: concurrently receiving a first transmission from the network access node and transmitting the first transmission to the user equipment; or concurrently receiving a second transmission from the user equipment and transmitting the second transmission to the network access node.

[0281] In some examples, identifying the at least one beam pair may include identifying beams from a common antenna array of these antenna arrays. In some examples, identifying the at least one beam pair may include determining that the repeater device cannot transmit from a first antenna array of these antenna arrays while concurrently receiving from a second antenna array of these antenna arrays. In some examples, process 2300 may further include performing signal measurements while concurrently transmitting from a first antenna array and receiving from a second antenna array, wherein determining that the repeater device cannot receive from a first antenna array of these antenna arrays while concurrently transmitting from a second antenna array of these antenna arrays is based on these signal measurements.

[0282] In some examples, process 2300 may further include receiving a beam configuration from the network access node; determining whether all beam pairs from the beam configuration can be used to relay transmissions between the network access node and the user equipment; generating an acknowledgement based on determining whether all beam pairs from the beam configuration can be used to relay the transmission, the acknowledgement indicating whether the repeater device supports the beam configuration; and transmitting the acknowledgement to the network access node.

[0283] In some examples, process 2300 may further include receiving a first beam configuration from the network access node; determining that at least one beam pair from the first beam configuration cannot be used to relay transmissions between the network access node and the user equipment; and transmitting a negative acknowledgement to the network access node, the negative acknowledgement indicating that the repeater device does not support the first beam configuration. In some examples, process 2300 may further include receiving a second beam configuration from the network access node after transmitting the negative acknowledgement.

[0284] Figure 24 is a flow chart illustrating an example process 2400 (e.g., method) at a repeater device for communicating beam information in a wireless communication network according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some of the illustrated features may not be required to implement all embodiments. In some examples, process 2400 may be performed by Figure 21 the repeater device 2100 illustrated in. In some examples, process 2400 may be performed by any suitable equipment or device for performing the functions or algorithms described below.

[0285] In block 2402, the repeater device may generate an indication of at least one beam group of the repeater device that can be used for concurrent transmission and reception (or concurrent transmission or reception). For example, as described above in connection with Figure 21 the beam configuration circuitry 2142 shown and described, may determine which beam groups can be used for concurrent transmission and reception (or concurrent transmission or reception). Additionally, as described above in connection with Figure 21 the beam configuration circuitry 2142 shown and described, may provide means for generating an indication of at least one beam group of the repeater device that can be used for concurrent transmission and reception (or concurrent transmission or reception). In some examples, the indication may specify that a first beam group of the at least one beam group can be used for concurrent transmission and reception (or concurrent transmission or reception).

[0286] In block 2404, the repeater device may transmit the indication to the network access node. For example, as described above in connection with Figure 21The illustrated and described beam configuration circuitry 2142, in conjunction with the communication and processing circuitry 2141 and the transceiver 2110, can convey the indication to the gNB via the fronthaul link. Additionally, as described above in connection with Figure 21 The illustrated and described beam configuration circuitry 2142, in conjunction with the communication and processing circuitry 2141 and the transceiver 2110, can provide means for conveying the indication to the network access node.

[0287] In some examples, process 2400 may further include identifying the at least one beam group by identifying beams from different antenna arrays. In some examples, process 2400 may further include performing signal measurements while transmitting and receiving concurrently via the at least one beam group, and identifying the at least one beam group based on these signal measurements.

[0288] In some examples, process 2400 may further include receiving a beam configuration from the network access node; determining whether all beam groups from the beam configuration can be used for concurrent transmission and reception; generating an acknowledgement based on determining whether all beam groups from the beam configuration can be used for concurrent transmission and reception, the acknowledgement indicating whether the repeater device supports the beam configuration; and transmitting the acknowledgement to the network access node.

[0289] In some examples, process 2400 may further include receiving a first beam configuration from the network access node; determining that the at least one beam group from the first beam configuration cannot be used for concurrent transmission and reception; and transmitting a negative acknowledgement to the network access node, the negative acknowledgement indicating that the repeater device does not support the first beam configuration. In some examples, process 2400 may further include receiving a second beam configuration from the network access node after transmitting the negative acknowledgement.

[0290] In some examples, process 2400 may further include transmitting connectivity information of at least one antenna array that supports the concurrent transmission and reception. In some examples, the connectivity information may include: MIMO repeater device configuration, two-way MIMO repeater device configuration, or single input single output (SISO) repeater device configuration. In some examples, the connectivity information may include at least one of the following: an indication of the number of antenna arrays at the repeater device, an indication of how these antenna arrays can be combined for beamforming, an indication of which of these antenna arrays can be combined for beamforming, an indication of which of these antenna arrays can be used for transmission, an indication of which of these antenna arrays can be used for reception, or a combination thereof.

[0291] Figure 25FIG. is a schematic diagram illustrating an example of a hardware implementation of a network access node 2500 (e.g., a scheduling entity, gNB, base station) employing a processing system 2514 in accordance with some aspects of the present disclosure. For example, the network access node 2500 may be a device configured to wirelessly communicate with a scheduled entity (e.g., a UE, a wireless communication device) and a repeater device and / or an IAB node, and may also be configured to communicate with one or more core network nodes (e.g., 5G core network nodes), as discussed in any one or more of Figures 1 - 55 In some implementations, the network access node 2500 may correspond to Figure 1 , 2 , 5 - 12, 14 - 17, 25, 29, 31, 37, and / or any one of the network access nodes (e.g., a scheduling entity, gNB, base station) shown in 39 - 44.

[0292] In accordance with various aspects of the present disclosure, an element, or any part of an element, or any combination of elements may be implemented using the processing system 2514. The processing system 2514 may include one or more processors 2504. The processing system 2514 may be substantially the same as the processing system 2114 illustrated in Figure 21 , including a bus interface 2508, a bus 2502, a memory 2505, a processor 2504, and a computer - readable medium 2506. In addition, the network access node 2500 may include an interface 2530 (e.g., a network interface), which may provide means for communicating with at least one other piece of equipment within the core network, with at least one radio access network, with at least one UE, with at least one other network access node, with at least one repeater device, and / or with at least one IAB node.

[0293] The bus interface 2508 may provide an interface between the bus 2502 and the transceiver 2510 and between the bus 2502 and the interface 2530. The transceiver 2510 may further be coupled to one or more antennas / antenna arrays 2520. The transceiver 2510 in combination with one or more antennas / antenna arrays 2520 may provide a communication interface 2530 or means for communicating with various other pieces of equipment over a wireless transmission medium. The interface 2530 may provide a communication interface or means for communicating with various other pieces of equipment and devices (e.g., other devices housed within the same piece of equipment as the network access node or other external devices) over an internal bus or an external transmission medium such as an Ethernet cable. Depending on the characteristics of the equipment, the interface 2530 may include a user interface (e.g., a keypad, a display, a speaker, a microphone, a joystick, control features, etc.). Of course, such a user interface is optional and may be omitted in some examples. In addition, the bus interface 2508 may further provide an interface between the bus 2502 and the power supply 2528.

[0294] The network access node 2500 may be configured to perform any one or more of the operations described herein (e.g., as described in connection with Figures 26 - 28 36, 38, and / or 49 - 52). In some aspects of the present disclosure, the processor 2504 utilized in the network access node 2500 may include circuitry configured for various functions. The processor 2504 is responsible for managing the bus 2502 and general processing, including the execution of software stored on the computer-readable medium 2506. The software, when executed by the processor 2504, causes the processing system 2514 to perform the various functions described below for any particular equipment. The computer-readable medium 2506 and the memory 2505 may also be used to store data manipulated by the processor 2504 when executing the software.

[0295] The processor 2504 may be configured to generate, schedule, and modify resource assignments or grants for time-frequency resources (e.g., a collection of one or more resource elements). For example, the processor 2504 may schedule time-frequency resources within multiple time-division duplex (TDD) and / or frequency-division duplex (FDD) subframes, time slots, and / or mini-slots to carry user data traffic and / or control information to and / or from multiple repeater devices.

[0296] The processor 2504 may be configured to schedule resources for downlink signal transmission. Downlink signals may include, for example, PDCCH, PDSCH, CSI-RS, or DMRS. The processor 2504 may further be configured to schedule resources that may be used by a repeater device to transmit uplink signals. Uplink signals may include, for example, PUCCH, PUSCH, SRS, DMRS, or PRACH. The processor 2504 may be further configured to schedule resources that may be used by a repeater device to transmit and / or receive sidelink signals.

[0297] In some aspects of the present disclosure, the processor 2504 may include communication and processing circuitry 2541. The communication and processing circuitry 2544 may be configured for various functions, including, for example, communicating with a user equipment (UE), a repeater device, or other wireless communication devices, a network core (e.g., a 5G core network), other network access nodes or scheduling entities, or any other entity (such as, for example, a local infrastructure or an entity communicating with the network access node 3500 via the Internet (such as a network provider)). The communication and processing circuitry 2541 may include one or more hardware components that provide a physical structure for performing various processes related to wireless communication (e.g., signal reception and / or signal transmission) as described herein. The communication and processing circuitry 2541 may further include one or more hardware components that provide a physical structure for performing various processes related to signal processing (e.g., processing received signals and / or processing signals for transmission) as described herein. Additionally, the communication and processing circuitry 2541 may be configured to receive and process downlink traffic and downlink control (e.g., similar to Figure 1 the uplink traffic 112 and uplink control 114), and process and transmit uplink traffic and uplink control (e.g., similar to uplink traffic 116 and uplink control 118). The communication and processing circuitry 2541 may further be configured to interact with one or more transceivers 2510 to encode and transmit downlink signals. The communication and processing circuitry 2541 may further be configured to interact with one or more transceivers 2510 to monitor and decode uplink signals. The communication and processing circuitry 2541 may further be configured to execute communication and processing software 2551 included on a computer-readable medium 2506 to implement one or more functions described herein.

[0298] In some examples, the communication and processing circuitry 2541 may be configured to receive and process uplink beamformed signals at millimeter wave frequencies or sub-6 GHz frequencies via the transceiver 2510 and the antenna array 2520. For example, the communication and processing circuitry 2541 may be configured to receive corresponding reference signals (e.g., SRS or DMRS) from a repeater device on each of a plurality of uplink beams during an uplink beam sweep.

[0299] In some examples, the communication and processing circuitry 2541 may be further configured to generate and transmit a downlink beamformed signal at millimeter wave frequencies or sub-6 GHz frequencies via the transceiver 2510 and the antenna array 2520. For example, the communication and processing circuitry 2541 may be configured to transmit a corresponding downlink reference signal (e.g., SSB or CSI-RS) to the repeater device on each of a plurality of downlink beams via at least one first antenna panel of the antenna array 2520 during downlink beam sweeping. The communication and processing circuitry 2541 may be further configured to receive a beam measurement report from the repeater device.

[0300] The communication and processing circuitry 2541 may be further configured to receive an uplink signal on one or more uplink receive beams via one or more uplink transmit beams applied to the uplink signal. For example, the communication and processing circuitry 2541 may be configured to receive an uplink signal on one or more uplink receive beams via at least one second antenna panel of the antenna array 2520. The uplink signal may include, for example, PUCCH, PUSCH, SRS, DMRS, or PRACH.

[0301] The communication and processing circuitry 2541 may be further configured to control the antenna array 2520 and the transceiver 2510 to generate a plurality of downlink transmit beams during downlink beam sweeping. The communication and processing circuitry 2541 may be further configured to use the communication and processing circuitry 2544 to receive a beam measurement report from the repeater device. The communication and processing circuitry 2541 may be further configured to identify one or more selected uplink beams based on these beam measurements. In some examples, the communication and processing circuitry 2541 may be configured to, for each of the serving downlink transmit beams, compare the corresponding RSRP (or other beam measurement) measured on each of the downlink receive beams to identify the serving downlink receive beam, and further identify the serving downlink receive beam as the selected uplink transmit beam. Each serving downlink receive beam may have the highest measured RSRP (or other beam measurement) for one of the downlink transmit beams.

[0302] The communication and processing circuitry 2541 may be configured to receive one or more uplink transmit beams in an uplink beam sweep. Each uplink transmit beam may carry an uplink reference signal (e.g., SRS) for measurement by the communication and processing circuitry 2541. The communication and processing circuitry 2541 may further be configured to obtain, for each of the uplink transmit beams, a plurality of beam measurements on each of a plurality of uplink receive beams of the antenna array 2520. The communication and processing circuitry 2541 may further be configured to select, based on the uplink beam measurements, a selected uplink transmit beam and a corresponding uplink receive beam that form a respective uplink BPL.

[0303] In some implementations in which communication involves receiving information, the communication and processing circuitry 2541 may obtain information from components of the network access node 2500 (e.g., from the transceiver 2510 that receives information via radio frequency signaling or some other type of signaling adapted to the applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, the communication and processing circuitry 2541 may output the information to another component of the processor 2504, to the memory 2505, or to the bus interface 2508. The information may include, for example, beam information 2515 that may be stored in the memory 2505. In some examples, the communication and processing circuitry 2541 may receive one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 2541 may receive information via one or more channels. In some examples, the communication and processing circuitry 2541 may include functionality of means for receiving.

[0304] In some implementations in which communication involves sending (e.g., transmitting) information, the communication and processing circuitry 2541 may obtain information from (e.g., from another component of the processor 2504, the memory 2505, or the bus interface 2508), process (e.g., encode) the information, and output the processed information. For example, the communication and processing circuitry 2541 may output the information to the transceiver 2510 (e.g., to transmit information via radio frequency signaling or some other type of signaling adapted to the applicable communication medium). In some examples, the communication and processing circuitry 2541 may send one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 2541 may send information via one or more channels. In some examples, the communication and processing circuitry 2541 may include functionality of means for sending (e.g., means for transmitting).

[0305] The processor 2504 may include beam configuration circuitry 2542, which is configured to perform operations related to beam configuration as discussed herein. The beam configuration circuitry 2542 may further be configured to provide functionality for generating a configuration of the means. The beam configuration circuitry 2542 may further be configured to provide functionality for transmitting the configuration of the means. The beam configuration circuitry 2542 may further be configured to provide functionality for determining that the repeater device is transmitting on fewer than all of the number of SSBs. The beam configuration circuitry 2542 may further be configured to provide functionality for receiving an indication. The beam configuration circuitry 2542 may further be configured to provide functionality for selecting a beam configuration. The beam configuration circuitry 2542 may further be configured to provide functionality for identifying a beam group. The beam configuration circuitry 2542 may further be configured to provide functionality for transmitting an indication. The beam configuration circuitry 2542 may be further configured to execute beam configuration software 2552 included on a computer-readable medium 2506 to implement one or more functions described herein.

[0306] The processor 2504 may include beam processing circuitry 2543, which is configured to perform operations related to beam processing as discussed herein. The beam processing circuitry 2543 may further be configured to provide functionality for transmitting an SSB transmission. The beam processing circuitry 2543 may further be configured to provide functionality for transmitting a beam configuration. The beam processing circuitry 2543 may be further configured to execute beam processing software 2553 included on a computer-readable medium 2506 to implement one or more functions described herein.

[0307] Figure 26 is a flowchart illustrating an example process 2600 (e.g., method) at a network access node for communicating beam information in a wireless communication network in accordance with some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some of the illustrated features may not be required to implement all embodiments. In some examples, process 2600 may be performed by Figure 25 the network access node 2500 illustrated in. In some examples, process 2600 may be performed by any suitable apparatus or device for performing the functions or algorithms described below.

[0308] At block 2602, the network access node may generate a first configuration indicating a first number of synchronization signal blocks (SSBs) to be transmitted by the repeater device. For example, as described above in connection with Figure 25 the beam configuration circuitry 2542 shown and described may select a set of SSBs to be transmitted by the repeater device. Additionally, as described above in connection withFigure 25 The beam configuration circuitry 2542 shown and described can provide means for generating a first configuration for indicating a first number of synchronization signal blocks (SSBs) to be transmitted by the repeater device.

[0309] In some examples, the first configuration can include SSB indices. In some examples, these SSB indices can be mapped to beam information that the repeater device may use for subsequent transmissions. In some examples, the beam information can include spatial quasi-co-location information for the first number of SSBs.

[0310] At block 2604, the network access node can transmit the first configuration to the repeater device. For example, the beam configuration circuitry 2542 shown and described above, together with the communication and processing circuitry 2541 and the transceiver 2510, can transmit the configuration to the MT of the repeater device via the fronthaul link. Additionally, the beam configuration circuitry 2542 shown and described above, together with the communication and processing circuitry 2541 and the transceiver 2510, can provide means for transmitting the first configuration to the repeater device. Figure 25 shown and described above, together with the communication and processing circuitry 2541 and the transceiver 2510, can transmit the configuration to the MT of the repeater device via the fronthaul link. Additionally, the beam configuration circuitry 2542 shown and described above, together with the communication and processing circuitry 2541 and the transceiver 2510, can provide means for transmitting the first configuration to the repeater device. Figure 25 The beam configuration circuitry 2542 shown and described can provide means for transmitting the first configuration to the repeater device.

[0311] In some examples, process 2600 can further include transmitting at least one SSB transmission to the repeater device after transmitting the first configuration.

[0312] At block 2606, the network access node can determine that the repeater device is transmitting fewer than all of the first number of SSBs. For example, the beam configuration circuitry 2542 shown and described above can determine that K'<K is received, determine that message 1 is not received on some beams, and so on. Additionally, the beam configuration circuitry 2542 shown and described above can provide means for determining that the repeater device is transmitting fewer than all of the first number of SSBs. Figure 25 shown and described above can determine that K'<K is received, determine that message 1 is not received on some beams, and so on. Additionally, the beam configuration circuitry 2542 shown and described above can provide means for determining that the repeater device is transmitting fewer than all of the first number of SSBs. Figure 25 The beam configuration circuitry 2542 shown and described can provide means for determining that the repeater device is transmitting fewer than all of the first number of SSBs.

[0313] In some examples, determining that the repeater device is transmitting fewer than all of the first number of SSBs can include receiving an indication that the repeater device is using a second number of beams to transmit the SSBs. In some examples, determining that the repeater device is transmitting fewer than all of the first number of SSBs can include determining that there is no communication with the user equipment on at least one beam associated with the first number of SSBs. In some examples, determining that the repeater device is transmitting fewer than all of the first number of SSBs can include determining that no random access message is received on at least one random access channel (RACH) occasion having the first number of SSBs.

[0314] At block 2608, the network access node may generate a second configuration after determining that the repeater device is transmitting fewer than all of the first number of SSBs, the second configuration indicating a second number of SSBs to be transmitted by the repeater device. For example, the beam configuration circuitry 2542 shown and described above in conjunction with Figure 25 may select a second set of SSBs (e.g., a smaller set of SSBs) to be transmitted by the repeater device. Additionally, the beam configuration circuitry 2542 shown and described above in conjunction with Figure 25 may provide means for generating a second configuration after determining that the repeater device is transmitting fewer than all of the first number of SSBs, the second configuration indicating a second number of SSBs to be transmitted by the repeater device.

[0315] At block 2610, the network access node may transmit the second configuration to the repeater device. For example, the beam configuration circuitry 2542 shown and described above in conjunction with Figure 25 along with the communication and processing circuitry 2541 and the transceiver 2510 may transmit the configuration to the MT of the repeater device via the fronthaul link. Additionally, the beam configuration circuitry 2542 shown and described above in conjunction with Figure 25 along with the communication and processing circuitry 2541 and the transceiver 2510 may provide means for transmitting the second configuration to the repeater device.

[0316] In some examples, process 2600 may further include receiving capability information from the repeater device; estimating the number of beams supported by the repeater device based on the capability information; and determining a first number of SSBs based on the number of beams supported by the repeater device. In some examples, the capability information may include at least one of the following: the maximum number of configured transmission configuration indicator (TCI) states per component carrier, the maximum number of configured spatial relationships, the maximum number of sounding reference signal (SRS) resource sets, the maximum number of SRS resources per resource set, or a combination thereof.

[0317] Figure 27 is a flow diagram of an example process 2700 (e.g., method) at a network access node for communicating beam information in a wireless communication network in accordance with some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some of the illustrated features may not be required to implement all embodiments. In some examples, process 2700 may be performed by the Figure 25 network access node 2500 illustrated in. In some examples, process 2700 may be performed by any suitable apparatus or device for performing the functions or algorithms described below.

[0318] At block 2702, the network access node may receive an indication of the number of antenna arrays of a repeater device and a mapping of beam indices to array indices of those antenna arrays. Figure 25 The beam configuration circuit system 2542 shown and described together with the communication and processing circuit system 2541 and the transceiver 2510 can receive capability information or configuration information from the MT of the repeater device via the forward link. Figure 25 The beam configuration circuitry 2542 shown and described, together with the communication and processing circuitry 2541 and transceiver 2510, may provide a means for receiving an indication of the number of antenna arrays of a repeater device and a mapping of beam indices to array indices of those antenna arrays.

[0319] At block 2704, the network access node may select a first beam configuration for the relay device based on the indication. Figure 25 The beam configuration circuitry 2542 shown and described may select a set of SSBs to be transmitted by the repeater device. Figure 25 The beam configuration circuitry 2542 shown and described may provide means for selecting a first beam configuration for the repeater device based on the indication.

[0320] At block 2706, the network access node may transmit a first beam configuration to the repeater device. Figure 25 The beam configuration circuit system 2542 shown and described together with the communication and processing circuit system 2541 and the transceiver 2510 can transmit the configuration to the MT of the relay device via the forward link. Figure 25 The beam configuration circuitry 2542, together with the communication and processing circuitry 2541 and the transceiver 2510 shown and described, may provide a means for transmitting a first beam configuration to a repeater device.

[0321] In some examples, process 2700 may further include identifying at least one beam pair that cannot be used by the repeater device to relay transmissions between the network access node and the user equipment, wherein identifying the at least one beam pair is based on the indication, wherein selecting the first beam configuration may include avoiding including the at least one beam pair in the first beam configuration. In some examples, identifying the at least one beam pair may include identifying a beam from a common antenna array of the antenna arrays based on the indication.

[0322] In some examples, identifying the at least one beam pair can include determining that the repeater device cannot transmit from the first antenna array among the antenna arrays while concurrently receiving from the second antenna array among the antenna arrays. In some examples, process 2700 can further include performing signal measurements while the repeater device is concurrently transmitting from the first antenna array and receiving from the second antenna array, wherein determining that the repeater device cannot transmit from the first antenna array among the antenna arrays while concurrently receiving from the second antenna array among the antenna arrays can be based on the signal measurements.

[0323] In some examples, process 2700 can further include receiving a measurement report from the user equipment based on signal measurements performed by the user equipment while the repeater device is concurrently transmitting from the first antenna array and receiving from the second antenna array, wherein determining that the repeater device cannot transmit from the first antenna array among the antenna arrays while concurrently receiving from the second antenna array among the antenna arrays is based on the measurement report.

[0324] In some examples, process 2700 can further include receiving an acknowledgement from the repeater device indicating whether the repeater device supports a first beam configuration. In some examples, process 2700 can further include receiving a negative acknowledgement from the repeater device indicating that the repeater device does not support the first beam configuration. In some examples, process 2700 can further include selecting a second beam configuration for the repeater device after receiving the negative acknowledgement; and transmitting the second beam configuration to the repeater device.

[0325] Figure 28 is a flow diagram depicting an example process 2800 (e.g., method) at a network access node for communicating beam information in a wireless communication network in accordance with some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some of the illustrated features may not be required to implement all embodiments. In some examples, process 2800 can be performed by Figure 25 the network access node 2500 illustrated in. In some examples, process 2800 can be performed by any suitable apparatus or device for performing the functions or algorithms described below.

[0326] At block 2802, the network access node can identify at least one beam group of the repeater device that can be used for concurrent transmission or reception. For example, as described above in connection with Figure 25The beam configuration circuitry 2542 as shown and described can receive an indication of the at least one beam group from the repeater device; identify the at least one beam group based on the configuration information received from the repeater device, or identify the at least one beam group based on these signal measurements or measurement reports. Additionally, as described above in connection with Figure 25 The beam configuration circuitry 2542 as shown and described can provide means for identifying at least one beam group of the repeater device that can be used for concurrent transmission or reception.

[0327] In some examples, identifying the at least one beam group can include receiving an indication of the at least one beam group from the repeater device. In some examples, the indication can specify that a first beam group in the at least one beam group can be used for concurrent transmission and reception. In some examples, identifying the at least one beam group can include identifying beams from different antenna arrays of the repeater device.

[0328] At block 2804, the network access node can select a first beam configuration for the repeater device that specifies the at least one beam group. For example, as described above in connection with Figure 25 The beam configuration circuitry 2542 as shown and described can select a set of SSBs to be transmitted by the repeater device. Additionally, as described above in connection with Figure 25 The beam configuration circuitry 2542 as shown and described can provide means for selecting a first beam configuration for the repeater device that specifies the at least one beam group.

[0329] At block 2806, the network access node can transmit the first beam configuration to the repeater device. For example, the beam configuration circuitry 2542 as shown and described, together with the communication and processing circuitry 2541 and the transceiver 2510, can transmit the configuration to the MT of the repeater device via the backhaul link. Additionally, as described above in connection with Figure 25 The beam configuration circuitry 2542 as shown and described, together with the communication and processing circuitry 2541 and the transceiver 2510, can provide means for transmitting the first beam configuration to the repeater device. Figure 25

[0330] In some examples, process 2800 can further include performing signal measurements while the repeater device is concurrently transmitting and receiving via the at least one beam group, wherein the identification of the at least one beam group is based on these signal measurements.

[0331] ​In some examples, process 2800 may further include receiving an acknowledgement from the repeater device indicating whether the repeater device supports the first beam configuration. In some examples, process 2800 may further include receiving a negative acknowledgement from the repeater device indicating that the repeater device does not support the first beam configuration. In some examples, process 2800 may further include selecting a second beam configuration for the repeater device after receiving the negative acknowledgement; and transmitting the second beam configuration to the repeater device.

[0332] In some examples, process 2800 may further include receiving connectivity information of at least one antenna array supporting the concurrent transmission and reception, wherein selecting the first beam configuration for the repeater device is based on the connectivity information. In some examples, the connectivity information may include: a multiple-input multiple-output (MIMO) repeater device configuration, a bi-directional MIMO repeater device configuration, or a single-input single-output (SISO) repeater device configuration. In some examples, the connectivity information may include at least one of the following: an indication of the number of antenna arrays at the repeater device, an indication of how the antenna arrays can be combined for beamforming, an indication of which of the antenna arrays can be combined for beamforming, an indication of which of the antenna arrays can be used for transmission, an indication of which of the antenna arrays can be used for reception, or a combination thereof.

[0333] Accordingly and as a summary, initially, the DU of a network access node (e.g., gNB) may configure the RU of a repeater device to transmit or relay K SSBs. For example, the DU may send an SSB index to the repeater device indicating which SSBs the DU is going to transmit. Here, each SSB index is associated with corresponding spatial quasi co-location (QCL) information indicating the beam to be used for transmitting the corresponding SSB.

[0334] In an implementation where the repeater device does not include store-and-forward functionality, the network access node may transmit each SSB to the repeater device. When receiving each SSB, the repeater device relays the SSB using the corresponding specified beam.

[0335] In an implementation where the repeater device includes store-and-forward functionality, the network access node may transmit a set of SSB information to the repeater device. Subsequently, the repeater device may continuously transmit SSBs (based on the SSB information) using the corresponding specified beam for each transmission.

[0336] In some examples, these K SSBs can be used as (spatial QCL) references for other communications by the RU. For example, the network access node can indicate a specific SSB index for subsequent transmissions (e.g., data transmissions). In this case, the RU will be configured to use the same beam as that used for the corresponding SSB for transmission.

[0337] In different examples, the network access node can select the initial number K in different ways. As an example, the network access node can select the K parameter based on the expected traffic in the area of the repeater device (e.g., based on current or historical scheduling). As another example, the network access node can select the K parameter based on historical information about the repeater device (e.g., the typical number of supported beams). In other examples, other techniques can be used to select the initial parameter K.

[0338] In some scenarios, after receiving the parameter K, the repeater device can determine that it can only support K' beams to transmit the SSB, where K' <= K. For example, the repeater device may not have enough resources (e.g., insufficient number of antenna arrays, insufficient number of antenna arrays, insufficient number of transmit and / or receive chains, insufficient processing power, etc.) to transmit K SSBs. As another example, the repeater device can determine that not all beams can be used for the relay function. For example, cross-beam interference or other interference may limit the number of beams that the repeater device can currently use. As another example, the beam used for the backhaul link may not be available for relaying the SSB. In any of these cases, the repeater device can select K' SSBs out of the K SSBs (where K' < K) and transmit those K' SSBs.

[0339] In some examples where K' < K, the repeater device can notify the network access node that the repeater device has selected to use K' beams. For example, the repeater device can send an indication of the parameter K' to the network access node (e.g., via UCI, RRC message, media access control element (MAC-CE), or some other suitable signaling). The network access node can then reconfigure the repeater device with a smaller number of SSBs.

[0340] In other examples, the repeater device may not notify the network access node that the repeater device has selected to use K' < K beams. In this case, the network access node can determine that some of the assigned SSBs are not being used and / or are not helping the communication performance. The network access node can then reconfigure the repeater device with a smaller number of SSBs.

[0341] The network access node can determine in different ways in different examples that some of the assigned SSBs are not being used by the repeater device and / or are not helping the communication performance.

[0342] In some examples, a network access node may monitor RACH opportunities associated with a beam to determine whether the beam is not being used by a repeater device or to determine whether the signal quality associated with the beam is relatively poor. For example, if the network access node has not received any random access preambles (e.g., Message 1) on the beam (e.g., over a period of time), the network access node may infer that the repeater device is not using the beam. As another example, if the network access node has received a relatively small number (e.g., less than a threshold number) of random access preambles (e.g., Message 1) on the beam (e.g., over a period of time), the network access node may infer that the signal quality associated with the beam is poor. In either case, the network access node may discard the corresponding SSB from the beam configuration for the repeater device.

[0343] In some examples, a network access node may measure signals associated with transmissions made by a repeater device and / or transmissions made by a UE served by the repeater device. If these measurements indicate that the signal quality associated with certain beams is relatively poor (e.g., below a threshold quality), the network access node may discard the corresponding SSB from the beam configuration for the repeater device.

[0344] In some examples, a network access node may monitor measurement reports from UEs served by a repeater device. If these measurement reports indicate that the signal quality associated with certain beams is relatively poor (e.g., below a threshold quality), the network access node may discard the corresponding SSB from the beam configuration for the repeater device.

[0345] In some examples (e.g., in the case where the MT and RU share backhaul resources), a network access node may estimate the beam information of a repeater device based on the capability signaling of the MT. For example, to infer how many beams the RU can generate / support, the network access node may monitor one or more of the maxNumberConfiguredTCIstatesPerCC (maximum number of configured TCI states per CC), maxNumberConfiguredSpatialRelations (maximum number of configured spatial relations), maxNumberSRS-ResourceSet (maximum number of SRS resource sets), maxNumberSRS-ResourcePerSet-BM (maximum number of SRS resources per set - BM) parameters, or a combination of two or more of these parameters, or other suitable parameters. Here, generally speaking, the parameters to be monitored may include those parameters for which there is a relationship between the magnitude of the parameter and the number of beams supported by the repeater device.

[0346] In some aspects, the present disclosure relates to a repeater device indicating to a network access node the number of arrays at the repeater device and / or the mapping of beam indices to these array indices. For example, the repeater device may send this information in a capabilities message or dynamically (e.g., in a UCI, RRC message, MAC-CE, etc.). This information may be sent together with other information, such as the number of beams the repeater device can generate on the serving side, the number of layers supported by the repeater device (e.g., coarse, fine, finer, etc.), the mapping of beam indices to layer indices, and the spatial QCL information between the beams.

[0347] In some aspects, the present disclosure relates to a repeater device indicating to a network access node beam pairs that cannot be used for relay operations. For example, the repeater device may send this information in a capabilities message or dynamically (e.g., in a UCI, RRC message, MAC-CE, etc.).

[0348] The repeater device may identify beam pairs that cannot be used for repeat operations in different ways in different examples. In some examples, the default assumption may be that beams on the same array may not be used for simultaneous transmission and reception (e.g., full-duplex operation). As another example, there may be constraints for multi-array antennas (e.g., the repeater device cannot receive from array X and forward on array Y). As yet another example, the repeater device may perform measurements to determine which beam combinations do not work or are unreliable (e.g., due to interference, permanent beam-blocking obstacles, transient obstacles, etc.).

[0349] In some examples, (e.g., in the case where the repeater device does not provide the above information), the network access node (e.g., DU) may determine this information based on the repeater device configuration information, signal measurements, or feedback from the repeater device. For example, the network access node may determine that the base station has obtained a pair of beams on the same array based on the antenna array information about the repeater device. As another example, based on RACH message transmission and reception, signal measurements, or measurement reports (e.g., as discussed above), the network access node may determine that a particular beam combination does not work or provides poor communication quality (e.g., below a threshold quality). As yet another example, upon receiving a beam configuration from the network access node, the repeater device may send back an acknowledgement indicating whether the configuration is supported (e.g., currently supported) by the repeater device. For example, if the configuration specifies a beam pair that the repeater device has determined is not suitable for simultaneous transmission and reception for simultaneous transmission and reception, the repeater device may send a negative acknowledgement (NAK) to the network access node. Otherwise, the repeater device may send a positive acknowledgement (ACK) to the network access node. In any of the above scenarios, once it is determined that a beam pair of the repeater device cannot be used for the intended purpose, the network access node may refrain from including that beam pair in the beam configuration for the repeater device.

[0350] In some aspects, the present disclosure relates to a repeater device indicating to a network access node beam groups for relay operations that cannot be used for simultaneous transmission and / or simultaneous reception (e.g., including carrier aggregation and / or full-duplex operation). For example, the repeater device may send this information in a capabilities message or dynamically (e.g., in UCI, RRC messages, MAC-CE, etc.).

[0351] The repeater device may identify beam groups that can or cannot be used for simultaneous transmission and / or reception in different ways in different examples. In some examples, the default assumption may be that beams on different arrays can be used for simultaneous transmission and reception. As another example, there may be constraints for multi-array antennas (e.g., the repeater device cannot receive from array X and forward on array Y). As yet another example, the repeater device may perform measurements to determine which beam groups are not working or are unreliable (e.g., due to interference, permanent beam-blocking obstacles, transient obstacles, etc.).

[0352] In some examples, (e.g., in the case where the repeater device does not provide the above information), the network access node (e.g., DU) may determine this information based on repeater device configuration information, signal measurements, or feedback from the repeater device. For example, the network access node may determine that the network access node has obtained a group of beams on different arrays based on antenna array information about the repeater device. As another example, based on RACH message exchanges, signal measurements, or measurement reports (e.g., as discussed above), the network access node may determine that a particular beam group is not working or provides poor communication quality (e.g., below a threshold quality). As yet another example, upon receiving a beam configuration from the network access node, the repeater device may send back an acknowledgement indicating whether the configuration is supported (e.g., currently supported) by the repeater device. For example, if the configuration specifies a beam group that the repeater device has determined is not suitable for simultaneous transmission and reception for simultaneous transmission and reception, the repeater device may send a negative acknowledgement (NAK) to the network access node. Otherwise, the repeater device may send a positive acknowledgement (ACK) to the network access node. In any of the above scenarios, once it is determined that a beam group of the repeater device cannot be used for the intended purpose, the network access node may refrain from including that beam group in the beam configuration for the repeater device.

[0353] If two-way forwarding (simultaneous UL and DL) is supported, the repeater device may send connectivity information of the array to the UE. The connectivity information may include, for example, at least one of the following: an indication of the number of antenna arrays at the repeater device, an indication of how these antenna arrays may be combined for beamforming, an indication of which of these antenna arrays can be combined for beamforming, an indication of which of these antenna arrays can be used for transmission, an indication of which of these antenna arrays can be used for reception, or a combination thereof.

[0354] II. Open-Loop Configuration of Radio Frequency (RF) Repeater Device

[0355] The network access node may schedule access to the cell to support access by multiple UEs. For example, the network access node may allocate different resources (e.g., time-domain and frequency-domain resources) for different UEs operating within the cell of the network access node. To extend the coverage of the wireless network, repeater devices may be used to relay communication traffic between two nodes. Current repeater devices seem to fill both ends of the spectrum. At one end are repeater devices that may have fixed and non-configurable antenna patterns, amplification settings, output power settings, and treat uplink and downlink resources in the same way. At the other end of the spectrum are so-called intelligent repeater devices that have greater configurability but rely on the network access node for control. Improvements to repeater device technology, including technologies that may allow the repeater device to configure itself with little or no interaction with the network access node, can enhance the performance and flexibility of wireless communication networks that employ repeater device technology.

[0356] According to aspects described herein, the repeater device may be configured as an open-loop repeater device. The open-loop repeater device may combine the amplification and forwarding aspects of layer 1 relaying with the upper layers of a protocol stack (such as a 5G protocol stack) (e.g., Figure 14Combined with enhancements to at least some of the functionality provided by the MAC, RLC, PDCP, RRC, L2 1444, and L3 1446). The open-loop repeater device can obtain side control information, or at least some aspects of the side control information, from the air broadcast of the network access node. The open-loop repeater device may not be directly controlled by the network access node and may not establish (not establish) an RRC connection with the network access node. The open-loop aspect reduces the processing overhead of the network access node, which may not need (not need) to actively control the open-loop repeater device, while it needs to control the intelligent repeater device. The open-loop aspect can reduce the control signaling overhead between the network access node and the open-loop repeater device because the network access node may not need (not need) to direct any control signaling to the open-loop repeater device; instead, the open-loop repeater device obtains (e.g., collects, harvests) information from the master information block (MIB), system information block type 1 (SIB1) block (also known as RMSI), and can also obtain information from other system information (OSI) in any one or more of the SIB2 - SIB9 system information blocks. According to some aspects, the open-loop repeater device can use the first two steps (message 1 and message 2) of the 4-step contention-based RACH procedure, or the two steps (message A and message B) of the 2-step contention-based RACH procedure to exchange information with the network access node. However, the open-loop repeater device may not need (not need) to establish an RRC connection with the network access node. The exchanged information can be used, for example, to configure one or more circuits of the open-loop repeater device. This configuration can, for example, implement beamforming to provide directivity to the receiving and transmitting hardware and / or functionality of the open-loop repeater device. This configuration can, for example, implement transmitter power control to avoid, for example, signals transmitted from the open-loop repeater device interfering with signals received by nearby UEs or a second network access node. This configuration can, for example, implement the feature of turning on or off such receivers and / or transmitters when one or more receivers and / or transmitters are not needed. Deciding whether to turn on or off the receivers and / or transmitters can be based on knowledge of the direction of the scheduled resources (e.g., UL, flexible, or DL). These and other features and aspects are described in more detail below.

[0357] Figure 29 FIG. is an illustration of a wireless communication network 2900 that illustrates communication between a network access node 2902 and a first UE 2914 via a first repeater device 2906 using beamformed signals according to some aspects of the present disclosure. The network access node 2902 may correspond to Figure 1 , 2any network access node (e.g., a scheduling entity, gNB, base station) shown in any of 5 - 12, 14 - 17, 25, 29, 31, 37, and / or 39 - 44. The first UE 2914 and the second UE 2926 may correspond to Figure 1 , 2 any UE (e.g., a scheduled entity, a wireless communication device) shown in any of 5 - 12, 14 - 17, 29, 31, and / or 44. The first repeater device 2906 and the second repeater device 2918 may correspond to Figures 7 - 21 any RF repeater device of 29, 31, 32, 37, 39, and / or 40.

[0358] In Figure 29 the example shown, the network access node 2902 may be configured to generate a plurality of beams 2904a - 2904g, each beam associated with a different beam direction (e.g., azimuth). The network access node 2902 may transmit and / or receive on any one or more of the plurality of beams 2904a - 2904g. The corresponding beams among the plurality of beams 2904a - 2904g may be directed to various angles (e.g., azimuth). The first UE 2914 and / or the second UE 2926 may each be at a certain distance from the network access node 2902. Additionally or alternatively, there may be a structure or an obstacle (not shown) between the direct line of sight between the network access node 2902 and the first UE 2914 and / or between the network access node 2902 and the second UE 2926.

[0359] The first repeater device 2906 may be located between the network access node 2902 and the first UE 2914. In some aspects, a repeater device may be referred to as a “smart repeater device” if it is controlled by another device (such as the network access node 2902), for example. The control may provide “side control information” to the smart repeater device, which facilitates the dynamic or semi - static configuration of the smart repeater device using, for example, beamforming information, power control information, and / or transmitter and receiver on / off information in combination with knowledge of whether a given resource is scheduled for uplink or downlink operation. The smart repeater device may receive the side control information in a closed - loop manner; that is, the network access node 2902 may have direct control over the smart repeater device. However, as described herein, the first repeater device 2906 may receive the side control information by capturing information from the master information block and system information block parameters in the air, without the need for direct control by the network access node 2902. In this context, the first repeater device 2906 may not be a smart repeater device, but instead the first repeater device 2906 may be an “open - loop repeater device” (hereinafter referred to as the first repeater device 2906).

[0360] The first repeater device 2906 may have an antenna array (not shown) that allows the first repeater device 2906 to perform beamforming and direct one or more of the plurality of beams 2908a - 2908g in various directions (e.g., azimuth). Beamforming may allow the first repeater device 2906 to form narrow directional beams 2908a - 2908g in multiple directions and / or form wide directional beams (not shown) in multiple directions and / or form an omnidirectional beam (not shown).

[0361] The first UE 2914 may have an antenna array (not shown) that allows the first UE 2914 to perform beamforming and direct a beam in various directions (e.g., azimuth). Beamforming may allow the first UE 2914 to form narrow directional beams 2916 (one of the multiple directional beams shown to avoid cluttering the drawing), and / or form wide directional beams (not shown) in multiple directions, and / or form an omnidirectional beam (not shown). In Figure 29 the example, the narrow directional beam 2916 of the first UE 2914 is aligned or substantially aligned with the directional beam 2908c of the first repeater device 2906.

[0362] The first repeater device 2906 may amplify and forward (e.g., convey) RF signals exchanged between the first UE 2914 and the network access node 2902. The amplification and forwarding may be two - way. The two - way link between the network access node 2902 and the first repeater device 2906 may be referred to herein as the backhaul link. The two - way link between the first repeater device 2906 and the first UE 2914 may be referred to herein as the access link.

[0363] The second repeater device 2918 (e.g., an RF repeater device) may be located between the network access node 2902 and the second UE 2926. The second repeater device 2918 may be configured with an omnidirectional beam 2920 or may have a fixed directional beam (not shown) (e.g., where the fixed directional beam may be a wide beam pointing in one direction (not shown) without the ability to be steered (mechanically or electrically). The second repeater device 2918 may not be provided with a steerable beam configuration and may not be adaptive over time. The second repeater device 2918 may not distinguish between uplink and downlink resources. The second repeater device 2918 may not have high complexity. The second repeater device 2918 may be implementation - based. That is, the second repeater device 2918 and other devices of its type may be implemented, for example, to adapt to a specific geographical location.

[0364] The second UE 2926 may have an antenna array (not shown) that allows the second UE 2926 to perform beamforming and direct beams in various directions (e.g., azimuth). Beamforming may allow the second UE 2926 to form narrow directional beams 2928 in multiple directions (one of the multiple directional beams shown to avoid cluttering the drawing), and / or form wide directional beams in multiple directions (not shown), and / or form an omnidirectional beam (not shown). In the example of FIG. 29, the narrow directional beam 2928 of the second UE 2926 is aligned or substantially aligned with the second repeater device 2918, and thus is aligned or substantially aligned with the omnidirectional beam 2920 of the second repeater device 2918.

[0365] The second repeater device 2918 may amplify and forward (e.g., amplify and repeat) RF signals exchanged between the second UE 2926 and the network access node 2902. Amplifying and forwarding may be bidirectional. The bidirectional link between the network access node 2902 and the second repeater device 2918 may be referred to as the backhaul link. The bidirectional link between the second repeater device 2918 and the second UE 2926 may be referred to as the access link herein.

[0366] As described, the first repeater device 2906 and the second repeater device 2918 may each amplify and forward RF signals (e.g., analog signals in the physical (PHY) layer). One difference between the first repeater device 2906 and the second repeater device 2918 is the ability of the first repeater device 2906 to use beamforming to improve the signal strength and signal-to-interference-plus-noise ratio (SINR) of traffic in the air communication between the first repeater device 2906 and the network access node 2902. Additionally, the first repeater device 2906 may be aware of the direction of the traffic it receives (e.g., uplink, downlink, and flexible).

[0367] By way of illustration, in the context of time-division duplex (TDD) operation and multi-beam operation, Figure 29Depicts the first four time slots 2934 (time slots n-3, n-2, n-1, and n) of a resource grid. The first repeater device 2906 can obtain the directionality of each symbol in each of these four time slots 2934 by decoding cell-specific information transmitted by the network access node 2902. Thus, the first repeater device 2906 can know in advance the position in the time-frequency resource of each uplink (UL) symbol 2936, flexible symbol 2938, and downlink symbol 2940 in any given time slot 2934 in a frame (not shown). Knowing the direction (DL, flexible, UL) can allow the first repeater device 2906 to save power, for example, by receiving only in the direction of the UE (e.g., the first UE 2914) during resources reserved for uplink communication. In other words, the first repeater device 2906 can save power and enjoy other benefits by not transmitting in the direction of the UE (e.g., the first UE 2914) during resources reserved for uplink. During uplink resources, the first repeater device 2906 can use beamforming techniques to form a first directional beam 2908c in the direction of the first UE 2914 and a second directional beam 2908g in the direction of the network access node. The first repeater device 2906 can configure itself (in an open-loop manner) based on information received from the network access node 2902 without establishing an RRC connection with the network access node 2902. The first repeater device 2906 can configure itself, for example, by coupling the antennas of its (an) antenna array to the input and output ends of an amplifier chain respectively to amplify and forward uplink traffic (if any) from the first UE 2914 to the network access node 2902 in a directionally oriented configuration.

[0368] Similarly, the first repeater device 2906 can save power and enjoy other benefits by not transmitting in the direction of the network access node (e.g., network access node 2902) during the resources reserved for the downlink. During downlink resources, the first repeater device 2906 can use beamforming techniques to form a first directional beam 2908c in the direction of the first UE 2914 and a second directional beam 2908g in the direction of the network access node. The first repeater device 2906 can configure itself (in an open-loop manner) based on the information received from the network access node 2902 without establishing an RRC connection with the network access node 2902. The first repeater device 2906 can configure itself, for example, by coupling the antennas of its (plural) antenna arrays to the input and output ends of the amplifier chain respectively to amplify and forward the downlink traffic (if any) from the network access node 2902 to the first UE 2914 in a directionally oriented configuration. Generally, the first repeater device 2906 can be multi-beam adaptive over time and can be fully aware of the DL / UL split; that is, fully aware of which resources are scheduled for DL and which resources are scheduled for UL.

[0369] In contrast, the second repeater device 2918 may not decode any cell-specific information. The second repeater device 2918 can receive RF signal traffic via its omnidirectional beam 2920, pass the RF signal traffic through its amplifier chain (not shown), and transmit (e.g., forward) the amplified RF signal traffic via the omnidirectional beam 2920 of the second repeater device 2918. In addition, the second repeater device 2918 may not be aware of the direction of the RF signal traffic (e.g., UL, flexible, DL) because the second repeater device 2918 may not have obtained this information from any signaling from the network access node 2902.

[0370] By way of illustration, in the context of time-division duplex (TDD) operation and multi-beam operation, Figure 29Depicts the second four time slots 2930 (time slots n-1, n, n+1, and n+2) of the resource grid. From the perspective of the second repeater device 2918, each symbol in each of the second four time slots 2930 is an undetermined symbol 2942 (i.e., the second repeater device 2918 may not make an effort to determine whether any given symbol is reserved for downlink, flexible, or uplink resources). Thus, the second repeater device 2918 can always receive omnidirectionally and transmit omnidirectionally. This has at least one drawback, such as wasting the transmitted signal energy by directing the transmitted signal energy mainly to directions other than the second UE 2926. Regarding the second repeater device 2918, the backhaul link two-way communication with the network access node 2902 and the access link two-way communication with the second UE 2926 can always be transmitted and / or received via the omnidirectional beam 2920 of the second repeater device 2918.

[0371] Figure 30A and 30B Are diagrams 3000, 3001 that compare the cumulative distribution function (CDF) on the vertical axis and compare the data rate (in bits per second per hertz) on the horizontal axis depending on whether "side control information" is provided to the repeater device. As described above, the side control information can allow the repeater device to, for example, use a directional beam for the backhaul link and the access link, improve operation by having knowledge of the direction of resources on a per-symbol and / or per-time-slot basis (e.g., UL, flexible, DL), and adjust the transmitter power of the repeater device.

[0372] Some evaluations indicate that greater performance advantages can be obtained when the side control information becomes available compared to a repeater device without side control information. The advantages can be observed in, for example, timing information. Knowing the DL / UL split at the time slot and symbol levels can also provide an advantage. As another example, the side control information can provide spatial transmission and / or reception information. The transmission and / or reception information can be used to ensure that the directional transmission and reception beams are directed in a direction corresponding to the positions of each served UE and the network access node for each scheduled resource.

[0373] Figure 30A and 30B Depict traces (curves) without side control information 3002, 3003 and traces with side control information 3004, 3005. Figure 30A and 30B Also depict the minimum useful rate 3006, 3007. Figure 30A and 30B Depict the results of "indirect UEs", which are UEs served by the repeater device. Figure 30ADepicts the downlink (DL) rate of the indirect UE. Figure 30B Depicts the uplink (UL) rate of the indirect UE.

[0374] As used in Figure 30A and 30B the cumulative distribution function (CDF) is the probability (given on the vertical axis) that the UL or DL rate will take a value less than or equal to the rate given on the horizontal axis. For example, in Figure 30A for a CDF of 0.7 (i.e., a 70% probability), Chart 3000 indicates that there is a 70% probability that the DL rate of the indirect UE without side control information 3002 will be less than 0.9 bits / second / hertz, while for the same 70% probability, the DL rate of the indirect UE with side control information 3004 will be less than 6.2 bits / second / hertz. This represents a rate improvement of the indirect UE with side control information 3004 relative to the indirect UE without side control information 3002. By another example, in Figure 30A for a CDF of 0.5 (i.e., a 50% probability), Figure 3000 indicates that there is a 50% probability that the DL rate of the indirect UE without side control information 3002 will be less than 0 bits / second / hertz (i.e., the rate is less than the minimum useful rate 3006), while for the same 50% probability, the DL rate of the indirect UE with side control information 3004 will be less than 3.4 bits / second / hertz. This again represents a rate improvement of the indirect UE with side control information 3004 relative to the indirect UE without side control information 3002.

[0375] For the UL rate, for example, in Figure 30B for a CDF of 0.7 (i.e., a 70% probability), Chart 3001 indicates that there is a 70% probability that the UL rate of the indirect UE without side control information 3003 will be less than 0.5 bits / second / hertz, while for the same 70% probability, the UL rate of the indirect UE with side control information 3005 will be less than 4.4 bits / second / hertz. This represents a rate improvement of the indirect UE with side control information 3004 relative to the indirect UE without side control information 3002. By another example, in Figure 30B for a CDF of 0.5 (i.e., a 50% probability), Figure 3001 indicates that there is a 50% probability that the UL rate of the indirect UE without side control information 3003 will be less than 0 bits / second / hertz (i.e., the rate is less than the minimum useful rate 3007), while for the same 50% probability, the UL rate of the indirect UE with side control information 3005 will be less than 1.6 bits / second / hertz. This again represents a rate improvement of the indirect UE with side control information 3005 relative to the indirect UE without side control information 3003.

[0376] Figure 31 is a call flow diagram illustrating an example of signaling 3100 of a wireless communication network including a network access node 3102, a repeater device 3104, and a UE 3106, according to some aspects of the present disclosure. The network access node 3102 may correspond to Figure 1 , 2 , any one of the network access nodes (e.g., a scheduling entity, a gNB, a base station) shown in any of 5-12, 14-17, 25, 29, 31, 37, and / or 39-44. The repeater device 3104 may correspond to Figures 7 - 21 , any one of the RF repeater devices of 29, 31, 32, 37, 39, and / or 40. The UE 1406 may correspond to Figure 1 , 2 , any one of the UEs (e.g., a scheduled entity, a wireless communication device) shown in any of 5-12, 14-17, 29, 31, and / or 44.

[0377] In Figure 31 's example, the network access node 3102 may first broadcast master information blocks (MIBs) 3108a, 3108b. The repeater device 3104 and the UE 3106 may each receive the MIBs 3108a, 3108b. The MIBs 3108a, 3108b may be transmitted on a broadcast channel (BCH) transport channel and a physical broadcast channel (PBCH) physical channel. The MIBs 3108a, 3108b may include parameters required to decode system information block type 1 (SIB1) and other information. For example, the MIBs 3108a, 3108b may be used to convey information (such as side control information) from the network access node 3102 to the repeater device 3104. Some parameters carried by the MIB (such as MIB3108a, 3108b) may include, for example, the parameter "cellBarred", which can be used to notify a repeater device (such as the repeater device 3104) that a network access node (such as the network access node 3102) has prohibited one or more wireless communication devices (e.g., such as the UE 3106) from camping on the cell associated with the MIB. The cell barred parameter may indicate to the repeater device 3104 that one or more circuits of the repeater device 3104 may be configured not to convey radio frequency (RF) traffic received at the repeater device 3104 from one or more wireless communication devices (e.g., from the UE 3106) in the uplink resources associated with the cell.

[0378] The network access node 3102 may then broadcast other system information (OSI) 3112a, 3112b. The OSI 3112a, 3112b may include any one of SIB2 - SIB9. The repeater device 3104 and the UE 3106 may each receive the OSI 3112a, 3112b.

[0379] When the repeater device 3104 and the UE 3106 have all the relevant information, one or both of them may enter the contention - based random access procedure. The existing RACH procedure may be referred to as the 4 - step contention - based RACH procedure 3120. First, the UE 3106 may transmit a contention - based PRACH preamble, also referred to as Message 1 3124. After detecting the preamble, the network access node 3102 responds with a random access response (RAR) (also referred to as Message 2 3128). The RAR may include the detected preamble ID, a timing advance command, a temporary C - RNTI (TC - RNTI), and an uplink grant for scheduling a PUSCH transmission from the UE 3106. The UE transmits Message 3 3130 in response to the Message 2 3128 RAR including an ID for contention resolution. Message 3 3130 may also be referred to as an RRC connection request. Upon receiving Message 3 3130, the network access node 3102 transmits a contention resolution message with the contention resolution ID, also referred to as Message 4 3132. The UE 3106 receives Message 4 3132, and if the UE 3106 finds its contention resolution ID, it sends an acknowledgment on the physical uplink control channel (PUCCH), which completes the 4 - step random access procedure.

[0380] From the perspective of the repeater device 3104, the 4 - step contention - based RACH procedure 3120 is similar; however, if the repeater device 3104 enters the RACH procedure 3120, the repeater device 3104 may choose not to establish an RRC connection with the network access node 3102. Accordingly, an open - loop repeater device (such as the repeater device 3104) may not request (not request) an RRC connection 3134 and may not participate (not participate) in contention resolution.

[0381] In addition, the 4-step contention-based RACH procedure 3120 is optional for the repeater device 3104 (as indicated by the dashed lines of the repeater device 3104 message 1 3122 PRACH preamble and the network access node 3102 message 2 3126 RAR). However, the repeater device 3104 may find the first two steps of the 4-step contention-based RACH procedure 3120 useful for exchanging information with the network access node 3102. For example, the repeater device 3104 may use the message 1 3122 PRACH preamble to convey information upward to the network access node 3102, while the network access node 3102 may use the message 2 3126 RAR to convey information downward to the repeater device 3104. First, the UE 3106 may optionally transmit the message 1 3124 PRACH preamble to the network access node 3102. After detecting the preamble, the network access node 3102 may respond with the message 2 3126 RAR. The message 2 3126 RAR may include the detected preamble ID, timing advance command, temporary C-RNTI (TC-RNTI), and an uplink grant for scheduling PUSCH transmission from the repeater device 3104; however, if provided, the repeater device 3104 may not use the uplink grant.

[0382] In 5G, an alternative to the 4-step contention-based RACH procedure 3120 is available. The alternative may be referred to as the 2-step contention-based RACH procedure 3140. The 4-step RACH procedure utilizes, for example, two round-trip cycles between the UE 3106 and the network access node 3102. The 2-step contention-based RACH procedure 3140 can reduce the latency and control signaling overhead by using only one round-trip cycle between the UE 3106 and the network access node 3102 or between the repeater device 3104 and the network access node 3102. The round-trip reduction can be achieved by combining the message 1 and message 3 of the 4-step contention-based RACH procedure 3120 into a single message (referred to as message A).

[0383] The repeater device 3104 may optionally transmit the message A 3142 upward to the network access node 3102. The message A 3142 may include a PRACH preamble and other data. Of course, the UE 3106 may also transmit the message A 3144 upward to the network access node 3102. The network access node 3102 may respond to the repeater device 3104 with the message B 3146. The network access node 3102 may respond to the UE 3106 with the message B 3106. The messages B 3146, 3148 may include the content previously associated with the message 2 and message 4.

[0384] Figure 32FIG. is a schematic diagram illustrating an example of a hardware implementation of a repeater device 3200 employing a processing system 3214 in accordance with some aspects of the present disclosure. For example, the repeater device 3200 may be a device configured to wirelessly communicate with a network access node (e.g., a scheduling entity, a gNB, a base station), a user equipment (e.g., a UE, a scheduled entity, a wireless communication device), and / or a core network node, all as discussed in any one or more of Figures 1 - 55 In some implementations, the processing system 3214 may provide some or all of the functionality of the MT unit. In some implementations, the repeater device 3200 may correspond to any one of the RF repeater devices of Figures 7 - 21 29, 31, 32, 37, 39, and / or 40.

[0385] In accordance with various aspects of the present disclosure, an element, or any portion of an element, or any combination of elements may be implemented using the processing system 3214. The processing system 3214 may include one or more processors 3204. The processing system 3214 may be substantially similar to the processing system 2114 illustrated in Figure 21 , including a bus interface 3208, a bus 3202, a memory 3205, a processor 3204, and a computer-readable medium 3206. Additionally, the repeater device 3200 may include additional features such as an interface 3230, a transceiver 3210, an antenna / antenna array 3220, and / or a power supply 3228. The interface 3230, the transceiver 3210, the antenna / antenna array 3220, and the power supply 3228 may be coupled to the bus interface 3208. The stated features of the repeater device 3200 may be substantially similar to the similarly numbered and similarly named features of the repeater device 2100 of Figure 21 . Accordingly, to avoid repetition, the description in conjunction with Figure 32 does not provide a description of the similarly numbered and similarly named features that may still be present in the repeater device 3200.

[0386] In various examples, the repeater device 3200 may be configured to perform any one or more of the functions described herein in Figures 1 - 55 . That is, the processor 3204 as utilized in the repeater device 3200 may be used to implement any one or more of the processes and procedures described herein (e.g., in Figures 22 - 24 , 33 - 34, and / or 46 - 47). The processor 3204 as utilized in the repeater device 3200 may include circuitry configured for various functions.

[0387] For example, the processor 3204 may include communication and processing circuitry 3241. The communication and processing circuitry 3241 of the repeater device 3200 may be configured for various functions and processes and may include one or more hardware components that provide the physical structures for performing the various functions and processes related to wireless communication as described herein (e.g., signal reception and / or signal transmission). In conjunction with Figure 21 Some of the various functions, processes, and corresponding one or more hardware components described are similar to the various similarly named functions, processes, and corresponding one or more hardware components associated with the communication and processing circuitry 3241 of the repeater device 3200 of Figure 32 Accordingly, to avoid repetition, the description of the communication and processing circuitry 3241 in conjunction with Figure 32 does not provide a description of the various functions, processes, and corresponding one or more hardware components that may still be common (or substantially similar) to both the communication and processing circuitry 3241 of Figure 32 and the communication and processing circuitry 3241 of Figure 21 The communication and processing circuitry 3241 may further be configured to execute communication and processing software 3251 stored on the computer-readable medium 3206 to implement one or more of the functions described herein.

[0388] In some aspects of the present disclosure, the processor 3204 may include side control information decoding circuitry 3242, which is configured for various functions, including, for example, decoding cell-specific information received from a network access node. In some examples, the side control information decoding circuitry 3242 may include one or more hardware components that provide the physical structures for performing the processes related to decoding cell-specific information received from a network access node. The side control information decoding circuitry 3242 may further be configured to execute side control information decoding software 3252 stored on the computer-readable medium 3206 to implement one or more of the functions described herein.

[0389] In some aspects of the present disclosure, the processor 3204 may include a repeater device configuration circuitry 3243, which is configured for various functions, including, for example, configuring the repeater device 3200 using cell-specific information, or configuring the repeater device 3200 using cell-specific information without using the cell-specific information to establish a Radio Resource Control (RRC) connection with the network access node. In some examples, the repeater device configuration circuitry 3243 may include one or more hardware components that provide a physical structure for performing processes related to: configuring the repeater device using cell-specific information or configuring the repeater device 3200 using cell-specific information without using the cell-specific information to establish an RRC connection with the network access node. The repeater device configuration circuitry 3243 may further be configured to execute repeater device configuration software 3253 stored on a computer-readable medium 3206 to implement one or more of the functions described herein.

[0390] In some aspects of the present disclosure, the processor 3204 may include a System Information (SI) acquisition circuitry 3244, which is configured for various functions, including, for example, acquiring a Master Information Block (MIB), remaining minimum system information (RMSI) identified by the MIB, and / or system information transmitted in a System Information Block (SIB), the SIB including resources identified by at least one of the MIB or the remaining minimum system information (RMSI), where the RMSI may be different from the SIB. In some examples, the SI acquisition circuitry 3244 may include one or more hardware components that provide a physical structure for performing processes related to: acquiring the MIB, the RMSI identified by the MIB, and / or the system information transmitted in the SIB, the SIB including resources identified by at least one of the MIB or the RMSI, where the RMSI may be different from the SIB. The System Information (SI) acquisition circuitry 3244 may further be configured to execute System Information (SI) acquisition software 3254 stored on a computer-readable medium 3206 to implement one or more of the functions described herein.

[0391] In some aspects of the present disclosure, the processor 3204 may include downlink control information (DCI) format circuitry 3245 configured for various functions, including, for example, obtaining cell-specific information that is transmitted as the payload of a DCI format, and receiving a series of DCI formats to dynamically change the configuration of the repeater device. In some examples, the downlink control information (DCI) format circuitry 3245 may include one or more hardware components that provide the physical structure for performing processes related to obtaining cell-specific information that is transmitted as the payload of a DCI format, and receiving a series of DCI formats to dynamically change the configuration of the repeater device. The downlink control information (DCI) format circuitry 3245 may further be configured to execute downlink control information (DCI) format software 3255 stored on a computer-readable medium 3206 to implement one or more of the functions described herein.

[0392] In some aspects of the present disclosure, the processor 3204 may include random access channel (RACH) processing circuitry 3246 configured for various functions, including, for example, transmitting a predetermined RACH preamble associated with a synchronization signal block (SSB) that identifies the direction of relayed radio traffic (e.g., UL, flexible, DL), where a network access node may convey information to the repeater device in a RACH response to the predetermined RACH preamble. In some examples, the predetermined RACH preamble may be one of a plurality of predetermined RACH preambles associated with respective information pre-established to convey the respective information from the repeater device to the network access node. In yet another example, the repeater device may determine the identity of the respective information to be conveyed to the network access node by selecting one of the plurality of predetermined RACH preambles. In some examples, the RACH processing circuitry 3246 may include one or more hardware components providing a physical structure for performing processes associated with: transmitting a predetermined RACH preamble associated with a synchronization signal block (SSB) that identifies the direction of relayed radio traffic (e.g., UL, flexible, DL), where a network access node may convey information to the repeater device in a RACH response to the predetermined RACH preamble. In some examples, the predetermined RACH preamble may be one of a plurality of predetermined RACH preambles associated with respective information pre-established to convey the respective information from the repeater device to the network access node. In yet another example, the repeater device may determine the identity of the respective information to be conveyed to the network access node by selecting one of the plurality of predetermined RACH preambles. The RACH processing circuitry 3246 may further be configured to execute RACH processing software 3256 stored on a computer-readable medium 3206 to implement one or more functions described herein.

[0393] In some aspects of the present disclosure, the processor 3204 may include power measurement circuitry 3247 configured to perform various functions, including, for example, measuring the power of resources in an access link in at least one of: a measurement window configured by the network access node, or within a resource set configured by the network access node. Additionally, the power measurement circuitry 3247 may be configured to measure the power level of a broadcast channel carrying cell-specific information from a given network access node; compare the power level to a predetermined low threshold and a predetermined high threshold; and configure the repeater device based on the comparison. Additionally, the power measurement circuitry 3247 may configure the repeater device to convey the radio frequency traffic when the power level is greater than the predetermined low threshold and less than the predetermined high threshold. In some examples, the power measurement circuitry 3247 may include one or more hardware components providing a physical structure for performing processes associated with measuring the power of resources in an access link in at least one of: a measurement window configured by the network access node, or within a resource set configured by the network access node. Additionally, the power measurement circuitry 3247 may include one or more hardware components providing a physical structure for performing processes associated with measuring the power level of a broadcast channel carrying the cell-specific information from a given network access node; comparing the power level to a predetermined low threshold and a predetermined high threshold; and configuring the repeater device based on the comparison. Additionally, the power measurement circuitry 3247 may include one or more hardware components providing a physical structure for performing processes associated with configuring the repeater device to convey the radio frequency traffic when the power level is greater than the predetermined low threshold and less than the predetermined high threshold. The power measurement circuitry 3247 may further be configured to execute power measurement software 3257 stored on a computer-readable medium 3206 to implement one or more of the functions described herein.

[0394] Figure 33 FIG. 3300 (e.g., method) at a repeater device in a wireless communication network in accordance with some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some of the illustrated features may not be required to implement all examples. In some examples, process 3300 may be performed by Figure 32 the repeater device 3200 illustrated in FIG. In some examples, process 3300 may be performed by any suitable apparatus or device for performing the functions or algorithms described herein.

[0395] At block 3302, the repeater device may decode cell-specific information received from a network access node. For example, as described above in connection with Figure 32The side control information decoding circuitry 3242 as shown and described, together with the transceiver 3210 and the antenna / antenna array 3220, can provide means for decoding the cell-specific information received from the network access node.

[0396] At block 3304, the repeater device can use the cell-specific information to configure itself (i.e., configure the repeater device). At block 3305, the repeater device can use the cell-specific information to configure itself (i.e., configure the repeater device) without establishing a radio resource control (RRC) connection with the network access node. For example, the repeater device configuration circuitry 3243 can provide means for using the cell-specific information to configure itself (e.g., configure the repeater device) and / or can provide means for using the cell-specific information to configure itself (i.e., configure the repeater device) without establishing a radio resource control (RRC) connection with the network access node. Block 3304 and block 3305 can be alternatives to each other.

[0397] At block 3306, the repeater device can forward signals between the first wireless communication device and the second wireless communication device according to the configuration. In one example, the network access node can be one of the first wireless communication device or the second wireless communication device. For example, as described above in connection with Figure 32 The communication and processing circuitry 3241 as shown and described, together with the transceiver 3210 and the antenna / antenna array 3220, can provide means for forwarding signals between the first wireless communication device and the second wireless communication device according to the configuration.

[0398] In some examples, the network access node can be one of the first wireless communication device or the second wireless communication device. The cell-specific information received from the network access node can be beam-specific information. The cell-specific information can be specific to a single repeater device or a group of repeater devices. In some aspects, the cell-specific information can be received on a specific beam directed to the location of the repeater device. In some aspects, the cell-specific information can be valid for a given time period or for an upcoming limited set of resources.

[0399] According to some aspects, the exemplary process 3300 at the repeater device in the wireless communication network can further include periodically verifying the cell-specific information by at least one of the following operations: obtaining new cell-specific information, reacquiring the previous decoded cell-specific information, or rereading the decoded cell-specific information received from the network access node. The exemplary process 3300 can include setting a timer to trigger the periodic verification of the cell-specific information.

[0400] According to some examples, the cell-specific information may be transmitted from the network access node and used to establish an RRC connection between the network access node and the wireless communication device. However, in some examples, the cell-specific information may not be used to establish an RRC connection between the repeater device and the network access node. In some examples, the signals forwarded by the repeater device may be beamformed. In some examples, these signals forwarded by the repeater device may be in analog form and have not been processed into digital form at intermediate frequency or baseband in the repeater device. In some examples, the cell-specific information may provide resource and configuration information for receiving repeater device control information. The resource information may include a time division duplex mode (TDD mode), repeater device switch information, frequency information of the network access node, or a combination thereof. The frequency information may be at least one of the following: for example, center frequency information, or channel bandwidth. In some examples, the cell-specific information may include information on limitations of unwanted transmissions.

[0401] In some examples, the cell-specific information may be system information, which may be transmitted in the master information block (MIB), in the remaining minimum system information (RMSI) identified by the MIB, and / or in a system information block (SIB) message specific to the repeater device. The cell-specific information may be, for example, system information that may be transmitted in a system information block (SIB), the SIB including resources identified by at least one of the master information block (MIB) or the remaining minimum system information (RMSI), where the RMSI is not the SIB. In another example, the cell-specific information may be transmitted as the payload of a downlink control information (DCI) format or a medium access control - control element (MAC-CE). The DCI may be group common DCI, and the DCI format may be associated with a synchronization signal block (SSB) or a beamforming configuration. In one example, the repeater device may also receive a series of DCI formats to dynamically change the configuration of the repeater device.

[0402] In one example, the repeater device may be one of a plurality of repeater devices arranged in a plurality of different respective directions relative to the network access node. The first repeater device among the plurality of repeater devices may receive a first DCI format message that configures the first repeater device among the plurality of repeater devices to disable repeater device reception and transmission, and the second repeater device among the plurality of repeater devices may receive a second DCI format message that configures the second repeater device among the plurality of repeater devices to enable repeater device reception and transmission.

[0403] According to some aspects, at least one of the following is performed: the cell-specific information can be broadcast to a plurality of repeater devices including the repeater device or the cell-specific information can be provided as a group common configuration to the plurality of repeater devices including the repeater device.

[0404] In one example, the cell-specific information can be repeater device-specific control information (referred to herein as repeater device control information). The repeater device-specific control information can be transmitted as a payload of a downlink control information (DCI) format associated with a common radio network temporary identifier (RNTI) that differentiates the DCI format from other DCI formats associated with other RNTIs associated with these wireless communication devices.

[0405] There may be regulatory rules and / or guidelines regarding unwanted emissions from wireless devices in various countries or regions of the world. Transmissions from repeater devices (such as those exemplified herein) may be subject to these regulatory rules and / or guidelines. The repeater device can be configured to increase or decrease the transmit power to remain in compliance with the local unwanted emission limits specified in such regulatory rules and / or guidelines. For example, the unwanted emission limits can be provided per frequency or frequency band. According to one example, the repeater device can receive a message conveying unwanted emission limit information. The message can be sent by a network access node to the repeater device. The message can allow network control of the unwanted emissions of the repeater device. In one example, in the case where the repeater device receives cell-specific information from a network access node, the cell-specific information can include unwanted emission limit information. The repeater device receiving such cell-specific information can be configured to increase and / or decrease its transmit power to keep the transmit power of the repeater device at or below the limit specified in the received unwanted emission limit information.

[0406] In one aspect, the repeater device can be a Layer 1 repeater unit. In another aspect, the repeater device can be identified with a predetermined RACH preamble and / or resource that may be different from the random access channel (RACH) preamble and / or resource of a wireless communication device. According to this aspect, process 3300 can further include transmitting a predetermined RACH preamble and / or a predetermined resource associated with a synchronization signal block (SSB), where the SSB identifies the direction of the relayed radio traffic (e.g., UL, flexible, DL). In this aspect, the network access node can convey information to the plurality of repeater devices in a RACH response to the predetermined random access channel (RACH) preamble and / or the predetermined resource. The predetermined RACH preamble and / or the predetermined resource can be one of a plurality of predetermined RACH preambles and / or predetermined resources associated with a plurality of respective information, pre-established to convey the respective information from the repeater device to the network access node. In this aspect, the repeater device can determine the identity of the respective information to be conveyed to the network access node by selecting one of the plurality of predetermined RACH preambles and / or predetermined resources. In one example, the information can correspond to at least one of the following: the power configuration of the repeater device, or the measured power of a resource in the access link. The measured power of the resource in the access link can be measured in at least one of the following: a measurement window configured by the network access node, or within a resource set configured by the network access node.

[0407] In one example, the repeater device can convey information to the network access node by at least one of the following: selecting a predetermined RACH preamble and / or a predetermined resource, including the information in the payload of a first RACH message, including the information in the payload of a third RACH message, or setting the transmitter power of the repeater device to one of a plurality of predetermined transmitter power levels, where each of the plurality of predetermined transmitter power levels conveys a different respective information segment. In some aspects, the network access node can convey information to the repeater device in one of a RACH response or a fourth RACH message.

[0408] According to one aspect, a change to the configuration of the repeater device can be made without establishing a control interface between the repeater device and the network access node. That is, an RRC connection can not be established between the repeater device and the network access node.

[0409] According to another aspect, the repeater device may configure itself (e.g., the repeater device may be configured to) convey radio frequency traffic received at the repeater device according to a control signal of the cell-specific information. The control signal may be broadcast from the network access node and exclusively directed to a plurality of repeater devices including the repeater device within the broadcast reception range of the network access node. The control signal may configure the plurality of repeater devices not to convey radio frequency traffic associated with the cell. In one aspect, the control signal may provide an indication that varies according to a Synchronization Signal Block (SSB) (varies according to the SSB), where the repeater device may determine whether to convey or not convey based on the detected SSB from the network access node and the provided indication that varies according to the SSB. In one aspect, the control signal may instruct the network access node transmitting the cell-specific information to prohibit one or more wireless communication devices (e.g., one or more UEs) from camping on the cell associated with the cell-specific information. In this example, the repeater device (e.g., one or more circuits of the repeater device) may configure itself (i.e., the repeater device) not to convey radio frequency traffic received at the repeater device from one or more wireless communication devices in the uplink resources associated with the cell. In this example, the repeater device may determine the Synchronization Signal Block (SSB) index value associated with the control signal, and configure the output power of the transmitter of the repeater device according to the SSB index value. According to some aspects, the repeater device may configure the output power of the repeater device by at least one of the following: configuring the maximum output power of the transmitter, configuring the maximum amplification gain of the transmitter, or configuring the first power assigned to the first traffic transmitted in the uplink and the second power assigned to the second traffic transmitted in the downlink, where the first power is different from the second power. In some examples, the repeater device may configure itself not to convey radio frequency traffic received at the repeater device associated with the SSB index value in the uplink resources associated with the cell. In this example, the repeater device may additionally determine the Synchronization Signal Block (SSB) index value associated with the control signal; map the SSB index value to one of a plurality of beams of the network access node according to a predetermined mapping relationship; and configure the repeater device not to convey radio frequency traffic received at the repeater device in the resources associated with one of the plurality of beams. In one aspect, the repeater device may further measure the power level of the broadcast channel carrying the cell-specific information from a given network access node; compare the power level with a predetermined low threshold and a predetermined high threshold; and configure the repeater device (i.e., configure itself) based on the comparison. In one aspect, the repeater device may configure the repeater device to convey the radio frequency traffic when the power level is greater than the predetermined low threshold and less than the predetermined high threshold.Further, the repeater device can determine a synchronization signal block (SSB) index value associated with the control signal, and configure the repeater device (i.e., configure itself) to convey radio traffic associated with the SSB index value in an uplink resource.

[0410] In some aspects, the repeater device can further determine a synchronization signal block (SSB) index value associated with the cell-specific information, and configure the transmitter of the repeater device based on the SSB index value. In some examples, configuring the transmitter can further include at least one of the following: configuring the transmitter with a maximum transmitter output power, configuring the transmitter with a maximum amplification gain, or configuring a first power assigned to the first traffic transmitted in the uplink and a second power assigned to the second traffic transmitted in the downlink, where the first power is different from the second power. Configuring the transmitter can further include at least one of the following: configuring the transmitter with a maximum transmitter output power, or configuring the transmitter with a maximum amplification gain.

[0411] In one example, the cell-specific information can indicate resources of at least one symbol in at least one time slot, and using the cell-specific information to configure the repeater device further includes: configuring the repeater device to exclusively convey traffic in the indicated resources during the at least one symbol in the at least one time slot. In another example, the resources can be at least one of an uplink resource, a downlink resource, or a flexible resource, and the repeater device can further replace the flexible resource with the uplink resource or the downlink resource according to control information or control configuration signaling received by the repeater device.

[0412] Figure 34 is a flowchart illustrating an exemplary process 3400 (e.g., method) at a repeater device in a wireless communication network according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some of the illustrated features may not be required to implement all examples. In some examples, process 3400 can be performed by Figure 32 the repeater device 3200 illustrated in. In some examples, process 3400 can be performed by any suitable equipment or device for performing the functions or algorithms described herein.

[0413] In block 3402, the repeater device can decode the cell-specific information received from the network access node to obtain at least one of a measurement window or a resource set. For example, as described above in connection with Figure 32The side control information decoding circuit system 3242 as shown and described, together with the transceiver 3210 and the antenna / antenna array 3220, can provide means for decoding the cell-specific information received from the network access node.

[0414] At block 3404, the repeater device can measure the direction-dependent power received during at least one of the measurement window or the resource set. For example, as described above in connection with Figure 32 The power measurement circuit system 3247 as shown and described, together with the transceiver 3210 and the antenna / antenna array 3220, can provide means for measuring the direction-dependent power received during at least one of the measurement window or the resource set.

[0415] At block 3406, the repeater device can configure the downlink resources of the repeater device based on the received power. For example, as described above in connection with Figure 32 The repeater device configuration circuit system 3243 as shown and described, together with the communication and processing circuit system 3241, can provide means for configuring the downlink resources of the repeater device based on the received power.

[0416] At block 3408, the repeater device can forward signals between the first wireless communication device and the second wireless communication device according to the configuration. For example, as described above in connection with Figure 32 The communication and processing circuit system 3241 as shown and described, together with the transceiver 3210 and the antenna / antenna array 3220, can provide means for forwarding signals between the first wireless communication device and the second wireless communication device according to the configuration. In one example, the network access node is one of the first wireless communication device or the second wireless communication device.

[0417] According to one aspect, the repeater device can compare the received direction-dependent power with a predetermined threshold. Subsequently, the repeater device can configure the downlink resources in at least one beam corresponding to at least one direction in which the received power is less than the predetermined threshold.

[0418] In one example, the repeater device can be a layer 1 repeater unit. In another example, a change to the configuration of the repeater device can be made in the absence of an RRC configuration established between the repeater device and any network access node including the network access node. In yet another example, at least one of the measurement window or the resource set is conveyed to the repeater device in control signaling in a random access channel (RACH) configuration that varies depending on the repeater device. The RACH configuration that varies depending on the repeater device can be broadcast from the network access node and is exclusively directed to a plurality of repeater devices including the repeater device within the broadcast reception range of the network access node. In some examples, the repeater device can be identified with a predetermined RACH preamble and / or predetermined resources.

[0419] Figure 35 FIG. is a schematic diagram illustrating an example of a hardware implementation of a network access node 3500 (e.g., a scheduling entity, gNB, base station) employing a processing system 3514 in accordance with some aspects of the present disclosure. For example, the network access node 3500 can be a device configured to wirelessly communicate with a scheduled entity, UE, wireless communication device, other network access nodes, repeater devices, and / or IAB nodes, as discussed in any one or more of Figures 1 - 15 In some implementations, the network access node 3500 can correspond to Figure 1 , 2 , 5 - 12, 14 - 17, 25, 29, 31, 37, and / or any network access node among the network access nodes (e.g., scheduling entity, gNB, base station) shown in any one of 39 - 44.

[0420] In accordance with various aspects of the present disclosure, an element, or any part of an element, or any combination of elements can be implemented using the processing system 3514. The processing system 3514 can include one or more processors 3504. The processing system 3514 can be substantially the same as the processing system 2514 illustrated in Figure 25 (or the processing system 2114 illustrated in Figure 21 ), including a bus interface 3508, a bus 3502, a memory 3505, a processor 3504, and a computer-readable medium 3506. Additionally, the network access node 3500 can include additional features such as an interface 3530, a transceiver 3510, an antenna / antenna array 3520, and / or a power supply 3528. The interface 3530, the transceiver 3510, the antenna / antenna array 3520, and the power supply 3528 can be coupled to the bus interface 3508. The stated features of the network access node 3500 can be substantially similar to the similarly numbered and similarly named features of the network access node 2500 in Figure 25 (or Figure 21(similar numbered and similarly named features of the repeater device 2100). Accordingly, to avoid repetition, the description in conjunction with Figure 35 does not provide a description of similarly numbered and similarly named features that may still be present in the network access node 3500.

[0421] The transceiver 3510 in combination with one or more antennas / antenna arrays 3520 can provide means for communicating with various other devices over a wireless transmission medium. The interface 3530 can provide a communication interface or means for communicating with various other devices and equipment (e.g., other devices housed within the same equipment as the network access node 3500 or other external devices) over an internal bus or an external transmission medium such as an Ethernet cable. Depending on the characteristics of the equipment, the interface 3530 may include a user interface (e.g., keypad, display, speaker, microphone, joystick, control features, etc.). Of course, such a user interface is optional and may be omitted in some examples. [0...

Claims

1. A method for wireless communication at a repeater device in a wireless communication network, the method comprising: Receive a first configuration specifying a first number of synchronization signal blocks (SSBs) to be transmitted by the repeater device; Select to transmit the SSBs using a second number of beams, wherein the second number of beams is less than or equal to the first number of SSBs; Receive at least one SSB transmission; And Transmit the at least one SSB transmission via the second number of beams.

2. A repeater device, comprising: Repeater unit; Memory; And A processor communicatively coupled to the repeater unit and the memory, wherein the processor is configured to: Receive a first configuration specifying a first number of synchronization signal blocks (SSBs) to be transmitted by the repeater unit of the repeater device; Select to transmit the SSBs using a second number of beams, wherein the second number of beams is less than or equal to the first number of SSBs; Receive at least one SSB transmission; And Transmit the at least one SSB transmission via the second number of beams.

3. A method for wireless communication at a network access node in a wireless communication network, the method comprising: Generate a first configuration indicating a first number of synchronization signal blocks (SSBs) to be transmitted by a repeater device; Transmit the first configuration to the repeater device; Determine that the repeater device is transmitting fewer than all of the first number of SSBs; Generate a second configuration after determining that the repeater device is transmitting fewer than all of the first number of SSBs, the second configuration indicating a second number of SSBs to be transmitted by the repeater device; And Transmit the second configuration to the repeater device.

4. A network access node, comprising: Transceiver; Memory; And A processor communicatively coupled to the transceiver and the memory, wherein the processor is configured to: Generate a first configuration indicating a first number of synchronization signal blocks (SSBs) to be transmitted by a repeater device; Transmit the first configuration to the repeater device via the transceiver; Determine that the repeater device is transmitting fewer than all of the first number of SSBs; Generate a second configuration after determining that the repeater device is transmitting fewer than all of the first number of SSBs, the second configuration indicating a second number of SSBs to be transmitted by the repeater device; And Transmit the second configuration to the repeater device via the transceiver.

Images