Systems, methods, and devices for managing measurement occasions and data traffic

Abstract

Described are solutions for managing measurement occasions and data traffic. Measurement occasions can be dynamically canceled under one or more conditions. Examples of such conditions can include a value, benefit, or need for the measurement occasion relative to a priority or throughput of data traffic that could otherwise be transmitted (Tx) or received (Rx) during the measurement occasion. Examples of conditions for canceling a measurement occasion can include a location with a cell, a reference signal received power (RSRP), a signal-to-noise ratio (SNR), a high mobility state or a low mobility state, and more. A measurement occasion can include a measurement gap or a scheduling restriction resulting in a pause or interruption of data traffic.

Description

Attorney Docket No.: 106842241440 (P69425WO1)SYSTEMS, METHODS, AND DEVICES FOR MANAGING MEASUREMENT OCCASIONS AND DATA TRAFFICCROSS-REFERENCE TO RELATED APPLICATIONS

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

[0002] This disclosure relates to wireless communication networks and mobile device capabilities.BACKGROUND

[0003] Wireless communication networks and wireless communication services are becoming increasingly dynamic, complex, and ubiquitous. For example, some wireless communication networks can be developed to implement fifth generation (5G) or new radio (NR) technology, sixth generation (6G) technology, and so on. Such technology can include solutions for enabling user equipment (UE) and network devices, such as base stations and satellites, to communicate with one another.BRIEF DESCRIPTION OF THE DRAWINGS

[0004] The present disclosure will be readily understood and enabled by the detailed description and accompanying figures of the drawings. Like reference numerals can designate like features and structural elements. Figures and corresponding descriptions are provided as non-limiting examples of aspects, implementations, etc., of the present disclosure, and references to "an" or “one” aspect, implementation, etc., may not necessarily refer to the same aspect, implementation, etc., and can mean at least one, one or more, etc.

[0005] Fig. l is a diagram of an example overview of one or more of the techniques described herein.

[0006] Fig. 2 is a diagram of an example network according to one or more implementations described herein.

[0007] Fig. 3 is a diagram of an example of a process for managing measurement occasions and data traffic according to one or more implementations described herein.

[0008] Fig. 4 is a diagram of an example of canceling a measurement occasion according to one or more implementations described herein.14917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1)

[0009] Fig. 5 is a diagram of an example of types of measurement occasions according to one or more implementations described herein.

[0010] Fig. 6 is a diagram of an example of a process for using conditions to manage measurement occasions and data traffic according to one or more implementations described herein.

[0011] Figs. 7-8 are diagrams of examples of UE capability information according to one or more implementations described herein.

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

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

[0014] Fig. 11 is a block diagram illustrating components, according to one or more implementations described herein, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.

[0015] Fig. 12 is a diagram of an example process for managing measurement occasions and data traffic according to one or more implementations described herein.

[0016] Fig. 13 is a diagram of an example process for managing measurement occasions and data traffic according to one or more implementations described herein.DETAILED DESCRIPTION

[0017] The following detailed description refers to the accompanying drawings. Like reference numbers in different drawings can identify the same or similar features, elements, operations, etc. Additionally, the present disclosure is not limited to the following description as other implementations can be utilized, and structural or logical changes made, without departing from the scope of the present disclosure.

[0018] Wireless communication networks can include user equipment (UE) capable of communicating with base stations and / or other network access devices. The base stations can provide a UE with access to a core network (CN) and additional external networks, such as the Internet. Wireless communication networks can implement various techniques and standards that enable wireless communications. An example of these techniques can include the UE measuring or determining the strength and quality of wireless signals between the UE and one or more base stations.24917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1)

[0019] A base station can allocate time and frequency resources to a UE. These resources can include uplink (UL) and downlink (DL) resources. The resources can include measurement gaps, during which the UE can measure or evaluate signals from one or more base stations. During the measurement gaps, the UE can temporarily pause the transmission (Tx) and reception (Rx) of data signaling. While pausing the Tx and Rx data can be helpful to ensure that signals are measured accurately, pausing the Tx and Rx of data can also amount to a disruption and overall decrease in data signaling and throughput between the UE and the serving cell (e.g., the base station to which the UE is connected). Additionally, an amount of transmission disruption caused by a measurement gap can be greater than the measurement gap itself, and the amount of transmission disruption can vary depending on a subcarrier spacing (SCS) being implemented whether 15 kilohertz (kHz), 30 kHz, 60 kHz, 120 kHz, and so on.

[0020] Currently available technologies can, therefore, can be deficient when too many or too few measurement gaps or other scheduling restrictions are proscribed. This can be particularly so for data traffic designed for higher throughputs, such as augmented reality (AR), extended reality (XR), virtual reality (VR), and more. High throughput data traffic can be referred to herein generally as XR. The scheduling or use of Tx and Rx data signaling can further be limited by other scheduling restrictions. Examples of additional scheduling restrictions can include procedures related to rando link management (RLM), beam failure detection (BFD), candidate beam detection (CBD), layer 1 (LI) measurement, inter- and intra-frequency measurements (without a measurement gap and with different (SCS), inter- and intra-frequency measurement with national chimney sweep guild (NCSG), and other types of radio resource management (RRM) procedures.

[0021] One or more of the techniques, described herein, include solutions to these deficiencies by dynamically adjusting the use of measurement gaps and / or scheduling restrictions according to one or more conditions. Examples of such conditions can include a throughput associated with data traffic between the UE and base station, a data traffic type, quality of service (QoS) or quality of experience (QoE) associated with data traffic, a current level or rate of mobility of the UE, a signal strength between the UE and a serving base station and / or one or more other base stations, whether a success or failure of a prior measurement procedure or RRM procedure, an amount of time since a prior measurement procedure or RRM procedure, a periodicity or other timing characteristic of measurement gaps or scheduling requestions, and more. As described herein, a measurement gap or scheduling restriction can be dynamically modified to enable data traffic Tx or Rx to occur34917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) during the measurement gap or scheduling restriction. This can include performing data traffic Tx or Rx instead of a measurement procedure or RRM procedure.

[0022] A measurement gap or scheduling restriction, and the use, modification, or nonuse of the a measurement gap or scheduling restriction, can be prioritized or deprioritized based on a benefit or preference for data traffic relative to a benefit or preference for the measurement gap or RRM procedure involving a scheduling restriction. The benefit or preference for prioritizing a measurement gap or scheduling restriction over data traffic throughput can be less when, for example, UE mobility is low and a signal strength of a serving cell is high. By contrast, the benefit or preference for prioritizing a measurement gap or scheduling restriction over data traffic throughput can be higher when, for example, UE mobility is high or a signal strength of a serving cell is low.

[0023] A measurement occasion, as referred to herein, can refer to a measurement gap, an interruption time associated with a measurement gap, a scheduling restriction, an interruption time associated with a scheduling restriction, or any combination thereof. A measurement gap can include a type-1 gap, a type-2 gap, a network controlled small gap (NCSG), a multi subscriber identity module (MUSIM) gap, a positioning gap, a concurrent gap, a pre-configured measurement gap, and so on, including any combination thereof. A type-1 gap can include a measurement gap configured by radio resource control (RRC) signaling using a GapConfig information element (IE) or parameter. A type-2 gap can include a measurement gap configured by RRC signaling using a GapConfig-rl7 IE or parameter.

