Interference handling for segmented carriers

Abstract

The invention generally relates to interference handling for segmented carriers. The present application relates to devices and components, including apparatuses, systems, and methods for providing interference handling for segmented carriers in a wireless communication system.

Description

[0001] Cross Reference to Related Applications

[0002] This application claims priority to U.S. Provisional Application No. 63 / 657,035, filed June 6, 2024, entitled “Interference Handling for Fragmented Carriers,” the disclosure of which is incorporated by reference herein in its entirety for all purposes. TECHNICAL FIELD

[0003] The present application relates to the field of wireless technology, and in particular to interference handling for fragmented carriers for user equipment. BACKGROUND

[0004] Third Generation Partnership Project (3GPP) networks enable user equipment (UE) to communicate with the network using carriers. Carriers of the network can be assigned to different user equipment (UE), where the UE can communicate with the network using the corresponding assigned carrier. Different carriers can be assigned to different UEs within the same area, where the different UEs can simultaneously communicate with the network using the corresponding assigned carriers. BRIEF DESCRIPTION OF DRAWINGS

[0005] Figure 1 A network environment is illustrated in accordance with some embodiments.

[0006] Figure 2 A user equipment (UE) is illustrated in accordance with some embodiments.

[0007] Figure 3 A network device is illustrated in accordance with some embodiments.

[0008] Figure 4 An example fragmented carrier arrangement is illustrated in accordance with some embodiments.

[0009] Figure 5 An example carrier gap arrangement is illustrated in accordance with some embodiments.

[0010] Figure 6 A process for configuring a UE is illustrated in accordance with some embodiments.

[0011] Figure 7 An example process for determining and reporting blocker power levels is illustrated in accordance with some embodiments.

[0012] Figure 8 An example process for configuring a UE is illustrated in accordance with some embodiments.

[0013] Figure 9An example process for generating a report of blocking party power levels is illustrated in accordance with some embodiments. DETAILED DESCRIPTION

[0014] The following detailed description references the drawings, wherein like numerals indicate the same or similar elements. In this description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to one skilled in the art that aspects of the various embodiments can be practiced without these specific details. In other instances, well-known devices, circuits, and methodologies have not been described in detail in order to avoid unnecessarily obscuring aspects of the various embodiments. As used herein, the phrase “A or B” means (A), (B), or (A and B). Also, as used herein, the phrase “based on” means “based, at least in part, on” such as it can be “based solely on” or it can be “based in part on something and based in part on something else.”

[0015] The following is a glossary of terms that can be used in the present disclosure.

[0016] As used herein, the term “circuitry” refers to, is part of, or includes: hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (for example, a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable system-on-a-chip (SoC)), a digital signal processor (DSP), or the like, that is configured to provide the described functionality. In some embodiments, circuitry can execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” can also refer to the combination of one or more hardware elements (or a combination of circuits used in electrical or electronic systems) with the program code that the hardware elements are used to execute. In these embodiments, the combination of hardware elements and program code can be referred to as a type of circuitry.

[0017] As used herein, the term “processor circuitry” refers to, is part of, or includes circuitry capable of sequentially and automatically processing a series of arithmetic or logical operations or recording, storing, or transferring digital data. The term “processor circuitry” can refer to an application processor, a baseband processor, a central processing unit (CPU), a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and / or functional processes.

[0018] As used herein, the term “interface circuitry” refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” can refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, and the like.

[0019] As used herein, the term “user equipment” or “UE” refers to a device with radio communication capabilities and can describe a remote user of network resources in a communication network. Further, the term “user equipment” or “UE” can be considered synonymous, and can be referred to as a client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, and the like. Moreover, the term “user equipment” or “UE” can include any type of wireless / wired device or any computing device including a wireless communication interface.

[0020] As used herein, the term “computer system” refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” or “system” can refer to various components of a computer that are communicatively coupled to one another. Further, the term “computer system” or “system” can refer to multiple computer devices or multiple computing systems that are communicatively coupled to one another and configured to share computing resources or networking resources.

[0021] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a particular device, such as a computer device, a mechanical device, memory space, processor / CPU time, processor / CPU usage, processor and accelerator load, hardware time or usage, power supply, input / output operations, port or network socket, channel / link allocation, throughput, memory usage, storage, network, database and application, units of work, and the like. A "hardware resource" can refer to computing, storage, or network resources provided by a physical hardware element. A "virtualized resource" can refer to computing, storage, or network resources provided by a virtualization infrastructure to an application, device, system, and the like. The term "network resource" or "communication resource" can refer to a resource that is accessible to a computer device / system via a communication network. The term "system resource" can refer to any kind of shared entity that provides a service, and can include a computing resource or a network resource. A system resource can be considered as a set of coherent functionalities, network data objects, or services that are accessible through a server, where such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0022] As used herein, the term "channel" refers to any tangible or intangible conveyance medium used to convey data or a stream of data. The term "channel" can be synonymous with or equivalent to "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier wave," "radio frequency carrier wave," or any other similar term denoting a pathway or medium through which data is conveyed. Additionally, as used herein, the term "link" refers to a connection between two devices for transmitting and receiving information.

[0023] As used herein, the terms "to instantiate," "instantiate," and the like refer to the creation of an instance. An "instance" also refers to a concrete occurrence of an object, which can occur, for example, during execution of program code.

[0024] The term "connect" can mean that two or more elements have an established signaling relationship with each other over a communication channel, link, interface, or reference point at a common communication protocol layer.

[0025] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term "network element" can be considered synonymous with or referred to as a networked computer, networked hardware, network equipment, network node, virtualized network function, and the like.

[0026] The term "information element" refers to a structural element containing one or more fields. The term "field" refers to individual content of an information element, or a data element containing content. An information element can include one or more additional information elements.

[0027] As used herein, the term“based on” can indicate that one item is based, at least in part, on another item and / or that one item is based, at least in part, on one or more additional items. For example, in embodiments, determining item 1 based on item 2 can indicate that item 1 is determined based on only item 2 and / or that item 1 is determined based on item 2 and one or more other items.

[0028] Third Generation Partnership Project (3GPP) networks are evolving to support segmented carrier assignments to user equipment (UEs). For example, a network can assign a first range of frequency carriers and a second range of frequency carriers to a first UE for simultaneous communication. There can be a third range of frequency carriers between the first range of frequency carriers and the second range of frequency carriers that is not assigned to the first UE (which can be referred to as a gap). This third range of frequency carriers can be assigned to other UEs for communication with the network. However, other UEs that communicate using the third range of frequency carriers can cause interference to communications on the first range of frequency carriers and / or the second range of frequency carriers, which can cause operational issues. The methods described throughout this disclosure can address this interference to ensure proper operation of the network.

[0029] Figure 1 A network environment 100 is illustrated in accordance with some embodiments. The network environment 100 can include a user equipment (UE) 104 communicatively coupled with a base station 108 of a radio access network (RAN) 110. The UE 104 and the base station 108 can communicate over an air interface compatible with 3GPP TS, such as those defining a Fifth Generation (5G) New Radio (NR) system or higher. The base station 108 can provide user plane and control plane protocol terminations toward the UE 104.

