Reference signal window configuration for mobile network entities

Abstract

Aspects of the present disclosure provide mechanisms for communicating reference signals using a common window configuration to facilitate cross-link interference (CLI) measurement and reporting for mobile network entities. The common window configuration may indicate a plurality of opportunities within a respective window for each of the one or more periods for communicating the one or more reference signals. A network entity (e.g., a mobile network entity or a stationary network entity) may utilize the common window configuration to receive a reference signal from another network entity within an opportunity of the plurality of opportunities in order to obtain CLI measurements indicative of CLIs between the network entities.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to pending U.S. non-provisional application No. 17 / 746,762, filed on May 17, 2022, which is assigned to the assignee of the present application and is hereby expressly incorporated herein by reference as if fully set forth below and for all applicable purposes. Technical Field

[0003] The techniques discussed below relate generally to wireless communication systems, and more particularly to configuring windows for sending and receiving reference signals to identify cross-link interference between mobile network entities or between a mobile network entity and a stationary network entity. Background Art

[0004] In wireless communication systems, such as those specified under the standards for 5G New Radio (NR), network entities (e.g., base stations) may communicate with user equipment (UE) (e.g., smartphones). Transmissions from a network entity to one or more UEs over an air interface are referred to as downlink (DL) transmissions, while transmissions from a UE to a network entity are referred to as uplink (UL) transmissions.

[0005] Each of the network entity and the UE may communicate in a half-duplex mode, in which only one node may transmit at a time (e.g., resources may be allocated for either DL transmission or UL transmission at a time), or in a full-duplex mode, in which both nodes may transmit simultaneously (e.g., resources may be allocated for both DL transmission and UL transmission at a time). Half-duplex is often implemented for wireless links using time division duplex (TDD).

[0006] In 5G wireless systems, UL TDD transmissions and DL TDD transmissions can be dynamically scheduled to adapt to the traffic load in the network. Dynamic TDD and full-duplex network configurations may suffer from cross-link interference between network entities. For example, cross-link interference may be caused by downlink transmissions occurring simultaneously with uplink transmissions. In one example, a downlink transmission may be initiated by one network entity, while an uplink transmission is received by another adjacent network entity. Summary of the invention

[0007] The following is a summary of one or more aspects of the present disclosure to provide a basic understanding of these aspects. This summary is not an extensive review of all expected features of the present disclosure, and is neither intended to identify the key or important elements of all aspects of the present disclosure, nor is it intended to describe the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a form as a preface to a more detailed description presented later.

[0008] In one example, a first network entity for wireless communication is disclosed. The first network entity includes a memory and a processor coupled to the memory. The processor is configured to receive a common window configuration for multiple mobile network entities from a central network entity. The common window configuration includes multiple opportunities within a corresponding window of each of one or more cycles for conveying one or more reference signals. The processor is further configured to: receive a first reference signal from a second network entity within a first opportunity among the multiple opportunities, wherein at least one of the first network entity or the second network entity is a mobile network entity among the multiple mobile network entities. The processor is further configured to: obtain a cross-link interference measurement indicating cross-link interference between the first network entity and the second network entity based on the first reference signal.

[0009] Another example provides a method capable of operating at a first network entity. The method includes: receiving a common window configuration for multiple mobile network entities from a central network entity. The common window configuration includes multiple opportunities within a corresponding window for each of one or more periods for conveying one or more reference signals. The method also includes: receiving a first reference signal from a second network entity within a first opportunity in the multiple opportunities, wherein at least one of the first network entity or the second network entity is a mobile network entity among the multiple mobile network entities. The method also includes: obtaining a cross-link interference measurement indicating cross-link interference between the first network entity and the second network entity based on the first reference signal.

[0010] Another example provides a central network entity, the central network entity comprising a memory and a processor coupled to the memory. The processor is configured to provide a common window configuration for multiple mobile network entities. The common window configuration includes multiple opportunities within a corresponding window for each of one or more cycles of one or more reference signals. The processor is further configured to: receive at least one cross-link interference measurement report indicating cross-link interference between neighboring network entities, at least one of the neighboring network entities being a mobile network entity among the multiple mobile network entities.

[0011] Another example provides a method operable at a central network entity. The method includes providing a common window configuration for a plurality of mobile network entities. The common window configuration includes a plurality of opportunities within a corresponding window for each of one or more periods for communicating one or more reference signals. The method also includes receiving at least one cross-link interference measurement report indicating cross-link interference between neighboring network entities, at least one of the neighboring network entities being a mobile network entity among the plurality of mobile network entities.

[0012] These and other aspects will be more fully understood after reading the following detailed description. After reading the following description of specific exemplary aspects in conjunction with the accompanying drawings, other aspects, features and examples will be apparent to those of ordinary skill in the art. Although each feature may be discussed below with respect to certain examples and drawings, all examples may include one or more of the features discussed herein. In other words, although one or more examples may be discussed as having certain features, one or more of such features may also be used according to the various examples discussed herein. Similarly, although each example may be discussed below as an example of a device, system or method, it should be understood that such examples may be implemented in various devices, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 is a diagram illustrating an example of a wireless communication system in accordance with some aspects.

[0014] Figure 2 is a diagram illustrating an example of a radio access network (RAN) in accordance with some aspects.

[0015] Figure 3 is a schematic illustration of organization of radio resources in an air interface utilizing orthogonal frequency division multiplexing (OFDM) in accordance with some aspects.

[0016] Figure 4 is a diagram providing a high-level illustration of one example of a configuration of a decomposed base station in accordance with some aspects.

[0017] Figure 5 is a diagram illustrating an example of IAB node functionality within an IAB network in accordance with some aspects.

[0018] Figure 6

[0013] An example of a wireless communication system supporting beamforming between network entities in accordance with some aspects is illustrated.

[0019] Figure 7 is a diagram illustrating cross-link interference (CLI) in a wireless communication network according to some aspects.

[0020] Fig. 8A is a diagram illustrating an example of a wireless communication network providing a common window configuration according to some aspects.

[0021] Figure 8B An example of a common window configuration in accordance with some aspects is illustrated.

[0022] Fig. 9 is a signaling diagram illustrating example signaling for CLI measurements using a common window configuration in accordance with some aspects.

[0023] Fig.10 is a flow chart illustrating an example process for CLI measurements using a common window configuration in accordance with some aspects.

[0024] Fig.11 is a flow chart illustrating another exemplary process for CLI measurements using a common window configuration in accordance with some aspects.

[0025] Fig.12 is a flow chart illustrating another exemplary process for CLI measurements using a common window configuration in accordance with some aspects.

[0026] Fig.13 is a signaling diagram illustrating example signaling for performing CLI measurements at a stationary network entity using a common window configuration in accordance with some aspects.

[0027] Fig.14 is a flow chart illustrating an example process for performing CLI measurements at a stationary network entity using a common window configuration in accordance with some aspects.

[0028] Fig.15 is a flow chart illustrating another example process for performing CLI measurements at a stationary network entity using a common window configuration in accordance with some aspects.

[0029] Fig.16 is a flow chart illustrating an example process for performing CLI measurements between a stationary network entity and a mobile network entity in accordance with some aspects.

[0030] Fig.17 is a signaling diagram illustrating example signaling for CLI measurements between a mobile network entity and a stationary network entity using a separate window configuration in accordance with some aspects.

[0031] Fig.18 is a block diagram illustrating an example of a hardware implementation of a network entity employing a processing system according to some aspects.

[0032] Fig.19 is a flow chart of an example process for performing CLI measurements using a common window configuration in accordance with some aspects.

[0033] Fig. 20 is a block diagram illustrating an example of a hardware implementation of a central network entity employing a processing system according to some aspects.

[0034] Fig.21 is a flow chart of an example process for configuring a common window configuration for CLI measurement and reporting in accordance with some aspects. DETAILED DESCRIPTION

[0035] The specific embodiments described below in conjunction with the accompanying drawings are intended as descriptions of various configurations and are not intended to represent the only configurations with which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, it is apparent to those skilled in the art that these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0036] Although various aspects and examples are described in this application by illustrating some examples, it will be understood by those skilled in the art that additional specific implementations and use cases can be generated in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, various aspects and / or uses can be generated via integrated chip examples and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not specifically point to use cases or applications, the applicability of various types of described innovations may occur. The scope of specific implementation can range from chip-level or module components to non-module, non-chip-level specific implementations, and further to aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more aspects of the described innovation. In some actual settings, the device in conjunction with the described aspects and features may also necessarily include additional components and features for the specific implementation and practice of the claimed and described examples. For example, the transmission and reception of wireless signals necessarily include several components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains (RF chains), power amplifiers, modulators, buffers, processors, interleavers, adders, summers, etc.). The innovations described herein are intended to be practiced in a variety of devices of different sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, disaggregated arrangements (e.g., base stations and / or UEs), end-user devices, etc.

[0037] In an example where at least one network entity is a mobile network entity, various aspects of the present disclosure provide techniques for facilitating cross-link interference (CLI) measurements between network entities. A central network entity (e.g., a central unit (CU), a real-time or non-real-time intelligent controller, or a core network node) may generate and provide a common window configuration for a mobile network entity. The common window configuration may indicate a plurality of opportunities within a window for communicating a reference signal, such as a synchronization signal block (SSB). The network entity may utilize the common window configuration to measure CLI with a neighboring network entity. For example, the network entity may send a reference signal within one opportunity of a window and listen to reference signals from other neighboring network entities within other opportunities of the window.

[0038] The various concepts presented throughout this disclosure may be implemented across a wide variety of telecommunication systems, network architectures, and communication standards. Figure 1 , various aspects of the present disclosure are illustrated with reference to a wireless communication system 100 as an illustrative example and not as a limitation. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. By means of the wireless communication system 100, the UE 106 may be enabled to perform data communications with an external data network 110, such as (but not limited to) the Internet.

[0039] The RAN 104 may implement any suitable one or more wireless communication technologies to provide radio access to the UE 106. As an example, the RAN 104 may operate according to the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification, commonly referred to as 5G. As another example, the RAN 104 may operate according to a hybrid of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, commonly referred to as Long Term Evolution (LTE). 3GPP refers to such a hybrid RAN as the Next Generation RAN or NG-RAN. Of course, many other examples may be utilized within the scope of the present disclosure.

[0040] As illustrated, RAN 104 includes multiple base stations 108. In a broad sense, a base station is a network element in a radio access network that is responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards or contexts, a base station may be referred to as a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a node B (NB), an evolved node B (eNB), a next generation node B (gNB), a transmission reception point (TRP) or some other suitable terminology by those skilled in the art. In some examples, a base station may include two or more TRPs that may be co-located or non-co-located. Each TRP may communicate on the same or different carrier frequencies in the same or different frequency bands. In an example where RAN 104 operates according to two standards, LTE and 5G NR, one of the base stations may be an LTE base station, and the other base station may be a 5G NR base station. In addition, one or more base stations in the base station may have a decomposed configuration.

[0041] RAN 104 is also illustrated as supporting wireless communications for multiple mobile devices. In the 3GPP standards, a mobile device may be referred to as a user equipment (UE), but those skilled in the art may also refer to it as a mobile station (MS), a user station, a mobile unit, a user unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile user station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology. A UE may be a device (e.g., a mobile device) that provides access to network services to a user.

[0042] Within the present disclosure, a "mobile" device does not necessarily need to have the ability to move, but may be stationary. The term mobile device or mobile equipment refers broadly to a wide variety of devices and technologies. A UE may include several hardware structural components sized, shaped, and arranged to facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile stations, cellular (cell) phones, smart phones, Session Initiation Protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablet devices, personal digital assistants (PDAs), and a wide range of embedded systems, e.g., corresponding to the "Internet of Things" (IoT).

[0043] The mobile device may also be a car or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-rotor aircraft, a quadcopter, a remote control device, a consumer and / or wearable device (such as glasses, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, etc. The mobile device may also be a digital home or smart home device (such as home audio, video and / or multimedia equipment), an appliance, a vending machine, a smart lighting device, a home security system, a smart meter Etc. The mobile device may also be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device that controls electrical power (e.g., a smart grid), lighting, water supply, etc., an industrial automation and enterprise device, a logistics controller, and / or agricultural equipment, etc. In addition, the mobile device may provide connected medical or telemedicine support, such as health care at a distance. Telemedicine devices may include telemedicine monitoring devices and telemedicine management devices, whose communications may be given priority or access priority over other types of information, for example, in terms of priority access for the transmission of critical service data and / or associated QoS for the transmission of critical service data.

[0044] Wireless communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmissions from a base station (e.g., base station 108) to one or more UEs (e.g., similar to UE 106) over the air interface can be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term downlink may refer to point-to-multipoint transmissions originating from a base station (e.g., base station 108). Another way to describe this scheme may be to use the term "broadcast channel multiplexing". Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) may be referred to as uplink (UL) transmissions. According to further aspects of the present disclosure, the term uplink may refer to point-to-point transmissions originating at a UE (e.g., UE 106).

[0045] In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a base station 108) allocates resources for communications among some or all devices and equipment within its service area or cell. Within the present disclosure, as discussed further below, a scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities (e.g., UE 106). That is, for scheduled communications, multiple UEs 106 (which may be scheduled entities) may utilize resources allocated by the scheduling entity 108.

[0046] Base station 108 is not the only entity that can act as a scheduling entity. That is, in some examples, a UE can act as a scheduling entity, thereby scheduling resources for one or more scheduled entities (e.g., one or more other UEs). For example, a UE can communicate directly with other UEs in a peer-to-peer or device-to-device manner and / or in a relay configuration.

[0047] like Figure 1 , the scheduling entity 108 may broadcast downlink traffic 112 to one or more scheduled entities (e.g., one or more UEs 106). Broadly speaking, the scheduling entity 108 is a node or device responsible for scheduling traffic in the wireless communication network, including downlink traffic 112 and, in some examples, uplink traffic 116 from one or more scheduled entities (e.g., one or more UEs 106) to the scheduling entity 108. On the other hand, the scheduled entity (e.g., UE 106) is a node or device that receives downlink control information 114 (including but not limited to scheduling information (e.g., grants), synchronization or timing information, or other control information) from another entity in the wireless communication network, such as the scheduling entity 108. The scheduled entity 106 may also send uplink control information 118 (including but not limited to scheduling requests or feedback information or other control information) to the scheduling entity 108.

[0048] In addition, uplink and / or downlink control information 114 and / or 118 and / or business 112 and / or 116 information may be sent on a waveform that may be time-divided into frames, subframes, time slots and / or symbols. As used herein, a symbol may refer to a time unit that carries one resource element (RE) per subcarrier in an orthogonal frequency division multiplexing (OFDM) waveform. A time slot may carry 7 or 14 OFDM symbols. A subframe may refer to a duration of 1 ms. Multiple subframes or time slots may be grouped together to form a single frame or radio frame. Within the present disclosure, a frame may refer to a predetermined duration (e.g., 10 ms) for wireless transmission, wherein each frame is composed of, for example, 10 subframes, each subframe being 1 ms. Of course, these definitions are not required, and any suitable scheme for organizing waveforms may be utilized, and the various time divisions of waveforms may have any suitable duration.

[0049] Generally speaking, the base stations 108 may include a backhaul interface for communicating with a backhaul portion 120 of the wireless communication system 100. The backhaul portion 120 may provide a link between the base stations 108 and the core network 102. Furthermore, in some examples, a backhaul network may provide interconnections between the respective base stations 108. Various types of backhaul interfaces may be employed, such as a direct physical connection using any suitable transport network, a virtual network, and the like.

[0050] The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 may be configured according to a 5G standard (e.g., 5GC). In other examples, the core network 102 may be configured according to a 4G Evolved Packet Core (EPC) or any other suitable standard or configuration.

