RRM measurement control based on OD-SSB or OD-smtc

Abstract

Described herein are solutions for controlling radio resource management (RRM) measurements based on on-demand system synchronization blocks (OD-SSB). Controlling the RRM measurements can include activating and deactivating RRM measurements of a carrier frequency corresponding to an OD-SSB or on-demand SSB based measurement timing configuration (OD-STMC). RRM measurements can be controlled by explicitly activating and deactivating RRM measurements of a carrier frequency of a secondary cell (SCell) and / or neighbor cell. RRM measurements can be controlled implicitly by activating and deactivating OD-SSB or OD-STMC of a carrier frequency. Many other aspects and examples are also described herein.

Description

Attorney Docket No.: 106842241540 (P69419WO1)RRM MEASUREMENT CONTROL BASED ON OD-SSB OR OD-SMTCCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 700,610, filed September 27, 2024, the content of which is incorporated herein in its entirety for all purposes.FIELD

[0002] This disclosure relates to wireless communication networks and mobile 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, 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 process for radio resource management (RRM) measurement control based on on-demand system synchronization blocks (OD-SSBs) according to one or more implementations described herein.

[0009] Fig. 5 is a diagram of an example of a process for RRM measurement control based on SSB based measurement timing configuration (SMTC) according to one or more14923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1) implementations described herein.

[0010] Fig. 6 is a diagram of an example of an information element (IE) for RRM measurement control according to one or more implementations described herein.

[0011] Fig. 7 is a diagram of an example of radio resource control (RRC) signaling for RRM measurement control using OD-SSB and on-demand SMTC (OD-SMTC) according to one or more implementations described herein.

[0012] Fig. 8 is a diagram of an example of RRC signaling for RRM measurement control using OD-SSB and OD-SMTC with SMTC1 according to one or more implementations described herein.

[0013] Fig. 9 is a diagram of an example of components of a device according to one or more implementations described herein.

[0014] Fig. 10 is a diagram of example interfaces of baseband circuitry according to one or more implementations described herein.

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

[0016] Fig. 12 is a diagram of an example process for RRM measurement control according to one or more implementations described herein.

[0017] Fig. 13 is a diagram of an example process for RRM measurement control according to one or more implementations described herein.DETAILED DESCRIPTION

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

[0019] 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.24923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1)

[0020] 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 aggregated 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. Intra carrier aggregation can refer to aggregating component carriers of from the same band or spectrum. Inter carrier aggregation can refer to aggregating component carriers from different, fragment, or non-contiguous bands or spectrums.

[0021] An aspect of wireless communication networks can include radio resource management (RRM). RRM can refer to information, signaling, and procedures responsible for the allocation and utilization of radio resources so as to help ensure optimal performance, reliability, quality of service (QoS), and more. RRM can play a meaningful role in managing the radio spectrum, coordinating connections between UEs and base stations, and adapting to dynamic network conditions. RRM can involve a broad set of network features, functions, and operations, such as include frequency spectrum management, radio resource allocation, interference management, load balancing, QoS management, UE power control, handover and mobility management, support for network slicing, predictive analytics and machine learning (ML), interfacing with core network functions, and more. One or more RRM procedures can involve a measurement procedure, whereby a device measures a signal to evaluate for signal strength, noise, quality, interference, and so on.

[0022] A base station can transmit system synchronization blocks (SSBs) to enable a UE to synchronize with and communicate with the base station. This can include the UE initiating a random access channel (RACH) procedure to connect to the base station and register with the network. Typically, the base station is configured to periodically transmit an SSB according to a schedule. However, in some scenarios, an SSB can be transmitted on-demand (OD). An SSB transmitted on-demand can be referred to as an OD-SSB. For example, a PCell can trigger OD- SSB transmissions for a carrier frequency from the SCell to the UE. This can enable the UE to perform RRM measurements based on the OD-SSB transmissions. The RRM measurements can include LI and / or L3 measurements. The OD-SSB transmissions can be triggered in scenarios where the SCell is not configured for always-on SSB transmissions (i.e., where SSBs are transmitted according to a pre-selected periodicity).34923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1)

[0023] OD-SSB transmissions can also be triggered in scenarios where the always-on SSB configuration of the SCell is subject to a periodicity. OD-SSB transmissions can also be triggered in scenarios where the SCell is configured to a UE (e.g., for carrier aggregation purposes) but the UE has not yet received an SCell activation command. In some implementations, OD-SSB transmissions can also be triggered in scenarios where the UE has received the SCell activation command. In any scenario, the UE cannot perform RRM measurement on a carrier frequency of the SCell when the SCell does not transmit an SSB whether due to an always-on configuration or OD-SSB.

[0024] The UE can, however, still perform RRM measurement on the same carrier frequency transmitted by a neighbor cell. Doing so can be beneficial, such as when the carrier frequency of the neighbor cell can be used by the UE. However, in other scenarios, performing RRM measurements for a neighbor cell can be a waste of batter power. For example, when the SCC of the SCell is intra-band and co-located with the PCC of the PCell, and UE 210 does not support intra-band, non-collocated carrier aggregation, performing RRM measurements on the same carrier frequency from a neighbor cell can be a waste of UE batter power. Similarly, performing RRM measurements can be a waste of UE batter power when a neighbor cell is incapable of transmitting an OD-SSB on the same carrier frequency as the SCC of the SCell.

[0025] One or more of the techniques described herein address these deficiencies by providing solutions for controlling RRM measurements based on OD-SSB. Controlling the RRM measurements of a UE can include activating and deactivating RRM measurements according to a carrier frequency of an OD-SSB. A base station can explicitly activate or deactivate RRM measurements using radio resource control (RRC) signaling, a media access control (MAC) control element (CE) (MAC-CE), or downlink control information (DCI). The base station can implicitly activate or deactivate RRM measurements on the UE based on enabling or disabling OD-SSB transmissions for a carrier frequency. In such a scenario, when the UE is unable to perform RRM measurements on OD-SSB transmissions from the SCell, the UE can still perform RRM measurements on OD-SSB transmissions from one or more neighbor cells. A neighbor or neighboring cell can include a base station with a cell coverage area wherein the UE is located but to which the UE is not connected. For example, the UE can be connected to a PCell via a PCC and an SCell via an SCC. Other cells within range of the UE can be neighbor cells.

[0026] One or more of the techniques described herein can also provide solutions for controlling RRM measurements using on-demand SSB based measurement timing configuration (SMTC) (OD-SMTC). Generally, an SSB burst periodicity can be set at, for example, 5, 10, 20, 40, 80 or 160 milliseconds (ms). When a UE is in a connected mode, the UE may not be required to perform measurements (e.g., RRM measurements) according to the SSB periodicity and an44923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1) appropriate measurement periodicity can be configured according to channel conditions. Doing so can avoid unnecessary measurements and save UE power. An SMTC window can be used to notify the UE about a periodicity and timing of the SSBs, which can be always-on SSB transmissions, OD-SSB transmissions, or a combination thereof. Controlling RRM measurements can be achieved by explicit or implicit activation and deactivation of OD-SMTC windows that include always-on SSB transmissions or OD-SSB transmissions

