Systems and methods for TDD configuration of smart nodes

Abstract

Systems and methods for time division duplex (TDD) configuration of smart nodes (SNs) are presented. A network node may receive one or more messages from a wireless communication node. The one or more messages may indicate a first set of TDD configuration parameters and a second set of TDD configuration parameters. The first set of TDD configuration parameters may be configured for the first link. The second set of TDD configuration parameters may be configured for the 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 of smart nodes (SNs). Background Art

[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 believed to increase the flexibility of mobile operators in network deployment. For example, some systems or architectures introduce integrated access and backhaul (IAB) as a new type of network node that does not require a wired backhaul and can be enhanced in some other systems. Another type of network node is the RF repeater, which simply amplifies and retransmits any signal they receive. RF repeaters have been widely deployed in 2G, 3G, and 4G to supplement the coverage provided by conventional full-stack units. Summary of the invention

[0003] The exemplary embodiments disclosed herein are intended to solve problems related to one or more problems existing in the prior art, and provide additional features, which will become apparent when referring to the following detailed description in conjunction with the accompanying drawings. According to various embodiments, example systems, methods, devices, and computer program products are disclosed herein. However, it should be understood that these embodiments are presented in an exemplary manner, not restrictive, and it will be apparent to a person of ordinary skill in the art who has read this disclosure that various modifications can be made to the disclosed embodiments while remaining within the scope of this disclosure.

[0004] At least one aspect relates to a system, method, apparatus, or computer-readable medium. A network node (e.g., a smart node (SN)) may receive one or more messages from a wireless communication node (e.g., a base station (BS) or a gNB). The one or more messages may 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 may be configured for a first link. The second set of TDD configuration parameters may be configured for a second link.

[0005] In some arrangements, 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; or a second communication link from a network node to a wireless communication node. 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; a second forwarding link from a network node to a wireless communication node; a third forwarding link from a network node to a wireless communication device; or a fourth forwarding link from a wireless communication device to a network node.

[0006] In some arrangements, the first link may operate in a first frequency band or carrier, or may be configured with the first frequency band or carrier. The second link may operate in a second frequency band or carrier, or may be configured with the 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 a first set of TDD configuration parameters, the first unit may control reception and / or transmission on the first link. In response to the first unit receiving a second set of TDD configuration parameters, the second unit may perform reception and / or transmission on the second link, or the first unit may forward the second set of TDD configuration parameters to the second unit to allow the second unit to control reception and / or transmission on the second link.

[0007] In some arrangements, if the first link and the second link are configured with different TDD modes or different directions in symbols / time slots: the network node may perform transmission or reception on the first link and stop forwarding on the second link; the network node may perform forwarding on the second link and stop transmission or reception on the first link; the network node may perform uplink operation and stop downlink operation; or the network node may perform downlink operation and stop uplink operation. The high priority link or direction may be configured to the network node by the wireless communication node or the 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 a first parameter that is publicly, cell-specifically, or semi-statically configured to control reception and / or transmission on the first link. In various arrangements, the second set of TDD configuration parameters may include a second parameter that is publicly, cell-specifically, or semi-statically configured to control reception and / or transmission on the second link.

[0009] In some arrangements, the first set of TDD configuration parameters may include a third parameter that is device-specifically, device-specifically, or semi-statically configured to control reception and / or transmission on the first link. In various implementations, the second set of TDD configuration parameters may include a fourth parameter that is device-specifically, device-specifically, or semi-statically configured to control reception and / or transmission on the second link.

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

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

[0012] In some arrangements, 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; or a second communication link from a network node to a wireless communication node. In some implementations, the second link includes at least one of the following links: a first forwarding link from a wireless communication node to a network node; a second forwarding link from a network node to a wireless communication node; a third forwarding link from a network node to a wireless communication device; or a fourth forwarding 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. In response to the first unit receiving a single set of TDD configuration parameters, the first unit may control reception and / or transmission on the first link; and / or in response to the first unit receiving a subcarrier spacing associated with the second unit, the first unit may determine a set of TDD configuration parameters based on the subcarrier spacing, the set of TDD configuration parameters being configured to control reception and / or transmission on the second link.

[0014] The systems and methods proposed herein include novel methods for time division duplex (TDD) configuration of SN. Specifically, the systems and methods proposed herein discuss novel solutions for indicating / providing / signaling one or more groups (e.g., two groups) of TDD uplink (UL) and / or downlink (DL) configuration (e.g., UL, DL and / or flexible symbols / time slots) parameters to SN (e.g., SN CU) (e.g., by BS), for example, one group of TDD configurations is used for SN CU transmission and / or reception, while another group of TDD configurations is used for SN FU transmission and / or reception (e.g., another group of TDD configurations is used for SN CU to control SN FU). SN FU and SN CU can operate in the same or different frequency bands / carriers. Therefore, the system and method of the technical solution can introduce configuration parameters for TDD to enhance / improve / improve the accuracy of controlling the SN to forward signals (e.g., other signals) to at least one of the BS or user equipment (UE), thereby increasing the flexibility of SN in network deployment.

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

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

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

[0018] In some arrangements, 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), for example, to control reception and / or transmission of a specific link. For example, as part of the third parameter, the parameter "tdd-UL-DL-ConfigurationDedicated" in the ServingCellConfig provided to the SN CU may be used for the SN CU (e.g., the first link).

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

[0020] In some cases, new parameters (e.g., tdd-UL-DL-ConfigurationDedicated-SN-FU) may be allocated by TDD-UL-DL-ConfigDedicated. For example, TDD-UL-DL-ConfigDedicated may be similar to the parameters currently defined in the specification and / or include enhanced parameters at least for subcarrier spacing. In some cases, for example, new parameters (e.g., tdd-UL-DL-ConfigurationDedicated-SN-FU) may be allocated by TDD-UL-DL-ConfigCommon and / or new parameters at least for subcarrier spacing.

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

