Cross-link interference measurement configuration

Abstract

Various aspects relate to configuring cross-link interference (CLI) measurements. In some examples, a base station may configure a first user equipment (UE) to relay a CLI configuration to a second UE. In response, the second UE may send a CLI measurement report to the first UE, whereby the first UE relays the CLI measurement report to the base station. In some examples, the base station may configure the first UE to schedule CLI measurements. In this case, the first UE may generate a CLI configuration for the second UE and send the CLI configuration to the second UE. The second UE may then send a CLI measurement report to the first UE. In some examples, the base station may send a CLI configuration to the UE, and the UE may send a CLI measurement report to another UE, which relays the CLI measurement report to the base station.

Description

Technical Field

[0001] The techniques discussed below relate generally to wireless communications, and more particularly to configuring cross-link interference (CLI) measurements. Background Art

[0002] A next generation wireless communication system (e.g., 5GS) may include a 5G core network and a 5G radio access network (RAN), such as a new radio (NR)-RAN. The NR-RAN supports communication via one or more cells. For example, a wireless communication device such as a user equipment (UE) may access a first cell of a first base station (BS) such as a gNB and / or access a second cell of a second base station.

[0003] A base station may schedule access to a cell to support access by multiple UEs. For example, a base station may allocate different resources (e.g., time domain and frequency domain resources) to different UEs operating within the cell of the base station. In some cases, signaling between a base station and a UE may be interfered with. For example, when a first UE sends an uplink signal at substantially the same time as a nearby second UE receives a downlink signal, the transmission of an uplink signal by the first UE may interfere with the reception of a downlink signal by the second UE. This type of interference may be referred to as cross-link interference (CLI), or more specifically, UE-to-UE CLI.

[0004] As the demand for mobile access continues to increase, research and development continue to drive advances in communication technologies, particularly technologies for enhancing mobile communications within wireless communication networks, not only to meet the growing demand for mobile access, but also to improve and enhance the user experience associated with mobile communications. Summary of the invention

[0005] An overview of one or more aspects of the present disclosure is presented below to provide a basic understanding of these aspects. This overview is not a comprehensive summary 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 simplified form as a prelude to a more detailed description presented later.

[0006] Various aspects of the present disclosure relate to configuring cross-link interference (CLI) measurements. For example, a base station may configure a UE to perform CLI measurements on one or more resources, generate a CLI measurement report based on the CLI measurements, and send the CLI measurement report to the base station. As another example, a first UE may configure a second UE to perform CLI measurements on one or more resources, generate a CLI measurement report based on the CLI measurements, and send the CLI measurement report to the first UE.

[0007] In some examples, the base station may configure the first UE to relay the CLI configuration to the second UE (e.g., via a sidelink channel). In response, the second UE may send a CLI measurement report to the first UE (e.g., via a sidelink channel), whereby the first UE relays the CLI measurement report to the base station. This approach may be used, for example, in the case where the second UE is out of coverage of the base station.

[0008] In some examples, the base station may configure the first UE to schedule CLI measurements. In this case, the first UE may generate a CLI configuration for the second UE and send the CLI configuration to the second UE (e.g., via a sidelink channel). The second UE may then send a CLI measurement report to the first UE (e.g., via a sidelink channel). This method may be used, for example, in a situation where the second UE is out of coverage of the base station.

[0009] In some examples, the base station may be able to reach the UE on a downlink channel, but the UE may not be able to reach the base station on an uplink channel. In this case, the base station may generate a CLI configuration for the UE and send the CLI configuration to the UE (e.g., via a downlink channel). However, the UE may send a CLI measurement report to another UE that has an uplink connection to the base station (e.g., via a sidelink channel). The other UE may then relay the CLI measurement report to the base station.

[0010] In some examples, a method of wireless communication at a first user device may include receiving a cross-link interference (CLI) configuration from a base station, determining that the CLI configuration is for a second UE, and sending the CLI configuration to the second UE after determining that the CLI configuration is for the second UE.

[0011] In some examples, the first user equipment may include a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor and the memory may be configured to receive a cross-link interference (CLI) configuration from a base station via the transceiver, determine that the CLI configuration is for a second UE, and send the CLI configuration to the second UE after determining that the CLI configuration is for the second UE.

[0012] In some examples, a first user device may include components for receiving a cross-link interference (CLI) configuration from a base station, components for determining that the CLI configuration is for a second UE, and components for sending the CLI configuration to the second UE after determining that the CLI configuration is for the second UE.

[0013] In some examples, an article for use by a first user device includes a computer-readable medium having instructions stored therein, the instructions being executable by one or more processors of the first user device to: receive a cross-link interference (CLI) configuration from a base station, determine that the CLI configuration is for a second UE, and send the CLI configuration to the second UE after determining that the CLI configuration is for the second UE.

[0014] One or more of the following features may apply to any of the methods, apparatus, and computer-readable media of the preceding paragraphs. Sending a CLI configuration may include sending the CLI configuration to a second UE via a sidelink channel. The CLI configuration may specify at least one CLI resource for the second UE to use for measurements for a CLI measurement report. The at least one CLI resource may include resources allocated to the first UE for uplink transmission to the base station and / or resources allocated to a third UE for uplink transmission to the base station. The CLI measurement report may be received from the second UE after the CLI configuration is sent to the second UE, it may be determined that the CLI measurement report is for the base station, and the CLI measurement report may be sent to the base station after determining that the CLI measurement report is for the base station. The CLI measurement report may indicate signal measurements made by the second UE on at least one CLI resource specified by the CLI configuration.

[0015] In some examples, a method of wireless communication at a first user device may include: receiving a cross-link interference (CLI) configuration specifying at least one CLI resource, measuring a signal on the at least one CLI resource, generating a CLI measurement report based on the measurement of the signal on the at least one CLI resource, and sending the CLI measurement report to a second UE.

[0016] In some examples, a first user equipment may include a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor and the memory may be configured to: receive a cross-link interference (CLI) configuration specifying at least one CLI resource, measure a signal on the at least one CLI resource, generate a CLI measurement report based on the measurement of the signal on the at least one CLI resource, and send the CLI measurement report to a second UE via the transceiver.

[0017] In some examples, a first user device may include: a component for receiving a cross-link interference (CLI) configuration specifying at least one CLI resource, a component for measuring a signal on at least one CLI resource, a component for generating a CLI measurement report based on the measurement of the signal on at least one CLI resource, and a component for sending the CLI measurement report to a second UE.

[0018] In some examples, an article for use by a first user device includes a computer-readable medium having instructions stored therein that are executable by one or more processors of the first user device to: receive a cross-link interference (CLI) configuration specifying at least one CLI resource, measure a signal on the at least one CLI resource, generate a CLI measurement report based on the measurement of the signal on the at least one CLI resource, and send the CLI measurement report to a second UE.

[0019] One or more of the following features may apply to any of the methods, apparatus, and computer-readable media of the preceding paragraphs. Sending a CLI configuration may include sending a CLI configuration to a second UE via a sidelink channel. Receiving a CLI configuration may include receiving a CLI configuration from a base station. At least one CLI resource may include a resource allocated by the base station for uplink transmission to the base station by a second UE or a third UE. It may be determined that the first UE cannot communicate with the base station via an uplink channel. Sending a CLI measurement report may include sending a CLI measurement report to the second UE via a sidelink channel after determining that the first UE cannot communicate with the base station via an uplink channel. Receiving a CLI configuration may include receiving a CLI configuration from a second UE. The CLI configuration may indicate that the first UE will send a CLI measurement report to the base station or the second UE. The CLI configuration may indicate that at least one CLI resource is an uplink resource or a sidelink resource.

[0020] In some examples, a method of wireless communication at a first user equipment may include receiving a message from a base station. In some aspects, the message may configure the first UE to schedule cross-link interference (CLI) measurements. The method may also include generating a first CLI configuration for a second UE after receiving the message, sending the first CLI configuration to the second UE, and receiving a CLI measurement report from the second UE after sending the first CLI configuration to the second UE.

[0021] In some examples, the first user equipment may include a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor and the memory may be configured to receive a message from a base station via the transceiver. In some aspects, the message may configure the first UE to schedule cross-link interference (CLI) measurements. The processor and the memory may also be configured to generate a first CLI configuration for a second UE after receiving the message, send the first CLI configuration to the second UE, and receive a CLI measurement report from the second UE after sending the first CLI configuration to the second UE.

[0022] In some examples, the first user equipment may include a component for receiving a message from a base station. In some aspects, the message may configure the first UE to schedule cross-link interference (CLI) measurements. The first user equipment may also include: a component for generating a first CLI configuration for a second UE after receiving the message, a component for sending the first CLI configuration to the second UE, and a component for receiving a CLI measurement report from the second UE after sending the first CLI configuration to the second UE.

[0023] In some examples, an article for use by a first user device includes a computer-readable medium having instructions stored therein, the instructions being executable by one or more processors of the first user device to receive a message from a base station. In some aspects, the message may configure the first UE to schedule cross-link interference (CLI) measurements. The computer-readable medium may also have instructions stored therein that are executable by one or more processors of the first user device to: generate a first CLI configuration for a second UE after receiving the message, send the first CLI configuration to the second UE, and receive a CLI measurement report from the second UE after sending the first CLI configuration to the second UE.

[0024] One or more of the following features may apply to any of the methods, apparatus, and computer-readable media of the preceding paragraphs. Sending a first CLI configuration may include sending the first CLI configuration to a second UE via a sidelink channel. Receiving a CLI measurement report may include receiving a CLI measurement report from a second UE via a sidelink channel. The second CLI configuration may be received from a base station. The second CLI configuration may specify at least one CLI resource for the first UE for measurement. Generating the first CLI configuration may include selecting a first resource from at least one CLI resource for the second UE for measurement and including an indication of the first resource in the first CLI configuration. The at least one CLI resource may include a resource allocated to a third UE for uplink transmission to the base station. Generating the first CLI configuration may include selecting a sidelink resource for the second UE for measurement and including an indication of the sidelink resource in the first CLI configuration. The sidelink resource may include a resource allocated to the third UE for sidelink transmission. Generating the first CLI configuration may include identifying interference to a first set of resources in a plurality of resources, selecting a sidelink resource from a second set of resources in a plurality of resources for the second UE for measurement, and including an indication of the sidelink resource in the first CLI configuration. The second set of resources may be different from the first set of resources.

[0025] In some examples, a method of wireless communication at a base station may include generating a cross-link interference (CLI) configuration for a first UE, sending the CLI configuration, and receiving a CLI measurement report generated by the first UE from a second UE after sending the CLI configuration.

[0026] In some examples, a base station may include a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor and the memory may be configured to generate a cross-link interference (CLI) configuration for a first UE, send the CLI configuration via the transceiver, and receive a CLI measurement report generated by the first UE from a second UE after sending the CLI configuration.

[0027] In some examples, a base station may include: a component for generating a cross-link interference (CLI) configuration for a first UE, a component for sending the CLI configuration, and a component for receiving a CLI measurement report generated by the first UE from a second UE after sending the CLI configuration.

[0028] In some examples, an article for use by a base station includes a computer-readable medium having instructions stored therein that can be executed by one or more processors of the base station to: generate a cross-link interference (CLI) configuration for a first UE, send the CLI configuration, and receive a CLI measurement report generated by the first UE from a second UE after sending the CLI configuration.

[0029] One or more of the following features may apply to any of the methods, apparatus, and computer-readable media of the preceding paragraphs. Sending a CLI configuration may include sending a CLI configuration to a first UE via a connection to the first UE. Sending a CLI configuration may include sending a CLI configuration to a second UE via a connection to the second UE. Sending a CLI configuration may include sending a message indicating that the second UE will forward the CLI configuration to the first UE. It may be selected to relay the CLI configuration to the second UE using the first UE after determining that the base station cannot communicate with the second UE. The CLI configuration may be sent to the second UE via a downlink channel after determining that the base station cannot communicate with the first UE via another downlink channel.

[0030] In some examples, a method of wireless communication at a base station may include selecting to use a first UE to schedule cross-link interference (CLI) measurements, generating a message to configure the first UE to schedule CLI measurements, and sending the message to the first UE.

[0031] In some examples, a base station may include a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor and the memory may be configured to: select to schedule a cross-link interference (CLI) measurement using a first UE, generate a message to configure the first UE to schedule the CLI measurement, and send the message to the first UE via the transceiver.

[0032] In some examples, a base station may include: a component for selecting to use a first UE to schedule cross-link interference (CLI) measurements, a component for generating a message to configure the first UE to schedule CLI measurements, and a component for sending the message to the first UE.

[0033] In some examples, an article for use by a base station includes a computer-readable medium having instructions stored therein that are executable by one or more processors of the base station to: select use of a first UE to schedule cross-link interference (CLI) measurements, generate a message configuring the first UE to schedule CLI measurements, and send the message to the first UE.

