Network control repeater device, method, and network including the same

Abstract

To provide repeater devices, methods and parent nodes to enable smart repeaters to perform functions and capabilities that are not yet realized or specified.SOLUTION: In a telecommunications system 20, a repeater node wirelessly communicates with a parent node and another node. The repeater node comprises receiver circuitry, processor circuitry, and transmitter circuitry. The receiver circuitry receives a frame of information from the parent node. The processor circuitry includes a customized control signal in the frame of information received from the parent node. The customized control signal is customized for the repeater node. The transmitter circuitry transmits the frame of information which includes the customized control signal to the other node which may be a wireless terminal.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] This technology relates to the wireless architecture and operation of wireless communication, particularly wireless relay networks including a type of relay node called a repeater.

Background Art

[0002] Typically, a wireless access network exists between a wireless device such as a user equipment (UE), a mobile phone, a mobile station, or any other device having a wireless terminal, and a core network. Examples of wireless access network types include GRAN (GSM wireless access network), GERAN including EDGE packet radio service, UTRAN (UMTS wireless access network), E-UTRAN including Long Term Evolution, and g-UTRAN, New Radio (NR).

[0003] A wireless access network may include one or more parent nodes, such as a base station node that facilitates wireless communication or provides an interface between a wireless terminal and an electric communication system. Non-limiting examples of base stations include NodeB ("NB"), eNodeB ("eNB"), Home eNodeB ("HeNB"), gNB (for New Radio ["NR"] technology systems), or some other similar technical terms depending on the type of wireless access technology.

[0004] The Third Generation Partnership Project ("3GPP") is a group that develops collaborative agreements, such as 3GPP standards, which aim to define globally applicable technical specifications and technical reports for wireless communication systems. Various 3GPP documents can describe specific aspects of radio access networks. The overall architecture of the fifth-generation system, also known as "NR" or "New Radio," and "NG" or "Next Generation," is shown in Figure 1 and is also described in 3GPP TS38.300. A 5G NR network consists of the NG RAN (Next Generation Radio Access Network) and the 5GC (5G Core Network). As shown, the NG RAN consists of gNBs (e.g., 5G base stations) and ng-eNBs (i.e., LTE base stations). Xn interfaces exist between gNBs-gNBs, (gNB)-(ng-eNB), and (ng-eNB)-(ng-eNB). Xn is the network interface between NG-RAN nodes. Xn-U represents the Xn user plane interface, and Xn-C represents the Xn control plane interface. The NG interface exists between the 5GC and the base station (i.e., the gNB and the ng-eNB). The gNB node provides NR user plane and control plane protocol termination to the UE and connects to the 5GC via the NG interface. The 5G NR (New Radio) gNB connects to the AMF (Access and Mobility Management Function) and UPF (User Plane Function) of the 5GC (5G core network).

[0005] In some cellular mobile communication systems and networks, such as Long-Term Evolution (LTE) and New Radio (NR), the service area is covered by one or more base stations, each of which may be connected to the core network by a fixed line backhaul link, such as fiber optic cable. In some examples, weak signals from base stations at the edge of the service area tend to cause users to experience performance problems such as reduced data rates and a high probability of link failure. The concept of relay nodes has been introduced to extend the coverage area and improve signal quality. To implement this, relay nodes may be connected to base stations using wireless backhaul links.

[0006] The Third Generation Partnership Project (3GPP) is discussing and standardizing the relay node concept for fifth-generation (5G) cellular systems. Relay nodes can utilize the same 5G radio access technology, such as New Radio (NR), to provide services to user equipment (UE) (access links) and simultaneously connect to the core network (backhaul link). These radio links can be multiplexed in time, frequency, and / or space. This system may be referred to as Integrated Access Backhaul (IAB).

[0007] Some such cellular mobile communication systems and networks may include IAB donors and IAB nodes, where the IAB donor can provide an interface to the core network for the UE and wireless backhaul capabilities to the IAB node. In addition, the IAB node can provide IAB functionality combined with wireless self-backhaul capabilities. IAB nodes may need to periodically perform inter-IAB node discovery to detect new IAB nodes in their vicinity based on cell-specific reference signals, such as synchronization signals and PBCH block SSBs. Cell-specific reference signals may be broadcast on a physical broadcast channel (PBCH), where packets may be carried or broadcast on a Master Information Block (MIB) section.

[0008] A radio frequency (RF) repeater is a type of relay node. A repeater node simply amplifies and forwards any signal it receives. Recently, 3GPP Item Description Draft Document RP-212703 has been proposed for 3GPP RAN1, which concerns the specification of smart repeaters. Where used herein, the term "smart repeater" is used interchangeably with "network controlled repeater" or "NCR".

[0009] Regarding smart repeaters, the 3GPP draft document RP-212703, which explains the items under consideration, states the following: A smart repeater is an extension of a conventional RF repeater that has the ability to receive and process side control information from the network. This side control information can enable the smart repeater to perform its amplification and transmission operations in a more efficient manner. Potential benefits may include mitigation of unwanted noise amplification, transmission and reception with better spatial directivity, and simplified network integration.

[0010] As RP-212703 points out, an integrated access backhaul node is a type of repeater. When describing various scenarios and assumptions, RP-212703 states the following: Smart repeaters are in-band RF repeaters used to extend network coverage on the FR1 and FR2 bands, but during consideration, FR2 deployment may be prioritized for both outdoor and O2I scenarios. - For single-hop fixed smart repeaters only - Smart repeaters are transparent to the UE (Unified User Interface). - Smart repeaters can maintain both gNB-repeater links and repeater-UE links simultaneously. Note 1: Cost efficiency is a key consideration for smart repeaters. ...A smart repeater, including the assumption of maximum transmit power [RAN1], requires the following side control information. - Beamforming information - Timing information for aligning the transmit / receive boundary of the smart repeater - Information regarding UL-DL TDD configuration - On / off information and improved energy efficiency for efficient interference management - Power control information for efficient interference management (as a second priority) L1 / L2 signaling (including its configuration) for carrying side control information [RAN1]

[0011] In the above, FR1 is understood to be a carrier frequency range up to 6 GHz, and FR2 is a frequency range up to 70 GHz. "UL" and "DL" refer to the uplink and downlink, respectively, "TDD" refers to time-division duplexing, and "O2I" refers to "outdoor to indoor".

[0012] What is needed are methods, apparatus, and / or technologies to enable smart repeaters to perform functions and capabilities that have not yet been realized or specified. [Overview of the project]

[0013] In one of its exemplary embodiments, the technology described herein relates to a repeater node in a telecommunications network that communicates wirelessly with a parent node and other nodes. In a basic exemplary embodiment and mode, the repeater node comprises a receiver circuit, a processor circuit, and a transmitter circuit. The receiver circuit is configured to receive frames of information from the parent node. The processor circuit is configured to include customized control signals within the frames of information received from the parent node. The customized control signals are customized for the repeater node. The transmitter circuit is configured to transmit frames of information containing the customized control signals to other nodes that may be wireless terminals. Exemplary methods for operating such a repeater node are also described.

[0014] In another exemplary embodiment, the technology described herein relates to a parent node of a telecommunications network that communicates wirelessly with repeater nodes. In a basic exemplary embodiment and mode, the parent node comprises a processor circuit and a transmitter circuit. The processor circuit is configured to allocate available radio resources to the repeater nodes. The available radio resources are suitable for inclusion by the repeater nodes of customized control signals. The customized control signals are customized for the repeater nodes. The transmitter circuit is configured to transmit frames of information containing the available radio resources to the repeater nodes. An exemplary method for operating such a parent node is also described. [Brief explanation of the drawing]

[0015] The aforementioned and other objectives, features, and advantages of the technology disclosed herein will become apparent from the following more specific description of preferred embodiments, as shown in the accompanying drawings. In the drawings, reference letters refer to the same parts across the various drawings. The drawings are not necessarily to scale, but rather are intended to illustrate the principles of the technology disclosed herein.

[0016] [Figure 1] This is a diagram illustrating the overall architecture of the 5G New Radio system.

[0017] [Figure 2] This diagram shows, in a simplified form, a telecommunications system comprising a parent node and smart repeater nodes in exemplary embodiments and modes, illustrating various exemplary and representative aspects of the technology described herein.

[0018] [Figure 3] Figure 2 is a schematic diagram showing the general structure of a parent node, smart repeater node, and wireless terminal according to an exemplary embodiment and mode.

[0019] [Figure 4] For example, it is a schematic diagram showing how an example of the general structure of the parent node and repeater node of the general exemplary embodiment and mode of FIG. 3 can be implemented according to a distributed architecture.

[0020] [Figure 5] It is a schematic diagram showing in more detail exemplary components and functions of the parent node, smart repeater node, and wireless terminal of the exemplary, non-exhaustive, and implementation-based telecommunications system of FIGS. 2, 3, and / or 4.

[0021] [Figure 6] It is a flowchart showing exemplary, non-limiting, and basic operations or steps that can be performed by the repeater node and mode of one or more exemplary embodiments of FIGS. 2, 3, 4, and FIG. 5.