[0027] 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 and base stations 120, 130, and 140. Base station 120 can be operating as a PCell to UE 110, and base station 130 can be operating as an SCell to UE 110. UE 110 can be connected to the PCell and the SCell via carrier aggregation comprising a primary component carrier (PCC) form the PCell and a secondary component carrier (SCC) from the SCell. The neighbor cell can be configured to use a frequency carrier that is the same as the SCC of SCell.

[0028] The PCell can explicitly or implicitly enable and disable RRM measurement procedures performed by UE 110 regarding the carrier frequency of the SCC and the same carrier frequency of the neighbor cell. Explicit activation and deactivation of RRM measurements can be achieved via an explicit indication to enable and disable RRM measurements of a carrier frequency of OD-SSB transmissions or OD-SMTC. This can involve RRC signaling, MAC-CE, or DCI. Implicit activation and deactivation of RRM measurements can be achieved by enabling or disabling OD-SSB or OD-SMTC on the SCell, the neighbor cell, or at the end of an OD-SSB transmission burst. This can also involve RRC signaling, MAC-CE, or DCI. Additional examples of these and many other techniques, features, and implementations are described below with reference to the figures that follow.

[0029] 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., long-term evolution (LTE)), 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 3GPP54923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1) standards (e.g., sixth generation (6G) standards, seventh generation (7G) standards, etc.), institute of electrical and electronics engineers (IEEE) standards, and more.

[0030] 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 short-lived 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)), proximitybased 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 loT 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.

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

[0032] 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; and64923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1) 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.

[0033] 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 can 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.

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

[0035] 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 74923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1) 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.

[0036] 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 can 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.

[0037] 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 by84923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1) individual RAN nodes 222. This virtualized framework can allow freed-up processor cores of RAN nodes 222 to perform or execute other virtualized applications.

[0038] 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 plane protocol terminations toward UEs 210, and that can be connected to a 5G core network (5GC) 230 via an NG interface.

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

[0040] 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 timefrequency 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 timefrequency 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.94923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1)There are several different physical downlink channels that are conveyed using such resource blocks.

[0041] 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 certain 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.

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

[0043] One or more of the techniques described herein can include solutions for controlling RRM measurements based on OD-SSB. Controlling the RRM measurements can include activating and deactivating RRM measurements of a carrier frequency corresponding to an OD- SSB or OD-STMC. RRM measurements can be explicitly controlled using RRC signaling, a MAC-CE, or DCI to activate and deactivate RRM measurements of a carrier frequency of an SCell and neighbor cell. RRM measurements can be implicitly controlled using RRC signaling, a MAC-CE, or DCI to activate and deactivate OD-SSB or OD-STMC of a carrier frequency. Many other aspects and examples are also described herein.

[0044] 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 104923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1) 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. For 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.

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

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

[0047] 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 with114923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1)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 over 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.

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

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

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

[0051] 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 MCG124923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1)310. MCG 310 and SCG 320 can also implement a standalone (SA) and / or a non-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, 5G NR, 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.

[0052] A fragmented cell and a non-fragmented cell can each include one or more types of cells, such as a PCell, SCell, neighbor cell, etc. A fragmented cell and a non-fragmented cell can each include bandwidths designated, at least in part, for allocation and use in UL and / or DL communications. A fragmented cell and non-fragmented cell can each include a different number, arrangement, allocation and sizes of bandwidths. The bandwidths of a fragmented SCell can include inter-band, non-contiguous, or fragmented frequency spectrums. By contrast, the bandwidths of a non-fragmented cell can include intra-band, contiguous, or non-fragmented frequency spectrums. A frequency spectrum can be associated with an SSB and / or 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.

[0053] Fig. 4 is a diagram of an example of a process 400 for radio resource management (RRM) measurement control based on on-demand system synchronization blocks (OD-SSBs) according to one or more implementations described herein. As shown, process 400 can be implemented by UE 210 and one or more base stations 222. A PCell, one or more SCells, and one or more neighbor cells can be implemented by one base station 222 or multiple base stations 222. For example, a single base station 222 can operate as both a PCell and one or more SCells relative to UE 210, and a neighbor cell call be implemented by another base station 222. In some examples, one base station 222 can operate as a PCell and one or more other base stations can operate as SCells and / or one or more neighbor cells relative to UE 210. The PCell, one or more SCells, and one or more neighbor cells can include any combination of non-fragmented or fragmented cells.

[0054] In some implementations, some or all of process 400 can be performed by one or more other systems or devices, including one or more of the devices of Fig. 2. Additionally, process 400 can include one or more fewer, additional, differently ordered and / or arranged operations than those shown in Fig. 4. In some implementations, some or all of the operations of 134923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1) process 400 can be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 400. As such, the techniques described herein are not limited to the number, sequence, arrangement, timing, etc., of the operations or processes depicted in Fig. 4.

[0055] As shown, process 400 can include UE 210 communicating UE capability information to the PCell (block 410). The UE capability information can include information about the capabilities of UE 210 for carrier aggregation. For example, the UE capability information can include an indication of whether UE 210 can engage in inter-frequency carrier aggregation, intra-frequency carrier aggregation, carrier aggregation between co-located cells, carrier aggregation between non-co-located cells, and so on.

[0056] Process 400 can include UE 210, the PCell, and the SCell communicating with one another for carrier aggregation purposes (block 420). The PCell can configure UE 210 to measure carrier bandwidths of the SCell and the neighbor cell (also referred to as a neighbor cell). UE 210 can generate a measurement report of the measurements and provide the measurement report to the PCell. The PCell can determine, based on the measurement report, whether the SCell (and / or a component carrier thereof) is to undergo addition and activation with respect to UE 210 for carrier aggregation purposes. UE 210 can establish carrier aggregation that can include a primary component carrier (PCC) from the PCell and a secondary component carrier (SCC) from the SCell.

[0057] Process 400 can include the PCell determining a network SSB configuration (block 430). For example, the PCell can communicate with the SCell and / or the neighbor cell via a backhaul network to determine information about a configuration and / or capabilities of the SCell and / or the neighbor cell. The information can include an arrangement or configuration of component carriers, candidate carriers, and other frequency spectrums of the SCell and / or the neighbor cell, including whether the SCell and the neighbor cell have one or more carriers in common.

[0058] The information can also include an indication of whether the SCell and / or neighbor cell is configured as having always-on SSB, an always-on SSB that is only active periodically, capable of OD-SSB, whether OD-SSB is activated or deactivated, etc. Always-on SSB can include a scenario in which a cell is consistently or repeatedly transmitted an SSB (e.g., to UEs 210) according to a schedule. This information can be determined on a cell-specific level, a carrier-specific level, a bandwidth part (BWP) level, etc., for the SCell and / or neighbor cell. As such, the PCell can determine whether

