Frequency band switching and switching time capability reporting

By introducing a capability inquiry and reporting mechanism in the wireless communication system, UE and network entities jointly determine the supported frequency band pairs, solving the problem of inefficient bandwidth reporting of band switching and handover time capability in the prior art, achieving more efficient resource utilization and performance improvement.

CN120019679APending Publication Date: 2025-05-16QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280100862.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-10-17
Publication Date
2025-05-16

AI Technical Summary

Technical Problem

Existing wireless communication systems have problems with inefficiency and waste of resources in band switching and handover time capability reporting, especially when multiple band pairs are supported.

Method used

By implementing a capability inquiry and reporting mechanism between user equipment (UE) and network entities, the UE sends capability information to indicate supported band pairs, based on which network entities avoid indicating unsupported band pairs, reducing latency and increasing throughput.

Benefits of technology

It effectively avoids unsupported frequency band configurations, reduces delay and power consumption, and improves the overall performance and resource utilization of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120019679A_ABST
    Figure CN120019679A_ABST
Patent Text Reader

Abstract

The invention discloses a method, UE and network entity for wireless communication. The method for wireless communication performed by the UE includes receiving a capability query and transmitting capability information in response to the capability query, the capability information indicating one or more of a plurality of possible band pairs by which the UE is configured to use.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for frequency band switching and switching time capability reporting. Background Art

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

[0003] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[0004] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by: improving spectrum efficiency; reducing costs; improving services; utilizing new spectrum; and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards; and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0005] Some aspects described herein relate to an apparatus for wireless communication at a user equipment (UE). The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a capability query. The one or more processors may be configured to send capability information in response to the capability query, the capability information indicating one or more frequency band pairs of a plurality of possible frequency band pairs that the UE is configured to use.

[0006] Some aspects described herein relate to an apparatus for wireless communication at a network entity. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send a capability query. The one or more processors may be configured to receive capability information in response to the capability query, the capability information indicating one or more frequency band pairs of a plurality of possible frequency band pairs that the UE is configured to use.

[0007] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving a capability query. The method may include sending capability information in response to the capability query, the capability information indicating one or more frequency band pairs of a plurality of possible frequency band pairs that the UE is configured to use.

[0008] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include sending a capability query. The method may include receiving capability information in response to the capability query, the capability information indicating one or more frequency band pairs of a plurality of possible frequency band pairs that the UE is configured to use.

[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a capability query. The instruction set, when executed by one or more processors of the UE, may cause the UE to send capability information in response to the capability query, the capability information indicating one or more frequency band pairs of a plurality of possible frequency band pairs that the UE is configured to use.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network entity. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to send a capability query. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to receive capability information in response to the capability query, the capability information indicating one or more frequency band pairs of a plurality of possible frequency band pairs that the UE is configured to use.

[0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a capability query. The apparatus may include means for sending capability information in response to the capability query, the capability information indicating one or more frequency band pairs of a plurality of possible frequency band pairs that the apparatus is configured to use.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a capability query. The apparatus may include means for receiving capability information in response to the capability query, the capability information indicating one or more frequency band pairs of a plurality of possible frequency band pairs that the UE is configured to use.

[0013] Aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.

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

[0015] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to be able to understand the above-mentioned features of the present disclosure in detail, a more specific description briefly summarized above may be obtained by reference to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings illustrate only certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0017] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0018] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment in a wireless network according to the present disclosure.

[0019] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0020] Figure 4 is a diagram illustrating an example of carrier aggregation according to the present disclosure.

[0021] Figure 5 is a diagram illustrating an example associated with frequency band switching and switching time capability reporting according to the present disclosure.

[0022] Figure 6 and Figure 7is a diagram illustrating an example process associated with frequency band switching and switching time capability reporting according to the present disclosure.

[0023] Figure 8 and Fig. 9 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0024] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is independently or in combination with any other aspect of the disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method practiced using other structures, functionality, or structure and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present invention.

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

[0026] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT and / or RATs beyond 5G (e.g., 6G).

[0027] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0028] In some examples, the network node 110 is or includes a network node that communicates with the UE 120 via a radio access link, such as an RU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or communicates with the core network via a backhaul link, such as a CU. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks) using any suitable transport network.

[0029] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​the network node 110 and / or the network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1 In the example shown in , network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0030] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions, but not another base station function. In this way, a single device may include more than one base station.

[0031] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown in , a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communication between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0032] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0033] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless or wired backhaul communication link. In some aspects, the network controller 130 may be, or may include, a CU or a core network device.

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

[0035] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

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

[0037] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0038] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0039] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0040] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0041] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, communication manager 140 may receive a capability query and may send capability information in response to the capability query that indicates one or more of a plurality of possible frequency band pairs that UE 120 is configured to use. Additionally or alternatively, communication manager 140 may perform one or more other operations described herein.

[0042] In some aspects, a network entity (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send a capability query and may receive capability information in response to the capability query that indicates one or more of a plurality of possible frequency band pairs that the UE 120 is configured to use. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0043] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1The examples described are different.

