Half-duplex and full-duplex bandwidth adaptation

Abstract

A method of wireless communication by a user equipment (UE) includes receiving a configuration for switching between a full frequency bandwidth slot in a half-duplex mode and a partial frequency bandwidth slot in a subband-based base station full duplex (SBFD) mode. The full frequency bandwidth time slot is used for uplink communication or downlink communication. The partial frequency bandwidth time slot is used for the uplink communication corresponding to an uplink sub-band or for downlink communication corresponding to at least one downlink sub-band. The method also includes switching between the full frequency bandwidth time slot and the partial frequency bandwidth time slot according to the configuration.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. patent application No. 17 / 971,499, filed on October 21, 2022, entitled “HALF-DUPLEX AND FULL DUPLEXBANDWIDTH ADAPTATION,” the disclosure of which is expressly incorporated by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to wireless communications, and more particularly to switching between half-duplex (HD) bandwidth time slots and full-duplex (FD) bandwidth time slots during communications. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the Third Generation Partnership Project (3GPP). Narrowband (NB) Internet of Things (IoT) and enhanced machine type communication (eMTC) are sets of enhancements to LTE for machine type communication.

[0005] A wireless communication network may include multiple base stations (BSs) that may support communications for multiple user equipments (UEs). User equipments (UEs) may communicate with base stations (BSs) via downlinks and uplinks. Downlinks (or forward links) refer to the communication link from a BS to a UE, while uplinks (or reverse links) refer to the communication link from a UE to a BS. As will be described in more detail, a BS may be referred to as a Node B, an evolved Node B (eNB), a gNB, an access point (AP), a radio head, a transmit and receive point (TRP), a new radio (NR) BS, a 5G Node B, etc.

[0006] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user equipment to communicate at city, country, region, and even global levels. New Radio (NR) (which may also be referred to as 5G) is an enhancement set of the LTE mobile standard released by the Third Generation Partnership Project (3GPP). NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink (DL), using CP-OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), and supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation, so as to better support mobile broadband Internet access. Summary of the invention

[0007] In various aspects of the present disclosure, a method for wireless communication by a user equipment (UE) includes receiving a configuration for switching between a full frequency bandwidth time slot and a partial frequency bandwidth time slot, the full frequency bandwidth time slot being used for uplink communication or downlink communication in a half-duplex mode, and the partial frequency bandwidth time slot being used for uplink communication corresponding to an uplink subband or for downlink communication corresponding to at least one downlink subband in a subband-based base station full-duplex mode. The method also includes switching between the full frequency bandwidth time slot and the partial frequency bandwidth time slot according to the configuration.

[0008] In other aspects of the present disclosure, a method for wireless communication by a network device includes: sending a configuration for switching between a full frequency bandwidth time slot and a partial frequency bandwidth time slot, the full frequency bandwidth time slot being used for uplink communication or downlink communication in a half-duplex mode, the partial frequency bandwidth time slot being used for uplink communication corresponding to an uplink subband and for downlink communication corresponding to at least one downlink subband in a subband-based base station full-duplex mode. The method also includes switching between the full frequency bandwidth time slot and the partial frequency bandwidth time slot according to the configuration.

[0009] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer readable media, user equipment, base stations, wireless communication devices, and processing systems as generally described with reference to and as illustrated in the accompanying drawings and description.

[0010] The features and technical advantages of examples according to the present disclosure have been outlined quite broadly above so that the following specific embodiments may be better understood. Additional features and advantages will be described. The disclosed concepts and specific examples may be readily utilized as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the disclosed concepts, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order that the features of the present disclosure may be understood in detail, a more specific description may be made with reference to various aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the accompanying drawings illustrate only certain aspects of the present disclosure and therefore should not be considered as limiting the scope thereof, as the description may allow for other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0012] Figure 1 is a block diagram conceptually illustrating an example of a wireless communication network in accordance with various aspects of the present disclosure.

[0013] Figure 2 is a block diagram conceptually illustrating an example of a base station communicating with a user equipment (UE) in a wireless communication network according to various aspects of the present disclosure.

[0014] Figure 3 is a block diagram illustrating an example decomposed base station architecture in accordance with aspects of the present disclosure.

[0015] Figure 4A , Figure 4B and Figure 4C is a block diagram illustrating full-duplex communication according to aspects of the present disclosure.

[0016] Figure 5 is a block diagram illustrating a sub-band full-duplex (SBFD) configuration in accordance with aspects of the present disclosure.

[0017] Figure 6 is a block diagram illustrating full-duplex and half-duplex operations in accordance with aspects of the present disclosure.

[0018] Figure 7 is a block diagram illustrating reference signal problems caused by a UE that is unaware of the configured downlink / uplink bandwidth in accordance with aspects of the present disclosure.

[0019] Fig. 8A and Figure 8B is a block diagram illustrating half-duplex and full-duplex bandwidth adaptation in accordance with aspects of the present disclosure.

[0020] Fig. 9 is a block diagram illustrating predetermined half-duplex and full-duplex bandwidth switching in accordance with aspects of the present disclosure.

[0021] Fig.10 is a block diagram illustrating different pre-configured bandwidth modes according to aspects of the present disclosure.

[0022] Fig.11 is a flow chart illustrating an example process performed, for example, by a user equipment (UE) according to aspects of the present disclosure.

[0023] Fig.12 is a flow chart illustrating an example process, for example, performed by a network device, according to aspects of the present disclosure. DETAILED DESCRIPTION

[0024] The following is a more comprehensive description of various aspects of the present disclosure with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of protection of the present disclosure will be fully conveyed to those skilled in the art. Based on the teachings, those skilled in the art should recognize that the scope of the present disclosure is intended to cover any aspect of the present disclosure, whether the aspect is implemented independently of any other aspect of the present disclosure or implemented in combination with any other aspect. For example, a device or a method can be implemented using any number of aspects described. In addition, the scope of the present disclosure is intended to cover such devices or methods that are practiced using other structures, functionality, or structures and functionality as a supplement to the various aspects of the present disclosure described or in addition. It should be understood that any aspect of the present disclosure disclosed can be embodied by one or more elements of the claims.

[0025] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0026] It should be noted that although various aspects may be described using terms commonly associated with 5G and later wireless technologies, various aspects of the present disclosure may be applied in communication systems based on other generations (such as and including 3G and / or 4G technologies).

