Method for mobile node to obtain neighboring node synchronization signal block (SSB) transmit configuration (STC)

Abstract

Certain aspects of the present disclosure provide a method for wireless communication by a first network entity. The first network entity obtains a synchronization signal block (SSB) transmit configuration (STC) of a second network entity. The first network entity measures one or more SSBs transmitted from the second network entity according to the STC configuration.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. patent application serial number 17 / 823,267, filed on August 30, 2022, which is hereby incorporated by reference into this application. Background Art Technical Field

[0003] Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for obtaining a synchronization signal block (SSB) transmission configuration (STC) of a node.

[0004] Related technologies

[0005] Wireless communication systems are widely deployed to provide various telecommunication services, such as telephony, video, data, messaging, broadcasts, or other similar types of services. These wireless communication systems may employ multiple-access technologies capable of supporting communications with multiple users by sharing available wireless communication system resources with those users.

[0006] Despite the tremendous technological advancements in wireless communication systems over the years, challenges remain. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and wireless receivers. Consequently, there is a continuing desire to improve the technical performance of wireless communication systems, including, for example, improving the speed and data carrying capacity of communications, improving the efficiency of shared communication media usage, reducing the power used by transmitters and receivers when performing communications, improving the reliability of wireless communications, avoiding redundant transmission and / or reception and related processing, improving the coverage area of ​​wireless communications, increasing the number and types of devices that can access wireless communication systems, increasing the ability of different types of devices to communicate with each other, and increasing the number and types of wireless communication media available for use. Consequently, there is a need for further improvements in wireless communication systems to overcome the aforementioned technical challenges and others. Summary of the Invention

[0007] One aspect provides a method for wireless communication by a first network entity, comprising: obtaining a synchronization signal block (SSB) transmission configuration (STC) of a second network entity; and measuring one or more SSBs sent from the second network entity according to the STC configuration.

[0008] On the other hand, a method for wireless communication by a node is provided, comprising: receiving signaling carrying a request for a synchronization signal block (SSB) transmission configuration (STC) of a second network entity from a first network entity; and sending signaling carrying the STC configuration of the second network entity to the first network entity in response to the request.

[0009] Other aspects provide: an apparatus operable to, configured to, or otherwise adapted to perform the aforementioned method and those described elsewhere herein; a non-transitory computer-readable medium comprising instructions that, when executed by a processor of the apparatus, cause the apparatus to perform the aforementioned method and those described elsewhere herein; a computer program product embodied on a computer-readable storage medium, the computer-readable storage medium comprising: code for performing the aforementioned method and those described elsewhere herein; and an apparatus comprising means for performing the aforementioned method and those described elsewhere herein. By way of example, an apparatus may comprise a processing system, a device having a processing system, or processing systems cooperating through one or more networks.

[0010] For purposes of illustration, the following detailed description and drawings set forth certain features. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The accompanying drawings depict certain features of the various aspects described herein and should not be considered as limiting the scope of the disclosure.

[0012] Figure 1 An example wireless communication network is depicted.

[0013] Figure 2 An example decomposed base station (BS) architecture is depicted.

[0014] Figure 3 Aspects of an example BS and example user equipment (UE) are depicted.

[0015] Figure 4A 、 Figure 4B 、 Figure 4C and Figure 4D Various example aspects of data structures for a wireless communication network are described.

[0016] Figure 5 Depicted is an example integrated access and backhaul (IAB) network architecture.

[0017] Figure 6 、 Figure 7 、 Figure 8 and Figure 9 Depicts different use cases for full-duplex (FD) communication.

[0018] Figure 10 、 Figure 11 、 Figure 12 and Figure 13 Different deployment scenarios for FD and half-duplex (HD) communications are depicted.

[0019] Figure 14ADepicted are example communications between a static IAB donor node, a static IAB node, and a UE.

[0020] Figure 14B Depicted are example synchronization signal block (SSB) transmission configurations (STC) and SSB measurement time configurations (SMTC) configured for a static IAB donor node, a static IAB node, and a UE.

[0021] Figure 15 、 Figure 16 and Figure 17 Depicted are example call flow diagrams illustrating communications between different network entities and nodes.

[0022] Figure 18 Depicted is an example communication between a static node and a mobile node.

[0023] Figure 19 A method for wireless communication by a first network entity is described.

[0024] Figure 20 Methods for wireless communications by nodes are described.

[0025] Figure 21 and Figure 22 Aspects of an example communication device are depicted. DETAILED DESCRIPTION

[0026] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for obtaining a synchronization signal block (SSB) transmission configuration (STC) of a node in full-duplex (FD) operation.

[0027] FD communication allows simultaneous transmissions between nodes (e.g., integrated access and backhaul (IAB) nodes, gNodeB (gNB)). Half-duplex (HD) communication flows in one direction at a time.

[0028] IAB generally refers to nodes that support multi-hop networks or multi-hop wireless backhaul, and allows the deployment of network entities with or without fiber backhaul transmission. IAB works by enabling a portion of the deployed network entities to act as donor nodes using fiber / wired connections. The remaining network entities (e.g., those without wired connections) are referred to as IAB nodes.

[0029] In a typical IAB network, the IAB donor includes a central unit (CU) that configures the IAB donor and / or the distributed units (DUs) of an IAB node (e.g., a mobile terminal module (MT) or a DU of an IAB node). For example, the CU may configure the IAB-DU and / or IAB-MT with STC and SSB measurement time configuration (SMTC) information to facilitate SSB transmission and measurement (e.g., for inter-node discovery and interference management).

[0030] In a typical IAB network, inter-node discovery and interference management are limited to static IAB nodes (not mobile IAB nodes). For example, when mobile IAB nodes are present within the IAB network, enhanced inter-node interference measurements are required for at least one of the following: from a static IAB node to a mobile IAB node, or from one mobile IAB node to another mobile IAB node. To take appropriate action for interference management and discover other nearby nodes (e.g., static or mobile nodes), the mobile IAB node may need to know the STC configuration of neighboring nodes.

[0031] As described above, the CU typically transmits the STC configuration of neighboring nodes to the mobile IAB node and also configures an SMTC window for the mobile IAB node to measure the SSBs of neighboring nodes. However, since the mobile IAB node is constantly moving, the nodes near the mobile IAB node are constantly changing and unknown. Therefore, due to the unknown neighboring nodes, the CU may not be able to generate and transmit a complete list of nodes near the mobile IAB node and / or directly configure an SMTC window for the mobile IAB node.

[0032] However, aspects of the present disclosure provide techniques that enable a mobile IAB node to obtain the STC configurations of neighboring nodes as well as its own SMTC configuration. Thus, the mobile IAB can measure inter-node interference during the STC windows of neighboring nodes. The mobile IAB node can obtain the STC configurations of neighboring nodes via different options. The techniques presented herein can result in coordinated scheduling between different mobile nodes and static nodes (once the mobile and static nodes discover each other), which can lead to reduced inter-node interference.

[0033] Introduction to wireless communication networks

[0034] The techniques and methods described herein can be used in various wireless communication networks. Although various aspects may be described herein using terms typically associated with 3G, 4G, and / or 5G wireless technologies, various aspects of the present disclosure may also be applicable to other communication systems and standards not explicitly mentioned herein.

[0035] Figure 1 An example of a wireless communication network 100 is depicted in which various aspects described herein may be implemented.

[0036] In general, the wireless communication network 100 includes various network entities (alternatively, network elements or network nodes). A network entity is typically a communication device and / or a communication function performed by a communication device (e.g., user equipment (UE), base station (BS), a component of a BS, a server, etc.). For example, various functions of a network and various devices associated with and interacting with the network can be considered network entities. In addition, the wireless communication network 100 includes terrestrial aspects, such as ground-based network entities (e.g., BS 102), and non-terrestrial aspects, such as satellites 140 and aircraft 145. The non-terrestrial aspects may include airborne network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., ground BSs) and UEs.

[0037] In the depicted example, the wireless communication network 100 includes a BS 102, a UE 104, and one or more core networks (such as an evolved packet core (EPC) 160 and a 5G core (5GC) network 190) that interoperate to provide communication services over various communication links (including wired links and wireless links).

[0038] Figure 1 Various example UEs 104 are depicted, which may more generally include: a cellular phone, a smartphone, a Session Initiation Protocol (SIP) phone, a laptop computer, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player, a camera, a game console, a tablet computer, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, an Internet of Things (IoT) device, an always-on (AON) device, an edge processing device, or other similar devices. UE 104 may also be more generally referred to as a mobile device, a wireless device, a wireless communication device, a station, a mobile station, a subscriber station, a mobile subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, and other user equipment.

[0039] BS 102 wirelessly communicates with (e.g., transmits signals to or receives signals from) UE 104 via communication link 120. Communication link 120 between BS 102 and UE 104 may include uplink (UL) (also known as a reverse link) transmissions from UE 104 to BS 102 and / or downlink (DL) (also known as a forward link) transmissions from BS 102 to UE 104. In various aspects, communication link 120 may utilize multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity.

[0040] BS 102 may generally include: a NodeB, an enhanced NodeB (eNB), a next generation enhanced NodeB (ng-eNB), a next generation NodeB (gNB or gNodeB), an access point, a base transceiver station, a radio BS, a radio transceiver, transceiver functionality, a transmit / receive point, and / or the like. Each of BSs 102 may provide communication coverage for a corresponding geographic coverage area 110, which may sometimes be referred to as a cell and may overlap in some cases (e.g., a small cell 102' may have a coverage area 110' that overlaps with a coverage area 110 of a macro cell). For example, a BS may provide communication coverage for a macro cell (covering a relatively large geographic area), a pico cell (covering a relatively small geographic area, such as a stadium), a femto cell (covering a relatively small geographic area, such as a home), and / or other types of cells.