[0051] See now Figure 2 , by way of illustrative example and not limitation, a schematic diagram of a radio access network (RAN) 200 according to some aspects of the present disclosure is provided. In some examples, the RAN 200 may be similar to the RAN described above and in Figure 1 is the same as the RAN 104 illustrated in .

[0052] The geographic area covered by the RAN 200 may be divided into a number of cellular regions (cells) that may be uniquely identified by a user equipment (UE) based on an identity broadcast from an access point or base station within the geographic area. Figure 2 Cells 202, 204, 206, and 208 are illustrated, each of which may include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors within a cell are served by the same base station. A radio link within a sector may be identified by a single logical identifier belonging to the sector. In a cell divided into sectors, multiple sectors within a cell may be formed by multiple groups of antennas, each of which is responsible for communicating with a UE in a portion of the cell.

[0053] Various base station arrangements can be used. Figure 2 , two base stations (base station 210 and base station 212) are shown in cells 202 and 204. A third base station (base station 214) is shown as controlling a remote radio head (RRH) 216 in cell 206. That is, the base station may have an integrated antenna, or may be connected to an antenna or RRH 216 by a feeder cable. In the illustrated example, cells 202, 204, and 206 may be referred to as macro cells because base stations 210, 212, and 214 support cells with large sizes. In addition, base station 218 is shown in cell 208, which may overlap with one or more macro cells. In this example, cell 208 may be referred to as a small cell (e.g., a micro cell, a pico cell, a femto cell, a home base station, a home node B, a home evolved node B, etc.) because base station 218 supports cells with relatively small sizes. Cell size settings may be performed according to system design and component constraints.

[0054] It should be understood that the RAN 200 may include any number of wireless base stations and cells. In addition, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, 218 provide wireless access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 may be similar to those described above and in Figure 1 The scheduling entity 108 illustrated in FIG. 1 is the same as or similar to that in FIG.

[0055] Figure 2 Also included is an unmanned aerial vehicle (UAV) 220, which may be a drone or a quadcopter. UAV 220 may be configured to act as a base station, or more specifically, a mobile base station. That is, in some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move depending on the location of a mobile base station (such as UAV 220).

[0056] Within the RAN 200, cells may include UEs that may communicate with one or more sectors of each cell. In addition, each base station 210, 212, 214, 218, and 220 may be configured to provide access to the core network 102 (see FIG. 1 ) for all UEs in the corresponding cell. Figure 1 ) access point. For example, UEs 222 and 224 may communicate with base station 210; UEs 226 and 228 may communicate with base station 212; UEs 230 and 232 may communicate with base station 214 via RRH 216; UE 234 may communicate with base station 218; and UE 236 may communicate with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may communicate with the base stations described above and in Figure 1 202. The UE / scheduled entity 106 illustrated in FIG. 202 is the same or similar to the UE / scheduled entity 106 illustrated in FIG. 202. In some examples, the UAV 220 (e.g., a quadcopter) can be a mobile network node and can be configured to act as a UE. For example, the UAV 220 can operate within the cell 202 by communicating with the base station 210.

[0057] In other aspects of RAN 200, sidelink signals can be used between UEs without relying on scheduling or control information from a base station. Sidelink communications can be utilized in device-to-device (D2D) networks, peer-to-peer (P2P) networks, vehicle-to-vehicle (V2V) networks, vehicle-to-everything (V2X) networks, and / or other suitable sidelink networks. For example, two or more UEs (e.g., UE 238, 240, and 242) can communicate with each other using sidelink signals 237 without relaying the communication through a base station. In some examples, UE 238, 240, and 242 can each act as a scheduling entity or a transmitting sidelink device and / or a scheduled entity or a receiving sidelink device to schedule resources and communicate sidelink signals 237 between them without relying on scheduling or control information from a base station. In other examples, two or more UEs (e.g., UE 226 and 228) within the coverage area of ​​a base station (e.g., base station 212) can also communicate sidelink signals 227 via a direct link (sidelink) without transmitting the communication through base station 212. In this example, base station 212 may allocate resources to UEs 226 and 228 for sidelink communications.

[0058] In some examples, a D2D relay framework may be included within a cellular network to facilitate relaying of communications to / from base station 212 via a D2D link (e.g., side link 227 or 237). For example, one or more UEs (e.g., UE 228) within the coverage area of ​​base station 212 may operate as relay UEs to expand the coverage of base station 212, improve transmission reliability to one or more UEs (e.g., UE 226), and / or allow the base station to recover from a failed UE link due to, for example, blocking or fading.

[0059] In order to obtain a low block error rate (BLER) for transmissions over the air interface while still achieving very high data rates, channel coding may be used. That is, wireless communications may typically utilize a suitable error-correcting block code. In a typical block code, an information message or sequence is split into code blocks (CBs), and an encoder (e.g., a codec) at the sender device then mathematically adds redundancy to the information message. Utilizing this redundancy in the encoded information message can improve the reliability of the message, enabling correction of any bit errors that may occur due to noise.

[0060] Data decoding can be implemented in a variety of ways. In early 5G NR specifications, user data is decoded using quasi-cyclic low-density parity check (LDPC) with two different basemaps: one basemap is used for large code blocks and / or high code rates, and the other basemap is used for other cases. Control information and the physical broadcast channel (PBCH) are decoded based on nested sequences using polar decoding. For these channels, puncturing, shortening, and repetition are used for rate matching.

[0061] Aspects of the present disclosure may be implemented using any suitable channel codes. Various implementations of base stations and UEs may include appropriate hardware and capabilities (eg, encoders, decoders, and / or codecs) to utilize one or more of these channel codes for wireless communications.

[0062] In the RAN 200, the ability of a UE to communicate while moving (independent of its location) is called mobility. The various physical channels between the UE and the RAN 200 are generally established, maintained, and released under the control of an access and mobility management function (AMF). In some scenarios, the AMF may include: a security context management function (SCMF) and a security anchor function (SEAF) that performs authentication. The SCMF may manage security contexts for both control plane functionality and user plane functionality in whole or in part.

[0063] In various aspects of the present disclosure, the RAN 200 may utilize DL-based mobility or UL-based mobility to implement mobility and handover (i.e., the transfer of a UE's connection from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity or at any other time, the UE may monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Based on the quality of these parameters, the UE may maintain communication with one or more neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE may perform a handover or handover from the serving cell to a neighboring (target) cell. For example, a UE 224 may move from a geographic area corresponding to its serving cell 202 to a geographic area corresponding to a neighboring cell 206. When the signal strength or quality from a neighboring cell 206 exceeds the signal strength and quality of its serving cell 202 for a given amount of time, the UE 224 may send a report message indicating the condition to its serving base station 210. In response, UE 224 may receive the handover command, and the UE may proceed with the handover to cell 206 .

[0064] In a network configured for UL-based mobility, the network can select a serving cell for each UE using a UL reference signal from each UE. In some examples, base stations 210, 212, and 214 / 216 may broadcast unified synchronization signals (e.g., unified primary synchronization signal (PSS), unified secondary synchronization signal (SSS), and unified physical broadcast channel (PBCH)). UEs 222, 224, 226, 228, 230, and 232 may receive unified synchronization signals, derive carrier frequency and slot timing from these synchronization signals, and send uplink pilots or reference signals in response to the derived timing. The uplink pilot signal sent by a UE (e.g., UE 224) may be received concurrently by two or more cells (e.g., base stations 210 and 214 / 216) within RAN 200. Each of the cells may measure the strength of the pilot signal, and the radio access network (e.g., one or more of the base stations 210 and 214 / 216 and / or a central node within the core network) may determine a serving cell for the UE 224. As the UE 224 moves through the RAN 200, the RAN 200 may continue to monitor the uplink pilot signals sent by the UE 224. When the signal strength or quality of the pilot signal measured by the neighboring cell exceeds the signal strength or quality measured by the serving cell, the RAN 200 may hand over the UE 224 from the serving cell to the neighboring cell with or without notifying the UE 224.

[0065] Although the synchronization signals transmitted by base stations 210, 212 and 214 / 216 may be uniform, the synchronization signal may not identify a specific cell, but may identify a zone of multiple cells operating on the same frequency and / or using the same timing. Using zones in a 5G network or other next generation communication network implements an uplink-based mobility framework and improves the efficiency of both the UE and the network, since the number of mobility messages that need to be exchanged between the UE and the network can be reduced.

[0066] In various specific implementations, the air interface in the radio access network 200 can utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum generally provides exclusive use of a portion of the spectrum with the help of a mobile network operator purchasing a license from a government regulator. Unlicensed spectrum provides shared use of a portion of the spectrum without the need for a government-granted license. Although it is generally still necessary to comply with some technical rules to access the unlicensed spectrum, generally any operator or device can obtain access. Shared spectrum can fall between licensed spectrum and unlicensed spectrum, where some technical rules or restrictions may be required to access the spectrum, but the spectrum can still be shared by multiple operators and / or multiple RATs. For example, a license holder of a portion of a licensed spectrum can provide licensed shared access (LSA) to share the spectrum with other parties (e.g., with appropriate licensee-determined conditions to obtain access).

[0067] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5GNR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0068] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4-a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0069] In view of the above aspects, unless otherwise specifically stated, it should be understood that if used in this document, the term "below 6 GHz" and the like can broadly refer to frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" and the like are used in this document, they can broadly refer to frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band.

[0070] Devices communicating in the radio access network 200 may utilize one or more multiplexing techniques and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification provides multiple access for UL transmissions from UEs 222 and 224 to the base station 210, and multiplexing of DL transmissions from the base station 210 to one or more UEs 222 and 224 using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP). In addition, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also referred to as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and may be provided using time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource extension multiple access (RSMA), or other suitable multiple access schemes. In addition, multiplexing of DL transmissions from base station 210 to UEs 222 and 224 may be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0071] The equipment in the radio access network 200 can also utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link in which two endpoints can communicate with each other in two directions. Full-duplex means that two endpoints can communicate with each other at the same time. Half-duplex means that only one endpoint can transmit information to the other endpoint at a time. Half-duplex simulation is often implemented for wireless links using time division duplex (TDD). In TDD, the transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, in some scenarios, the channel is dedicated to the transmission in one direction, and at other times, the channel is dedicated to the transmission in the other direction, where the direction can change very quickly, for example, several times per time slot. In wireless links, full-duplex channels generally rely on physical isolation of transmitters and receivers and suitable interference cancellation techniques. Full-duplex simulation is often implemented for wireless links by utilizing frequency division duplex (FDD) or space division duplex (SDD). In FDD, the transmissions in different directions can operate at different carrier frequencies (for example, within a paired spectrum). In SDD, transmissions in different directions on a given channel are separated from each other using spatial division multiplexing (SDM). In other examples, full-duplex communication may be implemented within an unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur within different sub-bands of the carrier bandwidth. This type of full-duplex communication may be referred to herein as sub-band full-duplex (SBFD), also known as flexible duplex.

[0072] Reference Figure 3 Various aspects of the present disclosure are described with reference to the schematically illustrated OFDM waveforms. It will be appreciated by those of ordinary skill in the art that various aspects of the present disclosure may be applied to SC-FDMA waveforms in substantially the same manner as described herein below. That is, while some examples of the present disclosure may focus on OFDM links for clarity, it will be appreciated that the same principles may also be applied to SC-FDMA waveforms.

[0073] Reference now Figure 3 , illustrates an expanded view of an exemplary subframe 302 showing an OFDM resource grid. However, as will be readily apparent to one skilled in the art, the PHY transmit structure for any particular application may differ from the example described herein, depending on any number of factors. Here, time is in the horizontal direction, in units of OFDM symbols; and frequency is in the vertical direction, in units of subcarriers of a carrier.

[0074] Resource grid 304 can be used to schematically represent the time-frequency resources for a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple available antenna ports, a corresponding plurality of resource grids 304 can be available for communication. Resource grid 304 is divided into a plurality of resource elements (REs) 306. RE (which is 1 subcarrier×1 symbol) is the smallest discrete portion of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation utilized in a particular implementation, each RE can represent one or more information bits. In some examples, a block of REs may be referred to as a physical resource block (PRB), or more simply a resource block (RB) 308, which contains any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB may include 12 subcarriers (a number independent of the parameter set used). In some examples, depending on the parameter set, an RB may include any suitable number of consecutive OFDM symbols in the time domain. Within the present disclosure, it is assumed that a single RB (such as RB 308) corresponds entirely to communication in a single direction (transmission or reception for a given device).

[0075] A collection of contiguous or discontinuous resource blocks may be referred to herein as a resource block group (RBG), a subband, or a bandwidth part (BWP). A collection of subbands or BWPs may span the entire bandwidth. Scheduling a scheduled entity (e.g., a UE) for downlink transmission, uplink transmission, or sidelink transmission typically involves scheduling one or more resource elements 306 within one or more subbands or bandwidth parts (BWPs). Therefore, a UE typically utilizes only a subset of a resource grid 304. In some examples, an RB may be the smallest resource unit that may be allocated to a UE. Therefore, the more RBs scheduled for a UE, and the higher the modulation scheme selected for the air interface, the higher the data rate for the UE. The RBs may be scheduled by a base station (e.g., a gNB, an eNB, etc.), or may be self-scheduled by a UE implementing D2D sidelink communication.

[0076] In this illustration, RB 308 is shown as occupying less than the entire bandwidth of subframe 302, with some subcarriers illustrated above and below RB 308. In a given implementation, subframe 302 may have a bandwidth corresponding to any number of one or more RBs 308. Furthermore, in this illustration, RB 308 is shown as occupying less than the entire duration of subframe 302, but this is just one possible example.

[0077] Each 1 ms subframe 302 may include one or more adjacent time slots. Figure 3In the example shown, as an illustrative example, a subframe 302 includes four time slots 310. In some examples, a time slot can be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include micro-slots (sometimes referred to as shortened transmission time intervals (TTIs)) with shorter durations (e.g., one to three OFDM symbols). These micro-slots or shortened transmission time intervals (TTIs) can be sent by occupying resources scheduled for ongoing time slot transmissions for the same UE or different UEs in some cases. Any number of resource blocks can be utilized within a subframe or time slot.

[0078] An expanded view of one of the time slots 310 illustrates that the time slot 310 includes a control region 312 and a data region 314. In general, the control region 312 may carry control channels, and the data region 314 may carry data channels. Of course, a time slot may contain full DL, full UL, or at least one DL portion and at least one UL portion. Figure 3 The structures illustrated in are merely exemplary in nature, and different slot structures may be utilized and may include one or more regions in each of the control region and the data region.

[0079] Although not in Figure 3 Although not shown in the example, various REs 306 within RB 308 may be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 306 within RB 308 may also carry pilot signals or reference signals. These pilot signals or reference signals may be provided to a receiving device to perform channel estimation of the corresponding channel, which may enable coherent demodulation / detection of control channels and / or data channels within RB 308.

[0080] In some examples, time slot 310 may be used for broadcast, multicast, groupcast, or unicast communications. For example, broadcast, multicast, or groupcast communications may refer to point-to-multipoint transmissions from one device (e.g., a base station, UE, or other similar device) to other devices. Here, broadcast communications are delivered to all devices, while multicast or groupcast communications are delivered to multiple intended receiving devices. Unicast communications may refer to point-to-point transmissions from one device to a single other device.