[0022] In some arrangements, 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 the SN CU, e.g., for the SN FU, which may be at least one of a MAC CE, a UE-specific and / or a group-common DCI, e.g., certain DCI formats or 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 arrangements, the system and method of the present technical solution may provide / indicate a single set of TDD / UL / DL configuration parameters to improve the accuracy of SN forwarding control and the flexibility of SN in network deployment. For example, the BS may indicate a set of TDD UL / DL configuration parameters to the SN (e.g., SNCU). The set of TDD UL / DL configuration parameters may be used 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 may indicate to the SN CU the (e.g., reference) subcarrier spacing for the SN FU. For example, the SN CU may split or assemble / 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 the TDD UL / DL configuration of the SN FU. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Various exemplary embodiments of the present solution are described in detail below with reference to the following drawings or figures. The drawings are provided for illustrative purposes only and depict only 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 breadth, scope or applicability of the present solution. It should be noted that for clarity and ease of illustration, these drawings are not necessarily drawn to scale.

[0026] Figure 1 An example cellular communication network in which the techniques disclosed herein may be implemented according to an embodiment of the present disclosure is shown;

[0027] Figure 2 A block diagram showing an example base station and user equipment apparatus according to some embodiments of the present disclosure;

[0028] Figure 3 A schematic diagram showing transmission links between a BS and a SN and between a SN and a UE according to some embodiments of the present disclosure is shown;

[0029] Figure 4a graph showing two frequency ranges associated with respective links according to some embodiments of the present disclosure; and

[0030] Figure 5 A flowchart of an example method for TDD configuration of a SN according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0031] 1. Mobile communication technology and environment

[0032] Figure 1 An example wireless communication network and / or system 100 is shown in which the techniques disclosed herein may be implemented according to an embodiment of the present disclosure. 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 an example network 100 includes a base station 102 (hereinafter referred to as "BS 102"; also referred to as a wireless communication node) and a user equipment device 104 (hereinafter referred to as "UE 104"; also referred to as a wireless communication device) that may communicate with each other via a communication link 110 (e.g., a wireless communication channel), and a cluster of cells 126, 130, 132, 134, 136, 138, and 140 covering a geographic area 101. In Figure 1 1, BS 102 and UE 104 are included within the respective geographic boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating with its allocated bandwidth to provide adequate radio coverage to its intended users.

[0033] For example, BS102 can work on the allocated channel transmission bandwidth to provide sufficient coverage to UE 104. BS102 and UE 104 can communicate via downlink radio frame 118 and uplink radio frame 124, respectively. Each radio frame 118 / 124 can be further divided into subframes 120 / 127, and subframes 120 / 127 can include data symbols 122 / 128. In the present disclosure, BS102 and UE 104 are described herein as non-limiting examples of "communication nodes", which can generally practice the methods disclosed herein. According to various embodiments of the present solution, such communication nodes may be capable of wireless and / or wired communication.

[0034] Figure 2A block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM / OFDMA signals) according to some embodiments of the present invention is shown. The system 200 may include components and elements configured to support known or conventional operating features that need not be described in detail herein. In one illustrative embodiment, as described above, the system 200 may be used in applications such as Figure 1 The wireless communication environment 100 may be used to communicate (eg, transmit and receive) data symbols.

