Joint dl / ul bandwidth technology in full duplex mode

Abstract

In one aspect, a method of wireless communication includes receiving, by a wireless communication device, first data during a slot according to a first resource bandwidth (RBW) configuration of a bandwidth part (BWP) configuration, where the BWP configuration is configured for uplink and downlink operations. The method further includes transmitting, by the wireless communication device, second data during the slot according to a second RBW configuration of the BWP configuration, where the second RBW configuration is different from the first RBW configuration. Other aspects and features are also claimed and described.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to Greek patent application No. 20200100291 (204877GR1), filed on May 29, 2020, entitled “JOINT DL / UL BWP IN FULL-DUPLEXMODE”, the disclosure of which is hereby incorporated by reference as fully set forth below and for all applicable purposes. Technical Field

[0003] This disclosure generally relates to wireless communication systems, and more particularly to full-duplex wireless communication. Certain embodiments of the techniques discussed below are capable of implementing and providing combined downlink and uplink bandwidth portion operation for full-duplex wireless communication modes.

[0004] introduction

[0005] Wireless communication networks are widely deployed to provide various communication services, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These wireless networks can be multiple-access networks capable of supporting multiple users by sharing available network resources. Typically, such multiple-access networks support communication for multiple users by sharing available network resources.

[0006] A wireless communication network may include several base stations or B-nodes capable of supporting communication between several user equipments (UEs). UEs may communicate with base stations via downlinks and uplinks. A downlink (or forward link) refers to the communication link from the base station to the UE, while an uplink (or reverse link) refers to the communication link from the UE to the base station.

[0007] The base station can transmit data and control information to the UE on the downlink and / or receive data and control information from the UE on the uplink. On the downlink, transmissions from the base station may encounter interference from neighboring base stations or other radio frequency (RF) transmitters. On the uplink, transmissions from the UE may encounter interference from uplink transmissions from other UEs communicating with neighboring base stations or from other RF transmitters. This interference can degrade the performance of both the downlink and uplink.

[0008] As the demand for mobile broadband access continues to grow, and more user devices (UEs) are accessing long-range wireless communication networks and more short-range wireless systems are being deployed in communities, the likelihood of network interference and congestion is increasing. Research and development are continuously advancing wireless technologies to not only meet the growing demand for mobile broadband access but also to enhance and improve the user experience of mobile communications.

[0009] Overview

[0010] The following outlines some aspects of this disclosure to provide a basic understanding of the techniques discussed. This overview is not an exhaustive summary of all conceived features of this disclosure, and is neither intended to identify all key or decisive elements of all aspects of this disclosure, nor to define the scope of any or all aspects of this disclosure. Its sole purpose is to provide, in an overview form, some concepts of one or more aspects of this disclosure as a prelude to the more detailed description that follows.

[0011] In one aspect of this disclosure, a wireless communication method includes: receiving first data by a wireless communication device during a time slot according to a first resource bandwidth (RBW) configuration configured with a bandwidth portion (BWP), wherein the BWP configuration is configured for uplink and downlink operation; and transmitting second data by the wireless communication device during the time slot according to a second RBW configuration configured with the BWP, the second RBW configuration being different from the first RBW configuration.

[0012] In an additional aspect of this disclosure, an apparatus configured for wireless communication is disclosed. The apparatus includes at least one processor and a memory coupled to the processor. The processor is configured to: receive first data during a time slot according to a first resource bandwidth (RBW) configuration configured with a bandwidth portion (BWP), wherein the BWP configuration is configured for uplink and downlink operation; and transmit second data during the time slot according to a second RBW configuration configured with the BWP, the second RBW configuration being different from the first RBW configuration.

[0013] In an additional aspect of this disclosure, a non-transient computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform operations including: receiving first data during a time slot according to a first resource bandwidth (RBW) configuration configured according to a bandwidth portion (BWP) configuration, wherein the BWP configuration is configured for uplink and downlink operations; and transmitting second data during the time slot according to a second RBW configuration configured according to the BWP configuration, the second RBW configuration being different from the first RBW configuration.

[0014] In an additional aspect of this disclosure, an apparatus configured for wireless communication is disclosed. The apparatus includes: means for receiving first data during a time slot according to a first resource bandwidth (RBW) configuration configured with a bandwidth portion (BWP), wherein the BWP configuration is configured for uplink and downlink operation; and means for transmitting second data during the time slot according to a second RBW configuration configured with the BWP, the second RBW configuration being different from the first RBW configuration.

[0015] In another aspect of this disclosure, a wireless communication method includes: a wireless communication device communicating during a first time slot according to a first resource bandwidth (RBW) configuration configured by a bandwidth portion (BWP); the wireless communication device changing from the first RBW configuration to a second RBW configuration based on a BWP handover trigger and RBW configuration information; and the wireless communication device communicating during a second time slot according to the second RBW configuration, which is different from the first RBW configuration.

[0016] In another aspect of this disclosure, a wireless communication method includes: operating by a user equipment (UE) in a first time slot according to a first bandwidth portion (BWP) configuration having a first resource bandwidth (RBW) configuration; determining a BWP handover trigger and an RBW configuration by the UE; determining a second RBW configuration for a second time slot based on the BWP handover trigger and the RBW configuration, the second RBW configuration being different from the first RBW configuration; and operating by the UE in accordance with the second RBW configuration during the second time slot.

[0017] In an additional aspect of this disclosure, an apparatus configured for wireless communication is disclosed. The apparatus includes: means for operation by a user equipment (UE) in a first time slot according to a first BWP configuration having a first RBW configuration; means for determining a BWP handover trigger and an RBW configuration by the UE; means for determining a second RBW configuration for a second time slot based on the BWP handover trigger and the RBW configuration, the second RBW configuration being different from the first RBW configuration; and means for operation by the UE during the second time slot according to the second RBW configuration.

[0018] In an additional aspect of this disclosure, a non-transient computer-readable medium having program code recorded thereon is disclosed. The program code further includes code for: operation by a user equipment (UE) in a first time slot according to a first BWP configuration having a first RBW configuration; determination by the UE of a BWP handover trigger and RBW configuration; determination by the UE of a second RBW configuration for a second time slot based on the BWP handover trigger and the RBW configuration, the second RBW configuration being different from the first RBW configuration; and operation by the UE in accordance with the second RBW configuration during the second time slot.

[0019] In an additional aspect of this disclosure, an apparatus configured for wireless communication is disclosed. The apparatus includes at least one processor and a memory coupled to the processor. The processor is configured to: be operated by a user equipment (UE) in a first time slot according to a first BWP configuration having a first RBW configuration; be determined by the UE of a BWP handover trigger and an RBW configuration; be determined by the UE of a second RBW configuration for a second time slot based on the BWP handover trigger and the RBW configuration, the second RBW configuration being different from the first RBW configuration; and be operated by the UE in the second time slot according to the second RBW configuration.

[0020] In another aspect of this disclosure, a wireless communication method includes: operating by a network entity in a first time slot according to a first BWP configuration having a first RBW configuration; determining a BWP handover trigger and an RBW configuration by the network entity; determining a second RBW configuration for a second time slot of the first BWP configuration based on the BWP handover trigger and the RBW configuration, the second RBW configuration being different from the first RBW configuration; and operating by the network entity in accordance with the second RBW configuration during the second time slot.

[0021] In an additional aspect of this disclosure, an apparatus configured for wireless communication is disclosed. The apparatus includes: means for operation by a network entity in a first time slot according to a first BWP configuration having a first RBW configuration; means for determining a BWP handover trigger and an RBW configuration by the network entity; means for determining, by the network entity, a second RBW configuration for a second time slot based on the BWP handover trigger and the RBW configuration, the second RBW configuration being different from the first RBW configuration; and means for operation by the network entity in the second time slot according to the second RBW configuration.

[0022] In an additional aspect of this disclosure, a non-transient computer-readable medium having program code recorded thereon is disclosed. The program code further includes code for: operation by a network entity in a first time slot according to a first BWP configuration having a first RBW configuration; determination by the network entity of a BWP handover trigger and an RBW configuration; determination by the network entity of a second RBW configuration for a second time slot based on the BWP handover trigger and the RBW configuration, the second RBW configuration being different from the first RBW configuration; and operation by the network entity in accordance with the second RBW configuration during the second time slot.

[0023] In an additional aspect of this disclosure, an apparatus configured for wireless communication is disclosed. The apparatus includes at least one processor and a memory coupled to the processor. The processor is configured to: be operated by a network entity in a first time slot according to a first BWP configuration having a first RBW configuration; be operated by the network entity to determine a BWP handover trigger and an RBW configuration; be operated by the network entity based on the BWP handover trigger and the RBW configuration to determine a second RBW configuration of the first BWP configuration for a second time slot, the second RBW configuration being different from the first RBW configuration; and be operated by the network entity during the second time slot according to the second RBW configuration.

[0024] Other aspects, features, and embodiments will become apparent to those skilled in the art after reading the following description of specific exemplary embodiments in conjunction with the accompanying drawings. Although features may be discussed hereinafter with reference to certain aspects and drawings, all embodiments may include one or more of the advantageous features discussed herein. In other words, although one or more aspects may be discussed having certain advantageous features, one or more such features may also be used depending on various aspects. Similarly, although exemplary aspects may be discussed hereinafter as aspects of an apparatus, system, or method, exemplary aspects may be implemented in various apparatuses, systems, and methods. Brief description of the attached diagram

[0026] A further understanding of the nature and advantages of this disclosure can be obtained by referring to the following figures. In the figures, similar components or features may have the same reference numerals. Furthermore, components of the same type may be distinguished by a dash following the reference numeral and a second reference numeral used to differentiate between similar components. If only the first reference numeral is used in the description, the description may be applied to any of the similar components having the same first reference numeral regardless of the second reference numeral.

[0027] Figure 1 This is a block diagram illustrating the details of a wireless communication system according to some embodiments of the present disclosure.

[0028] Figure 2 This is a block diagram that conceptually illustrates the design of a base station and a UE configured according to some embodiments of this disclosure.

[0029] Figure 3A This is a diagram illustrating a first example of full-duplex operation according to some embodiments of the present disclosure.

[0030] Figure 3B This is a diagram illustrating a second example of full-duplex operation according to some embodiments of the present disclosure.

[0031] Figure 3CThis is a diagram illustrating a third example of full-duplex operation according to some embodiments of the present disclosure.

[0032] Figure 3D This is a diagram illustrating a fourth example of full-duplex operation according to some embodiments of the present disclosure.

[0033] Figure 3E This is a diagram illustrating a fifth example of full-duplex operation according to some embodiments of the present disclosure.

[0034] Figure 3F This is a diagram illustrating a sixth example of full-duplex operation according to some embodiments of the present disclosure.

[0035] Figure 3G This is an example diagram of a BWP handover delay table according to some embodiments of the present disclosure.

[0036] Figure 3H This is a diagram illustrating the time delay in slots caused by switching the bandwidth of the DL BWP according to some embodiments of the present disclosure.

[0037] Figure 4 This is a block diagram illustrating an example of a wireless communication system (with a UE and a base station) having a joint BWP for full-duplex operation according to some embodiments of the present disclosure.

[0038] Figure 5 This is a diagram illustrating an example of the active bandwidth portion (BWP) of a resource bandwidth (RBW) according to some embodiments of the present disclosure.

[0039] Figure 6 This is a diagram of an example BWP including a DL RBW portion and an uplink BWP portion according to some embodiments of this disclosure.

[0040] Figure 7 This is a diagram of another example BWP including a DL RBW portion and an uplink BWP portion according to some embodiments of this disclosure.

[0041] Figure 8 This is a diagram of an example BWP including a UL / DL RBW portion according to some embodiments of this disclosure.

[0042] Figure 9 This is a flowchart illustrating example blocks performed by a UE configured according to some embodiments of this disclosure.

[0043] Figure 10 This is a flowchart illustrating example blocks performed by a base station configured according to some embodiments of the present disclosure.

[0044] Figure 11This is a block diagram conceptually illustrating the design of a UE configured to perform a precoded information update operation according to some embodiments of this disclosure.

[0045] Figure 12 This is a block diagram conceptually illustrating the design of a base station configured to perform precoded information update operations according to some embodiments of the present disclosure.

[0046] Figure 13 This is a flowchart illustrating example blocks performed by a wireless communication device configured according to some embodiments of the present disclosure.

[0047] Detailed description

[0048] The detailed description that follows, taken in conjunction with the accompanying drawings, is intended to describe various configurations and is not intended to limit the scope of this disclosure. Rather, this detailed description includes specific details to provide a thorough understanding of the subject matter of the invention. It will be apparent to those skilled in the art that these specific details are not required in every situation, and in some instances, well-known structures and components are shown in block diagram form for clarity of expression.

[0049] According to some aspects, this disclosure relates to bandwidth portion (BWP) operation for full-duplex wireless communication. According to some aspects, this disclosure provides teachings on enabling and providing improved flexibility and speed by using a BWP with both UL and DL resource bandwidth. Using a BWP with both UL and DL resources enables full-duplex wireless communication within the BWP. That is, uplink and downlink transmissions can be transmitted on the resources (e.g., time and frequency) of the BWP (such as a single BWP). Additionally, compared to using only a UL BWP and only a DL BWP, using a BWP with both UL and DL improves resource utilization and flexibility while also reducing latency.

[0050] Full-duplex wireless communication specifications may have handover delays for switching active BWPs. To illustrate, when switching from a first BWP with a first frequency range to a second BWP with a second frequency range, the handover may result in resources being unused due to the time involved. Unused resources cause communication delays. In some examples, the delay can be a BWP handover delay period in which network bandwidth and spectrum are essentially wasted due to unused resources. The techniques discussed herein can enhance network performance by improving the use of network bandwidth and spectrum through the use of more flexible and rapid procedures.