[0022] [Figure 7] It is a flowchart showing exemplary, non-limiting, and basic operations or steps that can be performed by the parent node and mode of one or more exemplary embodiments of FIGS. 2, 3, 4, and FIG. 5.

[0023] [Figure 8] It is a diagram showing the protocol stack of the control plane of the repeater node, wireless terminal, and parent node of the technology described in this specification.

[0024] [Figure 9] It is a diagram showing a resource grid that can form the basis of the frame described in this specification and New Radio as described by 3GPP TS38.211 v16.7.0.

[0025] [Figure 10] It is a simplified schematic diagram of functions that can be used by a smart repeater node to extract a control signal and replace the control signal with a repeater-customized control signal.

[0026] [Figure 11] This diagram illustrates exemplary elements comprising an electromachine that may include a wireless terminal, a wireless master node, and a core network node, according to exemplary embodiments and modes. [Modes for carrying out the invention]

[0027] In the following descriptions, specific details such as particular architectures, interfaces, and techniques are given for illustrative purposes, not limitation, to provide a complete understanding of the technology disclosed herein. However, those skilled in the art will recognize that the technology disclosed herein can also be practiced in other embodiments that deviate from these specific details. That is, those skilled in the art may devise various configurations that are not explicitly described or shown herein but embody the principles of the technology disclosed herein and fall within its spirit and scope. In some cases, detailed descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the technology disclosed herein with unnecessary details. All descriptions herein, including the principles, aspects, and embodiments of the technology disclosed herein and specific examples thereof, are intended to encompass both structural and functional equivalents. In addition, such equivalents are intended to include currently known equivalents as well as equivalents to be developed in the future, i.e., any developed elements that perform the same function regardless of their structure.

[0028] Accordingly, those skilled in the art will recognize, for example, that block diagrams in this specification can represent conceptual diagrams of exemplary circuits or other functional units embodying the principles of the present art. Similarly, it will be understood that any flowchart, state transition diagram, pseudocode, etc., can be substantially represented in a computer-readable medium and, therefore, represent various processes that can be performed by a computer or processor, whether or not such computer or processor is explicitly indicated.

[0029] As used herein, the term “core network” may refer to a device, group of devices, or subsystem within a telecommunications network that provides services to users of the telecommunications network. Examples of services provided by the core network include aggregation, authentication, call switching, service invocation, and gateways to other networks.

[0030] As used herein, the term “wireless terminal” can refer to any electronic device used to communicate voice and / or data by a telecommunications system such as a cellular network (but not limited to). Other technical terms used to refer to wireless terminals and non-exclusive examples of such devices include user equipment terminal, UE, mobile station, mobile device, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, subscriber unit, cellular phone, smartphone, personal digital assistant ("PDA"), laptop computer, tablet, netbook, e-reader, wireless modem, and the like.

[0031] As used herein, the terms “parent node,” “node,” or “base station” may refer to any device or group of devices that facilitate wireless communication or otherwise provide an interface between a wireless terminal and a telecommunications system. Non-exclusive examples of base stations include, in the 3GPP specification, NodeB ("NB"), Extended NodeB ("eNB"), Home eNB ("HeNB"), gNB (for New Radio ["NR"] technology systems), or several other similar technical terms.

[0032] As used herein, the terms “telecommunications system” or “communication system” may refer to any network of devices used to transmit information. Non-limiting examples of telecommunications systems include cellular networks or other wireless communication systems.

[0033] As used herein, the terms “cellular network” or “cellular radio network” may refer to a network distributed across multiple cells, where each cell is serviced by at least one fixed-location transceiver, such as a base station. A “cell” can be any communication channel specified by a standards-setting or regulatory body used by International Mobile Telecommunications-Advanced ("IMT Advanced"). All or a subset of cells may be adopted by 3GPP as licensed bands (e.g., frequency bands) used for communication between base stations, such as NodeB, and UE terminals. A cellular network using licensed frequency bands may include configured cells. A “configured cell” may include cells that are recognized by UE terminals and authorized by base stations to transmit or receive information. Examples of cellular radio access networks include E-UTRAN and any successors thereto (e.g., NUTRAN).

[0034] In this specification, any reference to “resource” means “radio resource” unless the context makes it clear that a different meaning is intended. Generally as used herein, a radio resource ("resource") is a unit of time-frequency capable of carrying information, for example, signal information or data information, over a radio interface.

[0035] An example of a wireless resource typically arises in the context of an information "frame," which is formatted and prepared by a node, for example. In Long-Term Evolution (LTE), a frame, which may have both a downlink portion (one or more) and an uplink portion (one or more), is communicated between a base station and a wireless terminal. Each LTE frame can have multiple subframes. For example, in the time domain, a 10ms frame consists of 10 1-millisecond subframes. LTE subframes are divided into two slots (thus, there are 20 slots in one frame). The transmitted signal in each slot is described by a resource grid consisting of resource elements (REs). Each column of the two-dimensional grid represents a symbol (e.g., an OFDM symbol on the downlink (DL) from the node to the wireless terminal, or an SC-FDMA symbol in the uplink (UL) frame from the wireless terminal to the node). Each row of the grid represents a subcarrier. A resource element (RE) is the smallest time-frequency unit of downlink transmission in a subframe. In other words, one symbol on one subcarrier in a subframe has a resource element (RE) uniquely defined by an index pair (k,l) in the slot (where k and l are indices in the frequency and time domains, respectively). To put it another way, one symbol on one subcarrier is a resource element (RE). Each symbol contains several subcarriers in the frequency domain, depending on the channel bandwidth and configuration. The smallest time-frequency resource supported by today's standards is a set of multiple subcarriers and multiple symbols (e.g., multiple resource elements (REs)), called a resource block (RB). A resource block may contain, for example, 84 resource elements in the case of a typical cyclic prefix, i.e., 12 subcarriers and 7 symbols.

[0036] In 5G New Radio ("NR"), a frame consists of a duration of 10 milliseconds. Each frame consists of 10 subframes, each with a duration of 1 millisecond, similar to LTE. μ It consists of slots. Each slot can have either 14 (normal CP) or 12 (extended CP) OFDM symbols. A slot is a typical unit for transmission used by the scheduling mechanism. NR allows transmissions to start with any OFDM symbol and continue only through the symbols necessary for communication. This is known as "mini-slot" transmission. This facilitates very low latency for critical data communications and, at the same time, minimizes interference to other RF links. Mini-slots help achieve lower latency in 5G NR architectures. Unlike slots, mini-slots are not tied to a frame structure. It helps puncture frames that exist without being scheduled. See, for example, https: / / www.rfwireless-world.com / 5G / 5G-NR-Mini-Slot.html, which is incorporated herein by reference.

[0037] Mobile networks used in wireless networks can be locations where the source and destination are interconnected by multiple nodes. In such networks, the source and destination may not be able to communicate directly with each other because the distance between them is greater than the transmission range of the nodes. That is, there is a need for intermediate nodes(s) to repeat or relay communications and provide the transmission of information. Therefore, intermediate nodes(s) can be used to repeat or relay information signals in a relay network, and the network topology has sources and destinations interconnected by such intermediate nodes. In hierarchical telecommunications networks, the backhaul portion of the network may include intermediate links between the core network and smaller subnetworks of the overall hierarchical network. Integrated Access Backhaul (IAB) next-generation NodeB uses 5G New Radio communications such as transmitting and receiving NR user plane (U-Plane) data traffic and NR control plane (C-Plane) data. Both UE and gNB may include addressable memory that electronically communicates with the processor. In one embodiment, instructions can be stored in memory and executed to process received packets and / or transmit packets according to different protocols, such as the Media Access Control (MAC) protocol and / or the Radio Link Control (RLC) protocol.

[0038] The Radio Resource Control (RRC) protocol can be used for signaling between a 5G radio network and an UE, where RRC may have at least two states (e.g., RRC_IDLE and RRC_CONNECTED) and state transitions, and the RRC_CONNECTED state may include two substates, active and inactive. The RRC sublayer may enable the establishment of a connection based on broadcasted system information and may also include security procedures. The U plane may include PHY, MAC, RLC, and PDCP layers.

[0039] The technologies described herein relate to various architectures related to the protocol architecture of relays, for example, describing how relay nodes and / or repeater nodes can be connected and their characteristics at the architectural level. For example, the technologies described herein relate to the architecture, functions, and capabilities of repeater nodes and UEs derived from an integrated access backhaul node, as well as the architecture, functions, and capabilities of parent nodes and wireless terminals communicating with repeater nodes. The repeater node lacks a layer above the physical layer on the service link side and appears as a UE to the parent node on the backhaul side.