[0035] The system 200 generally includes a base station 202 (hereinafter referred to as "BS 202") and a user equipment device 204 (hereinafter referred to as "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 connected and interconnected to each other via a data communication bus 220 as needed. 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 connected and interconnected to each other via a data communication bus 240 as needed. The BS 202 communicates with the UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for data transmission as described herein.

[0036] As will be appreciated by those skilled in the art, the system 200 may also include Figure 2 Modules of any number outside the modules shown. It will be appreciated by those skilled in the art that the various illustrative blocks, modules, circuits and processing logic described in conjunction with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware or any actual combination thereof. In order to clearly illustrate this interchangeability and compatibility of hardware, firmware and software, various illustrative components, blocks, modules, circuits and steps are generally described according to their functions. Whether this function is implemented as hardware, firmware or software depends on the specific application and the design constraints imposed on the entire system. People familiar with the concepts described herein can implement such functions in a manner suitable for each specific application, but such implementation decisions should not be interpreted as limiting the scope of the present disclosure.

[0037] According to some embodiments, the UE transceiver 230 may be referred to herein as an "uplink" transceiver 230, which includes a radio frequency (RF) transmitter and an RF receiver, each including circuitry coupled to an antenna 232. A duplex switch (not shown) may alternately couple the uplink transmitter or receiver to the uplink antenna in a time duplex manner. Similarly, according to some embodiments, the BS transceiver 210 may be referred to herein as a "downlink" transceiver 210, which includes an RF transmitter and an RF receiver, each including circuitry coupled to an antenna 212. The downlink duplex switch may alternately couple the downlink transmitter or receiver to the downlink antenna 212 in a time duplex manner. The operation of the two transceiver modules 210 and 230 may be coordinated in time such that the uplink receiver circuitry is coupled to the uplink antenna 232 when the downlink transmitter is coupled to the downlink antenna 212 to receive transmissions over the wireless transmission link 250. Instead, the operation of the two transceivers 210 and 230 may be coordinated in time such that the downlink receiver is coupled to the downlink antenna 212 while the uplink transmitter is coupled to the uplink antenna 232 to receive transmissions over the wireless transmission link 250. In some embodiments, there is a minimum guard time between changes in duplex direction to achieve tight time synchronization.

[0038] The UE transceiver 230 and the base station transceiver 210 are configured to communicate via a wireless data communication link 250 and cooperate with an appropriately configured RF antenna device 212 / 232 that can support a specific wireless communication protocol and modulation scheme. In some illustrative 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 to application to specific standards and related protocols. Instead, the UE transceiver 230 and the base station transceiver 210 can be configured to support alternative or additional wireless data communication protocols, including future standards or variants thereof.

[0039] According to various embodiments, for example, BS202 can be an evolved node B (eNB), a serving eNB, a target eNB, a femtocell or a microcell. In some embodiments, UE 204 can be embodied in various types of user devices, such as mobile phones, smart phones, personal digital assistants (PDAs), tablet computers, laptop computers, wearable computing devices, etc. Processor modules 214 and 236 can be implemented or completed with 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, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof for performing the functions described herein. In this way, the processor can be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor can also be implemented as a combination of a computing device, for example, a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a digital signal processor core, or any other such configuration.

[0040] In addition, the steps of the methods or algorithms described in conjunction with the embodiments disclosed herein may be directly embodied in hardware, in firmware, in software modules executed by the processor modules 214 and 236, respectively, or in any practical combination thereof. The memory modules 216 and 234 may be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this regard, the memory modules 216 and 234 may be connected to the processor modules 210 and 230, respectively, so that the processor modules 210 and 230 can read information from and write information to the memory modules 216 and 234, respectively. The memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230. In some embodiments, the memory modules 216 and 234 may each include a cache memory for storing temporary variables or other intermediate information during the execution of instructions executed by the 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.

[0041] The network communication module 218 generally represents the hardware, software, firmware, processing logic and / or other components of the base station 202 that enable bidirectional communication 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 communication module 218 can be configured to support Internet or WiMAX services. In a typical deployment, but not limited to, the network communication module 218 provides an 802.3 Ethernet interface so that the base station transceiver 210 can communicate with a traditional Ethernet-based computer network. In this way, the network communication module 218 can include a physical interface for connecting to a computer network (e.g., a mobile switching center (MSC)). The terms "configured for", "configured to" and their variations used herein for a specific operation or function refer to a device, component, circuit, structure, machine, signal, etc. that is physically constructed, programmed, formatted and / or arranged to perform a specific operation or function.

[0042] 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 are open to interconnection and communication with other systems. The model is divided into seven sub-parts or layers, each representing a conceptual set of services provided to the layers above and below it. The OSI model also defines a logical network and effectively describes computer packet transmission by using different layer protocols. The OSI model may also be referred to as a seven-layer OSI model or a seven-layer model. In some embodiments, the first layer may be a physical layer. In some embodiments, the second layer may be a medium access control (MAC) layer. In some embodiments, the third layer may be a radio link control (RLC) layer. In some embodiments, the fourth layer may be a packet data convergence protocol (PDCP) layer. In some embodiments, the fifth layer may be a radio resource control (RRC) layer. In some embodiments, the sixth layer may be a non-access (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer is another layer.

[0043] Various exemplary embodiments of the present solution are described below with reference to the accompanying drawings so that a person of ordinary skill in the art can make and use the present solution. After reading this disclosure, it will be apparent to a person of ordinary skill in the art that various changes or modifications may be made to the examples described herein without departing from the scope of the present solution. Therefore, 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 are merely exemplary methods. Based on design preferences, the specific order or hierarchy of steps of the disclosed methods or processes may be rearranged while remaining within the scope of the present solution. Therefore, a person of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or actions in a sample order, and unless otherwise expressly stated, the present solution is not limited to the specific order or hierarchy presented.

[0044] 2. System and method for TDD configuration of SN

[0045] 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 to conventional RF repeaters with the ability to receive and / or process auxiliary control information from the network. The auxiliary control information may allow the network-controlled repeater to perform / perform / operate its amplification and forwarding operations in a more efficient manner. Some benefits may include at least mitigation of unnecessary noise amplification, transmission and reception with better spatial directivity, and / or simplified network integration.

[0046] A network controlled repeater (NCR) can be considered a stepping stone to a reconfigurable smart surface (RIS). RIS nodes can adjust the phase and amplitude of a received signal to improve / enhance coverage (e.g., network communication coverage). As discussed herein, for simplicity, network nodes including but not limited to network controlled repeaters, smart repeaters, reconfigurable smart surfaces (RIS), integrated access and backhaul (IAB) may be represented, referred to, or provided as smart nodes (SN) (e.g., network nodes). For example, an SN may include, correspond to, or refer to a network node to help BS 102 improve coverage (e.g., avoid / get around congestion / obstacles, increase transmission range, etc.).

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

[0048] In addition, in some cases, the SN FU may include a radio frequency (RF) unit that itself cannot detect signals to obtain its TDD configuration. If the SN CU controls the SN FU forwarding (e.g., performing on / off, beam management and / or power control, etc.) based on the TDD configuration of the C-link, the TDD configuration of the C-link may cause resource conflicts, interference and / or performance losses because the TDD configuration of the C-link may be different from the TDD configuration of the F-link. Therefore, the system and method of the technical solution discussed in this article provide a mechanism, feature, operation or technology for obtaining / implementing / acquiring the accurate TDD configuration of the F-link (e.g., SN FU) so as to accurately control the forwarding of the SN FU (e.g., forwarding operation or signaling), for example.

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

[0050] like Figure 4As shown, the transmission links between BS 102 and SN 302 and between SN 302 and UE 104 may be defined / described / provided as follows:

[0051] - C1: control link from SN CU to BS (e.g., C-link or first communication link);

[0052] - C2: control link from BS to SN CU (e.g., C-link or second communication link);

[0053] - F1: forwarding link from SN FU to BS (e.g., F-link or first forwarding link,

[0054] In this case, it could be the backhaul link);

[0055] - F2: forwarding link from BS to SN FU (e.g., F-link or second forwarding link, which in this case can be a backhaul link)

[0056] - 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); and

[0057] - F4: forwarding link from SN FU to UE (eg, F-link or fourth forwarding link, which in this case may be an access link).

[0058] A control link (e.g., sometimes referred to as a communication link) may refer to or mean that a signal from one side will be detected and decoded by the other side so that the information transmitted in the control link can be used to control the state of a forwarding link (e.g., a backhaul link and / or an access link). A forwarding link may refer to a signal from BS102 or UE 104 that the SN FU is unaware of. In this case, the SN FU can amplify and forward the signal without decoding. For example, the F1 and F3 links may correspond to or be associated with a complete uplink (UL) forwarding link (e.g., a backhaul link and an access link, respectively) from UE104 to BS102, where F1 is a SN FU UL forwarding link. Additionally, the F2 and F4 links may correspond to or be associated with a complete DL forwarding link (e.g., a backhaul link and an access link, respectively) from BS102 to UE 104, where F4 is a SN FU DL forwarding link. The F1 and F2 links may correspond to or be referred to as a backhaul link, and the F3 and F4 links may correspond to or be referred to as an access link.

[0059] Figure 4A graph 400 of two frequency ranges associated with respective links is shown. For example, the frequency band of a C-link (e.g., SN CU) may be in a different frequency band than an F-link (e.g., SN FU), wherein the two operating frequency bands may be out-of-band. As shown, the C-link may work / operate / function in frequency range 1 (FR1) for initial access and / or control forwarding of the F-link. The F-link may operate in frequency range 2 (FR2) for extending network coverage. Thus, the two frequency bands may be out-of-band in at least one of the following cases:

[0060] The two frequency bands may correspond to different carriers;

[0061] The two frequency bands may be located in different frequency bands, for example, based on or according to a specification (or initial configuration); and / or

[0062] • The two frequency bands may be in different frequency ranges (eg, FR1 and FR2 (eg, FR2-1 and / or FR2-2)).

[0063] For example, if the CU controls FU forwarding (e.g., forwarding functions) based on the TDD configuration of the C-link, for example, performs on / off, beam management, and / or power control, resource conflicts, interference, and / or performance loss may occur because the TDD configuration of the C-link is different from the TDD configuration of the F-link. Therefore, the systems and methods discussed herein may provide mechanisms / techniques for accurate TDD configuration of the F-link to improve the accuracy of controlling the forwarding (e.g., forwarding operations / functions) of the FU.

[0064] In various implementations, the C-link used for SN CU transmission and / or reception may include at least one of the following links:

[0065] A first communication / control link (e.g., C1) from BS 102 to an SN CU (e.g., of SN 302); and / or

[0066] • A second communication link (eg, C2) from the SN CU to the BS 102.

[0067] In various arrangements, the F-link for SN FU transmission and / or reception may include at least one of the following links:

[0068] A first forwarding link (e.g., F1) from BS 102 to SN FU;

[0069] A second forwarding link (e.g., F2) from SN FU to BS 102;

[0070] A third forwarding link (e.g., F3) from the SN FU to the UE 104; and / or

[0071] • A fourth forwarding link (eg, F4) from UE 104 to SN FU.

[0072] Example Implementation 1 - Two Sets of TDD UL / DL Configuration Parameters

[0073] In various arrangements, BS 102 may indicate multiple sets (e.g., two sets) of TDD UL / DL configuration parameters to SN 302 (e.g., 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 SNFU transmission / reception. In this case, the second set may be used / configured for SN CU to control SN FU forwarding.

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

[0075] In various arrangements, 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:

[0076] • A first set of TDD UL / DL configuration parameters for the SN CU (eg, configured for the first link) may be indicated to the SN CU. The first set may include at least one of the first, third and / or fifth TDD UL / DL configuration parameters.

[0077] • A second set of TDD UL / DL configuration parameters for the SN FU (eg, configured for the second link) may be indicated to the SN CU. The second set may include at least one of the second, fourth and / or sixth TDD UL / DL configuration parameters.

[0078] First TDD UL / DL configuration parameters

[0079] In some implementations, BS 102 may indicate to the SN CU at least one first TDD UL / DL configuration parameter 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., for 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), e.g., for a TDD configuration for use by the SN CU. As provided / described in the following example TDD-UL-DL-ConfigCommon, 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.

[0080]

[0081] Second TDD UL / DL configuration parameters

[0082] In various implementations, the BS 102 may indicate at least one second TDD UL / DL configuration parameter (e.g., part of a second set of TDD configuration parameters) to the SN CU, where the second parameter may be used for the SN FU. The second parameter may be semi-statically configured (e.g., via system information and / or RRC signaling) and may 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, a new parameter may be defined / provided / configured (e.g., in SIB1 and / or ServingCellConfigCommon) for indicating the TDD UL / DL configuration for the SN FU to the SN CU. For example, a new parameter tdd-UL-DL-ConfigurationCommon-SN-FU in SIB1 and / or ServingCellConfigCommon may be defined / provided in the following example:

[0083] -------------------------------------------------

[0084] SIB1->ServingCellConfigCommonSIB->tdd-UL-DL-ConfigurationCommon-SN-FU,

[0085] and / or

[0086] ServingCellConfigCommon->tdd-UL-DL-ConfigurationCommon-SN-FU

[0087] -------------------------------------------------

[0088] In some implementations, the second TDD UL / DL configuration for the SN FU 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. For example, a new parameter (e.g., tdd-UL-DL-ConfigurationCommon-SN-FU) may be allocated by TDD-UL-DL-ConfigCommon.

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

[0090] In some implementations, the TDD UL / DL configuration indicated by the new parameter (e.g., indicated to the SN CU) of the SN FU in the first frequency band / carrier (e.g., the SN CU operating frequency band / carrier, e.g., in FR1), according to or based on the new parameter may include, correspond to, or be at least one of the following:

[0091] similar to the TDD UL / DL configuration of the BS 102 (e.g., a gNB or wireless communication node), indicating to one or more UEs 104 in a second frequency band / carrier (e.g., a SN FU operating band / carrier, e.g., in FR2);

[0092] Similar to the TDD UL / DL configuration of BS 102, indicated to one or more UEs 104 in the second frequency band / carrier by / via SIB1 and / or ServingCellConfigCommon; and / or

[0093] • A combination of public and dedicated configurations of the BS 102, indicated to one or more UEs 104 in the second frequency band / carrier.

[0094] Third TDD UL / DL configuration parameters

[0095] BS 102 may indicate at least one third TDD UL / DL configuration parameter for the SN CU (e.g., as part of the first set of TDD UL / DL configuration parameters) to 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, e.g., for controlling reception and / or transmission on a corresponding link (e.g., in this case, the first link).

[0096] In some implementations, the parameter tdd-UL-DL-ConfigurationDedicated in ServingCellConfig may be used to indicate to the SN CU the TDD UL / DL configuration for the SN CU. The TDD UL / DL configuration for the SN CU may include at least one of a time slot index, a number of DL symbols, and / or a number of UL symbols, etc., which may be provided / indicated in TDD-UL-DL-ConfigDedicated, an example of which may be provided as follows.

[0097]

[0098]

[0099] Fourth TDD UL / DL configuration parameters

[0100] In various arrangements, the BS 102 may indicate to the SN FU at least one fourth TDD UL / DL configuration parameter for the SN CU (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., device-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) for indicating the TDD UL / DL configuration for the SN CU to the SN FU. 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 as follows:

[0101]

[0102] In some implementations, one or more arrangements (e.g., implementations, options, situations, alternatives, configurations, etc.) of the fourth TDD UL / DL configuration parameters may be considered. For example, the fourth TDD UL / DL configuration parameters may be configured as follows:

[0103] Fourth TDD UL / DL configuration parameters—Arrangement 1:

[0104] In some implementations, a new parameter (e.g., tdd-UL-DL-ConfigurationDedicated-SN-FU) may be allocated by TDD-UL-DL-ConfigDedicated. TDD-UL-DL-ConfigDedicated may be similar to the parameter TDD-UL-DL-ConfigDedicated currently / initially defined in the specification (e.g., including similar elements, descriptions and / or features, etc.), or may include at least one enhanced parameter, e.g., including subcarrier spacing, etc. Examples of new parameters are as follows:

[0105] ServingCellConfig::=SEQUENCE{ ...

[0107] tdd-UL-DL-ConfigurationDedicated-SN-FU TDD-UL-DL-ConfigDedicatedOPTIONAL,--Cond TDD

[0108] Fourth TDD UL / DL configuration parameters—Arrangement 2:

[0109] In some cases, new parameters (e.g., tdd-UL-DL-ConfigurationDedicated-SN-FU) may be allocated by TDD-UL-DL-ConfigCommon and / or new parameters, for example, including at least subcarrier spacing, etc. An example of the new parameters in this case is as follows:

[0110] ServingCellConfig::=SEQUENCE{

[0111] tdd-UL-DL-ConfigurationDedicated-SN-FU TDD-UL-DL-ConfigCommonOPTIONAL,--Cond TDD

[0112] Fifth TDD UL / DL configuration parameters

[0113] In some arrangements, the BS 102 may indicate / provide at least one fifth TDD UL / DL configuration parameter for the SN CU to the SN CU (e.g., as part of the first set of TDD UL / DL configuration parameters). The fifth parameter may include or indicate at least one of a MAC CE, a UE-specific and / or group-common DCI (e.g., a certain predefined DCI format), etc.

[0114] Sixth TDD UL / DL configuration parameters

[0115] BS 102 may indicate at least one sixth TDD UL / DL configuration parameter for the SN FU to the SN CU (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., a certain predefined DCI format and / or a new DCI). In various arrangements, for example, at least one of the two sets of TDD UL / DL configuration parameters may include additional TDD UL / DL configuration parameters, such as the seventh, eighth, and / or ninth TDD UL / DL configuration parameters, etc.

[0116] As described herein, in addition to these examples, some of the other examples of two sets of TDD configuration parameters (e.g., indicated / provided by BS 102 to SN 302 (or SN CU)) may include the following combinations of TDD UL / DL configuration parameters as part of the two sets:

[0117] Example 1 of two sets of TDD configuration parameters

[0118] In some implementations, the first set of TDD UL / DL configuration parameters for the SN CU provided to the SN CU may include the first TDD UL / DL configuration parameters. The second set of TDD UL / DL configuration parameters for the SN FU provided to the SN CU may include the second TDD UL / DL configuration parameters.

[0119] Example 2 of two sets of TDD configuration parameters

[0120] In some implementations, the first set of TDD UL / DL configuration parameters may include a first TDD UL / DL configuration parameter.The second set of TDD UL / DL configuration parameters may include second and fourth TDD UL / DL configuration parameters.

[0121] Example 3 of two sets of TDD configuration parameters

[0122] In some implementations, the first set of TDD UL / DL configuration parameters may include first and third TDD UL / DL configuration parameters.The second set of TDD UL / DL configuration parameters may include second TDD UL / DL configuration parameters.

[0123] Example 4 of two sets of TDD configuration parameters

[0124] In some implementations, the first set of TDD UL / DL configuration parameters may include first and third TDD UL / DL configuration parameters.The second set of TDD UL / DL configuration parameters may include second and fourth TDD UL / DL configuration parameters.

[0125] Example 5 of two sets of TDD configuration parameters

[0126] The first set of TDD UL / DL configuration parameters may include a first TDD UL / DL configuration parameter. The second set of TDD UL / DL configuration parameters may include a fourth TDD UL / DL configuration parameter.

[0127] Example 6 of two sets of TDD configuration parameters

[0128] The first set of TDD UL / DL configuration parameters may include first and third TDD UL / DL configuration parameters. The second set of TDD UL / DL configuration parameters may include fourth TDD UL / DL configuration parameters.

[0129] Example 7 of two sets of TDD configuration parameters

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

[0131] 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 to the SN 302 (e.g., SN CU). For example, any one or 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 combination of the second, fourth, and / or sixth TDD UL / DL configuration parameters may be included as part of the second set. Upon / in response to the SN CU (e.g., first unit) receiving these TDD UL / DL configuration parameter sets, at least one of the SN CU and / or SN FU may control or perform reception and / or transmission on the corresponding link, for example, according to the TDD UL / DL configuration parameters discussed herein.

[0132] Example Implementation 2 - One set of TDD UL / DL configuration parameters

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

[0134] 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, this set of TDD UL / DL configuration parameters may include system information (e.g., parameters in SIB1), RRC signaling, MAC CE and / or DCI signaling, etc.

[0135] In various arrangements, BS 102 may indicate to the SN CU a (e.g., reference) subcarrier spacing for the SN FU. The SN CU may split / divide or assemble / aggregate the indicated TDD UL / DL configuration of the SN CU according to the subcarrier spacing of the CU and the FU, for example, 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, for example, 30 kHz, etc., and the reference subcarrier spacing of the FU in FR2 may be a second predetermined frequency, for example, 120 kHz, etc. In this case, for example, one DL / UL slot / symbol in the TDD UL / DL configuration of the CU may be split into four DL / UL slots / symbols in the TDD UL / DL configuration of the FU.

[0136] 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 bands of the FU and the UE 104) may be different from (e.g., not an exact match to) 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 splitting 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, in order 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, for example, the two configurations may be scaled based on one or more parameters indicated in the set of TDD UL / DL configuration parameters (e.g., according to their subcarrier spacing).

[0137] 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 BS102 to UE 104 may be DDDDDDFFUU (e.g., a power of 2, or in this case, a multiple of 2). Subsequently, the CU may split the indicated TDD UL / DL configuration of the CU to obtain / acquire / determine the TDD UL / DL configuration of the FU, which may be the same as the TDD UL / DL configuration indicated by BS102 to UE 104. In some cases, for example, if the TDD UL / DL configuration indicated by BS 102 to UE 104 is DDDDDDFFFU (e.g., representing 10 time slots, where "D" represents / corresponds to downlink time slots, "U" represents uplink time slots, and "F" represents flexible time slots, which may include flexible symbols), the CU does not obtain the TDD UL / DL configuration of the FU by dividing the indicated TDD UL / DL configuration of the CU. The configuration of the time slots may be configured by BS 102 to UE 104.

[0138] Example Implementation 3 - Out-of-Band C-Link and F-Link

[0139] In various arrangements, for the C-link (e.g., the first link) and the F-link (e.g., the second link) that are 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., from one link to the other, or between the two links that may not share the same RF). In some implementations, if the C-link and the F-link are configured with different TDD modes (e.g., directions), for example, in the same symbol / time slot, the C-link at the SN 302 may be configured as DL (e.g., C1 link) and the F-link at the SN 302 may be configured as UL (e.g., at least one of the F2 link and / or the F4 link). In the symbol / time slot, the SN 302 may select at least one link or direction to transmit and / or receive data (e.g., from the BS 102 or the UE 104).

[0140] For example, if the C-link (or CU) and the F-link (or FU) at the SN 302 are configured with different TDD modes or directions in symbols / time slots, at least one of the following example scenarios may occur:

[0141] SN 302 may perform / execute / initiate C-link transmission and / or reception (e.g., on the first link), and / or SN 302 may stop / terminate F-link forwarding (e.g., transmission and / or reception on the second link). For example, it may not be desirable for SN 302 to forward data (e.g., channel / signal) on the second link. In this case, a high priority may be given / assigned / provided to the transmission and / or reception control information in the C-link (e.g., the first link).

[0142] SN 302 may perform F-link forwarding (e.g., transmission and / or reception on the second link), and / or SN 302 may stop C-link transmission and / or reception. For example, it may not be desirable for SN 302 to transmit and / or receive data (e.g., channel / signal) on the first link. In this case, forwarding data from BS 102 and / or UE 104 may be given high priority for coverage between entities.

[0143] SN 302 may perform UL operations and / or stop DL operations. For example, if the C-link at SN 320 is configured as DL (e.g., C1 link) and the F-link at SN 302 is configured as UL (e.g., F2 link and / or F4 link), then in the symbol / time slot, SN 302 may perform F-link forwarding (e.g., from UE 104 to BS 102) and stop C-link reception (e.g., from BS 102). In another example, if the C-link at SN 302 is configured as UL (e.g., C2 link) and the F-link at SN 302 is configured as DL (e.g., F1 link and / or F3 link), then in the symbol / time slot, SN 302 may perform C-link transmission (e.g., to BS 102) and stop F-link forwarding (e.g., from BS 102 to UE 104). For example, it may not be desirable for SN 302 to transmit and / or receive data (eg, channels / signals) on the downlink.

[0144] SN 302 may perform DL operations and / or stop UL operations. For example, if the C-link at SN 320 is configured as DL (e.g., C1 link) and the F-link at SN 302 is configured as UL (e.g., F2 link and / or F4 link), then in the symbol / time slot, SN 302 may perform C-link reception and stop F-link forwarding. In another example, if the C-link at SN 302 is configured as UL (e.g., C2 link) and the F-link at SN 302 is configured as DL (e.g., F1 link and / or F3 link), then in the symbol / time slot, SN 302 may perform F-link forwarding and stop C-link transmission. For example, it may not be expected that SN 302 transmits and / or receives data (e.g., channel / signal) on the uplink.

[0145] • For example, the high priority link and / or direction may be configured by the BS 102 and / or OAM to the SN 302 via system information, RRC signaling, MAC CE and / or DCI, and other types of signaling.

[0146] Reference now Figure 5 , depicts a flow chart of a method 500 for TDD configuration of a SN. The method 500 may be used in conjunction with the present invention. Figures 1 to 4 In general, method 500 may include sending one or more messages (502). Method 500 may include receiving one or more messages (504).

[0147] Referring now to operation (502), and 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 the wireless communication node transmits, the network node may receive one or more messages.

[0148] 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).