[0044] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0045] At the network node 110, a transmit processor 220 may receive data intended for a UE 120 (or a set of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas) (shown as antennas 234a through 234t).

[0046] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0047] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0048] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0049] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 5 to 9 ) or any aspect of any of the methods described herein.

[0050] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component (shown as DEMOD) of the modem 232), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink communication and / or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 5 to 9 ) or any aspect of any of the methods described herein.

[0051] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the network node 110 may perform one or more techniques associated with frequency band switching and switching time capability reporting, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Figure 6 The process of 600 Figure 7 10 and / or operations of process 700 and / or other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly executed, or executed after compilation, conversion, and / or interpretation), may cause one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Figure 6 The process of 600 Figure 7 The process 700 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0052] In some aspects, a UE (e.g., UE 120 and / or Figure 8 The apparatus 800 may include a component for receiving a capability query; and / or a component for sending capability information in response to the capability query, the capability information indicating one or more of a plurality of possible frequency band pairs that the UE is configured to use. The components for the UE to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0053] In some aspects, a network entity (e.g., network node 110, RU 340, DU 330, CU 310, and / or Fig. 9The apparatus 900 may include a component for sending a capability query; and / or a component for receiving capability information in response to the capability query, the capability information indicating one or more of a plurality of possible frequency band pairs that the UE is configured to use. In some aspects, the components for the network entity to perform the operations described herein may include, for example, one or more of the following: the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0054] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0055] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0056] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also referred to as an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

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

[0058] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0059] Figure 3 3 is a diagram illustrating an example disaggregated base station architecture 300 according to the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units, such as a near-RT RIC 325 via an E2 link, or a non-RTRIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0060] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces, the one or more interfaces being configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of the units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, the wireless interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, or both.

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

[0062] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more high physical (PHY) layers, at least in part, according to a functional partition such as that defined by 3GPP. In some aspects, one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may further host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0063] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions based on functional split (e.g., functional split defined by 3GPP) (such as lower layer functional split), such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc. In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

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

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

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

[0067] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0068] Figure 4 4 is a diagram illustrating an example 400 of carrier aggregation according to the present disclosure. Carrier aggregation is a technique that enables two or more component carriers (CCs, sometimes referred to as carriers) to be combined (e.g., combined into a single channel) for a single UE 120 to enhance data capacity. As shown, carriers may be combined in the same or different frequency bands. Additionally or alternatively, contiguous or non-contiguous carriers may be combined. Network node 110 may configure carrier aggregation for UE 120 (such as in an RRC message, downlink control information (DCI), and / or another signaling message).

[0069] As indicated by reference numeral 405, in some aspects, carrier aggregation may be configured in an intra-band contiguous mode, where the aggregated carriers are contiguous with each other and in the same frequency band. As indicated by reference numeral 410, in some aspects, carrier aggregation may be configured in an intra-band discontiguous mode, where the aggregated carriers are discontiguous with each other and in the same frequency band. As indicated by reference numeral 415, in some aspects, carrier aggregation may be configured in an inter-band discontiguous mode, where the aggregated carriers are discontiguous with each other and in different frequency bands.

[0070] In carrier aggregation, a UE 120 may be configured with a primary carrier or primary cell (PCell) and one or more secondary carriers or secondary cells (SCells). In some aspects, the primary carrier may carry control information (e.g., downlink control information and / or scheduling information) for scheduling data communications on one or more secondary carriers, which may be referred to as cross-carrier scheduling. In some aspects, a carrier (e.g., a primary carrier or a secondary carrier) may carry control information for scheduling data communications on the carrier, which may be referred to as self-carrier scheduling or carrier self-scheduling.

[0071] When the network and UE are configured to use two frequency bands, the UE can report whether uplink transmission switching between the frequency bands is supported. Uplink transmission switching (also known as "UL Tx switching") allows the network to command the UE to change carriers in order to increase the throughput from the UE to the network or improve the reliability and quality between the UE and the network.

[0072] However, the network and UE may be configured to use additional frequency bands (e.g., three or four frequency bands). Therefore, the network may configure the UE for a more flexible uplink transmission switching situation. For example, the network may configure the UE with a frequency band pair in three or four frequency bands for performing uplink transmission switching. However, the UE may not support uplink transmission switching for all possible frequency band pairs. Therefore, the network may indicate unsupported frequency band pairs, which increases latency and reduces throughput from the UE to the network. In addition, power and processing resources are wasted because the UE will not be able to transmit according to instructions from the network, so that the network will send a new indication after failing to receive and decode the transmission from the UE.

[0073] Some techniques and apparatus described herein enable a UE (e.g., UE 120) to report which frequency band pairs are supported for uplink transmission switching. Therefore, the network (e.g., via network node 110) can avoid instructing UE 120 to use unsupported frequency band pairs. Therefore, latency is reduced and throughput is increased; in addition, power and processing resources are saved because the network can continue to successfully receive and decode transmissions from UE 120. In addition, UE 120 can report a switching period associated with reconfiguration from a first frequency band pair to a second frequency band pair. Therefore, the network can avoid transmitting to UE 120 during the switching period, or avoid instructing UE 120 to transmit. Therefore, power and processing resources are saved because transmissions during the switching period will generally be retransmitted.