[0051] According to some aspects, this disclosure provides teachings on enabling and providing improved flexibility and speed through resource bandwidth (RBW). RBW can generally be considered or defined as a portion of a bandwidth resource (such as a bandwidth portion (BWP)). In other words, a BWP may include one or more resource BWs or RBWs. RBW represents a sub-part of a BWP, such as a discrete, divisible portion of the BWP. A BWP may include one or more UL RBWs, DL RBWs, or combined RBWs of different sizes and / or orientations. In some scenarios, RBWs offer greater flexibility and granularity than BWPs. And by configuring / reconfiguring one or more RBWs of a BWP, network spectrum can be adjusted more rapidly (e.g., from time slot to time slot). Rapid adjustment helps reduce or eliminate latency, allowing spectrum adjustments to occur without delay. In some scenarios, BWPs can be adjusted and customized without incurring latency from switching BWPs (i.e., switching the bandwidth or size of a BWP). Such techniques can improve the use of network bandwidth and spectrum, resulting in higher throughput and lower latency.

[0052] This disclosure generally relates to providing or participating in licensed shared access between two or more wireless devices in one or more wireless communication systems (also referred to as wireless communication networks). In various implementations, technologies and apparatus may be used in wireless communication networks such as Code Division Multiple Access (CDMA) networks, Time Division Multiple Access (TDMA) networks, Frequency Division Multiple Access (FDMA) networks, Orthogonal FDMA (OFDMA) networks, Single Carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, fifth-generation (5G) or new radio (NR) networks (sometimes referred to as "5G NR" networks / systems / devices), and other communication networks. As described herein, the terms "network" and "system" may be used interchangeably.

[0053] CDMA networks can implement radio technologies such as Universal Terrestrial Radio Access (UTRA) and CDMA2000. UTRA includes Wideband CDMA (W-CDMA) and Low Chip Rate (LCR). CDMA2000 covers the IS-2000, IS-95, and IS-856 standards.

[0054] TDMA networks can implement radio technologies such as the Global System for Mobile Communications (GSM). The 3rd Generation Partnership Project (3GPP) defines the standard for the Radio Access Network (RAN) (also referred to as GERAN) for GSM EDGE (Enhanced Data Rate GSM Evolution). GERAN is the radio component of GSM / EDGE along with the network that connects base stations (e.g., Ater and Abis interfaces) to base station controllers (A interface, etc.). The radio access network represents the component of the GSM network through which telephone calls and packet data are routed from the Public Switched Telephone Network (PSTN) and the Internet to the subscriber's handset (also called user terminal or user equipment (UE)) and from the subscriber's handset to the PSTN and the Internet. A mobile phone operator's network may include one or more GERANs, which may be coupled to the Universal Terrestrial Radio Access Network (UTRAN) in the case of UMTS / GSM networks. Additionally, the operator's network may also include one or more LTE networks, and / or one or more other networks. Different network types may use different Radio Access Technologies (RATs) and Radio Access Networks (RANs).

[0055] OFDMA networks can implement radio technologies such as Evolved UTRA (E-UTRA), IEEE 802.11, IEEE 802.16, IEEE 802.20, and flash-OFDM. UTRA, E-UTRA, and GSM are part of the Universal Mobile Telecommunications System (UMTS). Specifically, Long Term Evolution (LTE) is a UMTS version using E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents from an organization called the 3rd Generation Partnership Project (3GPP), while cdma2000 is described in documents from an organization called 3rd Generation Partnership Project 2 (3GPP2). These various radio technologies and standards are known or under development. For example, 3GPP is a collaboration between various telecommunications association groups that aims to define globally applicable third-generation (3G) mobile phone specifications. 3GPP Long Term Evolution (LTE) is a 3GPP project aimed at improving the Universal Mobile Telecommunications System (UMTS) mobile phone standard. 3GPP defines specifications for next-generation mobile networks, mobile systems, and mobile devices. This disclosure may describe certain aspects with reference to LTE, 4G, or 5G NR technologies; however, this description is not intended to be limited to any particular technology or application, and one or more aspects described with reference to one technology may be understood to be applicable to another technology. In fact, one or more aspects of this disclosure relate to shared access to radio spectrum between networks using different radio access technologies or radio air interfaces.

[0056] 5G networks envision a variety of deployments, spectrums, services, and devices that can be implemented using a unified OFDM-based air interface. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also considered. 5G NR will be able to scale to provide coverage for: (1) ultra-high density (e.g., approximately 1 M nodes / km) 2 (1) A massive Internet of Things (IoT) with ultra-low complexity (e.g., approximately tens of bits per second), ultra-low energy consumption (e.g., approximately 10+ years of battery life), and deep coverage capable of reaching challenging locations; (2) A massive Internet of Things (IoT) with robust security (to protect sensitive personal, financial, or confidential information), ultra-high reliability (e.g., approximately 99.9999% reliability), ultra-low latency (e.g., approximately 1 millisecond (ms)), and mission-critical control for users with a wide range of mobility or lack of mobility; and (3) Enhanced mobile broadband, including extremely high capacity (e.g., approximately 10 Tbps / km). 2 Extreme data rates (e.g., multi-Gbps rates, 100+Mbps user experience rates), and deep insights with advanced discovery and optimization.

[0057] 5G NR devices, networks, and systems can utilize optimized OFDM-based waveform characteristics. These characteristics can include: scalable parameter design and transmission time intervals (TTI); a shared, flexible framework for efficiently multiplexing services and features using dynamic, low-latency Time Division Duplex (TDD) / Frequency Division Duplex (FDD) designs; and advanced radio technologies such as massive MIMO, robust millimeter-wave (mmWave) transmission, advanced channel coding, and device-centric mobility. The scalability of parameter design in 5G NR (and the scaling of subcarrier spacing) can efficiently address the operation of diverse services across diverse spectrum and deployments. For example, in various outdoor and macro coverage deployments implemented with FDD / TDD below 3 GHz, subcarrier spacing can occur at 15 kHz over bandwidths such as 1, 5, 10, and 20 MHz. For other various outdoor and small-cell coverage deployments with TDD above 3 GHz, subcarrier spacing can occur at 30 kHz over an 80 / 100 MHz bandwidth. For various other indoor broadband implementations, by using TDD in the unlicensed portion of the 5 GHz band, the subcarrier spacing can occur at 60 kHz over a 160 MHz bandwidth. Finally, for various deployments transmitting mmWave components under TDD at 28 GHz, the subcarrier spacing can occur at 120 kHz over a 500 MHz bandwidth.

[0058] 5G NR's scalable parameter design enables scalable TTIs to meet various latency and Quality of Service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs allows transmissions to begin at symbol boundaries. 5G NR also envisions a self-contained integrated subframe design that incorporates uplink / downlink scheduling information, data, and acknowledgments within the same subframe. Self-contained integrated subframes support communication in unlicensed or contention-based shared spectrum and support adaptive uplink / downlink that can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current traffic needs.

[0059] For clarity, aspects of the devices and technologies may be described below with reference to example 5G NR implementations or in a 5G-centric manner, and 5G terminology may be used in various sections of the following description as illustrative examples; however, this description is not intended to be limited to 5G applications.

[0060] Furthermore, it should be understood that in operation, wireless communication networks adapted according to the concepts herein can be operated using any combination of licensed or unlicensed spectrum, depending on load and availability. Accordingly, it will be apparent to those skilled in the art that the systems, apparatuses, and methods described herein can be applied to other communication systems and applications different from the specific examples provided.

[0061] While aspects and implementations are described herein by way of example, those skilled in the art will understand that additional implementations and use cases may arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, embodiments and / or uses may arise via integrated chip embodiments and / or other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to particular use cases or applications, broad applicability of the described innovations is possible. Implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or OEM devices or systems incorporating one or more of the described aspects. In some practical contexts, devices incorporating the described aspects and features may also necessarily include additional components and features for implementing and practicing the claimed and described embodiments. The innovations described in this paper are intended to be implemented in a wide variety of ways, including both large and small devices of different sizes, shapes and configurations, chip-level components, multi-component systems (e.g., RF chains, communication interfaces, processors), distributed deployments, end-user devices, and so on.

[0062] Figure 1 This is a block diagram illustrating the details of an example wireless communication system. The wireless communication system may include a wireless network 100. Wireless network 100 may, for example, include a 5G wireless network. As those skilled in the art will appreciate, Figure 1 The components appearing in this network likely have corresponding parts in other network deployments (including, for example, cellular network deployments and non-cellular network deployments (e.g., device-to-device, peer-to-peer, or self-organizing network deployments, etc.)).

[0063] Figure 1 The wireless network 100 described herein includes several base stations 105 and other network entities. A base station can be a station communicating with a UE and may also be referred to as an evolved B-node (eNB), a next-generation eNB (gNB), an access point, etc. Each base station 105 can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" can refer to such a specific geographic coverage area of ​​a base station and / or a base station subsystem serving that coverage area, depending on the context in which the term is used. In the implementation of the wireless network 100 herein, base stations 105 may be associated with the same operator or different operators (e.g., the wireless network 100 may include multiple operator wireless networks). Additionally, in the implementation of the wireless network 100 herein, base stations 105 may use one or more frequencies (e.g., licensed spectrum, unlicensed spectrum, or one or more bands of a combination thereof) from the same frequencies as adjacent cells to provide wireless communication. In some examples, an individual base station 105 or UE 115 may be operated by more than one network operating entity. In some other examples, each base station 105 and UE 115 may be operated by a single network operating entity.

[0064] Base stations can provide communication coverage for macrocells or small cells (such as picocells or femtocells), and / or other types of cells. Macrocells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access by UEs with service subscriptions to a network provider. Small cells (such as picocells) typically cover a relatively small geographic area and allow unrestricted access by UEs with service subscriptions to a network provider. Small cells (such as femtocells) also typically cover a relatively small geographic area (e.g., a residential area) and, in addition to unrestricted access, allow restricted access by UEs associated with that femtocell (e.g., UEs in a closed subscriber group (CSG), UEs of users in that residence, etc.). A base station for a macrocell may be referred to as a macro base station. A base station for a small cell may be referred to as a small cell base station, pico base station, femtocell, or home base station. Figure 1In the example shown, base stations 105d and 105e are conventional macro base stations, while base stations 105a-105c are macro base stations enabled with one of 3D, full-dimensional (FD), or massive MIMO enabled. Base stations 105a-105c utilize their higher-dimensional MIMO capabilities to increase coverage and capacity using 3D beamforming in both elevation and azimuth beamforming. Base station 105f is a small cell base station, which can be a home node or a portable access point. A base station can support one or more (e.g., two, three, four, etc.) cells.

[0065] Wireless Network 100 can support synchronous or asynchronous operation. For synchronous operation, each base station can have similar frame timing, and transmissions from different base stations can be roughly aligned in time. For asynchronous operation, each base station can have different frame timing, and transmissions from different base stations can be misaligned in time. In some scenarios, the network can be implemented or configured to handle dynamic switching between synchronous and asynchronous operation.

[0066] UE 115 is distributed across wireless network 100, and each UE can be stationary or mobile. It should be understood that although mobile devices are generally referred to as User Equipment (UE) in standards and specifications issued by 3GPP, such devices may also be referred to by those skilled in the art as mobile station (MS), subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal (AT), mobile terminal, radio terminal, remote terminal, handheld device, terminal, user agent, mobile client, client, gaming device, augmented reality device, vehicle component device / module, or any other suitable term. Within this document, a “mobile” device or UE does not necessarily have mobility capabilities and may be stationary. Some non-limiting examples of mobile devices may include implementations of one or more of the various UEs 115, including mobile stations, cellular phones, smartphones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablets, and personal digital assistants (PDAs). Mobile devices can also be “Internet of Things” (IoT) or “Internet of Everything” (IoE) devices, such as automobiles or other transportation vehicles, satellite radios, Global Positioning System (GPS) devices, logistics controllers, drones, multi-rotor aircraft, quadcopters, smart energy or security devices, solar panels or solar arrays, urban lighting, water supply or other infrastructure; industrial automation and enterprise equipment; consumer and wearable devices, such as glasses, wearable cameras, smartwatches, health or fitness trackers, mammalian implantable devices, posture tracking devices, medical devices, digital audio players (e.g., MP3 players), cameras, game consoles, etc.; and digital home or smart home devices, such as home audio, video and multimedia equipment, appliances, sensors, vending machines, smart lighting, home security systems, smart meters, etc. In one aspect, a UE can be a device that includes a Universal Integrated Circuit Card (UICC). In another aspect, a UE can be a device that does not include a UICC. In some aspects, a UE that does not include a UICC can also be referred to as an IoE device. Figure 1 The UEs 115a-115d described in the text are examples of mobile smartphone-type devices accessing the wireless network 100. The UE can also be a machine specifically configured for connected communications (including machine-type communication (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), etc.). Figure 1 The UE 115e-115k described in the text is an example of various machines configured for accessing communications on the wireless network 100.

[0067] Mobile devices (such as UE 115) can communicate with any type of base station (whether macro base station, pico base station, femto base station, relay, etc.). Figure 1 In this context, a communication link (represented as a lightning bolt) indicates radio transmissions between the UE and a serving base station (a serving base station is a base station designated to serve the UE on the downlink and / or uplink), or desired transmissions between base stations, and backhaul transmissions between base stations. In some scenarios, the UE may operate as a base station or other network node. Backhaul communication between base stations of the wireless network 100 can occur using wired and / or wireless communication links.

[0068] In the operation of wireless network 100, base stations 105a-105c use 3D beamforming and coordinated spatial technologies (such as Coordinated Multipoint (CoMP) or multi-connectivity) to serve UEs 115a and 115b. Macro base station 105d performs backhaul communication with base stations 105a-105c and small cell base station 105f. Macro base station 105d also transmits multicast services subscribed to and received by UEs 115c and 115d. Such multicast services may include mobile television or streaming video, or may include other services for providing community information (such as weather emergencies or alerts, such as Amber Alerts or Grey Alerts).