[0041] Although BS 102 is depicted in various aspects as a single communication device, BS 102 can be implemented in various configurations. For example, one or more components of BS 102 can be disaggregated, including a central unit (CU), one or more distributed units (DUs), one or more radio units (RUs), a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, to name a few examples. In another example, various aspects of BS 102 can be virtualized. More generally, a BS (e.g., BS 102) can include components located at a single physical location or components located at various physical locations. In examples where BS 102 includes components located at various physical locations, the various components can each perform a function such that the various components collectively achieve functionality similar to that of BS 102 located at a single physical location. In some aspects, BS 102 including components located at various physical locations can be referred to as a disaggregated radio access network (RAN) architecture, such as an open RAN (O-RAN) or virtualized RAN (VRAN) architecture. Figure 2 An example decomposed BS architecture is depicted and described.

[0042] Different BSs 102 within the wireless communication network 100 may also be configured to support different radio access technologies (such as 3G, 4G, and / or 5G). For example, a BS 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). A BS 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) may interface with the 5GC 190 via a second backhaul link 184. The BSs 102 may communicate with each other directly or indirectly (e.g., through the EPC 160 or the 5GC 190) over a third backhaul link 134 (e.g., an X2 interface), which may be wired or wireless.

[0043] The wireless communication network 100 may subdivide the electromagnetic spectrum into various categories, frequency bands, channels, or other characteristics. In some aspects, the subdivision is provided based on wavelength and frequency, where frequency may also be referred to as a carrier, subcarrier, channel, tone, or subband. For example, 3GPP currently defines Frequency Range 1 (FR1) as including 600 MHz to 6 GHz, which is often (interchangeably) referred to as "sub-6 GHz." Similarly, 3GPP currently defines Frequency Range 2 (FR2) as including 26 GHz-41 GHz, which is sometimes (interchangeably) referred to as "millimeter wave" ("mmW" or "mmWave"). A BS configured to communicate using mmWave / near mmWave radio bands (e.g., a mmWave BS, such as BS 180) may utilize beamforming (e.g., 182) with a UE (e.g., 104) to improve path loss and range.

[0044] The communication link 120 between the BS 102 and, for example, the UE 104 may be over one or more carriers, which may have different bandwidths (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, and / or other MHz) and may be aggregated in various ways. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL).

[0045] Communications using higher frequency bands may have higher path loss and shorter range than communications at lower frequencies. Figure 1180) may utilize beamforming 182 with UE 104 to improve path loss and range. For example, BS 180 and UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, BS 180 may transmit beamformed signals to UE 104 in one or more transmit directions 182′. UE 104 may receive beamformed signals from BS 180 in one or more receive directions 182″. UE 104 may also transmit beamformed signals to BS 180 in one or more transmit directions 182″. BS 180 may also receive beamformed signals from UE 104 in one or more receive directions 182′. BS 180 and UE 104 may then perform beam training to determine an optimal receive direction and an optimal transmit direction for each of BS 180 and UE 104. Notably, the transmit direction and receive direction of BS 180 may be the same or may be different. Similarly, the transmit direction and receive direction of UE 104 may or may not be the same.

[0046] Wireless communication network 100 also includes a Wi-Fi AP 150 that communicates with Wi-Fi stations (STAs) 152 via communication links 154 in, for example, the 2.4 GHz and / or 5 GHz unlicensed spectrum.

[0047] Some of the UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), and / or a physical sidelink feedback channel (PSFCH).

[0048] The EPC 160 may include various functional components, including a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and / or a packet data network (PDN) gateway 172, such as in the depicted example. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Generally speaking, the MME 162 provides bearer and connection management.

[0049] Generally speaking, user Internet Protocol (IP) packets are delivered through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation and other functions. The PDN Gateway 172 and the BM-SC 170 are connected to the IP services 176, which may include, for example, the Internet, an intranet, an IP Multimedia Subsystem (IMS), packet-switched (PS) streaming services, and / or other IP services.

[0050] BM-SC 170 can provide functionality for MBMS user service provisioning and delivery. BM-SC 170 can serve as the entry point for content providers' MBMS delivery, can be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and / or can be used to schedule MBMS delivery. MBMS Gateway 168 can be used to distribute MBMS services to BSs 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a specific service, and / or can be responsible for session management (start / stop) and collecting eMBMS-related charging information.

[0051] 5GC 190 may include various functional components, including: access and mobility management function (AMF) 192, other AMFs 193, session management function (SMF) 194, and user plane function (UPF) 195. AMF 192 may communicate with unified data management (UDM) 196.

[0052] AMF 192 is a control node that handles signaling between UE 104 and 5GC 190. AMF 192 provides, for example, Quality of Service (QoS) flow and session management.

[0053] Internet Protocol (IP) packets are passed through UPF 195, which connects to IP services 197 and provides IP address allocation for UEs and other functions for 5GC 190. IP services 197 may include, for example, the Internet, intranet, IMS, PS streaming services, and / or other IP services.

[0054] The wireless communication network 100 further includes a synchronization signal block (SSB) transmission configuration (STC) component 199, which may be configured to perform Figure 19 Operation 1900 and / or Figure 20 Operation 2000.

[0055] In various aspects, a network entity or network node may be implemented as a converged BS, a decomposed BS, a component of a BS, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, to name a few examples.

[0056] Figure 2 An example disaggregated BS 200 architecture is depicted. The disaggregated BS 200 architecture may include one or more central units (CUs) 210 that may communicate directly with a core network 220 via a backhaul link, or indirectly with the core network 220 through one or more disaggregated BS units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a service management and orchestration (SMO) framework 205, or both. The CUs 210 may communicate with one or more distributed units (DUs) 230 via corresponding midhaul links, such as an F1 interface. The DUs 230 may communicate with one or more radio units (RUs) 240 via corresponding fronthaul links. The RUs 240 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 240.

[0057] Each of the units (e.g., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO framework 205) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of these units, or an associated processor or controller that provides instructions to the communication interface of these units, may be configured to communicate with one or more of the other units via the transmission medium. For example, these units may include a wired interface configured to receive or transmit signals to one or more of the other units via the wired transmission medium. Additionally or alternatively, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive signals or transmit signals to one or more of the other units over the wireless transmission medium, or both.

[0058] In some aspects, the CU 210 may host one or more higher-layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 210. The CU 210 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP)), control plane functionality (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, the CU 210 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 210 may be implemented to communicate with the DU 230 for network control and signaling.

[0059] The DU 230 may correspond to a logical unit that includes one or more BS functions for controlling the operation of one or more RUs 240. In some aspects, the DU 230 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) based at least in part on a functional split, such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, the DU 230 may further host one or more lower PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 230 or with control functions hosted by the CU 210.

[0060] Lower layer functionality may be implemented by one or more RUs 240. In some deployments, a RU 240 controlled by a DU 230 may correspond to a logical node that hosts RF processing functionality or low PHY layer functionality (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional partitioning (such as a lower layer functional partitioning). In such an architecture, the RU 240 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, both real-time and non-real-time aspects of control and user plane communications with the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration may enable the implementation of the DU 230 and CU 210 in a cloud-based RAN architecture (such as a vRAN architecture).

[0061] The SMO framework 205 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 205 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 205 can be configured to interact with a cloud computing platform (such as Open Cloud (O-Cloud) 290) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements may include, but are not limited to, the CU 210, DU 230, RU 240, and near-RT RIC 225. In some implementations, the SMO framework 205 can communicate with hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 211) via the O1 interface. Additionally, in some implementations, the SMO framework 205 can communicate directly with one or more RUs 240 via the O1 interface. The SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of the SMO framework 205 .

[0062] The non-RT RIC 215 may be configured to include logic that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 225. The non-RT RIC 215 may be coupled to or in communication with the near-RT RIC 225 (e.g., via an A1 interface). The near-RT RIC 225 may be configured to include logic that enables near-real-time control and optimization of RAN elements and resources through data collection and actions over an interface (e.g., via an E2 interface) that connects one or more CUs 210, one or more DUs 230, or both, and the O-eNB with the near-RT RIC 225.

[0063] In some implementations, the non-RT RIC 215 may receive parameters or external enrichment information from an external server in order to generate an AI / ML model to be deployed in the near-RT RIC 225. This information may be utilized by the near-RT RIC 225 and may be received from a non-network data source or from a network function at the SMO framework 205 or the non-RT RIC 215. In some examples, the non-RT RIC 215 or the near-RT RIC 225 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 215 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions through the SMO framework 205 (such as via reconfiguration of O1) or by creating RAN management policies (such as A1 policies).

[0064] Figure 3 Aspects of an example BS 102 and UE 104 are depicted.

[0065] In general, BS 102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a to 334t (collectively 334), transceivers 332a to 332t (collectively 332) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., data source 312) and wireless reception of data (e.g., data sink 339). For example, BS 102 can transmit and receive data between BS 102 and UE 104. BS 102 includes a controller / processor 340 that can be configured to implement various functions described herein related to wireless communication.

[0066] BS 102 includes a controller / processor 340 that can be configured to perform various functions related to wireless communication. In the depicted example, the controller / processor 340 includes an STC component 341, which can represent Figure 1 The STC component 199. It is worth noting that, while depicted as one aspect of the controller / processor 340, in other implementations, the STC component 341 may additionally or alternatively be implemented in various other aspects of the BS 102.

[0067] In general, the UE 104 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a to 352r (collectively, 352), transceivers 354a to 354r (collectively, 354) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., retrieved from a data source 362) and wireless reception of data (e.g., provided to a data sink 360). The UE 104 includes a controller / processor 380 that can be configured to implement various functions described herein related to wireless communications.

[0068] UE 104 includes a controller / processor 380 that may be configured to perform various functions related to wireless communications.