[0074] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0075] Figure 5 is a diagram illustrating an example 500 associated with frequency band switching and switching time capability reporting according to the present disclosure. Figure 5 As shown, the network node 110 (eg, RU 340 and / or a device controlling RU 340 such as DU 330 and / or CU 310) and the UE 120 may communicate with each other (eg, over a wireless network such as Figure 1 wireless network 100).

[0076] As shown by reference numeral 505, the network node 110 may send (e.g., directly or via the RU 340) a capability query, and the UE 120 may receive the capability query. For example, the network node 110 may send an RRC message including a UECapabilityEnquiry data structure (e.g., as defined by a 3GPP specification and / or another standard) or a similar data structure. The capability query may trigger the UE 120 to report which frequency band pairs are supported for uplink transmission switching. In addition, the capability query may trigger the UE 120 to report the maximum number of MIMO layers per frequency band and / or one or more switching periods between different frequency band pairs.

[0077] UE 120 may encode the switching capability into the capability information, as indicated by reference numeral 510. UE 120 may indicate one or more frequency band pairs of a plurality of possible frequency band pairs that UE 120 is configured to use.

[0078] In one example, UE 120 may encode a plurality of bits that explicitly indicate one or more supported frequency band switching situations. For example, the plurality of bits may form a table data structure, such as the example Table 1 shown below:

[0079]

[0080]

[0081] Example Table 1

[0082] Although the example is shown as having four frequency bands, other examples may include fewer frequency bands (e.g., three frequency bands) or additional frequency bands. Similarly, although the example is shown as having a maximum of 2 MIMO layers, other examples may include a maximum of fewer layers (e.g., 1 MIMO layer) or additional layers (e.g., 4 MIMO layers) for at least one frequency band. In example Table 1, "Band A", "Band B", "Band C", and "Band D" refer to any four frequency bands used by UE 120 and network node 110. Although ten rows are shown, the table may have additional (or fewer) rows, depending on how many switching situations UE 120 supports.

[0083] Therefore, UE 120 can explicitly indicate which switching situations are supported. Therefore, when the maximum number of MIMO layers per frequency band is 0, 1, 2 or 4, the plurality of bits can be at least 256 bits. Alternatively, UE 120 can encode a bitmap or another similar type of indication based on a predefined list of switching situations. Therefore, each bit of the bitmap indicates whether UE 120 supports a frequency band pair associated with the bit in a plurality of possible frequency band pairs in the predefined list. The predefined list of switching situations can be stored in a memory of UE 120 (and / or otherwise programmed therein) (e.g., according to 3GPP specifications and / or another standard). Additionally or alternatively, network node 110 can indicate a predefined list of switching situations (e.g., in a capability query). In a combined example, multiple possible predefined lists may be stored in (and / or otherwise programmed into) a memory of UE 120 (e.g., in accordance with a 3GPP specification and / or another standard), and network node 110 may indicate (e.g., in a capability query) which of the multiple possible predefined lists to use.

[0084] In some aspects, for each frequency band pair, the UE 120 may also encode the maximum number of MIMO layers. For example, when the maximum number of MIMO layers is 2, the UE 120 may use 3 bits or 4 bits to encode the maximum number of MIMO layers per frequency band (depending on whether 3 or 4 frequency bands are used). In another example, when the maximum number of MIMO layers is 4, the UE 120 may use 6 bits or 8 bits to encode the maximum number of MIMO layers per frequency band (depending on whether 3 or 4 frequency bands are used).

[0085] UE 120 may also encode an indication of one or more switching periods associated with the one or more frequency band pairs. For example, the indication may include a table data structure, such as the example Table 2 shown below:

[0086] 1 2 3 4 5 6 7 8 9 10 1 N / A <![CDATA[T switch_1_2 ]]> <![CDATA[T switch_1_3 ]]> <![CDATA[T switch_1_4 ]]> <![CDATA[T switch_1_5 ]]> <![CDATA[T switch_1_6 ]]> <![CDATA[T switch_1_7 ]]> <![CDATA[T switch_1_8 ]]> <![CDATA[T switch_1_9 ]]> <![CDATA[T switch_1_10 ]]> 2 <![CDATA[T switch_2_1 ]]> N / A <![CDATA[T switch_2_3 ]]> <![CDATA[T switch_2_4 ]]> <![CDATA[T switch_2_5 ]]> <![CDATA[T switch_2_6 ]]> <![CDATA[T switch_2_7 ]]> <![CDATA[T switch_2_8 ]]> <![CDATA[T switch_2_9 ]]> <![CDATA[T switch_2_10 ]]> 3 <![CDATA[T switch_3_1 ]]> <![CDATA[T switch_3_2 ]]> N / A <![CDATA[T switch_3_4 ]]> <![CDATA[T switch_3_5 ]]> <![CDATA[T switch_3_6 ]]> <![CDATA[T switch_3_7 ]]> <![CDATA[T switch_3_8 ]]> <![CDATA[T switch_3_9 ]]> <![CDATA[T switch_3_10 ]]> 4 <![CDATA[T switch_4_1 ]]> <![CDATA[T switch_4_2 ]]> <![CDATA[T switch_4_3 ]]> N / A <![CDATA[T switch_4_5 ]]> <![CDATA[T switch_4_6 ]]> <![CDATA[T switch_4_7 ]]> <![CDATA[T switch_4_8 ]]> <![CDATA[T switch_4_9 ]]> <![CDATA[T switch_4_10 ]]> 5 <![CDATA[T switch_5_1 ]]> <![CDATA[T switch_5_2 ]]> <![CDATA[T switch_5_3 ]]> <![CDATA[T switch_5_4 ]]> N / A <![CDATA[T switch_5_6 ]]> <![CDATA[T switch_5_7 ]]> <![CDATA[T switch_5_8 ]]> <![CDATA[T switch_5_9 ]]> <![CDATA[T switch_5_10 ]]> 6 <![CDATA[T switch_6_1 ]]> <![CDATA[T switch_6_2 ]]> <![CDATA[T switch_6_3 ]]> <![CDATA[T switch_6_4 ]]> <![CDATA[T switch_6_5 ]]> N / A <![CDATA[T switch_6_7 ]]> <![CDATA[T switch_6_8 ]]> <![CDATA[T switch_6_9 ]]> <![CDATA[T switch_6_10 ]]> 7 <![CDATA[T switch_7_1 ]]> <![CDATA[T switch_7_2 ]]> <![CDATA[T switch_7_3 ]]> <![CDATA[T switch_7_4 ]]> <![CDATA[T switch_7_5 ]]> <![CDATA[T switch_7_6 ]]> N / A <![CDATA[T switch_7_8 ]]> <![CDATA[T switch_7_9 ]]> <![CDATA[T switch_7_10 ]]> 8 <![CDATA[T switch_8_1 ]]> <![CDATA[T switch_8_2 ]]> <![CDATA[T switch_8_3 ]]> <![CDATA[T switch_8_4 ]]> <![CDATA[T switch_8_5 ]]> <![CDATA[T switch_8_6 ]]> <![CDATA[T switch_8_7 ]]> N / A <![CDATA[T switch_8_9 ]]> <![CDATA[T switch_8_10 ]]> 9 <![CDATA[T switch_9_1 ]]> <![CDATA[T switch_9_2 ]]> <![CDATA[T switch_9_3 ]]> <![CDATA[T switch_9_4 ]]> <![CDATA[T switch_9_5 ]]> <![CDATA[T switch_9_6 ]]> <![CDATA[T switch_9_7 ]]> <![CDATA[T switch_9_8 ]]> N / A <![CDATA[T switch_9_10 ]]> 10 <![CDATA[T switch_10_1 ]]> <![CDATA[T switch_10_2 ]]> <![CDATA[T switch_10_3 ]]> <![CDATA[T switch_10_4 ]]> <![CDATA[T switch_10_5 ]]> <![CDATA[T switch_10_6 ]]> <![CDATA[T switch_10_7 ]]> <![CDATA[T switch_10_8 ]]> <![CDATA[T switch_10_9 ]]> N / A

[0087] Example Table 2

[0088] In Example Table 2, T switch_n_mRepresents a switching period from band pair n to band pair m. In some aspects, each switching period may be selected from a plurality of possible switching periods (e.g., 35 microseconds (μs), 70 μs, or 210 μs). Thus, when there are 3 or 4 possible switching periods, the UE 120 may use 180 bits to encode the switching period. The possible switching periods may be stored in (and / or otherwise programmed into) a memory of the UE 120 (e.g., according to a 3GPP specification and / or another standard). Additionally or alternatively, the network node 110 may indicate the possible switching periods (e.g., in a capability query). In a combined example, multiple groups of possible switching periods may be stored in (and / or otherwise programmed into) a memory of the UE 120 (e.g., according to a 3GPP specification and / or another standard), and the network node 110 may indicate (e.g., in a capability query) which group of possible switching periods (of the multiple groups of possible switching periods) is used.

[0089] In some aspects, a switching period associated with switching from a first frequency band pair to a second frequency band pair is also associated with switching from the second frequency band pair to the first frequency band pair. switch_n_m =T switch_m_n Therefore, when there are 3 or 4 possible switching periods, UE 120 may use 90 bits to encode the switching period.

[0090] Additionally or alternatively, UE 120 may omit one or more additional switching periods as default values. Thus, UE 120 may reduce the number of bits used to encode the switching period. The default values ​​may be stored in a memory of UE 120 (and / or otherwise programmed therein) (e.g., according to a 3GPP specification and / or another standard). Additionally or alternatively, network node 110 may indicate the default values ​​(e.g., in a capability query). In a combined example, multiple sets of possible default values ​​may be stored in a memory of UE 120 (and / or otherwise programmed therein) (e.g., according to a 3GPP specification and / or another standard), and network node 110 may indicate (e.g., in a capability query) which default value (of the multiple possible default values) to use.

[0091] As indicated by reference numeral 515, UE 120 may send capability information, and network node 110 may receive (e.g., directly or via RU 340) the capability information. For example, UE 120 may send an RRC message including a UECapabilityInformation data structure (e.g., as defined by a 3GPP specification and / or another standard) or a similar data structure.