[0034] One or more of the following features may apply to any of the methods, apparatus, and computer-readable media of the preceding paragraphs. The message may configure the first UE to schedule CLI measurements on at least one uplink resource. The message may configure the first UE to schedule CLI measurements on at least one sidelink resource. Generating a message to configure the first UE to schedule CLI measurements may be triggered by determining that the base station cannot communicate with the first UE. Generating a message to configure the first UE to schedule CLI measurements may be triggered by determining that the base station cannot communicate with the first UE and by determining that the second UE has a sidelink connection to the first UE. Selecting to use the first UE to schedule CLI measurements may be triggered by selecting to use CLI measurements to determine UE positioning. Sidelink resources may be selected for CLI measurements after determining that Uu CLI resources are not currently configured. Selecting to use the first UE to schedule CLI measurements may be triggered by determining that Uu CLI resources will be used for CLI measurements.

[0035] After reading the following specific embodiments, these and other aspects of the present disclosure will be more fully understood. After reading the following description of specific exemplary embodiments of the present disclosure in conjunction with the accompanying drawings, other aspects, features and embodiments of the present disclosure will become apparent to those of ordinary skill in the art. Although the features of the present disclosure are discussed with respect to certain embodiments and drawings below, all embodiments of the present disclosure may include one or more of the advantageous features discussed herein. In other words, although one or more embodiments are discussed as having certain advantageous features, one or more of these features may also be used according to the various embodiments of the present disclosure discussed herein. Similarly, although the exemplary embodiments are discussed below as device, system or method embodiments, it should be understood that these exemplary embodiments may be implemented in various devices, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 is a schematic diagram of a wireless communication system according to some aspects.

[0037] Figure 2 is a conceptual diagram of an example of a radio access network in accordance with some aspects.

[0038] Figure 3 is a diagram of radio resources in an air interface utilizing orthogonal frequency division multiplexing (OFDM) according to some aspects.

[0039] Figure 4 is a conceptual diagram of an example of a wireless communication network with user equipment (UE) in an intra-cell deployment in accordance with some aspects.

[0040] Figure 5 is a conceptual diagram of an example of a wireless communication network with UEs in an inter-cell homogeneous deployment in accordance with some aspects.

[0041] Figure 6 is a conceptual diagram of example resource allocation for a UE in accordance with some aspects.

[0042] Figure 7 is a conceptual diagram of an example of a wireless communication network with UEs in an intra-cell deployment in accordance with some aspects.

[0043] Figure 8 is a conceptual diagram of an example of a wireless communication network with UEs in an intra-cell deployment in accordance with some aspects.

[0044] Fig. 9 is a conceptual diagram of an example of a wireless communication network with UEs in an intra-cell deployment in accordance with some aspects.

[0045] Fig.10 is a conceptual diagram of an example of a wireless communication network in which a UE relays CLI information in accordance with some aspects.

[0046] Fig.11 is a conceptual diagram of an example of a wireless communication network in which a UE communicates via sidelink signaling in accordance with some aspects.

[0047] Fig.12 is a conceptual diagram of an example of a wireless communication network in which sidelink signaling is used to determine UE positioning in accordance with some aspects.

[0048] Fig.13 is a conceptual diagram of an example of a wireless communication network in which a UE schedules CLI measurements in accordance with some aspects.

[0049] Fig.14 is a block diagram illustrating an example of a hardware implementation for a UE employing a processing system according to some aspects.

[0050] Fig.15 is a flow chart of an example CLI measurement method according to some aspects.

[0051] Fig.16 is a flow chart of an example CLI measurement method according to some aspects.

[0052] Fig.17 is a flow chart of an example CLI measurement method according to some aspects.

[0053] Fig.18 is a block diagram illustrating an example of a hardware implementation for a base station employing a processing system according to some aspects.

[0054] Fig.19 is a flow chart of an example CLI measurement method according to some aspects.

[0055] Fig. 20 is a flow chart of an example CLI measurement method according to some aspects. DETAILED DESCRIPTION

[0056] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it is apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid blurring such concepts.

[0057] Although various aspects and embodiments are described in this application by the description of some examples, it will be understood by those of ordinary skill in the art that additional implementations and use cases can be implemented in many different arrangements and scenarios. The innovations described herein can be implemented across multiple different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, each embodiment and / or use can be implemented via an integrated chip embodiment and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase equipment, medical equipment, devices supporting artificial intelligence, etc.). Although some examples may or may not be specifically for use cases or applications, various applicability of the innovations may occur. The range of implementations can be from chip-level or modular components to non-modular, non-chip-level implementations, and can also be aggregated, distributed, or OEM devices or systems that include one or more aspects of the described innovations. In some practical settings, the devices that combine the described aspects and features may also have to include additional components and features for implementing and practicing the claimed and described embodiments. For example, the transmission and reception of wireless signals must include a large number of components for both analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, one or more processors, interleavers, adders / accumulators, etc.) The innovations described herein are intended to be practiced in a variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., of varying sizes, shapes, and structures.

[0058] The various concepts presented throughout this disclosure may be implemented in 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 by way of limitation. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and at least one scheduled entity 106. The at least one scheduled entity 106 may be referred to as a user equipment (UE) 106 in the following discussion. The RAN 104 includes at least one scheduling entity 108. The at least one scheduling entity 108 may be referred to as a base station (BS) 108 in the following discussion. Through the wireless communication system 100, the UE 106 is able to perform data communications with an external data network 110 such as (but not limited to) the Internet.

[0059] 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 in accordance with the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification, which is commonly referred to as 5G. As another example, the RAN 104 may operate under a mix of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, commonly referred to as LTE. 3GPP refers to this hybrid RAN as the Next Generation RAN or NG-RAN. Of course, many other examples may be used within the scope of the present disclosure.

[0060] As shown, the RAN 104 includes a number of 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 background contexts, those skilled in the art may refer to a base station 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 eNode B (eNB), a gNode B (gNB), or some other suitable terminology.

[0061] The radio access network 104 is further shown to support wireless communications for a plurality of mobile devices. In the 3GPP standard, a mobile device may be referred to as a user equipment (UE) 106, but one of ordinary skill in the art may also refer to it as a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handheld device, a terminal, a user agent, a mobile client, a client, or some other appropriate term. A UE may be a device that provides access to network services to a user.

[0062] Within this document, a "mobile" device need not necessarily have mobile capabilities and may be stationary. The term mobile device or mobile device broadly refers to a wide variety of devices and technologies. A UE may include a plurality of hardware structural components designed in size, shape, and arrangement to facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, and the like that are 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, for example, corresponding to the "Internet of Things" (IoT). In addition, a mobile device may be a car or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio device, a global positioning system (GPS) device, an object tracking device, a drone, a multi-purpose helicopter, a quadcopter, a remote control device, a consumer 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, and the like, and / or a wearable device. In addition, the mobile device can be a digital home or smart home device such as home audio, video and / or multimedia equipment, home appliances, vending machines, smart lighting, home security systems, smart meters, etc. In addition, the mobile device can also be a smart energy device, security equipment, solar panels or solar arrays, municipal infrastructure equipment that controls electricity (e.g., smart grids), lighting, water, etc.; industrial automation and enterprise equipment; logistics controllers; agricultural equipment; military defense equipment, vehicles, aircraft, ships, weapons, etc. In addition, the mobile device can provide connected medicine or telemedicine support (i.e., remote health care). Telemedicine devices can include telemedicine monitoring devices and telemedicine management devices, whose communications can be prioritized or given priority access relative to other types of information, for example, priority access regarding the transmission of critical service data, and / or associated QoS for the transmission of critical service data.

[0063] Wireless communication between RAN 104 and UE 106 may be described as utilizing an air interface. Transmissions from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) over an air interface may 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 scheduling entity (further described below; e.g., base station 108). Another way to describe the 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 other aspects of the present disclosure, the term uplink may refer to point-to-point transmissions originating from a scheduled entity (further described below; e.g., UE 106).

[0064] In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a base station 108) allocates resources for communication between some or all devices and equipment within its service area or cell. In 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. That is, for scheduled communications, a UE 106, which may be a scheduled entity, may utilize resources allocated by the scheduling entity 108.

[0065] 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, scheduling resources for one or more scheduled entities (e.g., one or more other UEs).

[0066] like Figure 1 As shown, the scheduling entity 108 may broadcast downlink traffic 112 to one or more scheduled entities 106. In a broad sense, the scheduling entity 108 is a node or device responsible for scheduling traffic in the wireless communication network, which includes downlink traffic 112 and, in some examples, uplink traffic 116 from one or more scheduled entities 106 to the scheduling entity 108. On the other hand, the scheduled entity 106 is a node or device that receives downlink control information 114, which includes, but is not limited to, scheduling information (e.g., grants), synchronization or timing information, or other control information from another entity in the wireless communication network (e.g., the scheduling entity 108).

[0067] In addition, uplink and / or downlink control information and / or traffic information can be divided into frames, subframes, time slots and / or symbols in time. As used herein, a symbol can refer to a time unit in which each subcarrier carries a resource element (RE) in an orthogonal frequency division multiplexing (OFDM) waveform. A time slot can carry 7 or 14 OFDM symbols. A subframe can refer to a duration of 1ms. Multiple subframes or time slots can be combined together to form a single frame or radio frame. Of course, these definitions are not required, and any appropriate scheme for organizing waveforms can be utilized, and the various time divisions of waveforms can have any appropriate duration.

[0068] Typically, the base stations 108 may include a backhaul interface for communicating with a backhaul portion 120 of the wireless communication system. The backhaul 120 may provide a link between the base stations 108 and the core network 102. Furthermore, in some examples, the 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, etc.

[0069] 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.

[0070] Reference now Figure 2 , a schematic diagram of a RAN 200 is provided by way of example and not limitation. In some examples, the RAN 200 may be similar to that described above and in Figure 1 The geographic area covered by the RAN 200 may be divided into cellular areas (cells) that may be uniquely identified by a user equipment (UE) based on an identity broadcast from an access point or base station. Figure 2 Macro cells 202, 204, and 206 and small cells 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 can 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 antenna groups, where each antenna is responsible for communicating with UEs in a portion of the cell.

[0071] Various base station arrangements can be used. Figure 2, two base stations 210 and a base station 212 are shown in cells 202 and 204; and a third 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 by a feeder cable. In the example shown, cells 202, 204, and 206 may be referred to as macro cells because base stations 210, 212, and 214 support cells with larger sizes. In addition, base station 218 is shown in a small cell 208 (e.g., a micro cell, a pico cell, a femto cell, a home base station, a home node B, a home eNode B, etc.) that may overlap with one or more macro cells. In this example, since base station 218 supports cells with relatively small sizes, cell 208 may be referred to as a small cell. Cell sizing may be performed based on system design and component constraints.

[0072] It should be understood that the radio access network 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 Figure 1 The base station / scheduling entity 108 is the same as shown in .

[0073] 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, and 218 may be configured to provide access to a core network (e.g., such as a base station 210, 212, 214, and 218) for all UEs in the corresponding cell. Figure 1 For example, UE 222 and UE 224 may communicate with base station 210; UE 226 and UE 228 may communicate with base station 212; UE 230 and UE 232 may communicate with base station 214 via RRH 216; and UE 234 may communicate with base station 218. In some examples, UE 222, 224, 226, 228, 230, 232, 234, 238, 240, and / or 242 may communicate with the base stations described above and in Figure 1 The UE / scheduled entity 106 shown in FIG. 1 is the same as that shown in FIG.

[0074] In some examples, an unmanned aerial vehicle (UAV) 220, which may be a drone or a quadcopter, may be a mobile network node and may be configured to act as a UE. For example, UAV 220 may operate within cell 202 by communicating with base station 210. In some examples, UAV 220 may be configured to act as a BS. That is, in some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile base station (such as UAV 220).

[0075] On the other hand of RAN 200, sidelink signals can be used between UEs without having to rely on scheduling or control information from a base station. For example, two or more UEs (e.g., UE 226 and 228) can communicate with each other using peer-to-peer (P2P) or sidelink signals 227 without relaying the communication through a base station (e.g., base station 212). In another example, UE 238 is illustrated communicating with UEs 240 and 242. Here, UE 238 can be used as a scheduling entity or a primary sidelink device, and UEs 240 and 242 can be used as scheduled entities or non-primary (e.g., auxiliary) sidelink devices. In another example, the UE can act as a scheduling entity in a device-to-device (D2D), peer-to-peer (P2P) or vehicle-to-vehicle (V2V) network and / or a mesh network. In the mesh network example, UE 240 and UE 242 can optionally communicate directly with each other in addition to communicating with UE 238 (e.g., acting as a scheduling entity). Thus, in a wireless communication system that schedules access to time-frequency resources and has a cellular configuration, a P2P configuration, or a mesh configuration, a scheduling entity and one or more scheduled entities can communicate using the scheduled resources. In some examples, the sidelink signal 227 includes sidelink traffic (e.g., a physical sidelink shared channel) and sidelink control (e.g., a physical sidelink control channel).

[0076] In some examples, two or more UEs (e.g., UE 226 and UE 228) within the coverage area of ​​serving base station 212 can communicate with base station 212 using cellular signals, and communicate with each other using direct link signals (e.g., sidelink signals 227) without relaying the communication through the base station. In an example of a V2X network within the coverage area of ​​base station 212, base station 212 and / or one or both of UE 226 and UE 228 can act as a scheduling entity to schedule sidelink communications between UE 226 and UE 228.