[0040] In addition, the techniques described herein disclose exemplary techniques in which time / frequency resources may be allocated by a parent node, such as a donor node DN, which is a gNB that supplies time / frequency resources to the repeater node or NCR, for the purpose of repeating uplink and downlink to the UE on a repeater UE link via an NCR. For example, the techniques described herein describe exemplary configuration and use of physical and radio link parameters for a network-controlled repeater serving link by exchanging non-information-carrying signals and broadcast signals of the backhaul link with those specified in the information elements of the (re)configuration message. As described above, the repeater node(s) of the techniques described herein are said to be “smart repeaters” in the sense that, for example, the repeater node(s) provide and generate repeater-customized control signals. The repeater node(s) are also said to be “network-controlled” in the sense that the network provides time / frequency resources that facilitate the repeater node inserting repeater-customized control signals into frames transmitted on the wireless access link, for example, via a parent node.

[0041] In addition, the technologies described herein provide smart repeater nodes with previously unrealized capabilities and advantages, such as beamforming and spatial multiplexing in amplification and forward repeaters, as well as separate routing on a single hop link. Beamforming is the application of multiple radiating elements that transmit the same signal at the same wavelength and phase, which together create a single antenna with a longer, more targeted stream formed by augmenting radio waves in a particular direction.

[0042] The advantage of the technology described herein is that it facilitates the use of beamforming and / or multiple-input multiple-output (MIMO) antenna technology, which is useful for carrying large amounts of data to a given unit area by taking advantage of the high capability of the millimeter-wave spectrum. It is preferable that the millimeter-wave spectrum does not propagate through walls. On the other hand, in at least some exemplary embodiments and modes, the repeater node of the technology described herein can be used to carry the millimeter-wave spectrum from inside to outside or vice versa. For example, the antenna connecting the repeater node of the technology described herein to a backhaul link / donor node may be outdoors, the antenna of the repeater node(s) described herein that connects the repeater node(s) to its access link may be indoors, and the repeater node(s) maintains transparency of the wireless terminal link relayed to the gNB.

[0043] According to the technology described herein, Figure 2 shows an exemplary and typical telecommunications system 20 in a simplified form, including a parent node 22, a wireless repeater node 28, and a wireless child node 30.

[0044] The parent node 22 communicates wirelessly with the repeater node 28. The parent node 22 may be, for example, a base station node, such as an eNodeB, gNodeB, gNB, or an access node that is directly or indirectly connected to or communicates with the core network. The parent node may be, for example, an Integrated Access Backhaul (IAB) node. If the parent node includes a Radio Resource Control Entity (RRC), the parent node may be considered a “donor node”. The parent node 22 may provide network access for other nodes, for example, other wireless terminals, but a parent node providing such access to other nodes may be independent of the repeater node 28.

[0045] The repeater node 28 described herein, as shown in Figure 2, is also referred to as a “smart repeater node” (SR) or “network-controlled repeater” (NCR), for example, because the repeater node 28 has the ability to generate one or more repeater-customized control signals as described herein. The parent node 22 and the repeater node 28 may be connected by a wireless backhaul link 32. The repeater node 28 and the wireless terminal 30 may be connected by a wireless access link 34, also referred to as a service link 34 or simply link 34.

[0046] Child node 30 may be, for example, a user equipment (UE) or a wireless integrated access backhaul (IAB) node, but for brevity, it will be described herein primarily as a wireless terminal 30. As used herein, the term “wireless terminal” can refer to any electronic device used to communicate voice and / or data by a telecommunications system such as a cellular network (but not limited to). Other technical terms used to refer to a wireless terminal and non-exclusive examples of such devices include user equipment terminal, UE, mobile station, mobile device, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, subscriber unit, cellular phone, smartphone, personal digital assistant ("PDA"), laptop computer, tablet, netbook, e-reader, wireless modem, etc. A wireless terminal may include a modem for a wireless handset, a modem for an IoT device, etc., supporting voice, data, video applications, etc.

[0047] Figure 2 also illustrates various non-limiting embodiments of the technology described herein. Illustrative embodiments are indicated by symbols 2-1 to 2-7. Each symbol has text, in a non-exclusive manner, that briefly refers to the exemplary features and / or operation of various exemplary embodiments. Embodiment 2-1 represents a notification by repeater node 28 regarding the smart capabilities of the repeater node. As described herein, the smart capabilities of the repeater node include the ability of repeater node 28 to insert customized repeater control signals into the frame of information transmitted to wireless terminal 30. As used herein, “customized control signals” and “repeater customized control signals” may refer to one or more control signals, such as side control signals, customized by or for repeater node 28. “Customized” means that the control signals are configured by or for repeater node 28, taking into account individual determinations of the repeater node’s own local environment or circumstances or operation, and are therefore not estimated, generated, or considered by the network in such a way that they are applicable to other nodes by a general determination of multiple nodes. For example, as further described herein, a customized control signal for a repeater may be one or more of the following: a reference signal RS, a channel state information CSI, and a signal synchronization block SSB including a broadcast channel such as a physical broadcast channel. The channel state information reference signal CSI-RS is used in the downlink (DL) direction of 5G NR and is a reference signal RS used for channel sounding purposes and for measuring the characteristics of the radio channel so that it can use the correct modulation, code rate, beamforming, etc. Furthermore, a customized control signal for a repeater may be useful for performing beamforming operations, as shown in Embodiment 2-7.

[0048] Embodiment 2-2 represents the allocation of available radio resources at a repeater node. As used herein, “available radio resources” includes, for example, radio resources of a radio resource frame, and therefore includes resource elements, bandwidth portions, demodulation reference signals (DMRS), channel state information reference signals (CS-RS), primary and secondary synchronization signals (PSS and SSS, respectively), etc., which are suitable for inclusion of customized control signals by the repeater node.

[0049] Embodiment 2-3 of Figure 2 represents communication (as determined in Embodiment 2-2) of available radio resources from or by the parent node 22 to the repeater node 28, which is suitable for carrying customized control signals for the repeater. Examples of messages that may include the communication in Embodiment 2-3 are described herein and may include (re)configuration messages, in particular information elements such as ServingCellConfigCommon, tdd-UL-DL-ConfigurationCommon, and tdd-UL-DL-ConfigurationDedicated-IAB-MT, as described herein.

[0050] Embodiment 2-4 of Figure 2 represents the transmission of a frame of modified information that allows a repeater to insert a customized control signal. The modified frame may be derived from a normal frame containing downlink transmission information, but differs in at least some respects. As used herein, a “modified” frame is a frame that has been altered or formatted to provide or allocate radio resources in order to allow the repeater node 28 to insert a repeater customized control signal. For example, a modified frame may include certain radio resources transmitted at zero power to give the repeater node an opportunity to insert a repeater customized control signal into those radio resources. After inserting the repeater customized control signal into the frame, the frame for transmission to the wireless terminal 30 becomes a “customized” frame. In Embodiment 2-4, the modified frame is transmitted from the parent node 22 to the repeater node 28 via the wireless backhaul link 32.

[0051] In conjunction with Embodiment 2-4, Figure 2 shows a simplified, representative modified frame M. The modified frame M includes a set of radio resources 36, which includes default control signals that would be included in a normal unmodified frame. The default control signals of set 36 are indicated by the content "DDDD". Frame M also includes, or is "modified" to specify, a set of radio resources 38, which are available radio resources (one or more) and are suitable for carrying the repeater's customized control signals. Such available resources of set 38 are indicated by exemplary content "0000". Content "0000" indicates that, in the exemplary embodiment, the available radio resources are transmitted at zero power.

[0052] Embodiment 2-5 of Figure 2 illustrates the insertion of a repeater-customized control signal by the repeater node 28 within the available radio resources of the modified frame, thereby resulting in the customized frame.

[0053] Embodiment 2-6 in Figure 2 represents the transmission by the repeater node 28 to the wireless terminal 30 via the wireless access link 34 of a customized frame containing a repeater-customized control signal.

[0054] In conjunction with embodiments 2-5 and 2-6, Figure 2 further illustrates a simplified, representative customized frame C. Frame C is said to be “customized” in that it differs from the modified frame M. For example, customized frame C differs from modified frame M by carrying a repeater customized control signal. Modified frame C may also have its default control signal removed or set to zero power. Figure 2 shows, for example, a customized frame C having a radio set of resources 36 previously used in modified frame M, where the default signal now has the content “0000” and represents zero power for those radio resources. Furthermore, Figure 2 shows a customized frame C having a radio set of resources 38 formatted or prepared by parent node 22 so as to be available for a repeater customized control signal, which now carries a repeater customized control signal represented by the content “RRRR”.

[0055] Those skilled in the art will understand that the depictions of the exemplary modified frame M and the exemplary customized frame C are simplified depictions, and therefore the sizes and contents of sets 36 and 38 relative to the entire frame are for illustrative purposes only and are neither to scale nor accurate.

[0056] As described above, Embodiment 2-7 represents the potential use of repeater-customized control signals in beamforming operations that may be performed between the repeater node 28 and the wireless terminal 30. Those skilled in the art will understand that repeater-customized control signals, such as the exemplary repeater-customized control signals described herein, are used in beamforming operations.

