Managing measurements for wireless networks

Abstract

Embodiments attempt to solve challenges in a wireless communications system. Embodiments describe various techniques, systems, and devices to support various measurement and interruption criteria for access nodes and user equipment in a 3GPP 5G NR or 6G system, among other wireless communications systems. Other embodiments are described and claimed.

Description

[0001] MANAGING MEASUREMENTS FOR WIRELESS NETWORKS

[0002] CROSS REFERENCE TO RELATED APPLICATIONS

[0003] This application claims the benefit of and priority to previously filed PCT International Application Number PCT / CN2023 / 129302, filed November 2, 2023, entitled “UE MEASUREMENTS WITHOUT GAP BUT WITH INTERRUPTIONS”, which is hereby incorporated by reference in its entirety.

[0004] BACKGROUND

[0005] 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, Intemet-of-Thing (loT) devices are also growing in usage and can coexist with user devices in various wireless communication systems such as cellular networks.

[0006] BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

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

[0008] FIG. 1 illustrates a wireless communication system in accordance with one embodiment.

[0009] FIG. 2 illustrates an access node in accordance with one embodiment.

[0010] FIG. 3 illustrates an operating environment in accordance with one embodiment.

[0011] FIG. 4A illustrates a data schema in accordance with one embodiment.

[0012] FIG. 4B illustrates a data schema in accordance with one embodiment.

[0013] FIG. 5 illustrates an apparatus for user equipment (UE) in accordance with one embodiment.

[0014] FIG. 6 illustrates logic diagram in accordance with one embodiment.

[0015] FIG. 7 illustrates an apparatus for an access node in accordance with one embodiment.

[0016] FIG. 8 illustrates a logic flow in accordance with one embodiment.

[0017] FIG. 9 illustrates a logic flow in accordance with one embodiment.

[0018] 1

[0019] RECTIFIED SHEET (RULE 91) ISA / KR FIG. 10 illustrates a network architecture in accordance with one embodiment.

[0020] FIG. 11 illustrates wireless network in accordance with one embodiment.

[0021] FIG. 12 illustrates an apparatus in accordance with one embodiment.

[0022] FIG. 13 illustrates a computer readable storage medium in accordance with one embodiment.

[0023] DETAILED DESCRIPTION

[0024] 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 some embodiments, for example, a wireless communications system may implement improvements for efficiently utilizing measurement gaps and interruptions for a UE to accurately measure radio signals to support improved network services, such as handover, load balancing, and overall network utilization and performance.

[0025] In many wireless communication systems, including long-term evolution (LTE) and fifth generation (5G) new radio (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. A goal of RRM is to ensure efficient and reliable use of radio resources while maintaining the quality of service (QoS) for all users. Some functions of RRM in 3GPP systems include radio resource allocation, congestion control, handover management, scheduling, and power control. RRM also plays a role in managing interference and optimizing network capacity and coverage. Overall, RRM helps ensure the efficient and effective operation of wireless networks.

[0026] Various 3GPP documents define RRM for a 5G NR and 6G system, including 3GPP Technical Standards (TS), Technical Reports (TR), Change Requests (CR), 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 standard titled ‘"Technical Specification Group Radio Access Network; NR; Requirements for support of radio resource management,” Release 18, Version 18.4.0 (December 2023), and including future versions, revisions or variants (collectively referred to as “3GPP TS 38.133 Standards”). The 3GPP TS 38.133 specifies requirements 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 standard titled ‘"NR; Radio Resource Control (RRC); Protocol specification,’’ Release 18, Version 18.0.0 (January 2024), 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, TR, CR, and WI as well as other wireless standards released by other standards entities. Embodiments are not limited in this context.

[0027] UEs in 3GPP systems perform measurements by following network instructions to monitor signal strength, quality, and other relevant parameters across different frequencies and radio access technologies (RATs). This process involves careful coordination to balance measurement needs with ongoing communication, utilizing techniques like measurement gaps or leveraging multiple receivers. The ultimate goal is to ensure that the UE maintains the best possible connection by enabling the network to make informed decisions based on accurate and timely measurement data.

[0028] The network defines what measurements the UE should perform and under what conditions to report them. The 3GPP TS 38.133 Standards and 3GPP TS 38.331 Standards define requirements on measurements in NR and the UE. Some UEs may need a ■‘measurement gap” in order to accurately measure radio signals to support improved network services, such as handover, load balancing, and overall network utilization and performance. 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 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.

[0029] A 3GPP 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 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.

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

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

[0032] Even when a UE has sufficient capabilities to perform measurements without gaps, it may potentially cause interruptions in data communications when taking measurements. These interruptions decrease user experience and overall system performance. In such cases, a UE may include in its capability information that it does not need a measurement gap to take measurements. However, the UE may also include in its capability information that it is requesting permission to cause interruptions in regular network service in order to perform measurements. For example, the UE may communicate support for measurements without measurement gaps and a request for interruptions to perform such measurements. In response, the 3GPP network may send a message to the UE with configuration information indicating whether the UE is allowed to measure intra-frequency and inter-frequency measurement objects without a measurement gap but with interruptions.

[0033] However, while a 3GPP network may grant a UE permission to perform measurements without a measurement gaps and with interruptions to perform such measurements, the 3GPP standards currently do not define any interruption requirements, conditions, or rules under which the UE is permitted to cause interruptions when taking measurements. This situation causes a number of technical problems to occur when a UE actually attempts to perform measurements without a measurement gap but with interruptions. For example, there may be multiple UEs in a serving cell performing interfrequency and intra-frequency communications across multiple carriers. Some of the UEs may be a combination of legacy UEs with older equipment that need a measurement gap and modem UEs that do not. A measuring UE may cause interference to other UEs in a same serving cell when it attempts to measure a frequency used by other UEs. This interference may be exacerbated when a UE performs longer interruptions for each measurement occasion or frequently performs interruptions for measurement operations. As a result, a lack of interruption requirements, conditions or rules governing interruptions by the measuring UE may affect performance of other UEs and affect overall system performance.

[0034] Embodiments solve these and other technical challenges. Embodiments are generally- directed to techniques to manage measurement operations for one or more UEs in a wireless communications system, such as a 3GPP system, for example. Some embodiments are particularly directed to techniques to provide interruption configuration information to the UE in order to manage when it can perform measurements without a measurement gap but with interruptions. The interruption configuration information may comprise a set of interruption parameters representing one or more interruption requirements, interruption conditions, or interruption rules that apply when a UE performs measurements. In some embodiments, the interruption parameters apply when a UE measures intra-frequency and inter-frequency measurement objects (MO-s) without measurement gap but with interruptions. Specifically, some embodiments introduces interruption parameters for an interruption length and / or interruption ratio allowed for a UE measuring intra-frequency and inter-frequency MO-s without measurement gap but with interruptions. For example, the interruption configuration information may include values for an interruption ratio and / or interruption length for active bandwidth part (BWP) interruptions of a communications resource. Embodiments are not limited to these examples.

[0035] 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 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.”

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

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

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

[0039] 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 functionality7. In some embodiments, the circuitry7may 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.

[0040] 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 38.331 Standards, or other 3GPP standards or specifications. However, other types of wireless standards are possible as well.

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

[0042] 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), electron! c / 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 (loT) devices, or combinations of them, among others.

[0043] In some implementations, any of the UEs 102 may be loT UEs, which can include a network access layer designed for low-power loT applications utilizing short-lived UE connections. An loT 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, loT networks, or combinations of them, among others. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An loT network describes interconnecting loT UEs, which can include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The loT UEs may execute background applications (e.g., keep-alive messages or status updates) to facilitate the connections of the loT network.

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

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

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

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

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

[0049] 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 crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low latencycommunications, 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 radiofrequencycircuitry 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.

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

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

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

[0053] 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. Such a time-frequency plane representation is a common practice for OFDM sy stems, 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.

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

[0055] 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 subblock 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=l. 2, 4, or 8).

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

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

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

[0059] 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 netw ork elements, such as network element 108a and netw ork 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 netw ork 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.

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

[0061] 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 S I 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.

[0062] 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 SI interface 124. In some implementations, the SI interface 124 may be split into two parts, an SI user plane (Sl-U) interface 128, which carries traffic data between the RAN nodes 106 and the serving gateway (S-GW), and the SI -MME interface 126, which is a signaling interface between the RAN nodes 106 and mobility management entities (MMEs).

[0063] 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 Fl interfaces. An example of a gNB dualarchitecture for a RAN node 106 is shown in FIG. 2.

[0064] FIG. 2 illustrates access node 200. The access node 200 is a sub-system of the wireless communications system 100 illustrated in FIG. 1. The access node 200 depicts a UE 202 connected to a gNB 206 over a connection 204. The UE 202 and connection 204 are similar to the UE 102 and the connections 118, 120 described with reference to FIG. 1. The gNB 206 is similar to the RAN node 106. and represents an implementation of the RAN node 106 as a gNB with a dual-architecture.

[0065] As depicted in FIG. 2. the gNB 206 is divided into two physical entities referred to a centralized or central unit (CU) and a distributed unit (DU). The gNB 206 may comprise a gNB-CU 214 and one or more gNB-DU 212. The gNB-CU 214 is further divided into a gNB-CU control plane (gNB-CU-CP) 208 and a gNB-CU user plane (gNB-CU-UP) 210. The gNB-CU-CP 208 and the gNB-CU-UP 210 communicate over an El interface. The gNB-CU-CP 208 communicates with one or more gNB-DU 212 over an Fl-C interface. The gNB-CU-UP 210 communicates with the one or more gNB-DU 212 over an Fl-U interface.

[0066] In some implementations, there is a single gNB-CU 214 for each gNB 206 that controls multiple gNB-DU 212. For example, the gNB 206 may have more than 100 gNB- DU 212 connected to a single gNB-CU 214. Each gNB-DU 212 is able to support one or more cells, where one gNB 206 can potentially control hundreds of cells in a 5G NR system.

[0067] The gNB-CU 214 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 208 and the gNB-CU-UP 210 provides support for higher layers of a protocol stack such as Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP) and RRC.

[0068] The gNB-DU 212 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 212 provides support for lower layers of the protocol stack such as Radio Link Control (RLC). MAC layer, and PHY layer.

[0069] As depicted in FIG. 2, the gNB-DU 212 includes a scheduler 216. In the wireless communications system 100 and / or the access node 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 216. The scheduler 216 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 216 within the gNB-DU 212 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, qualify of service requirements, and current network conditions, among other factors.

[0070] Based on scheduling decisions, the gNB-DU 212 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 types of messages. The RRC layer is responsible for managing the signaling between the UE 202 and the gNB-DU 212, including the signaling related to the configuration of measurement gaps. The RRC layer in the gNB-DU 212 thus plays a crucial role in orchestrating the scheduling and allocation of measurement gaps based on decisions made by the scheduler 216. 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 212 to make further decisions, such as handovers or beam adjustments.

[0071] 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 216 in the gNB-DU to allocate resources and manage user traffic efficiently, catering to diverse service requirements in 5G and 6G networks.

[0072] FIG. 3 illustrates an operating environment 300. The operating environment 300 illustrates operations for the wireless communications system 100 and / or the access node 200.

[0073] As depicted in FIG. 3, the UE 202 is in communication with a set of RAN nodes, such as RAN node 1 318 and RAN node 2 320, which are similar to RAN node 106a and RAN node 106b, respectively. For example, the RAN node 1 318 may comprise a serving cell (e.g.. a PCell) for the UE 202 and the RAN node 2 320 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 1 318 and the RAN node 2 320, 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.

[0074] The UE 202 may communicate with the scheduler 216 of the access node 200 to coordinate measurement operations for the UE 202. The UE 202 may send UE capability information 304 to the scheduler 216. The scheduler 216 may receive the UE capability information 304. and generate UE configuration information 306 for the UE 202. The scheduler 216 may send the UE configuration information 306 to the UE 202. The UE 202 may configure its measurement operations in accordance with the UE configuration information 306. The UE 202 may then take measurements of for various measurement configuration information 314 associated with the RAN node 1 318 and / or the RAN node 2 320. The UE 202 may send the UE measurement information 308 to the scheduler 216. The scheduler 216 may then update network settings and send new control directives to the UE 202 based on the UE measurement information 308.

[0075] During RRC connection setup, the UE 202 sends an RRC Connection Request message to the gNB 206. 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 206 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 206 to exchange RRC and NAS messages. The UE 202 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.

[0076] Sometime during or after RRC connection setup, the UE 202 sends UE capabilityinformation 304 to the gNB 206. The UE capability information 304 includes various types of information about UE capabilities. The UE capability information 304 may include an operation mode 310 for the UE 202, interruption information 312 for the UE 202, and other ty pes of UE capability- information 304. In some embodiments, the UE 202 sends the UE capability- information 304 in response to a network initiated message when the network decides the UE 202 should start performing inter-frequency or intra-frequency measurements. For example, the access node 200 may send RRC signaling such as a MecisurementConfig message to the UE 202, with aMeasGapConfig IE. For example, this message includes a configuration for measurement gaps, such as a Gap Pattern #0. which provides a 6 ms gap every 40 ms. In some embodiments, the UE 202 may send the UE capability information 304 in response to other RRC messages, or on its own initiative. Embodiments are not limited in this context.

[0077] The UE 202 encodes and sends one or more messages 302 comprising UE capability information 304 to a network node of a wireless communications system, such as an access node 200 of the wireless communications system 100. The UE capability information 304 comprises, at least in part, measurement capability information of the UE 202. The UE measurement capability information includes details such as supported frequency bands, measurement bandwidths, and ability to perform measurements without gaps. For intrafrequency measurements, the UE 202 typically does not use measurement gaps. For interfrequency or inter-RAT measurements, however, measurement gaps may be needed unless the UE 202 supports simultaneous measurements (e.g., the UE includes multiple radios, radio chains, advanced processors, and so forth). The messages 302 may be implemented, for example, as RRC messages as defined by the 3GPP TS 38.331 Standards.

[0078] The operation mode 310 indicates an operation mode for the UE 202. In some embodiments, the operation mode 310 may comprise a standalone (SA) operation mode as defined by the 3GPP 38.133 Standards. An SA operation mode is an operation mode when the UE 202 is configured with at least a primary cell (PCell) and not any multi-radio dual connectivity (MR-DC). In some embodiments, the operation mode 310 may comprise a MR- DC operation mode. Embodiments are not limited to these examples.

[0079] The interruption information 312 (or interruption requirement information) indicates measurement capabilities of the UE 202. including whether the UE 202 needs measurement gaps or is capable of operating with or 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 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 configuration information 314. Alternatively, the measurement configuration information 314 may include one or more values to indicate whether it requires a measurement gap or does not require a measurement gap. Additionally, or alternatively, the UE capability information 304 may comprise interruption information 312. The interruption information 312 indicates whether the UE 202 requests or needs interruption during measurement operations or no interruption during measurement operations. In many cases, this decision is left to the scheduler 216 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, which the scheduler 216 factors in when deciding to allow measurements without a measurement gap but with interruptions.

[0080] In some embodiments, 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, the 3GPP TS 38.331 Standards define 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. The NeedForGapsInfoNR IE includes measurement gap requirement information of the UE 202 for NR target bands. The IE NeedForGapsInfoNR indicates whether measurement gap is required for the UE to perform signal synchronization block (SSB) based measurements on an NR target band while NR-NR dual connectivity (NR-DC) or NR evolved universal terrestrial radio access network (E-UTRA) dual connectivity (NE- DC) is not configured. The field includes needForGapsInfoNR in RRCReconfigurationComplete message, needForGapsInfoNR in RRCResumeComplete message or musim-needForGapsInfoNR in UEAssistancelnformation message that is last reported by the UE 202, if any. The field also includes intraFreq-needForGap that indicates the measurement gap requirement information for NR intra-frequency measurement, interFreq-needForGap that indicates the measurement gap requirement information for NR inter-frequency measurement, bandNR indicates the NR target band to be measured, and / or gapindication that indicates whether measurement gap 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 an RRCReconfiguration or RRC Res lime 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.

[0081] In some embodiments, for example, the UE 202 communicates whether or not it needs measurement gaps with or without interruptions to the network using a defined information element (IE) of a control message. For example, the 3GPP TS 38.331 Standards define an IE referred to as a NeedFor Interr uptionlnfoNR IE. The IE NeedForlnterruptionlnfoNR indicates whether interruption is needed for the UE to perform SSB based measurements on an NR target band without measurement gap while NR-DC or NE-DC is not configured. The IE NeedForlnterruptionlnfoNR includes a field intraFreq-needFor Interruption that indicates the interruption requirement information for NR intra-frequency measurement. Each entry in the list is associated to the entry in list intraFreq-needForGcip-r 16 with the same index. This field shall be set to no-gap-no- interruption for the serving cell(s) belonging to the corresponding band(s) where bwpOperationMeasWithoutInterrupt-r!8 is supported by the UE. The IE NeedForlnterruptionlnfoNR also includes a field interFreq-needForlnterruption that indicates the interruption requirement information for NR inter-frequency measurement. Each entry7in the list is associated to the entry7in list inter Freq-needForGap-r 16 with the same index. The IE NeedForlnterruptionlnfoNR also includes a field