[0030] In some embodiments, the UE 104 and the base station 108 can establish data radio bearers (DRBs) to support data transmission over a wireless link between the two nodes. In one example, these DRBs can be used for traffic from an extended reality (XR) application that contains a large amount of data conveying real and virtual images and audio for presentation to a user.

[0031] The network environment 100 can also include a core network 112. For example, the core network 112 can include a 5th Generation Core Network (5GC) or a Next Generation Core Network. The core network 112 can be coupled to the base station 108 via fiber or wireless backhaul. The core network 112 can provide functionality for the UE 104 via the base station 108. These functionalities can include managing subscriber profile information, subscriber location, service authentication, or handover functionality for voice and data sessions.

[0032] In some embodiments, the network environment 100 can also include a UE 106. The UE 106 can be coupled with the UE 104 via a sidelink interface. In some embodiments, the UE 106 can act as a relay node to communicatively couple the UE 104 to the RAN 110. In other embodiments, the UE 106 and the UE 104 can represent terminal nodes of a communication link. For example, the UEs 104 and 106 can exchange data with each other.

[0033] Figure 2 A UE 200 according to some embodiments is illustrated. The UE 200 can be similar to and substantially interchangeable with the UE 104 or 106.

[0034] The UE 200 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, a computer, a tablet, an industrial wireless sensor (e.g., a microphone, a carbon dioxide sensor, a pressure sensor, a humidity sensor, a thermometer, a motion sensor, an accelerometer, a laser scanner, a fluid level sensor, an inventory sensor, a voltage / current meter, or an actuator), a video surveillance / monitoring device (e.g., a camera or a video camera), a wearable device (e.g., a smart watch), or an Internet of Things device.

[0035] The UE 200 can include a processor 204, an RF interface circuit 208, a memory / storage 212, a user interface 216, a sensor 220, a driver circuit 222, a power management integrated circuit (PMIC) 224, an antenna 226, and a battery 228. The components of the UE 200 can be implemented as integrated circuits (ICs), portions of ICs, discrete electronic devices, or other modules, logic components, hardware, software, firmware, or a combination thereof. Figure 2 The block diagram of FIG. 2 is intended to show a high-level view of certain ones of the components of the UE 200. However, some of the components shown can be omitted in some embodiments, additional components can be present, and different arrangements of the components shown can occur in other embodiments.

[0036] The components of the UE 200 can be coupled through one or more interconnects 232, which can represent any type of interface, input / output, bus (local, system, or expansion), transmission line, trace, or optical connection that allows the various circuit components (on common or different chips or chip sets) to interact with each other.

[0037] The processor 204 can include processor circuitry, such as, for example, a baseband processor circuit (BB) 204A, a central processor unit circuit (CPU) 204B, and a graphics processor unit circuit (GPU) 204C. The processor 204 can include any type of circuit or processor circuit that executes or otherwise operates computer-executable instructions, such as program code, software modules, or functional processes from the memory / storage 212, to cause the UE 200 to perform delay adaptation operations as described herein. The processor 204 can also include interface circuit 204D to communicatively couple the processor circuit with one or more other components of the UE 200.

[0038] In some embodiments, the baseband processor circuit 204A can access the communication protocol stack 236 in the memory / storage 212 to communicate over a 3GPP-compatible network. Generally, the baseband processor circuit 204A can access the communication protocol stack 236 to perform user plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and control plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and NAS layer. In some embodiments, PHY layer operations can additionally / alternatively be performed by components of the RF interface circuit 208.

[0039] The baseband processor circuit 204A can generate or process baseband signals or waveforms that carry information in a 3GPP-compatible network. In some embodiments, waveforms for NR can be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.

[0040] The memory / storage 212 can include one or more non-transitory computer- readable media that include instructions (e.g., the communication protocol stack 236) that are executable by one or more of the processors 204 to cause the UE 200 to perform various delay adaptation operations described herein.

[0041] The memory / storage 212 includes any type of volatile and / or nonvolatile memory needed to store and retrieve program instructions, data, and other types of computer-readable media. In some embodiments, some of memory / storage 212 can be on the processor 204 itself (e.g., on a chipset that is part of the baseband processor circuit 204A), while other memory / storage 212 is located off the processor 204, but can be accessed via a memory bus or other memory interface. The memory / storage 212 can include any suitable volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0042] The RF interface circuit 208 can include transceiver circuitry and radio frequency front module (RFEM) that allow the UE 200 to communicate with other devices through a radio access network. The RF interface circuit 208 can include various elements arranged in transmit or receive paths. These elements can include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, and control circuitry.

[0043] In the receive path, the RFEM can receive a radiated signal from the air interface via the antenna 226 and continue to filter and amplify that signal (with a low noise amplifier). The signal can be provided to a receiver of the transceiver that down-converts the RF signal to a baseband signal provided to the baseband processor of the processor 204.

[0044] In the transmit path, a transmitter of the transceiver up-converts baseband signals received from the baseband processor and provides RF signals to the RFEM. The RFEM can amplify the RF signals through a power amplifier before the signals are radiated across the air interface via the antenna 226.

[0045] In various embodiments, the RF interface circuit 208 can be configured to transmit / receive signals in a manner compatible with NR access technology.

[0046] The antenna 226 can include antenna elements to convert electrical signals into radio waves to travel through the air and to convert received radio waves into electrical signals. The antenna elements can be arranged in one or more antenna panels. The antenna 226 can have an antenna panel that is omnidirectional, directional, or a combination thereof to enable beamforming and multiple-input, multiple-output communication. The antenna 226 can include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, or phased array antennas. The antenna 226 can have one or more panels designed for a particular frequency band, including the bands in FR1 or FR2.