[0081] In an example of cellular communication over a cellular carrier via a Uu interface, for DL ​​transmissions, a scheduling entity (e.g., a base station) may allocate one or more REs 306 (e.g., within a control region 312) to one or more scheduled entities (e.g., UEs) to carry DL control information including one or more DL control channels, such as a physical downlink control channel (PDCCH). The PDCCH carries downlink control information (DCI), including, but not limited to, power control commands (e.g., one or more open-loop power control parameters and / or one or more closed-loop power control parameters), scheduling information, grants, and / or assignments of REs for DL ​​transmissions and UL transmissions. The PDCCH may also carry HARQ feedback transmissions, such as acknowledgements (ACKs) or negative acknowledgements (NACKs). HARQ is a technique well known to those of ordinary skill in the art, wherein the integrity of packet transmissions may be checked for accuracy at the receiving side, for example, using any suitable integrity checking mechanism, such as a checksum or a cyclic redundancy check (CRC). If the integrity of the transmission is confirmed, an ACK may be sent, and if it is not confirmed, a NACK may be sent. In response to the NACK, the sending device may transmit a HARQ retransmission, which may implement trace combining, incremental redundancy, and the like.

[0082] The base station may also allocate one or more REs 306 (e.g., in the control region 312 or the data region 314) to carry other DL signals, such as a demodulation reference signal (DMRS); a phase tracking reference signal (PT-RS); a channel state information (CSI) reference signal (CSI-RS); and a synchronization signal block (SSB). The SSBs may be broadcast at regular intervals based on a periodicity (e.g., 5ms, 10ms, 20ms, 40ms, 80ms, or 160ms). The SSBs include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast control channel (PBCH). The UE may utilize the PSS and SSS to achieve radio frame, subframe, time slot, and symbol synchronization in the time domain, to identify the center of the channel (system) bandwidth in the frequency domain, and to identify the physical cell identity (PCI) of the cell.

[0083] The PBCH in the SSB may also include a master information block (MIB) containing various system information and parameters for decoding a system information block (SIB). The SIB may be, for example, SystemInformationType 1 (SIB1), which may include various additional system information. The MIB and SIB1 together provide minimum system information (SI) for initial access. Examples of system information sent in the MIB may include, but are not limited to, subcarrier spacing (e.g., default downlink parameter set), system frame number, configuration of the PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), cell barring indicator, cell reselection indicator, grid offset, and search space for SIB1. Examples of remaining minimum system information (RMSI) sent in SIB1 may include, but are not limited to, random access search space, paging search space, downlink configuration information, and uplink configuration information. The base station may also send other system information (OSI).

[0084] In an UL transmission, a scheduled entity (e.g., a UE) may utilize one or more REs 306 to a scheduling entity to carry UL control information (UCI) including one or more UL control channels, such as a physical uplink control channel (PUCCH). The UCI may include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. Examples of uplink reference signals may include a sounding reference signal (SRS) and an uplink DMRS. In some examples, the UCI may include a scheduling request (SR), i.e., a request to a scheduling entity to schedule an uplink transmission. In this document, in response to the SR sent on the UCI, the scheduling entity may send downlink control information (DCI), which may schedule resources for uplink packet transmissions. The UCI may also include HARQ feedback, channel state feedback (CSF) (such as a CSI report), or any other suitable UCI.

[0085] In addition to control information, one or more REs 306 (e.g., within the data region 314) may also be allocated for data traffic. Such data traffic may be carried on one or more traffic channels, such as for DL ​​transmissions, on a physical downlink shared channel (PDSCH); or for UL transmissions, on a physical uplink shared channel (PUSCH). In some examples, one or more REs 306 within the data region 314 may be configured to carry other signals (such as one or more SIBs and DMRS). In some examples, the PDSCH may carry multiple SIBs, not limited to the SIB1 discussed above. For example, OSI may be provided in these SIBs (e.g., SIB2 and above SIBs).

[0086] In an example of sidelink communication on a sidelink carrier via a proximity service (ProSe) PC5 interface, a control region 312 of a time slot 310 may include a physical sidelink control channel (PSCCH) including sidelink control information (SCI) sent by an initiating (transmitting) sidelink device (e.g., a Tx V2X device or other Tx UE) toward a set of one or more other receiving sidelink devices (e.g., an Rx V2X device or other Rx UE). A data region 314 of the time slot 310 may include a physical sidelink shared channel (PSSCH) including sidelink data traffic sent by an initiating (transmitting) sidelink device within resources reserved by the transmitting sidelink device via the SCI on the sidelink carrier. Other information may also be sent via various REs 306 within the time slot 310. For example, HARQ feedback information may be sent from a receiving sidelink device to a transmitting sidelink device in a physical sidelink feedback channel (PSFCH) within the time slot 310. Additionally, one or more reference signals, such as a sidelink SSB, a sidelink CSI-RS, a sidelink SRS, and / or a sidelink positioning reference signal (PRS), may be sent within time slot 310 .

[0087] These physical channels described above are typically multiplexed and mapped to transport channels for processing at the medium access control (MAC) layer. The transport channels carry blocks of information called transport blocks (TBs). Based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission, the transport block size (TBS), which may correspond to the number of information bits, may be a controlled parameter.

[0088] Figure 3 The channels or carriers illustrated in the figure are not necessarily all channels or carriers that can be utilized between devices, and a person of ordinary skill in the art will recognize that other channels or carriers may be utilized in addition to those illustrated, such as other traffic channels, control channels, and feedback channels.

[0089] The deployment of a communication system (such as a 5G New Radio (NR) system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS) or one or more units (or one or more components) performing base station functionality) can be implemented in a clustered or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB (gNB), an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as a clustered base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0090] A clustered base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0091] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0092] Figure 4 A diagram illustrating an example decomposed base station 400 architecture is shown. The decomposed base station 400 architecture may include one or more central units (CUs) 410 that may communicate directly with a core network 420 via a backhaul link, or indirectly with the core network 420 through one or more decomposed base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 425 via an E2 link, or a non-real-time (non-RT) RIC 415 associated with a service management and orchestration (SMO) framework 405, or both. The CU 410 may communicate with one or more distributed units (DUs) 430 via respective midhaul links, such as an F1 interface. The DU 430 may communicate with one or more radio units (RUs) 440 via respective fronthaul links. The RU 440 may communicate with respective UEs 450 via one or more radio frequency (RF) access links. In some implementations, a UE 450 may be served simultaneously by multiple RUs 440.

[0093] Each of the units (i.e., CU 410, DU 430, RU 440, and near-RT RIC 425, non-RT RIC 415, and SMO framework 405) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, a unit may include a wired interface configured to receive or send signals to one or more of the other units on a wired transmission medium. Additionally, a unit may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) configured to receive or send signals or both to one or more of the other units on a wireless transmission medium.

[0094] In some aspects, CU 410 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 configured to communicate signals with other control functions hosted by CU 410. CU410 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 410 may be logically split 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, CU 410 may be implemented to communicate with DU 430 for network control and signaling.

[0095] DU 430 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 440. In some aspects, DU 430 may host one or more of the following: a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling or modulation and demodulation, etc.) at least in part according to a functional partitioning such as that defined by the Third Generation Partnership Project (3GPP). In some aspects, DU 430 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 430 or with control functions hosted by CU 410.

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

[0097] The SMO framework 405 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 405 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 405 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 490) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 410, DU 430, RU 440, and near-RT RIC 425. In some specific implementations, the SMO framework 405 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 411) via the O1 interface. Additionally, in some specific implementations, the SMO framework 405 may communicate directly with one or more RUs 440 via the O1 interface. The SMO framework 405 may also include a non-RT RIC 415 configured to support the functionality of the SMO framework 405 .

[0098] The non-RT RIC 415 may be configured to include logic functions that implement 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 425. The non-RT RIC 415 may be coupled to or communicate with the near-RT RIC 425 (such as via an A1 interface). The near-RT RIC 425 may be configured to include logic functions that implement near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 410, one or more DUs 430, or both, and the O-eNB with the near-RT RIC 425.

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

[0100] Figure 5 is a schematic diagram illustrating an example of IAB node functionality within an IAB network 500. Figure 5 In the example shown, the IAB node 502 is shown as being coupled to the core network 504 via a wired connection. The IAB node 502 may be referred to herein as an IAB donor node, which may be, for example, a clustered or decomposed enhanced gNB including functionality for controlling the IAB network 500. In some examples, the IAB donor node 502 may include a central unit (CU) 506 and a distributed unit (DU) 508. The CU 506 is configured to operate as a centralized network node (or central entity) within the IAB network 500. For example, the CU 506 may include radio resource control (RRC) layer functionality and packet data convergence protocol (PDCP) layer functionality to control / configure other nodes (e.g., IAB nodes and UEs) within the IAB network 500. Therefore, the CU 506 may be configured to implement centralized mechanisms for handover decisions, topology changes, routing, bearer mapping, UE security, and other suitable services.

[0101] The DU 508 is configured to operate as a scheduling entity to schedule scheduled entities (e.g., other IAB nodes and UEs) of the IAB donor node 502. For example, the DU 508 of the IAB donor node 502 may operate as a scheduling entity to schedule the IAB nodes 510 and 512 and the UEs 514 and 516. Thus, the DU 508 of the IAB donor node 502 may schedule communications with the IAB nodes 510 and 512 via respective backhaul links, and schedule communications with the UEs 514 and 516 via respective access links. In some examples, the DU 508 may include radio link control (RLC), medium access control (MAC), and physical (PHY) layer functionality to enable operation as a scheduling entity.

[0102] Each of the IAB nodes 510 and 512 may be configured as a layer 2 (L2) relay node including a corresponding DU 520 and a mobile terminal (MT) unit 518, so that each L2 relay IAB node 510 and 512 can operate as a scheduling entity and a scheduled entity. For example, the MT unit 518 within each of the L2 relay IAB nodes 510 and 512 is configured to operate as a scheduled entity that can be scheduled by the IAB donor node 502. Each MT unit 518 within the L2 relay IAB nodes 510 and 512 further facilitates communication with the IAB donor node 502 via a corresponding backhaul link. In addition, the DU 520 within each of the L2 relay IAB nodes 510 and 512 operates similarly to the DU 508 within the IAB donor node 502 to serve as a scheduling entity to schedule one or more corresponding scheduled entities (e.g., other IAB nodes and / or UEs) of the L2 relay IAB nodes 510 and 512.

[0103] For example, the DU 520 of the L2 relay IAB node 512 serves as a scheduling entity to schedule communication with the UE 522 via the access link, while the DU 520 of the L2 relay IAB node 510 serves as a scheduling entity to schedule communication with the MT unit 518 of the L2 relay IAB nodes 524 and 526 via the corresponding backhaul link and communication with the UE 528 via the access link. Each of the L2 relay IAB nodes 524 and 526 also includes a corresponding DU 520, which serves as a scheduling entity to communicate with the corresponding UEs 530 and 532.

[0104] In some examples, the IAB donor node 502, in combination with each of the L2 relay IAB nodes 510, 512, 524, and 526, may together form a decomposed base station. The decomposed base station includes a CU 506 and each of the DUs 508 and 520 controlled by the CU 506. The CU / DU functional division in the decomposed base station may facilitate the implementation of time-critical services, such as scheduling, retransmission, segmentation, and other similar services in the DUs 508 / 520, while concentrating less time-critical services in the CU 506. In addition, the CU / DU separation enables the termination of external interfaces in the CU 506 instead of in each DU, and further supports centralized termination of the PCDP to allow dual connectivity and handover between different DUs of the decomposed base station. It should be understood that the decomposed base station may be implemented in a network other than an IAB network, and the present disclosure is not limited to any particular type of network.

[0105] In some aspects of the present disclosure, a network entity and / or a UE may be configured for beamforming techniques. Figure 6An example of a wireless communication system supporting beamforming between a network entity 602 and a UE 604 is illustrated. In the beamforming system, the network entity 602 includes multiple antennas 610. The use of such multiple antenna technology enables the wireless communication system to utilize the spatial domain to support spatial multiplexing, beamforming, and transmit diversity.

[0106] Beamforming is a signal processing technique that can be used at the network entity 602 and the UE 604 to shape or direct an antenna beam (e.g., a transmit beam or a receive beam) along a spatial path between the network entity 602 and the UE 604. Beamforming can be achieved by combining signals communicated via antennas 610 (e.g., antenna elements of an antenna array or antenna panel) so that some of these signals experience constructive interference and other signals experience destructive interference. In order to produce the desired constructive / destructive interference, the network entity 602 can apply amplitude and / or phase offsets to the signals transmitted or received from each of the antennas 610. The UE 604 can also be configured with one or more beamforming antennas 612 (e.g., antenna panels) to transmit and / or receive beamformed signals to and / or from the network entity 602.

[0107] exist Figure 6 In the example shown, the network entity 602 may be able to generate one or more transmit / receive beams 606a-606e, each transmit / receive beam being associated with a different spatial direction. In addition, the UE 604 may be configured to generate multiple transmit / receive beams 608a-608e, each transmit / receive beam being associated with a different spatial direction. It should be noted that although some beams are shown as being adjacent to each other, such an arrangement may be different in different aspects. For example, the network entity 602 and the UE 604 may each transmit more or less beams distributed in all directions (e.g., 350 degrees) and in three dimensions.

[0108] The network entity 602 is typically capable of communicating with the UE 604 using beams of different beam widths. In some examples, in order to select a specific beam for communicating with the UE 604, the network entity 602 may transmit a reference signal, such as an SSB or a CSI-RS, on each of a plurality of beams (e.g., beams 606a-606e) in a beam scanning manner. In some examples, the SSB may be transmitted on a wider beam, while the CSI-RS may be transmitted on a narrower beam. The UE 604 may measure a reference signal received power (RSRP) or a signal to interference plus noise ratio (SINR) on each of these beams, and send a beam measurement report (e.g., a layer 1 (L1) measurement report) indicating the RSRP or SINR of one or more measured beams to the network entity 602. The network entity 602 may then select a specific beam for communicating with the UE 604 based on the L1 measurement report.

[0109] To facilitate transmission and measurement of reference signals (e.g., SSBs), the network entity 602 and the UE 604 may be configured (e.g., via a central network entity such as a CU) with an SSB measurement time configuration (SMTC) window and an SSB transmission configuration (STC) window that are aligned with a periodicity (e.g., 20 ms) of SSB transmissions on an access link between the network entity 602 and the UE 604. The STC window and the SMTC window may be configured at a network level such that each network entity 602 and the UE 604 within the network operates using the same STC window and the SMTC window. The STC window indicates a time period (e.g., one or more time slots, subframes, or frames) within which the network entity 602 may transmit SSBs (e.g., a set of SSB bursts including multiple SSBs transmitted in a beam scanning manner), the SSBs typically being transmitted on a raster frequency (e.g., a synchronization raster) that indicates a frequency position of the SSBs that may be used by the UE 604 for system acquisition when the SSB position is unknown. The SMTC window is aligned with the STC window to enable the UE 604 to measure the SSBs sent from the network entity 602.

[0110] In an example where UE 604 is an IAB node including a DU and an MT unit, UE 604 will need to send an SSB to a UE served by the IAB node and receive an SSB from an IAB parent node (such as network entity 602). Therefore, in this example, multiple STCs and corresponding SMTC windows may be configured for the IAB network. Each IAB node may be configured with a corresponding set of STC windows and SMTC windows, wherein the STC windows and SMTC windows are not aligned. In contrast, the SMTC window utilized by the IAB MT unit may be aligned with the STC window of an adjacent IAB node so that the IAB MT unit may receive and measure the SSB of an adjacent IAB DU. The exchanged SSBs may be used, for example, to mitigate or minimize cross-link interference (CLI) between adjacent IAB DUs. For example, the IAB MT unit 604 may obtain a CLI measurement indicating the CLI between the IAB MT unit 604 and the network entity 602 based on one or more SSBs sent by the network entity 602 during the STC window of the network entity 602 aligned with the SMTC window of the IAB MT unit 604. The IAB MT unit 604 may then generate a CLI measurement report and send it to, for example, a central network entity (e.g., a CU, a real-time or non-real-time intelligent controller, or a core network node, such as an operations, administration, and maintenance (OAM) function) to enable the central network entity to minimize or reduce the CLI between the network entities 602 and 604.

