SYSTEM AND METHOD FOR TDD CONFIGURATION FOR SMARTNODES - Patent application

Abstract

A system and method for time division duplex (TDD) configuration for a smart node (SN) are presented. A network node can receive one or more messages from a wireless communication node. The one or more messages can indicate a first set of TDD configuration parameters and a second set of TDD configuration parameters. The first set of TDD configuration parameters can be configured for a first link. The second set of TDD configuration parameters can be configured for a second link.

Description

[Technical Field]

[0001] The present disclosure relates generally to wireless communications, including, but not limited to, systems and methods for time division duplex (TDD) configuration for smart nodes (SNs). [Background technology]

[0002] Coverage is a fundamental aspect of cellular network deployment. Mobile operators rely on different types of network nodes to provide blanket coverage in their deployments. As a result, new types of network nodes are being considered to increase mobile operators' flexibility for their network deployments. For example, some systems or architectures introduce integrated access backhaul (IAB), which can be extended in other systems as a new type of network node that does not require wired backhaul. Another type of network node is the RF repeater, which simply amplifies and forwards any signals they receive. RF repeaters are found in widespread deployments in 2G, 3G, and 4G to complement the coverage provided by regular full-stack cells. Summary of the Invention [Means for solving the problem]

[0003] The exemplary embodiments disclosed herein are directed not only to solving problems associated with one or more of the problems presented in the prior art, but also to providing additional features that will become readily apparent by reference to the following detailed description when considered in conjunction with the accompanying drawings. According to various embodiments, exemplary systems, methods, devices, and computer program products are disclosed herein. It should be understood, however, that these embodiments are presented by way of example, and not limitation, and that various modifications to the disclosed embodiments may be made while remaining within the scope of the present disclosure, as will be apparent to those skilled in the art upon perusal of this disclosure.

[0004] At least one aspect is directed to a system, method, apparatus, or computer-readable medium. A network node (e.g., a smart node (SN)) can receive one or more messages from a wireless communication node (e.g., a base station (BS) or a gNB). The one or more messages can indicate a first set of time division duplex (TDD) configuration parameters and a second set of TDD configuration parameters. The first set of TDD configuration parameters can be configured for a first link. The second set of TDD configuration parameters can be configured for a second link.

[0005] In some arrangements, the first link may comprise at least one of the following links: a first communication link from a wireless communication node to a network node, or a second communication link from a network node to a wireless communication node. In various arrangements, the second link may comprise at least one of the following links: a first forward link from a wireless communication node to a network node, a second forward link from a network node to a wireless communication node, a third forward link from a network node to a wireless communication device, or a fourth forward link from a wireless communication device to a network node.

[0006] In some arrangements, the first link may operate in (or be configured with) a first frequency band or carrier. The second link may operate in (or be configured with) a second frequency band or carrier. In some arrangements, the network node may include a first unit and a second unit. In response to the first unit receiving the first set of TDD configuration parameters, the first unit may control reception and / or transmission over the first link. In response to the first unit receiving the second set of TDD configuration parameters, the second unit may perform reception and / or transmission over the second link, or the first unit may forward the second set of TDD configuration parameters to the second unit and enable the second unit to control reception and / or transmission over the second link.

[0007] In some arrangements, when the first link and the second link are configured with different TDD patterns or different directions in symbols / slots: the network node may transmit or receive over the first link and stop forwarding over the second link; the network node may transmit over the second link and stop transmitting or receiving over the first link; the network node may perform uplink operation and stop downlink operation; or the network node may perform downlink operation and stop UL operation. The high priority link or direction may be configured to the network node by the wireless communication node or an Operation, Administration, and Maintenance (OAM) node through system information, RRC signaling, MAC CE, or DCI.

[0008] In some arrangements, the first set of TDD configuration parameters may include first parameters configured generally, cell-specific, or semi-statically to control reception and / or transmission over a first link. In various arrangements, the second set of TDD configuration parameters may include second parameters configured generally, cell-specific, or semi-statically to control reception and / or transmission over a second link.

[0009] In some arrangements, the first set of TDD configuration parameters may include a device-specific, device-specific, or semi-statically configured third parameter for controlling reception and / or transmission over the first link. In various implementations, the second set of TDD configuration parameters may include a device-specific, device-specific, or semi-statically configured fourth parameter for controlling reception and / or transmission over the second link.

[0010] In some arrangements, the one or more messages may each be radio resource control (RRC) signaling or system information (SI). The first set of TDD configuration parameters may include a fifth parameter that is a medium access control control element (MAC CE) or DCI. In some implementations, the second set of TDD configuration parameters may include a sixth parameter that is a MAC CE or DCI.

[0011] At least one aspect is directed to a system, method, apparatus, or computer-readable medium. A network node (e.g., an SN) can receive one or more messages from a wireless communication node (e.g., a BS or a gNB). The one or more messages can indicate a single set of time division duplex (TDD) configuration parameters. The single set of TDD configuration parameters can be configured for a first link and, implicitly, for a second link.

[0012] In some arrangements, the first link may comprise at least one of the following links: a first communication link from a wireless communication node to a network node, or a second communication link from a network node to a wireless communication node. In some implementations, the second link comprises at least one of the following links: a first forward link from a wireless communication node to a network node, a second forward link from a network node to a wireless communication node, a third forward link from a network node to a wireless communication device, or a fourth forward link from a wireless communication device to a network node.

[0013] In some arrangements, the network node may include a first unit and a second unit, where in response to the first unit receiving the single set of TDD configuration parameters, the first unit may control reception and / or transmission over the first link, and / or in response to the first unit receiving the subcarrier spacing associated with the second unit, the first unit may determine, based on the subcarrier spacing, a set of TDD configuration parameters configured to control reception and / or transmission over the second link.

[0014] The systems and methods presented herein include novel approaches for time division duplex (TDD) configuration for SNs. Specifically, the systems and methods presented herein discuss novel solutions for indicating / providing / signaling (e.g., by a BS) one or more sets (e.g., two sets) of TDD uplink (UL) and / or downlink (DL) configuration (e.g., UL, DL, and / or flexible symbol / slot) parameters to an SN (e.g., an SN CU), such as using one set of TDD configurations for SN CU transmission and / or reception and another set of TDD configurations for SN FU transmission and / or reception (e.g., using another set of TDD configurations for the SN CU to control the SN FU). The SN FU and SN CU can operate within the same or different frequency bands / carriers. Therefore, the system and method of the technical solution can introduce configuration parameters for TDD and extend / improve / increase the precision in controlling the SN's (e.g., among other signals) forwarding signals to at least one of a BS or a user equipment (UE), thereby improving the SN's flexibility in network deployment.

[0015] For example, a first set of TDD UL / DL configuration parameters including at least one of the first, third, and / or fifth TDD UL / DL configuration parameters (e.g., as discussed herein) may be used / implemented / configured for the SN CU for the SN CU, and a second set of TDD UL / DL configuration parameters including at least one of the second, fourth, and / or sixth TDD UL / DL configuration parameters may be configured for the SN CU for the SN FU.

[0016] In various arrangements, the first parameters (e.g., TDD UL / DL configuration parameters) can be semi-statically configured (e.g., via system information and / or RRC signaling) and / or can be common or cell-specific (e.g., with respect to SN CUs and / or UEs in a cell with the first frequency band / carrier). For example, as part of the first parameters, parameters "tdd-UL-DL-ConfigurationCommon" and / or ServingCellConfigCommon" in SIB1 can be used to indicate the TDD UL / DL configuration used for the SN CU-SN CU.