[0077] The two main technologies that V2X networks can use include dedicated short-range communications (DSRC) based on the IEEE 802.11p standard and cellular V2X based on LTE and / or 5G (new radio) standards. V2X networks can connect vehicles to each other (vehicle-to-vehicle (V2V)), to road infrastructure (vehicle-to-infrastructure (V2I)), to pedestrians / cyclists (vehicle-to-pedestrian (V2P) (e.g., mobile devices such as user equipment (UE) and / or wearable devices of pedestrians / cyclists)), and / or to networks (vehicle-to-network (V2N)). For simplicity, various aspects of the present disclosure may refer to new radio (NR) cellular V2X networks, referred to herein as V2X networks. However, it should be understood that the concepts disclosed herein may not be limited to a specific V2X standard, or may be directed to sidelink networks other than V2X networks.

[0078] The sidelink signal 227 between UEs 226 and 228 or between UEs 238, 240, and 242 may be sent via a proximity service (ProSe) PC5 interface. ProSe communication may support different operation scenarios, such as in-coverage, out-of-coverage, and partial coverage. Out-of-coverage refers to a scenario in which a UE (e.g., UEs 238, 240, and 242) is outside the coverage of a base station (e.g., base station 212), but each UE is still configured for ProSe communication. Partial coverage refers to a scenario in which a UE is outside the coverage area of ​​a base station, while one or more other UEs communicating with the UE are within the coverage area of ​​the base station. In-coverage refers to a scenario in which a UE (e.g., UEs 226 and 228) communicates with a base station (e.g., base station 212) via a Uu connection (e.g., UE to RAN cellular interface) to receive ProSe service authorization and provisioning information to support ProSe operation.

[0079] In the radio access network 200, the ability of a UE to communicate independently of its location while moving is called mobility. The various physical channels between the UE and the radio access network are usually established, maintained, and released under the control of the access and mobility management function (AMF). AMF ( Figure 2 ) may include a Security Context Management Function (SCMF) for managing security contexts for both control plane and user plane functions, and a Security Anchor Function (SEAF) for performing authentication.

[0080] The radio access network 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, a UE may monitor various parameters of a signal from its serving cell and various parameters of neighboring cells. Depending 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 (shown as a vehicle, but any suitable form of UE may be used) 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 or quality of its serving cell 202 for a given amount of time, the UE 224 may send a report message to its serving base station 210 indicating the condition. In response, UE 224 may receive a handover command, and the UE may perform a handover to cell 206 .

[0081] In a network configured for UL-based mobility, the UL reference signal from each UE can be used by the network to select a serving cell for each UE. In some examples, base stations 210, 212, and 214 / 216 can broadcast a unified synchronization signal (e.g., a unified primary synchronization signal (PSS), a unified secondary synchronization signal (SSS), and a unified physical broadcast channel (PBCH)). UE 222, 224, 226, 228, 230, and 232 can receive a unified synchronization signal, derive carrier frequency and slot timing from the synchronization signal, and send an uplink pilot or reference signal in response to the derived timing. The uplink pilot signal sent by the UE (e.g., UE 224) can be received simultaneously by two or more cells (e.g., base stations 210 and 214 / 216) in the radio access network 200. Each cell can measure the strength of the pilot signal, and the radio access network (e.g., one or more of base stations 210 and 214 / 216 and / or a central node within the core network) can determine the serving cell for UE 224. As UE 224 moves in radio access network 200, the network may continue to monitor uplink pilot signals sent by 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, network 200 may switch UE 224 from the serving cell to the neighboring cell with or without notifying UE 224.

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

[0083] In various implementations, the air interface in the radio access network 200 can utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum typically provides dedicated use of a portion of the spectrum by 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-authorized license. Although some technical rules generally still need to be followed to access the unlicensed spectrum, generally speaking, any operator or device can obtain access qualifications. Shared spectrum may be between licensed spectrum and unlicensed spectrum, where technical rules or restrictions may be required to access the spectrum, but the spectrum may still be shared by multiple operators and / or multiple RATs. For example, a license holder of a portion of the licensed spectrum may provide licensed shared access (LSA) to share the spectrum with other parties (e.g., with conditions for obtaining access qualifications determined by the appropriate licensee).

[0084] The air interface in the radio access network 200 may use one or more multiplexing and multiple access algorithms to enable simultaneous communication of various devices. For example, using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP), the 5G NR specification provides multiple access for UL transmissions from UE 222 and 224 to the base station 210 and multiplexing for DL ​​transmissions from the base station 210 to one or more UEs 222 and 224. In addition, for UL transmissions, the 5G NR specification also provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also known 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, multiplexed 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.

[0085] The air interface in the radio access network 200 can further 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 both endpoints can communicate with each other at the same time. Half-duplex means that only one endpoint can send information to the other endpoint at a time point. In a wireless link, a full-duplex channel usually relies on the physical isolation of the transmitter and the receiver and suitable interference elimination techniques. Full-duplex simulation is often implemented for a wireless link by utilizing frequency division duplex (FDD) or time division duplex (TDD). In FDD, the transmission in different directions operates with different carrier frequencies. In TDD, time division multiplexing is used to separate the transmission in different directions on a given channel from each other. That is, at certain times, 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, wherein the direction can change very quickly, for example, several times per time slot.

[0086] Various aspects of the present disclosure will be described with reference to OFDM waveforms, examples of which are described in Figure 3 Schematically illustrated in FIG. It will be appreciated by those skilled 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.

[0087] Reference now Figure 3 , illustrates an expanded view of an example DL subframe (SF) 302A showing an OFDM resource grid 304. However, as will be readily appreciated by those skilled in the art, the PHY transmission structure for any particular application may differ from the examples described herein depending on many factors. Here, time is in the horizontal direction in units of OFDM symbols; and frequency is in the vertical direction in units of subcarriers.

[0088] 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 antenna ports available, a corresponding multiple number of resource grids 304 may be available for communication. Resource grid 304 is divided into multiple resource elements (REs) 306. RE (which is 1 subcarrier × 1 symbol) is the smallest discrete part of the time-frequency grid and contains a single complex value representing data or signals from a physical channel. Depending on the modulation utilized in a specific implementation, each RE can represent one or more information bits. In some examples, a block of REs can be referred to as a physical resource block (PRB), or more simply a resource block (RB) 308, which contains any appropriate number of consecutive subcarriers in the frequency domain. In one example, an RB can include 12 subcarriers, which is a number independent of the numerology used. In some examples, depending on the numerology, an RB can include any appropriate number of consecutive OFDM symbols in the time domain. In the present disclosure, it is assumed that a single RB (such as RB 308) corresponds entirely to a single communication direction (transmission or reception of a given device).

[0089] Scheduling a UE (e.g., a scheduled entity) for downlink, uplink, or sidelink transmissions typically involves scheduling one or more resource elements 306 within one or more subbands or bandwidth parts (BWPs). Each BWP may include two or more contiguous or consecutive RBs. Thus, a UE typically utilizes only a subset of a resource grid 304. In some examples, an RB may be the smallest unit of resources that may be allocated to a UE. Thus, 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, eNB, RSU, etc.) or may be self-scheduled by a UE implementing D2D sidelink communications.

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

[0091] Each 1 ms subframe 302A may be composed of one or more adjacent time slots. Figure 3In the example shown, as an illustrative example, a subframe 302B includes four time slots 310. In some examples, time slots can be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot can include 7 or 14 OFDM symbols with a nominal CP. Other examples may include micro-time slots with shorter durations (e.g., one or two OFDM symbols). In some cases, these micro-time slots can be sent, occupying resources scheduled for ongoing time slot transmissions by the same or different UEs. Within a subframe or time slot, any number of resource blocks can be utilized.

[0092] An expanded view of one of the time slots 310 illustrates the time slot 310, which includes a control region 312 and a data region 314. In general, the control region 312 may carry a control channel (e.g., PDCCH), and the data region 314 may carry a data channel (e.g., PDSCH or PUSCH). Of course, a time slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. Figure 3 The structure illustrated in is merely exemplary in nature, and different slot structures may be utilized and may include one or more of each of the control region and the data region.

[0093] Although in Figure 3 Although not shown in the figure, each RE 306 within the RB 308 can be scheduled to carry one or more physical channels including control channels, shared channels, data channels, etc. Other REs 306 within the RB 308 can also carry pilot or reference signals, including but not limited to demodulation reference signals (DMRS), control reference signals (CRS), or sounding reference signals (SRS). These pilot or reference signals can be provided to a receiving device to perform channel estimation of the corresponding channel, which can enable coherent demodulation / detection of control and / or data channels within the RB 308.

[0094] In some examples, time slot 310 may be used for broadcast or unicast communication. In a V2X or D2D network, broadcast communication may refer to point-to-multipoint transmission from one device (e.g., a vehicle, a base station (e.g., RSU, gNB, eNB, etc.), a UE, or other similar device) to other devices. Unicast communication may refer to point-to-point transmission from one device to a single other device.

[0095] In one example, the control region 312 of the time slot 310 may include a physical downlink control channel (PDCCH) including downlink control information (DCI) sent by a base station (e.g., gNB, eNB, RSU, etc.) to one or more UEs in a set of UEs, which may include one or more sidelink devices (e.g., V2X / D2D devices). In some examples, the DCI may include synchronization information to synchronize communications by multiple sidelink devices on the sidelink channel. In addition, the DCI may include scheduling information indicating one or more resource blocks allocated to the sidelink device for sidelink communications within the control region 312 and / or the data region 314. For example, the control region 312 of the time slot may also include control information sent by the sidelink device via the sidelink channel, and the data region 314 of the time slot 310 may include data sent by the sidelink device via the sidelink channel. In some examples, the control information may be sent within a physical sidelink control channel (PSCCH), and the data may be sent within a physical sidelink shared channel (PSSCH).

[0096] In DL transmission, a transmitting device (e.g., a scheduling entity) may allocate one or more REs 306 (e.g., within a control region 312) to carry DL control information including one or more DL control channels (such as PBCH; physical control format indicator channel (PCFICH); physical hybrid automatic repeat request (HARQ) indicator channel (PHICH); and / or physical downlink control channel (PDCCH), etc.) to one or more scheduled entities. The transmitting device may also allocate one or more REs 306 to carry other DL signals, such as DMRS; phase tracking reference signal (PT-RS); channel state information-reference signal (CSI-RS); primary synchronization signal (PSS), and secondary synchronization signal (SSS).

[0097] The synchronization signals PSS and SSS, and in some examples the PBCH and PBCH DMRS, may be sent in a synchronization signal block (SSB) comprising 3 consecutive OFDM symbols, numbered via time indices in ascending order from 0 to 3. In the frequency domain, the SSB may extend over 240 contiguous subcarriers, numbered via frequency indices in ascending order from 0 to 239. Of course, the present disclosure is not limited to this particular SSB configuration. Other non-limiting examples may utilize more or less than two synchronization signals; may include one or more supplemental channels in addition to the PBCH; may omit the PBCH; and / or may utilize different numbers of symbols and / or non-contiguous symbols for the SSB within the scope of the present disclosure.

[0098] The PCFICH provides information to assist the receiving device in receiving and decoding the PDCCH. The PDCCH carries downlink control information (DCI), including but not limited to power control commands, scheduling information, grants, and / or assignments of REs for DL ​​and UL transmissions. The PHICH carries HARQ feedback transmissions, such as acknowledgments (ACKs) or negative acknowledgments (NACKs). HARQ is a technology well known to those of ordinary skill in the art, in which, for example, the integrity of packet transmissions can be checked on the receiving side using any suitable integrity check mechanism, such as a checksum or a cyclic redundancy check (CRC) to ensure accuracy. If the integrity of the transmission is confirmed, an ACK can be sent, and if it is not confirmed, a NACK can be sent. In response to the NACK, the transmitting device can send a HARQ retransmission, which can implement chase combining, incremental redundancy, and the like.

[0099] In UL transmission, a transmitting device (e.g., a scheduled entity) may utilize one or more REs 306 to carry UL control information including one or more UL control channels, such as a physical uplink control channel (PUCCH), to a scheduling entity. The UL control information may include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. For example, the UL control information may include a DMRS or an SRS. In some examples, the control information may include a scheduling request (SR), i.e., a request to a scheduling entity to schedule an uplink transmission. Here, in response to the SR sent on the control channel, the scheduling entity may send downlink control information that may schedule resources for uplink packet transmission. The UL control information may also include HARQ feedback, channel state feedback (CSF), or any other suitable UL control information.

[0100] In an example of cellular communication over a cellular carrier via a Uu interface, for DL ​​transmission, a scheduling entity (e.g., a base station) may allocate one or more REs 306 (e.g., within a control region 312 of a slot 310) to carry DL control information including one or more DL control channels or DL ​​signals (such as synchronization signal blocks (SSBs), demodulation reference signals (DMRSs), channel state information-reference signals (CSI-RSs), PDCCHs, etc.) to one or more scheduled entities (e.g., UEs). The PDCCH carries downlink control information (DCI), including, for example, scheduling information providing grants and / or assignments of REs for DL ​​and UL transmissions.

