Recommendations for cross-carrier scheduling

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may send a recommendation associated with a special secondary cell (sSCell) or a primary cell (PCell) for cross-carrier scheduling based at least in part on a sSCell failure. The UE may receive a configuration for the cross-carrier scheduling associated with the recommendation. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims the priority of Indian Patent Application No. 202221038750, filed on July 6, 2022, entitled “RECOMMENDATION FOR CROSS-CARRIER SCHEDULING” and assigned to the assignee of this patent application. The disclosure of the prior application is considered a part of this patent application and is incorporated into this patent application by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for recommendations for cross-carrier scheduling. Background Art

[0004] 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).

[0005] A wireless network may include one or more base stations that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. A "downlink" (or "DL") refers to the communication link from a base station to a UE, and an "uplink" (or "UL") refers to the communication link from a UE to a base station.

[0006] 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 using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with a cyclic prefix (CP) on the downlink, using 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, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. 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

[0007] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include sending a recommendation associated with an sSCell or a primary cell (PCell) for cross-carrier scheduling based at least in part on a special secondary cell (sSCell) failure. The method may include receiving a configuration for the cross-carrier scheduling associated with the recommendation.

[0008] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include receiving a recommendation associated with an sSCell or PCell for cross-carrier scheduling. The method may include sending a configuration for the cross-carrier scheduling associated with the recommendation.

[0009] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include sending a recommendation for a value indicating how a control channel element (CCE) is distributed across an sSCell and a PCell for cross-carrier scheduling. The method may include receiving a configuration for cross-carrier scheduling associated with the recommendation.

[0010] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include receiving a recommendation for a value indicating how CCEs are distributed across an sSCell or a PCell for cross-carrier scheduling. The method may include sending a configuration for cross-carrier scheduling associated with the recommendation.

[0011] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send a recommendation associated with an sSCell or PCell for cross-carrier scheduling based at least in part on an sSCell failure. The one or more processors may be configured to receive a configuration for the cross-carrier scheduling associated with the recommendation.

[0012] Some aspects described herein relate to a network entity for wireless communication. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a recommendation associated with an sSCell or PCell for cross-carrier scheduling. The one or more processors may be configured to send a configuration associated with the recommendation for the cross-carrier scheduling.

[0013] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send a recommendation for a value indicating how CCEs are distributed across sSCells or PCells for cross-carrier scheduling. The one or more processors may be configured to receive a configuration for cross-carrier scheduling associated with the recommendation.

[0014] Some aspects described herein relate to a network entity for wireless communication. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a recommendation for a value indicating how CCEs are distributed across sSCells or PCells for cross-carrier scheduling. The one or more processors may be configured to send a configuration for cross-carrier scheduling associated with the recommendation.

[0015] 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 send a recommendation associated with an sSCell or PCell for cross-carrier scheduling based at least in part on an sSCell failure. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a configuration for the cross-carrier scheduling associated with the recommendation.

[0016] 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 receive a recommendation associated with an sSCell or PCell for cross-carrier scheduling. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to send a configuration for the cross-carrier scheduling associated with the recommendation.

[0017] 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 send a recommendation for a value indicating how CCEs are distributed across sSCells or PCells for cross-carrier scheduling. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a configuration for cross-carrier scheduling associated with the recommendation.

[0018] 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 receive a recommendation for a value indicating how CCEs are distributed across sSCells or PCells for cross-carrier scheduling. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to send a configuration for cross-carrier scheduling associated with the recommendation.

[0019] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a recommendation associated with an sSCell or PCell for cross-carrier scheduling based at least in part on an sSCell failure. The apparatus may include means for receiving a configuration for the cross-carrier scheduling associated with the recommendation.

[0020] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a recommendation associated with an sSCell or PCell for cross-carrier scheduling. The apparatus may include means for sending a configuration for the cross-carrier scheduling associated with the recommendation.

[0021] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a recommendation for a value indicating how CCEs are distributed across sSCells or PCells for cross-carrier scheduling. The apparatus may include means for receiving a configuration for cross-carrier scheduling associated with the recommendation.

[0022] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a recommendation for a value indicating how CCEs are distributed across sSCells or PCells for cross-carrier scheduling. The apparatus may include means for sending a configuration for cross-carrier scheduling associated with the recommendation.

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

[0024] 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 to the claims.

[0025] 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 (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. 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

[0026] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate 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.

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

[0028] Figure 2 is a diagram illustrating an example of a network entity communicating with a user equipment (UE) in a wireless network according to the present disclosure.

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

[0030] Figure 4 Examples of multiple carriers or connections according to the present disclosure are shown.

[0031] Figure 5 is a diagram illustrating an example of cross-carrier scheduling according to the present disclosure.

[0032] Figure 6 is a diagram illustrating an example of control channel element distribution according to the present disclosure.

[0033] Figure 7 is a diagram illustrating an example of configuring cross-carrier scheduling according to the present disclosure.

[0034] Figure 8 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0035] Fig. 9 is a diagram illustrating an example process performed, for example, by a network entity according to the present disclosure.

[0036] Fig.10 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0037] Fig.11 is a diagram illustrating an example process performed, for example, by a network entity according to the present disclosure.

[0038] Figure 12 to Figure 13 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0039] 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 interpreted as being limited to any specific structure or function presented throughout the present disclosure. On the contrary, 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 present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present 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 devices or methods implemented using other structures, functions, or structures and functions 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 claims.

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

[0041] 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 applied to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0042] 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, among other examples. The wireless network 100 may include a user equipment (UE) 120 or a plurality of UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e). The wireless network 100 may also include one or more network entities, such as a base station 110 (shown as BS110a, BS110b, BS110c, and BS110d) and / or other network entities. The base station 110 is a network entity that communicates with the UE 120. Base station 110 (sometimes referred to as BS) 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, and / or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of ​​a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.

[0043] The base station 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 base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown in , BS 110a may be a macro base station for macro cell 102a, BS 110b may be a pico base station for pico cell 102b, and BS 110c may be a femto base station for femto cell 102c. A base station may support one or more (eg, three) cells.