[0057] In some exemplary embodiments and modes, it is not necessary to implement all of the above embodiments, and in fact, each embodiment has its own independent technical significance without being combined with any other embodiment. For example, in some exemplary embodiments and modes, the capabilities of the repeater node 28 do not need to be announced as in Embodiment 2-1, since its capabilities can be understood or configured in advance at the parent node 22. Similarly, with respect to Embodiment 2-3, the radio resources that are available and suitable for carrying the repeater-customized control signals can also be configured at both the parent node 22 and the repeater node 28, and in such cases do not need to be communicated. As a further example, the repeater-customized control signals transmitted from the repeater node 28 to the wireless terminal 30 in Embodiment 2-6 do not necessarily need to be used in beamforming operations as shown by Embodiment 2-7.

[0058] Figure 3 shows an exemplary general structure of the parent node 22, repeater node 28, and wireless terminal 30 of the telecommunications system 20 of Figure 2. Figure 3 shows the parent node 22 including a parent node processor(s) 40, a parent node interface 42 to the core network, and a parent node transceiver 44 for communication via the wireless backhaul link 32. When the parent node 22 connects to or communicates with the core network directly, the access node interface 42 to the core network is directly connected to the core network. When the parent node 22 connects to the core network through another node, the access node interface 42 connects to the core network via such other node. The parent node processor(s) 40, for example in conjunction with Embodiment 2-2, functions to allocate available radio resources to the repeater nodes that are suitable for inclusion by the repeater nodes of customized control signals, which are customized for the repeater nodes. The parent node processor(s) 40 can also, for example in conjunction with Embodiment 2-3, functions to generate messages informing the repeater nodes about available radio resources. The parent node processor(s) 40 perform many other functions involved in the operation of the parent node, as will be understood by those skilled in the art. The parent node transceiver 44 may comprise a parent node transmitter circuit 45, also known as a parent node transmitter 45, and a parent node receiver circuit 46, also known as a parent node receiver 46. The parent node transmitter 45 functions, for example, in conjunction with Embodiment 2-4, to transmit frames of information, including frames M, of available radio resources to repeater nodes, and to transmit messages informing repeater nodes about available radio resources.

[0059] Figure 3 further illustrates that the repeater node 28 may comprise a repeater node processor(s) 50, a repeater node transceiver circuit 52 that functions as an interface with the parent node 22 and for communication via the wireless backhaul link 32, and a repeater node transceiver circuit 54 that functions as an interface with the wireless terminal 30 and for communication via the wireless access link 34. The repeater node transceiver circuit 52 and the repeater node transceiver circuit 54 may be separate circuits dedicated to communication via the wireless backhaul link 32 and the wireless access link 34, respectively, or they may be the same circuit that functions to transmit and receive via both the wireless backhaul link 32 and the wireless access link 34, but according to the timing and radio resource allocation of each link. For illustrative purposes, the repeater node transceiver circuit 52 and the repeater node transceiver circuit 54 are shown as separate circuits. Thus, the repeater node transceiver circuit 52 may comprise a repeater node wireless backhaul link transmitter circuit 55, also known as a parent node wireless backhaul link transmitter 55, and a repeater node wireless backhaul link receiver circuit 56, also known as a repeater node wireless backhaul link receiver 56. The repeater node transceiver 56 may function, for example in conjunction with embodiment 2-4, to receive frames of information from the parent node via the wireless backhaul link 32, for example, frame M. The repeater node transceiver 56 may also function, for example in conjunction with embodiment 2-3, to receive messages advising the repeater node 28 via the wireless backhaul link 32 about available radio resources suitable for carrying the repeater's customized control signals. The repeater node transceiver circuit 54 may comprise a repeater node wireless access link transmitter circuit 55', also known as a repeater node wireless access link transmitter, and a repeater node wireless access link receiver circuit 56', also known as a repeater node wireless access link receiver 56'.The repeater node transmitter 55' can, for example, function in conjunction with embodiment 2-6 to transmit a frame of information, including a customized control signal, such as frame C, to a wireless terminal 30 via the wireless access link 34.

[0060] The repeater node processor(s) 50 can, for example, in conjunction with Embodiment 2-5, function to include customized control signals within the frame of information received from the parent node, the customized control signals being customized for the repeater node. The repeater node processor(s) 50 perform many other functions involved in the operation of the repeater node, as will be understood by those skilled in the art.

[0061] Figure 3 further illustrates that the wireless terminal 30 comprises one or more wireless terminal node processors 60, a wireless terminal transceiver circuit 62, and a wireless terminal interface 64. The wireless terminal transceiver circuit 62 may include a wireless terminal transmitter circuit 65, also known as a wireless terminal transmitter 65, and a wireless terminal receiver circuit 66, also known as a wireless terminal receiver 66. The wireless terminal receiver 66 may function, for example, in conjunction with Embodiment 2-6, to receive a customized frame C from a repeater node 28 via the wireless access link 34. The wireless terminal transceiver circuit 62 may function to receive and transmit other information and signals via the wireless access link 34. Such an interface 64 may function for both user input and output operations and may include a screen, such as a touchscreen, which can (for example) display information to the user and receive information entered by the user. The interface 58 may also include other types of devices, such as a speaker, microphone, or haptic feedback device.

[0062] The wireless terminal node processor(s) 60 may, for example, acquire customized control signals from a customized frame C and use the repeater customized control signals for various operations, including the beamforming procedure of Embodiment 2-7. The wireless terminal node processor(s) 60 may perform many other functions involved in the operation of the wireless terminal, as will be understood by those skilled in the art.

[0063] Transceiver circuits such as the master node transceiver 44, repeater node transceiver circuit 52, repeater node transceiver circuit 54, and wireless terminal transceiver circuit 62 include one or more antennas for wireless transmission. Transmitter circuits such as the master node transmitter circuit 45, repeater node transmitter circuit 55, and wireless terminal transmitter circuit 65 may include, for example, one or more amplifiers, modulation circuits, and other conventional transmitting equipment. Receiver circuits such as the master node receiver circuit 46, repeater node receiver circuit 56, and wireless terminal receiver circuit 66 may include, for example, amplifiers, demodulation circuits, and other conventional receiving equipment. For brevity, details of the master node transceiver 44, repeater node transceiver circuit 52, repeater node transceiver circuit 54, and wireless terminal transceiver circuit 62 may not be fully shown in Figures 4 and 5, but can be understood from the description in Figure 3.

[0064] Figure 4 shows how the exemplary general structure of the parent node 22 and repeater node 28 in the general exemplary embodiment and mode of Figure 3 can be implemented according to a distributed architecture. For example, Figure 4 shows the parent node 22 comprising a parent node central unit 47 and a parent node distributed unit 48. The central unit 47 and the distributed unit 48 can be realized by, or include, one or more processor circuits, for example, a parent node processor(s) 40. One or more parent node processors(s) 40 may be shared by the parent node central unit 47 and the repeater node 28, or each of the central unit 47 and the distributed unit 48 may comprise one or more parent node processors(s) 40. Furthermore, the parent node central unit 47 and the parent node distributed unit 48 may be jointly installed at the same node site, or one or more distributed units 48 may be located at a site separate from the central unit 47 and connected to it by a packet network. The distributed unit 48 may include a transceiver circuit 44 which can comprise a transmitter circuit and a receiver circuit as described herein.

[0065] Figure 4 also shows that the repeater node 28 comprises a repeater node mobile termination 57 and a repeater node distribution unit 58, in addition to a repeater node processor(s) 50. In the implementation of Figure 4, the repeater node mobile termination 57 functions as a repeater node transceiver circuit 52, and the repeater node distribution unit 58 functions as a repeater node transceiver circuit 54. Figure 4 further shows that the repeater node processor(s) 50 may include or form part of one or more of the repeater node mobile termination 57 and the repeater node distribution unit 58.

[0066] The following information regarding the distributed architecture, at least partially derived from TS38.401, is provided along with the implementation shown in Figure 4. gNB Central Unit (gNB-CU, also known as CU): A logical node that hosts the RRC [Radio Resource Control], the SDAP and PDCP protocols of gNB or RRC, and the RRC and PDCP protocols of en-gNB that control the operation of one or more gNB-DUs. The gNB-CU terminates the F1 interface connected to the gNB-DU. gNB Distributed Units (gNB-DU, also known as DUs): These are logical nodes that host the MAC and PHY layers of RLC, gNB, or en-gNB, and their operation is partially controlled by gNB-CUs. A single gNB-DU supports one or more cells. A single cell is supported by only one gNB-DU. A gNB-DU terminates an F1 interface connected to a gNB-CU. gNB-CU-Control Plane (gNB-CU-CP, also known as CU-C): A logical node that hosts the RRC and the control plane portion of the PDCP protocol for the gNB-CU of en-gNB or gNB. gNB-CU-CP terminates the E1 interface connected to gNB-CU-UP and the F1-C interface connected to gNB-DU. gNB-CU-UserPlane (also known as gNB-CU-UP or CU-U): A logical node that hosts the user plane portion of the gNB-CU's PDCP protocol for en-gNB, and the user plane portions of the gNB-CU's PDCP protocol and SDAP protocol for gNB. gNB-CU-UP terminates the E1 interface connected to gNB-CU-CP and the F1-U interface connected to gNB-DU. NG-RAN node: As defined in TS38.300. PDU Session Resources: This term is used in the specifications for NG, Xn, and E1 interfaces. It refers to the NG-RAN interface and radio resources provided to support PDU sessions. In addition, as noted in TS38.300, the mobile termination (MT) function is defined as a component of a mobile device. In the context of this discussion, the MT is referred to as a function residing on an IAB node that terminates the radio interface layer of a backhaul Uu interface toward an IAB donor or another IAB node.