[0149] In various implementations, the first link may work / operate / run in a first frequency band or carrier (e.g., FR1), or may be configured with the first frequency band or carrier. The second link may work in a second frequency band or carrier (e.g., FR2), or may be configured with the second frequency band or carrier.

[0150] In various aspects, the network node may include a first unit (e.g., SN CU) and a second unit (e.g., SNFU). The two units of the network node may include or perform different functions. In some cases, the 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 the reception and / or transmission of (e.g., data / information) on 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 on a second link. In some cases (e.g., additionally or alternatively), in response to the first unit receiving a second set of TDD configuration parameters, the first unit may forward the second set of TDD configuration parameters to the second unit to allow the second unit to control the reception and / or transmission on a second link (e.g., at least one of the first, second, third, or fourth forwarding links).

[0151] In some implementations, if the first link and the second link are configured with different TDD modes and / or different directions in symbols / time slots, the network node may perform / execute / operate at least one of the following. For example, the network node may perform transmission or reception on the first link and stop forwarding on the second link. In another example, the network node may perform forwarding on the second link and stop transmission and / or reception on the first link. In a further example, the network node may perform uplink operations (e.g., transmission and / or reception on F2 links and F4 links) and stop downlink operations (e.g., stop transmission and / or reception on F1 and F3 links). In yet another example, the network node may perform downlink operations (e.g., transmission and / or reception on F1 links and F3 links) and stop UL operations (e.g., transmission and / or reception on F2 links and F4 links). In some cases, high priority links and / or directions may be configured to the network node by a wireless communication node and / or an operation, management and maintenance (OAM) node through system information, RRC signaling, MAC CE and / or DCI, etc.