[0044] In some examples, the cell may not necessarily be fixed, and the geographic area of ​​the cell may move according to the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 may be interconnected with each other and / or to one or more other base stations 110 or network entities in the wireless network 100 using any suitable transport network via various types of backhaul interfaces (such as direct physical connections or virtual networks).

[0045] In some aspects, the term "base station" (e.g., base station 110) or "network entity" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, and / or one or more components thereof. For example, in some aspects, a "base station" or "network entity" may refer to a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network entity" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with base station 110). In some aspects, the term "base station" or "network entity" 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 geographical location or in different geographical locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network entity" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network entity" may refer to one or more virtual base stations and / 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 entity" may refer to one of the base station functions but not the other. In this way, a single device may include more than one base station.

[0046] The wireless network 100 may include one or more relay stations. A relay station is a network entity that can receive transmissions of data from an upstream station (e.g., a network entity or UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a network entity). 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 , BS 110d (eg, a relay base station) can communicate with BS 110a (eg, a macro base station) and UE 120d to facilitate communication between BS 110a and UE 120d. Base station 110 that relays communication may be referred to as a relay station, relay base station, relay, etc.

[0047] The wireless network 100 may be a heterogeneous network having network entities including different types of BSs, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 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 base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0048] The network controller 130 may be coupled to or in communication with a set of network entities and may provide coordination and control for the network entities. The network controller 130 may communicate with the base station 110 via a backhaul communication link. The network entities may also communicate directly with each other or indirectly via a wireless or wired backhaul communication link.

[0049] UE 120 may be distributed throughout 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, and / or any other suitable device configured to communicate via a wireless medium.

[0050] Some UE 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UE. MTC UE and / or eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor and / or a location tag, which may communicate with a network entity, another device (e.g., a remote device) or some other entity. Some UE 120 may be considered as an Internet of Things (IoT) device and / or may be implemented as a NB-IoT (narrowband IoT) device. Some UE 120 may be considered as customer premises equipment. UE 120 may be included in 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 operationally coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0051] 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, an air interface, etc. Frequency may be referred to as a carrier, a 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.

[0052] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using a network entity as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, 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 base station 110.

[0053] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which 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 portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes occur with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0054] 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, and therefore 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.

[0055] In view of the above examples, unless otherwise explicitly stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term can be broadly referred to as a frequency that can be lower than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise explicitly stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term can be broadly referred to as a frequency that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can 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) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0056] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may send a recommendation associated with a sSCell or a primary cell (PCell) for cross-carrier scheduling based at least in part on a special secondary cell (sSCell) failure. The communication manager 140 may receive a configuration for cross-carrier scheduling associated with the recommendation. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0057] In some aspects, the communication manager 140 may send a recommendation for a value indicating how control channel elements (CCEs) are distributed across sSCells and PCells for cross-carrier scheduling. The communication manager 140 may receive a configuration for cross-carrier scheduling associated with the recommendation. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0058] In some aspects, a network entity (e.g., base station 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive a recommendation associated with an sSCell or PCell for cross-carrier scheduling. The communication manager 150 may send a configuration for cross-carrier scheduling associated with the recommendation.

[0059] In some aspects, the communication manager 150 may receive a recommendation for a value indicating how CCEs are distributed across sSCells or PCells for cross-carrier scheduling. The communication manager 150 may send a configuration for cross-carrier scheduling associated with the recommendation. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0060] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 Described differently.

[0061] Figure 2 2 is a diagram illustrating an example 200 of a network entity (e.g., base station 110) communicating with UE 120 in a wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

[0062] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the 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 (CQI) received from the UE 120. The base station 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 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., pre-decoding) 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 further process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0063] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the base station 110 and / or other base stations 110, and a set of received signals (e.g., R received signals) may be provided 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.

[0064] 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 network entities via the communication unit 294.

[0065] 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 (within a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or 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.

[0066] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a 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 a network entity. 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 aspects of any of the methods described herein (eg, with reference to Figures 4 to 13 ).

[0067] At a network entity (e.g., base station 110), uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., a demodulator component of modem 232 shown as DEMOD), detected by MIMO detector 236 (where applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 may provide decoded data to data sink 239 and decoded control information to controller / processor 240. The network entity may include a communication unit 244 and may communicate with network controller 130 via communication unit 244. The network entity may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the network entity may include a modulator and a demodulator. In some examples, the network entity 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 aspects of any of the methods described herein (e.g., reference 20 to FIG. 1 ). Figures 4 to 13 ).

[0068] A controller / processor of a network entity (e.g., controller / processor 240 of base station 110), controller / processor 280 of UE 120, and / or Figure 2 Any other components of may perform one or more techniques associated with the recommendation for cross-carrier scheduling, as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Figure 8 The process of 800 Fig. 9 The process of 900 Fig.10 The process of 1000 Fig.11 1100 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for a network entity 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, one or more instructions, when executed (e.g., directly or after compilation, conversion, and / or interpretation) by one or more processors of a network entity and / or UE 120, may cause the one or more processors, UE 120, and / or network entity to perform or direct, for example, Figure 8 The process of 800 Fig. 9 The process of 900 Fig.10 The process of 1000 Fig.11 The process 1100 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.

[0069] In some aspects, the UE 120 includes: a means for sending a recommendation associated with an sSCell or PCell for cross-carrier scheduling based at least in part on an sSCell failure; and / or a means for receiving a configuration for cross-carrier scheduling associated with the recommendation. The means for the UE 120 to perform the operations described herein may include, for example, one or more of the following: the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0070] In some aspects, a network entity (e.g., a base station 110) includes: a component for receiving a recommendation associated with an sSCell or PCell for cross-carrier scheduling; and / or a component for sending a configuration for cross-carrier scheduling associated with the recommendation. In some aspects, the component for the network entity to perform the operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0071] In some aspects, the UE 120 includes means for sending a recommendation for a value indicating how CCEs are distributed across sSCells or PCells for cross-carrier scheduling and / or means for receiving a configuration for cross-carrier scheduling associated with the recommendation.

[0072] In some aspects, the network entity includes: means for receiving a recommendation for a value indicating how CCEs are distributed across sSCells or PCells for cross-carrier scheduling; and / or means for sending a configuration for cross-carrier scheduling associated with the recommendation.