[0024] A scheduling restriction can be a measurement, associated with an RRM procedure or another type of procedure, which can be scheduled during a measurement gap or outside (e.g., before or after) of a measurement gap. An example of a scheduling restriction can include a new radio (NR) system synchronization block (SSB) measurement timing configuration (SMTC) configured for RRM measurement outside of a measurement gap.Examples of a scheduling restriction can also, or alternatively, include an LI reference signal (RS) (e.g., an SSB and channel state information (CSI) RS (CSLRS) configured for a RLM measurement, BFD measurement, CBD measurement, and / or LI measurement resulting in a scheduling restriction.

[0025] 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 station 120. UE 110 and base station 120 can determine to cancel one or more measurement occasions (at 1.1). This can be based on one or more factors, conditions, or situations, such as a value or priority of using time domain resources to observe a measurement occasion (e.g.,44917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) to perform a measurement procedure) or to instead use the time domain resources to transmit and receive data traffic (e.g., XR, AR, VR, or another type of high throughput data traffic). Canceling a measurement occasion can, therefore, enable UE 110 and base station 120 to use allocate more resources to high-priority data traffic when measurement occasions are of lower value or benefit (e.g., when signal strength is high) (at 1.2). By contrast, when measurement occasions are of higher value or benefit (e.g., when UE 110 is in a high mobility state or signal strength is low), measurement occasions can go uncanceled to allow for any number of measurements or procedures involving a measurement gap, scheduling restriction, or combination thereof (at 1.3). Additional examples of these and many other techniques, features, and implementations are described below with reference to the figures that follow.

[0026] Fig. 2 is an example network 200 according to one or more implementations described herein. Example network 200 can include UEs 210-1, 210-2, etc. (referred to collectively as “UEs 210” and individually as “UE 210”), a radio access network (RAN) 220, a core network (CN) 230, application servers 240, external networks 250. The systems and devices of example network 200 can operate in accordance with one or more communication standards, such as 2nd generation (2G), 3rd generation (3G), 4th generation (4G) (e.g., longterm evolution (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 3GPP standards (e.g., sixth generation (6G) standards, seventh generation (7G) standards, etc.), institute of electrical and electronics engineers (IEEE) standards (e.g., wireless metropolitan area network (WMAN), and more.

[0027] As shown, UEs 210 can include smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more wireless communication networks). Additionally, or alternatively, UEs 210 can include other types of mobile or non-mobile computing devices capable of wireless communications, such as personal data assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, etc. In some implementations, UEs 210 can include internet of things (loT) devices (or loT UEs) that can comprise a network access layer designed for low-power loT applications utilizing shortlived UE connections. Additionally, or alternatively, an loT UE can utilize one or more types of technologies, such as machine-to-machine (M2M) communications or machine-type communications (MTC) (e.g., to exchanging data with an MTC server or other device via a54917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) public land mobile network (PLMN)), proximity-based service (ProSe) or device-to-device (D2D) communications, sensor networks, loT networks, and more. Depending on the scenario, an M2M or MTC exchange of data can be a machine-initiated exchange, and an 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.

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

[0029] UEs 210 can use one or more wireless channels 212 to communicate with one another. As described herein, UE 210 can communicate with RAN node 222 to request SL resources. RAN node 222 can respond to the request by providing UE 210 with a dynamic grant (DG) or configured grant (CG) regarding SL resources. A DG can include a grant based on a grant request from UE 210. A CG can involve a resource grant without a grant request and can be based on a type of service being provided (e.g., services that have strict timing or latency requirements). UE 210 can perform a clear channel assessment (CCA) procedure based on the DG or CG, select SL resources based on the CCA procedure and the DG or CG; and communicate with another UE 210 based on the SL resources. The UE 210 can communicate with RAN node 222 using a licensed frequency band and communicate with the other UE 210 using an unlicensed frequency band.

[0030] 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 be64917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) 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.

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

[0032] 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 702.11 protocol, and AP 216 can comprise a wireless fidelity (Wi-Fi®) router or other AP. While not explicitly depicted in Fig. 2, AP 216 can be connected to another network (e.g., the Internet) without connecting to RAN 220 or CN 230. In some scenarios, UE 210, RAN 220, and AP 216 can be configured to utilize LTE- WLAN aggregation (LWA) techniques or LTE WLAN radio level integration with IPsec tunnel (LWIP) techniques. LWA can involve UE 210 in RRC CONNECTED being configured by RAN 220 to utilize radio resources of LTE and WLAN. LWIP can involve UE 210 using WLAN radio resources (e.g., connection interface 218) via IPsec protocol tunneling to authenticate and encrypt packets (e.g., Internet Protocol (IP) packets) communicated via connection interface 218. IPsec tunneling can include encapsulating the entirety of original IP packets and adding a new packet header, thereby protecting the original header of the IP packets.74917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1)

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

[0034] Some or all of RAN nodes 222, or portions thereof, can be implemented as one or more software entities running on server computers as part of a virtual network, which can be referred to as a centralized RAN (CRAN) and / or a virtual baseband unit pool (vBBUP). In these implementations, the CRAN or vBBUP can implement a RAN function split, such as a packet data convergence protocol (PDCP) split wherein radio resource control (RRC) and PDCP layers can be operated by the CRAN / vBBUP and other Layer 2 (L2) protocol entities can be operated by individual RAN nodes 222; a media access control (MAC) / physical (PHY) layer split wherein RRC, PDCP, radio link control (RLC), and MAC layers can be operated by the CRAN / vBBUP and the PHY layer can be operated by individual RAN nodes 222; or a “lower PHY” split wherein RRC, PDCP, RLC, MAC layers and upper portions of the PHY layer can be operated by the CRAN / vBBUP and lower portions of the PHY layer can be operated by individual RAN nodes 222. This virtualized framework can allow freed- up processor cores of RAN nodes 222 to perform or execute other virtualized applications.

[0035] 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, or84917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) 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.

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

[0037] In some implementations, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 222 to UEs 210, and uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid (e.g., a resource grid or time-frequency resource grid) that represents the physical resource for downlink in each slot. Such a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit in a resource grid is denoted as a resource element. Each resource grid comprises resource blocks, which describe the mapping of certain physical channels to resource elements (REs). Each resource block can comprise a collection of resource elements; in the frequency domain, this can represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.

[0038] 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 “unlicensed94917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) 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.

[0039] A physical downlink shared channel 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.

[0040] One or more of the techniques described herein can include solution for managing measurement occasions and data traffic. Measurement occasions can be dynamically canceled under one or more conditions. Examples of such conditions can include a value, benefit, or need for the measurement occasion relative to a priority or throughput of data traffic that could otherwise be transmitted (Tx) or received (Rx) during the measurement occasion. Examples of conditions for canceling a measurement occasion can include a location with a cell, a reference signal received power (RSRP), a signal-to-noise ratio (SNR), a high mobility state or a low mobility state, and more. A measurement occasion can include a measurement gap or a scheduling restriction resulting in a pause or interruption of data traffic. Many other aspects and examples are also described herein.

[0041] The RAN nodes 222 can be configured to communicate with one another via interface 223. In implementations where the system is an LTE system, interface 223 can be an X2 interface. In NR systems, interface 223 can be an Xn interface. The X2 interface can be defined between two or more RAN nodes 222 (e.g., two or more eNBs / gNBs or a combination thereof) that connect to evolved packet core (EPC) or CN 230, or between two104917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) 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.

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

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