[0111] CLI may occur when one network entity is transmitting while another adjacent network entity is receiving in the same frequency band at the same time. For example, in a dynamic TDD network configuration where uplink transmission and downlink transmission can be dynamically scheduled based on the traffic load in the cell, one network entity may schedule downlink transmission while another adjacent network entity schedules uplink transmission, which may result in CLI. In addition, in a full-duplex configuration where downlink transmission may be performed by one antenna panel (e.g., DL antenna panel) on the network entity and uplink reception may be performed by another antenna panel (e.g., UL antenna panel) on the network entity, adjacent network entities may transmit and receive simultaneously, which may result in CLI. Transmissions between network entities are typically performed at higher power and with better propagation conditions than the link between the network entity and the UE. Therefore, the cross-link interference experienced at the network entity may be more significant than the cross-link interference experienced at the UE. In order to minimize CLI between network entities, the central network entity may synchronize uplink and downlink communications between adjacent network entities.

[0112] However, in examples where one or more of the network entities are mobile network entities (such as mobile IAB nodes), coordinated inter-network entity CLI measurements may not be possible due to the mobility of the network entities. Figure 7 7 is a diagram illustrating cross-link interference (CLI) in a wireless communication network 700 according to some aspects. Figure 7 In the illustrated example, mobile network entity 702 is in wireless communication with UE 704, and mobile network entity 706 is in wireless communication with UE 708. Additionally, stationary (static) network entity 710 is in wireless communication with UE 712. Each of network entities 702, 706, and 710 may be a clustered network entity or a decomposed network entity.

[0113] In some examples, the network entities 702, 706, and 710 may be half-duplex network entities (e.g., network entities implementing dynamic TDD) or full-duplex network entities. In addition, one or more mobile network entities (e.g., network entity 702) may be configured with different uplink / downlink (UL / DL) configurations than other mobile network entities 706 and / or stationary network entity 710. The different UL / DL configurations may be a result of, for example, the mobility of the mobile network entities 702 and 706. In addition, the mobility of the mobile network entities 702 and 706 may place the mobile network entities 702 and 706 in close proximity to each other and to the stationary network entity 710.

[0114] like Figure 7 As shown, the mobile network entity 702 may transmit a downlink transmission 714 to the UE 704 using the selected (scheduled) frequency resources (e.g., one or more subcarriers in a frequency band) and time resources (e.g., symbols, time slots, subframes, etc.). In addition, the mobile network entity 706 may receive an uplink transmission 716 from the UE 708 on the same time resources in the same frequency band (e.g., on the same or adjacent subcarriers / channels). Since the downlink transmission 714 to the UE 704 and the uplink transmission 716 from the UE 708 occur simultaneously on the same frequency band, the mobile network entity 706 may experience a CLI 718 between the downlink transmission 714 and the uplink transmission 716 due to the proximity of the mobile network entities 702 and 706. In addition, the stationary network entity 710 may also receive an uplink transmission 720 from the UE 712 on the same time resources in the same frequency band as the downlink transmission 714. Thus, due to the proximity of the mobile network entity 702 and the stationary network entity 710 , the stationary network entity 710 may also experience a CLI 722 between the downlink transmission 714 and the uplink transmission 720 .

[0115] In this example, the central network entity may not be able to configure separate STC / SMTC windows to each of the network entities 702, 706, and 710 in order to mitigate CLI due to the mobility of the network entities 702 and 706. For example, the central network entity may not be aware of the neighboring network entities (e.g., network entities 706 and 710) of the mobile network entity 702, and therefore may not be able to configure the inter-network entity CLI Tx / Rx windows (e.g., STC windows and SMTC windows) to avoid conflicts with the neighboring network entities.

[0116] Various aspects of the present disclosure relate to techniques for providing and utilizing a common window configuration for mobile network entities (e.g., network entities 702 and 706). The common window configuration may include multiple opportunities within a corresponding window for each of one or more periods for communicating reference signals (e.g., SSBs) between network entities. Within the window, the network entity may select one of these opportunities to send a reference signal and may listen in the remaining opportunities to receive reference signals from neighboring network entities. By providing such a common window configuration, CLI measurements between mobile network entities and between mobile network entities and stationary network entities may be performed. Therefore, mitigation measures may be taken to reduce the CLI experienced by network entities 702, 706, and 710, thereby improving reliability, reducing resource usage (e.g., due to multiple retransmissions), and extending battery life of UEs and mobile network entities (e.g., by reducing the number of retransmissions that may be required based on the CLI).

[0117] Fig. 8A 800 is a diagram illustrating an example of a wireless communication network 800 that provides a common window configuration according to some aspects. The wireless communication network 800 includes a central network entity 802, mobile network entities 804 and 806, and a stationary network entity 808. The central network entity 802 may correspond to, for example, Figure 4 The CU shown is either a real-time or non-real-time intelligent controller or Figure 5 CU shown. Central network entity 802 may also correspond to a core network node, such as an OAM function. Each of network entities 804, 806, and 808 may be a clustered network entity or a decomposed network entity (e.g., one or more entities that may include a decomposed base station) and / or may be an IAB node.

[0118] According to some aspects, the central network entity 802 may generate a common window configuration 810 and provide it to each of the network entities 804, 806, and 808. For example, the central network entity 802 may provide the common window configuration 810 to the stationary network entity 808 via a midhaul link or a backhaul link. In addition, the central network entity 802 may provide the common window configuration 810 to the mobile network entities 804 and 806 via one or more additional aggregated / decomposed network entities (e.g., via midhaul / backhaul links) and wireless communication links between the mobile network entities 804 and 806 and the additional network entities (e.g., the stationary network entity 808). In some examples, the central network entity 802 may provide the common window configuration 810 to the network entities 804, 806, and 808 via a radio resource control (RRC) message. The common window configuration 810 may be periodic, aperiodic, semi-persistent, or event-triggered.

[0119] Figure 8B An example of a common window configuration 810 according to some aspects is illustrated. The common window configuration 810 includes a configuration of one or more cycles 812. Each cycle 812 includes a corresponding window 814, which includes multiple opportunities 816, during which reference signals (e.g., SSBs) can be communicated. The common window configuration can also be configured with a window periodicity corresponding to a cycle duration (e.g., 20ms). In one example, each window 814 can correspond to 5ms of a 20ms cycle 812. Each opportunity 816 can correspond to one or more consecutive symbols of a time slot in, for example, a window 814.

[0120] Fig. 8A The network entities 804, 806 and 808 shown may use Figure 8B The common window configuration 810 is shown to communicate reference signals therebetween in order to measure the CLI between the network entities 804, 806, and 808. For example, a mobile network entity (e.g., mobile network entity 806) may select one of the opportunities 816 (e.g., a first opportunity) at which to send a reference signal 820a (e.g., an SSB), and may then listen on the remaining opportunities 816 to receive the SSB from other neighboring mobile network entities. In addition, the mobile network entity 804 may select a different opportunity (e.g., a second opportunity) at which to send a reference signal 820b (e.g., an SSB), and may then listen on the remaining opportunities 816 to receive the SSB from other neighboring mobile network entities.

[0121] For example, the mobile network entity 804 may receive a reference signal 820a from the mobile network entity 806 on a first opportunity. The mobile network entity 804 may then obtain a CLI measurement based on the reference signal 820a, and generate and send a CLI measurement report 822a to the central network entity 802 for CLI mitigation. For example, the central network entity 802 may be configured to coordinate downlink transmissions and uplink transmissions between neighboring network entities 804, 806, and 808 that experience high CLI to reduce or eliminate CLI. In some examples, the mobile network entity 804 may generate the CLI measurement report 822a in response to the CLI measurement being greater than a threshold. The threshold may be pre-configured (e.g., via an original equipment manufacturer (OEM) based on one or more standards and / or specifications) or may be provided by the central network entity 802.

[0122] In addition, the stationary network entity 808 may listen during the opportunity 816 to receive reference signals from the neighboring mobile network entities 804 and 806. For example, the stationary network entity 808 may receive the reference signal 820b from the mobile network entity 804 at the second opportunity. The stationary network entity 808 may then obtain a CLI measurement based on the reference signal 820b, and generate a CLI measurement report 822b and send it to the central network entity 802 for CLI mitigation. In some examples, the stationary network entity 808 may generate the CLI measurement report 822b in response to the CLI measurement being greater than a threshold. The threshold used by the stationary network entity 808 may be the same as the threshold used by the mobile network entities 804 and 806, or may be a different threshold configured for the stationary network entity 808.

[0123] Fig. 9 is a diagram illustrating exemplary signaling between a central network entity 902 and mobile network entities 904 and 906 for CLI measurements using a common window configuration in accordance with some aspects. The central network entity 902 may correspond to, for example, Figure 4 The CU shown is either a real-time or non-real-time intelligent controller or Figure 5 CU shown. The central network entity 902 may also correspond to a core network node, such as an OAM function. Each of the mobile network entities 904 and 906 (a first mobile network entity and a second mobile network entity) may be a clustered network entity or a decomposed network entity (e.g., one or more entities that may include a decomposed base station) and / or may be an IAB node.

[0124] At 908, the central network entity 902 may provide a common window configuration for the mobile network entities 904 and 906 to communicate reference signals for CLI measurement and reporting. For example, the common window configuration may include multiple opportunities (e.g., N opportunities) within each corresponding window of one or more periods, at which reference signals (e.g., SSBs) may be transmitted / received. In addition, the common window configuration may be a periodic window configuration (e.g., having a window periodicity corresponding to the period duration), an aperiodic window configuration (e.g., dynamically configured for one or more periods), or an event-triggered window configuration (e.g., after an event occurs, the network entities 904 and 906 may begin using the common window configuration to communicate reference signals for CLI measurements). For example, the event may correspond to a request from a neighboring network entity to exchange reference signals for CLI measurements. As another example, the event may correspond to a threshold number of packets dropped due to interference.

[0125] At 910, the first mobile network entity 904 may select a first opportunity from a plurality of opportunities and send a reference signal (e.g., SSB) within the selected first opportunity. In some examples, the first mobile network entity 904 may randomly select the first opportunity per cycle or per group of cycles. For example, the first mobile network entity 904 may randomly select a first opportunity within a first cycle, and then randomly select another opportunity within a second cycle. For another example, the first mobile network entity 904 may randomly select a first opportunity for sending a reference signal within a group of cycles including the first cycle. For example, the group of cycles may correspond to a subset of a plurality of cycles (e.g., a number of consecutive cycles in a plurality of cycles).

[0126] In some examples, the first mobile network entity 904 may sense the first opportunity of one or more cycles to determine whether the first opportunity is available for use by the first mobile network entity 904 (e.g., in response to the first opportunity not being used by another neighboring network entity, the first opportunity may be considered available). Then, in response to determining that the first opportunity is available, the first mobile network entity 904 may select the first opportunity to send a reference signal.

[0127] In some examples, the first mobile network entity 904 may use the first transmit beam to transmit the reference signal. In some examples, the first mobile network entity 904 may use a different corresponding transmit beam (e.g., such as a first transmit beam) among the plurality of transmit beams on the first mobile network entity 904 for each period or each group of a plurality of periods (e.g., a subset of a plurality of periods). Figure 6For example, the first mobile network entity 904 may use a first transmit beam to transmit a reference signal in a first period (e.g., a first window of the first period), and then use a second transmit beam to transmit a reference signal in a second window of a second period. For another example, the first mobile network entity 904 may use a first transmit beam to transmit a reference signal in a first group of periods (or a subset of periods) (e.g., within a corresponding window of each period in the first group of periods), and then use a second transmit beam to transmit a reference signal in a second group of periods (or a subset of periods).

[0128] Similarly, the second mobile network entity 906 may use a receive beam to receive a reference signal from the first mobile network entity 904. In some examples, the second mobile network entity 906 may use a different corresponding receive beam (e.g., such as a plurality of receive beams) in the plurality of receive beams on the second mobile network entity 906 for each period or each group of a plurality of periods (e.g., a subset of a plurality of periods). Figure 6 As shown) to receive a reference signal from the first mobile network entity 904.

[0129] At 914, the second mobile network entity 906 may obtain a CLI measurement based on the reference signal. For example, the second mobile network entity 906 may obtain a reference signal received power (RSRP) or a signal to interference plus noise ratio (SINR) of the reference signal. At 914, the second mobile network entity 906 may then send a CLI measurement report including the CLI measurement to the central network entity 902. In some examples, the second mobile network entity 906 may send the CLI measurement report in response to the CLI measurement being greater than a threshold (e.g., indicating that the CLI may prevent the second mobile network entity 906 from decoding uplink transmissions from the UE or child IAB node).

[0130] At 916, the second mobile network entity 906 may select a second opportunity from a plurality of opportunities and send a reference signal (e.g., SSB) within the selected first opportunity. In some examples, the second mobile network entity 906 may randomly select the first opportunity per cycle or per group of cycles. For another example, before selecting the second opportunity, the second mobile network entity 906 may sense the second opportunity of one or more cycles to determine whether the first opportunity is available for use by the second mobile network entity 906 (e.g., whether the first opportunity is not used by another network entity to send a reference signal). The first mobile network entity 904 may listen during the second opportunity to receive a reference signal from the second mobile network entity 906. For example, at 910, the first mobile network entity may select opportunity 1 to send a reference signal, and then may listen to the remaining N-1 opportunities to discover reference signals from other neighboring mobile network entities. Similarly, the second mobile network entity 906 may select opportunity 2 to send a reference signal, and then may listen to opportunity 1 and the remaining N-2 opportunities to discover reference signals from other neighboring mobile network entities.

[0131] The second mobile network entity 906 may also transmit a reference signal using the transmit beam selected on the second mobile network entity. In addition, the first mobile network entity 904 may receive a reference signal from the second mobile network entity using the receive beam selected on the first mobile network entity 904. The transmit beam and the receive beam may vary per cycle or per group of multiple cycles.

[0132] At 918, the first mobile network entity 904 may obtain a CLI measurement (e.g., RSRP or SINR) based on the reference signal. At 920, the first mobile network entity 904 may then send a CLI measurement report including the CLI measurement to the central network entity 902. In some examples, the first mobile network entity 904 may send the CLI measurement report in response to the CLI measurement being greater than a threshold. The threshold may be pre-configured on the mobile network entities 904 and 906 or provided by the central network entity 902.

[0133] In some examples, each of the first mobile network entity 904 and the second mobile network entity 906 may be configured with different window periodicities based on the common window periodicity of the corresponding window of one or more periods indicated by the common window configuration. For example, the central network entity may configure the common window configuration using the common window periodicity. Each mobile network entity may send a reference signal using a common window periodicity or a multiple of the common window periodicity. For example, the common window periodicity may be K ms, the first mobile network entity 904 may use a window periodicity of 2K ms, and the second mobile network entity 906 may use a window periodicity of 3K ms. By assigning different periodicities to different mobile network entities, the number of mobile network entities using the common window configuration may be increased and / or the potential for reference signal conflicts between mobile network entities may be minimized. In some examples, the mobile network entities may determine their corresponding periodicities based on one or more factors (e.g., the speed of the mobile network entity, rules defined in the 3GPP standard or specification, etc.). In this example, the mobile network entities may provide their corresponding window periodicities to other neighboring mobile network entities, or the mobile network entities may sense the corresponding window periodicities. In other examples, the central network entity may configure a respective window periodicity for each mobile network entity and explicitly indicate the window periodicity to the respective mobile network entity or to the respective mobile network entity and one or more neighboring network entities.

[0134] Fig.10 is a flow chart illustrating an exemplary process 1000 for performing CLI measurements using a common window configuration according to some aspects. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for implementations of all embodiments. In some examples, process 1000 may consist of Fig.18 The process 1000 is performed by the network entity 1800 (eg, a mobile network entity) illustrated in FIG. In some examples, the process 1000 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0135] At block 1002, a mobile network entity may receive a common window configuration for the mobile network entity, the common window configuration comprising a plurality (e.g., N) of opportunities within a corresponding window for each of one or more periods. The mobile network entity may receive the common window configuration from a central network entity. In some examples, the common window configuration may be periodic, aperiodic, semi-persistent, or event-triggered.

[0136] At block 1004, the mobile network entity may select one of the N opportunities (e.g., a first opportunity) to send a reference signal. For example, the mobile network entity may randomly select an opportunity from a plurality of opportunities to send a reference signal. In some examples, the mobile network entity may use the selected opportunity to send a reference signal in each of the one or more cycles or in a subset of the one or more cycles. In some examples, the mobile network entity may sense an opportunity of at least one of the one or more cycles to determine whether the opportunity is available, and may select the opportunity to send a reference signal in response to determining that the opportunity is available.

[0137] At block 1006, the mobile network entity may then transmit a reference signal (e.g., SSB) within the selected opportunity (e.g., the first opportunity). In some examples, the mobile network entity may transmit the reference signal using a transmit beam. In some examples, the mobile network entity may transmit the reference signal using a different corresponding transmit beam of a plurality of transmit beams of the mobile network entity for each of the one or more periods or for each group of a plurality of periods in the one or more periods.

[0138] At block 1008, the mobile network entity may listen to reference signals sent by the neighboring network entity in the remaining N-1 occasions. In some examples, the mobile network entity may listen to additional reference signals from neighboring mobile network entities in the plurality of mobile network entities during the remaining occasions in the plurality of occasions in each of the one or more cycles.

[0139] Fig.11 is a flow chart illustrating another exemplary process 1100 for performing CLI measurements using a common window configuration according to some aspects. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for implementations of all embodiments. In some examples, process 1100 may be performed by Fig.18 The process 1100 is performed by the network entity 1800 (eg, a mobile network entity) illustrated in FIG. In some examples, the process 1100 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0140] At block 1102, a mobile network entity may receive a common window configuration for the mobile network entity, the common window configuration comprising a plurality (e.g., N) of opportunities within a corresponding window for each of one or more periods. The mobile network entity may receive the common window configuration from a central network entity. In some examples, the common window configuration may be periodic, aperiodic, semi-persistent, or event-triggered.

[0141] At block 1104, the mobile network entity may select a first opportunity from the N opportunities to send a reference signal. For example, the mobile network entity may randomly select a first opportunity from the plurality of opportunities to send a reference signal. In some examples, the mobile network entity may use the selected first opportunity to send a reference signal in each of the one or more cycles or in a subset of the one or more cycles. In some examples, the mobile network entity may sense a first opportunity of at least one of the one or more cycles to determine whether the first opportunity is available, and may select the first opportunity to send a reference signal in response to determining that the first opportunity is available.

[0142] At block 1106, the mobile network entity may then transmit a first reference signal (e.g., SSB) within the selected first opportunity. In some examples, the mobile network entity may transmit the first reference signal using a transmit beam. In some examples, the mobile network entity may transmit the first reference signal using a different corresponding transmit beam of a plurality of transmit beams of the mobile network entity for each of the one or more cycles or for each group of multiple cycles in the one or more cycles.

[0143] At block 1008, the mobile network entity may receive a second reference signal from a neighboring mobile network entity in a second opportunity in the N opportunities. In some examples, the mobile network entity may receive the second reference signal using a receive beam. In some examples, the mobile network entity may receive the second reference signal using a different corresponding receive beam in a plurality of receive beams of the mobile network entity for each of the one or more periods or for each group of a plurality of periods in the one or more periods.

[0144] At block 1110, the mobile network entity may obtain a CLI measurement indicating cross link interference (CLI) between the mobile network entity and a neighboring mobile network entity based on the second reference signal. For example, the CLI measurement may be an RSRP or SINR measurement. In some examples, the mobile network entity may also send a CLI measurement report including the CLI measurement to the central network entity (e.g., when the CLI measurement is greater than a threshold). In other examples, the mobile network entity may utilize the CLI measurement to perform a CLI mitigation technique (e.g., by selecting a transmit / receive beam with the lowest CLI) to reduce the CLI between the mobile network entity and the neighboring mobile network entity.

[0145] Fig.12is a flow chart illustrating another exemplary process 1200 for performing CLI measurements using a common window configuration according to some aspects. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for implementations of all embodiments. In some examples, process 1200 may be performed by Fig.18 The process 1200 is performed by the network entity 1800 (eg, a mobile network entity) illustrated in FIG. In some examples, the process 1200 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0146] At block 1202, a mobile network entity may receive a common window configuration for the mobile network entity, the common window configuration comprising a plurality (e.g., N) of opportunities within a corresponding window of each of a plurality of periods, the plurality of periods having a first periodicity of the corresponding windows of the one or more periods. The network entity may receive the common window configuration from a central network entity. In some examples, the common window configuration may be periodic, aperiodic, semi-persistent, or event-triggered.

[0147] At block 1204, the mobile network entity may identify a second periodicity that is a multiple of the first periodicity for sending the reference signal. For example, the central network entity may configure the common window configuration with a first periodicity of K ms. The mobile network entity may identify the second window periodicity as M*K, where M is greater than one. In some examples, the mobile network entity may determine the second periodicity based on the speed of the mobile network entity. For example, if the mobile network entity is traveling at a high speed, the mobile network entity may select a low value of M to generate a more frequent window periodicity (e.g., the second periodicity), and if the mobile network entity is traveling at a low speed, the mobile network entity may select a high value of M to generate a less frequent window periodicity (e.g., the second periodicity). In some examples, the mobile network entity may select the second periodicity based on an OEM configuration (e.g., based on one or more standards or specifications) or based on an explicit indication of the second periodicity received by the mobile network entity (e.g., from the central network entity).

[0148] At block 1206, the mobile network entity may select one of N opportunities within the available window based on the second periodicity to send a reference signal. For example, the mobile network entity may use the window to select an opportunity every M*K ms. In some examples, the mobile network entity may randomly select an opportunity from multiple opportunities within the available window to send a reference signal. In some examples, the mobile network entity may use the selected opportunity to send a reference signal within each available window or within a subset of the available windows based on the second periodicity. In some examples, the mobile network entity may sense the opportunity of at least one window based on the second periodicity to determine whether the opportunity is available, and may select the opportunity to send a reference signal in response to determining that the opportunity is available.

[0149] At box 1208, the mobile network entity may then send a reference signal (e.g., SSB) within the selected opportunity. In some examples, the mobile network entity may use a transmit beam to send the reference signal. At 1210, the mobile network entity may listen to the reference signal sent by the neighboring network entity in the remaining N-1 opportunities. The mobile network entity may also listen to and receive the reference signal sent by the neighboring network entity based on the corresponding periodicity of each neighboring network entity in other neighboring network entities. For example, the neighboring network entity may be configured with a third window periodicity L*K, where L is greater than one and is the same as or different from M. In some examples, the network entity may receive the third window periodicity of the neighboring network entity from the central network entity or from the neighboring network entity itself.

[0150] At 1212, the mobile network entity may determine whether there are more periods in the one or more periods (e.g., based on whether the common window configuration is periodic, aperiodic, semi-persistent, or event-triggered). If there are more periods in the one or more periods (the "yes" branch of box 1212), at box 1214, the mobile network entity may determine whether the next period is a transmission period in which the mobile network entity may send a reference signal based on the second periodicity. If the next period is a transmission period (the "yes" branch of box 1214), the mobile network entity may select one of the N occasions to send the reference signal in the next period (e.g., a corresponding window of the next period). In some examples, the selected occasion may be the same occasion or may be a different occasion. In addition, the mobile network entity may select a transmission beam for sending the reference signal. In some examples, the transmission beam may be the same transmission beam or a different transmission beam.

[0151] Fig.13is a signaling diagram illustrating exemplary signaling between a central network entity 1302, a stationary network entity 1304, and a mobile network entity 1306 for performing CLI measurements at the stationary network entity 1304 using a common window configuration according to some aspects. The central network entity 1302 may correspond to, for example, Figure 4 The CU shown is either a real-time or non-real-time intelligent controller or Figure 5 CU shown. The central network entity 1302 may also correspond to a core network node, such as an OAM function. Each of the stationary network entity 1304 and the mobile network entity 1306 may be a clustered network entity or a decomposed network entity (e.g., one or more entities that may include a decomposed base station) and / or may be an IAB node.

[0152] At 1308, the central network entity 1302 may provide a common window configuration for a mobile network entity (e.g., mobile network entity 1306) to communicate a reference signal for CLI measurement and reporting. For example, the common window configuration may include a plurality of opportunities (e.g., N opportunities) within each corresponding window of one or more periods, at which reference signals (e.g., SSB) may be transmitted / received. In addition, the common window configuration may be periodic, aperiodic, semi-persistent, or event-triggered.

[0153] At 1310, the mobile network entity 1306 may select a timing from a plurality of timings and transmit a reference signal (e.g., an SSB) during the selected timing. In some examples, the mobile network entity 1306 may randomly select a first timing per cycle or per group of cycles. In some examples, the mobile network entity 1306 may sense the timing of one or more cycles to determine whether the timing is available, and then select the timing to transmit the reference signal in response to determining that the first timing is available. In some examples, the mobile network entity 1306 may transmit the reference signal using a first transmit beam. In some examples, the mobile network entity 1306 may use a different corresponding transmit beam (e.g., such as a first transmit beam) from a plurality of transmit beams on the mobile network entity 1306 for each cycle or each group of multiple cycles (e.g., a subset of multiple cycles). Figure 6 As shown) to send a reference signal.

[0154] Similarly, the stationary network entity 1304 may use a receive beam to receive a reference signal from the mobile network entity 1306. In some examples, the stationary network entity 1304 may use a different corresponding receive beam (e.g., such as a plurality of receive beams) from the plurality of receive beams on the stationary network entity 1304 for each period or each group of multiple periods (e.g., a subset of multiple periods). Figure 6 ) to receive a reference signal from the mobile network entity 1306.

[0155] At 1312, the stationary network entity 1304 may obtain a CLI measurement based on the reference signal. For example, the stationary network entity 1304 may obtain a reference signal received power (RSRP) or a signal to interference plus noise ratio (SINR) of the reference signal. At 1314, the stationary network entity 1304 may then send a CLI measurement report including the CLI measurement to the central network entity 1302. In some examples, the stationary network entity 1304 may send the CLI measurement report in response to the CLI measurement being greater than a threshold.

[0156] Fig.14 is a flow chart illustrating an exemplary process 1400 for sending CLI measurements at a stationary network entity using a common window configuration according to some aspects. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for implementations of all embodiments. In some examples, process 1400 may be performed by Fig.18 The process 1400 is performed by the network entity 1800 (eg, a mobile network entity) illustrated in FIG. In some examples, the process 1400 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0157] At block 1402, a stationary network entity may receive a common window configuration for a mobile network entity, the common window configuration comprising a plurality (e.g., N) of opportunities within a corresponding window for each of one or more periods. The stationary network entity may receive the common window configuration from a central network entity. In some examples, the common window configuration may be periodic, aperiodic, semi-persistent, or event-triggered.

[0158] At block 1404, the stationary network entity may listen to a reference signal sent by a neighboring network entity during a common window. In some examples, the stationary network entity may listen to a corresponding window of each of one or more cycles. For example, the stationary network entity may listen at each of N opportunities during each common window in these common windows. In other examples, the common window configuration may include a first periodicity of a corresponding window of one or more cycles (e.g., a window periodicity corresponding to a cycle duration), and the neighboring mobile network entity may be configured with a second periodicity that is a multiple of the first periodicity. In this example, the stationary network entity may listen to the corresponding window within a selected period of one or more cycles based on a second periodicity associated with one or more cycles used by the neighboring mobile network entity to send a reference signal. In some examples, the stationary network entity may receive the second periodicity from the central network entity. In other examples, the stationary network entity may receive the second periodicity from the neighboring mobile network entity. If there are multiple neighboring mobile network entities, the stationary network entity may listen to the corresponding window within the selected period based on the corresponding second periodicity associated with each of these neighboring mobile network entities.

[0159] At block 1406, the stationary network entity may receive a reference signal from the neighboring mobile network entity (e.g., within an opportunity of a window listened to by the stationary network entity). In some examples, the stationary network entity may receive the reference signal using a receive beam. In some examples, the stationary network entity may receive the reference signal using a different corresponding receive beam of a plurality of receive beams of the stationary network entity for each of the one or more periods (e.g., based on a first periodicity or a second periodicity) or for each group of a plurality of periods in the one or more periods.

[0160] At block 1408, the stationary network entity may obtain a CLI measurement indicating cross link interference (CLI) between the stationary network entity and a neighboring mobile network entity based on the received reference signal. For example, the CLI measurement may be an RSRP or SINR measurement. At block 1410, the stationary network entity may also send a CLI measurement report including the CLI measurement to the central network entity. In some examples, the stationary network entity may send the CLI measurement report in response to the CLI measurement being greater than a threshold.

[0161] Fig.15is a flow chart illustrating an exemplary process 1500 for sending CLI measurements at a stationary network entity using a common window configuration according to some aspects. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for implementations of all embodiments. In some examples, process 1500 may be performed by Fig.18 The process 1500 is performed by the network entity 1800 (eg, a mobile network entity) illustrated in FIG. In some examples, the process 1500 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0162] At block 1502, a stationary network entity may receive a common window configuration for a mobile network entity, the common window configuration comprising a plurality (e.g., N) of opportunities within a corresponding window for each of one or more periods. The stationary network entity may receive the common window configuration from a central network entity. In some examples, the common window configuration may be periodic, aperiodic, semi-persistent, or event-triggered.

[0163] At block 1504, the stationary network entity may determine whether the stationary network entity has detected one or more reference signals transmitted by a neighboring mobile network entity during a common window. For example, the stationary network entity may be an IAB node with MT functionality or a stationary network entity with UE functionality that may detect reference signals (e.g., SSB) from neighboring network entities.

[0164] At block 1506, in response to detecting one or more reference signals sent by a neighboring mobile network entity during a common window, the stationary network entity may listen to the reference signal sent by the neighboring network entity during the common window. In some examples, the stationary network entity may listen to the corresponding window of each of the one or more cycles after detecting the reference signal. For example, the stationary network entity may listen at each of the N opportunities during each common window in these common windows. In other examples, the common window configuration may include a first periodicity of the corresponding window of one or more cycles (e.g., a window periodicity corresponding to the cycle duration), and the neighboring mobile network entity may be configured with a second periodicity that is a multiple of the first periodicity. In this example, the stationary network entity may listen to the corresponding window within a selected period of one or more cycles based on the second periodicity associated with the one or more cycles used by the neighboring mobile network entity to send the reference signal. In some examples, the stationary network entity may receive the second periodicity from the central network entity. In other examples, the stationary network entity may receive the second periodicity from the neighboring mobile network entity. If there are multiple neighboring mobile network entities, the stationary network entity may listen to a corresponding window within the selection period based on a corresponding second periodicity associated with each of the neighboring mobile network entities.

[0165] At block 1508, the stationary network entity may receive a reference signal from the neighboring mobile network entity (e.g., within an opportunity of a window listened to by the stationary network entity). In some examples, the stationary network entity may receive the reference signal using a receive beam. In some examples, the stationary network entity may receive the reference signal using a different corresponding receive beam of a plurality of receive beams of the stationary network entity for each of the one or more periods (e.g., based on a first periodicity or a second periodicity) or for each group of a plurality of periods in the one or more periods.