[0073] Although Figure 2 The blocks in the 200 and 210 are illustrated as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to 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.

[0074] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 Described differently.

[0075] Figure 3 is a diagram illustrating an example of a decomposed base station 300 according to the present disclosure.

[0076] 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 radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station, or one or more units (or one or more components) that perform base station functionality can be implemented in an aggregated architecture or a decomposed architecture. For example, a BS (such as a node B, an evolved NB (eNB), an NR BS, a 5GNB, an access point (AP), a TRP or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0077] The aggregated base station can be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. The decomposed base station can be configured to utilize a protocol stack 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 aspects, the CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed in one or more other RAN nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).

[0078] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an 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)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0079] The decomposed base station 300 architecture may include one or more CUs 310 that may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed base station units (such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via corresponding midhaul links (such as an F1 interface). The DU 330 may communicate with one or more RUs 340 via corresponding fronthaul links. Fronthaul links, midhaul links, and backhaul links may generally be referred to as "communication links." The RU 340 may communicate with a corresponding UE 120 via one or more RF access links. In some aspects, a UE 120 may be served simultaneously by multiple RUs 340. The DU 330 and the RU 340 may also be referred to as "O-RAN DU (O-DU)" and "O-RAN RU (O-RU)", respectively. The network entity may include a CU, DU, RU, or any combination of CU, DU, and RU. The network entity may include a decomposed base station or one or more components of a decomposed base station, such as a CU, DU, RU, or any combination of CU, DU, and RU. The network entity may also include one or more of the following: a TRP, a relay station, a passive device, an intelligent reflective surface (IRS), or other components that may provide a network interface or service for a UE, a mobile station, a sensor / actuator, or other wireless device.

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

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

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

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

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

[0085] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions 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.

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

[0087] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 Described differently.

[0088] Figure 4 is a diagram illustrating an example of multiple carriers or connections according to the present disclosure.

[0089] Figure 4 An example 400 of carrier aggregation is shown. 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. Carriers in the same or different frequency bands may be combined. Additionally or alternatively, contiguous carriers or non-contiguous carriers may be combined. Base station 110 may configure carrier aggregation for UE 120 (such as in an RRC message, downlink control information (DCI), and / or another signaling message).

[0090] 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. 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. 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.

[0091] In carrier aggregation, a UE 120 may be configured with a primary carrier or PCell and one or more secondary carriers or secondary cells (SCells), as shown in example 400. In some aspects, the primary carrier may carry control information (e.g., DCI and / or scheduling information) for scheduling data communications on one or more secondary carriers, which may be referred to as cross-carrier scheduling (CCS). 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.

[0092] Figure 4 An example 402 of dual connectivity is also shown. Example 402 is for an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA)-NR Dual Connectivity (ENDC) mode. In ENDC mode, UE 120 communicates using LTE RAT on a primary cell group (MCG), and UE 120 communicates using NR RAT on a secondary cell group (SCG). However, the various aspects described herein may be applicable to ENDC mode (e.g., where the MCG is associated with the LTE RAT and the SCG is associated with the NR RAT), NR-E-UTRA Dual Connectivity (NEDC) mode (e.g., where the MCG is associated with the NR RAT and the SCG is associated with the LTE RAT), NR Dual Connectivity (NRDC) mode (e.g., where the MCG is associated with the NR RAT and the SCG is also associated with the NR RAT), or another dual connectivity mode (e.g., where the MCG is associated with the first RAT and the SCG is associated with one of the first RAT or the second RAT). ENDC mode is sometimes referred to as NR or 5G non-standalone (NSA) mode. Thus, as used herein, “dual connectivity mode” may refer to an ENDC mode, a NEDC mode, an NRDC mode, and / or another type of dual connectivity mode.

[0093] As shown in example 402, the UE 120 can communicate with both an eNB (e.g., a 4G base station 110) and a gNB (e.g., a 5G base station 110), and the eNB and gNB can communicate with a 4G / LTE core network (shown as an evolved packet core (EPC) including a mobility management entity (MME), a packet data network gateway (PGW), a serving gateway (SGW), and / or other devices) (e.g., directly or indirectly). In example 402, the PGW and SGW are collectively referred to as P / SGW. In some aspects, the eNB and gNB can be co-located at the same base station 110. In some aspects, the eNB and gNB can be included in different base stations 110 (e.g., may not be co-located).

[0094] As further illustrated by example 402, in some aspects, a wireless network permitting operation in 5G NSA mode may permit such operation using an MCG for a first RAT (e.g., an LTE RAT or a 4G RAT) and an SCG for a second RAT (e.g., an NR RAT or a 5G RAT). In this scenario, the UE 120 may communicate with the eNB via the MCG and may communicate with the gNB via the SCG. In some aspects, the MCG may anchor the network connection between the UE 120 and the 4G / LTE core network (e.g., for mobility, coverage, and / or control plane information), and the SCG may be added as an additional carrier to increase throughput (e.g., for data traffic and / or user plane information). In some aspects, the gNB and the eNB may not communicate user plane information between each other. In some aspects, a UE 120 operating in dual connectivity mode may be concurrently connected to an LTE base station 110 (e.g., an eNB) and an NR base station 110 (e.g., a gNB) (e.g., in the case of ENDC or NEDC), or may be concurrently connected to one or more base stations 110 using the same RAT (e.g., in the case of NRDC). In some aspects, an MCG may be associated with a first frequency band (e.g., a sub-6 GHz band and / or a FR1 band), and an SCG may be associated with a second frequency band (e.g., a mmWave band and / or a FR2 band).

[0095] UE 120 may communicate via MCG and SCG using one or more radio bearers (e.g., data radio bearers (DRBs) and / or signaling radio bearers (SRBs)). For example, UE 120 may send or receive data via the MCG and / or SCG using one or more DRBs. Similarly, UE 120 may send or receive control information (e.g., RRC information and / or measurement reports) using one or more SRBs. In some aspects, a radio bearer may be dedicated to a specific cell group (e.g., a radio bearer may be an MCG bearer or an SCG bearer). In some aspects, a radio bearer may be a split radio bearer. Split radio bearers may be split in the uplink and / or downlink. For example, a DRB may be split on the downlink (e.g., UE 120 may receive downlink information for an MCG or SCG in a DRB) but not split on the uplink (e.g., an uplink may not be split from a primary path to an MCG or SCG such that UE 120 transmits in the uplink only on the primary path). In some aspects, the DRB may be split on the uplink from the primary path to the MCG or SCG. The DRB split in the uplink may use the primary path to send data until the size of the uplink transmit buffer meets the uplink data split threshold. If the uplink transmit buffer meets the uplink data split threshold, the UE 120 may use the DRB to send data to the MCG or SCG. The PCell may be part of the MCG and the SCell may be part of the SCG.