[0047] User interface 216 includes various input / output (I / O) devices designed to enable user interaction with UE 200. User interface 216 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting an input including, inter alia, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, or a headset, etc. Output device circuitry includes any physical or virtual means for showing information or otherwise conveying information, such as sensor readings, actuator positions, or other similar information. Output device circuitry can include any number or combination of audio or visual displays, including, inter alia, one or more simple visual outputs / indicators (e.g., binary status indicators (such as light-emitting diodes (LEDs) and multi-character visual outputs), or more complex outputs such as display devices or touchscreens (e.g., liquid crystal displays (LCD), LED displays, quantum dot displays, and projectors), where the output of characters, graphics, multimedia objects, etc. are generated or produced from the operation of UE 200.

[0048] Sensors 220 can include devices, modules, or subsystems whose purpose is to detect events or changes in its environment and send the information (sensor data) about the detected events to some other a device, module, or subsystem. Examples of such sensors include: inertial measurement units comprising an accelerometer, a gyroscope, or a magnetometer; microelectromechanical systems or nanoelectromechanical systems comprising a three-axis accelerometer, a three-axis gyroscope, or a magnetometer; a liquid level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravimeter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging sensor; a proximity sensor (e.g., an infrared radiation detector, etc.); a depth sensor; an ambient light sensor; an ultrasonic transceiver; and a microphone or other similar audio capture device.

[0049] The driver circuitry 222 can include software and hardware elements in operating to control particular devices embedded in, or attached to, or otherwise interfaced with the UE 200. The driver circuitry 222 can include individual drivers that facilitate input / output (I / O) operations and / or communications with various I / O devices existing within, or connected to, the UE 200. For example, the driver circuitry 222 can include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface, sensor drivers to obtain sensor readings of the sensors 220 and control and allow access to the sensors 220, actuators drivers to obtain actuator positions of electromechanical components or control and allow access to electromechanical components, a camera driver to control and allow access to an embedded image capture device, an audio driver to control and allow access to one or more audio devices.

[0050] The PMIC 224 can manage power provided to the various components of the UE 200. In particular, with respect to the processor 204, the PMIC 224 can control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.

[0051] The battery 228 can power the UE 200, although in some examples the UE 200 can be installed in a fixed location, and can have power supplied directly from a power grid. The battery 228 can be a lithium ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, and the like. In some implementations, such as in vehicle-based applications, the battery 228 can be a typical lead-acid automotive battery.

[0052] Figure 3 A network equipment 300 is illustrated in accordance with some embodiments. The network equipment 300 can be similar to, and substantially interchangeable with, the equipment of the base stations 108 or the core network 112 or external data networks 120.

[0053] The network equipment 300 can include a processor 304, RF interface circuitry 308 (if implemented as a base station), core network (CN) interface circuitry 314, memory / storage circuitry 312, and antenna structure 326.

[0054] The components of the network equipment 300 can be coupled with various other components over one or more interconnects 328.

[0055] The processor 304, RF interface circuitry 308, memory / storage circuitry 312 (including the communication protocol stack 310), antenna structure 326, and interconnects 328 can be similar to those described with respect to the UE 200. Figure 2 Like-named components have been described with respect to the UE 200.

[0056] The processor 304 can include processor circuitry, such as, for example, a baseband processor circuit (BB) 304A, a central processor unit circuit (CPU) 304B, and a graphics processor unit circuit (GPU) 304C. The processor 304 can include any type of circuit or processor circuit that executes or otherwise operates computer-executable instructions, such as program code, software modules, or functional processes from the memory / storage circuit 312, to cause the network device 300 to perform the operations described herein. The processor 304 can also include interface circuit 304D to communicatively couple the processor circuit with one or more other components of the network device 300.

[0057] The CN interface circuit 314 can provide connectivity to a core network (e.g., a 5thGeneration Core Network (5GC) using a 5GC-compatible network interface protocol, such as a carrier Ethernet protocol or some other suitable protocol). Network connectivity can be provided to / from the network device 300 via fiber or wireless backhaul. The CN interface circuit 314 can include one or more specialized processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 314 can include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0058] In Release 19 (R19), support for segmented carriers in downlink (DL) can be introduced. The problem to be solved is how to treat the segmented in-band blocks as a single component carrier (CC) in DL. The scope can be limited to frequency division duplex (FDD) bands, where the individual DL bandwidth can be less than or equal to 100 megahertz (MHz). The feasibility of using a single receive (Rx) chain per segmented FDD band can be evaluated, while the near-far problem and unwanted emission impact can be considered.

[0059] Figure 4 An example segmented carrier arrangement 400 is illustrated in accordance with some embodiments. For example, the arrangement 400 illustrates some example carrier assignments in which non-contiguous groups of carriers are assigned to the same UE. Each of the blocks within the illustrated arrangement 400 represents a 5 MHz spectrum, where blocks with the same fill represent carriers assigned to the same UE. For example, the same fill indicates spectrum access for the same operator. In the illustrated embodiment, each of the blocks is 5 MHz wide.

[0060] The arrangement 400 includes a first fragmented carrier arrangement 402. The first arrangement 402 can include a Personal Communications Service (PCS) (n25) example of a fragmented spectrum, which in an example implementation can be used for Toronto. The first arrangement 402 includes a first set of carriers 404, a second set of carriers 406, a third set of carriers 408, and a fourth set of carriers 410. The first set of carriers 404 and the third set of carriers 408 can be assigned to a first operator (as shown by the corresponding blocks without fill), which can assign the first set of carriers 404 and the third set of carriers 408 to a first UE. The second set of carriers 406 and the fourth set of carriers 410 can be assigned to a second operator (as shown by the corresponding blocks with diagonal fill), which can assign the second set of carriers 406 and the fourth set of carriers 410 to a second UE.

[0061] The first set of carriers 404 and the third set of carriers 408 are separated by the second set of carriers 406, such that the first set of carriers 404 and the third set of carriers 408 are non-contiguous. Since both the first set of carriers 404 and the third set of carriers 408 are assigned to the first operator, these carriers can be a fragmented carrier assignment to the first operator. The second set of carriers 406 and the fourth set of carriers 410 are separated by the third set of carriers 408, such that the second set of carriers 406 and the fourth set of carriers 410 are non-contiguous. Since both the second set of carriers 406 and the fourth set of carriers 410 are assigned to the second operator, these carriers can be a fragmented carrier assignment to the second operator. The carriers between the fragmented carriers in the fragmented carrier assignments can cause interference to the fragmented carriers. Conventional network implementations do not address this potential for interference to the fragmented carriers.

[0062] The arrangement 400 includes a second fragmented carrier arrangement 430. The second arrangement 430 can include a Broadband Radio Service (BRS) (n7) example of a fragmented spectrum, which in an example implementation can be used for Toronto. The second arrangement 430 includes a first set of carriers 432, a second set of carriers 434, a third set of carriers 436, and a fourth set of carriers 438. The first set of carriers 432 and the fourth set of carriers 438 can be assigned to a first operator (as shown by the corresponding blocks with diagonal fill), which can assign the first set of carriers 432 and the fourth set of carriers 438 to a first UE. The second set of carriers 434 can be assigned to a second operator (as shown by the corresponding blocks without fill), which can assign the second set of carriers 434 to a second UE. The third set of carriers 436 can be assigned to a third operator (as shown by the corresponding blocks with cross-hatch fill), which can assign the third set of carriers 436 to a third UE.

[0063] The first set of carriers 432 and the fourth set of carriers 438 are separated by the second set of carriers 434 and the third set of carriers 436, such that the first set of carriers 432 and the fourth set of carriers 438 are non-contiguous. Since both the first set of carriers 432 and the fourth set of carriers 438 are assigned to the first operator, these carriers can be a fragmented carrier assignment for the first operator. The carriers between the fragmented carriers in the fragmented carrier assignment can cause interference to the fragmented carriers. Conventional network implementations do not address this potential for interference to the fragmented carriers.

[0064] The arrangement 400 includes a third fragmented carrier arrangement 460. The third arrangement 460 can include an Advanced Wireless Services (AWS) 1 / 3 / 4 (n66) example of fragmented spectrum, which in the illustrated embodiment can be used for Montreal. The third arrangement 460 includes a first set of carriers 462, a second set of carriers 464, a third set of carriers 466, a fourth set of carriers 468, a fifth set of carriers 470, a sixth set of carriers 472, and a seventh set of carriers 474. The first set of carriers 462 and the third set of carriers 466 can be assigned to a first operator (as shown by the corresponding blocks without fill), which can assign the first set of carriers 462 and the third set of carriers 466 to a first UE. The second set of carriers 464 and the fifth set of carriers 470 can be assigned to a second operator (as shown by the corresponding blocks with cross-hatched fill), which can assign the second set of carriers 464 and the fifth set of carriers 470 to a second UE. The fourth set of carriers 468 and the sixth set of carriers 472 can be assigned to a third operator (as shown by the corresponding blocks with diagonal fill), which can assign the fourth set of carriers 468 and the sixth set of carriers 472 to a third UE. The seventh set of carriers 474 can be assigned to a fourth operator (as shown by the corresponding blocks with dashed fill), which can assign the seventh set of carriers 474 to a fourth UE.

[0065] The first set of carriers 462 and the third set of carriers 466 are separated by the second set of carriers 464, making the first set of carriers 462 and the third set of carriers 466 non-contiguous. Since both the first set of carriers 462 and the third set of carriers 466 are assigned to the first operator, these carriers can be a fragmented carrier assignment to the first operator. The second set of carriers 464 and the fifth set of carriers 470 are separated by the third set of carriers 466 and the fourth set of carriers 468, making the second set of carriers 464 and the fifth set of carriers 470 non-contiguous. Since both the second set of carriers 464 and the fifth set of carriers 470 are assigned to the second operator, these carriers can be a fragmented carrier assignment to the second operator. The fourth set of carriers 468 and the sixth set of carriers 472 are separated by the fifth set of carriers 470, making the fourth set of carriers 468 and the sixth set of carriers 472 non-contiguous. Since both the fourth set of carriers 468 and the sixth set of carriers 472 are assigned to the third operator, these carriers can be a fragmented carrier assignment to the third operator. The carrier between the fragmented carriers in the fragmented carrier assignment can cause interference to the fragmented carriers. Conventional network implementations do not address this possibility of interference to the fragmented carriers.

[0066] Figure 5 An example carrier gap arrangement 500 is illustrated in accordance with some embodiments. The arrangement 500 illustrates an example of a fragmented carrier assignment with gaps between the fragmented carriers.

[0067] The arrangement 500 includes a first set of carriers 502 and a second set of carriers 504. The first set of carriers 502 and the second set of carriers 504 can be assigned to a first UE. Each of the first set of carriers 502 and the second set of carriers 504 can include one or more carriers. In the illustrated embodiment, each of the first set of carriers 502 and the second set of carriers 504 can include a 20 MHz carrier. In the illustrated embodiment, the first set of carriers 502 can include four carriers and the second set of carriers 504 can include four carriers.

[0068] The arrangement 500 can include a gap 506 between the first set of carriers 502 and the second set of carriers 504. In the illustrated embodiment, the gap 506 can be 10 MHz. There can be other operators operating in the gap between two adjacent frequency blocks, presenting a strong interferer / blocker. The carriers within the gap can not be assigned to the first UE. In some embodiments, a portion of the carriers within the gap 506 can be assigned to other UEs. For example, in the illustrated embodiment, a portion of the carriers can be assigned to a second UE. The portion of the carriers assigned to the other UE can be referred to as an interferer and / or a blocker. Thus, the arrangement 500 can have an interferer / blocker in the gap 506.

[0069] The arrangement 500 can include guard bands in the first set of carriers 502 and / or the second set of carriers 504. For example, the first set of carriers 502 and the second set of carriers 504 can include guard bands at the edges of the carriers adjacent to the gap 506 that includes the interferer / blocker. In the illustrated embodiment, the first set of carriers 502 includes a first guard band 510 at the edge of the first set of carriers 502 adjacent to the interferer / blocker, and the second set of carriers 504 includes a second guard band 512 at the edge of the second set of carriers 504 adjacent to the interferer / blocker. The carriers within the guard bands can be unassigned and can provide some protection against interference between the interferer / blocker, the first set of carriers 502, and / or the second set of carriers 504.

[0070] Because there can be a blocker located between two frequency blocks, which can cause strong interference to DL reception, the interference must be handled in order to support segmented carrier operation. In this disclosure, the following methods address the interference. The methods can include one or more of the following: UE detection of the blocker, UE reporting of the blocker, UE capability reporting on simultaneous reception of two or more frequency blocks in the DL (the blocker can be closer to one frequency blocker than the other), and / or network configuration and scheduling based on UE reporting.

[0071] The methods described herein can enable detection of the blocker. Prior to scheduling, the network can configure the UE with inter-frequency (New Radio (NR)) / inter-Radio Access Technology (RAT) (Long Term Evolution (LTE)) measurements for the adjacent channels (i.e., the channels operating in the gap between two frequency blocks). For example, a base station can configure a first UE assigned the first set of carriers 502 and the second set of carriers 504, and / or generate a configuration to cause the first UE to measure the interferer / blocker between the first set of carriers 502 and the second set of carriers 504. The base station can configure the UE to measure a New Radio (NR) carrier Received Signal Strength Indicator (RSSI) for NR. Alternatively, the base station can configure the UE to measure an Evolved Universal Terrestrial Radio Access (E-UTRA) carrier RSSI for LTE.

[0072] Based on the measured RSSI and the channel bandwidth information read from the Master Information Block (MIB) / System Information Block (SIB), the UE can derive and report the blocker power level to the network by scaling. For NR, the channel bandwidth can be read from System Information Block 1 (SIB1). For LTE, the channel bandwidth can be read from the MIB. The estimated blocker power level = measured RSSI * channel bandwidth / RSSI measurement bandwidth. For example, the UE can estimate the blocker power level for the interferer / blocker based at least in part on the measured RSSI, the channel bandwidth, and / or the RSSI measurement bandwidth. The UE can estimate the blocker power level as:

[0073] The methods described herein can enable reporting of the blocker power level. For a first option on the reporting mechanism (“Option 1”), it can be configured to be periodic / aperiodic / event triggered by the network. For example, the base station can configure the UE to report the estimated blocker power level periodically, aperiodically, or as triggered by the occurrence of an event.

[0074] The reporting periodicity can be configured based on UE mobility. For example, the base station can determine a speed at which the UE is moving. The base station can determine a periodicity for reporting for the UE based on the determined speed of the UE. For example, the base station can determine that when the speed of travel is above a threshold, the periodicity for reporting for the UE will be a first periodicity, and when the speed of travel is below the threshold, the periodicity for reporting for the UE will be a second periodicity, where the first periodicity is more frequent than the second periodicity. In other embodiments, the base station can have defined ranges of speeds with corresponding thresholds, where for higher ranges of speeds, the periodicity is shorter. The base station can configure the UE with the determined periodicity.

[0075] In some embodiments where the reporting is triggered by the occurrence of an event, the event can be that the blocker level change is greater than a threshold, where the threshold can be preconfigured by the network through radio resource control (RRC). For example, the base station can configure the UE with a blocker level change threshold. The UE can determine an estimated blocker power level. The UE can compare the estimated blocker power level to the last reported blocker power level to determine a difference between the values. The UE can compare the difference to the blocker level change threshold to determine whether the difference is greater than the blocker level change threshold. The UE can generate and / or send a report of the blocker power level to the base station.

[0076] The reporting can be done via uplink control information (UCI) / medium access control (MAC) control element (CE) / RRC. For example, the UE can send a report to the base station indicating the determined blocker power level via UCI, MAC CE, or RRC.

[0077] For a second option, which can be referred to as “Option 2,” the reporting can be configured by RRC and based on MAC CE with the following information elements (IEs):

[0078]

[0079] For example, the base station can generate and / or transmit a blocker power report IE to the UE to configure the UE for blocker power reporting. The blocker power report can include a periodic timer IE, a prohibit timer IE, and / or a power factor change IE. The periodic timer IE can be used to configure a periodic timer of the UE for reporting, where the UE can transmit a blocker power report when the periodic timer expires. The prohibit timer IE can be used to configure a prohibit timer of the UE for reporting, where the UE can be prevented from transmitting a blocker report until the prohibit timer expires. As described above, the power factor change IE can be used to configure a blocker level change threshold for determining whether to report a blocker power level.

[0080] The methods described herein can enable UE capability reporting. If a UE can be simultaneously scheduled with two or more frequency blocks, the UE can indicate its capability. For example, the UE can provide an indication to the base station about whether the UE supports simultaneous scheduling of segmented carriers.

[0081] In a first option, which can be referred to as “Option 1,” the UE can indicate how many non-contiguous frequency blocks can be simultaneously scheduled in the downlink, DL, where the gap between any two adjacent frequency blocks is 5 MHz or greater. For example, the UE can determine how many non-contiguous frequency blocks with a guard band of 5 MHz or greater the UE supports. The UE can generate and / or transmit a capability information report indicating the determined number of supported non-contiguous frequency blocks.

[0082] In a second option, which can be referred to as “Option 2,” in addition to the number of non-contiguous frequency blocks, the UE can further indicate a maximum blocker power level in a gap that it can handle when supporting simultaneous DL scheduling. For example, in addition to the capability information report indicating the determined number of supported frequency blocks, the capability information report can include an indication of a maximum blocker power level for a blocker in a gap between supported non-contiguous frequency blocks.

[0083] In a first approach of the second option, which can be referred to as “Option 2.1,” the UE can further indicate a number of levels of maximum blocker power levels in a gap that it can handle when supporting simultaneous DL scheduling, along with a corresponding required guard band (GB) that is greater than a minimum GB specified in a specification. For example, the UE can determine one or more ranges of blocker power levels. The UE can also determine a guard band size for each of the ranges of blocker power levels. The UE can indicate the ranges of blocker power levels and the corresponding guard band sizes for each of the ranges of blocker power levels, such as within a capability information report. For example, the indicated guard band sizes can define a size of a first guard band 510( Figure 5 ) and / or a second guard band 512( Figure 5 ).

[0084] In some embodiments, as an example, the UE can indicate the following: P0 decibels-milliwatts (dBm) is less than or equal to a blocking party power less than P1 dBm, GB1; P1 dBm is less than or equal to a blocking party power less than P2 dBm, GB2; P2 dBm is less than or equal to a blocking party power less than P3 dBm, GB3... Thus, the UE can indicate that for a blocking party power level between 0 dBm and P1 dBm, the guard band size will be GB1, for a blocking party power level between P1 dBm and P2 dBm, the guard band size will be GB2, for a blocking party power level between P2 dBm and P3 dBm, the guard band size will be GB3, and so on.

[0085] Since multi-block scheduling is for DL, the GB for DL and uplink (UL) can be different. For example, in some embodiments, the GB for DL can be larger than the nominal GB, while the GB for UL can remain as the nominal GB.

[0086] The methods described herein can enable network configuration and scheduling. Multiple GB sizes can be specified, and the network can configure them to the UE through RRC. For example, a base station can determine a size of a guard band, such as a first guard band 510( Figure 5 ) and / or a second guard band 512( Figure 5 ). The base station can generate and / or transmit a configuration to the UE that configures the UE with one or more guard bands having the determined size.

[0087] In a first option, the network can change the GB setting using RRC or MAC CE according to the UE’s capability and blocking party power report. For example, a base station can receive capability information and / or a blocking party power level reported by a UE. The base station can determine a GB size for the UE based on the capability information and / or the blocking party power level reported by the UE. If the determined GB size is different from the current GB size, the base station can generate and / or transmit a configuration update to the UE that indicates the UE is to update the GB. A UE requirement, such as a GB setting change delay, can be specified to allow time for UE filter adaptation time. For example, the base station can implement a delay in the update of the GB size to allow for UE filter adaptation.

[0088] In a second option, the network does not explicitly configure the GB setting to the UE. Instead, the network can schedule the UE with RB allocations that always satisfy the required GB. For example, a base station can determine a GB size for a UE based on capability information and / or a blocking party power level reported by the UE. The base station can schedule the UE with RB allocations that avoid the determined GB size without explicitly configuring the UE with the determined GB size.

[0089] If the blocker power level is too high, the network can fall back to scheduling only one frequency block to such UEs. For example, the base station can determine whether the blocker power level of the blocker / interferer exceeds the supported blocker power level of the UE. If the base station determines that the blocker power level exceeds the supported blocker power level, the base station can determine that the UE will be configured with one frequency block instead of two or more non-contiguous frequency blocks. The base station can then generate and / or transmit a configuration to the UE to configure the UE with one frequency block instead of two or more frequency blocks.

[0090] Figure 6 A process 600 for configuring a UE according to some embodiments is illustrated. For example, the process 600 can implement one or more of the methods described throughout the present disclosure.

[0091] The process 600 can include the UE indicating capabilities at 602. For example, the UE can indicate UE capabilities to a base station as described throughout the present disclosure. The UE can generate and / or transmit a capability information message to the base station indicating frequency block and / or guard band information supported by the UE as described throughout the present disclosure.

[0092] The process 600 can include the network configuring a blocker power report at 604. For example, the base station can configure the UE to perform blocker power level measurements and / or report blocker power level measurement results according to the methods described herein.

[0093] The process 600 can include the UE performing estimation and reporting a blocker power report at 606. For example, the UE can measure RSSI and estimate a blocker power level for a blocker / interferer according to the methods described herein. Further, the UE can report the blocker power level according to the configuration of 604.

[0094] The process 600 can include determining whether the blocker power can be handled by a guard band at 608. For example, the base station can determine whether the UE supports blocker level power based on the capability information indicated at 602. The base station can determine the blocker level power based on the estimated blocker power level reported by the UE at 606.

[0095] If the base station determines that the blocker power can be handled by a guard band at 608, the process 600 can proceed to 610. The process 600 can include the network configuring a corresponding guard band in DL scheduling of multiple frequency blocks at 610. For example, the base station can determine appropriate frequency blocks and / or guard bands for the UE based on the blocker power level according to the methods described herein. The base station can configure the UE with the determined frequency blocks and / or guard bands.

[0096] If the base station determines that the blocker power cannot be handled by the guard band, the process 600 can proceed to 612. The process 600 can include the network scheduling only one frequency block in the DL at 612. For example, the base station can configure the UE with a single frequency block.

[0097] Figure 7 An example process 700 for determining and reporting a blocker power level is illustrated in accordance with some embodiments. The process 700 can be performed by a UE, such as the UE 104( Figure 1 ), the UE 106( Figure 1 ), and / or the UE 200( Figure 2 ).

[0098] The process 700 can include performing a measurement of an RSSI of a neighboring channel at 702. For example, the UE can perform a measurement of an RSSI of a neighboring channel operating in a gap between two frequency blocks to be configured for the UE.

[0099] The process 700 can include determining a blocker power level based at least in part on the measured RSSI at 704. In some embodiments, the process 700 can further include reading a channel bandwidth corresponding to the neighboring channel, wherein the blocker power level is further determined based at least in part on the channel bandwidth.

[0100] The process 700 can include generating a report indicating the blocker power level for transmission at 706. In some embodiments, the process 700 can further include identifying a blocker power report configuration to configure the blocker power level report. The blocker power report configuration can include a periodic timer information element to configure a periodic timer for the blocker power level report, a prohibit timer information element to configure a prohibit timer for the blocker power level report, or a power headroom change information element to configure a threshold power level difference for the blocker power level report.

[0101] In some embodiments, the process 700 can further include generating a capability indication for transmission. The capability indication can indicate how many non-contiguous frequency blocks can be simultaneously scheduled in a downlink (DL). In some of these embodiments, the capability indication can further indicate a maximum blocker power level for the gap when simultaneous DL scheduling is supported. Further, in some embodiments, the capability indication can further indicate a first minimum guard band for a first blocker power range and a second minimum guard band for a second blocker power range.

[0102] In some embodiments, the process 700 can further include identifying a guard band configuration received from a base station, and adapting a filter for the gap based at least in part on the guard band configuration.

[0103] In some embodiments, the process 700 can further include performing additional RSSI measurements for the adjacent channel, and determining one or more additional blocker power levels based at least in part on the additional RSSI measurements. The process 700 can further include periodically generating one or more reports indicating the one or more additional blocker power levels for transmission.

[0104] In some embodiments, the process 700 can further include performing additional RSSI measurements for the adjacent channel, and determining an additional blocker power level based at least in part on the additional RSSI measurements. The process 700 can further include determining a difference between the additional blocker power level and the blocker power level; determining whether the difference exceeds a threshold power level difference; and determining whether to generate an additional report indicating the additional blocker power level for transmission based at least in part on whether the difference is determined to exceed the threshold power level difference.

[0105] In embodiments, Figure 7 Any one or more of the operations in the process 700 can be performed in a different order than shown, and / or one or more of the operations can be performed concurrently. Furthermore, it will be appreciated that, in other embodiments, one or more of the operations can be omitted and / or one or more additional operations can be added to the process 700.

[0106] Figure 8 An example process 800 for configuring a UE is illustrated in accordance with some embodiments. The process 800 can be performed by a base station such as the base station 108( Figure 1 ) and / or the network device 300( Figure 3 ).

[0107] The process 800 can include configuring a UE for measuring an adjacent channel, at 802. For example, a base station can configure a user equipment (UE) for measuring an adjacent channel operating in a gap between two frequency blocks to be configured for the UE.

[0108] In some embodiments, configuring the UE for measuring the adjacent channel can include configuring the UE for inter-frequency measurements for the adjacent channel, or configuring the UE for inter-radio access technology (RAT) measurements for the adjacent channel.

[0109] In some embodiments, configuring the UE for measuring the adjacent channel can include configuring the UE to measure a new radio (NR) carrier received signal strength indicator (RSSI) of the adjacent channel, or configuring the UE to measure an evolved universal terrestrial radio access (E-UTRA) carrier RSSI of the adjacent channel.

[0110] In some embodiments, the process 800 can further include configuring the UE to periodically report the blocker power level for the adjacent channel, or to report the blocker power level for the adjacent channel when a change in the blocker power level exceeds a threshold.

[0111] In some embodiments, the process 800 can further include generating a blocker power report configuration for transmission to the UE. The blocker power report configuration can include a periodic timer information element to configure a periodic timer for blocker power level reporting, a prohibit timer information element to configure a prohibit timer for blocker power level reporting, or a power headroom change information element to configure a threshold power level difference for blocker power level reporting.

[0112] In some embodiments, the process 800 can further include identifying a capability indication message received from the UE. The capability indication message can include an indication of an amount of contiguous frequency blocks that can be simultaneously scheduled for the UE in the downlink, where the configuration is determined based at least in part on the indicated amount of contiguous frequency blocks. In some of these embodiments, the capability indication message can further include a maximum blocker power level for a gap, where the configuration is further determined based at least in part on the maximum blocker power level. In some of these embodiments, the process 800 can further include configuring a guard band for the gap based at least in part on the capability information from the capability indication message and the blocker power level. In other of these embodiments, the process 800 can further include scheduling a resource block allocation for the UE based at least in part on the capability information from the capability indication message and the blocker power level.

[0113] The process 800 can include identifying a report in 804. For example, the base station can identify a report received from a UE. The report can indicate a blocker power level for an adjacent channel.

[0114] The process 800 can include determining a configuration of the two frequency blocks in 806. For example, the base station can determine a configuration of two frequency blocks for the UE based at least in part on the blocker power level.

[0115] The process 800 can include configuring the UE according to the determined configuration in 808.

[0116] In an embodiment, Figure 8 Any one or more of the operations in the process 800 can be performed in a different order than shown and / or one or more of the operations can be performed concurrently. Furthermore, it will be appreciated that, in other embodiments, one or more of the operations can be omitted and / or one or more additional operations can be added to the process 800.

[0117] Figure 9 An example process 900 for generating a report of a blocker power level is illustrated in accordance with some embodiments. Process 900 can be performed by a UE, such as UE 104( Figure 1 ), UE 106( Figure 1 ), and / or UE 200( Figure 2 ).

[0118] Process 900 can include generating, in 902, a capability indication message for transmission to a base station. The capability indication message can include an indication of an amount of non-contiguous frequency blocks supported for simultaneous scheduling in a downlink (DL).

[0119] In some embodiments, the capability indication message can also include a maximum blocker power level for a gap in the DL supported for simultaneous scheduling, or an indication of one or more minimum guard bands for one or more blocker power ranges.

[0120] Process 900 can include identifying, in 904, a blocker power level configuration. For example, the UE can identify a blocker power level configuration for measuring a blocker power level of a neighbor channel operating in a gap between two frequency blocks configurable for the user equipment.