[0067] Figure 5 is a schematic diagram illustrating in more detail the components and functions of a parent node, smart repeater node, and wireless terminal in an exemplary and non-exclusive implementation of one or both of the telecommunications systems of Figures 3 and 4. Figure 5 specifically shows exemplary component units or functions of the parent node processor(s) 40 of the parent node 22, the repeater node processor(s) 50 of the repeater node 28, and the wireless terminal node processor(s) 60 of the wireless terminal 30. Each of such component units or functions may be implemented by a processor circuit or other circuitry that achieves the described function, and may be shared with other functions or dedicated to the described functionality.

[0068] For example, Figure 5 shows a parent node processor (one or more) 40 comprising a parent node frame handler / generator 70, a resource allocation manager 71, a smart repeater memory 72, and a repeater manager 73. Next, the parent node frame handler / generator 70 comprises a frame correction controller 74. The smart repeater memory 72 then comprises smart repeater correction information 75 and an allocation message generator 76. In the exemplary implementation of Figure 5, the smart repeater memory 72 functions as a directory or database of repeater nodes controlled by or communicating with the parent node 22, and stores repeater node capability information that can be obtained from the repeater node in embodiment 2-1 for each repeater node, such as repeater node 28. In this regard, information received in any repeater node capability message generated by repeater node 28 may indicate that repeater node 28 is configured to include repeater-customized control signals within a frame of information received from the parent node, and can be stored in the smart repeater memory 72. The repeater manager 73 manages one or more repeater nodes that can be controlled or communicated with the parent node 22 and operates in conjunction with the resource allocation manager 71. In conjunction with aspect 2-1, the smart repeater modification information 75 of the resource allocation manager 71 is configured to store or generate information indicating which radio resources in a frame can be allocated as available radio resources suitable for inclusion by a repeater node for a customized control signal, such as the radio resources in the set 38 frames M in Figure 2. The allocation message generator 76, in conjunction with aspect 2-3, functions to generate messages that notify repeater nodes about available radio resources. Such allocation messages generated by the allocation message generator 76 are included in a frame by the parent node frame handler / generator 70 and transmitted to the repeater node 28 by the parent node transceiver 44. Such messages may be in the same frame as the allocated radio resources, or may precede such a frame.The smart repeater correction information 75 of the resource allocation manager 71 is used by the frame correction controller 74 so that the parent node frame handler / generator 70 can generate a frame containing allocated radio resources suitable for inclusion by the repeater node with customized control signals, for example, a corrected frame M. The corrected frame M, in conjunction with aspect 2-4, is transmitted by the parent node transceiver 44 to the repeater node 28 via the wireless backhaul link 32.

[0069] Figure 5 further illustrates that the repeater node 28 includes a repeater node frame handler / generator 80, a repeater node capability memory 81, a repeater node capability manager 82, a repeater node capability message generator 83, and a repeater node customized control signal generator 84. The repeater node frame handler / generator 80 then comprises a frame customization controller 85. The repeater node capability memory 81 stores information about the capabilities of the repeater node 28, including, for example, the fact / indication that the repeater node 28 is a "smart" repeater node in the sense that it can insert repeater customized control signals into frames for transmission over the wireless access link 34. The information in the repeater node capability memory 81 may be pre-configured, for example, by direct input to the repeater node 28, or by downloading from another node. The repeater node capability manager 82 manages the operation of the repeater node 28, including requesting the repeater node capability message generator 83 to generate a repeater node capability message according to aspect 2-1. The repeater node customized control signal generator 84 determines what values ​​(one or more) should be used or set for the repeater customized control signal. As will be understood by those skilled in the art, such values ​​(one or more) for the repeater customized control signal may depend, and usually actually depend, on beamforming operations performed between the repeater node 28 and a wireless terminal such as the wireless terminal 30. Once the repeater node customized control signal generator 84 has determined the values ​​for the repeater customized control signal, the frame customization controller 85 “customizes” the frame to be transmitted over the wireless access link 34 using the repeater customized control signal, as shown herein, for example, in conjunction with aspect 2-5. The repeater node transceiver circuit 54 then transmits the customized frame C to the wireless terminal 30 over the wireless access link 34, in conjunction with aspect 2-6.

[0070] Figure 5 further shows the wireless terminal 30 including a wireless terminal frame handler / generator 90 and a beamforming controller 92. The wireless terminal transceiver circuit 62 receives a customized frame C in conjunction with aspect 6-0 within the frame processed by the wireless terminal frame handler / generator 90. The wireless terminal 30 then acquires the repeater-customized control signal so that the beamforming controller 92 can use the repeater-customized control signal in one or more beamforming procedures of aspect 2-7.

[0071] The transceiver circuits and distributed units in Figures 4 and 5 may include transmitter and receiver circuits as illustrated in Figure 3.

[0072] Figure 6 is a flowchart illustrating exemplary, non-limiting basic operations or steps that may be performed by a repeater node in one or more exemplary embodiments and modes from Figures 2, 3, 4, and 5. Operation 6-1 includes receiving an information frame from a parent node. The received frame may be a frame such as frame M described above in conjunction with aspect 2-4. Operation 6-2 includes including a customized control signal within the information frame received from the parent node. As described above, the customized control signal is customized for the repeater node. Including the repeater customized control signal in operation 6-2 may be done in conjunction with aspect 2-5 and may result in a customized frame C, as shown in Figure 2. Operation 6-3 includes transmitting the information frame containing the customized control signal to another node, such as a wireless terminal 30. Operation 6-3 may be performed in conjunction with aspect 2-6.

[0073] Figure 7 is a flowchart illustrating exemplary non-limiting basic operations or steps that may be performed by the parent node of one or more exemplary embodiments and modes of Figures 2, 3, 4, and 5. Operation 7-1 includes allocating available radio resources to the repeater node. As described above, the available radio resources are suitable for inclusion by the repeater node of a customized control signal, and the customized control signal is customized for the repeater node. Such an allocation may be represented by embodiment 2-1. Operation 7-2 includes transmitting a frame of information containing the available radio resources to the repeater node. The frame transmitted by operation 7-2 may be a modified frame M, as described in conjunction with embodiment 2-4.

[0074] A smart repeater (SR) or NCR, such as repeater node 28, according to the technology described herein, may be a stripped-down IAB node to maintain transparency to the UE served by a service link or access link, which is the link from the repeater to the UE, as opposed to the link from the repeater to the gNB or IAB node, which is the backhaul link. For the sake of simplicity in the following discussion, we assume that the backhaul link of the repeater node is a gNB. Thus, the protocol stack of the control planes of the repeater node, the UE being served, and the gNB looks like Figure 8.

[0075] In this way, downlink beamforming and multiplexing of the smart repeater link are performed by RRC, radio resource control from a parent node 22 or gNB, terminating at the mobile termination portion of the smart repeater 28 in the exemplary embodiment and mode shown in Figure 4.

[0076] The resource grid that may form the basis of the frames described herein can be described by 3GPP TS38.211 v16.7.0 and can be shown in Figure 9, and the following definitions and symbols apply.

number

number

number

[0077] According to one aspect of the technology described herein, a reference signal RS, in particular a channel state information CSI reference signal, resides in a known time-frequency domain of the OFDM resource grid. For example, the reference signal CSI RS may reside in a non-contiguous set of resource elements, and thus in a known set of OFDM subcarriers, regardless of the number of carriers.

[0078] However, in order to maintain both transparency to the UE on the SR / NCR service link, to emulate the performance characteristics of the base station, and to achieve flexibility in deployment, the techniques described herein enable the SR / NCR to carry non-information-carrying signals, such as reference signals, synchronization signals, and physical broadcast channel PBCHs, which are generated locally by, for example, the repeater node 28. The contents of the PBCH, in particular the master information block having system information block 1 (SIB1), are generated locally and are essentially identical to those broadcast by the parent node 20, but in the customized frame transmitted by the repeater node 28 to the wireless terminal, they occupy different time / frequency resources than in the modified frame composed by the parent node 20 and transmitted by the parent node 20 to the repeater node 28. An incidental benefit of this capability is that interference to the base station can be minimized, for example, as a result, the resources used for the repeater-customized control signals are selected to avoid interference to one or more nodes, such as the parent node 22.

[0079] To perform this local generation by the repeater node 28, received non-information-carrying signals are preferably removed. In addition, according to one exemplary embodiment and mode, in order to minimize interference, the techniques described herein can not only remove non-user data-carrying signals but also regenerate the entire signal synchronization block (SSB), including the broadcast channel, using different time resources than those transmitted from the base station.