[0069] Regarding example downlink transmissions, BS 102 includes a transmit processor 320 that can receive data from a data source 312 and control information from a controller / processor 340. The control information can be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical HARQ indicator channel (PHICH), a physical downlink control channel (PDCCH), a group common PDCCH (GC PDCCH), and / or other channels. In some examples, the data can be for a physical downlink shared channel (PDSCH).

[0070] The transmit processor 320 may process (e.g., encode and symbol map) data and control information to obtain data symbols and control symbols, respectively. The transmit processor 320 may also generate reference symbols (such as for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a PBCH demodulation reference signal (DMRS), and a channel state information reference signal (CSI-RS)).

[0071] The transmit (TX) multiple-input multiple-output (MIMO) processor 330 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, and / or reference symbols, as applicable, and may provide an output symbol stream to a modulator (MOD) in transceivers 332a through 332t. Each modulator in transceivers 332a through 332t may process a corresponding output symbol stream to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and frequency upconvert) the output sample stream to obtain a downlink signal. The downlink signals from the modulators in transceivers 332a through 332t may be transmitted via antennas 334a through 334t, respectively.

[0072] To receive downlink transmissions, UE 104 includes antennas 352a through 352r that can receive downlink signals from BS 102 and provide received signals to demodulators (DEMODs) in transceivers 354a through 354r, respectively. Each demodulator in transceivers 354a through 354r can condition (e.g., filter, amplify, downconvert, and digitize) a corresponding received signal to obtain input samples. Each demodulator can further process the input samples to obtain received symbols.

[0073] A MIMO detector 356 may obtain received symbols from all demodulators in transceivers 354a through 354r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 358 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 104 to a data sink 360, and provide decoded control information to a controller / processor 380.

[0074] With respect to example uplink transmissions, the UE 104 also includes a transmit processor 364 that can receive and process data from a data source 362 (e.g., for a PUSCH) and control information from a controller / processor 380 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 364 can also generate reference symbols for reference signals (e.g., for a sounding reference signal (SRS)). The symbols from the transmit processor 364 can be pre-decoded by a TX MIMO processor 366, if applicable, further processed by modulators in transceivers 354a through 354r (e.g., for SC-FDM), and transmitted to the BS 102.

[0075] At BS 102, uplink signals from UE 104 may be received by antennas 334 a through 334 t, processed by demodulators in transceivers 332 a through 332 t, detected by MIMO detector 336 if applicable, and further processed by a receive processor 338 to obtain decoded data and decoded control information transmitted by UE 104. Receive processor 338 may provide the decoded data to a data sink 339 and the decoded control information to a controller / processor 340.

[0076] Memories 342 and 382 may store data and program codes for BS 102 and UE 104, respectively.

[0077] The scheduler 344 may schedule UEs to transmit data on the downlink and / or uplink.

[0078] In various aspects, the BS 102 may be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" may refer to various mechanisms for outputting data, such as from the data source 312, the scheduler 344, the memory 342, the transmit processor 320, the controller / processor 340, the TX MIMO processor 330, the transceivers 332a to 332t, the antennas 334a to 334t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as from the antennas 334a to 334t, the transceivers 332a to 332t, the RX MIMO detector 336, the controller / processor 340, the receive processor 338, the scheduler 344, the memory 342, and / or other aspects described herein.

[0079] In various aspects, the UE 104 may also be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" may refer to various mechanisms for outputting data, such as from a data source 362, memory 382, ​​transmit processor 364, controller / processor 380, TX MIMO processor 366, transceivers 354a to 354t, antennas 352a to 352t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as from antennas 352a to 352t, transceivers 354a to 354t, RX MIMO detector 356, controller / processor 380, receive processor 358, memory 382, ​​and / or other aspects described herein.

[0080] In some aspects, the processor may be configured to perform various operations (such as those associated with the methods described herein) and respectively send (output) data to another interface configured to send data or receive (obtain) data from another interface configured to receive data.

[0081] Figure 4A 、 Figure 4B 、 Figure 4C and Figure 4D Describes a method for use in wireless communication networks such as Figure 1 Various aspects of the data structure of the wireless communication network 100).

[0082] Specifically, Figure 4A is a diagram 400 illustrating an example of a first subframe within a 5G (e.g., 5G NR) frame structure, Figure 4B is a diagram 430 illustrating an example of a DL channel within a 5G subframe, Figure 4C is a diagram 450 illustrating an example of a second subframe within a 5G frame structure, and Figure 4DFIG480 is a diagram illustrating an example of UL channels within a 5G subframe.

[0083] Wireless communication systems can utilize Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP) on both the uplink and downlink. Such systems can also support half-duplex operation using Time Division Duplex (TDD). OFDM and Single Carrier Frequency Division Multiplexing (SC-FDM) can be used to maximize the system bandwidth (e.g., Figure 4B and Figure 4D ) is divided into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. Modulation symbols can be transmitted in the frequency domain using OFDM and / or in the time domain using SC-FDM.

[0084] The wireless communication frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers, subframes within the subcarrier set are dedicated to either DL or UL. The wireless communication frame structure may also be time division duplex (TDD), where for a particular set of subcarriers, subframes within the subcarrier set are dedicated to both DL and UL.

[0085] exist Figure 4A and Figure 4C In the embodiment of the present invention, the wireless communication frame structure is TDD, where D is DL, U is UL, and X can be flexibly used between DL / UL. The UE can be configured with a time slot format (dynamically configured through DL control information (DCI) or semi-statically / statically configured through radio resource control (RRC) signaling) through a received time slot format indicator (SFI). In the depicted example, the 10ms frame is divided into 10 equally sized 1ms subframes. Each subframe may include one or more time slots. In some examples, each time slot may include 7 or 14 symbols, depending on the time slot format. The subframe may also include micro slots, which typically have fewer symbols than a full time slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0086] In certain aspects, the number of slots within a subframe is based on the slot configuration and parameter set. For example, for slot configuration 0, different parameter sets (μ) 0 through 5 allow for 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different parameter sets 0 through 2 allow for 2, 4, and 8 slots per subframe, respectively. Thus, for slot configuration 0 and parameter set μ, there are 14 symbols per slot and 2μ slots per subframe. The subcarrier spacing and symbol length / duration are a function of the parameter set. The subcarrier spacing may be equal to 2 μ × 15kHz, where μ is parameter set 0 to 5. Thus, parameter set μ=0 has a subcarrier spacing of 15kHz, and parameter set μ=5 has a subcarrier spacing of 480kHz. Symbol length / duration is inversely related to subcarrier spacing. Figure 4A、 Figure 4B 、 Figure 4C and Figure 4D An example is provided for slot configuration 0 with 14 symbols per slot and parameter set μ = 2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0087] like Figure 4A 、 Figure 4B 、 Figure 4C and Figure 4D As depicted in FIG, a resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also called a physical RB (PRB)) extending over, for example, 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0088] like Figure 4A As illustrated, some of the REs carry data for UEs (e.g., Figure 1 and Figure 3 The RS may include a demodulation RS (DMRS) and / or a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beamforming RS (BRS), a beam refinement RS (BRRS), and / or a phase tracking RS (PT-RS).

[0089] Figure 4B Examples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs), each CCE comprising, for example, nine RE Groups (REGs), each REG comprising, for example, four consecutive REs in an OFDM symbol.

[0090] The Primary Synchronization Signal (PSS) may be in symbol 2 of a particular subframe of a frame. The PSS is transmitted by a UE (e.g., Figure 1 and Figure 3 104) is used to determine subframe / symbol timing and physical layer identification.

[0091] A Secondary Synchronization Signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing.

[0092] Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DMRS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as the system information block (SIB)), and / or paging messages.

[0093] like Figure 4C As illustrated, some of the REs carry DMRS for channel estimation at the BS (indicated as R for a specific configuration, but other DMRS configurations are possible). The UE may transmit DMRS for PUCCH and DMRS for PUSCH. The PUSCH DMRS may be transmitted, for example, in the first one or two symbols of the PUSCH. The PUCCH DMRS may be transmitted in different configurations depending on whether a short PUCCH or a long PUCCH is transmitted and depending on the specific PUCCH format used. The UE 104 may transmit a sounding reference signal (SRS). The SRS may be transmitted, for example, in the last symbol of a subframe. The SRS may have a comb structure, and the UE may transmit the SRS on one of the teeth of the comb. The SRS may be used by the BS for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0094] Figure 4D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at the position indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

[0095] Example Integrated Access and Backhaul (IAB) Network

[0096] An integrated access and backhaul (IAB) network supports multi-hop networks or multi-hop wireless backhaul. Additionally or alternatively, each node in the IAB network uses the same radio access technology (e.g., 5G / NR). Additionally or alternatively, the nodes of the IAB network can share resources for access links and backhaul links, such as time resources, frequency resources, and space resources. Furthermore, various architectures of IAB nodes or IAB donors can be supported.

[0097] In some cases, the IAB donor includes a central unit (CU) that configures IAB nodes that access a core network via the IAB donor and a distributed unit (DU) that schedules and communicates with child nodes of the IAB donor.

[0098] In some cases, an IAB node includes a mobile terminal component (MT) that is scheduled by and communicates with the DU of the parent node, and a DU that schedules and communicates with the child nodes of the IAB node. The DU of the IAB node performs the functions described in conjunction with the network entity of the IAB node, and the MT of the IAB node performs the functions described in conjunction with the UE of the IAB node.