[0017] In various implementations, the second parameters can be semi-statically configured (e.g., via system information and / or RRC signaling) and / or can be common or cell-specific (e.g., with respect to SN FUs and / or UEs in a cell with the second frequency band / carrier). For example, as part of the second parameters, a new parameter can be defined / described (e.g., in SIB1 and / or ServingCellConfigCommon) to be used to indicate to the SN CU the TDD UL / DL configuration to be used for the SN FU. For example, the new parameter can include, but is not limited to, "tdd-UL-DL-ConfigurationCommon-SN-FU" in SIB1 and / or ServingCellConfigCommon, among others. The (e.g., reference) subcarrier spacing in the second parameters may be limited in some cases. With respect to the TDD UL / DL configuration for an SN FU indicated by the new parameters to an SN CU in a first frequency band / carrier (e.g., an SN CU working frequency band / carrier in the FR1 frequency band, etc.), this TDD UL / DL configuration may correspond to or be similar to the TDD UL / DL configuration of the BS that it indicates to one or more UEs in a second frequency band / carrier (e.g., an SN FU working frequency band / carrier in the FR2 frequency band, etc.).

[0018] In some deployments, the third parameter may be semi-statically configured (e.g., via RRC signaling) and / or may be dedicated (e.g., device-specific, link-specific, SN-specific, etc.) or UE-specific (e.g., device-specific) to control reception and / or transmission of a particular link, etc. For example, as part of the third parameter, the parameter "tdd-UL-DL-ConfigurationDedicated" in ServingCellConfig may be used for the SN CU for the SN CU (e.g., the first link).

[0019] In various aspects, the fourth parameter can be semi-statically configured (e.g., via RRC signaling) and / or can be dedicated or UE-specific. For example, as part of the fourth parameter, a new parameter can be defined for the SN CU (e.g., in the ServingCellConfig used in indicating the TDD UL / DL configuration), such as to be used for the SN FU. For example, a new parameter "tdd-UL-DL-ConfigurationDediated-SN-FU" in the ServingCellConfig, if any, can be defined.

[0020] In some cases, new parameters (e.g., tdd-UL-DL-ConfigurationDedicated-SN-FU) can be assigned by TDD-UL-DL-ConfigDedicated, which can be similar to the currently defined parameters in the specification and / or extended parameters, e.g., including at least subcarrier spacing. In some cases, new parameters (e.g., tdd-UL-DL-ConfigurationDedicated-SN-FU) can be assigned by TDD-UL-DL-ConfigCommon and / or new parameters, e.g., including at least subcarrier spacing.

[0021] In various implementations, the fifth parameter can include or correspond to a MAC CE, a UE-specific, and / or a group-common DCI. For example, the BS can indicate / provide a fifth TDD UL / DL configuration parameter to be used for the SN CU-SN CU, etc. The fifth parameter can be at least one of a MAC CE, a UE-specific, and / or a group-common DCI, such as a DCI format. If the fifth parameter is DCI signaling, the fifth parameter can be scrambled with a new SN-specific, link-specific, service type-specific, and / or SN logical unit-specific RNTI.

[0022] In some deployments, the sixth parameter may be at least one of a MAC CE, a UE-specific, and / or a group-common DCI. For example, the BS may indicate a sixth TDD UL / DL configuration parameter to be used for the SN FU-SN CU, etc., which may be at least one of a MAC CE, a UE-specific, and / or a group-common DCI, such as a DCI format or a new DCI. If the sixth parameter is DCI signaling, the sixth parameter may be scrambled by a new SN-specific, link-specific, service type-specific, and / or SN logical unit-specific RNTI.

[0023] In various configurations, the system and method of the technical solution may provide / indicate a single set of TDD / UL / DL configuration parameters to improve the accuracy of SN transmission control and the flexibility of SN in network deployment. For example, a BS may indicate one set of TDD UL / DL configuration parameters to an SN (e.g., an SN CU). The set of TDD UL / DL configuration parameters may be utilized for SN CU transmission and / or reception. The TDD UL / DL configuration for SN FU transmission and / or reception may be implicitly obtained / indicated / received / determined by the indicated TDD UL / DL configuration of the SN CU.

[0024] In some aspects, the BS can indicate (e.g., reference) subcarrier spacing of an SN FU to an SN CU. The SN CU can separate or aggregate / combine / aggregate the indicated TDD UL / DL configuration of the SN CU according to or based on the subcarrier spacing of the CU and / or FU to obtain a TDD UL / DL configuration for the SN FU. [Brief explanation of the drawings]

[0025] Various exemplary embodiments of the present solution are described in detail below with reference to the following figures or drawings. The drawings are provided for illustrative purposes only and merely depict exemplary embodiments of the present solution to facilitate the reader's understanding of the present solution. Therefore, the drawings should not be considered as limiting the scope, range, or applicability of the present solution. It should be noted that for clarity and ease of illustration, the drawings are not necessarily drawn to scale.

[0026] [Figure 1] FIG. 1 illustrates an example cellular communication network in which the techniques disclosed herein may be implemented according to certain embodiments of the present disclosure.

[0027] [Figure 2] FIG. 2 illustrates a block diagram of an example base station and user equipment device in accordance with some embodiments of the present disclosure.

[0028] [Figure 3] FIG. 3 illustrates a schematic diagram of transmission links between a BS-SN and an SN-UE according to some embodiments of the present disclosure.

[0029] [Figure 4] FIG. 4 illustrates a graph of two frequency ranges associated with each link according to some embodiments of the present disclosure.

[0030] [Figure 5]FIG. 5 illustrates a flow diagram of an example method for TDD configuration for an SN according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0031] (1. Mobile Communication Technology and Environment) 1 illustrates an example wireless communication network and / or system 100 in which the techniques disclosed herein according to certain embodiments of the present disclosure may be implemented. In the following discussion, the wireless communication network 100 may be any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and is referred to herein as “network 100.” Such example network 100 includes base stations 102 (hereinafter “BSs 102,” also referred to as wireless communication nodes), user equipment devices 104 (hereinafter “UEs 104,” also referred to as wireless communication devices) that may communicate with each other via communication links 110 (e.g., wireless communication channels), and clusters of cells 126, 130, 132, 134, 136, 138, and 140 overlaying a geographic area 101. In FIG. 1, the BSs 102 and the UEs 104 are contained within the respective geographic boundaries of the cells 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating in its allocated bandwidth and providing adequate wireless coverage to its intended users.

[0032] For example, the BS 102 may operate within an allocated channel transmission bandwidth to provide adequate coverage to the UE 104. The BS 102 and the UE 104 may communicate via downlink radio frames 118 and uplink radio frames 124, respectively. Each radio frame 118 / 124 may be further divided into subframes 120 / 127, which may include data symbols 122 / 128. In this disclosure, the BS 102 and the UE 104 are generally described herein as non-limiting examples of “communication nodes” that may practice the methods disclosed herein. Such communication nodes may be capable of wireless and / or wired communication in accordance with various embodiments of the present solution.

[0033] 2 illustrates a block diagram of an exemplary wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM / OFDMA signals) in accordance with some embodiments of the present solution. System 200 may include components and elements configured to support known or conventional operational features that need not be described in detail herein. In one illustrative embodiment, system 200 can be used to communicate (e.g., transmit and receive) data symbols within a wireless communication environment, such as wireless communication environment 100 of FIG. 1, as described above.