[0027] Certain aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, the described techniques (eg, receiving ...) can increase spectrum utilization.

[0028] New Radio (NR) may include scenarios with full-duplex communications, so that a single device can transmit and receive simultaneously. For example, these scenarios may operate with time division duplex (TDD) unpaired spectrum. In some implementations, the network (e.g., gNB) may operate in full-duplex mode, while half-duplex operation occurs on the user equipment (UE) side. Sub-band full-duplex (SBFD) mode enables network devices (e.g., base stations) to simultaneously send and receive downlink and uplink communications based on subbands in the same time slot. In the presence of strong self-interference, the base station may preferably switch from full-duplex (e.g., SBFD) operation to half-duplex operation. Such switching may involve a change in the downlink / uplink bandwidth of the UE.

[0029] Aspects of the present disclosure introduce a group common physical downlink control channel (GC-PDCCH) for half-duplex and full-duplex bandwidth adaptation. According to some aspects, a group common downlink control information (DCI) message may be introduced for downlink / uplink bandwidth switching of SBFD-aware UE groups. DCI may carry a separate downlink / uplink bandwidth field for each UE, or carry a common downlink / uplink bandwidth field for all UEs. If self-interference at a base station occurs occasionally but unpredictably, the base station may enable half-duplex mode for signaling critical control messages. In some aspects of the present disclosure, switching between half-duplex and full-duplex bandwidth occurs at a predetermined time. For example, a predetermined half-duplex / full-duplex bandwidth switching mode may be configured to periodically switch between downlink / uplink bandwidths for half-duplex and SBFD modes for a base station. These modes may be configured for each UE or for a UE group. Bandwidth (or subband) switching based on a predetermined mode may be indicated explicitly or implicitly.

[0030] Figure 11 is a diagram illustrating a network 100 in which various aspects of the present disclosure may be practiced. The network 100 may be a 5G or NR network, or some other wireless network (such as an LTE network). The wireless network 100 may include a plurality of BSs 110 (shown as BSs 110a, BSs 110b, BSs 110c, and BSs 110d) and other network entities. A BS is an entity that communicates with a user equipment (UE), and may also be referred to as a base station, an NR BS, a Node B, a gNB, a 5G Node B, an access point, a transmission and reception point (TRP), a network node, a network entity, etc. A base station may be implemented as an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, a side link node, etc. A base station may be implemented in an aggregated or monolithic base station architecture, or alternatively, in a decomposed base station architecture, and may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC.

[0031] Each BS can provide communication coverage for a specific geographical area. In 3GPP, the term "cell" can refer to the coverage area of ​​a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0032] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown in , BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a femto BS for femto cell 102c. A BS may support one or more (e.g., three) cells. The terms "eNB", "base station", "NR BS", "gNB", "AP", "Node B", "5G NB", "TRP", and "cell" may be used interchangeably.

[0033] In some aspects, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move according to the location of the mobile BS. In some aspects, the BSs may be interconnected with each other and / or to one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces (such as direct physical connections, virtual networks, etc.) using any appropriate transport network.

[0034] The wireless network 100 may also include a relay station. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a BS or a UE) and transmit the transmissions of the data to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions for other UEs. Figure 1 In the example shown in FIG. 1 , a relay station 110 d may communicate with a macro BS 110 a and a UE 120 d to facilitate communication between the BS 110 a and the UE 120 d. A relay station may also be referred to as a relay BS, a relay base station, a relay, or the like.

[0035] The wireless network 100 may be a heterogeneous network including different types of BSs (e.g., macro BSs, pico BSs, femto BSs, relay BSs, etc.). These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico BS, a femto BS, and a relay BS may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0036] For example, BSs 110 (shown as BS110a, BS110b, BS110c, and BS110d) and core network 130 may exchange communications via backhaul links 132 (e.g., S1, etc.). Base stations 110 may communicate with each other directly or indirectly (e.g., through core network 130) through other backhaul links (e.g., X2, etc.).

[0037] The core network 130 may be an evolved packet core (EPC), which may include at least one mobile management entity (MME), at least one serving gateway (S-GW), and at least one packet data network (PDN) gateway (P-GW). The MME may be a control node that handles signaling between the UE 120 and the EPC. All user IP packets may be delivered through the S-GW, which itself may be connected to the P-GW. The P-GW may provide IP address allocation and other functions. The P-GW may be connected to the IP services of the network operator. The operator's IP services may include the Internet, the intranet, the IP multimedia subsystem (IMS), and the packet switched (PS) streaming media services.

[0038] The core network 130 may provide user authentication, access authorization, tracking, IP connectivity, and other access, routing, or mobility functions. One or more of the base stations 110 or access node controllers (ANCs) may interface with the core network 130 via a backhaul link 132 (e.g., S1, S2, etc.) and may perform radio configuration and scheduling for communications with the UE 120. In some configurations, the various functions of each access network entity or base station 110 may be distributed across various network devices (e.g., radio heads and access network controllers), or merged into a single network device (e.g., base station 110).

[0039] UE 120 (e.g., 120a, 120b, 120c) may be dispersed throughout the wireless network 100, and each UE may be stationary or mobile. UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. UE may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device (smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device or a satellite radio), a component or sensor of a vehicle, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium.

[0040] One or more UEs 120 may establish a protocol data unit (PDU) session for a network slice. In some cases, the UE 120 may select a network slice based on an application or subscription service. By enabling different network slices to serve different applications or subscriptions, the UE 120 may improve its resource utilization in the wireless network 100 while also meeting the performance specifications of the individual applications of the UE 120. In some cases, the AMF ( Figure 1 ), to serve the network slice used by UE 120. In addition, session management of the network slice can be performed by an access and mobility management function (AMF).

[0041] The UE 120 may include a half-duplex / full-duplex (HD / FD) module 140. For simplicity, only one UE 120d is shown as including the HD / FD module 140. The HD / FD module 140 may receive a configuration for switching between a full frequency bandwidth time slot in a half-duplex mode and a partial frequency bandwidth time slot in a sub-band based base station full-duplex mode. The HD / FD module 140 may also switch between a full frequency bandwidth time slot and a partial frequency bandwidth time slot according to the configuration.