[0096] As indicated above, Figure 4 Some examples are provided. Other examples can be found in Figure 4 Described differently.

[0097] Figure 5 is a diagram illustrating an example 500 of a CCS according to the present disclosure.

[0098] In dynamic spectrum sharing (DSS), symbols containing LTE CRS cannot be used for NR physical downlink control channel (PDCCH). This leads to resource limitations, especially for NR-PDCCH using non-LTE-CRS symbols. DSS enhancement can solve the NR-PDCCH capacity problem by using CCS from SCell to main SCell or P(S)Cell. The SCell used for this purpose may be referred to as a special SCell (sSCell) for CCS with P(S)Cell. The UE can monitor the PDCCH on the P(S)Cell for self-scheduling. Example 500 shows examples of SCell, P(S)Cell, sSCell, and SCell.

[0099] As indicated above, Figure 5are provided as examples. Other examples can be found in the Figure 5 Described differently.

[0100] Figure 6 is a diagram illustrating an example 600 of CCE distribution according to the present disclosure.

[0101] A CCE may be a combination of resource element groups (REGs) including control information. The aggregation level may indicate the number of CCEs allocated for the PDCCH. Since both the PCell and sSCell may carry CCEs, the network entity may configure the value of α (alpha) to distribute the CCEs for the PDCCH between the PCell and the sSCell. CCS involves using CCEs on both the sSCell and the PCell to schedule data. Changing α changes how many CCEs are received by the UE on the PCell relative to the sSCell. Example 600 shows how some CCEs may be moved to the sSCell based on α. ​​Blind decoding (DC) and CCE capacity for P(S)Cell may be based at least in part on α and the minimum of the maximum number of slots for the PDCCH and the total number of slots for the PDCCH. The BD / CCE restriction for the sSCell may be based at least in part on (1-α) and the minimum of the maximum number of slots for the PDCCH and the total number of slots for the PDCCH.

[0102] However, since the use of sSCell is similar to carrier aggregation configuration, there is no process for handling radio link failures. Therefore, if the sSCell becomes bad or if sSCell decoding is missed due to, for example, multiple subscriber identity module (MSIM) restrictions, performance on the PCell will be degraded. Bad decoding degrades communications and limits throughput. Degraded communications waste processing resources and signaling resources.

[0103] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 Described differently.

[0104] Figure 7 is a diagram illustrating an example 700 of configuring a CCS according to the present disclosure. Figure 7 As shown, a network entity 710 (eg, network entity) and a UE 720 (eg, UE 120) may communicate with each other via, for example, a wireless network (eg, wireless network 100).

[0105] According to various aspects described herein, UE 720 may provide a recommendation for deactivating sSCell, redistributing CCE, or changing sSCell or PCell in case of sSCell failure for sSCell or PCell. Network entity 710 may reconfigure CCS of UE 720 and improve CCE and data throughput, which saves processing resources and signaling resources.

[0106] Example 700 illustrates a configuration of a UE 720 based at least in part on a recommendation from the UE 720. As indicated by reference numeral 725, the UE 720 may send a recommendation associated with an sSCell or PCell for CCS based at least in part on an sSCell failure. The sSCell may fail if the throughput of the sSCell drops below a throughput threshold, if the quality of the sSCell drops below a quality threshold, if the RSRP of the sSCell drops below an RSRP threshold, and / or if the reliability of the sSCell drops below a reliability threshold. The sSCell may be faulty or fail similarly to a radio link failure. As indicated by reference numeral 730, the network entity 710 may send a configuration for CCS, wherein the configuration is associated with the recommendation. As indicated by reference numeral 735, the UE 720 may perform an action based at least in part on the configuration.

[0107] In some aspects, the recommendation is to deactivate the sSCell in the event of a sSCell failure. The recommendation may be included in the UE assistance information. Thus, the action may include deactivating the sSCell so that the CCE is carried on the PCell. This may result in the CCE being carried only on the PCell. In this way, the CCE is not lost by the failed sSCell.

[0108] There may be multiple SCells configured by the network entity 710. In some aspects, the recommendation may be an indication of which cell should be the sSCell of the PCell. In some aspects, the UE 720 may identify a neighboring SCell that meets one or more thresholds or performs better than an existing sSCell. The UE 720 may recommend a change in the sSCell. The UE 720 may determine the SCell for the sSCell based at least in part on any conflicts, including conflicts involving multiple SIMs. For example, if a specific SCell is operating in a frequency band with a conflict when running on an MSIM, the UE 720 may avoid selecting the SCell as the sSCell. Therefore, the action performed by the UE 720 may be to select a new sSCell based at least in part on receiving a configuration indicating a switch to a new sSCell.

[0109] In some aspects, the UE 720 may recommend a cell as a PCell in a carrier aggregation configuration. For example, the PCell may typically be a serving cell, but if the sSCell is better in terms of channel conditions, interference or network load, and other conditions, the UE 720 may recommend the sSCell or another SCell as the PCell. The configuration may specify a new PCell to replace or supplement the PCell based at least in part on the sSCell or another SCell having a higher throughput or higher reliability than the PCell. In this way, the network entity 710 may perform a handover of the UE 720 to a better PCell. If a better SCell is available, this may avoid using a cell configured with a DSS as the PCell. Thus, the action performed by the UE 720 may be to use the SCell that is recommended and is part of the received configuration as the PCell.