[0101] In a UL transmission over the Uu interface, the scheduled entity may utilize one or more REs 306 to carry UL control information (UCI) including one or more UL control channels, such as a physical uplink control channel (PUCCH), to the scheduling entity. For example, the UCI may include pilots, reference signals, and information that enables or assists in decoding the uplink data transmission. For example, the UCI may include a DMRS or an SRS. In some examples, the UCI may include a scheduling request (SR), i.e., a request to the scheduling entity to schedule an uplink transmission.

[0102] In addition to control information, one or more REs 306 (e.g., within data region 314) may be allocated for user data or traffic data. Such traffic may be carried on one or more traffic channels (such as PDSCH for DL ​​transmissions or physical uplink shared channel (PUSCH) for UL transmissions). In some examples, one or more REs 306 within data region 314 may be configured to carry SIBs (e.g., SIB1) that carry system information that may enable access to a given cell.

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

[0104] References Figures 1 to 3 The channels or carriers described are not necessarily all channels or carriers that may be utilized between a scheduling entity and a scheduled entity, and one of ordinary skill in the art will recognize that other channels or carriers (such as other traffic, control, and feedback channels) may be utilized in addition to those shown.

[0105] Figure 4 An example wireless communication network 400 is illustrated in which a base station 402 communicates with a UE 404 (UE1) and a UE 404 (UE2) in an intra-cell deployment according to some aspects. The base station 402 (e.g., a cellular base station (e.g., referred to as a gNB in ​​5G NR)) provides a cell coverage area 408 ( Figure 4 1) provides wireless services to UEs (e.g., UEs 404 and 406) within a cell 1). Thus, as shown, UEs 404 and 406 are located within a cell coverage area 408. In some examples, base station 402 may correspond to Figure 1 and / or Figure 2 In some examples, UEs 404 and 406 may correspond to any base station or scheduling entity shown in Figure 1and / or Figure 2 Any UE or scheduled entity shown in .

[0106] As shown, UE 404 sends an uplink (UL) signal 410 to base station 402. In addition, UE 406 receives a downlink (DL) signal 412 from base station 402. These signals may be Uu signals as described herein. A portion 414 of the UL signal sent by UE 404 may be received by UE 406, while UE 406 receives DL signal 412 from base station 402. This portion 414 of the UL signal sent by UE 404 may interfere (e.g., in the form of noise) with UE 406 receiving DL signal 412. This type of interference is referred to as cross link interference (CLI), or more specifically, UE to UE CLI. UE 404 may be referred to as an aggressor UE (A-UE) because it is the source of the interference signal, and UE 406 may be referred to as a victim UE (V-UE) because the interference signal affects its reception of DL signal 412 from base station 402.

[0107] As discussed in more detail herein, the base station 402 (or an associated network) can instruct the victim UE 406 to perform measurements of CLI and report the measurements to the base station 402. Upon receiving the CLI measurement report from the UE 406, the base station 402 can take measures to mitigate CLI. For example, the base station 402 can configure a slot format for the aggressor UE 404 and / or a slot format for the victim UE 406 so that UL transmissions and DL receptions do not collide or overlap in the time domain. As another example, the base station 402 can reduce the UL transmit power of the aggressor UE 404, thereby reducing the CLI to the victim UE 406. The base station 402 can take other CLI mitigation measures.

[0108] Likewise, as discussed herein, the CLI measurement by the victim UE 406 may be performed by monitoring at least one resource used for transmission by the aggressor UE 404. For example, the victim UE 406 may determine a received signal strength indication (RSSI) based on a measurement of a portion 414 of the UL signal transmitted by the aggressor UE 404 (e.g., an estimated total energy within a particular frequency bandwidth in the portion 414 of the UL signal). Alternatively or additionally, the CLI measurement by the victim UE 406 may be performed by determining a reference signal received power (RSRP) based on a reference signal (such as a sounding reference signal (SRS)) in the portion 414 of the UL signal transmitted by the aggressor UE 404. The victim UE 406 may employ other techniques to determine the CLI caused by the portion 414 of the UL signal transmitted by the aggressor UE 404.

[0109] The CLI can be used in Figure 4 It may occur between UEs in the same cell or between UEs in different cells. Figure 5 An example is illustrated in which UEs are located in different cells.

[0110] Figure 5 An example wireless communication network 500 is illustrated that includes a first cell coverage area 502 (referred to as cell 1) and a second cell coverage area 504 (referred to as cell 2) in an inter-cell homogeneous deployment according to some aspects. A base station 506 (e.g., a cellular base station (e.g., referred to as a gNB in ​​5G NR)) provides wireless services to UEs (such as UE 508) within the first cell coverage area 502. Therefore, as shown, UE 508 is located within the first cell coverage area 502. A base station 510 (e.g., a cellular base station (e.g., referred to as a gNB in ​​5G NR)) provides wireless services to UEs (such as UE 512) within the second cell coverage area 504. Therefore, as shown, UE 512 is located within the second cell coverage area 504. In some examples, base stations 506 and 510 may correspond to Figure 1 , Figure 2 and Figure 4 In some examples, UE 508 and 512 may correspond to any base station or scheduling entity shown in any of the examples. Figure 1 , Figure 2 and Figure 4 Any UE or scheduled entity shown in any of the .

[0111] This configuration of the wireless communication network 520 is referred to as an inter-cell homogeneous deployment. That is, since the UE 508 is served by the first base station 506 (which is different from the second base station 510 serving the UE 512), the configuration is an inter-cell deployment. Likewise, since the first cell coverage area 502 of the first base station 506 does not substantially overlap with the second cell coverage area 504 of the second base station 510, the configuration is a homogeneous deployment. In a homogeneous deployment, the first cell coverage area 502 may have a similar size to the second cell coverage area 504.

[0112] UE 508 transmits an uplink (UL) signal 514 to first base station 506. UE 512 receives a downlink (DL) signal 516 from second base station 510. These signals may be Uu signals as described herein. A portion 518 of the UL signal transmitted by UE 508 may be received by UE 512, while UE 512 receives the DL signal 516 from second base station 510. The portion 518 of the UL signal transmitted by UE 508 may cause CLI to the reception of the DL signal 516 by UE 512. Thus, in Figure 5, UE 508 is an aggressor UE (A-UE), and UE 512 is a victim UE (V-UE).

[0113] The second base station 510 (or an associated network) may instruct the victim UE 512 to perform measurements of CLI and report the measurements to the second base station 510. In response, the second base station 510 may take measures to mitigate CLI, such as configuring a slot format for the aggressor UE 508 (e.g., by communicating with the first base station 506 via an X2 signaling link) and / or configuring a slot format for the victim UE 512 so that UL transmission and DL reception do not collide or overlap in the time domain. The second base station 510 may take other CLI mitigation measures.

[0114] Figure 6 An example of CLI between UL resources for a first UE (referred to as UE1) and DL resources for a second UE (referred to as UE2) is illustrated. Figure 6 The time domain diagram 600 of FIG. 6 illustrates a first time slot 602 scheduled for UE1 and a second time slot 604 scheduled for UE2 according to some aspects. The horizontal axis of the time domain diagram 600 represents time. In some examples, each time slot has a length of 14 OFDM symbols (numbered 0 to 13) as defined in 5G NR. In other examples, the length of the time slot can have a different number of OFDM symbols.

[0115] The time slot format of UE1 has OFDM symbols 0-5 designated for downlink (D) reception, OFDM symbols 6-7 designated as flexible (eligible for uplink (U) transmission or downlink (D) reception), and OFDM symbols 8-13 designated for uplink (U) transmission. The time slot format of UE2 has OFDM symbols 0-9 designated for downlink (D) reception, OFDM symbols 10-11 designated as flexible (eligible for uplink (U) transmission or downlink (D) reception), and OFDM symbols 12-13 designated for uplink (U) transmission. In this example, OFDM symbols 0-13 of the time slot belonging to UE1 are logically time-aligned with OFDM symbols 0-13 of the time slot belonging to UE2. However, since the propagation delay is different, the physical time alignment of the time slots may not be exact.

[0116] like Figure 6As shown, OFDM symbols 8-9 of the UE1 time slot designated for uplink (U) transmission logically overlap in the time domain with OFDM symbols 8-9 of the UE2 time slot. If UE1 and UE2 are close enough to each other, the uplink (U) signal transmission of UE1 during OFDM symbols 8-9 will interfere with the downlink (D) signal reception of UE2 during OFDM symbols 8-9. Therefore, as represented by the dashed rectangle 606 around the OFDM symbols 8-9 of the time slots of UE1 and UE2, cross-link interference (CLI) 608 may occur at the receiver of UE2. As a result, due to the CLI, UE2 may not be able to receive and decode the downlink (D) signal.

[0117] The slot formats of UE1 and UE2 may be independent of each other. That is, the OFDM symbols designated for the downlink in the slot format for one of the UEs need not coincide in time with the OFDM symbols designated for the uplink in the slot format for the other UE. Thus, the aggressor UE may or may not transmit when the victim UE is receiving. The UE performs CLI measurements based on the scheduling configuration and in some examples is independent of the slot format of the potential aggressor UE.

[0118] In view of the above, CLI measurements can be used for Uu interference management to account for DL / UL symbol pattern differences between UEs (e.g. Figure 6 ). For example, the base station may configure the UE to monitor for CLI periodically or at other times and frequencies, as discussed further herein. Thus, the victim UE may perform CLI measurements on CLI resources specified in a CLI configuration (e.g., generated by the base station), where the CLI resources correspond to resources used by the aggressor UE for transmission.

[0119] refer to Figures 4 to 6 For UE1 and UE2, the CLI measurement process may include the following operations. UE1 performs uplink transmission to its serving base station on specific resources. UE2 is configured with corresponding CLI measurement resources. For example, the base station may send a CLI configuration specifying CLI resources to UE2, which CLI resources correspond to the same time and frequency resources used by UE1 for its uplink transmission. Based on the CLI configuration, UE2 measures CLI on the configured resources. For example, UE2 may measure RSSI and / or RSRP. UE2 then reports the measurement results to the network (e.g., base station).

[0120] Conventionally, CLI measurement configuration for CLI measurements of NR signals is provided by the base station, as described above. However, in some situations, network-based CLI resource configuration is not available. For example, if a UE (e.g., a reduced capability (RedCap) UE) has lower coverage capability than a regular UE (e.g., because the RedCap UE has fewer antennas and / or smaller antennas), the RedCap UE may be out of coverage of the network even if other nearby UEs are within the coverage of the network. In this case, the CLI configuration cannot be provided directly by the base station to the RedCap UE. Figure 7 An example of this scenario is illustrated.

[0121] Figure 7 An example wireless communication network 700 is illustrated in which a base station 702 can communicate with a UE 704 (UE1), a UE 706 (UE2), and a UE 708 (UE3) in an intra-cell deployment according to some aspects. In some examples, the base station 702 can correspond to Figure 1 , Figure 2 , Figure 4 and Figure 5 In some examples, UEs 704, 706, and 708 may correspond to any base station or scheduling entity shown in any of the examples. Figure 1 , Figure 2 , Figure 4 and Figure 5 Any UE or scheduled entity shown in any of the .

[0122] Base station 702 (e.g., a cellular base station (e.g., referred to as gNB in ​​5G NR)) provides wireless services to UEs (such as UE 704 and 708) within a cell coverage area 710. For example, UE 704 can communicate with base station 702 via Uu signaling 714. In addition, UE 708 can communicate with base station 702 via Uu signaling 716. However, due to the limited capabilities of UE 706, base station 702 provides wireless services to UE 706 within a smaller cell coverage area 712. Therefore, in Figure 7 In the example of , UE 706 is unable to communicate directly with base station 702 via Uu signaling (eg, UL and DL signaling) at its current location.

[0123] UE 704 may send an uplink (UL) signal to base station 702 via Uu signaling 714. A portion 718 of the UL signal sent by UE 704 may be received by UE 706 as a CLI.

[0124] Similarly, UE 708 may send an uplink (UL) signal to base station 702 via Uu signaling 716. A portion 720 of the UL signal sent by UE 708 may be received by UE 706 as a CLI.

[0125] However, as described above, since UE 706 is not within the cell coverage area 712, base station 702 cannot directly send CLI configuration to UE 706 to request UE 706 to perform CLI measurement. Therefore, in this scenario, the base station cannot alleviate the CLI problem.

[0126] In some aspects, the disclosure relates to exchanging CLI-related information using a UE within coverage of a cellular network (eg, a cell coverage area of ​​a base station) with a UE not within coverage of the cellular network (eg, a RedCap UE).

[0127] In some aspects, the present disclosure also relates to using CLI measurements to measure path loss or range between a set of UEs. For example, the path loss or range information can be used for UE-based positioning enhancement. However, using Uu CLI resources configured by the base station may exhaust a large amount of Uu resources that can be better used for other purposes. That is, CLI measurements based on Uu signaling between UEs may be less efficient.

[0128] Thus, in some aspects, the present disclosure relates to configuring and performing CLI measurements using sidelink signals for UE positioning applications. For example, a UE (e.g., referred to as a positioning UE) may act as a coordinator to schedule CLI measurements on one or more sidelink channels. Here, both CLI scheduling and CLI measurements may be performed on sidelink resources, thereby reserving Uu resources for other purposes. In some aspects, such sidelink-based UE positioning techniques may enhance the coverage of CLI measurements (e.g., because UEs outside of the coverage of the network may still perform CLI measurements) and save resource costs for CLI resource configuration (e.g., by avoiding the use of Uu resources for at least some CLI measurements).