[0080] The process described for removing the above reference signal may be defined or configured by the gNB, for example by the parent node 22, and may be executed by the repeater node processor(s) 50 in the manner illustrated in Figure 10. Figure 10 provides a simplified illustration of how the repeater node processor(s), in particular the frame customization controller 85, can extract and replace the CSI RS to generate a frame C customized by the extended SSB. A full inverse DFT or FFT does not need to be performed by the repeater node 28, but only the carriers containing those that are to be configured need to be extracted and replaced. To illustrate this, a specified (selective) DFT / FFT is used, as the entire DFT / FFT does not need to be performed on the entire resource grid in question.

[0081] To facilitate the behavior of the repeater node 28 and the insertion of repeater-customized control signals, the donor node or parent node 22 may transmit in the time / frequency domain according to an NR frequency grid, which may have zero-power domains such as zero-power for reference, synchronization, and / or channel status information signals, and domains of zero-power level transmission from which the repeater node 28 can supply broadcast channels(s) of the access link 34. For this purpose, in a simplified manner, Figure 2 shows, for example, a set of radio resources 38 in a frame M with zero elements to reflect zero-power transmission of those radio resources.

[0082] In conjunction with aspect 2-3 of Figure 2, one exemplary method for establishing and / or (re)configuring the relationship between the parent node 22 and the repeater node 28 may involve the reuse or repurposement of the information element ServingCellConfigCommon, which is commonly used for handovers via synchronous RRC reconfiguration. The information element ServingCellConfigCommon contains enough elements to describe the cell to the wireless terminal 30 so that the UE can quickly, efficiently, and reliably connect to and hand over to the cell. The information elements for describing the cell to the wireless terminal include, for example, physical layer parameters required for the wireless terminal to communicate with another cell in the case of a handover. Changes are made as needed to recover from link failures, beam failures, or RRC reconfiguration events other than handovers. In a similar manner, the repeater node, NCR, needs information about how it appears to the wireless terminal that is repeated and essentially functions as a gNB.

[0083] In exemplary embodiments and modes, repeater node 28 essentially receives the entire bandwidth portion (BWP) of the downlink (DL) signal and is synchronized to it in RRC connection mode. In conjunction with aspect 2-5 of Figure 2, based on the configuration given by the relationships established by aspect 2-3, repeater node 28 determines which time / frequency resources, e.g., SSB(s) and / or RS(s), should be swapped, removes those unwanted RS(s) and / or SSB(s), reconstructs the DL signal as a customized frame C, and repeats, e.g., transmits, the DL signal as a customized frame C to wireless terminal 30. While this has so far been described in a separate time domain, those skilled in the art will understand that there are also analog ways to achieve this. In addition, if desired by the configuration, such as SSB transmission being at some other point in time, this can be done via a delay line, possibly by a timing advance mechanism. Such delays do not need to be applied to delay-sensitive traffic, but may be applied to delay-insensitive traffic, e.g., web browsing.

[0084] In addition, the bandwidth portion (BWP) of the cell presented to the UE served by the NCR, without conversion to a separate time domain, can also be modified via the configuration by strictly using up-conversion or down-conversion as an analog realization controlled by the configuration.

[0085] As described above, in some exemplary embodiments and modes, the downlink from the parent node 22 is transmitted in a zero-power time / space domain, which allows the repeater node 28 to use the transmission of signal synchronization blocks (SSBs) for the access or service link. Furthermore, such embodiments, particularly those deployed in frequency domain 2, also known as "FR2," in bandwidths above 24 GHz and thus limited to using time-division duplexing, can be configured using an information element such as tdd-UL-DL-ConfigurationCommon, which is described and incorporated by reference in the 3GPP TS38.213 v16.7.0 physical layer procedure for control, e.g., clauses 11 and 11.1ff. This configuration shows a slot format used for uplinks, downlinks, and flexible slots, which on the backhaul link allow the slots to be configured to be flexible so as to allow the allocation of SSBs within those slots via the configuration. The slot format is indicated as a Slot Format Indicator (SFI) according to Table 11.1.1-1 of 3GPP TS38.213 v16.7.0.

[0086] In some exemplary embodiments and modes, an information element (IE), such as tdd-UL-DL-ConfigurationCommon, but referred to herein as tdd-UL-DL-ConfigurationDedicated-IAB-MT, may be dedicated to a single SR / NCR despite its similarity to tdd-UL-DL-ConfigurationCommon. Using such a dedicated information element, it is possible to provide the use of multiple SR / NCRs that may have different uplink / downlink configurations on a backhaul link, which can be achieved by the fact that the backhaul link is expected to have very spatially narrow beam pairs. Furthermore, the slot format on the access link may be configured by IEtdd-UL-DL-ConfigurationCommon, which may be different from that configured on the backhaul link, or may be configured as a subset of the IE "similar to tdd-UL-DL-ConfigurationCommon" on the backhaul link. Similarly, the NCR may have an IE "similar to slotFormatCombinationPerCell" or be provided to indicate that multiple slot formats are configured for the SR / NCR. The configured slot format on each cell's access link can be changed via reconfiguration if tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated-IAB-MT is configured.

[0087] For the above, please refer to 3GPP TS38.213 v16.7.0, Clause 14. A portion of it is excerpted below. The IAB-MT may be provided by SlotFormatCombinationPerCell, which is a list of slot format combinations applicable to a single serving cell, and SlotFormatIndicator, which is a configuration for monitoring the list of slot format combinations over the number of slots specified in Clause 11.1.1, and DCI Format 2_0 indicating the slot format combinations. In addition to the slot formats in Table 11.1.1-1, the SFI field for the IAB-MT in DCI Format 2_0 may indicate the slot formats from the slot formats in Table 14-2 to the IAB-MT.

[0088] Therefore, if SlotFormatCombinationPerCell is provided for the access link, the UL / DL configuration may be dynamically changed via DCI, but if information elements such as tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated-IAB-MT can be changed by reconfiguration, it is the same as prior art.

[0089] As mentioned above, ServingCellConfigCommon, which is commonly used for handovers via synchronized RRC reconfiguration, can be used to describe the configuration of a cell served by repeater node 28. The ServingCellConfigCommon listed in Table 1 may include the information element “tdd-UL-DL-ConfigurationCommon equivalent”. Like other information elements of ServingCellConfigCommon, the information element “tdd-UL-DL-ConfigurationCommon equivalent” is cell-specific and describes the unpaired spectrum, downlink-uplink periodicity, and a specific number of uplink and downlink slots and boundary OFDM symbols, as defined in TS38.331 v.16.6.0, section 6.3.2. In addition, within its slot pattern, it determines where to place the SSB using specific DL symbols assigned according to the SSB information element of ServingCellConfigCommon.

[0090] According to one aspect of the technology described herein, a network control relay searches for a parent node 22 such as a user device, UE, and identifies itself as a UE via capability information. Using capability information supplied by a repeater node 28, the parent node 22 has enough information to identify the network control relay, e.g., a smart repeater node, and thus can (re)configure the network control relay. Reconfiguration may be preferred over preconfiguration in order to enable better use of time / frequency / spatial resources, including parameters related to the initial bandwidth portions of the uplink and downlink in particular.

[0091] Table 1: ServingCellConfigCommon (Excerpt from 3GPP TS38.331 v.16.6.0) The IE ServingCellConfigCommon is used to configure cell-specific parameters for a UE's serving cell. The IE contains parameters that the UE would normally obtain from the SSB, MIB, or SIB when accessing the cell from IDLE. In this IE, the network provides this information via dedicated signaling when configuring the UE with SCell or additional cell groups (SCG). It also provides it to SpCell (MCG and SCG) when reconfiguring synchronously. ServingCellConfigCommon information element: [Table 1] [Table 2] [Table 3-1] Description of the ServingCellConfigCommon field channel: Dialog Mode If present, this field indicates which channel access procedure to apply to operations using shared spectral channel access as defined in TS37.213

[48] . If the field is configured as "semiStatic", the UE shall apply the channel access procedure for semi-static channel occupancy as described in Section 4.3 of TS37.213. If the field is configured as "dynamic", the UE shall apply the channel access procedure of TS37.213, except for Section 4.3 of TS37.213. dmrs-TypeA-Position The location of the (first) DM-RS for the downlink (see TS38.211

[16] , clause 7.4.1.1.1) and the uplink (see TS38.211

[16] , clause 6.4.1.1.3). closelinkConfigCommon A common downlink configuration for a serving cell, including the frequency information configuration and the initial downlink BWP common configuration. The parameters provided herein must be consistent with the parameters configured by the serving cell's MIB and SIB1 (if provided), with the exception that controlResourceSetZero and searchSpaceZero may be configured in ServingCellConfigCommon even if the MIB does not exist. discoveryBurstWindowLength The length of the discovery burst window is shown in milliseconds (see TS37.213

[48] ). longBitmap A bitmap where the maximum number of SS / PBCH blocks per half frame is equal to 64, as defined in TS38.213