[0059] Process 400 can include the PCell determining RRM measurement skip instructions (block 440). For example, the PCell can determine RRM measurement skip instructions for UE 144923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1)210. The PCell can determine the instructions based on the arrangement or configuration of frequency spectrums of the SCell and / or the neighbor cell, the SSB configuration and capabilities of the SCell and / or the neighbor cell. The PCell can determine RRM measurement skip instructions based on the UE capability information. The RRM measurement skip instructions can include an indication of whether UE 210 is to skip RRM measurements or not skip RRM measurements relative to a component carrier.

[0060] For example, the PCell can determine that UE 210 is to perform RRM measurements of the SCell when the SCell is configured for always-on SSB or capable of OD-SSB. An OD- SSB can be triggered by the network (e.g., the PCell) by prompting the SCell via the backhaul network. By contrast, the PCell can determine that UE 210 can skip RRM measurements for the SCell when the SCell is not configured for always-on SSB or capable of OD-SSB. In some implementations, even when the SCell is not configured for always-on SSB or capable of OD- SSB, the PCell can determine that UE 210 is not to skip RRM measurements when the neighbor SCell is configured for always-on SSB or capable of OD-SSB on the same carrier frequency as the SCell component carrier used as a carrier aggregation.

[0061] In another example, the PCell can determine that UE 210 is to skip RRM measurements when an SCC is not used as a PCC from a deployment perspective; the SCell is intra-band and co-located with the PCell; and UE 210 does not support intra-band, noncollocated carrier aggregation. Thus, the PCell can determine that UE 210 is to skip the RRM measurement. This is because the SCell cannot be changed to another non-co-located neighbor cell because UE 210 does not support intra-band, non-collocated carrier aggregation. In another example, the PCell can determine that UE 210 is to skip RRM measurements when the PCC is aware that OD-SSB is not available or transmitted from any other neighbor cells on the same carrier. Process 400 can include the PCell communicating instructions to the SCell and / or neighbor cell for OD-SSB transmissions (block 455). The instructions can be to activate or deactivate the OD-SSB transmissions. The instructions can be sent via a backhaul network or as RRC signaling, a MAC control element (CE) (MAC-CE), downlink control information (DCI), and so on.

[0062] Process 400 can include the PCell communicating RRM measurement instructions (block 450). For example, the PCell can send UE 210 instructions to perform RRM measurements on a signal from the SCell (block 460). Additionally, or alternatively, the PCell can send UE 210 instructions to perform RRM measurements on a signal from the neighbor cell (block 470). The RRM measurement instructions can include an indication to skip RRM measurements when the SCell does not have always-on SSB transmissions or when the always- on SSB transmissions only occur periodically. In some implementations, RRM measurement 154923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1) instructions can be to skip, forego, or to refrain from RRM measurements all together, skip RRM measurements for the SCell but perform RRM measurements for the neighbor cell on the same frequency carrier, etc.

[0063] Additionally, or alternatively, the PCell can send UE 210 instructions to skip or not perform RRM measurements on a signal form the SCell and / or a signal from the neighbor cell (block 480). The RRM measurement instructions can be explicit or implicit instructions to skip (or to not skip) RRM measurement associated with a component carrier of a carrier aggregation scenario. The carrier aggregation scenario can include a primary component carrier (PCC) associated with a PCell and a secondary component carrier associated with an (SCell). The PCell and the SCell can be co-located (e.g., of the same base station) or non-co-located (e.g., of different base stations). Additionally, or alternatively, the component carriers can be from contiguous or non-fragmented bandwidths or from non-contiguous or fragmented bandwidths. In some implementations, the instructions can be for UE 210 perform an RRM measurement on a carrier frequency of a neighbor cell that is the same carrier frequency of the component carrier of the SCell. The PCell can also send explicit instructions to activate and / or deactivate RRM measurements and / or OD-SSBs (see, e.g., 450).

[0064] The explicit instructions to skip the RRM measurement can be sent as RRC signaling, a MAC control element (CE) (MAC-CE), downlink control information (DCI), and so on. The explicit instructions can include an information element (IE), a parameter, and / or 1 -bit indicator. In one example, the explicit instructions can be an OD-SSB_RRMSkip parameter of an RRC IE or MAC-CE (see, block 450). A value of 1, yes, true, etc., of the OD-SSB_RRMSkip parameter can indicate that UE 210 is to skip the RRM measurement. In some implementations, another type of IE, parameter, Boolean, or bit value can be used. The RRM measurements can be for one or more RRM procedures. In some implementations, the RRM measurements can include an LI and / or L3 measurement. In some implementations, an NSCC SSB parameter can be equal to a number of configured SCell(s) with only SSB based L3 measurement configured, which is measured without a measurement gap (MG) except for the SCells where the value of the OD- SSB RRMSkip parameter is set to yes, 1, true, etc.

[0065] The PCell can trigger or indicate OD-SSB transmissions by the SCell or neighbor cell via RRC signaling (not shown). The RRC signaling can also be used to configure the SCell, activate the SCell with respect to UE 210, and provide OD-SSB configurations. MAC-CE can be used to indicate or trigger OD-SSB transmission for the SCell and / or the neighbor cell when the SCell is configured to UE 210 but before UE 210 receives a SCell activation command form the PCell. MAC-CE can be used to indicate or trigger OD-SSB transmission for the SCell and / or the neighbor cell when UE 210 receives an SCell activation command (e.g., for carrier aggregation 164923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1) purposes).

[0066] In some implementations, RRM measurement can be implicitly enabled and disabled (see, block 450). The PCell can enable or trigger OD-SSB via RRC signaling and / or MAC-CE. In response, UE 210 can automatically enable RRM measurement on the PCell, SCell, and / or neighbor cells on the same carrier frequency. The PCell can explicitly deactivate OD-SSB, thus causing UE 210 to implicitly disable RRM measurements. The PCell can explicitly deactivate the SCell with respect to UE 210 and carrier aggregation, thus causing UE 210 to implicitly disable RRM measurements (see, block 450). Additionally, or alternatively, UE 210 can implicitly discontinue RRM measurements after a set of consecutive SSB transmission bursts turns off OD-SSB or any other the SSB transmissions stop for any other reason. When UE 210 implicitly disables RRM measurements, UE 210 can do so for the RRM measurements for both the SCell and the neighbor cells on the same carrier frequency. In some implementations, an Nscc SSB parameter can be equal to a number of configured SCell(s) with only SSB based L3 measurement configured, which is measured without a measurement gap (MG) except for the ones with OD-SSB only and the OD-SSB is not being transmitted.

[0067] One or more of the techniques, described herein, can include solutions for partial cancelation of RRM measurement of an SSC. In some implementations, only some cells can share the same pattern of OD-SSB (in terms of on and off periodicity) while other cells can use always-on SSB. Base station 222 can provide UE 210 with network (NW) assistance information to help or enable UE 210 to reduce RRM measurement overhead and power consumption. RRC signaling, a MAC-CE, or DCI can be provided to UE 210. The information can include a cell ID (e.g. a PCell identity (PCI)) or cell list as, or as part of, OD-SSB configuration information for the network. UE 210 can apply the same OD-SSB configuration to all indicated cells (e.g., cells indicated in the cell list), including periodicity, time offset, as well as on / off status of OD-SSB. In some implementations, base station 222 can also, or alternatively, indicate cells with an always-on SSB configuration so that once OD-SSB is not transmitted by some cells, UE 210 can selectively measure those cells using an always-on SSB approach.