[0129] In some aspects, the present disclosure relates to two modes of CLI measurement configuration. For example, both modes can be used to enable a UE (eg, RedCap UE) out of network coverage to obtain CLI measurement configuration and / or report CLI measurements.

[0130] In the first mode (Mode 1), the first UE (a UE connected to the network) relays the network's CLI configuration to a second UE (e.g., a UE out of coverage). For example, the first UE may relay the CLI measurement configuration from the network responsible for scheduling the second UE for CLI measurements. Thus, in Mode 1, the connected UE acts as a relay.

[0131] In the second mode (Mode 2), a first UE (a UE connected to the network) generates a CLI configuration for a second UE (e.g., a UE out of coverage). In some examples, the first UE may use its own CLI configuration (or a configured resource subset or measurement opportunity) previously provided by the network as the CLI configuration for the second UE.

[0132] In both Mode 1 and Mode 2, the connected UE maintains a connection with the base station and also maintains a sidelink connection with at least one other UE (which may be referred to herein as a CLI UE). Mode 1 will refer to Figure 8 and Fig. 9 Describe in more detail.

[0133] Figure 8 The diagram illustrates a scenario where a base station is able to send CLI configuration to a UE but is unable to receive CLI measurement reports from the UE. Here, the DL has sufficient coverage so that a CLI UE (e.g., UE2) is able to receive CLI resource configuration from its serving base station. However, the UL of the CLI UE has limited coverage (e.g., due to the limited transmission capability of the CLI UE). Therefore, the CLI UE cannot directly send measurement reports to the base station via the UL channel. In this case, the connected UE can act as a UL CLI report relay. That is, the connected UE (e.g., UE1) can relay the CLI measurement report generated by the CLI UE to the base station.

[0134] Figure 8 An example wireless communication network 800 is illustrated in which a base station 802 can communicate with a UE 804 (UE1), a UE 806 (UE2), and a UE 808 (UE3) in an intra-cell deployment according to some aspects. In some examples, the base station 802 can correspond to Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 6 and Figure 7 In some examples, UEs 804, 806, and 808 may correspond to any base station or scheduling entity shown in any of the examples. Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 6 and Figure 7Any UE or scheduled entity shown in any of the .

[0135] A base station 802 (e.g., a cellular base station (e.g., referred to as a gNB in ​​5G NR)) provides wireless services to UEs (e.g., UEs 804, 806, and 808) within a cell coverage area 810. For example, UE 804 can communicate with base station 802 via Uu signaling 814. In addition, UE 808 can communicate with base station 802 via Uu signaling 816. However, due to the limited capabilities of UE 806, base station 802 may only provide downlink services to UE 806 within cell coverage area 810 via Uu signaling 818. For example, due to the limited transmission power of UE 806, base station 802 may only provide uplink services to UE 806 within a smaller cell coverage area 812.

[0136] UE 808 may send an uplink (UL) signal to base station 802 via Uu signaling 816. A portion 820 of the UL signal sent by UE 808 may be received by UE 806 as a CLI.

[0137] The base station may send a CLI configuration to the UE 806, the CLI configuration instructing the UE 806 to measure the CLI on resources used for UL transmission by the UE 808. In this case, since the UE 806 cannot directly send the CLI measurement report to the base station 802 via UL signaling (e.g., Uu signaling), the UE 806 may send the measurement report to the UE 804 via the sidelink 822, whereupon the UE 806 relays the measurement report to the base station (e.g., via Uu signaling 814).

[0138] Fig. 9 The diagram illustrates a scenario where the base station cannot communicate directly with the UE on the DL or UL. In this case, the connected UE can act as a CLI configuration relay. For example, the base station can configure the UE connected to the base station (e.g., UE1) to relay the CLI resource configuration from the base station to the CLI UE (e.g., UE2). In addition, the base station can configure the connected UE (e.g., UE1) to relay the CLI measurement report generated by the CLI UE (e.g., UE2) to the base station. This latter operation may not be used for UE-based positioning applications. In some examples, the base station may configure the connected UE using RRC configuration.

[0139] Fig. 9 An example wireless communication network 900 is illustrated in which a base station 902 can communicate with UE 904 (UE1), UE 906 (UE2), UE 908 (UE3), and UE 910 (UE4) in an intra-cell deployment according to some aspects. In some examples, base station 902 can correspond to Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 6 , Figure 7 and Figure 8 In some examples, UEs 904, 906, 908, and 910 may correspond to any base station or scheduling entity shown in any of the examples. Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 6 , Figure 7 and Figure 8 Any UE or scheduled entity shown in any of the .

[0140] Base station 902 (e.g., a cellular base station (e.g., referred to as gNB in ​​5G NR)) provides wireless services to UEs (e.g., UEs 904, 908, and 910) within a cell coverage area 912. For example, UE 904 can communicate with base station 902 via Uu signaling 916. In addition, UE 908 can communicate with base station 902 via Uu signaling 918. Similarly, UE 910 can communicate with base station 902 via Uu signaling 920. However, due to the limited capabilities of UE 906, base station 902 may only provide services to UE 906 within a smaller cell coverage area 914. Therefore, in Fig. 9 In the example of , UE 906 is unable to communicate directly with base station 902 via Uu signaling (eg, UL and DL signaling) at its current location.

[0141] UE 908 may send an uplink (UL) signal to base station 902 via Uu signaling 918. A portion 922 of the UL signal sent by UE 908 may be received by UE 906 as a CLI.

[0142] Similarly, UE 910 may transmit an uplink (UL) signal to base station 902 via Uu signaling 920. A portion 924 of the UL signal transmitted by UE 910 may be received by UE 906 as a CLI.

[0143] Since the base station 902 cannot directly send the CLI configuration to the UE 906 in this scenario, the base station 902 can send the CLI configuration for the UE 906 to the UE 904 via the sidelink signaling 926. Then, the UE 904 can relay the CLI configuration to the UE 906. In this case, since the UE 906 cannot directly send the CLI measurement report to the base station 902 via UL signaling (e.g., Uu signaling), the UE 906 can send the measurement report to the UE 904 via the sidelink signaling 926, whereby the UE 906 relays the measurement report to the base station (e.g., via Uu signaling 916).

[0144] The above Mode 2 will refer to Figures 10 to 13 Described in more detail, Mode 2 may include two sub-modes: Mode 2-1 and Mode 2-2.

[0145] In mode 2-1, the connected UE can use its own CLI configuration provided by the network to schedule CLI measurements for the CLI UE. The gNB configures CLI resources for UE1 to be used for CLI measurements of UE1 from UE3 or other aggressor UEs. Therefore, UE1 has the CLI configuration from the gNB and also has a sidelink connection with UE2.

[0146] The base station may configure UE1 to act as a coordinator to schedule UE2 for CLI measurement. Here, UE1 allocates CLI resources to UE2. In some examples, UE1 may pass its own UL resources (SRS) as CLI resources to UE2. In some examples, this CLI scheduling may be done via a sidelink channel between UE1 and UE2. In some examples, the base station may configure UE1 using RRC configuration.

[0147] Once configured to measure CLI, UE2 measures the signal in the specified CLI resource. In mode 2-1, the CLI resource is a Uu resource. The CLI resource may include the coordinator itself. The CLI resource may include the CLI resource configured for UE1. After measuring CLI, the UE reports the CLI measurement to UE1 via the sidelink channel.

[0148] UE1 may then take various actions based on the CLI measurement information. In some examples, UE1 determines a CLI interference level at UE2 based on the CLI measurement information. In some examples, UE1 performs UE positioning operations based on the CLI measurement information (e.g., determining the location of UE1 based on the known locations of other UEs).

[0149] Fig.10 An example wireless communication network 1000 is illustrated in which a base station 1002 can communicate with UE 1004 (UE1), UE 1006 (UE2), and UE 1008 (UE3) in an intra-cell deployment according to some aspects. In some examples, base station 1002 can correspond to Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 6 , Figure 7 , Figure 8 and Fig. 9 In some examples, UEs 1004, 1006, and 1008 may correspond to any base station or scheduling entity shown in any of the examples. Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 6 , Figure 7 , Figure 8 and Fig. 9 Any UE or scheduled entity shown in any of the .

[0150] UE 1008 may send an uplink (UL) signal to base station 1002 via Uu signaling 1010. Portion 1012 of the UL signal sent by UE 1008 may be received as CLI by UE 1006. Portion 1014 of the UL signal sent by UE 1008 may also be received by UE 1004 as CLI.

[0151] Since the base station 1002 cannot directly send the CLI configuration to the UE 1006 in this scenario, the base station 1002 can configure the UE 1004 as a CLI coordinator (e.g., by sending an RRC message via Uu signaling 1016). Then, the UE 1004 can generate the CLI configuration for the UE 1006 and send it to the UE 1004 via the sidelink signaling 1018.

[0152] In mode 2-2, a connected UE may use a sidelink resource subset or a sidelink measurement opportunity for CLI measurement. Here, UE1 acts as a coordinator to allocate CLI measurement resources from the available sidelink resources. Therefore, in this mode, CLI resources are from the sidelink resource set.

[0153] Fig.11 An example wireless communication network 1100 is illustrated in which UE 1102 (UE1), UE 1104 (UE2), and UE 1106 (UE3) communicate via sidelink signaling. In some examples, UE 1102, 1104, and 1106 may correspond to Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 6 , Figure 7 , Figure 8 , Fig. 9 and Fig.10 Any UE or scheduled entity shown in any of the .

[0154] In the scenario where UE 1102 is the CLI coordinator, UE 1102 may schedule UE 1106 (via sidelink signaling 1108) to transmit on a particular sidelink resource. UE 1102 may then generate a CLI configuration and send it to UE 1104 via sidelink signaling 1110. Here, the CLI configuration may specify that UE 1104 will monitor a particular sidelink resource for CLI 1112.

[0155] In Mode 2-2, the connected UE may also use the sidelink channel to nearby UEs for UE positioning as described above. Fig.12 An example of the sidelink-based UE positioning is illustrated.

[0156] Fig.12 An example wireless communication network 1200 is illustrated in which UE 1202 (UE1), UE 1204 (UE2), UE 1206 (UE3), and UE 1208 (UE4) communicate via sidelink signaling. In some examples, UE 1202, 1204, 1206, and 1208 may correspond to Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 6 , Figure 7 , Figure 8 , Fig. 9 , Fig.10 and Fig.11 Any UE or scheduled entity shown in any of the .

[0157] UE 1202 may configure UE 1204, UE 1206, and UE 1208 (e.g., via corresponding sidelink channels) to transmit on corresponding CLI resources. UE 1202 may then measure CLI signals from UE 1204 (e.g., sidelink signaling 1210), CLI signals from UE 1206 (e.g., sidelink signaling 1212), and CLI signals from UE 1208 (e.g., sidelink signaling 1214). UE 1204 may then generate location information based on these measurements (e.g., by determining a distance from each UE based on a path loss to each UE).

[0158] refer to Fig.13 For the CLI resource configuration in Mode 1, the connected UE relays the Uu CLI resource configuration generated by the network for the UE outside the network. Therefore, in Mode 1, the connected UE does not utilize this specific CLI resource.

[0159] In contrast, for CLI resource configuration in Mode 2-1, a connected UE may use its own configured CLI resources to schedule CLI measurements by another UE (e.g., a UE outside the network). In addition, in Mode 2-2, a connected UE allocates a subset of CLI resources or configures measurement opportunities for other UE CLI measurements on sidelink resources.

[0160] Fig.13 An example is illustrated in which a connected UE acting as a coordinator can select resources for CLI measurements performed by the UE to avoid transmissions by other UEs. For example, the connected UE can monitor CLI measurement resource opportunities to determine whether the connected UE is receiving strong CLI from another UE during a portion of the CLI measurement resource opportunity. If so, the connected UE can schedule other UEs to perform CLI measurements on different portions of the CLI measurement resource opportunity.

[0161] Fig.13 An example wireless communication network 1300 is illustrated in which a base station 1302 communicates with UE 1304 (UE1), UE 1306 (UE2), UE 1308 (UE3), and UE 1310 (UE1-1) in an intra-cell deployment according to some aspects. In some examples, base station 1302 may correspond to Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 6 , Figure 7 , Figure 8 , Fig. 9 , Fig.10 , Fig.11 and Fig.12 In some examples, UEs 1304, 1306, 1308, and 1310 may correspond to any base station or scheduling entity shown in any of the examples. Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 6 , Figure 7 , Figure 8 , Fig. 9 , Fig.10 , Fig.11 and Fig.12 Any UE or scheduled entity shown in any of the .

[0162] UE 1310 may communicate with base station 1302 via Uu signaling 1312. UE 1310 may send an uplink (UL) signal to base station 1302 via Uu signaling 1314 on allocated resources 1316. For example, UE 1310 may send the UL signal on a subset (e.g., one or more symbols) 1318 of the allocated resources 1316. A portion 1320 of the UL signal sent by UE 1310 may be received by UE 1304 as CLI. By measuring the transmission of UE 1310 during CLI measurement resource opportunities 1322, UE 1304 may identify a subset of resources (e.g., symbols) 1324 that are affected by strong CLI from UE 1310.