[0110] In some aspects, the UE 720 may recommend a value for α. For example, if the sSCell channel state or traffic state is poor or the sSCell must be tuned away due to MSIM restrictions, the UE 720 may recommend a value for α of 1 so that all CCEs are carried on the PCell. If the sSCell is good and has no restrictions, and the PCell performs poorly (does not meet a threshold) or is heavily loaded, the value of α may be set to 0 or close to 0. In a scenario where both the PCell and the sSCell are sufficient or both perform poorly, the UE 720 may determine and recommend a value for α based at least in part on network load meeting a load threshold, a block error rate (BLER) meeting a BLER threshold (e.g., a maximum BLER), a channel state, a traffic state, and / or other states. The actions performed by the UE 720 may include, based at least in part on a configuration associated with the recommendation, expecting more CCEs on the PCell or more CCEs on the sSCell. As a result, more CCEs will be received correctly, and CCS based on CCEs will improve. The power and performance of the DSS will also be improved. Although various aspects have been described with respect to carrier aggregation and / or dual connectivity, the aspects described herein may also be applicable to NR standalone (SA) networks.

[0111] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 Described differently.

[0112] Figure 8 8 is a diagram illustrating an example process 800 performed, for example, by a UE according to the present disclosure. Example process 800 is an example in which a UE (eg, UE 120, UE 720) performs operations associated with a recommendation for CCS when an sSCell is faulty (failure occurs).

[0113] like Figure 8 As shown, in some aspects, process 800 may include sending a recommendation associated with an sSCell or PCell for CCS based at least in part on the sSCell failure (block 810). Fig.12 The depicted communication manager 1208 and / or sending component 1204) may send a recommendation associated with an sSCell or PCell for CCS based at least in part on an sSCell failure, as described above.

[0114] like Figure 8 As further shown, in some aspects, process 800 may include receiving a configuration for a CCS associated with a recommendation (block 820). Fig.12 The depicted communication manager 1208 and / or receiving component 1202 can receive a configuration for the CCS associated with a recommendation, as described above.

[0115] Process 800 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 the first aspect, as part of CCS, sSCell and PCell are used to send CCE.

[0117] In a second aspect, alone or in combination with the first aspect, a recommendation is to deactivate the sSCell.

[0118] In a third aspect, alone or in combination with one or more of the first and second aspects, deactivation of a specified sSCell is configured, and process 800 includes stopping use of the sSCell based at least in part on the configuration.

[0119] In a fourth aspect, alone or in combination with one or more of the first to third aspects, it is recommended to indicate a new sSCell for CCS with a PCell.

[0120] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, a configuration specifies activation of a new sSCell, and process 800 includes using the new sSCell based at least in part on the configuration.

[0121] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, a configuration specifies activation of a new sSCell, and process 800 includes switching from the sSCell to the new sSCell based at least in part on the configuration.

[0122] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, a recommendation is made to indicate a new PCell to replace or supplement the PCell based at least in part on the sSCell having a higher throughput or higher reliability than the PCell.

[0123] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, configuration specifies a new PCell, and process 800 includes using the new PCell for CCS based at least in part on the configuration.

[0124] although Figure 8 An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8 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 800 may be performed in parallel.

[0125] Fig. 9 900 is a diagram illustrating an example process 900 performed, for example, by a network entity according to the present disclosure. Example process 900 is an example in which a network entity (e.g., base station 110, network entity 710) performs operations associated with configuring a UE for CCS when an sSCell is faulty (failure occurs).

[0126] like Fig. 9 As shown, in some aspects, process 900 may include receiving a recommendation associated with an sSCell or PCell for CCS (block 910). For example, a network entity (e.g., using Fig.13 The depicted communication manager 1308 and / or receiving component 1302) can receive a recommendation associated with an sSCell or PCell for CCS, as described above.

[0127] like Fig. 9 As further shown, in some aspects, process 900 may include sending a configuration for the CCS associated with the recommendation (block 920). Fig.13 The depicted communication manager 1308 and / or sending component 1304) can send a configuration for the CCS associated with the recommendation, as described above.

[0128] Process 900 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.

[0129] In a first aspect, process 900 includes generating a configuration based at least in part on a recommendation.

[0130] In a second aspect, alone or in combination with the first aspect, generating the configuration includes generating the configuration further based on a channel state or a traffic state of the sSCell or PCell.

[0131] In a third aspect, alone or in combination with one or more of the first and second aspects, a recommendation is to deactivate sSCell.

[0132] In a fourth aspect, alone or in combination with one or more of the first to third aspects, deactivation of a designated sSCell is configured.

[0133] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, it is recommended to indicate a new sSCell for CCS with a PCell.

[0134] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, activation of a designated new sSCell is configured.

[0135] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, a new PCell indicating that the PCell is to be replaced or supplemented is recommended.

[0136] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the configuration specifies that the new PCell is to replace or supplement the PCell.

[0137] although Fig. 9 An example block diagram of process 900 is shown, but in some aspects, process 900 may include Fig. 9 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 900 may be performed in parallel.

[0138] Fig.10 1 is a diagram illustrating an example process 1000 performed, for example, by a UE according to the present disclosure. Example process 1000 is an example in which a UE (eg, UE 120, UE 720) performs operations associated with a recommendation for CCS when an sSCell is faulty (failure occurs).

[0139] like Fig.10 As shown, in some aspects, process 1000 may include sending a recommendation for a value indicating how CCEs are distributed across sSCells and PCells for CCS (block 1010). Fig.12 The depicted communication manager 1208 and / or sending component 1204) can send recommendations for values ​​indicating how CCEs are distributed across sSCells and PCells for CCS, as described above.

[0140] like Fig.10 As further shown, in some aspects, process 1000 may include receiving a configuration for a CCS associated with a recommendation (block 1020). Fig.12 The depicted communication manager 1208 and / or receiving component 1202 can receive a configuration for the CCS associated with a recommendation, as described above.

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

[0142] In a first aspect, the value indicates that more CCEs are used for sSCell than for PCell.

[0143] In a second aspect, alone or in combination with the first aspect, the value indicates that more CCEs are used for the PCell than for the sSCell. In some aspects, the value may indicate that the amount of CCEs is equal (substantially equal) between the PCell and the sSCell.

[0144] In a third aspect, alone or in combination with one or more of the first and second aspects, the value is based at least in part on one or more of: an sSCell channel state or a PCell channel state.

[0145] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the value is based at least in part on one or more of the following: the BLER of the sSCell satisfies the BLER threshold or the BLER of the PCell satisfies the BLER threshold.