[0069] The implementation of wireless network 100 supports mission-critical communication with highly reliable and redundant links for mission-critical equipment such as UE 115e, which is a drone. Redundant communication links with UE 115e include those from macro base stations 105d and 105e, and small cell base station 105f. Other machine-type devices (such as UE 115f (thermometer), UE 115g (smart meter), and UE 115h (wearable device)) can communicate directly with base stations (such as small cell base station 105f and macro base station 105e) via wireless network 100, or in a multi-hop configuration via wireless network 100 by communicating with another user equipment relaying its information to the network (e.g., UE 115f relays temperature measurement information to smart meter UE 115g, which is then reported to the network via small cell base station 105f). Wireless network 100 can also provide additional network efficiency through dynamic, low-latency TDD / FDD communication, such as in vehicle-to-vehicle (V2V) mesh networks between UEs 115i-115k communicating with macro base station 105e.

[0070] Figure 2 A block diagram illustrating a conceptual design of base station 105 and UE 115 is shown. Base station 105 and UE 115 can be... Figure 1Any one of the base stations and one of the UEs. For restricted association scenarios (as mentioned above), base station 105 can be... Figure 1 In the small cell base station 105f, UE 115 can be UE 115c or 115D operating within the service area of ​​base station 105f. To access small cell base station 105f, UE 115 will be included in the list of accessible UEs of small cell base station 105f. Base station 105 can also be some other type of base station. Figure 2 As shown, base station 105 may be equipped with antennas 234a to 234t, and UE 115 may be equipped with antennas 252a to 252r for facilitating wireless communication.

[0071] At base station 105, transmit processor 220 can receive data from data source 212 and control information from controller / processor 240. The control information can be used for Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid ARQ (Automatic Repeat Request) Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), Enhanced Physical Downlink Control Channel (EPDCCH), MTC Physical Downlink Control Channel (MPDCCH), etc. Data can be used for PDSCH, etc. Additionally, transmit processor 220 can process (e.g., encode and map symbol) data and control information to obtain data symbols and control symbols respectively. Transmit processor 220 can also generate reference symbols, for example, for primary synchronization signal (PSS) and secondary synchronization signal (SSS), and reference signals that vary depending on the cell. The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, and / or reference symbols where applicable, and can provide the output symbol stream to modulators (MODs) 232a to 232t. For example, spatial processing performed on data symbols, control symbols, or reference symbols may include precoding. Each modulator 232 can process its respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 can additionally or alternatively process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signal from modulators 232a to 232t can be transmitted via antennas 234a to 234t, respectively.

[0072] At UE 115, antennas 252a to 252r can receive downlink signals from base station 105 and can respectively provide the received signals to demodulators (DEMODs) 254a to 254r. Each demodulator 254 can condition (e.g., filter, amplify, downconvert, and digitize) its respective received signal to obtain an input sample. Each demodulator 254 can further process the input sample (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 256 can obtain the received symbols from demodulators 254a to 254r, perform MIMO detection on these received symbols where applicable, and provide detected symbols. Receiver processor 258 can process (e.g., demodulate, deinterleave, and decode) these detected symbols, provide the decoded data to UE 115 to data sink 260, and provide the decoded control information to controller / processor 280.

[0073] On the uplink, at UE 115, transmit processor 264 can receive and process data from data source 262 (e.g., data for the Physical Uplink Shared Channel (PUSCH)) and control information from controller / processor 280 (e.g., control information for the Physical Uplink Control Channel (PUCCH)). Additionally, transmit processor 264 can also generate reference symbols for reference signals. Symbols from transmit processor 264 can be pre-encoded by TX MIMO processor 266, further processed by modulators 254a to 254r (e.g., for SC-FDM, etc.), and transmitted to base station 105, where applicable. At base station 105, uplink signals from UE 115 can be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236, and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 115. Processor 238 can provide decoded data to data trap 239 and decoded control information to controller / processor 240.

[0074] Controllers / processors 240 and 280 can respectively direct operations at base station 105 and UE 115. Controllers / processors 240 and / or other processors and modules at base station 105 and / or controllers / processors 280 and / or other processors and modules at UE 115 can perform or direct the execution of various processes used in the techniques described herein, such as performing or directing... Figure 9 and Figure 10 The execution and / or other processes used in the techniques described herein are as explained herein. Memory 242 and 282 may store data and program code for base station 105 and UE 115, respectively. Scheduler 244 may schedule the UE for data transmission on downlink and / or uplink.

[0075] Wireless communication systems operated by different network operating entities (e.g., network operators) can share spectrum. In some instances, one network operating entity may be configured to use an entire designated shared spectrum for at least one time period, after which another network operating entity uses the same entire designated shared spectrum for a different time period. Thus, in order to allow network operating entities to use the entire designated shared spectrum and to mitigate interference communications between different network operating entities, specific resources (e.g., time) can be allocated and distributed to different network operating entities for specific types of communication.

[0076] For example, specific time resources can be allocated to a network operating entity, reserved for its exclusive use of the entire shared spectrum for communication. Additional time resources can also be allocated to a network operating entity, giving it priority over other network operating entities for communication within the shared spectrum. These time resources, preferentially allocated to the network operating entity, can be utilized by other network operating entities on a wait-and-see basis if the prioritized entity does not utilize them. Additional time resources can be allocated to any network operator for use on a wait-and-see basis.

[0077] Spectrum access control can be accomplished in several ways. In some deployments, for example, access to shared spectrum and arbitration of time resources among different network operating entities can be centrally controlled. Centralized control can be performed by a single entity (e.g., a scheduling entity, base station, etc.). In some deployments, spectrum control can be autonomously determined by a predefined arbitration scheme. In other arrangements or deployments (alternatively or additionally), spectrum control can be dynamically determined based on interactions between the network operator's radio nodes.

[0078] In some scenarios, UE 115 and base station 105 may operate in a shared radio spectrum band. Some shared bands may include licensed or unlicensed (e.g., contention-based) spectrum. In the unlicensed frequency portion of a shared radio spectrum band, UE 115 or base station 105 may conventionally perform media sensing procedures to contend for access to the spectrum. For example, UE 115 or base station 105 may perform Listen-Before-Speak or Listen-Before-Transmit (LBT) procedures (such as Open Channel Assessment (CCA)) before communication to determine whether a shared channel is available. In some implementations, CCA may include energy detection procedures to determine whether any other active transmissions exist. For example, the device may infer that a change in the Received Signal Strength Indicator (RSSI) of the power meter indicates that the channel is occupied. Specifically, signal power concentrated in a specific bandwidth and exceeding a predetermined noise floor may indicate another wireless transmitter. CCA may also include the detection of a specific sequence indicating channel usage. For example, another device may transmit a specific preamble before transmitting a data sequence. In some cases, LBT procedures may include radio nodes acting as collision-proxies adjusting their own backoff windows based on the amount of energy detected on the channel and / or ACK / NACK feedback on their own transmitted packets.

[0079] Figure 3A , 3B The example of full-duplex communication mode was explained with 3C. Figure 3A The diagram illustrates the operation of a full-duplex base station and a half-duplex UE. Figure 3B The diagram illustrates the operation of a full-duplex base station and a full-duplex UE, and... Figure 3C The diagram illustrates the operation of a full-duplex UE with multiple transmit / receive points (TRPs). In some deployments, full-duplex operation typically corresponds to transmitting and / or receiving data simultaneously or substantially simultaneously via multiple antennas. In some instances, half-duplex operation typically corresponds to transmitting or receiving data via a single antenna at a specific time.

[0080] Figure 3A , 3B The 3C standard describes interference caused by full-duplex operation. For clarity, external interference and self-interference can occur during full-duplex operation. External interference is caused by external sources (such as nearby UEs or base stations). Self-interference is caused by the device itself. Self-interference can be caused by leakage, such as when transmitted energy from the transmitting antenna is received directly or indirectly (e.g., by reflection) by the receiving antenna.

[0081] exist Figure 3A , 3B In 3C, multiple TRPs are explained, such as the first TRP (TRP1) and the second TRP (TRP2). The first and second TRPs may include or correspond to the same base station (such as the same gNB) or different base stations. Figure 3A, 3B In 3C, the first TRP (TRP1) can operate in the same frequency band or in a different frequency band. For example, the first TRP (TRP1) can operate in a first frequency band (such as FR4 or 60GHz), and the second TRP (TRP2) can operate in a second frequency band (such as FR2 or 28GHz).

[0082] Additionally, Figure 3A , 3B The 3C documentation describes multiple UEs, such as the first UE (UE1) and the second UE (UE2). In some implementations, a UE is a full-duplex UE with one or more antenna modules. Figure 3A , 3B 3C further describes the signal paths between each TRP and each UE.

[0083] Reference Figure 3A , Figure 3A Example diagram 300 for the first type of full-duplex communication is illustrated. (Refer to...) Figure 3A Figure 300 illustrates the two signal paths (beam paths) between the TRP and the UE and example interference. Figure 3A In the example described, the first TRP (TRP1) transmits downlink data to the first UE (UE1) via a first signaling path, and the first TRP (TRP2) receives uplink data from the second UE (UE2) via a second signaling path. Both the first TRP and the UE are subject to interference. For example, the first TRP is subject to self-interference from simultaneous transmission and reception. Additionally, the devices receive interference caused by other nearby devices. For example, the operation of the second TRP 2 may cause interference from all other nodes (such as...). Figure 3A The interference at the first UE and the first TRP (explained in the text) is also mentioned. Additionally, the transmission of uplink data by the second UE can cause interference at the second TRP.

[0084] Reference Figure 3B , Figure 3B Example diagram 310 illustrates the use of the second type of full-duplex communication. (Refer to...) Figure 3B Figure 310 illustrates the two signal paths (beam paths) between the TRP and the UE and an example of interference. Figure 3BIn the example described, the first TRP (TRP1) transmits downlink data to the first UE (UE1) via a first signaling path, and the first TRP (TRP1) receives uplink data from the first UE (UE1) via a second signaling path. Additionally, the second TRP (TRP2) transmits downlink data to the second UE (UE2) via a third signaling path. The first TRP is subject to interference. For example, the first TRP is subject to self-interference from simultaneous transmission and reception, as well as interference from the operation of the second TRP and the UE. Additionally, other devices may receive interference caused by the operation of other nearby devices, as described in reference [reference needed]. Figure 3A As described.

[0085] Reference Figure 3C , Figure 3C Example diagram 320 illustrates a method for using the third type of full-duplex communication. (Refer to...) Figure 3C Figure 320 illustrates the three signal paths (beam paths) between the TRP and the UE and example interference. Figure 3C In the example described, the first TRP (TRP1) receives uplink data from the first UE (UE1) via a first signaling path, and the first TRP (TRP2) transmits downlink data to the first UE via a second signaling path and to the second UE via a third signaling path. The first TRP is susceptible to interference. For example, the first TRP is susceptible to self-interference from simultaneous transmission and reception. Additionally, other devices may receive interference caused by the operation of other nearby devices, as described in [reference]. Figure 3A As described.

[0086] Figure 3D , 3E 3F explained an example of full-duplex communication operation. Figure 3D and 3F The diagram illustrates in-band full-duplex (IBFD) operation, and... Figure 3E The image shows subband full-duplex operation. In some deployments, in-band full-duplex (IBFD) operation corresponds to transmitting and receiving on the same time and frequency resources. For example... Figure 3D and 3E As shown in Figures 330 and 340, downlink and uplink resources share the same time and frequency resources. Downlink and uplink resources may completely or partially overlap, such as... Figure 3D and 3E As shown separately. In some deployments, subband full-duplex operation (often referred to as frequency division duplex (FDD) or flexible duplex) corresponds to transmitting and receiving data at the same time but on different frequency resources. For example... Figure 3F As shown in Figure 350, downlink resources and uplink resources are separated by a relatively "thin" guard band (GB). For illustrative purposes, Figure 3F The guard band is amplified. In current wireless standard specifications, the guard band typically distinguishes the SBFD from the paired spectrum (e.g., IBFD).

[0087] Cross-division duplex (xDD) is an advanced duplexing scheme in which devices operate on the same Time Division Duplex (TDD) carrier but on different frequency resources, specifically on the Low Length (UL) and Low Length (DL). xDD can enhance uplink (UL) coverage on TDD carriers by utilizing self-interference cancellation (SIC) capabilities at the base station. xDD combines the efficient handling of asymmetric UL and downlink (DL) traffic by TDD with the coverage advantages of Frequency Division Duplex. xDD can be used in conjunction with SBFD or IBD.

[0088] Figure 3G and 3H An example of BWP handover delay was explained. Figure 3G The BWP handover latency table 360 ​​was explained, and... Figure 3H The explanation details the time delay of 370 seconds in timeslots caused by switching the frequency / bandwidth of the DL BWP. (See reference...) Figure 3G The latency caused during BWP handover depends on both time and UE capabilities. To explain, time slot length (in milliseconds) and UE type (Type 1 or Type 2) can be used as a basis... Figure 3G The table determines the delay in timeslots. This delay can also depend on the subcarrier spacing (SCS). As explained, if the subcarrier spacing (SCS) changes, the BWP handover delay is the larger of the two delays for both types of UEs.

[0089] Reference Figure 3H The first DL BWP (DL BWP1) switches to the second DL BWP (DL BWP2). Figure 3H In the example, the bandwidth / frequency range of the DL BWP is reduced. This handover causes a delay in which the wireless communication device does not transmit or receive data. Since this example is for DL, the base station does not transmit DL data and the UE does not receive DL data. Since the BWPs proposed herein include DL BWPs, UL BWPs, and combined BWPs (e.g., DL / UL BWPs), both the UE and the base station will face handover delays and wasted transmission or reception opportunities.

[0090] Figure 4Examples of a wireless communication system 400 supporting joint downlink and uplink bandwidth portion operation for full-duplex wireless communication modes, according to various aspects of this disclosure, are described. In some examples, the wireless communication system 400 may implement various aspects of the wireless communication system 100. For example, the wireless communication system 400 may include a UE 115 and a network entity 405. Joint downlink and uplink bandwidth portion operation for full-duplex wireless communication modes can improve throughput and reliability by increasing flexibility and reducing handover latency. This can thereby improve network and device performance.

[0091] Network entity 405 and UE 115 can be configured to communicate via frequency bands (such as FR1 for millimeter waves, which has frequencies from 410 to 7125 MHz), FR2 (which has frequencies from 24250 to 52600 MHz), and / or one or more other frequency bands). It should be noted that for some data channels, the SCS can be equal to 15, 30, 60, or 120 kHz. Network entity 405 and UE 115 can be configured to communicate via one or more component carriers (CCs) (such as the representative first CC 481, second CC 482, third CC 483, and fourth CC 484). Although four CCs are shown, this is for illustrative purposes only, and more or fewer CCs may be used. One or more CCs can be used to convey control channel transmissions, data channel transmissions, and / or sidelink channel transmissions.