[0163] In the scenario where UE 1304 is the CLI coordinator for the set of UEs 1326, UE 1304 may schedule UE 1308 (via sidelink signaling 1130) to transmit on specific sidelink resources 1332 that avoid strong CLI from UE 1310. UE 1304 may then generate a CLI configuration and send it to UE 1306 via sidelink signaling 1334. Here, the CLI configuration may specify that UE 1306 is to measure specific sidelink resources 1336 for CLI 1338 from UE 1308.

[0164] Mode switching can be adopted based on different use cases (or purposes). In some examples, in order to enhance the coverage of low-layer UEs (e.g., RedCap UEs), Mode 1 (relay-connected UEs) can be used. In some examples, in order to provide UE positioning enhancement using CLI measurements, Mode 2 can be used. In some examples, if there are no configured available CLI resources (e.g., such as in an ad hoc network where Uu resources for CLI measurements have not yet been configured), Mode 2-2 can be used. In this case, sidelink resources can be used for CLI measurements. In some examples, if the CLI process is limited to Uu CLI measurements, Mode 1 or Mode 2-1 can be used to perform CLI measurements on Uu CLI resources. In some examples, mode switching can be based on UE capabilities. For example, if the connected UE has relay capabilities but does not support CLI coordinator functionality, or if the connected UE has frequency band limitations, Mode 1 can be used.

[0165] Fig.14 14 is a block diagram illustrating an example of a hardware implementation for a UE 1400 employing a processing system 1414. For example, the UE 1400 may be a sidelink device or other device configured to wirelessly communicate with a base station, such as Figures 1 to 13 In some implementations, UE 1400 may correspond to Figure 1 , Figure 2 , Fig.10 , Figure 5 , Figure 7 , Figure 8 , Fig. 9 , Fig.10 , Fig.11 , Fig.12 and Fig.13 Any UE or scheduled entity shown in any of the .

[0166] According to various aspects of the present disclosure, the processing system 1414 may be utilized to implement an element, or any portion of an element, or any combination of elements. The processing system 1414 may include one or more processors 1404. Examples of processors 1404 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout the present disclosure. In various examples, the UE 1400 may be configured to perform any one or more of the functions described herein. That is, the processor 1404 as utilized in the UE 1400 may be used to implement any one or more of the processes and procedures described herein.

[0167] In some cases, the processor 1404 may be implemented via a baseband or modem chip, and in other implementations, the processor 1404 itself may include multiple devices that are different and distinct from the baseband or modem chip (e.g., in scenarios that can work together to implement the embodiments discussed herein). And as mentioned above, various hardware arrangements and components other than a baseband modem processor may be used in implementations, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / accumulators, etc.

[0168] In this example, the processing system 1414 can be implemented using a bus architecture, which is generally represented by bus 1402. Depending on the specific application and overall design constraints of the processing system 1414, the bus 1402 may include any number of interconnecting buses and bridges. The bus 1402 communicatively couples various circuits including one or more processors (generally represented by processor 1404), memory 1405, and computer-readable media (generally represented by computer-readable media 1406). The bus 1402 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, where these components are well known in the art and therefore will not be described any further. The bus interface 1408 provides an interface between the bus 1402 and the transceiver 1410, and an interface between the bus 1402 and the interface 1430. The transceiver 1410 provides a communication interface or component for communicating with various other devices over a wireless transmission medium. In some examples, the UE may include two or more transceivers 1410, each transceiver being configured to communicate with a corresponding network type (e.g., terrestrial or non-terrestrial). The interface 1430 provides a communication interface or component for communicating with various other devices and equipment (e.g., other devices contained in the same device as the UE or other external devices) via an internal bus or an external transmission medium such as an Ethernet cable. Depending on the nature of the device, the interface 1430 may include a user interface (e.g., a keyboard, a display, a speaker, a microphone, a joystick). Of course, such a user interface is optional and may be omitted in some examples (such as, IoT devices).

[0169] The processor 1404 is responsible for managing the bus 1402 and general processing, which includes executing software stored on the computer-readable medium 1406. The software, when executed by the processor 1404, causes the processing system 1414 to perform the various functions described below for any particular device. The computer-readable medium 1406 and the memory 1405 can also be used to store data that is manipulated by the processor 1404 when executing the software.

[0170] One or more processors 1404 in the processing system can execute software. Software should be broadly interpreted to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, processes, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms. The software can be located on a computer-readable medium 1406.

[0171] Computer readable medium 1406 may be a non-transitory computer readable medium. For example, non-transitory computer readable media include magnetic storage devices (e.g., hard disks, floppy disks, tapes), optical disks (e.g., compact disks (CDs) or digital versatile disks (DVDs)), smart cards, flash memory devices (e.g., cards, sticks, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable hard disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer readable medium 1406 may be located in processing system 1414, outside processing system 1414, or distributed among multiple entities including processing system 1414. Computer readable medium 1406 may be embodied in a computer program product. For example, a computer program product may include a computer readable medium in a packaging material. Those skilled in the art will recognize how to best implement the described functions presented throughout this disclosure according to the specific application and the overall design constraints imposed on the entire system.

[0172] UE 1400 may be configured to perform any one or more of the operations described herein (e.g., as described above in conjunction with Figures 1 to 13 As described and in combination with Figures 15 to 17 In some aspects of the present disclosure, the processor 1404 as utilized in the UE 1400 may include circuits configured for various functions.

[0173] The processor 1404 may include a communication and processing circuit 1441. The communication and processing circuit 1441 may be configured to communicate with a base station such as a gNB. The communication and processing circuit 1441 may include one or more hardware components that provide a physical structure for performing various processes associated with wireless communication (e.g., signal reception and / or signal transmission) as described herein. The communication and processing circuit 1441 may also include one or more hardware components that provide a physical structure for performing various processes associated with signal processing (e.g., processing received signals and / or processing signals for transmission) as described herein. In some examples, the communication and processing circuit 1441 may include two or more transmit / receive chains, each transmit / receive chain configured to process signals of different RAT (or RAN) types. The communication and processing circuit 1441 may also be configured to execute communication and processing software 1451 included on the computer-readable medium 1406 to implement one or more functions described herein.

[0174] In some examples, the communication and processing circuit 1441 may also be configured to generate a scheduling request and send it to the base station (e.g., via the UCI in the PUCCH) to receive an uplink grant for the PUSCH. The communication and processing circuit 1441 may also be configured to generate an uplink signal and interact with the transceiver 1410 to send the uplink signal. The uplink signal may include, for example, a PUCCH, a PUSCH, an SRS, a DMRS, or a PRACH. The communication and processing circuit 1441 may also be configured to interact with the transceiver 1410 to monitor downlink signals and decode downlink signals. The downlink signal may include, for example, a PDCCH, a PDSCH, a CSI-RS, or a DMRS.

[0175] The communication and processing circuit 1441 is configured to communicate via a sidelink carrier to exchange sidelink control information and sidelink data with other sidelink devices. In some examples, the communication and processing circuit 1441 can be configured to send PSCCH (which may include a sidelink synchronization signal block (S-SSB), other control information and / or pilot signals) and / or PSSCH (which may include sidelink data) within a radio frame based on the sidelink transmission timing. In some examples, the sidelink transmission timing can be determined based on synchronization with a synchronization source (e.g., gNB, eNB, GNSS, etc.), self-synchronization with an internal timing / frequency reference, or synchronization with another sidelink device (e.g., based on a received S-SS as described herein).

[0176] In some implementations where the communication involves receiving information, the communication and processing circuitry 1441 may obtain information from a component of the UE 1400 (e.g., from a transceiver 1410 that receives information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium), process the information (e.g., decode), and output the processed information. For example, the communication and processing circuitry 1441 may output the information to another component of the processor 1404, the memory 1405, or the bus interface 1408. In some examples, the communication and processing circuitry 1441 may receive one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1441 may receive information via one or more channels. In some examples, the communication and processing circuitry 1441 may include functionality of a component for receiving.

[0177] In some implementations where communication involves transmitting (e.g., sending) information, the communication and processing circuitry 1441 may obtain information (e.g., from the processor 1404, the memory 1405, or another component of the bus interface 1408), process (e.g., encode) the information, and output the processed information. For example, the communication and processing circuitry 1441 may output the information to the transceiver 1410 (e.g., send 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 1441 may send one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1441 may send information via one or more channels. In some examples, the communication and processing circuitry 1441 may include functionality of a component for transmitting (e.g., a component for sending).

[0178] The processor 1404 may include a CLI management circuit 1442 configured to perform CLI management related operations as discussed herein. The CLI management circuit 1442 may include functionality for receiving a component of a CLI configuration. The CLI management circuit 1442 may include functionality for determining that the CLI configuration is a component for another UE. The CLI management circuit 1442 may include functionality for sending a component of a CLI configuration. The CLI management circuit 1442 may include functionality for receiving a component of a message that configures a UE to schedule CLI measurements. The CLI management circuit 1442 may include functionality for generating a component of a CLI configuration. The CLI management circuit 1442 may include functionality for selecting a component for scheduling CLI measurements using a UE. The CLI management circuit 1442 may include functionality for generating a component of a message that configures a UE to schedule CLI measurements. The CLI management circuit 1442 may include functionality for sending a component of a message to a UE. The CLI management circuit 1442 may also be configured to execute CLI management software 1452 included on the computer-readable medium 1406 to implement one or more functions described herein.

[0179] The processor 1404 may include a CLI processing circuit 1443 configured to perform CLI processing related operations as discussed herein. The CLI processing circuit 1443 may include the functionality of a component for measuring signals on a CLI resource. The CLI processing circuit 1443 may include the functionality of a component for generating a CLI measurement report. The CLI processing circuit 1443 may include the functionality of a component for sending a CLI measurement report. The CLI processing circuit 1443 may include the functionality of a component for receiving a CLI measurement report. The CLI processing circuit 1443 may include the functionality of a component for processing a CLI measurement report. The CLI processing circuit 1443 may also be configured to execute CLI processing software 1453 included on the computer readable medium 1406 to implement one or more functions described herein.

[0180] Fig.15 1 is a flow chart illustrating an example method 1500 for a wireless communication system according to some aspects of the present disclosure. 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 method 1500 may be performed by Fig.14 In some examples, the method 1500 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0181] At block 1502, a UE (e.g., UE1 described above) may receive a cross-link interference (CLI) configuration from a base station. Fig.14 The CLI management circuit 1442 shown and described together with the communication and processing circuit 1441 and the transceiver 1410 can receive an RRC configuration message including a CLI configuration from the gNB.

[0182] In some examples, the CLI configuration specifies at least one CLI resource for the second UE to use for measuring for the CLI measurement report. In some examples, the at least one CLI resource may include resources allocated to the first UE for uplink transmission to the base station. In some examples, the at least one CLI resource may include resources allocated to the third UE for uplink transmission to the base station.

[0183] At block 1504, the UE may determine that the CLI configuration is for a second UE. Fig.14The CLI management circuit 1442 shown and described can determine that the CLI configuration received from the gNB is for another UE. In some examples, the RRC configuration message carrying the CLI configuration can indicate that the CLI configuration is for a particular UE. In this case, determining that the CLI configuration is for a second UE can include parsing the RRC message to determine whether the CLI configuration is for the UE or another UE.

[0184] At 1506, the UE may send the CLI configuration to the second UE after determining that the CLI configuration is for the second UE. Fig.14 The illustrated and described CLI management circuitry 1442 in conjunction with the communication and processing circuitry 1441 and transceiver 1410 may extract the CLI configuration from the received RRC message and relay the extracted CLI configuration to the second UE. In some examples, sending the CLI configuration may include sending the CLI configuration to the second UE via a sidelink channel.

[0185] In some examples, the method may further include receiving a CLI measurement report from the second UE after sending the CLI configuration to the second UE, determining that the CLI measurement report is for the base station, and sending the CLI measurement report to the base station after determining that the CLI measurement report is for the base station. In some examples, the CLI measurement report indicates signal measurements made by the second UE on at least one CLI resource specified by the CLI configuration. In some examples, the at least one CLI resource may include resources allocated to the first UE for uplink transmission to the base station. In some examples, the at least one CLI resource may include resources allocated to the third UE for uplink transmission to the base station.

[0186] Fig.16 1 is a flow chart illustrating an example method 1600 for a wireless communication system according to some aspects of the present disclosure. 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 method 1600 may be performed by Fig.14 In some examples, the method 1600 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0187] At block 1602, a UE (e.g., UE2 described above) may receive a cross-link interference (CLI) configuration specifying at least one CLI resource. Fig.14 The CLI management circuit 1442 shown and described together with the communication and processing circuit 1441 and the transceiver 1410 can receive an RRC configuration message including a CLI configuration from the gNB. As another example, the above in conjunction with Fig.14The CLI management circuitry 1442 in conjunction with the communication and processing circuitry 1441 and the transceiver 1410 shown and described may receive a sidelink message including a CLI configuration generated or relayed by another UE.

[0188] In some examples, receiving the CLI configuration may include receiving the CLI configuration from a base station. In some examples, the CLI configuration indicates that at least one CLI resource is an uplink resource or a sidelink resource.

[0189] At block 1604, the UE may measure a signal on at least one CLI resource. Fig.14 The illustrated and described CLI processing circuitry 1443 in conjunction with the communication and processing circuitry 1441 and the transceiver 1410 may measure RSSI and / or RSRP on CLI resources (eg, Uu resources or sidelink resources) specified in the CLI configuration.

[0190] At block 1606, the UE may generate a CLI measurement report based on measurements of signals on at least one CLI resource. Fig.14 The CLI processing circuit 1443 shown and described may generate a report message indicating RSSI and / or RSRP measured on the CLI resources. The message may indicate whether the report is going to the gNB or the coordinator UE.

[0191] At block 1608, the UE may send a CLI measurement report to the second UE. Fig.14 The CLI processing circuit 1443 shown and described together with the communication and processing circuit 1441 and the transceiver 1410 can send a report to the coordinator UE that generates the CLI configuration. As another example, the above combined Fig.14 The CLI processing circuit 1443 shown and described in conjunction with the communication and processing circuit 1441 and the transceiver 1410 can send a report to a relay UE, which forwards the report to the gNB that generates the CLI configuration. In some examples, sending the CLI measurement report can include sending the CLI measurement report to a second UE via a sidelink channel.

[0192] In some examples, the method may also include determining that the first UE cannot communicate with the base station via an uplink channel. In this case, sending the CLI measurement report may include sending the CLI measurement report to the second UE via a sidelink channel after determining that the first UE cannot communicate with the base station via the uplink channel.

[0193] In some examples, receiving the CLI configuration may include receiving the CLI configuration from the second UE. In some examples, receiving the CLI configuration from the second UE may include receiving the CLI configuration from the second UE via a sidelink channel. In some examples, the CLI configuration indicates that the first UE will send a CLI measurement report to the base station. In some examples, at least one CLI resource may include a resource allocated by the base station for uplink transmission to the base station by the second UE or the third UE. In some examples, the CLI configuration indicates that the first UE will send a CLI measurement report to the second UE.

[0194] Fig.17 1 is a flow chart illustrating an example method 1700 for a wireless communication system according to some aspects of the present disclosure. 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 method 1700 may be performed by Fig.14 In some examples, the method 1700 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0195] At block 1702, a UE (e.g., UE1 described above) may receive a message from a base station, wherein the message configures a first UE to schedule cross-link interference (CLI) measurements. Fig.14 The CLI management circuit 1442 shown and described, together with the communication and processing circuit 1441 and the transceiver 1410, can receive an RRC configuration message from the gNB, wherein the RRC configuration message specifies that the UE will act as a coordinator for scheduling other CLI measurements to be performed by other UEs.