[0044] 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 network114917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) elements (e.g., virtual network functions (VNFs) offering applications that use IP bearer resources with CN 230 (e.g., universal mobile telecommunications system packet services (UMTS PS) domain, LTE PS data services, etc.). Application servers 240 can also, or alternatively, be configured to support one or more communication services (e.g., voice 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.

[0045] Fig. 3 is a diagram of an example of a process 300 for managing measurement occasions and data traffic according to one or more implementations described herein. As shown, process 300 can be implemented by UE 210 and base station 222. In some implementations, some or all of process 300 can be performed by one or more other systems or devices, including one or more of the devices of Fig. 2. Additionally, process 300 can include one or more fewer, additional, differently ordered and / or arranged operations than those shown in Fig. 3. In some implementations, some or all of the operations of process 300 can be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 300. As such, the techniques described herein are not limited to the number, sequence, arrangement, timing, etc., of the operations or processes depicted in Fig. 3.

[0046] One or more of the operations of process 300 can involve cancelable and / or non- cancelable measurement occasions. Such operations can involve only cancelable measurement occasions, only non-cancelable measurement occasions, or both cancelable and non-cancelable measurement occasions. For example, block 320 can include UE 210 determining only cancelable measurement, determining only non-cancelable measurement occasions, or determining both cancelable measurement occasions. As another example, block 330 can include UE 210 sending only cancelable measurement, sending only non- cancelable measurement occasions, or sending both cancelable measurement occasions.

[0047] Other blocks or operations can be similar. Furthermore, the possible variation can be dynamically implemented based on one or more configurations, factors, conditions, modes of operation, or circumstances. As such, references to operations, information, and functional relating to cancelable measurement occasions can be applied to non-cancelable measurement occasions, or both cancelable measurement occasions and non-cancelable measurement occasions. Similarly, references to operations, information, conditions, and functional relating124917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) to non-cancelable measurement occasions can be applied to cancelable measurement occasions, or both non-cancelable measurement occasions and cancelable measurement occasions.

[0048] As shown, process 300 can include base station communicating configuration information to UE 210 (block 310). The configuration information can include measurement occasions and other timing or scheduling information. A measurement occasion can be a measurement gap, an interruption time associated with a measurement gap, a scheduling restriction, an interruption time associated with a scheduling restriction, or any combination thereof. A measurement gap can include a type-1 gap, type-2 gap, NCSG, MUSIM gap, positioning gap, concurrent gap, pre-configured measurement gap, and so on. A scheduling restriction can be a measurement, associated with an RRM procedure or another type of procedure, which can be scheduled during a measurement gap or outside (e.g., before or after) of a measurement gap.

[0049] An interruption time associated with a measurement gap can include the measurement gap in addition to time preceding or following the measurement gap, during which Rx and Tx traffic communications are limited or prevented as a result of the measurement gap. This can include time associated with transitioning into or out of a measurement mode of operation and an Rx and Tx traffic communications mode of operation. An interruption time associated with a scheduling restriction may include the measurement restriction in addition to time preceding or following the scheduling restriction, during which Rx and Tx traffic communications are limited or prevented as a result of the scheduling restriction. This can include time associated with transitioning into or out of a mode of operation associated with the scheduling restriction and an Rx and Tx traffic communications mode of operation. A measurement occasion can include or involve any procedure that involves a pause or interruption in the transmission or reception of data traffic because of the nature of the procedure. The procedure can include one or more measurement procedures and / or other types of procedures including procedures that do not involve measurements.

[0050] Process 300 can include UE 210 determining one or more measurement occasions that can be canceled and / or measurement occasions that cannot be canceled (block 320). A cancelable measurement occasion can include a measurement occasion that can be skipped or canceled due to one or more factors, conditions, or circumstances. A non-cancelable measurement occasion can include a measurement occasion that is not to be skipped or canceled due to one or more factors, conditions, or circumstances. In some implementations,134917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1)UE 210 can determine measurement occasions that are not to be canceled, in which case other measurement occasions are assumed to be canceled or cancelable. In some implementations, UE 210 can determine measurement occasions that can be canceled or that are to be canceled, in which case other measurement occasions are assumed to be not canceled or non-cancelable measurement occasions. In some implementations, UE 210 can determine whether each measurement occasion is cancelable or non-cancelable. The measurement occasions considered can be those of a certain type, of a certain group, within specified time domain range, those associated with a measurement gap, those associated with a scheduling restriction, those associated with one or more specified procedures, those according to a specified priority up to a threshold number, and more, including any combination thereof.

[0051] Time and frequency resources can be used for UL and / or DL communications during a canceled measurement occasion. UE 210 can determine that a measurement occasion can be canceled based on one or more conditions on circumstances, such as signal quality and / or strength, a location of UE 210 with reference to base station 222 (e.g., at a cell edge where mobility performance is low), whether UE 210 is in a high mobility state (e.g., on a high speed train), whether the UE 210 is in a low mobility state (e.g., is geographically stationary), and / or one or more additional or alternative conditions or situations.

[0052] UE 210 can determine whether a next measurement occasion is cancelable and / or whether one or more measurement occasions can be canceled over a period of time or within a duration of time. The cancelable occasions can be the same type of measurement occasions or different types of measurement occasions. In some implementations, UE 210 can perform several operations, each associated with a particular type of measurement occasion, for determining measurement occasions that are cancelable over a period of time.

[0053] Process 300 can include UE 210 can communicate one or more cancelable and / or non-cancelable measurement occasions to base station 222 (block 330). UE 210 can indicate one or more measurement occasions that can be skipped or canceled or that cannot be skipped or canceled. UE 210 may indication the cancelable measurement occasions using UE assistance information (UAI), UL control information (UCI), or a MAC control element (CE) (MAC-CE). The indicated measurement occasions can be associated by XR traffic or another type of traffic. The measurement occasions can be indicated using a one or more parameters or information elements, such as a MeasCancel Assistinfo parameter or information element (IE). For example, MeasCancelAssistlnfo can indicate that a number of measurement occasions (indicated by numofCancelableOccasion) are cancelable.144917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1)

[0054] A numofCancelableOccasion paremter or information element can be a fixed value hard coded or specified by a communication standard (e.g., measurement occasion 1, measurement occasion 2, etc.) or a dynamic value from a pre-defined super set specified by a communication standard (e.g., super set 1, super set 2., etc.), where the value of numofCancelableOccasion can change each time. In some implementations, numofCancelableOccasion can be a Boolean value (e.g., yes or no, true or false, etc.) such that base station 222 may not trigger measurement occasion cancelation until a yes or true value is received. A fixed, hard coded, or specified number of cancelable or non-cancelable measurement occasions can include a number of cancelable or non-cancelable measurements specified by a communication standard (e.g., a non-dynamic number of cancelable or non- cancelable measurements). A super set of cancelable or non-cancelable measurement occasions can include integer values starting from one and proceeding according to a designated sequence (e.g., 1, 2, 3, ... ).

[0055] Different combinations of IES, CEs, and / or parameters can be used for different types of traffic and / or measurement occasions. For example, UE 210 can use a MeasCancelAssistlnfoGap IE can a numofCancelableOccasionsGap parameter for measurement gaps; a MeasCancelAssistlnfoSMTC and numofCancelableOccasionsSMTC parameter for SMTC outside measurement gaps; a MeasCancelAssistlnfoRLM IE and numofCancelableOccasionsRLM parameters for RLM operations; a MeasCancelAssistlnfoBFD IE and numofCancelableOccasionsBFD parameter for BFD operations; a MeasCancelAssistlnfoLl IE and numofCancelableOccasionsLl for LI operations; and so on.

[0056] In some implementations, base station 222 can have a better understanding of where a handover zone or area within a cell is located (e.g., near a cell edge) In such scenarios, UE 210 can be configured to not prioritize XR traffic over RRM measurements or measurement occasions. Base station 222 can provide configuration information to UE 210 to monitor for such locations and indicate to base station 222 when UE 210 is located in such areas. For example, UE 210 can constantly monitor for conditions consistent with a handover zone (e.g., a location where a handover procedure is likely) and indicate to base station 222 when the conditions are satisfied. Examples of such conditions can include a measured signal strength with respect to a signal strength threshold (e.g., a reference signal received power (RSRP) below a decibel threshold (e.g., 90 dBm) or a distance between UE 210 to base station 222 (e.g., a positioning measurement such as an Rx-Tx measurement).

[0057] Process 300 can include base station determining whether one or more154917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) measurement occasions are to be canceled and / or one or more measurement occasions that are not to be canceled (block 340). For example, base station 222 can determine whether one or more measurement occasions are to be canceled (or not canceled) based on the cancelable measurement occasions indicated by UE 210. In some implementations, upon receiving an indication of one or more measurement occasions that can be canceled, base station 222 may, or may not, trigger cancelation of a measurement occasion. Base station 222 can determine which of the cancelable measurement occasions are to be canceled, can generate information indicating the measurement occasions to be canceled. Base station 222 can determine that all or some of the cancelable measurement occasions are to be canceled. In some implementations, base station 222 can selectively cancel measurement occasions based on one or more factors or conditions, including a type of measurement occasions and / or a purpose or degree of importance associated with the measurement occasion. For example, when a measurement gap based hand over is only for load balancing purposes, base station 222 can determine to cancel the measurement gap when the serving cell is not under a full load.