[0099] Figure 5 is a diagram illustrating an example IAB network architecture. As shown, the IAB network includes an IAB donor connected to a core network via a wired connection (e.g., as a wired optical fiber). In some aspects, the Ng interface of the IAB donor terminates at the core network. Additionally or alternatively, the IAB donor is connected to one or more devices of the core network that provide a core access and mobility management function (AMF). In some cases, the IAB donor includes a network entity (such as an anchor base station) and / or a network controller. As shown, the IAB donor includes a CU that can perform ANC functions or AMF functions. The CU can configure the DU of the IAB donor or can configure one or more IAB nodes (e.g., MTs or DUs of IAB nodes) connected to the core network via the IAB donor. In some cases, the CU of the IAB donor can control or configure the entire IAB network connected to the core network via the IAB donor, such as by using control messages or configuration messages (e.g., radio resource control (RRC) configuration messages, medium access control (MAC) control elements, or F1 application protocol (F1 AP) messages).

[0100] The IAB network also includes IAB nodes (e.g., IAB nodes 1 to 4) connected to the core network via an IAB donor. As shown in the figure, the IAB node may include an MT and a DU. The MT of an IAB node (e.g., a child node) may be controlled or scheduled by another IAB node (e.g., a parent node) or by an IAB donor. The DU of an IAB node (e.g., a parent node) may control or schedule other IAB nodes (e.g., child nodes of the parent node) or UEs. Therefore, the DU may be referred to as a scheduling node or scheduling component, and the MT may be referred to as a scheduled node or scheduled component. In some cases, the IAB donor includes the DU but not the MT. That is, the IAB donor may configure, control, or schedule communications of the IAB node or UE. The UE includes only the MT but not the DU. That is, communications of the UE may be controlled or scheduled by the IAB donor or the IAB node (e.g., the parent node of the UE).

[0101] In some cases, certain nodes are configured to participate in the control / scheduling process. For example, when a first node controls or schedules communications for a second node (e.g., when the first node provides DU functionality for the mobile equipment of the second node), the first node may be referred to as the parent node of the second node, and the second node may be referred to as the child node of the first node. The child node of the second node may be referred to as the grandchild node of the first node. Thus, the DU of the parent node may control or schedule communications for the child node of the parent node. The parent node may be an IAB donor or an IAB node, and the child node may be an IAB node or a UE. Communications for the mobile equipment of the child node may be controlled or scheduled by the parent node of the child node.

[0102] like Figure 5 As further shown in , the link between the UE and the IAB donor or between the UE and the IAB node is called an access link. Each access link is a wireless access link that provides the UE with radio access to the core network via the IAB donor and potentially via one or more IAB nodes.

[0103] like Figure 5 As further shown in FIG, a link between an IAB donor and an IAB node or between two IAB nodes is referred to as a backhaul link. Each backhaul link is a wireless backhaul link that provides radio access to the core network to the IAB node via the IAB donor and potentially via one or more other intervening IAB nodes. In some cases, the backhaul link is a primary backhaul link or a secondary backhaul link (e.g., a backup backhaul link). In some cases, if the primary backhaul link fails, becomes congested, or becomes overloaded, the secondary backhaul link is used. In an IAB network, network resources (e.g., time resources, frequency resources, spatial resources) used for wireless communications can be shared between the access link and the backhaul link.

[0104] As described above, in an IAB network, IAB nodes (e.g., non-anchor base stations) are stationary (i.e., they do not move). In contrast, in a mobile IAB network, some IAB nodes may have mobility (i.e., they may move around in the IAB network). Such IAB nodes may be referred to as mobile IAB nodes. For example, an IAB node may be installed on a vehicle (e.g., a bus, train, or car). In a mobile IAB network, there may be a mix of stationary IAB nodes and mobile IAB nodes. In some cases, a mobile IAB node may be restricted to being a "leaf" node in the mobile IAB network. That is, a mobile IAB node is only permitted to serve as a last-hop IAB node, and only child access UEs are connected to the mobile IAB node. In some cases, a mobile IAB node may be permitted to have another IAB node as a child node.

[0105] In some cases, a mobile IAB node can provide an independently moving cell site. In such cases, a moving cell site (e.g., a vehicle (such as a bus, train, or car)) can be used by the IAB node to serve surrounding UEs (e.g., within an urban area). Here, the mobile IAB node can move relatively randomly at relatively low speeds (e.g., city speeds) and over relatively large distances. In this case, the mobility of a given UE (not carried on a vehicle) is independent of the mobility of the IAB node (i.e., the movement of the UE cannot be predicted based on the movement of the mobile IAB node), but can also be at relatively low speeds (similar to the speed of the mobile IAB node).

[0106] In some cases, a mobile IAB node can be provided in conjunction with a moving cell site (e.g., a high-speed train). In such a case, the mobile IAB node can be installed on a moving cell site (e.g., installed on top of a high-speed train) to serve UEs on or in the moving cell site (e.g., UEs inside the high-speed train). Here, the mobility of the mobile IAB node can be predictable at relatively high speeds and over large distances. In this use case, the UE on or in the moving cell site moves in conjunction with the mobile IAB node (i.e., the UE movement can be predicted based on the movement of the mobile IAB node).

[0107] In some cases, such as when a loose group of UEs moves roughly together, the mobile IAB node can facilitate a platoon. In such cases, a single IAB node can provide network connectivity for nearby UEs. For example, a mobile IAB node installed on a first vehicle traveling on a highway can provide network connectivity for UEs in the first vehicle and UEs in other vehicles traveling in the same direction and at a similar speed on the highway. In such cases, the mobile IAB node is connected to the network, while the other vehicles can house corresponding child nodes. Here, the mobile IAB node moves at a relatively constant speed and with local predictability over a relatively large distance. In addition, these UEs move in conjunction with the mobile IAB node.

[0108] The mobility state of a communication device or node (e.g., an IAB node) can be defined by several characteristics. In general, the mobility state may refer to the node's mobility category, degree of mobility, and / or mobility capability. The mobility state of a component can be static (e.g., unchanged) or dynamic (e.g., changing over time). The mobility state may depend on other factors, such that it indicates a relative state relative to other network components. The mobility state may be based on one or more characteristics as needed or according to design / operating principles. The first characteristic is the level of mobility (e.g., stationary, low-speed mobility, medium-speed mobility, high-speed mobility). The mobility level may generally reflect a point-in-time speed, a speed range, a running average historical mobility / speed pattern, or some other representation of general mobility capability. The second characteristic is the change or transition from one mobility state to another (e.g., the mobility state of an IAB node may change or transition over time). For example, a mobile IAB node may transition to stationary (e.g., from low mobility), or may transition from one mobility class to another (e.g., from medium mobility to high mobility). In some instances, there may be a timer associated with such transitions (e.g., the IAB node may transition from one state to another within a specified time window). Mobility state characteristics may generally be shared by or between devices for enhanced network operation (e.g., using a variety of signals / messages on various interfaces).

[0109] Example Full-Duplex (FD) Use Case

[0110] The technology presented herein involves obtaining the synchronization signal block (SSB) transmission configuration (STC) of a neighboring node by a mobile node in a full-duplex (FD) and / or half-duplex (HD) system. FD allows simultaneous transmission between nodes (e.g., user equipment (UE) and / or network entities). In an HD system, communication flows in one direction at a time.

[0111] The technology presented herein can be applied in various frequency bands used for New Radio (NR). For example, for the higher frequency bands known as frequency range (FR) 4 (e.g., 52.6 GHz-114.25 GHz), an orthogonal frequency division multiplexing (OFDM) waveform with a very large subcarrier spacing (SCS; 960 kHz-3.84 MHz) is required to combat severe phase noise. Due to the large SCS, the slot length tends to be very short. In the lower frequency band known as FR2 (24.25 GHz to 52.6 GHz) with an SCS of 120 kHz, the slot length is 125 μSec, while in FR4 with 960 kHz, the slot length is 15.6 μSec. In some cases, a frequency band known as FR2x may be used.

[0112] There are various motivations for utilizing FD communications, such as enabling simultaneous uplink / downlink transmission in FR2. In some cases, FD capabilities may enable flexible time division duplex (TDD) capabilities and may be present at the network entity, the UE, or both. For example, at the UE, uplink transmissions may be transmitted from one antenna panel, and downlink receptions may be performed at another antenna panel. In another example, at a gNodeB (gNB), uplink transmissions may be from one panel, and downlink receptions may be performed at another panel.

[0113] FD capability may depend on beam separation (e.g., self-interference between downlink and uplink, clutter echo, etc.). FD capability may mean that the UE or gNB is able to use frequency division multiplexing (FDM) or spatial division multiplexing (SDM) on timeslots that are conventionally reserved for uplink-only or downlink-only timeslots (or flexible timeslots that can be dynamically indicated as uplink or downlink).

[0114] Potential benefits of FD communications include reduced latency (e.g., it is possible to receive downlink signals in what are conventionally considered uplink-only time slots, which can achieve latency savings), coverage enhancement, spectral efficiency enhancement (per cell and / or per UE), and / or overall more efficient resource utilization.

[0115] Figure 6 、 Figure 7 and Figure 8 An example use case for FD communication is illustrated. Figure 9 Some possible characteristics of these use cases are summarized.

[0116] like Figure 6 As illustrated, for a first use case (e.g., use case 1), a UE transmits on the uplink to a second transmitter receiver point (TRP) while simultaneously communicating on the downlink with a first TRP 1. For this use case, FD is disabled at the gNB (i.e., TRP) and enabled at the UE.

[0117] like Figure 7 As illustrated, for the second use case (e.g., Use Case 2), a gNB communicates with a second UE (UE2) on the uplink while simultaneously communicating with a first UE (UE 1) on the downlink. For this use case, FD is enabled at the gNB and disabled at the UE. The use case where FD is enabled at the gNB and disabled at the UE may also be suitable for integrated access and backhaul (IAB) applications (e.g., Figure 9 as shown in the table).