[0196] At block 1704, the UE may generate a first CLI configuration for the second UE after receiving the message. Fig.14 The CLI management circuit 1442 shown and described can identify resources (e.g., Uu resources or CLI resources) to be measured by a second UE (e.g., a nearby UE) and generate a CLI configuration specifying the resources. In some examples, the identified resources are CLI resources scheduled by the gNB for the UE. In some examples, the identified resources are sidelink resources that the UE identifies as resources for transmission by a third UE located near the second UE.

[0197] At block 1706, the UE may send the first CLI configuration to the second UE. Fig.14The illustrated and described CLI management circuit 1442 in conjunction with the communication and processing circuit 1441 and transceiver 1410 may send a DLI configuration to the second UE by allocating resources for D2D communication. In some examples, sending the first CLI configuration may include sending the first CLI configuration to the second UE via a sidelink channel.

[0198] At block 1708, the UE may receive a CLI measurement report from the second UE after sending the first CLI configuration to the second UE. Fig.14 The illustrated and described CLI processing circuitry 1443 in conjunction with the communication and processing circuitry 1441 and transceiver 1410 may monitor resources allocated for D2D communications to receive CLI measurements from the second UE. In some examples, sending the CLI measurement report may include receiving the CLI measurement report from the second UE via a sidelink channel.

[0199] In some examples, the method may further include receiving a second CLI configuration from the base station. In this case, the second CLI configuration may specify at least one CLI resource for the first UE to use for making measurements. In addition, generating the first CLI configuration may include selecting a first resource of the at least one CLI resource for the second UE to use for making measurements and including an indication of the first resource in the first CLI configuration. In some examples, the at least one CLI resource may include a resource allocated to the third UE for uplink transmission to the base station.

[0200] In some examples, generating the first CLI configuration may include selecting a sidelink resource for the second UE for making measurements and including an indication of the sidelink resource in the first CLI configuration. In some examples, the sidelink resource may include resources allocated to the third UE for sidelink transmissions.

[0201] In some examples, generating the first CLI configuration may include identifying interference to a first set of resources in the plurality of resources, selecting a sidelink resource for the second UE from a second set of resources in the plurality of resources for making measurements, and including an indication of the sidelink resource in the first CLI configuration. In this case, the second set of resources may be different from the first set of resources.

[0202] In some examples, the method may further include extracting CLI signal measurement information from the CLI measurement report. In some examples, the method may further include calculating a CLI level at the second UE based on the CLI signal measurement information.

[0203] In some examples, the method may further include extracting CLI signal measurement information from the CLI measurement report. In some examples, the method may further include calculating UE location information based on the CLI signal measurement information.

[0204] In some examples, the method may further include selecting to use CLI measurements to determine UE positioning. In this case, generating the first CLI configuration may include selecting a sidelink resource for the second UE to use for measurement after selecting to use CLI measurements to determine UE positioning.

[0205] In some examples, the method may further include determining that Uu CLI resources are not currently configured. In some examples, the method may further include selecting to use sidelink resources for CLI measurements after determining that Uu CLI resources are not currently configured.

[0206] In some examples, the method may further include determining that the Uu CLI resources are to be used for CLI measurements. In this case, generating the first CLI configuration may include selecting Uu resources for the second UE to use for measurement after determining that the Uu CLI resources are to be used for CLI measurements.

[0207] Fig.18 1 is a block diagram illustrating an example of a hardware implementation for a base station (BS) 1800 employing a processing system 1814. In some implementations, the BS 1800 may correspond to Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 7 , Figure 8 , Fig. 9 , Fig.10 and Fig.13 Any BS (e.g., gNB) or scheduling entity shown in any of the above.

[0208] According to various aspects of the present disclosure, the processing system 1814 may be used to implement an element, or any portion of an element, or any combination of elements. The processing system may include one or more processors 1804. The processing system 1814 may be used with Fig.14 The processing system 1414 shown is substantially the same, including a bus interface 1808, a bus 1802, a memory 1805, a processor 1804, and a computer-readable medium 1806. In addition, the BS 1800 may include an interface 1830 (e.g., a network interface) that provides means for communicating with at least one other device within the core network and with at least one radio access network.