[0058] Process 300 can include base station 222 send information to UE 210, indicating one or more measurement occasions that can be canceled and / or not canceled (block 350). In some implementations, UE 210 can implement the cancelation by engaging in Tx and Rx data traffic communications. Base station 222 can send the information to UE 210 via downlink control information (DCI) or another type of information (e.g. radio resource control (RRC) information, RRM information, etc.). Base station 222 can also, or alternatively, send UE 210 information to allocate time and frequency resources for Tx and Rx communications during the canceled measurement occasion(s). In some implementations, UE 210 can ignore or not respond to the cancelation (e.g., not conduct data Rx / Tx during a canceled measurement occasion. In some implementations, UE 210 can be configured to always respond to the cancelation by performing Tx and Rx data traffic communications during a canceled measurement occasion. Additionally, or alternatively, base station 222 can determine whether and how often to perform measurement occasion cancelation. Process 300 can include UE 210 and base station 222 engaging in Tx and Rx data traffic communications during canceled measurement occasions (block 360). Process 300 can include UE 210 and / or base station 222 engaging in measurement procedures according to measurement occasions that have not been canceled (block 370).

[0059] Fig. 4 is a diagram of an example 400 of canceling a measurement occasion according to one or more implementations described herein. Example 400 can include a164917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) series of measurement occasions scheduled along a time domain (at 4.1). The measurement occasions can be spaced apart from one another by time domain resources allocated to Tx and Rx data traffic (e.g., XR traffic, AR traffic, or another type of high-volume data traffic). As described herein, UE 210 and / or bases station 222 can determine whether to skip or cancel one or more measurement occasions based on one or more factors or conditions, such as a location of UE 210 within a cell, a strength of a signal between UE 210 and base station 222, a mobility state of UE 210, and more. Based on the conditions, UE 210 and / or base station 222 can determine to skip or cancel one or more measurement occasions (at 4.2). Time domain resources corresponding to the canceled measurement occasions can be reallocated to Tx and Rx data traffic (at 4.3). Doing so can increase an overall throughput, QoS, QoE, etc., associated with a service or application associated with the data traffic.

[0060] Fig. 5 is a diagram of an example 500 of types of measurement occasions 510 according to one or more implementations described herein. Measurement occasion 510 can be one or more of measurement gap 520, RRM measurement 530, or LI measurement operation 540. LI measurement operation 540 can be one or more of REM operation 542, BFD operation 544, CBD operation 546, LI measurement 548, and / or any combination thereof. LI measurement 548 can include one or more Ll-RSRP and Ll-SINR measurements. Additionally, or alternatively, measurement occasions 510 can include time resources preceding or following a measurement gap or a scheduling restriction, in addition to or instead of the measurement gap or the scheduling restriction.

[0061] A measurement gap can include a type-1 gap, a type-2 gap, a NCSG, a MUSIM gap, a positioning gap, a concurrent gap, a pre-configured measurement gap, and so on, including any combination thereof. A scheduling restriction can be a measurement, associated with an RRM procedure or another type of procedure, which can be scheduled during a measurement gap or outside (e.g., before or after) of a measurement gap. An example of a scheduling restriction can include a NR SMTC configured for RRM measurement outside of a measurement gap. Examples of a scheduling restriction can also, or alternatively, include an LI RS (e.g., an SSB and CSLRS) configured for a RLM measurement, BFD measurement, CBD measurement, and / or LI measurement resulting in a scheduling restriction.

[0062] In some implementations, measurement occasions 510 can include multiple measurement gaps, which can be spaced apart along a time domain, occur consecutively along a time domain, overlap with one another along a time domain, occur concurrently along a time domain, or any combination thereof. Measurement occasion 510 can therefore include174917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) one or more of a variety of types of information, measurements, and operations. One or more of the implementations, described herein, can involve the collection, evaluation, and / or communication of information relating to any of measurement occasions 510.

[0063] Fig. 6 is a diagram of an example of a process 600 for using conditions to manage measurement occasions and data traffic according to one or more implementations described herein. As shown, process 600 can be implemented by UE 210 and base station 222. In some implementations, some or all of process 600 can be performed by one or more other systems or devices, including one or more of the devices of Fig. 2. Additionally, process 600 can include one or more fewer, additional, differently ordered and / or arranged operations than those shown in Fig. 6. In some implementations, some or all of the operations of process 600 can be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 600. As such, the techniques described herein are not limited to the number, sequence, arrangement, timing, etc., of the operations or processes depicted in Fig. 6.

[0064] One or more of the operations of process 600 can involve cancelable and / or non- cancelable measurement occasions. Such operations can involve only cancelable measurement occasions, only non-cancelable measurement occasions, or both cancelable and non-cancelable measurement occasions. For example, block 620 can include UE 210 determining only cancelable measurement, determining only non-cancelable measurement occasions, or determining both cancelable measurement occasions. As another example, block 630 can include UE 210 sending only cancelable measurement, sending only non- cancelable measurement occasions, or sending both cancelable measurement occasions.

[0065] Other blocks or operations can be similar. Furthermore, the possible variation can be dynamically implemented based on one or more configurations, factors, conditions, modes of operation, or circumstances. As such, references to operations, information, and functional relating to cancelable measurement occasions can be applied to non-cancelable measurement occasions, or both cancelable measurement occasions and non-cancelable measurement occasions. Similarly, references to operations, information, conditions, and functional relating to non-cancelable measurement occasions can be applied to cancelable measurement occasions, or both non-cancelable measurement occasions and cancelable measurement occasions.

[0066] As shown, process 600 can include UE 210 communicating UE capability information to base station 222 (block 605). UE 210 can determine whether UE 210 is capable of canceling or skipping one or more measurement occasions. UE 210 can generate184917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1)UE capability information that includes an indication of whether UE 210 is capable of canceling or skipping one or more measurement occasions. UE 210 can communicate the UE capability information to base station 222 as UE assistance information or another type of information. The UE capability information can indicate one or more conditions under which a measurement occasion can be canceled, one or more types of measurement occasions that can be canceled, and more. Examples of UE capability information are provided below in the examples that follow.

[0067] Process 600 can include base station communicating configuration information to UE 210 (block 610). The configuration information can include measurement occasions and other timing or scheduling information. In some implementations, the configuration information can be used by UE 210 to determine measurement occasions and other timing or scheduling information. A measurement occasion can be a measurement gap, an interruption time associated with a measurement gap, a scheduling restriction, an interruption time associated with a scheduling restriction, or any combination thereof. A measurement gap can include a type-1 gap, type-2 gap, NCSG, MUSIM gap, positioning gap, concurrent gap, preconfigured measurement gap, and so on. A scheduling restriction can be a measurement, associated with an RRM procedure or another type of procedure, which can be scheduled during a measurement gap or outside (e.g., before or after) of a measurement gap. The configuration information can include factors, conditions, or scenarios for determining whether to cancel one or more measurement occasions.

[0068] Process 600 can include UE 210 monitoring measurement occasion conditions (block 614) and determining one or more conditions are satisfied (block 618) and determining one or more measurement occasions that can be canceled and / or that cannot be canceled (block 620). A cancelable measurement occasion can include a measurement occasion that can be skipped or canceled due to one or more factors, conditions, or circumstances. A non-cancelable measurement occasion can include a measurement occasion that is not to be skipped or canceled due to one or more factors, conditions, or circumstances. In some implementations, UE 210 can determine measurement occasions that are not to be canceled, in which case other measurement occasions are assumed to be canceled or cancelable.

[0069] In some implementations, UE 210 can determine measurement occasions that can be canceled or that are to be canceled, in which case other measurement occasions are assumed to be not canceled or non-cancelable measurement occasions. In some implementations, UE 210 can determine whether each measurement occasion is cancelable or194917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) non-cancelable. The measurement occasions considered can be those of a certain type, of a certain group, within specified time domain range, those associated with a measurement gap, those associated with a scheduling restriction, those associated with one or more specified procedures, those according to a specified priority up to a threshold number, and more, including any combination thereof.

[0070] Time and frequency resources can be used for UL and / or DL communications during a canceled measurement occasion. UE 210 can determine that a measurement occasion can be canceled or not canceled based on one or more conditions on circumstances, such as signal quality and / or strength, signal -to-noise ratio (SNR), a location of UE 210 with reference to base station 222 (e.g., at a cell edge where mobility performance is low), a distance between UE 210 and base station 222, whether UE 210 is in a high mobility state (e.g., on a high speed train), whether the UE 210 is in a low mobility state (e.g., is geographically stationary), and / or one or more additional or alternative conditions or situations.

[0071] UE 210 can determine whether a next measurement occasion is cancelable or non- cancelable, and / or whether one or more measurement occasions can be canceled or not canceled over a period of time or within a duration of time. The cancelable or non-cancelable occasions can be the same type of measurement occasions or different types of measurement occasions. In some implementations, UE 210 can perform several operations, each associated with a particular type of measurement occasion, for determining measurement occasions that are cancelable over a period of time. In some implementations, UE 210 can determine to cancel one or more measurement occasions instead of (or in addition to) determining that one or more measurement occasions are cancelable. In such implementations, UE 210 can information base station 222 which measurement occasions are canceled and Tx and Rx data traffic communications can be communicated during the canceled measurement occasions.

[0072] Process 600 can include UE 210 can communicate one or more cancelable and / or non-cancelable measurement occasions to base station 222 (block 630). UE 210 can indicate one or more measurement occasions that can be skipped or canceled. UE 210 may indication the cancelable measurement occasions using UE assistance information (UAI), UL control information (UCI), or a MAC control element (CE) (MAC-CE). The indicated measurement occasions can be associated by XR traffic or another type of traffic. The measurement occasions can be indicated using a one or more parameters or information elements, such as a MeasCancelAssistlnfo parameter or information element (IE). For example, MeasCancelAssistlnfo can indicate that a number of measurement occasions (indicated by204917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) numofCancelableOccasion) are cancelable.

[0073] A numofCancelableOccasion paremter or information element can be a fixed value hard coded or specified by a communication standard (e.g., measurement occasion 1, measurement occasion 2, etc.) or a dynamic value from a pre-defined super set specified by a communication standard (e.g., super set 1, super set 2., etc.), where the value of numofCancelableOccasion can change each time. In some implementations, numofCancelableOccasion can be a Boolean value (e.g., yes or no, true or false, etc.) such that base station 222 may not trigger measurement occasion cancelation until a yes or true value is received.

[0074] Different combinations of IES, CEs, and / or parameters can be used for different types of traffic and / or measurement occasions. For example, UE 210 can use a MeasCancelAssistlnfoGap IE can a numofCancelableOccasionsGap parameter for measurement gaps; a MeasCancelAssistlnfoSMTC and numofCancelableOccasionsSMTC parameter for SMTC outside measurement gaps; a MeasCancelAssistlnfoRLM IE and numofCancelableOccasionsRLM parameters for RLM operations; a MeasCancelAssistlnfoBFD IE and numofCancelableOccasionsBFD parameter for BFD operations; a MeasCancelAssistlnfoLl IE and numofCancelableOccasionsLl for LI operations; and so on.

[0075] In some implementations, base station 222 can have a better understanding of where a handover zone or area within a cell is located (e.g., near a cell edge) In such scenarios, UE 210 can be configured to not prioritize XR traffic over RRM measurements or measurement occasions. Base station 222 can provide configuration information to UE 210 to monitor for such locations and indicate to base station 222 when UE 210 is located in such areas. For example, UE 210 can constantly monitor for conditions consistent with a handover zone (e.g., a location where a handover procedure is likely) and indicate to base station 222 when the conditions are satisfied. Examples of such conditions can include a measured signal strength with respect to a signal strength threshold (e.g., a reference signal received power (RSRP) below a decibel threshold (e.g., 90 dBm) or a distance between UE 210 to base station 222 (e.g., a positioning measurement such as an Rx-Tx measurement).

[0076] Process 600 can include base station determining whether one or more measurement occasions are to be canceled and / or one or more measurement occasions that are not to be canceled (block 640). For example, base station 222 can determine whether one or more measurement occasions are to be canceled (or not canceled) based on the cancelable measurement occasions indicated by UE 210. In some implementations, upon receiving an214917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) indication of one or more measurement occasions that can be canceled, base station 222 may, or may not, trigger cancelation of a measurement occasion. Base station 222 can determine which of the cancelable measurement occasions are to be canceled, can generate information indicating the measurement occasions to be canceled. Base station 222 can determine that all or some of the cancelable measurement occasions are to be canceled. In some implementations, base station 222 can selectively cancel measurement occasions based on one or more factors or conditions, including a type of measurement occasions and / or a purpose or degree of importance associated with the measurement occasion. For example, when a measurement gap based hand over is only for load balancing purposes, base station 222 can determine to cancel the measurement gap when the serving cell is not under a full load.

[0077] Process 600 can include base station 222 send information to UE 210, indicating one or more measurement occasions that can be canceled and / or not canceled (block 650). In some implementations, UE 210 can implement the cancelation by engaging in Tx and Rx data traffic communications. Base station 222 can send the information to UE 210 via downlink control information (DCI) or another type of information (e.g. radio resource control (RRC) information, RRM information, etc.). Base station 222 can also, or alternatively, send UE 210 information to allocate time and frequency resources for Tx and Rx communications during the canceled measurement occasion(s). In some implementations, UE 210 can ignore or not respond to the cancelation (e.g., not conduct data Rx / Tx during a canceled measurement occasion. In some implementations, UE 210 can be configured to always respond to the cancelation by performing Tx and Rx data traffic communications during a canceled measurement occasion. Additionally, or alternatively, base station 222 can determine whether and how often to perform measurement occasion cancelation. Process 600 can include UE 210 and base station 222 engaging in Tx and Rx data traffic communications during canceled measurement occasions (block 660). Process 600 can include UE 210 and / or base station 222 engaging in measurement procedures according to measurement occasions that have not been canceled (block 670). A measurement procedure can relate to or otherwise include a procedure that involves a measurement occasion (e.g., a pause or in a pause or interruption of data traffic).

[0078] Figs. 7-8 are diagrams of examples 700 and 800 of UE capability information according to one or more implementations described herein. UE 210 can provide the UE capability information of one or more of examples 700 and 800 to indicate an ability of UE 210 to cancel measurement occasions and / or a number, type, etc., of measurement occasions224917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) that are cancelable. The information of examples 700 and 800 can be communicated by UE 210 to base station 222 as UE assistance information.

[0079] As shown, examples 700 and 800 each include a table with a definition of parameters column, a per column, an M column, a frequency division duplex (FDD) and time division duplex (TDD) difference (FDD-TDD DIFF) column, and a frequency resource 1 (FR1) and frequency resource 2 (FR2) different (FR1-FR2 DIFF) column. The definition of parameters column can include a definition of one or more parameters. The per column can indicate whether a parameter can be implemented on a per-UE and / or a per-FR basis. The M column can indicate whether the capability is mandatorily supported by UE 210. The FDD- TDD DIF column can indicate whether the capability can be supported differentially between FDD and TDD. The FR1-FR2 DIFF column can indicate whether the capability can be supported differentially between FR1 and FR2.

[0080] Referring to example 700, UE capability information can include one or more parameters relating to assistance information (info) for measurement occasion cancelation. The parameter(s) can indicate support for providing UE assistance information regarding cancelable measurement occasions. The parameters can include a MeasCancelAssistlnfo parameter that can indicate, for example, whether UE 210 is capable of canceling measurement occasions. The parameters can also, or alternatively, include a numofCancelableOccasions parameter that can indicate, for example, whether UE 210 is capable of canceling measurement occasions for a particular FR (e.g., FR1, FR2, etc.).