[0152] In various arrangements, the first set of TDD configuration parameters and the second set of TDD configuration parameters may include various (e.g., a large number of) parameters, respectively. For example, the first set of TDD configuration parameters may include a first parameter, which is publicly, cell-specifically and / or semi-statically configured to control reception and / or transmission on the first link. One or more messages may be RRC signaling or system information (SI). The first set of TDD configuration parameters may include a third parameter, which is device-specifically, device-specifically and / or semi-statically configured to control reception and / or transmission on the first link. The first set of TDD configuration parameters may include a fifth parameter, which is a MAC CE and / or DCI, etc.

[0153] In another example, the second set of TDD configuration parameters may include a second parameter, which is commonly, cell-specifically and / or semi-statically configured to control reception and / or transmission on the second link. The one or more messages may be RRC signaling or SI. The second set of TDD configuration parameters may include a fourth parameter, which is device-specifically, device-specifically and / or semi-statically configured to control reception and / or transmission on the second link. The second set of TDD configuration parameters may include a sixth parameter, which is a MAC CE and / or DCI, etc.

[0154] In various arrangements, the network node may receive one or more messages from the wireless communication node, the one or more messages indicating a single set of TDD configuration parameters. For example, a single set of TDD configuration parameters may be configured for the first link and implicitly for the second link. In some implementations, the first link may include at least one of the following: 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. For example, the second link may include at least one of the following: a first forwarding link from the wireless communication node to the network node, a second forwarding link from the network node to the wireless communication node, a third forwarding link from the network node to the wireless communication device, and / or a fourth forwarding link from the wireless communication device to the network node.