[0092] Such transmissions may include the Physical Downlink Control Channel (PDCCH), Physical Downlink Shared Channel (PDSCH), Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), Physical Sidelink Control Channel (PSCCH), Physical Sidelink Shared Channel (PSSCH), or Physical Sidelink Feedback Channel (PSFCH). These transmissions may be scheduled by aperiodic and / or periodic grants.

[0093] Each periodic permission may have a corresponding configuration, such as configuration parameters / settings. Periodic permission configuration may include configured permission (CG) configurations and settings. Additionally or alternatively, one or more periodic permissions (e.g., their CGs) may have or be assigned a CC ID (such as an expected CC ID).

[0094] Each CC may have a corresponding configuration, such as configuration parameters / settings. This configuration may include bandwidth, bandwidth portion, HARQ procedure, TCI status, RS, control channel resources, data channel resources, or a combination thereof. Additionally or alternatively, one or more CCs may have or be assigned a cell ID, a bandwidth portion (BWP) ID, or both. The cell ID may include a unique cell ID for the CC, a virtual cell ID, or a specific cell ID for a specific CC among multiple CCs. Additionally or alternatively, one or more CCs may have or be assigned a HARQ ID. Each CC may also have corresponding management functionalities, such as beam management, BWP handover functionality, or both. In some implementations, two or more CCs are quasi-coexisting so that these CCs have the same beam and / or the same symbols.

[0095] In some implementations, control information can be communicated via network entity 405 and UE 115. For example, control information can be communicated using MAC-CE transmission, RRC transmission, DCI transmission, another transmission, or a combination thereof.

[0096] UE 115 may include various components (e.g., architecture, hardware components) for performing one or more of the functions described herein. These components may include, for example, a processor 402, a memory 404, a transmitter 410, a receiver 412, an encoder 413, a decoder 414, a duplex manager 415, an RBW manager 416, and antennas 252a-r. Processor 402 may be configured to execute instructions stored in memory 404 to perform the operations described herein. In some implementations, processor 402 includes or corresponds to controller / processor 280, and memory 404 includes or corresponds to memory 282. Memory 404 may also be configured to store trigger condition data 406, BWP configuration data 408, RBW configuration data 442, setting data 444, or combinations thereof, as further described herein.

[0097] Trigger condition data 406 includes or corresponds to data associated with or corresponding to the transmission of trigger condition information. For example, trigger condition data 406 may indicate one or more possible trigger conditions and / or one or more active trigger conditions. Trigger condition data 406 may also include thresholds or data for evaluating trigger conditions, such as a DCI indicator value of 1 corresponding to switching BWP / RBW configurations. Additionally or alternatively, trigger conditions based on desired operating conditions may be static, dynamic, or variable.

[0098] BWP configuration data 408 includes or corresponds to data indicating or corresponding to a BWP configuration. For example, BWP configuration data 408 may indicate possible BWP configurations and / or active (e.g., currently in use) BWP configurations. In some implementations, BWP configuration data 408 may further indicate whether a particular UL BWP (e.g., its specific UL RBW portion) or generally a UL RBW is configured for RACH procedures, such as whether a RACH configuration is included.

[0099] As mentioned above, a BWP may include one or more RBWs. Since RBWs can be defined in one or more BWPs, the configurations used for RBWs can differ. RBW configurations can be based on one or more RBW configuration parameters, such as RBW configuration data 442. RBW configuration data 442 includes or corresponds to data indicating a portion or sub-BWP resource unit of the BWP, such as the RBW configuration of the BWP. RBW configuration data 442 can be used to indicate a specific active RBW (or master RBW) of an active (e.g., currently used) BWP configuration or a specific configuration that may indicate an RBW. RBW configuration data 442 may further include possible RBW configurations for possible BWP configurations indicated by BWP configuration data 408. RBW configuration data 442 may further include one or more of the following: RBW default settings, RBW timer settings, UL and DL association settings, etc.

[0100] Configuration data 444 includes or corresponds to data associated with joint BWP operation. Configuration data 444 may include one or more types of joint BWP operation modes and / or thresholds or conditions for switching BWP modes and / or configuration. For example, configuration data 444 may have data indicating different thresholds for different full-duplex modes (such as IBFD and SBFD modes).

[0101] Transmitter 410 is configured to transmit data to one or more other devices, and receiver 412 is configured to receive data from one or more other devices. For example, transmitter 410 may transmit data, and receiver 412 may receive data via a network (such as a wired network, a wireless network, or a combination thereof). For example, UE 115 may be configured to transmit and / or receive data via a direct device-to-device connection, a local area network (LAN), a wide area network (WAN), a modem-to-modem connection, the Internet, an intranet, an extranet, a cable transmission system, a cellular communication network, any combination thereof, or any other communication network now known or developed hereafter that allows communication between two or more electronic devices. In some implementations, transmitter 410 and receiver 412 may be replaced by a transceiver. Additionally or alternatively, transmitter 410, receiver 412, or both may include or correspond to references. Figure 2One or more components of the described UE 115.

[0102] Encoder 413 and decoder 414 can be configured to encode and decode data for transmission. Duplex manager 415 can be configured to determine and perform full-duplex mode management and operation. For example, duplex manager 415 is configured to control and coordinate full-band duplex operation. RBW manager 416 can be configured to determine specific RBW configurations. For example, RBW manager 416 is configured to determine and / or select BWP and / or RBW configurations.

[0103] Network entity 405 includes a processor 430, a memory 432, a transmitter 434, a receiver 436, an encoder 437, a decoder 438, a duplex manager 439, an RBW manager 440, and an antenna 234a-t. Processor 430 may be configured to execute instructions stored in memory 432 to perform the operations described herein. In some implementations, processor 430 includes or corresponds to controller / processor 240, and memory 432 includes or corresponds to memory 242. Memory 432 may be configured to store trigger condition data 406, BWP configuration data 408, RBW configuration data 442, setting data 444, or combinations thereof, similar to UE 115 and further described herein.

[0104] Transmitter 434 is configured to transmit data to one or more other devices, and receiver 436 is configured to receive data from one or more other devices. For example, transmitter 434 may transmit data, and receiver 436 may receive data via a network (such as a wired network, a wireless network, or a combination thereof). For example, network entity 405 may be configured to transmit and / or receive data via a direct device-to-device connection, a local area network (LAN), a wide area network (WAN), a modem-to-modem connection, the Internet, an intranet, an extranet, a cable transmission system, a cellular communication network, any combination thereof, or any other communication network now known or developed hereafter that allows communication between two or more electronic devices. In some implementations, transmitter 434 and receiver 436 may be replaced by a transceiver. Additionally or alternatively, transmitter 434, receiver 436, or both may include or correspond to references. Figure 2 One or more components of the network entity 405 described.

[0105] Encoder 437 and decoder 438 may include the same functionality as described with reference to encoder 413 and decoder 414, respectively. Duplex manager 439 may include similar functionality as described with reference to duplex manager 415. RBW manager 440 may include similar functionality as described with reference to RBW manager 416.

[0106] During operation of the wireless communication system 400, network entity 405 may determine that UE 115 has joint BWP capability and thereby determine RBW configuration / handover. For example, UE 115 may transmit message 448 including a joint BWP operation indicator 490 (e.g., an RBW configuration indicator). Indicator 490 may indicate joint BWP operation capability or a specific type or mode of joint BWP operation. In some implementations, network entity 405 sends control information to instruct UE 115 to use joint BWP operation and / or a specific type of joint BWP operation. For example, in some implementations, message 448 (or another message, such as configuration transmission 450) is transmitted by network entity 405. Configuration transmission 450 may include or indicate joint BWP operation or adjust or implement settings for a specific type of joint BWP operation.

[0107] During operation, the device of the wireless communication system 400 performs joint BWP operation. For example, UE 115 determines one or more triggering conditions for initiating an RBW configuration change. Exemplary triggering conditions include DCI indication, timer expiration, RRC indication, etc. UE 115 may evaluate one or more triggering conditions per time slot to determine whether to adjust the RBW configuration. As an example, network entity 405 may transmit a DCI transmission 452 (e.g., a PDCCH transmission) indicating the RBW configuration to UE 115. To explain, DCI transmission 452 may include indicators (e.g., one or more indicator bits indicating a specific RBW configuration for an active BWP in an upcoming time slot). UE 115 may change the RBW configuration for the upcoming time slot. A specific change or adjustment to the RBW configuration may involve a change in the active BWP in some implementations. Alternatively, network entity 405 may transmit a MAC CE transmission 454 indicating the RBW configuration to UE 115. MAC CE transmission 454 may include indicators similar to DCI transmission 452. Details of such dynamic (e.g., DCI- or MAC CE-based) RBW configuration changes are further described in this document.

[0108] As another example, UE 115 may initiate an inactivity timer for the RBW of the current BWP. To illustrate, UE 115 may start an inactivity timer for each RBW of the current BWP when selecting / activating the current BWP. UE 115 may then restart / reset the timers for each RBW when UE 115 selects or uses the corresponding RBW, such as via dynamic signaling (e.g., DCI signaling). Alternatively, UE 115 may start an inactivity timer for each RBW when selecting / using each RBW of the current BWP. In response to the expiration of one or more RBW timers, UE 115 may change the RBW configuration for the upcoming time slot. Specific changes or adjustments to the RBW configuration may involve changes to the active BWP in some implementations. Details of such RBW configuration changes based on the expiration of inactivity timers are described further herein.

[0109] As another example, UE 115 can evaluate and determine whether the current BWP supports RACH procedures. To illustrate, UE 115 can evaluate the UL RBW of the current BWP based on conditions (such as the expiration of a timer (e.g., a RACH configuration verification timer), based on RBW configuration (e.g., RBW selection), etc.) or per time slot when selecting / activating the current BWP. In response to determining that at least one UL RBW is not configured for RACH procedures, UE 115 can change the RBW configuration for an upcoming time slot. Specific changes or adjustments to the RBW configuration may involve changes to the active BWP in some implementations. Details of such RACH configuration-based RBW configuration changes (e.g., MAC elements) are further described herein.

[0110] After evaluating the trigger conditions and determining that a trigger condition exists for changing a specific RBW, UE 115 determines the specific RBW configuration or configuration change. UE 115 can then change / set the RBW of the active BWP, or can switch the BWP itself so that the new active BWP portion has the specific RBW configuration indicated by the evaluation of the trigger conditions. Although described above with reference to UE 115, network entity 105 similarly evaluates the trigger conditions and determines the new RBW configuration. Thus, UE 115 and network entity 405 determine RBW configuration data 442 based on the trigger conditions and BWP configuration data 408.

[0111] Network entity 405 and UE 115 perform data channel transmission 456 for an upcoming time slot according to the RBW configuration indicated by RBW configuration data 442. For example, network entity 405 transmits a DCI for that time slot to schedule UL and DL transmissions for that time slot. This DCI may be the same DCI used to indicate RBW configuration / configuration change (i.e., DCI 452). Alternatively, if the triggering condition is timer-based or MAC element-based, network entity 405 may not transmit a DCI or other transmissions to indicate RBW configuration change, and / or the DCI transmitted by network entity 405 for scheduling may not include an RBW configuration indicator.

[0112] Based on the scheduled UL and DL transmissions indicated by the DCI and the determined RBW configuration, network entity 405 transmits downlink data (e.g., DL symbols) and UE 115 transmits uplink data (UL symbols).

[0113] Accordingly, UE 115 and network entity 405 can transmit and receive information in different RBW configurations in sequential / coherent time slots.

[0114] thus, Figure 4 Enhanced BWP configuration and operation for full-duplex operation are described. Improvements can be achieved when operating in full-duplex mode using a combined BWP and trigger-based RBW configuration. Performing combined BWP and trigger-based RBW configuration operations results in reduced bandwidth / spectrum waste during handover, and thereby enhanced UE and network performance through increased throughput and reduced latency.

[0115] The combined BWP described herein can be a UL and DL BWP having both UL and DL RBWs. RBWs may include a set of RBWs configured only for DL ​​and a set of RBWs configured only for UL, or a set of RBWs that can be configured with four or more DL / UL BWPs. DL-only RBWs and UL-only RBWs (i.e., separate RBWs) may be particularly useful for SBFD, and the flexibility of configurable / combined RBWs (i.e., RBWs that can be configured for UL or DL) may be particularly useful for IBDFD.

[0116] A combined BWP may include multiple RBWs, such as eight RBWs in an illustrative, non-limiting example. Thus, in such an example with eight RBWs, the combined BWP may include four DL RBWs and four UL RBWs, or six DL RBWs and two UL RBWs. Alternatively, the combined BWP may include eight UL / DL RBWs, or four UL / DL RBWs, four DL RBWs, and four UL RBWs.

[0117] When using both UL RBW and DL RBW only, the RBWs of the combined BWP can have separate IDs or the same ID. For example, DL RBW1, DL RBW2, and UL RBW1 and UP RBW2, or RBW1-RBW4, where 1 and 2 are DL and 3 and 4 are uplinks. Separate IDs can resemble the BWP identifier used in FDD, and the same ID can resemble the BWP in TDD.

[0118] The RBW configuration of the bandwidth portion can be switched due to one or more trigger conditions. Trigger conditions may include DCI indication, inactivity timer, MAC-CE, or a combination thereof. Thus, the RBW configuration of the bandwidth portion BWP can be switched dynamically (DCI), based on previous use (timer), based on MAC configuration, and / or statically / semi-statically (RRC).