[0034] The system 200 generally includes a base station 202 (hereinafter “BS 202”) and a user equipment device 204 (hereinafter “UE 204”). The BS 202 includes a BS (base station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each of which is coupled and interconnected, as needed, via a data communication bus 220. The UE 204 includes a UE (user equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each of which is coupled and interconnected, as needed, via a data communication bus 240. The BS 202 communicates with the UE 204 via a communication channel 250, which may be any wireless channel or other medium suitable for the transmission of data as described herein.

[0035] As will be understood by those skilled in the art, system 200 may further include any number of modules other than those shown in FIG. 2 . Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein may be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, the various illustrative components, blocks, modules, circuits, and steps are described generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software may depend on the particular application and design constraints imposed on the overall system. Those skilled in the art familiar with the concepts described herein may implement such functionality in an appropriate manner for each particular application, but such implementation decisions should not be interpreted as limiting the scope of the present disclosure.

[0036] According to some embodiments, the UE transceiver 230 may be referred to herein as an “uplink” transceiver 230 including a radio frequency (RF) transmitter and an RF receiver, each with circuitry coupled to an antenna 232. A duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in a time-duplexed manner. Similarly, according to some embodiments, the BS transceiver 210 may be referred to herein as a “downlink” transceiver 210 including an RF transmitter and an RF receiver, each with circuitry coupled to an antenna 212. A downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in a time-duplexed manner. The operation of the two transceiver modules 210 and 230 may be coordinated in time such that the downlink transmitter is coupled to the downlink antenna 212 at the same time that the uplink receiver circuitry is coupled to the uplink antenna 232 for reception of transmissions over the wireless transmission link 250. Conversely, the operation of the two transceivers 210 and 230 may be coordinated in time such that the uplink transmitter is coupled to the uplink antenna 232 at the same time that the downlink receiver is coupled to the downlink antenna 212 for reception of transmissions over the wireless transmission link 250. In some embodiments, there is close time synchronization with minimal guard time between duplex direction changes.

[0037] The UE transceiver 230 and the base station transceiver 210 are configured to communicate over a wireless data communication link 250 and cooperate with appropriately configured RF antenna arrangements 212 / 232 that can support particular wireless communication protocols and modulation schemes. In some demonstrative embodiments, the UE transceiver 210 and the base station transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that the present disclosure is not necessarily limited in application to particular standards and associated protocols. Rather, the UE transceiver 230 and the base station transceiver 210 may be configured to support alternative or additional wireless data communication protocols, including future standards or variations thereof.

[0038] According to various embodiments, the BS 202 may be, for example, an evolved nodeB (eNB), a serving eNB, a target eNB, a femto station, or a pico station. In some embodiments, the UE 204 may be embodied in various types of user devices, such as a mobile phone, a smartphone, a personal digital assistant (PDA), a tablet, a laptop computer, a wearable computing device, etc. The processor modules 214 and 236 may be implemented or realized using a general-purpose processor, a content-addressable memory, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array, any suitable programmable logic device, respective gate or transistor logic, respective hardware components, or any combination thereof, designed to perform the functions described herein. As such, a processor may be realized as a microprocessor, a controller, a microcontroller, a state machine, or the like. A processor may also be implemented as a combination of computing devices, e.g., a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration.

[0039] Furthermore, the steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied in hardware, firmware, a software module, or any practical combination thereof, executed directly by processor modules 214 and 236, respectively. Memory modules 216 and 234 may be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. In this regard, memory modules 216 and 234 may be coupled to processor modules 210 and 230, respectively, such that processor modules 210 and 230 may read information from and write information to memory modules 216 and 234, respectively. Memory modules 216 and 234 may also be integrated within their respective processor modules 210 and 230. In some embodiments, memory modules 216 and 234 may each include cache memory for storing temporary variables or other intermediate information during execution of instructions to be executed by processor modules 210 and 230, respectively. Memory modules 216 and 234 may also each include non-volatile memory for storing instructions to be executed by processor modules 210 and 230, respectively.

[0040] The network communications module 218 generally represents the hardware, software, firmware, processing logic, and / or other components of the base station 202 that enable bidirectional communications between the base station transceiver 210 and other network components and communication nodes configured to communicate with the base station 202. For example, the network communications module 218 may be configured to support Internet or WiMAX traffic. In a typical deployment, without limitation, the network communications module 218 provides an 802.3 Ethernet interface so that the base station transceiver 210 may communicate with conventional Ethernet-based computer networks. As such, the network communications module 218 may include a physical interface for connection to a computer network (e.g., a mobile switching center (MSC)). As used herein with respect to specified operations or functions, the terms “configured for,” “configured to,” and conjugations thereof, refer to a device, component, circuit, structure, machine, signal, etc. that is physically constructed, programmed, formatted, and / or arranged to perform the specified operations or functions.

[0041] The Open Systems Interconnection (OSI) model (referred to herein as the "Open Systems Interconnection Model") is a conceptual and logical layout that defines network communications used by systems (e.g., wireless communication devices, wireless communication nodes) that open them to interconnect and communicate with other systems. The model is divided into seven subcomponents or layers, each of which represents a conceptual collection of services provided to the layers above and below it. The OSI model also defines logical networks and effectively describes computer packet transfers by using different layer protocols. The OSI model may also be referred to as the seven-layer OSI model or seven-layer model. In some embodiments, the first layer may be the physical layer. In some embodiments, the second layer may be the medium access control (MAC) layer. In some embodiments, the third layer may be the radio link control (RLC) layer. In some embodiments, the fourth layer may be the packet data convergence protocol (PDCP) layer. In some embodiments, the fifth layer may be the radio resource control (RRC) layer. In some embodiments, the sixth layer is a non-access stratum (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer may be another layer.

[0042] Various exemplary embodiments of the present solution are described below with reference to the accompanying figures to enable those skilled in the art to make and use the present solution. As will be apparent to those skilled in the art, after perusing this disclosure, various changes or modifications of the examples described herein can be made without departing from the scope of the present solution. Thus, the present solution is not limited to the exemplary embodiments and applications described and illustrated herein. In addition, the specific order or hierarchy of steps in the methods disclosed herein is merely an example approach. Based on design preferences, the specific order or hierarchy of steps in a disclosed method or process can be rearranged while remaining within the scope of the present solution. Thus, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or acts in a sample order, and that the present solution is not limited to the specific order or hierarchy presented, unless expressly stated otherwise. 2. Systems and Methods for TDD Configuration for SNs

[0043] In some systems (e.g., 5G New Radio (NR), Next Generation (NG) systems, 3GPP systems, and / or other systems), network-controlled repeaters may be introduced as an enhancement over traditional RF repeaters, with the network-controlled repeaters having the capability to receive and / or process side control information from the network. The side control information may enable the network-controlled repeater to perform / execute / operate its amplify-and-forward operations in a more efficient manner. Some benefits may include at least mitigation of unnecessary noise amplification, transmission and reception with better spatial directionality, and / or simplified network integration.

[0044] A network-controlled repeater (NCR) may be considered a stepping stone to a reconfigurable intelligent surface (RIS). RIS nodes can adjust the phase and amplitude of received signals to improve / extend coverage (e.g., network communication coverage). As discussed herein, network nodes, including but not limited to network-controlled repeaters, smart repeaters, reconfigurable intelligent surfaces (RIS), and integrated access backhaul (IAB), may be represented, referred to, or provided as smart nodes (SNs) (e.g., network nodes) for simplicity. For example, an SN may include, correspond to, or refer to a type of network node for assisting the BS 102 in improving coverage (e.g., avoiding / avoiding obstacles / jamming, increasing transmission range, etc.).

[0045] However, in some cases, the frequency band of the C link (e.g., communication / control link or SN CU) may be in a different frequency band than the F link (e.g., forward link or SN FU). For example, the two operating frequency bands may be out-of-band. When the C link and the F link are located out-of-band, the number of DL symbols / slots, the number of UL symbols / slots, the number of flexible symbols / slots, the reference subcarrier spacing, and / or the periodicity in the TDD UL / DL configurations of the C link and the F link (e.g., among other parameters) may be different. Therefore, the TDD configurations of the C link and the F link may be different and cannot be assumed to be the same.

[0046] Furthermore, in some cases, an SN FU may include a radio frequency (RF) unit that cannot, by itself, detect signals to obtain its TDD configuration. When an SN CU controls SN FU transmission based on the TDD configuration of the C link (e.g., to perform on / off, beam management, and / or power control, etc.), the TDD configuration of the C link may cause resource collisions, interference, and / or performance loss because the TDD configuration of the C link may not be the same as the TDD configuration for the F link. Therefore, the systems and methods of the technical solutions discussed herein provide mechanisms, features, operations, or techniques for acquiring / achieving / obtaining the precise TDD configuration of the F link (e.g., SN FU), such as to precisely control the transmission (e.g., transmission operations or signaling) of the SN FU.

[0047] FIG. 3 illustrates a schematic diagram 300 of transmission links between the BS 102 and the SN 302 and between the SN 302 and the UE 104. The SN 302 can include or consist of at least two functional parts / components / units (e.g., functional entities), such as a communication unit (CU) (e.g., an SN CU, sometimes referred to as a first functional entity or unit) and a forwarding unit (FU) (e.g., an SN FU, sometimes referred to as a second functional entity or unit). The functional entities can support different functions. For example, an SN CU can be a network controlled repeater (NCR) MT. In another example, an SN FU can be an NCR forwarder / forwarder (Fwd). The SN CU operates / behaves similarly to or includes similar features to the UE 104, e.g., can receive and decode side control information from the BS 102. The SN CU can be a control unit, controller, mobile terminal (MT), part of a UE, a third-party IoT device, etc. The SN FU may perform intelligent amplify and forward operations using the side control information received by the SN CU. The SN FU may be a radio unit (RU), a RIS, etc. For simplicity, a CU (e.g., an SN CU) and a FU (e.g., an SN FU) may correspond to or refer to a first unit and a second unit, respectively.

[0048] The transmission links between the BS 102 and the SN 302 and between the SN 302 and the UE 104 as shown in FIG. 4 may be defined / described / provided as follows: C1: Control link from SN CU to BS (e.g., C link or first communication link) C2: Control link from BS to SN CU (e.g., C link or second communication link) F1: forwarding link from SN FU to BS (e.g., F link or first forwarding link, which in this case may be a backhaul link) F2: forwarding link from BS to SN FU (e.g., F link or second forwarding link, which in this case may be a backhaul link) F3: forwarding link from UE to SN FU (e.g., F link or third forwarding link, which in this case may be an access link) F4: forwarding link from SN FU to UE (e.g., F link or fourth forwarding link, which may be an access link in this case)

[0049] A control link (e.g., sometimes referred to as a communication link) may refer to (or mean) that signals from one side will be detected and decoded by the other side so that information transmission within the control link can be utilized to control the status of a forwarding link (e.g., a backhaul link and / or an access link). A forwarding link may mean that signals from the BS 102 or the UE 104 are unknown to the SN FU. In this case, the SN FU can amplify and forward the signals without decoding them. For example, the F1 and F3 links may correspond to (or be associated with) full uplink (UL) forwarding links (e.g., backhaul links and access links, respectively) from the UE 104 to the BS 102, with F1 being the SN FU UL forwarding link. Additionally, the F2 and F4 links may correspond to (or be associated with) full DL forwarding links (e.g., backhaul links and access links, respectively) from the BS 102 to the UE 104, with F4 being the SN FU DL forwarding link. The F1 and F2 links may correspond to (or may be referred to as) backhaul links, and the F3 and F4 links may correspond to (or may be referred to as) access links.

[0050] FIG. 4 illustrates a graph 400 of two frequency ranges associated with each link. For example, the frequency band of the C link (e.g., SN CU) may be in a different frequency band than the F link (e.g., SN FU), and the two operating frequency bands may be out-of-band. As shown, the C link may work / operate / function within Frequency Range 1 (FR1) for initial access and / or control the forwarding of the F link. The F link may work within Frequency Range 2 (FR2) for extending network availability. Thus, the two frequency bands may be out-of-band in at least one of the following cases: · The two frequency bands can correspond to different carriers. The two frequency bands may be located in different frequency bands based on or according to a specification (or initial configuration), etc.; and / or The two frequency bands may be in different frequency ranges (e.g., FR1 and FR2 (e.g., FR2-1 and / or FR2-2)).

[0051] For example, if the CU controls FU transmission (e.g., transmission functionality) based on the TDD configuration of the C link to perform on / off, beam management, and / or power control, etc., resource collisions, interference, and / or performance loss may occur as a result of the TDD configuration of the C link being different from the TDD configuration of the F link. Thus, the systems and methods discussed herein can provide mechanisms / techniques for precise TDD configuration of the F link for enhanced precision in controlling FU transmission (e.g., transmission operation / functionality).

[0052] In various implementations, the C link for SN CU transmission and / or reception may include at least one of the following links: a first communication / control link (e.g., C1) from the BS 102 to an SN CU (e.g., in the SN 302); and / or A second communication link (e.g., C2) from the SN CU to the BS 102

[0053] In various arrangements, the F link used for SN FU transmission and / or reception may include at least one of the following links: A first forwarding link (e.g., F1) from BS 102 to the SN FU A second forwarding link (e.g., F2) from the SN FU to BS 102 a third forwarding link (e.g., F3) from the SN FU to the UE 104, and / or A fourth forwarding link (e.g., F4) from the UE 104 to the SN FU (Example Implementation 1 - Two Sets of TDD UL / DL Configuration Parameters)

[0054] In various arrangements, the BS 102 may indicate multiple sets (e.g., two sets) of TDD UL / DL configuration parameters to the SN 302 (e.g., an SN CU). For example, the two sets may include a first set of TDD configuration parameters for SN CU transmission / reception and a second set of TDD configuration parameters for SN FU transmission / reception. In this case, the second set may be used / configured for the SN CU to control SN FU transfer.

[0055] For example, in addition to indicating to the SN CU a (e.g., first) set of TDD UL / DL configuration parameters (e.g., cell-specific and / or dedicated TDD configuration) to be used for the SN CU, the BS 102 may indicate to the SN CU another (e.g., second) set of TDD UL / DL configuration parameters to be used for the SN FU. For example, the SN CU may use the second set of TDD configuration parameters to control SN FU transmission, on / off (e.g., enable / disable, true / false, activated / deactivated, etc.) state / condition, beam management, and / or power control. In various implementations, a set of TDD configuration parameters may refer to, for example, a single TDD configuration parameter or a combination of multiple TDD configuration parameters.

[0056] In various deployments, the two sets of TDD configuration parameters indicated / provided / configured / transmitted / sent by the BS 102 to the SN 302 (or SN CU) may include at least one of the following: A first set of TDD UL / DL configuration parameters for the SN CU may be indicated to the SN CU (e.g., configured for the first link). The first set may include at least one of the first, third, and / or fifth TDD UL / DL configuration parameters. A second set of TDD UL / DL configuration parameters for the SN FU may be indicated to the SN CU (e.g., configured for the second link). The second set may include at least one of the second, fourth, and / or sixth TDD UL / DL configuration parameters. (First TDD UL / DL configuration parameter)

[0057] In some implementations, the BS 102 may indicate to the SN CU at least one first TDD UL / DL configuration parameter to be used for the SN CU (e.g., as part of a first set of TDD configuration parameters). The first parameter may be semi-statically configured (e.g., via system information and / or RRC signaling) and / or common or cell-specific (e.g., with respect to SN FUs and / or UEs in a cell with a first frequency band / carrier). The first parameter may be indicated based on, according to, or via at least one of tdd-UL-DL-ConfigurationCommon and / or ServingCellConfigCommon in System Information Block Type 1 (SIB1), such as for the TDD configuration to be used for the SN CU. As provided / described in an example TDD-UL-DL-ConfigCommon below, the TDD UL / DL configuration for the SN CU may include at least one of a reference subcarrier spacing, a periodicity, a number of DL slots, a number of DL symbols, a number of UL slots, and / or a number of UL symbols, etc. [Table 1] (Second TDD UL / DL configuration parameter)

[0058] In various implementations, the BS 102 can indicate at least one second TDD UL / DL configuration parameter to the SN CU (e.g., as part of a second set of TDD configuration parameters), where the second parameter can be used for the SN FU. The second parameter can be semi-statically configured (e.g., via system information and / or RRC signaling) and can be common or cell-specific (e.g., for SN FUs and / or UEs in a cell with a second frequency band / carrier). In some cases, new parameters can be defined / provided / configured for the SN CU (e.g., in SIB1 and / or ServingCellConfigCommon) for indicating the TDD UL / DL configuration for the SN FU. For example, new parameters tdd-UL-DL-ConfigurationCommon-SN-FU and / or ServingCellConfigCommon in SIB1 can be defined / provided in the following example: [Table 2]

[0059] In some implementations, the second TDD UL / DL configuration for the SN-FU can include at least one of a reference subcarrier spacing, a periodicity, a number of DL slots, a number of DL symbols, a number of UL slots, and / or a number of UL symbols, etc. The new parameters (e.g., tdd-UL-DL-ConfigurationCommon-SN-FU) can be assigned by, for example, TDD-UL-DL-ConfigCommon.

[0060] In some cases, the (e.g., reference) subcarrier spacing included as part of the second configuration parameters may be limited. In some scenarios, the SN CU may be deployed in a low band and the SN FU may be deployed in a high band (e.g., relative to the low band), and the subcarrier spacing used by the SN FU may be limited, for example. For example, assuming that the SN CU works / is operable / functions in the FR1 band and the SN FU works in the FR2 band, the (e.g., reference) subcarrier spacing in the new parameters for the FU may be equal to or greater than a certain value, such as 60 kHz or 120 kHz, among others. In other scenarios / cases, the (e.g., reference) subcarrier spacing in the new parameters for the FU may be less than a certain value, for example, 60 kHz or 120 kHz, among others. The value (e.g., upper limit / upper limit value / upper threshold or lower limit) may be predetermined / pre-configured, for example, according to specifications, the configuration of the BS 102 and / or SN 302, and / or the capabilities of the SN 302 (e.g., support, compatibility, etc.), among other criteria.

[0061] In some implementations, the TDD UL / DL configuration indicated by, according to, or based on this new parameter for an SN FU (e.g., indicated to an SN CU) in a first frequency band / carrier (e.g., an SN CU working frequency band / carrier in FR1, etc.) may include (may correspond to, or be) at least one of the following: Similar to the TDD UL / DL configuration of the BS 102 (e.g., gNB or wireless communication node) shown to one or more UEs 104 in a second frequency band / carrier (e.g., SN FU working frequency band / carrier in FR2, etc.) similar to the TDD UL / DL configuration of the BS 102 indicated through / via SIB1 and / or ServingCellConfigCommon to one or more UEs 104 in the second frequency band / carrier; and / or A combination of common and dedicated configurations of the BS 102 shown to one or more UEs 104 in a second frequency band / carrier (Third TDD UL / DL configuration parameter)

[0062] The BS 102 may indicate to the SN CU (e.g., as part of the first set of TDD UL / DL configuration parameters) at least one third TDD UL / DL configuration parameter to be used for the SN CU. The third parameter may be semi-statically configured (e.g., via RRC signaling) and may be dedicated (e.g., device-specific, link-specific, and / or SN-specific, etc.), UE-specific, or SN-specific, such as for controlling reception and / or transmission over the respective link (e.g., in this case, the first link).

[0063] In some implementations, the parameter tdd-UL-DL-ConfigurationDedicated in the ServingCellConfig can be used to indicate to the SN CU the TDD UL / DL configuration to be used for the SN CU. The TDD UL / DL configuration to be used for the SN CU can include at least one of a slot index, a number of DL symbols, and / or a number of UL symbols, etc., which can be provided / indicated in the TDD-UL-DL-ConfigDedicated, examples of which can be provided as follows: [Table 3] (4th TDD UL / DL configuration parameter)

[0064] In various arrangements, the BS 102 may indicate to the SN CU at least one fourth TDD UL / DL configuration parameter to be used for the SN FU (e.g., as part of the second set of TDD UL / DL configuration parameters). The fourth parameter may be semi-statically configured (e.g., via RRC signaling) and may be dedicated (e.g., equipment-specific, link-specific, SN-specific, etc.), UE-specific, and / or SN-specific. In some cases, a new parameter may be defined / configured (e.g., in ServingCellConfig) to be used for indicating the TDD UL / DL configuration to be used for the SN FU-SN CU. For example, tdd-UL-DL-ConfigurationDediated-SN-FU may be configured as a new parameter (e.g., defined in ServingCellConfig), an example of which is provided below. [Table 4]

[0065] In some implementations, one or more configurations (e.g., implementations, options, instances, alternatives, configurations, etc.) of the fourth TDD UL / DL configuration parameter may be considered. For example, the fourth TDD UL / DL configuration parameter may be configured as follows: (4th TDD UL / DL configuration parameter - Configuration 1)

[0066] In some implementations, a new parameter (e.g., tdd-UL-DL-ConfigurationDedicated-SN-FU) can be assigned by TDD-UL-DL-ConfigDedicated. TDD-UL-DL-ConfigDedicated may be similar to the currently / originally defined parameter TDD-UL-DL-ConfigDedicated in the specification (e.g., including similar elements, descriptions, and / or features, etc.) or may include at least one extended parameter including, among others, subcarrier spacing, etc. Examples of new parameters can be shown as follows: [Table 5] (4th TDD UL / DL configuration parameter - Configuration 2)

[0067] In some cases, new parameters (e.g., tdd-UL-DL-ConfigurationDedicated-SN-FU) can be assigned by TDD-UL-DL-ConfigCommon and / or by new parameters including, among others, at least subcarrier spacing, etc. Examples of new parameters in this case can be shown as follows: [Table 6] (5th TDD UL / DL configuration parameter)

[0068] In some deployments, the BS 102 may indicate / provide to the SN CU (e.g., as part of the first set of TDD UL / DL configuration parameters) at least one fifth TDD UL / DL configuration parameter to be used for the SN CU. The fifth parameter may include or indicate, among other things, at least one of MAC CE, UE-specific, and / or group-common DCI (e.g., some predefined DCI format). (6th TDD UL / DL configuration parameter)

[0069] The BS 102 may indicate to the SN CU at least one sixth TDD UL / DL configuration parameter to be used for the SN FU (e.g., as part of the second set of TDD UL / DL configuration parameters). The sixth parameter may include, correspond to, or indicate at least one of a MAC CE, a UE-specific, and / or a group-common DCI (e.g., certain predefined DCI formats and / or new DCI). In various deployments, at least one of the two sets of TDD UL / DL configuration parameters may include additional TDD UL / DL configuration parameters, such as, for example, a seventh, eighth, and / or ninth TDD UL / DL configuration parameter.

[0070] In addition to these examples of two sets of TDD configuration parameters (e.g., indicated / provided by the BS 102 to the SN 302 (or SN CU)), some examples, among others, may include the following combinations of TDD UL / DL configuration parameters as part of the two sets: (Example 1 for two sets of TDD configuration parameters)

[0071] In some implementations, a first set of TDD UL / DL configuration parameters for an SN CU used for the SN CU can include first TDD UL / DL configuration parameters, and a second set of TDD UL / DL configuration parameters for an SN CU used for the SN FU can include second TDD UL / DL configuration parameters. (Example 2 for two sets of TDD configuration parameters)

[0072] In some implementations, the first set of TDD UL / DL configuration parameters can include a first TDD UL / DL configuration parameter, and the second set of TDD UL / DL configuration parameters can include second and fourth TDD UL / DL configuration parameters. (Example 3 for two sets of TDD configuration parameters)

[0073] In some implementations, the first set of TDD UL / DL configuration parameters may include first and third TDD UL / DL configuration parameters, and the second set of TDD UL / DL configuration parameters may include a second TDD UL / DL configuration parameter. (Example 4 for two sets of TDD configuration parameters)

[0074] In some implementations, the first set of TDD UL / DL configuration parameters may include first and third TDD UL / DL configuration parameters, and the second set of TDD UL / DL configuration parameters may include second and fourth TDD UL / DL configuration parameters. (Example 5 for two sets of TDD configuration parameters)

[0075] The first set of TDD UL / DL configuration parameters can include a first TDD UL / DL configuration parameter, and the second set of TDD UL / DL configuration parameters can include a fourth TDD UL / DL configuration parameter. (Example 6 for two sets of TDD configuration parameters)

[0076] The first set of TDD UL / DL configuration parameters may include first and third TDD UL / DL configuration parameters, and the second set of TDD UL / DL configuration parameters may include a fourth TDD UL / DL configuration parameter. (Example 7 for two sets of TDD configuration parameters)

[0077] The first set of TDD UL / DL configuration parameters may include first, third, and fifth TDD UL / DL configuration parameters, and the second set of TDD UL / DL configuration parameters may include second, fourth, and sixth TDD UL / DL configuration parameters.

[0078] Other combinations of TDD UL / DL configuration parameters included as part of the two sets of TDD UL / DL configuration parameters may also be used or indicated for the SN 302 (e.g., an SN CU). For example, any one or any combination of the first, third, and / or fifth TDD UL / DL configuration parameters may be included as part of the first set, and any one or any combination of the second, fourth, and / or sixth TDD UL / DL configuration parameters may be included as part of the second set. When / in response to the SN CU (e.g., a first unit) receiving the sets of TDD UL / DL configuration parameters, at least one of the SN CU and / or SN FU may control or implement reception and / or transmission over the respective links in accordance with the TDD UL / DL configuration parameters, etc., as discussed herein. (Example Implementation 2 - One Set of TDD UL / DL Configuration Parameters)

[0079] In various implementations, the BS 102 may indicate a set of TDD UL / DL configuration parameters to the SN 302 (e.g., an SN CU). For example, the set of TDD UL / DL configuration parameters may indicate / provide a TDD UL / DL configuration to be used for SN CU transmission / reception. Furthermore, the set of TDD UL / DL configuration parameters may implicitly indicate a TDD UL / DL configuration for SN FU transmission / reception (e.g., implicitly acquired / obtained / received by the SN CU).

[0080] In some implementations, a set of TDD UL / DL configuration parameters may include or correspond to a single configuration parameter or a combination of multiple configuration parameters. For example, a set of TDD UL / DL configuration parameters may include, among others, system information (e.g., parameters in SIB1), RRC signaling, MAC CE, and / or DCI signaling.

[0081] In various arrangements, the BS 102 may indicate (e.g., reference) subcarrier spacing of an SN FU to an SN CU. The SN CU may divide / split or aggregate / aggregate the indicated TDD UL / DL configuration of the SN CU according to the subcarrier spacing of the CU and the FU, such as to obtain at least one TDD UL / DL configuration of the SN FU. For example, the reference subcarrier spacing of the CU in FR1 may be a first predefined / predetermined / preconfigured frequency such as 30 kHz, and the reference subcarrier spacing of the FU in FR2 may be a second predefined frequency such as 120 kHz. In this case, one DL / UL slot / symbol in the TDD UL / DL configuration of the CU may be divided into, for example, four DL / UL slots / symbols in the TDD UL / DL configuration of the FU.

[0082] In some cases, the TDD UL / DL configuration indicated by the BS 102 to one or more UEs 104 in FR2 (e.g., the frequency band of the FUs and UEs 104) may differ from (e.g., not exactly match) the TDD UL / DL configuration indicated by the BS 102 to the CU in FR1 (e.g., the frequency band of the CU). For example, the TDD UL / DL configuration of the FU obtained by dividing the TDD UL / DL configuration of the CU may not be consistent with the actual / real TDD UL / DL configuration of the FU indicated by the BS 102 to the UE 104. In this case, to match the TDD UL / DL configuration indicated by the BS 102 to the UE 104 and the TDD UL / DL configuration indicated by the BS 102 to the CU, the two configurations may be scaled (e.g., according to their subcarrier spacing), for example, based on one or more parameters indicated in the TDD UL / DL configuration parameter set.

[0083] For example, the reference subcarrier spacing of the CU in FR1 may be 30 kHz, and the reference subcarrier spacing of the FU in FR2 may be 60 kHz. In this example, the TDD UL / DL configuration of the CU may be DDDFU. The TDD UL / DL configuration indicated by the BS 102 to the UE 104 may be DDDDDDFFUU (e.g., a power of 2, or in this case, a multiple of 2). Subsequently, the CU can divide the indicated TDD UL / DL configuration of the CU and obtain / obtain / determine the TDD UL / DL configuration of the FU, which may be the same as the TDD UL / DL configuration indicated by the BS 102 to the UE 104. In some cases, if the TDD UL / DL configuration indicated by the BS 102 to the UE 104 is, for example, DDDDDDFFFU (e.g., representing 10 slots, where "D" represents / corresponds to a downlink slot, "U" represents an uplink slot, and "F" represents a flexible slot that may include a flexible symbol), the CU may not derive the TDD UL / DL configuration of the FU from dividing the indicated TDD UL / DL configuration of the CU. The configuration of the slots can be configured for the UE 104 by the BS 102. (Example Implementation 3 - Out-of-Band C-Link and F-Link)

[0084] In various arrangements, with respect to a C link (e.g., a first link) and an F link (e.g., a second link) located out of band, the two links may share the same RF, or in some cases there may be leakage between the two links (e.g., they may not share the same RF from one link to another or between both links). In some implementations, when the C link and the F link are configured with different TDD patterns (e.g., directions) in the same symbol / slot, etc., the C link in the SN 302 can be configured as DL (e.g., C link), and the F link in the SN 302 can be configured as UL (e.g., at least one of the F link and / or F link). In a symbol / slot, the SN 302 can select at least one of the links or directions for transmitting and / or receiving data (e.g., from the BS 102 or the UE 104).

[0085] For example, if the C link (or CU) and F link (or FU) in SN 302 are configured with different TDD patterns or directions in symbols / slots, at least one of the following example scenarios may occur: The SN 302 may perform / execute / start C-link transmission and / or reception (e.g., via the first link); and / or the SN 302 may stop / terminate F-link transfer (e.g., transmission and / or reception via the second link). For example, the SN 302 may not be expected to transfer data (e.g., channels / signals) via the second link. In this case, a high priority may be given / assigned / provided to transmitting and / or receiving control information on the C-link (e.g., the first link). The SN 302 may perform F-link forwarding (e.g., transmission and / or reception via the second link); and / or the SN 302 may stop C-link forwarding and / or reception. For example, the SN 302 may not be expected to transmit and / or receive data (e.g., channels / signals) via the first link. In this case, high priority may be given to forwarding data from the BS 102 and / or the UE 104 due to availability between the entities. The SN 302 may perform UL operation and / or suspend DL operation. For example, if, at a symbol / slot, the C link at the SN 320 is configured as a DL (e.g., a C1 link) and the F link at the SN 302 is configured as a UL (e.g., an F2 link and / or an F4 link), the SN 302 may perform F link transmission (e.g., from the UE 104 to the BS 102) and suspend C link reception (e.g., from the BS 102). In another example, if, at a symbol / slot, the C link at the SN 302 is configured as a UL (e.g., a C2 link) and the F link at the SN 302 is configured as a DL (e.g., an F1 link and / or an F3 link), the SN 302 may perform C link transmission (e.g., to the BS 102) and suspend F link transmission (e.g., from the BS 102 to the UE 104). For example, the SN 302 may not be expected to transmit and / or receive data (e.g., channels / signals) via the downlink. The SN 302 may perform DL operation and / or suspend UL operation. For example, if, at a symbol / slot, the C link at the SN 302 is configured as DL (e.g., C1 link) and the F link at the SN 302 is configured as UL (e.g., F2 link and / or F4 link), the SN 302 may perform C link reception and suspend F link forwarding. In another example, if, at a symbol / slot, the C link at the SN 302 is configured as UL (e.g., C2 link) and the F link at the SN 302 is configured as DL (e.g., F1 link and / or F3 link), the SN 302 may perform F link forwarding and suspend C link transmission. For example, the SN 302 may not be expected to transmit and / or receive data (e.g., channels / signals) via the uplink. · High priority links and / or directions may be configured by the BS 102 and / or OAM to the SN 302, for example, through system information, RRC signaling, MAC CE, and / or DCI, among other types of signaling.

[0086] Referring now to Figure 5, depicted is a flow diagram of a method 500 for TDD configuration for an SN. Method 500 may be implemented using any of the components and devices detailed herein in conjunction with Figures 1-4. In overview, method 500 may include transmitting one or more messages (502). Method 500 may include receiving one or more messages (504).

[0087] Referring now to operation (502), in some implementations, a wireless communication node (e.g., a BS or gNB) may send / transmit / provide / signal one or more messages to a network node (e.g., an SN). The one or more messages may indicate or include an indication of a first set of TDD configuration parameters (e.g., TDD UL / DL configuration parameters) and a second set of TDD configuration parameters. The first set of TDD configuration parameters may be configured for a first link (e.g., a control / communication link or C-link). The second set of TDD configuration parameters may be configured for a second link (e.g., a forwarding link or F-link). Referring now to operation (504), after transmission by the wireless communication node, the network node may receive one or more messages.

[0088] In various implementations, the first link may include at least one of the following links: a first communication link from a wireless communication node to a network node (e.g., a C1 link), and / or a second communication link from a network node to a wireless communication node (e.g., a C2 link). In various arrangements, the second link may include at least one of the following links: a first forwarding link from a wireless communication node to a network node (e.g., an F1 link), a second forwarding link from a network node to a wireless communication node (e.g., an F2 link), a third forwarding link from a network node to a wireless communication device (e.g., a UE) (e.g., an F3 link), or a fourth forwarding link from a wireless communication device to a network node (e.g., an F4 link).

[0089] In various implementations, the first link may operate / function within or be configured with a first frequency band or carrier (e.g., FR1), and the second link may operate within or be configured with a second frequency band or carrier (e.g., FR2).

[0090] In various aspects, a network node may include a first unit (e.g., an SN CU) and a second unit (e.g., an SN FU). The two units of the network node may include or implement different functionality. In some cases, TDD configuration parameters may be used by the SN CU and / or the SN FU. For example, in response to the first unit receiving a first set of TDD configuration parameters, the first unit may control reception and / or transmission (e.g., of data / information) over a first link (e.g., at least one of the first communication link or the second communication link). In another example, in response to the first unit receiving a second set of TDD configuration parameters, the second unit may perform reception and / or transmission over the second link. In some cases (e.g., additionally or alternatively), in response to the first unit receiving the second set of TDD configuration parameters, the first unit may forward the second set of TDD configuration parameters to the second unit, such as to enable the second unit to control reception and / or transmission over a second link (e.g., at least one of the first, second, third, or fourth forwarding links).

[0091] In some implementations, when the first link and the second link are configured with different TDD patterns and / or different directions in symbols / slots, the network node may perform / execute / act at least one of the following. For example, the network node may perform transmission and / or reception via the first link and stop forwarding via the second link. In another example, the network node may perform forwarding via the second link and stop transmission and / or reception via the first link. In a further example, the network node may perform uplink operations (e.g., transmission and / or reception via the F2 and F4 links) and stop downlink operations (e.g., stop transmission and / or reception via the F1 and F3 links). In yet another example, the network node may perform downlink operations (e.g., transmission and / or reception via the F1 and F3 links) and stop UL operations (e.g., transmission and / or reception via the F2 and F4 links). In some cases, high priority links and / or directions may be configured to the network node by the wireless communication node and / or the operations, administration, and maintenance (OAM) node through, among other things, system information, RRC signaling, MAC CE, and / or DCI.

[0092] In various arrangements, the first set of TDD configuration parameters and the second set of TDD configuration parameters can each include various (e.g., multiple) parameters. For example, the first set of TDD configuration parameters can include a first parameter configured generally, cell-specifically, and / or semi-statically to control reception and / or transmission over the first link. The one or more messages can each be RRC signaling or system information (SI). The first set of TDD configuration parameters can include a third parameter configured device-specifically, device-specifically, and / or semi-statically to control reception and / or transmission over the first link. The first set of TDD configuration parameters can include a fifth parameter that is, among other things, a MAC CE and / or DCI.

[0093] In another example, the second set of TDD configuration parameters may include a second parameter configured generally, cell-specifically, and / or semi-statically to control reception and / or transmission over the second link. The one or more messages may each be RRC signaling or SI. The second set of TDD configuration parameters may include a fourth parameter configured device-specifically, device-specifically, and / or semi-statically to control reception and / or transmission over the second link. The second set of TDD configuration parameters may include a sixth parameter that is, among other things, a MAC CE and / or DCI.

[0094] In various arrangements, the network node may receive one or more messages from the wireless communication node indicating a single set of TDD configuration parameters. The single set of TDD configuration parameters may be configured, for example, for the first link and implicitly for the second link. In some implementations, the first link may include at least one of a first communication link from the wireless communication node to the network node and / or a second communication link from the network node to the wireless communication node. The second link may include, for example, at least one of a first forward link from the wireless communication node to the network node, a second forward link from the network node to the wireless communication node, a third forward link from the network node to the wireless communication device, and / or a fourth forward link from the wireless communication device to the network node.

[0095] In some implementations, a network node may include a first unit and a second unit. For example, in response to the first unit receiving a single set of TDD configuration parameters, the first unit may thereafter or subsequently control reception and / or transmission over the first link. In a further example, in response to the first unit receiving subcarrier spacing associated with the second unit, the first unit may determine a set of TDD configuration parameters, such as be configured to control reception and / or transmission over the second link based on the subcarrier spacing.

[0096] While various embodiments of the present solution have been described above, it should be understood that they are presented by way of example only, and not by way of limitation. Similarly, various diagrams may depict example architectures or configurations, which are provided to enable those skilled in the art to understand example features and functionality of the present solution. However, such skilled artisans will understand that the present solution is not limited to the example architectures or configurations shown, but can be implemented using various alternative architectures and configurations. In addition, as will be understood by those skilled in the art, one or more features of one embodiment can be combined with one or more features of another embodiment described herein. Thus, the scope and scope of the present disclosure should not be limited by any of the example embodiments described above.

[0097] It should also be understood that any reference to elements herein using a designation such as "first," "second," etc., generally does not limit the quantity or order of those elements. Rather, these designations may be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, reference to a first and a second element does not imply that only two elements may be employed or that the first element must precede the second element in some manner.

[0098] Additionally, those skilled in the art will understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, the data, instructions, commands, information, signals, bits, and symbols that may be referenced in the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0099] Those skilled in the art will further appreciate that any of the various illustrative logic blocks, modules, processors, means, circuits, methods, and functions described in connection with the aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementations, analog implementations, or a combination of the two), firmware, various forms of programs or design code incorporating instructions (which may be referred to herein for convenience as “software” or “software modules”), or any combination of these techniques. To clearly illustrate this interchangeability of hardware, firmware, and software, the various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these techniques, depends on the particular application and design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in various ways for each particular application, but such implementation decisions do not cause a departure from the scope of the present disclosure.

[0100] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, devices, components, and circuits described herein may be implemented in or by integrated circuits (ICs), which may include general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, or any combination thereof. The logic blocks, modules, and circuits may further include antennas and / or transceivers to communicate with various components within a network or device. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration for performing the functions described herein.

[0101] When implemented in software, the functions can be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media includes both computer storage media and communication media, including any medium that can enable a computer program or code to be transferred from one place to another. A storage medium can be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0102] As used herein, the term "module" refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purposes of discussion, various modules are described as individual modules; however, as would be apparent to one skilled in the art, two or more modules may be combined to form a single module that performs the associated functions according to embodiments of the present solution.