[0068] Fig. 5 is a diagram of an example of a process for RRM measurement control based on on-demand SSB based measurement timing configuration (OD-SMTC) according to one or more implementations described herein. An OD-SMTC can include one or more SMTC windows during which UE 210 performs an RRM measurement on one or more OD-SSBs transmitted by an SCell or neighbor cell(s). OD-SMTC can be activated or deactivated upon SCell addition, SCell activation, and via RRC signaling, a MAC-CE, or DCI explicitly or implicitly configuring UE 210 and an SCell.

[0069] As shown, process 500 can be implemented by UE 210 and one or more base stations 174923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1)222. A PCell, one or more SCells, and one or more neighbor cells can be implemented by one base station 222 or multiple base stations 222. For example, a single base station 222 can operate as both a PCell and one or more SCells relative to UE 210, and a neighbor cell call be implemented by another base station 222. In some examples, one base station 222 can operate as a PCell and one or more other base stations can operate as SCells and / or one or more neighbor cells relative to UE 210. The PCell, one or more SCells, and one or more neighbor cells can include any combination of non-fragmented or fragmented cells.

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

[0071] As shown, process 500 can be implemented by UE 210 and one or more base stations 222. A PCell, one or more SCells, and one or more neighbor cells can be implemented by one base station 222 or multiple base stations 222. For example, a single base station 222 can operate as both a PCell and one or more SCells relative to UE 210, and a neighbor cell call be implemented by another base station 222. In some examples, one base station 222 can operate as a PCell and one or more other base stations can operate as SCells and / or one or more neighbor cells relative to UE 210. The PCell, one or more SCells, and one or more neighbor cells can include any combination of non-fragmented or fragmented cells.

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

[0073] As shown, process 500 can include UE 210 communicating UE capability information to the PCell (block 510). The UE capability information can include information about the capabilities of UE 210 for carrier aggregation. For example, the UE capability information can include an indication of whether UE 210 can engage in inter-frequency carrier 184923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1) aggregation, intra-frequency carrier aggregation, carrier aggregation between co-located cells, carrier aggregation between non-co-located cells, and so on.

[0074] Process 500 can include UE 210, the PCell, and the SCell communicating with one another for carrier aggregation purposes (block 520). The PCell can configure UE 210 to measure carrier bandwidths of the SCell and the neighbor cell (also referred to as a neighbor cell). UE 210 can generate a measurement report of the measurements and provide the measurement report to the PCell. The PCell can determine, based on the measurement report, whether the SCell (and / or a component carrier thereof) is to undergo addition and activation with respect to UE 210 for carrier aggregation purposes. UE 210 can establish carrier aggregation that can include a primary component carrier (PCC) from the PCell and a secondary component carrier (SCC) from the SCell.

[0075] Process 500 can include the PCell determining a network SSB configuration (block 530). For example, the PCell can communicate with the SCell and / or the neighbor cell via a backhaul network to determine information about a configuration and / or capabilities of the SCell and / or the neighbor cell. The information can include an arrangement or configuration of component carriers, candidate carriers, and other frequency spectrums of the SCell and / or the neighbor cell, including whether the SCell and the neighbor cell have one or more carriers in common. In some implementations, this can be done via RRC signaling, MAC signaling, DCI, etc., and / or can involve UE 210.

[0076] The information can also include an indication of whether the SCell and / or neighbor cell is configured as having always-on SSB, an always-on SSB that is only active periodically, capable of OD-SSB, whether OD-SSB is activated or deactivated, etc. Always-on SSB can include a scenario in which a cell is consistently or repeatedly transmitted an SSB (e.g., to UEs 210) according to a schedule. This information can be determined on a cell-specific level, a carrier-specific level, a bandwidth part (BWP) level, etc., for the SCell and / or neighbor cell. As such, the PCell can determine whether

[0077] Process 500 can include the PCell determining RRM measurement skip instructions (block 540). For example, the PCell can determine RRM measurement skip instructions for UE 210. The PCell can determine the instructions based on the arrangement or configuration of frequency spectrums of the SCell and / or the neighbor cell, the SSB configuration and capabilities of the SCell and / or the neighbor cell. The PCell can determine RRM measurement skip instructions based on the UE capability information. The RRM measurement skip instructions can include an indication of whether UE 210 is to skip RRM measurements or not skip RRM measurements relative to a component carrier.

[0078] For example, the PCell can determine that UE 210 is to perform RRM measurements 194923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1) of the SCell when the SCell is configured for always-on SSB or capable of OD-SSB and / or OD- SMTC. An OD-SMTC can include an SMTC window that includes one or more OD-SSB transmissions, with a particular periodicity, and that occurs a certain number of times or for a certain duration. An OD-SSB and / or OD-SMTC can be triggered by the network (e.g., the PCell) by prompting the SCell via the backhaul network. By contrast, the PCell can determine that UE 210 can skip RRM measurements for the SCell when the SCell is not configured for always-on SSB or capable of OD-SSB and / or OD-SMTC. In some implementations, even when the SCell is not configured for always-on SSB or capable of OD-SSB and / or OD-SMTC, the PCell can determine that UE 210 is not to skip RRM measurements when the neighbor SCell is configured for always-on SSB or capable of OD-SSB and / or OD-SMTC on the same carrier frequency as the SCell component carrier used as a carrier aggregation.

[0079] In another example, the PCell can determine that UE 210 is to skip RRM measurements when an SCC is not used as a PCC from a deployment perspective; the SCell is intra-band and co-located with the PCell; and UE 210 does not support intra-band, noncollocated carrier aggregation. Thus, the PCell can determine that UE 210 is to skip the RRM measurement. This is because the SCell cannot be changed to another non-co-located neighbor cell because UE 210 does not support intra-band, non-collocated carrier aggregation. In another example, the PCell can determine that UE 210 is to skip RRM measurements when the PCC is aware that OD-SSB and / or OD-SMTC is not available or transmitted from any other neighbor cells on the same frequency carrier. Process 500 can include the PCell communicating instructions to the SCell and / or neighbor cell for OD-SSB transmissions using and / or OD-SMTC (block 555). The instructions can be to activate or deactivate the OD-SSB transmissions with OD-SMTC. The instructions can be sent via a backhaul network or as RRC signaling, a MAC- CE, DCI, and so on.