[0119] Regarding dynamic handover, upon receiving DL scheduling or UL approval, the UE determines the BWP and resource BW from the scheduling DCI. For example, the DCI may include an indicator (e.g., one or more indicator bits) that identifies the RBW configuration.

[0120] Although the following explanation pertains to DL scheduling, similar operations apply to UL granting. In the DL scheduling scenario, the UL RBW undergoes different events when a DL RBW is switched. For example, the UL RBW may remain the same (unchanged). As another example, the UL RBW changes based on some association between the DL RBW and the UL RBW. This UL RBW change association can be predefined or configurable, such as RRC configuration. To illustrate, if DL RBW1 is active, this implies that UL RBW1 must be active. Thus, when switching from another DL RBW to DL RBW1, the UL switches to UL RBW1 (or remains on UL RBW1).

[0121] Similarly, in UL scheduling scenarios, when a UL BWP is switched, the UE determines the new BWP and resource BW based on the scheduling DCI. For example, the DL RBW may remain the same (unchanged). As another example, the DL RBW changes based on some association between the DL RBW and the UL RBW. As mentioned above, the DL RBW change association can be predefined or configurable, such as RRC configuration. To explain, if UL RBW1 is active, this implies that DL RBW1 must be active. Thus, when switching from another UL RBW to UL RBW1, the DL RBW switches to DL RBW1 (or remains on DL RBW1).

[0122] Regarding inactivity timer switching, one or more RBWs in the BWP section may have corresponding inactivity timers. Such RBW inactivity timers can be used, as well as regular inactivity timers for the BWP.

[0123] In some implementations of RBWs with inactivity timers, if an RBW timer is missing in a particular RBW, the UE may not switch back to the default RBW via any timer (such as the RBW inactivity timer, the BWP inactivity timer, or a combination thereof). This can be useful in situations where the gNB wants to configure timers for the DL resource BW instead of the UL resource BW.

[0124] Additionally, an inactivity timer for the BWP can be defined or not. When the inactivity timer for the BWP expires, the UE can switch the entire BWP to a new (configuration default) DL / UL BWP with resource BWPs for both DL and UL. Alternatively, the UE can switch to separate default DL BWPs and default UL BWPs.

[0125] Regarding MAC entity handover, the UE may determine whether to handover at least some BWPs based on RACH capabilities. For example, since the RACH procedure is not configured for active resource BW or BWP, the UE may handover UL resource BW or UL BWP.

[0126] For a given BWP, at least one UL resource BW should have a RACH configuration. If, for a given DL / UL BWP, no resource BW includes a RACH configuration, the UE can switch the joint BWP to the default UL BWP that includes a RACH configuration. The DL configuration remains unchanged depending on the joint BWP.

[0127] Alternatively, the UE can switch the joint BWP to the default joint BWP with a resource BW that includes RACH configuration, or switch the joint BWP to the default UL BWP and the default DL BWP.

[0128] Figures 5-7 This is a diagram illustrating an example of the active bandwidth portion (BWP) of a resource bandwidth (RBW) according to some embodiments of this disclosure. Figure 5 The example BWP layout is explained, where frequency is the horizontal axis (x-axis) and time is the vertical axis (y-axis). Figure 5 In this configuration, the BWP has four RBWs. These four RBWs can be allocated for UL or DL. The base station disclosed herein can be dynamically and flexibly configured. Figure 5 BWP, such as Figure 6 and 7 As explained in the text.

[0129] Reference Figure 6 The example BWP600, comprising a DL RBW section and an uplink BWP section, is explained. The DL RBW section includes two (2) RBWs, and the UL RBW section includes three (3) RBWs. The first DL RBW1 is the active DL RBW, and the fifth RBW (the third UL RBW) is the active UL RBW. Figure 6 In this context, RBWs are numbered sequentially.

[0130] Reference Figure 7 Another example BWP700, comprising a DL RBW section and an uplink BWP section, is explained. The DL RBW section includes two (2) RBWs, and the UL RBW section includes three (3) RBWs, similar to... Figure 6 However, in Figure 7 In this design, UL and DLRBW are numbered respectively, namely, first DL RBW1 and first UL RBW1. Additionally, second DL RBW2 is now an active DL RBW, and second UL RBW2 is an active UL RBW.

[0131] For reference Figure 4 As described, a network entity (e.g., a base station) may indicate a change to the active BWP (e.g., its active RBW) by sending a DCI or an RRC message. Alternatively, a UE may determine to change the active BWP (e.g., its active RBW) in response to determining that a previous active UL RBW (e.g., RBW5 / UL RBW3) does not contain a RACH configuration.

[0132] Additionally, the UE may determine to change the active BWP (e.g., its active RBW) in response to the expiration of an inactivity timer. For example, the UE may determine to change the active UL RBW from the active RBW in response to determining that the inactivity timer associated with RBW 5 / UL RBW3 has expired. Figure 6 Switching from RBW 5 / UL RBW3 to... Figure 7 The active RBW is UL RBW 2. To illustrate, if the UE does not use RBW 5 / UL RBW3 for X time slots, the active RBW is changed. As another example, in response to determining that the inactivity timer associated with RBW 1 / DL RBW1 has expired, the UE switches the active RBW to the default DL RBW. To illustrate, if the UE does not use RBW1 / DL RBW1 for X time slots, the UE switches the active RBW to the default active DL RBW, such as DL RBW2.

[0133] Alternatively, the UE may determine whether to switch a portion of the BWP (e.g., the DL RBW portion or the UL RBW portion) or the entire BWP based on the expiration of the RBW inactivity timer. To illustrate, the UE may determine to switch to either of the two inactivity timers used for the UL and DL RBWs. Figure 8 The BWP configuration. The UE can additionally or alternatively switch the BWP configuration based on the expiration of the BWP inactivity timer.

[0134] In any of the examples above, switching the active RBW of one type (e.g., UL or DL) affects the active RBW of another type (e.g., the other of UL or DL). For illustration, in response to determining that an active DL RBW should be switched to DL RBW2, the UE may determine, based on an association table, that a UL RBW should be switched to the corresponding / associated RBW, such as UL RBW2.

[0135] Reference Figure 8 The example BWP 800 includes the UL / DL RBW section. The UL and DL RBW sections are separate from the explanation. Figure 6 and 7 compared to, Figure 8 The example BWP has a UL / DL RBW section comprising four (4) DL / UL RBWs. The DL / UL RBWs can be configured for downlink or uplink, such as via DCI, timers, RRC, MAC elements, etc. Figure 7 In this context, RBWs are numbered sequentially, similar to... Figure 6 .

[0136] Figure 9 This is a flowchart illustrating example blocks performed by a UE configured according to one aspect of this disclosure. Each example block will also be referenced as follows: Figure 11 It is described in UE 115 as explained in the document. Figure 11 This is a block diagram illustrating a UE115 configured according to one aspect of this disclosure. UE115 includes features such as those for... Figure 2 The structure, hardware, and components described in UE 115. For example, UE 115 includes a controller / processor 280, which operates to execute logical or computer instructions stored in memory 282, and various components that control UE 115 and provide the features and functionality of UE 115. Under the control of controller / processor 280, UE 115 transmits and receives signals via wireless radio 1100a-r and antenna 252a-r. Wireless radio 1100a-r includes various components and hardware, such as... Figure 2The components described for UE 115 include demodulator / modulator 254a-r, MIMO detector 256, receiver processor 258, transmitter processor 264, and TX MIMO processor 266. For example... Figure 11 As explained in the example, memory 282 stores full-duplex logic 1102, BWP logic 1103, RBW logic 1104, trigger condition data 1105, BWP configuration data 1106, RBW configuration data 1107, timer 1108, and setting data 1109.

[0137] In box 900, a wireless communication device (such as a UE) operates within a first time slot according to a first BWP configuration, which has a first RBW configuration. For example, UR 115 communicates (e.g., transmits and / or receives data) according to a specific active BWP, as shown in reference. Figures 4-8 As described.

[0138] In box 901, UE 115 determines the BWP handover trigger and RBW configuration. For example, UE 115 determines whether to switch to the active BWP configuration based on DCI transmission, RRC transmission, inactivity timer expiration, or MAC elements (e.g., RACH protocol configuration conditions), as referenced. Figures 4-8 As described. To explain, UE 115 may receive a DCI that includes an indication of a specific RBW configuration. As another explanation, UE 115 may evaluate the current BWP configuration and / or timers and determine the specific RBW configuration used for that BWP.

[0139] In box 902, UE 115 determines a second RBW configuration for the second time slot based on the BWP handover trigger and the RBW configuration, the second RBW configuration being different from the first RBW configuration. For example, UE 115 determines that the current RBW configuration is different from the indicated RBW configuration and UE 115 determines to switch the RBW configuration, as shown in reference... Figures 4-8 As described.

[0140] In a particular implementation, as a supplement to or replacement of the operations of blocks 901 and 902, UE 115 changes from a first RBW configuration to a second RBW configuration based on BWP handover triggering and RBW configuration information. This change may include adjusting or tuning components of UE 115 to operate according to the second RBW. For example, antenna configurations, antenna assemblies, or filters may be adjusted or tuned to achieve transmission or reception via the second RBW configuration. Additionally, a second adjustment or tuning may be performed for the other of the transmission or reception. That is, UE 115 may adjust the RBW (e.g., two RBWs) for both transmission and reception (e.g., uplink and downlink or sidelink outgoing and incoming).

[0141] In box 903, UE 115 operates according to a second RBW configuration during the second time slot. For example, UE 115 communicates (e.g., transmits and / or receives) data according to the second configuration of a specific active BWP, as referenced. Figures 4-8 As described.

[0142] UE 115 may perform additional boxes in other implementations (or UE 115 may be configured to perform further additional operations). For example, UE 115 may perform one or more of the operations described above. As another example, UE 115 may perform one or more aspects as described below.

[0143] In the first aspect, the BWP handover trigger is based on DCI, inactivity timer, RRC signaling, or MAC entity handover, and operates according to the second RBW configuration during the second time slot, including: the UE transmitting UL data during the active UL RBW; the UE receiving DL data during the active DL RBW; or both.

[0144] In the second aspect, either alone or in combination with one or more of the above aspects, the first BWP configuration is a combined BWP configuration and is configured for both DL and UL.

[0145] In a third aspect, either alone or in combination with one or more of the foregoing aspects, the first BWP configuration has one or more DL RBWs and one or more UL RBWs.

[0146] In the fourth aspect, either alone or in combination with one or more of the above aspects, the first BWP configuration has four or more DL RBWs and four or more UL RBWs.

[0147] In the fifth aspect, the UE operates in SBFD alone or in combination with one or more of the above aspects.

[0148] In the sixth aspect, either alone or in combination with one or more of the foregoing aspects, the first BWP configuration has one or more joint RBWs, which can be configured as DL, UL, or both.

[0149] In the seventh aspect, the UE operates in IBFD alone or in combination with one or more of the above aspects.

[0150] In the eighth aspect, either alone or in combination with one or more of the above aspects, UE 115 configures a specific joint RBW as the downlink based on the RBW configuration table.

[0151] In the ninth aspect, the one or more DL RBWs and the one or more UL RBWs have unique identification numbers, either alone or in combination with one or more of the foregoing aspects.

[0152] In the tenth aspect, individually or in combination with one or more of the foregoing aspects, at least one of the one or more DL RBWs and at least one of the one or more UL RBWs have the same identification number.

[0153] In the eleventh aspect, either alone or in combination with one or more of the foregoing aspects, UE 115 receives DCI transmissions indicating RBW configuration.

[0154] In the twelfth aspect, either alone or in combination with one or more of the foregoing aspects, UE 115 determines BWP changes based on indicators in the DCI.

[0155] In the thirteenth aspect, either alone or in combination with one or more of the foregoing aspects, UE 115 determines the BWP and RBW based on indicators in the DCI.

[0156] In the fourteenth aspect, either alone or in combination with one or more of the foregoing aspects, the indicator corresponds to the indicator bit in the DCI.

[0157] In the fifteenth aspect, either alone or in combination with one or more of the foregoing aspects, UE 115 switches the DL RBW to the second DL RBW based on an indicator in the DCI.

[0158] In the sixteenth aspect, either alone or in combination with one or more of the foregoing aspects, UE 115 maintains UL RBW in response to switching DLRBW to a second DL RBW.

[0159] In the seventeenth aspect, the UL RBW-based indicator in the DCI is maintained, either alone or in combination with one or more of the foregoing aspects.

[0160] In the eighteenth aspect, alone or in combination with one or more of the foregoing aspects, UE 115 switches the UL RBW to the second UL RBW in response to switching the DLRBW to the second DL RBW.

[0161] In the nineteenth aspect, either alone or in combination with one or more of the foregoing aspects, the UE switches the UL RBW to the second UL RBW based on an indicator in the DCI.

[0162] In the twentieth aspect, either alone or in combination with one or more of the foregoing aspects, UE 115 switches the DL BWP to a second DL BWP based on an indicator in the DCI, and determines the DL RBW based on the second DL BWP.

[0163] In the twenty-first aspect, either alone or in combination with one or more of the foregoing aspects, UE 115 switches the UL RBW to the second UL RBW based on an indicator in the DCI.

[0164] In the twenty-second aspect, either alone or in combination with one or more of the foregoing aspects, UE 115 maintains DL RBW in response to switching UL RBW to a second UL RBW.

[0165] In aspect twenty-three, either alone or in combination with one or more of the foregoing aspects, UE 115 maintains DL RBW based on indicators in DCI.

[0166] In the twenty-fourth aspect, either alone or in combination with one or more of the foregoing aspects, UE 115 switches DL RBW to the second DL RBW in response to switching UL RBW to the second UL RBW.

[0167] In the twenty-fifth aspect, either alone or in combination with one or more of the foregoing aspects, UE 115 switches the DL RBW to the second DL RBW based on an indicator in the DCI.