[0042] The core network 130 or the base station 110 or any other network device (e.g., Figure 3 10a) may include an HD / FD encoding module 138. For simplicity, only one base station 110a is shown as including an HD / FD module 138. The HD / FD module 138 may send a configuration for switching between full frequency bandwidth time slots in half-duplex mode and partial frequency bandwidth time slots in sub-band based base station full-duplex mode. The HD / FD module 138 may also switch between full frequency bandwidth time slots and partial frequency bandwidth time slots according to the configuration.

[0043] Some UEs may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. For example, MTC and eMTC UEs include robots, drones, remote devices, sensors, meters, monitors, location tags, etc. that can communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide connectivity to or to a network (e.g., a wide area network such as the Internet or a cellular network), for example, via a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered as customer premises equipment (CPE). UE 120 may be included in a housing that houses components of UE 120 (e.g., processor components, memory components, etc.).

[0044] Generally speaking, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a specific radio access technology (RAT) and can operate on one or more frequencies. RAT can also be referred to as radio technology, air interface, etc. Frequency can also be referred to as carrier, frequency channel, etc. In a given geographic area, each frequency can support a single RAT to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0045] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary to communicate with each other) using one or more sidelink channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, etc.), mesh networks, etc. In this case, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein performed by base station 110. For example, base station 110 may configure UE 120 via downlink control information (DCI), radio resource control (RRC) signaling, medium access control-control element (MAC-CE), or via system information (e.g., system information block (SIB)).

[0046] As pointed out above, Figure 1 This is provided as an example only. Other examples can be found in the reference Figure 1 The examples described are different.

[0047] Figure 2 A block diagram of a design 200 of a base station 110 and a UE 120 is shown, which may be Figure 1 A base station in the base station and Figure 1 Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general T≧1 and R≧1.

[0048] At the base station 110, the transmit processor 220 may receive data for one or more UEs from the data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for the UE based at least in part on the MCS selected for each UE, and provide data symbols for all UEs. Reducing the MCS lowers throughput but increases the reliability of transmission. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI), etc.) and control information (e.g., CQI requests, grants, upper layer signaling, etc.), and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS)) and synchronization signals (e.g., primary synchronization signals (PSS) and secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and may provide T output symbol streams to T modulators (MOD) 232a to 232t. Each modulator 232 may process a corresponding output symbol stream (e.g., for orthogonal frequency division multiplexing (OFDM) or the like) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a to 232t may be transmitted via T antennas 234a to 234t, respectively. According to various aspects described in more detail below, position coding may be used to generate synchronization signals to convey additional information.

[0049] At the UE 120, antennas 252a to 252r may receive downlink signals from the base station 110 and / or other base stations, and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. The MIMO detector 256 may obtain received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to the data sink 260, and provide decoded control information and system information to the controller / processor 280. The channel processor may determine reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), channel quality indicator (CQI), etc. In some aspects, one or more components of UE 120 may be included in a housing.

[0050] On the uplink, at the UE 120, a transmit processor 264 may receive data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.) from a controller / processor 280 and process the data and control information. The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by a TX MIMO processor 266 (if applicable), further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to the base station 110. At the base station 110, uplink signals from the UE 120 and other UEs may be received by the antenna 234, processed by the demodulator 254, detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and communicate with the core network 130 via the communication unit 244. The core network 130 may include a communication unit 294, a controller / processor 290, and a memory 292.

[0051] Controller / processor 240 of base station 110, controller / processor 280 of UE 120, and / or Figure 2Any other components of the base station 110 may perform one or more techniques associated with half-duplex / full-duplex switching, as described in greater detail elsewhere. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of may perform or direct e.g. Fig.11 and Fig.12 The processes and / or operations of other processes as described. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. Scheduler 246 may schedule UEs for data transmission on the downlink and / or uplink.

[0052] In some aspects, UE 120 and / or base station 110 may include components for receiving, components for switching, and components for transmitting. Such components may include a combination of Figure 2 One or more components of a UE 120 or base station 110 are described.

[0053] As pointed out above, Figure 2 This is provided as an example only. Other examples can be found in the reference Figure 2 The examples described are different.

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

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

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

[0057] Figure 3 A diagram illustrating an example decomposed base station 300 architecture is shown. The decomposed base station 300 architecture may include one or more central units (CUs) 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more distributed units (DUs) 330 via respective midhaul links, such as an F1 interface. The DU 330 may communicate with one or more radio units (RUs) 340 via respective fronthaul links. The RU 340 may communicate with respective UEs 120 via one or more radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0058] Each of these units (e.g., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RTRIC 315, and SMO framework 305) may include one or more interfaces, or may be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface that is configured to receive or send signals to one or more of the other units via a wired transmission medium. In addition, the unit may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) that is configured to receive or send signals to one or more of the other units via a wireless transmission medium, or both.

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

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

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

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

[0063] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions on an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB 311 with the near-RT RIC 325.

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

[0065] NR may include scenarios with full-duplex communications, so that a single device can transmit and receive simultaneously. For example, these scenarios can operate with time division duplex (TDD) unpaired spectrum. In some implementations, the network (e.g., gNB) can operate in full-duplex mode, while half-duplex operation occurs on the user equipment (UE) side.

[0066] Sub-band non-overlapping full-duplex mode can operate in a dynamic / flexible TDD environment. In some cases, cross-link interference (CLI) may occur. For example, during sub-band non-overlapping full-duplex operation, both intra-sub-band cross-link interference and inter-sub-band cross-link interference may occur.

[0067] Figure 4A , Figure 4B and Figure 4C is a block diagram illustrating an example of full-duplex communication according to aspects of the present disclosure. Figure 4A , a network device (e.g., gNB) 110 transmits from a first panel (A) to a first UE 120-f. The network device 110 receives a signal from a second UE 120-g having a second panel (B). Cross-link interference 402 may be caused by full-duplex operation such that the transmission to the first UE 120-f interferes with the signal received from the second UE 120-g. Figure 4B In the example of FIG. 4 , a signal 404 transmitted from a network device 110 reflects off a structure 406 and interferes with a signal 408 received from a device (not shown). This type of interference may be referred to as clutter. Self-interference (e.g., cross-link interference) may also occur in Figure 4B In the scene depicted in Figure 4C As seen in FIG. 4 , downlink / uplink (DL / UL) multi-user multiple-input multiple-output (MU-MIMO) communications may occur while in full-duplex mode. That is, a downlink signal 410 to a first user (not shown) may interfere with a signal 412 received from a second user (not shown). Clutter may also interfere with communications.

