Method for indicating measurement gaps

Abstract

A method performed by a network node for enabling measurement gaps is disclosed. For example, the method includes receiving capability data from a user equipment (UE); utilizing the capability data to configure measurement configuration data that includes measurement occasions (MOs) for the UE to be able to conduct measurements; designating one or more of the MOs to be assigned as one or more measurement gap occasions (MGOs); and sending a MGO indicator that identifies the one or more assigned MGOs to the UE.

Description

METHOD FOR INDICATING MEASUREMENT GAPSTECHNICAL FIELD

[0001] The present disclosure relates generally to communications, and more particularly to methods and related mobile devices and mobile network nodes performing wireless and / or cellular based communications and signaling.BACKGROUND

[0002] In the ongoing Release- 18 study item on extended Reality (XR), several enhancements are being proposed to increase XR capacity of 5G-Advanced systems. At present, extended Reality (XR) includes services provided by computer technologies and wearables that allow for human-machine interaction in real / virtual mixed environments. Notably, XR includes Virtual Reality (VR), Augmented Reality (AR), Mixed Reality (MR), Cloud Gaming, and the areas interpolated among them. As such, XR is usually considered a mixed eMBB / URLLC service. As indicated in Table 1 below, XR traffic is a mixture of heterogeneous uplink / downlink (UL / DL) data flows, including video, audio, and control traffic.

[0003] More specifically, Table 1 as shown below highlights that XR traffic flows have different characteristics (e.g., packet rate in frames per second (fps) and bit rate in bits per second (bps)) and requirements in terms of (application) packet delay budget (PDB), e.g., in milliseconds (ms). Among XR flows, DL video and UL scene traffic are periodic (with possible jitter, particularly in the DL) and have variable large-sized application packets.TABLE 1

[0004] Mobility and measurement gap

[0005] Handover is a key functionality in a radio network which enables the user equipment (UE) to move from being served by one source cell to be served by another target cell. The handover can be of different degrees of complexity depending on: i) if the network nodes that serve the two cells are the same or different network node, e.g., a gNB that hasmultiple TRPs (Transmission / Reception Points) each serving a cell, ii) if the cells operate on same or different carrier frequency, iii) if the cells operate of different carrier frequencies, but if the carrier frequencies are on same or different frequency band, e.g., source cell is operating on FR1 while the target cell is operating on FR2, and / or iv) if the cells have same or different RAT (Radio Access Technology).

[0006] Generally, it can be said that handover is performed when a target cell becomes stronger than the source cell. To determine the strength of a cell, the UE performs measurements on reference signals transmitted by the gNBs serving the cells and the UE transmits a measurement report to its serving gNB. One type of reference signal related to mobility on which UE performs measurements in New Radio (NR) are synchronization signal blocks (SSBs), which include PSS (Primary Synchronization Signal), SSS (Secondary Synchronization Signal) and PBCH (Physical Broadcast Channel). In NR, the SSB can be configured with periodicities 5 ms, 10 ms, 20 ms, 40 ms, 80 ms and 160 ms. Another type of reference signal is the CSI-RS (Channel State Information Reference Signal) which in NR replaces the CRS (Common Reference Signal) in Long Term Evolution (LTE) systems. The CSI-RS can be used for link adaptation purposes, i.e., UE reports the suggested number of layers, pre-coder, and MCS (Modulation and Coding Scheme), and for mobility purposes wherein the UE reports the signal strength of the CSI-RS.

[0007] When the UE needs to perform an inter-frequency measurement, i.e., perform measurement on SSB / CSLRS on a carrier frequency that is different than the frequency the UE is currently operating on, the UE may not be capable of simultaneously receiving or transmitting on its serving cell. Measurement gaps are defined (configured) time locations where the UE can perform measurements without being required to receive or transmit. The UE may need measurement gaps to perform inter-frequency measurements as well as intrafrequency measurements. Besides needing a measurement gap for SSB / CSLRS measurements, the UE may also need measurement gaps for other purposes including: i) a positioning measurement gap, which is a measurement gap to perform measurements on positioning reference signals; ii) a MUSIM measurement gap, which is measurement gap for MUSIM (Multi -Universal Subscriber Identity Module) purposes such as cell identification and measurement, paging monitoring, SIB acquisition, and / or on-demand SI request of the target cell in the target network; and iii) UL gap for Tx power management.

[0008] All measurement gaps are similar in the sense that each has a gap length. The gap length is a time duration where the UE conducts preparations and measurements. A MUSIM measurement gap can be aperiodic in the sense that the measurement gap occurs at a specificRadio Resource Control (RRC) configured starting SFN (System Frame Number) and starting subframe. The MUSIM measurement gap can also be configured as periodic with a gap repetition period. All other measurement gaps are periodic. All measurement gaps except positioning measurement gaps are configured via RRC. Positioning measurement gaps can be pre-configured via RRC and then activated and de-activated by media access control (MAC) control element (CE) signaling.

[0009] Section 9.1.2 of the 3GPP Technical Specification (TS) 38.133 indicates that if theUE requires measurement gaps to identify and measure intra-frequency cells and / or interfrequency cells and / or inter-RAT E-UTRAN cells, and the UE does not support independent measurement gap patterns for different frequency ranges in order for the requirements in the following clauses to apply the network must provide a single per-UE measurement gap pattern for concurrent monitoring of all frequency layers.

[0010] If the UE requires measurement gaps to identify and measure intra-frequency cells and / or inter-frequency cells and / or inter-RAT E-UTRAN cells, and the UE supports independent measurement gap patterns for different frequency ranges, in order for the requirements in the following clauses to apply the network must provide either per-FR measurement gap patterns for frequency range where UE requires per-FR measurement gap for concurrent monitoring of all frequency layers of each frequency range independently, or a single per-UE measurement gap pattern for concurrent monitoring of all frequency layers of all frequency ranges.

[0011] If the UE is configured via LPP to measure PRS for any RSTD, PRS-RSRP, and UE Rx-Tx time difference measurement as defined in 3 GPP standards, the network must provide: i) a single per-UE measurement gap pattern for concurrent monitoring of all positioning frequency layers and intra-frequency, inter-frequency and / or inter-RAT frequency layers of all frequency ranges, or ii) for some measurement gap patterns, if UE supports independent measurement gap patterns for different frequency ranges for PRS measurement, per-FR measurement gap pattern for the frequency range for concurrent monitoring of all positioning frequency layers and intra-frequency, inter-frequency cells and / or inter-RAT frequency layers in the corresponding frequency range.

[0012] During the per-UE measurement gaps, the UE is not required to conduct reception / transmission from / to the corresponding E-UTRAN PCell, E-UTRAN Scell(s), and NR serving cells for E-UTRA-NR dual connectivity except the reception of signals used for RRM measurement(s) and the signals used for random access procedure according to 3GPP Standard TS38.321. The UE is also not required to conduct reception / transmission from / to thecorresponding NR serving cells for SA (with single carrier or CA configured) except the reception of signals used for RRM measurement(s), PRS measurement s) and the signals used for random access procedure. Further, the UE is not required to conduct reception / transmission from / to the corresponding Pcell, Scell(s) and E-UTRAN serving cells for NR-E-UTRA dual connectivity except the reception of signals used for RRM measurement(s), PRS measurement(s) and the signals used for random access procedure. The UE is also not required to conduct reception / transmission from / to the corresponding NR serving cells for NR-DC except the reception of signals used for RRM measurement(s), PRS measurement(s) and the signals used for random access procedure.

[0013] During the per-FR measurement gaps, the UE is not required to conduct reception / transmission from / to the corresponding E-UTRAN Pcell, E-UTRAN Scell(s) and NR serving cells in the corresponding frequency range for E-UTRA-NR dual connectivity except the reception of signals used for RRM measurement(s) and the signals used for random access procedure according to 3GPP TS38.321. The UE is also is not required to conduct reception / transmission from / to the corresponding NR serving cells in the corresponding frequency range for SA (with single carrier or CA configured) except the reception of signals used for RRM measurement(s), PRS measurement s) and the signals used for random access procedure according to 3GPP TS38.321. Further, the UE is not required to conduct reception / transmission from / to the corresponding Pcell, Scell(s) and E-UTRAN serving cells in the corresponding frequency range for NR-E-UTRA dual connectivity except the reception of signals used for RRM measurement(s), PRS measurement s) and the signals used for random access procedure according to TS38.321. The UE is also not required to conduct reception / transmission from / to the corresponding NR serving cells in the corresponding frequency range for NR-DC except the reception of signals used for RRM measurements), PRS measurements) and the signals used for random access procedure according to TS38.321.

