Flexible carrier aggregation methods for wireless communication devices
Dynamic frequency channel adjustments in 6G networks address the inflexibility of current CA configurations, improving spectrum efficiency and power management by adapting to traffic conditions.
Patent Information
- Application Number
- PCT/CN2025/094856
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-14
- Publication Date
- 2026-11-19
AI Technical Summary
Current 3GPP specifications lack flexibility in carrier aggregation (CA) configurations, particularly in 6G networks, which are expected to operate across a broader frequency range, leading to inefficiencies in spectrum usage and power consumption due to fixed duplexing patterns that do not adapt to dynamic traffic loads.
Implementing dynamic frequency channel changes, including altering the direction, duplexing mode, or duplexing configuration of component carriers, subbands, and bandwidth parts (BWP) through semi-static or dynamic signaling, allowing flexible carrier aggregation that adapts to traffic conditions.
Enhances spectrum efficiency and reduces power consumption by dynamically adjusting communication parameters to match traffic demands, optimizing throughput and resource utilization in 6G networks.
Smart Images

Figure CN2025094856_19112026_PF_FP_ABST
Abstract
Description
FLEXIBLE CARRIER AGGREGATION METHODS FOR WIRELESS COMMUNICATION DEVICESFIELD OF THE DISCLOSURE
[0001] This document generally describes methods and devices operating in wireless communication systems such as (but not limited to) the ones described in standard documents, known as 3rd Generation Partnership Project (3GPP) communication systems. The methods and devices are directed to managing flexible carrier aggregation (CA) .BACKGROUND
[0002] This background description is provided for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent it is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.
[0003] The 3GPP has specified a radio interface referred to as the 5G new radio (5G NR) . An architecture for a 5G NR wireless communication system includes a 5G core (5GC) network, a 5G radio access network (5G-RAN) , and at least one user equipment (5G UE) . The 3GPP is currently working on the development of 6G technical documents.
[0004] Both the 5G and 6G communication systems are expected to provide various telecommunication services (e.g., audio, video, data, messaging, holographic communication, sensing, digital twins, etc. ) based on multiple-access technologies, such as orthogonal frequency division multiple access (OFDMA) technologies, that support communication with multiple UEs. Improvements in the mobile broadband continue the progression of such wireless communication technologies. For example, CA is expected to evolve in 6G to allow for more flexibility.
[0005] CA is a technique used in cellular communication to increase user throughput and optimize spectrum usage. The CA technique refers to aggregating multiple physical carriers or component carriers to serve the same UE. Multiple features have been specified in the 5G to support more flexible CA including uplink (UL) transmission (Tx) switching, fast secondary cell (SCell) activation, cross-carrier scheduling, etc. With the introduction of a new frequency range for the 6G communication systems, additional CA flexibility, enhancement, and optimization are needed for the 6G networks to increase the spectrum efficiency and power savings.
[0006] The 6G is expected to increase the frequency range when compared to that of 5G. This change makes the CA more significant. Currently, the 5G system has a frequency range that includes two frequency ranges, FR1 and FR2. FR1 indicates the range 410 MHz to 7, 125 MHz. FR2 includes a first frequency range of 24.25 GHz to 52.6 GHz, which is labelled as FR2-1, and a second frequency range of 52.6 GHz to 71.0 GHz, which is labelled as FR2-2. FR3 is the new range to be included and supported in 6G and is from 7.125 GHz to 24.25 GHz.
[0007] The frequency range FR is used with different frequency band protocols. A frequency band is a range of frequencies in a spectrum as defined in technical specification (TS) 38.101 and TS 38.104. In the current 5G specifications, the frequency bands are classified as Frequency Division Duplex (FDD) bands and Time Division Duplex (TDD) bands. Following the introduction of Supplementary Downlink (SDL) and Supplementary Uplink (SUL) , SDL bands and SUL bands are specified. An FDD band includes at least one UL / DL carrier pair, whereas a TDD band comprises at least one bidirectional carrier. An FDD cell utilizes a UL carrier and a DL carrier from a single FDD band. A TDD cell employs a bidirectional carrier within a single TDD band. When the SUL is configured, a serving cell (FDD or TDD) includes at most one SUL carrier. A cell may be configured with only a DL carrier. However, current 3GPP specifications do not allow configurations with more flexible CA.SUMMARY
[0008] According to various embodiments, the CA flexibility may be enhanced by dynamically changing a feature or characteristic related to using a frequency channel. The feature may be one of a direction, a duplexing mode, or a duplexing configuration. The frequency channel may be a component carrier, a logical carrier, a subband, or a bandwidth part (BWP) . The feature is dynamically changed in the sense that, after communication between the UE and a network entity (NE) has occurred based on a configured frequency channel, either the UE or the NE determines to change the feature of the frequency channel based on a condition or a measurement using dynamic signaling. Then, the UE and NE communicate based on the modified frequency channel.
[0009] In one embodiment, the UE or the NE changes either an UL or a downlink (DL) direction of the communication. In another embodiment, the feature change is associated with a duplexing configuration. The duplexing configuration defines a duplexing mode, the size of a subband full duplex (SBFD) subband, and / or parts of a spectrum of the frequency channel to be switched on or off. The duplexing mode corresponds to one of a full frequency duplex mode, a non-overlapping SBFD mode, or an overlapping SBFD mode.
[0010] In one embodiment, a logical carrier is associated with one or more physical carriers, which have a non-contiguous spectrum. Thus, the NE may schedule resources for the logical carrier (which is associated with a non-contiguous spectrum) . For this embodiment, the NE may perform dynamic carrier aggregation as the physical carriers (or portions / subbands of the physical carriers or groups of physical resource blocks) are mapped to the logical carrier and the logical carrier may be changed flexibly and potentially without a radio resource control (RRC) reconfiguration.BRIEF DESCRIPTION OF THE DRAWINGS
[0011] FIG. 1A is a block diagram of an example system having an NE and a UE that can implement the techniques of this disclosure related to dynamically changing a feature of a frequency channel used by the NE and UE for communication.
[0012] FIG. 1B is a block diagram of an example protocol stack for UEs and NEs as shown in FIG. 1A.
[0013] FIG. 2A is a flow chart illustrating a method performed by the NE for dynamically changing a feature of a frequency channel used for communication between the NE and UE according to an embodiment.
[0014] FIG. 2B is a flow chart illustrating a method performed by the UE for dynamically changing a feature of a frequency channel used for communication between the NE and UE according to an embodiment.
[0015] FIG. 3A is a signal diagram that illustrates a method for dynamically changing a UL carrier into a DL carrier for communication between the NE and UE according to an embodiment.
[0016] FIG. 3B is a signal diagram that illustrates a method for dynamically changing a DL carrier into a UL carrier for communication between the NE and UE according to an embodiment.
[0017] FIG. 3C is a signal diagram that illustrates a method for dynamically changing a duplexing configuration used for communication between the NE and UE according to an embodiment.
[0018] FIG. 3D is another signal diagram that illustrates a method for dynamically changing a duplexing configuration used for communication between the NE and UE according to an embodiment.
[0019] FIG. 3E is a signal diagram that illustrates a method for dynamically changing a UL subband into a DL subband for communication between the NE and UE according to an embodiment.
[0020] FIG. 3F is a signal diagram that illustrates a method for dynamically changing a DL subband into a UL subband for communication between the NE and UE according to an embodiment.
[0021] FIG. 3G is a schematic diagram of a flexible frequency selection for a serving cell according to an embodiment.
[0022] FIG. 3H is a schematic diagram of another flexible frequency selection for a serving cell according to an embodiment.
[0023] FIGs. 4A and 4B schematically illustrate switching a UL subband to a DL subband according to an embodiment.
[0024] FIGs. 4C and 4D schematically illustrate switching a DL subband to a UL subband according to an embodiment.
[0025] FIGs. 4E and 4F schematically illustrate switching off parts of a carrier spectrum according to an embodiment.
[0026] FIG. 5 is a signal diagram illustrating a configuration of a logical carrier and dynamic updating a mapping of the logical carrier according to an embodiment.
[0027] FIG. 6 schematically illustrates an example mapping between logical resources of the logical carrier and physical resources of component carriers. DETAILED DESCRIPTION OF THE EMBODIMENTS
[0028] Methods and devices described in this section embody techniques related to CA flexibility, which enable optimized spectrum usage by overcoming the TDD restriction of a fixed pattern, which may not align with dynamic traffic load changes in either direction. In the case of multiple carriers, this flexibility is relevant when the UE specific primary carrier is congested, experiences poor channel conditions, or lacks sufficient bandwidth to support the traffic demands in a particular direction. Also, these techniques are relevant to adjust subbands directions in full duplex scenarios (e.g., SBFD) depending on traffic, interference, or other conditions.
[0029] In one embodiment, a carrier direction (e.g., DL, UL, frequency duplexing (like overlapping / non-overlapping SBFD) , or any other type of duplexing) , a BWP direction or a subband direction may be configured by the NE, for the UE, via semi-static signaling (e.g., RRC) or signaled via dynamic signaling (downlink control information (DCI) , medium access control-control element (MAC-CE) , or other protocol layer lower than the RRC protocol layer. The support for a flexible frequency channel (e.g., carrier direction, where the carrier may be a component carrier or logical carrier or both, flexible BWP direction, flexible subbands directions / sizes, or flexible duplexing patterns or configurations) , may be reflected in the UE capabilities. This means that the UE reports to the NE its capability to support any of these feature changes. The UE may report on which carriers, BWPs, or subbands the flexible direction / sizes is supported. Various scenarios are possible for supporting the flexible frequency channel.
[0030] Prior to discussing these possible scenarios, a wireless communication system 100 that supports a flexible frequency channel is introduced, as illustrated in FIG. 1A. The wireless communication system 100 includes a UE 102, a first NE 104 (in this case, the NE may be a base station (BS) ) , a second NE 106, and a core network (CN) 110. The NE may be associated with a radio access network (RAN) node, a part of a RAN node, a functionality of the CN, or a combination of these elements. The CN 110 may be or include an evolved packet core (EPC) 111, a 5G core (5GC) 160, and / or a 6G core (6GC) 180. The first NE 104 may be an evolved NodeB (eNB) supporting an S1 interface for communicating with the EPC 111, a next generation eNB (ng-eNB) supporting an NG interface for communicating with the 5GC 160, or a gNodeB (gNB) that supports an NR radio interface as well as an NG interface for communicating with the 5GC 160. The first NE 104 may also be an 6G BS supporting the NG interface, a new NG interface, or a 6G BS-to-CN (e.g., N6G) interface for communicating with the 5GC 160 or the 6GC 180. In one embodiment, the first NE 104 is a distributed RAN node, i.e., it includes a centralized unit (not shown) and a distributed unit (not shown) .
[0031] To directly exchange messages with each other during the scenarios discussed below, the NEs 104 and 106 may support an X2, Xn, new Xn, or 6G BS-to-BS (e.g., X6G) interface (s) . Among other components, the EPC 111 may include a Serving Gateway (SGW) 112, a Mobility Management Entity (MME) 114, and a Packet Data Network Gateway (PGW) 116. The SGW 112 is generally configured to transfer user-plane packets related to audio calls, video calls, Internet traffic, etc., and the MME 114 is configured to manage authentication, registration, paging, and other related functions. The PGW 116 provides connectivity from the UE to one or more external packet data networks, e.g., an Internet network and / or an Internet Protocol (IP) Multimedia Subsystem (IMS) network.
[0032] The 5GC 160 includes a User Plane Function (UPF) 162, an Access and Mobility Management (AMF) 164, and / or a Session Management Function (SMF) 166. The UPF 162 is generally configured to transfer user-plane packets related to audio calls, video calls, Internet traffic, etc., the AMF 164 is configured to manage authentication, registration, paging, and other related functions, and the SMF 166 is configured to manage PDU sessions. The 6GC 180 includes a 6G UPF 182, a 6G AMF 184, and / or 6G SMF 186, similar to the UPF 162, the AMF 164, and the SMF 176, respectively, but with enhanced functions.
[0033] As illustrated in FIG. 1A, the first NE 104 supports a cell 124 (may support more cells, but only one is shown for simplicity) , and the second NE 106 supports a cell 126 (may support more cells) . The cells 124 and / or 126 may operate on the same carrier frequency or different carrier frequencies. For example, the cell 126 may operate on a DL carrier frequency f1 and the cell 124 may operate on the DL carrier frequency f1. In cases where the cells 124 and / or 126 operate in a time division duplex (TDD) mode, the cells 124 and / or 126 operate in UL carrier frequencies same as the DL carrier frequencies. In cases where the cells 124 and / or 126 operate in a frequency division duplex (FDD) mode, the cells 124 and / or 126 operate in UL carrier frequencies different from the DL carrier frequencies. The cells 124 and 126 may partially overlap to provide seamless service continuity. Thus, while the UE 102 may move among the cells 124 and 126, the UE 102 still communicates with the CN 110 via at least one of these cells. In some other scenarios, the UE may communicate in CA with the first NE 104, i.e., the UE and the first NE use (simultaneously or not) two different carriers 128 and 129 having different frequencies.
[0034] The wireless communication network 100 may include any suitable number of NEs supporting 6G cells, NR cells, and / or EUTRA cells. More particularly, the EPC 111 may be connected to any suitable number of NEs supporting EUTRA cells, while the 5GC 160 and / or the 6GC 180 may be connected to any suitable number of NEs supporting 6G cells and / or NR cells. Although the examples below refer to specific CN types (EPC, 5GC, 6GC) and radio access technologies (RAT) types (6G, 5G NR and EUTRA) , in general, the techniques of this disclosure also may apply to other suitable radio access and / or core network technologies such as seventh generation (7G) radio access and / or 7G core network.
[0035] With continued reference to FIG. 1A, the first NE 104 is equipped with processing hardware 130 that includes one or more general-purpose processors (e.g., CPUs) and a non-transitory computer-readable memory (CRM) storing instructions that the one or more general-purpose processors execute. Additionally or alternatively, the processing hardware 130 may include special-purpose processing units. According to an embodiment illustrated in FIG. 1A, the processing hardware 130 includes a processor 132 to process data that the first NE 104 transmits in the DL direction, or data that the first NE 104 receives in the UL direction. The processing hardware 130 also includes a transceiver 134 configured to transmit data in the DL direction and to receive data in the UL direction. The processing hardware 136 also includes a CA manager 136 configured to CA communication with the UE (s) . The CRM 138 stores executable codes for the processor 132 to perform methods according to embodiments described in this section. The second NE 106 includes generally similar components. In particular, components 140, 142, 144, 146, and 148 of the second NE 106 may be similar to the components 130, 132, 134, 136, and 138, respectively.
[0036] The UE 102 is equipped with processing hardware 150 that may include one or more general-purpose processors such as CPUs and non-transitory CRM storing machine-readable instructions executable on the one or more general-purpose processors, and / or special-purpose processing units. As schematically illustrated in FIG. 1A, the processing hardware 150 includes a processor 152 to prepare data that the UE 102 transmits in the UL direction, or to process data that the UE 102 receives in the DL direction. The processing hardware 150 also includes a transceiver 154 configured to transmit data in the UL direction and to receive data in the DL direction. The processing hardware 150 further includes a CA manager 156 configured to manage changes of the frequency channel used by the CA. The processing hardware 150 also includes a CRM 158 that stores executable codes for the processor 152 to perform methods according to embodiments described in this section.
[0037] FIG. 1B illustrates, in a simplified manner, an example protocol stack 190 according to which the UE 102 may communicate with a 6gNB (e.g., NE 104) and / or a gNB (e.g., NE 106) . In the example stack 190, an NR physical layer (PHY) 191B provides transport channels to a NR MAC sublayer 192B, which in turn provides logical channels to a NR RLC sublayer 193B. The NR RLC sublayer 193B in turn provides data transfer services to an NR PDCP sublayer 194B. The NR PDCP sublayer 194B in turn may provide data transfer services to a Service Data Adaptation Protocol (SDAP) 195B sublayer and / or an RRC sublayer 196B. Similarly, a 6G PHY 191A provides transport channels to a 6G MAC sublayer 192A, which in turn provides logical channels to the 6G RLC sublayer 193A. The 6G RLC sublayer 193A in turn provides RLC channels to a 6G PDCP sublayer 194A. The 6G PDCP sublayer 194A in turn may provide data transfer services to a 6G SDAP sublayer 195A or a 6G RRC sublayer 196A. In some embodiments, the 6G SDAP sublayer 195A may be omitted. In such cases, the PDCP sublayer 194A may support functionalities of the SDAP sublayer 195A. The UE 102, in some embodiments, supports both the 6G and the NR stack as shown in FIG. 1B. This means that the UE is capable of supporting handover between 6G and NR BSs and / or supporting dual connectivity (DC) over 6G and NR interfaces.
[0038] The 6G PDCP sublayer 194A and the NR PDCP sublayer 194B receive packets (e.g., from an Internet Protocol (IP) layer, layered directly or indirectly over the PDCP layer 194A or 194B) that may be referred to as service data units (SDUs) , and output packets (e.g., to the RLC layer 193A or 193B) that may be referred to as protocol data units (PDUs) . Except where the difference between SDUs and PDUs is relevant, this document, for simplicity, refers to both SDUs and PDUs as “packets. ”
[0039] In one embodiment, on a control plane, the 6G PDCP sublayer 193A and the NR PDCP sublayer 193B may provide services to the RRC sublayer 196A and the RRC sublayer 196B to exchange RRC messages or non-access-stratum (NAS) messages, respectively. On a user plane, the 6G PDCP sublayer 194A and the NR PDCP sublayer 194B may provide services to the SDAP 195A and the SDAP 195B to support a data exchange, respectively. In some embodiments, the 6G PDCP sublayer 194A and the NR PDCP sublayer 194B may provide services to upper layer (s) (e.g., Internet Protocol (IP) layer or Ethernet layer) to support a data exchange. The services may include data transfer services, integrity protection, ciphering, header compression, and / or data compression. Data exchanged on the 6G PDCP sublayer 194A and NR PDCP sublayer 194B may be SDAP PDUs, IP packets, or Ethernet packets.
[0040] FIG. 2A shows a method 200A for wireless communication performed by a NE (for example, NE 104) with a UE (for example, UE 102) in which a frequency channel is flexible (i.e., may be modified, changed, adjusted) . The method 200A starts by optionally receiving 202A a UE capability information indicating support for adjustment of at least one of a communication direction or duplexing configuration of a frequency channel. As previously discussed, the frequency channel is understood in this embodiment to be at least one of: a component carrier, a subband, a BWP, or a logical carrier.
[0041] The NE transmits 203A, to the UE 102, via first signaling (e.g., RRC message) associated with a first protocol layer (e.g., the RRC layer) , a configuration for the frequency channel. Then, the NE transmits 210A to the UE 102, via second signaling (e.g., DCI or MAC-CE) associated with a second protocol layer (e.g., PHY or MAC layer) , lower than the first protocol layer (see FIG. 1B) , an indication for changing at least one of a transmission direction or a duplexing configuration of the frequency channel. After the indication is transmitted, the NE communicates 216A with the UE on the frequency channel based on the indication. When the NE uses CA communication with the UE, the NE may also communicate 214A on the frequency channel without the indication, i.e., the NE communicates with the UE on the original frequency channel and on the changed frequency channel. For the CA communication, the NE may simultaneously communicate with the UE on the original frequency channel and the changed frequency channel.
[0042] In one embodiment, the indication for changing the transmission direction of the frequency channel corresponds to at least one of: switching the transmission direction of a component carrier from an UL direction to a DL direction, switching the transmission direction of the component carrier from the DL direction to the UL direction, switching the transmission direction of one or more subbands of the frequency channel from the DL direction to the UL direction, or switching the transmission direction of the one or more subbands of the frequency channel from the UL direction to the DL direction. These possibilities are discussed later with regard to FIGs. 3A, 3B, 3E, and 3F.
[0043] In another embodiment, the indication for changing the duplexing configuration of the frequency channel corresponds to at least one of: changing a duplexing mode to at least one of a full frequency duplex mode, a non-overlapping subband full duplex, SBFD mode, or an overlapping SBFD mode, changing a size of one or more SBFD UL subbands, changing a size of one or more SBFD DL subbands, or switching on or off parts of a spectrum of the frequency channel. These possibilities are discussed later with regard to FIGs. 3C, 3D, and 4A to 4F.
[0044] The method 200A may further include transmitting an updated logical carrier which remaps a logical resource of the logical carrier to a physical resource of one or more component carriers. This step is later discussed in more detail with regard to FIGs. 5 and 6. The transmitting of the indication in any of these embodiments is triggered by detecting a DL condition associated with an amount of traffic or buffering.
[0045] In one embodiment, which is discussed later with regard to FIG. 3G, the configuration for the frequency channel includes a first list of DL frequency channels, a second list of UL frequency channels, a first list of DL BWPs, associated with the first list of DL frequency channels, and a second list of UL BWPs associated with the second list of UL frequency channels. The indication indicates at least one of: a DL carrier among the first list of DL frequency channels or an UL carrier among the second list of UL frequency channels.
[0046] In another embodiment, which is discussed later with regard to FIG. 3H, the configuration for the frequency channel includes a plurality of DL BWPs, and a plurality of UL BWPs, each DL BWP being associated with DL frequency channel information and each UL BWP being associated with UL frequency channel information, and the indication indicates at least one of: a switch to a first DL BWP among the plurality of DL BWPs or a first UL BWP among the plurality of UL BWPs, an activation of a second DL BWP among the plurality of DL BWPs or a second UL BWP among the plurality of UL BWPs, or a deactivation of a third DL BWP among the plurality of DL BWPs or a third UL BWP among the plurality of UL BWPs.
[0047] FIG. 2A illustrates the application of the flexible frequency channel to a communication method 200A performed by the NE. The same flexible frequency channel capability, when performed by the UE in a method 200B, is illustrated in FIG. 2B.The method 200B is performed by the UE (e.g., UE 102) and starts, by optionally providing 202B UE capability information indicating support for adjustment of at least one of a transmission direction or duplexing configuration. The UE receives 203B, from a NE (e.g., NE 104) via first signaling (e.g., RRC message) associated with a first protocol layer (e.g., RRC layer) a configuration for a frequency channel, which, as discussed above with regard to the method 200A, may be at least one of a component carrier, a subband, a BWP, or a logical carrier.
[0048] The UE receives 210B from the NE, via second signaling (e.g., DCI or MAC-CE) associated with a second protocol layer (e.g., PHY or MAC layer) lower than the first protocol layer, an indication for changing at least one of the transmission direction or the duplexing configuration of the frequency channel. The UE communicates 216B with the NE on the frequency channel based on the indication. The UE may also communicate 214B with the NE on the frequency channel without the indication (e.g., based on the original frequency channel, not adjusted as indicated by the indication) . The communications 216B and 214B may happen simultaneously for FDD CA communication.
[0049] In one embodiment, the indication for changing the transmission direction of the frequency channel corresponds to at least one of: switching the transmission direction of a component carrier from an UL direction to a DL direction, switching the transmission direction of the component carrier from the DL direction to the UL direction, switching the transmission direction of one or more subbands of the frequency channel from the UL direction to the DL direction, or switching the transmission direction of the one or more subbands of the frequency channel from the DL direction to the UL direction, as discussed later with regard to FIGs. 3A, 3B, 3E, and 3F.
[0050] In one embodiment, the indication for changing the duplexing configuration of the frequency channel corresponds to at least one of: changing a duplexing mode to at least one of a full frequency duplex mode, a non-overlapping SBFD mode, or an overlapping SBFD mode, changing a size of one or more SBFD UL subbands, changing a size of one or more SBFD DL subbands, or switching on or off parts of a spectrum of the frequency channel, as discussed later with regard to FIGs. 3C, 3D, and 4A to 4F.
[0051] In one embodiment, the logical carrier is mapped to one or more component carriers (see discussion of FIG. 6) , which covers a non-contiguous spectrum. For this embodiment, the UE receives an updated mapping which remaps a logical resource of the logical carrier to a physical resource of one or more component carriers, as discussed later with regard to FIG. 5.
[0052] For the above embodiments associated with method 200B, the receiving the indication is triggered by detecting a UL condition associated with an amount of traffic or buffering.
[0053] In one embodiment, the configuration for the frequency channel includes a first list of DL frequency channels, a second list of UL frequency channels, a first list of DL BWPs, associated with the first list of DL frequency channels, and a second list of UL BWPs associated with the second list of UL frequency channels. The indication indicates at least one of: a DL carrier among the first list of DL frequency channels or an UL carrier among the second list of UL frequency channels. This embodiment is discussed later in more detail with regard to FIG. 3G.
[0054] In one embodiment, the configuration for the frequency channel includes a plurality of DL BWPs, and a plurality of UL BWPs, each DL BWP being associated with DL frequency channel information and each UL BWP being associated with UL frequency channel information. The indication indicates at least one of: a switch to a first DL BWP among the plurality of DL BWPs or a first UL BWP among the plurality of UL BWPs, an activation of a second DL BWP among the plurality of DL BWPs or a second UL BWP among the plurality of UL BWPs, or a deactivation of a third DL BWP among the plurality of DL BWPs or a third UL BWP among the plurality of UL BWPs. This embodiment is discussed later in more detail with regard to FIG. 3H.
[0055] Various scenarios of the methods 200A and 200B are discussed with regard to FIGs. 3A to 3H. FIG. 3A illustrates a method 300A in which a communication direction of a component carrier (or a logical carrier) is changed. Note that although some of the figures refer to a “carrier, ” this term is understood in these embodiments to mean a physical carrier or a logical carrier. In some of these embodiments, the methods may use a combination of physical and logical carriers. For example, when a figure refers to “carrier 1” and “carrier 2, ” each of these carriers may be a physical carrier or a logical carrier.
[0056] The method 300A starts with the NE 104 transmitting 301A a UE capability enquiry message to the UE 102. The UE 102 responds by transmitting 302A the UE capability information to the NE 104. The capability information may explicitly indicate whether the UE 102 supports flexible frequency channel, e.g., carrier direction operation. The capability information may also specify support for such operation on one or more particular carriers of the supported / configured carriers, such as "carrier 2" in this scenario. If the NE and UE use multiple carriers, for example, carrier 1 and carrier 2 as in the method 300A (i.e., for CA operation) , only one carrier may be flexible, not both of them. In other words, the method 300A works when at least one carrier of the plural carriers that are used by the NE and UE is flexible.
[0057] The NE 104 transmits 303A an RRC message (e.g., RRC (re-) configuration message) to the UE 102. This message (re-) configures the UE parameters including (re-) configuring at least "carrier 2" as a "flexible carrier. " Configuring a carrier as “flexible” indicates that its transmission direction (e.g., UL / DL) is not fixed but may be switched dynamically (e.g., via DCI or MAC-CE messages) or semi-statically (e.g., via RRC) based on subsequent signaling or predefined conditions. The transmitted configuration may configure an initial transmission direction for carrier 2 (e.g., UL, as in this scenario) . The UE may reply 304A to the RRC (re-) configuration message with a message indicating that the RRC reconfiguration is complete. Following the RRC (re-) configuration, the UE 102 and NE 104 may start an operational phase. During this phase, transmissions may occur on multiple carriers (i.e., CA communication) .
[0058] For example, the NE 104 may schedule 305A DL data on a first carrier (carrier 1) using DCI carrying a DL assignment, which is followed by the transmission 306A of the corresponding DL data (e.g., physical downlink shared channel (PDSCH) ) on carrier 1. Concurrently or subsequently, the NE 104 may schedule 307A UL data transmissions for the UE 102 on the flexible carrier 2, via DCI carrying an UL grant. The DCI carrying the UL grant may be transmitted 307A on another carrier, e.g., carrier 1. Then, the UE 102 transmits 308A UL data (e.g., physical uplink shared channel (PUSCH) ) to the NE 104 on carrier 2. For this UL data transmission, the UE operates the carrier 2 in its configured initial UL direction.
[0059] At any time during the data communication or after the data communication is completed, the NE 104 determines 309A that a specific trigger condition is met. This trigger condition indicates the need to change the transmission direction of the flexible carrier 2. Some of the possible trigger conditions may include the NE 104 detecting sustained heavy DL traffic load, observing DL data buffers exceeding a certain threshold, receiving feedback from the UE 102 (e.g., regarding channel conditions) , or any other network optimization criteria. Based on this determination, the NE transmits 310A signaling to the UE 102 instructing a switch in the transmission direction of carrier 2, from the current UL direction to a DL direction. In some embodiments, the NE 104 may transmit one common signaling or multiple separate signaling to the UE 102 instructing a switch in the transmission direction of multiple carriers from the UL direction to the DL direction. This signaling may be conveyed via RRC, MAC-CE, or DCI or any other types of signaling.
[0060] In an alternative embodiment, the UE 102 determines 309B to change the transmission direction of the carrier 2. For this embodiment, step 309A is not present and step 310A has a reversed direction, i.e., the UE signals to the NE the direction switching for the carrier 2. Also, the NE may transmit an acknowledgement (ACK) signal to the UE to confirm the direction switching for the carrier 2. In yet another embodiment, the UE determines 309B to support the determination 309A of the NE, i.e., the UE informs the NE that a direction change for the carrier 2 is recommended, but the NE makes 309A the actual determination to change the carrier’s direction.
[0061] The UE 102 may transmit 311A an acknowledgement (ACK) signal to the NE to confirm the successful reception of the direction switching instruction indicated in step 310A. After receiving the switching instruction, the UE 102 may perform 312A an internal calibration / reconfiguration / activation of its relevant components, such as its radio frequency (RF) transceiver chain and baseband processing units associated with carrier 2. This reconfiguration prepares the UE 102 to deactivate UL transmissions for carrier 2 and start receiving DL transmissions on carrier 2. After this reconfiguration process, a new communication phase with the changed direction of carrier 2 starts. The NE 104 may continue scheduling 313A and transmitting 314A the DL data on carrier 1. In addition, the NE 104 schedules 315A DL data on carrier 2 via DCI and transmits 316A the corresponding DL data to the UE 102 on carrier 2. Therefore, carrier 2 is now utilized for DL transmissions (instead of UL transmission 308A) and as a result, the overall DL throughput available to the UE 102 is increased.
[0062] FIG. 3B illustrates a method 300B in which the UL traffic is heavy, and thus, the NE (or UE) determines to change the DL communication direction for carrier 1 (step 306A) to UL (step 314B) . All the steps in method 300B that have the same reference numbers as the steps in method 300A are similar, and thus, their description is omitted in this embodiment. Different from method 300A, the UE in method 300B determines 317B when to change the communication direction of carrier 1, from DL to UL. The UE trigger in this case is a heavy UL traffic, high UL buffering, etc. Optionally, the NE may make 317A the decision to switch the DL direction of the carrier 1 to the UL direction, or, the NE may support the decision 317B of the UE. Also different from method 300A is that the UE requests 314B the NE to switch the communication direction of carrier 1 from DL to UL and the NE approves 310B the direction switch. Also, because both carriers 1 and 2 become UL carriers, the UL data scheduling 313B for carrier 1 and the UL data scheduling 315B for carrier 2 take place before changing the communication direction. In one embodiment, the UL data scheduling 313B and 315B may be omitted if the UE is configured with UL resources (e.g., configured grants) prior to the direction change to handle UL data.
[0063] FIG. 3C illustrates a method 300C in which the NE determines 309A to change (decrease) the size of one or more UL subbands for an SBFD mode. The SBFD mode is a duplexing scheme that allows simultaneous transmission and reception of data on non-overlapping frequency resources or subbands within the same TDD carrier. The size of UL and DL subbands of the SBFD may be changed by the NE (or UE or both) to accommodate the need for more UL or DL traffic. Steps 310C to 316C are similar to steps 310A to 316A in the method 300A except that, instead of changing the communication direction of a carrier, the size of one or more subbands is changed. Similar to the method 300A, the UE may make 309B the determination to adjust the subband size, or the UE may assist the NE to make this determination.
[0064] FIG. 3D illustrates a method 300D similar to method 300C, except that, in this method, the UE determines 317B to increase the size of the one or more SBFD UL subbands. Because the UE makes this determination, the UE requests 314D the NE to approve the increase, and the NE responds 310D with an approval of the increase. As in the previous methods, this method may be modified so that the NE makes 317A the determination to increase the size of the one or more SBFD UL subbands, or the NE may assist the UE in making this determination.
[0065] FIG. 3E illustrates a method 300E in which a communication direction of one or more SBFD subbands is changed, from UL to DL, based on a determination 309A made by the NE. As discussed for the previous methods, in one variation of this method, the UE makes the determination 309B or the UE assists the NE in making the determination 309A. All other steps in FIG. 3E are similar to the steps in FIG. 3C except that instead of changing the size of the subband, the communication direction of the subband is changed.
[0066] FIG. 3F illustrates a method 300F in which a communication direction of one or more SBFD subbands is changed, from DL to UL, based on a determination 317A made by the NE. As discussed for the previous methods, in one variation of this method, the UE makes the determination 317B or the UE assists the NE in making the determination 317A. All other steps in FIG. 3F are similar to the steps in FIG. 3E except that instead of changing the UL direction to the DL direction for one or more subbands, the direction is changed from DL to UL for those subbands.
[0067] One skilled in the art would understand that it is possible to combine the various methods discussed with regard to FIGs. 3A to 3F so that in one embodiment, both the communication direction of the subband and the size of that subband may be changed, or the communication direction of a carrier is changed and the size of one or more of the SBFD subbands is changed.
[0068] In one embodiment, which may be combined with any of the embodiments associated with FIGs. 3A to 3F, a new RRC parameter, a new DCI bit-field, or a new MAC-CE field may be specified / signaled to indicate the UL / DL direction of one or multiple carriers, or / and BWPs, or / and subbands. In one embodiment, a bitmap may be used for the signaling to indicate the directions, if the indication is for more than one carrier / BWP / subband.
[0069] In one embodiment, which is illustrated in FIG. 3G, an RRC parameter may configure a list of frequency information, e.g., frequencyDL-list for DL for a serving cell 124, and an RRC parameter or the same parameter may configure another list of frequency information e.g., frequencyUL-list for UL for a serving cell. In other words, the NE may configure a set of DL carriers 332 and a set of UL carriers 336, 338 and the NE may dynamically indicate to the UE one or a pair of the pre-configured UL / DL carriers (332 and 338 for the case illustrated in FIG. 3G) . The NE may indicate to the UE (e.g., via DCI or via MAC-CE) one of the configured UL / DL frequency information (332 and 338) . Before the dynamic indication, a default frequency information may be configured or used for frequency information for the serving cell.
[0070] The NE may configure the BWPs associated with different carrier frequency configurations. For example, a list of DL BWP 330 (e.g., DL BWB list 1, DL BWP list 2, etc. ) is associated with a DL frequency information 332 (e.g., DL Carrier Frequency Information 1, DL Carrier Frequency Information 2, etc. ) . A list of UL BWP 334 (e.g., UL BWB list 1, UL BWP list 2, etc. ) is associated with a UL carrier frequency information 336 (e.g., UL Carrier Frequency Information 1, UL Carrier Frequency Information 2, etc. ) . Alternatively, the NE may configure multiple frequency starting points and / or bandwidth in a BWP, which are one-to-one associated with the configured carrier frequency information. When the carrier frequency information is updated (e.g., indicated / activated / deactivated) , the NE and UE switches the BWP or applies the corresponding configured frequency starting point and / or bandwidth for the configured or activated BWP (s) . Figure 3G illustrates one example for the flexible frequency selection for a serving cell.
[0071] In one embodiment, the DCI / MAC-CE indicating the communication direction may be used for other functionalities, e.g., SCell activation / deactivation, BWP switching, or SBFD activation / deactivation.
[0072] In another embodiment, the indication of the UL / DL direction may be handled through BWP switching / activation / deactivation or BWP and serving cell association, and the NE configures the carrier frequency information, e.g., frequencyDL or frequencyUL for the DL BWP 340 or UL BWP 344, respectively, as illustrated in FIG. 3H. For example, the UE may be configured by the NE with a set of DL BWPs 340 and a set of UL BWPs 344. Each BWP configuration includes frequency-domain parameters, such as the carrier frequency. Currently, the frequency-domain parameters are configured at a serving cell level and not at the BWP level. Accordingly, the switching of the BWP includes the switching of the frequency-domain parameters (e.g., carrier frequency) . This change would make the system benefit from re-using the BWP switching mechanisms, which is dynamic, and the switching may be performed via DCI or MAC-CE or via timers to also switch the frequency-domain parameters, which includes selecting, for example, a BWP on a different carrier.
[0073] The NE configures the frequency domain starting point and the bandwidth for the BWP based on the configured carrier frequency information for the BWP. Subsequently, the NE activates one or more configured DL and / or UL BWPs (342, 346) for operation within a serving cell 124. Thus, BWPs are configured independently, incorporating their respective frequency parameters, and may be associated with a serving cell through semi-static or dynamic signaling. A BWP may be associated with one or multiple serving cells. One DL BWP and one UL BWP associated with a serving cell may be from same frequency band or from different frequency bands and are associated with the same serving cell.
[0074] A serving cell, e.g., secondary cell, may have one active DL BWP only or one active UL BWP only (not necessarily both DL BWP and UL BWP both active) , where the serving cell may be an activated serving cell. In one example, the NE may deactivate all the UL BWPs or deactivate all the DL BWPs for an activated serving cell. In some embodiments, the NE may refrain from deactivating all DL BWP or deactivating all UL BWP for a primary cell (PCell) or primary secondary cell (PSCell) . In some embodiments, the NE may configure the carrier frequency information in the serving cell configuration, and for a BWP without the carrier frequency information configured, the NE and UE may determine the carrier frequency information for the BWP is the same as the carrier frequency information configured in the serving cell configuration. The above description may include the initial BWP. Figure 3H illustrates one example for the flexible frequency selection for a serving cell based on BWP switching.
[0075] In one embodiment, the UE may require a specific processing time to implement a reconfiguration (312A to 312F) of the UL / DL direction for one or more carriers or BWPs or duplexing subbands. This processing time requirement can be communicated to the NE by the UE as part of its capability information (301A to 301F) . The UE is expected to apply the newly indicated UL / DL direction for the affected carrier (s) or BWP (s) or duplexing subband (s) once this processing period has elapsed. The processing time may be measured from a defined point relative to the reception (e.g., 310A, 310B, 310E, and 310F) of the signaling that indicates the direction change (e.g., end of last symbol of PDCCH or end of the last symbol of the PUSCH / PUCCH for the acknowledgement of the corresponding control signaling) . In some embodiments, the NE and UE may determine the processing time or delay for the activation / deactivation for the BWPs based on whether the carrier frequency information for the new activated BWP is the same or different as a current active BWP.
[0076] In one embodiment, the configuration of the UL / DL direction may be semi-persistent. This means that the UE is instructed by the NE via dynamic signaling (e.g., DCI or MAC-CE, etc. ) or semi-static signaling (e.g., RRC, etc. ) to change the transmission direction for one or more carrier (s) and / or BWP (s) for a specific duration, after which the UE reverts to the previous or a default configuration of the UL / DL direction.
[0077] A change of UL / DL direction for one or multiple carrier (s) and / or BWP (s) may be indicated by the NE to one or multiple UE (s) for a specific time duration, e.g., for one or multiple time slot (s) , subframe (s) / frame (s) , symbol (s) , for a specific time duration in milliseconds or for any durations specified or indicated to the UE. The indicated time can be contiguous or non-contiguous. For example, the UE may be indicated to switch an UL carrier to DL to receive large bursts of extended reality (XR) traffic and then switch it back to UL after the end of the burst. The UE may also send a request to the NE (e.g., a specific data rate is needed for a specific period of time for a specific service, a specific spectrum width is needed for a specific period of time for a specific service, etc. ) or a need for reliable link for a specific service (e.g., ultra-reliable low latency communication (URLLC) service) . The NE may configure the UE with additional carriers as needed or the NE can adjust the direction / duplexing of the existing carriers.
[0078] The UL / DL direction for sections, portions, or subbands of a communication carrier (or a logic carrier) may be switched. A carrier may be partitioned into frequency portions (e.g., including a specific number of resource blocks (RBs) or RB groups (RBGs) ) or into one or more subbands. The transmission direction assigned to these portions or subbands may subsequently be switched between DL and UL. This flexible capability of the frequency channel may also include a duplexing configuration, for example, other duplexing modes, including, for instance, non-overlapping SBFD, overlapping SBFD, or full frequency duplex. As an illustration, a subband direction may be switched from 'DL only' to full duplex (permitting simultaneous DL and UL transmission) , or similarly from 'UL only' to full duplex. A bitmap may be utilized for signaling to the NE the designated direction, where each bit corresponds to a particular subband. For example, a bit set to '1' could denote the DL direction, whilst a bit set to '0' indicates the UL direction. The signaling mechanism itself may be semi-static (e.g., via RRC) or dynamic (e.g., via DCI or MAC-CE) . The specific bit-field (s) used to indicate the subband direction (s) can be specified or configured for particular DCI formats (e.g., 0_0, 0_1, 1_0, 1_1, 2_0, 2_1, etc. ) .
[0079] In this respect, FIG. 4A illustrates a configuration 400A of slots in the time-frequency domain (with the X axis being the time and the Y axis being the frequency) in which the NE transmits a DCI or MAC-CE 402A indicating the switching of the direction of the UL subbands 1 and 2 (of a TDD / SBFD pattern) to DL. FIG. 4B illustrates the UL subbands 1 and 2 being changed to DL subbands 1 and 2, while UL subband 3 is not changed. FIG. 4C illustrates a configuration 400C in which the NE transmits a DCI or MAC-CE 402C for changing DL subbands 1 to 3 (of a TDD / SBFD pattern) to UL subbands 1 to 3, as illustrated in FIG. 4D.
[0080] In another embodiment, illustrated in FIGs. 4E and 4F, a carrier (or a logic carrier) , a portion of a carrier, or a subband, may be switched on or off to reduce UE and / or NE power consumption. When the traffic load is low, the NE may switch off a portion (DL subbands 410 and UL subband 1 412 of a TDD / SBFD pattern) of its active spectrum, thereby reducing power consumption. FIG. 4E shows the configuration 400E in which the subbands 410 and 412 are still on, but targeted to be switched off, and FIG. 4F shows a configuration 400F in which these subbands are switched off. The NE may provide an indication 402E (e.g., via DCI or MAC-CE) to the UE regarding the switching on or off of part of its spectrum. In one example, the carrier may be divided into multiple subbands, and a bitmap may be used to indicate to the UE which subband is switched on or off. It is also possible to switch on / off a carrier for a specific UE or a group of UEs using dynamic signaling. This indication may be provided semi-statically, by the NE to the UE (e.g., via RRC signaling) or dynamically (e.g., via DCI or MAC-CE signaling) .
[0081] The NE and the UE may exchange signaling at the start of a service or a session to negotiate the required bandwidth. The NE may subsequently activate a set of subbands based on these service requirements. The NE may specify that switching a portion / subband of the contiguous network spectrum on or off should maintain the contiguity of the remaining active spectrum. Furthermore, the NE may specify that subband (s) carrying synchronization signal blocks (SSBs) and / or physical broadcast channel (PBCH) should remain active to avoid impacting UEs in idle mode.
[0082] In another embodiment, the SSBs and / or PBCH on a specific carrier may be dynamically switched on or off. Their deactivation may be interpreted by the UE as an indication that the carrier is deactivated or will be deactivated after a specified time duration (e.g., specified / configured time duration) . The deactivation of some subband (s) can be semi-persistent, applying for a limited duration (e.g., for a specific number of symbols, slots, subframes, or frames) . In some embodiments, the NE may configure the on / off status for one or multiple DL / UL subbands for different time-domain windows, e.g., different slots / subframes / frames, by RRC signaling, MAC-CE, or DCI. In one embodiment, with regard to the spectrum sharing between different systems, e.g., 5G and 6G, or different scenarios, e.g., Non-Terrestrial Network (NTN) and Terrestrial Network (TN) , the NE may configure the time-domain window, e.g., periodicity and slot offset (s) , for the on / off status for one or multiple DL / UL subbands. The NE may update some of the configurations by another signaling, e.g., RRC signaling, MAC-CE, or DCI.
[0083] In one embodiment, the UE may send assistance information to the NE about the preferred carriers, from a performance perspective, and / or an energy saving perspective, and / or an interference perspective. The UE may indicate its preference about the carriers, subbands, BWPs that can be switched on / off. The UE may send assistance information to the NE about the preferred bands that can be aggregated together (e.g., FR1 with FR3, FR2 with FR3, etc. ) .
[0084] The following considerations apply to any of the above discussed embodiments. In one embodiment, a change of UL / DL direction for the carriers may be determined based on the cell discontinuous transmission (DTX) / discontinuous reception (DRX) operation of a carrier. The NE may configure the cell DTX / DRX operation for each carrier. If a carrier is in an inactive period, another carrier may be used for some channels or signals with urgent requests, e.g., some urgent scheduling requests. The NE may configure a UE with a semi-static or dynamic configuration to indicate which carrier is to be used if a serving cell is inactive.
[0085] In another embodiment, one or multiple DL slot (s) or UL slot (s) may be assigned to one or multiple carrier (s) or BWP (s) , i.e., the slot start offset and duration remain the same but the associated carrier (s) or BWP (s) may change. A mapping may be configured from the NE to the UE to indicate which carrier / BWP is to be used for a specific slot or a specific time duration. The mapping may be applied periodically or triggered for a specific time duration.
[0086] The configuration of the UL / DL direction or duplexing mode (e.g., SBFD, etc. ) for one or multiple carrier (s) (or logic carriers) or one or multiple BWP (s) or one or multiple subband (s) may be specified according to a periodic switching pattern. Specifying such periodic switching patterns may be beneficial for scenarios with predictable traffic variations (e.g., periodic XR traffic, etc. ) . The periodic patterns may be configured via semi-static signaling (e.g., RRC signaling) . The configuration may indicate the parameters required by the UE to configure the pattern. These parameters may include the periodicity and potentially a start offset, which aligns the start of the pattern relative to a reference point (e.g., slot index, frame, subframe, or a System Frame Number) . The sequence of UL and DL transmission units (e.g., subframes, frames, slots, or symbols) within each period may also form a part of the configuration of the frequency channel. The activation / deactivation or modification of the periodic patterns may be signaled dynamically (e.g., via DCI or MAC-CE) . This allows the NE to have the flexibility to adapt the pre-configured patterns for specific durations without requiring slower RRC signaling.
[0087] In one embodiment, a new DCI format may be specified for the indication of the UL / DL direction of a carrier (or logic carrier) , BWP, or a frequency subband. Alternatively, one or multiple existing DCI formats (e.g., 0_0, 0_1, 1_0, 1_1, 2_0, 2_1, etc. ) may be used for signaling the UL / DL direction of a carrier (logic carrier) , BWP, or a frequency subband. A new bit-field may be introduced to signal the UL / DL direction. The new bit-field may be configured to the UE per a DCI format.
[0088] In one embodiment, carriers (physical or logical) , BWPs, or subbands may be categorized into multiple groups based on their primary intended transmission direction or duplexing. For example, one group of carriers, potentially those located in lower frequency bands, which are often useful for better coverage especially for UEs at the cell edge, may be designated as a pool primarily intended for UL transmission. Another group of carriers, perhaps utilizing higher frequency bands with wider bandwidth suitable for greater capacity, may be designated as a pool primarily for DL reception. This initial categorization defining the UL and DL carrier pools may be configured via semi-static configuration (e.g., using RRC signaling) .
[0089] Following this initial grouping into potential UL and DL carriers, the NE may then indicate to one or multiple UEs which specific carrier or carriers from the UL pool are assigned to them for their UL transmissions. Similarly for DL communication, the NE may indicate the specific carrier or carriers assigned from the designated DL pool for the UE DL reception. The assigning of specific carriers from the pre-defined pools, to individual UEs, may be managed either semi-statically (e.g., configuring specific carrier sets per UE via RRC) or dynamically (e.g., indicating carriers for use via DCI or MAC-CE signaling) .
[0090] In one embodiment, the NE may dynamically or semi-statically activate / deactivate UL / DL carriers for one or multiple UEs. For example, based on the traffic, the NE may activate an additional DL carrier for a specific UE.
[0091] In one embodiment, the dynamic switching of the transmission direction for a specific carrier may provide a good mechanism to enable and support other services and applications like Integrated Sensing and Communication (ISAC) . In one embodiment, the UL / DL switching may be used as follows: a frequency channel (e.g., carrier or a BWP or a subband) may be used for communication transmissions in DL or UL and then dynamically or semi-statically re-purposed for sensing (e.g., on some subframes, frames, slots, mini-slots, or symbols) . For example, a UE may be receiving data in DL and then transitions to a UE-to-transmission to reception point (TRP) bi-static sensing, where sensing in UL is performed and where the NE receives and processes UL signals from the UE relevant to sensing on that same carrier, BWP, or subband. Operationally, the NE scheduler manages the carrier, BWP, or subband usage and their associated UL / DL directions based on the scheduling needs and service needs.
[0092] When DL / UL communication data and other services data are queued for transmission at the NE and at the device side, the carrier resources and carrier direction may be allocated accordingly. This dynamic allocation necessitates tight coordination between the communication scheduling functions and the other services (e.g., sensing) control functions within the NE. Furthermore, this configuration manages potential trade-offs, as dedicating resources to other services might momentarily reduce the available capacity or increase latency for communication traffic, and vice-versa. A specific switching pattern between different services and / or between UL / DL directions of the same carrier, BWP, or / and subband may be adapted based on the application requirements for communication and any other service.
[0093] The NE may instruct the UE to switch the transmission direction of a carrier, potentially enabling quality measurements in the reverse direction (e.g., sounding reference signal (SRS) transmissions, etc. ) , transmission / reception of low-latency data (e.g., URLLC, XR, artificial intelligence (AI) , etc. ) transmission / reception of urgent / high-priority control information (DCI, hybrid automatic repeat request (HARQ) -ACK, buffer status report (BSR) , etc. ) or any other type of UL / DL transmission / reception. For instance, a UE initially receiving data in the DL on a specific carrier may be instructed by the NE to switch the carrier direction from DL to UL. This allows the UE to transmit SRS or other UL signals, after which it may be instructed to switch back to the DL direction. Based on the resulting UE transmissions, the NE may instruct the UE to operate in the UL direction or switch to another duplexing mode on that carrier (e.g., SBFD) .
[0094] The NE trigger for switching the direction or duplexing mode of the frequency channel may be conveyed to the UE via semi-static signaling (e.g., RRC) or dynamic signaling (e.g., DCI, MAC-CE) . This switching trigger may include parameters such as: the target direction or duplexing mode, an indication of the reason (e.g., SRS transmission, low latency UL data bursts, HARQ-ACK, high priority BSR, etc. ) , the switching time (or a time offset relative to the trigger signal) , the duration before switching back (e.g., specified in slots, symbols, subframes, or frames) , a configuration of the signal (s) that the UE is expected to receive / transmit during the change of direction (e.g., SRS configuration, time / frequency resource allocation, modulation and coding scheme (MCS) , transmit power control (TPC) command, etc. ) . Alternatively, some of this information may be semi-statically configured or specified instead of being indicated dynamically in the switching trigger. Existing signaling mechanisms (e.g., DCI formats, MAC-CEs, etc. ) may be adapted for this purpose using existing or newly-defined information elements (IEs) , fields, or bit-fields. Furthermore, new signaling methods (e.g., new DCI formats or MAC-CEs) may be specified or configured for this functionality.
[0095] In an embodiment, the NE may switch a carrier from UL / DL communication to UL / DL sensing mode and the UE may use its transmitter / receiver chain to transmit / detect sensing signals. The UE may re-tune its RF chain and / or calibrate its RF parameters when switching from communication to sensing or from sensing to communication. In this scenario, the NE may indicate “sensing” in the trigger signal.
[0096] In one embodiment, the NE configures guard periods between the transition from one direction / duplex-mode to another direction / duplex-mode or the transition from one service (e.g., communication) to another service (e.g., sensing) . The guard periods may be specified / configured by the NE for the UE or indicated in the trigger signal or any other type of signal. During the guard-period or during the transition from one direction / duplex-mode to another direction / duplex-mode, the configuration may specify that the UE flushes its HARQ buffer (s) and pauses or resets any running timers.
[0097] In one embodiment, the NE may indicate to the UE to switch from full duplexing mode (e.g., overlapping / non-overlapping SBFD, etc. ) to a TDD duplexing or to a UL / DL direction. The UE may be experiencing high cross-link interference (CLI) and the NE may decide (e.g., based on the CLI measurements reporting from the UE) to switch the UE from one duplex mode to another duplex mode. In one embodiment, a timer may be specified, and the UE may be configured to automatically switch back to the previous direction / duplexing-mode after the timer expiry.
[0098] In one embodiment, the UE may be configured to acknowledge reception of the trigger indicating the switch of the direction / duplexing-mode to ensure the NE and the UE are aligned and that the UE has received the trigger.
[0099] In one embodiment, to assess the channel quality following the switch, an SRS may be automatically transmitted in UL, or a channel state information reference signal (CSI-RS) may be received in DL. A time offset may be specified relative to the time of the switch, and the UE may be expected to transmit the SRS or receive the CSI-RS upon expiration of this offset.
[0100] In one embodiment, the switching or the planned switching from one direction / duplex-mode to another direction / duplex-mode may be signaled from one base station to another base station (e.g., on the Xn interface) . Switching the direction / duplex-mode of one carrier dynamically may cause interference with a neighbor base station and thus an indication may be needed to enable interference mitigation techniques. Additional information may be exchanged between base stations (e.g., the new direction / duplex-mode of the carrier, duration of the switching, etc. ) .
[0101] The UE may assist the NE in selecting the optimal UL and / or DL carrier, or the optimal UL / DL carriers split, or the optimal carrier aggregation combination, or the optimal BWP, or the optimal UL / DL TDD pattern, or the optimal duplex configuration (e.g., size / location of UL subband (s) and / or size / location of DL subband (s) ) by providing assistance information. This information may include details such as the preferred carrier size, the carrier location (e.g., higher band, lower band) , the carriers it prefers for aggregation and the preferred aggregation combinations, the preferred BWP (e.g., recommending the switching between the current BWP and another optimal BWP, for example to save power) , the preferred TDD pattern, the preferred full duplexing time / frequency pattern. Reporting the assistance information by the UE may be triggered by specific events. Such events may include, for example, radio link monitor (RLM) / beam failure detection (BFD) indications for a carrier, lower reference signal received power (RSRP) / reference signal received quality (RSRQ) / power headroom report (PHR) observed for a carrier, high cross-link interference (CLI) on a specific carrier, latency or jitter associated with a specific carrier, quality of service (QoS) requirements are not met (e.g., packet error rate (PER) , packet delay budget (PDB) , etc. ) , or a trigger from an application layer, UE power saving requirements, or overheating conditions. The UE may also report the cause that prompts its recommendation for an UL / DL carrier change.
[0102] In one embodiment, the timer / counter for RLM / BFD / timing advance (TA) management and other functionalities may be reset after the change of the UL / DL carrier or the change of the carrier direction or the change of the duplexing mode (e.g., SBFD duplexing, etc. ) . UE may flush the HARQ buffer or maintain the HARQ buffer after the change of the UL / DL carrier or the change of the carrier direction or the change of the duplexing mode.
[0103] In one embodiment, the UE may report assistance information based on sensing information (e.g., blockage of a path from the NE to the UE on a specific carrier) . The UE may report assistance information to improve a communication link and the NE scheduling based on information extracted / obtained from the collected sensing information. UE assistance information based on the UE sensing information may be configured to be reported periodically with a specified periodicity or with a periodicity configured by the NE. UE assistance information based on the UE sensing information may be triggered by the NE (e.g., via dynamic signaling like DCI or MAC-CE, etc. ) .
[0104] In one embodiment, if at a specific time, all carriers serving a UE are configured exclusively for UL or exclusively for DL transmission, the UE may not be expected to receive or transmit certain signals. For example, if all carriers are UL, the UE may not be expected to monitor and receive certain DL signals, such as PDCCH / PDSCH.
[0105] The previous embodiments were discussed with regard to a physical carrier (also called component carrier) and / or a logical carrier. The logical carrier and how to schedule resource over a non-contiguous spectrum are discussed with regard to FIGs. 5 and 6.
[0106] The logical carrier is introduced to aggregate a non-contiguous spectrum, either within the same band or across multiple bands, such that the aggregated spectrum is treated by the NE and UE as a single logical carrier to support, for example, large data transmissions. This approach enables the creation of a wider effective bandwidth and wider logical carriers from potentially fragmented spectra, improved utilization of the available spectrum, simpler scheduling, and reduced signaling overhead. Also, this approach may simplify the higher layers operation by allowing higher layers to operate on a stable logical carrier and let the lower layers (e.g., PHY, MAC, etc. ) to handle the dynamic physical resources mapping.
[0107] In one embodiment, one logical carrier mapping to one or more physical carriers may be specified or configured by the NE and transmitted to the UE. The logical carrier may be viewed as a dynamic aggregation where the physical carriers (or portions / subbands of the physical carriers or groups of PRBs) are mapped to the logical carrier and may be changed flexibly and potentially without full RRC reconfiguration each time (so far as the aggregated carriers are static and configured via RRC signaling) .
[0108] FIG. 5 illustrates a method 500 that configures a logical carrier, applies dynamic adaptation to the logical carrier, and maps the logical carrier to the physical carriers / resources. The NE (for example, NE 104) may enquire 501 about the UE capabilities for supporting a logical carrier. The UE (for example, UE 102) may reply 502 indicating its capabilities. The NE may transmit 503 a configuration to the UE with the logical carrier using, for example, RRC signaling. The NE transmitted configuration may indicate a logical carrier identity (ID) and may configure the initial mapping of the logical carrier / resources to the physical carriers / resources. The UE may signal 504 to the NE, using an RRC message, that the configuration is complete.
[0109] The UE and the NE may then communicate on the configured logical carrier and the PDCCH may be referring to the logical carrier in the scheduling and then PDSCH / PUSCH happen on physical resources according to the mapping. More specifically, the NE transmits 505 DCI scheduling DL data on the logical carrier and the NE then transmits 506 the DL data on the logical carrier. The NE may also transmit 507 DCI scheduling UL data on the logical carrier and the UE transmits 508 the UL data on the logical carrier.
[0110] The NE determines 509 to dynamically change the mapping of the logical carrier on the physical carriers / resources and transmits 510 the updated logical carrier mapping to the UE. The change of the mapping may take place due to changing conditions such as: interference, spectrum availability, traffic needs. For the re-mapping, instead of using the slow RRC reconfiguration, the NE uses the faster dynamic signaling to indicate the new updated mapping. The UE may acknowledge the new mapping by transmitting 511 an ACK message to the NE.
[0111] The UE may reconfigure 512 the RF and baseband for DL for the new mapping, similar to steps 312A to 312F. Then, the NE transmits 513 the DCI scheduling of the DL data on the logical carrier with updated mapping and transmits 514 the DL data on the logical carrier with updated mapping. The NE receives 515 DCI scheduling of UL data on the logical carrier with the updated mapping and transmits 516 the UL data on the logical carrier with the updated mapping.
[0112] FIG. 6 is a diagram showing a possible mapping 600 between resources on the logical carrier and resources on physical carriers. The figure distinguishes between a logical construct domain 602, shown above a horizonal dashed line 601, and a physical construct domain 604, shown below the horizonal dashed line 601. In the physical construct domain 604, a first physical component carrier 610, associated with a first frequency band (Band#n) is shown. The first component carrier 610 includes a first set of physical resources 612. Also shown in the physical construct domain 602 is a second physical component carrier 620, associated with a second frequency band (Band#m) . The second component carrier 620 includes a second set of physical resources 622. The physical resources 612 and 622 are indicated as potentially representing granular resource units such as, but not limited to, PRBs, subbands, or BWPs. The arrow labeled "Frequency" shows the frequency dimension associated with the physical construct domain 602. In the logical construct domain 604, a logical component carrier 630 is shown. Allocated logical resources (also referred to as virtual resources) 632 are shown on the logical component carrier 630. FIG. 6 also shows a mapping 640 of the logical resources 632 from the logical carrier 630 to physical resources 612 and 622 on the physical carriers 610 and 620.
[0113] In one embodiment, the MAC scheduler considers that the multiple physical resources 612, 622 across multiple physical carriers 610, 620 are a single resource 632 if they all map to the same logical carrier 630.
[0114] In one embodiment, a logical BWP may also be specified / configured and it spans across multiple physical carriers and maps to physical resources across multiple carriers or it maps to multiple physical BWPs belonging to multiple physical carriers. A total number of physical BWPs per logical BWP may be different for UL and DL logical BWPs.
[0115] In one embodiment, a mixture of UL / DL physical BWPs may map to the same logical BWP. In another embodiment, a mixture of UL / DL physical carriers may map to the same logical carrier.
[0116] In one embodiment, the mapping between a logical carrier and physical resources or the mapping between the logical BWP and physical resources may be semi-statically configured (e.g., via RRC) or dynamically activated / deactivated (e.g., via DCI, MAC-CE) .
[0117] In one embodiment, the logical carrier 630 may be defined with a logical carrier ID, with a set of physical resources (e.g., physical carriers, frequency ranges, RBs, etc. ) , mapping rules for logical to physical mapping, and other parameters (e.g., numerologies, TDD configuration, etc. ) .
[0118] In one embodiment, a logical BWP may be defined with a logical BWP ID, with a set of physical resources (e.g., physical carriers, frequency ranges, RBs, PRBs, etc. ) , mapping rules for logical to physical mapping, and other parameters (e.g., numerologies, TDD configuration, DCI formats, etc. ) .
[0119] In one embodiment, a configuration associated with the logical carrier may be configured at the logical carrier level or at the physical resources level. For example, channel quality indicator (CQI) measurements or RSRP / RSRQ / received signal strength indicator (RSSI) measurements may be associated with the logical carrier or may be associated to specific sets of physical resources mapped the logical carrier (e.g., physical carriers) . Also, frequency domain resource allocation (FDRA) and / or time domain resource allocation (TDRA) may be specified to be performed at the logical carrier level or at the associated physical resources level. Hence, the configuration and the measurements may be specified / configured to be at the logical entity level or at the associated physical component (s) level. An indication (e.g., RRC, DCI, MAC-CE, etc. ) may be specified for the NE to inform the UE if the TDRA allocation (or any other configuration or signaling) is performed at the logical carrier level or at the associated physical carrier level. Indication of resource allocation (or any other configuration or signaling) at the logical carrier level may be specified as a UE capability and the UE informs the NE if it can support such capability.
[0120] In one embodiment, a common timing baseline may be specified for a logical carrier or a logical BWP. For example, a physical reference carrier may be specified / configured per logical carrier. A propagation time may be very different for carriers, especially when located in different frequency bands (e.g., FR1 and FR2 or FR3) . One physical carrier may be adopted as the reference carrier in the group of physical carriers, and the reference carrier is mapped to the same logical carrier for these scenarios. The reference carrier may be configured to the UE via semi-static signaling (e.g., RRC) . The reference carrier may be adjusted via dynamic signaling (e.g., DCI, MAC-CE) .
[0121] In one embedment, the NE may specify that the non-contiguous spectra or the physical carriers mapped to the same logical carrier share the same TA group (TAG) .
[0122] In one embodiment, the scheduling may be based on the logical resources of the logical carrier, i.e., a DCI may indicate logical RBs on the logical carrier. The physical carrier scheduled by the DCI may be indicated in the DCI or may be determined from a logical RBs to physical RBs pre-defined / configured mapping.
[0123] In one embodiment, the logical carrier set-up may be carried out during the RRC configuration via RRC messaging. A bit-map may be used to indicate to the UE the mapping between the physical carriers and the logical carrier. The mapping may be adjusted via dynamic signaling (e.g., DCI, MAC-CE, etc. ) .
[0124] In one embodiment, the NE may specify that the physical carriers mapped to the same logical carrier have the same numerology. In another embodiment, the NE may specify that the physical carriers mapped to the same logical carrier may have different numerologies. In one embodiment, the NE may specify that the physical carriers mapped to the same logical carrier are located in the same frequency band (e.g., FR1, FR2, FR3, etc. ) . In another embodiment, the NE may specify that the physical carriers mapped to the same logical carrier may be located in different frequency bands (e.g., FR1, FR2, FR3, etc. ) . The physical carriers mapped to the same logical carrier located in different frequency bands may be supported as a UE capability. The UE reports to the NE its support of this capability.
[0125] In one embodiment, the NE may specify that the physical carriers mapped to the same logical carrier have the same multiplexing scheme (e.g., FDD, TDD, SBFD, etc. ) . In another embodiment, the NE may specify that the physical carriers mapped to the same logical carrier may have different multiplexing schemes (e.g., FDD, TDD, SBFD, etc. ) . Physical carriers mapped to the same logical carrier having different multiplexing schemes (e.g., FDD, TDD, SBFD, etc. ) may be supported as a UE capability. The UE reports to the NE its support of this capability.
[0126] In one embodiment, the NE may specify that the physical carriers mapped to the same logical carrier and having the same multiplexing TDD scheme may also have the same TDD UL / DL configuration and / or same TDD UL / DL pattern. In another embodiment, the NE may specify that the physical carriers mapped to the same logical carrier and having the same multiplexing TDD scheme may have different TDD UL / DL configurations and / or different TDD UL / DL patterns.
[0127] In one embodiment, a transport block (TB) may be mapped to resources across multiple physical carriers. A TB may be transmitted with the same MCS or with multiple MCSs across the multiple physical carriers. A single MCS or an MCS per carrier / spectrum may be configured (for semi-statically configured resources) or indicated dynamically (e.g., via DCI, MAC-CE, etc. ) for the resources carrying the TB.
[0128] In one embodiment, a Control Resource Set (CORESET) , and / or a search space, may be configured per carrier, per spectrum, or per logical carrier, or across non-contiguous spectra. A CORESET is constituted of control channel elements (CCEs) and one CCE is made of 6 resource element groups (REG) where each REG is one RB in frequency dimension and one symbol in time dimension. The NE may specify that a CORESET and / or a CCE and / or an REG may or may not span non-contiguous spectra. CCEs and / or REGs of the same CORESET may be distributed across a non-contiguous spectrum.
[0129] In one embodiment, the maximum number of PDCCH candidates and / or the maximum number of blind decoding attempts and / or the maximum number of DCI formats to monitor may be defined to be across non-contiguous spectra or per logical carrier.
[0130] In one embodiment, the NE may specify that a PRB bundle (e.g., precoding resource block group (PRG) ) may not span non-contiguous spectra or may not span multiple physical carriers mapped to the same logical carrier. In another embodiment, the NE may specify that a PRG may span non-contiguous spectra or span multiple physical carriers mapped to the same logical carrier under some conditions (e.g., if carriers or the non-contiguous spectra are in the same frequency band) .
[0131] In one embodiment, the NE may indicate one common transmission configuration indicator (TCI) state or multiple spectrum-specific TCI states. In one embodiment, one common TCI state may be indicated per logical carrier. Conditions may be specified for indicating one common TCI state per logical carrier (e.g., if carriers or the non-contiguous spectra are in the same frequency band, etc. ) .
[0132] In one embodiment, the NE may specify the common power control parameters or spectrum-specific power control parameters may be configured. The NE may configure the pathloss reference signal in one spectrum or across the non-contiguous spectra or for a logical carrier, and UE may calculate the pathloss in cross-spectrum or intra-spectrum manner. For cross-spectrum manner, the NE may further configure / indicate the pathloss offset.
[0133] In one embodiment, the NE may specify that for discrete Fourier transform-spread orthogonal frequency division multiplexing (DFT-s-OFDM) waveform, the DFT may be performed per spectrum or across spectra (e.g., use a single DFT when the spectrum consists of closely spaced components, i.e., small frequency gaps and if the components are widely separated, consider using multiple DFTs. ) . Alternatively, only cyclic prefix-OFDM (CP-OFDM) waveform is used for this operation. The DFT per spectrum or across spectra may be defined / specified as a UE capability and the UE reports to the NE the support of this capability. The NE may enable this capability if supported by the UE.
[0134] In one embodiment, for a CSI report, the NE may configure a common or spectrum-specific energy power allocated to one RE (EPRE) ratio between the CSI-RS and PDSCH or between the CSI-RS and SSB. A subband size for CSI-RS may not span non-contiguous spectra. For wideband CSI report, the UE may report the wideband rank indicator (RI) / precoding matrix indicator (PMI) / CQI in spectrum-specific or spectrum-common manner or for a set of carriers in continuous / non-continuous spectra. The CSI-RS resource configuration and / or the CSI reporting configuration may be spectrum-specific or spectrum-common.
[0135] In one embodiment, AI and AI / machine learning (ML) models may be used to update the mapping between the logical carrier and the physical resources / carriers. The AI / ML models may predict the demand in terms of spectrum and proactively update the mapping functions.
[0136] In one embodiment, multiple BWPs within a carrier and / or across carriers may be simultaneously active in the same direction (e.g., UL or DL) and dynamic signaling (e.g., DCI, MAC-CE) may be used to quickly activate / deactivate the BWPs for fast adaptation.
[0137] For all the above embodiments, the descriptions and scenarios described in one figure may apply to any other figure, if applicable. In the same spirit, examples, embodiments, and methods described above may be combined, if there is no conflict. An event or block described above may be optional or omitted. For example, an event or block with dashed lines in the figures may be optional.
[0138] In some embodiments, the term “message” is used and may be replaced by “information element (IE) ” , and vice versa. In some embodiments, “IE” is used and may be replaced by “field” , and vice versa. In some embodiments, the term “configuration” may be replaced by “configurations” or “configuration parameters” , and vice versa. In some embodiments, the term “activate” may be replaced by “enable” or “configure” , and vice versa. In some embodiments, the term “deactivate” may be replaced by “disable” or “release” , and vice versa. In some embodiments, the term “applied to” may be replaced by “configured for” or “activated for” , and vice versa. In some embodiments, the term “distributed” may be replaced by “disaggregated” . In some embodiments, the term “secure” may be replaced by “security” , and vice versa.
[0139] A user device in which the techniques of this disclosure may be performed (e.g., the UE 102) may be any suitable device capable of wireless communications such as a smartphone, a tablet computer, a laptop computer, a mobile gaming console, a point-of-sale (POS) terminal, a health monitoring device, a drone, a camera, a media-streaming dongle or another personal media device, a wearable device such as a smartwatch, a wireless hotspot, a femtocell, or a broadband router. Further, the user device in some cases may be embedded in an electronic system such as the head unit of a vehicle or an advanced driver assistance system (ADAS) . Still further, the user device may operate as an internet-of-things (IoT) device or a mobile-internet device (MID) . Depending on the type, the user device may include one or more general-purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.
[0140] Certain embodiments are described in this disclosure as including logic or a number of components or modules. Modules may be software modules (e.g., code, or machine-readable instructions stored on non-transitory machine-readable medium) or hardware modules. A hardware module is a tangible unit capable of performing certain operations and may be configured or arranged in a certain manner. A hardware module may include dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC) , a digital signal processor (DSP) , etc. ) to perform certain operations. A hardware module may also include programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. The decision to implement a hardware module in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.
[0141] When implemented in software, the techniques may be provided as part of the operating system, a library used by multiple applications, a particular software application, etc. The software may be executed by one or more general-purpose processors or one or more special-purpose processors.
[0142] Upon reading this document, those of skill in the art will appreciate still additional and alternative structural and functional designs for handling mobility between NEs or their components, through the principles disclosed herein. Thus, while particular embodiments and applications have been illustrated and described, it is to be understood that the disclosed embodiments are not limited to the precise construction and components disclosed herein. Various modifications, changes and variations, which will be apparent to those of ordinary skill in the art, may be made in the arrangement, operation and details of the method and apparatus disclosed herein without departing from the spirit and scope defined in the appended claims.
Claims
1.A method (200B) for wireless communication performed by a user equipment, UE, (102) , the method comprising:receiving (203B) , from a network entity, NE, (104) via first signaling associated with a first protocol layer, a configuration for a frequency channel;receiving (210B) , from the NE via second signaling associated with a second protocol layer lower than the first protocol layer, an indication for changing at least one of a transmission direction or a duplexing configuration of the frequency channel; andcommunicating (216B) , with the NE, on the frequency channel based on the indication.2.The method of Claim 1, wherein the first signaling is a radio resource control, RRC, message, and wherein the second signaling is a downlink control information, DCI, or a medium access control-control element, MAC-CE.3.The method of Claim 1 or 2, wherein the indication for changing the transmission direction of the frequency channel corresponds to at least one of:switching the transmission direction of a component carrier from an uplink, UL, direction to a downlink, DL, direction,switching the transmission direction of the component carrier from the DL direction to the UL direction,switching the transmission direction of one or more subbands of the frequency channel from the UL direction to the DL direction, orswitching the transmission direction of the one or more subbands of the frequency channel from the DL direction to the UL direction.4.The method of any of Claims 1 to 3, wherein the indication for changing the duplexing configuration of the frequency channel corresponds to at least one of:changing a duplexing mode to at least one of a full frequency duplex mode, a non-overlapping subband full duplex, SBFD mode, or an overlapping SBFD mode,changing a size of one or more SBFD uplink, UL, subbands,changing a size of one or more SBFD downlink, DL, subbands, orswitching on or off parts of a spectrum of the frequency channel.5.The method of any of Claims 1 to 4, wherein the frequency channel is at least one of:a component carrier,a subband,a bandwidth part, BWP, ora logical carrier.6.The method of Claim 5, wherein the logical carrier is mapped to one or more component carriers, which cover a non-contiguous spectrum.7.The method of Claim 5, further comprising:receiving an updated mapping which remaps a logical resource of the logical carrier to a physical resource of one or more component carriers.8.The method of any of Claims 1 to 7, further comprising:communicating with the NE on the frequency channel without the indication for carrier aggregation operation.9.The method of any of Claims 1 to 8, wherein the receiving the indication is triggered by detecting a UL condition associated with an amount of traffic or buffering.10.The method of any of Claims 1 to 9, wherein the configuration for the frequency channel includes a first list of downlink, DL, frequency channels, a second list of uplink, UL, frequency channels, a first list of DL bandwidth parts, BWPs, associated with the first list of DL frequency channels, and a second list of UL BWPs associated with the second list of UL frequency channels;wherein the indication indicates at least one of: a DL carrier among the first list of DL frequency channels or a UL carrier among the second list of UL frequency channels.11.The method of any of Claims 1 to 9, wherein the configuration for the frequency channel includes a plurality of downlink, DL, bandwidth parts, BWPs, and a plurality of uplink, UL, BWPs, each DL BWP being associated with DL frequency channel information and each UL BWP being associated with UL frequency channel information;wherein the indication indicates at least one of:a switch to a first DL BWP among the plurality of DL BWPs or a first UL BWP among the plurality of UL BWPs,an activation of a second DL BWP among the plurality of DL BWPs or a second UL BWP among the plurality of UL BWPs, ora deactivation of a third DL BWP among the plurality of DL BWPs or a third UL BWP among the plurality of UL BWPs.12.A method (200A) for wireless communication performed by a network entity, NE, (104) , the method comprising:transmitting (203A) , to a user equipment, UE, (102) via first signaling associated with a first protocol layer, a configuration for a frequency channel;transmitting (210A) , to the UE (102) , via second signaling associated with a second protocol layer lower than the first protocol layer, an indication for changing at least one of a transmission direction or a duplexing configuration of the frequency channel; andcommunicating (216A) , with the UE, on the frequency channel based on the indication.13.The method of Claim 12, wherein the first signaling is a radio resource control, RRC, message, and the second signaling is a downlink control information, DCI, or a medium access control-control element, MAC-CE.14.The method of Claim 12 or 13, wherein the indication for changing the transmission direction of the frequency channel corresponds to at least one of:switching the transmission direction of a component carrier from an uplink, UL, direction to a downlink, DL, direction,switching the transmission direction of the component carrier from the DL direction to the UL direction,switching the transmission direction of one or more subbands of the frequency channel from the DL direction to the UL direction, orswitching the transmission direction of the one or more subbands of the frequency channel from the UL direction to the DL direction.15.The method of any of Claims 12 to 14, wherein the indication for changing the duplexing configuration of the frequency channel corresponds to at least one of:changing a duplexing mode to at least one of a full frequency duplex mode, a non-overlapping subband full duplex, SBFD mode, or an overlapping SBFD mode,changing a size of one or more SBFD uplink, UL, subbands,changing a size of one or more SBFD downlink, DL, subbands, orswitching on or off parts of a spectrum of the frequency channel.16.The method of any of Claims 12 to 15, wherein the frequency channel is at least one of:a component carrier,a subband,a bandwidth part, BWP, ora logical carrier.17.The method of Claim 16, further comprising:transmitting an updated logical carrier which remaps a logical resource of the logical carrier to a physical resource of one or more component carriers.18.The method of any of Claims 12 to 17, wherein the configuration for the frequency channel includes a first list of downlink, DL, frequency channels, a second list of uplink, UL, frequency channels, a first list of DL bandwidth parts, BWPs, associated with the first list of DL frequency channels, and a second list of UL BWPs associated with the second list of UL frequency channels;wherein the indication indicates at least one of: a DL carrier among the first list of DL frequency channels or an UL carrier among the second list of UL frequency channels.19.The method of any of Claims 12 to 17, wherein the configuration for the frequency channel includes a plurality of downlink, DL, bandwidth parts, BWPs, and a plurality of uplink, UL, BWPs, each DL BWP being associated with DL frequency channel information and each UL BWP being associated with UL frequency channel information;wherein the indication indicates at least one of:a switch to a first DL BWP among the plurality of DL BWPs or a first UL BWP among the plurality of UL BWPs,an activation of a second DL BWP among the plurality of DL BWPs or a second UL BWP among the plurality of UL BWPs, ora deactivation of a third DL BWP among the plurality of DL BWPs or a third UL BWP among the plurality of UL BWPs.20.A communication device (102, 104) comprising a processor (132, 142) and a transceiver (134, 144) configured to cooperatively execute the methods of claims 1 to 19.