[0068] Sub-band full-duplex (SBFD) mode enables simultaneous transmission and reception of downlink and uplink communications based on subbands in the same time slot. SBFD communication increases the uplink duty cycle, resulting in reduced latency. For example, downlink signals can be received only in uplink time slots, which enables latency savings. The increased uplink duty cycle also improves uplink coverage and enhances system capacity, resource utilization, and spectrum efficiency. SBFD operation enables flexible and dynamic uplink / downlink resource adaptation based on uplink / downlink traffic in a robust manner.

[0069] Figure 5 5 is a block diagram illustrating sub-band full duplex (SBFD) configurations according to aspects of the present disclosure. In a first configuration 502, a component carrier (CC) bandwidth (BW) of a time slot includes an uplink subband 506 located between two downlink subbands 504, 508. In a second configuration 520, a component carrier (CC) bandwidth (BW) of a time slot includes a downlink subband 522 and an uplink subband 524.

[0070] In the presence of strong self-interference, the base station may preferably switch from full-duplex (e.g., SBFD) operation to half-duplex operation. Such switching may involve a change in the downlink / uplink bandwidth of the UE. In the case where the base station operates in half-duplex mode, the UE downlink / uplink bandwidth may be the full operating bandwidth that fully utilizes the spectrum. When the base station operates in SBFD mode, the downlink / uplink bandwidth may be narrower than the full bandwidth to save UE power.

[0071] Figure 6 6 is a block diagram illustrating full-duplex and half-duplex operations according to aspects of the present disclosure. In full-duplex operation 610, each of the downlink bandwidth 602 and the uplink bandwidth 604 is less than the full bandwidth, in part due to the gap 606 between the uplink subband 602 and the downlink subband 604. When experiencing strong self-interference (SI) 606, the base station may prefer half-duplex operation 620. According to aspects of the present disclosure, the base station may switch to half-duplex operation 620. After switching to half-duplex operation 620, each of the downlink bandwidth 622 and the uplink bandwidth 624 covers the full spectrum, and the self-interference 606 is reduced.

[0072] In addition to the power savings achieved by transmitting at a bandwidth less than the full bandwidth, additional benefits may be lost if the UE is unaware of the actual configured downlink / uplink bandwidth for SBFD operation of the base station. For example, if the UE is unaware of the actual downlink / uplink bandwidth being used, the bandwidth of the downlink / uplink reference signal may be unnecessarily wide. For periodic or semi-periodic channel state information reference signal (CSI-RS) measurements, the UE can measure the full bandwidth instead of the bandwidth over which the CSI-RS is actually transmitted. The full bandwidth may be affected by inter-UE CLI from the actual uplink bandwidth, especially by inter-UE CLI from UEs in neighboring cells in the absence of inter-cell coordination. This type of measurement may result in inaccurate layer one (L1) measurements, as well as incorrect triggering of beam failure recovery (BFR), radio link failure (RLF), handover (HO), etc.

[0073] Figure 7 is a block diagram illustrating a reference signal problem caused by a UE that is unaware of the configured downlink / uplink bandwidth in accordance with aspects of the present disclosure. Figure 7 In the example of FIG. 1 , the base station operates in full-duplex mode with a downlink bandwidth 702 and an uplink bandwidth 704 in the configured uplink / downlink bandwidth. The base station sends a CSI RS 706 on the downlink bandwidth 702. If the UE is not aware of the downlink / uplink bandwidth configuration, the UE measures the CSI-RS across both the downlink bandwidth 702 and the uplink bandwidth 704. The measurement 708 may be affected by the inter-UE CLI from the actual uplink bandwidth 704, especially by the inter-UE CLI from the neighboring cell UEs.

[0074] For periodic or semi-periodic sounding reference signals (SRS), if the UE does not know the downlink / uplink bandwidth configured for full-duplex operation, the UE can send SRS in the full bandwidth 710. As a result, the UE can make the inter-UE CLI reach the actual downlink bandwidth 702, where SRS 710 is sent on the full bandwidth. In the absence of inter-cell coordination, interference is particularly likely to occur for neighboring cell UEs.

[0075] Restricting downlink and uplink reference signals to half-duplex time slots can solve the described problem. However, such scheduling may reduce the flexibility of reference signal location and periodicity. In addition, the additional CLI suppression provided by separate UE downlink and uplink radio frequency (RF) bandwidths may not always be achieved. The UE RF front end may see interference variations, and such variations may cause challenges to automatic gain control (AGC), low noise amplifier (LNA) and / or mixer operation.

[0076] Aspects of the present disclosure introduce a group common physical downlink control channel (GC-PDCCH) for half-duplex and full-duplex bandwidth adaptation. According to some aspects, a group common DCI message may be introduced for downlink / uplink bandwidth switching of SBFD aware UE groups. DCI may carry a separate downlink / uplink bandwidth field for each UE, or carry a common downlink / uplink bandwidth field for all UEs. The downlink / uplink bandwidth may be equal to the downlink / uplink subband of the SBFD time slot. In some aspects, the downlink bandwidth is non-continuous with two non-continuous downlink subbands. If self-interference at the base station occurs occasionally but unpredictably, the base station may enable half-duplex mode for signaling critical control messages. For example, half-duplex operation may be enabled for the transmission of signals, such as synchronization signal blocks (SSBs), system information blocks (SIBs), paging messages, and initial access messages. The initial access message may include a physical random access channel (PRACH) message.

[0077] Fig. 8A and Figure 8B is a block diagram illustrating half-duplex and full-duplex bandwidth adaptation according to aspects of the present disclosure. Fig. 8A In the example of , the use of the bandwidth allocated to the UE switches between a full-duplex configuration and a half-duplex configuration, and returns to a full-duplex configuration. At time t1, a time slot is configured for full-duplex operation, for example in SBFD mode. Fig. 8A In the example of , a single downlink bandwidth (e.g., subband) and a single uplink bandwidth (e.g., subband) are configured for each time slot to achieve full-duplex communication. At time t2, the base station sends a GC-PDCCH message initiating a change to half-duplex bandwidth. The GC-PDCCH message can be a group common DCI message addressed to a single UE or addressed to a UE group.