[0014] UEs shall support the measurement gap patterns listed in Table 2 based on the applicability specified in Table 3. For example, the UE determines measurement gap timing based on gap offset configuration and measurement gap timing advance configuration provided by higher layer signaling as specified in 3GPP TS 38.331 and TS 36.331.TABLE 2

[0015] Notably, Table 3 below depicts the applicability for Gap Pattern Configurations supported by the E-UTRA-NR dual connectivity UE or NR-E-UTRA dual connectivity UE.TABLE 3

[0016] Measurement gap configuration

[0017] Measurement gaps can be provided to a UE via RRC (Radio Resource Control) as indicated in Section 6.3.2 of 3GPP TS38.331. For example, the information element (IE) MeasGapConfig specifies the measurement gap configuration and controls setup / release of measurement gaps. An example MeasGapConfig information element 100 is depicted in Figure 1. Likewise, Tables 4A-4B present exemplary descriptions for the different fields of MeasGapConfig information element 100 in Figure 1. Notably, Tables 4A-4B may also be found in 6.3.2 of 3GPP TS38.331.TABLE 4ATABLE 4B SUMMARY

[0018] There currently exist certain challenge(s). For latency-sensitive services, such as XR, measurement gaps make it challenging for a gNodeB (gNB) to serve UEs in such a manner that latency requirements are stilled fulfilled. For example, when a 10 ms Packet Delay Budget (PDB) is utilized, a 3 ms or 6 ms gap length can mean that an XR frame that arrives just before the gap will have to be served within only 7 ms or 4 ms, respectively. This means that measurement gap can have a big impact on XR capacity as shown in Figure 2.

[0019] Notably, graph 200 in Figure 2 depicts the fraction (or percentage) of satisfied XR users (60 frames / sec) with or without measurement gaps configured and activated. Thereliability requirement for XR users is 99%, which means that 99% of the XR frames shall be correctly delivered within the PDB=10 ms. For ‘noGap’ (e.g., see line 201 in Figure 2), no user has measurement gap, while for the ‘3 ms gap length’ and ‘6 ms gap length’ (e.g., see lines 203 and 202 in Figure 2, respectively), all users have a measurement gap configured and activated with 3 ms or 6 ms gap length and 80 ms gap repetition period.

[0020] In simulation, the measurement gap is configured to be aligned with SSB locations where the SSBs are transmitted with a 20 ms periodicity. To avoid all UEs from having a measurement gap at the same time, the UEs are randomly assigned to one of four measurement gap groups, where group z has a measurement gap with a starting time I in ms:Ti (mod 80) = z • 20

[0021] It should also be noted that the 3 ms or 6 ms gap length specifies the minimum achievable gap. In practice there are often other scheduling restrictions that increases the gap length, i.e., the effective gap length is longer than the gap length signaled to the UE. For example, for DL transmissions, the UE cannot be scheduled ‘X’ slots before the gap because the Hybrid Automatic Repeat request (HARQ) ACK / NACK (Acknowledgement / Negative Acknowledgement) feedback transmission will fall into the measurement gap. Likewise, for uplink transmissions, the UE cannot be scheduled ‘ Y’ slots after the measurement gap because the downlink control information (DCI) carrying the UL grant would then fall into the measurement gap.

[0022] The key problem is that an existing semi-static measurement gap configuration can prevent the urgent scheduling of XR traffic, which will lead to extra delay if the XR traffic arrival collides with the configured measurement gap(s).

[0023] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. As described herein, methods for dynamically assigning or canceling measurements that require a measurement gap by dynamic indication via DCI / MAC (Medium Access Control) CE (Control Element) comprise: i) pre-configuring measurement occasions where measurements that require measurement gap can occur, and / or ii) indicating one or more of the pre-configured measurement occasions to be assigned as a one or more measurement gap occasions, i.e., the UE may perform measurements that require measurement gap.

[0024] The solution further describes methods for indication of type of measurement such as perFRl (Frequency Range 1), perFR2 (Frequency Range 2), positioning, MUSIM or ULgap for Tx power management. The solution further describes timeline requirements for said dynamic indication.

[0025] In some embodiments, the disclosed subject matter pertains to methods for dynamically assigning or canceling measurements that require a measurement gap.

[0026] In one embodiment, the disclosed subject matter includes a method performed by a network node for enabling measurement gaps that comprises receiving capability data from a user equipment (UE); utilizing the capability data to configure measurement configuration data that includes measurement occasions (MOs) for the UE to be able to conduct measurements; designating one or more of the MOs to be assigned as one or more measurement gap occasions (MGOs); and sending a MGO indicator that identifies the one or more assigned MGOs to the UE. In some embodiments, the disclosed method may be embodied as a software program or algorithm that is stored in memory and executed by processing circuitry of network node (e.g., a gNodeB, eNodeB, or the like).

[0027] In one embodiment, the disclosed subject matter includes a method performed by a UE for utilizing an indicated measuring gap that comprises receiving a MGO indicator from a network node servicing the UE; obtaining measurement occasions, MOs, that can be used as one or more MGOs by the UE; and determining one or more of the obtained MOs to be used as MGOs based on the MGO indicator. In some embodiments, the disclosed method may be embodied as a software program or algorithm that is stored in memory and executed by processing circuitry of network node (e.g., a gNodeB, eNodeB, or the like).

[0028] In one embodiment, the disclosed subject matter includes a method performed by a network node that comprises receiving capability data from a UE; utilizing the capability data to configure measurement configuration data that includes measurement gap occasions (MGOs) for the UE to be able to conduct measurements; and designating one or more MGOs to be assigned as one or measurement occasions MOs; and sending a MGO indicator that identifies the one or more designated MGOs to the UE. In some embodiments, the disclosed method may be embodied as a software program or algorithm that is stored in memory and executed by processing circuitry of network node (e.g., a gNodeB, eNodeB, or the like).

[0029] Certain embodiments may provide one or more of the following technical advantage(s). Notably, the disclosed subject matter improves a gNB’s ability to control when the UE performs measurements that require a measurement gap.BRIEF DESCRIPTION OF THE DRAWINGS

[0030] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings:

[0031] Figure 1 depicts an example MeasGapConfig information element;

[0032] Figure 2 depicts a graph depicting a fraction of satisfied XR users without or without a measurement gap configured and activated;

[0033] Figure 3 depicts a diagram of a sequence of measurement occasions (MOs) according to some embodiments;

[0034] Figure 4 depicts example Radio Resource Control information element according to some embodiments;

[0035] Figure 5 depicts a diagram of a DCI indicating a MO that can be used as an measurement gap occasion (MGO) according to some embodiments;

[0036] Figure 6 depicts a diagram of a MGO indicator that is used to indicate a type of MO according to some embodiments;

[0037] Figure 7 depicts the management of mandatory and optional occasions according to some embodiments;

[0038] Figure 8 depicts a flow chart of an example method performed by a network node for enabling an measurement gap occasion according to some embodiments;

[0039] Figure 9 depicts a flow chart of an example method performed by a user equipment for enabling an measurement gap occasion according to some embodiments;

[0040] Figure 10 depicts a flow chart of an example method performed by a network node for canceling a measurement gap occasion according to some embodiments;

[0041] Figure 11 depicts a block diagram of a communication system in accordance with some embodiments;

[0042] Figure 12 is a block diagram of a user equipment in accordance with some embodiments;

[0043] Figure 13 is a block diagram of a network node in accordance with some embodiments;

[0044] Figure 14 is a block diagram of a host device in accordance with some embodiments; and

[0045] Figure 15 is a block diagram of a virtualization environment in accordance with some embodiments.DETAILED DESCRIPTION

[0046] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0047] Below embodiments can be applied to licensed, unlicensed, time division duplex (TDD), frequency division duplex (FDD), shared spectrum, any spectrum types (e.g., existing spectrums like FR1, FR2 or new regions, such as beyond FR2, or high-bands, or terahertz (THz) frequencies which are likely to be used in 6G), and / or any combination.

[0048] Below embodiments are described using Uu interface node examples (e.g., where the gNB transmits SSBs and the UE monitors / measures the SSB / signaling). However, the same embodiments can be extended to a direct communications interface (PC5) without departing from the scope of the disclosed subject matter. In some embodiments, a UE may transmit SSB(s) while another UE monitors / measures the SSB / signaling. Note, during extension, the signaling can be revised as per the interface applicability. For example, instead of DCI, the UE will transmit sidelink control information (SCI) and the like.