[0118] like Figure 8As illustrated, for the third use case (e.g., Use Case 3), the UE communicates with the gNB simultaneously, transmitting on the uplink while receiving on the downlink. For this use case, FD is enabled at both the gNB and the UE.

[0119] like Figure 10 In the example, FD is enabled at the gNB and disabled at the UE. For example, a first gNB is communicating with one UE on the uplink while simultaneously communicating with another UE on the downlink. Similarly, a second gNB is communicating with one UE on the uplink while simultaneously communicating with another UE on the downlink. The implementation of FD communication / TDD systems can present challenges in some situations. One such challenge is cross-link interference (CLI), which occurs when one gNB (e.g., the first gNB) is transmitting while another gNB (e.g., the second gNB) is receiving in the same frequency band. gNBs typically transmit at higher power and have better propagation conditions between them, i.e., lower path loss between gNBs compared to the link between the gNB and the UE. Therefore, when a gNB in ​​the uplink experiences downlink interference from another gNB, CLI can be significant. This can then result in reduced throughput. In this case, CLI can also occur between UEs when one UE is transmitting and another is receiving in the same frequency band.

[0120] like Figure 11 As illustrated, FD is enabled at both the gNB and the UE. For example, a first gNB is communicating with a second UE on the downlink while simultaneously communicating with the first UE on the downlink and uplink. In this case, CLI may exist between gNBs when one gNB is transmitting and another gNB is receiving in the same frequency band. In this case, CLI may also exist between UEs (e.g., from the first UE to the second UE) when one UE is transmitting and another UE is receiving in the same frequency band.

[0121] like Figure 12As illustrated, HD is enabled at the gNB and FD is enabled at the UE. For example, a first gNB communicates with a first UE on the uplink, and a second gNB communicates with the first and second UEs on the downlink. The first UE communicates with the second gNB on the downlink while simultaneously communicating with the first gNB on the uplink. In this case, CLI may exist between gNBs (e.g., from the second gNB to the first gNB) when one gNB is transmitting and the other gNB is receiving in the same frequency band. In this case, CLI may also exist between UEs (e.g., from the first UE to the second UE) when one UE is transmitting and the other UE is receiving in the same frequency band.

[0122] like Figure 13 In the illustrated example, a parent node (e.g., an IAB donor node) is associated with two child nodes (e.g., IAB nodes). The IAB nodes may be network entities. Both IAB nodes are FD-enabled. For example, each IAB node is communicating with one UE on the uplink while simultaneously communicating with another UE on the downlink. In this case, when one IAB node is transmitting and the other IAB node is receiving in the same frequency band, CLI may exist between the IAB nodes.

[0123] Example static Integrated Access and Backhaul (IAB) node

[0124] Figure 14A Depicted are example communications between an integrated access and backhaul (IAB) donor node, an IAB node, and user equipment (UE). The IAB donor node may be a static node and include IAB donor A and IAB donor B. The IAB node may be a static node and include IAB donor A and IAB donor B. The UE includes UE A and UE B.

[0125] The IAB donor (e.g., IAB donor A, IAB donor B) includes a central unit (CU) that configures the IAB donor and / or a distributed unit (DU) (e.g., a mobile terminal module (MT) or a DU of an IAB node) of the IAB node connected to the core network via the IAB donor. Figure 14B As illustrated, the CU of the IAB donor can configure the synchronization signal block (SSB) transmission configuration (STC) and SSB measurement time configuration (SMTC) in time division multiplexing (TDM) at the IAB-DU and / or IAB-MT, respectively, for half-duplex (HD) constraints to facilitate the transmission and measurement of SSBs (e.g., for inter-node discovery and interference management).

[0126] like Figure 14BAs further illustrated, the STC configuration may include various parameters such as an SSB center frequency, an SSB subcarrier spacing, an SSB transmission periodicity (e.g., the periodicity of transmission of one or more SSBs), an SSB transmission timing offset (e.g., a starting point of an SSB transmission periodicity in time slots), an index of an SSB to be transmitted (e.g., at least one index associated with one or more SSBs to be transmitted), or any combination thereof. In some cases, multiple STCs may be configured for an IAB node. The STC configuration may be specific to a cell or frequency location per DU.

[0127] like Figure 14B As further illustrated, the SMTC configuration may include various parameters, such as an SSB center frequency (e.g., a center frequency associated with the transmission of one or more SSBs), an SSB subcarrier spacing (e.g., an SSB subcarrier spacing associated with the transmission of one or more SSBs), an SMTC window periodicity (e.g., measurements occurring at each period T corresponding to the SMTC window periodicity), an SMTC window timing offset (e.g., a timing offset relative to a reference time point), an SMTC window duration (e.g., the duration of the window during which measurements are performed), a list of one or more physical cell IDs to be measured, a list of one or more SSBs to be measured, or any combination thereof.

[0128] In some cases, the CU of the IAB donor may configure an STC configuration for a neighboring IAB-MT at the IAB-DU and / or IAB-donor-DU (e.g., both are static nodes) to measure the SSB from the IAB-DU and / or IAB-donor-DU. The maximum number of STC configurations configured for the IAB-DU and / or IAB-donor-DU is five. In one example, the five STC configurations may include one STC configuration for the access link and four STC configurations for the backhaul link. STC information (e.g., STC configuration) is transmitted by the CU of the IAB donor to the IAB-DU and / or IAB-donor-DU via the F1 interface (e.g., IAB information IAB-donor-CU->IAB STC information). The used STC information may also be transmitted by the IAB-DU and / or IAB-donor-DU to the CU of the IAB donor (e.g., F1 setup request->serving cell information->IAB information IAB-DU->IAB STC information).

[0129] The inter-node discovery and interference management based on STC and SMTC configurations described above are for static IAB nodes (not mobile IAB nodes). For example, when a mobile IAB node (or gNodeB (gNB)) exists within an IAB network, enhanced inter-gNB interference measurements are required for at least one of: from a static IAB node / gNB to a mobile IAB node, or from a mobile IAB node to another mobile IAB node. To take appropriate measures for interference management and discover other nearby nodes (e.g., static or mobile nodes), the mobile IAB node requires the STC configuration of neighboring gNBs (e.g., static or mobile gNBs).

[0130] Typically, the IAB donor's CU may transmit a list of STC configurations of neighboring gNBs to the mobile IAB node. The IAB donor's CU may also initially configure an SMTC window for the mobile IAB node to measure the SSBs of neighboring gNBs. However, when the mobile IAB node moves away from the neighboring gNBs, the mobile IAB node may not be able to find the SSBs of any current neighboring gNBs because the neighboring gNBs may have changed. In such a situation, the mobile IAB node may interfere with / stop its own access link SSB transmission during its own access link STC window. The mobile IAB node may then switch to using its MT function to listen to other neighboring gNB access link SSBs to search for any new candidate neighboring gNBs. The mobile IAB node may use its MT function to find the new neighboring gNB. After finding the new neighboring gNB using its MT function, the mobile IAB node may need to obtain the STC configuration of the new neighboring gNB (e.g., via the different options mentioned below). After obtaining the STC configuration of the new neighboring gNB, the mobile IAB node can self-configure and update its new SMTC window to listen to / measure the STC window of the new neighboring gNB and report the new neighboring gNB to the CU of the IAB donor node. Based on this report, the CU of the IAB donor node can reconfigure the STC and SMTC configuration of the mobile IAB node to transmit and receive from the new neighboring gNB. The mobile IAB node can then switch back to its DU functionality and begin sending SSBs for the access link again. Therefore, obtaining the STC configuration of the new neighboring gNB helps the mobile IAB node recover and reconnect with the new neighboring gNB.

[0131] As described above, although the IAB donor's CU transmits a list of STC configurations of neighboring gNBs to the mobile IAB node, since the mobile IAB node is moving around, the gNBs near the mobile IAB node are changing and are unknown. Therefore, due to the unknown neighboring gNBs of the mobile IAB node, the IAB donor's CU cannot generate a complete list of nearby gNBs and transmit it to the mobile IAB node (e.g., also due to the large overhead) and / or directly configure the SMTC window for the mobile IAB node. Therefore, a technique is needed for the mobile IAB node to obtain the STC configurations of neighboring gNBs as well as its own SMTC configuration so that the mobile IAB can measure inter-gNB interference during the STC windows of its neighboring gNBs.

[0132] Technical aspects related to mobile IAB / gNB obtaining neighboring STC configurations

[0133] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for obtaining a synchronization signal block (SSB) transmission configuration (STC) of a network entity.

[0134] For example, the techniques presented herein enable a mobile network entity to obtain the STC configuration of a neighboring network entity, enabling the mobile network entity to measure inter-network entity interference during the neighboring network entity's STC window. The mobile network entity may obtain the STC configuration of a neighboring network entity via one or more options. In one option, the neighboring network entity may broadcast its own STC configuration to the mobile network entity. In another option, the mobile network entity may transmit a request to the neighboring network entity for the neighboring network entity's STC configuration.

[0135] The proposed technique may result in coordinated scheduling between different mobile network entities and static network entities (once the mobile network entities and the static network entities discover each other), which will result in reduced inter-network entity interference. Figure 15 、 Figure 16 、 Figure 17 、 Figure 18 、 Figure 19 and Figure 20 The technology proposed in this article can be understood.