[0155] In some implementations, the network node may include a first unit and a second unit. For example, in response to, after, or after the first unit receives a single set of TDD configuration parameters, the first unit may control reception and / or transmission on the first link. In another example, in response to the first unit receiving a subcarrier spacing associated with the second unit, the first unit may determine a set of TDD configuration parameters based on the subcarrier spacing, for example, the set of TDD configuration parameters is configured to control reception and / or transmission on the second link.

[0156] Although various embodiments of the present solution have been described above, it should be understood that they are provided only in an exemplary and non-limiting manner. Similarly, various figures can depict example architectures or configurations, and these example architectures or configurations are provided to enable those of ordinary skill in the art to understand the exemplary features and functions of the present solution. However, these personnel will understand that the present solution is not limited to the example architectures or configurations shown, but can be implemented using a variety of alternative architectures and configurations. In addition, as will be understood by those of ordinary skill in the art, one or more features of an embodiment can be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of the present disclosure should not be limited by any of the above-mentioned exemplary embodiments.

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

[0158] In addition, those of ordinary skill in the art will understand that information and signals may be represented using any of a variety of different 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.

[0159] Those of ordinary skill in the art will further understand that any of the various illustrative logic blocks, modules, processors, devices, circuits, methods, and functions described in conjunction with the aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of the two), firmware, various forms of programs or design codes containing instructions (for convenience, referred to herein as "software" or "software modules"), or any combination of these technologies. In order to clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been generally described above according to their functions. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these technologies, depends on the specific application and the design constraints imposed on the entire system. Technicians can implement the described functions in various ways for each specific, but such implementation decisions will not cause a departure from the scope of this disclosure.