[0081] Referring to example 800, UE capability information can include one or more parameters relating to assistance information (info) for measurement cancelation. The parameter(s) can indicate support for providing UE assistance information regarding the cancelation of measurement gaps, SMTC measurement occasions, RLM measurement occasions, and more. The parameters can include a MeasCancelAssistlnfoGap parameter that can indicate, for example, for example, whether UE 210 is capable canceling measurement gaps and / or a numofCancelableOccasionsGap parameter that can indicate, for example, for example, a number of measurement gaps or occasion to be canceled.

[0082] The parameters can include a MeasCancelAssistlnfoSMTC parameter that can indicate, for example, for example, whether UE 210 is capable canceling measurement occasions associated with SMTC and / or a numofCancelableOccasionsSMTC parameter that can indicate, for example, a number of measurement occasions associated with SMTC to be canceled. The parameters can include a MeasCancelAssistlnfoRLM parameter that can indicate, for example, whether UE 210 is capable canceling measurement occasions234917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) associated with RLM and / or a numofCancelableOccasionsRLM parameter that can indicate, for example, a number of measurement occasions associated with RLM to be canceled. The foregoing parameters can have different, additional, or less information than the examples provided above.

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

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

[0085] Baseband circuitry 904 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. Baseband circuitry 904 can include one or more baseband processors or control logic to process baseband signals received from a receive signal path of RF circuitry 906 and to generate baseband signals for a transmit signal path of RF circuitry 906. Baseband circuity 904 can interface with application circuitry 902 for generation and processing of the baseband signals and for controlling operations of RF circuitry 906. For example, in some implementations, baseband circuitry 904 can include a 3G baseband processor 904A, a 4G baseband processor 904B, a 5G baseband processor 904C, or other baseband processor(s) 904D for other existing generations, generations in244917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) development or to be developed in the future (e.g., 5G, 6G, 7G, etc.). Baseband circuitry 904 (e.g., one or more of baseband processors 904 A-D) can handle various radio control 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 904 A-D can be included in modules stored in memory 904G and executed via a central processing unit (CPU) 904E. The radio control functions can include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some implementations, modulation / demodulation circuitry of baseband circuitry 904 can include Fast-Fourier Transform (FFT), precoding, or constellation mapping / de-mapping functionality. In some implementations, encoding / decoding circuitry of baseband circuitry 904 can include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functionality. Implementations of modulation / demodulation and encoder / decoder functionality are not limited to these examples and can include other suitable functionality in other implementations.

[0086] In some implementations, memory 904G can receive and / or store information and instructions for managing measurement occasions and data traffic. Measurement occasions can be dynamically canceled under one or more conditions. Examples of such conditions can include a value, benefit, or need for the measurement occasion relative to a priority or throughput of data traffic that could otherwise be transmitted (Tx) or received (Rx) during the measurement occasion. Examples of conditions for canceling a measurement occasion can include a location with a cell, a reference signal received power (RSRP), a signal -to-noise ratio (SNR), a high mobility state or a low mobility state, and more. A measurement occasion can include a measurement gap or a scheduling restriction resulting in a pause or interruption of data traffic. These and many other features and examples are described herein.

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

[0088] In some implementations, baseband circuitry 904 can provide for communication compatible with one or more radio technologies. For example, in some implementations,254917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) 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.

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

[0090] In some implementations, the receive signal path of RF circuitry 906 can include mixer circuitry 906A, amplifier circuitry 906B and filter circuitry 906C. In some implementations, the transmit signal path of RF circuitry 906 can include filter circuitry 906C and mixer circuitry 906 A. RF circuitry 906 can also include synthesizer circuitry 906D for synthesizing a frequency for use by mixer circuitry 906A of the receive signal path and the transmit signal path. In some implementations, mixer circuitry 906A of the receive signal path can be configured to down-convert RF signals received from FEM circuitry 908 based on the synthesized frequency provided by synthesizer circuitry 906D. Amplifier circuitry 906B can be configured to amplify the down-converted signals and filter circuitry 906C can be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals can be provided to baseband circuitry 904 for further processing. In some implementations, the output baseband signals can be zero-frequency baseband signals, although this may not be a requirement. In some implementations, mixer circuitry 906A of the receive signal path can comprise passive mixers, although the scope of the implementations is not limited in this respect.

[0091] 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. The264917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) 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 down conversion and up conversion, respectively. In some implementations, mixer circuitry 906A of the receive signal path and mixer circuitry 906A of the transmit signal path can include two or more mixers and can be arranged for image rejection. In some implementations, mixer circuitry 906 A of the receive signal path and mixer circuitry 906A can be arranged for direct down conversion and direct up conversion, respectively. In some implementations, mixer circuitry 906 of the receive signal path and mixer circuitry 906A of the transmit signal path can be configured for super-heterodyne operation.

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

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

[0094] 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.274917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1)

[0095] 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 phase detector, a charge pump and a D-type flip-flop. In these implementations, the delay elements can be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

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

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

[0098] 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.,284917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) 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).

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

[0100] While Fig. 9 shows PMC 912 coupled only with baseband circuitry 904.However, in other implementations, PMC 912 can be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 902, RF circuitry 906, or FEM circuitry 908.

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

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

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

[0104] 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 data294917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1)(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.

[0105] Fig. 10 is a diagram of example interfaces 1000 of baseband circuitry according to one or more implementations described herein. One or more components or features of example interfaces 1000 can correspond to one or more components or features described above or elsewhere. Baseband circuitry 1004 can comprise processors 1004A, 1004B, 1004C, 1004D, and 1004E and a memory 1004G utilized by said processors. Each of processors 1004 A, 1004B, 1004C, 1004D, and 1004E can include a memory interface, 1006 A, 1006B, 1006C, 1006D, and 1006E, respectively, to send / receive data to / from memory 1004G. Baseband circuitry can be a component of a UE and / or another type of device or system capable of transmitting and / or receiving wireless signals.

[0106] Baseband circuitry 1004 can further include one or more interfaces to communicatively couple to other circuitries / devices, such as memory interface 1012 (e.g., an interface to send / receive data to / from memory external to baseband circuitry 1004), an application circuitry interface 1014 (e.g., an interface to send / receive data to / from the application circuitry as described herein), an RF circuitry interface 1016, a wireless hardware connectivity interface 1018 (e.g., an interface to send / receive data to / from near field communication components, Bluetooth® components (e.g., Bluetooth® Low Energy), WiFi® components, and other communication components), and a power management interface 1020 (e.g., an interface to send / receive power or control signals to / from a PMC).

[0107] 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 interact304917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) with hypervisor 1102. For example, hypervisor 1102 can schedule or otherwise manage hardware resource 1100.

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

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

[0110] In some implementations, memory / storage devices 1120 receive and / or store information and instructions 1155 for managing measurement occasions and data traffic. Measurement occasions can be dynamically canceled under one or more conditions. Examples of such conditions can include a value, benefit, or need for the measurement occasion relative to a priority or throughput of data traffic that could otherwise be transmitted (Tx) or received (Rx) during the measurement occasion. Examples of conditions for canceling a measurement occasion can include a location with a cell, a reference signal received power (RSRP), a signal-to-noise ratio (SNR), a high mobility state or a low mobility state, and more. A measurement occasion can include a measurement gap or a scheduling restriction resulting in a pause or interruption of data traffic. These and many other features and examples are described herein.[OHl] 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.

[0112] 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 any314917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) 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.

[0113] Fig. 12 is a diagram of an example process 1200 for real-time precise ionosphere corrections according to one or more implementations described herein. As shown, process 1200 can be implemented by I&D server 280. 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.

