Attorney Docket No. AE9962-PCT /1020.9962WO USER EQUIPMENT CAPABILITY FOR INTERRUPTIONS WITHOUT MEASUREMENT GAPS [0001] This application claims the benefit of and priority to previously filed United States Provisional Patent Application Serial Number 63/416,828, filed October 17, 2022, entitled “UE CAPABILITY FOR INTERRUPTIONS ON UE WHEN NO MEASUREMENT GAPS USED”, which is hereby incorporated by reference in its entirety. BACKGROUND [0002] Wireless communication systems are rapidly growing in usage. Further, wireless communication technology has evolved from voice-only communications to also include the transmission of data, such as Internet and multimedia content, to a variety of devices. To accommodate a growing number of devices communicating, many wireless communication systems share the available communication channel resources among devices. Further, Internet-of-Thing (IoT) devices are also growing in usage and can coexist with user devices in various wireless communication systems such as cellular networks. BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS [0003] To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced. [0004] FIG. 1 illustrates a wireless communication system in accordance with one embodiment. [0005] FIG. 2 illustrates a wireless communication system in accordance with one embodiment. [0006] FIG. 3 illustrates an operating environment in accordance with one embodiment. [0007] FIG. 4 illustrates a data schema for measurement information in accordance with one embodiment. [0008] FIG. 5 illustrates an apparatus for a user equipment (UE) in accordance with one embodiment. [0009] FIG. 6 illustrates an apparatus for a base station in accordance with one embodiment. [0010] FIG. 7 illustrates a logic flow in accordance with one embodiment. [0011] FIG. 8 illustrates a logic flow in accordance with one embodiment. Attorney Docket No. AE9962-PCT /1020.9962WO [0012] FIG. 9 illustrates a first network in accordance with one embodiment. [0013] FIG. 10 illustrates a second network in accordance with one embodiment. [0014] FIG. 11 illustrates a third network in accordance with one embodiment. [0015] FIG. 12 illustrates a computer readable storage medium in accordance with one embodiment. DETAILED DESCRIPTION [0016] Embodiments are generally directed to wireless communication systems. Some embodiments are particularly directed to improving measurement capabilities for user equipment (UE) in a wireless communications system. In one embodiment, for example, a wireless communications system may implement improvements for efficiently utilizing measurement gaps for a UE to accurately measure radio signals to support improved network services, such as handover, load balancing, and overall network utilization and performance. [0017] In many wireless communication systems, including long-term evolution (LTE) and fifth generation (5G) new radio (5G NR) and sixth generation (6G) cellular networks, a UE transmits data to a base station (BS) over a radio using various radio resources. As such, radio resource management (RRM) is a crucial component of a radio access network (RAN), such as RAN in Third Generation Partnership Project (3GPP) systems, including LTE , 5G NR and 6G cellular networks. RRM manages the allocation and coordination of the radio resources, including frequency, power, and time slots, among different users and services in the network. The primary goal of RRM is to ensure efficient and reliable use of radio resources while maintaining the quality of service (QoS) for all users. Some of the key functions of RRM in 3GPP systems include radio resource allocation, congestion control, handover management, scheduling, and power control. RRM also plays a critical role in managing interference and optimizing network capacity and coverage. Overall, RRM helps ensure the efficient and effective operation of wireless networks. [0018] Various 3GPP documents define RRM for a 5G NR and 6G system, including 3GPP Technical Standards (TS), Technical Reports (TR) and/or Work Items (WI). Various embodiments discussed herein may be implemented in a wireless communications system as defined by the 3GPP TS 38.133 titled “Technical Specification Group Radio Access Network; NR; Requirements for support of radio resource management,” Release 17, Version 18.2.0 (June 2023), and including future versions, revisions or variants (collectively referred to as “3GPP TS 38.133 Standards”). The 3GPP TS 38.133 specifies requirements Attorney Docket No. AE9962-PCT /1020.9962WO for support of RRM for the frequency division duplexing (FDD) and time division duplexing (TDD) modes of NR. These requirements include requirements on measurements in NR and the UE as well as requirements on node dynamical behavior and interaction, in terms of delay and response characteristics. Various embodiments discussed herein may also be implemented in a wireless communications system as defined by the 3GPP TS 38.331 titled “NR; Radio Resource Control (RRC); Protocol specification,” Release 17, Version 17.5.0 (June 2023), and including future versions, revisions or variants (collectively referred to as “3GPP TS 38.331 Standards”). It may be appreciated that the embodiments may be implemented in accordance with other 3GPP TS and TR, as well as other wireless standards released by other standards entities. Embodiments are not limited in this context. [0019] An important part of RRM is efficiently utilizing measurement gaps for a UE to accurately measure radio signals to support improved network services, such as handover, load balancing, and overall network utilization and performance. The 3GPP TS 38.133 Standards define a feature referred to as a “measurement gap”. A measurement gap is a specific time period or interval during which a UE, such as a mobile phone, temporarily halts its regular communication with the serving cell and performs measurements on other frequencies or radio access technologies (RATs). These measurements help the network and the UE to assess the radio conditions and characteristics of neighboring cells. Measurement gaps serve different purposes, such as signal quality measurement to assess a quality of signals from neighboring cells to ensure optimal connectivity and facilitate handovers when the UE is moving, inter-frequency and intra-frequency measurements to allow the UE to perform measurements on different frequencies and RATs, and cell selection or re-selection to decide on a most suitable cell for connection or reconnection, thereby optimizing network resource utilization and user experience. [0020] The network schedules measurement gaps based on a variety of factors, including network conditions, UE mobility, and communication needs. During the scheduled measurement gap, the UE pauses its normal data transmission and reception activities with the serving cell and starts measuring signals from neighboring cells. After completing the measurements, the UE reports the results back to the network. The network, which then makes decisions such as whether a handover is needed or if the UE should change frequencies. Once the measurement gap is over, the UE resumes its regular communication with the serving cell. [0021] For modern technologies like 5G and 6G, the 3GPP standards introduced a network-controlled small gap (NCSG) feature. NCSG allows for more refined and network- Attorney Docket No. AE9962-PCT /1020.9962WO controlled implementation of measurement gaps, enhancing the granularity and flexibility of scheduling. NCSG introduces smaller and optimized gaps, minimizing the disruption to user data transmission and improving overall user experience. NCSG also supports measurements across multiple RATs, addressing the diverse and complex requirements of heterogeneous network environments in contemporary mobile communication systems. NCSG in 3GPP standards is a crucial enhancement for measurement in modern mobile networks, enabling accurate and diversified measurements to optimize network performance, user experience, and facilitate seamless mobility in heterogeneous network environments. [0022] The network activates a NCSG and it instructs the UE to create small gaps in its ongoing communications. These small gaps allow the UE to perform measurements. During these small gaps, the UE can perform measurements on different frequencies and RATs, enhancing its ability to find the best available signal and enabling improved handover, load balancing, and overall network performance. This is particularly important in 5G and 6G networks, where multiple bands and technologies need to be managed simultaneously. The UE can use these gaps to synchronize with the cells of interest and acquire system information. In 5G NR, for example, a UE routinely performs measurements to assess the signal quality, strength, and other characteristics of the serving and neighboring cells, which are critical for handovers, cell selection or re-selection, and overall network optimization. These measurements can be categorized as: (1) intra-frequency measurements performed within the same frequency band as the serving cell; and (2) inter-frequency measurements performed on different frequency bands than that of the serving cell. [0023] In 3GPP Release 17 and beyond, advancements have been made to allow a UE to perform measurements without needing a dedicated measurement gap, thus mitigating interruptions to data communication and improving the overall user experience and system performance. Modern UEs are equipped with advanced receivers capable of performing measurements on different frequency simultaneously without needing to interrupt the primary serving cell communication, multiple antennas and advanced signal processing to manage concurrent reception from different cells or frequencies allowing seamless measurements, parallel processing capabilities to allow a UE to handle multiple tasks concurrently, enhanced measurement reporting capabilities, and advanced interference measurement techniques to enable the UE to isolate and filter out interference while performing measurements. When the UE is capable of performing certain measurements without requiring a break or measurement gap in communication, it can continue Attorney Docket No. AE9962-PCT /1020.9962WO transmitting and receiving data while simultaneously measuring signal characteristics from the serving and neighboring cells. If the UE does not need gaps for measurements, it can maintain continuous communication with the network, which is crucial for applications that are sensitive to latency and interruptions. [0024] The UE communicates whether or not it needs measurement gaps to the network using control messages. For the UE to indicate to the network that it does not require measurement gaps, there usually is a signaling mechanism involving Radio Resource Control (RRC) messages between the UE and the network. The UE indicates its capabilities, including the ability to perform measurements without gaps, to the network during the initial connection setup, or during subsequent capability updates. This is often conveyed through the RRC Connection Setup or RRC Connection Reconfiguration process, wherein the UE sends its capability information to the network. This information typically contains various parameters and features that the UE supports, including its ability to make measurements without requiring dedicated measurement gaps. If the network is aware of this capability, it can then optimize the scheduling and resource allocation accordingly. Based on the received capability information, the network configures the relevant policies and parameters for the UE, avoiding the allocation of measurement gaps and scheduling resources more efficiently. The UE, with its advanced receiver and processing capabilities, continues to perform measurements and reports them back to the network as needed, allowing the network to make informed decisions on handovers, beam management, and other aspects, without interrupting the ongoing communications. [0025] In 3GPP Release 17, the UE communicates whether or not it needs measurement gaps to the network using a defined information element (IE). For example, 3GPP TS 38.331 Release 17 defines an IE referred to as a NeedForGapsInfoNR IE to serve as a mechanism for a UE to communicate to the network whether it requires measurement gaps to perform inter-frequency and intra-frequency measurements. Similarly, 3GPP TS 38.331 Release 17 defines an IE referred to as a NeedForNCSG-InfoNR IE for NCSG. Both the NeedForGapsInfoNR IE and the NeedForNCSG-InfoNR IE include various defined data fields, one of which is a gapIndication field, among other types of data fields. [0026] For the NeedForGapsInfoNR IE, the gapIndication field indicates whether a measurement gap is required for the UE to perform synchronization signal block (SSB) based measurements on the concerned NR target band while NR dual-connectivity (NR-DC) or NR evolved universal terrestrial radio access network (E-UTRAN) dual connectivity (NE-DC) is not configured. The UE determines this information based on the resultant Attorney Docket No. AE9962-PCT /1020.9962WO configuration of the RRCReconfiguration or RRCResume message that triggers this response. The gapIndication field carries one of two enumerated values {gap, no-gap}, where the first value gap indicates that a measurement gap is needed, and the second value no-gap indicates a measurement gap is not needed. [0027] For the NeedForNCSG-InfoNR IE, the gapIndication field indicates whether measurement gap or NCSG is required for the UE to perform SSB based measurements on the concerned NR target band while NR-DC or NE-DC is not configured. The UE determines this information based on the resultant configuration of the RRCReconfiguration or RRCResume message that triggers this response. The gapIndication field carries one of three enumerated values {gap, ncsg, nogap-noncsg}, where the first value gap indicates that a measurement gap is needed, the second value ncsg indicates that a NCSG is needed, and the third value nogap-noncsg indicates neither a measurement gap nor a NCSG is needed. [0028] Currently, the Working Group 4 under the Radio Access Network (RAN) Technical Specification Group (RAN4) is attempting to define further enhancements on NR measurement gap. Two objectives are under consideration. [0029] The first objective considers enhancements of pre-configured measurement gaps (MGs), multiple concurrent MGs and NCSG. The first objective includes defining RRM requirements for UEs configured with a combination of pre-configured MGs, and/or multiple concurrent MGs and/or NCSG. The first objective further includes prioritizing at least joint requirements for UE configured with: (1) Case 1: Pre-configured MGs and multiple concurrent MGs (i.e., concurrent MGs where at least one of the gaps is a pre- configured gap); and (2) Case 2: NCSG and multiple concurrent MGs (i.e., concurrent MGs where at least one of the gaps is NCSG). It is worthy to note that prioritization among other possible combinations of pre-configured MG, concurrent MG and NCSG were considered as well. [0030] The second objective considers defining RRM requirements for measurement without gaps for the case of a NR SSB-based inter-frequency and intra-frequency measurements without gaps for UEs reporting NeedForGapsInfoNR IE. This case includes a study of whether the additional interruption is allowed when UE reporting “NeedForGapsInfoNR”. Further, this case includes: (1) defining the interruption length, occasion and ratio, if the interruption is allowed; and (2) defining related requirements, such as carrier-specific scaling factor (CSSF), measurement period, scheduling restriction, and so forth. Attorney Docket No. AE9962-PCT /1020.9962WO [0031] Some embodiments provide multiple solutions for the second objective. RAN4 is currently attempting to define RRM requirements for measurement without gaps for certain use cases. In particular, RAN4 is studying whether interruption is allowed when a UE reports the NeedForGapsInfoNR IE or the NeedForNCSG-InfoNR IE. This study attempts to define an interruption length, an occasion and ratio, if the interruption is allowed. [0032] In the context of 5G or 6G measurements, an “interruption” refers to a temporary disruption or halt in the measurement process. Interruptions can occur due to various factors, such as changes in network conditions, handovers between cells, signaling events, or other network operations. During an interruption, the UE temporarily suspends its ongoing measurements or communication to perform the necessary procedure and then resumes normal operation once the interruption is resolved. Interruptions in measurements may vary depending on the specific measurement scenario in 5G. For example, during a handover procedure, when the UE switches from one cell to another, there may be a brief interruption in measurements as the UE transfers its connection to the new serving cell. Similarly, interruptions can occur during certain signaling processes, such as network- controlled mobility for optimized resource allocation or network-assisted beamforming. Managing interruptions effectively is crucial for maintaining accurate and reliable measurement results in 5G and 6G networks. Measurement algorithms and protocols are designed to handle interruptions in a way that ensures precise measurements and minimizes any impact on network performance or user experience. Section 8.2 of the 3GPP TS 38.133 Standards, for example, defines a set of interruptions and associated interruption requirements related to interruptions on a primary serving cell (PSCell) and a secondary cell (SCell). Embodiments are not limited to these types of interruptions and interruption requirements. [0033] To define UE capability on UE measurements with the pre-configured gaps in NR, RAN4 is considering several options for the open issues on interruption requirements when a UE is reporting NeedForGapsInfoNR IE or NeedForNCSG-InfoNR IE. The first open issue is whether an interruption is expected when the UE reports a “no-gap” scenario. The first open issue can be resolved one of three ways, such as by allowing interruptions, denying interruptions, or introducing additional UE capabilities to differentiate whether the UE actually needs an interruption. The second open issue is interruption requirements when interruptions are allowed. The second open issue can be resolved: (1) visibly by starting with NCSG and frequency and frame structure (FFS) the exact values; or (2) invisibly by Attorney Docket No. AE9962-PCT /1020.9962WO starting with adopting deactivated secondary cell's interruption requirement and FFS an interruption ratio (e.g., a data dropping rate). [0034] In the 3GPP TS 38.331 Standards, NCSG was introduced for measurement enhancements. NCSG may also have interruption requirements in those cases when a UE can support NCSG. The necessary interruption requirements on a UE are dependent on the UE’s capability and network configuration. The UE can indicate UE capability to support NCSG using the defined IE referred to as a NeedForNCSG-InfoNR IE, as defined in 3GPP TS 38.331 Version 17.1.0. [0035] Therefore, from a RAN4 perspective, the interruption requirements when the network configures the different types of measurement gaps can be implicitly applied up to these indications (e.g., “gap, ncsg, nogap-noncsg”). For example, when a UE can support “nogap-noncsg”, there may not be any interruptions allowed. Consequently, whether interruptions are allowed, and corresponding interruption requirements when allowed, remains an ambiguous and undefined topic in current 3GPP standards. [0036] Embodiments attempt to solve these and other challenges by defining enhanced UE capability for UE measurements with pre-configured gaps in 5G NR and 6G. More particularly, embodiments define UE capability on UE measurements for measurement gaps, including NCSG, when a UE reports a UE capability of measurement without gaps. Examples of measurements without gaps include indications of “no-gap” and/or “nogap- noncsg” in network messages, such as RRM or RRC messages, which indicate that a UE does not need a measurement gap to perform inter-frequency or intra-frequency measurements. Stated another way, the UE has a UE capability of supporting both normal communications and measurement operations simultaneously. Embodiments are not limited to these examples. [0037] One embodiment, for example, attempts to more clearly define UE behavior on interruption requirements when a UE reports a UE capability of measurement without gaps. Embodiments define UE behavior based on three different observations. [0038] The first observation is when a UE indicates a defined IE such as NeedForNCSG- NR the exact interruption requirements may be conducted. Similarly, if a UE needs to support the “NeedForGapsInfoNR” for the measurements without gaps, the necessary interruption requirements for UE can be also defined. However, there remains some unresolved ambiguities when a UE reports with “no-gap”. One ambiguity is whether a UE reporting “no-gap” means neither NCSG nor legacy measurement gap beyond Release 17 is needed for the NeedForGapsInfoNR IE. Attorney Docket No. AE9962-PCT /1020.9962WO [0039] The second observation is when a UE indicates “no-gap” in the NeedForGapsInfoNR IE, it is ambiguous in the legacy specifications as to whether neither NCSGs nor legacy measurement gaps are to be configured by the network. If the indication “no-gap” in NeedForGapsInfoNR IE means neither NCSG nor legacy measurement gaps are needed from a UE perspective, the interruption may not be allowed. However, in 3GPP TS 38.331 Release 17, the “no-gap” indication in “NeedForNCSG-NR” seems to have an alternative, or at least, an ambiguous interpretation. [0040] The third observation is how to define the interruption requirements need RAN2 further clarification on the indication of “no-gap” in NeedForGapsNR message, such as whether it is consistent with that in “NeedForNCSG-NR” IE. [0041] From a RAN4 perspective, in order to more clearly define UE behaviors on the interruption requirements, a similar mechanism in Release 17 NCSG can be adopted. For instance, if the “nogap-nointerruption” is reported in NeedForGapsInfoNR IE, the UE behaviors can be explicitly defined as: (1) measurement without gap; and (2) no interruption allowed. This addresses the first open issue of whether an interruption is expected when a UE reports “no-gap” by introducing additional UE capability to differentiate whether the UE needs interruption. This also addresses the second open issue of interruption requirement when an interruption is allowed by starting with NCSG as a base case and FFS the exact values needed. [0042] Embodiments clearly define UE behavior on interruption requirements when a UE reports a UE capability of measurement without gaps. In a first embodiment, for example, interruption requirements when a UE is performing SSB measurements without gap by reporting in the NeedForGapsInfoNR IE are defined in Table 1 as follows: [0043] TABLE 1 Network Case A: configuration for No measurement gap (MG) UE capability of “NeedForGap” gap No requirements no-gap Measurements out of gap, Attorney Docket No. AE9962-PCT /1020.9962WO interruption allowed, and interruption requirements defined in 3GPP TS38.1339.1.9[3] nogap-noncsg Measurements out of gap, No interruption allowed [0044] In a second embodiment, assume the NeedForGapsInfoNR IE includes a set of capabilities denoted as {capability 1, capability 2, capability 3,..., capability N}, where N represents any positive integer. In one embodiment, [capability 1] is one or more values that indicate interruption is allowed, and [capability 2] is one or more values that indicate no interruption is allowed. When a UE reports “[capability 1]” to indicate that interruption is allowed, the interruption should be allowed for each of intra-frequency and inter-frequency measurements for which the UE reports “[capability 1]”. The interruption will impact all the serving cells if UE does not support per-frequency range (FR) gap, and all the serving cells in the same FR as the measurement if UE supports per-FR gap. When a UE reports “[capability 2]” to indicate no interruption allowed, the interruption is not allowed for each of intra-frequency and inter-frequency measurements for which the UE reports “[capability 2]”. The other capabilities N may be defined for interruption and interruption requirements for other use cases, as needed for a given implementation. [0045] In a third embodiment, a new IE is defined for communication between the UE and the network to indicate interruption information. In one example, the new IE may be referred to as a NeedForInterruptionInfoNR-R18 IE. Embodiments are not limited to this particular name or associated information fields. This new IE carries information indicating when interruptions are allowed or not allowed, and interruption requirements for when interruptions are allowed, among other types of interruption and/or capabilities information. [0046] The present disclosure will now be described with reference to the attached drawing figures, wherein like reference numerals are used to refer to like elements throughout, and wherein the illustrated structures and devices are not necessarily drawn to scale. As utilized herein, terms “component,” “system,” “interface,” and the like are intended to refer to a computer-related entity, hardware, software (e.g., in execution), and/or firmware. For example, a component can be a processor (e.g., a microprocessor, a controller, or other processing device), a process running on a processor, a controller, an object, an executable, a program, a storage device, a computer, a tablet PC and/or a user Attorney Docket No. AE9962-PCT /1020.9962WO equipment (e.g., mobile phone, etc.) with a processing device. By way of illustration, an application running on a server and the server can also be a component. One or more components can reside within a process, and a component can be localized on one computer and/or distributed between two or more computers. A set of elements or a set of other components can be described herein, in which the term “set” can be interpreted as “one or more.” [0047] Further, these components can execute from various computer readable storage media having various data structures stored thereon such as with a module, for example. The components can communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network, such as, the Internet, a local area network, a wide area network, or similar network with other systems via the signal). [0048] As another example, a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry, in which the electric or electronic circuitry can be operated by a software application or a firmware application executed by one or more processors. The one or more processors can be internal or external to the apparatus and can execute at least a part of the software or firmware application. As yet another example, a component can be an apparatus that provides specific functionality through electronic components without mechanical parts; the electronic components can include one or more processors therein to execute software and/or firmware that confer(s), at least in part, the functionality of the electronic components. [0049] Use of the word exemplary is intended to present concepts in a concrete fashion. As used in this application, 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 Attorney Docket No. AE9962-PCT /1020.9962WO more numbered items may be distinct or they may be the same, although in some situations the context may indicate that they are distinct or that they are the same. [0050] As used herein, the term “circuitry” may refer to, be part of, or include a circuit, an integrated circuit (IC), a monolithic IC, a discrete circuit, a hybrid integrated circuit (HIC), an Application Specific Integrated Circuit (ASIC), an electronic circuit, a logic circuit, a microcircuit, a hybrid circuit, a microchip, a chip, a chiplet, a chipset, a multi-chip module (MCM), a semiconductor die, a system on a chip (SoC), a processor (shared, dedicated, or group), a processor circuit, a processing circuit, or associated memory (shared, dedicated, or group) operably coupled to the circuitry that execute one or more software or firmware programs, a combinational logic circuit, or other suitable hardware components that provide the described functionality. In some embodiments, the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, circuitry may include logic, at least partially operable in hardware. [0051] FIG. 1 illustrates an example of a wireless communication wireless communications system 100. For purposes of convenience and without limitation, the example wireless communications system 100 is described in the context of the long-term evolution (LTE) and fifth generation (5G) new radio (NR) (5G NR) cellular networks communication standards as defined by one or more 3GPP TS 38.133 Standards, 3GPP TS 38.304 Standards, 3GPP 38.331 Standards, or 3GPP 38.500 Standards, or other 3GPP standards or specifications. However, other types of wireless standards are possible as well. [0052] The wireless communications system 100 supports two classes of UE devices, including a reduced capability (RedCap) UE 102a and standard UE 102b (collectively referred to as the "UEs 102"). In one embodiment, the UE 102a may have a set of one or more reduced capabilities relative to a set of standard capabilities of the standard UE 102b. Examples of reduced capabilities may include without limitation: (1) 20 megahertz (MHz) in sub-7 gigahertz (GHz) or 100 MHz in millimeter wave (mmWave) frequency bands; (2) a single transmit (Tx) antenna (1 Tx); (3) a single receive (Rx) antenna (1 Rx), with 2 antennas (2 Rx) being optional; (4) optional support for half-duplex FDD; (5) lower-order modulation, with 256-quadrature amplitude modulation (QAM) being optional; and (6) support for lower transmit power. In one embodiment, for example, the standard UE 102b may have a 2 Rx antenna, while the UE 102a may only have a 1 Rx antenna. The UE 102a may have other reduced capabilities as well. Embodiments are not limited in this context. Attorney Docket No. AE9962-PCT /1020.9962WO [0053] In this example, the UEs 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks). In other examples, any of the UEs 102 can include other mobile or non-mobile computing devices, such as consumer electronics devices, cellular phones, smartphones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handsets, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, an Instrument Cluster (IC), head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), Electronic Engine Management System (EEMS), electronic/engine control units (ECUs), electronic/engine control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or "smart" appliances, machine-type communications (MTC) devices, machine- to-machine (M2M) devices, Internet of Things (IoT) devices, or combinations of them, among others. [0054] In some implementations, any of the UEs 102 may be IoT UEs, which can include a network access layer designed for low-power IoT applications utilizing short-lived UE connections. An IoT UE can utilize technologies such as M2M or MTC for exchanging data with an MTC server or device using, for example, a public land mobile network (PLMN), proximity services (ProSe), device-to-device (D2D) communication, sensor networks, IoT networks, or combinations of them, among others. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An IoT network describes interconnecting IoT UEs, which can include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The IoT UEs may execute background applications (e.g., keep-alive messages or status updates) to facilitate the connections of the IoT network. [0055] The UEs 102 are configured to connect (e.g., communicatively couple) with a radio access network (RAN) 112. In some implementations, the RAN 112 may be a next generation RAN (NG RAN), an evolved UMTS terrestrial radio access network (E- UTRAN), or a legacy RAN, such as a UMTS terrestrial radio access network (UTRAN) or a GSM EDGE radio access network (GERAN). As used herein, the term "NG RAN" may refer to a RAN 112 that operates in a 5G NR wireless communications system 100, and the term "E-UTRAN" may refer to a RAN 112 that operates in an LTE or 4G wireless communications system 100. Attorney Docket No. AE9962-PCT /1020.9962WO [0056] To connect to the RAN 112, the UEs 102 utilize connections (or channels) 118 and 120, respectively, each of which can include a physical communications interface or layer, as described below. In this example, the connections 118 and 120 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a global system for mobile communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a push-to-talk (PTT) protocol, a PTT over cellular (POC) protocol, a universal mobile telecommunications system (UMTS) protocol, a 3GPP LTE protocol, a 5G NR protocol, or combinations of them, among other communication protocols. [0057] The UE 102b is shown to be configured to access an access point (AP) 104 (also referred to as "WLAN node 104," "WLAN 104," "WLAN Termination 104," "WT 104" or the like) using a connection 122. The connection 122 can include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, in which the AP 104 would include a wireless fidelity (Wi-Fi) router. In this example, the AP 104 is shown to be connected to the Internet without connecting to the core network of the wireless system, as described in further detail below. [0058] The RAN 112 can include one or more nodes such as RAN nodes 106a and 106b (collectively referred to as "RAN nodes 106" or "RAN node 106") that enable the connections 118 and 120. As used herein, the terms "access node," "access point," or the like may describe equipment that provides the radio baseband functions for data or voice connectivity, or both, between a network and one or more users. These access nodes can be referred to as base stations (BS), gNodeBs, gNBs, eNodeBs, eNBs, NodeBs, RAN nodes, rode side units (RSUs), transmission reception points (TRxPs or TRPs), and the link, and can include ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell), among others. As used herein, the term "NG RAN node" may refer to a RAN node 106 that operates in an 5G NR wireless communications system 100 (for example, a gNB), and the term "E-UTRAN node" may refer to a RAN node 106 that operates in an LTE or 4G wireless communications system 100 (e.g., an eNB). In some implementations, the RAN nodes 106 may be implemented as one or more of a dedicated physical device such as a macrocell base station, or a low power (LP) base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells. [0059] In some implementations, some or all of the RAN nodes 106 may be implemented as one or more software entities running on server computers as part of a virtual network, Attorney Docket No. AE9962-PCT /1020.9962WO which may be referred to as a cloud RAN (CRAN) or a virtual baseband unit pool (vBBUP). The CRAN or vBBUP may implement a RAN function split, such as a packet data convergence protocol (PDCP) split in which radio resource control (RRC) and PDCP layers are operated by the CRAN/vBBUP and other layer two (e.g., data link layer) protocol entities are operated by individual RAN nodes 106; a medium access control (MAC)/physical layer (PHY) split in which RRC, PDCP, MAC, and radio link control (RLC) layers are operated by the CRAN/vBBUP and the PHY layer is operated by individual RAN nodes 106; or a "lower PHY" split in which RRC, PDCP, RLC, and MAC layers and upper portions of the PHY layer are operated by the CRAN/vBBUP and lower portions of the PHY layer are operated by individual RAN nodes 106. This virtualized framework allows the freed-up processor cores of the RAN nodes 106 to perform, for example, other virtualized applications. In some implementations, an individual RAN node 106 may represent individual gNB distributed units (DUs) that are connected to a gNB central unit (CU) using individual F1 interfaces (not shown in FIG. 1). In some implementations, the gNB-DUs can include one or more remote radio heads or RFEMs, and the gNB-CU may be operated by a server that is located in the RAN 112 (not shown) or by a server pool in a similar manner as the CRAN/vBBUP. Additionally or alternatively, one or more of the RAN nodes 106 may be next generation eNBs (ng-eNBs), including RAN nodes that provide E-UTRA user plane and control plane protocol terminations toward the UEs 102, and are connected to a 5G core network (e.g., core network 114) using a next generation interface. [0060] In vehicle-to-everything (V2X) scenarios, one or more of the RAN nodes 106 may be or act as RSUs. The term "Road Side Unit" or "RSU" refers to any transportation infrastructure entity used for V2X communications. A RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, where a RSU implemented in or by a UE may be referred to as a "UE-type RSU," a RSU implemented in or by an eNB may be referred to as an "eNB-type RSU," a RSU implemented in or by a gNB may be referred to as a "gNB-type RSU," and the like. In some implementations, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs 102 (vUEs 102). The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications or other software to sense and control ongoing vehicular and pedestrian traffic. The RSU may operate on the 5.9 GHz Direct Short Range Communications (DSRC) band to provide very low latency communications required for high speed events, such as Attorney Docket No. AE9962-PCT /1020.9962WO crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low latency communications, as well as other cellular communications services. Additionally or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) or provide connectivity to one or more cellular networks to provide uplink and downlink communications, or both. The computing device(s) and some or all of the radiofrequency circuitry of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and can include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network, or both. [0061] Any of the RAN nodes 106 can terminate the air interface protocol and can be the first point of contact for the UEs 102. In some implementations, any of the RAN nodes 106 can fulfill various logical functions for the RAN 112 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. [0062] In some implementations, the UEs 102 can be configured to communicate using orthogonal frequency division multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 106 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, OFDMA communication techniques (e.g., for downlink communications) or SC-FDMA communication techniques (e.g., for uplink communications), although the scope of the techniques described here not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers. [0063] The RAN nodes 106 can transmit to the UEs 102 over various channels. Various examples of downlink communication channels include Physical Broadcast Channel (PBCH), Physical Downlink Control Channel (PDCCH), and Physical Downlink Shared Channel (PDSCH). Other types of downlink channels are possible. The UEs 102 can transmit to the RAN nodes 106 over various channels. Various examples of uplink communication channels include Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), and Physical Random Access Channel (PRACH). Other types of uplink channels are possible. [0064] In some implementations, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 106 to the UEs 102, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot. Attorney Docket No. AE9962-PCT /1020.9962WO 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 a number of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block comprises a collection of resource elements; in the frequency domain, this may 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. [0065] The PDSCH carries user data and higher-layer signaling to the UEs 102. The PDCCH carries information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs 102 about the transport format, resource allocation, and hybrid automatic repeat request (HARQ) information related to the uplink shared channel. Downlink scheduling (e.g., assigning control and shared channel resource blocks to the UE 102b within a cell) may be performed at any of the RAN nodes 106 based on channel quality information fed back from any of the UEs 102. The downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 102. [0066] The PDCCH uses control channel elements (CCEs) to convey the control information. Before being mapped to resource elements, the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub- block interleaver for rate matching. In some implementations, each PDCCH may be transmitted using one or more of these CCEs, in which each CCE may correspond to nine sets of four physical resource elements collectively referred to as resource element groups (REGs). Four Quadrature Phase Shift Keying (QPSK) symbols may be mapped to each REG. The PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition. In LTE, there can be four or more different PDCCH formats defined with different numbers of CCEs (e.g., aggregation level, L=1, 2, 4, or 8). [0067] Some implementations may use concepts for resource allocation for control channel information that are an extension of the above-described concepts. For example, some implementations may utilize an enhanced PDCCH (EPDCCH) that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more Attorney Docket No. AE9962-PCT /1020.9962WO enhanced CCEs (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements collectively referred to as an enhanced REG (EREG). An ECCE may have other numbers of EREGs. [0068] The RAN nodes 106 are configured to communicate with one another using an interface 132. In examples, such as where the wireless communications system 100 is an LTE system (e.g., when the core network 114 is an evolved packet core (EPC) network), the interface 132 may be an X2 interface 132. The X2 interface may be defined between two or more RAN nodes 106 (e.g., two or more eNBs and the like) that connect to the EPC 114, or between two eNBs connecting to EPC 114, or both. 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 may provide flow control mechanisms for user data packets transferred over the X2 interface, and may be used to communicate information about the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information for user data transferred from a master eNB to a secondary eNB; information about successful in sequence delivery of PDCP protocol data units (PDUs) to a UE 102 from a secondary eNB for user data; information of PDCP PDUs that were not delivered to a UE 102; information about a current minimum desired buffer size at the secondary eNB for transmitting to the UE user data, among other information. The X2-C may provide intra- LTE access mobility functionality, including context transfers from source to target eNBs or user plane transport control; load management functionality; inter-cell interference coordination functionality, among other functionality. [0069] In some implementations, such as where the wireless communications system 100 is a 5G NR system (e.g., when the core network 114 is a 5G core network), the interface 132 may be an Xn interface 132. The Xn interface may be defined between two or more RAN nodes 106 (e.g., two or more gNBs and the like) that connect to the 5G core network 114, between a RAN node 106 (e.g., a gNB) connecting to the 5G core network 114 and an eNB, or between two eNBs connecting to the 5G core network 114, or combinations of them. In some implementations, the Xn interface can include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support/provide data forwarding and flow control functionality. The Xn-C may provide management and error handling functionality, functionality to manage the Xn-C interface; mobility support for UE 102 in a connected mode (e.g., CM- CONNECTED) including functionality to manage the UE mobility for connected mode between one or more RAN nodes 106, among other functionality. The mobility support can Attorney Docket No. AE9962-PCT /1020.9962WO include context transfer from an old (source) serving RAN node 106 to new (target) serving RAN node 106, and control of user plane tunnels between old (source) serving RAN node 106 to new (target) serving RAN node 106. A protocol stack of the Xn-U can include a transport network layer built on Internet Protocol (IP) transport layer, and a GPRS tunneling protocol for user plane (GTP-U) layer on top of a user datagram protocol (UDP) or IP layer(s), or both, to carry user plane PDUs. The Xn-C protocol stack can include an application layer signaling protocol (referred to as Xn Application Protocol (Xn-AP or XnAP)) and a transport network layer (TNL) that is built on a stream control transmission protocol (SCTP). The SCTP may be on top of an IP layer, and may provide the guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transmission is used to deliver the signaling PDUs. In other implementations, the Xn-U protocol stack or the Xn-C protocol stack, or both, may be same or similar to the user plane and/or control plane protocol stack(s) shown and described herein. [0070] The RAN 112 is shown to be communicatively coupled to a core network 114 (referred to as a "CN 114"). The CN 114 includes multiple network elements, such as network element 108a and network element 108b (collectively referred to as the "network elements 108"), which are configured to offer various data and telecommunications services to customers/subscribers (e.g., users of UEs 102) who are connected to the CN 114 using the RAN 112. The components of the CN 114 may be implemented in one physical node or separate physical nodes and can include 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 functions virtualization (NFV) may be used to virtualize some or all of the network node functions described here using executable instructions stored in one or more computer-readable storage mediums, as described in further detail below. A logical instantiation of the CN 114 may be referred to as a network slice, and a logical instantiation of a portion of the CN 114 may be referred to as a network sub-slice. NFV architectures and infrastructures may 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 network components or functions, or both. [0071] An application server 110 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS packet services (PS) domain, LTE PS data services, among others). The application server 110 can also be configured to support Attorney Docket No. AE9962-PCT /1020.9962WO one or more communication services (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, among others) for the UEs 102 using the CN 114. The application server 110 can use an IP communications interface 130 to communicate with one or more network elements 108a. [0072] In some implementations, the CN 114 may be a 5G core network (referred to as "5GC 114" or "5G core network 114"), and the RAN 112 may be connected with the CN 114 using a next generation interface 124. In some implementations, the next generation interface 124 may be split into two parts, a next generation user plane (NG-U) interface 114, which carries traffic data between the RAN nodes 106 and a user plane function (UPF), and the S1 control plane (NG-C) interface 126, which is a signaling interface between the RAN nodes 106 and access and mobility management functions (AMFs). Examples where the CN 114 is a 5G core network are discussed in more detail with regard to later figures. [0073] In some implementations, the CN 114 may be an EPC (referred to as "EPC 114" or the like), and the RAN 112 may be connected with the CN 114 using an S1 interface 124. In some implementations, the S1 interface 124 may be split into two parts, an S1 user plane (S1-U) interface 128, which carries traffic data between the RAN nodes 106 and the serving gateway (S-GW), and the S1-MME interface 126, which is a signaling interface between the RAN nodes 106 and mobility management entities (MMEs). [0074] As previously discussed, in some implementations, an individual RAN node 106 may be implemented as a gNB dual-architecture comprising multiple gNB-DUs that are connected to a gNB-CU using individual F1 interfaces. An example of a gNB dual- architecture for a RAN node 106 is shown in FIG. 2. [0075] FIG. 2 illustrates wireless communications system 200. The wireless communications system 200 is a sub-system of the wireless communications system 100 illustrated in FIG. 1. The wireless communications system 200 depicts a UE 202 connected to a gNB 204 over a connection 214. The UE 202 and connection 214 are similar to the UE 102 and the connections 118, 120 described with reference to FIG. 1. The gNB 204 is similar to the RAN node 106, and represents an implementation of the RAN node 106 as a gNB with a dual-architecture. [0076] As depicted in FIG. 2, the gNB 204 is divided into two physical entities referred to a centralized or central unit (CU) and a distributed unit (DU). The gNB 204 may comprise a gNB-CU 212 and one or more gNB-DU 210. The gNB-CU 212 is further divided into a gNB-CU control plane (gNB-CU-CP) 206 and a gNB-CU user plane (gNB-CU-UP) 208. The gNB-CU-CP 206 and the gNB-CU-UP 208 communicate over an E1 interface. The Attorney Docket No. AE9962-PCT /1020.9962WO gNB-CU-CP 206 communicates with one or more gNB-DU 210 over an F1-C interface. The gNB-CU-UP 208 communicates with the one or more gNB-DU 210 over an F1-U interface. [0077] In some implementations, there is a single gNB-CU 212 for each gNB 204 that controls multiple gNB-DU 210. For example, the gNB 204 may have more than 100 gNB- DU 210 connected to a single gNB-CU 212. Each gNB-DU 210 is able to support one or more cells, where one gNB 204 can potentially control hundreds of cells in a 5G NR system. [0078] The gNB-CU 212 is mainly involved in controlling and managing the overall network operations, performing tasks related to the control plane, such as connection establishment, mobility management, and signaling. It is responsible for non-real-time functionalities, which include policy decisions, routing, and session management among others. The gNB-CU-CP 206 and the gNB-CU-UP 208 provides support for higher layers of a protocol stack such as Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP) and RRC. [0079] The gNB-DU 210 is responsible for real-time, high-speed functions, such as the scheduling of radio resources, managing the data plane, and performing error handling and retransmissions. The gNB-DU 210 provides support for lower layers of the protocol stack such as Radio Link Control (RLC), MAC layer, and PHY layer. [0080] As depicted in FIG. 2, the gNB-DU 210 includes a scheduler 218. In the wireless communications system 100 and/or the wireless communications system 200, scheduling of measurement gaps for UE 202, including their configuration and allocation, is primarily handled by the base station of the serving cell, by the scheduler 218. The scheduler 218 is involved in real-time operations and is responsible for making immediate decisions regarding the allocation of radio resources, managing interference, and adhering to Quality of Service (QoS) requirements for different services and users. The scheduler 218 within the gNB-DU 210 makes decisions about resource allocation, including when and how to schedule measurement gaps for the UE 202. It considers the capabilities of the UE 202, mobility state, quality of service requirements, and current network conditions, among other factors. [0081] Based on scheduling decisions, the gNB-DU 210 sends configuration information to the UE 202, instructing it when to perform measurements by allocating specific time intervals as measurement gaps. This information is usually conveyed through Radio Resource Control (RRC) messages, such as RRC Reconfiguration messages, among other Attorney Docket No. AE9962-PCT /1020.9962WO types of messages. The RRC layer is responsible for managing the signaling between the UE 202 and the gNB-DU 210, including the signaling related to the configuration of measurement gaps. The RRC layer in the gNB-DU 210 thus plays a crucial role in orchestrating the scheduling and allocation of measurement gaps based on decisions made by the scheduler 218. After receiving the configuration, the UE 202 performs measurements during the allocated gaps and reports the results back to the network, enabling the gNB-DU 210 to make further decisions, such as handovers or beam adjustments. [0082] Although the scheduler is located within the gNB-DU, it frequently interacts with the gNB-CU. The gNB-CU provides the necessary control and configuration information to the gNB-DU, which it uses to make real-time scheduling decisions and manage radio resources effectively. The configuration, policies, and user-specific QoS parameters provided by the gNB-CU aid the scheduler 218 in the gNB-DU to allocate resources and manage user traffic efficiently, catering to diverse service requirements in 5G and 6G networks. [0083] FIG. 3 illustrates an operating environment 300. The operating environment 300 illustrates operations for the wireless communications system 100 and/or the wireless communications system 200. [0084] As depicted in FIG. 3, the UE 202 is in communication with a set of RAN nodes, such as RAN node 1308 and RAN node 2310, which are similar to RAN node 106a and RAN node 106b, respectively. For example, the RAN node 1308 may comprise a serving cell (e.g., a PCell) for the UE 202 and the RAN node 2310 may comprise a neighbor cell (e.g., SCell) for the UE 202. The UE 202 may comprise a mobile device moving between communication envelopes for the RAN node 1308 and the RAN node 2310, and therefore the UE 202 may need to perform measurements of intra-frequency or inter-frequency signals for handover operations, beamforming operations, or other UE and/or network operations. [0085] The UE 202 may communicate with the scheduler 218 to coordinate measurement operations for the UE 202. The UE 202 may send UE capability information 302 to the scheduler 218. The scheduler 218 may receive the UE capability information 302, and generate UE configuration information 304 for the UE 202. The scheduler 218 may send the UE configuration information 304 to the UE 202. The UE 202 may configure its measurement operations in accordance with the UE configuration information 304. The UE 202 may then take measurements of for various measurement objects (MOs) associated with the RAN node 1308 and/or the RAN node 2310. The UE 202 may send the UE Attorney Docket No. AE9962-PCT /1020.9962WO measurement information 306 to the scheduler 218. The scheduler 218 may then update network settings and send new control directives to the UE 202 based on the UE measurement information 306. [0086] During RRC connection setup, the UE 202 sends an RRC Connection Request message to the gNB 204. The RRC Connection Request includes information such as a UE identity and establishment cause (e.g., mo-data, mo-signalling, etc.). Upon receiving the RRC Connection Request message and after processing it, the gNB 204 sends an RRC Connection Setup message to the UE 202. This message carries the initial configuration for the UE 202, including a Signalling Radio Bearer 1 (SRB1) configuration and other parameters necessary for the UE 202 to communicate in RRC Connected mode. SRB1 is used for transmitting RRC and Non-Access Stratum (NAS) messages. Once the UE 202 receives and processes the RRC Connection Setup message, it moves to the RRC Connected state and responds with an RRC Connection Setup Complete message. This message usually carries the selected public land mobile network identifier (PLMN-ID) and initial NAS message, which typically includes the Service Request message or Attach Request message to initiate NAS level procedures for network attachment and service accessibility. The RRC Connection Setup process results in the establishment of SRB1, allowing the UE 202 and gNB 204 to exchange RRC and NAS messages. The UE moves from RRC Idle state to RRC Connected state, enabling it to initiate the NAS procedures to access network services. The initial configurations provided in the RRC Connection Setup message will enable the UE 202 to communicate with the network in the RRC Connected state effectively. [0087] Sometime during or after RRC connection setup, the UE 202 sends UE configuration information 304 to the gNB 204. The UE capability information 302 includes measurement information 312 about UE capabilities, including whether the UE 202 is capable of communicating with or without measurement gaps. The UE capability information 302 may include measurement information 312, interruption information 314, or a combination of measurement information 312 and interruption information 314. [0088] The measurement information 312 may comprise information describing measurement capabilities of the UE 202, including whether the UE 202 needs measurement gaps or is capable of operating without measurement gaps. For example, the UE 202 may be equipped with advanced receivers capable of performing measurements on different frequency simultaneously without needing to interrupt the primary serving cell communication, multiple antennas and advanced signal processing to manage concurrent reception from different cells or frequencies allowing seamless measurements, parallel Attorney Docket No. AE9962-PCT /1020.9962WO processing capabilities to allow a UE to handle multiple tasks concurrently, enhanced measurement reporting capabilities, and advanced interference measurement techniques to enable the UE 202 to isolate and filter out interference while performing measurements. The UE 202 may include such capabilities to support measurement operations without a measurement gap in the measurement information 312. Alternatively, the measurement information 312 may include one or more values to indicate whether it requires a measurement gap or does not require a measurement gap. [0089] The interruption information 314 may comprise information describing interrupts when the UE 202 is capable of performing measurement operations without a measurement gap, such as information that indicates when the UE 202 explicitly requests interruption or no interruption during measurement operations. In many cases, this decision is left to the scheduler 218 to optimize network resources for all UEs in a system. In some cases, however, the UE 202 may explicitly or implicitly request interrupts and interrupt requirements based on its particular configuration. [0090] While the UE 202 is capable of sending interruption information 314, the UE 202 does not necessarily need to send interruption information 314. The scheduler 218 may be arranged to infer or deduct the interruption information 314 based on the measurement information 312 received from the UE 202 by the scheduler 218. For example, the scheduler 218 is capable of inferring or deducing the interruption information 314 based on one or more values contained within the measurement information 312, such as specific values enumerated for one or more IEs as defined in 3GPP 38.133 and/or 3GPP 38.331 Release 17 and/or Release 18 standards, some examples of which are described below. [0091] In one embodiment, for example, the UE 202 communicates whether or not it needs measurement gaps to the network using a defined information element (IE) of a control message. For example, 3GPP TS 38.331 Release 17 defines an IE referred to as a NeedForGapsInfoNR IE to serve as a mechanism for a UE to communicate to the network whether it requires measurement gaps to perform inter-frequency and intra-frequency measurements. Similarly, 3GPP TS 38.331 Release 17 defines an IE referred to as a NeedForNCSG-InfoNR IE for NCSG. Both the NeedForGapsInfoNR IE and the NeedForNCSG-InfoNR IE include various defined data fields, one of which is a gapIndication field, for example. [0092] For the NeedForGapsInfoNR IE, the gapIndication field indicates whether a measurement gap is required for the UE to perform synchronization signal block (SSB) based measurements on the concerned NR target band while NR dual-connectivity (NR-DC) Attorney Docket No. AE9962-PCT /1020.9962WO or NR evolved universal terrestrial radio access network (E-UTRAN) dual connectivity (NE-DC) is not configured. The UE determines this information based on the resultant configuration of the RRCReconfiguration or RRCResume message that triggers this response. The gapIndication field carries one of two enumerated values {gap, no-gap}, where the first value gap indicates that a measurement gap is needed, and the second value no-gap indicates a measurement gap is not needed. [0093] For the NeedForNCSG-InfoNR IE, the gapIndication field indicates whether measurement gap or NCSG is required for the UE to perform SSB based measurements on the concerned NR target band while NR-DC or NE-DC is not configured. The UE determines this information based on the resultant configuration of the RRCReconfiguration or RRCResume message that triggers this response. The gapIndication field carries one of three enumerated values {gap, ncsg, nogap-noncsg}, where the first value gap indicates that a measurement gap is needed, the second value ncsg indicates that a NCSG is needed, and the third value nogap-noncsg indicates neither a measurement gap nor a NCSG is needed. [0094] As previously discussed, embodiments attempt to define enhanced UE capability on UE measurements with pre-configured gaps in 5G NR and 6G. More particularly, embodiments define UE capability on UE measurements for measurement gaps, including NCSG, when a UE reports a UE capability of measurement without gaps. Examples of measurements without gaps include indications of “no-gap” and/or “nogap-noncsg” in network messages, such as RRM messages, which indicate that a UE does not need a measurement gap to perform inter-frequency or intra-frequency measurements. Stated another way, the UE has a UE capability of supporting normal communications and measurement operations simultaneously. Embodiments are not limited to these examples. [0095] One embodiment, for example, attempts to more clearly define UE behavior on interruption requirements when a UE reports a UE capability of measurement without gaps. Embodiments define UE behavior based on three different observations. [0096] The first observation is when a UE indicates a defined IE such as NeedForNCSG- NR the exact interruption requirements may be conducted. Similarly, if a UE needs to support the “NeedForGapsInfoNR” for the measurements without gaps, the necessary interruption requirements for UE can be also defined. However, there remains some unresolved ambiguities when a UE reports with “no-gap”. One ambiguity is whether a UE reporting “no-gap” means neither NCSG nor legacy measurement gap beyond Release 17 is needed for the NeedForGapsInfoNR IE. Attorney Docket No. AE9962-PCT /1020.9962WO [0097] The second observation is when a UE indicates “no-gap” in the NeedForGapsInfoNR IE, it is ambiguous in the legacy specifications as to whether neither NCSGs nor legacy measurement gaps are to be configured by the network. If the indication “no-gap” in NeedForGapsInfoNR IE means neither NCSG nor legacy measurement gaps are needed from a UE perspective, the interruption may not be allowed. However, in 3GPP TS 38.331 Release 17, the “no-gap” indication in “NeedForNCSG-NR” seems to have an alternative, or at least, an ambiguous interpretation. [0098] The third observation is how to define the interruption requirements need RAN2 further clarification on the indication of “no-gap” in NeedForGapsNR message, such as whether it is consistent with that in “NeedForNCSG-NR” IE. [0099] From a RAN4 perspective, in order to more clearly define UE behaviors on the interruption requirements, a similar mechanism in Release 17 NCSG can be adopted. For instance, if the “nogap-nointerruption” is reported in NeedForGapsInfoNR IE, the UE behaviors can be explicitly defined as: (1) measurement without gap; and (2) no interruption allowed. This addresses the first open issue of whether an interruption is expected when a UE reports “no-gap” by introducing additional UE capability to differentiate whether the UE needs interruption. This also addresses the second open issue of interruption requirement when an interruption is allowed by starting with NCSG as a base case and FFS the exact values needed. Embodiments clearly define UE behavior on interruption requirements when a UE reports a UE capability of measurement without gaps. [0100] In a first embodiment, for example, the UE 202 may send the UE capability information 302 with measurement information 312 to the scheduler 218. The scheduler 218 may infer interruption information 314 from the measurement information 312. The measurement information 312 may include measurement capabilities or preferences of the UE 202. The measurement information 312 may optionally include implicit or explicit interruption information 314 associated with the measurement information 312. The interruption information 314 may include implicit or explicit requests for interruptions and/or associated interruption requirements when a UE 202 is performing measurements, such as SSB measurements without gap. In one embodiment, the UE capability information 302 may include the NeedForGapsInfoNR IE, with data fields and values as defined in Table 1 as follows: [0101] TABLE 1 Attorney Docket No. AE9962-PCT /1020.9962WO Network Case A: configuration for No measurement gap (MG) UE capability of “NeedForGap” gap No requirements no-gap Measurements out of gap, interruption allowed, and interruption requirements defined in 3GPP TS38.1339.1.9[3] nogap-noncsg Measurements out of gap, No interruption allowed [0102] In a second embodiment, for example, the UE capability information 302 may include custom or specially defined IEs to convey capability information, such as measurement information 312 and/or interruption information 314. For example, assume the UE capability information 302 includes a NeedForGapsInfoNR IE, that includes a set of data fields to carry one or more values representing a set of capabilities denoted as {capability 1, capability 2, capability 3,..., capability N}, where N represents any positive integer. In one embodiment, [capability 1] is one or more values that indicate interruption is allowed, and [capability 2] is one or more values that indicate no interruption is allowed. When the UE 202 reports “[capability 1]” to indicate that interruption is allowed, the interruption should be allowed for each of intra-frequency and inter-frequency measurements for which the UE reports “[capability 1]”. The interruption will impact all the serving cells if UE 202 does not support per-frequency range (FR) gap, and all the serving cells in the same FR as the measurement if UE 202 supports per-FR gap. When the UE 202 reports “[capability 2]” to indicate no interruption allowed, the interruption is not allowed for each of intra-frequency and inter-frequency measurements for which the UE 202 reports “[capability 2]”. The other capabilities N may be defined for interruption and interruption requirements for other use cases, as needed for a given implementation. [0103] In a third embodiment, a new IE is defined for communication between the UE and the network to indicate interruption information. In one example, the new IE may be Attorney Docket No. AE9962-PCT /1020.9962WO referred to as a NeedForInterruptionInfoNR-R18 IE. Embodiments are not limited to this particular name or associated information fields. This new IE carries information indicating when interruptions are allowed or not allowed, and interruption requirements for when interruptions are allowed, among other types of interruption and/or capabilities information. [0104] The new IE named NeedForInterruptionInfoNR-R18 IE introduces new interruption requirements that apply when the UE 202 is capable of communicating a NeedforGapInfoNR. The new IE carries information to measure inter-frequency MOs without measurement gap but with interruptions. The new IE introduces an interruption length and/or ratio allowed for the UE 202 measuring inter-frequency MOs without measurement gap but with interruptions. An example of the NeedForInterruptionInfoNR- R18 IE is proposed for inclusion in 3GPP 38.133 Release 18, as detailed below. [0105] 8.2.2.2.X Interruptions due to measurements without gap carried out by UE supporting [NeedForInterruptionInfoNR-R18] [0106] When a UE supports [NeedForInterruptionInfoNR-R18] measurements and indicates [no-gap-with-interruption] on intra-frequency SSB-based or inter-frequency SSB- based measurements the UE is allowed to cause interruptions while performing measurements on the frequency layer for which [no-gap-with-interruption] is indicated. [0107] The UE is allowed to cause interruption with interruption ratio no more than the requirements specified below upon UE measurements on a specific frequency layer that corresponds to the configured MO, where Tcycle is [FFS]. [0108] - up to [2.50%] probability of missed ACK/NACK when 80ms ≤ Tcycle < 160ms, or [0109] - up to [1.25%] probability of missed ACK/NACK when 160ms ≤ Tcycle < 320ms, or [0110] - up to [0.625%] probability of missed ACK/NACK when 320ms ≤ Tcycle. [0111] The interruptions are allowed for all the serving cells in the same FR as NR MO being measured if UE supports per-FR measurement gaps, and all the serving cells if UE does not support per-FR measurement gaps. [0112] Table 8.2.2.2.X-1: Interruption length X SCS (kHz) NR Slot Interruption length X (slots) length (ms) Attorney Docket No. AE9962-PCT /1020.9962WO 0 15 1 TBD 1 30 0.5 TBD 2 60 0.25 TBD 3 120 0.125 TBD [0113] Editors’ note: Discussion is ongoing on cases where DRX or measurement gap is configured. Further update to this sub-clause subjects to the conclusions of those discussions. [0114] Editors’ note2: Definition of Tcycle resembles measurement cycle definition in the measurement period requirements. [0115] Editors’ note3: Total interruption ratio requirements will be updated subject to further conclusions. [0116] FIG. 4 illustrates a more detailed view of a data schema 400 or messaging format suitable for communicating the UE capability information 302. As depicted in FIG. 4, the UE 202 may communicate UE capability information 302 including measurement information 312 and/or the interruption information 314 in message defined in accordance with one or more 3GPP standards, such as 3GPP TS 38.133 Standards, for example. [0117] The UE capability information 302 may be carried by a network message comprising an information element 402. Examples of network messages and/or information element 402 may include without limitation any network messages with a NeedForGapsNR IE, NeedForNCSG-NR IE, NeedForNCSG-InfoNR IE, NeedForInterruptionInfoNR-R18 IE, and other 3GPP defined messages and/or information elements. Examples of configuration value 404 may include without limitation a gap value 406, a no-gap value 408, a ncsg value 410, a nogap-noncsg value 412, an interruption value 414, a no interruption value 416, a no-gap-with-interruption value 418, and a no-gap- without-interruption value 420. Each of the gap value 406, no-gap value 408, ncsg value 410 and nogap-noncsg value 412 may comply with corresponding values defined in 3GPP 38.133 or 38.331 Standards. The interruption value 414, the no interruption value 416, the no-gap-with-interruption value 418, and the no-gap-without-interruption value 420 are new values that explicitly denote when the UE 202 is capable of handling interruptions or cannot Attorney Docket No. AE9962-PCT /1020.9962WO handle interruptions while performing measurement operations. Embodiments are not limited to these examples. [0118] FIG. 5 illustrates an apparatus 500 suitable for implementation as a UE 202 in the wireless communications system 100. As previously discussed, the UE 202 may take measurements and actions based on one or more measurement criteria as defined by the 3GPP TS 38.133 Standards, the 3GPP TS 38.504 Standards, the 3GPP TS 38.331 Standards, or other 3GPP standards or non-3GPP standards. Embodiments are not limited in this context. [0119] As depicted in FIG. 5, the apparatus 500 may comprise a processor circuitry 504, a memory 508 with a measurement manager 514, a memory interface 520, a data storage device 526, and radio-frequency (RF) circuitry 522. The apparatus 500 may optionally include a set of platform components (not shown) suitable for a UE 102a, such as input/output devices, memory controllers, different memory types, network interfaces, hardware ports, and so forth. [0120] The apparatus 500 for the UE 202 may receive one or more measurement object 510 from a base station 524 via the RF circuitry 522. The base station 524 may comprise a RAN node 106a or a RAN node 106b implemented as, for example, a NodeB or an eNodeB of the wireless communications system 100. [0121] The measurement object 510 refers to a specific entity or parameter that is being measured or monitored by the UE 202. It represents a target for measurement or evaluation within the radio frequency (RF) environment. The measurement object 510 is used in the context of various measurement procedures and functions within the 5G network. Examples for the measurement object 510 includes measurements for: (1) signal quality, signal strength, or other relevant parameters of serving cells and neighboring cells to assist in handover decisions and interference management; (2) reference signals received from the gNB 204 or cells in the vicinity to estimate signal quality, timing, and other characteristics for purposes like beamforming, channel estimation, or synchronization; (3) radio resource blocks (RBs) to determine quality or interference level of specific RBs to evaluate the suitability for data transmission; (4) channel quality indicators (CQIs) for channel conditions to provide feedback to the gNB 204, which aids in link adaptation and scheduling decisions; (5) interference levels caused by neighboring cells or sources to assess the impact on the communication link; and (6) parameters related to movement, speed, velocity, or path-loss to assist handover, location-based services, or mobility management. These are just a few examples of a measurement object 510 in 5G or 6G. Measurement object 510 is Attorney Docket No. AE9962-PCT /1020.9962WO used for performance monitoring, network optimization, and providing relevant information for efficient and reliable communication in the network. [0122] For example, the measurement object 510 may include the reference signals communicated between the UE 202 and the RAN node 1308 and the RAN node 2310, respectively. In this case, the measurement object 510 may comprise, for example, reference signals for SS-RSRP measurement, reference signals for SS-RSRQ measurement, BFD reference signals, RLM reference signals, SDT reference signals, or any other signals suitable for measurement or relaxed measurement in the wireless communications system 100. [0123] The apparatus 500 for the UE 202 may include the memory interface 520. The memory interface 520 may be arranged to send or receive, to or from a data storage device 526 or a data storage device 530, measurement information 512 for a 5G NR system. The data storage device 530 may be located external to the UE 202 (off-device) and the data storage device 526 may be located internal to the UE 202 (on-device). When the data storage device 526 is implemented on-device, the data storage device 526 may comprise volatile or non-volatile memory, as described in more detail with reference to FIG. 11. [0124] The measurement information 512 may comprise one or more measurement values 506 as measured by the measurement generator 502 and/or measurement criteria 516 for the UE 202. The UE 202 may be provisioned with the measurement criteria 516 by an original equipment manufacturer (OEM) or as received from the base station 524 via RRM, RRC, or other control signaling. [0125] The apparatus 500 may include processor circuitry 504 communicatively coupled to the memory 508, the memory interface 520, the data storage device 526 and the RF circuitry 522. The memory 508 may store instructions that when executed by the processor circuitry 504 may implement or manage a measurement manager 514 for the UE 202. The measurement manager 514 may include a measurement generator 502, a measurement inferencer 518, and measurement information 512. The measurement information 512 may include, for example, measurement values 506 and measurement criteria 516. [0126] The measurement generator 502 may perform measurements of one or more measurement object 510 received from a base station 524 of a cell, such as a serving cell and/or a neighbor cell, to obtain one or more measurement values 506. The measurement inferencer 518 may retrieve one or more measurement criterion or relaxed measurement criterion from a set of measurement criteria 516 associated with the UE 202. The measurement inferencer 518 may evaluate the one or more measurement values 506 in Attorney Docket No. AE9962-PCT /1020.9962WO accordance with the one or more measurement criterion or relaxed measurement criterion of the measurement criteria 516 to obtain a measurement result 528. For instance, the measurement inferencer 518 may use a mathematical comparison operation to compare the measurement values 506 with the measurement criteria 516 to determine whether the measurement values 506 are equal to, greater than or less than the measurement criteria 516. The measurement inferencer 518 may store the measurement result 528 in the data storage device 526 and/or the data storage device 530. [0127] The measurement inferencer 518 may take an action for the UE 202 based on the measurement result 528. For instance, the processor circuitry 504 may determine whether to select the base station 524 of the cell as a serving cell for the UE 202 based on the measurement results 528. In another example, the processor circuitry 504 may determine whether to search for a base station of a neighbor cell of the cell as a serving cell for the UE 202 based on the measurement results 528. In yet another example, the processor circuitry 504 may determine whether to request a change in beamforming parameters based on the measurement results 528. In still another example, the processor circuitry 504 may request a change in transmission power parameters based on the measurement results 528. In still another example, the processor circuitry 504 may determine whether to initiate network operations based on the measurement results 528. It may be appreciated that the UE 202 may take other actions based on the measurement results 528 as defined in 3GPP or non- 3GPP standards. Embodiments are not limited in this context. [0128] In one embodiment, for example, the apparatus 500 may also include the processor circuitry 504 to perform synchronization signal based reference signal received power (SS- RSRP) measurements or synchronization signal based reference signal received quality (SS- RSRQ) measurements for a parameter of the UE 202. [0129] In one embodiment, for example, the apparatus 500 may also include where the cell is an intra-frequency NR cell, an inter-frequency NR cell, or an inter-radio access technology (RAT) evolved universal terrestrial radio access network (E-UTRAN) cell. [0130] As previously discussed, the UE 102a may take measurements and actions based on one or more measurement criteria as defined by the 3GPP TS 38.133 Standards, the 3GPP TS 38.504 Standards, the 3GPP TS 38.331 Standards, or other 3GPP standards or non-3GPP standards. [0131] FIG. 6 illustrates an apparatus 600 suitable for implementation as a base station 602 in the wireless communications system 100 and/or the wireless communications system 200. The base station 602 is an example of the gNB 204. As previously discussed, the base Attorney Docket No. AE9962-PCT /1020.9962WO station 602 may receive UE capability information 302 and/or UE measurement information 306 from the UE 202. The base station 602 may send UE configuration information 304 to the UE 202. [0132] As depicted in FIG. 6, the apparatus 600 may comprise a processor circuitry 604, a memory 606 with a scheduler 218, a memory interface 630, a data storage device 632, and RF circuitry 634. The apparatus 600 may optionally include a set of platform components (not shown) suitable for a UE 202, such as input/output devices, memory controllers, different memory types, network interfaces, hardware ports, and so forth. [0133] The base station 602 includes a memory interface 630 to send or receive, to or from a data storage device 632, measurement information 312 and/or measurement information 614 for a wireless communications system 100 and/or the wireless communications system 200. The base station 602 also includes processor circuitry 604 communicatively coupled to the memory interface 630, the processor circuitry 604 to execute a decoder 608 to decode a message from a UE 202 with UE capability information 302. The UE capability information 302 may comprise an information element 402 with a configuration value 404 to indicate whether the UE supports measurements of a measurement object 510 without a measurement gap 612. A schedule manager 610 may determine whether the configuration value 404 for the information element 402 indicates the UE 202 supports measurements of the measurement object 510 with or without the measurement gap 612. [0134] When the schedule manager 610 determines the UE 202 supports measurements of the measurement object 510 with the measurement gap 612, the schedule manager 610 schedules a measurement gap 612 for the UE 202. The schedule manager 610 then includes the measurement gap 612 in UE configuration information 304, and forwards the UE configuration information 304 to the UE 202. [0135] When the schedule manager 610 determines the UE 202 supports measurements of the measurement object 510 without the measurement gap 612, the schedule manager 610 determines whether the UE 202 is allowed to cause interruptions while performing measurements of the measurement object 510 without the measurement gap 612 based on the configuration value 404. In one embodiment, the schedule manager 610 makes this determination based on the interruption information 314. The interruption information 314 may include the values as defined in Table 1 or for the defined capability sets, such as capability 1, capability 2,..., capability N, for example. [0136] The base station 602 may also include where the message includes a NeedForGapsInfoNR information element 402 and the configuration value 404 includes a Attorney Docket No. AE9962-PCT /1020.9962WO no-gap value 408. The schedule manager 610 may further determines the UE 202 is allowed to cause interruptions while performing measurements of the measurement object 510, where the measurement object 510 includes a synchronization signal block (SSB), based on the interruption information 314. [0137] The base station 602 may also include where the message includes a NeedForGapsInfoNR information element 402 and the configuration value 404 includes a nogap-noncsg value 412. The schedule manager 610 further determines the UE 202 is not allowed to cause interruptions while performing measurements of the measurement object 510. [0138] The base station 602 may also include where the message includes a NeedForNCSG-NR information element and the configuration value 404 includes a nogap- noncsg value 412. The schedule manager 610 further determines the UE 202 is not allowed to cause interruptions while performing measurements of the measurement object 510, based on the interruption information 314. [0139] The base station 602 may also include where the configuration value 404 includes a first configuration value 404 to indicate the UE 202 is allowed to cause interruptions while performing measurements of the measurement object 510, where the measurement object 510 includes intra-frequency or inter-frequency signals for which the UE 202 reports. [0140] The base station 602 may also include where the configuration value 404 includes a second configuration value 404 to indicate the UE 202 is not allowed to cause interruptions while performing measurements of the measurement object 510, where the measurement object 510 includes intra-frequency or inter-frequency signals for which the UE 202 reports. [0141] The base station 602 may also include where the message includes a NeedForInterruptionInfoNR information element 402 and the configuration value 404 includes a no-gap-with-interruption value 418. The schedule manager 610 to further determine the UE 202 is allowed to cause interruptions while performing measurements of the measurement object 510, where the measurement object 510 includes an intra-frequency synchronization signal block (SSB) or an inter-frequency SSB on a frequency layer for which the no-gap-with-interruption value 418 is indicated. [0142] The base station 602 may also include where the message includes a NeedForInterruptionInfoNR information element 402 and the configuration value 404 includes a no-gap-with-interruption value 418. The schedule manager 610 to further determine the UE 202 is allowed to cause interruptions while performing measurements of the measurement object 510, where the interruptions have a defined interruption ratio. For Attorney Docket No. AE9962-PCT /1020.9962WO example, the UE 202 is allowed to cause interruption with an interruption ratio of no more than the requirements specified below upon UE 202 measurements on a specific frequency layer that corresponds to the configured measurement object 510, where Tcycle is [FFS]. [0143] - up to [2.50%] probability of missed ACK/NACK when 80ms ≤ Tcycle < 160ms, or [0144] - up to [1.25%] probability of missed ACK/NACK when 160ms ≤ Tcycle < 320ms, or [0145] - up to [0.625%] probability of missed ACK/NACK when 320ms ≤ Tcycle. [0146] The base station 602 may also include where the message includes a NeedForInterruptionInfoNR information element 402 and the configuration value 404 includes a no-gap-with-interruption value 418. The schedule manager 610 to further determine the UE 202 is allowed to cause interruptions while performing measurements of the measurement object 510, where the interruptions allowed for all serving cells in a same frequency range (FR) as the measurement object 510 being measured when the UE 202 supports per-FR measurement gaps, and all serving cells when the UE 202 does not support per-FR measurement gaps. [0147] The base station 602 may also include where the message includes a NeedForInterruptionInfoNR information element 402 and the configuration value 404 includes a no-gap-without-interruption value 420. The schedule manager 610 to further determine the UE 202 is not allowed to cause interruptions while performing measurements of the measurement object 510. [0148] Once the decoder 608 of the base station 602 receives and decodes the UE capability information 302, and it retrieves the measurement information 312 and/or interruption information 314, the schedule manager 610 may then determine whether to schedule a measurement gap 612 or not schedule a measurement gap 612 for the UE 202. The schedule manager 610 may generate UE configuration information 304, and send to the UE configuration information 304 to the UE 202. The UE 202 receives the UE configuration information 304, and performs measurement operations in accordance with the UE configuration information 304 to support various network operations, such as handover operations, among others. [0149] Operations for the disclosed embodiments may be further described with reference to the following figures. Some of the figures may include a logic flow. Although such figures presented herein may include a particular logic flow, it can be appreciated that the Attorney Docket No. AE9962-PCT /1020.9962WO logic flow merely provides an example of how the general functionality as described herein can be implemented. Further, a given logic flow does not necessarily have to be executed in the order presented unless otherwise indicated. Moreover, not all acts illustrated in a logic flow may be required in some embodiments. In addition, the given logic flow may be implemented by a hardware element, a software element executed by a processor, or any combination thereof. The embodiments are not limited in this context. [0150] FIG. 7 illustrates an embodiment of a logic flow 700. The logic flow 700 may be representative of some or all of the operations executed by one or more embodiments described herein. For example, the logic flow 700 may include some or all of the operations performed by devices or entities within the wireless communications system 100 and/or the wireless communications system 200, such as the base station 602 and/or the gNB 204. More particularly, the logic flow 700 illustrates a use case where the base station 602 may use the UE capability information 302 carried by the information element 402 to perform scheduling for measurement operations made by the UE 202. Embodiments are not limited in this context. [0151] In block 702, logic flow 700 decodes a message from user equipment (UE) with UE capability information, the UE capability information to comprise an information element with a configuration value to indicate whether the UE supports measurements of a measurement object without a measurement gap. In block 704, logic flow 700 determines the configuration value for the information element indicates the UE supports measurements of the measurement object without the measurement gap. In block 706, logic flow 700 determines whether the UE is allowed to cause interruptions while performing measurements of the measurement object without the measurement gap based on the configuration value. [0152] By way of example, with reference to base station 602, the decoder 608 decodes a message from UE 202 with UE capability information 302, the UE capability information 302 to comprise an information element 402 with a configuration value 404 to indicate whether the UE 202 supports measurements of a measurement object 510 without a measurement gap 612. The schedule manager 610 determines the configuration value 404 for the information element 402 indicates the UE 202 supports measurements of the measurement object 510 without the measurement gap 612. The schedule manager 610 determines whether the UE 202 is allowed to cause interruptions while performing measurements of the measurement object 510 without the measurement gap 612 based on the configuration value 404 and associated interruption information 314. The interruption Attorney Docket No. AE9962-PCT /1020.9962WO information 314 may be part of the information element 402 or stored in the base station 602 and/or data storage device 632. [0153] FIG. 8 illustrates an embodiment of a logic flow 800. The logic flow 800 may be representative of some or all of the operations executed by one or more embodiments described herein. For example, the logic flow 800 may include some or all of the operations performed by devices or entities within the wireless communications system 100 and/or the wireless communications system 200, such as the UE 202, for example. More particularly, the logic flow 800 illustrates a use case where the UE 202 may generate and send the UE capability information 302 carried by the information element 402 to the base station 602 so that the base station 602 may perform scheduling for measurement operations conducted by the UE 202. Embodiments are not limited in this context. [0154] In block 802, logic flow 800 receives a message requesting UE capability information from user equipment (UE). In block 804, logic flow 800 determines the UE capability information for the UE. In block 806, logic flow 800 generates a message with the UE capability information, the UE capability information to comprise an information element with a configuration value to indicate whether the UE supports measurements of a measurement object without a measurement gap. In one embodiment, the logic flow 800 selects the configuration value for the information element to indicate the UE supports measurements of the measurement object with the measurement gap. In one embodiment, the logic flow 800 selects the configuration value for the information element to indicate the UE supports measurements of the measurement object without the measurement gap. In one embodiment, the logic flow 800 optionally adds a configuration value to indicate whether the UE is allowed to cause interruptions while performing measurements of the measurement object without the measurement gap. In block 808, the logic flow 800 sends the message with the UE capability information to a base station. [0155] By way of example, with reference to UE 202, the UE 202 receives a message requesting UE capability information 302 for user equipment (UE) from a base station 602. In one embodiment, the message may optionally include a measurement object 510 which the UE 202 may use to perform measurements. The measurement manager 514 determines the UE capability information 302 for the UE 202. The measurement manager 514 generates a message with the UE capability information 302, the UE capability information 302 to comprise an information element 402 with a configuration value 404 to indicate whether the UE 202 supports measurements of a measurement object 510 with a measurement gap 612 or without a measurement gap 612. In one embodiment, the measurement manager 514 Attorney Docket No. AE9962-PCT /1020.9962WO selects the configuration value 404 for the information element 402 to indicate the UE 202 supports measurements of the measurement object 510 with the measurement gap 612. In one embodiment, the measurement manager 514 selects the configuration value 404 for the information element 402 to indicate the UE 202 supports measurements of the measurement object 510 without the measurement gap 612. In one embodiment, measurement manager 514 optionally adds a configuration value 404 to indicate whether the UE 202 is allowed to cause interruptions while performing measurements of the measurement object 510 without the measurement gap 612 based on interruption information 314 stored by the UE 202 and/or the data storage device 530. The measurement manager 514 sends the message with the UE capability information 302 to the base station 602. [0156] Once the base station 602 receives and decodes the UE capability information 302, the base station 602 determines whether the configuration value 404 indicates measurement with the measurement gap 612 or without the measurement gap 612. When the configuration value 404 indicates measurement without the measurement gap 612, the base station 602 determines whether the measurement without the measurement gap 612 includes interruptions or does not include interruptions, based on the interruption information 314. When the base station determines the measurement without the measurement gap 612 includes interruptions, it then determines interruption requirements for the interruptions, based on the interruption information 314. The base station 602 then encodes this information into a message with UE configuration information 304, and it sends the UE configuration information 304 to the UE 202. [0157] Once the UE 202 receives and decodes the UE configuration information 304, the UE 202 conducts measurements operations on the measurement object 510 in accordance with the UE configuration information 304. The UE 202 periodically sends a message with UE measurement information 306 to convey the measurement results to the base station 602. The base station 602 receives and decodes the UE measurement information 306, and updates network settings and optimizes network performance based on the UE measurement information 306. This may include sending new UE configuration information 304 to the UE 202 to modify measurement operations conducted by the UE 202. [0158] FIGS. 9-12 illustrate various systems, devices and components that may implement aspects of disclosed embodiments. The systems, devices, and components may be the same, or similar to, the systems, device and components described with reference to FIG. 1. [0159] FIG. 9 illustrates a network 900 in accordance with various embodiments. The network 900 may operate in a manner consistent with 3GPP technical specifications for Attorney Docket No. AE9962-PCT /1020.9962WO LTE or 5G/NR systems. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like. [0160] The network 900 may include a UE 902, which may include any mobile or non- mobile computing device designed to communicate with a RAN 930 via an over-the-air connection. The UE 902 may be communicatively coupled with the RAN 930 by a Uu interface. The UE 902 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in- car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, IoT device, etc. [0161] In some embodiments, the network 900 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. [0162] In some embodiments, the UE 902 may additionally communicate with an AP 904 via an over-the-air connection. The AP 904 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 930. The connection between the UE 902 and the AP 904 may be consistent with any IEEE 902.11 protocol, wherein the AP 904 could be a wireless fidelity (Wi-Fi®) router. In some embodiments, the UE 902, RAN 930, and AP 904 may utilize cellular-WLAN aggregation (for example, LWA/LWIP). Cellular-WLAN aggregation may involve the UE 902 being configured by the RAN 930 to utilize both cellular radio resources and WLAN resources. [0163] The RAN 930 may include one or more access nodes, for example, AN 960. AN 960 may terminate air-interface protocols for the UE 902 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and L1 protocols. In this manner, the AN 960 may enable data/voice connectivity between CN 918 and the UE 902. In some embodiments, the AN 960 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool. The AN 960 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 960 may be a macrocell base station or a low power base station for providing femtocells, Attorney Docket No. AE9962-PCT /1020.9962WO picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells. [0164] In embodiments in which the RAN 930 includes a plurality of ANs, they may be coupled with one another via an X2 interface (if the RAN 930 is an LTE RAN) or an Xn interface (if the RAN 930 is a 5G RAN). The X2/Xn interfaces, which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc. [0165] The ANs of the RAN 930 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 902 with an air interface for network access. The UE 902 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 930. For example, the UE 902 and RAN 930 may use carrier aggregation to allow the UE 902 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell. In dual connectivity scenarios, a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG. The first/second ANs may be any combination of eNB, gNB, ng-eNB, etc. [0166] The RAN 930 may provide the air interface over a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells. Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol. [0167] In V2X scenarios the UE 902 or AN 960 may be or act as an RSU, which may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor Attorney Docket No. AE9962-PCT /1020.9962WO installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network. [0168] In some embodiments, the RAN 930 may be an LTE RAN 926 with eNBs, for example, eNB 954. The LTE RAN 926 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSI- RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE. The LTE air interface may operating on sub-6 GHz bands. [0169] In some embodiments, the RAN 930 may be an NG-RAN 928 with gNBs, for example, gNB 956, or ng-eNBs, for example, ng-eNB 958. The gNB 956 may connect with 5G-enabled UEs using a 5G NR interface. The gNB 956 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng- eNB 958 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface. The gNB 956 and the ng-eNB 958 may connect with each other over an Xn interface. [0170] In some embodiments, the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 928 and a UPF 938 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN 928 and an AMF 934 (e.g., N2 interface). [0171] The NG-RAN 928 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data. The 5G- NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface. The 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking. The 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH. [0172] In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of the SCS. For example, Attorney Docket No. AE9962-PCT /1020.9962WO the UE 902 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 902, the SCS of the transmission is changed as well. Another use case example of BWP is related to power saving. In particular, multiple BWPs can be configured for the UE 902 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 902 and in some cases at the gNB 956. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load. [0173] The RAN 930 is communicatively coupled to CN 918 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 902). The components of the CN 918 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 918 onto physical compute/storage resources in servers, switches, etc. A logical instantiation of the CN 918 may be referred to as a network slice, and a logical instantiation of a portion of the CN 918 may be referred to as a network sub-slice. [0174] In some embodiments, the CN 918 may be an LTE CN 924, which may also be referred to as an EPC. The LTE CN 924 may include MME 906, SGW 908, SGSN 914, HSS 916, PGW 910, and PCRF 912 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 924 may be briefly introduced as follows. [0175] The MME 906 may implement mobility management functions to track a current location of the UE 902 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc. [0176] The SGW 908 may terminate an S1 interface toward the RAN and route data packets between the RAN and the LTE CN 924. The SGW 908 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement. [0177] The SGSN 914 may track a location of the UE 902 and perform security functions and access control. In addition, the SGSN 914 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 906; MME selection for handovers; etc. The S3 reference point between the MME 906 and Attorney Docket No. AE9962-PCT /1020.9962WO the SGSN 914 may enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states. [0178] The HSS 916 may include a database for network users, including subscription- related information to support the network entities’ handling of communication sessions. The HSS 916 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS 916 and the MME 906 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 918. [0179] The PGW 910 may terminate an SGi interface toward a data network (DN) 922 that may include an application/content server 920. The PGW 910 may route data packets between the LTE CN 924 and the data network 922. The PGW 910 may be coupled with the SGW 908 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 910 may further include a node for policy enforcement and charging data collection (for example, PCEF). Additionally, the SGi reference point between the PGW 910 and the data network 922 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services. The PGW 910 may be coupled with a PCRF 912 via a Gx reference point. [0180] The PCRF 912 is the policy and charging control element of the LTE CN 924. The PCRF 912 may be communicatively coupled to the app/content server 920 to determine appropriate QoS and charging parameters for service flows. The PCRF 910 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI. [0181] In some embodiments, the CN 918 may be a 5GC 952. The 5GC 952 may include an AUSF 932, AMF 934, SMF 936, UPF 938, NSSF 940, NEF 942, NRF 944, PCF 946, UDM 948, and AF 950 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 952 may be briefly introduced as follows. [0182] The AUSF 932 may store data for authentication of UE 902 and handle authentication-related functionality. The AUSF 932 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 952 over reference points as shown, the AUSF 932 may exhibit an Nausf service- based interface. [0183] The AMF 934 may allow other functions of the 5GC 952 to communicate with the UE 902 and the RAN 930 and to subscribe to notifications about mobility events with respect to the UE 902. The AMF 934 may be responsible for registration management (for example, for registering UE 902), connection management, reachability management, Attorney Docket No. AE9962-PCT /1020.9962WO mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 934 may provide transport for SM messages between the UE 902 and the SMF 936, and act as a transparent proxy for routing SM messages. AMF 934 may also provide transport for SMS messages between UE 902 and an SMSF. AMF 934 may interact with the AUSF 932 and the UE 902 to perform various security anchor and context management functions. Furthermore, AMF 934 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 930 and the AMF 934; and the AMF 934 may be a termination point of NAS (N1) signaling, and perform NAS ciphering and integrity protection. AMF 934 may also support NAS signaling with the UE 902 over an N3 IWF interface. [0184] The SMF 936 may be responsible for SM (for example, session establishment, tunnel management between UPF 938 and AN 960); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 938 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 934 over N2 to AN 960; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 902 and the data network 922. [0185] The UPF 938 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 922, and a branching point to support multi-homed PDU session. The UPF 938 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF-to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 938 may include an uplink classifier to support routing traffic flows to a data network. [0186] The NSSF 940 may select a set of network slice instances serving the UE 902. The NSSF 940 may also determine allowed NSSAI and the mapping to the subscribed S- NSSAIs, if needed. The NSSF 940 may also determine the AMF set to be used to serve the Attorney Docket No. AE9962-PCT /1020.9962WO UE 902, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 944. The selection of a set of network slice instances for the UE 902 may be triggered by the AMF 934 with which the UE 902 is registered by interacting with the NSSF 940, which may lead to a change of AMF. The NSSF 940 may interact with the AMF 934 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 940 may exhibit an Nnssf service-based interface. [0187] The NEF 942 may securely expose services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 950), edge computing or fog computing systems, etc. In such embodiments, the NEF 942 may authenticate, authorize, or throttle the AFs. NEF 942 may also translate information exchanged with the AF 950 and information exchanged with internal network functions. For example, the NEF 942 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 942 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 942 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re- exposed by the NEF 942 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 942 may exhibit an Nnef service-based interface. [0188] The NRF 944 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 944 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 944 may exhibit the Nnrf service-based interface. [0189] The PCF 946 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior. The PCF 946 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 948. In addition to communicating with functions over reference points as shown, the PCF 946 exhibit an Npcf service-based interface. [0190] The UDM 948 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 902. For example, subscription data may be communicated via an N8 reference point between the UDM 948 and the AMF 934. The UDM 948 may include two parts, an application front end Attorney Docket No. AE9962-PCT /1020.9962WO and a UDR. The UDR may store subscription data and policy data for the UDM 948 and the PCF 946, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 902) for the NEF 942. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 948, PCF 946, and NEF 942 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 948 may exhibit the Nudm service-based interface. [0191] The AF 950 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control. [0192] In some embodiments, the 5GC 952 may enable edge computing by selecting operator/3 ^rd party services to be geographically close to a point that the UE 902 is attached to the network. This may reduce latency and load on the network. To provide edge- computing implementations, the 5GC 952 may select a UPF 938 close to the UE 902 and execute traffic steering from the UPF 938 to data network 922 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 950. In this way, the AF 950 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 950 is considered to be a trusted entity, the network operator may permit AF 950 to interact directly with relevant NFs. Additionally, the AF 950 may exhibit a Naf service-based interface. [0193] The data network 922 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application/content server 920. [0194] FIG. 10 schematically illustrates a wireless network 1000 in accordance with various embodiments. The wireless network 1000 may include a UE 1002 in wireless communication with an AN 1024. The UE 1002 and AN 1024 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein. [0195] The UE 1002 may be communicatively coupled with the AN 1024 via connection 1046. The connection 1046 is illustrated as an air interface to enable communicative Attorney Docket No. AE9962-PCT /1020.9962WO coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies. [0196] The UE 1002 may include a host platform 1004 coupled with a modem platform 1008. The host platform 1004 may include application processing circuitry 1006, which may be coupled with protocol processing circuitry 1010 of the modem platform 1008. The application processing circuitry 1006 may run various applications for the UE 1002 that source/sink application data. The application processing circuitry 1006 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations [0197] The protocol processing circuitry 1010 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 1046. The layer operations implemented by the protocol processing circuitry 1010 may include, for example, MAC, RLC, PDCP, RRC and NAS operations. [0198] The modem platform 1008 may further include digital baseband circuitry 1012 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 1010 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions. [0199] The modem platform 1008 may further include transmit circuitry 1014, receive circuitry 1016, RF circuitry 1018, and RF front end (RFFE) 1020, which may include or connect to one or more antenna panels 1022. Briefly, the transmit circuitry 1014 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 1016 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 1018 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 1020 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 1014, receive circuitry 1016, RF circuitry 1018, RFFE Attorney Docket No. AE9962-PCT /1020.9962WO 1020, and antenna panels 1022 (referred generically as “transmit/receive components”) may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc. [0200] In some embodiments, the protocol processing circuitry 1010 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components. [0201] A UE reception may be established by and via the antenna panels 1022, RFFE 1020, RF circuitry 1018, receive circuitry 1016, digital baseband circuitry 1012, and protocol processing circuitry 1010. In some embodiments, the antenna panels 1022 may receive a transmission from the AN 1024 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 1022. [0202] A UE transmission may be established by and via the protocol processing circuitry 1010, digital baseband circuitry 1012, transmit circuitry 1014, RF circuitry 1018, RFFE 1020, and antenna panels 1022. In some embodiments, the transmit components of the UE 1024 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 1022. [0203] Similar to the UE 1002, the AN 1024 may include a host platform 1026 coupled with a modem platform 1030. The host platform 1026 may include application processing circuitry 1028 coupled with protocol processing circuitry 1032 of the modem platform 1030. The modem platform may further include digital baseband circuitry 1034, transmit circuitry 1036, receive circuitry 1038, RF circuitry 1040, RFFE circuitry 1042, and antenna panels 1044. The components of the AN 1024 may be similar to and substantially interchangeable with like-named components of the UE 1002. In addition to performing data transmission/reception as described above, the components of the A 1004 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling. [0204] FIG. 11 is a block diagram illustrating components, according to some example embodiments, 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 1130 including one or more processors (or processor Attorney Docket No. AE9962-PCT /1020.9962WO cores) 1110, one or more memory/storage devices 1122, and one or more communication resources 1126, each of which may be communicatively coupled via a bus 1120 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 1102 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1130. [0205] The processors 1110 may include, for example, a processor 1112 and a processor 1114. The processors 1110 may be, for example, 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 DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof. [0206] The memory/storage devices 1122 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 1122 may include, but are not limited to, any type of volatile, non-volatile, or semi-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. [0207] The communication resources 1126 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 1104 or one or more databases 1106 or other network elements via a network 1108. For example, the communication resources 1126 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components. [0208] Instructions 106, 1118, 1124, 1128, 1132 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1110 to perform any one or more of the methodologies discussed herein. The instructions 106, 1118, 1124, 1128, 1132 may reside, completely or partially, within at least one of the processors 1110 (e.g., within the processor’s cache memory), the memory/storage devices 1122, or any suitable combination thereof. Furthermore, any portion of the instructions 106, 1118, 1124, 1128, 1132 may be transferred to the hardware resources 1130 from any combination of the peripheral devices 1104 or the databases 1106. Accordingly, the memory of processors 1110, the memory/storage devices 1122, the peripheral devices Attorney Docket No. AE9962-PCT /1020.9962WO 1104, and the databases 1106 are examples of computer-readable and machine-readable media. [0209] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section. [0210] FIG. 12 illustrates computer readable storage medium 1200. Computer readable storage medium 1200 may comprise any non-transitory computer-readable storage medium or machine-readable storage medium, such as an optical, magnetic or semiconductor storage medium. In various embodiments, computer readable storage medium 1200 may comprise an article of manufacture. In some embodiments, computer readable storage medium 1200 may store computer executable instructions 1202 with which circuitry can execute. For example, computer executable instructions 1202 can include computer executable instructions 1202 to implement operations described with respect to logic flow 700 and/or logic flow 800. Examples of computer readable storage medium 1200 or machine-readable storage medium 1200 may include any tangible media capable of storing electronic data, including volatile memory or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and so forth. Examples of computer executable instructions 1202 may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, object-oriented code, visual code, and the like. [0211] The components and features of the devices described above may be implemented using any combination of discrete circuitry, application specific integrated circuits (ASICs), logic gates and/or single chip architectures. Further, the features of the devices may be implemented using microcontrollers, programmable logic arrays and/or microprocessors or any combination of the foregoing where suitably appropriate. It is noted that hardware, firmware and/or software elements may be collectively or individually referred to herein as “logic” or “circuit.” Attorney Docket No. AE9962-PCT /1020.9962WO [0212] It will be appreciated that the exemplary devices shown in the block diagrams described above may represent one functionally descriptive example of many potential implementations. Accordingly, division, omission or inclusion of block functions depicted in the accompanying figures does not infer that the hardware components, circuits, software and/or elements for implementing these functions would necessarily be divided, omitted, or included in embodiments. [0213] At least one computer-readable storage medium may include instructions that, when executed, cause a system to perform any of the computer-implemented methods described herein. [0214] Some embodiments may be described using the expression “one embodiment” or “an embodiment” along with their derivatives. These terms mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment. Moreover, unless otherwise noted the features described above are recognized to be usable together in any combination. Thus, any features discussed separately may be employed in combination with each other unless it is noted that the features are incompatible with each other. [0215] With general reference to notations and nomenclature used herein, the detailed descriptions herein may be presented in terms of program procedures executed on a computer or network of computers. These procedural descriptions and representations are used by those skilled in the art to most effectively convey the substance of their work to others skilled in the art. [0216] A procedure is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. These operations are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical, magnetic or optical signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It proves convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like. It should be noted, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to those quantities. [0217] Further, the manipulations performed are often referred to in terms, such as adding or comparing, which are commonly associated with mental operations performed by a Attorney Docket No. AE9962-PCT /1020.9962WO human operator. No such capability of a human operator is necessary, or desirable in most cases, in any of the operations described herein, which form part of one or more embodiments. Rather, the operations are machine operations. Useful machines for performing operations of various embodiments include general purpose digital computers or similar devices. [0218] Some embodiments may be described using the expression "coupled" and "connected" along with their derivatives. These terms are not necessarily intended as synonyms for each other. For example, some embodiments may be described using the terms “connected” and/or “coupled” to indicate that two or more elements are in direct physical or electrical contact with each other. The term "coupled,” however, may also mean that two or more elements are not in direct contact with each other, but yet still co-operate or interact with each other. [0219] Various embodiments also relate to apparatus or systems for performing these operations. This apparatus may be specially constructed for the required purpose or it may comprise a general purpose computer as selectively activated or reconfigured by a computer program stored in the computer. The procedures presented herein are not inherently related to a particular computer or other apparatus. Various general purpose machines may be used with programs written in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the required method steps. The required structure for a variety of these machines will appear from the description given. [0220] What has been described above includes examples of the disclosed architecture. It is, of course, not possible to describe every conceivable combination of components and/or methodologies, but one of ordinary skill in the art may recognize that many further combinations and permutations are possible. Accordingly, the novel architecture is intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. [0221] The various elements of the devices as previously described with reference to FIGS. 1-12 may include various hardware elements, software elements, or a combination of both. Examples of hardware elements may include devices, logic devices, components, processors, microprocessors, circuits, processors, circuit elements (e.g., transistors, resistors, capacitors, inductors, and so forth), integrated circuits, application specific integrated circuits (ASIC), programmable logic devices (PLD), digital signal processors (DSP), field programmable gate array (FPGA), memory units, logic gates, registers, semiconductor device, chips, microchips, chip sets, and so forth. Examples of software Attorney Docket No. AE9962-PCT /1020.9962WO elements may include software components, programs, applications, computer programs, application programs, system programs, software development programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (API), instruction sets, computing code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. However, determining whether an embodiment is implemented using hardware elements and/or software elements may vary in accordance with any number of factors, such as desired computational rate, power levels, heat tolerances, processing cycle budget, input data rates, output data rates, memory resources, data bus speeds and other design or performance constraints, as desired for a given implementation. [0222] One or more aspects of at least one embodiment may be implemented by representative instructions stored on a machine-readable medium which represents various logic within the processor, which when read by a machine causes the machine to fabricate logic to perform the techniques described herein. Such representations, known as “IP cores” may be stored on a tangible, machine readable medium and supplied to various customers or manufacturing facilities to load into the fabrication machines that make the logic or processor. Some embodiments may be implemented, for example, using a machine-readable medium or article which may store an instruction or a set of instructions that, if executed by a machine, may cause the machine to perform a method and/or operations in accordance with the embodiments. Such a machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, or the like, and may be implemented using any suitable combination of hardware and/or software. The machine-readable medium or article may include, for example, any suitable type of memory unit, memory device, memory article, memory medium, storage device, storage article, storage medium and/or storage unit, for example, memory, removable or non-removable media, erasable or non-erasable media, writeable or re-writeable media, digital or analog media, hard disk, floppy disk, Compact Disk Read Only Memory (CD-ROM), Compact Disk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), optical disk, magnetic media, magneto-optical media, removable memory cards or disks, various types of Digital Versatile Disk (DVD), a tape, a cassette, or the like. The instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, Attorney Docket No. AE9962-PCT /1020.9962WO encrypted code, and the like, implemented using any suitable high-level, low-level, object- oriented, visual, compiled and/or interpreted programming language. [0223] It will be appreciated that the exemplary devices shown in the block diagrams described above may represent one functionally descriptive example of many potential implementations. Accordingly, division, omission or inclusion of block functions depicted in the accompanying figures does not infer that the hardware components, circuits, software and/or elements for implementing these functions would necessarily be divided, omitted, or included in embodiments. [0224] At least one computer-readable storage medium may include instructions that, when executed, cause a system to perform any of the computer-implemented methods described herein. [0225] Some embodiments may be described using the expression “one embodiment” or “an embodiment” along with their derivatives. These terms mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment. Moreover, unless otherwise noted the features described above are recognized to be usable together in any combination. Thus, any features discussed separately may be employed in combination with each other unless it is noted that the features are incompatible with each other. [0226] The following examples pertain to further embodiments, from which numerous permutations and configurations will be apparent. [0227] Example Set 1 [0228] Example 1 may include the method to define UE capability to differentiate the scenario of the interruption is allowed when there is no measurement gap used. [0229] Example 2 may include the method of example 1 or some other example herein, wherein the basic indication of such capability includes one by which the legacy measurement gap is used and the interruption is allowed [0230] Example 3 may include the method of example 1 or some other example herein, wherein the basic indication of such capability includes one by which the legacy measurement gap is not used but NCSG, and the visible shorter interruption is allowed. Attorney Docket No. AE9962-PCT /1020.9962WO [0231] Example 4 may include the method of example 1 or some other example herein, wherein the basic indication of such capability includes one by which neither the legacy measurement gap nor NCSG is used , and no interruption is allowed. [0232] Example 5 may include the method of example 2 or some other example herein, wherein the interruption can be applied to all serving cells if this gap is not per-FR. [0233] Example Set 2 [0234] In one example, an apparatus for a base station, includes a memory interface to send or receive, to or from a data storage device, measurement information for a wireless communications system. The apparatus also includes processor circuitry communicatively coupled to the memory interface, the processor circuitry to decode a message from user equipment (UE) with UE capability information, the UE capability information to comprise an information element with a configuration value to indicate whether the UE supports measurements of a measurement object without a measurement gap, determine the configuration value for the information element indicates the UE supports measurements of the measurement object without the measurement gap, and determine whether the UE is allowed to cause interruptions while performing measurements of the measurement object without the measurement gap based on the configuration value. [0235] The apparatus of any previous example may also include where the message includes a NeedForGapsInfoNR information element and the configuration value includes a no-gap value, further includes determine the UE is allowed to cause interruptions while performing measurements of the measurement object, the measurement object includes a synchronization signal block (SSB). [0236] The apparatus of any previous example may also include where the message includes a NeedForGapsInfoNR information element and the configuration value includes a nogap-noncsg value, further includes determine the UE is not allowed to cause interruptions while performing measurements of the measurement object. [0237] The apparatus of any previous example may also include where the message includes a NeedForNCSG-NR information element and the configuration value includes a nogap-noncsg value, further includes determine the UE is not allowed to cause interruptions while performing measurements of the measurement object. [0238] The apparatus of any previous example may also include where the configuration value includes a first configuration value to indicate the UE is allowed to cause Attorney Docket No. AE9962-PCT /1020.9962WO interruptions while performing measurements of the measurement object, the measurement object includes intra-frequency or inter-frequency signals for which the UE reports. [0239] The apparatus of any previous example may also include where the configuration value includes a second configuration value to indicate the UE is not allowed to cause interruptions while performing measurements of the measurement object, the measurement object includes intra-frequency or inter-frequency signals for which the UE reports. [0240] The apparatus of any previous example may also include where the message includes a NeedForInterruptionInfoNR information element and the configuration value includes a no-gap-with-interruption value, further includes determine the UE is allowed to cause interruptions while performing measurements of the measurement object, the measurement object includes an intra-frequency synchronization signal block (SSB) or an inter-frequency SSB on a frequency layer for which the no-gap-with-interruption value is indicated. [0241] The apparatus of any previous example may also include where the message includes a NeedForInterruptionInfoNR information element and the configuration value includes a no-gap-with-interruption value, further includes determine the UE is allowed to cause interruptions while performing measurements of the measurement object, the interruptions having a defined interruption ratio. [0242] The apparatus of any previous example may also include where the message includes a NeedForInterruptionInfoNR information element and the configuration value includes a no-gap-with-interruption value, further includes determine the UE is allowed to cause interruptions while performing measurements of the measurement object, the interruptions allowed for all serving cells in a same frequency range (FR) as the measurement object being measured when the UE supports per-FR measurement gaps, and all serving cells when the UE does not support per-FR measurement gaps. Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims. [0243] In one example, a method for a base station, includes decoding a message from user equipment (UE) with UE capability information, the UE capability information to comprise an information element with a configuration value to indicate whether the UE supports measurements of a measurement object without a measurement gap, determining the configuration value for the information element indicates the UE supports measurements of the measurement object without the measurement gap, and determining whether the UE is Attorney Docket No. AE9962-PCT /1020.9962WO allowed to cause interruptions while performing measurements of the measurement object without the measurement gap based on the configuration value. [0244] The method of any previous example may also include where the message includes a NeedForGapsInfoNR information element and the configuration value includes a no-gap value, further includes determining the UE is allowed to cause interruptions while performing measurements of the measurement object, the measurement object includes a synchronization signal block (SSB). [0245] The method of any previous example may also include where the message includes a NeedForGapsInfoNR information element and the configuration value includes a nogap- noncsg value, further includes determining the UE is not allowed to cause interruptions while performing measurements of the measurement object. [0246] The method of any previous example may also include where the message includes a NeedForNCSG-NR information element and the configuration value includes a nogap- noncsg value, further includes determining the UE is not allowed to cause interruptions while performing measurements of the measurement object. [0247] The method of any previous example may also include where the configuration value includes a first configuration value to indicate the UE is allowed to cause interruptions while performing measurements of the measurement object, the measurement object includes intra-frequency or inter-frequency signals for which the UE reports. [0248] The method of any previous example may also include where the configuration value includes a second configuration value to indicate the UE is not allowed to cause interruptions while performing measurements of the measurement object, the measurement object includes intra-frequency or inter-frequency signals for which the UE reports. [0249] The method of any previous example may also include where the message includes a NeedForInterruptionInfoNR information element and the configuration value includes a no-gap-with-interruption value, further includes determining the UE is allowed to cause interruptions while performing measurements of the measurement object, the measurement object includes an intra-frequency synchronization signal block (SSB) or an inter-frequency SSB on a frequency layer for which the no-gap-with-interruption value is indicated. [0250] The method of any previous example may also include where the message includes a NeedForInterruptionInfoNR information element and the configuration value includes a no-gap-with-interruption value, further includes determining the UE is allowed to cause Attorney Docket No. AE9962-PCT /1020.9962WO interruptions while performing measurements of the measurement object, the interruptions having a defined interruption ratio. [0251] The method of any previous example may also include where the message includes a NeedForInterruptionInfoNR information element and the configuration value includes a no-gap-with-interruption value, further includes determining the UE is allowed to cause interruptions while performing measurements of the measurement object, the interruptions allowed for all serving cells in a same frequency range (FR) as the measurement object being measured when the UE supports per-FR measurement gaps, and all serving cells when the UE does not support per-FR measurement gaps. Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims. [0252] In one example, a non-transitory computer-readable storage medium, the computer- readable storage medium including instructions that when executed by processing circuitry, cause the processing circuitry to decode a message from user equipment (UE) with UE capability information, the UE capability information to comprise an information element with a configuration value to indicate whether the UE supports measurements of a measurement object without a measurement gap, determine the configuration value for the information element indicates the UE supports measurements of the measurement object without the measurement gap, and determine whether the UE is allowed to cause interruptions while performing measurements of the measurement object without the measurement gap based on the configuration value. [0253] The computer-readable storage medium of any previous example may also include where the message includes a NeedForGapsInfoNR information element and the configuration value includes a no-gap value, where the instructions further cause the processing circuitry to determine the UE is allowed to cause interruptions while performing measurements of the measurement object, the measurement object includes a synchronization signal block (SSB). [0254] The computer-readable storage medium of any previous example may also include where the message includes a NeedForGapsInfoNR information element and the configuration value includes a nogap-noncsg value, where the instructions further cause the processing circuitry to determine the UE is not allowed to cause interruptions while performing measurements of the measurement object. [0255] The computer-readable storage medium of any previous example may also include where the message includes a NeedForNCSG-NR information element and the configuration value includes a nogap-noncsg value, where the instructions further cause the processing Attorney Docket No. AE9962-PCT /1020.9962WO circuitry to determine the UE is not allowed to cause interruptions while performing measurements of the measurement object. [0256] The computer-readable storage medium of any previous example may also include where the configuration value includes a first configuration value to indicate the UE is allowed to cause interruptions while perform measurements of the measurement object, the measurement object includes intra-frequency or inter-frequency signals for which the UE reports. [0257] The computer-readable storage medium of any previous example may also include where the configuration value includes a second configuration value to indicate the UE is not allowed to cause interruptions while perform measurements of the measurement object, the measurement object includes intra-frequency or inter-frequency signals for which the UE reports. [0258] The computer-readable storage medium of any previous example may also include where the message includes a NeedForInterruptionInfoNR information element and the configuration value includes a no-gap-with-interruption value, where the instructions further cause the processing circuitry to determine the UE is allowed to cause interruptions while performing measurements of the measurement object, the measurement object includes an intra-frequency synchronization signal block (SSB) or an inter-frequency SSB on a frequency layer for which the no-gap-with-interruption value is indicated. [0259] The computer-readable storage medium of any previous example may also include where the message includes a NeedForInterruptionInfoNR information element and the configuration value includes a no-gap-with-interruption value, where the instructions further cause the processing circuitry to determine the UE is allowed to cause interruptions while performing measurements of the measurement object, the interruptions having a defined interruption ratio. [0260] The computer-readable storage medium of any previous example may also include where the message includes a NeedForInterruptionInfoNR information element and the configuration value includes a no-gap-with-interruption value, where the instructions further cause the processing circuitry to determine the UE is allowed to cause interruptions while performing measurements of the measurement object, the interruptions allowed for all serving cells in a same frequency range (FR) as the measurement object being measured when the UE supports per-FR measurement gaps, and all serving cells when the UE does not support per-FR measurement gaps. Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims. Attorney Docket No. AE9962-PCT /1020.9962WO [0261] In one example, an apparatus for a base station, includes means for decoding a message from user equipment (UE) with UE capability information, the UE capability information to comprise an information element with a configuration value to indicate whether the UE supports measurements of a measurement object without a measurement gap, means for determining the configuration value for the information element indicates the UE supports measurements of the measurement object without the measurement gap, and means for determining whether the UE is allowed to cause interruptions while performing measurements of the measurement object without the measurement gap based on the configuration value. [0262] The apparatus of any previous example may also include where the message includes a NeedForGapsInfoNR information element and the configuration value includes a no-gap value, further includes means for determining the UE is allowed to cause interruptions while performing measurements of the measurement object, the measurement object includes a synchronization signal block (SSB). [0263] The apparatus of any previous example may also include where the message includes a NeedForGapsInfoNR information element and the configuration value includes a nogap-noncsg value, further includes means for determining the UE is not allowed to cause interruptions while performing measurements of the measurement object. [0264] The apparatus of any previous example may also include where the message includes a NeedForNCSG-NR information element and the configuration value includes a nogap-noncsg value, further includes means for determining the UE is not allowed to cause interruptions while performing measurements of the measurement object. [0265] The apparatus of any previous example may also include where the configuration value includes a first configuration value to indicate the UE is allowed to cause interruptions while performing measurements of the measurement object, the measurement object includes intra-frequency or inter-frequency signals for which the UE reports. [0266] The apparatus of any previous example may also include where the configuration value includes a second configuration value to indicate the UE is not allowed to cause interruptions while performing measurements of the measurement object, the measurement object includes intra-frequency or inter-frequency signals for which the UE reports. [0267] The apparatus of any previous example may also include where the message includes a NeedForInterruptionInfoNR information element and the configuration value includes a no-gap-with-interruption value, further includes means for determining the UE is allowed to cause interruptions while performing measurements of the measurement object, Attorney Docket No. AE9962-PCT /1020.9962WO the measurement object includes an intra-frequency synchronization signal block (SSB) or an inter-frequency SSB on a frequency layer for which the no-gap-with-interruption value is indicated. [0268] The apparatus of any previous example may also include where the message includes a NeedForInterruptionInfoNR information element and the configuration value includes a no-gap-with-interruption value, further includes means for determining the UE is allowed to cause interruptions while performing measurements of the measurement object, the interruptions having a defined interruption ratio. [0269] The apparatus of any previous example may also include where the message includes a NeedForInterruptionInfoNR information element and the configuration value includes a no-gap-with-interruption value, further includes means for determining the UE is allowed to cause interruptions while performing measurements of the measurement object, the interruptions allowed for all serving cells in a same frequency range (FR) as the measurement object being measured when the UE supports per-FR measurement gaps, and all serving cells when the UE does not support per-FR measurement gaps. Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims. [0270] Terminology [0271] For the purposes of the present document, the following terms and definitions are applicable to the examples and embodiments discussed herein. [0272] The term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry. Attorney Docket No. AE9962-PCT /1020.9962WO [0273] The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information. The term “processor circuitry” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes. Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators. The terms “application circuitry” and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.” [0274] The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like. [0275] The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface. [0276] The term “network element” as used herein refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, Attorney Docket No. AE9962-PCT /1020.9962WO switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like. [0277] The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources. [0278] The term “appliance,” “computer appliance,” or the like, as used herein refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource. A “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to providing a specific computing resource. [0279] The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like. A “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s). A “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/systems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable. [0280] The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with and/or equivalent to “communications channel,” “data Attorney Docket No. AE9962-PCT /1020.9962WO communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information. [0281] The terms “instantiate,” “instantiation,” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code. [0282] The terms “coupled,” “communicatively coupled,” along with derivatives thereof are used herein. The term “coupled” may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term “directly coupled” may mean that two or more elements are in direct contact with one another. The term “communicatively coupled” may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and/or the like. [0283] The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content. [0284] The term “SMTC” refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration. [0285] The term “SSB” refers to an SS/PBCH block. [0286] The term “a “Primary Cell” refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure. [0287] The term “Primary SCG Cell” refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation. [0288] The term “Secondary Cell” refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA. [0289] The term “Secondary Cell Group” refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC. Attorney Docket No. AE9962-PCT /1020.9962WO [0290] The term “Serving Cell” refers to the primary cell for a UE in RRC_CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell. [0291] The term “serving cell” or “serving cells” refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC_CONNECTED configured with CA/. [0292] The term “Special Cell” refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell.