Systems, methods, and non-transitory processor-readable media for signal forwarding
By introducing intelligent nodes into cellular networks for frequency switching and signal forwarding, the problem of insufficient cellular network coverage has been solved, enabling more flexible and efficient network deployment.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- ZTE CORP
- Filing Date
- 2023-11-02
- Publication Date
- 2026-05-26
Smart Images

Figure CN122095718A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates generally to wireless communications, and more specifically to systems, methods, and non-transitory processor-readable media for forwarding signals. Background Technology
[0002] Although network deployment methods have continuously evolved and developed based on traditional network deployments, coverage remains a fundamental aspect of cellular network deployment. Mobile operators rely on different types of network nodes to provide comprehensive coverage in their respective deployments. Therefore, the use of new types of network nodes is being considered to improve the flexibility of network deployment. Summary of the Invention
[0003] In some arrangements, systems, methods, apparatuses, and non-transitory computer-readable media, a frequency switching is performed by a first functional unit of a first communication node to switch from a first frequency to a second frequency. A second functional unit of the first communication node performs at least one of receiving a signal from a first of a second or third communication node, or forwarding a signal to a second of a second or third communication node.
[0004] The above and other aspects and their implementations are described in more detail in the accompanying drawings, description and claims. Attached Figure Description
[0005] Various example arrangements of this solution are described in detail below with reference to the accompanying drawings. The drawings are for illustrative purposes only and depict only example arrangements of this solution to facilitate the reader's understanding. Therefore, the drawings should not be considered to limit the breadth, scope, or applicability of this solution. It should be noted that these drawings are not necessarily drawn to scale for clarity and ease of explanation.
[0006] Figure 1 This is a diagram illustrating an example cellular communication system based on some arrangement.
[0007] Figure 2 This is a block diagram showing an example of a BS, UE, and SN arranged according to some configurations.
[0008] Figure 3 This is a block diagram illustrating the transmission links between the BS and SN, and between the SN and UE, according to various arrangements.
[0009] Figure 4 This is a flowchart illustrating example methods for performing frequency switching and receiving / forwarding signals for a signal receiver (SN) according to various arrangements. Detailed Implementation
[0010] Various example arrangements of this solution are described below with reference to the accompanying drawings to enable those skilled in the art to manufacture and use this solution. As will be apparent to those skilled in the art, various changes or modifications can be made to the examples described herein without departing from the scope of this solution after reading this disclosure. Therefore, this solution is not limited to the example arrangements and applications described and shown herein. Furthermore, the specific order or hierarchy of steps in the methods disclosed herein is merely an example method. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes can be rearranged while remaining within the scope of this solution. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or actions in an example order, and unless otherwise expressly stated, this solution is not limited to the specific order or hierarchy presented.
[0011] Figure 1 An example wireless communication system 100 arranged according to this disclosure is shown. The wireless communication system 100 can be used to implement a wireless network, such as a cellular network or a narrowband network. System 100 includes a BS 102, a UE 104, and a smart node (SN) 106.
[0012] As used herein, an SN is a network node (e.g., a communication node) that supports controlled amplification and forwarding operations or forwarding operations of wireless signals. Examples of SNs include repeaters (e.g., network control repeaters (NCRs), UE control repeaters, smart repeaters, etc.), relay nodes, reconfigurable smart surfaces (RIS), smart reflective surfaces (IRS), integrated access and backhaul (IAB) nodes, parts or components of base stations (BS), transmit and receive points (TRPs), user equipment (UEs), controllers, wireless communication devices, etc. As used herein, a forwarding operation of an SN can refer to receiving signals, transmitting signals, or receiving and transmitting signals, or one or more of these.
[0013] For example, an IAB node is a network node that does not require wired backhaul. A radio frequency (RF) repeater is another type of network node that amplifies and forwards any received signals. RF repeaters are widely deployed in 2G, 3G, and 4G to supplement the coverage provided by conventional full-stack cells. An RF repeater has only one radio unit.
[0014] NCR is an enhancement to traditional RF repeaters because it has the ability to receive and process sidelink control information from the network. This sidelink control information allows NCR to perform amplification and forwarding operations more efficiently. Therefore, NCR reduces the need for noise amplification, transmission, and reception with better spatial directivity and simplifies network integration. The mechanisms disclosed in this paper can also be used in other systems, such as RIS.
[0015] BS 102 and UE 104 can communicate indirectly with each other via SN 106. For example, BS 102 can communicate with SN 106 via a first communication link 110 (e.g., a first wireless communication channel) (e.g., sending data, signals, messages, and information to SN 106, and receiving data, signals, messages, and information from SN 106), and vice versa. SN 106 can communicate with UE 104 via a second communication link 120 (e.g., a second wireless communication channel) (e.g., sending data, signals, messages, and information to UE 104, and receiving data, signals, messages, and information from UE 104), and vice versa. In some examples, SN 106 can forward signals received from BS 102 via the first communication link 110 to UE 104 via the second communication link 120. In some examples, SN 106 can amplify signals received from BS 102 via the first communication link 110 and forward them to UE 104 via the second communication link 120. Therefore, SN 106 can extend the coverage of BS 102.
[0016] As shown in the figure, system 100 can provide wireless communication services to a cluster of cells (e.g., at least 160, 162, 164, 166, 168, 170, and 172) covering geographic area 101. At least one BS is located in each of cells 160, 162, 164, 166, 168, 170, and 172 and operates under a certain bandwidth to provide wireless coverage and wireless communication services to users (e.g., UEs) within that cell. For example, BS 102 can operate under channel transmission bandwidth to provide wireless coverage and wireless communication services to UEs within cell 160 where BS 102 is located. Although UE 104 is shown as being in cell 160, BS 102 can communicate indirectly with UE 104 via SN 106, so UE 104 may or may not be in cell 160 as long as UE 104 is within the service area of SN 106. In other words, as long as SN 106 is within cell 160 and UE 104 is within the service area of SN 106, BS 102 can communicate indirectly with UE 104 via SN 106.
[0017] In some arrangements, BS 102 communicates with SN 106 via a radio frame structure including time-domain elements (such as frames), and vice versa. SN 106 communicates with UE 104 via a radio frame structure including time-domain elements (such as frames), and vice versa. Each frame may be further subdivided into subframes and / or time slots. Each time slot may include multiple data symbols. In this disclosure, BS 102, UE 104, and SN 106 are described herein as non-limiting examples of communication nodes or network nodes that can practice the methods disclosed herein. According to various arrangements of this solution, such communication nodes are capable of wireless and / or wired communication.
[0018] Figure 2 This is a block diagram illustrating an example of a BS 102, UE 104, and SN 106 arranged in some manner. BS 102 includes a BS transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a BS network communication module 218, each module being coupled and interconnected with each other as needed via a BS data communication bus 220. SN 106 includes an SN transceiver module 260, an SN antenna 262, an SN processor module 264, and an SN memory module 266, each module being coupled and interconnected with each other as needed via an SN data communication bus 270. UE 104 includes a UE transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each module being coupled and interconnected with each other as needed via a UE data communication bus 240.
[0019] BS 102 communicates with SN 106 via a first communication channel 110 (e.g., a first wireless transmission link, a first wireless data transmission link, etc.), which can be any wireless channel or other medium suitable for data transmission as described herein. SN 106 communicates with UE 104 via a second communication channel 120 (e.g., a second wireless transmission link, a second wireless data transmission link, etc.), which can be any wireless channel or other medium suitable for data transmission as described herein.
[0020] Each of BS 102, SN 106 and UE 104 may also include, except Figure 2Any number of modules other than those shown herein. The various illustrative blocks, modules, circuits, and processing logic described in conjunction with the arrangements disclosed herein can 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, various illustrative components, blocks, modules, circuits, and steps are typically described according to their functionality. Whether this functionality is implemented as hardware, firmware, or software depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement these functions appropriately for each specific application, but these implementation decisions should not be construed as limiting the scope of this disclosure.
[0021] According to some arrangements, BS transceiver module 210 includes a radio frequency (RF) transmitter and an RF receiver, each including circuitry coupled to BS antenna 212. A duplex switch (not shown) may alternatively couple the transmitter or receiver to the antenna in a time-division duplex manner. UE transceiver module 230 includes an RF transmitter and an RF receiver, each including circuitry coupled to UE antenna 232. A duplex switch (not shown) may alternatively couple the transmitter or receiver to the antenna in a time-division duplex manner. SN transceiver module 260 includes an RF transmitter and an RF receiver, each including circuitry coupled to SN antenna 262. A duplex switch (not shown) may alternatively couple the transmitter or receiver to the antenna in a time-division duplex manner.
[0022] BS transceiver module 210 and SN transceiver module 260 are configured to communicate via a first communication link 110 and cooperate with an RF antenna arrangement appropriately configured to support a specific wireless communication protocol and modulation scheme. UE transceiver module 230 and SN transceiver module 260 are configured to communicate via a second communication link 120 and cooperate with an RF antenna arrangement appropriately configured to support a specific wireless communication protocol and modulation scheme.
[0023] In some illustrative arrangements, the BS transceiver module 210, UE transceiver module 230, and SN transceiver module 260 are configured to support industry standards such as Long Term Evolution (LTE), 5G standards, and 6G standards. However, it should be understood that this disclosure is not necessarily limited to the application of specific standards and related protocols. Rather, the BS transceiver module 210, UE transceiver module 230, and SN transceiver module 260 can be configured to support alternative or additional wireless data communication protocols, including future standards or variations thereof.
[0024] In some deployments, UE 104 can be embodied in various types of user equipment, such as mobile phones, smartphones, personal digital assistants (PDAs), tablets, laptops, wearable computing devices, vehicles, etc. In some deployments, BS 102 may include gNB, evolved Node B (eNB), serving eNB, serving gNB, etc.
[0025] Processor modules 214, 236, and 264 may be implemented or realized using general-purpose processors, content-addressable memory, digital signal processors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), any suitable programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. In this way, the processor can be implemented as a microprocessor, controller, microcontroller, state machine, etc. The processor can also be implemented as a combination of computing devices, such as a combination of a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other such configuration.
[0026] Furthermore, the steps of the methods or algorithms described in conjunction with the arrangements disclosed herein can be directly embodied in hardware, firmware, software modules executed by processor modules 214, 236, and 264 respectively, or any practical combination thereof. Memory modules 216, 234, and 266 can 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 respect, memory modules 216, 234, and 266 can be coupled to processor modules 214, 236, and 264 respectively, such that processor modules 214, 236, and 264 can read information from and write information to memory modules 216, 234, and 266 respectively. Memory modules 216, 234, and 266 can also be integrated into their respective processor modules 214, 236, and 264. In some arrangements, memory modules 216, 234, and 266 may each include a cache memory for storing temporary variables or other intermediate information during the execution of instructions executed by processor modules 214, 236, and 264, respectively. Memory modules 216, 234, and 266 may also each include non-volatile memory for storing instructions executed by processor modules 214, 236, and 264, respectively.
[0027] BS network communication module 218 typically refers to the hardware, software, firmware, processing logic, and / or other components of BS 102 that enable bidirectional communication between BS transceiver module 210 and other network components and communication nodes (such as the core network) configured to communicate with BS 102. For example, BS network communication module 218 may be configured to support Internet or WiMAX traffic. In a typical deployment, without limitation, BS network communication module 218 provides an 802.3 Ethernet interface, enabling BS transceiver module 210 to communicate with traditional Ethernet-based computer networks. In this way, BS network communication module 218 may include a physical interface for connecting to a computer network (e.g., a mobile switching center (MSC)). The terms “configured for,” “configured as,” and variations thereof, used herein with respect to a specified operation or function, refer to a device, component, circuit, structure, machine, signal, etc., physically constructed, programmed, formatted, and / or arranged to perform the specified operation or function.
[0028] In some examples, the CU and FU can be separate and / or dedicated components or hardware of the SN (e.g., separate SN processor module 264 and SN memory module 266). In some examples, the CU and FU can be different logic or algorithms running on the same components or hardware of the SN (e.g., the same SN processor module 264 and SN memory module 266). In some examples, the SN may include an interface to enable information exchange / conversion between the CU and FU.
[0029] Figure 3 This is a block diagram illustrating the transmission links between BS 102 and SN 106, and between SN 106 and UE 104, according to various arrangements. In some arrangements, SN 106 may include a first functional unit for receiving and decoding side-link control information from a controller (e.g., BS, UE, or another third-party entity). Examples of first functional units include a control / communication unit (CU), a mobile terminal (MT) unit, a portion or functional unit of the UE, a third-party IoT device, etc. CU 310 is generally used to refer to various examples of the first functional unit. CU 310 can be implemented using a combination of SN processor module 264 and SN memory module 266.
[0030] In some arrangements, SN 106 may include a second functional unit for amplifying and forwarding received radio signals or performing forwarding operations based on sidelink control information received by the SN. Examples of second functional units include forwarding units (FU or Fwd), radio units (RU), distributed units (DU), a portion or functional unit of the UE, a portion of the functional unit of the RIS, etc. FU 320 is commonly used to refer to various examples of the second functional unit. FU 320 can be implemented using a combination of SN processor module 264 and SN memory module 266.
[0031] The control link between BS 102 and CU 310 includes links C1 and C2 via the first communication link 110. The control link between CU 310 and UE 104 includes links C3 and C4 via the second communication link 120. The forwarding link between BS 102 and FU 320 includes links F1 and F2 via the first communication link 110. The forwarding link between FU 320 and UE 104 includes links F3 and F4 via the second communication link 120.
[0032] In some examples, links C1 and C4 are control links (or C links) from the controller (e.g., BS 102 or UE 104) to CU 310. Links C2 and C3 are C links from CU 130 to the controller. F1 is a forwarding link (F link) from BS 102 to FU 320. F2 is an F link from FU 320 to BS 102. F3 is a forwarding link from FU 320 to UE 104. F4 is a forwarding link from UE 104 to FU 320.
[0033] FU 320 is unaware of signals from BS 102 via F-link F1 to FU 320, or signals from UE 104 via F-link F4 to FU 320. FU 320 simply forwards or amplifies and forwards these signals without decoding them. Links F1 and F2 are also called backhaul links (B-links). Links F3 and F4 are also called access links (A-links). B-links and A-links are part of F-links, and their combination constitutes a complete F-link. For example, the combination of links F1 and F3 is a complete downlink F-link from BS 102 to UE 104, where F3 is an SN FU downlink F-link. The combination of links F2 and F4 is a complete uplink F-link from UE 104 to BS 102, where F2 is an SN FU uplink F-link.
[0034] In the C-link, signals from the transmitter are detected and decoded by the receiver, allowing the information transmitted in the C-link to be used to control the state of the F-link. For example, CU 310 detects, decodes, and processes signals from BS 102 via C-link C1 to CU 310 and signals from UE 104 via C-link C4 to CU 310 to control the F-link.
[0035] CU 310 can receive sidelink control information from the controller (e.g., via at least one of links C1 and C4) to control the amplification and forwarding operations or forwarding operations of FU 302. Examples of sidelink control information include downlink control information (DCI), uplink control information (UCI), sidelink (or side) control information (SCI), etc. After receiving the sidelink control information, SN 106 requires a certain time delay to decode the sidelink control information, perform beam switching, and / or perform inter-module operations.
[0036] The CU 310 uses a first parameter set, a first subcarrier spacing (SCS), and a first cyclic prefix (CP) for transmission, such as the Physical Downlink Control Channel (PDCCH) and Physical Uplink Control Channel. The FU 320 uses a second parameter set (e.g., a reference parameter set), a second SCS (e.g., a reference SCS), and a second CP (e.g., a reference CP) for forwarding operations. In some examples, the first parameter set differs from the second parameter set. In some examples, the first SCS differs from the second SCS. In some examples, the first CP differs from the second CP.
[0037] To dynamically adjust network configuration to adapt to service changes and reduce power consumption, UE 104 can perform frequency handovers, such as bandwidth portion (BWP) handovers. In some examples, SN CU 310 can also perform BWP handovers. During a BWP handover by SN CU 310, SN CU 310 does not receive or transmit any signals. In some arrangements, SN FU 320 performs forwarding during a BWP handover performed by SN CU 310, and SN FU 320 determines the backhaul link beam at SN FU 320 after the BWP handover. In some arrangements, a new active BWP or a previous active BWP can be replaced by a default BWP or a reference BWP (e.g., using ServingCellAndBWP Id). BS 102 can configure default and reference BWPs.
[0038] In some configurations, SN FU 320 is excluded from transmitting or receiving signals (e.g., SN FU 320 is not required to transmit or receive information) until the frequency switching (e.g., BWP switching) process is complete. During the BWP switching process of SN CU 310, SN FU 320 is excluded from transmitting or receiving signals, or does not transmit or receive signals. While SN CU 310 is performing the BWP switching process, SN CU 310 shuts down SN FU 320. For example, SN FU 320 is excluded from transmitting or receiving signals, or does not transmit or receive signals until the BWP switching process is complete.
[0039] For example, in response to determining that at least one condition is met, SN FU 320 is excluded from transmitting or receiving signals, or does not transmit or receive signals for the same duration during which SN CU 310 also does not need to transmit or receive signals. The duration during which SN CU 310 does not need to transmit or receive signals can be used for BWP handover.
[0040] In some configurations, at least one condition includes a DCI-based BWP handover. In some examples, in response to determining that the BWP handover includes a downlink control information (DCI)-based BWP handover, the SNFU 320 is excluded from transmitting or receiving signals, or does not transmit or receive signals, during the BWP handover process of the SN CU 310. In some examples, in response to the SNCU 310 detecting a DCI format indicating a change in the active downlink or uplink BWP, the SNFU 320 is excluded from transmitting or receiving signals, or does not transmit or receive signals, during the BWP handover process of the SN CU 310. In some examples, in response to the SN CU 310 detecting a DCI format having a BWP indicator field indicating a change in the active downlink or uplink BWP, the SNFU 320 is excluded from transmitting or receiving signals, or does not transmit or receive signals, during the BWP handover process of the SN CU 310.
[0041] In some examples, in response to SN CU 310 detecting a DCI format with a BWP indicator field indicating a change in the active downlink BWP of the cell, SN FU 320 is excluded from transmitting or receiving signals, or does not receive or transmit signals, for the duration from the end of the third symbol of the time-domain resource (e.g., time slot) of the physical downlink control channel (PDCCH) in DCI format received from SN CU 310 to the start of the time-domain resource (e.g., time slot) indicated by the time slot offset value of the time-domain resource allocation field in the DCI format.
[0042] In some examples, in response to SN CU 310 detecting a DCI format indicating a change in the cell's active uplink BWP, SN FU is excluded from transmission or reception, or does not receive or transmit, for the duration from the end of the third symbol of the time domain resource (e.g., time slot) received from SN CU 310 including the PDCCH of DCI format to the start of the time domain resource (e.g., time slot) indicated by the time slot offset value in the time domain resource allocation field of the DCI format.
[0043] In some examples, in response to SN CU 310 detecting a DCI format with a secondary cell (SCell) sleep indication indicating a change in the active downlink BWP of the SCell in the time domain resources (e.g., time slot n) of the primary cell (PCell), SN FU 320 is excluded from transmitting or receiving signals, or does not transmit or receive signals during the BWP handover of SN CU 310.
[0044] In some examples, in response to SN CU 310 detecting a DCI format with an SCell sleep indication indicating a change in the active downlink BWP of the SCell in the time domain resources (e.g., time slot n) of the PCell, SN FU 320 is excluded from transmission or reception, or does not transmit or receive in the SCell for the duration.
[0045] In some examples, the SCS of the time-domain resource (e.g., a timeslot or symbol) is the same as at least one of the SCS of the PDCCH, the SCS of the BWP (e.g., at least one of the SCS before BWP handover, the SCS after BWP handover, or the smaller or larger of the SCS before and after BWP handover), and the reference SCS configured for the forwarding operation of SN FU 320. In some examples, the SCS of the time-domain resource (e.g., a timeslot or symbol) may be the same as the SCS received by the PDCCH or the SCS of the BWP.
[0046] In some examples, after SN CU 310 receives a BWP handover request at downlink slot n on the serving cell, SN FU 320 can immediately follow up at T BWP切换延迟 Signals are received or transmitted in the first time slot (e.g., time slot a) following the duration of +Y, which begins at the start of downlink time slot n. The SN FU 320 is excluded from transmitting or receiving signals, or does not transmit or receive signals until immediately following T. BWP切换延迟 The duration of +X ends at the first slot (e.g., slot b) that occurs after the start of downlink slot n, which begins at the start of downlink slot n (except in cases where DCI triggers BWP handover). In some examples, TBWP切换延迟 It is the BWP handover delay, defined according to time-domain resource units such as time slots.
[0047] In some examples, the value of X or Y can be equal to 0, 1, or another suitable value (defined according to time-domain resource units, such as time slots). In some examples, X or Y can be a predefined value, declared by the vendor or service provider, or indicated by the controller (e.g., BS). In some examples, X or Y can be determined for different situations; for example, the X or Y of the serving cell for which the UE receives the DCI for the BWP handover request may be the same as or different from the X or Y of the serving cell where the BWP handover occurs.
[0048] In some examples, time slot a or time slot b can be determined by at least one of the reference SCS configured for SN FU 320 forwarding, the SCS received by PDCCH, or the SCS of the BWP (e.g., the SCS before BWP handover, the SCS after BWP handover, or the smaller or larger of the SCS before and after BWP handover). In some examples, the SCS of time slot a or time slot b is one of the reference SCS configured for SN FU 320 forwarding, the SCS received by PDCCH, or the SCS of the BWP. In some examples, time slot a or time slot b can be defined or represented by one of the reference SCS configured for SN FU 320 forwarding, the SCS received by PDCCH, or the SCS of the BWP. In some examples, the SCS of time slot a or time slot b can be defined or represented by a reference SCS. In some examples, the SCS of time slot a or time slot b is a reference SCS. In some examples, time slot a or time slot b can be a complete time slot. In some examples, the start time of slot a or slot b is no earlier than T after downlink slot n. BWP切换延迟 + Y or T BWP切换延迟 The start time of the time slot at the duration of +X.
[0049] In some examples, T BWP切换延迟 Alternatively, downlink slot n may have at least one of the following: a reference SCS configured for forwarding operations of SN FU 320, an SCS for PDCCH reception, or an SCS for BWP (e.g., the smaller or larger of the SCS before BWP handover, the SCS after BWP handover, or the SCS before and after BWP handover). In some examples, T BWP切换延迟 The SCS for the downlink time slot is one of the reference SCS configured for forwarding operations of the SN FU 320, the SCS for PDCCH reception, or the SCS for BWP. In some examples, T BWP切换延迟The SCS of a downlink time slot can be defined or represented by one of the reference SCS configured for forwarding operations of the SN FU 320, the SCS of PDCCH reception, or the SCS of the BWP. In some examples, T BWP切换延迟 Alternatively, downlink slot n can be used with the SCS received by the PDCCH or the SCS of the BWP. In some examples, T BWP切换延迟 Or the SCS of the downlink timeslot is the same as the SCS received by the PDCCH or the SCS of the BWP. In some examples, T BWP切换延迟 The SCS of a downlink time slot can be defined or represented by the SCS received by the PDCCH or the SCS of the BWP.
[0050] In some arrangements, at least one condition includes a timer-based BWP handover. In some examples, in response to determining that the BWP handover includes a timer-based BWP handover, the SN FU 320 is excluded from transmitting or receiving signals, or does not transmit or receive signals, during the BWP handover process of the SN CU 310.
[0051] In some examples, for cells where the active downlink BWP of SN CU 310 changes due to the expiration of the BWP inactivity timer and / or to accommodate the delay in the change of active downlink BWP or active uplink BWP required by SN CU 310, SN FU 320 is excluded from transmitting or receiving signals, or does not receive or transmit signals, for the duration from the time domain unit (e.g., a subframe of FR1 or half a subframe of FR2) after the expiration of the BWP inactivity timer until the start of the time domain resources where SN CU 310 (or SN FU 320) can receive or transmit signals.
[0052] In some examples, the SN CU 310 can initiate BWP handover at downlink time slot n. Time slot n is the first time slot (e.g., time slot c) of the time unit immediately following the expiration of the BWP inactivity timer bwp-InactivityTimer on the serving cell (e.g., downlink subframe (FR1) or downlink half-frame (FR-2)), and the SN FU 320 should be able to initiate BWP handover immediately following T. BWP切换延迟 Reception or transmission occurs on the first time slot (e.g., time slot d) following the duration, where T... BWP切换延迟 The duration is calculated from the start time of downlink time slot n. In some examples, the duration T is the time after the timer bwp-InactivityTimer expires. BWP切换延迟 During this period, SN FU 320 320 is excluded from transmitting or receiving signals, or does not receive or transmit signals, wherein the duration T BWP切换延迟 It is the time period during which BWP switching occurs based on a timer.
[0053] In some examples, time slot d can be one of the reference SCS configured for forwarding operations of SN FU 320, the SCS received by PDCCH, or the SCS of BWP (e.g., at least one of the smaller or larger of the SCS before BWP handover, the SCS after BWP handover, or the SCS before and after BWP handover). In some examples, the SCS of time slot d is at least one of the reference SCS configured for forwarding operations of SN FU 320, the SCS received by PDCCH, or the SCS of BWP. In some examples, time slot d can be defined or represented by one of the reference SCS configured for forwarding operations of SN FU 320, the SCS received by PDCCH, or the SCS of BWP. In some examples, time slot d can be used in conjunction with a reference SCS. In some examples, time slot d can be a complete time slot. In some examples, the start time of time slot d is no earlier than T after downlink time slot n. BWP切换延迟 The start time of the time slot at the duration of T. In some examples, T BWP切换延迟 This refers to the BWP handover delay. In some examples, the SCS of slot d is the reference SCS. In other examples, slot d can be defined or represented by the reference SCS.
[0054] In some examples, T BWP切换延迟 Downlink slot n or slot c may have at least one of the following: a reference SCS configured for forwarding operations of SN FU 320, an SCS for PDCCH reception, or an SCS for BWP (e.g., the smaller or larger of the SCS before BWP handover, the SCS after BWP handover, or the SCS before and after BWP handover). In some examples, T BWP切换延迟 The SCS of downlink slot n or slot c is the same as one of the reference SCS configured for forwarding operations of SN FU 320, the SCS of PDCCH reception, or the SCS of BWP. In some examples, T BWP切换延迟 The SCS of downlink slot n or slot c can be defined or represented by one of the reference SCS configured for forwarding operations of SN FU 320, the SCS of PDCCH reception, or the SCS of BWP. In some examples, T BWP切换延迟 Downlink slot n or slot c can be used with the SCS received by the PDCCH or the SCS of the BWP. In some examples, T BWP切换延迟 The SCS of downlink slot n or slot c is the same as the SCS received by the PDCCH or the SCS of the BWP. In some examples, T BWP切换延迟 The SCS of downlink slot n or slot c can be defined or represented by the SCS received by PDCCH or the SCS of BWP.
[0055] In some configurations, at least one condition includes a BWP handover based on Radio Resource Control (RRC). In some examples, in response to determining that the BWP handover includes an RRC-based BWP handover, the SN FU 320 is excluded from transmitting or receiving signals, or does not transmit or receive signals, during the BWP handover process of the SN CU 310.
[0056] In some examples, after SN CU 310 receives an RRC reconfiguration including an active BWP handover or a parameter change of the active BWP, SN FU 320 may receive or transmit on the first time slot (e.g., time slot e) immediately following the duration, which begins at the start of downlink time slot n. The duration may include multiple time-domain resources (e.g., time slots) defined by the following formula: .
[0057] In some examples, time slot e may have at least one of the following: a reference SCS, a PDCCH reception SCS, or a BWP SCS configured for forwarding operations of the SN FU 320 (e.g., the smaller or larger of the SCS before BWP handover, the SCS after BWP handover, or the SCS before and after BWP handover). In some examples, the SCS of time slot e is the same as one of the reference SCS, PDCCH reception SCS, or BWP SCS configured for forwarding operations of the SN FU 320. In some examples, the SCS of time slot e may be defined or represented by one of the reference SCS, PDCCH reception SCS, or BWP SCS configured for forwarding operations of the SN FU 320. In some examples, time slot d may be used with a reference SCS. In some examples, the SCS of time slot e is the same as the reference SCS. In some examples, the SCS of time slot e may be defined or represented by a reference SCS.
[0058] In some examples, downlink slot n is the last time-domain resource (e.g., a slot) overlapping with the Physical Downlink Shared Channel (PDSCH) that contains or carries RRC commands. In some examples, downlink slot n may have at least one of the following: a reference SCS configured for forwarding operations of SN FU 320, a PDCCH received SCS, or a BWP SCS (e.g., the smaller or larger of the pre-BWP handover SCS, post-BWP handover SCS, or the SCS before and after the BWP handover). In some examples, the SCS of downlink slot n is the same as one of the reference SCS configured for forwarding operations of SN FU 320, a PDCCH received SCS, or a BWP SCS. In some examples, the SCS of downlink slot n may be defined or represented by one of the reference SCS configured for forwarding operations of SN FU 320, a PDCCH received SCS, or a BWP SCS. In some examples, downlink slot n may be used in conjunction with either the PDCCH received SCS or the BWP SCS. In some examples, the SCS of downlink slot n is the same as the SCS received by the PDCCH or the SCS of the BWP. In other examples, the SCS of downlink slot n can be defined or represented by the SCS received by the PDCCH or the SCS of the BWP.
[0059] In some examples, where BWP handover involves changing the SCS, the slot length (e.g., NR slot length) can be determined by (e.g., the same as) the smaller of the SCS before and after the BWP handover.
[0060] In some examples, It can be defined as the length of the RRC process delay, in milliseconds.
[0061] In some examples, This is the time the UE uses to perform BWP handover, for example, . SN FU 320 at Within a defined time period, the signal is excluded from transmission or reception, or no signal is received or transmitted. In response to the determination... This allows for longer switching delays. In some examples, It is the time between downlink data transmission and acknowledgment.
[0062] In some examples, SN FU 320 can maintain transmission and reception while SN CU 310 performs a BWP handover procedure. In other words, SN FU 320 can continue to transmit or receive signals for the duration during which SN CU 310 is excluded from transmitting or receiving signals, or from receiving or transmitting signals. This period during which SN CU 310 is excluded from transmitting or receiving signals, or from receiving or transmitting signals, can be used for BWP handover.
[0063] In some arrangements, explicit beamforming can be provided for reception and transmission on the backhaul link after a BWP handover. In some examples, where SN 106 simultaneously receives and transmits via both the control link and the backhaul link across a set of time-domain resources (e.g., symbols), the Transmission Configuration Indication (TCI) status or spatial filter (e.g., Sounding Reference Signal (SRS) Resource Indicator (SRI)) used for reception and transmission can be the same as the TCI status or spatial filter on the control link in that set of time-domain resources. The arrangements disclosed herein also apply to SN CU 310 commencing signal transmission and reception after a BWP handover (e.g., after the BWP handover is completed).
[0064] In some examples, SN 106 does not simultaneously receive and transmit on the control link and the backhaul link. Explicit beam indication of the backhaul link can be provided via RRC signaling, Media Access Control (MAC)-Control Element (CE), DCI signaling, or a combination of two or more thereof. When SN CU 310 performs a BWP handover procedure (e.g., after the BWP handover procedure begins or after it completes), SN (SN FU 320) needs to determine the backhaul link beam in response to the active BWP being switched on the C link (at SN CU 310). While the arrangement disclosed herein uses MAC CE as an example of explicit beam indication, other examples of explicit beam indication (e.g., RRC signaling, DCI signaling, etc.) can be similarly implemented.
[0065] In some configurations, the BWP handover process may include four phases: BWP handover initiation, BWP handover during, BWP handover completed but before a new MAC CE has been received, and BWP handover completed and a new MAC CE has been received. The various mechanisms described herein apply to one or all of these phases.
[0066] In some configurations, SN FU 320 is excluded from transmitting or receiving signals, or does not transmit or receive signals, until after BWP handover, SN CU 310 receives a new MAC CE indicating the TCI state (e.g., downlink TCI state, uplink TCI state, combined TCI state, or unified TCI state) or an SRI for the backhaul link. In some examples, SN FU 320 is excluded from transmitting, or does not transmit, until after BWP handover, SN CU 310 receives a new MAC CE indicating the downlink (e.g., downlink beam) TCI state of the backhaul link. In some examples, SN FU 320 is excluded from transmitting, or does not transmit, until after BWP handover, SN CU 310 receives a new MAC CE indicating the TCI state (e.g., downlink TCI state, uplink TCI state, combined TCI state, or unified TCI state) or an SRI for the backhaul link. In some examples, the TCI status ID indicated by the new MAC CE refers to or corresponds to a TCI status with the same ID in the TCI status list of the new active downlink BWP. In some examples, "after BWP handover" means after the BWP handover process begins or after the BWP handover process completes. In other words, after the BWP handover begins or after the BWP handover process completes, SN FU 320 is turned off (e.g., SN FU 320 does not transmit or receive signals) as long as SN 106 (e.g., SN CU 310) does not receive a new MAC CE indicating the TCI status of the backhaul link beam indication or SRI.
[0067] In some configurations, SN FU 320 uses a previous (e.g., latest, most recently used) TCI state (e.g., downlink TCI state, uplink TCI state, combined TCI state, or unified TCI state) or a previous SRI prior to the BWP handover until SN CU 310 receives a new MAC CE indicating the TCI state or an SRI for the backhaul link after the BWP handover. In some examples, SN FU 320 uses a previous TCI state prior to the BWP handover until SN CU 310 receives a new MAC CE indicating the downlink TCI state of the backhaul link after the BWP handover. In some examples, SN FU 320 uses a previous uplink TCI state, combined TCI state, unified TCI state, or SRI prior to the BWP handover until a new MAC CE indicating the uplink TCI state, combined TCI state, unified TCI state, or SRI of the backhaul link after the BWP handover is received. In some examples, the TCI state ID indicated by the previous MAC CE refers to or corresponds to a TCI state with the same ID in the TCI state list of the previous active downlink BWP, and that TCI state is the previous TCI state. In some examples, the TCI state ID indicated by the new MAC CE refers to or corresponds to a TCI state with the same ID in the TCI state list of the new active downlink BWP. In some examples, "after BWP handover" means after the start of the BWP handover process or after the completion of the BWP handover process. In other words, in examples where a previous MAC CE for backhaul link beam indication is received before the BWP handover (before the start or completion of the BWP handover process), the SN FU 320 performs reception or transmission on the backhaul link based on the TCI state or SRI list (or SRS resource list) belonging to the previous active BWP. In some examples, the TCI status or SRI is determined based on the TCI status ID or SRI ID indicated by the previous MAC CE and the list of TCI status or SRI in the previous active BWP of the C link until after the BWP switch, when the SN CU 310 receives a new MAC CE indicating the TCI status or an SRI for the backhaul link.
[0068] In some configurations, a previous MAC CE is received before the BWP handover for beam indication of the backhaul link. The backhaul link beam after the BWP handover can include a default beam according to predefined rules associated with the previous active BWP, until SN CU 310 receives a new MAC CE indicating the TCI state (e.g., downlink TCI state, uplink TCI state, combined TCI state, or unified TCI state) or an SRI for the downlink or uplink beam for the backhaul link after the BWP handover. For reception on the backhaul link, in the example where SN 106 does not receive a unified TCI state indication received by SN CU 310, reception on the backhaul link uses the same quasi-co-address (QCL) parameters used for PDCCH reception in the control resource set (CORESET) with the lowest ID (e.g., controlResourceSetId) in the previous active downlink BWP. In the example where SN 106 receives a unified TCI status indication for SN CU 310 reception, reception on the backhaul link uses the QCL parameters provided by the indicated unified TCI status for SN CU 310 reception. For transmissions on the backhaul link, in the example where SN 106 does not receive a unified TCI status indication for SN CU 310 transmissions, transmissions on the backhaul link use the same spatial filter associated with the PUCCH resource with the smallest ID (e.g., PUCCHResourceId) in the PUCCH resource set of the previous active uplink BWP. In the example where SN 106 receives a unified TCI status indication for SNCU 310 transmissions, transmissions on the backhaul link use the spatial filter corresponding to the unified TCI status indicated by the SN CU 310 transmission. In some examples, "before BWP handover" means before the BWP handover process begins or before the BWP handover process completes. In some examples, "after BWP handover" means after the BWP handover process begins or after the BWP handover process completes.
[0069] In some configurations, a previous MAC CE for backhaul link beam indication is received before BWP handover. After BWP handover, the backhaul link beam can apply a default beam according to predefined rules associated with the new active BWP until SN CU 310 receives a new MAC CE indicating the TCI state (e.g., downlink TCI state, uplink TCI state, combined TCI state, or unified TCI state) or an SRI for the downlink or uplink beam for the backhaul link after BWP handover. For reception on the backhaul link, in some examples where SN 106 does not receive a unified TCI state indication received by SN CU 310, reception on the backhaul link uses the same QCL parameters used for PDCCH reception in the CORESET with the lowest ID (e.g., controlResourceSetId) in the new active downlink BWP. In some examples where SN 106 receives a unified TCI state indication for SN CU 310 reception, reception on the backhaul link uses the QCL parameters provided by the indicated unified TCI state for SN CU 310 reception. For transmissions on the backhaul link, in some examples where SN 106 does not receive a unified TCI status indication for the SN CU 310 transmission, the transmissions on the backhaul link use the same spatial filter as the PUCCH resource with the smallest ID (e.g., PUCCH ResourceId) in the PUCCH resource set of the new active uplink BWP. In examples where SN 106 receives a unified TCI status indication for the SN CU 310 transmission, the transmissions on the backhaul link use the spatial filter corresponding to the unified TCI status indicated by the SN CU 310 transmission. In some examples, "before BWP handover" means before the BWP handover process begins or before the BWP handover process completes. In some examples, "after BWP handover" means after the BWP handover process begins or after the BWP handover process completes.
[0070] In some configurations, a previous MAC CE for backhaul link beam indication is received prior to the BWP handover. The TCI state (e.g., downlink TCI state, uplink TCI state, combined TCI state, or unified TCI state) or SRI is determined based on the TCI state list or SRI list of the new active BWP after the BWP handover. In some examples, the TCI state or SRI is determined based on the TCI state ID or SRI ID indicated by the previous MAC CE prior to the BWP handover and the TCI state list or SRI list in the new active BWP of the C link. In some examples, the TCI state ID indicated by the previous MAC CE refers to or corresponds to a TCI state with the same ID in the TCI state list of the new active downlink BWP. In some examples, the uplink TCI state ID (and / or combined TCI state ID or unified TCI state ID) or SRI ID indicated by the previous MAC CE refers to or corresponds to an uplink TCI state with the same ID in the uplink TCI state list of the new active uplink BWP or an SRI with the same ID in the SRI list. In some examples, "before BWP handover" means before the BWP handover process begins or before it completes. In some examples, "after BWP handover" means after the BWP handover process begins or after it completes. In some examples, the TCI status or SRI is determined based on the TCI status ID or SRI ID indicated by the previous MAC CE and the TCI status list or SRI list in the new active BWP for the C link, only if the size of the TCI status list (or SRI list) in the previous active BWP is the same as the size of the TCI status list (or SRI list) in the new active BWP, or if the content of the TCI status list (or SRI list) in the previous active BWP is the same as the content of the TCI status list (or SRI list) in the new active BWP.
[0071] In some examples, the size of the TCI status list (or SRI list) in the previous active BWP is different from the size of the TCI status list (or SRI list) in the new active BWP, or in some examples, the contents of the TCI status list (or SRI list) are different regardless of whether the two lists are the same size (e.g., the same TCI ID in the two lists is associated with different reference signals or QCL types), and the TCI status ID indicated by the previous MAC CE may not be mapped to the TCI status (or SRI) in the TCI status list (or SRI list) in the new active BWP.
[0072] In some arrangements, where the TCI status ID (or SRI ID) previously indicated by the MAC CE is in the TCI status list (or SRI list) of the new active BWP, the TCI status or SRI is determined based on the TCI status ID or SRI ID previously indicated by the MAC CE and the TCI status list or SRI list of the new active BWP after the BWP switch. That is, in this case, the TCI status ID indicated by the previous MAC CE may be the same as one of the TCI status IDs in the TCI status list of the new active BWP. In some arrangements, where the TCI status ID (or SRI ID) previously indicated by the MAC CE is not in the TCI status list (or SRI list) of the new active BWP, at least one of the first, second, third, fourth, and fifth methods can be performed. That is, in this case, no TCI status ID (or SRI ID) in the TCI status list (or SRI list) of the new active BWP is the same as the TCI status ID (or SRI ID) indicated by the MAC CE.
[0073] In some arrangements, where the size of the TCI status list (or SRI list) in the previous active BWP is different from the size of the TCI status list (or SRI list) in the new active BWP, at least one of the first, second, third, fourth, and fifth methods can be executed. In some arrangements, where the content of the TCI status list (or SRI list) in the previous active BWP is different from the content of the TCI status list (or SRI list) in the new active BWP, at least one of the first, second, third, fourth, and fifth methods can be executed.
[0074] In some examples, at least one of the first, second, third, fourth, and fifth methods can be performed regardless of whether the TCI status ID (or SRI ID) indicated by the MAC CE is in the TCI status list (or SRI list) in the new active BWP.
[0075] In some arrangements where the two TCI status lists are the same size, the two SRI lists are the same size, the contents of the TCI status lists are the same, or the contents of the SRI lists are the same, the TCI status or SRI is determined based on the TCI status list or SRI list of the new active BWP after the BWP switch.
[0076] In some configurations, where the size of the TCI status list (or SRI list) in the previous active BWP is different from the size of the TCI status list (or SRI list) in the new active BWP, and the TCI status ID indicated by the MAC CE is in the TCI status list in the new active BWP, then the TCI status or SRI is determined based on the TCI status list or SRI list of the new active BWP after the BWP switch.
[0077] In some configurations, the contents of the TCI status list (or SRI list) in the previous active BWP are different from the contents of the TCI status list (or SRI list) in the new active BWP, and the TCI status ID indicated by the MAC CE is in the TCI status ID in the TCI status list of the new active BWP. The TCI status or SRI is determined based on the TCI status list or SRI list of the new active BWB after the BWP switch.
[0078] In some arrangements, where the TCI status ID (or SRI ID) indicated by the previous MAC CE is not in the TCI status list (or SRI list) in the new active BWP, at least one of the first, second, third, fourth and fifth methods can be performed.
[0079] In some examples, in the first approach, the SN FU 320 is excluded from transmission or reception, or does not transmit or receive until a new MAC CE is received that updates the TCI status (or SRI) of the backhaul link beam.
[0080] In some examples, in the second approach, the indicated TCI status (or SRI) is determined based on the TCI status list (or SRI list) of the previous active BWP.
[0081] In some examples, in the third approach, the backhaul link beam can be applied with a default beam based on predefined rules associated with the previous or new active BWP.
[0082] In some examples, in the fourth method, the TCI state ID (or SRI ID) indicated by MAC CE refers to or corresponds to the TCI state (or SRI) with the lowest or highest ID in the TCI state list (or SRI list) of the new active BWP.
[0083] In some examples, in the fifth method, the TCI state ID (or SRI ID) indicated by MAC CE refers to or corresponds to the TCI state (or SRI) in the TCI state list (or SRI list) of the new active BWP that has the ID closest to the TCI state ID (or SRI-ID).
[0084] In some examples, prior or latest MAC CE beam indications for the backhaul link are received before the BWP handover. After the BWP handover, the backhaul link beam can be assigned a default beam according to predefined rules. In some examples, this document describes in more detail the predefined rules used to determine the backhaul link beam (e.g., determining reception and transmission on the backhaul link).
[0085] In some arrangements, a default beam for the backhaul link can be provided according to predefined rules. In some arrangements, where SN 106 simultaneously receives and transmits via both the control link and the backhaul link within a set of time-domain resources (e.g., symbols), the TCI state or spatial filter (or SRI) used for receiving and transmitting can be the same as the TCI state or spatial filter (or SRI) on the control link within that set of time-domain resources (e.g., symbols). This can be applied to situations where SN CU 310 can begin transmitting and receiving signals after a BWP handover.
[0086] In some examples, where SN 106 does not receive and transmit simultaneously on the control link and the backhaul link, if SN 106 does not support determining the backhaul link beam based on explicit indication (e.g., via MAC CE), or if SN 106 does not receive or apply explicit indication, then SN FU 320 determines the backhaul link beam after BWP handover in the manner described herein.
[0087] In some examples, the backhaul link can apply a default beam according to predefined rules associated with the previous active BWP. For reception on the backhaul link, in examples where no unified TCI status indication for SN CU 310 reception is received on SN 106, reception on the backhaul link uses the same QCL parameters used for PDCCH reception in the CORESET with the lowest ID (e.g., controlResourceSetId) in the previous active downlink BWP. In examples where a unified TCI status indication for SN CU 310 reception is received on SN 106, reception on the backhaul link uses the QCL parameters provided by the indicated unified TCI status for SN CU 310 reception. For transmission on the backhaul link, in examples where no unified TCI status indication for SN CU 310 transmission is received on SN 106, transmission on the backhaul link uses the same spatial filter associated with the PUCCH resource with the lowest ID (e.g., PUCCH ResourceId) in the PUCCH resource set of the previous active uplink BWP. In the example where SN 106 receives a unified TCI status indication for a transmission on SN CU 310, the transmission on the backhaul link uses a spatial filter corresponding to the unified TCI status indicated by the transmission on SN CU 310. The backhaul link can apply a default beam according to predefined rules associated with the previous active BWP until the BWP handover is complete, or until the QCL parameters / spatial filters for the receive / transmit PDCCH / PUCCH of the C link are updated after the BWP handover (e.g., associated with a new active BWP).
[0088] In some examples, the backhaul link can apply a default beam according to predefined rules associated with the new active BWP. For reception on the backhaul link, in examples where SN 106 does not receive a unified TCI status indication for SN CU 310 reception, reception on the backhaul link uses the same QCL parameters used for PDCCH reception in the CORESET with the lowest ID (e.g., controlResourceSetId) in the new active downlink BWP. In examples where SN 106 receives a unified TCI status indication for SN CU 310 reception, reception on the backhaul link uses the QCL parameters provided by the indicated unified TCI status for SN CU 310 reception. For transmission on the backhaul link, in examples where SN does not receive a unified TCI status indication for SN CU 310 transmission, transmission on the backhaul link uses the same spatial filter associated with the PUCCH resource with the lowest ID (e.g., pucch-ResourceId) in the PUCCH resource set in the new active uplink BWP. In the example where SN 106 does not receive a unified TCI status indication for SN CU 310 transmissions, the transmissions on the backhaul link use a spatial filter corresponding to the unified TCI status indicated by the transmissions on SN CU 310. "After BWP handover" refers to either after the start or completion of the BWP handover process. The SN may receive an indication of the unified TCI status for reception before or after the BWP handover. After the BWP handover, or after the BWP handover is completed (e.g., associated with a new active BWP), and after the QCL parameters / spatial filters for PDCCH / PUCCH reception / transmission on the C link are updated, the backhaul link can apply a default beam according to predefined rules associated with the new active BWP.
[0089] In some deployments, BWP handover can be divided into two phases: a first phase defined as the period from the start of the handover to its completion, and a second phase defined as the period after the handover is complete. By analyzing each phase, solutions (e.g., predefined rules) can be provided for each phase.
[0090] The first phase is defined as the time period from the start of the BWP handover to its completion. In some examples, SN106 (e.g., SN-CU 310) receives a unified TCI status indication for SN-CU 330's reception / transmission. In some examples where SN-CU 310 does not receive or transmit any signals during the first phase, SN106 (e.g., SN-CU 310) receives a unified TCI status indication for SN-CU 310's reception / transmission before the BWP handover begins.
[0091] In some configurations, reception / transmission on the backhaul link is determined based on the unified TCI status used for SN-CU 310 reception / transmission. The unified TCI status used for SN-CU 310 reception / transmission is associated with the previously active BWP in the indication or the indicated BWP.
[0092] During the first phase, in some examples, SN 106 (e.g., SN-CU 310) did not receive an indication of the unified TCI status for SN-CCU 310 reception / transmission before the BWP handover began.
[0093] In some arrangements, reception on the backhaul link is based on the same QCL parameters as PDCCH reception in the CORESET with the lowest CORESETID in the previous active DL BWP. In some arrangements, transmission on the backhaul link is based on or uses the same spatial filter as that used or associated with the PUCCH resource with the lowest PUCCH resource ID in the previous active UL BWP.
[0094] In some arrangements, reception on the backhaul link is based on or uses the same QCL parameters as the PDCCH reception in the CORESET with the lowest CORESET ID in the new active DL BWP. In some arrangements, transmission on the backhaul link is based on or uses the same spatial filter as that used or associated with the PUCCH resource with the lowest PUCCH resource ID in the new active UL BWP.
[0095] The second phase is defined as the time period after the BWP handover is completed. In some examples, SN 106 (e.g., SN-CU310) receives an indication of the unified TCI status for SN-CU 30 reception / transmission after the BWP handover is completed (regardless of whether SN 106 received the indication of the unified TCI status for SN-CU 310 reception / transmission before the BWP handover).
[0096] In some examples, reception / transmission on the backhaul link is determined based on the unified TCI status indicated for reception / transmission on the SN-CU 310. The unified TCI status is indicated in the indication received by the SN 106 (e.g., SN-CU 310) after BWP handover. The unified TCI status is associated with the new active BWP or the BWP specified in the indication.
[0097] In some examples, SN 106 (e.g., SN-CU 310) receives an indication of the unified TCI status for SN-CU reception / transmission only before the BWP handover begins. That is, after the BWP handover is complete, SN 106 (e.g., SN-CU 310) does not receive an indication of the unified TCI status for SN-CU 310 reception / transmission.
[0098] In some examples, reception on the backhaul link is determined based on the same QCL parameters as the PDCCH reception in the CORESET with the lowest CORESET ID in the previous active DL BWP. In some examples, transmission on the backhaul link is based on or uses the same spatial filter used or associated with the PUCCH resource with the lowest PUCCH resource ID in the previous active UL BWP.
[0099] In some examples, reception on the backhaul link is determined based on the same QCL parameters as the PDCCH reception in the CORESET with the lowest CORESETID in the new active DL BWP. In some examples, transmission on the backhaul link is based on or uses the same spatial filter as the PUCCH resource with the lowest PUCCH resource ID or its associated spatial filter used in the new active UL BWP. This mechanism can be applied if the QCL parameters / spatial filter for PDCCH / PUCCH reception / transmission has been updated after BWP handover is complete. This mechanism can be performed by SN 106 until an indication of the unified TCI status for reception / transmission for SN-CU 310 is received after BWP handover begins.
[0100] In some examples, reception / transmission on the backhaul link is determined based on the unified TCI status indicated for reception / transmission of the SN-CU 310. The unified TCI status for reception / transmission of the SN-CU 310 is associated with the BWP indicated in a previous active BWP or indication.
[0101] In some examples, SN 106 (e.g., SN-CU 310) does not receive an indication of the unified TCI status for the receive / transmit of SN-CU 330. That is, SN 106 (e.g., SN-CU 310) will not receive an indication of the unified TCI status for the receive / transmit of SN-CU 330, either before or after the BWP handover.
[0102] In some examples, reception on the backhaul link is determined based on the same QCL parameters as the PDCCH reception in the CORESET with the lowest CORESET ID in the previous active DL BWP. In some examples, transmission on the backhaul link is based on or uses the same spatial filter as the spatial filter used or associated with the PUCCH resource with the lowest PUCCH resource ID in the previous active UL BWP. This mechanism can be applied when the QCL parameters / spatial filters for PDCCH / PUCCH reception / transmission have not been updated after the BWP handover is complete.
[0103] In some examples, reception on the backhaul link is determined based on the same QCL parameters as the PDCCH reception in the CORESET with the lowest CORESETID in the new active DL BWP. In other examples, transmission on the backhaul link is based on or uses the same spatial filter as the PUCCH resource with the lowest PUCCH resource ID or its associated spatial filter used in the new active UL BWP. This mechanism can be applied when the QCL parameters / spatial filters for PDCCH / PUCCH reception / transmission have been updated after the BWP handover is complete.
[0104] Figure 4 This is a flowchart illustrating an example method 400 for performing frequency switching and receiving / forwarding signals on an SN 106 according to various arrangements. Method 400 can be performed by an SN 106 (e.g., SN CU 310 and SN FU 320).
[0105] At 410, a first functional unit (e.g., CU 310) of the first communication node (e.g., SN 106) performs a frequency switch to switch from a first frequency to a second frequency. At 420, a second functional unit (e.g., FU 320) of the first communication node performs at least one of the following operations: receiving a signal from a first of a second communication node (e.g., BS 102) or a third communication node (e.g., UE 104), or forwarding a signal to a second of a second or third communication node.
[0106] In some examples, the first communication node includes an SN. The first functional unit includes a CU. The second functional unit includes a FU. Frequency switching includes BWP switching. The first frequency includes a first BWP or a first frequency range. The second frequency includes a second BWP or a second frequency range.
[0107] In some examples, the first communication node includes at least one of an SN, a repeater, a relay node, a RIS, an IRS, an IAB node, a part or component of a BS, a TRP, a UE, a controller, or a wireless communication device. In some examples, the second communication node includes a BS. The third communication node includes a UE or a wireless communication device.
[0108] In some examples, method 400 further includes disabling the transmission or reception of a second functional unit of the first communication node during a frequency switch; and, in response to the completion of the frequency switch, enabling the second functional unit to perform at least one of the following operations: receiving a signal from the first of the second or third communication nodes by the second functional unit, and forwarding the signal to the second of the second or third communication nodes by the second functional unit.
[0109] In some examples, during frequency switching, the first functional unit is excluded from at least one of the transmission or reception. In some examples, during frequency switching, the second functional unit is excluded from at least one of the transmission or reception.
[0110] In some examples, during a frequency handover, the second functional unit is disabled in response to determining that the frequency handover includes a DCI-based frequency handover. In some examples, during a frequency handover, the second functional unit is disabled in response to the first functional unit detecting a DCI format indicating a change in the frequency of an active downlink or uplink.
[0111] In some examples, during frequency switching, in response to the first functional unit detecting a DCI format with a BWP indicator field, the second functional unit is shut down, which indicates an active downlink or uplink frequency change.
[0112] In some examples, during frequency switching, in response to the first functional unit detecting a DCI format with a SCell sleep indicator, the second functional unit is shut down, which indicates a change in the active downlink BWP of the SCell in the time domain resources of the PCell.
[0113] In some examples, during a frequency switch, in response to determining that the frequency switch includes a timer-based frequency switch, the second functional unit is turned off.
[0114] In some examples, during frequency switching, the second functional unit is turned off in response to the first functional unit changing the active downlink BWP due to at least one of the expiration of the BWP inactive timer, the change delay of the active downlink BWP, or the change delay of the active uplink BWP.
[0115] In some examples, during a frequency switch, in response to determining that the frequency switch includes an RRC-based frequency switch, the second functional unit is turned off.
[0116] In some examples, the second functional unit is turned off until the first functional unit receives an indication of the TCI status or SRI after the frequency switch has started or after the frequency switch has been completed.
[0117] In some examples, the second functional unit uses the previous TCI state or previous SRI used before the frequency switch until a new indication of a new TCI state or new SRI is received after the frequency switch.
[0118] In some examples, the second functional unit uses the default beam to receive the signal and forwards it after a frequency switch. The default beam is determined based on the previous active beam used before the frequency switch.
[0119] In some examples, the second functional unit uses the default beam to receive the signal and forwards it after a frequency switch. The default beam is determined based on the new active beam used after the frequency switch.
[0120] In some examples, the second functional unit determines at least one of the TCI status or SRI based on at least one of the TCI status list or SRI list of the new active BWP used after the frequency switch.
[0121] In some examples, the TCI status ID or SRI ID indicated by the indication received before the frequency switch is in the TCI status list or SRI list of the active BWP used after the frequency switch. The TCI status or SRI is determined based on at least one of the TCI status list or SRI list of the active BWP used after the frequency switch.
[0122] In some examples, the TCI status ID or SRI ID indicated by the indication received before the frequency switch is not in the TCI status list or SRI list of the new active BWP used after the frequency switch. In some examples, the second functional unit shuts down transmission or reception until a new indication updating the TCI status or SRI of the backhaul link is received after the frequency switch. In some examples, the second functional unit uses the previous TCI status or previous SRI used before the frequency switch until a new indication indicating a new TCI status or new SRI is received after the frequency switch. In some examples, the second functional unit uses a default beam to receive and forward signals after the frequency switch, the default beam being determined based on either the previous active BWP used before the frequency switch or the new active BWP used after the frequency switch. In some examples, the second functional unit uses a TCI status with a TCI status ID that is the lowest or highest ID in the TCI status list of the new active BWP, or the second functional unit uses an SRI with a SRI ID that is the lowest or highest ID in the SRI list of the new active BWP. In some examples, the second functional unit uses a TCI state with a TCI state ID that is closest to the TCI state ID in the TCI state list of the new active BWP, or the second functional unit uses an SRI with an SRI ID that is closest to the SRI ID in the SRI list of the new active BWP.
[0123] In some examples, the size of the TCI status list in the previous active BWP used before the frequency switch is different from the size of the TCI status list in the new active BWP used after the frequency switch. In some examples, the size of the SRI list in the previous active BWP used before the frequency switch is different from the size of the SRI list in the new active BWP used after the frequency switch. In some examples, the second functional unit disables transmission or reception until a new indication of updated TCI status or SRI for the backhaul link is received after the frequency switch. In some examples, the second functional unit uses the previous TCI status or previous SRI used before the frequency switch until a new indication of a new TCI status or new SRI is received after the frequency switch. In some examples, the second functional unit uses a default beam to receive signals and forward signals after the frequency switch, the default beam being determined based on either the previous active BWP used before the frequency switch or the new active BWP used after the frequency switch. In some examples, the second functional unit uses a TCI state with a TCI state ID that is the lowest or highest ID in the new active BWP's TCI state list; or the second functional unit uses an SRI with a SRI ID that is the lowest or highest ID in the new active BWP's SRI list. In some examples, the second functional unit uses a TCI state with a TCI state ID that is closest to a TCI state ID in the new active BWP's TCI state list; or the second functional unit uses an SRI with a SRI ID that is closest to a SRI ID in the new active BWP's SRI list.
[0124] In some examples, the contents of the TCI status list in the previous active BWP used before the frequency switch differ from the contents of the TCI status list in the new active BWP used after the frequency switch. In some examples, the contents of the SRI list in the previous active BWP used before the frequency switch differ from the contents of the SRI list in the new active BWP used after the frequency switch. In some examples, the second functional unit disables transmission or reception until a new indication of updated TCI status or SRI for the backhaul link is received after the frequency switch. In some examples, the second functional unit uses the previous TCI status or previous SRI used before the frequency switch until a new indication of a new TCI status or new SRI is received after the frequency switch. In some examples, the second functional unit uses a default beam to receive signals and forward signals after the frequency switch, the default beam being determined based on either the previous active BWP used before the frequency switch or the new active BWP used after the frequency switch. In some examples, the second functional unit uses a TCI state with a TCI state ID that is the lowest or highest ID in the new active BWP's TCI state list; or the second functional unit uses an SRI with a SRI ID that is the lowest or highest ID in the new active BWP's SRI list. In some examples, the second functional unit uses a TCI state with a TCI state ID that is closest to a TCI state ID in the new active BWP's TCI state list; or the second functional unit uses an SRI with a SRI ID that is closest to a SRI ID in the new active BWP's SRI list.
[0125] In some examples, the size of the TCI status list in the previous active BWP used before the frequency switch is different from the size of the TCI status list in the new active BWP used after the frequency switch. In some examples, the size of the SRI list in the previous active BWP used before the frequency switch is different from the size of the SRI list in the new active BWP used after the frequency switch. In some examples, the TCI status ID or SRI ID indicated by the indication received before the frequency switch is within the TCI status list or SRI list of the new active BWP. In some examples, the indicated TCI status or SRI is determined based on the TCI status list or SRI list of the new active BWP.
[0126] In some examples, the contents of the TCI status list in the previous active BWP used before the frequency switch differ from the contents of the TCI status list in the new active BWP used after the frequency switch. In some examples, the contents of the SRI list in the previous active BWP used before the frequency switch differ from the contents of the SRI list in the new active BWP used after the frequency switch. In some examples, the TCI status ID or SRI ID indicated by an indication received before the frequency switch is a TCI status ID or SRI ID in the TCI status list or SRI list of the new active BWP. In some examples, the TCI status or SRI is determined based on the TCI status list or SRI list of the new active BWP.
[0127] In some examples, the second functional unit uses a default beam to receive and relay signals. The default beam is determined based on the previous active beam used prior to the frequency conversion.
[0128] In some examples, the second functional unit uses a default beam to receive and relay signals. The default beam is determined based on the new active beamhead used after a frequency switch.
[0129] In some examples, method 400 further includes forwarding a signal by a second functional unit to a first of a second or third communication node. The first of the second or third communication nodes includes a base station. Receiving a signal from or forwarding a signal to the first of the second or third communication nodes is performed based on a unified TCI state of at least one of the reception or transmissions performed by the first functional unit. The unified TCI state is associated with an active BWP or an indicated BWP used prior to a frequency switch.
[0130] In some examples, method 400 further includes forwarding a signal by a second functional unit to a first of a second or third communication node. The first of the second or third communication nodes includes a base station. Receiving a signal from or forwarding a signal to the first of the second or third communication nodes is performed, at least one of which is based on the QCL parameters for downlink reception (e.g., PDCCH) in the CORESET with the lowest ID in the active downlink BWP used prior to frequency switching.
[0131] In some examples, method 400 further includes forwarding a signal by a second functional unit to a first of a second or third communication node. The first of the second or third communication nodes includes a base station. Receiving a signal from or forwarding a signal to the first of the second or third communication nodes is performed, at least one of which is based on a spatial filter of an uplink (e.g., PUCCH) resource having the lowest ID among the active uplink BWPs used prior to the frequency switch.
[0132] In some examples, method 400 further includes forwarding a signal by the second functional unit to a first of the second or third communication nodes. The first of the second or third communication nodes includes a base station. Receiving a signal from or forwarding a signal to the first of the second or third communication nodes is performed based on a unified TCI state for at least one of the reception or transmission of the first functional unit. The unified TCI state is indicated in an indication received after frequency switching is completed, and the unified TCI state is associated with the active BWP used after the frequency switching or the BWP in the indication.
[0133] In some examples, method 400 further includes forwarding a signal by a second functional unit to a first of a second or third communication node. The first of the second or third communication nodes includes a base station. Receiving a signal from or forwarding a signal to the first of the second or third communication nodes is performed, at least one of which is based on the QCL parameters for downlink reception (e.g., PDCCH) in the CORESET with the lowest ID in the active downlink BWP used after frequency switching.
[0134] In some examples, method 400 further includes forwarding a signal by a second functional unit to a first of a second or third communication node. The first of the second or third communication nodes includes a base station. Receiving a signal from or forwarding a signal to the first of the second or third communication nodes is performed, at least one of which is based on a spatial filter of an uplink resource (e.g., PUCCH) having the lowest ID among the active uplink BWPs used after a frequency switch.
[0135] In some examples, method 400 further includes forwarding a signal by the second functional unit to a first of the second or third communication nodes. The first of the second or third communication nodes includes a base station. Receiving a signal from or forwarding a signal to the first of the second or third communication nodes is performed based on a unified TCI state for at least one of the reception or transmission by the first functional unit. The unified TCI state is indicated in the indication and is associated with the active BWP used prior to the frequency switch or the BWP in the indication.
[0136] While various arrangements of this disclosure have been described above, it should be understood that they are by way of example only and not as limitations. Similarly, various figures may depict exemplary architectures or configurations provided to enable those skilled in the art to understand exemplary features and functionality of the solution. However, such individuals will understand that the solution is not limited to the exemplary architectures or configurations shown, but can be implemented using various alternative architectures and configurations. Furthermore, as those skilled in the art will understand, one or more features of one arrangement may be combined with one or more features of another arrangement described herein. Therefore, the breadth and scope of this disclosure should not be limited by any of the illustrative arrangements described above.
[0137] It should also be understood that any reference to elements using names such as "first," "second," etc., in this document generally does not restrict the number or order of these elements. Rather, these names can be used as a convenient means of distinguishing two or more elements or instances of elements in this document. Therefore, mentioning the first and second elements does not imply that only two elements can be used, nor does it imply that the first element must precede the second element in some way.
[0138] Furthermore, those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, and symbols that may be referenced in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.
[0139] Those skilled 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 can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of program or design code containing instructions (which may be referred to herein as "software" or "software module" for convenience), or any combination of these technologies. To clearly illustrate this interchangeability of hardware, firmware, and software, the various illustrative components, blocks, modules, circuits, and steps have been generally described above according to their functionality. 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 system as a whole. Those skilled in the art can implement the described functionality in various ways for each specific application, but such implementation decisions will not depart from the scope of this disclosure.
[0140] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, devices, components, and circuits described herein can be implemented within or executed 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. Logic blocks, modules, and circuits may also include antennas and / or transceivers for communicating with various components within a network or device. A general-purpose processor may be a microprocessor, but may also be any conventional processor, controller, or state machine. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration performing the functions described herein.
[0141] If implemented in software, these functions can be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include computer storage media and communication media, encompassing any medium capable of transferring computer programs or code from one place to another. Storage media can be any available medium accessible to a computer. For example (but not limited to), such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that can be used to store the required program code in the form of instructions or data structures and is accessible to a computer.
[0142] In this document, the term "module" refers to software, firmware, hardware, and any combination of these elements used to perform the functions described herein. Furthermore, for ease of discussion, various modules are described herein as discrete modules; however, it will be apparent to those skilled in the art that, depending on the arrangement of this solution, two or more modules can be combined into a single module to perform the relevant functions.
[0143] Furthermore, the arrangement of this solution may also incorporate memory or other storage devices, as well as communication components. It should be understood that, for clarity, the above description refers to different functional units and processors in illustrating the arrangement of this solution. However, it is evident that any suitable allocation of functions among different functional units, processing logic elements, or domains can be employed without diminishing the effectiveness of this solution. For example, a function originally conceived to be performed by a separate processing logic element or controller may also be performed by the same processing logic element or controller. Therefore, references to specific functional units indicate only the appropriate means of providing the stated function and do not represent a strict logical or physical structure or organizational form.
[0144] Various modifications to the implementations described herein will become apparent to those skilled in the art, and the general principles defined herein can be applied to other implementations without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but should be given the broadest scope consistent with the novel features and principles disclosed herein, as set forth in the following claims.
Claims
1. A wireless communication method, comprising: The first functional unit of the first communication node performs frequency switching to switch from the first frequency to the second frequency; as well as At least one of the following: The second functional unit of the first communication node receives a signal from the first of the second or third communication nodes; or The second functional unit forwards the signal to the second communication node or the second of the third communication nodes.
2. The method according to claim 1, wherein The first communication node includes a smart node (SN); The first functional unit includes a control / communication unit (CU); The second functional unit includes a forwarding unit (FU); The frequency switching includes bandwidth portion (BWP) switching; The first frequency includes a first BWP or a first frequency range; and The second frequency includes a second BWP or a second frequency range.
3. The method of claim 1, wherein, The first communication node includes at least one of a smart node (SN), a repeater, a relay node, a reconfigurable smart surface (RIS), a smart reflective surface (IRS), an integrated access and backhaul (IAB) node, a part or component of a base station (BS), a transmission and reception point (TRP), a user equipment (UE), a controller, or a wireless communication device.
4. The method according to claim 1, wherein The second communication node includes a base station (BS); and The third communication node includes a user equipment (UE) or a wireless communication device.
5. The method according to claim 1, further comprising: During frequency switching, the transmission or reception of the second functional unit of the first communication node is turned off; as well as In response to the completion of the frequency switch, the second functional unit is activated to perform at least one of the following: The second functional unit receives a signal from the first of the second communication node or the third communication node; and The second functional unit forwards the signal to the second communication node or the second of the third communication nodes.
6. The method of claim 5, wherein, At least one of the following: During frequency switching, the first functional unit is excluded from at least one of the transmission or reception; or During frequency switching, the second functional unit is excluded from at least one of the transmission or reception.
7. The method of claim 5, wherein, During frequency switching, in response to determining that the frequency switching includes frequency switching based on downlink control information (DCI), the second functional unit is turned off.
8. The method of claim 5, wherein, During frequency switching, in response to the first functional unit detecting a downlink control information (DCI) format indicating a change in the frequency of an active downlink or uplink, the second functional unit is shut down.
9. The method of claim 5, wherein, During frequency switching, in response to the first functional unit detecting a downlink control information (DCI) format with a bandwidth portion (BWP) indicator field, the second functional unit is shut down, the indicator field indicating an active downlink or uplink frequency change.
10. The method of claim 5, wherein, During frequency switching, in response to the first functional unit detecting a downlink control information (DCI) format with a secondary cell (SCell) sleep indication, the second functional unit is shut down, the sleep indication indicating a change in the active downlink bandwidth portion (BWP) of the SCell in the time domain resources of the primary cell (PCell).
11. The method of claim 5, wherein, During frequency switching, in response to determining that the frequency switching includes timer-based frequency switching, the second functional unit is turned off.
12. The method of claim 5, wherein, During frequency switching, the second functional unit is shut down in response to the first functional unit changing the active downlink bandwidth portion (BWP) due to at least one of the expiration of the BWP inactive timer, the change delay of the active downlink BWP, or the change delay of the active uplink BWP.
13. The method of claim 5, wherein, During frequency switching, in response to determining that the frequency switching includes frequency switching based on Radio Resource Control (RRC), the second functional unit is turned off.
14. The method of claim 1, wherein, The second functional unit is turned off until, after frequency switching begins or after frequency switching is completed, the first functional unit receives an indication indicating the Transmission Configuration Indicator (TCI) status or the Probe Reference Signal (SRS) Resource Indicator (SRI).
15. The method of claim 1, wherein, The second functional unit uses the previous Transmission Configuration Indicator (TCI) state or the previous Sound Reference Signal (SRS) Resource Indicator (SRI) used before the frequency switch until a new indication indicating a new TCI state or a new SRI is received after the frequency switch.
16. The method of claim 1, wherein, The second functional unit uses a default beam to receive the signal and forwards the signal after a frequency switch, wherein the default beam is determined based on the previous active BWP used prior to the frequency switch.
17. The method of claim 1, wherein, The second functional unit uses a default beam to receive the signal and forwards the signal after a frequency switch, wherein the default beam is determined based on the new active BWP used after the frequency switch.
18. The method of claim 1, wherein, The second functional unit determines at least one of the Transmission Configuration Indicator (TCI) status or Probe Reference Signal (SRS) Resource Indicator (SRI) based on at least one of the TCI status list or SRI list of the new active BWP used after the frequency switch.
19. The method of claim 1, wherein The Transmission Configuration Indicator (TCI) status ID or SRI ID indicated by the indication received before the frequency switch; and the TCI status list or SRI list of the active BWP used after the frequency switch; and The TCI status or Detection Reference Signal (SRS) Resource Indicator (SRI) is determined based on at least one of the TCI status list or SRI list of the active BWP used after the frequency switch.
20. The method of claim 1, wherein The Transmission Configuration Indicator (TCI) status ID or SRI ID indicated by the indication received before the frequency switch is not in the TCI status list or SRI list of the new active BWP used after the frequency switch; and At least one of the following: The second functional unit shuts down transmission or reception until a new indication of the updated TCI status or SNR (Sound Reference Signal) Resource Indicator (SRI) is received after a frequency switch. The second functional unit uses the previous TCI state or previous SRI used before the frequency switch until a new indication of a new TCI state or new SRI is received after the frequency switch. The second functional unit uses a default beam to receive signals and forwards the signals after a frequency switch, wherein the default beam is determined based on a previous active BWP used before the frequency switch or a new active BWP used after the frequency switch; The second functional unit uses a TCI state with a TCI state ID, which is the lowest or highest ID in the TCI state list of the new active BWP; or the second functional unit uses an SRI with an SRI ID, which is the lowest or highest ID in the SRI list of the new active BWP; or The second functional unit uses a TCI state with a TCI state ID that is closest to a TCI state ID in the TCI state list of the new active BWP, or the second functional unit uses an SRI with an SRI ID that is closest to an SRI ID in the SRI list of the new active BWP.
21. The method of claim 1, wherein At least one of the following: The size of the Transmission Configuration Indicator (TCI) status list in the previous active BWP used before the frequency switch is different from the size of the TCI status list in the new active BWP used after the frequency switch; or The size of the Sounding Reference Signal (SRS) Resource Indicator (SRI) list in the previous active BWP used before the frequency switch is different from the size of the SRI list in the new active BWP used after the frequency switch; and At least one of the following: The second functional unit shuts down transmission or reception until a new indication of the updated TCI status or SNR (Sound Reference Signal) Resource Indicator (SRI) is received after a frequency switch. The second functional unit uses the previous TCI state or previous SRI used before the frequency switch until a new indication of a new TCI state or new SRI is received after the frequency switch. The second functional unit uses a default beam to receive signals and forwards the signals after a frequency switch, wherein the default beam is determined based on a previous active BWP used before the frequency switch or a new active BWP used after the frequency switch; The second functional unit uses a TCI state with a TCI state ID, which is the lowest or highest ID in the TCI state list of the new active BWP; or the second functional unit uses an SRI with an SRI ID, which is the lowest or highest ID in the SRI list of the new active BWP; or The second functional unit uses a TCI state with a TCI state ID that is closest to a TCI state ID in the TCI state list of the new active BWP, or the second functional unit uses an SRI with an SRI ID that is closest to an SRI ID in the SRI list of the new active BWP.
22. The method of claim 1, wherein At least one of the following: The contents of the Transport Configuration Indicator (TCI) status list in the previous active BWP used before the frequency switch are different from the contents of the TCI status list in the new active BWP used after the frequency switch; or The contents of the Sounding Reference Signal (SRS) Resource Indicator (SRI) list in the previous active BWP used before the frequency switch are different from the contents of the SRI list in the new active BWP used after the frequency switch; and At least one of the following: The second functional unit shuts down transmission or reception until a new indication of the updated TCI status or SNR (Sound Reference Signal) Resource Indicator (SRI) is received after a frequency switch. The second functional unit uses the previous TCI state or previous SRI used before the frequency switch until a new indication of a new TCI state or new SRI is received after the frequency switch. The second functional unit uses a default beam to receive signals and forwards the signals after a frequency switch, wherein the default beam is determined based on a previous active BWP used before the frequency switch or a new active BWP used after the frequency switch; The second functional unit uses a TCI state with a TCI state ID, which is the lowest or highest ID in the TCI state list of the new active BWP; or the second functional unit uses an SRI with an SRI ID, which is the lowest or highest ID in the SRI list of the new active BWP; or The second functional unit uses a TCI state with a TCI state ID that is closest to a TCI state ID in the TCI state list of the new active BWP, or the second functional unit uses an SRI with an SRI ID that is closest to an SRI ID in the SRI list of the new active BWP.
23. The method of claim 1, wherein At least one of the following: The size of the Transport Configuration Indicator (TCI) status list in the previous active BWP used before the frequency switch is different from the size of the TCI status list in the new active BWP used after the frequency switch; or a size of a sounding reference signal (SRS) resource indicator (SRI) list in a previous active BWP used before the frequency switching is different from a size of an SRI list of a new active BWP used after the frequency switching; as well as The TCI status ID or SRI ID indicated by the indication received before the frequency switch is in the TCI status list or SRI list in the new active BWP. as well as The indicated TCI status or SRI is determined based on the new activity BWP's TCI status list or SRI list.
24. The method of claim 1, wherein At least one of the following: The contents of the Transport Configuration Indicator (TCI) status list in the previous active BWP used before the frequency switch are different from the contents of the TCI status list in the new active BWP used after the frequency switch; or a content of a sounding reference signal (SRS) resource indicator (SRI) list in a previous active BWP used before the frequency switching is different from a content of an SRI list of a new active BWP used after the frequency switching; as well as The TCI status ID or SRI ID indicated by the indication received before the frequency switch is in the TCI status list or SRI list in the new active BWP. as well as The TCI status or SRI is determined based on the new activity BWP's TCI status list or SRI list.
25. The method of claim 1, wherein, The second functional unit uses a default beam to receive and forward signals, wherein the default beam is determined based on the previous active BWP used prior to the frequency conversion.
26. The method of claim 1, wherein, The second functional unit uses a default beam to receive and forward signals, wherein the default beam is determined based on the new active BWP used after a frequency switch.
27. The method of claim 1, further comprising the second functional unit forwarding the signal to the first of the second communication node or the third communication node, wherein, The second communication node or the first of the third communication nodes includes a base station, wherein receiving the signal from the second communication node or the first of the third communication nodes or forwarding the signal to the second communication node or the first of the third communication nodes, at least one of these two actions is performed based on a Unified Transmission Configuration Indicator (TCI) state of at least one of the reception or transmission performed by the first functional unit, wherein the unified TCI state is associated with an active bandwidth portion (BWP) used before frequency switching or a BWP in an indication.
28. The method of claim 1, further comprising the second functional unit forwarding the signal to the first of the second communication node or the third communication node, wherein, The second communication node or the first of the third communication nodes includes a base station, wherein receiving the signal from the second communication node or the first of the third communication nodes or forwarding the signal to the second communication node or the first of the third communication nodes, at least one of these two actions is performed based on the quasi-co-address (QCL) parameters for downlink reception in the control resource set (CORESET) with the lowest ID in the active downlink bandwidth portion (BWP) used prior to frequency switching.
29. The method of claim 1, further comprising the second functional unit forwarding the signal to the first of the second communication node or the third communication node, wherein, The second communication node or the first of the third communication nodes includes a base station, wherein receiving the signal from the second communication node or the first of the third communication nodes or forwarding the signal to the second communication node or the first of the third communication nodes, at least one of these two actions is performed based on a spatial filter of uplink resources having the lowest ID in the active uplink bandwidth portion (BWP) used prior to frequency switching.
30. The method of claim 1, further comprising the second functional unit forwarding the signal to the first of the second communication node or the third communication node, wherein, The second communication node or the first of the third communication nodes includes a base station, wherein receiving the signal from the second communication node or the first of the third communication nodes or forwarding the signal to the second communication node or the first of the third communication nodes, at least one of these two actions is performed based on a Uniform Transmission Configuration Indicator (TCI) state for at least one of the reception or transmission of the first functional unit, wherein the uniform TCI state is indicated in an indication, the uniform TCI state is received after a frequency switch is completed, and the uniform TCI state is associated with the active bandwidth portion (BWP) used after the frequency switch or the BWP in the indication.
31. The method of claim 1, further comprising the second functional unit forwarding the signal to the first of the second communication node or the third communication node, wherein, The second communication node or the first of the third communication nodes includes a base station, wherein receiving the signal from the second communication node or the first of the third communication nodes or forwarding the signal to the second communication node or the first of the third communication nodes, at least one of these two actions is performed based on the quasi-co-address (QCL) parameters for downlink reception in the control resource set (CORESET) with the lowest ID in the active downlink bandwidth portion (BWP) used after frequency switching.
32. The method of claim 1, further comprising the second functional unit forwarding the signal to the first of the second communication node or the third communication node, wherein, The second communication node or the first of the third communication nodes includes a base station, wherein receiving the signal from the second communication node or the first of the third communication nodes or forwarding the signal to the second communication node or the first of the third communication nodes, at least one of these two actions is performed based on a spatial filter of uplink resources having the lowest ID in the active uplink bandwidth portion (BWP) used after a frequency switch.
33. The method of claim 1, further comprising the second functional unit forwarding the signal to the first of the second communication node or the third communication node, wherein, The second communication node or the first of the third communication nodes includes a base station, wherein receiving the signal from the second communication node or the first of the third communication nodes or forwarding the signal to the second communication node or the first of the third communication nodes, at least one of these two actions is performed based on a Unified Transmission Configuration Indicator (TCI) state for at least one of the reception or transmission of the first functional unit, wherein the unified TCI state is indicated in the indication and is associated with the active bandwidth portion (BWP) used before frequency switching or the BWP in the indication.
34. A wireless communication device, comprising at least one processor and a memory, wherein, The at least one processor is configured to read code from the memory and implement the method of claim 1.
35. A computer program product comprising computer-readable program medium code stored thereon, the code, when executed by at least one processor, causing the at least one processor to implement the method of claim 1.