[0160] In addition, it will be understood by those of ordinary skill in the art that the various illustrative logic blocks, modules, devices, components, and circuits described herein may be implemented or performed within or by an integrated circuit (IC) including a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, 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 within a device. A general purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a DSP core, or any other suitable configuration to perform the functions described herein.

[0161] If implemented in software, the function may be stored as one or more instructions or codes on a computer-readable medium. Therefore, the steps of the method or algorithm disclosed herein may be implemented as software stored on a computer-readable medium. Computer-readable media include computer storage media and communication media, and communication media include any media that enables a computer program or code to be transferred from one place to another. The storage medium can be any available medium that a computer can access. As an example and not limitation, such a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, which can be used to store the desired program code in the form of instructions or data structures and any other medium that can be accessed by a computer.

[0162] As used herein, the term "module" refers to software, firmware, hardware, and any combination of these elements to perform the relevant functions described herein. In addition, for the purpose of discussion, various modules are described as discrete modules; however, it is obvious to a person of ordinary skill in the art that two or more modules can be combined to form a single module that performs the relevant functions of the implementation according to the present solution.

[0163] In addition, memory or other storage devices and communication components can be used in the implementation of the present solution. It should be understood that, for the sake of clarity, the above description has described the implementation of the present solution with reference to different functional units and processors. However, it will be apparent that any appropriate distribution of functions between different functional units, processing logic elements or domains can be used without departing from the present solution. For example, the functions illustrated as being performed by a separate processing logic element or controller can be performed by the same processing logic element or controller. Therefore, references to specific functional units are only references to suitable devices for providing the described functions, rather than indicating a strict logical or physical structure or organization.

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