[0049] In embodiments, a Measurement Occasion (MO) is referred to as a time occasion with a start time and time duration (or length) where the UE can possibly have a measurement gap occasion (MGO). For example, Figure 3 depicts a diagram of a sequence of measurement occasions according to some embodiments. Notably, the MOs 301 may have a 20 ms periodicity aligned with the time locations for SSB transmissions 302 as illustrated in Figure 3.

[0050] In some embodiments, a gNB sends an MGO indicator indicating that one or more MOs can be used by UE as a MGO. The MGO indicator may be transmitted as a DCI, MAC CE, or RRC message.

[0051] In some embodiments, the MGO indicator indicates an entry in a RRC configured list or table (e.g., row, column, index in a table / list) stored in the UE where the entry identifies MOs and their type. The type may be MO for perFRl (Frequency Range 1), perFR2 (Frequency Range 2), positioning, MUSIM, or UL gap for Tx power management.

[0052] In some embodiments, the one or more MOs may either be explicitly indicated or implicitly indicated by the MGO indicator. For example, implicitly indicated MOs may include i) a starting MO and a number of MOs and / or ii) a bitmap referencing / indicating an ‘X’ number of MOs, wherein each MO has an identifier in the bitmap, e.g., M0#n, . . ., M0#n+m-l where “n” is a numbering variable and “m” is the size of the bitmap, and where a value ‘0’ (or ‘ 1’)may indicate that corresponding MO shall not be used as an MGO while a value ‘ 1’ (or ‘0’) may indicate that corresponding MO may be used as MGO.

[0053] Likewise, with implicitly indicated MOs, the MGO indicator may indicate a value ‘ Y’ indicating a number of ‘ Y’ MOs that may be used by the UE as MGOs, where the indicated Y MOs, which may be identified / referenced as M0#n, ..., MO#n+Y-l, etc., are determined relative to the transmission of the MGO indicator or starting from the first MO after ‘R’ symbols / slots etc. after the last symbol of the physical downlink control channel (PDCCH) signal that carried the DCI including the MGO indicator. In some embodiments, “R” represents the number of symbols that come after the last symbol of the PDCCH signal that carries the MGO indicator.

[0054] In some embodiments, the MGO is measurement object specific, i.e., different measurement gap occasions are used depending on the carrier and / or cell that is to be measured. In one scenario, the UE may be configured with multiple MGOs where each MGO has one or more associated measurement objects. The associated measurement objects can be indicated in the MGO indicator.

[0055] In some embodiments, the MGO to be applied may depend on the UE’s active carrier bandwidth parts (BWPs), serving cells, and the measurement objects. For example, the UE may be able to measure reference signals on a carrier / cell without a measurement gap if the reference signal of the carrier / cell to be measured is contained in the active BWP of one of the UE’s serving cells. In this scenario, the network (e.g., a network node, gNB, etc.) may still configure the UE with a MGO, but the measurement gap may be skipped if the current configuration is such that the UE can conduct a reference signal measurement without a measurement gap. Similarly, in the case of a multi-beam operation, the current beam of the UE may be used as a factor when determining the need for a measurement gap. For example, if the gNB knows that the cell / reference signal to be measured can be received with the UE’s current receive beam, then no measurement gap is required. It is also possible that the network (e.g., a network node, gNB, etc.) configures the UE with multiple MGOs associated with different UE configurations, and the UE switches between these MGOs depending on its current configuration. For example, the UE may be configured with two MGOs and the UE switches between these depending on the currently active BWP on the Pcell. For example, if the UE is using BWP#1, the UE could use a denser MGO pattern. Likewise, the UE is using if BWP#2, the UE could use a sparser MGO pattern or no MGO pattern at all (e.g., if the UE is able to measure reference signals without a measurement gap on the MOs).

[0056] In some embodiments, the MGO indicator is broadcast, multicast, or transmitted as a group-common DCI indicating one or more MOs and a list of UE identifiers identifying the UEs that may use the one or more MOs as MGOs. In some embodiments, the group- common DCI is scrambled with a group-common MGO-Radio Network Temporary Identifier (MGO-RNTI). In some embodiments, the group-common DCI is formatted by the network node as a set of bit-blocks, e.g., block number 1, block number 2, . . ., block number A, where each block comprises a UE-specific MGO indicator. In some examples, each block comprises a UE identifier explicitly, while in other examples the UE identifier is implicitly defined by an RRC configured parameter indicating the starting bit position, e.g., startingBit, of the UE’s block. For example, UE may be configured with a RRC IE 400 as shown in Figure 4.

[0057] In some embodiments, the fieldType in RRC IE 400 may be present to indicate the size of the block, i.e., the number of bits for the block. For example, fieldType = 0 may indicate mo number of bits while fieldType = 1 may indicate mi number of bits. In some such examples, the block includes only the MGO indicator while in other examples the block may include multiple sub-blocks. For example, the block may be formatted as: MGO type (ri bits) and / or MGO indicator (r2 bits).

[0058] In some embodiments, the MGO type may be the type of the MO as discussed above. The and / or r2may be fixed by specification or explicitly configured. For example, may have a fixed number of bits while r2may be determined from fieldType. In some examples, fieldType is replaced by fieldType 1 and fieldType2, whereby rxis determined from fieldTypel and r2is determined from fieldType2.

[0059] In some embodiments, the MGO indicator is transmitted as a field in a downlink and / or uplink UE-dedicated (e.g., UE-specific / unicast) DCI, e.g., Format 0 0, Format 0 1, Format 0 2, Format 1 0, Format 1 1 and / or Format 1 2.

[0060] Figure 5 illustrates a number of MOs 503 that can possibly be designated as MGOs. For example, Figure 5 depicts a DCI 501 indicating a MO that UE may use as an MGO 502. In some embodiments, the MGO indicator 501 may indicate the type of MO. For example, the UE may be pre-configured with a first set of MOs of a first type and a second set of MOs of a second type, where MGO indicator may include a MO indicator and MO type indicator. For example, the first set of MOs 6011...3 and second set of MOs 6021 . 3 may be fully timeoverlapping as illustrated in Figure 6.

[0061] In some embodiments, the signaling can indicate a MGO configuration of more than one carrier and / or cell. For example, a DCI transmitted in BWP#B I in a carrier#Clindicates two MGO configurations associated with BWP B1 in carrier#Cl (i.e.,. associated configuration is MG0 M1) and BWP B2 in carrier#C2 (i.e., associated configuration is MGO M2).

[0062] In some embodiments, the UE operates (e.g., receives and / or transmits) on a set of carriers and / or cells, wherein the UE may need a measurement gap but only of a first subset of the set of carriers / cells and is still capable to operate (e.g., receive and / or transmit) on a second subset of the set of carriers / cells. In such embodiments, the MGO indicator may indicate if a first subset or second subset of the set of carriers / cells applies the MO as an MGO.

[0063] In some embodiments (e.g., as described above), the Layer 1 / Layer 2 (L1 / L2) signaling (e.g., DCI or MAC CE) can indicate a change in a MGO / MO pattern. For instance, consider a scenario where a UE is currently being served with enhanced mobile broadband (eMBB) traffic and have a configured MO pattern, such as with gap pattern ID 0. After some time, the UE is triggered with events where the UE is served with XR traffic. The network (e.g., network node) then sends a signal indicating a change in the gap pattern ID, e.g., to ID 11 with fewer measurement gaps in order to serve XR traffic with higher capacity as compared to earlier eMBB traffic.

[0064] In some embodiments, a network node can send dynamic signaling to override a MGO location that has been previously allocated by some previous dynamic or semi-static signaling. Further, in some embodiments, a network node can define prioritization policies on using MO / MGO and the overlapping scheduled resources. For instance, if the scheduled resource belongs to and / or is mapped to Ultra-Reliable Low Latency Communications (URLLC) or XR traffic (e.g., possibly mapped using logical channel / logical channel group (LCH / LCG) mapping / restrictions), then the data transmission will take precedence and the MGO will be deprioritized. However, if the scheduled resource belongs to and / or is mapped to the eMBB traffic, then the MGO will be prioritized, and scheduled eMBB transmissions over the overlapped resource will be deprioritized, i.e., because eMBB can handle longer delays unlike XR / URLLC.