[0103] Additionally, memory or other storage devices and communication components may be employed in embodiments of the solution. It should be understood that, for purposes of clarity, the above description describes embodiments of the solution with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements, or domains may be used without departing from the solution. For example, functionality illustrated as being performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. References to specific functional units are therefore merely to suitable means for providing the described functionality, rather than to indicate a strict logical or physical structure or organization.

[0104] Various modifications of the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the scope of the present disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as recited in the following claims.

Claims

1. A wireless communication method, the wireless communication method comprising: receiving, by the network node, one or more messages from the wireless communication node indicating a first set of time division duplex (TDD) configuration parameters and a second set of TDD configuration parameters; the first set of TDD configuration parameters is configured for a first link; The wireless communication method, wherein the second set of TDD configuration parameters is configured for a second link.

2. The first link is a first communication link from the wireless communication node to the network node; or a second communication link from the network node to the wireless communication node; 10. The wireless communication method of claim 1, comprising at least one of:

3. The second link is a first forwarding link from said wireless communication node to said network node; a second forwarding link from said network node to said wireless communication node; a third forwarding link from the network node to a wireless communication device; or a fourth forwarding link from the wireless communication device to the network node; 10. The wireless communication method of claim 1, comprising at least one of:

4. 10. The wireless communication method of claim 1, wherein the first link operates on or is configured with a first frequency band or carrier, and the second link operates on or is configured with a second frequency band or carrier.