[0121] Process 900 can include determining, in 906, a blocker power level for the neighbor channel. For example, the UE can determine the blocker power level for the neighbor channel according to the blocker power level configuration. In some embodiments, the blocker power level can include performing a measurement of a received signal strength indicator (RSSI) of the neighbor channel, where the blocker power level is determined based at least in part on the measured RSSI.

[0122] Process 900 can include generating, in 908, a report. For example, the UE can generate a report indicating the blocker power level for transmission.

[0123] In embodiments, Figure 9 Any one or more of the operations in

[0124] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled in a way to minimize risks of unintentional or unauthorized access or use, and the nature of the appropriate level of protection should be clearly indicated to users.

[0125] For one or more embodiments, at least one of the components illustrated in one or more of the preceding figures can be configured to perform one or more operations, techniques, procedures, or methods set forth in the Example section below. For example, the baseband circuitry described above in connection with one or more of the preceding figures can be configured to operate according to one or more of the examples described below. In another example, circuitry associated with a UE, base station, network element, etc. described above in connection with one or more of the preceding figures can be configured to operate according to one or more of the examples set forth in the Example section below.

[0126] Example

[0127] In the following sections, additional example embodiments are provided.

[0128] Example 1 can include a method comprising performing a measurement of a received signal strength indicator (RSSI) of a neighbor channel operating in a gap between two frequency blocks to be configured for a user equipment (UE); determining a blocker power level based at least in part on the measured RSSI; and generating a report indicating the blocker power level for transmission.

[0129] Example 2 can include the method of Example 1, further comprising reading a channel bandwidth corresponding to the neighbor channel, wherein the blocker power level is further determined based at least in part on the channel bandwidth.

[0130] Example 3 can include the method of Example 1, further comprising performing an additional RSSI measurement for the neighbor channel; determining one or more additional blocker power levels based at least in part on the additional RSSI measurement; and periodically generating one or more reports indicating the one or more additional blocker power levels for transmission.

[0131] Example 4 can include the method of Example 1, further comprising performing an additional RSSI measurement for the neighbor channel; determining an additional blocker power level based at least in part on the additional RSSI measurement; determining a difference between the additional blocker power level and the blocker power level; determining whether the difference exceeds a threshold power level difference; and determining whether to generate an additional report indicating the additional blocker power level for transmission based at least in part on whether the difference is determined to exceed the threshold power level difference.

[0132] Example 5 can include a method as described in example 1, further comprising identifying a blocker power reporting configuration for configuring a blocker power level report, the blocker power reporting configuration comprising a periodic timer information element for configuring a periodic timer for the blocker power level report, a prohibit timer information element for configuring a prohibit timer for the blocker power level report, or a power headroom change information element for configuring a threshold power level difference for the blocker power level report.

[0133] Example 6 can include a method as described in example 1, further comprising generating a capability indication for transmission, the capability indication indicating how many discontinuous frequency blocks can be simultaneously scheduled in downlink (DL).

[0134] Example 7 can include a method as described in example 6, wherein the capability indication further indicates a maximum blocker power level for the gap when simultaneous DL scheduling is supported.

[0135] Example 8 can include a method as described in example 6, wherein the capability indication further indicates a first minimum guard band for a first blocker power range and a second minimum guard band for a second blocker power range.

[0136] Example 9 can include a method as described in example 1, further comprising identifying a guard band configuration received from a base station, and adapting a filter for the gap based at least in part on the guard band configuration.

[0137] Example 10 can include a method comprising configuring a user equipment (UE) for measuring a neighbor channel operating in a gap between two frequency blocks to be configured for the UE; identifying a report received from the UE, the report indicating a blocker power level for the neighbor channel; determining a configuration for the two frequency blocks of the UE based at least in part on the blocker power level; and configuring the UE according to the determined configuration.

[0138] Example 11 can include a method as described in example 10, wherein configuring the UE for measuring the neighbor channel comprises configuring the UE for inter- frequency measurements for the neighbor channel, or configuring the UE for inter-radio access technology (RAT) measurements for the neighbor channel.

[0139] Example 12 can include the method of example 10, wherein configuring the UE to measure the adjacent channel comprises configuring the UE to measure a New Radio (NR) Carrier Received Signal Strength Indicator (RSSI) of the adjacent channel or configuring the UE to measure an Evolved Universal Terrestrial Radio Access (E-UTRA) Carrier RSSI of the adjacent channel.

[0140] Example 13 can include the method of example 10, further comprising configuring the UE to periodically report a blocker power level for the adjacent channel or configuring the UE to report a blocker power level for the adjacent channel when a change in the blocker power level exceeds a threshold value.

[0141] Example 14 can include the method of example 10, further comprising generating a blocker power reporting configuration for transmission to the UE, the blocker power reporting configuration comprising a periodic timer information element to configure a periodic timer for the blocker power level reporting, a prohibit timer information element to configure a prohibit timer for the blocker power level reporting, or a power headroom change information element to configure a threshold power level difference for the blocker power level reporting.

[0142] Example 15 can include the method of example 10, further comprising identifying a capability indication message received from the UE, the capability indication message comprising an indication of an amount of non-contiguous frequency blocks that can be simultaneously scheduled for the UE in a downlink, wherein the configuration is determined based at least in part on the amount of non-contiguous frequency blocks indicated.

[0143] Example 16 can include the method of example 15, wherein the capability indication message further comprises a maximum blocker power level for the gap, wherein the configuration is further determined based at least in part on the maximum blocker power level.

[0144] Example 17 can include the method of example 15, further comprising configuring a guard band for the gap based at least in part on capability information from the capability indication message and the blocker power level.

[0145] Example 18 can include the method of example 15, further comprising scheduling a resource block allocation for the UE based at least in part on capability information from the capability indication message and the blocker power level.

[0146] Example 19 can include a method comprising generating a capability indication message for transmission to a base station, the capability indication message comprising an indication of an amount of non-contiguous frequency blocks supported for simultaneous scheduling in a downlink (DL); identifying a blocker power level configuration for measuring a blocker power level for a neighbor channel operating in a gap between two frequency blocks capable of being configured for a user equipment; determining the blocker power level for the neighbor channel according to the blocker power level configuration; and generating a report indicating the blocker power level for transmission.

[0147] Example 20 can include the method of example 19, wherein determining the blocker power level comprises performing a measurement of a received signal strength indicator (RSSI) of the neighbor channel, wherein the blocker power level is determined based at least in part on the measured RSSI.

[0148] Example 21 can include the method of example 19, wherein the capability indication message further comprises a maximum blocker power level for the gap in the DL supported simultaneously, or an indication of one or more minimum guard bands for one or more blocker power ranges.

[0149] Example 22 can include an apparatus comprising means for performing one or more elements of a method described in or related to any of examples 1-21, or any other method or process described herein.

[0150] Example 23 can include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-21, or any other method or process described herein.