[0065] In some embodiments, the MGO indicator may indicate two or more MOs that are conflicting, i.e., the UE cannot perform measurements on all of the two or more MOs. In such embodiments, it may be up to UE implementation to select which MO to choose as the MGO. In other embodiments, the UE is provided priorities for the two or more MOs. The priority may in some embodiments be included in the MGO indicator.

[0066] In some embodiments, the MGO indicator is transmitted in a UE-dedicated DCI where the indicated one or more MOs to be used as a MGO are conditioned to occur if aPhysical Downlink Shared Channel (PDSCH) assigned by the DCI is correctly decoded by the UE.

[0067] In some embodiments, the MGO indicator can indicate a conditional MGO operation, i.e., if some transmissions conducted over a shared channel are not correctly decoded the UE will use an indicated one or more MOs as the MGO(s). This is because erroneous / incorrect decoding of data transmissions trigger the new measurements which can be helpful in decoding the scheduled retransmission or new transmissions onwards. In one example, the MGO indicator, as stated above, can be merged and / or included in resource allocation signaling (e.g., DCI / RRC) allocating a shared channel (e.g., PUSCH / PDSCH which may be Dynamic Grant (DG) based, Semi -Persistent Scheduling / Configure Grant (SPG / CG) based, or multi-slot variants as well). Hence, if the transmissions over a shared channel are not decoded properly, the UE will be triggered to perform measurements in the indicated MO (e.g., as defined in the signaling or with a-priory configuration).

[0068] In some embodiments, the MGO indicator may be transmitted to the UE if a timeline requirement is fulfilled. As used herein, a timeline requirement being fulfilled means that the MGO indicator is transmitted early enough to provide the UE sufficient processing time, i.e., decoding of the indicator and perform the action indicated. In addition, the UE may also apply a MO as an MGO if a timeline requirement is fulfilled. Further, if the MGO indicator is included in the scheduling DCI, then the network is able to send DCI (and thus the MGO indicator) even just before the MO. However, the first DCI that conducts the ‘MO -> MGO’ change shall fulfill the timeline requirement while later DCI (also including the MGO indicator) can be transmitted without timeline restriction.

[0069] In some embodiments, the timeline requirement may be expressed as that the first symbol s0of the earliest MO indicated as an MGO does not precede a symbol with CP starting after (i.e., a ‘MGO procedure time’) after a last symbol of the PDCCH signal that carries the MGO indicator, where:and where K and Tcare defined in 3GPP TS 38.211, / / is the numerology, NMG0may be based on the UE PDSCH processing capability or UE PUSCH processing capability. In some examples, NMG0may be replaced with NMG0+ dxwhere dxis an extra time margin. The value for NMG0and / or dxmay depend on UE capability.

[0070] If the MOs indicated by the MGO indicator are conditioned on the correct decoding of one or more PDSCH assigned by the DCI that also indicates the MGO indicator, the first symbol s0of the earliest MO indicated as an MGO does not start before a symbol with CP starting after and after a last symbol of any PDSCH assigned by the DCI, whereis given by the maximumthe i-th PDSCH with a corresponding HARQ-ACK transmission on a PUCCH that is in the group of overlappingextra margin andis based on the UE PDSCH processing capability.

[0071] In some embodiments, the MGO indicator implicitly indicates a single MO that the UE may use as a MGO wherein the single MO is the first (i.e., earliest) MO such that a timeline requirement is fulfilled. In some embodiments, the MGO indicator may include a bitfield indicating a MO type / configuration only where, e.g., all ‘0’ (or all ‘ 1 ’) may indicate “no MO is indicated as a MGO”. For example, the MGO indicator may have values as shown in Table 5 below:TABLE S

[0072] In some embodiments, a MO may be configured to UE to have one or more sub- MOs and wherein the MGO indicator may indicate that the whole MO or one or more of the sub-MOs shall be used as a MGO. For example, during a MO there may be 2N reference signals that the UE can measure on where the first N reference signals are present on the first half of the MO and where the second N reference signals are present on the second half of the MO and wherein the MGO indicator may indicate the UE shall use the first half or second half of the MO as a MGO. In some examples, the sub-MOs can be configured as separate configurations of MOs while in other examples the MGO indicator comprises an indication of sub-MO gap length and gap offset, wherein the sub-MO gap offset is a time offset with respect to the start time of the MO.

[0073] In some embodiments, a network node can configure MOs using L1 / L2 / RRC signaling. However, the network node can additionally indicate which occasions (e.g., MOs) from the configured occasions set that the UE is allowed to ‘’skip’ (or cancel) themeasurements if specific conditions are fulfilled. The conditions can be specified by the network node, e.g., a form of explicit signaling is required to conform the cancelled status, or left to implementation (i.e., implicit behavior, e.g., UE autonomously decides). In some embodiments, the network node is configured to specify a subset or a bitmap of a subset of MOs, which the UE can consider optional for measurement in the initial signaling when MOs are configured. In another embodiment, instead of defining an optional skipping subset of MOs, the network node can indicate a subset or a bitmap of a subset of MOs that are mandatory for the reference signal measurement operation from the set of occasions and the remaining will be optional for reference signal measurements subject to the conditions. When the UE intends to skip the optional MO, or when the network node wants the UE to skip the optional MO, an explicit or implicit signaling can be sent by the network node to the UE. Some designs of explicit or implicit signaling are discussed in the above embodiments. For example, Figure 7 depicts a diagram 700 where the condition for the skipping (i.e., cancellation) of an optional occasion is that if a UE receives some explicit signaling indicating the cancellation before the configured optional occasion which is set optional. Further, in order to send LI signaling, an optimal or desired search space / CORESET is configured for the UE to monitor related DCIs which may indicate a cancellation of occasions. In some embodiments, the network node configures a search space before the occasions. However, the search space can be configured with any pattern as per the network requirements.

[0074] In Figure 7, diagram 700 illustrates an example DCI monitoring process that can be conducted by a UE. Notably, diagram 700 depicts how the UE monitors the cancellation DCI for an occasion in the search space configured before the concerned occasion. In another embodiment, another pattern can be defined, where, e.g., in Figure 8, the configured search space before N+l occasion where the UE can monitor DCI, which may indicate the cancellation of N+l or N+2 or both occasions. Similarly, in the search space before the N+4 occasion, the UE may monitor the DCI, which may indicate cancellation of N+4 or N+5 or both occasions, and so on. While in Figure 7, a LI format (e.g., DCI) is selected, it is understood that other formats can be utilized without departing from the scope of the disclosed subject matter. For example, L2 or MAC CEs can also be utilized for the cancellation indication, but these formats will be slower. In another embodiment, instead of cancellation, the UE may assume a default behavior of not utilizing the optional occasions for reference signal measurements, unless the UE receives some indication, e.g., via LI or L2 signaling, before the optional occasions (as per the required timeline) to use the optional occasions for measurements. Further, in the example illustrated in Figure 7, one signaling transmission indicates the cancellation of one occasion (orutilization of one occasion as explained above). However, these are examples such that an indication can map to one or more occasions (e.g., using a bitmap) or indicate the length of the window (after the offset from the indication) containing occasions, where these occasions (if are configured optional, and the mandatory occasions perhaps can be excluded / ignored as their status cannot be changed, i.e., measurements over them are compulsory) are regarded as canceled or considered for utilization for measurement depending on default behavior. In addition, for optional an MO, the UE can indicate or recommend to the network node (e.g., gNB) in some UL signaling whether the UE wants to use the MO or not for measurement gaps depending on what is the default usage. Hence, based on this proposal, a flexible UE-specific configuration can be designed. For instance, the UEs are provided with MO pattern or resources. However, depending on the UE’s requirement s), the functionality can be chosen accordingly. For instance, if a UE is located close to a cell boundary, then the UE’s default setting will be to utilize the MOs for measurements and send explicit L1 / L2 signaling if the network node wants the UE to cancel some specific occasions and prioritize the overlapping resource for data transmission / scheduling. Alternatively, if a UE is located away from cell boundary, then the UE’s default setting will be to not utilize the MOs for measurements and send explicit L1 / L2 signaling if the network node wants the UE to utilize some specific occasions for measurements.