[13] , clause 4.1. lte-CRS-ToMatchAround A parameter that determines the LTE CRS pattern that the UE must evaluate for consistency. mediumBitmap A bitmap where the maximum number of SS / PBCH blocks per half frame is equal to 8, as defined in TS38.213

[13] , clause 4.1. n-TimingAdvanceOffset The N_TA-Offset applied to all uplink transmissions on this serving cell. If this field is not present, the UE applies the value defined for the duplex mode and frequency range of this serving cell. See TS38.133

[14] , Table 7.1.2-2. rateMatchPatternToAddModList The resource pattern on which the UE should rate-match PDSCHs. The UE rate-matches the combination of all resources shown in the rate-match pattern. A rate-match pattern defined at the cell level applies only to the same number of PDSCHs (see TS38.214

[19] , clause 5.1.4,1). shortBitmap A bitmap where the maximum number of SS / PBCH blocks per half frame is equal to 4, as defined in TS38.213

[13] , clause 4.1. ss-PBCH-BlockPower The average EPRE of resource elements carrying secondary synchronization signals in dBm used by the network for SSB transmission. See TS38.213

[13] , clause 7. ssb-periodicityServingCell SSB periodicity in milliseconds for rate matching purposes. If this field is not present, the UE applies the value ms5. (See TS38.213

[13] , clause 4.1) ssb-PositionQCL The QCL relationship between the SSB locations of this serving cell is shown as specified in TS38.213

[13] , clause 4.1. [Table 3-2] (Continuation of the table above) Description of the ServingCellConfigCommon field ssb-PositionsInBurst In operation under the license spectrum, this indicates the time-domain position of a transmitted SS block within a half-frame that has an SS / PBCH block as defined in TS38.213

[13] , clause 4.1. The first / leftmost bit corresponds to SS / PBCH block index 0, the second bit corresponds to SS / PBCH block index 1, and so on. A bitmap value of 0 indicates that the corresponding SS / PBCH block is not transmitted, and a value of 1 indicates that the corresponding SS / PBCH block is transmitted. The network configures this field with the same pattern as the corresponding field in ServingCellConfigCommonSIB. When operating with shared spectral channel access, only the mediumBitmap is used, and the UE is Assume that one or more SS / PBCH blocks indicated by ssb-PositionsInBurst are transmitted within the discovery burst transmission window and may have candidate SS / PBCH block indexes corresponding to the SS / PBCH block indexes provided by ssb-PositionsInBurst (see TS38.213

[13] , clause 4.1). If the k-th bit of ssb-PositionsInBurst is set to 1, the UE assumes that it can send one or more SS / PBCH blocks within the discovery burst send window with candidate SS / PBCH block indices corresponding to SS / PBCH block indices equal to k-1. If the k-th bit is set to 0, the UE assumes that no corresponding SS / PBCH blocks(s) are sent. The k-th bit is set to 0, where k > ssb-PositionQCL, and the number of SS / PBCH blocks actually sent is less than or equal to the number of ones in the bitmap. The network configures this field with the same pattern as in the corresponding field of ServingCellConfigCommonSIB. ssbSubcarrierSpacing The subcarrier spacing for SSB. Only values ​​of 15kHz or 30kHz (FR1) and 120kHz or 240kHz (FR2) are applicable. UpdaterUplinkConfig The network configures this field only if uplinkConfigCommon is configured. If this field is not present, the UE will release supplementaryUplinkConfig and, if configured, supplementaryUplink configured in the ServingCellConfig of this serving cell. tdd-UL-DL-ConfigurationCommon See cell-specific TDD UL / DL configuration, TS38.213

[13] , clause 11.1.

[0092] According to other aspects of the technology described herein, The smart repeater or SR may be a repeater having a UE interface to a backhaul link, or it may be a physical layer PHY on a service link. • The service link may have a CS IRS generated by the repeater, configured by the CU's radio resource control, RRC. Beamforming on the service link from repeater node 28 is similar to the transmit configuration instruction TCI, but can be achieved when DL RS, beam pairs, etc. on the service link are configured by the CU of parent node 22. • The synchronous signal block SSB is time-delayed on the service link compared to that on the backhaul link, preventing interference with the signal synchronization block of access node 22.

[0093] Various exemplary embodiments and modes described herein may be used in conjunction with one or more exemplary embodiments and modes described herein.

[0094] Certain units and functions of System 20 may be implemented by electromechanical devices. For example, electromechanical devices may refer to processor circuits described herein, such as a parent node processor (one or more) 40, a repeater node processor (one or more) 50, and a wireless terminal node processor (one or more) 60. Furthermore, the term “processor circuit” is not limited to meaning one processor, but may include multiple processors, and multiple processors may operate at one or more sites. Furthermore, as used herein, the term “server” is not limited to a single server unit, but may include multiple servers and / or other electronic devices, which may be jointly installed at one site or distributed across different sites. With these understandings in mind, Figure 11 shows an example of an electromechanical device, for example, a processor circuit, comprising one or more processors 290, a program instruction memory 292, other memory 294 (e.g., RAM, cache, etc.), input / output interfaces 296 and 297, a peripheral interface 298, a support circuit 299, and a bus 300 for communication between the aforementioned units. The processor(s) 290 may include processor circuits as described herein, for example, a parent node processor(s) 40, a repeater node processor(s) 50, and a wireless terminal node processor(s) 60.

[0095] The memories or registers described herein may be indicated by memory 294 or any computer-readable medium, and may be one or more readily available memories such as random access memory (RAM), read-only memory (ROM), floppy disks, hard disks, flash memory, or any other form of local or remote digital storage, preferably non-volatile, and thus may include memory. Support circuits 299 are coupled to the processor 290 to support the processor in a conventional manner. These circuits include caches, power supplies, clock circuits, input / output circuits, and subsystems.

[0096] While the processes and methods of the embodiments of this disclosure may be discussed as being implemented as software routines, some of the method steps disclosed herein may be performed in hardware and by software running on a processor. Thus, these embodiments may be implemented in software running on a computer system, in hardware such as application-specific integrated circuits, or in other types of hardware implementations, or in a combination of software and hardware. The software routines of the embodiments of this disclosure can run on any computer operating system and can run using any CPU architecture.

[0097] The functionality of various elements, including but not limited to those labeled or described as “computer,” “processor,” or “controller,” including functional blocks, may be provided by circuit hardware and / or hardware capable of executing software in the form of coded instructions stored on a computer-readable medium. Therefore, such functionality and the exemplified functional blocks are understood to be either hardware-implemented and / or computer-implemented, and thus machine-implemented.

[0098] In terms of hardware implementation, a functional block may include, but is not limited to, hardware (e.g., digital or analog) circuitry, including, digital signal processor (DSP) hardware, reduced instruction set processors, application-specific integrated circuits (ASICs), and / or field-programmable gate arrays (FPGAs), as well as (where appropriate) state machines capable of performing such functions.

[0099] From a computer implementation perspective, a computer is generally understood to comprise one or more processors or one or more controllers, and the terms computer, processor, and controller may be used interchangeably herein. When provided by a computer or processor or controller, the functions may be provided by a single dedicated computer or processor or controller, a single shared computer or processor or controller, or by multiple individual computers or processors or controllers, some of which may be shared or distributed. Furthermore, the use of the terms “processor” or “controller (control unit)” may also be interpreted as referring to other hardware capable of performing and / or running such functions, such as the exemplary hardware listed above.

[0100] The term “configured” can relate to the capabilities of a device, whether it is in an operational or non-operational state. “Configured” can also refer to specific settings within a device that give the device its operational characteristics, whether it is in an operational or non-operational state. For example, hardware, software, firmware, registers, memory values, and / or similar elements can be “configured” within a device, whether it is in an operational or non-operational state, to give the device certain characteristics.

[0101] Nodes that communicate using an air interface also have appropriate wireless communication circuits. Furthermore, the techniques disclosed herein can all be embodied in any form of computer-readable memory, such as solid memory, magnetic disks, or optical disks, which include an appropriate set of computer instructions that would cause a processor to implement the techniques described herein.

[0102] Furthermore, the functional blocks or various functions of the wireless terminal 30, parent node 22, and repeater node 28 used in each of the embodiments described above can generally be implemented or executed by a circuit that is an integrated circuit or a set of integrated circuits. A circuit designed to perform the functions described herein may comprise a general-purpose processor, a digital signal processor (DSP), an application-specific or general-purpose application integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gates or transistor logic, or individual hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or the processor may be a conventional processor, controller, microcontroller, or state machine. The general-purpose processor or each circuit described above may consist of digital circuits or analog circuits. Furthermore, if advances in semiconductor technology lead to the emergence of integrated circuit technologies that replace current integrated circuits, integrated circuits using these technologies will also become available.

[0103] The technologies disclosed herein are intended to solve the problem of wireless communication concentration and are necessarily based on computer technology, and will be understood to overcome problems that specifically arise in wireless communication. Furthermore, the technologies disclosed herein improve the basic functions of methods and procedures for enabling better use of spectrum in wireless access networks, for example, in environments in which a single base station or gNB may not be able to overcome propagation loss due to propagation loss from an outdoor environment to an indoor environment.