[0166] At block 1510, the stationary network entity may obtain a cross-link interference (CLI) measurement indicating a CLI between the stationary network entity and a neighboring mobile network entity based on the received reference signal. For example, the CLI measurement may be an RSRP or SINR measurement. At block 1512, the stationary network entity may also send a CLI measurement report including the CLI measurement to the central network entity. In some examples, the stationary network entity may send the CLI measurement report in response to the CLI measurement being greater than a threshold.

[0167] Fig.16is a flow chart illustrating an exemplary process 1600 for performing CLI measurements between a stationary network entity and a mobile network entity according to some aspects. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for implementations of all embodiments. In some examples, the process 1600 may be performed by Fig.18 The process 1600 is performed by the network entity 1800 (eg, a mobile network entity) illustrated in FIG. In some examples, the process 1600 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0168] At block 1602, a mobile network entity may receive a common window configuration for the mobile network entity, the common window configuration comprising a plurality (e.g., N) of opportunities within a corresponding window for each of one or more periods. The mobile network entity may receive the common window configuration from a central network entity. In some examples, the common window configuration may be periodic, aperiodic, semi-persistent, or event-triggered.

[0169] At block 1604, the mobile network entity may select a first opportunity from the N opportunities to send a reference signal. For example, the mobile network entity may randomly select a first opportunity from the plurality of opportunities to send a reference signal. In some examples, the mobile network entity may use the selected first opportunity to send a reference signal in each of the one or more cycles or in a subset of the one or more cycles. In some examples, the mobile network entity may sense a first opportunity of at least one of the one or more cycles to determine whether the first opportunity is available, and may select the first opportunity to send a reference signal in response to determining that the first opportunity is available.

[0170] At block 1606, the mobile network entity may then transmit a first reference signal (e.g., SSB) within the selected first opportunity. In some examples, the mobile network entity may transmit the first reference signal using a transmit beam. In some examples, the mobile network entity may transmit the first reference signal using a different corresponding transmit beam of a plurality of transmit beams of the mobile network entity for each of the one or more cycles or for each group of multiple cycles in the one or more cycles. In some examples, the first reference signal may be received, for example, by one or more neighboring network entities (e.g., a stationary network entity and / or a mobile network entity) for measuring a CLI between the mobile network entity and the neighboring network entity based on the first reference signal.

[0171] At block 1608, the mobile network entity may be further configured to receive a second reference signal from a stationary network entity on the access link. For example, the mobile network entity may be an IAB node having an MT unit or a mobile network entity having UE functionality. In this example, the mobile network entity may receive the second reference signal from a neighboring stationary network entity using an SMTC window configured for the access link (e.g., aligned with SSB transmissions on the access link between the stationary network entity and one or more UEs).

[0172] At block 1610, the mobile network entity may obtain a CLI measurement indicating cross link interference (CLI) between the mobile network entity and a neighboring stationary network entity based on the second reference signal. For example, the CLI measurement may be an RSRP or SINR measurement. At block 1612, the mobile network entity may also send a CLI measurement report including the CLI measurement to the central network entity (e.g., when the CLI measurement is greater than a threshold).

[0173] In some examples, in addition to or as an alternative to access link CLI measurements, the mobile network entity may need to measure additional pre-configured inter-network entity CLI reference signals of the stationary network entity. In this example, a separate window configuration for the stationary network entity may be configured (e.g., by a central network entity) and provided to the mobile network entity by the central network entity or the stationary network entity (e.g., the stationary network entity may broadcast the separate window configuration of the stationary network entity).

[0174] Fig.17 is a signaling diagram illustrating exemplary signaling between a central network entity 1702, a stationary network entity 1704, and a mobile network entity 1706 for performing CLI measurements between the mobile network entity 1706 and the stationary network entity 1704 using a separate window configuration according to some aspects. The central network entity 1702 may correspond to, for example Figure 4 The CU shown is either a real-time or non-real-time intelligent controller or Figure 5 CU shown. The central network entity 1702 may also correspond to a core network node, such as an OAM function. Each of the stationary network entity 1704 and the mobile network entity 1706 may be a clustered network entity or a decomposed network entity (e.g., one or more entities that may include a decomposed base station) and / or may be an IAB node.

[0175] At 1708, the central network entity 1702 may provide a separate window configuration for the stationary network entity 1704 to communicate a reference signal for CLI measurement and reporting. The separate window configuration may be similar to the STC / SMTC window configuration for the access link, but is configured for the stationary network entity 1704 for the purpose of CLI measurement by the neighboring mobile network entity. For example, the separate window configuration may include different CLI measurement resources and / or a different periodicity than the STC / SMTC window configuration for the access link. The central network entity 1702 may provide the separate window configuration to both the stationary network entity 1704 and the neighboring mobile network entity. In other examples, the stationary network entity 1704 may provide (e.g., broadcast) the separate window configuration to the mobile network entity 1706.

[0176] At 1710, the stationary network entity 1704 may transmit a reference signal (eg, SSB) based on the single window configuration. In some examples, the stationary network entity 1704 may transmit a set of SSB bursts within a window of the single window configuration.

[0177] At 1712, the mobile network entity 1706 may obtain a CLI measurement indicating a CLI between the mobile network entity 1706 and the stationary network entity 1704 based on the reference signal. For example, the mobile network entity 1706 may obtain a reference signal received power (RSRP) or a signal to interference plus noise ratio (SINR) of the reference signal. At 1714, the mobile network entity 1706 may then send a CLI measurement report including the CLI measurement to the central network entity 1702. In some examples, the mobile network entity 1706 may send the CLI measurement report in response to the CLI measurement being greater than a threshold.

[0178] Fig.18 1 is a block diagram illustrating an example of a hardware implementation of a network entity 1800 employing a processing system 1814 according to some aspects. The network entity 1800 can be, for example, any base station (e.g., gNB, eNB) or Figure 1 , Figure 2 , Figures 4 to 8A , Fig. 9 , Fig.13 and / or Fig.17The network entity 1800 may also be implemented in an aggregated or monolithic base station architecture, or in a decomposed base station architecture, and may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (Near-RT) RAN intelligent controller (RIC), or a non-real-time (Non-RT) RIC. In addition, the network entity 1800 may be a stationary network entity or a mobile network entity.

[0179] According to various aspects of the present disclosure, a processing system 1814 including one or more processors, such as processor 1804, may be used to implement an element or any portion of an element or any combination of elements. Examples of processor 1804 include a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gated logic, a discrete hardware circuit, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. In various examples, network entity 1800 may be configured to perform any one or more of the functions described herein. That is, processor 1804 as utilized in network entity 1800 may be used to implement, for example, Figures 9 to 17 and / or Fig.19 Any one or more of the methods or processes described and illustrated in.

[0180] In some examples, the processor 1804 may be implemented via a baseband or modem chip, and in other implementations, the processor 1804 may include several devices distinct and different from the baseband or modem chip (e.g., in scenarios such as those that may work together to implement the examples discussed herein). And as mentioned above, various hardware arrangements and components outside of the baseband modem processor may be used in implementations, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.

[0181] In this example, the processing system 1814 may be implemented using a bus architecture, which is generally represented by bus 1802. Bus 1802 may include any number of interconnecting buses and bridges, depending on the specific application of the processing system 1814 and the overall design constraints. Bus 1802 communicatively couples together various circuits including one or more processors, which are generally represented by processor 1804, memory 1805, and computer-readable media, which are generally represented by computer-readable media 1806. Bus 1802 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[0182] The bus interface 1808 provides an interface between the bus 1802, the transceiver 1810 and one or more antenna arrays 1830 (e.g., one or more antenna panels). The transceiver 1810 can be, for example, a wireless transceiver. The transceiver 1810 provides a component for communicating with various other devices through a transmission medium (e.g., an air interface). The transceiver 1810 can also be coupled to an antenna array for beamforming. The bus interface 1808 further provides an interface between the bus 1802 and a user interface 1812 (e.g., a keypad, a display, a touch screen, a speaker, a microphone, control features, etc.). Of course, such a user interface 1812 can be omitted in some examples.

[0183] Computer readable medium 1806 may be a non-transitory computer readable medium. Non-transitory computer readable media include, for example, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact disks (CDs) or digital versatile disks (DVDs)), smart cards, flash memory devices (e.g., card, stick or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer readable medium 1806 may reside in processing system 1814, outside processing system 1814, or distributed across multiple entities including processing system 1814. Computer readable medium 1806 may be embodied in a computer program product. For example, a computer program product may include a computer readable medium in a packaging material. In some examples, computer readable medium 1806 may be part of memory 1805. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure, depending on the specific application and the overall design constraints imposed on the overall system. In some examples, computer-readable medium 1806 may be implemented on an article of manufacture, which may also include one or more other elements or circuits, such as processor 1804 and / or memory 1805.

[0184] The computer readable medium 1806 may store computer executable code (e.g., software). Software shall be construed broadly to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures / procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0185] One or more processors (such as processor 1804) can be responsible for managing bus 1802 and general processing, including executing software (e.g., instructions or computer executable code) stored on computer readable medium 1806. The software, when executed by processor 1804, causes processing system 1814 to perform various processes and functions described herein for any particular device. Computer readable medium 1806 and / or memory 1805 can also be used to store data that can be manipulated by processor 1804 when executing software. For example, memory 1805 can store one or more of common window configuration 1816, one or more periodicities 1818 associated with common window configuration 1816, measurement (e.g., CLI measurement) 1820, threshold 1822, and individual window configuration 1824.

[0186] In some aspects of the present disclosure, the processor 1804 may include circuits configured for various functions. For example, the processor 1804 may include a communication and processing circuit 1842 configured to communicate with one or more UEs and / or one or more adjacent network entities. In addition, the communication and processing circuit 1842 may be configured to communicate with a central network entity (e.g., a CU, a real-time or non-real-time intelligent controller, or a core network node) via a mid-haul link and / or a backhaul link. In some examples, the communication and processing circuit 1842 may include one or more hardware components that provide a physical structure that performs processes related to wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing signals for transmission). For example, the communication and processing circuit 1842 may include one or more transmission chains / reception chains. The communication and processing circuit 1842 may be further configured to execute communication and processing software 1852 stored on a computer-readable medium 1806 to implement one or more functions described herein.