Claims

1. A wireless communication method, comprising: receiving, by a network node, one or more messages from a wireless communication node, the one or more messages 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; and The second set of TDD configuration parameters is configured for the second link.

2. The wireless communication method according to claim 1, wherein: The first link includes at least one of the following links: a first communications link from the wireless communications node to the network node; or A second communication link from the network node to the wireless communication node.

3. The wireless communication method according to claim 1, wherein: The second link includes at least one of the following links: a first forwarding link from the wireless communication node to the network node; a second forwarding link from the network node to the wireless communication node; a third forwarding link from the network node to the wireless communication device; or A fourth forwarding link from the wireless communication device to the network node.

4. The wireless communication method according to claim 1, wherein: The first link operates in or is configured with a first frequency band or carrier, and wherein the second link operates in or is configured with a second frequency band or carrier.

5. The wireless communication method according to claim 1, wherein: The network node includes a first unit and a second unit, and the method further includes: In response to the first unit receiving the first set of TDD configuration parameters, controlling reception and / or transmission on the first link by the first unit; and In response to the first unit receiving the second set of TDD configuration parameters, the second unit performs reception and / or transmission on the second link, or the first unit forwards the second set of TDD configuration parameters to the second unit to allow the second unit to control reception and / or transmission on the second link.

6. The wireless communication method according to claim 1, wherein: If the first link and the second link are configured with different TDD modes or different directions in symbols / time slots, the method includes: performing, by the network node, transmission or reception on the first link, and ceasing, by the network node, forwarding on the second link; performing, by the network node, forwarding on the second link, and ceasing, by the network node, transmitting or receiving on the first link; An uplink operation is performed by the network node, and a downlink operation is stopped by the network node; or performing, by the network node, a downlink operation, and ceasing, by the network node, an uplink operation; The high priority link or direction is configured to the network node by the wireless communication node or the operation, administration and maintenance (OAM) node through system information, RRC signaling, MAC CE or DCI.

7. The wireless communication method according to claim 1, wherein: The first set of TDD configuration parameters includes first parameters used commonly, cell-specifically or semi-statically to control reception and / or transmission on the first link.

8. The wireless communication method according to claim 1, wherein: The second set of TDD configuration parameters includes second parameters used commonly, cell-specifically or semi-statically to control reception and / or transmission on the second link.

9. The wireless communication method according to claim 1, wherein: The first set of TDD configuration parameters includes a third parameter used device-dedicatedly, device-specifically or semi-statically to control reception and / or transmission on the first link.

10. The wireless communication method according to claim 1, wherein: The second set of TDD configuration parameters includes a fourth parameter used device-dedicatedly, device-specifically or semi-statically to control reception and / or transmission on 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 according to claim 1, wherein: The first set of TDD configuration parameters includes a fifth parameter, which is a medium access control element (MAC CE) or DCI.

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

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

15. The wireless communication method according to claim 14, wherein: The first link includes at least one of the following links: a first communications link from the wireless communications node to the network node; or A second communication link from the network node to the wireless communication node.

16. The wireless communication method according to claim 14, wherein: The second link includes at least one of the following links: a first forwarding link from the wireless communication node to the network node; a second forwarding link from the network node to the wireless communication node; a third forwarding link from the network node to the wireless communication device; or A fourth forwarding link from the wireless communication device to the network node.

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

18. A wireless communication device, comprising a processor and a memory, wherein: The processor is configured to read code from the memory and implement the method according to any one of claims 1 to 17.

19. A computer program product comprising computer readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement the method according to any one of claims 1 to 17.

Images