[0092] As indicated by reference numeral 520, the network node 110 may determine a configuration for the UE 120. For example, the network node 110 may select a frequency band pair for the UE 120 to use for uplink transmission switching.

[0093] As indicated by reference numeral 525, the network node 110 may send (eg, directly or via the RU 340) an indication of the configuration, and the UE 120 may receive the indication of the configuration. For example, the network node 110 may send an RRC message indicating the configuration.

[0094] By using such as Figure 5 According to the described technique, the UE 120 reports which frequency band pairs are supported for uplink transmission switching. Therefore, the network node 110 avoids indicating unsupported frequency band pairs in the configuration. Therefore, latency is reduced and throughput is increased; in addition, power and processing resources are saved because the network node 110 can continue to successfully receive and decode transmissions from the UE 120. In addition, the UE 120 reports one or more switching periods. Therefore, during the switching period, the network node 110 avoids transmitting to the UE 120, or avoids instructing the UE 120 to transmit. Therefore, power and processing resources are saved because transmissions during the switching period will generally be retransmitted.

[0095] As indicated above, Figure 5 are provided as examples. Other examples can be found in relation to Figure 5 The examples described are different.

[0096] Figure 6 600 is a diagram illustrating an example process 600 performed, for example, by a UE according to the present disclosure. The example process 600 is a diagram in which a UE (e.g., UE 120 and / or Figure 8 An example of an apparatus 800) performing operations associated with frequency band switching and switching time capability reporting.

[0097] like Figure 6 As shown, in some aspects, process 600 may include receiving a capability query (block 610). For example, a UE (e.g., using Figure 8 The communication manager 140 and / or receiving component 802 depicted in FIG. 8 may receive a capability query, as described above in conjunction with Figure 5 As described.

[0098] like Figure 6 As further shown, in some aspects, process 600 may include sending capability information in response to the capability query, the capability information indicating one or more of a plurality of possible frequency band pairs configured for use (block 620). Figure 8The communication manager 140 and / or the sending component 804 depicted in FIG. 1 may send capability information in response to the capability query, the capability information indicating one or more frequency band pairs of a plurality of possible frequency band pairs configured for use, as described above in conjunction with Figure 5 as described.

[0099] Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0100] In a first aspect, the capability information includes a plurality of bits that explicitly indicate one or more supported frequency band switching scenarios for the one or more frequency band pairs.

[0101] In a second aspect, alone or in combination with the first aspect, the capability information indicates a switching case for uplink transmission switching based on one or more frequency band pairs and supported by the UE.

[0102] In a third aspect, alone or in combination with one or more of the first and second aspects, the capability information further indicates a number of antenna ports for each frequency band in the one or more frequency band pairs.

[0103] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the capability information comprises a bitmap, wherein each bit of the bitmap indicates whether a frequency band pair in a predefined set of frequency band pairs and associated with the bit is supported.

[0104] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the predefined set of frequency band pairs is programmed into a memory of the UE.

[0105] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the capability query indicates a predefined set of the frequency band pairs.

[0106] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the capability information further indicates a maximum number of MIMO layers for each frequency band pair.

[0107] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the one or more frequency band pairs include a plurality of frequency band pairs, and the capability information further indicates one or more switching periods associated with switching between frequency band pairs in the plurality of frequency band pairs.

[0108] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the capability information comprises a table encoding the one or more switching periods.

[0109] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, a switching period associated with switching from the first frequency band pair to the second frequency band pair is also associated with switching from the second frequency band pair to the first frequency band pair.

[0110] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the capability information omits one or more additional switching periods as default values.

[0111] although Figure 6 Example blocks of process 600 are shown, but in some aspects, process 600 may include Figure 6 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 600 may be performed in parallel.

[0112] Figure 7 700 is a diagram illustrating an example process 700 performed, for example, by a network entity according to the present disclosure. The example process 700 is a diagram in which a network entity (e.g., network node 110 and / or Fig. 9 An example of a device 900) performing operations associated with frequency band switching and switching time capability reporting.

[0113] like Figure 7 As shown, in some aspects, process 700 may include sending a capability query (block 710). For example, a network entity (e.g., using Fig. 9 The communication manager 150 and / or the sending component 904 depicted in FIG. 10 may send a capability query, as described above in conjunction with Figure 5 as described.

[0114] like Figure 7 As further shown, in some aspects, process 700 may include receiving capability information in response to the capability query, the capability information indicating one or more frequency band pairs of a plurality of possible frequency band pairs configured for use (block 720). Fig. 9 The communication manager 150 and / or receiving component 902 depicted in FIG. 1 may receive capability information in response to a capability query, the capability information indicating one or more frequency band pairs of a plurality of possible frequency band pairs configured for use, as described above in conjunction with Figure 5 as described.

[0115] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0116] In a first aspect, the capability information includes a plurality of bits that explicitly indicate one or more supported frequency band switching scenarios for the one or more frequency band pairs.

