Fragmented scell addition and activation
Fragmented SCell addition and activation in wireless networks enable non-contiguous frequency spectrums for carrier aggregation, addressing limitations of current techniques and enhancing network flexibility and efficiency.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-09-17
- Publication Date
- 2026-04-02
AI Technical Summary
Current techniques for adding and activating secondary cells (SCells) in wireless communication networks are limited to contiguous frequency domain component carriers, restricting carrier aggregation capabilities.
Implement fragmented SCell addition and activation, allowing for non-contiguous frequency spectrums through anchor and non-anchor spectrums, enabling carrier aggregation with PCell communication for measurement and selection of suitable SCells.
Enhances carrier aggregation by supporting non-contiguous frequency spectrums, improving network flexibility and efficiency in wireless communication networks.
Smart Images

Figure US2025046739_02042026_PF_FP_ABST
Abstract
Description
Attorney Docket No. 106842241740 (P69028WO1)FRAGMENTED SCELL ADDITION AND ACTIVATIONCROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 700,593, filed September 27, 2024, the content of which is herein incorporated by reference in its entirety for all purposes.FIELD
[0002] This disclosure relates to wireless communication networks and mobile device capabilities.BACKGROUND
[0003] Wireless communication networks and wireless communication services are becoming increasingly dynamic, complex, and ubiquitous. For example, some wireless communication networks can be developed to implement fifth generation (5G) or new radio (NR) technology, sixth generation (6G) technology, and so on. Such technology can include solutions for enabling user equipment (UE) and network devices, such as base stations and satellites, to communicate with one another.BRIEF DESCRIPTION OF THE DRAWINGS
[0004] The present disclosure will be readily understood and enabled by the detailed description and accompanying figures of the drawings. Like reference numerals can designate like features and structural elements. Figures and corresponding descriptions are provided as non-limiting examples of aspects, implementations, etc., of the present disclosure, and references to "an" or “one” aspect, implementation, etc., may not necessarily refer to the same aspect, implementation, etc., and can mean at least one, one or more, etc.
[0005] Fig. l is a diagram of an example overview of one or more of the techniques described herein.
[0006] Fig. 2 is a diagram of an example network according to one or more implementations described herein.
[0007] Fig. 3 is a diagram of an example of a master cell group (MCG) and a secondary cell group (SCG) according to one or more implementations described herein.
[0008] Fig. 4 is a diagram of an example of a fragmented secondary cell (SCell) and nonfragmented SCells according to one or more implementations described herein.
[0009] Fig. 5 is a diagram of an example of a process for fragmented SCell addition and14898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) activation according to one or more implementations described herein.
[0010] Figs. 6-7 are diagrams of examples of fragmented SCells according to one or more implementations described herein.
[0011] Fig. 8 is a diagram of an example of a process for fragmented SCell addition and activation based on cell quality according to one or more implementations described herein.
[0012] Fig. 9 is a diagram of an example of components of a device according to one or more implementations described herein.
[0013] Fig. 10 is a diagram of example interfaces of baseband circuitry according to one or more implementations described herein.
[0014] Fig. 11 is a block diagram illustrating components, according to one or more implementations described herein, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
[0015] Fig. 12 is a diagram of an example process for fragmented SCell addition and activation according to one or more implementations described herein.
[0016] Fig. 13 is a diagram of an example process for fragmented SCell addition and activation according to one or more implementations described herein.DETAILED DESCRIPTION
[0017] The following detailed description refers to the accompanying drawings. Like reference numbers in different drawings can identify the same or similar features, elements, operations, etc. Additionally, the present disclosure is not limited to the following description as other implementations can be utilized, and structural or logical changes made, without departing from the scope of the present disclosure.
[0018] Wireless communication networks can include user equipment (UE) capable of communicating with base stations and / or other network access devices. The base stations can provide a UE with access to a core network (CN) and additional external networks, such as the Internet. Wireless communication networks can implement various techniques and standards that enable wireless communications. An example of these techniques can include allocating time and frequency resources to enable UEs and base stations to communicate with one another.
[0019] A UE can connected to one or more base stations. The base stations can include a primary cell (PCell) and one or more secondary cells (SCells) that can enable carrier aggregation (CA) to be implemented between the UE and the base stations. The aggregated24898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) carriers can include a primary component carrier (PCC) from the PCell and one or more secondary component carriers (SCC) from one or more SCells. The aggregated carriers can include different characteristics, such as different frequency bands, numerologies, slot lengths, and more. The PCell can communicate with the UE to cause a component carrier of an SCell to be added and activated for the UE for carrier aggregation purposes. However, currently available techniques for adding and activating an SCell (or an SCC of an SCell) can be limited to component carriers that are contiguous in a frequency domain.
[0020] One or more of the techniques, described herein, can address these and other deficiencies by providing solutions for fragmented SCell addition and activation. A fragmented SCell, as described herein, can include an SCell with fragmented or noncontiguous frequency spectrums that can be used for carrier aggregation. The fragmented SCell can include an anchor spectrum and one or more non-anchor spectrums. A PCell can communicate with a UE to add and activate a fragmented SCell for a carrier aggregation procedure performed by the UE. This can include the PCell enabling the UE to provide measurement reports of the spectrums of fragmented SCells, determining which fragmented SCells are well-suited for carrier aggregation, and enabling the UE to aggregate carriers from the frequency spectrums of a fragmented SCell.
[0021] A frequency spectrum, as referred to herein, can include a frequency band, bandwidth, or another type of frequency domain resource designated, at least in part, for allocation and use in uplink (UL) or downlink (DL) communications. A frequency spectrum can be associated with a measurement occasion and can include a candidate component carrier for carrier aggregation purposes. Fragmented frequency spectrums, as referred to herein, can include frequency spectrums that are non-contiguous within a frequency band for purposes of intra-band non-contiguous carrier aggregation, or across different frequency bands for purposes of inter-band carrier aggregation. Fragmented frequency spectrums can be intra-band or inter-band frequency resources. An SCell can have contiguous frequency spectrums, fragmented frequency spectrums, or a combination thereof.
[0022] Fig. 1 is a diagram of an example overview 100 of one or more of the implementations described herein. As shown, overview 100 can include UE 110, PCell 120, one or more SCells 130, and fragmented spectrums 140. PCell 120 can communicate with UE 110 to enable UE 210 to evaluate SCell 130 for carrier aggregation purposes (at 1.1).
[0023] UE 110 can evaluate SCell 130 based on measurements of fragmented spectrums 140 of SCell 130. Fragmented spectrums 140 can each be associated with a measurement occasion and can include an anchor spectrum and one or more non-anchor spectrums. In34898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) some implementations, UE 110 can evaluate SCell 130 based on the anchor spectrum, while in other implementations, UE 110 can evaluate SCell 130 based on a combination of fragmented spectrums 140.
[0024] UE 110 can communicate a report to PCell 120 that indicates the measurements or a level of quality of SCell 130. Based on the report, PCell 120 can select SCell 130 for carrier aggregation purposes (at 1.2), and can communicate an indication to UE 110 that SCell 130 has been selected for addition and activation (at 1.3). Additional examples of these and many other techniques, features, and implementations are described below with reference to the figures that follow.
[0025] Fig. 2 is an example network 200 according to one or more implementations described herein. Example network 200 can include UEs 210-1, 210-2, etc. (referred to collectively as “UEs 210” and individually as “UE 210”), a radio access network (RAN) 220, a core network (CN) 230, application servers 240, external networks 250. The systems and devices of example network 200 can operate in accordance with one or more communication standards, such as 2nd generation (2G), 3rd generation (3G), 4th generation (4G) (e.g., longterm evolution (LEE)), and / or 5th generation (5G) (e.g., new radio (NR)) communication standards of the 3rd generation partnership project (3GPP). Additionally, or alternatively, one or more of the systems and devices of example network 200 can operate in accordance with other communication standards and protocols discussed herein, including future versions or generations of 3GPP standards (e.g., sixth generation (6G) standards, seventh generation (7G) standards, etc.), institute of electrical and electronics engineers (IEEE) standards, and more.
[0026] As shown, UEs 210 can include smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more wireless communication networks).Additionally, or alternatively, UEs 210 can include other types of mobile or non-mobile computing devices capable of wireless communications, such as personal data assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, etc. In some implementations, UEs 210 can include internet of things (loT) devices (or loT UEs) that can comprise a network access layer designed for low-power loT applications utilizing shortlived UE connections. Additionally, or alternatively, an loT UE can utilize one or more types of technologies, such as machine-to-machine (M2M) communications or machine-type communications (MTC) (e.g., to exchanging data with an MTC server or other device via a public land mobile network (PLMN)), proximity-based service (ProSe) or device-to-device (D2D) communications, sensor networks, loT networks, and more. Depending on the scenario, an M2M or MTC exchange of data can be a machine-initiated exchange, and an loT44898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) network can include interconnecting loT UEs (which can include uniquely identifiable embedded computing devices within an Internet infrastructure) with short-lived connections. In some scenarios, loT UEs can execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the loT network.
[0027] UEs 210 can communicate and establish a connection with one or more other UEs 210 via one or more wireless channels 212, each of which can comprise a physical communications interface / layer. The connection can include an M2M connection, MTC connection, D2D connection, SL connection, etc. The connection can involve a PC5 interface. In some implementations, UEs 210 can be configured to discover one another, negotiate wireless resources between one another, and establish connections between one another, without intervention or communications involving RAN node 222 or another type of network node. In some implementations, discovery, authentication, resource negotiation, registration, etc., can involve communications with RAN node 222 or another type of network node.
[0028] UEs 210 can use one or more wireless channels 212 to communicate with one another. As described herein, UE 210 can communicate with RAN node 222 to request SL resources. RAN node 222 can respond to the request by providing UE 210 with a dynamic grant (DG) or configured grant (CG) regarding SL resources. A DG can include a grant based on a grant request from UE 210. A CG can involve a resource grant without a grant request and can be based on a type of service being provided (e.g., services that have strict timing or latency requirements). UE 210 can perform a clear channel assessment (CCA) procedure based on the DG or CG, select SL resources based on the CCA procedure and the DG or CG; and communicate with another UE 210 based on the SL resources. The UE 210 can communicate with RAN node 222 using a licensed frequency band and communicate with the other UE 210 using an unlicensed frequency band.
[0029] UEs 210 can communicate and establish a connection with RAN 220, which can involve one or more wireless channels 214-1 and 214-2, each of which can comprise a physical communications interface / layer. In some implementations, a UE can be configured with dual connectivity (DC) as a multi-radio access technology (multi-RAT) or multi-radio dual connectivity (MR-DC), where a multiple receive and transmit (Rx / Tx) capable UE can use resources provided by different network nodes (e.g., 222-1 and 222-2) that can be connected via non-ideal backhaul (e.g., where one network node provides NR access and the other network node provides either E-UTRA for LTE or NR access for 5G). A network node can be referred to herein as a base station 222. In such a scenario, one network node can54898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) operate as a master node (MN) and the other as the secondary node (SN). The MN and SN can be connected via a network interface, and at least the MN can be connected to the CN 230. Additionally, at least one of the MN or the SN can be operated with shared spectrum channel access, and functions specified for UE 210 can be used for an integrated access and backhaul mobile termination (IAB-MT). Similar for UE 210, the IAB-MT can access the network using either one network node or using two different nodes with enhanced dual connectivity (EN-DC) architectures, new radio dual connectivity (NR-DC) architectures, or the like. In some implementations, a base station (as described herein) can be an example of network node 222. In some scenarios, RAN 220 can coordinate with core network 230 via interfaces 224, 226, and / or 228.
[0030] In some scenarios, UE 210 can perform one or more operations enable collaborative estimation of UE locations. The operation(s) can include determining that UE 210 is moving with other UEs 210 and forming a group with the other UEs 210. Additionally, UEs 210 can determine their locations collaboratively, based on location information and / or location information metadata exchanged between UEs 210.
[0031] As shown, UE 210 can also, or alternatively, connect to access point (AP) 216 via connection interface 218, which can include an air interface enabling UE 210 to communicatively couple with AP 216. AP 216 can comprise a wireless local area network (WLAN), WLAN node, WLAN termination point, etc. The connection interface 218 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, and AP 216 can comprise a wireless fidelity (Wi-Fi®) router or other AP. While not explicitly depicted in Fig. 2, AP 216 can be connected to another network (e.g., the Internet) without connecting to RAN 220 or CN 230. In some scenarios, UE 210, RAN 220, and AP 216 can be configured to utilize LTE-WLAN aggregation (LWA) techniques or LTE WLAN radio level integration with IPsec tunnel (LWIP) techniques. LWA can involve UE 210 in RRC CONNECTED being configured by RAN 220 to utilize radio resources of LTE and WLAN. LWIP can involve UE 210 using WLAN radio resources (e.g., connection interface 218) via IPsec protocol tunneling to authenticate and encrypt packets (e.g., Internet Protocol (IP) packets) communicated via connection interface 218. IPsec tunneling can include encapsulating the entirety of original IP packets and adding a new packet header, thereby protecting the original header of the IP packets.
[0032] RAN 220 can include one or more RAN nodes 222-1 and 222-2 (referred to collectively as RAN nodes 222, and individually as RAN node 222) that enable channels 214-1 and 214-2 to be established between UEs 210 and RAN 220. RAN nodes 222 can64898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) include network access points configured to provide radio baseband functions for data and / or voice connectivity between users and the network based on one or more of the communication technologies described herein (e.g., 2G, 3G, 4G, 5G, WiFi, etc.). As examples therefore, a RAN node can be an E-UTRAN Node B (e.g., an enhanced Node B, eNodeB, eNB, 4G base station, etc.), a next generation base station (e.g., a 5G base station, NR base station, next generation eNBs (gNB), etc.). RAN nodes 222 can include a roadside unit (RSU), a transmission reception point (TRxP or TRP), and one or more other types of ground stations (e.g., terrestrial access points). In some scenarios, RAN node 222 can be a dedicated physical device, such as a macrocell base station, and / or a low power (LP) base station for providing femtocells, picocells or the like having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells. A RAN node can generally be referred to herein as base station 222.
[0033] Some or all of RAN nodes 222, or portions thereof, can be implemented as one or more software entities running on server computers as part of a virtual network, which can be referred to as a centralized RAN (CRAN) and / or a virtual baseband unit pool (vBBUP). In these implementations, the CRAN or vBBUP can implement a RAN function split, such as a packet data convergence protocol (PDCP) split wherein radio resource control (RRC) and PDCP layers can be operated by the CRAN / vBBUP and other Layer 2 (L2) protocol entities can be operated by individual RAN nodes 222; a media access control (MAC) / physical (PHY) layer split wherein RRC, PDCP, radio link control (RLC), and MAC layers can be operated by the CRAN / vBBUP and the PHY layer can be operated by individual RAN nodes 222; or a “lower PHY” split wherein RRC, PDCP, RLC, MAC layers and upper portions of the PHY layer can be operated by the CRAN / vBBUP and lower portions of the PHY layer can be operated by individual RAN nodes 222. This virtualized framework can allow freed- up processor cores of RAN nodes 222 to perform or execute other virtualized applications.
[0034] In some implementations, an individual RAN node 222 can represent individual gNB-distributed units (DUs) connected to a gNB-control unit (CU) via individual Fl or other interfaces. In such implementations, the gNB-DUs can include one or more remote radio heads or radio frequency (RF) front end modules (RFEMs), and the gNB-CU can be operated by a server (not shown) located in RAN 220 or by a server pool (e.g., a group of servers configured to share resources) in a similar manner as the CRAN / vBBUP. Additionally, or alternatively, one or more of RAN nodes 222 can be next generation eNBs (i.e., gNBs) that can provide evolved universal terrestrial radio access (E-UTRA) user plane and control plane74898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) protocol terminations toward UEs 210, and that can be connected to a 5G core network (5GC) 230 via an NG interface.
[0035] Any of the RAN nodes 222 can terminate an air interface protocol and can be the first point of contact for UEs 210. In some implementations, any of the RAN nodes 222 can fulfill various logical functions for the RAN 220 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. UEs 210 can be configured to communicate using orthogonal frequency-division multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 222 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an OFDMA communication technique (e.g., for downlink communications) or a single carrier frequency-division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink (SL) communications), although the scope of such implementations may not be limited in this regard. The OFDM signals can comprise a plurality of orthogonal subcarriers.
[0036] In some implementations, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 222 to UEs 210, and uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid (e.g., a resource grid or time-frequency resource grid) that represents the physical resource for downlink in each slot. Such a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit in a resource grid is denoted as a resource element. Each resource grid comprises resource blocks, which describe the mapping of certain physical channels to resource elements (REs). Each resource block can comprise a collection of resource elements; in the frequency domain, this can represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.
[0037] Further, RAN nodes 222 can be configured to wirelessly communicate with UEs 210, and / or one another, over a licensed medium (also referred to as the “licensed spectrum” and / or the “licensed band”), an unlicensed shared medium (also referred to as the “unlicensed spectrum” and / or the “unlicensed band”), or combination thereof. A licensed spectrum can correspond to channels or frequency bands selected, reserved, regulated, etc., for certain84898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) types of wireless activity (e.g., wireless telecommunication network activity), whereas an unlicensed spectrum can correspond to one or more frequency bands that are not restricted for certain types of wireless activity. Whether a particular frequency band corresponds to a licensed medium or an unlicensed medium can depend on one or more factors, such as frequency allocations determined by a public-sector organization (e.g., a government agency, regulatory body, etc.) or frequency allocations determined by a private-sector organization involved in developing wireless communication standards and protocols, etc.
[0038] The PDSCH can carry user data and higher layer signaling to UEs 210. The physical downlink control channel (PDCCH) can carry information about the transport format and resource allocations related to the PDSCH channel, among other things. The PDCCH can also inform UEs 210 about the transport format, resource allocation, and hybrid automatic repeat request (HARQ) information related to the uplink shared channel. Typically, downlink scheduling (e.g., assigning control and shared channel resource blocks to UE 210 within a cell) can be performed at any of the RAN nodes 222 based on channel quality information fed back from any of UEs 210. The downlink resource assignment information can be sent on the PDCCH used for (e.g., assigned to) each of UEs 210.
[0039] One or more of the techniques described herein can include solutions for fragmented SCell addition and activation. A fragmented SCell can include an SCell with fragmented or non-contiguous frequency spectrums that can be used for carrier aggregation. A PCell can communicate with UE 210 to add and activate a fragmented SCell for a carrier aggregation procedure involving UE 210. This can include the PCell enabling UE 210 to provide measurement reports of the spectrums of fragmented SCells, determining which fragmented SCells are well-suited for carrier aggregation, and enabling UE 210 to aggregate carriers from the frequency spectrums of a fragmented SCell. Many other aspects and examples are also described herein.
[0040] The RAN nodes 222 can be configured to communicate with one another via interface 223. In implementations where the system is an LTE system, interface 223 can be an X2 interface. In NR systems, interface 223 can be an Xn interface. The X2 interface can be defined between two or more RAN nodes 222 (e.g., two or more eNBs / gNBs or a combination thereof) that connect to evolved packet core (EPC) or CN 230, or between two eNBs connecting to an EPC. In some implementations, the X2 interface can include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U can provide flow control mechanisms for user data packets transferred over the X2 interface and can be used to communicate information about the delivery of user data between eNBs or gNBs. For94898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) example, the X2-U can provide specific sequence number information for user data transferred from a master eNB (MeNB) to a secondary eNB (SeNB); information about successful in sequence delivery of PDCP packet data units (PDUs) to a UE 210 from an SeNB for user data; information of PDCP PDUs that were not delivered to a UE 210; information about a current minimum desired buffer size at the SeNB for transmitting to the UE user data; and the like. The X2-C can provide intra-LTE access mobility functionality (e.g., including context transfers from source to target eNBs, user plane transport control, etc.), load management functionality, and inter-cell interference coordination functionality.
[0041] As shown, RAN 220 can be connected (e.g., communicatively coupled) to CN 230. CN 230 can comprise a plurality of network elements 232, which are configured to offer various data and telecommunications services to customers / subscribers (e.g., users of UEs 210) who are connected to the CN 230 via the RAN 220. In some implementations, CN 230 can include an evolved packet core (EPC), a 5G CN (5GC), and / or one or more additional or alternative types of CNs. The components of the CN 230 can be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some implementations, network function virtualization (NFV) can be utilized to virtualize any or all the above-described network node roles or functions via executable instructions stored in one or more computer-readable storage mediums (described in further detail below).
[0042] A logical instantiation of the CN 230 can be referred to as a network slice, and a logical instantiation of a portion of the CN 230 can be referred to as a network sub-slice. Network function virtualization (NFV) architectures and infrastructures can be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches. In other words, NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC components / functions.
[0043] As shown, CN 230, application servers 240, and external networks 250 can be connected to one another via interfaces 234, 236, and 238, which can include IP network interfaces. Application servers 240 can include one or more server devices or network elements (e.g., virtual network functions (VNFs) offering applications that use IP bearer resources with CN 230 (e.g., universal mobile telecommunications system packet services (UMTS PS) domain, LTE PS data services, etc.). Application servers 240 can also, or alternatively, be configured to support one or more communication services (e.g., voice over104898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1)IP (VoIP sessions, push-to-talk (PTT) sessions, group communication sessions, social networking services, etc.) for UEs 210 via the CN 230. Similarly, external networks 250 can include one or more of a variety of networks, including the Internet, thereby providing the mobile communication network and UEs 210 of the network access to a variety of additional services, information, interconnectivity, and other network features.
[0044] Fig. 3 is a diagram of an example 300 of a master cell group (MCG) 310 and a secondary cell group (SCG) 320 according to one or more implementations described herein. An MCG can include a group of cells associated with a master node, comprising a PCell and one or more SCells. An SCG can include a group of serving cells associated with a secondary node, comprising a primary cell of the secondary cell group (PSCell) and optionally one or more SCells. MCG 310 and SCG 320 can each be implemented by one or more base station 222 and / or another type of RAN node or access point.
[0045] MCG 310 can be implemented by one or more base stations and can include one or more layers. Examples of such layers can include a PDCP layer, an RLC layer, a MAC layer, and multiple PHY layers. Each PHY layer can correspond to a different implementation of a cell with respect to UE 210. Additionally, or alternatively, the PHY layers can operate in combination (e.g., be managed, controlled by, etc.) the PDCP, RLC, and MAC layers. In some implementations, one PHY layer 340 can operate as a PCell or a special cell (SpCell) and other PHY layers 342 and 344 can operate as SCells to the PCell.
[0046] SCG 320 can include multiple layers as well, including an RLC layer, a MAC layer, and multiple PHY layers 350, 352, and 354. SCG 320 may not include a PDCP layer, but instead can rely on the PDCP layer of MCG 310 via connection 330. Similar to the PHY layers of MCG 310, the PHY layers of SCG 320 can each function or operate as a cell with respect to UE 210. In some implementations, one PHY layer 350 can operate as a primary cell (PCell) to PHY layers 352 and 354, which can operate as secondary cells to the PCell of PHY layer 350. Additionally, MCG 310 and SCG 320 can each include a PCell (e.g., 340 and 350), and a PCell can be referred to herein as a special cell or special primary cell, represented as SpCell. Further, a SCell, of either MCG 310 or SCG 320, can operate as a scheduling secondary cell (sSCell) configured to provide configuration, scheduling, activation, deactivation, and other functions or commands toward a SpCell of either MCG 310 or SCG 320.
[0047] MCG 310 and SCG 320 can be involved in a dual connectivity scenario with UE 210, in which case a random access channel (RACH) procedure, and the like, can be directed to MCG 310. MCG 310 and SCG 320 can also implement a standalone (SA) and / or a nonl l4898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) standalone (NSA) network environment for UE 210. In a SA network environment, MCG 310 and SCG 320 can communicate with UE 210 using 5G NR communication standards. In an NSA network environment, MCG 310 and SCG 320 can communicate with UE 210 using a combination of 4G LTE, 5GNR, and 6G communication standards. Carrier aggregation can include a scenario in which UE 210 aggregates component carriers from a PCell under MCG 310 and an SCell under MCG 310. Dual connectivity can include a scenario in which UE 210 connects to cells under MCG 310 and SCG 320.
[0048] Fig. 4 is a diagram of an example 400 of a fragmented SCell and non-fragmented SCells according to one or more implementations described herein. As shown, fragmented SCell 410 and non-fragmented SCells 420 and 430 can each include bandwidths designated, at least in part, for allocation and use in UL and / or DL communications. Fragmented SCell 410 and non-fragmented SCells 420 and 430 can each include a different number, arrangement, allocation and sizes of bandwidths. The bandwidths of fragmented SCell 410 can include inter-band, non-contiguous, or fragmented frequency spectrums. By contrast, the bandwidths of non-fragmented SCells 420 and 430 can include intra-band, contiguous, or non-fragmented frequency spectrums.
[0049] Techniques, described herein, can include solutions for adding and activating fragmented SCells to a carrier aggregation procedure involving inter-band or fragmented frequency bands or spectrums. Such carrier aggregation procedures, and / or the aggregated carriers corresponding thereto, can involve the aggregation of component carriers from both fragmented and non-fragmented SCells. A frequency spectrum, as referred to herein, can include a frequency band, bandwidth, or another type of frequency domain resource designated, at least in part, for allocation and use in UL and / or DL communications. A frequency spectrum can be associated with a measurement occasion and can include a candidate component carrier for carrier aggregation purposes. Fragmented frequency spectrums, as referred to herein, can include frequency spectrums that are non-contiguous within a bandwidth or frequency band for purposes of intra-band contiguous carrier aggregation. Fragmented frequency spectrums can be intra-band frequency resources. An SCell can have contiguous frequency spectrums, fragmented frequency spectrums, or a combination thereof.
[0050] Fig. 5 is a diagram of an example of a process 500 for fragmented SCell addition and activation according to one or more implementations described herein. As shown, process 500 can be implemented by UE 210 and one or more base stations 222. A PCell and one or more SCells can be implemented by one base station 222 or multiple base station 222.124898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1)For example, a single base station 222 can operate as both a PCell and one or more SCells relative to UE 210. In some examples, one base station 222 can operate as a PCell and one or more other base stations can operate as SCells relative to UE 210.
[0051] The SCells can include at least one fragmented SCell, and one or more additional fragmented SCells, non-fragmented SCells, or a combination thereof. In some implementations, some or all of process 500 can be performed by one or more other systems or devices, including one or more of the devices of Fig. 2. Additionally, process 500 can include one or more fewer, additional, differently ordered and / or arranged operations than those shown in Fig. 5. In some implementations, some or all of the operations of process 500 can be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 500. As such, the techniques described herein are not limited to the number, sequence, arrangement, timing, etc., of the operations or processes depicted in Fig. 5. Fig. 5 is described below with reference to Figs. 6 and 7.
[0052] As shown, process 500 can include UE 210 providing a PCell with UE capability information (block 505). The UE capability information can include an indication of whether UE 210 supports fragmented SCell addition and activation. The indication can be of whether UE 210 supports a two-step SCell management approach to fragmented SCell addition and activation as described with reference to Fig. 5. Additionally, or alternatively, the indication can be of whether UE 210 supports a fragmented SCell addition and activation approach based on SCell quality as described with reference to Fig. 8. The UE capability information can be defined per UE 210 and / or per frequency range (FR) (e.g., FR1 and FR2). For example, different UEs 210 can have different UE capability information, the UE capability information of a UE 210 can depend on a condition, scenario, or context, and the UE capability information of UE 210 can be different for FR1 and FR2.
[0053] Process 500 can include a PCell communicating SCell configuration information to UE 210 (block 510). The SCell configuration information can be for one SCell or multiple SCells. The SCell configuration information can include an indication of whether the SCell is a fragmented SCell or a non-fragmented SCell. The SCell configuration information can include spectrum information associated with an SCell. Examples of spectrum information can include a number, arrangement, and configuration of spectrums in the SCell, a spectrum type associated with each spectrum (e.g., anchor spectrum or non-anchor spectrum), synchronization information associated with each spectrum, and / or timing or measurement information associated with each spectrum. The synchronization information can be a system synchronization block (SSB) and the timing or measurement information can include, or134898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) enable UE 210 to determine, measurement occasions for each spectrum. In some implementations, the SCell configuration information can include information pertaining to the anchor spectrum pf a fragmented SCell. In some implementations, the SCell configuration information can include information pertaining to the anchor spectrum and one or more nonanchor spectrums of the SCell.
[0054] Figs. 6-7 are diagrams of examples 600 and 700 of fragmented SCells according to one or more implementations described herein. Referring to Fig. 6, a fragmented SCell can include fragmented or disconnected spectrums. The fragmented SCell can include anchor spectrum 610 and one or more non-anchor spectrums 620, 630, 640, . . . 650. Non-anchor spectrums 620, 630, 640, . . . 650 can be referred to collectively as spectrums 620-650, while anchor spectrum 610 and non-anchor spectrums 620-650 can be referred to collectively as spectrums 610-650. The fragmented SCell of example 600 can include an anchor spectrum 610 and non-anchor spectrums 620-650. The spectrums 610-650 can be configured to have the same or a similar amount of bandwidth or frequency domain resources. Additionally, or alternatively, a distance along a frequency domain between spectrums 610-650 can vary such that spectrums 610-650 are non-contiguous relative to one another.
[0055] Similar to example 600, example 700 of Fig. 7 can include fragmented spectrums 710, 720, 730, 740, . . . 750, which can be referred to collectively as spectrums 710-750. In contrast to example 600, spectrums 710-750 may not include any anchor spectrums or non- anchor spectrums. Spectrum 710-750 can have different bandwidths or frequency domain resources. For example, spectrum 710 includes a bandwidth that is significantly larger than any of spectrums 720, 730, 740, . . . 750. Further, the various bandwidths of spectrums 720- 750 can vary in size. Spectrums 610-650 and 710-750 can each be associated with different system information (e.g., a different SSB) and / or a different measurement information (e.g., a different measurement occasion).
[0056] Referring to Fig. 5, process 500 can include UE 210 measuring one or more anchor spectrums (block 520). UE 210 can use the SCell configuration information to synchronize with an anchor spectrum of a corresponding SCell, determine a measurement occasion for the anchor spectrum, and measure a signal of the anchor spectrum during the measurement occasion. The signal can be a reference signal. Based on the measurements, UE 210 can determine characteristics of the anchor spectrum, such as a signal quality, strength (e.g., reference signal received power (RSRP)), interference (e.g., a signal-to-noise ratio (SNR), signal-to-interference-plus-noise ratio (SINR), etc.), and more. In some implementations, UE 210 can refrain from measuring signals and determining characteristics144898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) of non-anchor spectrums of an SCell until after addition and / or activation of the SCell by the PCell.
[0057] Process 500 can include UE 210 communicating a measurement report to the PCell (block 530). The measurement report can indicate the measurements obtained by UE 210. The measurement report can include one or more characteristics of an anchor spectrum of an SCell, such as a signal quality, RSRP, SNR, SINR, and more. The measurement report can be limited to measurements and characteristics of anchor spectrum, such that measurements and characteristics of non-anchor spectrums are not reported.
[0058] Process 500 can include the PCell selecting one or more SCells for addition and activation (block 540). For example, the PCell can receive the measurement report from UE 210, and based on the measurement report, the PCell can select one or more SCells for addition and activation with respect to UE 210. In some implementations, the PCell can select an SCell based on the SCell being the most suited for addition and activation from among a group of SCells represented in the measurement report. In some implementations, the PCell can select an SCell based on the SCell being adequately suited for addition and activation (e.g., SCells with anchor spectrums that satisfy a quality, performance, or measurement threshold). In some implementations, the PCell can select an SCell based on a comparison of the SCell to other SCells represented by the measurement report. The PCell can select multiple SCells for addition and activation. The number of SCells selected can be limited to a maximum number of SCells, a maximum number of anchor spectrums, and / or a maximum number of non-anchor spectrums. In some implementations, the PCell can select an SCell based on a load balance framework for allocating SCells and / or spectrums to UEs 210.
[0059] Process 500 can include the PCell communicating SCell addition and activation information to UE 210 (block 550). For example, upon selecting an SCell for addition and activation, the PCell can communicate an indication of the SCell to UE 210. The PCell can also communicate an indication to UE 210 for the SCell to be added and / or activated with respect to UE 210. Addition of an SCell can include RRC reconfiguration to add the SCell as a serving cell for UE. Activation of the SCell can include MAC-CE to activate the SCell from deactivated mode to active mode so that it can be used for data communication. In some implementations, the PCell can provide spectrum information of the selected SCell to UE 210. For example, when the previous spectrum information provided by the PCell (e.g., block 510) included anchor spectrum information but not non-anchor spectrum information, the PCell can provide non-anchor spectrum information to UE 210 after the SCell has been selected. The spectrum information can include time and frequency resources, including154898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) measurement information and measurement occasions, for measuring signals of the nonanchor spectrums.
[0060] Process 500 can include UE 210 measuring non-anchor spectrums of the selected SCell (block 560). UE 210 can measure signals, during measurement occasions, of each of the non-anchor spectrums of the selected SCell. In some implementations, the PCell can indicate the spectrum configuration of SCell to UE 210 via an RRC message indicating SCell addition or another type of transmission. UE 210 can measure signals of the non-anchor spectrums indicated. In some implementations, multiple SCell can be selected and UE 210 can measure non-anchor spectrums of the multiple SCells. The non-anchor spectrum configurations of each of the selected SCells can be different. Measurement occasions for non-anchor spectrums can be pre-configured and triggered by UE 210 automatically after the SCell is added and activated. UE 210 can measure one or more non-anchor spectrums in response to a particular event or trigger, such as receiving an RRC message indicating SCell addition.
[0061] Process 500 can include UE 210 can generate a measurement report of the non- anchor spectrums (block 570). The measurement report can be based on the measurements of the non-anchor spectrums. Additionally, or alternatively, UE 210 can determine one or more characteristics of the non-anchor spectrums, such as a signal quality, strength (e.g., reference signal received power (RSRP)), interference (e.g., a signal-to-noise ratio (SNR), signal-to- interference-plus-noise ratio (SINR), etc.), and more. In some implementations, UE 210 can refrain from measuring signals and determining characteristics of non-anchor spectrums of an SCell until after addition and / or activation of the SCell by the PCell. The measurement report can include the measurement and / or one or more of the characteristics determined by UE 210. UE 210 can communicate the measurement report to the PCell.
[0062] Process 500 can include the PCell selecting one or more non-anchor spectrums (block 580). For example, the PCell can receive the measurement report from UE 210. The PCell can select one or more of the non-anchor spectrums (or one or more portions of a non- anchor spectrum) of the selected SCell based on the measurement report. The PCell can do so by determining the non-anchor spectrums that would be best or most suited for UE 210 (e.g., for carrier aggregation purposes). In some implementations, the PCell can selected multiple non-anchor spectrums according to which non-anchor spectrums satisfy a specified measurement threshold, quality threshold, RSRP threshold, etc. In some implementations, determine whether to select a non-anchor spectrum can include comparing a signal measurement and / or characteristic of one non-anchor spectrum to one or more other non-164898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) anchor spectrums to determine whether the non-anchor spectrum is the best, most suitable, or adequate for UE 210.
[0063] Process 500 can include the PCell communicating an indication of the selected non-anchor spectrum for addition and activation (block 590). The PCell can communicate one non-anchor spectrum or multipole non-anchor spectrum based on, for example, how many non-anchor spectrums were selected. In some implementations, the PCell can communicate additional information to enable the addition and / or activation of the non- anchor spectrums for UE 210. In some implementations, addition and activation of a non- anchor spectrum can occur at the same time / message or at different times / messages and / or in response to the same or different triggers, conditions, or schedules. Non-anchor spectrum addition can include RRC reconfiguration to add the non-anchor spectrum as part of the serving cell. Non-anchor spectrum activation can include MAC-CE or DCI to activate the non-anchor spectrum from deactivated mode to active mode so that it can be used for data communication. Non-anchor spectrum activation can be triggered via a MAC communication or DCI procedure.
[0064] In some implementations, the PCell can communicate an indication of a bandwidth part (BWP) of a non-anchor spectrum. For example, the PCell can select a non- anchor spectrum based on the measurement report from UE 210 (see, block 580). The PCell can determine or select a BWP of the non-anchor spectrum based on the measurement report and / or SCell configuration information of the selected SCell. The PCell can communicate an indication of the BWP to UE 210 for addition and activation. In some implementation, the PCell can communicate an indication of the BWP addition and the BWP activation in the same or different communications, which can be in response to the same or different conditions. For example the PCell can communicate an indication of the selected BWP to UE 210 upon selection of the BWP. The PCell can communicate an indication of addition of the BWP in response to a first trigger, a first condition, or a schedule. The PCell can communicate an indication of activation of the BWP in response to a first trigger, a first condition, or a schedule in response to a second trigger, a second condition, or the schedule. Additional BWP activation can be achieved via a DCI communication or procedure.
[0065] Fig. 8 is a diagram of an example of a process 800 for fragmented SCell addition and activation based on cell quality according to one or more implementations described herein. As shown, process 800 can be implemented by UE 210 and one or more base stations 222. A PCell and one or more SCells can be implemented by one base station 222 or multiple base station 222. For example, a single base station 222 can operate as both a PCell and one174898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) or more SCells relative to UE 210. In some examples, one base station 222 can operate as a PCell and one or more other base stations can operate as SCells relative to UE 210. The SCell can include fragmented spectrums. In some implementations, the spectrums can include an anchor spectrum and one or more non-anchor spectrums (see, Fig. 6), while in other implementations the spectrums may not include an anchor spectrum or any non-anchor spectrums (see, Fig. 7).
[0066] The SCells can include at least one fragmented SCell, and one or more additional fragmented SCells, non-fragmented SCells, or a combination thereof. In some implementations, some or all of process 800 can be performed by one or more other systems or devices, including one or more of the devices of Fig. 2. Additionally, process 800 can include one or more fewer, additional, differently ordered and / or arranged operations than those shown in Fig. 8. In some implementations, some or all of the operations of process 800 can be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 800. As such, the techniques described herein are not limited to the number, sequence, arrangement, timing, etc., of the operations or processes depicted in Fig. 8.
[0067] As shown, process 800 can include UE 210 providing base station 222 with UE capability information (block 805). The UE capability information can include an indication of whether UE 210 supports fragmented SCell addition and activation. The indication can be of whether UE 210 supports a two-step SCell management approach to fragmented SCell addition and activation as described above with reference to Fig. 5. In some implementations, the UE capability information can include an indication of whether UE 210 supports SCell quality evaluation and / or an indication of whether UE 210 supports prioritizing measurements of SCell spectrums. The UE capability information can be defined per UE 210 and / or per FR. For example, different UEs 210 can have different UE capability information, the UE capability information of a UE 210 can depend on a condition, scenario, or context, and the UE capability information of UE 210 can be different for FR1 and FR2. As described below, the PCell can provide UE 210 with one or more types of information based on the UE capability information received from UE 210.
[0068] Process 800 can include a PCell communicating SCell configuration information to UE 210 (block 810). The SCell configuration information can be for one SCell or multiple SCells. The SCell configuration information can include an indication of whether the SCell is a fragmented SCell or a non-fragmented SCell. The SCell configuration information can include spectrum information associated with an SCell. Examples of spectrum information184898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) can include a number, arrangement, and configuration of spectrums in the SCell, a spectrum type associated with each spectrum, synchronization information associated with each spectrum, and / or timing or measurement information associated with each spectrum. The synchronization information can be a system synchronization block (SSB) and the timing or measurement information can include, or enable UE 210 to determine, measurement occasions for each spectrum. In some implementations, the SCell configuration information can include information pertaining to the anchor spectrum pf a fragmented SCell. In some implementations, the SCell configuration information can include information pertaining to the anchor spectrum and one or more non-anchor spectrums of the SCell.
[0069] Process 800 can include the PCell communicating SCell quality evaluation information to UE 210 (block 814). In some implementations, the SCell quality evaluation information can include an indication to evaluate SCell quality by evaluating spectrums equally (e.g., using the same evaluation technique for each spectrum). In some implementations, the SCell quality evaluation information can include an indication to evaluate SCell quality by evaluating spectrums differently. In some implementations, the SCell quality evaluation information can include one or more rules, schemes, or techniques for applying different weights to different spectrums of the SCell, an example of which is discussed in detail below. In some implementations, the quality evaluation information can include one or more additional, or alternative, evaluation rules, schemes, or techniques for determining a quality of an SCell.
[0070] Process 800 can include the PCell communicating measurement scheme information to UE 210 (block 816). The measurement scheme information can indicate or include a measurement scheme or technique for measuring spectrums differently. In some implementations, the measurement scheme can include measuring spectrums according to a priority associated with each spectrum of the SCell, an example of which is discussed in detail below. In some implementations, the measurement scheme can include measuring spectrums according to one or more additional or alternative measurement rules, schemes, or techniques.
[0071] Process 800 can include UE 210 determining a quality of one or more SCells (block 820). UE 210 can also, or alternatively, determine a quality evaluation scheme and / or a measurement scheme for determining the quality of an SCell. In some implementations, UE 210 can determine the quality evaluation scheme and / or the measurement scheme based in whole, or in part, on SCell configuration information, SCell quality evaluation information and / or measurement scheme information provided by the PCell. Some or all of this194898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) information can be provided via downlink control information (DCI) and / or RRC messaging. In some implementations, the PCell can configure UE 210 to apply a quality evaluation scheme and / or a measurement scheme to determine the quality of an SCell.
[0072] UE 210 can use the SCell configuration information to synchronize with spectrums of an SCell, determine a measurement occasion for each spectrum, and measure a signal of each spectrum during the measurement occasion. The signal can be a reference signal. Based on the measurements, UE 210 can determine characteristics of the spectrum, such as a signal quality, strength (e.g., reference signal received power (RSRP)), interference (e.g., a signal-to-noise ratio (SNR), signal-to-interference-plus-noise ratio (SINR), etc.), and more. In some implementations, UE 210 can refrain from measuring signals and determining characteristics of non-anchor spectrums of an SCell until after addition and / or activation of the SCell by the PCell.
[0073] UE 210 can measure the spectrums of the SCell according to a measurement scheme. The measurement scheme can include measuring each spectrum equally (e.g., using the same measurement technique for each spectrum). The measurement scheme can be implemented according to a pre-defined communication standard. Additionally, or alternatively, the measurement scheme can include using different measuring techniques for different spectrums. UE 210 can apply a different priority to measuring different spectrums. UE 210 can determine the priority for measuring each spectrum based on cell configuration information, spectrum configuration information, measurement scheme information, and more. In some implementations, spectrums of greater bandwidths can be measured with according to a higher priority than spectrums of smaller bandwidths. Referring to Fig. 7 for example, spectrum 710 can be measured using 50% of the overall measurement occasions allocated to measuring the spectrums of the SCell, while spectrums 720, 730, 740, and 750 can be measured with using the remaining 50% of the overall measurement occasions. Allocating different priorities for measuring different spectrums can help ensure, for example, great measurement accuracy for spectrums of greater value or resources, which can in turn help ensure the quality of the SCell properly ascertained.
[0074] UE 210 can determine the value of the SCell by applying a quality evaluation scheme that includes averaging the measurements of each spectrum. Additionally, or alternatively, UE 210 can determine the value of the SCell by applying different weights (as portion or percent of a whole) and combining the weighted measurements of each spectrum. For example, the SCell can include 5 spectrums of varying bandwidths and frequency domain locations. A measurement of a first spectrum can be weighted at 60%, while the204898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) measurements for the remaining 4 spectrums can each be weighted at 10%. The 5 weighted measurements can be combined into a whole, or 100% measurement value, which can indicate the quality of the SCell. The measurement weights for each spectrum can be configured by the PCell via DCI, RRC messaging, etc., and / or determined by UE 210. For example, UE 210 can determine the measurement weight for each spectrum based on, for example, a total number of spectrums in the SCell, a relative position or overall arrangement of spectrums in the frequency domain, an actual bandwidth or relative bandwidth of spectrums, and / or one or more other characteristic of the spectrums.
[0075] Process 800 can include UE 210 communicating an SCell quality report to the PCell (block 830). The quality report can include information of one SCell or multiple SCells. The quality report can indicate a level of quality or suitability of SCells for addition and activation relative to UE 210. For each SCell and / or spectrum of each SCell, the quality report can also, or alternatively, include the measurements and / or characteristics of the spectrums of the SCell, such as a signal quality, RSRP, SNR, SINR, and more. In some implementations, UE 210 can send the PCell multiple SCell quality reports that can each include information regarding one SCell, a group of SCells, or a number of SCells.
[0076] Process 800 can include the PCell selecting an SCell based on SCell quality (block 840). For example, the PCell can receive the SCell quality report from UE 210, and based on the quality report, the PCell can select one or more SCells for addition and activation with respect to UE 210. In some implementations, the PCell can select an SCell based on the SCell having a highest level of quality and therefore being the most suited for addition and activation. In some implementations, the PCell can select an SCell based on the SCell having a level of quality above a quality threshold. In some implementations, the PCell can select multiple SCells for addition and activation. The number of SCells selected can be limited to a maximum number of SCells, a maximum number of spectrums, and / or a maximum number of non-anchor spectrums. In some implementations, the PCell can select an SCell based on a load balance framework for allocating SCells and / or spectrums to UEs 210.
[0077] Process 800 can include the PCell communicating SCell addition and activation information to UE 210 (block 850). For example, upon selecting an SCell for addition and activation, the PCell can communicate an indication of the selected SCell to UE 210. The PCell can also communicate an indication to UE 210 for the SCell to be added and / or activated with respect to UE 210. Addition of an SCell can include RRC reconfiguration to add the SCell as a serving cell for UE. Activation of the SCell can include MAC-CE to214898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) activate the SCell from deactivated mode to active mode so that it can be used for data communication.
[0078] Fig. 9 is a diagram of an example of components of a device according to one or more implementations described herein. In some implementations, device 900 can include application circuitry 902, baseband circuitry 904, RF circuitry 906, front-end module (FEM) circuitry 908, one or more antennas 910, and power management circuitry (PMC) 912 coupled together at least as shown. In some implementations, device 900 can include fewer elements (e.g., a RAN node may not utilize application circuitry 902 and can instead include a processor / controller to process data received from a core network. In some implementations, device 900 can include additional elements such as, for example, memory / storage, display, camera, sensor (including one or more temperature sensors, such as a single temperature sensor, a plurality of temperature sensors at different locations in device 900, etc.), or input / output (I / O) interface. In other implementations, the components described below can be included in more than one device (e.g., said circuitries can be separately included in more than one device for cloud-RAN (C-RAN) implementations).
[0079] Application circuitry 902 can include one or more application processors. For example, application circuitry 902 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) can include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors can be coupled with or can include memory / storage and can be configured to execute instructions stored in the memory / storage to enable various applications or operating systems to run on device 900. In some implementations, processors of application circuitry 902 can process data packets received from a core network.
[0080] Baseband circuitry 904 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. Baseband circuitry 904 can include one or more baseband processors or control logic to process baseband signals received from a receive signal path of RF circuitry 906 and to generate baseband signals for a transmit signal path of RF circuitry 906. Baseband circuity 904 can interface with application circuitry 902 for generation and processing of the baseband signals and for controlling operations of RF circuitry 906. For example, in some implementations, baseband circuitry 904 can include a 3G baseband processor 904A, a 4G baseband processor 904B, a 5G baseband processor 904C, or other baseband processor(s) 904D for other existing generations, generations in development or to be developed in the future (e.g., 5G, 6G, 7G, etc.). Baseband circuitry 904 (e.g., one or more of baseband processors 904 A-D) can handle various radio control functions224898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) that enable communication with one or more radio networks via RF circuitry 906. In other implementations, some or all of the functionality of baseband processors 904 A-D can be included in modules stored in memory 904G and executed via a central processing unit (CPU) 904E. The radio control functions can include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some implementations, modulation / demodulation circuitry of baseband circuitry 904 can include Fast-Fourier Transform (FFT), precoding, or constellation mapping / de-mapping functionality. In some implementations, encoding / decoding circuitry of baseband circuitry 904 can include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functionality. Implementations of modulation / demodulation and encoder / decoder functionality are not limited to these examples and can include other suitable functionality in other implementations.
[0081] In some implementations, memory 904G can receive and / or store information and instructions for fragmented SCell addition and activation. A fragmented SCell can include an SCell with fragmented or non-contiguous frequency spectrums that can be used for carrier aggregation. A PCell can communicate with UE 210 to add and activate a fragmented SCell for a carrier aggregation procedure involving UE 210. This can include the PCell enabling UE 210 to provide measurement reports of the spectrums of fragmented SCells, determining which fragmented SCells are well-suited for carrier aggregation, and enabling UE 210 to aggregate carriers from the frequency spectrums of a fragmented SCell. Operations described as being performed by, for example, UE 210 can be performed by baseband circuitry 904. Many other aspects and examples are also described herein.
[0082] In some implementations, baseband circuitry 904 can include one or more audio digital signal processor(s) (DSP) 904F. Audio DSP 904F can include elements for compression / decompression and echo cancellation and can include other suitable processing elements in other implementations. Components of baseband circuitry 904 can be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some implementations. In some implementations, some or all of the constituent components of baseband circuitry 904 and application circuitry 902 can be implemented together such as, for example, on a system on a chip (SOC).
[0083] In some implementations, baseband circuitry 904 can provide for communication compatible with one or more radio technologies. For example, in some implementations, baseband circuitry 904 can support communication with a NG-RAN, an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks234898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1)(WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN), etc. Implementations in which baseband circuitry 904 is configured to support radio communications of more than one wireless protocol can be referred to as multi-mode baseband circuitry.
[0084] RF circuitry 906 can enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various implementations, RF circuitry 906 can include switches, filters, amplifiers, etc., to facilitate the communication with the wireless network. RF circuitry 906 can include a receive signal path which can include circuitry to down-convert RF signals received from FEM circuitry 908 and provide baseband signals to baseband circuitry 904. RF circuitry 906 can also include a transmit signal path which can include circuitry to up-convert baseband signals provided by baseband circuitry 904 and provide RF output signals to FEM circuitry 908 for transmission.
[0085] In some implementations, the receive signal path of RF circuitry 906 can include mixer circuitry 906A, amplifier circuitry 906B and filter circuitry 906C. In some implementations, the transmit signal path of RF circuitry 906 can include filter circuitry 906C and mixer circuitry 906 A. RF circuitry 906 can also include synthesizer circuitry 906D for synthesizing a frequency for use by mixer circuitry 906A of the receive signal path and the transmit signal path. In some implementations, mixer circuitry 906A of the receive signal path can be configured to down-convert RF signals received from FEM circuitry 908 based on the synthesized frequency provided by synthesizer circuitry 906D. Amplifier circuitry 906B can be configured to amplify the down-converted signals and filter circuitry 906C can be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals can be provided to baseband circuitry 904 for further processing. In some implementations, the output baseband signals can be zero-frequency baseband signals, although this may not be a requirement. In some implementations, mixer circuitry 906A of the receive signal path can comprise passive mixers, although the scope of the implementations is not limited in this respect.
[0086] In some implementations, mixer circuitry 906A of the transmit signal path can be configured to up-convert input baseband signals based on the synthesized frequency provided by synthesizer circuitry 906D to generate RF output signals for FEM circuitry 908. The baseband signals can be provided by baseband circuitry 904 and can be filtered by filter circuitry 906C. In some implementations, mixer circuitry 906A of the receive signal path and244898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) mixer circuitry 906A of the transmit signal path can include two or more mixers and can be arranged for quadrature down conversion and up conversion, respectively. In some implementations, mixer circuitry 906A of the receive signal path and mixer circuitry 906A of the transmit signal path can include two or more mixers and can be arranged for image rejection. In some implementations, mixer circuitry 906 A of the receive signal path and mixer circuitry 906A can be arranged for direct down conversion and direct up conversion, respectively. In some implementations, mixer circuitry 906 of the receive signal path and mixer circuitry 906A of the transmit signal path can be configured for super-heterodyne operation.
[0087] In some implementations, the output baseband signals, and the input baseband signals can be analog baseband signals, although the scope of the implementations is not limited in this respect. In some alternate implementations, the output baseband signals, and the input baseband signals can be digital baseband signals. In these alternate implementations, RF circuitry 906 can include analog-to-digital converter (ADC) and digital- to-analog converter (DAC) circuitry and baseband circuitry 904 can include a digital baseband interface to communicate with RF circuitry 906.
[0088] In some dual-mode implementations, a separate radio integrated circuitry can be provided for processing signals for each spectrum, although the scope of the implementations is not limited in this respect. In some implementations, synthesizer circuitry 906D can be a fractional -N synthesizer or a fractional N / N+l synthesizer, although the scope of the implementations is not limited in this respect as other types of frequency synthesizers can be suitable. For example, synthesizer circuitry 906D can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
[0089] Synthesizer circuitry 906D can be configured to synthesize an output frequency for use by mixer circuitry 906 A of RF circuitry 906 based on a frequency input and a divider control input. In some implementations, synthesizer circuitry 906D can be a fractional N / N+l synthesizer. In some implementations, frequency input can be provided by a voltage- controlled oscillator (VCO). Divider control input can be provided by either baseband circuitry 904 or the applications circuitry 902 depending on the desired output frequency. In some implementations, a divider control input (e.g., N) can be determined from a look-up table based on a channel indicated by the applications circuitry 902.
[0090] Synthesizer circuitry 906D of RF circuitry 906 can include a divider, a delay- locked loop (DLL), a multiplexer, and a phase accumulator. In some implementations, the254898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) divider can be a dual modulus divider (DMD), and the phase accumulator can be a digital phase accumulator (DPA). In some implementations, the DMD can be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio. In some example implementations, the DLL can include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these implementations, the delay elements can be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.
[0091] In some implementations, synthesizer circuitry 906D can be configured to generate a carrier frequency as the output frequency, while in other implementations, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some implementations, the output frequency can be a LO frequency (fLO). In some implementations, RF circuitry 906 can include an in- phase / quadrature (I / Q) / polar converter.
[0092] FEM circuitry 908 can include a receive signal path which can include circuitry configured to operate on RF signals received from one or more antennas 910, amplify the received signals and provide the amplified versions of the received signals to RF circuitry 906 for further processing. FEM circuitry 908 can also include a transmit signal path which can include circuitry configured to amplify signals for transmission provided by RF circuitry 906 for transmission by one or more of the one or more antennas 910. In various implementations, the amplification through the transmit or receive signal paths can be done solely in RF circuitry 906, solely in FEM circuitry 908, or in both RF circuitry 906 and FEM circuitry 908.
[0093] In some implementations, FEM circuitry 908 can include a transmit / receive switch to switch between transmit mode and receive mode operation. FEM circuitry 908 can include a receive signal path and a transmit signal path. The receive signal path of FEM circuitry 908 can include a low noise amplifier to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to RF circuitry 906). The transmit signal path of FEM circuitry 908 can include a power amplifier to amplify input RF signals (e.g., provided by RF circuitry 906), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of one or more antennas 910).264898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1)
[0094] In some implementations, PMC 912 can manage power provided to baseband circuitry 904. In particular, PMC 912 can control power-source selection, voltage scaling, battery charging, or direct current (DC) to DC (DC-to-DC) conversion. PMC 912 can often be included when device 900 is capable of being powered by a battery, for example, when device 900 is included in a UE. PMC 912 can increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.
[0095] While Fig. 9 shows PMC 912 coupled only with baseband circuitry 904.However, in other implementations, PMC 912 can be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 902, RF circuitry 906, or FEM circuitry 908.
[0096] In some implementations, PMC 912 can control, or otherwise be part of, various power saving mechanisms of device 900. For example, if device 900 is in an RRC Connected state, where device 900 is still connected to the RAN node as device 900 expects to receive traffic shortly, then device 900 can enter a state known as discontinuous reception mode (DRX) after a period of inactivity. During this state, device 900 can power down for brief intervals of time and thus save power.
[0097] If there is no data traffic activity for an extended period of time, then device 900 can transition off to an RRC Idle state, where device 900 disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. Device 900 can go into a very low power state and device 900 can perform paging where again device 900 periodically can wake up to listen to the network and then power down again. Device 900 may not receive data in this state; in order to receive data, device 900 can transition back to RRC Connected state.
[0098] An additional power saving mode can allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device 900 can be unreachable to the network and can power down completely. Any data sent during this time can incur a large delay and device 900 can assume the delay is acceptable.
[0099] Processors of application circuitry 902 and processors of baseband circuitry 904 can be used to execute elements of one or more instances of a protocol stack. For example, processors of baseband circuitry 904, alone or in combination, can be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of baseband circuitry 904 can utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As274898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) referred to herein, Layer 3 can comprise a radio resource control layer. As referred to herein, Layer 2 can comprise a medium access control layer, a radio link control layer, and a packet data convergence protocol layer, described in further detail below. As referred to herein, Layer 1 can comprise a physical layer of a UE / RAN node.
[0100] Fig. 10 is a diagram of example interfaces 1000 of baseband circuitry according to one or more implementations described herein. One or more components or features of example interfaces 1000 can correspond to one or more components or features described above or elsewhere. Baseband circuitry 1004 can comprise processors 1004A, 1004B, 1004C, 1004D, and 1004E and a memory 1004G utilized by said processors. Each of processors 1004 A, 1004B, 1004C, 1004D, and 1004E can include a memory interface, 1006 A, 1006B, 1006C, 1006D, and 1006E, respectively, to send / receive data to / from memory 1004G. Baseband circuitry can be a component of a UE and / or another type of device or system capable of transmitting and / or receiving wireless signals.
[0101] Baseband circuitry 1004 can further include one or more interfaces to communicatively couple to other circuitries / devices, such as memory interface 1012 (e.g., an interface to send / receive data to / from memory external to baseband circuitry 1004), an application circuitry interface 1014 (e.g., an interface to send / receive data to / from the application circuitry as described herein), an RF circuitry interface 1016, a wireless hardware connectivity interface 1018 (e.g., an interface to send / receive data to / from near field communication components, Bluetooth® components (e.g., Bluetooth® Low Energy), WiFi® components, and other communication components), and a power management interface 1020 (e.g., an interface to send / receive power or control signals to / from a PMC).
[0102] Fig. 11 is a block diagram illustrating components, according to some example implementations, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Fig. 11 shows a diagrammatic representation of hardware resources 1100 including one or more processors 1110 (or processor cores), one or more memory / storage devices 1120, and one or more communication resources 1130, each of which can be communicatively coupled via a bus 1140. For implementations where node virtualization or network function virtualization is utilized, a hypervisor can be executed to provide an execution environment for one or more network slices / sub-slices to utilize hardware resources 1100. Hardware resources 1100 can interact with hypervisor 1102. For example, hypervisor 1102 can schedule or otherwise manage hardware resource 1100.284898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1)
[0103] Processors 1110 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) can include, for example, a processor 1112 and a processor 1114.
[0104] Memory / storage devices 1120 can include main memory, disk storage, or any suitable combination thereof. Memory / storage devices 1120 can include, but are not limited to any type of volatile or non-volatile memory such as dynamic random-access memory (DRAM), static random-access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.
[0105] In some implementations, memory / storage devices 1120 receive and / or store information and instructions 1155 for fragmented SCell addition and activation. A fragmented SCell can include an SCell with fragmented or non-contiguous frequency spectrums that can be used for carrier aggregation. A PCell can communicate with UE 210 to add and activate a fragmented SCell for a carrier aggregation procedure involving UE 210. This can include the PCell enabling UE 210 to provide measurement reports of the spectrums of fragmented SCells, determining which fragmented SCells are well-suited for carrier aggregation, and enabling UE 210 to aggregate carriers from the frequency spectrums of a fragmented SCell. Many other aspects and examples are also described herein.
[0106] Communication resources 1130 can include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 1104 or one or more databases 1106 via a network 1108. For example, communication resources 1130 can include wired communication components (e.g., for coupling via a universal serial bus), cellular communication components, near field communication components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components.
[0107] Instructions 1150A, 1150B, 1150C, 1150D, and / or 1150E can comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of processors 1110 to perform any one or more of the methodologies discussed herein. Instructions 1150 can reside, completely or partially, within at least one of processors 1110 (e.g., within a cache memory), memory / storage devices 1120, or any suitable combination thereof. Furthermore, any portion of instructions 1150A-E can be transferred to hardware294898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) resources 1100 from any combination of peripheral devices 1104 or databases 1106. Accordingly, memory of processors 1110, memory / storage devices 1120, peripheral devices 1104, and databases 1106 are examples of computer-readable and machine-readable media.
[0108] Fig. 12 is a diagram of an example process 1200 for fragmented SCell addition and activation according to one or more implementations described herein. As shown, process 1200 can be implemented by UE 210 and / or baseband circuitry 904. In some implementations, some or all of process 1200 can be performed by one or more other systems or devices, including one or more of the devices of Fig. 2. Additionally, process 1200 can include one or more fewer, additional, differently ordered and / or arranged operations than those shown in Fig. 12. In some implementations, some or all of the operations of process 1200 can be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 1200. As such, the techniques described herein are not limited to the number, sequence, arrangement, timing, etc., of the operations or processes depicted in Fig. 12.
[0109] As shown, process 1200 can include receive, from a primary cell (PCell), secondary cell (SCell) configuration information comprising a spectrum configuration of at least one fragmented SCell (block 1210). Process 1200 can include determine a measurement of at least one spectrum of the at least one fragmented SCell (block 1220). Process 1200 can include communicate, to the PCell, a report based on the measurement (block 1230). Process 1200 can include receive, from the PCell, addition and activation information associated with the at least one SCell for carrier aggregation (block 1240). One or more of the examples described herein can also, or alternatively be part of process 1200.
[0110] Fig. 13 is a diagram of an example process 1300 for fragmented SCell addition and activation according to one or more implementations described herein. As shown, process 1300 can be implemented by base station 222. . Base station 222 can include a PCell or an SCell (relative to UE 210) and can be implemented by the same base station or different base station. In some implementations, some or all of process 1300 can be performed by one or more other systems or devices, including one or more of the devices of Fig. 2. Additionally, process 1300 can include one or more fewer, additional, differently ordered and / or arranged operations than those shown in Fig. 13. In some implementations, some or all of the operations of process 1300 can be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 1300. As such, the techniques described herein are not limited to the number, sequence, arrangement, timing, etc., of the operations or processes depicted in Fig. 13.304898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1)
[0111] As shown, process 1300 can include communicate, to a UE, secondary cell (SCell) configuration information comprising a spectrum configuration of at least one fragmented SCell (block 1310). Process 1300 can include receive, from the UE, a report based on a measurement of at least one spectrum of the at least one fragmented SCell (block 1320). Process 1300 can include determine, based on the report, to select the a measurement of at least one spectrum of the at least one fragmented SCell for addition and activation for carrier aggregation (block 1330). Process 1300 can include communicate, to the UE, an indication of SCell addition and activation associated with the at least one SCell (block 1340). One or more of the examples described herein can also, or alternatively be part of process 1300.
[0112] Examples herein can include subject matter such as a method, means for performing acts or blocks of the method, at least one machine-readable medium including executable instructions that, when performed by a machine (e.g., a processor (e.g., processor, etc.) with memory, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like) cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to implementations and examples described.
[0113] In example 1, which can also include one or more of the examples described herein, a UE or baseband circuitry can comprise: one or more processors configured to: process secondary cell (SCell) configuration information comprising a spectrum configuration of at least one fragmented SCell; determine a measurement of at least one spectrum of the at least one fragmented SCell; generate a report based on the measurement; and process addition and activation information associated with the at least one SCell for carrier aggregation.
[0114] In example 2, which can also include one or more of the examples described herein, the one or more processors are configured to: generate user equipment (UE) capability information comprising an indication of the UE to support carrier aggregation based on an anchor carrier and a non-anchor carrier of a fragmented SCell.
[0115] In example 3, which can also include one or more of the examples described herein, the one or more processors are configured to: generate user equipment (UE) capability information comprising an indication of the UE to support carrier aggregation based on a quality level of a fragmented SCell.
[0116] In example 4, which can also include one or more of the examples described herein, the one or more processors are configured to: generate user equipment (UE) capability314898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) information comprising an indication of the UE to support carrier aggregation involving a fragmented SCell in at least one frequency range (FR).
[0117] In example 5, which can also include one or more of the examples described herein, the spectrum configuration comprises an indication of a system synchronization block (SSB) and a measurement occasion associated with the at least one spectrum.
[0118] In example 6, which can also include one or more of the examples described herein, the spectrum configuration comprises an indication of an anchor spectrum of the at least one fragmented SCell, and the at least one spectrum comprises the anchor spectrum.
[0119] In example 7, which can also include one or more of the examples described herein, the one or more processors are configured to: receive, in response to the report, an indication of SCell selection and addition associated with the at least SCell being selected for carrier aggregation.
[0120] In example 8, which can also include one or more of the examples described herein, the spectrum configuration further comprises an indication of at least one non-anchor spectrum of the at least one fragmented SCell, and the one or more processors are configured to: determine a measurement of the at least one non-anchor spectrum, generate an additional report based on the measurement of the at least on non-anchor spectrum, and receive, in response to the additional report, an indication of addition and activation of the at least on non-anchor carrier for carrier aggregation.
[0121] In example 9, which can also include one or more of the examples described herein, the one or more processors are configured to: receive additional SCell configuration information comprising a configuration of at least one non-anchor spectrum of the at least one SCell, determine a measurement of the at least one non-anchor spectrum, generate an additional report based on the measurement of the at least on non-anchor spectrum, and receive, in response to the additional report, an indication of addition and activation of the at least on non-anchor carrier for carrier aggregation.
[0122] In example 10, which can also include one or more of the examples described herein, the indication of the addition and activation of the at least on non-anchor carrier is received via a media access control (MAC) procedure, or the indication of the addition and activation of the at least on non-anchor carrier comprises an indication of addition and activation of at least one bandwidth part (BWP) that is received via downlink control information (DCI).
[0123] In example 11, which can also include one or more of the examples described herein, the SCell configuration information comprises a spectrum configuration for all324898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) candidate spectrums of the at least one SCell for carrier aggregation.
[0124] In example 12, which can also include one or more of the examples described herein, the SCell configuration information further comprises a measurement occasion associated with each candidate spectrum of the at least one SCell.
[0125] In example 13, which can also include one or more of the examples described herein, the one or more processors are configured to determine a measurement for each candidate spectrum based on the measurement occasion associated with each candidate spectrum.
[0126] In example 14, which can also include one or more of the examples described herein, the one or more processors are configured to determine a measurement for each candidate spectrum according to a measurement scheme configured to prioritize measurement of certain candidate spectrums of the at least one SCell.
[0127] In example 15, which can also include one or more of the examples described herein, the one or more processors are configured to determine a quality of the SCell based on an average of measurements for each candidate spectrum of the at least one SCell, and the report comprises the quality of the SCell.
[0128] In example 16, which can also include one or more of the examples described herein, the one or more processors are configured to determine a quality of the SCell based on a combination of weighted measurements for each candidate spectrum of the at least one SCell, and the report comprises the quality of the SCell.
[0129] In example 17, which can also include one or more of the examples described herein, the report comprises a quality for each candidate spectrum of the at least one SCell.
[0130] In example 18, which can also include one or more of the examples described herein, the report is generated in response to determining that the quality of the SCell exceeds a quality threshold.
[0131] In example 19, which can also include one or more of the examples described herein, the report is generated periodically.
[0132] In example 20, which can also include one or more of the examples described herein, a method may comprise receiving, from a primary cell (PCell), secondary cell (SCell) configuration information comprising a spectrum configuration of at least one fragmented SCell; determining a measurement of at least one spectrum of the at least one fragmented SCell; communicating, to the PCell, a report based on the measurement; and receiving, from the PCell, addition and activation information associated with the at least one SCell for carrier aggregation.334898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1)
[0133] In example 21, which can also include one or more of the examples described herein, the spectrum configuration comprises an indication of an anchor spectrum of the at least one fragmented SCell, and the at least one spectrum comprises the anchor spectrum.
[0134] In example 22, which can also include one or more of the examples described herein, a method can include receiving, in response to the report, an indication of SCell selection and addition associated with the at least SCell being selected for carrier aggregation.
[0135] In example 23, which can also include one or more of the examples described herein, the spectrum configuration further comprises an indication of at least one non-anchor spectrum of the at least one fragmented SCell, and the method further comprising: determining a measurement of the at least one non-anchor spectrum, communicating an additional report based on the measurement of the at least on non-anchor spectrum, and receiving, in response to the additional report, an indication of addition and activation of the at least on non-anchor carrier for carrier aggregation.
[0136] In example 24, which can also include one or more of the examples described herein, the SCell configuration information comprises a spectrum configuration for all candidate spectrums of the at least one SCell for carrier aggregation.
[0137] In example 25, which can also include one or more of the examples described herein, a base station can comprise: one or more processors configured to: communicate, to a user equipment (UE), secondary cell (SCell) configuration information comprising a spectrum configuration of at least one fragmented SCell; receive, from the UE, a report based on a measurement of at least one spectrum of the at least one fragmented SCell; determine, based on the report, to select the a measurement of at least one spectrum of the at least one fragmented SCell for addition and activation for carrier aggregation; and communicate, to the UE, an indication of SCell addition and activation associated with the at least one SCell.
[0138] In example 26, which can also include one or more of the examples described herein, the one or more processors are configured to: receive user equipment (UE) capability information comprising an indication of the UE to support carrier aggregation based on an anchor carrier and a non-anchor carrier of a fragmented SCells.
[0139] In example 27, which can also include one or more of the examples described herein, the one or more processors are configured to: receive user equipment (UE) capability information comprising an indication of the UE to support carrier aggregation based on a quality level of a fragmented SCell.
[0140] In example 28, which can also include one or more of the examples described herein, the one or more processors are configured to: receive user equipment (UE) capability344898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) information comprising an indication of the UE to support carrier aggregation involving a fragmented SCell in at least one frequency range (FR).
[0141] In example 29, which can also include one or more of the examples described herein, the spectrum configuration comprises an indication of a system synchronization block (SSB) and a measurement occasion associated with the at least one spectrum.
[0142] The above description of illustrated examples, implementations, aspects, etc., of the subject disclosure, including what is described in the Abstract, is not intended to be exhaustive or to limit the disclosed aspects to the precise forms disclosed. While specific examples, implementations, aspects, etc., are described herein for illustrative purposes, various modifications are possible that are considered within the scope of such examples, implementations, aspects, etc., as those skilled in the relevant art can recognize.
[0143] In this regard, while the disclosed subject matter has been described in connection with various examples, implementations, aspects, etc., and corresponding Figures, where applicable, it is to be understood that other similar aspects can be used or modifications and additions can be made to the disclosed subject matter for performing the same, similar, alternative, or substitute function of the subject matter without deviating therefrom. Therefore, the disclosed subject matter should not be limited to any single example, implementation, or aspect described herein, but rather should be construed in breadth and scope in accordance with the appended claims below.
[0144] In particular regard to the various functions performed by the above described components or structures (assemblies, devices, circuits, systems, etc.), the terms (including a reference to a “means”) used to describe such components are intended to correspond, unless otherwise indicated, to any component or structure which performs the specified function of the described component (e.g., that is functionally equivalent), even though not structurally equivalent to the disclosed structure which performs the function in the herein illustrated exemplary implementations. In addition, while a particular feature can have been disclosed with respect to only one of several implementations, such feature can be combined with one or more other features of the other implementations as can be desired and advantageous for any given application.
[0145] As used herein, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and354898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form. Furthermore, to the extent that the terms “including”, “includes”, “having”, “has”, “with”, or variants thereof are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising.” Additionally, in situations wherein one or more numbered items are discussed (e.g., a “first X”, a “second X”, etc.), in general the one or more numbered items can be distinct, or they can be the same, although in some situations the context can indicate that they are distinct or that they are the same.
[0146] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.4898-4661 -8703, v. 3
Claims
Attorney Docket No. 106842241740 (P69028WO1)CLAIMSWhat is claimed is:
1. Baseband circuitry, comprising: one or more processors configured to: process secondary cell (SCell) configuration information comprising a spectrum configuration of at least one fragmented SCell; determine a measurement of at least one spectrum of the at least one fragmented SCell; generate a report based on the measurement; and process addition and activation information associated with the at least one SCell for carrier aggregation.
2. The baseband circuitry of claim 1, wherein the one or more processors are configured to: generate user equipment (UE) capability information comprising an indication of the UE to support carrier aggregation based on an anchor carrier and a non-anchor carrier of a fragmented SCell.
3. The baseband circuitry of claim 1, wherein the one or more processors are configured to: generate user equipment (UE) capability information comprising an indication of the UE to support carrier aggregation based on a quality level of a fragmented SCell.
4. The baseband circuitry of claim 1, wherein the one or more processors are configured to: generate user equipment (UE) capability information comprising an indication of the UE to support carrier aggregation involving a fragmented SCell in at least one frequency range (FR).
5. The baseband circuitry of claim 1, wherein the spectrum configuration comprises an indication of a system synchronization block (SSB) and a measurement occasion associated with the at least one spectrum.
6. The baseband circuitry of claim 1, wherein: the spectrum configuration comprises an indication of an anchor spectrum of the at least one fragmented SCell, and374898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) the at least one spectrum comprises the anchor spectrum.
7. The baseband circuitry of claim 6, wherein the one or more processors are configured to: receive, in response to the report, an indication of SCell selection and addition associated with the at least SCell being selected for carrier aggregation.
8. The baseband circuitry of claim 7, wherein: the spectrum configuration further comprises an indication of at least one non-anchor spectrum of the at least one fragmented SCell, and the one or more processors are configured to: determine a measurement of the at least one non-anchor spectrum, generate an additional report based on the measurement of the at least on non-anchor spectrum, and receive, in response to the additional report, an indication of addition and activation of the at least on non-anchor carrier for carrier aggregation.
9. The baseband circuitry of claim 7, wherein the one or more processors are configured to: receive additional SCell configuration information comprising a configuration of at least one non-anchor spectrum of the at least one SCell, determine a measurement of the at least one non-anchor spectrum, generate an additional report based on the measurement of the at least on non-anchor spectrum, and receive, in response to the additional report, an indication of addition and activation of the at least on non-anchor carrier for carrier aggregation.
10. The baseband circuitry of claim 9, wherein: the indication of the addition and activation of the at least on non-anchor carrier is received via a media access control (MAC) procedure, or the indication of the addition and activation of the at least on non-anchor carrier comprises an indication of addition and activation of at least one bandwidth part (BWP) that is received via downlink control information (DCI).384898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1)11. The baseband circuitry of claim 1, wherein the SCell configuration information comprises a spectrum configuration for all candidate spectrums of the at least one SCell for carrier aggregation.
12. The baseband circuitry of claim 11, wherein the SCell configuration information further comprises a measurement occasion associated with each candidate spectrum of the at least one SCell.
13. The baseband circuitry of claim 12, wherein the one or more processors are configured to determine a measurement for each candidate spectrum based on the measurement occasion associated with each candidate spectrum.
14. The baseband circuitry of claim 12, wherein the one or more processors are configured to determine a measurement for each candidate spectrum according to a measurement scheme configured to prioritize measurement of certain candidate spectrums of the at least one SCell.
15. The baseband circuitry of any of claims 13 and 14, wherein: the one or more processors are configured to determine a quality of the SCell based on an average of measurements for each candidate spectrum of the at least one SCell, and the report comprises the quality of the SCell.
16. The baseband circuitry of any of claims 13 and 14, wherein: the one or more processors are configured to determine a quality of the SCell based on a combination of weighted measurements for each candidate spectrum of the at least one SCell, and the report comprises the quality of the SCell.
17. The baseband circuitry of any of claims 13 and 14, wherein the report comprises a quality for each candidate spectrum of the at least one SCell.
18. The baseband circuitry of any of claims 13 and 14, wherein the report is generated in response to determining that the quality of the SCell exceeds a quality threshold.
19. A method, comprising:394898-4661 -8703, v. 3Attorney Docket No. 106842241740 (P69028WO1) receiving, from a primary cell (PCell), secondary cell (SCell) configuration information comprising a spectrum configuration of at least one fragmented SCell; determining a measurement of at least one spectrum of the at least one fragmented SCell; communicating, to the PCell, a report based on the measurement; and receiving, from the PCell, addition and activation information associated with the at least one SCell for carrier aggregation.
20. A base station, comprising: one or more processors configured to: communicate, to a user equipment (UE), secondary cell (SCell) configuration information comprising a spectrum configuration of at least one fragmented SCell; receive, from the UE, a report based on a measurement of at least one spectrum of the at least one fragmented SCell; determine, based on the report, to select the a measurement of at least one spectrum of the at least one fragmented SCell for addition and activation for carrier aggregation; and communicate, to the UE, an indication of SCell addition and activation associated with the at least one SCell.404898-4661 -8703, v. 3
Citation Information
Patent Citations
Carrier aggregation method and device in wireless communication system
US20190246426A1
Anchor cell management procedure for synchronization signal block (SSB)-less carrier
US20240235798A1
Link quality monitoring on multiple candidate cell groups
WO2024031329A1