[0082] NeedFor Interr uptionNR. This field includes a value interruptionindication that indicates whether interruption is needed for the UE to perform SSB based measurements without measurement gap. A value no-gap-with-interruption indicates that interruption is needed. A value no-gap-no-interruption indicates interruption is not needed.

[0083] In various embodiments, the UE 202 may communicate UE configuration information 304 such as the operation mode 310 and / or interruption information 312 (including measurement capability information) using the NeedFor Gaps Inf oNR IE, the NeedForlnterruptionlnfoNR IE, or a combination of the NeedForGapsInfoNR IE and the NeedForlnterruptionlnfoNR IE. For example, the UE 202 reports the interruption information 312 of NR target bands in an RRC message, such as an RRCReconfigurationComplete or RRCResumeComplete message. Embodiments are not limited in this context.

[0084] The access node 200 for the wireless communications system 100 receives and decodes one or more messages from one or more UEs within a serving cell (e.g., a primary7cell or PCell), including the messages 302 from the UE 202. The access node 200 may be implemented as a base station such as a gNB 206 or a network function (NF) of a core network (CN) node. The messages 302 comprise the UE capability7information 304 and, at least in part, the measurement capability7information from the UE. The messages 302 may comprise, for example, RRC messages as defined by the 3GPP TS 38.331 Standards and / or the 3GPP TS 38.133 Standards. The UE capability information 304 may also include the operation mode 310 of the UE 202 and the interruption information 312 of the UE 202. The access node 200 assesses a need for measurements based on factors like network topology, UE mobility, and service requirements. The access node 200 prepares measurement configuration information 314. Non-limiting examples of measurement configuration information 314 includes information specifying the target frequencies and cells, measurement objects (MO-s), reporting configurations detailing when and how- measurements should be reported, measurement identities linking the above components, and measurement gap configurations if necessary, based on the UE capability information 304 including the operation mode 310, interruption information 312, UE measurement capability information and / or measurement requirements of the UE 202 and / or the wireless communications system 100.

[0085] In some embodiments, given the various combinations of configurable values for the UE capability information 304. a scenario occurs where the access node 200 receives one or more messages 302 from the UE 202 with the NeedForGapsInfoNR IE set to a no-gap value and / or a needForlnterruptionlnfoNR IE set to a no-gap-with-interruption value. In such cases, the access node 200 prepares interruption configuration information 316. The interruption configuration information 316 defines when and how the UE 202 is allowed to cause interruptions while performing measurements on the frequency layers of the bands for which the no-gap-with-interruption is indicated. In some embodiments, for example, the interruption configuration information 316 is defined by 3GPP TS 38.133 Standards, including IE, IE fields, field values, and procedures.

[0086] The access node 200 sends the measurement configuration information 314 and / or the interruption configuration information 316 to the UE 202 via one or more RRC messages. For example, when the UE capability information 304 comprises a NeedForGapsInfoNR IE set to a gap value and / or a needFor Interr uptionlnfoNR-r 18 IE set to a no-gap-with-interruption value, the access node 200 may send a message 302 to the UE 202 with the measurement configuration information 314. For example, when the UE capability' information 304 comprises a NeedForGapsInfoNR IE set to ano-gap value and / or a needFor Inter ruptionlnfoNR-r 18 IE set to a no-gap-with-interruption value, the access node 200 may send a message 302 to the UE 202 with the measurement configuration information 314 and / or the interruption configuration information 316 indicating the UE 202 is allowed to measure intra-frequency and inter-frequency measurement objects without a measurement gap but with interruptions. The interruption configuration information 316 may comprise a set of interruption configuration parameters to define, manage and control interruptions performed by the UE 202. For example, the interruption configuration information 316 may include values for an interruption ratio and / or interruption length for active bandwidth part (BWP) interruptions of the resource to use when performing layer 1 (LI) measurements, among other types of parameters and values. The access node 200 sends the measurement configuration information 314 and interruption configuration information 316 in an IE of one or more messages 302, such as an RRC Connection Reconfiguration message as defined by the 3GPP TS 38.331 Standards.

[0087] Once the access node 200 approves measurements on certain measurement objects at certain frequencies based on the UE configuration information 304, the sends the measurement configuration information 314 and / or the interruption configuration information 316 to the UE 202 in various ways, such as implicit notification or explicit notification.

[0088] In implicit notification, for example, the access node 200 configures and sends the measurement configuration information 314 using normal measurement object configurations and configuration messages as defined in the 3GPP TS 38.331 Standards. By virtue of the access node 200 sending the measurement configuration information 314 automatically authorizes the UE 202 to cause interruption. In this case, no additional messages to explicitly authorize interruptions are needed. For example, the access node 200 may use an RRCConnectionReconfiguration message (in LTE) or an RRCReconfiguration message (5G NR), which are messages used by the base station (eNodeB in LTE or gNB in 5G NR) to configure the UE's measurement procedures. These messages may include a measConflg IE that contains the measurement configuration parameters, including measurement objects, reporting configurations, and measurement identities. The IE MeasConfig specifies measurements to be performed by the UE, and covers intra-frequency, inter-frequency and inter-RAT mobility as well as configuration of measurement gaps.

[0089] Some fields within measConflg include measObjectToAddModList that specifies the measurement objects (e.g., frequencies or cells) the UE should measure, reportConfigToAddModList that defines the reporting criteria for measurement results, measIdToAddModList that associates measurement objects with reporting configurations, quantity Config that configures measurement quantities and filtering, and measGapConflg IE that specifies the measurement gap configuration. If the measGapConflg IE is absent, the UE 202 is expected to perform measurements without measurement gaps. By omitting this IE, the UE 202 understands that no measurement gaps are allocated and it should perform measurements without gaps. In addition, the UE 202 understands that it may use interruptions. The UE 202 may retrieve the interruption configuration information 316, such as values for an interruption ratio and / or interruption length, that are pre-configured and stored for use by the UE in local memory to perform interruption operations. In explicit notification, for example, the access node 200 configures and sends the measurement configuration information 314 using normal measurement object configurations and configuration messages, and it also sends the interruption configuration information 316 to the UE 202 using custom IE fields and / or custom messages (e.g., RRC messages). The interruption configuration information 316, such as values for an interruption ratio and / or interruption length, are part of the custom IE fields and / or custom messages. The UE 202 retrieves these values from the interruption configuration information 316, and it stores the values for use by the UE 202 in local memory' for use in performing interruption operations.

[0090] In some embodiments, the access node 200 may use a combination of implicit and explicit notification to notify and configure the UE 202 for performing measurements without measurement gap and with interruption. Embodiments are not limited to a specific notification technique used to authorize the UE 202 to perform measurements without measurement gap but with interruption.

[0091] Upon receiving the RRC Connection Reconfiguration message, the UE 202 parses a set of measurement configuration parameters and interruption configuration parameters from the measurement configuration information 314 and the interruption configuration information 316, respectively. The UE 202 stores the measurement objects, reporting configurations, measurement identities, and interruption configuration parameters in local memory. The UE 202 then adjusts its measurement procedures according to the measurement configuration parameters and the interruption configuration parameters. The UE 202 carries out the measurements as specified by the measurement configuration parameters and the interruption configuration parameters. For example, the UE 202 measures signal strength, quality, and other relevant metrics for the designated frequencies and cells, such as for the RAN node 1 318 and / or the RAN node 2 320. Further, the UE 202 utilizes the measurement gaps if configured, and if not configured, the interruption parameters. In some embodiments, for example, the interruption parameters cause the UE 202 to perform interruptions for certain frequency bands at specified measurement occasions, such as during a measurement gap the access node 200 has defined for other UEs in the same serving cell as the UE 202. Based on the reporting configurations, the UE 202 sends UE measurement information 308, such as measurement reports with collected measurements back to the access node 200. The measurement reports are triggered by events (e.g., signal strength thresholds) or periodic intervals.

[0092] The access node 200 receives an RRC message from the UE 202 including a measurement report. The access node 200 analyzes the measurement report to make decisions on: (1) handovers for transferring the UE to a different cell or frequency; (2) load balancing by distributing UEs across cells to optimize network performance; (3) interference management by adjusting network parameters to reduce interference; and (4) other network tasks.