[0117] In a second aspect, alone or in combination with the first aspect, the capability information indicates a switching case for uplink transmission switching based on one or more frequency band pairs and supported by the UE.

[0118] In a third aspect, alone or in combination with one or more of the first and second aspects, the capability information further indicates a number of antenna ports for each frequency band in the one or more frequency band pairs.

[0119] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the capability information comprises a bitmap, wherein each bit of the bitmap indicates whether a frequency band pair in a predefined set of frequency band pairs and associated with the bit is supported.

[0120] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the predefined set of frequency band pairs is programmed into a memory of the network entity.

[0121] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the capability query indicates a predefined set of the frequency band pairs.

[0122] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the capability information further indicates a maximum number of MIMO layers for each frequency band pair.

[0123] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the one or more frequency band pairs include a plurality of frequency band pairs, and the capability information further indicates one or more switching periods associated with switching between frequency band pairs in the plurality of frequency band pairs.

[0124] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the capability information comprises a table encoding the one or more switching periods.

[0125] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, a switching period associated with switching from the first frequency band pair to the second frequency band pair is also associated with switching from the second frequency band pair to the first frequency band pair.

[0126] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the capability information omits one or more additional switching periods as default values.

[0127] although Figure 7Example blocks of process 700 are shown, but in some aspects, process 700 may include Figure 7 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 700 may be performed in parallel.

[0128] Figure 8 800 is a diagram of an example apparatus 800 for wireless communication according to the present disclosure. The apparatus 800 may be a UE, or the UE may include the apparatus 800. In some aspects, the apparatus 800 includes a receiving component 802 and a sending component 804, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 800 may communicate with another apparatus 806 (such as a UE, a RU, or another wireless communication device) using the receiving component 802 and the sending component 804. As further shown, the apparatus 800 may include a communication manager 140. The communication manager 140 may include an encoding component 808, etc.

[0129] In some aspects, the apparatus 800 may be configured to perform Figure 5 Additionally or alternatively, the apparatus 800 may be configured to perform one or more processes described herein (such as Figure 6 In some aspects, Figure 8 The device 800 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Figure 8 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0130] The receiving component 802 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 806. The receiving component 802 may provide the received communications to one or more other components of the device 800. In some aspects, the receiving component 802 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to the one or more other components of the device 800. In some aspects, the receiving component 802 may include combining Figure 2One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.

[0131] The transmitting component 804 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 806. In some aspects, one or more other components of the device 800 may generate communications and may provide the generated communications to the transmitting component 804 for transmission to the device 806. In some aspects, the transmitting component 804 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 806. In some aspects, the transmitting component 804 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 804 can be co-located with the receive component 802 in a transceiver.

[0132] In some aspects, receiving component 802 may receive (e.g., from device 806) a capability query. Encoding component 808 may encode capability information indicating one or more of a plurality of possible frequency band pairs that device 800 is configured to use. Encoding component 808 may include combining Figure 2 The described UE's modem, modulator, transmit MIMO processor, transmit processor, controller / processor, memory, or a combination thereof. Transmitting component 804 can transmit capability information (eg, to device 806) in response to the capability query.

[0133] Figure 8 The number and arrangement of components shown are provided as examples. In practice, there may be Figure 8 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Figure 8 Two or more components shown may be implemented in a single component, or Figure 8 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 8 The illustrated set of component(s) may be described as being executable by Figure 8 Another collection of components shown performs one or more functions.

[0134] Fig. 9is a diagram of an example apparatus 900 for wireless communication according to the present disclosure. Apparatus 900 may be a network entity, or a network entity may include apparatus 900. In some aspects, apparatus 900 includes a receiving component 902 and a sending component 904, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 900 may communicate with another apparatus 906 (such as a UE, RU, or another wireless communication device) using receiving component 902 and sending component 904. As further shown, apparatus 900 may include a communication manager 150. Communication manager 150 may include configuration component 908, etc.

[0135] In some aspects, the apparatus 900 may be configured to perform Figure 5 Additionally or alternatively, the apparatus 900 may be configured to perform one or more of the processes described herein (such as Figure 7 In some aspects, Fig. 9 The device 900 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig. 9 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0136] The receiving component 902 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 906. The receiving component 902 may provide the received communications to one or more other components of the device 900. In some aspects, the receiving component 902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to the one or more other components of the device 900. In some aspects, the receiving component 902 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described network nodes.

[0137] Transmit component 904 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 906. In some aspects, one or more other components of device 900 may generate communications and may provide the generated communications to transmit component 904 for transmission to device 906. In some aspects, transmit component 904 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 906. In some aspects, transmit component 904 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network nodes. In some aspects, the transmit component 904 can be co-located with the receive component 902 in a transceiver.

[0138] In some aspects, sending component 904 can send a capability query (e.g., to device 906). Receiving component 902 can receive capability information in response to the capability query, the capability information indicating one or more of a plurality of possible frequency band pairs that device 906 is configured to use. Thus, configuring component 908 can determine a configuration for device 906 to use based on the capability information. Configuring component 908 can include combining Figure 2 The MIMO detector, receive processor, controller / processor, memory, or a combination thereof of the described network node. The transmitting component 90 may transmit an indication of the configuration (eg, to the device 906).