[0078] At time t3, the base station and UE switch to a half-duplex bandwidth configuration so that the downlink bandwidth occupies the entire allocated bandwidth of the first time slot, and then the uplink bandwidth occupies the entire allocated bandwidth of subsequent time slots. Half-duplex operation may be suitable for critical control messaging.

[0079] At time t4, the base station sends a GC-PDCCH message initiating a change to full-duplex bandwidth. At time t5, the base station and the UE switch to the full-duplex bandwidth configuration. Fig. 8A In the example of , a single downlink bandwidth (eg, sub-band) and a single uplink bandwidth (eg, sub-band) are configured for each time slot to achieve full-duplex communication.

[0080] exist Figure 8B In the example of , the bandwidth allocated to the UE can also be switched between full-duplex configuration and half-duplex configuration. Figure 8B In , the full-duplex configuration includes two non-contiguous downlink subbands. At time t1, a time slot is configured for full-duplex operation, such as in SBFD mode. Figure 8B In the example of , two downlink bandwidths (e.g., subbands) are separated by a single uplink bandwidth (e.g., subband) in each time slot to achieve full-duplex communication. At time t2, the base station sends a GC-PDCCH message initiating a change to half-duplex bandwidth. The GC-PDCCH message can be a group common DCI message addressed to a single UE or addressed to a group of UEs.

[0081] At time t3, the base station and UE switch to a half-duplex bandwidth configuration so that the downlink bandwidth occupies the entire allocated bandwidth of the first time slot, and then the uplink bandwidth occupies the entire allocated bandwidth of subsequent time slots. Half-duplex operation may be suitable for critical control messaging.

[0082] At time t4, the base station sends a GC-PDCCH message initiating a change to full-duplex bandwidth. At time t5, the base station and the UE switch to the full-duplex bandwidth configuration. Figure 8B In the example of , two downlink bandwidths (eg, sub-bands) are separated by a single uplink bandwidth (eg, sub-band) in each time slot to achieve full-duplex communication.

[0083] In some aspects of the present disclosure, switching between half-duplex and full-duplex bandwidth occurs at a predetermined time. For example, a predetermined half-duplex / full-duplex bandwidth switching pattern can be configured to periodically switch between downlink / uplink bandwidths for half-duplex and SBFD modes for a base station. These modes can be configured for each UE or for a group of UEs.

[0084] The half-duplex cycle may contain opportunities for critical control messages. Critical messages may include, for example, synchronization signal blocks (SSBs), system information blocks (SIBs), paging messages, and initial access messages. Initial access messages may include physical random access channel (PRACH) messages.

[0085] The SBFD time slot may be configured with a pattern indicating a single downlink bandwidth and a single uplink bandwidth. The downlink bandwidth and the uplink bandwidth may be equal to the downlink and uplink subbands of the SBFD time slot. In other specific implementations, the SBFD time slot may be configured with a pattern including a single uplink bandwidth located between a pair of non-contiguous downlink bandwidths (e.g., subbands). A predetermined half-duplex / full-duplex bandwidth switching pattern may be configured for each UE or for a group of UEs to periodically switch between downlink and uplink bandwidths for half-duplex and SBFD modes of the base station.

[0086] Assuming the same pair of downlink bandwidth part (BWP) and uplink BWP has been configured, the pre-configured mode changes the downlink and uplink bandwidth (e.g., subband) but does not change the BWP. The same BWP pair spans both legacy downlink / uplink symbols or slots and SBFD symbols or slots. Fig. 9 is a block diagram illustrating predetermined half-duplex and full-duplex bandwidth switching according to aspects of the present disclosure. Fig. 9 In the example of , downlink and uplink BWP 902 have been configured. At time t1, the time slots are configured for half-duplex bandwidth, so that the downlink bandwidth occupies the entire configured BWP 902 of the first time slot, and then the uplink bandwidth occupies the entire configured BWP 902 of the subsequent time slot. At time t2, the mode is switched to full-duplex operation, such as SBFD mode. A single downlink bandwidth (e.g., subband) and a single uplink bandwidth (e.g., subband) are configured for each time slot to achieve full-duplex communication. At time t3, the base station and UE switch to half-duplex operation. At time t4, the base station and UE switch to a full-duplex bandwidth configuration, where a single downlink bandwidth (e.g., subband) and a single uplink bandwidth (e.g., subband) are configured for each time slot.

[0087] Bandwidth (or subband) switching based on a predetermined pattern may be indicated explicitly or implicitly. In some implementations, explicit signaling may include UE-specific signaling or group common layer one (L1), layer two (L2), or layer three (L3) signaling. Explicit signaling may indicate each switch between duplex modes. Alternatively, explicit signaling may be based on a semi-static pattern.

[0088] Implicit signaling can be triggered by specific events, such as changes in duplex / operating mode, which can be explicitly signaled or implicitly determined. An example of an implicit trigger is switching to the original or default mode when a timer expires after having switched to fallback mode without further instructions to stay in fallback mode. For explicit indications, the event can be a semi-static duplex mode, or a dynamic indication of a duplex mode switch. For implicit indications, if the UE is in full-duplex mode, rules can be defined. For example, if the UE's self-interference or cross-link interference from neighboring UEs is too large (e.g., greater than a threshold), the UE will implicitly fall back to the old half-duplex mode.

[0089] Half-duplex and SBFD modes may have different preconfigured bandwidth modes. In one example, the SBFD mode may have multiple parameter sets with different guard band sizes. Different guard band sizes change the corresponding downlink bandwidth (e.g., subband) or uplink bandwidth (e.g., subband) size. In another example, the SBFD mode may have multiple parameter sets with different uplink subband sizes that will change the corresponding downlink bandwidth (e.g., subband) and / or guard band size.

[0090] Fig.10 1 is a block diagram illustrating different pre-configured bandwidth modes according to aspects of the present disclosure. In a first pre-configured bandwidth mode 1010, a downlink bandwidth 1012 has a first size, a guard band 1014 has a first size, and an uplink bandwidth 1016 has a first size. In a second pre-configured bandwidth mode 1020, a downlink bandwidth 1022 has a second size, a guard band 1024 has a second size, and an uplink bandwidth 1026 has a second size. Because the second mode 1020 has a different guard band size than the first mode 1010, the uplink bandwidths 1016, 1026 and the downlink bandwidths 1012, 1022 also have different sizes in the different pre-configured bandwidth modes 1010, 1020.