[0093] In various embodiments, the access node 200 and the UE 202 may exchange messages 302 with UE capability information 304, UE configuration information 306, and UE measurement information 308 in accordance with one or more 3GPP standards, such as the 3GPP TS 38.331 Standards and the 3GPP TS 38.133 Standards. In a specific example, the access node 200 generates, encodes, and sends the interruption configuration information 316 in accordance with the 3GPP TS 38. 133 Standards as defined in Section 8.2.2.2.19 titled “Interruptions due to measurements without gap carried out by UE supporting [NeedForInterruptionInfoNR-R18 .'' Section 8.2.2.2.19 of the 3GPP TS 38.133 Standards is described in the following paragraphs.

[0094] When a UE supports [NeedForlnterruptionlnfoNR-Rl 8] 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 layers of the bands for which [no-gap-with-interruption] is indicated. Requirements in this section apply only when the UE is in SA operation mode.

[0095] 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 Tcyciej is the interruption cycle on a certain frequency layer i, specified in Table 8.2.2.2.19-1, where CS SFoutsidegap,i is defined in clause 9.1.5.1 for measurement conducted outside measurement gaps.

[0096] Table 8.2.2.2.19-1 defines a Tcycie,i length for inter / intra-frequency measurement target carrier i as follows: UE is allowed to cause interruption on a certain frequency layer i with the maximum 2L interruption ratio that equals . The total allowed maximum interruption ratio (D) on cycle, i each of the active serving cells due to UE measurements without gap applied in this subclause is specified in Equation (1), as follows:

[0097] EQUATION (1)

[0098] In Equation (1), A is the total number of configured SSB based frequency layers to be measured outside gap including intra-frequency and inter-frequency target carriers where UE indicates that interruption is needed through [no-gap-with-interruption] , and / . is the maximum interruption length for each interruption occasion specified in the Table 8.2.2.2.19-2 and 8.2.2.2.19-3. Table 8.2.2.2.19-2 defines an interruption length L in frequency range 1 (FR1) as defined in clause 5.1 of the 3GPP TS 38.104 standard, as follows:

[0099] Table 8.2.2.2.19-3 defines an interruption length L in frequency range 2 (FR2) as defined in clause 5.1 of the 3GPP TS 38.104 standard, as follows:

[0100] Discussion is ongoing on cases where DRX is configured. Further update to this subclause subjects to the conclusions of the discussion.

[0101] In some embodiments, a specific example for Table 8.2.2.2.19-2 may be implemented as shown in Table 1, as follows: Table 1 : Tcycle,i length for intra-frequency measurement target carrier i

[0102] In some embodiments, a specific example for Table 8.2.2.2.19-3 may be implemented as shown in Table 2, as follows:

[0103] Table 2: Tcycle,i length for inter-frequency measurement target carrier i

[0104] In various embodiments, interruption requirements apply when a NeedforlnlerruplionlnfoNR (3GPP NR UE capability signaling name) capable UE measures intra-frequency and inter-frequency MO-s without measurement gap but with interruptions. The interruption performance needs to be guaranteed so that the UE does not cause more interruption occasions or longer interruptions for each occasion when the UE measures on target measurement objects without measurement gap. This case defines the method to guarantee the UE interruption performance.

[0105] Some embodiments may define the requirements of interruption length / ratio allowed for a UE measuring intra-frequency and inter-frequency MO-s without measurement gap but with interruptions. By defining the requirements of interruption caused by UE measurements without measurement gap but with interruptions, UE interruption performance is guaranteed. UE implementation needs to consider this definition to fulfill the performance requirements.

[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 layers of the bands for which no-gap-with-interruption is indicated. Requirements in this document may apply only when the UE is in SA operation mode.

[0107] During the interruption, the UE may not receive a downlink data signal (e.g., PDSCH) and / or control signal (e g., PDCCH). Alternatively, or additionally, the UE may not transmit an uplink data signal (e.g., PUSCH) and / or control signal (e.g., PUCCH). For example, the UE may interrupt on ongoing transmission or reception and / or not start a transmission or reception that it otherwise would (e.g., that has been scheduled and / or otherwise configured).

[0108] 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 measurement objects, where Tcycie.i is the interruption cycle on a certain frequency layer i according to the network configuration, specified in Table 1 and 2 above. An interruption cycle means that the UE is allowed to cause interruption less or equal frequently than that of every cycle length time.

[0109] A Tcyde definition is different between cases of intra-frequency target carrier or interfrequency target carrier, by different carrier specific scaling factor (CSSF) definitions between the cases. The CSSF scales measurement delay requirements when a UE is configured to monitor multiple measurement objects. For intra-frequency cases, CSSFintra is used while for inter-frequency cases CSSFinter is used.

[0110] CSSFintra is a carrier specific scaling factor and is determined according to CSSFoutside_gap.i for measurement conducted outside measurement gaps, when intra- frequency SMTC is fully non overlapping or partially overlapping with measurement gaps or NCSG, or according to CSSFwdthin_gap,i for measurement conducted within measurement gaps, when intra-frequency SMTC is fully overlapping with measurement gaps.

[0111] CSSFinter is a carrier specific scaling factor and is determined according to CSSFoutside_gap.i for measurement conducted outside measurement gaps or NCSG. such as when inter-frequency SMTC is fully non overlapping or partially overlapping with measurement gaps, or according to CSSFwithin_gap,i for measurement conducted within measurement gaps, such as when inter-frequency SMTC is fully overlapping with measurement gaps.

[0112] The total allowed maximum interruption ratio on each of the active serving cells due to UE measurements without gap applied in this sub-clause is specified in Equation (1), where N is the total number of configured SSB based measurement target frequency layers, including intra-frequency and inter-frequency target carriers, and L is the maximum interruption length for each interruption occasion specified in Table 3 and Table 4 below.

[0113] Table 3: Interruption length L in FR1 Table 4: Interruption length L in FR2

[0114] In some embodiments, if measurement gap is configured and the gap occasions are partially or fully overlapped with the SMTC occasions on a certain frequency layer that UE indicates no-gap-with-interruption, no interruption from measurements on such layer is allowed. This is because all the measurements with interruption are required to be carried out within the configured measurement gaps. Though the measurements do not require measurement gap but forcing them done within the gaps avoid interruptions.

[0115] In some embodiments, the interruptions are allowed for all the active 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.

[0116] FIG. 4A illustrates a more detailed view of a message format 400 or data schema suitable for communicating the UE capability information 304. As depicted in FIG. 4A, the UE 202 may communicate UE capability information 304 including the operation mode 310 and / or the interruption configuration information 316 in a message defined in accordance with one or more 3GPP standards, such as the 3GPP TS 38.133 Standards and the 3GPP TS 38.331 Standards, for example. For instance, the message format 400 may be used to generate and encode one or more messages 302 as RRC messages. Embodiments are not limited to these examples.

[0117] The UE 202 communicates whether or not it needs measurement gaps to the network using a defined IE of a control message, such as information element 402. In some embodiments, the information element 402 may comprise a NeedForGapsInfoNR IE to serve as a mechanism for a UE 202 to communicate to the access node 200 whether it requires measurement gaps to perform inter- frequency and intra- frequency measurements. The NeedForGapsInfoNR IE includes measurement gap requirement information of the UE 202 for NR target bands, as defined using the frequency layer value 414 and the frequency band value 416. The IE NeedForGapsInfoNR indicates whether measurement gap is required for the UE 202 to perform SSB based measurements on an NR target band while NR-DC or NE- DC is not configured.

[0118] In various embodiments, the information element 402 may comprise one or more IE fields 404. For the example, an IE field 404 may comprise a gapindication that indicates whether measurement gap is required for the UE 202 to perform SSB based measurements on the concerned NR target band while NR-DC or NE-DC is not configured. The UE 202 determines this information based on the resultant configuration of the RRCReconflguration ox RRC Resume message that triggers this response. The gapindication field carries one of two enumerated values {gap, no-gap}, where the first value gap represented as gap value 406 indicates that a measurement gap is needed, and the second value no-gap represented as no-gap value 408 indicates a measurement gap is not needed. In some embodiments, for example, the UE 202 communicates interruption information 312 to indicate whether or not it needs measurement gaps with or without interruptions to the network using the information element 402. For example, the information element 402 may comprise a NeedForlnterruptionlnfoNR IE. The IE NeedForlnterruptionlnfoNR indicates whether interruption is needed for the UE 202 to perform SSB based measurements on an NR target band without measurement gap while NR-DC or NE-DC is not configured. The IE NeedForlnterruptionlnfoNR includes an IE field 404 NeedForlnterruptionNR. This field includes a value interruptionindication that indicates whether interruption is needed for the UE 202 to perform SSB based measurements without measurement gap (e.g., no-gap value 408). A value no-gap-with- interruption as represented by no-gap-with-interruption value 410 indicates that interruption is needed. A value no-gap-no-interruption as represented by no-gap-no-interruption value 412 indicates interruption is not needed.

[0119] In various embodiments, the UE 202 may use the information element 402 and the IE field 404 to communicate other t pes of information, such as the operation mode 310, the frequency layer value 414, the frequency band value 416, and other UE values 418 (e.g.. hardware resources, software resources, radio resources, power resources, interfaces, etc.). Embodiments are not limited in this context.

[0120] FIG. 4B illustrates a more detailed view of a message format 420 or data schema suitable for communicating the UE configuration information 306. As depicted in FIG. 4B, the UE 202 may communicate UE configuration information 306 including the measurement configuration information 314 and / or the interruption configuration information 316 in a message defined in accordance with one or more 3GPP standards, such as the 3GPP TS 38.133 Standards and the 3GPP TS 38.331 Standards, for example. For instance, the message format 420 may be used to generate and encode one or more messages 302 as RRC messages. Embodiments are not limited to these examples.

[0121] In some embodiments, given the various combinations of configurable values for the UE capability information 304, a scenario occurs where the access node 200 receives one or more messages 302 from the UE 202 with the information element 422 implemented as the NeedForGapsInfoNR IE set to a no-gap value 408 and / or a needForlnterruptionlnfoNR IE set to a no-gap-with-interruption value 410. In such cases, the access node 200 prepares interruption configuration information 316. The interruption configuration information 316 defines when and how the UE 202 is allowed to cause interruptions while performing measurements on the frequency layers of the bands for which the no-gap-with-interruption is indicated. In some embodiments, for example, the interruption configuration information 316 is defined by 3GPP TS 38.133 Standards, including IE, IE fields, field values, and procedures.

[0122] The access node 200 sends the measurement configuration information 314 and the interruption configuration information 316 to the UE 202 via one or more RRC messages. For example, when the UE capability information 304 comprises a NeedForGapsInfoNR IE set to a no-gap value 408 and / or a needFor Interr uptionlnfoNR-r 18 IE set to a no-gap-with- interruption value 410, the access node 200 may send one or more messages 302 to the UE 202 with the measurement configuration information 314 and the interruption configuration information 316 indicating the UE 202 is allowed to measure intra- frequency and interfrequency measurement objects without a measurement gap but with interruptions. The interruption configuration information 316 may comprise a set of interruption configuration parameters to define, manage and control interruptions performed by the UE 202. For example, the access node 200 sends the measurement configuration information 314 and interruption configuration information 316 in the information element 422 of one or more messages 302, such as an RRC Connection Reconfiguration message as defined by the 3GPP TS 38.331 Standards.

[0123] In various embodiments, the access node 200 generates, encodes, and sends the interruption configuration information 316 in accordance with the 3GPP TS 38.133 Standards as defined in Section 8.2.2.2.19 titled “Interruptions due to measurements without gap carried out by UE supporting [NeedForInterruptionInfoNR-R18}F Section 8.2.2.2.19 of the 3GPP TS 38.133 Standards as described with reference to FIG. 3. However, embodiments are not limited to this example.

[0124] The access node 200 tests for fulfillment of at least 3 conditions when determining whether to allow or deny the UE 202 permission to perform measurements without a measurement gap but with interruptions. The three conditions are whether the UE 202: (1) supports NeedFor InterruptionInfoNR-R18 measurements; (2) indicates no-gap-with- interruption value 410 on intra-frequency SSB-based or inter-frequency SSB-based measurements; and (3) operates in an SA operation mode. When the three conditions are TRUE, the access node 200 determines that the UE 202 is allowed to cause interruptions while performing measurements on the frequency layers of the bands for which no-gap- with-interruption value 410 is indicated by frequency layer value 438 and frequency band value 440. The access node 200 uses the interruption value 426 to indicate permission to perform interruptions during measurements is granted to the UE 202. When one or more of the three conditions are FALSE, the access node 200 determines that the UE 202 is denied its request to cause interruptions. The access node 200 uses the no-interruption value 428 to indicate permission to perform interruptions during measurements is denied to the UE 202.

[0125] When the UE 202 is allowed to cause interruptions (e.g., using interruption value 426), the access node 200 sets an interruption ratio value 430 to indicate an interruption ratio no more than the requirements specified below upon UE measurements on a specific frequency layer value 414 that corresponds to the configured MO, where Tcycie,i is the interruption cycle on a certain frequency layer i, specified in Table 8.2.2.2. 19-1, where CS SFoutside gap, i is defined in clause 9.1.5.1 for measurement conducted outside measurement gaps. The UE 202 is allowed to cause interruption on a certain frequency layer 2D i with the maximum interruption ratio that equals - . The total allowed maximum

[0126] Tcycle interruption ratio (D) on each of the active serving cells due to UE measurements without gap applied in this sub-clause is specified in Equation (1), where N is the total number of configured SSB based frequency layers to be measured outside gap including intrafrequency and inter-frequency target carriers where UE 202 indicates that interruption is needed through [no-gap-with-interruption] , and L is the maximum interruption length for each interruption occasion specified in the Table 8.2.2.2.19-2 and 8.2.2.2.19-3.

[0127] Table 8.2.2.2.19-2 defines an interruption length L in FR1. Table 8.2.2.2.19-3 defines an interruption length L in FR2.

[0128] In some cases, the access node 200 may send an interruption length value 432 to the UE 202 and / or an interruption occasion value 434 using an IE field 424 of the information element 422. The access node 200 may also use the information element 422 and other IE fields 424 to send other AN values 436, such as parameters for the measurement configuration information 314. Embodiments are not limited to these examples.

[0129] 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.331 Standards, or other 3GPP standards or non-3GPP standards. Embodiments are not limited in this context.

[0130] As depicted in FIG. 5, the apparatus 500 may comprise a processor circuitry' 504, a memory7506 with a measurement manager 510, a memory' interface 518, a data storage device 522, and radio-frequency (RF) circuitry' 520. The memory' interface 518 may store machine-readable instructions (e.g., program code) for software applications that when executed causes the software applications to perform certain defined functions. Non-limiting examples of the applications may include an encoder / decoder such as codec 508 and a measurement generator 502. The codec 508 encodes and decodes messages 302. The measurement generator 502 performs measurements for the UE 202 using one or more sensors. The apparatus 500 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.

[0131] The apparatus 500 for the UE 202 may receive one or more messages 302 from an access node 200 via the RF circuitry 520. The access node 200 may comprise part of a RAN node 1 318 or a RAN node 2 320 implemented as, for example, a NodeB. an eNB, or a gNB 206 of the wireless communications system 100.

[0132] The codec 508 receives and decodes encoded messages 302 from the access node 200. The codec 508 encodes and sends encoded messages 302 to the access node 200. The messages 302 may include, among other types of information, the operation mode 310 and the interruption information 312 using the IE field 404 of the information element 402. The messages 302 may include, among other Npes of information, the measurement configuration information 314 and the interruption configuration information 316 using the IE field 424 of the information element 422.

[0133] The measurement manager 510 receives the decoded information and performs measurements based on the measurement configuration information 314 and the interruption configuration information 316. For example, the measurement manager 510 extracts one or more values from the IE fields 424 of the information element 422, and it stores them in memory 506. Based on these values, the measurement generator 502 retrieves a measurement object 512, a set of one or more measurement criteria 514, and it begins to generate measurement values 516 according to the set of measurement criteria 514.

[0134] A measurement object 512 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 512 is used in the context of various measurement procedures and functions within the 5G or 6G network. Examples for the measurement object 512 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 206 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 206. 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 512 in 5G or 6G. Measurement object 512 is used for performance monitoring, network optimization, and providing relevant information for efficient and reliable communication in the network.

[0135] For example, the measurement object 512 may include the reference signals communicated between the UE 202 and the RAN node 1 318 and the RAN node 2 320, respectively. In this case, the measurement object 512 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.

[0136] The apparatus 500 for the UE 202 may include the memory interface 518. The memory interface 518 may be arranged to send or receive, to or from a data storage device 522 or a data storage device 522, UE measurement information 308 such as measurement object 512 for a 5G NR or 6G system. The data storage device 522 may be located external to the UE 202 (off-device) or the data storage device 522 may be located internal to the UE 202 (on-device). When the data storage device 522 is implemented on-device, the data storage device 522 may comprise volatile or non-volatile memory, as described in more detail with reference to FIG. 12.

[0137] The UE measurement information 308 may comprise one or more measurement values 516 as measured by the measurement generator 502 and / or measurement criteria 514 for the UE 202. The UE 202 may be provisioned with the measurement criteria 514 by an original equipment manufacturer (OEM) or as received from the access node 200 via RRM, RRC. or other control signaling.

[0138] FIG. 6 illustrates a logic diagram 600. The logic diagram 600 is an example of a UE 202 performing measurement operations to generate UE measurement information 308 in accordance with the UE capability information 304 and / or the UE configuration information 306. Specifically, the logic diagram 600 illustrates the UE 202 sharing measurements with interruptions based on the UE configuration information 306 from the access node 200.

[0139] As depicted in FIG. 6. the logic diagram 600 illustrates a sequence of SSBs 604, a sequence of measurement gaps 606, and four SSB measurement timing configuration (SMTC) for target carriers 1 (SMTC1), 2 (SMTC2), 3 (SMTC3), and 4 (SMTC4). It may be appreciated that the number of target carriers can be set to any number as needed for a given implementation. The SMTC is configured by the network and specifies the timing window during which the UE 202 should perform measurements on the SSBs 604 of a target cell or carrier. This is because, in 5G NR, cells may transmit SSBs 604 in bursts, and the UE 202 needs to know when to expect these transmissions to measure signal quality accurately.

[0140] Some roles of the SMTC include measurement timing, beam management, and mobility and handover. For measurement timing, it provides the timing information so that the UE 202 knows exactly when to monitor and measure SSBs 604 for neighboring cells. This prevents the UE 202 from performing measurements outside of the scheduled time, which would be inefficient or even impossible in some scenarios. For beam management, 5G NR heavily relies on beamforming, where SSBs 604 are transmitted across multiple beams. The SMTC helps the UE 202 to measure the beams from neighboring cells at the correct time. This is important for processes like beam selection, beam switching, and handovers between cells. For mobility and handover, during mobility procedures, such as handover from one cell to another, the UE 202 uses SMTC to perform measurements on potential target cells (neighbors). The timing configuration ensures that measurements are done during the appropriate windows, allowing the network to make accurate handover decisions based on the measurement reports from the UE 202.

[0141] SMTC is particularly important in inter-frequency and inter-RAT measurements. For example, when the UE 202 needs to measure SSBs 604 on a different frequency band or across different RATs (such as measuring between LTE and 5G NR), the SMTC window ensures that the UE 202 knows when to tune to the target frequency and perform the necessary measurements.

[0142] The logic diagram 600 illustrates a case where if a measurement gap 606 is configured and the gap occasions are partially or fully overlapped with the SMTC occasions on a certain frequency layer that the UE 202 indicates no-gap-with-interruption, no interruption from measurements on such layer is allowed. This is because all the measurements with interruption are required to be carried out within the configured measurement gaps 606. Even though the measurements do not necessarily require a measurement gap 606, forcing the UE 202 to perform measurements within the measurement gaps 606 avoids unnecessary interruptions. For example, the UE 202 may perform measurements within a measurement occasion 602 without interruption. FIG. 7 illustrates an apparatus 700 suitable for implementation as an access node 200 in the wireless communications system 100. The access node 200 is an example of the gNB 206. As previously discussed, the access node 200 may receive UE capability7information 304, such as operation mode 310 and interruption information 312, from the UE 202. The access node 200 may send UE configuration information 306, such as measurement configuration information 314 and interruption configuration information 316, to the UE 202. The access node 200 may use the UE capability information 304 to generate the interruption configuration information 316 based on one or more criteria defined by the 3GPP TS 38.133 Standards, the 3GPP TS 38.331 Standards, or other 3GPP standards or non-3GPP standards. Embodiments are not limited in this context.

[0143] As depicted in FIG. 7, the apparatus 700 may comprise a processor circuitry 702, a memory 704, a memory interface 728, a data storage device 730, and RF circuitry 732. The memory interface 728 may store machine-readable instructions (e.g., program code) for software applications that when executed causes the software applications to perform certain defined functions. Non-limiting examples of the applications may include an encoder / decoder such as codec 706 and a scheduler 216. The codec 706 encodes and decodes messages 302. The scheduler 216 operates to schedule measurements, measurement gaps, and interruptions, among other functions as described with reference to FIG. 2 . The apparatus 700 may optionally include a set of platform components (not shown) suitable for an access node 200, such as input / output devices, memory controllers, different memory types, network interfaces, hardware ports, and so forth.

[0144] The apparatus 700 for the access node 200 may receive one or more messages 302 from one or more UEs 202 via the RF circuitry' 732. The access node 200 may comprise part of a RAN node 1 318 or a RAN node 2 320 implemented as, for example, a NodeB, an eNB, or a gNB 206 of the wireless communications system 100.

[0145] The codec 706 receives and decodes encoded messages 302 from the UE 202. The codec 508 encodes and sends encoded messages 302 to the UE 202. The messages 302 may include, among other types of information, the operation mode 310 and the interruption information 312 using the IE field 404 of the information element 402. The messages 302 may include, among other ty pes of information, the measurement configuration information 314 and the interruption configuration information 316 using the IE field 424 of the information element 422.

[0146] The access node 200 includes a memory interface 728 to send or receive, to or from a data storage device 730, the interruption information 312, the measurement configuration information 314. the interruption configuration information 316. and / or UE measurement information 308 for a wireless communications system 100. The access node 200 also includes processor circuitry 702 communicatively coupled to the memory interface 728, the processor circuitry 702 to execute a codec 706 to decode a message from a UE 202 with UE capability information 304. The UE capability information 304 may comprise an information element 402 with an operation mode 310 and / or an interruption information 312 to indicate whether the UE supports measurements of a measurement object 512 with or without a measurement gap 606. A schedule manager 708 may determine whether the interruption information 312 for the information element 402 indicates the UE 202 supports measurements of the measurement object 512 with or without the measurement gap 606.

[0147] When the schedule manager 708 determines the UE 202 supports measurements of the measurement object 512 with the measurement gap, the schedule manager 708 schedules a measurement gap for the UE 202. The schedule manager 708 then includes the measurement gap in UE configuration information 306, and forwards the UE configuration information 306 to the UE 202.

[0148] When the schedule manager 708 determines the UE 202 supports measurements of the measurement object 512 without the measurement gap 606, the schedule manager 708 determines whether the UE 202 is allowed to cause interruptions while performing measurements of the measurement object 512 without the measurement gap 606 based on the interruption information 312. In one embodiment, the schedule manager 708 makes this determination based on the criteria set forth in Section 8.2.2.2.19 of the 3GPP TS 38.133 Standards as described with reference to FIG. 3, FIG. 4A, and FIG. 4B.

[0149] The access node 200 tests for fulfillment of at least 3 conditions when determining whether to allow or deny the UE 202 permission to perform measurements without a measurement gap but with interruptions. The three conditions are whether the UE 202: (1) supports NeedForInterruptionInfoNR-R18 measurements; (2) indicates no-gap-with- interruption value 410 on intra-frequency SSB-based or inter-frequency SSB-based measurements; and (3) operates in an SA operation mode. When the three conditions are TRUE, the access node 200 determines that the UE 202 is allowed to cause interruptions while performing measurements on the frequency layers of the bands for which no-gap- with-interruption value 410 is indicated by frequency layer value 438 and frequency band value 440. The access node 200 uses the interruption value 426 to indicate permission to perform interruptions during measurements is granted to the UE 202. When one or more of the three conditions are FALSE, the access node 200 determines that the UE 202 is denied its request to cause interruptions. The access node 200 uses the no-interruption value 428 to indicate permission to perform interruptions during measurements is denied to the UE 202.

[0150] When the UE 202 is allowed to cause interruptions (e.g., using interruption value 426), the access node 200 sets an interruption ratio value 430 to indicate an interruption ratio no more than the requirements specified below upon UE measurements on a specific frequency layer value 414 that corresponds to the configured MO, where Tcycie,i is the interruption cycle on a certain frequency layer i, specified in Table 8.2.2.2. 19-1, where CS SFoutside gap, i is defined in clause 9.1.5.1 for measurement conducted outside measurement gaps. The UE 202 is allowed to cause interruption on a certain frequency layer 2D i with the maximum interruption ratio that equals - . The total allowed maximum

[0151] Tcycle interruption ratio (D) on each of the active serving cells due to UE measurements without gap applied in this sub-clause is specified in Equation (1), where N is the total number of configured SSB based frequency layers to be measured outside gap including intrafrequency and inter-frequency target carriers where UE 202 indicates that interruption is needed through [no-gap-with-interruption] , and L is the maximum interruption length for each interruption occasion specified in the Table 8.2.2.2.19-2 and 8.2.2.2.19-3.

[0152] Table 8.2.2.2.19-2 defines an interruption length L in FR1. Table 8.2.2.2.19-3 defines an interruption length L in FR2.

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

[0154] 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, the access node 200, the UE 202, the operating environment 300, the message format 400, the message format 420, the apparatus 500, the logic diagram 600, and / or the apparatus 700. More particularly, the logic flow 800 illustrates a use case where the access node 200 may use the UE capability information 304 carried by the information element 402 to perform scheduling for measurement operations made by the UE 202. Embodiments are not limited in this context.

[0155] In block 802. logic flow 800 decodes an encoded message from user equipment (UE) with UE capability information, the message comprising an information element carrying interruption information that indicates the UE supports measurements without a measurement gap but with interruptions. In block 804, logic flow 800 determines whether to allow the UE to cause interruptions while performing measurements based on the interruption information from the UE and an interruption ratio or an interruption length for the interruptions caused by the UE. In block 806, logic flow 800 optionally generates interruption configuration information defining the interruption ratio or the interruption length for the interruptions caused by the UE when the UE is allowed to cause interruptions. In block 808, logic flow 800 encodes a message for the UE to allow the UE to perform measurements without the measurement gap but with the interruptions.

[0156] By way of example, with reference to apparatus 700 for the access node 200, the apparatus 700 includes a memory interface 728 to communicate information for a wireless communications system 100. The apparatus 700 also includes processor circuitry 702 operably coupled to the memory7interface 728 to decode an encoded message from UE 202 with UE capability information 304. The message includes an information element 402 carrying interruption information 312 that indicates the UE 202 supports measurements without a measurement gap 606 but with interruptions. The scheduler 216 of the apparatus 700 determines whether to allow the UE 202 to cause interruptions while performing measurements based on the interruption information 312 from the UE 202 along with information from other UEs 202 within a same serving cell as the UE 202. The scheduler 216 makes this determination using a set of conditions or parameters for the UE 202 and the other UEs 202 within the primary cell of the UE 202. For example, the scheduler 216 makes this determination based on an interruption ratio value 430 or an interruption length value 432 for the interruptions caused by the UE 202 as defined in the 3GPP TS 38.133 Standards.

[0157] When the scheduler 216 determines to allow the UE 202 to cause interruptions while performing measurements without a measurement gap 606, it notifies the UE 202 in one of multiple ways. In a first technique, the scheduler 216 notifies the UE 202 that it is allowed to perform measurements without measurement gap but with interruptions using normal measurement configuration messages and IE fields. The UE 202 is configured to understand that when it receives and decodes the measurement configuration messages and measurement configuration IE fields that authorize measurements without measurement gap but with interruptions, it is also authorized to cause interruptions when performing measurements. It may retrieve and use a set of interruption parameters, such as an interruption ratio value 430 or an interruption length value 432 for the interruptions caused by the UE 202, that are stored in local memory' when performing interruptions. For example, an original equipment manufacturer (OEM) may provision a UE 202 with this information. In a second technique, the scheduler 216 optionally generates interruption configuration information 316 defining an interruption ratio value 430 or an interruption length value 432 for the interruptions caused by the UE 202. The codec 706 encodes a message for the UE 202 with the interruption configuration information 316. The message may be an existing RRC message using existing IE fields, a new RRC message using new IE fields, or a combination of both. Embodiments are not limited in this context.

[0158] To assist in making its decision, the scheduler 216 determines whether the UE 202 is in a SA operation mode based on an operation mode 310 value set for an IE field 404 of the information element 402. The SA operation mode is an operation mode where the UE 202 is configured with at least a primary' cell (PCell) and not any multi-radio dual connectivity' (MR-DC). In some embodiments, the scheduler 216 determines to allow the UE to cause interruptions while performing measurements only when the UE 202 is in the SA operation mode.

[0159] In some embodiments, the information element 402 is a NeedForlnlerruptionlnfoNR- rl8 information element that carries interruption information such as a no-gap-with- interruption value 410 on intra-frequency synchronization signal block (SSB)-based or inter-frequency SSB-based measurements. Specifically, the information element 402 is a NeedForInterruptionInfoNR-rl8 information element that includes an IE field 404 such as an NeedForInterruptionNR-rI8 field to indicate whether interruption is needed for the UE 202 to perform synchronization signal block (SSB) based measurements without measurement gap 606. The NeedForlnterruptionNR-r 18 field carries an interruptionindication or interruptionlndication-r!8 set to a no-gap-with-interruption value 410 that indicates interruption is needed or a no-gap-no-interruption value 412 that indicates interruption is not needed.

[0160] In some embodiments, the scheduler 216 may determine and / or generate the interruption configuration information 316 based on the indication that the UE 202 is allowed to cause interruptions while performing measurements on frequency layers of frequency bands for which the interruption information 312 is indicated, such as by frequency layer value 414 and frequency band value 416. In some embodiments, the scheduler 216 may determine and / or generate the interruption configuration information 316 based on the indication that the UE 202 is allowed to cause interruptions on a certain frequency layer i with a maximum interruption 2L ratio that equals - , where L is a maximum interruption length for each interruption * Cycle. i T occasion andcycIe'tis an interruption cycle on the certain frequency layer i.

[0161] In some embodiments, the scheduler 216 may determine and / or generate a total allowed maximum interruption ratio (D) on an active serving cell due to UE measurements without gap based on Equation (1) as D ~ , where Vis a total number of configured synchronization signal block (SSB) based frequency layers to be measured outside gap including intra-frequency and inter-frequency target carriers where the UE 202 indicates that interruption is needed through the interruption parameter, and L is a maximum interruption length for each interruption occasion.

[0162] In some embodiments, the apparatus 700 for the access node 200 may include RF circuitry 732 operably coupled to the processor circuitry 702. The RF circuitry 732 is arranged to receive the encoded message from the UE 202 and send the encoded message to the UE 202 as RF signals 204. The encoded messages may comprise, for example, RRC messages. Embodiments are not limited to these example embodiments.

[0163] FIG. 9 illustrates an embodiment of a logic flow 900. The logic flow 900 may be representative of some or all of the operations executed by one or more embodiments described herein. For example, the logic flow 900 may include some or all of the operations performed by devices or entities within the wireless communications system 100, the access node 200, the UE 202, the operating environment 300, the message format 400, the message format 420, the apparatus 500, the logic diagram 600, and / or the apparatus 700. More particularly, the logic flow 900 illustrates a use case where the UE 202 may use the UE configuration information 306 carried by the information element 422 to perform measurement operations made by the UE 202. Embodiments are not limited in this context.

[0164] In block 902, logic flow 900 encodes a message with UE capability information for an access node, the encoded message includes an information element carrying interruption information that indicates the UE supports measurements without a measurement gap but with interruptions. In block 904. logic flow 900 optionally encodes a message for the access node indicating the UE is in a standalone (SA) operation mode where the UE is configured with at least a primary cell (PCell) and not any multi-radio dual connectivity (MR-DC). In block 906, logic flow 900 decodes an encoded message from the access node that indicates the UE is allowed to perform measurements without the measurement gap but with the interruptions. In block 908, logic flow 900 performs measurements based on the interruption configuration information perform measurements based on an interruption ratio or an interruption length defined by the access node. In block 910, logic flow 900 encodes a message with a measurement report includes the measurements for the access node.

[0165] By way of example, with reference to apparatus 500 for UE 202, the apparatus 500 includes a memory interface 518 to communicate information for a wireless communications system 100. The apparatus 500 also includes processor circuitry 504 operably coupled to the memory interface 518. The codec 508 of the apparatus 500 encodes a message with UE capability7information 304 for an access node 200. The encoded message includes an information element 402 carrying interruption information 312 that indicates the UE 202 supports measurements without a measurement gap but with interruptions. The codec 508 decodes an encoded message from the access node 200 that indicates the UE 202 is allowed to perform measurements without the measurement gap but with the interruptions.

[0166] The UE 202 may obtain interruption parameters to perform the interruptions using multiple techniques. In a first technique, the scheduler 216 notifies the UE 202 that it is allowed to perform measurements without measurement gap but with interruptions using normal measurement configuration messages and IE fields. The UE 202 is configured to understand that when it receives and decodes the measurement configuration messages and measurement configuration IE fields that authorize measurements without measurement gap but with interruptions, it is also authorized to cause interruptions when performing measurements. The UE 202 may retrieve and use a set of interruption parameters, such as an interruption ratio value 430 or an interruption length value 432 for the interruptions caused by the UE 202, that are stored in local memory when performing interruptions. For example, an original equipment manufacturer (OEM) may provision a UE 202 with this information. In a second technique, the scheduler 216 optionally generates interruption configuration information 316 defining an interruption ratio value 430 or an interruption length value 432 for the interruptions caused by the UE 202. The codec 706 encodes a message for the UE 202 with the interruption configuration information 316. The message may be an existing RRC message using existing IE fields, a new RRC message using new IE fields, or a combination of both. The codec 508 decodes the encoded message with interruption configuration information 316 from the access node 200. The interruption configuration information 316 defines an interruption ratio or an interruption length for the interruptions caused by the UE 202 as indicted by the interruption ratio value 430 and the interruption length value 432, respectively. The UE 202 performs measurements based on the interruption configuration information 316. The codec 508 encodes a message with a measurement report that includes the measurement values 516 for the access node 200.

[0167] To assist the scheduler 216 of the access node 200 in making a decision, the UE 202 sends operation mode 310 in an IE field 404 of the information element 402 to indicate it is in a SA operation mode. The SA operation mode is an operation mode where the UE 202 is configured with at least a primary' cell (PC ell) and not any multi-radio dual connectivity (MR-DC). In some embodiments, the scheduler 216 determines to allow the UE to cause interruptions while performing measurements only when the UE 202 is in the SA operation mode.

[0168] In some embodiments, the information element 402 is a NeedForlnterruptionlnfoNR- rl8 information element that carries interruption information such as a no-gap-with- interruption value 410 on intra-frequency synchronization signal block (SSB)-based or inter-frequency SSB-based measurements. Specifically, the information element 402 is a NeedForlnterruptionlnfoNR-r 18 information element that includes an IE field 404 such as an NeedForlnterruptionNR-r 18 field to indicate whether interruption is needed for the UE 202 to perform synchronization signal block (SSB) based measurements without measurement gap 606. The NeedForlnterruptionNR-r 18 field carries an interruptionindication or interruptionlndication-r 18 set to a no-gap-with-interruption value 410 that indicates interruption is needed or a no-gap-no-interruption value 412 that indicates interruption is not needed.

[0169] In some embodiments, the scheduler 216 may determine and / or generate the interruption configuration information 316 based on the indication that the UE 202 is allowed to cause interruptions while performing measurements on frequency layers of frequency bands for which the interruption information 312 is indicated, such as by frequency layer value 414 and frequency band value 416. The UE 202 then performs measurements using the frequency layer value 414 and frequency band value 416.

[0170] In some embodiments, the scheduler 216 may determine and / or generate the interruption configuration information 316 based on the indication that the UE 202 is allowed to cause interruptions on a certain frequency layer i with a maximum interruption 2L ratio that equals - , where L is a maximum interruption length for each interruption occasion and cydej, is an interruption cycle on the certain frequency layer i. The UE 202 then performs measurements using the interruption configuration information 316. In some embodiments, the scheduler 216 may determine and / or generate a total allowed maximum interruption ratio (D) on an active serving cell due to UE measurements 2L without gap based on Equation (1) as - , where / Vis a total number of

[0171] , l1cycle i configured synchronization signal block (SSB) based frequency layers to be measured outside gap including intra-frequency and inter-frequency target carriers where the UE 202 indicates that interruption is needed through the interruption parameter, and L is a maximum interruption length for each interruption occasion. The UE 202 then performs measurements using the interruption configuration information 316.

[0172] In some embodiments, the apparatus 500 for the UE 202 may include RF circuitry 520 operably coupled to the processor circuitry 504. The RF circuitry 520 is arranged to receive the encoded message from the access node 200 and send the encoded message to the access node 200 as RF signals 204. The encoded messages may comprise, for example, RRC messages. Embodiments are not limited to these example embodiments.

[0173] FIG. 9 illustrates a network architecture 900. FIG. 9 illustrates block diagrams of NF components (NFs) and interfaces in connection with embodiments / aspects described herein. In the 5G network architecture of FIG. 9, a next generation (NG) radio access network (RAN) (NG-RAN) comprises a functional split feature that splits a gNodeB (gNB) (also referred to as an “NG RAN,” “NG RAN node,” or the like) into a gNB-Centralized Unit (CU) (gNB-CU) that implements the upper layer of gNB function and gNB-Distributed Unit (DU) (gNB-DU) that implements the lower layer gNB function. The 5G core NFs and gNB- CU can be implemented as Virtualized Network Functions (VNFs), and the gNB-CU and / or gNB-DU can be implemented as Physical Network Function(s) (PNF(s). An Operator can create a virtualized 5G networks by using the European Telecommunications Standards Institute (ETSI) network functions virtualization (NFV) lifecycle management function to instantiate a Network Service (NS) in the cloud that includes various VNFs (e.g., 5G core NFs, gNB-CU), PNFs (e.g. gNB-DU), and VNF Forwarding Graph(s) (VNFFG(s)).

[0174] FIG. 9 illustrates an architecture of a network architecture 900 including a second CN 902 in accordance with various embodiments. The network architecture 900 is similar to the wireless communication system 200, and may illustrate equipment, devices and network elements similar to those described with reference to the wireless communication system 200. As depicted in FIG. 9, the network architecture 900 includes a user equipment (UE) 928, a RAN 930 or access node (AN); and a DN 934, which can all be the same or similar to similarly named elements as discussed herein. The DN 934 is the same or similar to the DN 234, and it can implement, for example, operator services, Internet access or 3rd party services, as discussed further below. The CN 214 may be implemented as a 5GC or 5GS, and it can include an Authentication Server Function (AUSF) 920; an AMF 922; an SMF 924; a NEF 908; a PCF 912; an NRF 910; a Unified Data Management (UDM) 914; an application function (AF) 916; an LMF 926; a user plane function (UPF) 932; Network Slice-Specific Authentication and Authorization Function (NSSAAF) 918; and an NSSF 906, each with respective components for processing corresponding 5GC network functions (NFs).

[0175] The UPF 932 can act as an anchor point for intra-RAT and inter-RAT mobility, an external protocol data unit (PDU) session point of interconnect to DN 203, and a branching point to support multi-homed PDU session. The UPF 932 can 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, uplink (UL)Zdownlink (DL) rate enforcement), perform Uplink Traffic verification (e.g., Service Data Flow (SDF) to Quality of Service (QoS) flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 932 can include an uplink classifier to support routing traffic flows to a data network. The DN 934 can represent various network operator services, Internet access, or third party7services. DN 934 can include, or be similar to, application server XQ30 discussed previously. The UPF 932 can interact with the SMF 924 via an N4 reference point between the SMF 924 and the UPF 932.

[0176] The AUSF 920 can store data for authentication of UE 302 and handle authentication-related functionality. The AUSF 920 can facilitate a common authentication framework for various access types. The AUSF 920 can communicate with the AMF 922 via an N12 reference point between the AMF 922 and the AUSF 920; and can communicate with the UDM 914 via an N13 reference point between the UDM 914 and the AUSF 920. Additionally, the AUSF 920 can exhibit an Nausf service-based interface.

[0177] The AMF 922 can be responsible for registration management (e.g., for registering UE 302, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization. The AMF 922 can be a termination point for an N 11 reference point between the AMF 922 and the SMF 924. The AMF 922 can provide transport for SM messages between the UE 302 and the SMF 924, and act as a transparent proxy for routing SM messages. AMF 922 can also provide transport for SMS messages between UE 302 and a Short Message Service (SMS) function (SMSF) (not shown by FIG. 9). AMF 922 can act as Security Anchor Function (SEAF), which can include interaction with the AUSF 920 and the UE 302, receipt of an intermediate key that was established as a result of the UE 302 authentication process. Where Universal Subscriber Identity Module (USIM) based authentication is used, the AMF 922 can retrieve the security material from the AUSF 920. AMF 922 can also include a Security Context Management (SCM) function, which receives a key from the SEAF that it uses to derive access-network specific keys. Furthermore, AMF 922 can be a termination point of a RAN CP interface or RAN connection point interface, which can include or be an N2 reference point between the RAN 930 and the AMF 922; and the AMF 922 can be a termination point of Non Access Stratum (NAS) layer (Nl) signaling, and perform NAS ciphering and integrity protection.

[0178] AMF 922 can also support NAS signaling with a UE 302 over an N3 Interworking Function (IWF) interface. The N3 IWF can be used to provide access to untrusted entities. N3IWF can be a termination point for the N2 interface between the RAN 930 and the AMF 922 for the control plane, and can be a termination point for the N3 reference point between the RAN 930 and the UPF for the user plane. As such, the AMF 922 can handle N2 signaling from the SMF 924 and the AMF 922 for PDU sessions and QoS, encapsulate / de- encapsulate packets for IPSec and N3 tunneling, mark N3 user-plane packets in the uplink, and enforce QoS corresponding to N3 packet marking considering QoS requirements associated with such marking received over N2. N3IWF can also relay uplink and downlink control-plane NAS signaling between the UE 302 and AMF 922 via an Nl reference point between the UE 302 and the AMF 922, and relay uplink and downlink user-plane packets between the UE 302 and UPF 932. The N3IWF also provides mechanisms for IPsec tunnel establishment with the UE 302. The AMF 922 can exhibit an Namf service-based interface, and can be a termination point for an N14 reference point between two AMFs and an N17 reference point between the AMF 922 and a 5G-Equipment Identity Register (E1R) (not shown by FIG. 9).

[0179] The UE 302 can need to register with the AMF 922 in order to receive network services. Registration Management (RM) is used to register or deregister the UE 302 with the network (e g., AMF 922), and establish a UE context in the network (e g., AMF 922). The UE 302 can operate in an RM-REGISTERED state or an RM-DEREGISTERED state. In the RM-DEREGISTERED state, the UE 302 is not registered with the network, and the UE context in AMF 922 holds no valid location or routing information for the UE 302 so the UE 302 is not reachable by the AMF 922. In the RM-REGISTERED state, the UE 302 is registered with the network, and the UE context in AMF 922 can hold a valid location or routing information for the UE 302 so the UE 302 is reachable by the AMF 922. In the RM- REGISTERED state, the UE 302 can perform mobility Registration Update procedures, perform periodic Registration Update procedures triggered by expiration of the periodic update timer (e.g., to notify the network that the UE 302 is still active), and perform a Registration Update procedure to update UE capability information or to re-negotiate protocol parameters with the network, among others.

[0180] The AMF 922 can store one or more RM contexts for the UE 302, where each RM context is associated with a specific access to the network. The RM context can be a data structure, database object, etc. that indicates or stores, inter alia, a registration state per access type and the periodic update timer. The AMF 922 can also store a 5GC MM context that can be the same or similar to the (E)MM context discussed previously. In various embodiments, the AMF 922 can store a CE mode B Restriction parameter of the UE 302 in an associated MM context or RM context. The AMF 922 can also derive the value, when needed, from the UE's usage setting parameter already stored in the UE context (and / or MM / RM context).

[0181] Connection Management (CM) can be used to establish and release a signaling connection between the UE 302 and the AMF 922 over the N1 interface. The signaling connection is used to enable NAS signaling exchange between the UE 302 and the CN 902, and comprises both the signaling connection between the UE and the Access Network (AN) (e.g.. Radio Resource Control (RRC) connection or UE-N3IWF connection for non-3GPP access) and the N2 connection for the UE 302 between the AN (e g., RAN 930) and the AMF 922. The UE 302 can operate in one of two CM states, CM-IDLE mode or CM- CONNECTED mode. When the UE 302 is operating in the CM-IDLE state / mode, the UE 302 can have no NAS signaling connection established with the AMF 221 over the N1 interface, and there can be RAN 930 signaling connection (e.g., N2 and / or N3 connections) for the UE 302. When the UE 302 is operating in the CM-CONNECTED state / mode, the UE 302 can have an established NAS signaling connection with the AMF 922 over the N1 interface, and there can be a RAN 930 signaling connection (e g., N2 and / or N3 connections) for the UE 302. Establishment of an N2 connection between the RAN 930 and the AMF 922 can cause the UE 302 to transition from CM-IDLE mode to CM- CONNECTED mode, and the UE 302 can transition from the CM-CONNECTED mode to the CM-IDLE mode when N2 signaling between the RAN 930 and the AMF 922 is released.

[0182] The SMF 924 can be responsible for SM (e.g., session establishment, modify and release, including tunnel maintain between UPF and AN node); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement 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 over N2 to AN; and determining SSC mode of a session. SM can refer to management of a PDU session, and a PDU session or ‘'session” can refer to a PDU connectivity service that provides or enables the exchange of PDUs between a UE 302 and a DN 934 identified by a Data Network Name (DNN). PDU sessions can be established upon UE 302 request, modified upon UE 302 and 5GC CN 902 request, and released upon UE 302 and 5GC CN 902 request using NAS SM signaling exchanged over the N1 reference point between the UE 302 and the SMF 924. Upon request from an application server, the 5GC CN 902 can trigger a specific application in the UE 302. In response to receipt of the trigger message, the UE 302 can pass the trigger message (or relevant parts / information of the trigger message) to one or more identified applications in the UE 302. The identified application(s) in the UE 302 can establish a PDU session to a specific DNN. The SMF 924 can check whether the UE 302 requests are compliant with user subscription information associated with the UE 302. In this regard, the SMF 924 can retrieve and / or request to receive update notifications on SMF 924 level subscription data from the UDM 914.

[0183] The SMF 924 can include the following roaming functionality: handling local enforcement to apply QoS SLAs (VPLMN); charging data collection and charging interface (VPLMN); lawful intercept (in VPLMN for SM events and interface to LI system); and support for interaction with external DN 934 for transport of signaling for PDU session authorization / authentication by external DN 934. An N16 reference point between two SMFs 924 can be included in the network architecture 900, which can be between another SMF 924 in a visited network and the SMF 924 in the home network in roaming scenarios. Additionally, the SMF 924 can exhibit the Nsmf service-based interface.

[0184] The NEF 908 can provide means for securely exposing the services and capabilities provided by 3GPP network functions for third party, internal exposure / re-exposure, Application Functions (e.g., AF 916), edge computing or fog computing systems, etc. In such embodiments, the NEF 908 can authenticate, authorize, and / or throttle the AFs 916. NEF 908 can also translate information exchanged with the AF 916 and information exchanged with internal network functions. For example, the NEF 908 can translate between an AF-Service-Identifier and an internal 5GC information. NEF 908 can also receive information from other network functions (NFs) based on exposed capabilities of other network functions. This information can be stored at the NEF 908 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be reexposed by the NEF 908 to other NFs and AFs, and / or used for other purposes such as analytics. Additionally, the NEF 908 can exhibit an Nnef service-based interface.

[0185] The NRF 910 can 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 910 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,’' “instantiation.” and the like can refer to the creation of an instance, and an “instance” can refer to a concrete occurrence of an object, which can occur, for example, during execution of program code. Additionally, the NRF 910 can exhibit the Nnrf service-based interface.

[0186] The PCF 912 can provide policy rules to control plane function(s) to enforce them, and can also support unified policy framework to govern network behavior. The PCF 912 can also implement a front end (FE) to access subscription information relevant for policy decisions in a Uniform Data Repository7(UDR) or user datagram protocol of the UDM 914. The PCF 912 can communicate with the AMF 922 via an N15 reference point between the PCF 912 and the AMF 922, which can include a PCF 912 in a visited network and the AMF 922 in case of roaming scenarios. The PCF 912 can communicate with the application function AF 916 via an N5 reference point between the PCF 912 and the AF 916; and with the SMF 924 via an N7 reference point between the PCF 912 and the SMF 924. The network architecture 900 and / or CN 902 can also include an N24 reference point between the PCF 912 (in the home network) and a PCF 912 in a visited network. Additionally, the PCF 912 can exhibit an Npcf service-based interface.

[0187] The UDM 914 can handle subscription-related information to support the network entities' handling of communication sessions, and can store subscription data of UE 302. For example, subscription data can be communicated between the UDM 914 and the AMF 922 via an N8 reference point between the UDM 914 and the AMF 922. The UDM 914 can include two parts, an application FE and a Uniform Data Repository (UDR) (the FE and UDR are not shown by FIG. 9). The UDR can store subscription data and policy data for the UDM 914 and the PCF 912, and / or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs UE 302) for the NEF 908. The Nudr service-based interface can be exhibited by the UDR to allow the UDM 914, PCF 912, and NEF 908 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 914 can include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends can 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. The UDR can interact with the SMF 924 via an N10 reference point between the UDM 914 and the SMF 924. UDM 914 can also support SMS management, wherein an SMS-FE implements the similar application logic as discussed previously. Additionally, the UDM 914 can exhibit the Nudm service-based interface.

[0188] The AF 916 can provide application influence on traffic routing, provide access to the NCE, and interact with the policy framework for policy control. The NCE can be a mechanism that allows the 5GC CN 902 and AF 916 to provide information to each other via NEF 908, which can be used for edge computing implementations. In such implementations, the network operator and third party services can be hosted close to the UE 302 access point of attachment to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network. For edge computing implementations, the 5GC can select a UPF 932 close to the UE 302 and execute traffic steering from the UPF 932 to DN 934 via the N6 interface. This can be based on the UE subscription data, UE location, and information provided by the AF 916. In this way, the AF 916 can influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 916 is considered to be a trusted entity, the network operator can permit AF 916 to interact directly with relevant NFs. Additionally, the AF 916 can exhibit a Naf servicebased interface.

[0189] The NSSF 906 can select a set of network slice instances serving the UE 302. The NSSF 906 can also determine allowed NSSAI and the mapping to the subscribed single Network Slice Selection Assistance Information (S-NSSAIs), if needed. The NSSF 906 can also determine the AMF 922 set to be used to serve the UE 302, or a list of candidate AMF 922 based on a suitable configuration and possibly by query ing the NRF 910. The selection of a set of network slice instances for the UE 302 can be triggered by the AMF 922 with which the UE 302 is registered by interacting with the NSSF 906, which can lead to a change of AMF 922. The NSSF 906 can interact with the AMF 922 via an N22 reference point between AMF 922 and NSSF 906; and can communicate with another NSSF 906 in a visited network via an N31 reference point (not shown by FIG. 9). Additionally, the NSSF 906 can exhibit an Nnssf service-based interface.

[0190] The CN 902 can include an SMSF, which can be responsible for SMS subscription checking and verification, and relaying SM messages to / from the UE 302 to / from other entities, such as an SMS-GMSC / IWMSC / SMS-router. The SMS can also interact with AMF 922 and UDM 914 for a notification procedure that the UE 302 is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM 914 when UE 302 is available for SMS).

[0191] The CN 902 can also include other elements that are not shown by FIG. 9, such as a Data Storage system / architecture, a 5G-EIR, a SEPP, and the like. The Data Storage system can include a SDSF. an UDSF, and / or the like. Any NF can store and retrieve unstructured data into / from the UDSF (e.g., UE contexts), via N18 reference point between any NF and the UDSF (not shown by FIG. 9. Individual NFs can share a UDSF for storing their respective unstructured data or individual NFs can each have their own UDSF located at or near the individual NFs. Additionally, the UDSF can exhibit an Nudsf service-based interface (not shown by FIG. 9. The 5G-EIR can be an NF that checks the status of PEI for determining whether particular equipment / entities are blacklisted from the network; and the SEPP can be a non-transparent proxy that performs topology hiding, message filtering, and policing on inter-PLMN control plane interfaces.

[0192] Additionally, there can be many more reference points and / or service-based interfaces between the NF services in the NFs; however, these interfaces and reference points have been omitted from FIG. 9 for clarity. In one example, the CN 902 can include an Nx interface, which is an inter-CN interface between the Mobility Management Entity (MME) and the AMF 922 in order to enable interworking between CN 902 and other CN. Other example interfaces / reference points can include an N5g-Equipment Identity Register (EIR) service-based interface exhibited by a 5G-EIR, an N27 reference point between the Network Repository Function (NRF) in the visited network and the NRF in the home network; and an N31 reference point between the NSSF in the visited network and the NSSF in the home network. Further, any of the above functions, entities, etc. can include or be comprised by a component as referred to herein.

[0193] The LMF 926 (or individual instances of the LMF 926) is a core network component responsible for determining and managing the geographical location of user equipment (UE). The LMF collects data from the radio network and various other sources to calculate the position of the UE using techniques like triangulation, time of arrival (TOA), and observed time difference of arrival (OTDOA). It supports both network-based and UE-based positioning methods, with the network or the UE itself calculating the location based on available signals. The LMF interacts with the 5G base stations (gNodeB) to gather necessary measurements, and it can also leverage Global Navigation Satellite Systems (GNSS) for more accurate positioning when necessary. In addition to its role in determining device location, the LMF is responsible for sharing this information with authorized entities, such as location-based services or emergency responders. The LMF is vital for enabling services like emergency calls, where precise location information is required, and for supporting Internet of Things (loT) applications where location tracking is necessary. It interfaces with other core network functions, like the Access and Mobility Management Function (AMF). and integrates seamlessly into the 5G service-based architecture to provide secure and reliable location services across various use cases. The LMF 926 may be deployed in a distributed manner. More than one LMF 926 can be present in the communication path between various NF Services. The LMF 926, although not an NF instance, can also be deployed distributed, redundant, and scalable.

[0194] The DN 934 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 server 210. In some implementations, the DN 934 may be, or include, one or more edge compute nodes. Additionally or alternatively, the DN 934 may be an Edge DN 934, which is a (local) Data Netw ork that supports the architecture for enabling edge applications. In these embodiments, the application server 210 may represent the physical hardware systems / devices providing app server functionality and / or the application software resident in the cloud or at an edge compute node that performs server function(s). In some embodiments, the application server 210 provides an edge hosting environment that provides support required for Edge Application Server's execution.

[0195] The Access Stratum (AS) layer in a 3GPP system is responsible for the radio communication between the user equipment (UE) and the radio access network (RAN). It handles tasks related to the physical transmission of data over the air interface, including managing the establishment, maintenance, and release of radio connections. The AS layer oversees the radio resource control (RRC), which handles signaling between the UE and the base station (gNodeB in 5G or eNodeB in 4G), and it ensures that data is transmitted efficiently and reliably over the wireless link. This layer is involved in functions such as scheduling, handovers, and ensuring quality of service (QoS) for different types of data traffic.

[0196] In contrast, the Non-Access Stratum (NAS) layer operates betw een the UE and the core network, managing higher-level signaling that is not directly tied to the radio access network. The NAS layer is responsible for tasks such as mobility management, session management, and security between the UE and the core network (like AMF in 5G or MME in 4G). It handles authentication, network registration, location tracking, and the establishment of IP sessions, ensuring secure communication. While the AS layer manages the radio connection, the NAS layer oversees the broader network functions, allowing the device to communicate securely and move seamlessly across different network areas.

[0197] FIG. 10 illustrates a network architecture 1000. FIG. 10 illustrates block diagrams of NF components (NFs) and interfaces in connection with embodiments / aspects described herein. In the 5G network architecture of FIG. 10, a next generation (NG) radio access network (RAN) (NG-RAN) comprises a functional split feature that splits a gNodeB (gNB) (also referred to as an “NG RAN,” “NG RAN node,” or the like) into a gNB-Centralized Unit (CU) (gNB-CU) that implements the upper layer of gNB function and gNB-Distributed Unit (DU) (gNB-DU) that implements the lower layer gNB function. The 5G core NFs and gNB-CU can be implemented as Virtualized Network Functions (VNFs), and the gNB-CU and / or gNB-DU can be implemented as Physical Network Function(s) (PNF(s). An Operator can create a virtualized 5G networks by using the European Telecommunications Standards Institute (ETSI) network functions virtualization (NFV) lifecycle management function to instantiate a Network Service (NS) in the cloud that includes various VNFs (e.g., 5G core NFs, gNB-CU), PNFs (e.g. gNB-DU), and VNF Forwarding Graph(s) (VNFFG(s)).

[0198] FIG. 10 illustrates an architecture of a network architecture 1000 including a second CN 1002 in accordance with various embodiments. The network architecture 1000 is similar to the wireless communication system 200, and may illustrate equipment, devices and network elements similar to those described with reference to the wireless communication system 200. As depicted in FIG. 10. the network architecture 1000 includes a user equipment (UE) 1028, a RAN 1030 or access node (AN); and a DN 1034, which can all be the same or similar to similarly named elements as discussed herein. The DN 1034 is the same or similar to the DN 234, and it can implement, for example, operator services, Internet access or 3rd party services, as discussed further below. The CN 214 may be implemented as a 5GC or 5GS, and it can include an Authentication Server Function (AUSF) 1020; an AMF 1022; an SMF 1024; a NEF 1008; a PCF 1012; an NRF 1010; a Unified Data Management (UDM) 1014; an application function (AF) 1016; an LMF 1026; a user plane function (UPF) 1032; Network Slice-Specific Authentication and Authorization Function (NSSAAF) 1018; and an NSSF 1006, each with respective components for processing corresponding 5GC network functions (NFs).

[0199] The UPF 1032 can act as an anchor point for intra-RAT and inter-RAT mobility’, an external protocol data unit (PDU) session point of interconnect to DN 203, and a branching point to support multi-homed PDU session. The UPF 1032 can 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, uplink (UL) / downlink (DL) rate enforcement), perform Uplink Traffic verification (e.g.. Service Data Flow (SDF) to Quality of Service (QoS) flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 1032 can include an uplink classifier to support routing traffic flows to a data network. The DN 1034 can represent various network operator services, Internet access, or third party services. DN 1034 can include, or be similar to, application server XQ30 discussed previously. The UPF 1032 can interact with the SMF 1024 via an N4 reference point between the SMF 1024 and the UPF 1032.

[0200] The AUSF 1020 can store data for authentication of UE 302 and handle authentication-related functionality . The AUSF 1020 can facilitate a common authentication framework for various access types. The AUSF 1020 can communicate with the AMF 1022 via an N12 reference point between the AMF 1022 and the AUSF 1020; and can communicate with the UDM 1014 via an N13 reference point between the UDM 1014 and the AUSF 1020. Additionally, the AUSF 1020 can exhibit an Nausf service-based interface.

[0201] The AMF 1022 can be responsible for registration management (e.g., for registering UE 302, etc.), connection management, reachability management, mobility management, and lawful interception of AMF -related events, and access authentication and authorization. The AMF 1022 can be a termination point for an N11 reference point between the AMF 1022 and the SMF 1024. The AMF 1022 can provide transport for SM messages between the UE 302 and the SMF 1024, and act as a transparent proxy for routing SM messages. AMF 1022 can also provide transport for SMS messages between UE 302 and a Short Message Service (SMS) function (SMSF) (not shown by FIG. 10). AMF 1022 can act as Security Anchor Function (SEAF). which can include interaction with the AUSF 1020 and the UE 302, receipt of an intermediate key that was established as a result of the UE 302 authentication process. Where Universal Subscriber Identity Module (USIM) based authentication is used, the AMF 1022 can retrieve the security material from the AUSF 1020. AMF 1022 can also include a Security Context Management (SCM) function, which receives a key from the SEAF that it uses to derive access-network specific keys. Furthermore, AMF 1022 can be a termination point of a RAN CP interface or RAN connection point interface, which can include or be an N2 reference point between the RAN 1030 and the AMF 1022; and the AMF 1022 can be a termination point of Non Access Stratum (NAS) layer (Nl) signaling, and perform NAS ciphering and integrity protection.

[0202] AMF 1022 can also support NAS signaling with a UE 302 over an N3 Interworking

[0203] Function (IWF) interface. The N3 IWF can be used to provide access to untrusted entities. N31WF can be a termination point for the N2 interface between the RAN 1030 and the AMF 1022 for the control plane, and can be a termination point for the N3 reference point between the RAN 1030 and the UPF for the user plane. As such, the AMF 1022 can handle N2 signaling from the SMF 1024 and the AMF 1022 for PDU sessions and QoS, encapsulate / de-encapsulate packets for IPSec and N3 tunneling, mark N3 user-plane packets in the uplink, and enforce QoS corresponding to N3 packet marking considering QoS requirements associated with such marking received over N2. N3IWF can also relay uplink and downlink control-plane NAS signaling between the UE 302 and AMF 1022 via an N1 reference point between the UE 302 and the AMF 1022, and relay uplink and downlink user-plane packets between the UE 302 and UPF 1032. The N3IWF also provides mechanisms for IPsec tunnel establishment with the UE 302. The AMF 1022 can exhibit an Namf service-based interface, and can be a termination point for an N14 reference point between two AMFs and an N17 reference point between the AMF 1022 and a 5G- Equipment Identity Register (EIR) (not shown by FIG. 10).

[0204] The UE 302 can need to register with the AMF 1022 in order to receive network services. Registration Management (RM) is used to register or deregister the UE 302 with the network (e.g., AMF 1022), and establish a UE context in the network (e.g., AMF 1022). The UE 302 can operate in an RM-REGISTERED state or an RM-DEREGISTERED state. In the RM-DEREGISTERED state, the UE 302 is not registered with the network, and the UE context in AMF 1022 holds no valid location or routing information for the UE 302 so the UE 302 is not reachable by the AMF 1022. In the RM-REGISTERED state, the UE 302 is registered with the network, and the UE context in AMF 1022 can hold a valid location or routing information for the UE 302 so the UE 302 is reachable by the AMF 1022. In the RM-REGISTERED state, the UE 302 can perform mobility Registration Update procedures, perform periodic Registration Update procedures triggered by expiration of the periodic update timer (e.g.. to notify the network that the UE 302 is still active), and perform a Registration Update procedure to update UE capability information or to re-negotiate protocol parameters with the network, among others.

[0205] The AMF 1022 can store one or more RM contexts for the UE 302, where each RM context is associated with a specific access to the network. The RM context can be a data structure, database object, etc. that indicates or stores, inter alia, a registration state per access type and the periodic update timer. The AMF 1022 can also store a 5GC MM context that can be the same or similar to the (E)MM context discussed previously. In various embodiments, the AMF 1022 can store a CE mode B Restriction parameter of the UE 302 in an associated MM context or RM context. The AMF 1022 can also derive the value, when needed, from the UE's usage seting parameter already stored in the UE context (and / or MM / RM context).

[0206] Connection Management (CM) can be used to establish and release a signaling connection between the UE 302 and the AMF 1022 over the N 1 interface. The signaling connection is used to enable NAS signaling exchange between the UE 302 and the CN 1002, and comprises both the signaling connection between the UE and the Access Network (AN) (e.g., Radio Resource Control (RRC) connection or UE-N3IWF connection for non-3GPP access) and the N2 connection for the UE 302 between the AN (e.g., RAN 1030) and the AMF 1022. The UE 302 can operate in one of two CM states, CM-IDLE mode or CM- CONNECTED mode. When the UE 302 is operating in the CM-IDLE state / mode, the UE 302 can have no NAS signaling connection established with the AMF 221 over the N1 interface, and there can be RAN 1030 signaling connection (e g., N2 and / or N3 connections) for the UE 302. When the UE 302 is operating in the CM-CONNECTED state / mode, the UE 302 can have an established NAS signaling connection with the AMF 1022 over the N1 interface, and there can be a RAN 1030 signaling connection (e.g., N2 and / or N3 connections) for the UE 302. Establishment of an N2 connection between the RAN 1030 and the AMF 1022 can cause the UE 302 to transition from CM-IDLE mode to CM-CONNECTED mode, and the UE 302 can transition from the CM-CONNECTED mode to the CM-IDLE mode when N2 signaling between the RAN 1030 and the AMF 1022 is released.

[0207] The SMF 1024 can be responsible for SM (e.g., session establishment, modify and release, including tunnel maintain between UPF and AN node); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement 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 over N2 to AN; and determining SSC mode of a session. SM can refer to management of a PDU session, and a PDU session or “session” can refer to a PDU connectivity service that provides or enables the exchange of PDUs between a UE 302 and a DN 1034 identified by a Data Network Name (DNN). PDU sessions can be established upon UE 302 request, modified upon UE 302 and 5GC CN 1002 request, and released upon UE 302 and 5GC CN 1002 request using NAS SM signaling exchanged over the N1 reference point between the UE 302 and the SMF 1024. Upon request from an application server, the 5GC CN 1002 can trigger a specific application in the UE 302. In response to receipt of the trigger message, the UE 302 can pass the trigger message (or relevant parts / information of the trigger message) to one or more identified applications in the UE 302. The identified application(s) in the UE 302 can establish a PDU session to a specific DNN. The SMF 1024 can check whether the UE 302 requests are compliant with user subscription information associated with the UE 302. In this regard, the SMF 1024 can retrieve and / or request to receive update notifications on SMF 1024 level subscription data from the UDM 1014.

[0208] The SMF 1024 can include the following roaming functionality': handling local enforcement to apply QoS SLAs (VPLMN); charging data collection and charging interface (VPLMN); lawful intercept (in VPLMN for SM events and interface to LI system); and support for interaction with external DN 1034 for transport of signaling for PDU session authorization / authentication by external DN 1034. An N16 reference point between two SMFs 1024 can be included in the network architecture 1000, which can be between another SMF 1024 in a visited network and the SMF 1024 in the home network in roaming scenarios. Additionally, the SMF 1024 can exhibit the Nsmf service-based interface.

[0209] The NEF 1008 can provide means for securely exposing the services and capabilities provided by 3GPP network functions for third party7, internal exposure / re-exposure, Application Functions (e.g., AF 1016), edge computing or fog computing systems, etc. In such embodiments, the NEF 1008 can authenticate, authorize, and / or throttle the AFs 1016. NEF 1008 can also translate information exchanged with the AF 1016 and information exchanged with internal network functions. For example, the NEF 1008 can translate between an AF-Service-Identifier and an internal 5GC information. NEF 1008 can also receive information from other netw ork functions (NFs) based on exposed capabilities of other network functions. This information can be stored at the NEF 1008 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be reexposed by the NEF 1008 to other NFs and AFs, and / or used for other purposes such as analytics. Additionally, the NEF 1008 can exhibit an Nnef service-based interface.

[0210] The NRF 1010 can 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 1010 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,’' “instantiation,” and the like can refer to the creation of an instance, and an “instance” can refer to a concrete occurrence of an object, which can occur, for example, during execution of program code. Additionally, the NRF 1010 can exhibit the Nnrf service-based interface. The PCF 1012 can provide policy rules to control plane function(s) to enforce them, and can also support unified policy framework to govern network behavior. The PCF 1012 can also implement a front end (FE) to access subscription information relevant for policy decisions in a Uniform Data Repository (UDR) or user datagram protocol of the UDM 1014. The PCF 1012 can communicate with the AMF 1022 via an N15 reference point between the PCF 1012 and the AMF 1022, which can include a PCF 1012 in a visited network and the AMF 1022 in case of roaming scenarios. The PCF 1012 can communicate with the application function AF 1016 via an N5 reference point between the PCF 1012 and the AF 1016: and with the SMF 1024 via an N7 reference point between the PCF 1012 and the SMF 1024. The network architecture 1000 and / or CN 1002 can also include an N24 reference point between the PCF 1012 (in the home network) and a PCF 1012 in a visited network. Additionally, the PCF 1012 can exhibit an Npcf service-based interface.

[0211] The UDM 1014 can handle subscription-related information to support the network entities' handling of communication sessions, and can store subscription data of UE 302. For example, subscription data can be communicated between the UDM 1014 and the AMF 1022 via an N8 reference point between the UDM 1014 and the AMF 1022. The UDM 1014 can include two parts, an application FE and a Uniform Data Repository (UDR) (the FE and UDR are not shown by FIG. 10). The UDR can store subscription data and policy data for the UDM 1014 and the PCF 1012, and / or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs UE 302) for the NEF 1008. The Nudr service-based interface can be exhibited by the UDR to allow the UDM 1014, PCF 1012, and NEF 1008 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 1014 can include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends can 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. The UDR can interact with the SMF 1024 via an N10 reference point between the UDM 1014 and the SMF 1024. UDM 1014 can also support SMS management, wherein an SMS-FE implements the similar application logic as discussed previously. Additionally, the UDM 1014 can exhibit the Nudm service-based interface.

[0212] The AF 1016 can provide application influence on traffic routing, provide access to the NCE, and interact with the policy framework for policy control. The NCE can be a mechanism that allows the 5GC CN 1002 and AF 1016 to provide information to each other via NEF 1008, which can be used for edge computing implementations. In such implementations, the network operator and third party services can be hosted close to the UE 302 access point of attachment to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network. For edge computing implementations, the 5GC can select a UPF 1032 close to the UE 302 and execute traffic steering from the UPF 1032 to DN 1034 via the N6 interface. This can be based on the UE subscription data, UE location, and information provided by the AF 1016. In this way, the AF 1016 can influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 1016 is considered to be a trusted entity, the network operator can permit AF 1016 to interact directly with relevant NFs. Additionally, the AF 1016 can exhibit a Naf servicebased interface.

[0213] The NSSF 1006 can select a set of network slice instances serving the UE 302. The NSSF 1006 can also determine allowed NSSAI and the mapping to the subscribed single Network Slice Selection Assistance Information (S-NSSAIs), if needed. The NSSF 1006 can also determine the AMF 1022 set to be used to serve the UE 302, or a list of candidate AMF 1022 based on a suitable configuration and possibly by querying the NRF 1010. The selection of a set of network slice instances for the UE 302 can be triggered by the AMF 1022 with which the UE 302 is registered by interacting with the NSSF 1006, which can lead to a change of AMF 1022. The NSSF 1006 can interact with the AMF 1022 via an N22 reference point between AMF 1022 and NSSF 1006; and can communicate with another NSSF 1006 in a visited network via an N31 reference point (not shown by FIG. 10). Additionally, the NSSF 1006 can exhibit an Nnssf service-based interface.

[0214] The CN 1002 can include an SMSF, which can be responsible for SMS subscription checking and verification, and relaying SM messages to / from the UE 302 to / from other entities, such as an SMS-GMSC / IWMSC / SMS-router. The SMS can also interact with AMF 1022 and UDM 1014 for a notification procedure that the UE 302 is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM 1014 when UE 302 is available for SMS).

[0215] The CN 1002 can also include other elements that are not shown by FIG. 10, such as a Data Storage system / architecture, a 5G-EIR, a SEPP, and the like. The Data Storage system can include a SDSF, an UDSF. and / or the like. Any NF can store and retrieve unstructured data into / from the UDSF (e.g., UE contexts), via N18 reference point between any NF and the UDSF (not shown by FIG. 10. Individual NFs can share a UDSF for storing their respective unstructured data or individual NFs can each have their own UDSF located at or near the individual NFs. Additionally, the UDSF can exhibit an Nudsf service-based interface (not shown by FIG. 10. The 5G-EIR can be an NF that checks the status of PEI for determining whether particular equipment / entities are blacklisted from the network; and the SEPP can be a non-transparent proxy that performs topology hiding, message filtering, and policing on inter-PLMN control plane interfaces.

[0216] Additionally, there can be many more reference points and / or service-based interfaces between the NF services in the NFs; however, these interfaces and reference points have been omitted from FIG. 10 for clarity. In one example, the CN 1002 can include an Nx interface, which is an inter-CN interface between the Mobility Management Entity (MME) and the AMF 1022 in order to enable interworking between CN 1002 and other CN. Other example interfaces / reference points can include an N5g-Equipment Identity Register (EIR) service-based interface exhibited by a 5G-EIR, an N27 reference point between the Network Repository Function (NRF) in the visited network and the NRF in the home network; and an N31 reference point between the NSSF in the visited network and the NSSF in the home network. Further, any of the above functions, entities, etc. can include or be comprised by a component as referred to herein.

[0217] The LMF 1026 (or individual instances of the LMF 1026) is a core network component responsible for determining and managing the geographical location of user equipment (UE). The LMF collects data from the radio network and various other sources to calculate the position of the UE using techniques like triangulation, time of arrival (TOA), and observed time difference of arrival (OTDOA). It supports both network-based and UE- based positioning methods, with the network or the UE itself calculating the location based on available signals. The LMF interacts with the 5G base stations (gNodeB) to gather necessary’ measurements, and it can also leverage Global Navigation Satellite Systems (GNSS) for more accurate positioning when necessary. In addition to its role in determining device location, the LMF is responsible for sharing this information with authorized entities, such as location-based services or emergency responders. The LMF is vital for enabling services like emergency calls, where precise location information is required, and for supporting Internet of Things (loT) applications where location tracking is necessary. It interfaces with other core network functions, like the Access and Mobility Management Function (AMF), and integrates seamlessly into the 5G service-based architecture to provide secure and reliable location services across various use cases. The LMF 1026 may be deployed in a distributed manner. More than one LMF 1026 can be present in the communication path between various NF Services. The LMF 1026, although not an NF instance, can also be deployed distributed, redundant, and scalable. The DN 1034 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 server 210. In some implementations, the DN 1034 may be, or include, one or more edge compute nodes. Additionally or alternatively, the DN 1034 may be an Edge DN 1034. which is a (local) Data Network that supports the architecture for enabling edge applications. In these embodiments, the application server 210 may represent the physical hardware systems / devices providing app server functionality and / or the application software resident in the cloud or at an edge compute node that performs server function(s). In some embodiments, the application server 210 provides an edge hosting environment that provides support required for Edge Application Server's execution.

[0218] The Access Stratum (AS) layer in a 3GPP system is responsible for the radio communication between the user equipment (UE) and the radio access network (RAN). It handles tasks related to the physical transmission of data over the air interface, including managing the establishment, maintenance, and release of radio connections. The AS layer oversees the radio resource control (RRC), which handles signaling between the UE and the base station (gNodeB in 5G or eNodeB in 4G), and it ensures that data is transmitted efficiently and reliably over the wireless link. This layer is involved in functions such as scheduling, handovers, and ensuring quality of service (QoS) for different types of data traffic.

[0219] In contrast, the Non-Access Stratum (NAS) layer operates between the UE and the core network, managing higher-level signaling that is not directly tied to the radio access network. The NAS layer is responsible for tasks such as mobility management, session management, and security between the UE and the core network (like AMF in 5G or MME in 4G). It handles authentication, network registration, location tracking, and the establishment of IP sessions, ensuring secure communication. While the AS layer manages the radio connection, the NAS layer oversees the broader network functions, allowing the device to communicate securely and move seamlessly across different network areas.

[0220] FIG. 11 is a block diagram illustrating an apparatus 1100 with various 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 cores) 1110, one or more memory 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.

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

[0222] The memory devices 1122 (or storage devices) may include main memory', disk storage, or any suitable combination thereof. The memory 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 memory7, solid-state storage, etc.

[0223] 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 2008. 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.

[0224] The instructions 1116, instructions 1118, instructions 1124, instructions 1128, and / or instructions 1132 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 2010 to perform any one or more of the methodologies discussed herein. The instructions 1116, instructions 1118, instructions 1124, instructions 1128. and / or instructions 1132 may reside, completely or partially, within at least one of the processors 1110 (e.g., within the processor’s cache memory7), the memory' devices 1122, or any suitable combination thereof. Furthermore, any portion of the instructions 1116, instructions 1118, instructions 1124, instructions 1128, and / or instructions 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 devices 1122, the peripheral devices 1104, and the databases 1106 are examples of computer-readable and machine-readable media. 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.

[0225] FIG. 13 illustrates computer readable storage medium 1300. Computer readable storage medium 1300 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 1300 may comprise an article of manufacture. In some embodiments, computer readable storage medium 1300 may store computer executable instructions 1302 with which circuitry' can execute. For example, computer executable instructions 1302 can include computer executable instructions 1302 to implement operations described with respect to logic flow 800 and / or logic flow 900. Examples of computer readable storage medium 1300 or machine-readable storage medium 1300 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 1302 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.

[0226] 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.”

[0227] It will be appreciated that the exemplary devices shown in the block diagrams described above may represent one functionally7descriptive example of many7potential implementations. Accordingly, division, omission or inclusion of block functions depicted in the accompanying figures does not infer that the hardware components, circuits, softw are and / or elements for implementing these functions would necessarily be divided, omitted, or included in embodiments.

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

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

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

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

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

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

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

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

[0236] The various elements of the devices as previously described with reference to FIGS. 1- > 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 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.

[0237] 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, encrypted code, and the like, implemented using any suitable high-level, low-level, object- oriented, visual, compiled and / or interpreted programming language.

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

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

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

[0241] The following examples pertain to further embodiments, from which numerous permutations and configurations will be apparent.

[0242] Example Set 1

[0243] Example 1 may include when a UE supports NeedForInlerruptionInfoNR-R18 measurements and indicates no-gap-with-interruption on intra-frequency S SB-based or inter-frequency SSB-based measurements without measurement gaps, the UE is allowed to cause interruptions while performing measurements on the frequency layers of the bands for which no-gap-with-interruption is indicated.

[0244] Example 2 may include Tcycie,i is the interruption cycle on a certain frequency layer i according to the network configuration, specified in Table 1 and 2. Interruption cycle means that the UE is allowed to cause interruption less or equal frequently than that of every cycle length time.

[0245] Table 1 : Tcycle,i length for intra-frequency measurement target carrier i

[0246] Table 2: Tcycle,i length for inter-frequency measurement target carrier i

[0247] Example 3 may include when UE is allowed to cause interruption with interruption ratio no more than the requirements specified in this document upon UE measurements on a specific frequency layer that corresponds to the configured measurement objects. Example 4 may include the total allowed maximum interruption ratio on each of the active serving cells due to UE measurements without gap applied in this sub-clause is specified as

[0248] EQUATION (1) Where, N is the total number of configured SSB based measurement target frequencylayers, including intra-frequency and inter-frequency target carriers, and L is the maximum interruption length for each interruption occasion specified in the Table 3 and 4.

[0249] Example 5 may include the interruptions are allowed for all the active 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.

[0250] Example 6 may include if the measurement gap is configured and the gap occasions are partially or fully overlapped with the SMTC occasions on a certain frequency layer that UE indicates no-gap-with-interruption, no interruption from measurements on such layer is allowed. This is because all the measurements with interruption are required to be carried out within the configured measurement gaps. Though the measurements do not require measurement gap but forcing them done within the gaps avoid interruptions.

[0251] Example 7 may include a method of a user equipment (UE), the method comprising: encoding, for transmission to a next generation Node B (gNB), capability information to indicate that the UE is capable of performing a measurement without a measurement gap and with an interruption; and performing the measurement on a reference signal with an interruption.

[0252] Example 8 may include the method of example 7 or some other example herein, wherein the UE does not receive a downlink data or control signal or transmit an uplink data or control signal during the interruption.

[0253] Example 9 may include the method of example 7-8 or some other example herein, wherein the UE is to configure the interruption to have an associated interruption ratio that is less than or equal to an interruption ratio requirement.

[0254] Example 10 may include the method of example 7-9 or some other example herein, further comprising determining a cycle time, Tcycle, associated with the interruption, wherein the UE is allowed to cause interruptions with a period between interruptions that is equal to or greater than the cycle time.

[0255] Example 11 may include the method of example 10 or some other example herein, wherein the cycle time is based on a DRX cycle of the UE.

[0256] Example 12 may include the method of example 10-11 or some other example herein, wherein the cycle time is based on whether the measurement is an intra-frequency measurement or an inter-frequency measurement.

[0257] Example 13 may include the method of example 10-12 or some other example herein, wherein the cycle time is determined based on a carrier specific scaling factor (CSSF).

[0258] Example 14 may include the method of example 13 or some other example herein, wherein the CSSF is different for intra-frequency measurements than for inter-frequency measurements.

[0259] Example 15 may include the method of example 10-14 or some other example herein, wherein the cycle time is determined in accordance with Table 1 and / or Table 2 herein.

[0260] Example 16 may include the method of example 7-15, further comprising determining a total allowed maximum interruption ratio on an active serving cell; and performing the measurement with the interruption in accordance with the total allowed maximum interruption ratio.

[0261] Example 17 may include the method of example 16 or some other example herein, wherein the total allowed maximum interruption ratio is determined according to:

[0262] EQUATION (1)

[0263] Where. N is the total number of configured target frequency layers, including intrafrequency and inter-frequency target carriers, and L is the maximum interruption length for each interruption occasion.

[0264] Example 18 may include the method of example 17 or some other example herein, wherein L is in accordance with Table 3 and / or Table 4.

[0265] Example 19 may include the method of example 7-18 or some other example herein, wherein the reference signal corresponds to a synchronization signal block (SSB).

[0266] Example Set 2

[0267] Example 1. An apparatus for an access node, comprising: a memory interface to communicate information for a wireless communications system; and processor circuitry operably coupled to the memory7interface to: decode an encoded message from user equipment (UE) with UE capability7information, the message comprising an information element carrying interruption information that indicates the UE supports measurements without a measurement gap but with interruptions; determine whether to allow the UE to cause interruptions while performing measurements based on the interruption information from the UE and an interruption ratio or an interruption length for the interruptions caused by the UE; and encode a message for the UE to allow the UE to perform measurements without the measurement gap but with the interruptions.

[0268] Example 2. The apparatus of example 1, comprising: determine whether the UE is in a standalone (SA) operation mode where the UE is configured with at least a primary7cell (PC ell) and not any multi-radio dual connectivity (MR-DC); and determine to allow the UE to cause interruptions while performing measurements when the UE is in the SA operation mode.

[0269] Example 3. The apparatus of example 1, wherein the information element is a NeedForInterruptionInfoNR-rl8 information element. Example 4. The apparatus of example 1, wherein the interruption information is a no- gap-with-interruption value.

[0270] Example 5. The apparatus of example 1, wherein the interruption information is a no- gap-with-interruption value on intra-frequency synchronization signal block (SSB)-based or inter-frequency SSB-based measurements.

[0271] Example 6. The apparatus of example 1, wherein the information element is a NeedForInterruptionlnfoNR-rl8 information element comprising a NeedForlnterruptionNR- rl8 field to indicate whether interruption is needed for the UE to perform synchronization signal block (SSB) based measurements without measurement gap, the NeedForInterruptionNR-rl8 field to carry an interruptionindication set to a no-gap-with- interruption value that indicates interruption is needed or a no-gap-no-interruption value that indicates interruption is not needed.

[0272] Example 7. The apparatus of example 1, wherein the interruption configuration information indicates the UE is allowed to cause interruptions while performing measurements on frequency layers of frequency bands for which the interruption information is indicated.

[0273] Example 8. The apparatus of example 1, wherein the interruption configuration information indicates that the UE is allowed to cause interruptions on a certain frequency layer i with a maximum interruption ratio that equals , where L is a maximum

[0274] Tcycl .i interruption length for each interruption occasion and is an interruption cycle on the certain frequency layer i.

[0275] Example 9. The apparatus of example 1, wherein a total allowed maximum interruption ratio (D) on an active serving cell due to UE measurements without gap is specified as D - , where Vis a total number of configured synchronization signal block (SSB) based frequency layers to be measured outside gap including intra- frequency and inter-frequency target carriers where the UE indicates that interruption is needed through the interruption parameter, and L is a maximum interruption length for each interruption occasion.

[0276] Example 10. The apparatus of example 1, comprising: generate interruption configuration information defining the interruption ratio or the interruption length for the interruptions caused by the UE when the UE is allowed to cause interruptions; and encode the message for the UE with the interruption configuration information. Example 11. An apparatus for a user equipment (UE), comprising: a memory interface to communicate information for a wireless communications system; and processor circuitry operably coupled to the memory interface to: encode a message with UE capability information for an access node, the encoded message comprising an information element carrying interruption information that indicates the UE supports measurements without a measurement gap but with interruptions; decode an encoded message from the access node that indicates the UE is allowed to perform measurements without the measurement gap but with the interruptions; and perform measurements based on an interruption ratio or an interruption length defined by the access node. The apparatus of example 11 may encode a message with a measurement report comprising the measurements for the access node.

[0277] Example 12. The apparatus of example 11. comprising encode a message for the access node indicating the UE is in a standalone (SA) operation mode where the UE is configured with at least a primary cell (PCell) and not any multi-radio dual connectivity (MR-DC).

[0278] Example 13. The apparatus of example 11, wherein the information element is a NeedForInterruptionInfoNR-rl8 information element.

[0279] Example 14. The apparatus of example 11. wherein the interruption information is a no-gap-with-interruption value.

[0280] Example 15. The apparatus of example 11, wherein the interruption information is a no-gap-with-interruption value on intra-frequency synchronization signal block (SSB)-based or inter-frequency SSB-based measurements.

[0281] Example 16. The apparatus of example 11, wherein the information element is a NeedForInterruptionInfoNR-rl8 information element comprising a NeedForlnterruptionNR- r 18 field to indicate whether interruption is needed for the UE to perform synchronization signal block (SSB) based measurements without measurement gap, the NeedForInterruptionNR-rl8 field to carry an interruptionindication set to a no-gap-with- interruption value that indicates interruption is needed or a no-gap-no-interruption value that indicates interruption is not needed.

[0282] Example 17. The apparatus of example 11, wherein the interruption configuration information indicates the UE is allowed to cause interruptions while performing measurements on frequency layers of frequency bands for which the interruption information is indicated.

[0283] Example 18. The apparatus of example 11, wherein the interruption configuration information indicates that the UE is allowed to cause interruptions on a certain frequency layer i with a maximum interruption ratio that equals - , where L is a maximum interruption length for each interruption occasion and is an interruption cycle on the certain frequency layer i.

[0284] Example 19. The apparatus of example 11, wherein a total allowed maximum interruption ratio (£>) on an active serving cell due to UE measurements without gap is

[0285] 2L specified as D — , where A is a total number of configured synchronization signal block (SSB) based frequency layers to be measured outside gap including intrafrequency and inter-frequency target carriers where the UE indicates that interruption is needed through the interruption information, and £ is a maximum interruption length for each interruption occasion.

[0286] Example 20. The apparatus of example 11, wherein the encoded message comprises interruption configuration information defining the interruption ratio or the interruption length for the interruptions caused by the UE when the UE is allowed to cause interruptions.

[0287] Example 21. The apparatus of example 1, wherein the interruption configuration information is carried by the encoded message from the access node or stored in a memory unit of the UE.

[0288] Example 22. The apparatus of example 11, wherein the interruption configuration information is carried by the encoded message from the access node or stored in a memory unit of the UE.

[0289] Example 23. A method for an access node, comprising: decoding an encoded message from user equipment (UE) with UE capability information, the message comprising an information element carrying interruption information that indicates the UE supports measurements without a measurement gap but with interruptions; determining whether to allow the UE to cause interruptions while performing measurements based on the interruption information from the UE and an interruption ratio or an interruption length for the interruptions caused by the UE; and encoding a message for the UE to allow the UE to perform measurements without the measurement gap but with the interruptions.

[0290] Example 24. The method of example 23, comprising: determining whether the UE is in a standalone (SA) operation mode where the UE is configured with at least a primary cell (PCell) and not any multi-radio dual connectivity (MR-DC); and determining to allow the UE to cause interruptions while performing measurements when the UE is in the SA operation mode. Example 25. The method of example 23, wherein the information element is a NeedForInterruptionInfoNR-rl8 information element.

[0291] Example 26. The method of example 23, wherein the interruption information is a no-gap-with-interruption value.

[0292] Example 27. The method of example 23, wherein the interruption information is a no-gap-with-interruption value on intra-frequency synchronization signal block (SSB)-based or inter-frequency SSB-based measurements.

[0293] Example 28. The method of example 23, wherein the information element is a NeedForInterruptionInfoNR-rl8 information element comprising a NeedForlnterruptionNR- rl 8 field to indicate whether interruption is needed for the UE to perform synchronization signal block (SSB) based measurements without measurement gap, the NeedForInterruptionNR-rl8 field to carry an interruptionindication set to a no-gap-with- interruption value that indicates interruption is needed or a no-gap-no-interruption value that indicates interruption is not needed.

[0294] Example 29. The method of example 23, wherein the interruption configuration information indicates the UE is allowed to cause interruptions while performing measurements on frequency layers of frequency bands for which the interruption information is indicated.

[0295] Example 30. The method of example 23, wherein the interruption configuration information indicates that the UE is allowed to cause interruptions on a certain frequency 2L layer i with a maximum interruption ratio that equals - , where L is a maximum

[0296] Tcycle.i interruption length for each interruption occasion and '^cyde,i is an interruption cycle on the certain frequency layer i.

[0297] Example 31. The method of example 23. wherein a total allowed maximum interruption ratio (D) on an active serving cell due to UE measurements without gap is specified as D — , where jVis a total number of configured synchronization signal block (SSB) based frequency layers to be measured outside gap including intra- frequency and inter-frequency target carriers where the UE indicates that interruption is needed through the interruption parameter, and £ is a maximum interruption length for each interruption occasion.

[0298] Example 32. The method of example 23, comprising: generating interruption configuration information defining the interruption ratio or the interruption length for the interruptions caused by the UE when the UE is allowed to cause interruptions; and encoding the message for the UE with the interruption configuration information.

[0299] Example 33. A method for a user equipment (UE), comprising: encoding a message with UE capability information for an access node, the encoded message comprising an information element carrying interruption information that indicates the UE supports measurements without a measurement gap but with interruptions; decoding an encoded message from the access node that indicates the UE is allowed to perform measurements without the measurement gap but with the interruptions; performing measurements based on an interruption ratio or an interruption length defined by the access node. The method of example 33 may further comprise encoding a message with a measurement report comprising the measurements for the access node.

[0300] Example 34. The method of example 33, comprising encoding a message for the access node indicating the UE is in a standalone (SA) operation mode where the UE is configured w ith at least a primary cell (PCell) and not any multi-radio dual connectivity (MR-DC).

[0301] Example 35. The method of example 33, wherein the information element is a NeedForInterruptionInfoNR-rl8 information element.

[0302] Example 36. The method of example 33, wherein the interruption information is a no-gap-wdth-interruption value.

[0303] Example 37. The method of example 33. wherein the interruption information is a no-gap-wath-interruption value on intra-frequency synchronization signal block (SSB)-based or inter-frequency SSB-based measurements.

[0304] Example 38. The method of example 33. wherein the information element is a NeedForlnterruptionTnfoNR-rl 8 information element comprising a NeedForlnterruptionNR- rl8 field to indicate whether interruption is needed for the UE to perform synchronization signal block (SSB) based measurements without measurement gap, the NeedForInterruptionNR-rl8 field to carry an interruptionindication set to a no-gap-with- interruption value that indicates interruption is needed or a no-gap-no-interruption value that indicates interruption is not needed.

[0305] Example 39. The method of example 33. wherein the interruption configuration information indicates the UE is allowed to cause interruptions while performing measurements on frequency layers of frequency bands for which the interruption information is indicated. Example 40. The method of example 33, wherein the interruption configuration information indicates that the UE is allowed to cause interruptions on a certain frequency 2L layer / with a maximum interruption ratio that equals 7, - , where L is a maximum cycle >i interruption length for each interruption occasion andcyde’lis an interruption cycle on the certain frequency layer i.

[0306] Example 41. The method of example 33, wherein a total allowed maximum interruption ratio (D) on an active serving cell due to UE measurements without gap is 2L specified as D ■ - - , where N is a total number of configured synchronization i=l ' 'cycle.i signal block (SSB) based frequency layers to be measured outside gap including intrafrequency and inter-frequency target carriers where the UE indicates that interruption is needed through the interruption information, and L is a maximum interruption length for each interruption occasion.

[0307] Example 42. The method of example 33, wherein the encoded message comprises interruption configuration information defining the interruption ratio or the interruption length for the interruptions caused by the UE when the UE is allowed to cause interruptions.

[0308] Example 43. The method of example 33, wherein the interruption configuration information is carried by the encoded message from the access node or stored in a memory' unit of the UE.

[0309] Example 44. The method of example 23, wherein the interruption configuration information is carried by the encoded message from the access node or stored in a memory' unit of the UE.

[0310] Example 45. Machine-readable storage including machine-readable instructions, when executed by circuitry, causes the circuitry to perform operations for an access node, comprising: decode an encoded message from user equipment (UE) with UE capability’ information, the message comprising an information element carry ing interruption information that indicates the UE supports measurements without a measurement gap but with interruptions; determine whether to allow the UE to cause interruptions while performing measurements based on the interruption information from the UE and an interruption ratio or an interruption length for the interruptions caused by the UE; and encode a message for the UE to allow the UE to perform measurements without the measurement gap but with the interruptions. Example 46. The machine-readable storage of example 45, comprising: determine whether the UE is in a standalone (SA) operation mode where the UE is configured with at least a primary cell (PCell) and not any multi-radio dual connectivity (MR-DC); and determine to allow the UE to cause interruptions while performing measurements when the UE is in the SA operation mode.

[0311] Example 47. The machine-readable storage of example 45, wherein the information element is a NeedForInterruptionInfoNR-rl8 information element.

[0312] Example 48. The machine-readable storage of example 45, wherein the interruption information is a no-gap-with-interruption value.

[0313] Example 49. The machine-readable storage of example 45, wherein the interruption information is a no-gap-with-interruption value on intra-frequency synchronization signal block (SSB)-based or inter-frequency SSB-based measurements.

[0314] Example 50. The machine-readable storage of example 45, wherein the information element is a NeedForInterruptionInfoNR-rl8 information element comprising a NeedForInterruptionNR-rl8 field to indicate whether interruption is needed for the UE to perform synchronization signal block (SSB) based measurements without measurement gap. the NeedForInterruptionNR-rl8 field to carry an interruptionindication set to a no-gap-with- interruption value that indicates interruption is needed or a no-gap-no-interruption value that indicates interruption is not needed.

[0315] Example 51. The machine-readable storage of example 45, wherein the interruption configuration information indicates the UE is allowed to cause interruptions while performing measurements on frequency layers of frequency bands for which the interruption information is indicated.

[0316] Example 52. The machine-readable storage of example 45, wherein the interruption configuration information indicates that the UE is allowed to cause interruptions on a 2L certain frequency layer i with a maximum interruption ratio that equals - , where L is a

[0317] Tcyde,i maximum interruption length for each interruption occasion and is an interruption cycle on the certain frequency layer i.

[0318] Example 53. The machine-readable storage of example 45, wherein a total allowed maximum interruption ratio (D) on an active serving cell due to UE measurements without gap is specified as D — where A is a total number of configured synchronization signal block (SSB) based frequency layers to be measured outside gap including intra-frequency and inter-frequency target carriers where the UE indicates that interruption is needed through the interruption parameter, and £ is a maximum interruption length for each interruption occasion.

[0319] Example 54. The machine-readable storage of example 45. comprising instructions to: generate interruption configuration information defining the interruption ratio or the interruption length for the interruptions caused by the UE when the UE is allowed to cause interruptions; and encode the message for the UE with the interruption configuration information.

[0320] Example 55. Machine-readable storage including machine-readable instructions, when executed by circuitry, causes the circuitry to perform operations for a user equipment (UE). comprising: encoding a message with UE capability information for an access node, the encoded message comprising an information element carrying interruption information that indicates the UE supports measurements without a measurement gap but with interruptions; decoding an encoded message from the access node that indicates the UE is allowed to perform measurements without the measurement gap but with the interruptions; performing measurements based on an interruption ratio or an interruption length defined by the access node. The method of example 33 may further comprise encoding a message with a measurement report comprising the measurements for the access node.

[0321] Example 56. The machine-readable storage of example 55, comprising instructions to encode a message for the access node indicating the UE is in a standalone (SA) operation mode where the UE is configured with at least a primary' cell (PCell) and not any multiradio dual connectivity (MR-DC).

[0322] Example 57. The machine-readable storage of example 55, wherein the information element is a NeedFor!nterruptionInfoNR-rl8 information element.

[0323] Example 58. The machine-readable storage of example 55, wherein the interruption information is a no-gap-with-interruption value.

[0324] Example 59. The machine-readable storage of example 55, wherein the interruption information is a no-gap-with-interruption value on intra-frequency synchronization signal block (SSB)-based or inter-frequency SSB-based measurements.

[0325] Example 60. The machine-readable storage of example 55, wherein the information element is a NeedFor!nterruptionInfoNR-rl8 information element comprising a NeedForInterruptionNR-rl8 field to indicate whether interruption is needed for the UE to perform synchronization signal block (SSB) based measurements without measurement gap, the NeedForInterruptionNR-rl8 field to carry an interruptionindication set to a no-gap-with- interruption value that indicates interruption is needed or a no-gap-no-interruption value that indicates interruption is not needed.

[0326] Example 61. The machine-readable storage of example 55, wherein the interruption configuration information indicates the UE is allowed to cause interruptions while performing measurements on frequency layers of frequency bands for which the interruption information is indicated.

[0327] Example 62. The machine-readable storage of example 55, wherein the interruption configuration information indicates that the UE is allowed to cause interruptions on a

[0328] 2L certain frequency layer i with a maximum interruption ratio that equals where L is a maximum interruption length for each interruption occasion and Tvde,i is an interruption cycle on the certain frequency layer i.

[0329] Example 63. The machine-readable storage of example 55, wherein a total allowed maximum interruption ratio (D) on an active serving cell due to UE measurements without gap is specified as D ~ , where N is a total number of configured synchronization signal block (SSB) based frequency layers to be measured outside gap including intra-frequency and inter-frequency target carriers where the UE indicates that interruption is needed through the interruption information, and L is a maximum interruption length for each interruption occasion.

[0330] Example 64. The machine-readable storage of example 55, wherein the encoded message comprises interruption configuration information defining the interruption ratio or the interruption length for the interruptions caused by the UE when the UE is allowed to cause interruptions.

[0331] Example 65. The machine-readable storage of example 55, wherein the interruption configuration information is carried by the encoded message from the access node or stored in a memory unit of the UE.

[0332] Example 66. The machine-readable storage of example 45, wherein the interruption configuration information is carried by the encoded message from the access node or stored in a memory unit of the UE.

[0333] Example 67. An apparatus for an access node, comprising: means for decoding an encoded message from user equipment (UE) with UE capability information, the message comprising an information element carry ing interruption information that indicates the UE supports measurements without a measurement gap but with interruptions; means for determining whether to allow the HE to cause interruptions while performing measurements based on the interruption information from the UE and an interruption ratio or an interruption length for the interruptions caused by the UE; and means for encoding a message for the UE to allow the UE to perform measurements without the measurement gap but with the interruptions.

[0334] Example 68. The apparatus of example 67, comprising: means for determining whether the UE is in a standalone (SA) operation mode where the UE is configured with at least a primary cell (PCell) and not any multi-radio dual connectivity (MR-DC); and means for determining to allow the UE to cause interruptions while performing measurements when the UE is in the SA operation mode.

[0335] Example 69. The apparatus of example 67, wherein the information element is a NeedForInterruptionInfoNR-rl8 information element.

[0336] Example 70. The apparatus of example 67, wherein the interruption information is a no-gap-with-interruption value.

[0337] Example 71. The apparatus of example 67, wherein the interruption information is a no-gap-with-interruption value on intra-frequency synchronization signal block (SSB)-based or inter-frequency SSB-based measurements.

[0338] Example 72. The apparatus of example 67, wherein the information element is a NeedForInterruptionInfoNR-rl8 information element comprising a NeedForlnterruptionNR- rl 8 field to indicate whether interruption is needed for the UE to perform synchronization signal block (SSB) based measurements without measurement gap, the NeedForInterruptionNR-rl8 field to carry an interruptionindication set to a no-gap-with- interruption value that indicates interruption is needed or a no-gap-no-interruption value that indicates interruption is not needed.

[0339] Example 73. The apparatus of example 67, wherein the interruption configuration information indicates the UE is allowed to cause interruptions while performing measurements on frequency layers of frequency bands for which the interruption information is indicated.

[0340] Example 74. The apparatus of example 67, wherein the interruption configuration information indicates that the UE is allowed to cause interruptions on a certain frequency layer i with a maximum interruption ratio that equals ■ — — , where L is a maximum T yde,i interruption length for each interruption occasion and «s aninterruption cycle on the certain frequency layer i. Example 75. The apparatus of example 67, wherein a total allowed maximum interruption ratio (D) on an active serving cell due to UE measurements without gap is specified , where A is a total number of configured synchronization signal block (SSB) based frequency layers to be measured outside gap including intrafrequency and inter-frequency target carriers where the UE indicates that interruption is needed through the interruption parameter, and L is a maximum interruption length for each interruption occasion.

[0341] Example 76. The apparatus of example 67, comprising: means for generating interruption configuration information defining the interruption ratio or the interruption length for the interruptions caused by the UE when the UE is allowed to cause interruptions; and means for encoding the message for the UE with the interruption configuration information.

[0342] Example 77. An apparatus for a user equipment (UE), comprising: means for encoding a message with UE capability information for an access node, the encoded message comprising an information element carry ing interruption information that indicates the UE supports measurements without a measurement gap but with interruptions; means for decoding an encoded message from the access node that indicates the UE is allowed to perform measurements without the measurement gap but with the interruptions; and means for performing measurements based on an interruption ratio or an interruption length defined by the access node. The method of example 33 may further comprise means for encoding a message with a measurement report comprising the measurements for the access node.

[0343] Example 78. The apparatus of example 77, comprising means for encoding a message for the access node indicating the UE is in a standalone (SA) operation mode where the UE is configured with at least a primary cell (PCell) and not any multi-radio dual connectivity (MR-DC).

[0344] Example 79. The apparatus of example 77, wherein the information element is a NeedForInterruptionInfoNR-rl8 information element.

[0345] Example 80. The apparatus of example 77, wherein the interruption information is a no-gap-with-interruption value.

[0346] Example 81. The apparatus of example 77, wherein the interruption information is a no-gap-with-interruption value on intra-frequency synchronization signal block (SSB)-based or inter-frequency SSB-based measurements. Example 82. The apparatus of example 77, wherein the information element is a NeedForInterruptionInfoNR-rl8 information element comprising a NeedForlnterruptionNR- rl 8 field to indicate whether interruption is needed for the UE to perform synchronization signal block (SSB) based measurements without measurement gap, the NeedForInterruptionNR-rl8 field to carry an interruptionindication set to a no-gap-with- interruption value that indicates interruption is needed or a no-gap-no-interruption value that indicates interruption is not needed.

[0347] Example 83. The apparatus of example 77, wherein the interruption configuration information indicates the UE is allowed to cause interruptions while performing measurements on frequency layers of frequency bands for which the interruption information is indicated.

[0348] Example 84. The apparatus of example 77, wherein the interruption configuration information indicates that the UE is allowed to cause interruptions on a certain frequency

[0349] 2L layer i with a maximum interruption ratio that equals - , where L is a maximum

[0350] - 'cycle, i interruption length for each interruption occasion and ^cycle-i is an interruption cycle on the certain frequency layer i.

[0351] Example 85. The apparatus of example 77, wherein a total allowed maximum interruption ratio (D) on an active serving cell due to UE measurements without gap is 2L specified as D — , where TV is a total number of configured synchronization Tcyele.i signal block (SSB) based frequency layers to be measured outside gap including intrafrequency and inter-frequency target carriers where the UE indicates that interruption is needed through the interruption information, and L is a maximum interruption length for each interruption occasion.

[0352] Example 86. The apparatus of example 77, wherein the encoded message comprises interruption configuration information defining the interruption ratio or the interruption length for the interruptions caused by the UE when the UE is allowed to cause interruptions.

[0353] Example 87. The apparatus of example 77, wherein the interruption configuration information is carried by the encoded message from the access node or stored in a memory' unit of the UE.

[0354] Example 88. The apparatus of example 67, wherein the interruption configuration information is carried by the encoded message from the access node or stored in a memory’ unit of the UE. Terminology

[0355] For the purposes of the present document, the following terms and definitions are applicable to the examples and embodiments discussed herein.

[0356] 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 functionality7of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

[0357] 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 memory7structures 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.”

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

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

[0360] 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, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and / or the like.

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

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

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

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

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

[0366] 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 w ith 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 w ith 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. The term “information element7’ 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.

[0367] The term “SMTC” refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

[0368] The term “SSB” refers to an SS / PBCH block.

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

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

[0371] The term “Secondary Cell” refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA.

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

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

[0374] 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 / .

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

Claims

CLAIMSWhat is claimed is:

1. A method for a user equipment (UE), comprising: encoding a message with UE capability information for an access node, the encoded message comprising an information element carry ing interruption information that indicates the UE supports measurements without a measurement gap but with interruptions; decoding an encoded message from the access node that indicates the UE is allowed to perform measurements without the measurement gap but with the interruptions; and performing measurements based on an interruption ratio or an interruption length defined by the access node.

2. The method of claim 1, comprising encoding a message for the access node indicating the UE is in a standalone (SA) operation mode where the UE is configured with at least a primary' cell (PCell) and not any multi-radio dual connectivity (MR-DC).

3. The method of claim 1, wherein the information element is a NeedForInterruptionInfoNR-rl8 information element.

4. The method of claim 1. wherein the interruption information is a no-gap-with-interruption value.

5. The method of claim 1, wherein the interruption information is a no-gap-with-interruption value on intra-frequency synchronization signal block (SSB)-based or inter-frequency SSB- based measurements.

6. The method of claim 1, wherein the information element is a NeedForInterruptionInfoNR-rl8 information element comprising a NeedForlnterruptionNR- rl 8 field to indicate whether interruption is needed for the UE to perform synchronization signal block (SSB) based measurements without measurement gap, the NeedForInterruptionNR-rl8 field to carry an interruptionindication set to a no-gap-with- interruption value that indicates interruption is needed or a no-gap-no-interruption value that indicates interruption is not needed.

7. The method of any of claims 1 to 6, wherein the interruption configuration information indicates the UE is allowed to cause interruptions while performing measurements on frequency layers of frequency bands for which the interruption information is indicated.

8. The method of any of claims 1 to 6, wherein the interruption configuration information indicates that the UE is allowed to cause interruptions on a certain frequency layer i with a maximum interruption ratio that equals Tcycle.i . where L is a maximum interruption lengthfor each interruption occasion and is an interruption cycle on the certain frequency layer i.

9. The method of any of claims 1 to 6, wherein the interruption configuration information is carried by the encoded message from the access node or stored in a memory unit of the UE.

10. The method of any of claims 1 to 6, wherein the encoded message comprises interruption configuration information defining the interruption ratio or the interruption length for the interruptions caused by the UE when the UE is allowed to cause interruptions.

11. An apparatus for a user equipment (UE), comprising: a memory interface to communicate information for a wireless communications system; and processor circuitry operably coupled to the memory' interface to: encode a message with UE capability information for an access node, the encoded message comprising an information element carrying interruption information that indicates the UE supports measurements without a measurement gap but with interruptions; decode an encoded message from the access node that indicates the UE is allowed to perform measurements without the measurement gap but with the interruptions; and perform measurements based on an interruption ratio or an interruption length defined by the access node.

12. The apparatus of claim 11, comprising encode a message for the access node indicating the UE is in a standalone (SA) operation mode where the UE is configured with at least a primary cell (PCell) and not any multi-radio dual connectivity (MR-DC).

13. The apparatus of claim 11, wherein the information element is a NeedForInterruptionInfoNR-rl8 information element.

14. The apparatus of claim 11, wherein the interruption information is a no-gap-with- interruption value.

15. The apparatus of claim 11, wherein the interruption information is a no-gap-with- interruption value on intra-frequency synchronization signal block (SSB)-based or interfrequency SSB-based measurements.

16. The apparatus of claim 11, wherein the information element is a NeedForInterruptionInfoNR-rl8 information element comprising a NeedForlnterruptionNR- rl 8 field to indicate whether interruption is needed for the UE to perform synchronization signal block (SSB) based measurements without measurement gap, the NeedForInterruptionNR-rl8 field to carry an interruptionindication set to a no-gap-with- interruption value that indicates interruption is needed or a no-gap-no-interruption value that indicates interruption is not needed.

17. The apparatus of any of claims 11 to 16. wherein the interruption configuration information indicates the UE is allowed to cause interruptions while performing measurements on frequency layers of frequency bands for which the interruption information is indicated.

18. The apparatus of any of claims 11 to 16, wherein the interruption configuration information indicates that the UE is allowed to cause interruptions on a certain frequency2E layer i with a maximum interruption ratio that equals — - — , where L is a maximum Tcyclt i interruption length for each interruption occasion and cyd.e,i is an interruption cycle on the certain frequency layer i.

19. The apparatus of any of claims 11 to 16, wherein the interruption configuration information is carried by the encoded message from the access node or stored in a memory unit of the UE.

20. The apparatus of any of claims 11 to 16, wherein the encoded message comprises interruption configuration information defining the interruption ratio or the interruption length for the interruptions caused by the UE when the UE is allowed to cause interruptions.

21. An apparatus for a user equipment (UE), comprising: means for encoding a message with UE capability information for an access node, the encoded message comprising an information element carrying interruption information that indicates the UE supports measurements without a measurement gap but with interruptions;means for decoding an encoded message from the access node that indicates the UE is allowed to perform measurements without the measurement gap but with the interruptions; and means for performing measurements based on an interruption ratio or an interruption length defined by the access node.

22. The apparatus of claim 21, comprising means for encoding a message for the access node indicating the UE is in a standalone (SA) operation mode where the UE is configured with at least a primary cell (PCell) and not any multi-radio dual connectivity (MR-DC).

23. The apparatus of claim 21, wherein the information element is a NeedForInterruptionInfoNR-rl8 information element.

24. The apparatus of claim 21, wherein the interruption information is a no-gap-with- interruption value.

25. The apparatus of claim 21, wherein the interruption information is a no-gap-with- interruption value on intra-frequency synchronization signal block (SSB)-based or inter- frequency SSB-based measurements.

Images