[0187] In some implementations where communication involves receiving information, the communication and processing circuitry 1842 may obtain information from a component of the network entity 1800 (e.g., from a transceiver 1810 that receives information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, the communication and processing circuitry 1842 may output the information to another component of the processor 1804, to the memory 1805, or to the bus interface 1808. In some examples, the communication and processing circuitry 1842 may receive one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1842 may receive information via one or more channels. In some examples, the communication and processing circuitry 1842 may include functionality of a means for receiving. In some examples, the communication and processing circuitry 1842 may include functionality of a means for processing (including means for demodulating, means for decoding, etc.).

[0188] In some implementations where communication involves transmitting (e.g., sending) information, the communication and processing circuitry 1842 may obtain information (e.g., from another component of the processor 1804, the memory 1805, or the bus interface 1808), process the information (e.g., modulate, encode, etc. the information), and output the processed information. For example, the communication and processing circuitry 1842 may output the information to the transceiver 1810 (e.g., which transmits the information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, the communication and processing circuitry 1842 may transmit one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1842 may transmit information via one or more channels. In some examples, the communication and processing circuitry 1842 may include functionality of components for transmitting (e.g., components for sending). In some examples, the communication and processing circuitry 1842 may include functionality of components for generating (including components for modulating, components for encoding, etc.).

[0189] The communication and processing circuit 1842 may be further configured to receive a common window configuration 1816 for a plurality of mobile network entities from the central network entity and store the common window configuration 1816, for example, in the memory 1805. The common window configuration 1816 may include a plurality of opportunities within a corresponding window of each of one or more periods for communicating one or more reference signals. In addition, the common window configuration 1816 may be periodic, aperiodic, semi-persistent, or event-triggered.

[0190] The communication and processing circuit 1842 may be further configured to receive a first reference signal from another (e.g., second) network entity within a first opportunity in a plurality of opportunities, wherein at least one of the network entity 1800 and the other (second) network entity is a mobile network entity in a plurality of mobile network entities. In addition, the communication and processing circuit 1842 may be configured to send a second reference signal within a second opportunity in a plurality of opportunities.

[0191] In an example where the network entity 1800 is a mobile network entity, the communication and processing circuit 1842 may be further configured to listen to an additional reference signal from a neighboring mobile network entity in the plurality of mobile network entities during a remaining opportunity (e.g., different from the second opportunity) in the plurality of opportunities in each of the one or more cycles. In an example where the network entity 1800 is a stationary network entity, the communication and processing circuit 1842 may be configured to listen to a corresponding window in each of the one or more cycles. In some examples, the stationary network entity 1800 may be configured to listen to a corresponding window in each of the remaining cycles of the one or more cycles in response to detecting the first reference signal within an initial cycle of the one or more cycles.

[0192] In some examples, the common window configuration 1816 may include a first periodicity 1818 (e.g., a window periodicity) of the corresponding window of the one or more periods. The communication and processing circuit 1842 may be configured to listen to the corresponding window within a selected period of the one or more periods based on a second periodicity 1818 associated with one or more periods used by the second network entity to receive the first reference signal. Here, the second periodicity may be a multiple of the first periodicity. In this example, the network entity 1800 may be a stationary network entity or a mobile network entity. The communication and processing circuit 1842 may be configured to receive the second periodicity 1818 from the central network entity or from the second network entity, and store the second periodicity 1818 in, for example, the memory 1805.

[0193] In an example where the network entity 1800 is a mobile network entity, the communication and processing circuit 1842 may be further configured to receive a third reference signal from a third network entity (e.g., a stationary network entity) over an access link. In some examples, the communication and processing circuit 1842 may be further configured to receive a separate window configuration 1824 associated with the third network entity and store the separate window configuration, for example, in the memory 1805. The communication and processing circuit 1842 may be further configured to receive a fourth reference signal from the third network entity based on the separate window configuration.

[0194] The communication and processing circuitry 1842 may be further configured to send a cross link interference (CLI) measurement report to a central network entity. The communication and processing circuitry 1842 may be further configured to execute communication and processing instructions (software) 1852 stored in the computer readable medium 1806 to implement one or more of the functions described herein.

[0195] The processor 1804 may further include a reference signal management circuit 1844 configured to generate and process reference signals according to at least one of the common window configuration 1816, the individual window configuration 1824, or the access link window configuration (e.g., STC / SMTC window configuration). For example, the reference signal management circuit 1844 may be configured to send and / or receive reference signals between the network entity 1800 and a neighboring network entity using the common window configuration 1816. The reference signal management circuit 1844 may be further configured to trigger the common window configuration 1816 upon occurrence of an event.

[0196] In some examples, the reference signal management circuit 1844 may be configured to select a second opportunity on which to send the second reference signal. In some examples, the reference signal management circuit 1844 may be configured to randomly select a second opportunity from a plurality of opportunities to send the second reference signal. In some examples, the reference signal management circuit 1844 may be configured to operate with the communication and processing circuit 1842 to use the second opportunity to send the second reference signal in each of the one or more cycles or in a subset of the one or more cycles. In some examples, the reference signal management circuit 1844 may be configured to sense the second opportunity of at least one of the one or more cycles to determine whether the second opportunity is available, and select the second opportunity to send the second reference signal in response to determining that the second opportunity is available.

[0197] In addition, the reference signal management circuit 1844 can be configured to select a transmit beam for transmitting a second reference signal via the communication and processing circuit 1842, the transceiver 1810, and the antenna array 1830. In some examples, the reference signal management circuit 1844 can be configured to operate with the communication and processing circuit 1842, the transceiver 1810, and the antenna array 1830 to transmit the second reference signal using a different corresponding transmit beam of the plurality of transmit beams of the network entity 1800 for each of the one or more cycles or for each group of multiple cycles in the one or more cycles.

[0198] The reference signal management circuit 1844 may be further configured to select a receive beam on which to receive the first reference signal. In some examples, the reference signal management circuit 1844 may be configured to operate with the communication and processing circuit 1842, the transceiver 1810, and the antenna array 1830 to receive the first reference signal using a different corresponding receive beam of the plurality of receive beams of the network entity 1800 for each of the one or more cycles or for each group of multiple cycles in the one or more cycles.

[0199] The reference signal management circuit 1844 may be further configured to select a second periodicity 1818 (e.g., and store the second periodicity 1818 in, for example, the memory 1805) for sending the second reference signal. Here, the second periodicity is a multiple of the first periodicity 1818 of the corresponding window of one or more periods indicated by the common window configuration 1816. In some examples, the reference signal management circuit 1844 may be configured to select the second periodicity based on the speed of the network entity 1800. The reference signal management circuit 1844 may be further configured to provide the second periodicity to one or more neighboring network entities (mobile network entities and / or stationary network entities) via the communication and processing circuit 1842 and the transceiver 1810. The reference signal management circuit 1844 may be further configured to execute the reference signal management instructions (software) 1854 stored on the computer-readable medium 1806 to implement one or more functions described herein.

[0200] The processor 1804 may further include a CLI measurement circuit 1846 configured to obtain a first CLI measurement 1820 based on a first reference signal received from a neighboring (e.g., second) network entity. For example, the CLI measurement 1820 may be an RSRP or SINR of the first reference signal. In addition, the CLI measurement circuit 1846 may be further configured to obtain a second CLI measurement 1820 based on a third reference signal transmitted from a stationary (e.g., third) network entity on an access link. The CLI measurement circuit 1846 may be further configured to obtain a third CLI measurement 1820 based on a fourth reference signal transmitted from the stationary (e.g., fourth) network entity based on a separate window configuration associated with the stationary (e.g., fourth) network entity.

[0201] The CLI measurement circuit 1846 may be further configured to generate and send a CLI measurement report including the CLI measurement 1820 (e.g., the first, second, or third CLI measurement) to the central network entity. In some examples, the CLI measurement circuit 1846 may compare the CLI measurement 1820 (e.g., the first, second, or third CLI measurement) to a threshold 1822 maintained in the memory 1805 to determine whether to send the CLI measurement report. For example, the CLI measurement circuit 1846 may be configured to generate and send a CLI measurement report including the CLI measurement 1820 in response to the CLI measurement 1820 being greater than the threshold 1822. In some examples, the same threshold 1822 may be used for the first, second, and third CLI measurements. In other examples, different thresholds 1822 may be used for the first, second, and third CLI measurements. The CLI measurement circuit 1846 may be further configured to execute CLI measurement instructions (software) 1856 stored on the computer-readable medium 1806 to implement one or more functions described herein.

[0202] Fig.19 is a flow chart illustrating an exemplary process 1900 for performing CLI measurements using a common window configuration according to some aspects. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for implementations of all embodiments. In some examples, process 1900 may be performed by Fig.18 The process 1900 is performed by the network entity 1800 illustrated in FIG. In some examples, the process 1900 can be performed by any suitable device or component for performing the functions or algorithms described below.

[0203] At block 1902, the network entity may receive a common window configuration for a plurality of mobile network entities from a central network entity, wherein the common window configuration includes a plurality of opportunities within a corresponding window for each of one or more periods for communicating one or more reference signals. In some examples, the common window configuration is periodic, aperiodic, semi-persistent, or event-triggered. For example, the above with respect to Fig.18 The communication and processing circuitry 1842 and transceiver 1810 shown and described may together provide means for receiving a common window configuration.

[0204] At block 1904, the network entity may receive a first reference signal from a second network entity within a first opportunity in a plurality of opportunities, wherein at least one of the first network entity or the second network entity is a mobile network entity among a plurality of mobile network entities. In some examples, the network entity may receive the first reference signal using a different corresponding receive beam of a plurality of receive beams of the first network entity for each of the one or more periods or for each group of a plurality of periods in the one or more periods. For example, the above with respect to Fig.18 The illustrated and described communications and processing circuitry 1842 together with reference signal management circuitry 1844, transceiver 1810, and antenna array 1830 may provide means for receiving a first reference signal.

[0205] At block 1906, the network entity may obtain a CLI measurement indicating cross-link interference between the first network entity and the second network entity based on the first reference signal. Fig.18 The CLI measurement circuit 1846 shown and described may provide means for obtaining CLI measurements.

[0206] In one configuration, the network entity includes: a component for receiving a common window configuration for a plurality of mobile network entities from a central network entity, the common window configuration including a plurality of occasions within a corresponding window of each of one or more periods for communicating one or more reference signals; a component for receiving a first reference signal from a second network entity within a first opportunity of the plurality of occasions, at least one of the first network entity or the second network entity being one of the plurality of mobile network entities; and a component for obtaining a CLI measurement indicating cross-link interference between the first network entity and the second network entity based on the first reference signal. In one aspect, the aforementioned component may be Fig.18 The processor 1804 is shown configured to perform the functions recited by the aforementioned means. In another aspect, the aforementioned means may be a circuit or any device configured to perform the functions recited by the aforementioned means.

[0207] Of course, in the above examples, the circuits included in the processor 1804 are provided only as examples, and other components for performing the described functions may be included in various aspects of the present disclosure, including but not limited to instructions stored in the computer-readable storage medium 1806, or Figure 1 , Figure 2 , Figures 4 to 8A , Fig. 9 , Fig.13 and 17 Any of the foregoing and using, for example, Figures 9 to 17 and Fig.19Any other suitable means or components of the described processes and / or algorithms.

[0208] Fig. 20 2014 is a block diagram illustrating an example of a hardware implementation of a central network entity 2000 employing a processing system 2014 in accordance with some aspects. The central network entity 2000 may be, for example, a central unit (CU), a near real-time (near-RT) RAN intelligent controller (RIC), a non-real-time (non-RT) RIC, or a core network node (e.g., an OAM function).

[0209] According to various aspects of the present disclosure, a processing system 2014 including one or more processors (such as the processor 2004) may be used to implement an element or any portion of an element or any combination of elements. The processing system 2014 may be combined with the above Fig.18 The processing system 1814 shown and described is substantially the same, including a bus interface 2008, a bus 2002, a memory 2005, a processor 2004, and a computer-readable medium 2006. Therefore, for the sake of brevity, their description will not be repeated. In addition, the central network entity 2000 may include an optional user interface 2012 and a communication interface 2010 (e.g., a network interface and / or a transceiver).

[0210] The processor 2004 as utilized in the central network entity 2000 may be used to implement any one or more of the processes described below. In some examples, the memory 2005 may store one or more of the common window configuration 2016, one or more periodicities 2018 associated with the common window configuration 2016, the individual window configuration 2020, and the CLI measurement report 2022 for use by the processor 2004 when executing software (instructions) stored on the computer readable medium 2006.

[0211] In some aspects of the present disclosure, the processor 2004 may include a communication and processing circuit 2042 configured for various functions, including, for example, communicating with one or more other network entities and / or a core network. In some examples (e.g., in a converged base station architecture), the communication and processing circuit 2042 may include one or more hardware components that provide a physical structure that performs processes related to wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing signals for transmission). In addition, the communication and processing circuit 2042 may be configured to: process and transmit downlink traffic (e.g., packets) and downlink control, and receive and process uplink traffic (e.g., packets) and uplink control.

[0212] The communication and processing circuitry 2042 may be further configured to provide a common window configuration for a plurality of mobile network entities. The common window configuration may be provided to both the mobile network entity and the stationary network entity. The communication and processing circuitry 2042 may be further configured to receive at least one CLI measurement report 2022 indicating measured cross link interference (CLI) between neighboring network entities, wherein at least one of the neighboring network entities is a mobile network entity in the plurality of mobile network entities. The communication and processing circuitry 2042 may be further configured to execute communication and processing instructions (software) 2052 stored on the computer readable medium 2006 to implement one or more functions described herein.

[0213] The processor 2004 may further include a window configuration management circuit 2044 configured to generate a common window configuration 2016 and store the common window configuration 2016 in, for example, the memory 2005. For example, the common window configuration 2016 may include a plurality of opportunities within a corresponding window for each of one or more periods of communicating one or more reference signals. In some examples, the common window configuration 2016 may be periodic, aperiodic, semi-persistent, or event-triggered.

[0214] In some examples, the common window configuration 2016 includes a first periodicity 2018 of a corresponding window of one or more periods. In some examples, the window configuration management circuit 2044 can be configured to obtain a second periodicity used by the mobile network entity to send a reference signal. Here, the second periodicity can be a multiple of the first periodicity. For example, the window configuration management circuit 2044 can be configured to receive a second periodicity from the mobile network entity (e.g., via one or more other mobile and / or stationary network entities). For another example, the window configuration management circuit 2044 can be configured to assign or select a second periodicity for the mobile network entity (e.g., based on one or more standards or specifications). The window configuration management circuit 2044 can also operate with the communication and processing circuit 2042 to provide the second periodicity of the mobile network entity to an additional network entity (e.g., a stationary network entity or other mobile network entity) and / or to the mobile network entity.

[0215] In some examples, the window configuration management circuit 2044 may be further configured to generate a separate window configuration 2020 for a stationary network entity and store the separate window configuration 2020 in, for example, the memory 2005. The separate window configuration 2020 may be similar to the STC / SMTC window configuration for an access link. However, the separate window configuration 2020 may include different CLI measurement resources and / or different periodicity than the STC / SMTC access link window configuration. The window configuration management circuit 2044 may be further configured to operate with the communication and processing circuit 2042 to provide the separate window configuration 2020 for the stationary network entity to the stationary network entity and to at least one mobile network entity near the stationary network entity. The window configuration management circuit 2044 may be further configured to execute the window configuration management instructions (software) 2054 stored on the computer-readable medium 2006 to implement one or more functions described herein.

[0216] The processor 2004 may further include a CLI measurement report processing circuit 2046 configured to process a CLI measurement report 2022 received from a neighboring network entity and mitigate CLI between the neighboring network entities. For example, the CLI measurement report processing circuit 2046 may be configured to generate instructions and provide instructions to the neighboring network entity to synchronize downlink communications and uplink communications and / or use transmit / receive beams that can reduce CLI. In an example where the neighboring network entity includes a stationary network entity and a mobile network entity, the CLI measurement report processing circuit 2046 may be configured to receive at least one CLI measurement report from the stationary network entity or the mobile network entity. In some examples, the CLI measurement report processing circuit 2046 is configured to receive the CLI measurement report based on at least one of the access link window configuration (e.g., STC / SMTC window configuration) or the separate window configuration 2020 of the stationary network entity. The CLI measurement report processing circuit 2046 may be further configured to execute CLI measurement report processing instructions (software) 2056 stored on the computer readable medium 2006 to implement one or more functions described herein.

[0217] Fig.21 is a flow chart illustrating an exemplary process 2100 for configuring a common window configuration for CLI measurement and reporting according to some aspects. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for implementations of all embodiments. In some examples, process 2100 may be performed by Fig. 20The process 2100 is performed by the central network entity 2000 illustrated in FIG. In some examples, the process 2100 can be performed by any suitable device or component for performing the functions or algorithms described below.

[0218] At block 2102, the central network entity may provide a common window configuration for multiple mobile network entities. The common window configuration may include multiple opportunities within a corresponding window for each of one or more periods of communicating one or more reference signals. In some examples, the common window configuration is periodic, aperiodic, semi-persistent, or event-triggered.

[0219] In some examples, the neighboring network entities include a mobile network entity and an additional network entity among a plurality of mobile network entities, and the common window configuration includes a first periodicity of a corresponding window of one or more periods. In this example, the central network entity may provide the additional network entity with a second periodicity used by the mobile network entity to send a reference signal, wherein the second periodicity is a multiple of the first periodicity. In some examples, the neighboring network entities include a stationary network entity and a mobile network entity among a plurality of mobile network entities. In this example, the central network entity may also provide the mobile network entity with a separate window configuration for the stationary network entity. For example, the above with reference to Fig. 20 The communication and processing circuitry 2042, together with the window configuration management circuitry 2044 and the communication interface 2010, as shown and described may provide means for providing a common window configuration.

[0220] At block 2104, the central network entity may receive at least one cross-link interference measurement report indicating cross-link interference between neighboring network entities, wherein at least one of the neighboring network entities is a mobile network entity among the plurality of mobile network entities. In some examples, the neighboring network entity includes a stationary network entity and a mobile network entity among the plurality of mobile network entities. In this example, the central network entity may receive at least one cross-link interference measurement report from the stationary network entity or the mobile network entity. In some examples, the at least one cross-link interference measurement report is based on at least one of an access link window configuration associated with the stationary network entity or a separate window configuration for the stationary network entity. For example, the above in conjunction with Fig. 20 The communication and processing circuitry 2042, along with the CLI measurement report processing circuitry 2046 and the communication interface 2010, as shown and described may provide means for receiving at least one cross-link interference measurement report.

[0221] In one configuration, the central network entity includes: means for providing a common window configuration for a plurality of mobile network entities, the common window configuration comprising a plurality of opportunities within a respective window in each of one or more periods for communicating one or more reference signals; and means for receiving at least one cross-link interference measurement report indicating cross-link interference between neighboring network entities, at least one of the neighboring network entities being one of the plurality of mobile network entities. In one aspect, the aforementioned means may be Fig. 20 The processor 2004 is shown configured to perform the functions recited by the aforementioned means. In another aspect, the aforementioned means may be a circuit or any device configured to perform the functions recited by the aforementioned means.

[0222] Of course, in the above examples, the circuits included in the processor 2004 are provided only as examples, and other components for performing the described functions may be included in various aspects of the present disclosure, including but not limited to instructions stored in the computer-readable storage medium 2006, or Figure 1 , Figure 2 , Figures 4 to 8A , Fig. 9 , Fig.13 and Fig.17 Any of the foregoing and using, for example, Figures 9 to 17 and Fig.21 Any other suitable means or components of the described processes and / or algorithms.

[0223] The following provides an overview of various aspects of the disclosure:

[0224] Aspect 1: A method capable of operating at a first network entity, the method comprising: receiving a common window configuration for multiple mobile network entities from a central network entity, the common window configuration comprising multiple opportunities within a corresponding window in each of one or more periods for communicating one or more reference signals; receiving a first reference signal from a second network entity within a first opportunity among the multiple opportunities, at least one of the first network entity or the second network entity being one of the multiple mobile network entities; and obtaining a cross-link interference measurement indicating cross-link interference between the first network entity and the second network entity based on the first reference signal.

[0225] Aspect 2: The method according to aspect 1, wherein the common window configuration is periodic, non-periodic, semi-persistent or event-triggered.

[0226] Aspect 3: A method according to Aspect 1 or 2, wherein receiving the first reference signal further comprises: for each of the one or more periods or for each group of multiple periods in the one or more periods, using different corresponding receiving beams among the multiple receiving beams of the first network entity to receive the first reference signal.

[0227] Aspect 4: The method according to any one of aspects 1 to 3, wherein the first network entity is one of the multiple mobile network entities, and the method further comprises: sending a second reference signal in a second timing among the multiple timings.

[0228] Aspect 5: A method according to Aspect 4, wherein sending the second reference signal further comprises: for each of the one or more periods or for each group of multiple periods in the one or more periods, sending the second reference signal using different corresponding transmit beams among the multiple transmit beams of the first network entity.

[0229] Aspect 6: The method according to aspect 4 or 5 further comprises: during the remaining opportunities of the multiple opportunities in each cycle of the one or more cycles, listening to additional reference signals from neighboring mobile network entities among the multiple mobile network entities.

[0230] Aspect 7: According to the method according to any one of aspects 4 to 6, the method further comprises: randomly selecting the second opportunity from the multiple opportunities to send the second reference signal.

[0231] Aspect 8: The method according to aspect 7 further comprises: sending the second reference signal using the second opportunity in each of the one or more cycles or in a subset of the one or more cycles.

[0232] Aspect 9: According to the method described in any one of Aspects 4 to 6, the method further includes: sensing the second opportunity of at least one of the one or more periods to determine whether the second opportunity is available for use by the first network entity; and in response to determining that the second opportunity is available, selecting the second opportunity to send the second reference signal.

[0233] Aspect 10: A method according to any one of Aspects 4 to 9, wherein the common window configuration includes a first periodicity of the corresponding window of the one or more periods, and sending the second reference signal also includes: sending the second reference signal with a second periodicity, and the second periodicity is a multiple of the first periodicity.

[0234] Aspect 11: The method according to aspect 10, further comprising: selecting the second periodicity based on a speed of the first network entity.

[0235] Aspect 12: The method according to any one of aspects 1 to 3, wherein the first network entity is a stationary network entity and the second network entity is a mobile network entity among the plurality of mobile network entities.

[0236] Aspect 13: The method according to aspect 12, further comprising: monitoring the corresponding window of each of the one or more cycles.

[0237] Aspect 14: A method according to Aspect 12, wherein the common window configuration includes a first periodicity of the corresponding window of the one or more periods, and the method further includes: based on a second periodicity associated with the one or more periods used by the second network entity to send the first reference signal, listening to the corresponding window within a selected period of the one or more periods, the second periodicity being a multiple of the first periodicity.

[0238] Aspect 15: The method according to aspect 14, the method further comprising: receiving the second periodicity from the central network entity or the second network entity.

[0239] Aspect 16: According to the method of any one of Aspects 12 to 15, the method further comprises: in response to the cross-link interference measurement being greater than a threshold, sending a cross-link interference measurement report including the cross-link interference measurement to the central network entity.

[0240] Aspect 17: According to the method of any one of Aspects 12 or 16, the method further includes: in response to detecting the first reference signal in an initial period of the one or more periods, listening to the corresponding window of each remaining period of the one or more periods.

[0241] Aspect 18: A method according to any one of Aspects 1 to 11, wherein the first network entity is one of the multiple mobile network entities, and the method also includes: receiving a third reference signal from a third network entity on an access link, the third network entity being a stationary network entity; and obtaining a second cross-link interference measurement indicating a second cross-link interference between the first network entity and the third network entity based on the third reference signal.

[0242] Aspect 19: The method according to aspect 18, the method further comprising: in response to the second cross-link interference measurement being greater than a threshold, sending a cross-link interference measurement report including the second cross-link interference measurement to the central network entity.

[0243] Aspect 20: According to the method described in Aspect 18 or 19, the method also includes: receiving a separate window configuration associated with the third network entity; receiving a fourth reference signal from the third network entity based on the separate window configuration; and obtaining a third cross-link interference measurement indicating a third cross-link interference between the first network entity and the third network entity based on the fourth reference signal.

[0244] Aspect 21: A first network entity, comprising a memory and a processor, the processor being coupled to the memory, the processor being configured to execute the method according to any one of aspects 1 to 20.

[0245] Aspect 22: A first network entity comprising means for performing the method according to any one of aspects 1 to 20.

[0246] Aspect 23: A non-transitory computer-readable medium having instructions stored therein, wherein the instructions can be executed by one or more processors of a first network entity to perform the method according to any one of aspects 1 to 20.

[0247] Aspect 24: A method capable of operating at a central network entity, the method comprising: providing a common window configuration for multiple mobile network entities, the common window configuration comprising multiple opportunities within a corresponding window in each of one or more periods for communicating one or more reference signals; and receiving at least one cross-link interference measurement report indicating cross-link interference between adjacent network entities, at least one of the adjacent network entities being one of the multiple mobile network entities.

[0248] Aspect 25: The method according to Aspect 24, wherein the common window configuration is periodic, non-periodic, semi-persistent or event-triggered.

[0249] Aspect 26: A method according to Aspect 24 or 25, wherein the adjacent network entities include mobile network entities and additional network entities among the multiple mobile network entities, and the common window configuration includes a first periodicity of the corresponding window of the one or more periods, and the method further includes: providing the additional network entity with a second periodicity used by the mobile network entity to send a reference signal, the second periodicity being a multiple of the first periodicity.

[0250] Aspect 27: A method according to any one of Aspects 24 to 26, wherein the neighboring network entity includes a stationary network entity and a mobile network entity among the multiple mobile network entities, and wherein receiving the at least one cross-link interference measurement report also includes: receiving the at least one cross-link interference measurement report from the stationary network entity or the mobile network entity.

[0251] Aspect 28: The method of aspect 27, wherein the at least one cross-link interference measurement report is based on at least one of an access link window configuration associated with the stationary network entity or a separate window configuration for the stationary network entity.

[0252] Aspect 29: The method according to aspect 28, further comprising: providing the separate window configuration for the stationary network entity to the mobile network entity.

[0253] Aspect 30: A central network entity, comprising a memory and a processor, the processor being coupled to the memory, the processor being configured to perform the method according to any one of aspects 24 to 29.

[0254] Aspect 31: A central network entity comprising means for performing the method according to any one of aspects 24 to 29.

[0255] Aspect 32: A non-transitory computer-readable medium having instructions stored therein, the instructions being executable by one or more processors of a central network entity to perform the method according to any one of aspects 24 to 29.

[0256] Several aspects of wireless communication networks have been presented with reference to exemplary implementations. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures and communication standards.

[0257] By way of example, various aspects may be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile (GSM). Various aspects may also be extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution-Data Optimized (EV-DO). Other examples may be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

[0258] Within the present disclosure, the word "exemplary" is used to mean "serving as an example, instance, or illustration". Any specific implementation or aspect described herein as "exemplary" is not necessarily to be construed as superior or superior to other aspects of the present disclosure. Likewise, the term "aspect" does not require that all aspects of the present disclosure include the discussed features, advantages, or modes of operation. The term "coupled" is used herein to refer to a direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, objects A and C may still be considered to be coupled to each other, even if they are not in direct physical contact with each other. For example, a first object may be coupled to a second object, even if the first object has never been in direct physical contact with the second object. The term "circuit" is used broadly, and is intended to include both hardware implementations of electronic devices and conductors (where these electronic devices and conductors, when connected and configured, implement the execution of the functions described in the present disclosure, without limitation on the type of electronic circuit) and software implementations of information and instructions (where these information and instructions, when executed by a processor, implement the execution of the functions described in the present disclosure).

[0259] Figures 1 to 21 One or more of the components, steps, features, and / or functions illustrated in the present disclosure may be rearranged and / or combined into a single component, step, feature, or function, or may be embodied in several components, steps, or functions. Additional elements, components, steps, and / or functions may also be added without departing from the novel features disclosed herein. Figure 1 , Figure 2 , Figures 4 to 8A , Fig. 9 , Fig.13 , Fig.17 , Fig.18 and / or Fig. 20The apparatus, device and / or components illustrated in the can be configured to perform one or more of the methods, features or steps described herein. The novel algorithms described herein can also be effectively implemented in software and / or embedded in hardware.

[0260] It should be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of an exemplary process. It should be understood that the specific order or hierarchy of steps in these methods can be rearranged based on design preferences. The attached method claims present elements of various steps in an example order, but are not intended to be limited to the specific order or hierarchy presented unless explicitly stated herein.

[0261] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. 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. Therefore, the claims are not intended to be limited to the various aspects shown herein, but to conform to the full scope consistent with the language of the claims, wherein unless explicitly stated otherwise, reference to an element in the singular form is not intended to mean "one and only one", but "one or more". Unless otherwise specified, the term "some" refers to one or more. A phrase referring to "at least one of" a list of items refers to any combination of those items, including a single member. As an example, "at least one of a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will be known later to a person of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, regardless of whether such disclosure is explicitly recited in the claims, anything disclosed herein is not intended to be disclosed to the public. No claim element is to be construed under 35 USC §112(f) unless the element is expressly recited using the phrase “means for” or, in the case of a method claim, the phrase “step for.”

Claims

1. A first network entity configured for wireless communication, the first network entity comprising: Memory; and a processor coupled to the memory, the processor being configured to: receiving, from a central network entity, a common window configuration for a plurality of mobile network entities, the common window configuration comprising a plurality of opportunities within a respective window of each of one or more periods for communicating one or more reference signals; receiving a first reference signal from a second network entity within a first timing of the plurality of timings, at least one of the first network entity or the second network entity being a mobile network entity among the plurality of mobile network entities; as well as A cross-link interference measurement indicative of cross-link interference between the first network entity and the second network entity is obtained based on the first reference signal.

2. The first network entity according to claim 1, wherein the common window configuration is periodic, aperiodic, semi-persistent or event-triggered.

3. The first network entity according to claim 1, wherein the processor is further configured to: For each of the one or more periods or for each group of multiple periods of the one or more periods, the first reference signal is received using a different corresponding receive beam of a plurality of receive beams of the first network entity.

4. The first network entity of claim 1 , wherein the first network entity is one of the plurality of mobile network entities, and wherein the processor is further configured to: A second reference signal is sent in a second timing among the plurality of timings.

5. The first network entity according to claim 4, wherein the processor is further configured to: For each of the one or more cycles or for each group of multiple cycles in the one or more cycles, the second reference signal is sent using a different corresponding transmission beam among multiple transmission beams of the first network entity.

6. The first network entity according to claim 4, wherein the processor is further configured to: During remaining opportunities of the plurality of opportunities of each of the one or more cycles, additional reference signals from neighboring mobile network entities of the plurality of mobile network entities are listened to.

7. The first network entity according to claim 4, wherein the processor is further configured to: The second timing is randomly selected from the plurality of timings to transmit the second reference signal.

8. The first network entity according to claim 7, wherein the processor is further configured to: The second reference signal is sent using the second opportunity in each of the one or more cycles or in a subset of the one or more cycles.

9. The first network entity according to claim 4, wherein the processor is further configured to: sensing the second opportunity of at least one of the one or more cycles to determine whether the second opportunity is available for use by the first network entity; and In response to determining that the second opportunity is available, selecting the second opportunity to send the second reference signal.

10. The first network entity of claim 4, wherein the common window configuration comprises a first periodicity of the respective windows of the one or more periods, and wherein the processor is further configured to: The second reference signal is sent with a second periodicity, where the second periodicity is a multiple of the first periodicity.

11. The first network entity according to claim 10, wherein the processor is further configured to: The second periodicity is selected based on a speed of the first network entity.

12. The first network entity of claim 1, wherein the first network entity is a stationary network entity and the second network entity is a mobile network entity among the plurality of mobile network entities.

13. The first network entity according to claim 12, wherein the processor is further configured to: The corresponding window of each of the one or more cycles is listened to.

14. The first network entity of claim 12, wherein the common window configuration comprises a first periodicity of the respective windows of the one or more periods, and wherein the processor is further configured to: Based on a second periodicity associated with the one or more periods used by the second network entity to send the first reference signal, the corresponding window is listened to within a selected period of the one or more periods, the second periodicity being a multiple of the first periodicity.

15. The first network entity according to claim 14, wherein the processor is further configured to: The second periodicity is received from the central network entity or the second network entity.

16. The first network entity of claim 12, wherein the processor is further configured to: In response to the cross-link interference measurement being greater than a threshold, sending a cross-link interference measurement report including the cross-link interference measurement to the central network entity.

17. The first network entity of claim 12, wherein the processor is further configured to: In response to detecting the first reference signal in an initial period of the one or more periods, listening to the corresponding window of each remaining period of the one or more periods.

18. The first network entity of claim 1, wherein the first network entity is one of the plurality of mobile network entities, and wherein the processor is further configured to: receiving a third reference signal from a third network entity on an access link, the third network entity being a stationary network entity; and A second cross-link interference measurement indicative of second cross-link interference between the first network entity and the third network entity is obtained based on the third reference signal.

19. The first network entity according to claim 18, wherein the processor is further configured to: In response to the second cross-link interference measurement being greater than a threshold, sending a cross-link interference measurement report including the second cross-link interference measurement to the central network entity.

20. The first network entity of claim 18, wherein the processor is further configured to: receiving a separate window configuration associated with the third network entity; receiving a fourth reference signal from the third network entity based on the single window configuration; and A third cross-link interference measurement indicative of third cross-link interference between the first network entity and the third network entity is obtained based on the fourth reference signal.

21. A method operable at a first network entity, the method comprising: receiving, from a central network entity, a common window configuration for a plurality of mobile network entities, the common window configuration comprising a plurality of opportunities within a respective window of each of one or more periods for communicating one or more reference signals; receiving a first reference signal from a second network entity within a first timing of the plurality of timings, at least one of the first network entity or the second network entity being a mobile network entity among the plurality of mobile network entities; as well as A cross-link interference measurement indicative of cross-link interference between the first network entity and the second network entity is obtained based on the first reference signal.

22. The method according to claim 21, wherein the first network entity is one of the plurality of mobile network entities, and the method further comprises: A second reference signal is sent in a second timing among the plurality of timings.

23. A central network entity, comprising: Memory; and a processor coupled to the memory, the processor being configured to: providing a common window configuration for a plurality of mobile network entities, the common window configuration comprising a plurality of opportunities within a respective window of each of one or more periods for communicating one or more reference signals; as well as At least one cross-link interference measurement report is received indicating cross-link interference between neighboring network entities, at least one of the neighboring network entities being a mobile network entity of the plurality of mobile network entities.

24. The central network entity of claim 23, wherein the common window configuration is periodic, aperiodic, semi-persistent or event-triggered.

25. The central network entity of claim 23, wherein the neighboring network entities include a mobile network entity and an additional network entity of the plurality of mobile network entities, and the common window configuration includes a first periodicity of the respective windows of the one or more periods, and wherein the processor is further configured to: A second periodicity used by the mobile network entity to send a reference signal is provided to the additional network entity, the second periodicity being a multiple of the first periodicity.

26. The central network entity of claim 23, wherein the neighboring network entities include a stationary network entity and a mobile network entity of the plurality of mobile network entities, and wherein the processor is further configured to: The at least one cross-link interference measurement report is received from the stationary network entity or the mobile network entity.

27. The central network entity of claim 26, wherein the at least one cross-link interference measurement report is based on at least one of an access link window configuration associated with the stationary network entity or a separate window configuration for the stationary network entity.

28. The central network entity of claim 27, wherein the processor is further configured to: The separate window configuration for the stationary network entity is provided to the mobile network entity.

29. A method operable at a central network entity, the method comprising: providing a common window configuration for a plurality of mobile network entities, the common window configuration comprising a plurality of opportunities within a respective window of each of one or more periods for communicating one or more reference signals; as well as At least one cross-link interference measurement report is received indicating cross-link interference between neighboring network entities, at least one of the neighboring network entities being a mobile network entity of the plurality of mobile network entities.

30. The method of claim 29, wherein the neighboring network entity comprises a stationary network entity and a mobile network entity of the plurality of mobile network entities, and wherein receiving the at least one cross-link interference measurement report further comprises: The at least one cross-link interference measurement report is received from the stationary network entity or the mobile network entity.

Images