[0075] Methods for selecting a MO as a MGO and / or a gNB method for determining to send MGO indicator are disclosed herein. In some embodiments, the network node uses traffic awareness information when determining if a MO should be used by the UE as an MGO. The network node, e.g., a gNB, may send a MGO indicator indicating a MO to be used as a MGO if one or more out of the following conditions are fulfilled: i) gNB has no outstanding timesensitive data, e.g. all XR data has been served, ii) the gNB has received an ACK for all scheduled PDSCHs comprising time-sensitive data, iii) the gNB has correctly decoded all scheduled PUSCHs comprising time-sensitive data, and / or iv) the gNB does not expect new time sensitive data to arrive earlier than a time ta= tMG0+ A, where tMG0is the start (or end) time of the MGO and A is a threshold. For example, tMG0is the start time of the MGO, A = "gap length" corresponds to that gNB does not expect new time sensitive data to arrive earlier than the end time of the MGO. In some embodiments, A is selected based on the distribution of the data arrival jitter. For example, A may be selected such that at the probability that new time sensitive data arrives earlier than ta= tMG0+ A is lower than P.

[0076] Methods for UE measurement report at the reception of the MGO indicator are disclosed herein. In some embodiments, when the MGO is indicated by a gNB, the UE can also trigger a measurement report. The measurement report can be RS SI, RSRP, RSRQ, or any other format of measurements to assist the optimal selection of a target cell for handover. For example, a UE report is triggered immediately after the measurement indicated by the MGO, and the report result is sent in the next earliest uplink resource. In some embodiments, after an ‘N’ (i.e., where N is greater than or equal to 1) number of MOs are measured based on the MGO indication, a UE may be configured to report measurement results. The N is configured as a higher layer by a network node in a network. All the measurement reports can be either LI reporting via a physical channel or L3 reporting via RRC. If a periodic or event-trigger measurement report is pre-configured in ReportConfigNR, the MGO indication triggered report may also override the preconfigured report. For example, when a periodic report is preconfigured but a MGO indication triggered report is received, the receiving UE will cancel the next earliest periodic report but prepare the measurement report as soon as the UE receives MGO indication.

[0077] In some embodiments, the indication of MGO can also include the timing information of the measurement report, e.g., X slots / frames / symbols index where the measurement result is reported. A UE can measure the indicated MGO and prepares the measurement results to report them in the indicated time. In addition, the indication can also include a grant for radio resource for the measurement result report if it is signaled by DCI.

[0078] Figure 8 is a flow chart of a method and / or process 800 (e.g., a process for indicating measurement gaps) executed by one or more network nodes (e.g., a gNB, eNB, or any other access network node that can establish a wireless / cellular connection). In some embodiments, process 800 may represent a software algorithm that is stored in memory and executed by one or more processors (and / or processing circuitry) of a network node. For example, process 800 may be stored in memory 1304 and executed by processing circuitry 1302 as shown in Figure 13 and described below.

[0079] In block 801, process 800 includes receiving capability data from a user equipment (UE). In some embodiments, a network node, such as a gNB, receives capability data from a UE being serviced. For example, the capability data may include RRC measurement information corresponding to the sending UE.

[0080] In block 802, process 800 includes utilizing the capability data to configure measurement configuration data that includes measurement occasions (MOs) for the UE to be able to conduct measurements. In some embodiments, the network node uses the capabilitydata received from the UE to configure measurement configuration data related to the UE. The measurement configuration data may include MOs that the UE may be able to use to conduct measurements. Notably, the MOs may be a time occasion with a start time and a time duration / length where it is possible for the UE to have a measurement gap occasion (MGO).

[0081] In block 803, process 800 includes designating one or more of the MOs to be assigned as one or more measurement gap occasions (MGOs). In some embodiments, the network node is configured to designate one or more of the MOs to be assigned to be one or more MGOs.

[0082] In block 804, process 800 includes sending a MGO indicator that identifies the one or more assigned MGOs to the UE. In some embodiments, the network node is configured to transmit the MGO indicator(s) to the UE via a message and / or signal such as, but not limited to, a DCI message, a media access control (MAC) CE message, and / or an RRC message. In some embodiments, the MGO indicator identifies one or more MOs to be assigned as an MGO. The MGO indicator may also implicitly or explicitly (as described above) identify an entry in an RRC configured table located on the UE.

[0083] In some embodiments, the network node comprises an eNodeB or a gNodeB. In some embodiments, the MGO indicator is communicated by the network node to the UE via a downlink control indication (DCI) message, a MAC control element message, or a radio resource control (RRC) message. In some embodiments, the MGO indicator either implicitly or explicitly identifies an entry in an RRC configured table stored on the UE. In some embodiments, the MGO indicator identifies a row index in the RRC configured table stored on the UE. In some embodiments, the MGO indicator identifies one of a plurality of multiple RRC configured tables, a row index in the identified RRC configured table, and type information that identifies a measurement configuration stored on the UE. In some embodiments, the one or more assigned MGOs are aligned with time locations of synchronization signal block, SSB, transmissions. In some embodiments, the MGO identifier indicates a measurement type for each of the measurements. In some embodiments, the measurement type comprises a FR1 measurement, a FR2 measurement, or a positioning measurement.

[0084] In some embodiments, the UE is configured to cancel at least one of the one or more assigned MGOs based on the active BWP, serving cells, and / or measurement objects. In some embodiments, the MGO indicator is transmitted to the UE if a timeline requirement is fulfilled for MOs assigned as MGOs. In some embodiments, either the MOs or MGOs are referenced after at least one symbol after the end of a PDCCH signal that carries the MGO indicator. In some embodiments, the timeline requirement includes a first symbol (s0), whichcorresponds to the earliest MO that is indicated as an MGO, that does not precede a previous symbol with a cyclic prefix (CP) starting after a last symbol of a PDCCH signal that carries the MGO indicator. In some embodiments, the MGO indicator indicates a subset or a bitmap of subset of measurement occasions that are mandatory for measurement by the UE and / or a remaining subset of measurement occasions that is optional for measurement by the UE. In some embodiments, the UE performs a measurement of a reference signal during the assigned MGOs. In some embodiments, the UE does not transmit or receive any signal communications during the assigned MGOs.

[0085] After the MGO indicator is sent to the UE, the UE executes a number of steps to utilize one or more MGOs to conduct at least one measurement and / or “activate” a measurement gap (such that the UE cannot be reached by data / signaling during that measurement gap period). Notably, Figure 9 below illustrates an example of the UE processing conducted after it receives the MGO indicator from the source gNB.

[0086] Figure 9 is a flow chart of a method and / or process 900 (e.g., a process for utilizing an indicated measuring gap) executed by one or more UEs (e.g., a smartphone, tablet, laptop computer, or any other computing device that can utilize a wireless / cellular data connection). In some embodiments, process 900 may represent a software algorithm that is stored in memory and executed by one or more processors (and / or processing circuitry) of a UE. For example, process 900 may be stored in memory 1210 and executed by processing circuitry 1202 as shown in Figure 12 and described below.

[0087] In block 901, process 900 includes receiving a MGO indicator from a network node servicing the UE. In some embodiments, the UE receives the MGO indicator via a message and / or signal such as, but not limited to, a DCI message, a MAC CE message, and / or an RRC message. As described above, the MGO indicator identifies one or more MOs to be assigned as an MGO.

[0088] In block 902, process 900 includes obtaining MOs that can be used as one or more MGOs by the UE. In some embodiments, the MOs are obtained by the UE using the MGO indicator to obtain RRC configuration data of the MOs, which can be indicated / designated as MGOs. In some embodiments, the MOs are obtained via the reception of an RRC message configuring the UE with MOs or sets of MOs. In some embodiments, the MOs may be obtained via entries in a table (e.g., a table including an Entry 1 : Measurement MOs of length x and an Entry 2: Measurement MOs of length y).

[0089] In block 903, process 900 includes determining one or more of the obtained MOs to be used as MGOs based on the MGO indicator. In some embodiments, the UE may beconfigured to determine a particular set of MOs is referenced or identified by the MGO indicator. For example, the UE may utilize the MGO indicator to identify an entry implicitly or explicitly in an RRC configured table. Notably, the MGO indicator can identify a row index in the table. If multiple tables are utilized, the MGO indicator can also indicate a “measurement type” as well as identify the particular table (e.g., “row index” and “type” data can be used to identify a particular configuration).

[0090] In optional block 904, process 900 may include utilizing the determined one or more MGOs to conduct at least one measurement. In some embodiments, the UE utilizes the determined MGOs to perform a measurement during the designated time period of the MGO (i.e., the UE cannot be reached by data / signaling during this measurement gap period).