[0146] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the value is based at least in part on one or more of: sSCell traffic state or PCell traffic state.

[0147] although Fig.10 An example block diagram of process 1000 is shown, but in some aspects, process 1000 may include Fig.10 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1000. Additionally or alternatively, two or more of the blocks in the process 1000 may be performed in parallel.

[0148] Fig.11 is a diagram illustrating an example process 1100, performed, for example, by a network entity, according to the present disclosure. The example process 1100 is an example in which a network entity (eg, base station 110, network entity 710) performs operations associated with a recommendation for a CCS.

[0149] like Fig.11 As shown, in some aspects, process 1100 may include receiving a recommendation for a value indicating how CCEs are distributed across sSCells and PCells for CCS (block 1110). For example, a network entity (e.g., using Fig.13 The depicted communication manager 1308 and / or receiving component 1302) can receive a recommendation for values ​​indicating how CCEs are distributed across sSCells and PCells for CCS, as described above.

[0150] like Fig.11 As further shown, in some aspects, process 1100 may include sending a configuration for the CCS associated with the recommendation (block 1120). Fig.13 The depicted communication manager 1308 and / or sending component 1304) can send a configuration for the CCS associated with the recommendation, as described above.

[0151] Process 1100 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.

[0152] In a first aspect, a value indicates that more CCEs are used for sSCell than for PCell, and the configuration includes the value.

[0153] In a second aspect, alone or in combination with the first aspect, a value indicates that more CCEs are used for the PCell than for the sSCell, and the configuration includes the value. In some aspects, a value may indicate that the amount of CCEs is equal (substantially equal) between the PCell and the sSCell.

[0154] In a third aspect, alone or in combination with one or more of the first and second aspects, the configuration is based at least in part on a value and one or more of: an sSCell channel state or a PCell channel state.

[0155] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the configuration is based at least in part on a value and one or more of: the BLER of the sSCell satisfies a BLER threshold or the BLER of the PCell satisfies a BLER threshold.

[0156] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the configuration is based at least in part on a value and one or more of: an sSCell traffic state or a PCell traffic state.

[0157] although Fig.11An example block diagram of process 1100 is shown, but in some aspects, process 1100 may include Fig.11 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 1100 may be performed in parallel.

[0158] Fig.12 1 is a diagram of an example apparatus 1200 for wireless communication according to the present disclosure. Apparatus 1200 may be a UE (e.g., UE 120, UE 720), or a UE may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202 and a transmitting component 1204 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using receiving component 1202 and transmitting component 1204. As further shown, apparatus 1200 may include a communication manager 1208. Communication manager 1208 may control and / or otherwise manage one or more operations of receiving component 1202 and / or transmitting component 1204. In some aspects, communication manager 1208 may include a communication manager 1208 in conjunction with receiving component 1202 and / or transmitting component 1204. Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the UE described herein. The communication manager 1208 may be or be similar to Figure 1 and Figure 2 For example, in some aspects, the communication manager 1208 can be configured to perform one or more of the functions described as being performed by the communication manager 140. In some aspects, the communication manager 1208 can include a receiving component 1202 and / or a sending component 1204. The communication manager 1208 can include a recommendation component 1210, among other things.

[0159] In some aspects, the apparatus 1200 may be configured to perform Figures 1 to 7 Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as Figure 8 The process of 800 Fig.10 In some aspects, the apparatus 1200 and / or Fig.12 One or more of the components shown in the figure may include a combination of Figure 2 Additionally or alternatively, Fig.12 One or more of the components shown may be combined with Figure 2Additionally or alternatively, one or more components in the set of components 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 may be executed by a controller or processor to perform the function or operation of the component.

[0160] The receiving component 1202 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1206. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 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 one or more other components of the device 1200. In some aspects, the receiving component 1202 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of a described UE.

[0161] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1206. In some aspects, one or more other components of the device 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 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 1206. In some aspects, the transmitting component 1204 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 1204 can be co-located with the receive component 1202 in a transceiver.

[0162] In some aspects, the sending component 1204 can send a recommendation associated with an sSCell or PCell for CCS based at least in part on the sSCell failure. The recommending component 1210 can generate a recommendation based at least in part on the traffic state and / or channel state of the sSCell, PCell, or other SCell. The receiving component 1202 can receive a configuration for CCS associated with the recommendation.

[0163] In some aspects, sending component 1204 can send a recommendation for values ​​indicating how CCEs are distributed across sSCells and PCells for CCS. Receiving component 1202 can receive a configuration for CCS associated with the recommendation.

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

[0165] Fig.13 is a diagram of an example apparatus 1300 for wireless communication according to the present disclosure. Apparatus 1300 may be a network entity (e.g., base station 110, network entity 710), or a network entity may include apparatus 1300. In some aspects, apparatus 1300 includes a receiving component 1302 and a transmitting component 1304 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1300 may communicate with another apparatus 1306 (such as a UE, a base station, or another wireless communication device) using receiving component 1302 and transmitting component 1304. As further shown, apparatus 1300 may include a communication manager 1308. Communication manager 1308 may control and / or otherwise manage one or more operations of receiving component 1302 and / or transmitting component 1304. In some aspects, communication manager 1308 may include a communication manager 1308 in conjunction with Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the network entities described. The communication manager 1308 may be or be similar to Figure 1 and Figure 2 For example, in some aspects, the communications manager 1308 can be configured to perform one or more of the functions described as being performed by the communications manager 150. In some aspects, the communications manager 1308 can include a receiving component 1302 and / or a sending component 1304. The communications manager 1308 can include a configuring component 1310, among other things.

[0166] In some aspects, the apparatus 1300 may be configured to perform Figures 1 to 8Additionally or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as Fig. 9 The process of 900 Fig.10 In some aspects, Fig.13 The device 1300 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.13 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components 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 may be executed by a controller or processor to perform the function or operation of the component.

[0167] The receiving component 1302 may receive communications from the device 1306, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1302 may provide the received communications to one or more other components of the device 1300. In some aspects, the receiving component 1302 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 one or more other components of the device 1300. In some aspects, the receiving component 1302 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 entities.