[0104] One or more of the following documents, all of which are incorporated herein by reference, may relate to the technology described herein. All specifications are considered to be as close as possible to those around Release 16.4, if updated by September 2021, with the exception of TR38.874, which was last updated in November 2018. 3GPP TS38.401,NG-RAN;Architecture description 3GPP TR38.874,Study on Integrated Access and Backhaul 3GPP TS38.473 F1 application protocol (F1AP) 3GPP TS38.470,NG-RAN;F1 general aspects and principles https: / / www.sharetechnote.com / html / 5G / 5G_ResourceGrid.html 3GPP TS38.211 v16.7.0 NR;Physical channels and mod 3GPP TS38.213 v16.7.0 Physical layer procedures for control RP-213700,Study on NR Network-controlled Repeaters,RAN #94 RP-212703,(Draft) Study on Smart Repeaters,RAN #94

[0105] The technologies disclosed herein encompass one or more of the following non-limiting, non-exclusive, exemplary embodiments and modes:

[0106] Exemplary Embodiment 1: A repeater node in a telecommunications network that wirelessly communicates with a parent node and another node, A receiver circuit configured to receive information frames from a parent node, A processor circuit configured to include a customized control signal within a frame of information received from a parent node, wherein the customized control signal is customized for the repeater node. A transmitter circuit configured to send a frame of information containing customized control signals to another node, A repeater node equipped with [a specific feature / feature].

[0107] Exemplary Embodiment 2: The repeater node according to Exemplary Embodiment 1, wherein the processor circuit is further configured to generate customized control signals.

[0108] Exemplary Embodiment 3: The repeater node according to Exemplary Embodiment 1, wherein the customized control signal is at least one of a reference signal, channel state information, and a signal synchronization block.

[0109] Exemplary Embodiment 4: The repeater node according to Exemplary Embodiment 1, wherein a customized control signal includes a broadcast channel.

[0110] Exemplary Embodiment 5: The processor circuit is further configured to generate a repeater node capability message, which communicates to the parent node that the repeater node is configured to include customized control signals within a frame of information received from the parent node. The transmitter circuit is further configured to send repeater node capability messages to the parent node. A repeater node according to Exemplary Embodiment 1.

[0111] Exemplary Embodiment 6: The receiver circuit is further configured to receive resource allocation messages from the parent node, the resource allocation messages are configured to allocate to the repeater node an available radio resource suitable for inclusion by the repeater node of a customized control signal. The processor circuit is further configured to include customized control signals within the available radio resources. A repeater node according to Exemplary Embodiment 1.

[0112] Exemplary Embodiment 7: The repeater node according to Exemplary Embodiment 6, wherein the resource allocation message includes a (re)configuration message.

[0113] Exemplary Embodiment 8: A method in a repeater node of a telecommunications network that wirelessly communicates with a parent node and another node, Receiving a frame of information from the parent node, The frame of information received from the parent node includes a customized control signal, and the customized control signal is customized for the repeater node. Sending a frame of information containing customized control signals to another node, Methods that include...

[0114] Exemplary Embodiment 9: The method according to Exemplary Embodiment 8, further comprising generating a customized control signal.

[0115] Exemplary Embodiment 10: The method according to Exemplary Embodiment 8, wherein the customized control signal is at least one of a reference signal, channel state information, and a signal synchronization block.

[0116] Exemplary Embodiment 11: The method according to Exemplary Embodiment 8, wherein a customized control signal includes a notification channel.

[0117] Exemplary Embodiment 12: Generating a repeater node capability message, wherein the repeater node capability message is configured to communicate to the parent node that the repeater node is configured to include customized control signals within a frame of information received from the parent node. Sending a repeater node capability message to the parent node, The method of exemplary embodiment 8, further including the following.

[0118] Exemplary Embodiment 13: Receiving a resource allocation message from a parent node, wherein the resource allocation message is configured to allocate a radio resource to the repeater node that is suitable for the repeater node to incorporate a customized control signal. The available wireless resources include customized control signals, The method of exemplary embodiment 8, further including the following.

[0119] Exemplary Embodiment 14: A master node of a telecommunications network that communicates wirelessly with a repeater node, A processor circuit configured to allocate available radio resources to repeater nodes, wherein the available radio resources are suitable for inclusion of customized control signals by the repeater nodes, and the customized control signals are customized for the repeater nodes. A transmitter circuit configured to send a frame of information containing available radio resources to a repeater node, A parent node that includes this feature.

[0120] Exemplary Embodiment 15: The parent node according to Exemplary Embodiment 14, wherein the processor circuit is further configured to generate messages that inform repeater nodes about available radio resources.

[0121] Exemplary Embodiment 16: The parent node according to Exemplary Embodiment 14, wherein the processor circuit is further configured to generate resource allocation messages that notify repeater nodes of available radio resources, and the transmitter circuit is further configured to transmit resource allocation messages to the repeater nodes.

[0122] Exemplary Embodiment 17: The parent node according to Exemplary Embodiment 16, wherein the resource allocation message includes a (re)configuration message.

[0123] Exemplary Embodiment 18: The parent node according to Exemplary Embodiment 14, wherein the available radio resources are suitable for use by a repeater node as at least one of a reference signal, channel state information, and a signal synchronization block.

[0124] Exemplary Embodiment 19: The parent node according to Exemplary Embodiment 14, wherein the available wireless resources are suitable for use by repeater nodes as broadcast channels.

[0125] While the above description contains many specifics, these should be interpreted not as limiting the scope of the technology disclosed herein, but merely as providing some examples of currently preferred embodiments of the technology disclosed herein. The scope of the technology disclosed herein should be determined by the appended claims and their legal equivalents. Thus, the scope of the technology disclosed herein fully encompasses other embodiments that may be apparent to those skilled in the art, and as a result, the scope of the technology disclosed herein is not limited to anything other than the appended claims, and it will be recognized that singular references to elements in the claims mean "one or more" rather than "one and only one" unless explicitly stated. The above embodiments can be combined with one another. All structural, chemical, and functional equivalents to elements of the above preferred embodiments known to those skilled in the art are expressly incorporated herein by reference and are intended to be included in the claims. Furthermore, devices or methods do not need to address each problem that is required to be solved by the technology disclosed herein, for devices or methods are included in the claims. Furthermore, no element, component, or method step in this disclosure is intended to be made available to the public, regardless of whether such element, component, or method step is expressly enumerated in the claims.

Claims

1. A repeater node in a telecommunications network that communicates wirelessly with a parent node and other nodes, A receiving unit configured to receive an information frame from the parent node, which includes a frame containing wireless resources transmitted by the parent node with zero power, A processor unit configured to generate customized control signals and include the customized control signals in the radio resources transmitted at zero power by the parent node, thereby generating customized frames from the frames, wherein the customized control signals are customized by the repeater node. A transmission unit configured to transmit the customized frame to the other node, A repeater node equipped with [a specific feature / feature].

2. The repeater node according to claim 1, wherein the customized control signal includes at least one of a reference signal, channel state information, and a signal synchronization block.

3. The repeater node according to claim 1, wherein the customized control signal includes a broadcast channel.

4. The receiving unit is further configured to receive resource allocation messages from the parent node to the repeater node via dedicated signaling, and the resource allocation message is configured to allocate to the repeater node the available radio resources within the frame of the information that are suitable for inclusion of the customized control signal by the repeater node. The processor unit is further configured to include the customized control signals within the available wireless resources. The repeater node according to claim 1.

5. The repeater node according to claim 4, wherein the resource allocation message includes a (re)configuration message.

6. A method in a repeater node of a telecommunications network that communicates wirelessly with a parent node and other nodes, Receiving an information frame from the parent node, which includes a frame containing radio resources transmitted by the parent node with zero power; A customized control signal, which is generated by the repeater node, By including the customized control signal in the radio resource transmitted at zero power by the parent node, a customized frame is generated from the frame. Sending the customized frame to the other node, Methods that include...

7. A master node of a telecommunications network that communicates wirelessly with repeater nodes, A processor unit configured to allocate available radio resources to the repeater node, wherein the available radio resources are suitable for the generation of customized control signals by the repeater node and for the inclusion of the customized control signals by the repeater node, and the customized control signals are customized by the repeater node. The repeater node is configured to transmit a frame of information including the available radio resources, which are radio resources transmitted at zero power, A parent node that includes this feature.

8. The parent node according to claim 7, wherein the processor unit is further configured to generate a resource allocation message that notifies the repeater node of the available radio resources, and the transmission unit is further configured to transmit the resource allocation message to the repeater node.

9. The parent node according to claim 8, wherein the resource allocation message includes a (re)configuration message.

10. The parent node according to claim 7, wherein the available radio resources are suitable for use by the repeater node as at least one of a reference signal, channel state information, and a signal synchronization block.

11. The parent node according to claim 7, wherein the available wireless resources are suitable for use by the repeater node as broadcast channels.

Images