[0168] In the twenty-sixth aspect, either alone or in combination with one or more of the foregoing aspects, UE 115 switches the UL BWP to a second UL BWP based on an indicator in the DCI and determines the UL RBW based on the second UL BWP.

[0169] In the twenty-seventh aspect, either alone or in combination with one or more of the foregoing aspects, UE 115 receives an RRC message indicating an association between DL RBW and UL RBW, the association indicating a handover of the corresponding RBW for UL and DL.

[0170] In aspect twenty-eight, individually or in combination with one or more of the above aspects, each RBW of the BWP has a corresponding inactivity timer.

[0171] In the twenty-ninth aspect, either alone or in combination with one or more of the foregoing aspects, UE 115 determines that a particular RBW does not have a dedicated inactivity timer; and based on the determination that the particular RBW does not have a dedicated inactivity timer, maintains the current RBW configuration of the particular RBW in response to the expiration of another inactivity timer.

[0172] In the thirtieth aspect, either alone or in combination with one or more of the foregoing aspects, UE 115, based on the determination that a particular RBW does not have a dedicated inactivity timer, suppresses the default BWP configuration for switching to that particular RBW in response to the expiration of another inactivity timer.

[0173] In the thirty-first aspect, alone or in combination with one or more of the foregoing aspects, the DL RBW has a dedicated inactive timer, while the UL RBW does not have a dedicated inactive timer.

[0174] In aspect thirty-two, either alone or in combination with one or more of the foregoing aspects, UE 115 switches the entire BWP to a new joint BWP having both RBWs for DL ​​and UL in response to the expiration of the BWP's inactivity timer.

[0175] In aspect thirty-three, either alone or in combination with one or more of the foregoing aspects, UE 115 switches to separate default DL BWP and default UL BWP in response to the expiration of the BWP's inactivity timer.

[0176] In aspect thirty-four, either alone or in combination with one or more of the foregoing aspects, the active UL RBW is configured for RACH protocol or includes RACH configuration.

[0177] In aspect thirty-five, either alone or in combination with one or more of the foregoing aspects, the current BWP is configured for RACH procedures.

[0178] In the thirty-sixth aspect, either alone or in combination with one or more of the foregoing aspects, UE 115 determines that the current combined (DL / UL) BWP is not configured for RACH procedures; and in response to determining that the current combined (DL / UL) BWP is not configured for RACH procedures, UE 115 switches the combined BWP to the default UL BWP that is configured for RACH procedures.

[0179] In aspect thirty-seven, either alone or in combination with one or more of the foregoing aspects, UE 115 maintains the DL configuration of the joint BWP in response to determining that the current joint (DL / UL) BWP is not configured for RACH procedures.

[0180] In aspect thirty-eight, either alone or in combination with one or more of the foregoing aspects, UE 115 determines that the current combined (DL / UL) BWP is not configured for RACH procedures; and in response to determining that the current combined (DL / UL) BWP is not configured for RACH procedures, UE 115 switches the combined BWP to a default combined BWP that has an RBW configured for RACH procedures.

[0181] In aspect thirty-nine, either alone or in combination with one or more of the foregoing aspects, UE 115 determines that the current combined (DL / UL) BWP is not configured for RACH procedures; and in response to determining that the current combined (DL / UL) BWP is not configured for RACH procedures, UE 115 switches the combined BWP to a default UL BWP and a default DL BWP, each of which is configured for RACH procedures.

[0182] In the fortieth aspect, either alone or in combination with one or more of the foregoing aspects, UE 115 transmits a message indicating that the wireless communication device is configured to configure the RBW BWP before determining the BWP handover trigger and RBW configuration.

[0183] In the forty-first aspect, either alone or in combination with one or more of the foregoing aspects, UE 115 receives from the second wireless communication device a configuration message indicating a configurable RBW BWP mode before determining the BWP handover trigger and RBW configuration.

[0184] In aspect 42, either alone or in combination with one or more of the foregoing aspects, a second RBW configuration different from the first RBW configuration corresponds to: different active UL RBWs, different active DL RBWs, different total number of RBWs, different number of UL RBWs, different number of DL RBWs, at least one RBW with different bandwidths, at least one RBW with different time-frequency resource sets, or a combination thereof.

[0185] In aspect 43, UE 115 operates in cross-split duplex (xDD) mode, either alone or in combination with one or more of the above aspects.

[0186] In another aspect, a wireless communication method includes: communicating by a wireless communication device during a first time slot according to a first resource bandwidth (RBW) configuration configured by a bandwidth portion (BWP); changing from the first RBW configuration to a second RBW configuration by the wireless communication device based on a BWP handover trigger and RBW configuration information; and communicating by the wireless communication device during a second time slot according to the second RBW configuration, which is different from the first RBW configuration.

[0187] In an additional aspect, changing from a first RBW configuration to a second RBW configuration, either alone or in combination with one or more of the foregoing aspects, includes: adjusting components to the second RBW configuration by the wireless communication device.

[0188] In an additional aspect, changing from a first RBW configuration to a second RBW configuration, either alone or in combination with one or more of the foregoing aspects, includes: the wireless communication device tuning a component to the second RBW configuration, and the component including a filter or antenna component.

[0189] In an additional aspect, the second RBW configuration is associated with the BWP configuration, either alone or in combination with one or more of the aspects mentioned above. For example, the RBW does not involve changes to the currently active BWP.

[0190] In an additional aspect, the second RBW configuration is associated with the second BWP configuration, either alone or in combination with one or more of the foregoing aspects. For example, an RBW change is based on or associated with a BWP change.

[0191] Accordingly, the UE and base station can perform joint downlink and uplink bandwidth portion operations for full-duplex wireless communication mode, and can switch between resources within the bandwidth portion without causing handover latency. By performing joint downlink and uplink bandwidth portion operations for full-duplex wireless communication mode, throughput and reliability can be improved.

[0192] Figure 10 This is a flowchart illustrating an example block performed by a wireless communication device configured according to another aspect of this disclosure. The example block will also be referenced as follows: Figure 12 The base station 105 (e.g., gNB) described in the text is used for description. Figure 12 This is a block diagram illustrating a base station 105 configured according to one aspect of this disclosure. Base station 105 includes components as described above. Figure 2 The base station 105 is described in the following description: its structure, hardware, and components. For example, base station 105 includes a controller / processor 240, which operates to execute logical or computer instructions stored in memory 242, and various components that control base station 105 and provide the characteristics and functionality of base station 105. Under the control of controller / processor 240, base station 105 transmits and receives signals via wireless radio 1201a-t and antenna 234a-t. Wireless radio 1201a-t includes components such as those described in... Figure 2 The various components and hardware explained for base station 105 include modulator / demodulator 232a-t, MIMO detector 236, receiver processor 238, transmitter processor 220, and TX MIMO processor 230. For example... Figure 12 As illustrated in the example, memory 242 stores full-duplex logic 1202, BWP logic 1203, RBW logic 1204, trigger condition data 1205, BWP configuration data 1206, RBW configuration data 1207, timer 1208, and setting data 1209. One or more of 1202-1209 may include or correspond to one of 1102-1109.

[0193] In block 1000, a wireless communication device (such as a base station) operates according to a first BWP configuration within a first time slot, the first BWP configuration having a first RBW configuration. For example, base station 105 transmits and / or receives data according to a specific active BWP, as shown in reference. Figures 4-8 As described.

[0194] In box 1001, base station 105 determines the BWP handover trigger and RBW configuration. For example, base station 105 determines whether to hand over the active BWP configuration based on DCI transmissions, RRC transmissions, inactivity timer expiration, or MAC elements (e.g., RACH protocol configuration conditions), as referred to Figures 4-8 As described. To explain, base station 105 may transmit a DCI including an indication of a specific RBW configuration. As another explanation, base station 105 may evaluate the current BWP configuration and / or timers and determine the specific RBW configuration for that BWP.

[0195] In block 1002, base station 105 determines a second RBW configuration for the second time slot based on the BWP handover trigger and the RBW configuration, the second RBW configuration being different from the first RBW configuration. For example, base station 105 determines that the current RBW configuration is different from the indicated RBW configuration and base station 105 determines that the RBW configuration needs to be switched, as shown in reference... Figures 4-8 As described.

[0196] In block 1003, base station 105 operates according to the second RBW configuration during the second time slot. For example, base station 105 transmits and / or receives data according to the second configuration of a specific active BWP, as shown in reference. Figures 4-8 As described.

[0197] Base station 105 may perform additional boxes in other implementations (or base station 105 may be configured to perform further additional operations). For example, base station 105 may perform one or more of the operations described above.

[0198] In the first aspect, the BWP handover trigger is based on DCI, inactivity timer, RRC signaling, or MAC entity handover, and operates according to the second RBW configuration during the second time slot, including: receiving UL data by the UE during the active UL RBW; transmitting DL data by the UE during the active DL RBW; or both.

[0199] In the second aspect, either alone or in combination with one or more of the above aspects, the first BWP configuration is a combined BWP configuration and is configured for both DL and UL.

[0200] In a third aspect, either alone or in combination with one or more of the foregoing aspects, the first BWP configuration has one or more DL RBWs and one or more UL RBWs.

[0201] In the fourth aspect, either alone or in combination with one or more of the above aspects, the first BWP configuration has four or more DL RBWs and four or more UL RBWs.

[0202] In the fifth aspect, base station 105 operates in SBFD alone or in combination with one or more of the above aspects.

[0203] In the sixth aspect, either alone or in combination with one or more of the foregoing aspects, the first BWP configuration has one or more joint RBWs, which may be configured as DL, UL, or both.

[0204] In the seventh aspect, base station 105 operates in IBFD alone or in combination with one or more of the above aspects.

[0205] In the eighth aspect, either alone or in combination with one or more of the above aspects, base station 105 configures a specific joint RBW as the downlink based on the RBW configuration table.

[0206] In the ninth aspect, the one or more DL RBWs and the one or more UL RBWs have unique identification numbers, either alone or in combination with one or more of the foregoing aspects.

[0207] In the tenth aspect, individually or in combination with one or more of the foregoing aspects, at least one of the one or more DL RBWs and at least one of the one or more UL RBWs have the same identification number.

[0208] In the eleventh aspect, either alone or in combination with one or more of the above aspects, base station 105 transmits DCI transmission indicating RBW configuration.

[0209] In the twelfth aspect, either alone or in combination with one or more of the above aspects, base station 105 determines BWP changes based on indicators in DCI.

[0210] In the thirteenth aspect, either alone or in combination with one or more of the above aspects, base station 105 determines BWP and RBW based on indicators in DCI.

[0211] In the fourteenth aspect, either alone or in combination with one or more of the foregoing aspects, the indicator corresponds to the indicator bit in the DCI.

[0212] In the fifteenth aspect, either alone or in combination with one or more of the above aspects, base station 105 switches DL RBW to a second DL RBW based on an indicator in DCI.

[0213] In the sixteenth aspect, either alone or in combination with one or more of the above aspects, base station 105 maintains UL RBW in response to switching DLRBW to a second DL RBW.

[0214] In the seventeenth aspect, the UL RBW-based indicator in the DCI is maintained, either alone or in combination with one or more of the foregoing aspects.

[0215] In the eighteenth aspect, alone or in combination with one or more of the above aspects, base station 105 switches UL RBW to the second UL RBW in response to switching DLRBW to the second DL RBW.

[0216] In the nineteenth aspect, either alone or in combination with one or more of the foregoing aspects, the UE switches the UL RBW to the second UL RBW based on an indicator in the DCI.

[0217] In the twentieth aspect, either alone or in combination with one or more of the above aspects, base station 105 switches DL BWP to a second DL BWP based on an indicator in DCI, and determines DL RBW based on the second DL BWP.

[0218] In the twenty-first aspect, either alone or in combination with one or more of the above aspects, base station 105 switches UL RBW to a second UL RBW based on an indicator in DCI.

[0219] In the twenty-second aspect, either alone or in combination with one or more of the above aspects, base station 105 maintains DL RBW in response to switching UL RBW to a second UL RBW.

[0220] In the twenty-third aspect, either alone or in combination with one or more of the above aspects, base station 105 maintains DL RBW based on indicators in DCI.

[0221] In the twenty-fourth aspect, either alone or in combination with one or more of the foregoing aspects, base station 105 switches DL RBW to the second DL RBW in response to switching UL RBW to the second UL RBW.

[0222] In the twenty-fifth aspect, either alone or in combination with one or more of the above aspects, base station 105 switches DL RBW to a second DL RBW based on an indicator in DCI.

[0223] In the twenty-sixth aspect, either alone or in combination with one or more of the above aspects, base station 105 switches the UL BWP to a second UL BWP based on an indicator in the DCI, and determines the UL RBW based on the second UL BWP.

[0224] In the twenty-seventh aspect, either alone or in combination with one or more of the foregoing aspects, base station 105 transmits an RRC message indicating an association between DL RBW and UL RBW, the association indicating a handover of the corresponding RBW for UL and DL.

[0225] In aspect twenty-eight, individually or in combination with one or more of the above aspects, each RBW of the BWP has a corresponding inactivity timer.

[0226] In the twenty-ninth aspect, either alone or in combination with one or more of the above aspects, base station 105 determines that a particular RBW does not have a dedicated inactivity timer; and based on the determination that the particular RBW does not have the dedicated inactivity timer, maintains the current RBW configuration of the particular RBW in response to the expiration of another inactivity timer.

[0227] In the thirtieth aspect, alone or in combination with one or more of the foregoing aspects, base station 105, based on determining that a particular RBW does not have a dedicated inactivity timer, suppresses the default BWP configuration for handover to that particular RBW in response to the expiration of another inactivity timer.

[0228] In the thirty-first aspect, alone or in combination with one or more of the foregoing aspects, the DL RBW has a dedicated inactive timer, while the UL RBW does not have a dedicated inactive timer.

[0229] In the thirty-second aspect, either alone or in combination with one or more of the above aspects, base station 105 switches the entire BWP to a new joint BWP having both RBWs for DL ​​and UL in response to the expiration of the BWP's inactivity timer.