[0080] Process 500 can include the PCell communicating RRM measurement instructions (block 550). For example, the PCell can send UE 210 instructions to perform RRM measurements on a signal from the SCell (block 560). Additionally, or alternatively, the PCell can send UE 210 instructions to perform RRM measurements on a signal from the neighbor cell (block 570). The RRM measurement instructions can include an indication to skip RRM measurements when the SCell does not have always-on SSB transmissions or when the always- on SSB transmissions only occur periodically. In some implementations, RRM measurement instructions can be to skip, forego, or to refrain from RRM measurements all together, skip RRM measurements for the SCell but perform RRM measurements for the neighbor cell on the same frequency carrier, etc.

[0081] Additionally, or alternatively, the PCell can send UE 210 instructions to skip or not 204923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1) perform RRM measurements on a signal form the SCell and / or a signal from the neighbor cell (block 580). The RRM measurement instructions can be explicit or implicit instructions to skip (or to not skip) RRM measurement associated with a component carrier of a carrier aggregation scenario. The carrier aggregation scenario can include a primary component carrier (PCC) associated with a PCell and a secondary component carrier associated with an (SCell). The PCell and the SCell can be co-located (e.g., of the same base station) or non-co-located (e.g., of different base stations). Additionally, or alternatively, the component carriers can be from contiguous or non-fragmented bandwidths or from non-contiguous or fragmented bandwidths. In some implementations, the instructions can be for UE 210 perform an RRM measurement on a carrier frequency of a neighbor cell that is the same carrier frequency of the component carrier of the SCell. The PCell can also send explicit instructions to activate and / or deactivate RRM measurements and / or OD-SSBs within OD-SMTC windows (see, e.g., 550).

[0082] The explicit instructions to skip the RRM measurement can be sent as RRC signaling, a MAC control element (CE) (MAC-CE), downlink control information (DCI), and so on. The explicit instructions can include an information element (IE), a parameter, and / or 1 -bit indicator. In one example, the explicit instructions can be an OD-SMTC_RRMSkip parameter of an RRC IE or MAC-CE (see, block 550). A value of 1, yes, true, etc., of the OD-SMTC_RRMSkip parameter can indicate that UE 210 is to skip the RRM measurement. In some implementations, another type of IE, parameter, Boolean, or bit value can be used. The RRM measurements can be for one or more RRM procedures. In some implementations, the RRM measurements can include an LI and / or L3 measurement. In some implementations, an NSCC SSB parameter can be equal to a number of configured SCell(s) with only SSB based L3 measurement configured, which is measured without a measurement gap (MG) or SMTC window except for the SCells where the value of the OD-SMTC_RRMSkip parameter is set to yes, 1, true, etc.

[0083] The PCell can trigger or indicate OD-SSB transmissions by the SCell or neighbor cell via RRC signaling (not shown). The RRC signaling can also be used to configure the SCell, activate the SCell with respect to UE 210, and provide OD-SSB and / or OD-SMTC configurations. MAC-CE can be used to indicate or trigger OD-SSB transmission using OD- SMTC for the SCell and / or the neighbor cell when the SCell is configured to UE 210 but before UE 210 receives a SCell activation command form the PCell. MAC-CE can be used to indicate or trigger OD-SSB transmission with OD-SMTC for the SCell and / or the neighbor cell when UE 210 receives an SCell activation command (e.g., for carrier aggregation purposes).

[0084] In some implementations, RRM measurement can be implicitly enabled and disabled (see, block 550). The PCell can enable or trigger OD-SMTC via RRC signaling and / or MAC- CE. In response, UE 210 can automatically enable RRM measurement on the PCell, SCell,214923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1) and / or neighbor cells on the same carrier frequency. The PCell can explicitly deactivate OD- SSB, thus causing UE 210 to implicitly disable RRM measurements. The PCell can explicitly deactivate the SCell with respect to UE 210 and carrier aggregation, thus causing UE 210 to implicitly disable RRM measurements (see, block 550). Additionally, or alternatively, UE 210 can implicitly discontinue RRM measurements after a set of consecutive SSB transmission bursts turns off OD-SSB and / or OD-SMTC or any other the SSB transmissions stop for any other reason. When UE 210 implicitly disables RRM measurements, UE 210 can do so for the RRM measurements for both the SCell and the neighbor cells on the same carrier frequency. In some implementations, an Nscc SMTC parameter can be equal to a number of configured SCell(s) with only SSB based L3 measurement configured, which is measured without a measurement gap (MG) except for the ones with OD-SMTC only and the OD-SMTC is not being transmitted.

[0085] Fig. 6 is a diagram of an example 600 of an IES for RRM measurement control according to one or more implementations described herein. Example 600 can represent information transmitted via RRC signaling, MAC-CE, or DCI to . As shown, example 600 can include a MeasObjctNR IE with one or more parameters, such as a ssbFrequency parameter, ssbSubcarrierSpacing parameter, smtcl parameter, smtc2 parameter, and so on. IE 600 can include also, or alternatively include an ODSSB-ConfigMobility IE that can include a smtc parameter, ssb-ToMeasure parameter, PCI parameter, and more. The IEs of example 600 can be used to configure measurement of OD-SSBs. For example, an ODSSB-ConfigMobility IE can include, at least, a list of SMTC parameters and a list of ssb-ToMeasure parameters for different OD-SSB patterns. Additionally, or alternatively, an OD-SSB or OD-SSB configuration can adapt between different periodicities via MAC-CE. The techniques described herein can include one or more additional, fewer, alternative, or alternatively arranged IEs and / or parameters to enable RRM measurement control based on OD-SSB and OD-SMTC.

[0086] Fig. 7 is a diagram of an example 700 of radio resource control (RRC) signaling for RRM measurement control using OD-SSB and on-demand SMTC (OD-SMTC) according to one or more implementations described herein. The events, times, windows, number of SMTCs, number of OD-SSBs, etc., of example 700 are provided as a non-limited example of one or more of the techniques described herein. As shown, example 700 can include time (T) represented along a horizontal axis. At Tl, a PCell can activated an SCell using MAC-CE or another type of signaling or information. A MAC-CE application delay can transpire between the activation of the SCell and UE 210 adapting to an ODSSB-ConfigMobility IE of the MAC-CE, which can coincide with a start of an OD-SMTC periodicity. The delay can result from UE 210 transitioning from not performing RRM measurements to performing RRM measurements based on OD-SSB and / or OD-SMTC windows. The ODSSB-ConfigMobility IE can include a number, 224923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1) configuration, periodicity, and pattern of OD-SSBs and / or OD-SMTC windows. An OD-SMTC, as referred to herein, can have a numerology, including a periodicity, duration, number of OD- SMTC windows in an SMTC set, a time offset, etc.

[0087] An OD-SMTC period or window that includes can occur during the OD-SMTC periodicity, such that includes two or more OD-SSBs can occur within the OD-SMTC window, and an end of the OD-SMTC periodicity can coincide with an end of the SMTC window. Additional SMTC windows with additional OD-SSBs can follow, each OD-SMTC window occurring within an OD-SMTC periodicity. As shown, OD-SSB transmissions can be terminated (e.g., after a burst of OD-SSB transmissions or in repones to an explicit or implicit instruction to terminated OD-SSB transmissions). In response, UE 210 can adapt or transitions to RRM measurements based on another type of SSB transmission from the SCell (e.g., always-on SSB transmissions) unless or until UE 210 receives another ODSSB-ConfigMobility IE of another MAC-CE from the PCell.