[0151] Example 24 can include an apparatus comprising logic, modules, or circuitry for performing one or more elements of a method described in or related to any of examples 1-21, or any other method or process described herein.

[0152] Example 25 can include methods, techniques, or processes as described in or related to any of examples 1-21, or portions or parts thereof.

[0153] Example 26 can include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-21, or portions thereof.

[0154] Example 27 can include a signal as described in or related to any of examples 1-21, or portions thereof.

[0155] Example 28 can include a datagram, information element, packet, frame, segment, PDU, or message as described in or related to any of examples 1-21, or portions thereof.

[0156] Example 29 can include a signal encoded with data as described in or related to any of examples 1-21, or portions thereof.

[0157] Example 30 can include a signal encoded with a datagram, IE, packet, frame, segment, PDU, or message as described in or related to any of examples 1-21, or portions thereof.

[0158] Example 31 can include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process as described in or related to any of examples 1-21, or portions thereof.

[0159] Example 32 can include a computer program comprising instructions, wherein execution of the program by a processing element will cause the processing element to perform a method, technique, or process as described in or related to any of examples 1-21, or portions thereof.

[0160] Example 33 can include a signal in a wireless network as shown and described herein.

[0161] Example 34 can include a method of communicating in a wireless network as shown and described herein.

[0162] Example 35 can include a system for providing wireless communication as shown and described herein.

[0163] Example 36 can include an apparatus for providing wireless communication as shown and described herein.

[0164] Unless otherwise expressly stated, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. In view of the teachings above, modifications and variations are possible, or modifications and variations may be obtained from the practice of various embodiments.

[0165] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the above disclosure is fully understood. It is intended that the following claims be construed as encompassing all such variations and modifications.

Claims

1. A method, the method comprising: Perform measurements of the Received Signal Strength Indicator (RSSI) of adjacent channels operating in the gap between two frequency blocks to be configured for the User Equipment (UE); The blocking power level is determined at least in part based on the measured RSSI; as well as Generate a report indicating the power level of the blocking side used for transmission.

2. The method according to claim 1, further comprising: Read the channel bandwidth corresponding to the adjacent channel, wherein the blocking power level is further determined at least in part based on the channel bandwidth.

3. The method according to claim 1 or claim 2, further comprising: Perform additional RSSI measurements for the adjacent channels; The power levels of one or more additional blocking sides are determined at least in part based on the additional RSSI measurements. as well as Periodically generate one or more reports indicating the power level of the one or more additional blocking sides used for transmission.

4. The method according to claim 1 or claim 2, further comprising: Perform additional RSSI measurements for the adjacent channels; The additional blocking power level is determined at least in part based on the additional RSSI measurement; Determine the difference between the additional blocking power level and the blocking power level; Determine whether the difference exceeds the threshold power level difference; as well as Whether to generate an additional report indicating the additional blocking power level used for transmission is determined at least in part based on whether the difference is determined to exceed the threshold power level difference.

5. The method according to claim 1 or claim 2, further comprising: Identify a blocking power reporting configuration used to configure blocking power level reporting, the blocking power reporting configuration including: Periodic timer information element for configuring a periodic timer for power level reporting of the blocking side; A disable timer information element used to configure a disable timer for power level reporting by the blocking party; or Power factor change information element used to configure the threshold power level difference for the power level reporting of the blocking side.

6. The method according to claim 1 or claim 2, further comprising: Generate a capability indication for transmission, which indicates how many discontinuous frequency blocks can be scheduled simultaneously in the downlink (DL).

7. The method of claim 6, wherein the capability indication further indicates the maximum blocking power level for the gap when supporting simultaneous DL scheduling.

8. The method of claim 6, wherein the capability indication further indicates: The first minimum protection band for the first blocking power range; and The second minimum protection band is used for the second blocking power range.

9. The method according to claim 1 or claim 2, further comprising: Identify the guard band configuration received from the base station; as well as The filter for the gap is adapted at least in part based on the guard band configuration.

10. A method, the method comprising: Generate a blocking power level configuration for transmission to the user equipment (UE) to measure adjacent channels operating in the gap between two frequency blocks that can be configured for the UE; Identify a report received from the UE, the report indicating the blocking power level for the adjacent channel; The configuration of the two frequency blocks for the UE is determined at least in part based on the power level of the blocking side; as well as Generate a guard band configuration for sending to the UE based on the determined configuration.

11. The method of claim 10, wherein the blocking power level is configured as follows: Configure the UE for inter-frequency measurements of the adjacent channels; or The UE is configured for inter-Radio Access Technology (RAT) measurements for the adjacent channels.

12. The method according to claim 10 or claim 11, wherein the blocking power level is configured as follows: Configure the UE to measure the New Radio (NR) Carrier Received Signal Strength Indicator (RSSI) of the adjacent channel; or Configure the UE to measure the RSSI of the Evolved Universal Terrestrial Radio Access (E-UTRA) carrier of the adjacent channel.

13. The method according to claim 10 or claim 11, further comprising: The UE is configured to periodically report the blocking power level for the adjacent channel; or The UE is configured to report the blocking power level for the adjacent channel when the change in the blocking power level exceeds a threshold.

14. The method according to claim 10 or claim 11, further comprising: Generate a blocking power report configuration for transmission to the UE, the blocking power report configuration including: Periodic timer information element for configuring a periodic timer for power level reporting of the blocking side; A disable timer information element used to configure a disable timer for power level reporting by the blocking party; or Power factor change information element used to configure the threshold power level difference for the power level reporting of the blocking side.

15. The method according to claim 10 or claim 11, further comprising: Identify a capability indication message received from the UE, the capability indication message including an indication of the amount of discontinuous frequency blocks that the UE can simultaneously schedule in the downlink, wherein the configuration is determined at least in part based on the amount of the indicated discontinuous frequency blocks.

16. The method of claim 15, wherein the capability indication message further includes a maximum blocking power level for the gap, wherein the configuration is further determined at least in part based on the maximum blocking power level.

17. The method according to claim 15, further comprising: The guard band for the gap is configured at least in part based on capability information from the capability indication message and the power level of the blocking side.

18. One or more computer-readable media having instructions that, when executed, cause processing circuitry to perform the following operations: Generate a capability indication message for transmission to the base station, the capability indication message including an indication of the amount of discontinuous frequency blocks that support simultaneous scheduling in the downlink (DL); Identify the blocking power level configuration used to measure the blocking power level of adjacent channels operating in the gap between two frequency blocks that can be configured for user equipment; The blocking power level for the adjacent channel is determined based on the blocking power level configuration; and Generate a report indicating the power level of the blocking side used for transmission.

19. One or more computer-readable media according to claim 18, wherein determining the blocking power level comprises: Perform a measurement of the Received Signal Strength Indicator (RSSI) of the adjacent channel, wherein the blocking power level is determined at least in part based on the measured RSSI.

20. One or more computer-readable media according to claim 18 or claim 19, wherein the capability indication message further comprises: The DL supports the maximum blocking power level for the gap simultaneously. or Indication of one or more minimum protection bands for one or more blocking power ranges.

Images