[0209] BS 1800 may be configured to perform any one or more of the operations described herein (e.g., as described above in conjunction with Figures 1 to 13 As described and in combination with Fig.19 and Fig. 20In some aspects of the present disclosure, the processor 1804 as utilized in the BS 1800 may include circuits configured for various functions.

[0210] Processor 1804 may be configured to generate, schedule, and modify resource assignments or grants of time-frequency resources (e.g., a set of one or more resource elements). For example, processor 1804 may schedule time-frequency resources within a plurality of time division duplex (TDD) and / or frequency division duplex (FDD) subframes, time slots, and / or mini-slots to carry user data traffic and / or control information to or from a plurality of UEs and / or from a plurality of UEs.

[0211] Processor 1804 may be configured to schedule resources for transmission of downlink signals. Downlink signals may include, for example, PDCCH, PDSCH, CSI-RS, or DMRS. Processor 1804 may also be configured to schedule resources that may be used by the UE to send uplink signals. Uplink signals may include, for example, PUCCH, PUSCH, SRS, DMRS, or PRACH. Processor 1804 may also be configured to schedule resources that may be used by the UE to send and / or receive sidelink signals.

[0212] In some aspects of the present disclosure, the processor 1804 may include a communication and processing circuit 1841. The communication and processing circuit 1841 may be configured to communicate with the UE. The communication and processing circuit 1841 may include one or more hardware components that provide a physical structure for performing various processes related to communication (e.g., signal reception and / or signal transmission) as described herein. The communication and processing circuit 1841 may also include one or more hardware components that provide a physical structure for performing various processes related to signal processing (e.g., processing received signals and / or processing signals for transmission) as described herein. The communication and processing circuit 1841 may also be configured to execute the communication and processing software 1851 included on the computer-readable medium 1806 to implement one or more functions described herein. The communication and processing circuit 1841 may also be configured to interact with the transceiver 1810 to encode and transmit downlink signals. The communication and processing circuit 1841 may also be configured to interact with the transceiver 1810 to monitor and decode uplink signals.

[0213] In some implementations where the communication involves receiving information, the communication and processing circuitry 1841 may obtain information from a component of the BS 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 the information (e.g., decode), and output the processed information. For example, the communication and processing circuitry 1841 may output the information to another component of the processor 1804, the memory 1805, or the bus interface 1808. In some examples, the communication and processing circuitry 1841 may receive one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1841 may receive information via one or more channels. In some examples, the communication and processing circuitry 1841 may include functionality of a component for receiving.

[0214] In some implementations where communication involves transmitting (e.g., sending) information, the communication and processing circuitry 1841 may obtain information (e.g., from the processor 1804, the memory 1805, or another component of the bus interface 1808), process (e.g., encode) the information, and output the processed information. For example, the communication and processing circuitry 1841 may output the information to the transceiver 1810 (e.g., send 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 1841 may send one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1841 may send information via one or more channels. In some examples, the communication and processing circuitry 1841 may include functionality of a component for transmitting (e.g., a component for sending).

[0215] The processor 1804 may include a CLI management circuit 1842 configured to perform CLI management related operations as discussed herein. The CLI management circuit 1842 may include functionality for generating a component for a CLI configuration. The CLI management circuit 1842 may include functionality for sending a component for a CLI configuration. The CLI management circuit 1842 may include functionality for selecting a component for scheduling CLI measurements using a UE. The CLI management circuit 1842 may include functionality for generating a component for configuring a UE to schedule CLI measurements. The CLI management circuit 1842 may include functionality for sending a component for a message to a UE. The CLI management circuit 1842 may also be configured to execute CLI management software 1852 included on the computer-readable medium 1806 to implement one or more functions described herein.

[0216] The processor 1804 may include a CLI processing circuit 1843 configured to perform CLI processing related operations as described herein. The CLI processing circuit 1843 may include the functionality of a component for receiving a CLI measurement report. The CLI processing circuit 1843 may include the functionality of a component for processing a CLI measurement report. The CLI processing circuit 1843 may also be configured to execute CLI processing software 1853 included on the computer readable medium 1806 to implement one or more functions described herein.

[0217] Fig.19 1 is a flow chart illustrating an example method 1900 for a wireless communication system according to some aspects of the present disclosure. 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 method 1900 may be performed by Fig.18 In some examples, the method 1900 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0218] At block 1902, the BS may generate a cross-link interference (CLI) configuration for the first UE. Fig.18 The CLI management circuit 1842 shown and described may determine that the first UE is affected by interference (identify resources (e.g., Uu resources) to be measured by the first UE (e.g., a nearby UE)) and generate a CLI configuration specifying the resources (e.g., based on information received from the first UE explicitly indicating an error associated with ...

[0219] At block 1904, the BS may send a CLI configuration. Fig.18 The CLI management circuit 1842 shown and described together with the communication and processing circuit 1841 and the transceiver 1810 can send a DLI configuration (e.g., via a downlink) to a UE that is to perform CLI measurements. As another example, the above in conjunction with Fig.18 The illustrated and described CLI management circuitry 1842 in conjunction with the communication and processing circuitry 1841 and transceiver 1810 may send a CLI configuration to a first UE (eg, via a Uu link), which relays the CLI configuration to a UE that is to perform CLI measurements.

[0220] In some examples, sending the CLI configuration may include sending the CLI configuration to the first UE via a connection to the first UE. In some examples, sending the CLI configuration may include sending the CLI configuration to the second UE via a connection to the second UE. In some examples, sending the CLI configuration may include sending a message indicating that the second UE will forward the CLI configuration to the first UE.

[0221] At block 1906, the BS may receive a CLI measurement report generated by the first UE from the second UE after sending the CLI configuration. Fig.18 The illustrated and described CLI processing circuitry 1843 in conjunction with the communication and processing circuitry 1841 and transceiver 1810 may receive a CLI measurement report (eg, via a Uu link) from a second UE that relayed the CLI configuration from a first UE that performed the CLI measurements.

[0222] In some examples, the method may also include determining that the base station cannot communicate with the second UE. In some examples, the method may also include selecting to relay the CLI configuration to the second UE using the first UE after determining that the base station cannot communicate with the second UE.

[0223] In some examples, the method may also include determining that the base station cannot communicate with the first UE via the first downlink channel. In this case, sending the CLI configuration may include sending the CLI configuration to the second UE via a second downlink channel after determining that the base station cannot communicate with the first UE via the first downlink channel.

[0224] In some examples, the method may further include determining that the base station cannot communicate with the first UE via the first downlink channel. In some examples, the method may further include determining that the second UE has a sidelink connection to the first UE. In this case, sending the CLI configuration may include sending the CLI configuration to the second UE via a second downlink channel after determining that the base station cannot communicate with the first UE via the first downlink channel and after determining that the second UE has a sidelink connection to the first UE.

[0225] In some examples, the method may also include determining that the Uu CLI resources will be used for CLI measurements. In some examples, the method may also include selecting to relay the CLI configuration to the second UE using the first UE after determining that the Uu CLI resources will be used for CLI measurements. In this case, the CLI configuration may specify at least one Uu resource.

[0226] In some examples, the method may also include determining that the second UE does not support the CLI coordinator function. In some examples, the method may also include selecting to relay the CLI configuration to the second UE using the second UE after determining that the second UE does not support the CLI coordinator function.

[0227] Fig. 20 2000 is a flowchart illustrating an example method 2000 for a wireless communication system according to some aspects of the present disclosure. 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 method 2000 may be performed by Fig.18 In some examples, method 2000 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0228] At block 2002, the BS may choose to schedule cross-link interference (CLI) measurements using the first UE. Fig.18 The CLI management circuitry 1842 as shown and described may determine that CLI measurements for a set of sidelink devices are to be performed using sidelink resources.

[0229] At block 2004, the BS may generate a message to configure the first UE to schedule CLI measurements. Fig.18 The CLI management circuitry 1842 shown and described may generate an RRC configuration message specifying that the first UE is to act as a coordinator to schedule other UEs for CLI measurements.

[0230] In some examples, the message configures the first UE to schedule CLI measurements on at least one uplink resource. In some examples, the message configures the first UE to schedule CLI measurements on at least one sidelink resource.

[0231] At block 2006, the BS may send a message to the first UE. Fig.18 The CLI management circuit 1842, in conjunction with the communication and processing circuit 1841 and the transceiver 1810, may be shown and described to send an RRC configuration message to a sidelink UE (eg, via a downlink).

[0232] In some examples, the method may further include determining that the base station cannot communicate with the first UE. In this case, generating a message to configure the first UE to schedule CLI measurements may be triggered by determining that the base station cannot communicate with the first UE.

[0233] In some examples, the method may further include determining that the base station cannot communicate with the first UE. In some examples, the method may further include determining that the second UE has a sidelink connection to the first UE. In this case, generating a message to configure the first UE to schedule CLI measurements may be triggered by determining that the base station cannot communicate with the first UE and by determining that the second UE has a sidelink connection to the first UE.

[0234] In some examples, the method may further include selecting to use CLI measurements to determine UE positioning. In this case, selecting to use the first UE to schedule CLI measurements may be triggered by selecting to use CLI measurements to determine UE positioning.

[0235] In some examples, the method may further include determining that Uu CLI resources are not currently configured. In some examples, the method may further include selecting to use sidelink resources for CLI measurements after determining that Uu CLI resources are not currently configured.

[0236] In some examples, the method may further include determining that the Uu CLI resources are to be used for CLI measurements. In this case, selecting to schedule CLI measurements using the first UE may be triggered by determining that the Uu CLI resources are to be used for CLI measurements.

[0237] In some examples, the method may further include generating a CLI configuration for the first UE. In some examples, the method may further include sending the CLI configuration to the first UE. In some examples, the method may further include receiving a CLI measurement report generated by the first UE after sending the CLI configuration. In some examples, the method may further include determining a CLI level at the first UE based on the CLI measurement report.

[0238] Several aspects of wireless communication networks have been presented with reference to example 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.

[0239] For 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 Communications (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 using IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802.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.

[0240] In the present disclosure, the word "exemplary" is used to mean "serving as an example, instance or illustration". Any implementation or aspect described herein as "exemplary" should not be interpreted as being preferred or advantageous over other aspects of the present disclosure. Likewise, the term "aspects" does not require that all aspects of the present disclosure include the features, advantages or modes of operation discussed. 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, then objects A and C may be considered 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 terms "circuit" and "circuitry" are used in a broad sense, and are intended to include hardware implementations of electronic devices and conductors (wherein when these electronic devices and conductors are connected and configured, the execution of the functions described in the present disclosure is achieved, without being a limitation on the type of electronic circuits) and software implementations of information and instructions (wherein when these information and instructions are executed by a processor, the execution of the functions described in the present disclosure is achieved). As used herein, the term "determining" may include, for example, ascertaining, resolving, selecting, choosing, establishing, calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database, or another data structure), etc. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc.

[0241] Can Figures 1 to 20 One or more of the components, steps, features and / or functions shown in the present invention may be rearranged and / or combined into a single component, step, feature or function, or may be embodied in several components, steps or functions. In addition, additional elements, components, steps and / or functions may be added without departing from the novel features disclosed herein. Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 7 , Figure 8 , Fig. 9 , Fig.10 , Fig.11 , Fig.12 , Fig.13 , Fig.14 and Fig.18 The apparatus, devices and / or components illustrated in the drawings may be configured to perform one or more of the methods, features or steps described herein. The novel algorithms described herein may also be effectively implemented in software and / or embedded in hardware.

[0242] It is to be understood that the specific order or hierarchy of steps in the disclosed methods is merely an illustration of an example process. Based on design preferences, it is to be understood that the specific order or hierarchy of steps in the methods may be rearranged. The attached method claims present elements of the various steps in an example order and are not meant to be limited to the specific order or hierarchy presented, except where specifically recited therein.

[0243] 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 will be given the full scope consistent with the language of the claims, where reference to an element in the singular is not intended to mean "one and only one" (unless specifically stated), but to mean "one or more". Unless otherwise specifically stated, the term "some" refers to one or more. The phrase "at least one" of the list of options refers to any combination of those options, 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 disclosure that are known or subsequently known 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, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recorded in the claims.

Claims

1. A method for wireless communication at a first user equipment UE, the method comprising: receiving a cross-link interference CLI configuration from a base station; determining that the CLI configuration is for a second UE; as well as After determining that the CLI configuration is for the second UE, sending the CLI configuration to the second UE so that the second UE can perform CLI measurement based on the CLI configuration, The first UE is within the cell coverage area of ​​the base station, and the second UE is not within the cell coverage area of ​​the base station.

2. The method of claim 1 , wherein sending the CLI configuration comprises: The CLI configuration is sent to the second UE via a sidelink channel.

3. The method of claim 1 , wherein the CLI configuration specifies at least one CLI resource for the second UE to use for performing measurements for a CLI measurement report.

4. A first user equipment UE, comprising: Transceiver; Memory; as well as a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to: receiving a cross-link interference CLI configuration from a base station via the transceiver; determining that the CLI configuration is for a second UE; and After determining that the CLI configuration is for the second UE, sending the CLI configuration to the second UE so that the second UE can perform CLI measurement based on the CLI configuration, The first UE is within the cell coverage area of ​​the base station, and the second UE is not within the cell coverage area of ​​the base station.

5. The first user equipment according to claim 4, wherein the processor and the memory are further configured to: The CLI configuration is sent to the second UE via a sidelink channel.

6. The first user equipment of claim 4, wherein the CLI configuration specifies at least one CLI resource for the second UE to use for performing measurements for a CLI measurement report.

7. The first user equipment of claim 6, wherein the at least one CLI resource comprises a resource allocated to the first UE for uplink transmission to the base station.

8. The first user equipment of claim 6, wherein the at least one CLI resource comprises a resource allocated to a third UE for uplink transmission to the base station.

9. The first user equipment according to claim 4, wherein the processor and the memory are further configured to: After sending the CLI configuration to the second UE, receiving a CLI measurement report from the second UE; determining that the CLI measurement report is for the base station; and After determining that the CLI measurement report is for the base station, sending the CLI measurement report to the base station.

10. The first user equipment according to claim 9, wherein the CLI measurement report indicates signal measurements performed by the second UE on at least one CLI resource specified by the CLI configuration.

11. The first user equipment of claim 10, wherein the at least one CLI resource comprises a resource allocated to the first UE for uplink transmission to the base station.

12. The first user equipment of claim 10, wherein the at least one CLI resource comprises a resource allocated to a third UE for uplink transmission to the base station.

13. A method for wireless communication at a first user equipment UE, the method comprising: receiving, from a second UE, a CLI configuration specifying at least one cross-link interference CLI resource; measuring a signal on the at least one CLI resource; generating a CLI measurement report based on the measurements of the signals on the at least one CLI resource; as well as sending the CLI measurement report to the second UE, The first UE is within the cell coverage area of ​​the base station, and the second UE is not within the cell coverage area of ​​the base station.

14. The method of claim 13, wherein sending the CLI measurement report comprises: The CLI measurement report is sent to the second UE via a sidelink channel.

15. A first user equipment, comprising: Transceiver; Memory; as well as a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to: receiving, from a second UE, a CLI configuration specifying at least one cross-link interference CLI resource; measuring a signal on the at least one CLI resource; generating a CLI measurement report based on the measurements of the signals on the at least one CLI resource; as well as sending the CLI measurement report to the second UE via the transceiver, The first UE is within the cell coverage area of ​​the base station, and the second UE is not within the cell coverage area of ​​the base station.

16. The first user equipment according to claim 15, wherein the processor and the memory are further configured to: The CLI measurement report is sent to the second UE via a sidelink channel.

17. The first user equipment according to claim 15, wherein: The processor and the memory are further configured to receive the CLI configuration from a base station; and The at least one CLI resource comprises a resource allocated by the base station for uplink transmission to the base station by the second UE or the third UE.

18. The first user equipment according to claim 17, wherein the processor and the memory are further configured to: determining that the first UE cannot communicate with the base station via an uplink channel; After determining that the first UE cannot communicate with the base station via the uplink channel, the CLI measurement report is sent to the second UE via a sidelink channel.

19. The first user equipment according to claim 15, wherein the processor and the memory are further configured to: The CLI configuration is received from the second UE.

20. The first user equipment according to claim 15, wherein the processor and the memory are further configured to: The CLI configuration is received from the second UE via a sidelink channel.

21. The first user equipment of claim 15, wherein the CLI configuration indicates that the first UE is to send the CLI measurement report to a base station.

22. The first user equipment of claim 15, wherein the CLI configuration indicates that the first UE is to send the CLI measurement report to the second UE.

23. The first user equipment of claim 15, wherein the CLI configuration indicates that the at least one CLI resource is an uplink resource or a sidelink resource.

24. A first user equipment UE, comprising: Transceiver; Memory; as well as a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to: receiving, via the transceiver, a message from a base station, wherein the message configures the first UE to schedule cross-link interference (CLI) measurements; generating a first CLI configuration for the second UE after receiving the message; sending the first CLI configuration to the second UE; and After sending the first CLI configuration to the second UE, receiving a CLI measurement report from the second UE, The first UE is within the cell coverage area of ​​the base station, and the second UE is not within the cell coverage area of ​​the base station.

25. The first user equipment according to claim 24, wherein the processor and the memory are further configured to: sending the first CLI configuration to the second UE via a sidelink channel; and The CLI measurement report is received from the second UE via the sidelink channel.

26. The first user equipment according to claim 24, wherein the processor and the memory are further configured to: receiving a second CLI configuration from the base station, wherein the second CLI configuration specifies at least one CLI resource for the first UE to perform measurement; A first resource of the at least one CLI resource is selected for the second UE to use for measurement and an indication of the first resource is included in the first CLI configuration.

27. The first user equipment of claim 26, wherein the at least one CLI resource comprises a resource allocated to a third UE for uplink transmission to the base station.

28. The first user equipment according to claim 24, wherein the processor and the memory are further configured to: selecting a sidelink resource for the second UE to use for making measurements; and An indication of the sidelink resource is included in the first CLI configuration.

29. The first user equipment of claim 28, wherein the sidelink resources comprise resources allocated to a third UE for sidelink transmission.

30. The first user equipment of claim 24, wherein the processor and the memory are further configured to: identifying interference to a first set of resources among a plurality of resources; selecting a sidelink resource for the second UE from a second set of resources in the plurality of resources for measurement, wherein the second set of resources is different from the first set of resources; and An indication of the sidelink resource is included in the first CLI configuration.

31. The first user equipment of claim 24, wherein the processor and the memory are further configured to: Extracting CLI signal measurement information from the CLI measurement report; and The CLI level at the second UE is calculated according to the CLI signal measurement information.

32. The first user equipment of claim 24, wherein the processor and the memory are further configured to: Extracting CLI signal measurement information from the CLI measurement report; and Calculate UE location information based on the CLI signal measurement information.

33. The first user equipment according to claim 24, wherein the processor and the memory are further configured to: Selecting to use the CLI measurement to determine UE positioning; After selecting to use the CLI measurements to determine UE positioning, sidelink resources are selected for the second UE for making measurements.

34. The first user equipment of claim 24, wherein the processor and the memory are further configured to: Ensure that no Uu CLI resources are currently configured; and After determining that the Uu CLI resource is not currently configured, selecting to use a sidelink resource for the CLI measurement.

35. The first user equipment of claim 24, wherein the processor and the memory are further configured to: determining that Uu CLI resources will be used for the CLI measurement; After determining that Uu CLI resources are to be used for the CLI measurement, Uu resources are selected for the second UE for performing the measurement.

Images