[0088] Fig. 8 is a diagram of an example 800 of RRC signaling for RRM measurement control using OD-SSB and OD-SMTC with SMTC1 according to one or more implementations described herein. As shown, example 800 can include time (T) represented along a horizontal axis. SMTC1 can include SMTC windows for always-on SSB transmissions (or always-SSBs) according to an SMTC1 periodicity. OD-SSB transmissions can also occur during a set of SMTC windows (or OD-SMTC) between a periodicity of SMTC1 windows. As such, always-on SSB transmissions can be measured during of SMTC1 windows, and OD-SSB transmissions can be measured within OD-SMTC windows occurring between SMTC1 windows. An OD-SMTC, as referred to herein, can have a numerology, including a periodicity, duration, number of OD- SMTC windows in an SMTC set, a time offset, etc.

[0089] The SCell can be configured for always-on SSB transmissions during SMTC1 windows occurring at an SMTC1 periodicity. At TO, the PCell can send RRC reconfiguration information for SCell addition, which can cause the SCell to be deactivated for always-on SSB transmissions during SMTC1 windows and configured for OD-SSB transmissions during OD- SMTC windows. At Tl, the PCell can send a MAC-CE for SCell activation. A MAC-CE application delay can transpire, during which the SCell discontinues always-on SSB transmissions during SMTC1 windows and begins OD-SSB transmissions during OD-SMTC windows. The OD-SSB transmissions during OD-SMTC windows can occur according to an OD-SMTC periodicity, and each OD-SMTC window can include an OD-SSB transmission. SCell activation can occur between Tl (reception of the MAC-CE) and T2 (channel state information (CSI) is obtained. At T3, OD-SSB, and corresponding RRM measurement procedures, can be terminated, UE 210 can transition or adapt back to RRM measurement of234923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1) always-on SSB transmissions during SMTC1 windows occurring at an SMTC1 periodicity. As shown, this can occur after SCell activation is completed and in response to receive an SS-B ConfigMobility IE or another type of IE, CE, information or instruction. . As shown, UE 210 can transition between RRM measurements of always-on SSB transmissions during SMTC1 windows and RRM measurements of OD-SSBs during OD-SMTC windows can occur during SCell addition (TO to Tl), SCell activation (T1 to T2), and completion of SCell activation (T2 and T3). These transitions can be prompted or triggered by UE 210 receiving RRC signaling for SCell addition at TO, receiving a MAC-CE for SCell activation at Tl, and receiving an SSB- ConfigMobility IE at T2 or T3.

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

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

[0092] 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 244923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1) 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 904 A, 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 904A-D) can handle various radio control functions 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 904A-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.

[0093] In some implementations, memory 904G can receive and / or store information and instructions for controlling RRM measurements based on OD-SSB. Controlling the RRM measurements can include activating and deactivating RRM measurements of a carrier frequency corresponding to an OD-SSB or OD-STMC. RRM measurements can be explicitly controlled using RRC signaling, a MAC-CE, or DCI to activate and deactivate RRM measurements of a carrier frequency of an SCell and neighbor cell. RRM measurements can be implicitly controlled using RRC signaling, a MAC-CE, or DCI to activate and deactivate OD-SSB or OD-STMC of a carrier frequency. Many other aspects and examples are also described herein.

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

[0095] In some implementations, baseband circuitry 904 can provide for communication compatible with one or more radio technologies. For example, in some implementations,254923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1) baseband circuitry 904 can support communication with a NG-RAN, an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (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.

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

[0097] In some implementations, the receive signal path of RF circuitry 906 can include mixer circuitry 906 A, 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.

[0098] 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 and mixer circuitry 906A of the transmit signal path can include two or more mixers and can be arranged for quadrature 264923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1) 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 906A 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.

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

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

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

[0102] 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, the 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 phase274923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1) 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.

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

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

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

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

[0107] 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 284923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1) similar power management operations for, other components such as, but not limited to, application circuitry 902, RF circuitry 906, or FEM circuitry 908.

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

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

[0110] 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, [oni] 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). As 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.

[0112] 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 1004A, 1004B, 1004C, 1004D, and 1004E can include a memory interface, 1006 A, 1006B, 1006C, 1006D, and 294923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1)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.

[0113] 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), Wi-Fi® 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).

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

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

[0116] 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.304923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1)

[0117] In some implementations, memory / storage devices 1120 receive and / or store information and instructions 1155 for controlling RRM measurements based on OD-SSB. Controlling the RRM measurements can include activating and deactivating RRM measurements of a carrier frequency corresponding to an OD-SSB or OD-STMC. RRM measurements can be explicitly controlled using RRC signaling, a MAC-CE, or DCI to activate and deactivate RRM measurements of a carrier frequency of an SCell and neighbor cell. RRM measurements can be implicitly controlled using RRC signaling, a MAC-CE, or DCI to activate and deactivate OD- SSB or OD-STMC of a carrier frequency. Many other aspects and examples are also described herein.

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

[0119] 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 hardware 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.

[0120] Fig. 12 is a diagram of an example process 1200 for RRM measurement control according to one or more implementations described herein. As shown, process 1200 can be implemented by UE 210. 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.314923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1)

[0121] As shown, process 1200 can include receiving and / or processing measurement instructions relating to a secondary cell (SCell) using a frequency carrier for a first on-demand system synchronization block (OD-SSB) transmission (block 1210). Process 1200 can include when the measurement instructions comprise an indication to skip measurement of the first OD- SSB transmission, foregoing measurement the first OD-SSB transmission of the frequency carrier (block 1220). Process 1200 can include when the measurement instructions comprise an indication to measure the first OD-SSB transmission, measuring the frequency carrier during a second OD-SSB transmission from a neighbor cell (block 1230). One or more of the examples described herein can also, or alternatively be part of process 1200.

[0122] Fig. 13 is a diagram of an example process for RRM measurement control according to one or more implementations described herein. As shown, process 1300 can be implemented by base station 222. 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.

[0123] As shown, process 1300 can include determining measurement instructions relating to the a secondary cell (SCell) using a frequency carrier for a first on-demand system synchronization block (OD-SSB) transmission, the measurement instructions pertaining to the UE measuring a first OD-SSB transmission from the SCell or measuring a second OD-SSB transmission from a neighboring cell (block 1310). Process 1300 can include communicating the measurement instructions to a user equipment (UE) configured to use carrier aggregation to communicate with the base station and the SCell (block 1320). One or more of the examples described herein can also, or alternatively be part of process 1300.

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