[0168] Transmit component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1306. In some aspects, one or more other components of device 1300 may generate communications and may provide the generated communications to transmit component 1304 for transmission to device 1306. In some aspects, transmit component 1304 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 1306. In some aspects, transmit component 1304 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 entities. In some aspects, the transmit component 1304 can be co-located with the receive component 1302 in a transceiver.

[0169] In some aspects, receiving component 1302 can receive a recommendation associated with an sSCell or PCell for CCS. Sending component 1304 can send a configuration for CCS associated with the recommendation. Configuration component 1310 can generate a configuration based at least in part on the recommendation.

[0170] In some aspects, receiving component 1302 can receive a recommendation for values ​​indicating how CCEs are distributed across sSCells and PCells for CCS. Sending component 1304 can send a configuration for CCS associated with the recommendation.

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

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

[0173] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: sending a recommendation associated with an sSCell or a primary cell (PCell) for cross-carrier scheduling based at least in part on a special secondary cell (sSCell) failure; and receiving a configuration for the cross-carrier scheduling associated with the recommendation.

[0174] Aspect 2: The method according to aspect 1, wherein as part of the cross-carrier scheduling, the sSCell and the PCell are used to send control channel elements (CCEs).

[0175] Aspect 3: The method according to aspect 1 or 2, wherein the recommendation is to deactivate the sSCell.

[0176] Aspect 4: The method according to aspect 3, wherein the configuration specifies deactivation of the sSCell, and wherein the method further comprises ceasing use of the sSCell based at least in part on the configuration.

[0177] Aspect 5: The method according to aspect 1 or 2, wherein the recommendation indicates a new sSCell for cross-carrier scheduling with the PCell.

[0178] Aspect 6: The method according to any one of aspects 1 to 5, wherein the configuration specifies activation of the new sSCell, and wherein the method further comprises using the new sSCell based at least in part on the configuration.

[0179] Aspect 7: The method according to aspect 5, wherein the configuration specifies activation of the new sSCell, and wherein the method further comprises switching from the sSCell to the new sSCell based at least in part on the configuration.

[0180] Aspect 8: The method according to any one of aspects 1 to 7, wherein the recommendation indicates a new PCell to replace or supplement the PCell based at least in part on the sSCell having a higher throughput or a higher reliability than the PCell.

[0181] Aspect 9: The method according to aspect 8, wherein the configuration specifies the new PCell, and wherein the method further comprises using the new PCell for the cross-carrier scheduling based at least in part on the configuration.

[0182] Aspect 10: A method of wireless communication performed by a network entity, the method comprising: receiving a recommendation associated with a special secondary cell (sSCell) or a primary cell (PCell) for cross-carrier scheduling; and sending a configuration for the cross-carrier scheduling associated with the recommendation.

[0183] Aspect 11: The method according to aspect 10, further comprising generating the configuration based at least in part on the recommendation.

[0184] Aspect 12: The method according to aspect 11, wherein generating the configuration comprises generating the configuration further based on a channel state or a traffic state of the sSCell or the PCell.

[0185] Aspect 13: The method according to Aspect 10, wherein the recommendation is to deactivate the sSCell.

[0186] Aspect 14: The method according to Aspect 13, wherein the configuration specifies deactivation of the sSCell.

[0187] Aspect 15: The method according to aspect 10, wherein the recommendation indicates a new sSCell for cross-carrier scheduling with the PCell.

[0188] Aspect 16: The method according to aspect 15, wherein the configuration specifies activation of the new sSCell.

[0189] Aspect 17: The method according to aspect 10, wherein the recommendation indicates a new PCell to replace or supplement the PCell.

[0190] Aspect 18: The method according to aspect 17, wherein the configuration specifies that the new PCell is to replace or supplement the PCell.

[0191] Aspect 19: A method of wireless communication performed by a user equipment (UE), the method comprising: sending a recommendation for a value indicating how a control channel element (CCE) is distributed across a special secondary cell (sSCell) and a primary cell (PCell) for cross-carrier scheduling; and receiving a configuration for cross-carrier scheduling associated with the recommendation.

[0192] Aspect 20: The method according to aspect 19, wherein the value indicates that more CCEs are used for the sSCell than for the PCell.

[0193] Aspect 21: The method according to aspect 19, wherein the value indicates that the amount of CCEs used for the PCell and the amount of CCEs used for the sSCell are equal or that the amount of CCEs used for the PCell is more than that of CCEs used for the sSCell.

[0194] Aspect 22: The method according to any one of aspects 19 to 21, wherein the value is based at least in part on one or more of: sSCell channel state or PCell channel state.

[0195] Aspect 23: The method according to aspects 19 to 22, wherein the value is based at least in part on one or more of the following: a block error rate (BLER) of the sSCell satisfies a BLER threshold or a BLER of the PCell satisfies the BLER threshold.

[0196] Aspect 24: The method according to aspects 19 to 23, wherein the value is based at least in part on one or more of the following: sSCell traffic state or PCell traffic state.

[0197] Aspect 25: A method of wireless communication performed by a network entity, the method comprising: receiving a recommendation for a value indicating how a control channel element (CCE) is distributed across a special secondary cell (sSCell) and a primary cell (PCell) for cross-carrier scheduling; and sending a configuration for cross-carrier scheduling associated with the recommendation.

[0198] Aspect 26: The method according to aspect 25, wherein the value indicates that more CCEs are used for the sSCell than for the PCell, and wherein the configuration includes the value.

[0199] Aspect 27: The method according to aspect 25, wherein the value indicates that the amount of CCEs used for the PCell and the amount of CCEs used for the sSCell are equal or the amount of CCEs used for the PCell is more than the amount of CCEs used for the sSCell, and wherein the configuration includes the value.

[0200] Aspect 28: The method according to any one of Aspects 25 to 27, wherein the configuration is based at least in part on the value and one or more of: an sSCell channel state or a PCell channel state.

[0201] Aspect 29: A method according to any one of Aspects 25 to 28, wherein the configuration is based at least in part on the value and one or more of the following: a block error rate (BLER) of the sSCell satisfies a BLER threshold or the BLER of the PCell satisfies the BLER threshold.

[0202] Aspect 30: A method according to any one of aspects 25 to 29, wherein the configuration is based at least in part on the value and one or more of: sSCell traffic state or PCell traffic state.

[0203] Aspect 31: 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 30.

[0204] Aspect 32: 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 30.

[0205] Aspect 33: An apparatus for wireless communication, the apparatus comprising: at least one means for performing the method according to one or more of aspects 1 to 30.

[0206] Aspect 34: 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 30.

[0207] Aspect 35: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising: one or more instructions, which, 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 30.

[0208] 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.

[0209] As used herein, the term "component" is intended to be broadly interpreted as hardware, and / or a combination of 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, execution threads, procedures and / or functions, etc. As used herein, "processor" is implemented by a combination of hardware and / or hardware and software. It will be apparent that the system and / or method 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, the operation and behavior of the system and / or method are not described herein with reference to specific software codes, because it will be understood by those skilled in the art that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0210] 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.

[0211] 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 listed 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 (which 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).

[0212] Any element, action or instruction used herein should not be interpreted as key or necessary, unless clearly stated. 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 you 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" etc. are intended to be open terms, which do not limit the elements they modify (for example, "elements with" A can also have B). In addition, the phrase "based on" is intended to represent "at least partially based on", unless explicitly stated otherwise. In addition, as used herein, the term "or" is intended to be open when used in a series, and can be used interchangeably with "and / or", unless otherwise explicitly stated (for example, if used in combination with "any" or "only one").

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory and configured to: sending a recommendation associated with a special secondary cell (sSCell) or a primary cell (PCell) for cross-carrier scheduling based at least in part on a special secondary cell (sSCell) failure; and A configuration for the cross-carrier scheduling associated with the recommendation is received.

2. The UE of claim 1, wherein as part of the cross-carrier scheduling, the sSCell and the PCell are used to send control channel elements (CCEs).

3. The UE according to claim 1, wherein the recommendation is to deactivate the sSCell.

4. The UE of claim 3, wherein the configuration specifies deactivation of the sSCell, and wherein the one or more processors are configured to stop use of the sSCell based at least in part on the configuration.

5. The UE according to claim 1, wherein the recommendation indicates a new sSCell for cross-carrier scheduling with the PCell.

6. The UE of claim 5, wherein the configuration specifies activation of the new sSCell, and wherein the one or more processors are configured to use the new sSCell based at least in part on the configuration.

7. The UE of claim 5, wherein the configuration specifies activation of the new sSCell, and wherein the one or more processors are configured to switch from the sSCell to the new sSCell based at least in part on the configuration.

8. The UE of claim 1, wherein the recommendation indicates a new PCell to replace or supplement the PCell based at least in part on the sSCell having a higher throughput or a higher reliability than the PCell.

9. The UE of claim 8, wherein the configuration specifies the new PCell, and wherein the one or more processors are configured to use the new PCell for the cross-carrier scheduling based at least in part on the configuration.

10. A network entity for wireless communication, the network entity comprising: Memory; and one or more processors coupled to the memory and configured to: receiving a recommendation associated with a special secondary cell (sSCell) or a primary cell (PCell) for cross-carrier scheduling; and A configuration for the cross-carrier scheduling associated with the recommendation is sent.

11. The network entity of claim 10, wherein the one or more processors are configured to generate the configuration based at least in part on the recommendation.

12. The network entity according to claim 11, wherein to generate the configuration, the one or more processors are configured to generate the configuration further based on a channel state or a traffic state of the sSCell or the PCell. The network entity of claim 10 , wherein the recommendation is to deactivate the sSCell.

14. The network entity of claim 13, wherein the configuration specifies deactivation of the sSCell.

15. The network entity of claim 10, wherein the recommendation indicates a new sSCell for cross-carrier scheduling with the PCell.

16. The network entity of claim 15, wherein the configuration specifies activation of the new sSCell.

17. The network entity of claim 10, wherein the recommendation indicates a new PCell to replace or supplement the PCell.

18. The network entity of claim 17, wherein the configuration specifies that the new PCell is to replace or supplement the PCell.

19. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory and configured to: sending a recommendation for a value indicating how control channel elements (CCEs) are distributed across a special secondary cell (sSCell) and a primary cell (PCell) for cross-carrier scheduling; and A configuration for cross-carrier scheduling associated with the recommendation is received.

20. The UE of claim 19, wherein the value indicates that more CCEs are used for the sSCell than for the PCell.

21. The UE according to claim 19, wherein the value indicates that the amount of CCEs used for the PCell and the amount of CCEs used for the sSCell are equal or that the amount of CCEs used for the PCell is more than that of CCEs used for the sSCell.

22. The UE of claim 19, wherein the value is based at least in part on one or more of: sSCell channel state or PCell channel state.

23. The UE of claim 19, wherein the value is based at least in part on one or more of: a block error rate (BLER) of the sSCell satisfies a BLER threshold or a BLER of the PCell satisfies the BLER threshold.

24. The UE of claim 19, wherein the value is based at least in part on one or more of: sSCell traffic state or PCell traffic state.

25. A network entity for wireless communication, the network entity comprising: Memory; and one or more processors coupled to the memory and configured to: receiving a recommendation for a value indicating how control channel elements (CCEs) are distributed across a special secondary cell (sSCell) and a primary cell (PCell) for cross-carrier scheduling; and A configuration for cross-carrier scheduling associated with the recommendation is sent.

26. The network entity of claim 25, wherein the value indicates that more CCEs are used for the sSCell than for the PCell, and wherein the configuration includes the value.

27. The network entity of claim 25, wherein the value indicates that the amount of CCEs used for the PCell and the amount of CCEs used for the sSCell are equal or that the amount of CCEs used for the PCell is more than that for the sSCell, and wherein the configuration includes the value.

28. The network entity of claim 25, wherein the configuration is based at least in part on the value and one or more of: an sSCell channel state or a PCell channel state.

29. The network entity of claim 25, wherein the configuration is based at least in part on the value and one or more of: a block error rate (BLER) of the sSCell satisfies a BLER threshold or a BLER of the PCell satisfies the BLER threshold.

30. The network entity of claim 25, wherein the configuration is based at least in part on the value and one or more of: an sSCell traffic state or a PCell traffic state.

Images