[0091] As shown above, Figures 4 to Fig.10 Other examples may be provided with respect to Figures 4 to Fig.10 The examples described are different.

[0092] Fig.11 1 is a flow chart illustrating an example process 1100 performed, for example, by a user equipment (UE) according to aspects of the present disclosure. The example process 1100 is an example of switching between half-duplex (HD) bandwidth time slots and full-duplex (FD) bandwidth time slots during communication. The operations of the process 1100 may be implemented by the UE 120.

[0093] At box 1102, a user equipment (UE) receives a configuration for switching between a full frequency bandwidth time slot in a half-duplex mode and a partial frequency bandwidth time slot in a subband-based base station full-duplex mode. The partial frequency bandwidth may be for uplink communication corresponding to an uplink subband or for downlink communication corresponding to at least one downlink subband. The full frequency bandwidth time slot may be used for uplink or downlink communication. For example, a UE (e.g., using antenna 252, DEMOD / MOD 254, MIMO detector 256, receiving processor 258, controller / processor 280, memory 282, etc.) may receive the configuration. In some aspects, the configuration is a group common downlink control information (DCI) message that may carry a configuration for a UE group. In other aspects, the configuration is a UE-specific downlink control information (DCI) message that carries a configuration for a separate UE. The partial bandwidth time slot for downlink communication may include a non-contiguous frequency subband or a single continuous frequency subband. A full frequency bandwidth time slot for uplink communication or downlink communication in half-duplex mode may correspond to a signaling for at least one of the following: a synchronization signal block (SSB), a system information block (SIB), a paging message, or a physical random access channel (PRACH). The configuration may include a predetermined bandwidth or subband switching mode that does not change the bandwidth portion (BWP) configured for uplink communication and / or downlink communication. In some aspects, the configuration includes explicit signaling dedicated to the UE or dedicated to a UE group. Explicit signaling can be used for semi-static switching between full frequency bandwidth time slots and partial frequency bandwidth time slots. In other aspects, explicit signaling is radio resource control (RRC) signaling, medium access control-control element (MAC-CE) or downlink control information (DCI) signaling. In other aspects, explicit signaling is used for dynamic switching per switch between full frequency bandwidth time slots and partial frequency bandwidth time slots. The configuration may be implicit signaling triggered by an event. In some aspects, the event includes a change in duplex mode. In other aspects, the event comprises expiration of a timer after switching to the fallback mode without instructions to remain in the fallback mode, the event triggering a return from the fallback mode to the first mode.

[0094] The user equipment (UE) switches between full frequency bandwidth time slots and partial frequency bandwidth time slots according to the configuration at block 1104. For example, the UE (eg, using controller / processor 280, memory 282, etc.) may receive the configuration.

[0095] Fig.12 1 is a flow chart illustrating an example process 1200 performed, for example, by a network device according to aspects of the present disclosure. The example process 1200 is an example of switching between half-duplex (HD) bandwidth time slots and full-duplex (FD) bandwidth time slots during communication. The operations of process 1200 may be implemented by base station 110.

[0096] At box 1202, the base station sends a configuration for switching between a full frequency bandwidth time slot for uplink communication or downlink communication in half-duplex mode and a partial frequency bandwidth time slot in a sub-band-based base station full-duplex mode. The partial frequency bandwidth time slot can be for uplink communication corresponding to the uplink subband and for downlink communication corresponding to at least one downlink subband. For example, the base station (e.g., using antenna 234, MOD / DEMOD 232, TX MIMO processor 230, transmit processor 220, controller / processor 240, memory 242, etc.) can send the configuration. In some aspects, the configuration is a group common downlink control information (DCI) message, which can carry a configuration for a UE group. In other aspects, the configuration is a UE-specific downlink control information (DCI) message carrying a configuration for a separate UE. The partial bandwidth time slot for downlink communication can include non-contiguous frequency subbands or a single continuous frequency subband. A full frequency bandwidth time slot for uplink communication or downlink communication in half-duplex mode may correspond to a signaling for at least one of the following: a synchronization signal block (SSB), a system information block (SIB), a paging message, or a physical random access channel (PRACH). The configuration may include a predetermined bandwidth or subband switching mode that does not change the bandwidth portion (BWP) configured for uplink communication and / or downlink communication. In some aspects, the configuration includes explicit signaling dedicated to the UE or dedicated to a UE group. Explicit signaling can be used for semi-static switching between full frequency bandwidth time slots and partial frequency bandwidth time slots. In other aspects, explicit signaling is radio resource control (RRC) signaling, medium access control-control element (MAC-CE) or downlink control information (DCI) signaling. In other aspects, explicit signaling is used for dynamic switching per switch between full frequency bandwidth time slots and partial frequency bandwidth time slots. The configuration may be implicit signaling triggered by an event. In some aspects, the event includes a change in duplex mode. In other aspects, the event comprises expiration of a timer after switching to the fallback mode without instructions to remain in the fallback mode, the event triggering a return from the fallback mode to the first mode.

[0097] At block 1204, the user equipment (UE) switches between full frequency bandwidth time slots and partial frequency bandwidth time slots according to the configuration. For example, the UE (eg, using controller / processor 280, memory 282, etc.) may receive the configuration.

[0098] Example aspects

[0099] Aspect 1: A method for wireless communication by a user equipment (UE), the method comprising: receiving a configuration for switching between a full-frequency bandwidth time slot and a partial-frequency bandwidth time slot, the full-frequency bandwidth time slot being used for uplink communication or downlink communication in half-duplex mode, the partial-frequency bandwidth time slot being used for the uplink communication corresponding to an uplink subband or for downlink communication corresponding to at least one downlink subband in a subband-based base station full-duplex mode; and switching between the full-frequency bandwidth time slot and the partial-frequency bandwidth time slot according to the configuration.

[0100] Aspect 2: The method according to aspect 1, wherein the configuration includes a group common downlink control information (DCI) message.

[0101] Aspect 3: The method according to aspect 1 or 2, wherein the DCI message carries the configuration for the UE group.

[0102] Aspect 4: The method according to aspect 1, wherein the configuration includes a UE-specific downlink control information (DCI) message.