[0136] like Figure 15 As illustrated, at 1502, a first network entity (e.g., such as Figure 1 The first network entity may receive an STC configuration of the second network entity from a second network entity (e.g., a gNodeB (gNB) or BS 102) in the wireless communication network 100. For example, the first network entity may receive broadcast signaling (e.g., remaining minimum system information (RMSI)) from the second network entity that carries the STC configuration of the second network entity.

[0137] In one example, the first network entity is a mobile integrated access and backhaul (IAB) node (e.g., Figure 18 In another example, the first network entity is a static IAB node. In one example, the second network entity is a mobile IAB node. In another example, the second network entity is a static IAB node.

[0138] At 1504, the second network entity sends one or more SSBs to the first network entity.

[0139] At 1506 , the first network entity measures one or more SSBs from the second network entity according to the received STC configuration of the second network entity.

[0140] like Figure 16 As illustrated, at 1602, a first network entity receives an indication from a second network entity, e.g., via one or more bits (other than an STC configuration). For example, the first network entity receives broadcast signaling (e.g., RMSI) from the second network entity carrying the indication that the second network entity has an STC configuration. In certain aspects, some network entities may not have an STC configuration, however, some network entities (e.g., acting as a parent node or as an IAB distributed unit (DU) connected to a child node) may have an STC configuration.

[0141] At 1604, the first network entity sends a request for STC configuration of the second network entity to the second network entity (e.g., an on-demand request). In one example, in response to the received indication, the first network entity may transmit random access channel (RACH) signaling carrying the request for STC configuration of the second network entity to the second network entity (e.g., in idle mode). In another example, in response to the received indication, the first network entity may transmit a scheduling request (SR) to the second network entity, the scheduling request (SR) indicating the request for STC configuration of the second network entity. In another example, in response to the received indication, the first network entity may transmit Uu signaling with mobile terminal component (MT) / UE functionality to the second network entity (e.g., in connected mode) carrying the request for STC configuration of the second network entity.

[0142] In certain aspects, the request may also include a request to send an aperiodic cross-link interference (CLI) reference signal (RS) to the first network entity. For example, the first network entity may request the second network entity to transmit an aperiodic inter-gNB CLI RS for additional measurements (e.g., for refining beam measurements). In one example, if SSB1 of gNB 1 and SSB5 of gNB 2 are measured with low inter-gNB CLI, the first network entity may further request a P2 procedure for measuring coexisting narrow beams that are quasi-co-located (QCLed) with wide SSB beams.

[0143] In certain aspects, the request may also include a request to change the periodicity of sending the CLI RS to the first network entity. For example, the first network entity may request a change in the inter-gNB measurement RS periodicity due to a change in speed of the first network entity and / or the second network entity.

[0144] In certain aspects, the request may also include a request to switch from the current IAB donor node to the new IAB donor node. For example, if the first network entity needs to switch the current IAB donor node due to mobility of the first network entity, the first network entity may transmit a request to switch from the current IAB donor node to the new IAB donor node.

[0145] At 1606 , in response to the request, the first network entity receives an STC configuration of the second network entity from the second network entity.

[0146] At 1608, the second network entity sends one or more SSBs to the first network entity.

[0147] At 1610 , the first network entity measures one or more SSBs from the second network entity according to the received STC configuration of the second network entity.

[0148] like Figure 17 As illustrated, the first network entity receives the indication from the second network entity at 1702. As described above, the indication indicates that the second network entity has an STC configuration.

[0149] At 1704, the first network entity sends a request for the STC configuration of the second network entity to the node (instead of transmitting it to the second network entity). The request may also include identification (ID) information of the second network entity.

[0150] In certain aspects, the request further comprises a request to receive an aperiodic CLI RS from the second network entity. In certain aspects, the request further comprises a request to change a periodicity of transmission of the CLI RS from the second network entity.

[0151] In one example, the node is a central unit (CU) of an IAB donor node. In another example, the node is an operations administration and management (OAM) node.

[0152] At 1706, the first network entity receives an STC configuration of the second network entity from the node.

[0153] In certain aspects, a first network entity may receive sidelink signaling from a second network entity that carries an STC configuration of the second network entity. For example, if both the first network entity and the second network entity have sidelink functionality / capability, the second network entity (e.g., a neighboring gNB with sidelink capability) may broadcast the STC configuration of the second network entity to the first network entity via sidelink signaling (e.g., discovery signaling).

[0154] In certain aspects, when both the first network entity and the second network entity have sidelink capabilities, the first network entity may first send sidelink signaling to the second network entity, including a request for STC configuration. In response to the request, the first network entity may receive sidelink signaling from the second network entity, including the STC configuration of the second network entity. In certain aspects, the request also includes a request to send an aperiodic CLI RS to the first network entity. In certain aspects, the request also includes a request to change the periodicity of sending the CLI RS to the first network entity. In certain aspects, the request also includes a request to switch from a current IAB donor node to a new IAB donor node.

[0155] In certain aspects, the first network entity may receive signaling from the node configuring an SSB Measurement Time Configuration (SMTC). The SMTC configuration may include one or more parameters indicating an SMTC window for the first network entity. The first network entity may measure one or more SSBs from the second network entity during the SMTC window. For example, the CU configures the SMTC window for the first network entity to measure the STC window of the second network entity.

[0156] In certain aspects, a first network entity may detect a number of SSBs from a second network entity. When at least one detected SSB is above a threshold, the first network entity may configure an SMTC configuration. The SMTC configuration includes one or more parameters indicating an SMTC window for the first network entity. The SMTC window is aligned with the STC window of the second network entity to measure one or more SSBs from the second network entity. For example, if the first network entity detects an SSB from the second network entity that is greater than a threshold, the first network entity may self-configure the SMTC window to directly measure the STC window of the second network entity without the delay of waiting for a CU.

[0157] In certain aspects, to configure the SMTC configuration, the first network entity may update the current SMTC window to the new SMTC window.

[0158] In certain aspects, a first network entity may perform beam measurements based on a CLI RS received from a second network entity. The first network entity may send a report to the second network entity or node indicating the beam measurements to coordinate scheduling (e.g., to avoid high inter-gNB interference transmission / reception).

[0159] Figure 19 Example operations 1900 for wireless communication are illustrated. Operations 1900 may be performed, for example, by a first network entity (e.g., such as Figure 1 Operation 1900 may be implemented as a process in one or more processors (e.g., Figure 3 Furthermore, the signal transmission and reception performed by the first network entity in operation 1900 may be performed by one or more antennas (e.g., Figure 3 In some aspects, the signal transmission and / or reception by the first network entity may be implemented by obtaining and / or outputting signals via a bus interface of one or more processors (e.g., controller / processor 340).

[0160] Operations 1900 begin at 1902, where an STC configuration of a second network entity is obtained. For example, the network entity may use Figure 1 or Figure 3 The antenna and / or transmitter / transceiver components of the BS 102 shown and / or Figure 21 The antenna and / or transmitter / transceiver components of the apparatus shown are used to obtain the STC configuration of the second network entity.

[0161] At 1904, the first network entity measures one or more SSBs sent from the second network entity according to the STC configuration. For example, the network entity may use Figure 1 or Figure 3 The antenna and / or receiver / transceiver components of the BS 102 shown and / or Figure 21 The apparatus shown includes an antenna and / or receiver / transceiver assembly for measuring one or more SSBs.

[0162] It should be noted that Figure 19 This is merely one example of one method, and other methods are possible that are consistent with the present disclosure and that include fewer, additional, or alternative steps.

[0163] Figure 20 Example operations 2000 for wireless communication are illustrated. Operations 2000 may be performed, for example, by a node (e.g., such as Figure 1 Operation 2000 may be performed by one or more processors (e.g., Figure 3 Furthermore, the signal transmission and reception by the node in operation 2000 may be performed by, for example, one or more antennas (e.g., Figure 3In some aspects, the transmission and / or reception of signals by a node may be achieved by obtaining and / or outputting signals via a bus interface of one or more processors (e.g., controller / processor 340).

[0164] Operations 2000 begin at 2002, where signaling is received from a first network entity carrying a request for STC configuration of a second network entity. For example, a node may use Figure 1 or Figure 3 The antenna and / or receiver / transceiver components of the BS 102 shown and / or Figure 22 The antenna and / or receiver / transceiver components of the apparatus are shown to receive signaling carrying a request for STC configuration.

[0165] At 2004, in response to the request, the node sends signaling carrying the STC configuration of the second network entity to the first network entity. For example, the node may use Figure 1 or Figure 3 The antenna and / or transmitter / transceiver components of the BS 102 shown and / or Figure 22 The antenna and / or transmitter / transceiver components of the device are shown to send signaling carrying STC configuration.

[0166] It should be noted that Figure 20 This is merely one example of one method, and other methods are possible that are consistent with the present disclosure and that include fewer, additional, or alternative steps.

[0167] Example Communication Device

[0168] Figure 21 Depicted are aspects of an example communication device 2100. In some aspects, the communication device 2100 is a first network entity, such as described above with respect to Figure 1 and Figure 3 BS102 as described.

[0169] The communication device 2100 includes a processing system 2102 coupled to a transceiver 2108 (e.g., a transmitter and / or receiver) and / or a network interface. The transceiver 2108 is configured to transmit and receive signals for the communication device 2100 via an antenna 2110, such as the various signals described herein. The network interface 2112 is configured to receive signals via a communication link (e.g., such as those described herein). Figure 2 The backhaul link, midhaul link, and / or fronthaul link) may be used to obtain and transmit signals of the communication device 2100. The processing system 2102 may be configured to perform processing functions of the communication device 2100, including processing signals received and / or to be transmitted by the communication device 2100.

[0170] The processing system 2102 includes one or more processors 2120. In various aspects, the one or more processors 2120 may represent one or more of the receive processor 338, the transmit processor 320, the TX MIMO processor 330, and / or the controller / processor 340, as described with respect to FIG. Figure 3 The one or more processors 2120 are coupled to the computer readable medium / memory 2130 via the bus 2106. In some aspects, the computer readable medium / memory 2130 is configured to store instructions (e.g., computer executable code) that, when executed by the one or more processors 2120, cause the one or more processors 2120 to perform operations related to the computer readable medium / memory 2130. Figure 19 The described operations 1900 or any aspects related to these operations. It should be noted that reference to a processor of the communication device 2100 performing a function may include one or more processors of the communication device 2100 performing that function.

[0171] In the depicted example, the computer-readable medium / memory 2130 stores: code (e.g., executable instructions) for obtaining 2131, which includes code for obtaining the STC configuration of the second network entity; and code for measuring 2132, which includes code for measuring one or more SSBs sent from the second network entity according to the STC configuration. Processing of the codes 2131-2132 may cause the communication device 2100 to perform operations related to Figure 19 The operations 1900 or any aspect related thereto.

[0172] The one or more processors 2120 include circuits configured to implement (e.g., execute) code stored in the computer-readable medium / memory 2130, including: circuitry for obtaining 2121, which includes circuitry for obtaining the STC configuration of the second network entity; and circuitry for measuring 2122, which includes circuitry for measuring one or more SSBs sent from the second network entity according to the STC configuration.

[0173] The processing by circuits 2121-2122 enables the communication device 2100 to perform Figure 19 The operations 1900 or any aspect related thereto may be described.

[0174] The various components of the communication device 2100 may provide for performing Figure 19 The means for sending, transmitting, or outputting for sending may include: Figure 3 The transceiver 332 and / or antenna 334 of the BS 102 illustrated in FIG. Figure 21 The transceiver 2108 and antenna 2110 of the communication device 2100 in FIG. Components for receiving or obtaining may include Figure 3 The illustrated transceiver 332 and / or antenna 334 of the BS 102, and / or Figure 21 The transceiver 2108 and antenna 2110 of the communication device 2100 in FIG.

[0175] Figure 22 Depicted are aspects of an example communications device 2200. In some aspects, the communications device 2200 is a node, such as described above with respect to Figure 1 and Figure 3 BS102 as described.

[0176] The communication device 2200 includes a processing system 2202 coupled to a transceiver 2208 (e.g., a transmitter and / or receiver) and / or a network interface. The transceiver 2208 is configured to transmit and receive signals for the communication device 2200 via an antenna 2210, such as the various signals described herein. The network interface 2212 is configured to receive signals via a communication link (e.g., such as those described herein). Figure 2 The backhaul link, midhaul link, and / or fronthaul link) obtain and transmit signals of the communication device 2200. The processing system 2202 can be configured to perform processing functions of the communication device 2200, including processing signals received and / or to be transmitted by the communication device 2200.

[0177] The processing system 2202 includes one or more processors 2220. In various aspects, the one or more processors 2220 may represent one or more of the receive processor 338, the transmit processor 320, the TX MIMO processor 330, and / or the controller / processor 340, as described with respect to FIG. Figure 3 The one or more processors 2220 are coupled to the computer readable medium / memory 2230 via the bus 2206. In some aspects, the computer readable medium / memory 2230 is configured to store instructions (e.g., computer executable code) that, when executed by the one or more processors 2220, cause the one or more processors 2220 to perform operations related to the computer readable medium / memory 2230. Figure 20 The described operations 2000 or any aspects related to these operations. It should be noted that reference to a processor of the communication device 2200 performing a function may include one or more processors of the communication device 2200 performing that function.

[0178] In the depicted example, the computer-readable medium / memory 2230 stores: code (e.g., executable instructions) for receiving 2231, including code for receiving signaling carrying a request for STC configuration of a second network entity from a first network entity, and code for sending 2232, including code for sending signaling carrying STC configuration of the second network entity to the first network entity in response to the request. Processing of the codes 2231-2232 may cause the communication device 2200 to perform operations related to Figure 20 The operations 2000 or any aspect related thereto.

[0179] The one or more processors 2220 include circuits configured to implement (e.g., execute) code stored in a computer-readable medium / memory 2230, the circuits including: a circuit for receiving 2221 including a circuit for receiving signaling carrying a request for STC configuration of a second network entity from a first network entity; and a circuit for sending 2222 including a circuit for sending signaling carrying the STC configuration of the second network entity to the first network entity in response to the request.

[0180] The processing by circuits 2221-2222 enables the communication device 2200 to perform Figure 20 The operations 2000 or any aspect related thereto.

[0181] The various components of the communication device 2200 may provide for performing Figure 20 The means for sending, transmitting or outputting for sending may include: Figure 3 The transceiver 332 and / or antenna 334 of the BS 102 illustrated in FIG. Figure 22 The transceiver 2208 and antenna 2210 of the communication device 2200 in FIG. Components for receiving or obtaining may include Figure 3 The illustrated transceiver 332 and / or antenna 334 of the BS 102, and / or Figure 22 The transceiver 2208 and antenna 2210 of the communication device 2200 in FIG.

[0182] Sample Clauses

[0183] Specific implementation examples are described in the following numbered clauses:

[0184] Clause 1: A method for wireless communication by a first network entity, the method comprising: obtaining a synchronization signal block (SSB) transmission configuration (STC) of a second network entity; and measuring one or more SSBs transmitted from the second network entity according to the STC configuration.

[0185] Clause 2: The method, alone or in combination with clause 1, wherein the first network entity is a mobile integrated access and backhaul (IAB) node or a static IAB node.

[0186] Clause 3: The method, alone or in combination with clause 1, wherein the second network entity is a mobile integrated access and backhaul (IAB) node or a static IAB node.

[0187] Clause 4: The method, alone or in combination with clause 1, wherein said obtaining comprises receiving broadcast signaling from said second network entity carrying said STC configuration of said second network entity.

[0188] Clause 5: A method, alone or in combination with clause 1, wherein the obtaining comprises: receiving signaling carrying an indication from the second network entity, wherein the indication indicates that the second network entity has the STC configuration; in response to the received indication, sending signaling carrying a request for the STC configuration to the second network entity; and in response to the request, receiving signaling carrying the STC configuration from the second network entity.

[0189] Clause 6: A method, alone or in combination with clause 5, wherein the request further comprises a request for at least one of: sending an aperiodic cross-link interference (CLI) reference signal (RS) to the first network entity, changing the periodicity of sending the CLI RS to the first network entity, or switching from a current integrated access and backhaul (IAB) donor node to a new IAB donor node.

[0190] Clause 7: A method, alone or in combination with clause 1, wherein the obtaining comprises: receiving signalling carrying an indication from the second network entity, wherein the indication indicates that the second network entity has the STC configuration; in response to the received indication, sending signalling carrying a request for the STC configuration of the second network entity to a node; and in response to the request, receiving signalling carrying the STC configuration of the second network entity from the node.

[0191] Clause 8: The method, alone or in combination with clause 7, wherein the request further comprises identification (ID) information of the second network entity.

[0192] Clause 9: The method, alone or in combination with clause 7, wherein the node is a Central Unit (CU) of an Integrated Access and Backhaul (IAB) donor node or an Operation, Administration and Maintenance (OAM) node.

[0193] Clause 10: A method, alone or in combination with clause 7, wherein the request further comprises a request for at least one of: receiving an aperiodic cross-link interference (CLI) reference signal (RS) from the second network entity or changing the periodicity of the transmission of the CLI RS from the second network entity.

[0194] Clause 11: The method, alone or in combination with clause 1, wherein said obtaining comprises receiving sidelink signaling from said second network entity carrying said STC configuration of said second network entity.

[0195] Clause 12: A method, alone or in combination with clause 1, wherein the obtaining comprises: sending sidelink signaling carrying a request for the STC configuration to the second network entity; and receiving sidelink signaling carrying the STC configuration from the second network entity in response to the request.

[0196] Clause 13: A method, alone or in combination with clause 12, wherein the request further comprises a request for at least one of: sending an aperiodic cross-link interference (CLI) reference signal (RS) to the first network entity, changing the periodicity of sending the CLI RS to the first network entity, or switching from a current integrated access and backhaul (IAB) donor node to a new IAB donor node.

[0197] Clause 14: A method, alone or in combination with the first clause, comprising receiving signaling from a node to configure an SSB measurement time configuration (SMTC), wherein the SMTC configuration comprises one or more parameters indicating at least an SMTC window of the first network entity; and the measurement comprises measuring the one or more SSBs from the second network entity during the SMTC window.

[0198] Clause 15: The method, alone or in combination with clause 14, wherein the node is a Central Unit (CU) of an Integrated Access and Backhaul (IAB) donor node or an Operation, Administration and Maintenance (OAM) node.

[0199] Clause 16: A method, alone or in combination with the first clause, further comprising: detecting a number of SSBs from the second network entity; and configuring an SSB measurement time configuration (SMTC) when at least one detected SSB is above a threshold, wherein the SMTC configuration comprises one or more parameters indicating at least an SMTC window of the first network entity, and wherein the SMTC window is aligned with an STC window of the second network entity to measure the one or more SSBs from the second network entity.

[0200] Clause 17: The method, alone or in combination with clause 16, wherein said configuring comprises updating a current SMTC window to a new SMTC window.

[0201] Clause 18: A method, alone or in combination with the first clause, further comprising: performing beam measurements based on a cross-link interference (CLI) reference signal (RS) received from the second network entity; and sending a report indicating the beam measurement value to the second network entity or node to coordinate scheduling.

[0202] Clause 19: The method, alone or in combination with clause 18, wherein the node is a Central Unit (CU) of an Integrated Access and Backhaul (IAB) donor node or an Operation, Administration and Maintenance (OAM) node.

[0203] Clause 20: A method for wireless communication by a node, the method comprising: receiving signaling from a first network entity carrying a request for a synchronization signal block (SSB) transmission configuration (STC) of a second network entity; and sending signaling to the first network entity carrying the STC configuration of the second network entity in response to the request.

[0204] Clause 21: The method, alone or in combination with clause 20, wherein the request further comprises identification (ID) information of the second network entity.

[0205] Clause 22: The method, alone or in combination with clause 20, wherein the node is a Central Unit (CU) of an Integrated Access and Backhaul (IAB) donor node or an Operation, Administration and Maintenance (OAM) node.

[0206] Clause 23: The method, alone or in combination with clause 20, wherein the first network entity is a mobile integrated access and backhaul (IAB) node or a static IAB node.

[0207] Clause 24: The method, alone or in combination with clause 20, wherein the second network entity is a mobile integrated access and backhaul (IAB) node or a static IAB node.

[0208] Clause 25: A method, alone or in combination with Clause 20, further comprising: configuring the first network entity using an SSB measurement time configuration (SMTC), wherein the SMTC configuration comprises one or more parameters indicating at least an SMTC window of the first network entity, and wherein the SMTC window is aligned with an STC window of the second network entity to measure one or more SSBs from the second network entity.

[0209] Clause 26: An apparatus comprising: a memory comprising executable instructions; and a processor configured to execute the executable instructions and cause the apparatus to perform the method of any one of clauses 1 to 25.

[0210] Clause 27: An apparatus comprising means for performing the method of any one of clauses 1 to 25.

[0211] Clause 28: A non-transitory computer-readable medium comprising executable instructions that, when executed by a processor of an apparatus, cause the apparatus to perform the method of any one of clauses 1 to 25.

[0212] Clause 29: A computer program product embodied on a computer readable storage medium comprising code for performing the method according to any one of clauses 1 to 25.

[0213] Additional Notes

[0214] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein do not limit the scope, applicability, or aspects set forth in the claims. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, the functions and arrangements of the elements discussed may be changed without departing from the scope of this disclosure. Various examples may omit, replace, or add various processes or components as appropriate. For example, the methods described may be performed in an order different from that described, and various actions may be added, omitted, or combined. In addition, the features described with respect to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement a device or practice a method. In addition, the scope of this disclosure is intended to cover such devices or methods practiced using other structures, functionalities, or structures and functionalities in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0215] The various illustrative logical blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or performed using a general purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. While a general purpose processor may be a microprocessor, in an alternative embodiment, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC), or any other such configuration.

[0216] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items (including single members). By way of example, "at least one of a, b, or c" is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination having multiples of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0217] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, database, or another data structure), ascertaining, and the like. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. Furthermore, "determining" may include resolving, selecting, choosing, establishing, and the like.

[0218] The methods disclosed herein include one or more actions for implementing the methods. Method actions may be interchangeable with each other without departing from the scope of the claims. In other words, unless a specified order of actions is specified, the order and / or use of specific actions may be modified without departing from the scope of the claims. In addition, the various operations of the above methods may be performed by any suitable component capable of performing the corresponding function. The component may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs), or processors.

[0219] The following claims are not intended to be limited to the aspects shown herein, but should be given the full scope consistent with the language of the claims. Within the claims, unless expressly stated, reference to an element in the singular is not intended to mean "one and only one", but "one or more". Unless otherwise specified, the term "some" refers to one or more. No claim element is to be interpreted under the provisions of 35 U.S.C. § 112 (f) unless the element is explicitly stated using the phrase "parts for...". All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are known or will later be known to one of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims.

Claims

1. A first network entity configured for wireless communication, the first network entity comprising: a memory including computer executable instructions; and a processor configured to execute the computer executable instructions and cause the first network entity to: obtaining a synchronization signal block (SSB) transmission configuration (STC) of the second network entity; as well as One or more SSBs sent from the second network entity are measured according to the STC configuration.

2. The first network entity according to claim 1, wherein the first network entity is a mobile integrated access and backhaul (IAB) node or a static IAB node.

3. The first network entity of claim 1, wherein the second network entity is a mobile integrated access and backhaul (IAB) node or a static IAB node. 4 . The first network entity of claim 1 , wherein the obtaining comprises receiving, from the second network entity, broadcast signaling carrying the STC configuration of the second network entity.

5. The first network entity according to claim 1, wherein the obtaining comprises: receiving signaling carrying an indication from the second network entity, wherein the indication indicates that the second network entity has the STC configuration; In response to the received indication, sending signaling carrying a request for the STC configuration to the second network entity; as well as In response to the request, signaling carrying the STC configuration is received from the second network entity.

6. The first network entity of claim 5, wherein the request further comprises a request for at least one of: sending an aperiodic cross-link interference (CLI) reference signal (RS) to the first network entity, changing a periodicity of sending the CLI RS to the first network entity, or switching from a current integrated access and backhaul (IAB) donor node to a new IAB donor node.

7. The first network entity according to claim 1, wherein the obtaining comprises: receiving signaling carrying an indication from the second network entity, wherein the indication indicates that the second network entity has the STC configuration; In response to the received indication, sending signaling carrying a request for the STC configuration of the second network entity to a node; as well as In response to the request, signaling carrying the STC configuration of the second network entity is received from the node.

8. The first network entity of claim 7, wherein the request further comprises identification (ID) information of the second network entity.

9. The first network entity of claim 7, wherein the node is a Central Unit (CU) of an Integrated Access and Backhaul (IAB) donor node or an Operation, Administration, and Maintenance (OAM) node.

10. The first network entity of claim 7, wherein the request further comprises a request for at least one of: receiving an aperiodic cross-link interference (CLI) reference signal (RS) from the second network entity or changing a periodicity of transmission of the CLIRS from the second network entity.

11. The first network entity of claim 1 , wherein the obtaining comprises receiving sidelink signaling carrying the STC configuration of the second network entity from the second network entity.

12. The first network entity according to claim 1, wherein the obtaining comprises: sending sidelink signaling carrying a request for the STC configuration to the second network entity; as well as In response to the request, sidelink signaling carrying the STC configuration is received from the second network entity.

13. The first network entity of claim 12, wherein the request further comprises a request for at least one of: sending an aperiodic cross-link interference (CLI) reference signal (RS) to the first network entity, changing a periodicity of sending the CLI RS to the first network entity, or switching from a current integrated access and backhaul (IAB) donor node to a new IAB donor node.

14. The first network entity of claim 1, wherein the processor is further configured to execute the computer executable instructions and cause the first network entity to: receiving signaling configuring an SSB measurement time configuration (SMTC) from a node, wherein the SMTC configuration includes one or more parameters indicating at least an SMTC window of the first network entity; and The measuring includes measuring the one or more SSBs from the second network entity during the SMTC window.

15. The first network entity of claim 14, wherein the node is a Central Unit (CU) of an Integrated Access and Backhaul (IAB) donor node or an Operation, Administration and Maintenance (OAM) node.

16. The first network entity of claim 1, wherein the processor is further configured to execute the computer executable instructions and cause the first network entity to: detecting a number of SSBs from the second network entity; and When at least one detected SSB is above a threshold, an SSB measurement time configuration (SMTC) is configured, wherein the SMTC configuration includes one or more parameters indicating at least an SMTC window of the first network entity, and wherein the SMTC window is aligned with an STC window of the second network entity to measure the one or more SSBs from the second network entity.

17. The first network entity according to claim 16, wherein the configuring comprises updating a current SMTC window to a new SMTC window.

18. The first network entity of claim 1, wherein the processor is further configured to execute the computer executable instructions and cause the first network entity to: performing beam measurement based on a cross-link interference (CLI) reference signal (RS) received from the second network entity; and A report indicating beam measurements to coordinate scheduling is sent to the second network entity or node.

19. The first network entity of claim 18, wherein the node is a Central Unit (CU) of an Integrated Access and Backhaul (IAB) donor node or an Operation, Administration and Maintenance (OAM) node.

20. A node for wireless communication, the node comprising: a memory including computer executable instructions; and a processor configured to execute the computer executable instructions and cause the node to: receiving signaling from the first network entity carrying a request for a synchronization signal block (SSB) transmission configuration (STC) of the second network entity; as well as In response to the request, signaling carrying the STC configuration of the second network entity is sent to the first network entity.

21. The node of claim 20, wherein the request further comprises identification (ID) information of the second network entity.

22. The node of claim 20, wherein the node is a Central Unit (CU) of an Integrated Access and Backhaul (IAB) donor node or an Operation, Administration and Maintenance (OAM) node.

23. The node of claim 20, wherein the first network entity is a mobile integrated access and backhaul (IAB) node or a static IAB node.

24. The node of claim 20, wherein the second network entity is a mobile integrated access and backhaul (IAB) node or a static IAB node.

25. The node of claim 20, wherein the processor is further configured to execute the computer executable instructions and cause the node to: The first network entity is configured using an SSB measurement time configuration (SMTC), wherein the SMTC configuration includes one or more parameters indicating at least an SMTC window of the first network entity, and wherein the SMTC window is aligned with an STC window of the second network entity to measure one or more SSBs from the second network entity.

26. A method for wireless communication by a first network entity, the method comprising: obtaining a synchronization signal block (SSB) transmission configuration (STC) of the second network entity; as well as One or more SSBs sent from the second network entity are measured according to the STC configuration.

27. The method of claim 26, wherein the first network entity is a mobile integrated access and backhaul (IAB) node or a static IAB node.

28. The method of claim 26, wherein the second network entity is a mobile integrated access and backhaul (IAB) node or a static IAB node.

29. A method for wireless communication by a node, the method comprising: receiving signaling from the first network entity carrying a request for a synchronization signal block (SSB) transmission configuration (STC) of the second network entity; as well as In response to the request, signaling carrying the STC configuration of the second network entity is sent to the first network entity.

30. The method of claim 29, wherein: The request also includes identification (ID) information of the second network entity; and The node is a Central Unit (CU) of an Integrated Access and Backhaul (IAB) donor node or an Operation, Administration and Maintenance (OAM) node.

Images