5. The network node includes a first unit and a second unit, and the method includes: controlling, by the first unit, reception and / or transmission over the first link in response to the first unit receiving the first set of TDD configuration parameters; and in response to the first unit receiving the second set of TDD configuration parameters, performing reception and / or transmission via the second link by the second unit, or transferring the second set of TDD configuration parameters by the first unit to the second unit, enabling the second unit to control reception and / or transmission via the second link. The wireless communication method of claim 1 , further comprising:

6. When the first link and the second link are configured with different TDD patterns or different directions in symbols / slots, the method further comprises: performing, by the network node, transmission or reception via the first link and stopping, by the network node, forwarding via the second link; performing, by said network node, a forwarding via said second link and stopping, by said network node, a transmission or reception via said first link; performing uplink operations by said network node and stopping downlink operations by said network node; or performing downlink operations by the network node and stopping UL operations by the network node; Including, 2. The wireless communication method of claim 1, wherein a high priority link or direction is configured by the wireless communication node or an Operation, Administration, and Maintenance (OAM) node to the network node through system information, RRC signaling, MAC CE, or DCI.

7. 2. The wireless communication method of claim 1, wherein the first set of TDD configuration parameters includes first parameters that are general, cell-specific, or semi-static for controlling reception and / or transmission over the first link.