[0139] Fig. 9 The number and arrangement of components shown are provided as examples. In practice, there may be Fig. 9 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig. 9 Two or more components shown may be implemented in a single component, or Fig. 9 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig. 9 The illustrated set of component(s) may be described as being executable by Fig. 9 Another collection of components shown performs one or more functions.

[0140] The following provides an overview of some aspects of the disclosure:

[0141] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a capability query; and sending capability information in response to the capability query, the capability information indicating one or more frequency band pairs of a plurality of possible frequency band pairs that the UE is configured to use.

[0142] Aspect 2: The method according to aspect 1, wherein the capability information comprises a plurality of bits, the plurality of bits explicitly indicating one or more supported frequency band switching situations for the one or more frequency band pairs.

[0143] Aspect 3: The method according to aspect 2, wherein the capability information further indicates the number of antenna ports for each frequency band in the one or more frequency band pairs.

[0144] Aspect 4: The method according to aspect 1, wherein the capability information comprises a bitmap, wherein each bit of the bitmap indicates whether a frequency band pair in a predefined set of frequency band pairs and associated with the bit is supported.

[0145] Aspect 5: The method according to aspect 4, wherein the predefined set of frequency band pairs is programmed into a memory of the UE.

[0146] Aspect 6: The method according to aspect 4, wherein the capability query indicates the predefined set of frequency band pairs.

[0147] Aspect 7: The method according to any one of aspects 1 to 6, wherein the capability information indicates a switching situation for uplink transmission switching based on the one or more frequency band pairs and supported by the UE.

[0148] Aspect 8: The method according to any one of aspects 1 to 7, wherein the capability information further indicates a maximum number of multiple-input multiple-output layers for each frequency band pair.

[0149] Aspect 9: The method according to any one of aspects 1 to 8, wherein the one or more frequency band pairs include a plurality of frequency band pairs, and the capability information further indicates one or more switching periods associated with switching between frequency band pairs in the plurality of frequency band pairs.

[0150] Aspect 10: The method according to aspect 9, wherein the capability information comprises a table encoding the one or more switching periods.

[0151] Aspect 11: The method according to any one of aspects 9 to 10, wherein a switching period associated with switching from a first frequency band pair to a second frequency band pair is also associated with switching from the second frequency band pair to the first frequency band pair.

[0152] Aspect 12: The method according to any one of aspects 9 to 11, wherein the capability information omits one or more additional switching periods as default values.

[0153] Aspect 13: A method of wireless communication performed by a network entity, the method comprising: sending a capability query; and receiving capability information in response to the capability query, the capability information indicating one or more frequency band pairs of a plurality of possible frequency band pairs that a user equipment (UE) is configured to use.

[0154] Aspect 14: The method according to aspect 13, wherein the capability information includes a plurality of bits, the plurality of bits explicitly indicating one or more supported frequency band switching situations for the one or more frequency band pairs.

[0155] Aspect 15: The method according to aspect 14, wherein the capability information further indicates the number of antenna ports for each frequency band of the one or more frequency band pairs.

[0156] Aspect 16: The method according to aspect 13, wherein the capability information comprises a bitmap, wherein each bit of the bitmap indicates whether a frequency band pair in a predefined set of frequency band pairs and associated with the bit is supported.

[0157] Aspect 17: The method according to aspect 16, wherein the predefined set of frequency band pairs is programmed into a memory of the network entity.

[0158] Aspect 18: The method according to aspect 16, wherein the capability query indicates the predefined set of frequency band pairs.

[0159] Aspect 19: The method according to any one of aspects 13 to 18, wherein the capability information indicates a switching situation for uplink transmission switching based on the one or more frequency band pairs and supported by the UE.

[0160] Aspect 20: The method according to any one of aspects 13 to 19, wherein the capability information further indicates a maximum number of multiple-input multiple-output layers for each frequency band pair.

[0161] Aspect 21: A method according to any one of aspects 13 to 20, wherein the one or more frequency band pairs include a plurality of frequency band pairs, and the capability information further indicates one or more switching periods associated with switching between frequency band pairs in the plurality of frequency band pairs.

[0162] Aspect 22: The method according to aspect 21, wherein the capability information comprises a table encoding the one or more switching periods.

[0163] Aspect 23: The method according to any one of aspects 21 to 22, wherein a switching period associated with switching from a first frequency band pair to a second frequency band pair is also associated with switching from the second frequency band pair to the first frequency band pair.

[0164] Aspect 24: The method according to any one of aspects 21 to 23, wherein the capability information omits one or more additional switching periods as default values.

[0165] Aspect 25: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 12.

[0166] Aspect 26: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 12.

[0167] Aspect 27: An apparatus for wireless communication, the apparatus comprising at least one component configured to perform the method according to one or more of aspects 1 to 12.

[0168] Aspect 28: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 12.

[0169] Aspect 29: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 12.

[0170] Aspect 30: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 13 to 24.

[0171] Aspect 31: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 13 to 24.

[0172] Aspect 32: An apparatus for wireless communication, the apparatus comprising at least one component configured to perform the method according to one or more of aspects 13 to 24.