[0091] In some embodiments, the network node comprises an eNodeB or a gNodeB. In some embodiments, the MGO indicator is communicated by the network node to the UE via a downlink control indication, DCI, message, a MAC control element message, or a radio resource control, RRC, message. In some embodiments, the MGO indicator either implicitly or explicitly identifies an entry in an RRC configured table. In some embodiments, the MGO indicator identifies a row index in the RRC configured table. In some embodiments, the MGO indicator identifies one of a plurality of multiple RRC configured tables, a row index in the identified RRC configured table, and type information that identifies a measurement configuration. In some embodiments, the one or more MGOs are aligned with of time locations of synchronization signal block (SSB) transmissions. In some embodiments, the MGO identifier indicates a measurement type of the at least one measurement. In some embodiments, the measurement type of the at least one measurement includes a FR1 measurement, a FR2 measurement, or a positioning measurement. In some embodiments, the MOs are obtained based on an RRC configuration and / or the MGO indicator.

[0092] Figure 10 is a flow chart of a method and / or process 1000 (e.g., a process for skipping and / or cancelling measurement gaps) executed by one or more network nodes (e.g., a gNB, eNB, or any other access network node that can establish a wireless / cellular connection). In some embodiments, process 1000 may represent a software algorithm that is stored in memory and executed by one or more processors (and / or processing circuitry) of a network node. For example, process 1000 may be stored in memory 1304 and executed by processing circuitry 1302 as shown in Figure 13 and described below.

[0093] In block 1001, process 1000 includes receiving capability data from a UE.

[0094] In block 1002, process 1000 includes utilizing the capability data to configure measurement configuration data that includes measurement gap occasions (MGOs) for the UE to be able to conduct measurements.

[0095] In block 1003, process 1000 includes designating one or more MGOs to be assigned as one or measurement occasions MOs.

[0096] In block 1004, process 1000 includes sending a MGO indicator that identifies the one or more designated MGOs to the UE.

[0097] In some embodiments, the UE is prohibited from performing a measurement of a reference signal during the one or more identified MGOs. In some embodiments, the UE is permitted to transmit and / or receive signal communications during the one or more identified MGOs. In some embodiments, the UE conducts the measurement irrespective of the one or more designated MGOs if the reference signal being measured is contained in an active bandwidth part (BWP) of at least one serving mobile network cell supporting the UE. In some embodiments, the UE skips the one or more designated MGOs in response to receiving an instruction via explicit signaling from the network node. In some embodiments, the network node comprises an eNodeB or a gNodeB. In some embodiments, the MGO indicator is communicated by the network node to the UE via a DCI message, a media access control, MAC, control element message, or a RRC message. In some embodiments, the MGO indicator either implicitly or explicitly identifies an entry in an RRC configured table stored on the UE. In some embodiments, the MGO indicator identifies a row index in the RRC configured table stored on the UE. In some embodiments, the MGO indicator identifies one of a plurality of multiple RRC configured tables, a row index in the identified RRC configured table, and type information that identifies a measurement configuration stored on the UE. In some embodiments, the one or more assigned MGOs are aligned with time locations of synchronization signal block (SSB) transmissions.

[0098] Figure 11 shows an example of a communication system 1100 in accordance with some embodiments. In the example, the communication system 1100 includes a telecommunication network 1102 that includes an access network 1104, such as a radio access network (RAN), and a core network 1106, which includes one or more core network nodes 1108. The access network 1104 includes one or more access network nodes, such as network nodes 1110a and 1110b (one or more of which may be generally referred to as network nodes 1110), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non- 3 GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a basebandportion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 1102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 1102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 1102, including one or more network nodes 1110 and / or core network nodes 1108.

[0099] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O- CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 1110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1112a, 1112b, 1112c, and 1112d (one or more of which may be generally referred to as UEs 1112) to the core network 1106 over one or more wireless connections.

[0100] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 1100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0101] The UEs 1112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 1110 and other communication devices. Similarly, the network nodes 1110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 1112 and / or with other network nodes or equipment in the telecommunication network 1102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 1102.

[0102] In the depicted example, the core network 1106 connects the network nodes 1110 to one or more hosts, such as host 1116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1106 includes one more core network nodes (e.g., core network node 1108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0103] The host 1116 may be under the ownership or control of a service provider other than an operator or provider of the access network 1104 and / or the telecommunication network 1102, and may be operated by the service provider or on behalf of the service provider. The host 1116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0104] As a whole, the communication system 1100 of Figure 12 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM);Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0105] In some examples, the telecommunication network 1102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1102. For example, the telecommunications network 1102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0106] In some examples, the UEs 1112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi -standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e., being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN- DC).

[0107] In the example, the hub 1114 communicates with the access network 1104 to facilitate indirect communication between one or more UEs (e.g., UE 1112c and / or 1112d) and network nodes (e.g., network node 1110b). In some examples, the hub 1114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1114 may be a broadband router enabling access to the core network 1106 for the UEs. As another example, the hub 1114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1110, or by executable code, script, process, or other instructions in the hub 1114. As another example, the hub 1114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, thehub 1114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 1114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0108] The hub 1114 may have a constant / persistent or intermittent connection to the network node 1110b. The hub 1114 may also allow for a different communication scheme and / or schedule between the hub 1114 and UEs (e.g., UE 1112c and / or 1112d), and between the hub 1114 and the core network 1106. In other examples, the hub 1114 is connected to the core network 1106 and / or one or more UEs via a wired connection. Moreover, the hub 1114 may be configured to connect to an M2M service provider over the access network 1104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1110 while still connected via the hub 1114 via a wired or wireless connection. In some embodiments, the hub 1114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 1110b. In other embodiments, the hub 1114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0109] Figure 12 shows a UE 1200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0110] A UE may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-RangeCommunication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle- to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).[OHl] The UE 1200 includes processing circuitry 1202 that is operatively coupled via a bus 1204 to an input / output interface 1206, a power source 1208, a memory 1210, a communication interface 1212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 12. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0112] The processing circuitry 1202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1210. The processing circuitry 1202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general -purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1202 may include multiple central processing units (CPUs).

[0113] In the example, the input / output interface 1206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 1200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor,a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0114] In some embodiments, the power source 1208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 1208 may further include power circuitry for delivering power from the power source 1208 itself, and / or an external power source, to the various parts of the UE 1200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1208 to make the power suitable for the respective components of the UE 1200 to which power is supplied.

[0115] The memory 1210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1210 includes one or more application programs 1214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1216. The memory 1210 may store, for use by the UE 1200, any of a variety of various operating systems or combinations of operating systems.

[0116] The memory 1210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD- DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 1210 may allow the UE 1200 to access instructions, application programs and the like, stored on transitory or non-transitory memorymedia, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1210, which may be or comprise a device-readable storage medium.

[0117] The processing circuitry 1202 may be configured to communicate with an access network or other network using the communication interface 1212. The communication interface 1212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1222. The communication interface 1212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 1218 and / or a receiver 1220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1218 and receiver 1220 may be coupled to one or more antennas (e.g., antenna 1222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0118] In the illustrated embodiment, communication functions of the communication interface 1212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0119] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0120] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0121] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 1200 shown in Figure 12.

[0122] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0123] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controlleroperating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0124] Figure 13 shows a network node 1300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), 0-RAN nodes or components of an 0-RAN node (e.g, O-RU, O-DU, O-CU).

[0125] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an 0-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0126] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi -standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0127] The network node 1300 includes a processing circuitry 1302, a memory 1304, a communication interface 1306, and a power source 1308. The network node 1300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 1300 comprisesmultiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1304 for different RATs) and some components may be reused (e.g., a same antenna 1310 may be shared by different RATs). The network node 1300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1300.

[0128] The processing circuitry 1302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 1300 components, such as the memory 1304, to provide network node 1300 functionality.

[0129] In some embodiments, the processing circuitry 1302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1302 includes one or more of radio frequency (RF) transceiver circuitry 1312 and baseband processing circuitry 1314. In some embodiments, the radio frequency (RF) transceiver circuitry 1312 and the baseband processing circuitry 1314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1312 and baseband processing circuitry 1314 may be on the same chip or set of chips, boards, or units.

[0130] The memory 1304 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computerexecutable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1302. The memory 1304 may store any suitable instructions, data,or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 1302 and utilized by the network node 1300. The memory 1304 may be used to store any calculations made by the processing circuitry 1302 and / or any data received via the communication interface 1306. In some embodiments, the processing circuitry 1302 and memory 1304 is integrated.