[0114] As shown, process 1200 can include communicating an indication of the at least one measurement occasion being cancelable (block 1210). Process 1200 can include receiving information indicating that the at least one measurement occasion is canceled (block 1220). Process 1200 can include communicating transmitted (Tx) or received (Rx) data traffic during a time domain of the at least one measurement occasion (block 1230). One or more of the examples described herein can also, or alternatively be part of process 1200.

[0115] Fig. 13 is a diagram of an example process 1300 for real-time precise ionosphere corrections according to one or more implementations described herein. As shown, process 1300 can be implemented by I&D server 280. 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.

[0116] As shown, process 1300 can include communicating, to a user equipment (UE), at324917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) least one condition for canceling at least one measurement occasion (block 1310). Process 1300 can include receiving, from the UE, an indication of the at least one measurement occasion being cancelable (block 1320). Process 1300 can include determining whether to cancel the at least one measurement occasion; (block 1330). Process 1300 can include communicating, to the UE, an indication of the at least one measurement occasion being canceled (block 1340). Process 1300 can include communicating transmitted (Tx) or received (Rx) data traffic during a time domain of the at least one measurement occasion (block 1350). One or more of the examples described herein can also, or alternatively be part of process 1300.

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

[0118] In example 1, which can also include one or more of the examples described herein, baseband circuitry and / or a UE can determine that at least one measurement occasion is cancelable based on at least one condition; generate an indication of the at least one measurement occasion being cancelable; receive information indicating that the at least one measurement occasion is canceled; and process transmitted (Tx) or received (Rx) data traffic during a time domain of the at least one measurement occasion.

[0119] In example 2, which can also include one or more of the examples described herein, the data traffic comprises uplink (UL) data traffic or downlink (DL) data traffic.

[0120] In example 3, which can also include one or more of the examples described herein, the data traffic comprise at least one of: extended reality (XR) data traffic, augmented reality (AR) data traffic, virtual reality (VR) data traffic, high throughput data traffic, or a combination thereof.

[0121] In example 4, which can also include one or more of the examples described herein, the at least one measurement occasion comprises at least one of: a measurement gap, an interruption time associated with a measurement gap, a scheduling restriction, an interruption time associated with a scheduling restriction, or any combination thereof.

[0122] In example 5, which can also include one or more of the examples described herein, the measurement gap comprises at least one of: a type-1 gap, a type-2 gap, a network334917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) controlled small gap (NCSG), a multi subscriber identity module (MUSIM) gap, a positioning gap, a concurrent gap, a pre-configured measurement gap, or a combination thereof.

[0123] In example 6, which can also include one or more of the examples described herein, the interruption time associated with a measurement gap comprises a time preceding or following the measurement gap, during which Rx and Tx data traffic communications are limited as a result of the measurement gap or a process or signal associated with the measurement gap.

[0124] In example 7, which can also include one or more of the examples described herein, the scheduling restriction comprises a time during which transmission (Tx) or reception (Rx) of data traffic is restricted as a result of at least one of: a measurement associated with a radio resource management (RRM) procedure, a new radio (NR) system synchronization block (SSB) measurement timing configuration (SMTC) for a RRM measurement outside of a measurement gap, a layer 1 (LI) reference signal (RS), an LI measurement, an RLM procedure, a system synchronization block (SSB) and channel state information (CSI) RS (CSI-RS) configured for a radio link management (RLM) measurement, or a combination thereof.

[0125] In example 8, which can also include one or more of the examples described herein, the scheduling restriction comprises a time during which transmission (Tx) or reception (Rx) of data traffic is restricted as a result of at least one of: a beam failure detection (BFD) measurement, a candidate beam detection (CBD) measurement, an LI measurement resulting in a scheduling restriction, a procedure scheduled during a measurement gap, a procedure occurring immediately before, immediacy after, or overlapping with a measurement gap, or a combination thereof.

[0126] In example 9, which can also include one or more of the examples described herein, the indication of the at least one measurement occasion being cancelable comprises at least one of: user equipment (UE) assistance information (UAI), uplink (UL) control information (UCI), or a media access control (MAC) control element (CE).

[0127] In example 10, which can also include one or more of the examples described herein, the indication of the at least one measurement occasion being cancelable comprises: a MeasCancelAssistlnfo information element (IE), and a numofCancelableOccasions parameter.

[0128] In example 11, which can also include one or more of the examples described herein, the indication of the at least one measurement occasion being cancelable comprises: a344917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) fixed value of cancelable measurement occasions, or a super set of cancelable measurement occasions.

[0129] In example 12, which can also include one or more of the examples described herein, the indication of the at least one measurement occasion being cancelable comprises at least one of a numofCancelableOccasionsGap parameter, a numofCancelableOccasionsSMTC parameter, a numofCancelableOccasionsRLM parameter, a numofCancelableOccasionsBFD parameter, a numofCancelableOccasionsLl parameter, or a combination thereof.

[0130] In example 13, which can also include one or more of the examples described herein, the at least one condition comprises: a current location within a coverage area of a serving base station, a distance to a base station being less than or equal to a distance threshold, a reference signal received power (RSRP) being greater than or equal to an RSRP threshold, a signal-to-noise ratio (SNR) being less than or equal to an SNR threshold, the transmitted (Tx) or received (Rx) data traffic comprising high throughput data traffic, a mobility state comprising a high mobility state, a low mobility state, or a velocity relative to a mobility threshold, a radio resource management (RRM) measurement relative to an RRM measurement threshold.

[0131] In example 14, which can also include one or more of the examples described herein, the current location comprises: a cell edge of the coverage area of the base station, a handover zone of the coverage area of the base station, or a combination thereof.

[0132] In example 15, which can also include one or more of the examples described herein, the one or more processors are to: receive the at least one condition from a base station.

[0133] In example 16, which can also include one or more of the examples described herein, the one or more processors are to: determine, in response to the information indicating that the at least one measurement occasion is canceled, whether to process transmitted (Tx) or received (Rx) data traffic during the time domain of the at least one measurement occasion.

[0134] In example 17, which can also include one or more of the examples described herein, the one or more processors are to: generate user equipment (UE) capability information comprising an indication of an ability to cancel at least one measurement occasion.

[0135] In example 18, which can also include one or more of the examples described herein, the user equipment (UE) capability information comprises at least one of: assistance information for measurement cancelation, assistance information for measurement occasion354917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) cancelation, assistance information for measurement gap cancelation, assistance information for measurement system synchronization block (SSB) measurement timing configuration (SMTC) cancelation, assistance info for radio link management (RLM) cancelation, or a combination thereof.

[0136] In example 19, which can also include one or more of the examples described herein, a method can comprise: determining that at least one measurement occasion is cancelable based on at least one condition; communicating an indication of the at least one measurement occasion being cancelable; receiving information indicating that the at least one measurement occasion is canceled; and communicating transmitted (Tx) or received (Rx) data traffic during a time domain of the at least one measurement occasion.

[0137] In example 20, which can also include one or more of the examples described herein, further comprising: receiving the at least one condition from a base station.

[0138] In example 21, which can also include one or more of the examples described herein, further comprising: determining, in response to the information indicating that the at least one measurement occasion is canceled, whether to process transmitted (Tx) or received (Rx) data traffic during the time domain of the at least one measurement occasion.

[0139] In example 22, which can also include one or more of the examples described herein, further comprising: communicating user equipment (UE) capability information comprising an indication of an ability to cancel at least one measurement occasion.

[0140] In example 23, which can also include one or more of the examples described herein, a base station comprises: one or more processors configured to: communicate, to a user equipment (UE), at least one condition for canceling at least one measurement occasion; receive, from the UE, an indication of the at least one measurement occasion being cancelable; determine whether to cancel the at least one measurement occasion; communicate, to the UE, an indication of the at least one measurement occasion being canceled; and communicate transmitted (Tx) or received (Rx) data traffic during a time domain of the at least one measurement occasion.

[0141] In example 24, which can also include one or more of the examples described herein, the one or more processors are to: determine whether to cancel the at least one measurement occasion by determining whether the base station is configured to cancel any measurement occasions.