[0173] Aspect 33: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 13 to 24.

[0174] Aspect 34: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 13 to 24.

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

[0176] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0177] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0178] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0179] Any element, action or instruction used herein should not be interpreted as key or necessary, unless explicitly described as such. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only want to refer to a project, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to represent "based at least in part", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: Receiving capability inquiry; as well as Capability information is sent in response to the capability query, the capability information indicating one or more frequency band pairs of a plurality of possible frequency band pairs that the UE is configured to use. 2 . The apparatus according to claim 1 , wherein the capability information indicates a switching case for uplink transmission switching based on the one or more frequency band pairs and supported by the UE. 3 . The apparatus of claim 1 , wherein the capability information comprises a plurality of bits that explicitly indicate one or more supported frequency band switching scenarios for the one or more frequency band pairs. 4 . The apparatus of claim 3 , wherein the capability information further indicates a number of antenna ports for each of the one or more frequency band pairs. 5 . The apparatus of claim 1 , wherein the capability information comprises a bitmap, wherein each bit of the bitmap indicates whether a frequency band pair in a predefined set of frequency band pairs and associated with the bit is supported.

6. The apparatus of claim 5, wherein the predefined set of frequency band pairs is programmed into a memory of the UE. The apparatus of claim 5 , wherein the capability query indicates the predefined set of frequency band pairs.

8. The apparatus of claim 1, wherein the capability information further indicates a maximum number of multiple-input multiple-output layers for each frequency band pair.

9. The apparatus of claim 1, wherein the one or more frequency band pairs comprises a plurality of frequency band pairs, and the capability information further indicates one or more switching periods associated with switching between frequency band pairs in the plurality of frequency band pairs.

10. The apparatus of claim 9, wherein the capability information comprises a table encoding the one or more switching periods.

11. The apparatus of claim 9, wherein a switching period associated with switching from a first frequency band pair to a second frequency band pair is also associated with switching from the second frequency band pair to the first frequency band pair. 12 . The apparatus of claim 9 , wherein the capability information omits one or more additional switching periods as a default value.

13. An apparatus for wireless communication at a network entity, the apparatus comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: Send capability query; as well as Capability information is received in response to the capability query, the capability information indicating one or more frequency band pairs of a plurality of possible frequency band pairs that a user equipment (UE) is configured to use. 14 . The apparatus according to claim 13 , wherein the capability information indicates a switching case for uplink transmission switching based on the one or more frequency band pairs and supported by the UE.

15. The apparatus of claim 13, wherein the capability information comprises a plurality of bits that explicitly indicate one or more supported frequency band switching scenarios for the one or more frequency band pairs.

16. The apparatus of claim 15, wherein the capability information further indicates a number of antenna ports for each of the one or more frequency band pairs.

17. The apparatus of claim 13, wherein the capability information comprises a bitmap, wherein each bit of the bitmap indicates whether a frequency band pair in a predefined set of frequency band pairs and associated with the bit is supported.

18. The apparatus of claim 17, wherein the predefined set of frequency band pairs is programmed into a memory of the network entity.

19. The apparatus of claim 17, wherein the capability query indicates the predefined set of frequency band pairs.

20. The apparatus of claim 13, wherein the capability information further indicates a maximum number of multiple-input multiple-output layers for each frequency band pair.

21. The apparatus of claim 13, wherein the one or more frequency band pairs comprises a plurality of frequency band pairs, and the capability information further indicates one or more switching periods associated with switching between frequency band pairs in the plurality of frequency band pairs.

22. The apparatus of claim 21, wherein the capability information comprises a table encoding the one or more switching periods.

23. The apparatus of claim 21, wherein a switching period associated with switching from a first frequency band pair to a second frequency band pair is also associated with switching from the second frequency band pair to the first frequency band pair.

24. The apparatus of claim 21, wherein the capability information omits one or more additional switching periods as a default value.

25. A method of wireless communication performed by a user equipment (UE), the method comprising: Receiving capability inquiry; as well as Capability information is sent in response to the capability query, the capability information indicating one or more frequency band pairs of a plurality of possible frequency band pairs that the UE is configured to use. 26 . The method according to claim 25 , wherein the capability information indicates a switching case for uplink transmission switching based on the one or more frequency band pairs and supported by the UE.

27. The method of claim 25, wherein the capability information comprises a plurality of bits that explicitly indicate one or more supported frequency band switching scenarios for the one or more frequency band pairs.

28. The method of claim 25, wherein the capability information comprises a bitmap, wherein each bit of the bitmap indicates whether a frequency band pair in a predefined set of frequency band pairs and associated with the bit is supported.

29. The method of claim 25, wherein the one or more frequency band pairs comprises a plurality of frequency band pairs, and the capability information further indicates one or more switching periods associated with switching between frequency band pairs in the plurality of frequency band pairs.

30. A method of wireless communication performed by a network entity, the method comprising: Send capability query; as well as Capability information is received in response to the capability query, the capability information indicating one or more frequency band pairs of a plurality of possible frequency band pairs that a user equipment (UE) is configured to use.