[0103] Aspect 5: The method according to aspect 1 or 4, wherein the DCI message carries the configuration for an individual UE.

[0104] Aspect 6: The method according to any one of the preceding aspects, wherein the partial bandwidth time slot used for downlink communication includes non-contiguous frequency sub-bands.

[0105] Aspect 7: The method according to any one of aspects 1 to 5, wherein the partial bandwidth time slot used for downlink communication includes a single continuous frequency sub-band.

[0106] Aspect 8: A method according to any one of the preceding aspects, wherein the full-frequency bandwidth time slot used for the uplink communication or the downlink communication in the half-duplex mode corresponds to signaling for at least one of the following: a synchronization signal block (SSB), a system information block (SIB), a paging message, or a physical random access channel (PRACH).

[0107] Aspect 9: The method according to any one of the preceding aspects, wherein the configuration comprises a predetermined bandwidth or sub-band switching pattern.

[0108] Aspect 10: The method according to any one of the preceding aspects, wherein the bandwidth or the subband switching pattern does not change a bandwidth part (BWP) configured for the uplink communication and / or the downlink communication.

[0109] Aspect 11: A method according to any one of the preceding aspects, wherein the configuration comprises explicit signaling.

[0110] Aspect 12: The method according to any one of the preceding aspects, wherein the explicit signaling is dedicated to the UE.

[0111] Aspect 13: The method according to any one of aspects 1 to 11, wherein the explicit signaling is dedicated to a UE group.

[0112] Aspect 14: The method according to any one of the preceding aspects, wherein the explicit signaling is used for semi-static switching between the full frequency bandwidth time slot and the partial frequency bandwidth time slot.

[0113] Aspect 15: The method according to any one of the preceding aspects, wherein the explicit signaling is radio resource control (RRC) signaling, medium access control-control element (MAC-CE) or downlink control information (DCI) signaling.

[0114] Aspect 16: The method according to any one of aspects 1 to 13 and 15, wherein the explicit signaling is used for per-switch dynamic switching between the full frequency bandwidth time slot and the partial frequency bandwidth time slot.

[0115] Aspect 17: A method according to any one of aspects 1 to 10, wherein the configuration comprises implicit signaling.

[0116] Aspect 18: The method according to any one of aspects 1 to 10 or 17, wherein the implicit signaling is triggered by an event.

[0117] Aspect 19: The method according to any one of aspects 1 to 10, 17 or 18, wherein the event comprises a change in duplex mode.

[0118] Aspect 20: A method according to any one of Aspects 1 to 10 or 17 to 19, wherein the event includes the expiration of a timer after switching to the fallback mode without an instruction to remain in the fallback mode, and the event triggers a return from the fallback mode to the first mode.

[0119] Aspect 21: A method according to any one of the preceding aspects, wherein: the configuration of the partial frequency bandwidth time slot includes: a first parameter set specifying a first guard band size, a first uplink bandwidth size, and a first downlink bandwidth size; or a second parameter set specifying a second guard band size, a second uplink bandwidth size, and a second downlink bandwidth size, and the first parameter set is different from the second parameter set.

[0120] Aspect 22: A method according to any one of the preceding aspects, wherein a first preconfigured bandwidth mode including a first uplink bandwidth, a first guard band and / or a first downlink bandwidth in the first parameter set is different from a second preconfigured bandwidth mode including a second uplink bandwidth, a second guard band and / or a second downlink bandwidth in the second parameter set.

[0121] Aspect 23: A method for wireless communication by a network device, the method comprising: sending a configuration for switching between a full-frequency bandwidth time slot and a partial-frequency bandwidth time slot, the full-frequency bandwidth time slot being used for uplink communication or downlink communication in half-duplex mode, the partial-frequency bandwidth time slot being used for the uplink communication corresponding to the uplink subband and for downlink communication corresponding to at least one downlink subband in a subband-based base station full-duplex mode; and switching between the full-frequency bandwidth time slot and the partial-frequency bandwidth time slot according to the configuration.

[0122] Aspect 24: The method according to aspect 23, wherein the configuration includes a group common downlink control information (DCI) message.

[0123] Aspect 25: The method according to aspect 23 or 24, wherein the portion of the frequency bandwidth time slot used for downlink communication includes non-contiguous frequency sub-bands.

[0124] Aspect 26: The method according to aspect 23 or 24, wherein the portion of the frequency bandwidth time slot used for downlink communication includes a single continuous frequency sub-band.

[0125] Aspect 27: The method according to any one of aspects 23 to 26, wherein the configuration comprises a predetermined bandwidth or sub-band switching pattern.

[0126] Aspect 28: The method according to any one of Aspects 23 to 27, wherein the bandwidth or the subband switching pattern does not change a bandwidth part (BWP) configured for the uplink communication and / or the downlink communication.

[0127] Aspect 29: A method according to any one of Aspects 23 to 28, wherein the configuration comprises explicit signaling.

[0128] Aspect 30: A method according to any one of Aspects 23 to 28, wherein the configuration comprises implicit signaling.

[0129] Aspect 31: A method according to any one of aspects 23 or 25 to 30, wherein the DCI message carries the configuration for an individual UE.

[0130] Aspect 32: A method according to any one of Aspects 23 to 31, wherein the full-frequency bandwidth time slot used for the uplink communication and the downlink communication in the half-duplex mode corresponds to signaling for at least one of the following: a synchronization signal block (SSB), a system information block (SIB), paging, or a physical random access channel (PRACH).

[0131] Aspect 33: A method according to any one of aspects 23 to 32, wherein the explicit signaling is dedicated to a user equipment (UE).

[0132] Aspect 34: The method according to any one of aspects 23 to 32, wherein the explicit signaling is dedicated to a group of user equipment (UE).

[0133] Aspect 35: The method according to any one of Aspects 23 to 34, wherein the explicit signaling is used for semi-static switching between the full frequency bandwidth time slot and the partial frequency bandwidth time slot.

[0134] Aspect 36: A method according to any one of Aspects 23 to 28, 30, 31 or 32, wherein the implicit signaling is triggered by an event.