[0125] In example 1, which can also include one or more of the examples described herein, 324923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1) baseband circuitry 904 and / or UE 210 can comprise: one or more processors configured to: receive and / or process measurement instructions relating to a secondary cell (SCell) using a frequency carrier for a first on-demand system synchronization block (OD-SSB) transmission; when the measurement instructions comprise an indication to skip measurement of the first OD- SSB transmission, forego measurement the first OD-SSB transmission of the frequency carrier; and when the measurement instructions comprise an indication to measure the first OD-SSB transmission, measure the frequency carrier during a second OD-SSB transmission from a neighbor cell.

[0126] In example 2, which can also include one or more of the examples described herein, the measurement instructions are configured for a radio resource management (RRM) measurement.

[0127] In example 3, which can also include one or more of the examples described herein, measuring the frequency carrier during the second OD-SSB transmission comprises performing a radio resource management (RRM) procedure.

[0128] In example 4, which can also include one or more of the examples described herein, the frequency carrier comprises a secondary component carrier (SCC) of a carrier aggregation scenario comprising a primary component carrier (PCC) of a primary cell (PCell) and the SCC of the SCell.

[0129] In example 5, which can also include one or more of the examples described herein, the one or more processors are configured to: measure the first OD-SSB transmission of the SCell, instead of processing the measurement instructions, when the SCell is configured for OD- SSB transmissions.

[0130] In example 6, which can also include one or more of the examples described herein, the one or more processors are configured to: measure an SSB transmission from the SCell, instead of processing the measurement instructions, when SSB transmissions from the SCell are always on.

[0131] In example 7, which can also include one or more of the examples described herein, the measurement instructions are received via at least one of: radio resource control (RRC) signaling from a primary cell (PCell), a media access control (MAC) control element (CE) from a primary cell (PCell), downlink control information (DCI) from a primary cell (PCell), or a combination thereof.

[0132] In example 8, which can also include one or more of the examples described herein, the one or more processors are configured to: activate and deactivate OD-SSB measurement based on at least one of: radio resource control (RRC) signaling from a primary cell (PCell), a media access control (MAC) control element (CE) from the primary cell (PCell), downlink334923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1) control information (DCI) from a primary cell (PCell), or a combination thereof.

[0133] In example 9, which can also include one or more of the examples described herein, the first OD-SSB transmission comprises an on-demand SSB based measurement timing configuration (OD-SMTC).

[0134] In example 10, which can also include one or more of the examples described herein, the first OD-SSB transmission occurs during an OD-SMTC window.

[0135] In example 11, which can also include one or more of the examples described herein, the second OD-SSB transmission is measured according to a periodicity, duration, and time offset of the OD-SMTC.

[0136] In example 12, which can also include one or more of the examples described herein, the one or more processors are configured to: activate and deactivate OD-SSB measurement for OD-SMTC based on at least one of radio resource control (RRC) signaling from a primary cell (PCell), a media access control (MAC) control element (CE) from the primary cell (PCell), downlink control information (DCI) from a primary cell (PCell), or a combination thereof.

[0137] In example 13, which can also include one or more of the examples described herein, the one or more processors are configured to: measure the frequency carrier for OD-SSB transmissions when OD-SMTC is activated; and forego measurement the frequency carrier for OD-SSB transmissions when OD-SMTC is deactivated.

[0138] In example 14, which can also include one or more of the examples described herein, the one or more processors are configured to: measure the frequency carrier for SSB transmissions according to an SMTC when OD-SSB is deactivated or OD-SMTC is deactivated.

[0139] In example 15, which can also include one or more of the examples described herein, the measurement instructions are determined implicitly based on a primary cell (PCell) explicitly signaling to enable or disable OD-SSB transmissions on the SCell or the neighbor cell.

[0140] In example 16, which can also include one or more of the examples described herein, the one or more processors are configured to: determine that the OD-SSB transmissions are enabled or disabled on the SCell or the neighbor cell based on at least one of: radio resource control (RRC) signaling from a primary cell (PCell), a media access control (MAC) control element (CE) from the primary cell (PCell), downlink control information (DCI) from a primary cell (PCell), or a combination thereof.

[0141] In example 17, which can also include one or more of the examples described herein, the one or more processors are configured to: enable and disable measurement of OD-SSB transmissions on the carrier frequency based on at least one of: the OD-SSB transmissions being enabled or disabled, the SCell being activated or deactivated, termination of a set of consecutive transmission bursts of the second OD-SSB transmission, or a combination thereof.344923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1)

[0142] In example 18, which can also include one or more of the examples described herein, the one or more processors are configured to: receive an indication of a plurality of OD-SSB transmission patterns, select an OD-SSB transmission pattern, of the plurality of OD-SSB transmission patterns, corresponding to the second OD-SSB transmission, and measure the second OD-SSB transmission according to the OD-SSB transmission pattern.

[0143] In example 19, which can also include one or more of the examples described herein, each OD-SSB transmission pattern of the plurality of OD-SSB transmission patterns comprises at least one of: an OD-SSB periodicity, OD-SSB duration, and OD-SSB time offset.

[0144] In example 20, which can also include one or more of the examples described herein, the one or more processors are configured to: receive an indication of a plurality of OD-SMTC patterns, select an OD-SMTC pattern, of the plurality of OD-SMTC patterns, corresponding to the second OD-SSB transmission, and measure the second OD-SSB transmission according to the OD-SMTC pattern.

[0145] In example 21, which can also include one or more of the examples described herein, each SMTC transmission pattern of the plurality of SMTC transmission patterns comprises at least one of: an SMTC periodicity, SMTC duration, and SMTC time offset.

[0146] In example 22, which can also include one or more of the examples described herein, a method, performed by baseband circuitry and / or UE 210 can comprise: receiving, from a primary cell (PCell), measurement instructions relating to a secondary cell (SCell) using a frequency carrier for a first on-demand system synchronization block (OD-SSB) transmission; when the measurement instructions comprise an indication to skip measurement of the first OD- SSB transmission, foregoing measurement the first OD-SSB transmission of the frequency carrier; and when the measurement instructions comprise an indication to measure the first OD- SSB transmission, measuring the frequency carrier during a second OD-SSB transmission from a neighbor cell.

[0147] In example 23, which can also include one or more of the examples described herein, a base station or another type of radio access point device can comprise: one or more processors configured to: determine measurement instructions relating to the a secondary cell (SCell) using a frequency carrier for a first on-demand system synchronization block (OD-SSB) transmission, the measurement instructions pertaining to the UE measuring a first OD-SSB transmission from the SCell or measuring a second OD-SSB transmission from a neighboring cell; and communicate the measurement instructions to a user equipment (UE) configured to use carrier aggregation to communicate with the base station and the SCell.

[0148] In example 24, which can also include one or more of the examples described herein, the one or more processors are configured to: receive, from the UE, user equipment (UE)354923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1) capability information comprising an indication of whether the UE is capable of OD-SSB transmission measurement.

[0149] In example 25, which can also include one or more of the examples described herein, the one or more processors are configured to: enable the UE to implement carrier aggregation comprising a primary component carrier (PCC) from the base station and a secondary component carrier (SCC) from a secondary cell (SCell).