[0131] The communication interface 1306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 1306 comprises port(s) / terminal(s) 1316 to send and receive data, for example to and from a network over a wired connection. The communication interface 1306 also includes radio front-end circuitry 1318 that may be coupled to, or in certain embodiments a part of, the antenna 1310. Radio front-end circuitry 1318 comprises filters 1320 and amplifiers 1322. The radio front-end circuitry 1318 may be connected to an antenna 1310 and processing circuitry 1302. The radio front-end circuitry may be configured to condition signals communicated between antenna 1310 and processing circuitry 1302. The radio front-end circuitry 1318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1320 and / or amplifiers 1322. The radio signal may then be transmitted via the antenna 1310. Similarly, when receiving data, the antenna 1310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1318. The digital data may be passed to the processing circuitry 1302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0132] In certain alternative embodiments, the network node 1300 does not include separate radio front-end circuitry 1318, instead, the processing circuitry 1302 includes radio front-end circuitry and is connected to the antenna 1310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1312 is part of the communication interface 1306. In still other embodiments, the communication interface 1306 includes one or more ports or terminals 1316, the radio front-end circuitry 1318, and the RF transceiver circuitry 1312, as part of a radio unit (not shown), and the communication interface 1306 communicates with the baseband processing circuitry 1314, which is part of a digital unit (not shown).

[0133] The antenna 1310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1310 may be coupled to the radio frontend circuitry 1318 and may be any type of antenna capable of transmitting and receiving dataand / or signals wirelessly. In certain embodiments, the antenna 1310 is separate from the network node 1300 and connectable to the network node 1300 through an interface or port.

[0134] The antenna 1310, communication interface 1306, and / or the processing circuitry 1302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 1310, the communication interface 1306, and / or the processing circuitry 1302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0135] The power source 1308 provides power to the various components of network node 1300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1300 with power for performing the functionality described herein. For example, the network node 1300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1308. As a further example, the power source 1308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0136] Embodiments of the network node 1300 may include additional components beyond those shown in Figure 13 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1300 may include user interface equipment to allow input of information into the network node 1300 and to allow output of information from the network node 1300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1300.

[0137] Figure 14 is a block diagram of a host 1400, which may be an embodiment of the host 1216 of Figure 12, in accordance with various aspects described herein. As used herein, the host 1400 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtualmachine, container, or processing resources in a server farm. The host 1400 may provide one or more services to one or more UEs.

[0138] The host 1400 includes processing circuitry 1402 that is operatively coupled via a bus 1404 to an input / output interface 1406, a network interface 1408, a power source 1410, and a memory 1412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 13 and 14, such that the descriptions thereof are generally applicable to the corresponding components of host 1400.

[0139] The memory 1412 may include one or more computer programs including one or more host application programs 1414 and data 1416, which may include user data, e.g., data generated by a UE for the host 1400 or data generated by the host 1400 for a UE. Embodiments of the host 1400 may utilize only a subset or all of the components shown. The host application programs 1414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 1414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 1400 may select and / or indicate a different host for over-the-top services for a UE. The host application programs 1414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0140] Figure 15 is a block diagram illustrating a virtualization environment 1500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host.Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0141] Applications 1502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0142] Hardware 1504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1508a and 1508b (one or more of which may be generally referred to as VMs 1508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 1506 may present a virtual operating platform that appears like networking hardware to the VMs 1508.

[0143] The VMs 1508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1506. Different embodiments of the instance of a virtual appliance 1502 may be implemented on one or more of VMs 1508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0144] In the context of NFV, a VM 1508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1508, and that part of hardware 1504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1508 on top of the hardware 1504 and corresponds to the application 1502.

[0145] Hardware 1504 may be implemented in a standalone network node with generic or specific components. Hardware 1504 may implement some functions via virtualization. Alternatively, hardware 1504 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1510, which, among others, oversees lifecycle management of applications 1502. In some embodiments, hardware 1504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1512 which may alternatively be used for communication between hardware nodes and radio units.

[0146] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0147] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.EMBODIMENTSGroup A EmbodimentsAl . A method performed by a user equipment, UE, for utilizing an indicated measuring gap, the method comprising: receiving (701) a measurement gap occasion, MGO, indicator from a network node servicing the UE; obtaining (702) measurement occasions, MOs, that can be used as one or more MGOs by the UE; determining (703) one or more of the obtained MOs to be used as MGOs based on the MGO indicator; and utilizing (704) the determined one or more MGOs to conduct at least one measurement.A2. The method of embodiment Al, wherein the network node comprises an eNodeB or a gNodeB.A3. The method of any of the previous embodiments, wherein the measurement gap indicator is communicated by the cellular network base station to the UE via a downlink control indication, DCI, message, a MAC control element message, or a radio resource control, RRC, message.A4. The method of any of the previous embodiments, wherein the MGO indicator either implicitly or explicitly identifies an entry in an RRC configured table.A5. The method of any of the previous embodiments, wherein the MGO indicator identifies a row index in the RRC configured table.A6. The method of any of the previous embodiments, wherein the MGO indicator identifies one of a plurality of multiple RRC configured tables, a row index in the identified RRC configured table, and type information that identifies a measurement configuration.A7. The method of any of the previous embodiments, wherein the one or more MGOs are aligned with of time locations of SSBs transmissions.A8. The method of any of the previous embodiments, further comprising: utilizing the MGOindicator to cancel the one or more measurements.A9. The method of any of the previous embodiments, wherein the MGO identifier indicates a measurement type of the at least one measurement.A10. The method of any of the previous embodiments, wherein the measurement type of the at least one measurement includes a FR1 measurement, a FR2 measurement, or a positioning measurement.Al l. The method of any of the previous embodiments, wherein the MOs are obtained based on i) an RRC configuration (e.g., an MGO indicator implicitly associated with the configured MOs) or ii) both the RRC configuration and the MGO indicator (e.g., the MGO indicator indicates the MOs that are to be MGOs as well as identifying the RRC configuration or entry in an RRC configured table).A12. The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.Group B EmbodimentsBl . A method performed by a network node for indicating measurement gaps, the method comprising: receiving (601) capability data from a user equipment (UE); utilizing (602) the capability data to configure measurement configuration data that includes measurement occasions (MOs) for the UE to be able to conduct measurements; designating (603) one or more of the MOs to be assigned as one or more measurement gap occasions (MGOs); and sending (604) a MGO indicator that identifies the one or more designated MOs to the UE.B2. The method of embodiment Al, wherein the network node comprises an eNodeB or a gNodeB.B3. The method of any of the previous embodiments, wherein the measurement gap indicatoris communicated by the network node to the UE via a downlink control indication, DCI, message, a MAC control element message, or a radio resource control, RRC, message.B4. The method of any of the previous embodiments, wherein the MGO indicator either implicitly or explicitly identifies an entry in an RRC configured table stored on the UE.B5. The method of any of the previous embodiments, wherein the MGO indicator identifies a row index in the RRC configured table stored on the UE.B6. The method of any of the previous embodiments, wherein the MGO indicator identifies one of a plurality of multiple RRC configured tables, a row index in the identified RRC configured table, and type information that identifies a measurement configuration stored on the UE.B7. The method of any of the previous embodiments, wherein the one or more MGOs are aligned with of time locations of SSBs transmissions.B8. The method of any of the previous embodiments, wherein the MGO identifier indicates a measurement type for each of the measurements.BIO. The method of any of the previous embodiments, wherein the measurement type comprises a FR1 measurement, a FR2 measurement, or a positioning measurement.Bl 1. The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.Group C EmbodimentsCl . A user equipment for utilizing an indicated measuring gap, comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.C2. A network node for indicating measurement gaps, the network node comprising:processing circuitry configured to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the processing circuitry.C3. A user equipment (UE) for utilizing an indicated measuring gap, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.C4. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.C5. The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.C6. A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.C7. The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.C8. The method of any of the previous 2 embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.C9. A communication system configured to provide an over-the-top (OTT) service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.CIO. The communication system of the previous embodiment, further comprising: the network node; and / or the UE.Cl l. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, theprocessing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to receive the user data from a user equipment (UE) for the host.C12. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application that receives the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.C13. The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data.C14. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs any of the steps of any of the Group B embodiments to receive the user data from the UE for the host.Cl 5. The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host.Cl 6. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the operations of any of the Group A embodiments to receive the user data from the host.Cl 7. The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host.C18. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.Cl 9. A method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs any of the operations of any of the Group A embodiments to receive the user data from the host.C20. The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the host application.C21. The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.C22. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to transmit the user data to the host.C23. The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.C24. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.C25. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A embodiments to transmit the user data to the host.C26. The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.C27. The method of the previous 2 embodiments, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