[0230] In aspect thirty-three, either alone or in combination with one or more of the above aspects, base station 105 switches to separate default DL BWP and default UL BWP in response to the expiration of the inactivity timer of BWP.

[0231] In aspect thirty-four, either alone or in combination with one or more of the foregoing aspects, the active UL RBW is configured for RACH protocol or includes RACH configuration.

[0232] In aspect thirty-five, either alone or in combination with one or more of the foregoing aspects, the current BWP is configured for RACH procedures.

[0233] In the thirty-sixth aspect, either alone or in combination with one or more of the foregoing aspects, base station 105 determines that the current combined (DL / UL) BWP is not configured for RACH procedures; and in response to determining that the current combined (DL / UL) BWP is not configured for RACH procedures, base station 105 switches the combined BWP to the default UL BWP configured for RACH procedures.

[0234] In the thirty-seventh aspect, either alone or in combination with one or more of the foregoing aspects, base station 105 maintains the DL configuration of the joint BWP in response to determining that the current joint (DL / UL) BWP is not configured for RACH procedures.

[0235] In the thirty-eighth aspect, alone or in combination with one or more of the above aspects, base station 105 determines that the current combined (DL / UL) BWP is not configured for RACH procedures; and in response to determining that the current combined (DL / UL) BWP is not configured for RACH procedures, base station 105 switches the combined BWP to a default combined BWP with an RBW configured for RACH procedures.

[0236] In the thirty-ninth aspect, either alone or in combination with one or more of the foregoing aspects, base station 105 determines that the current combined (DL / UL) BWP is not configured for RACH procedures; and in response to determining that the current combined (DL / UL) BWP is not configured for RACH procedures, base station 105 switches the combined BWP to a default UL BWP and a default DL BWP, each of which is configured for RACH procedures.

[0237] In the fortieth aspect, alone or in combination with one or more of the foregoing aspects, base station 105 receives a message indicating that the UE is configured to use the configurable RBW BWP before determining the BWP handover trigger and RBW configuration.

[0238] In the forty-first aspect, either alone or in combination with one or more of the foregoing aspects, base station 105 transmits a configuration message indicating a configurable RBW BWP mode before determining BWP handover triggering and RBW configuration.

[0239] In aspect 42, either alone or in combination with one or more of the foregoing aspects, a second RBW configuration different from the first RBW configuration corresponds to: different active UL RBWs, different active DL RBWs, different total number of RBWs, different number of UL RBWs, different number of DL RBWs, at least one RBW with different bandwidths, at least one RBW with different time-frequency resource sets, or a combination thereof.

[0240] In aspect 43, base station 105 operates in cross-split duplex (xDD) mode, either alone or in combination with one or more of the above aspects.

[0241] Accordingly, the UE and base station can perform joint downlink and uplink bandwidth portion operations for full-duplex wireless communication mode, and can switch between resources within the bandwidth portion without causing handover latency. By performing joint downlink and uplink bandwidth portion operations for full-duplex wireless communication mode, throughput and reliability can be improved.

[0242] Figure 13 This is a flowchart illustrating example blocks performed by a wireless communication device (e.g., UE 115 or base station 105) configured according to one aspect of this disclosure. The example blocks will also relate to, for example... Figure 11 The explanation of UE115 and related matters Figure 12 The base station 105 described in the text is used for description.

[0243] In box 1300, the wireless communication device receives first data during a time slot according to a first resource bandwidth (RBW) configuration based on a bandwidth portion (BWP) configuration. The BWP configuration is configured for both uplink and downlink operation. For example, UE 115 or base station 105 receives the first data according to the first RBW of a specific active BWP, as shown in reference... Figures 4-12 As described.

[0244] In block 1301, the wireless communication device transmits second data during the time slot according to a second RBW configuration of the BWP configuration. The second RBW configuration differs from the first RBW configuration. For example, UE 115 or base station 105 transmits second data according to the second RBW (which differs from the first RBW) of a specific active BWP, as shown in reference... Figures 4-12 As described. Specifically, such full-duplex operation or simultaneous transmission and reception in blocks 1300 and 1301 may include or correspond to full-duplex operation as described in blocks 900, 903, 1000, and 1003. For illustration, wireless communication devices may... Figure 9 and 10 The operation is as described in boxes 900, 903, 1000, or 1003 as in boxes 1300 and 1301. Additionally, the wireless communication device can switch the RBW of the BWP or switch the BWP without inducing a handover delay, as described in boxes 901 and 902 or 1001 and 1002. After the handover, the wireless communication device can again operate in full-duplex mode, as described in boxes 900, 903, 1000, 1003, or 1300 and 1301. Example differences between the RBW of the BWP and RBW configuration are shown in [reference]. Figures 5-8 To provide explanations and descriptions.

[0245] In addition, although Figure 13 The example is described with reference to uplink and downlink full-duplex operation, but full-duplex operation may include or may be sidelink communication. That is, in other implementations, uplink transmission may be outgoing sidelink transmission, downlink transmission may be incoming sidelink transmission, or both.

[0246] The wireless communication device may perform additional frames in other implementations (or the wireless communication device may be configured to perform additional operations). For example, the wireless communication device may perform operations such as those described above. Figures 4-12 The operations described herein. As another example, a wireless communication device may perform one or more aspects as described below.

[0247] In the first aspect, the wireless communication device includes user equipment (UE).

[0248] In a second aspect, alone or in combination with one or more of the foregoing aspects, the wireless communication device includes a network device.

[0249] In the third aspect, either alone or in combination with one or more of the above aspects, the BWP configuration is a combined BWP configuration and is configured for both downlink (DL) and uplink (UL).

[0250] In a fourth aspect, either alone or in combination with one or more of the above aspects, the BWP configuration has one or more DL RBWs and one or more UL RBWs, and the wireless communication device operates in subband full-duplex (SBFD).

[0251] In a fifth aspect, either alone or in combination with one or more of the above aspects, the BWP configuration has one or more joint RBWs that can be configured as DL, UL or both, and the wireless communication device operates in in-band full-duplex (IBFD).

[0252] In a sixth aspect, alone or in combination with one or more of the foregoing aspects, the method further includes: configuring a specific joint RBW among the one or more joint RBWs as a downlink by the wireless communication device based on an RBW configuration table.

[0253] In the seventh aspect, either alone or in combination with one or more of the foregoing aspects, the BWP configuration has one or more downlink (DL) RBWs and one or more uplink (UL) RBWs, and the one or more DL RBWs and the one or more UL RBWs have unique identifiers.

[0254] In the eighth aspect, either alone or in combination with one or more of the foregoing aspects, the BWP configuration has one or more downlink (DL) RBWs and one or more uplink (UL) RBWs, and at least one of the one or more DL RBWs and at least one of the one or more UL RBWs have the same identification number.

[0255] In the ninth aspect, either alone or in combination with one or more of the foregoing aspects, a second RBW configuration different from the first RBW configuration corresponds to: different active UL RBWs, different active DL RBWs, different numbers of UL RBWs, different numbers of DL RBWs, at least one RBW with different bandwidths, at least one RBW with different time-frequency resource sets, or combinations thereof.

[0256] In a tenth aspect, alone or in combination with one or more of the foregoing aspects, the wireless communication device is further configured to: adjust the components to a third RBW configuration of the BWP configuration based on BWP handover triggering and RBW configuration information; and communicate according to the third RBW configuration during a second time slot, the third RBW configuration being different from the first RBW configuration, the second RBW configuration, or both.

[0257] In the eleventh aspect, alone or in combination with one or more of the foregoing aspects, the component includes a filter or antenna assembly, and adjusting the component includes adjusting the physical or software configuration of the component.

[0258] In the twelfth aspect, alone or in combination with one or more of the above aspects, the wireless communication device is further configured to: determine BWP handover trigger and RBW configuration information; and determine a third RBW configuration for the second time slot based on the BWP handover trigger and the RBW configuration information.

[0259] In the thirteenth aspect, alone or in combination with one or more of the foregoing aspects, the BWP handover triggers a handover based on downlink control information (DCI) transmission, inactivity timer, radio resource control (RRC) signaling, or media access control (MAC) entity, and wherein communication during the second time slot according to the third RBW configuration includes: transmitting UL data during the active uplink (UL) RBW; receiving DL data during the active downlink (DL) RBW; or both.

[0260] In the fourteenth aspect, alone or in combination with one or more of the foregoing aspects, the wireless communication device is further configured to: receive downlink control information (DCI) transmissions indicating RBW configuration information; and determine BWP handover triggering and RBW configuration information based on indicators in the DCI transmissions.

[0261] In the fifteenth aspect, adjusting a component to a third RBW configuration, either alone or in combination with one or more of the foregoing aspects, includes switching from a DL RBW associated with a first RBW configuration to a second DL RBW associated with a third RBW configuration based on an indicator in the DCI transmission.

[0262] In the sixteenth aspect, alone or in combination with one or more of the foregoing aspects, the wireless communication device is further configured to maintain the UL RBW associated with the third RBW configuration in response to switching from a DL RBW to a second DL RBW or based on an indicator in DCI transmission.

[0263] In the seventeenth aspect, alone or in combination with one or more of the foregoing aspects, the wireless communication device is further configured to switch from a UL RBW associated with a first RBW configuration to a second UL RBW associated with a third RBW configuration based on switching the DL RBW to a second DL RBW.

[0264] In the eighteenth aspect, alone or in combination with one or more of the foregoing aspects, the wireless communication device is further configured to: adjust a component to a third RBW configuration of a second BWP configuration based on BWP handover triggering and RBW configuration information; and to communicate according to the third RBW configuration during a second time slot, the third RBW configuration being different from the first RBW configuration, the second RBW configuration, or both.

[0265] In the nineteenth aspect, alone or in combination with one or more of the foregoing aspects, the wireless communication device is further configured to: receive downlink control information (DCI) transmissions; switch from a DL BWP associated with a BWP configuration to a second DL BWP associated with a second BWP configuration based on an indicator in the DCI transmissions; and determine the DL RBW of the second BWP configuration based on the second DL BWP.

[0266] In a twentieth aspect, either alone or in combination with one or more of the foregoing aspects, the wireless communication device is further configured to: receive downlink control information (DCI) transmissions; switch from a UL BWP associated with a BWP configuration to a second UL BWP associated with a second BWP configuration based on an indicator in the DCI transmissions; switch from a UL RBW associated with a BWP configuration to a second UL RBW associated with a second BWP configuration based on the second UL BWP; and maintain a DL RBW associated with a BWP configuration in response to switching the UL RBW to the second UL RBW.

[0267] In the twenty-first aspect, either alone or in combination with one or more of the foregoing aspects, the wireless communication device is further configured to: receive downlink control information (DCI) transmissions; switch from a UL BWP associated with a BWP configuration to a second UL BWP associated with a second BWP configuration based on an indicator in the DCI transmissions; switch from a UL RBW to a second UL RBW based on the second UL BWP; and switch from a DL RBW associated with a first RBW configuration to a second DL RBW associated with a second RBW configuration based on switching from a UL RBW to a second UL RBW based on switching from a UL RBW to a second DL RBW associated with a second RBW configuration.

[0268] In a twentieth aspect, either alone or in combination with one or more of the foregoing aspects, the wireless communication device is further configured to: receive downlink control information (DCI) transmissions; switch from a UL BWP associated with a first RBW configuration to a second UL BWP associated with the first RBW configuration based on an indicator in the DCI transmission; and determine a UL RBW based on the second UL BWP.

[0269] In the twenty-third aspect, either alone or in combination with one or more of the foregoing aspects, the wireless communication device is further configured to: receive a Radio Resource Control (RRC) message indicating an association between a DL RBW and a UL RBW, wherein the association indicates a corresponding RBW handover for a UL and DL RBW configuration for a BWP configuration; and determine at least one of a first RBW configuration or a second RBW configuration based on the association between the DL RBW and the UL RBW.

[0270] In the twenty-fourth aspect, individually or in combination with one or more of the above aspects, each RBW configured by the BWP has a corresponding inactivity timer.

[0271] In the twenty-fifth aspect, alone or in combination with one or more of the foregoing aspects, the wireless communication device is further configured to: determine that the second RBW configuration of the BWP configuration does not have a dedicated inactivity timer; and based on the determination that the second RBW configuration does not have a dedicated inactivity timer, maintain the configuration of the second RBW configuration for communication during the second time slot in response to the expiration of the inactivity timer of another RBW of the BWP configuration.

[0272] In the twenty-sixth aspect, alone or in combination with one or more of the foregoing aspects, the wireless communication device is further configured to switch from the BWP configuration to a second BWP configuration in response to the expiration of an inactivity timer for the BWP configuration, the second BWP configuration being a joint BWP configuration including RBWs for both DL and UL.

[0273] In the twenty-seventh aspect, alone or in combination with one or more of the foregoing aspects, the wireless communication device is further configured to switch from the BWP configuration to separate default DLBWP configuration and default UL BWP configuration in response to the expiration of an inactivity timer for the BWP configuration.

[0274] In the twentieth aspect, individually or in combination with one or more of the foregoing aspects, the BWP configuration is a joint BWP configuration, and the wireless communication device is further configured to: determine that the joint BWP configuration is not configured for RACH procedures; and in response to determining that the joint BWP is not configured for RACH procedures, switch the joint BWP configuration to the default UL BWP configuration configured for RACH procedures.

[0275] In the twenty-ninth aspect, individually or in combination with one or more of the foregoing aspects, the BWP configuration is a joint BWP configuration, and the wireless communication device is further configured to: determine that the joint BWP configuration is not configured for RACH procedures; and in response to determining that the joint BWP is not configured for RACH procedures, switch the joint BWP configuration to a default joint BWP configuration having an RBW configured for RACH procedures.

[0276] In the thirtieth aspect, individually or in combination with one or more of the foregoing aspects, the BWP configuration is a combined BWP configuration, and the wireless communication device is further configured to: determine that the combined BWP configuration is not configured for RACH procedures; and in response to determining that the combined BWP is not configured for RACH procedures, switch the combined BWP configuration to a default UL BWP configuration and a default DL BWP configuration, each of which is configured for RACH procedures.

[0277] In the thirty-first aspect, alone or in combination with one or more of the foregoing aspects, the wireless communication device operates in cross-split duplex (xDD) mode.

[0278] Accordingly, the wireless communication device can perform joint downlink and uplink bandwidth portion operations for full-duplex wireless communication mode. By performing joint downlink and uplink bandwidth portion operations for full-duplex wireless communication mode, throughput and reliability can be improved.

[0279] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.

[0280] The components, functional blocks, and modules described in this document (e.g., Figure 2 The components, functional blocks, and modules (in this document) may include processors, electronic devices, hardware devices, electronic components, logic circuits, memory, software code, firmware code, etc., or any combination thereof. Furthermore, the features discussed herein related to the joint BWP and its RBW configuration may be implemented via dedicated processor circuitry, via executable instructions, and / or combinations thereof.

[0281] Those skilled in the art will further appreciate that, in conjunction with the various illustrative logic blocks, modules, circuits, and algorithmic steps disclosed herein (e.g., Figure 9 and 10 The logic blocks (in this document) can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, various illustrative components, blocks, modules, circuits, and steps are described above in a generalized manner in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in different ways for each specific application, but such implementation decisions should not be construed as departing from the scope of this disclosure. Those skilled in the art will also readily recognize that the order or combination of components, methods, or interactions described herein are merely illustrative and that components, methods, or interactions of various aspects of this disclosure may be combined or performed in ways other than those described and illustrated herein.

[0282] The various illustrative logic blocks, modules, and circuits described herein can be implemented or executed using a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in alternatives, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration.

[0283] The steps of the methods or algorithms described herein can be implemented directly in hardware, in a software module executed by a processor, or a combination of both. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor so that the processor can read and write information from / to the storage medium. In an alternative, the storage medium may be integrated into the processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In an alternative, the processor and storage medium may reside as discrete components in the user terminal.

[0284] In one or more exemplary designs, the described functionality may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functionality may be stored or transmitted as one or more instructions or code on or through a computer-readable medium. A computer-readable medium includes both computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one location to another. A computer-readable storage medium may be any available medium accessible to a general-purpose or special-purpose computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and is accessible to a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Furthermore, a connection may also be appropriately referred to as a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL), then the coaxial cable, fiber optic cable, twisted pair, or DSL is included in the definition of a medium. As used in this article, disk and disc include compact discs (CDs), laser discs, optical discs, digital multi-purpose discs (DVDs), hard disks, solid-state drives (SSDs), and Blu-ray discs. Disks typically reproduce data magnetically, while discs reproduce data optically using lasers. Combinations of these should also be included within the scope of computer-readable media.

[0285] As used herein (including in the claims), the term “and / or” in a list of two or more items means that any one of the listed items may be used alone, or any combination of two or more listed items may be used. For example, if a composition is described as containing components A, B, and / or C, then the composition may contain only A; only B; only C; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B, and C. Moreover, as used herein (including in the claims), the word “or” in a list of items containing “at least one of” indicates a disjunctive list, such that a list such as “at least one of A, B, or C” means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) or any combination thereof.

[0286] The prior description of this disclosure is provided to enable any person skilled in the art to make or use this disclosure. Various modifications to this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the spirit or scope of this disclosure. Therefore, this disclosure is not intended to be limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A wireless communication method, comprising: The wireless communication device receives first data during a time slot according to a first resource bandwidth (RBW) configuration in a first portion of a bandwidth portion (BWP) configuration, wherein the BWP configuration is configured for uplink and downlink operation; as well as The wireless communication device transmits second data during the time slot according to a second RBW configuration in a second part of the BWP configuration, the second RBW configuration being different from the first RBW configuration.

2. The method as described in claim 1, wherein, The wireless communication equipment includes user equipment (UE).

3. The method as described in claim 1, wherein, The wireless communication device includes a network device.

4. The method of claim 1, wherein, The BWP configuration is a combined BWP configuration and is configured for both downlink (DL) and uplink (UL).

5. The method of claim 4, wherein, The BWP configuration has one or more DL RBWs and one or more UL RBWs, and the wireless communication device operates in subband full-duplex (SBFD).

6. The method of claim 1, wherein, The BWP configuration has one or more joint RBWs, wherein the one or more joint RBWs can be configured as DL, UL or both, and wherein the wireless communication device operates in in-band full-duplex (IBFD).

7. The method of claim 6, further comprising: The wireless communication device configures a specific joint RBW from one or more joint RBWs as a downlink based on the RBW configuration table.

8. The method of claim 1, wherein, The BWP configuration has one or more downlink (DL) RBWs and one or more uplink (UL) RBWs, wherein the one or more DL RBWs and the one or more UL RBWs have unique identifiers.

9. The method of claim 1, wherein, The BWP configuration has one or more downlink (DL) RBWs and one or more uplink (UL) RBWs, wherein at least one of the one or more DL RBWs and at least one of the one or more UL RBWs have the same identifier number.

10. The method of claim 1, wherein, The second RBW configuration, which differs from the first RBW configuration, corresponds to: Different active UL RBWs, different active DL RBWs, different numbers of UL RBWs, different numbers of DL RBWs, at least one RBW with different bandwidths, at least one RBW with different time-frequency resource sets, or combinations thereof.

11. An apparatus configured for wireless communication, comprising: At least one processor; as well as Memory coupled to the at least one processor, The at least one processor is configured to: During a time slot, first data is received according to a first resource bandwidth (RBW) configuration in a first portion of a bandwidth portion (BWP) configuration, wherein the BWP configuration is configured for uplink and downlink operation; as well as During the time slot, second data is transmitted according to a second RBW configuration in the second part of the BWP configuration, the second RBW configuration being different from the first RBW configuration.

12. The apparatus of claim 11, wherein, The at least one processor is further configured to: The component is adjusted to the third RBW configuration of the BWP configuration based on the BWP switching trigger and RBW configuration information; as well as Communication is performed during the second time slot according to the third RBW configuration, which is different from the first RBW configuration, the second RBW configuration, or both.

13. The apparatus of claim 12, wherein, The component includes a filter or antenna assembly, and wherein adjusting the component includes: Adjust the physical or software configuration of the component.

14. The apparatus of claim 13, wherein, The at least one processor is further configured to: Determine the BWP handover trigger and the RBW configuration information; and The third RBW configuration for the second time slot is determined based on the BWP switching trigger and the RBW configuration information.

15. The apparatus of claim 12, wherein, The BWP handover triggering is based on downlink control information (DCI) transmission, inactivity timer, radio resource control (RRC) signaling, or media access control (MAC) entity handover, wherein communication during the second time slot according to the third RBW configuration includes: Transmit UL data during active uplink (UL) RBW; Receive DL data during active downlink (DL) RBW; or Both of these.

16. The apparatus of claim 12, wherein, The at least one processor is further configured to: Receive downlink control information (DCI) transmission indicating the RBW configuration information; and The BWP handover trigger and the RBW configuration information are determined based on the indicator in the DCI transmission.

17. The apparatus of claim 16, wherein, Adjusting the component to the third RBW configuration includes: The switch is made from the DL RBW associated with the first RBW configuration to the second DL RBW associated with the third RBW configuration based on the indicator in the DCI transmission.

18. The apparatus of claim 17, wherein, The at least one processor is further configured to: The UL RBW associated with the third RBW configuration is maintained in response to switching from the DL RBW to the second DL RBW or based on the indicator in the DCI transmission.

19. The apparatus of claim 17, wherein, The at least one processor is further configured to: Switching from the UL RBW associated with the first RBW configuration to the second UL RBW associated with the third RBW configuration is based on switching the DL RBW to the second DL RBW.

20. The apparatus of claim 11, wherein, The at least one processor is further configured to: The component is adjusted to the third RBW configuration of the second BWP configuration based on the BWP switching trigger and RBW configuration information. as well as Communication is performed during the second time slot according to the third RBW configuration, which is different from the first RBW configuration, the second RBW configuration, or both.

21. A non-transitory computer-readable medium storing instructions, which, when executed by a processor, cause the processor to perform operations including: During a time slot, first data is received according to a first resource bandwidth (RBW) configuration in a first portion of a bandwidth portion (BWP) configuration, wherein the BWP configuration is configured for uplink and downlink operation; and During the time slot, second data is transmitted according to a second RBW configuration in the second part of the BWP configuration, the second RBW configuration being different from the first RBW configuration.

22. The non-transient computer-readable medium of claim 21, wherein, When executed by the processor, the instructions further cause the processor to perform the following operations: Receive downlink control information (DCI) transmissions; Switching from the DL BWP associated with the BWP configuration to the second DL BWP associated with the second BWP configuration based on the indicator in the DCI transmission; as well as The DL RBW configured by the second BWP is determined based on the second DL BWP.

23. The non-transient computer-readable medium of claim 21, wherein, When executed by the processor, the instructions further cause the processor to perform the following operations: Receive downlink control information (DCI) transmissions; Switching from the UL BWP associated with the BWP configuration to the second UL BWP associated with the second BWP configuration based on the indicator in the DCI transmission; Switching from the UL RBW associated with the BWP configuration to the second UL RBW associated with the second BWP configuration based on the second UL BWP; as well as In response to switching the UL RBW to the second UL RBW, the DL RBW associated with the BWP configuration is maintained.

24. The non-transient computer-readable medium of claim 21, wherein, When executed by the processor, the instructions further cause the processor to perform the following operations: Receive downlink control information (DCI) transmissions; Switching from the UL BWP associated with the BWP configuration to the second UL BWP associated with the second BWP configuration based on the indicator in the DCI transmission; Switching from UL RBW to the second UL RBW based on the second UL BWP; as well as In response to switching the UL RBW to the second UL RBW, a switch is made from the DL RBW associated with the first RBW configuration to the second DL RBW associated with the second RBW configuration.

25. The non-transient computer-readable medium of claim 21, wherein, When executed by the processor, the instructions further cause the processor to perform the following operations: Receive downlink control information (DCI) transmissions; The UL BWP associated with the first RBW configuration is switched to the second UL BWP associated with the first RBW configuration based on the indicator in the DCI transmission. as well as The UL RBW is determined based on the second UL BWP.

26. The non-transient computer-readable medium of claim 21, wherein, When executed by the processor, the instructions further cause the processor to perform the following operations: Receive a Radio Resource Control (RRC) message indicating an association between a DL RBW and a UL RBW, wherein the association indicates a corresponding RBW handover configured for the UL and DL RBWs configured for the BWP; as well as The first RBW configuration or the second RBW configuration is determined based on the association between the DL RBW and the UL RBW.

27. A device configured for wireless communication, comprising: A means for receiving first data during a time slot according to a first resource bandwidth (RBW) configuration in a first portion of a bandwidth portion (BWP) configuration, wherein the BWP configuration is configured for uplink and downlink operation; as well as Means for transmitting second data during the time slot according to a second RBW configuration in a second part of the BWP configuration, the second RBW configuration being different from the first RBW configuration.

28. The device as claimed in claim 27, wherein, Each RBW configured in the BWP has a corresponding inactivity timer.

29. The apparatus of claim 27, further comprising: A means for determining that the second RBW configuration of the BWP configuration does not have a dedicated inactivity timer; as well as A means for maintaining the configuration settings of the second RBW configuration for communication during the second time slot in response to the expiration of the inactivity timer of another RBW of the BWP configuration, based on the determination that the second RBW configuration does not have the dedicated inactivity timer.

30. The apparatus of claim 27, further comprising: Means for switching from the BWP configuration to a second BWP configuration in response to the expiration of an inactivity timer for the BWP configuration, the second BWP configuration being a combined BWP configuration including RBWs for both DL and UL.

31. The apparatus of claim 27, further comprising: A means for switching from the BWP configuration to separate default DL BWP configurations and default UL BWP configurations in response to the expiration of an inactivity timer for the BWP configuration.

32. The device as claimed in claim 27, wherein, The BWP configuration is a combined BWP configuration, and the device further includes: A means for determining that the combined BWP configuration is not configured for RACH procedures; and A means for switching the joint BWP configuration to the default UL BWP configuration configured for RACH procedures in response to determining that the joint BWP configuration is not configured for RACH procedures.

33. The device as claimed in claim 27, wherein, The BWP configuration is a combined BWP configuration, and the device further includes: A means for determining that the combined BWP configuration is not configured for RACH procedures; and A means for switching the joint BWP configuration to a default joint BWP configuration having an RBW configured for RACH procedures in response to determining that the joint BWP configuration is not configured for RACH procedures.

34. The device as claimed in claim 27, wherein, The BWP configuration is a combined BWP configuration, and the device further includes: A means for determining that the combined BWP configuration is not configured for RACH procedures; and Means for switching the combined BWP configuration to a default UL BWP configuration and a default DL BWP configuration in response to determining that the combined BWP configuration is not configured for RACH procedures, each of the default UL BWP configuration and the default DL BWP configuration being configured for RACH procedures.

35. The device as claimed in claim 27, wherein, The device operates in cross-split-duplex (xDD) mode.

36. A wireless communication method, comprising: Communication is performed by the wireless communication device during the first time slot according to the first resource bandwidth (RBW) configuration in the first part of the bandwidth portion (BWP) configuration; The wireless communication device changes from the first RBW configuration to the second RBW configuration based on BWP handover triggering and RBW configuration information; as well as The wireless communication device communicates during a second time slot according to a second RBW configuration, which is different from the first RBW configuration.

37. The method of claim 36, wherein, The change from the first RBW configuration to the second RBW configuration includes: The wireless communication device adjusts the components to the second RBW configuration.

38. The method of claim 36, wherein, The change from the first RBW configuration to the second RBW configuration includes: The component is tuned to the second RBW configuration by the wireless communication device, and wherein the component includes a filter or antenna component.

39. The method of claim 36, wherein, The second RBW configuration is associated with the BWP configuration.

40. The method of claim 36, wherein, The second RBW configuration is associated with the second BWP configuration.

Images