[0135] Aspect 37: A method according to any one of Aspects 23 to 36, wherein: the configuration of the partial frequency bandwidth time slot includes: a first parameter set specifying a first guard band size, a first uplink bandwidth size, and a first downlink bandwidth size; or a second parameter set specifying a second guard band size, a second uplink bandwidth size, and a second downlink bandwidth size; and the first parameter set is different from the second parameter set.

[0136] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of these aspects.

[0137] As used, the term "component" is intended to be broadly interpreted as hardware, firmware, and / or a combination of hardware and software. As used, a processor is implemented using hardware, firmware, and / or a combination of hardware and software.

[0138] Some aspects are described in conjunction with thresholds. As used, satisfying a threshold may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0139] It will be apparent that the described systems and / or methods can be implemented in various forms of hardware, firmware, and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit the aspects. Therefore, the operation and performance of these systems and / or methods are described without reference to specific software code, and it should be understood that software and hardware used to implement these systems and / or methods can be designed based at least in part on these descriptions.

[0140] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features can be combined in a manner that is not specifically set forth in the claims and / or is not disclosed in the specification. Although each dependent claim listed below may directly rely on only one claim, the disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. The phrase "at least one" mentioned in the list of items refers to any combination of those items, including a single member. For example, "at least one of a, b or c" is intended to cover a, b, c, ab, ac, bc and abc, and any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc and ccc, or any other ordering of a, b and c).

[0141] The elements, actions or instructions used should not be interpreted as critical or essential unless explicitly described as such. In addition, as used, the articles "a" and "an" are intended to include one or more items, and they can be used interchangeably with "one or more". In addition, as used, the terms "set" and "group" are intended to include one or more items (e.g., related items, unrelated items, combinations of related items and unrelated items, etc.), and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms are used. In addition, as used, the terms "having" and the like are intended to be open terms. In addition, the phrase "based on" is intended to mean "based at least in part on", unless explicitly stated otherwise.

Claims

1. A method for wireless communication by a user equipment (UE), the method include: receiving a configuration for switching between full frequency bandwidth time slots for uplink communication or downlink communication in half-duplex mode and partial frequency bandwidth time slots for uplink communication corresponding to an uplink subband or for downlink communication corresponding to at least one downlink subband in a subband-based base station full-duplex mode; as well as According to the configuration, switching is performed between the full frequency bandwidth time slot and the partial frequency bandwidth time slot.

2. The method of claim 1, wherein the configuration comprises a group common downlink control information (DCI) message.

3. The method of claim 2, wherein the DCI message carries the configuration for a UE group.

4. The method of claim 1, wherein the configuration comprises a UE-specific downlink control information (DCI) message. The method of claim 4 , wherein the DCI message carries the configuration for an individual UE.

6. The method of claim 1, wherein the portion of bandwidth time slots used for downlink communications comprises non-contiguous frequency sub-bands.

7. The method of claim 1, wherein the portion of bandwidth time slot used for downlink communications comprises a single contiguous frequency sub-band.

8. The method of claim 1, wherein the full frequency bandwidth time slot used for the uplink communication or the downlink communication in the half-duplex mode corresponds to signaling for at least one of: a synchronization signal block (SSB), a system information block (SIB), a paging message, or a physical random access channel (PRACH).

9. The method of claim 1, wherein the configuration comprises a predetermined bandwidth or sub-band switching pattern.

10. The method of claim 9, wherein the predetermined bandwidth or the sub-band switching pattern does not change a bandwidth part (BWP) configured for the uplink communication and / or the downlink communication. The method of claim 9 , wherein the configuring comprises explicit signaling.

12. The method of claim 11, wherein the explicit signaling is dedicated to the UE.

13. The method of claim 11, wherein the explicit signaling is specific to a group of UEs.

14. The method of claim 11, wherein the explicit signaling is used for semi-static switching between the full frequency bandwidth timeslot and the partial frequency bandwidth timeslot.

15. The method of claim 11, wherein the explicit signaling is radio resource control (RRC) signaling, medium access control-control element (MAC-CE), or downlink control information (DCI) signaling.

16. The method of claim 11, wherein the explicit signaling is used for per-switch dynamic switching between the full frequency bandwidth time slot and the partial frequency bandwidth time slot.

17. The method of claim 9, wherein the configuring comprises implicit signaling. The method of claim 17 , wherein the implicit signaling is triggered by an event. The method of claim 18 , wherein the event comprises a change in duplex mode.

20. The method of claim 18, wherein the event comprises expiration of a timer after switching to the fallback mode without instructions to remain in the fallback mode, the event triggering a return from the fallback mode to the first mode.

21. The method according to claim 9, in: The configuration of the partial frequency bandwidth time slot comprises: a first parameter set specifying a first guard band size, a first uplink bandwidth size, and a first downlink bandwidth size; or A second set of parameters specifying a second guard band size, a second uplink bandwidth size, and a second downlink bandwidth size, the first set of parameters being different from the second set of parameters.

22. The method of claim 21, wherein a first preconfigured bandwidth mode including a first uplink bandwidth, a first guard band and / or a first downlink bandwidth in the first parameter set is different from a second preconfigured bandwidth mode including a second uplink bandwidth, a second guard band and / or a second downlink bandwidth in the second parameter set.

23. A method for wireless communication by a network device, the method include: sending a configuration for switching between full frequency bandwidth time slots for uplink communication or downlink communication in half-duplex mode and partial frequency bandwidth time slots for uplink communication corresponding to an uplink subband and for downlink communication corresponding to at least one downlink subband in a subband-based base station full-duplex mode; as well as According to the configuration, switching is performed between the full frequency bandwidth time slot and the partial frequency bandwidth time slot.

24. The method of claim 23, wherein the configuration comprises a group common downlink control information (DCI) message.

25. The method of claim 23, wherein the portion of the frequency bandwidth time slot used for downlink communications comprises non-contiguous frequency sub-bands.

26. The method of claim 23, wherein the portion of the frequency bandwidth time slot used for downlink communications comprises a single contiguous frequency sub-band.

27. The method of claim 23, wherein the configuration comprises a predetermined bandwidth or sub-band switching pattern.

28. The method of claim 27, wherein the predetermined bandwidth or the sub-band switching pattern does not change a bandwidth part (BWP) configured for the uplink communication and / or the downlink communication.

29. The method of claim 23, wherein the configuring comprises explicit signaling.

30. The method of claim 23, wherein the configuring comprises implicit signaling.

Images