Claims

CLAIMSWhat is claimed is:

1. A method (800) performed by a network node (1300) for enabling measurement gaps, the method comprising: receiving (801) capability data from a user equipment, UE (1200); utilizing (802) the capability data to configure measurement configuration data that includes measurement occasions, MOs, for the UE to be able to conduct measurements; designating (803) one or more of the MOs to be assigned as one or more measurement gap occasions, MGOs; and sending (804) a MGO indicator that identifies the one or more assigned MGOs to the UE.

2. The method of claim 1, wherein the network node comprises an eNodeB or a gNodeB.

3. The method of any of claims 1 to 2, wherein the MGO indicator is communicated by the network node to the UE via a downlink control indication, DCI, message, a media access control, MAC, control element message, or a radio resource control, RRC, message.

4. The method of any of claims 1 to 3, wherein the MGO indicator either implicitly or explicitly identifies an entry in an RRC configured table stored on the UE.

5. The method of claim 4, wherein the MGO indicator identifies a row index in the RRC configured table stored on the UE.

6. The method of any of claims 1 to 5, wherein the MGO indicator identifies one of a plurality of multiple RRC configured tables, a row index in the identified RRC configured table, and type information that identifies a measurement configuration stored on the UE.

7. The method of any of claims 1 to 6, wherein the one or more assigned MGOs are aligned with time locations of synchronization signal block, SSB, transmissions.

8. The method of any of claims 1 to 7, wherein the MGO identifier indicates a measurement type for each of the measurements.

9. The method of any of claims 1 to 8, wherein the measurement type comprises a FR1 measurement, a FR2 measurement, or a positioning measurement.

10. The method of any of claims 1 to 9, wherein the UE is configured to cancel at least one of the one or more assigned MGOs based on the active carrier bandwidth part, BWP, serving cells, and / or measurement objects.

11. The method of any of claims 1 to 10, wherein the MGO indicator is transmitted to the UE if a timeline requirement is fulfilled for MOs assigned as MGOs.

12. The method of any of claims 1 to 11 wherein either the MOs or MGOs are referenced after at least one symbol after the end of a physical downlink control channel, PDCCH, signal that carries the MGO indicator.

13. The method of cany of claims 1 to 12, wherein the timeline requirement includes a first symbol (s0), which corresponds to the earliest MO that is indicated as an MGO, that does not precede a previous symbol with a cyclic prefix, CP, starting after a last symbol of a PDCCH signal that carries the MGO indicator.

14. The method of any of claims 1 and 13, wherein the MGO indicator indicates a subset or a bitmap of subset of measurement occasions that are mandatory for measurement by the UE and / or a remaining subset of measurement occasions that is optional for measurement by the UE.

15. The method any of claims 1 and 14, wherein the UE performs a measurement of a reference signal during the assigned MGOs.

16. The method any of claims 1 and 15, wherein the UE does not transmit or receive any signal communications during the assigned MGOs.

17. A network node (1300) comprising: processing circuitry (1302); and at least one memory (1304) storing instructions executable by the processing circuitry to perform operations to:receiving (801) capability data from a user equipment, UE (1200); utilizing (802) the capability data to configure measurement configuration data that includes measurement occasions, MOs, for the UE to be able to conduct measurements; designating (803) one or more of the MOs to be assigned as one or more measurement gap occasions, MGOs; and sending (804) a MGO indicator that identifies the one or more assigned MGOs to the UE.

18. The network node of claim 17, wherein the at least one memory stores further instruction executable by the processing circuitry to perform further operations comprising operations of any one of claims 2 to 16.

19. A method performed by a user equipment, UE, (1200) for utilizing an indicated measuring gap, the method comprising: receiving (901) a measurement gap occasion, MGO, indicator from a network node (1300) servicing the UE; obtaining (902) measurement occasions, MOs, that can be used as one or more MGOs by the UE; and determining (903) one or more of the obtained MOs to be used as MGOs based on the MGO indicator.

20. The method of claim 19, further comprising utilizing (904) the determined one or more MGOs to conduct at least one reference signal measurement.

21. The method of any of claims 19 to 20, wherein the network node comprises an eNodeB or a gNodeB.

22. The method of any of claims 19 to 21, wherein the MGO indicator is communicated by the network node to the UE via a downlink control indication, DCI, message, a MAC control element message, or a radio resource control, RRC, message.

23. The method of any of claims 19 to 22, wherein the MGO indicator either implicitly or explicitly identifies an entry in an RRC configured table.

24. The method of claim 23, wherein the MGO indicator identifies a row index in the RRC configured table.

25. The method of any of claims 19 to 24, wherein the MGO indicator identifies one of a plurality of multiple RRC configured tables, a row index in the identified RRC configured table, and type information that identifies a measurement configuration.

26. The method of any of claims 19 to 25, wherein the one or more MGOs are aligned with of time locations of synchronization signal block, SSB, transmissions.

27. The method of any of claims 19 to 26, wherein the MGO identifier indicates a measurement type of the at least one measurement.

28. The method of claim 27, wherein the measurement type of the at least one measurement includes a FR1 measurement, a FR2 measurement, or a positioning measurement.

29. The method of any of claims 19 to 28, wherein the MOs are obtained based on an RRC configuration and / or the MGO indicator.

30. A user equipment, UE, (1200) comprising: processing circuitry (1202); and at least one memory (1210) storing instructions executable by the processing circuitry to perform operations to: receiving (901) a measurement gap occasion, MGO, indicator from a network node (1300) servicing the UE; obtaining (902) measurement occasions, MOs, that can be used as one or more MGOs by the UE; and determining (903) one or more of the obtained MOs to be used as MGOs based on the MGO indicator.

31. The user equipment of claim 30, wherein the at least one memory stores further instruction executable by the processing circuitry to perform further operations comprising operations of any one of claims 20 to 29.

32. A method performed by a network node, the method comprising: receiving (1001) capability data from a user equipment, UE; utilizing (1002) the capability data to configure measurement configuration data that includes measurement gap occasions, MGOs, for the UE to be able to conduct measurements; designating (1003) one or more MGOs to be assigned as one or measurement occasions, MOs; and sending (1004) a MGO indicator that identifies the one or more designated MGOs to the UE.

33. The method of claim 32, wherein the UE is prohibited from performing a measurement of a reference signal during the one or more identified MGOs.

34. The method of any of claims 32 to 33, wherein the UE is permitted to transmit and / or receive signal communications during the one or more identified MGOs.

35. The method of any of claims 32 to 34, wherein the UE conducts the measurement irrespective of the one or more designated MGOs if the reference signal being measured is contained in an active bandwidth part, BWP, of at least one serving mobile network cell supporting the UE.

36. The method of any of claims 32 to 35, wherein the UE skips the one or more designated MGOs in response to receiving an instruction via explicit signaling from the network node.

37. The method of any of claims 32 to 36, wherein the network node comprises an eNodeB or a gNodeB.

38. The method of any of claims 32 to 37, wherein the MGO indicator is communicated by the network node to the UE via a downlink control indication, DCI, message, a media access control, MAC, control element message, or a radio resource control, RRC, message.

39. The method of any of claims 32 to 38, wherein the MGO indicator either implicitly or explicitly identifies an entry in an RRC configured table stored on the UE.

40. The method of any of claims 32 to 39, wherein the MGO indicator identifies a rowindex in the RRC configured table stored on the UE.

41. The method of any of claims 32 to 40, wherein the MGO indicator identifies one of a plurality of multiple RRC configured tables, a row index in the identified RRC configured table, and type information that identifies a measurement configuration stored on the UE.

42. The method of any of claims 32 to 41, wherein the one or more assigned MGOs are aligned with time locations of synchronization signal block, SSB, transmissions.

43. A network node (1300) comprising: processing circuitry (1302); and at least one memory (1304) storing instructions executable by the processing circuitry to perform operations to: receiving (1001) capability data from a user equipment, UE; utilizing (1002) the capability data to configure measurement configuration data that includes measurement gap occasions, MGOs, for the UE to be able to conduct measurements; designating (1003) one or more MGOs to be assigned as one or measurement occasions, MOs; and sending (1004) a MGO indicator that identifies the one or more designated MGOs to the UE.

44. The network node of claim 43, wherein the at least one memory stores further instruction executable by the processing circuitry to perform further operations comprising operations of any one of claims 33 to 42.

Images