[0142] In example 25, which can also include one or more of the examples described herein, the one or more processors are to: determine whether to cancel the at least one measurement occasion by determining whether canceling the at least one measurement364917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) occasion is consistent with a measurement occasion cancelation policy, the measurement occasion cancelation policy comprising at least one rule regarding how often measurement occasions can be canceled.

[0143] In example 26, which can also include one or more of the examples described herein, the one or more processors are to: determine whether to cancel the at least one measurement occasion by selectively determining whether to cancel measurement occasions based at least one cancelation condition.

[0144] In example 27, which can also include one or more of the examples described herein, the at least one cancelation condition comprises: whether the at least on measurement occasion is for load balancing purposes while the base station is not under a full load.

[0145] In example 28, which can also include one or more of the examples described herein, the one or more processors are to: receive user equipment (UE) capability information comprising an indication that the UE is capable of canceling measurement occasions.

[0146] In example 29, which can also include one or more of the examples described herein, the interruption time associated with the scheduling restriction comprises a time preceding or following the scheduling restriction, during which Rx and Tx data traffic communications are limited as a result of the scheduling restriction or a process or signal associated with the scheduling restriction.

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

[0148] In this regard, while the disclosed subject matter has been described in connection with various examples, implementations, aspects, etc., and corresponding Figures, where applicable, it is to be understood that other similar aspects can be used or modifications and additions can be made to the disclosed subject matter for performing the same, similar, alternative, or substitute function of the subject matter without deviating therefrom. Therefore, the disclosed subject matter should not be limited to any single example, implementation, or aspect described herein, but rather should be construed in breadth and scope in accordance with the appended claims below.

[0149] In particular regard to the various functions performed by the above described components or structures (assemblies, devices, circuits, systems, etc.), the terms (including a374917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) 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.

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

[0151] 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.384917-5489-1855, v. 3

Claims

Attorney Docket No.: 106842241440 (P69425WO1)CLAIMSWhat is claimed is:

1. Baseband circuitry, comprising: one or more processors configured to: determine that at least one measurement occasion is cancelable based on at least one condition; generate an indication of the at least one measurement occasion being cancelable; receive information indicating that the at least one measurement occasion is canceled; and process transmitted (Tx) or received (Rx) data traffic during a time domain of the at least one measurement occasion.

2. The baseband circuitry of claim 1, wherein the data traffic comprises uplink (UL) data traffic or downlink (DL) data traffic.

3. The baseband circuitry of claim 1, wherein the data traffic comprise at least one of: extended reality (XR) data traffic, augmented reality (AR) data traffic, virtual reality (VR) data traffic, high throughput data traffic, or a combination thereof.

4. The baseband circuitry of claim 1, wherein the at least one measurement occasion comprises at least one of: a measurement gap, an interruption time associated with a measurement gap, a scheduling restriction, an interruption time associated with a scheduling restriction, or any combination thereof.

5. The baseband circuitry of claim 4, wherein the measurement gap comprises at least one of: a type-1 gap,394917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) a type-2 gap, a network controlled small gap (NCSG), a multi subscriber identity module (MUSIM) gap, a positioning gap, a concurrent gap, a pre-configured measurement gap, or a combination thereof.

6. The baseband circuitry of claim 4, wherein the interruption time associated with a measurement gap comprises a time preceding or following the measurement gap, during which Rx and Tx data traffic communications are limited as a result of the measurement gap or a process or signal associated with the measurement gap.

7. The baseband circuitry of claim 4, wherein the scheduling restriction comprises a time during which transmission (Tx) or reception (Rx) of data traffic is restricted as a result of at least one of: a measurement associated with a radio resource management (RRM) procedure, a new radio (NR) system synchronization block (SSB) measurement timing configuration (SMTC) for a RRM measurement outside of a measurement gap, a layer 1 (LI) reference signal (RS), an LI measurement, an RLM procedure, a system synchronization block (SSB) and channel state information (CSI) RS (CSLRS) configured for a radio link management (RLM) measurement, or a combination thereof.

8. The baseband circuitry of claim 4, wherein the scheduling restriction comprises a time during which transmission (Tx) or reception (Rx) of data traffic is restricted as a result of at least one of: a beam failure detection (BFD) measurement, a candidate beam detection (CBD) measurement, an LI measurement resulting in a scheduling restriction, a procedure scheduled during a measurement gap, a procedure occurring immediately before, immediacy after, or overlapping with a measurement gap, or404917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) a combination thereof.

9. The baseband circuitry of claim 4, wherein the interruption time associated with the scheduling restriction comprises a time preceding or following the scheduling restriction, during which Rx and Tx data traffic communications are limited as a result of the scheduling restriction or a process or signal associated with the scheduling restriction.

10. The baseband circuitry of any of claims 1 to 9, wherein the indication of the at least one measurement occasion being cancelable comprises at least one of: user equipment (UE) assistance information (UAI), uplink (UL) control information (UCI), or a media access control (MAC) control element (CE).

11. The baseband circuitry of any of claims 1 to 9, wherein the indication of the at least one measurement occasion being cancelable comprises: a MeasCancelAssistlnfo information element (IE), and a numofCancelableOccasions parameter.

12. The baseband circuitry of any of claims 1 to 9, wherein the indication of the at least one measurement occasion being cancelable comprises: a fixed value of cancelable measurement occasions, or a super set of cancelable measurement occasions.

13. The baseband circuitry of any of claims 1 to 9, wherein the indication of the at least one measurement occasion being cancelable comprises at least one of: a numofCancelableOccasionsGap parameter, a numofCancelableOccasionsSMTC parameter, a numofCancelableOccasionsRLM parameter, a numofCancelableOccasionsBFD parameter, a numofCancelableOccasionsLl parameter, or a combination thereof.

14. The baseband circuitry of any of claims 1 to 9, wherein the at least one condition comprises:414917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) a current location within a coverage area of a serving base station, a distance to a base station being less than or equal to a distance threshold, a reference signal received power (RSRP) being greater than or equal to an RSRP threshold, a signal-to-noise ratio (SNR) being less than or equal to an SNR threshold, the transmitted (Tx) or received (Rx) data traffic comprising high throughput data traffic, a mobility state comprising a high mobility state, a low mobility state, or a velocity relative to a mobility threshold, a radio resource management (RRM) measurement relative to an RRM measurement threshold.

15. The baseband circuitry of claim 14, wherein the current location comprises: a cell edge of the coverage area of the base station, a handover zone of the coverage area of the base station, or a combination thereof.

16. The baseband circuitry of any of claims 1 to 9, wherein the one or more processors are to: receive the at least one condition from a base station.

17. The baseband circuitry of any of claims 1 to 9, wherein the one or more processors are to: determine, in response to the information indicating that the at least one measurement occasion is canceled, whether to process transmitted (Tx) or received (Rx) data traffic during the time domain of the at least one measurement occasion.

18. The baseband circuitry of any of claims 1 to 9, wherein the one or more processors are to: generate user equipment (UE) capability information comprising an indication of an ability to cancel at least one measurement occasion.

19. A method, comprising: determining that at least one measurement occasion is cancelable based on at least one condition; communicating an indication of the at least one measurement occasion being cancelable; receiving information indicating that the at least one measurement occasion is canceled; and424917-5489-1855, v. 3Attorney Docket No.: 106842241440 (P69425WO1) communicating transmitted (Tx) or received (Rx) data traffic during a time domain of the at least one measurement occasion.

20. A base station, comprising: one or more processors configured to: communicate, to a user equipment (UE), at least one condition for canceling at least one measurement occasion, receive, from the UE, an indication of the at least one measurement occasion being cancelable; determine whether to cancel the at least one measurement occasion; communicating, to the UE, an indication of the at least one measurement occasion being canceled; and communicating transmitted (Tx) or received (Rx) data traffic during a time domain of the at least one measurement occasion.4917-5489-1855, v. 3

Images