8. 2. The wireless communication method of claim 1, wherein the second set of TDD configuration parameters includes second parameters that are general, cell-specific, or semi-static for controlling reception and / or transmission over the second link.

9. 10. The wireless communication method of claim 1, wherein the first set of TDD configuration parameters includes a third parameter that is device-specific, device-specific, or semi-static for controlling reception and / or transmission over the first link.

10. 10. The wireless communication method of claim 1, wherein the second set of TDD configuration parameters includes a fourth parameter that is device-specific, device-specific, or semi-static for controlling reception and / or transmission over the second link.

11. The wireless communication method according to any one of claims 7 to 10, wherein the one or more messages are each Radio Resource Control (RRC) signaling or System Information (SI).

12. The wireless communication method of claim 1 , wherein the first set of TDD configuration parameters includes a fifth parameter that is a Medium Access Control Control Element (MAC CE) or DCI.

13. The wireless communication method of claim 1 , wherein the second set of TDD configuration parameters includes a sixth parameter that is a MAC CE or a DCI.

14. A wireless communication method, the wireless communication method comprising: receiving, by the network node, one or more messages from the wireless communication node indicating a single set of time division duplex (TDD) configuration parameters; 10. A wireless communication method, wherein the single set of TDD configuration parameters is configured for a first link and implicitly for a second link.

15. The first link is a first communication link from the wireless communication node to the network node; or a second communication link from the network node to the wireless communication node; 15. The wireless communication method of claim 14, comprising at least one of:

16. The second link is a first forwarding link from said wireless communication node to said network node; a second forwarding link from said network node to said wireless communication node; a third forwarding link from the network node to a wireless communication device; or a fourth forwarding link from the wireless communication device to the network node; 15. The wireless communication method of claim 14, comprising at least one of:

17. The network node includes a first unit and a second unit, and the method includes: controlling, by the first unit, reception and / or transmission over the first link in response to the first unit receiving the single set of TDD configuration parameters; determining, by the first unit in response to the first unit receiving the subcarrier spacing associated with the second unit, a set of TDD configuration parameters configured to control reception and / or transmission over the second link based on the subcarrier spacing; The wireless communication method of claim 14, further comprising:

18. A wireless communication device comprising a processor and a memory, said processor configured to read a code from said memory and to perform a method according to any of claims 1-17.

19. 18. A computer program product comprising computer readable program medium code stored thereon, the code, when executed by a processor, causing the processor to perform a method according to any of claims 1-17.

Images