[0150] In example 26, which can also include one or more of the examples described herein, measurement instructions are determined based on at least one of: whether the UE capability information indicates that the UE is capable of OD-SSB transmission measurement, whether the SCell is configured for always on SSB transmissions, whether always on SSB transmissions of the SCell are subject to a periodicity, whether the SCell is configured for OD-SSB transmissions, or whether the SCell is configured for on-demand SSB based measurement timing configuration (OD-SMTC).

[0151] In example 27, which can also include one or more of the examples described herein, the one or more processors are configured to: enable or disable OD-SSB transmissions on the SCell, enable or disable OD-SSB transmissions on the neighbor cell, enable or disable OD- SMTC on the SCell, enable or disable OD-SMTC on the neighbor cell, or a combination thereof.

[0152] In example 28, which can also include one or more of the examples described herein, one or more processors are configured to: communicate information to the UE regarding at least one of: whether OD-SSB transmissions are enabled or disabled on the SCell, whether OD-SSB transmissions are enabled or disabled on the neighbor cell, whether OD-SMTC is enabled or disabled on the SCell, whether OD-SMTC is enabled or disabled on the neighbor cell, or a combination thereof.

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

[0154] 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 364923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1) aspect described herein, but rather should be construed in breadth and scope in accordance with the appended claims below.

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

[0156] 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 and 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.

[0157] 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.374923-5609-8409, v. 2

Claims

Attorney Docket No.: 106842241540 (P69419WO1)CLAIMSWhat is claimed is:

1. Baseband circuitry, comprising: one or more processors configured to: process measurement instructions relating to a secondary cell (SCell) using a frequency carrier for a first on-demand system synchronization block (OD-SSB) transmission; when the measurement instructions comprise an indication to skip measurement of the first OD-SSB transmission, forego measurement the first OD-SSB transmission of the frequency carrier; and when the measurement instructions comprise an indication to measure the first OD-SSB transmission, measure the frequency carrier during a second OD-SSB transmission from a neighbor cell.

2. The baseband circuitry of claim 1, wherein the measurement instructions are configured for a radio resource management (RRM) measurement.

3. The baseband circuitry of claim 1, wherein measuring the frequency carrier during the second OD-SSB transmission comprises performing a radio resource management (RRM) procedure.

4. The baseband circuitry of claim 1, wherein the frequency carrier comprises a secondary component carrier (SCC) of a carrier aggregation scenario comprising a primary component carrier (PCC) of a primary cell (PCell) and the SCC of the SCell.

5. The baseband circuitry of claim 1, wherein the one or more processors are configured to: measure the first OD-SSB transmission of the SCell, instead of processing the measurement instructions, when the SCell is configured for OD-SSB transmissions.

6. The baseband circuitry of claim 1, wherein the one or more processors are configured to: measure an SSB transmission from the SCell, instead of processing the measurement instructions, when SSB transmissions from the SCell are always on.384923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1)7. The baseband circuitry of claim 1, wherein the measurement instructions are received via at least one of: radio resource control (RRC) signaling from a primary cell (PCell), a media access control (MAC) control element (CE) from a primary cell (PCell), downlink control information (DCI) from a primary cell (PCell), or a combination thereof.

8. The baseband circuitry of claim 1, wherein the one or more processors are configured to: activate and deactivate OD-SSB measurement based on at least one of: radio resource control (RRC) signaling from a primary cell (PCell), a media access control (MAC) control element (CE) from the primary cell (PCell), downlink control information (DCI) from a primary cell (PCell), or a combination thereof.

9. The baseband circuitry of claim 1, wherein the first OD-SSB transmission comprises an on- demand SSB based measurement timing configuration (OD-SMTC).

10. The baseband circuitry of claim 9, wherein the first OD-SSB transmission occurs during an OD-SMTC window.

11. The baseband circuitry of claim 9, wherein the second OD-SSB transmission is measured according to a periodicity, duration, and time offset of the OD-SMTC.

12. The baseband circuitry of claim 9, wherein the one or more processors are configured to: activate and deactivate OD-SSB measurement for OD-SMTC based on at least one of radio resource control (RRC) signaling from a primary cell (PCell), a media access control (MAC) control element (CE) from the primary cell (PCell), downlink control information (DCI) from a primary cell (PCell), or a combination thereof.

13. The baseband circuitry of claim 12, wherein the one or more processors are configured to: measure the frequency carrier for OD-SSB transmissions when OD-SMTC is activated; and forego measurement the frequency carrier for OD-SSB transmissions when OD-SMTC is deactivated.394923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1)14. The baseband circuitry of claim 13, wherein the one or more processors are configured to: measure the frequency carrier for SSB transmissions according to an SMTC when OD-SSB is deactivated or OD-SMTC is deactivated.

15. The baseband circuitry of claim 1, wherein the measurement instructions are determined implicitly based on a primary cell (PCell) explicitly signaling to enable or disable OD-SSB transmissions on the SCell or the neighbor cell.

16. The baseband circuitry of claim 1, wherein the one or more processors are configured to: determine that the OD-SSB transmissions are enabled or disabled on the SCell or the neighbor cell based on at least one of: radio resource control (RRC) signaling from a primary cell (PCell), a media access control (MAC) control element (CE) from the primary cell (PCell), downlink control information (DCI) from a primary cell (PCell), or a combination thereof.

17. The baseband circuitry of claim 1, wherein the one or more processors are configured to: enable and disable measurement of OD-SSB transmissions on the carrier frequency based on at least one of: the OD-SSB transmissions being enabled or disabled, the SCell being activated or deactivated, termination of a set of consecutive transmission bursts of the second OD-SSB transmission, or a combination thereof.

18. The baseband circuitry of claim 1, wherein the one or more processors are configured to: receive an indication of a plurality of OD-SSB transmission patterns, select an OD-SSB transmission pattern, of the plurality of OD-SSB transmission patterns, corresponding to the second OD-SSB transmission, and measure the second OD-SSB transmission according to the OD-SSB transmission pattern.

19. A method, comprising: receiving, from a primary cell (PCell), measurement instructions relating to a secondary cell (SCell) using a frequency carrier for a first on-demand system synchronization block (OD-SSB) transmission;404923-5609-8409, v. 2Attorney Docket No.: 106842241540 (P69419WO1) when the measurement instructions comprise an indication to skip measurement of the first OD-SSB transmission, foregoing measurement the first OD-SSB transmission of the frequency carrier; and when the measurement instructions comprise an indication to measure the first OD-SSB transmission, measuring the frequency carrier during a second OD-SSB transmission from a neighbor cell.

20. A base station, comprising: one or more processors configured to: determine measurement instructions relating to the a secondary cell (SCell) using a frequency carrier for a first on-demand system synchronization block (OD-SSB) transmission, the measurement instructions pertaining to the UE measuring a first OD-SSB transmission from the SCell or measuring a second OD-SSB transmission from a neighboring cell; and communicate the measurement instructions to a user equipment (UE) configured to use carrier aggregation to communicate with the base station and the SCell.414923-5609-8409, v. 2

Images