Handling the ratio of measurement gap occasions
By determining and transmitting a RMGO based on performance-related conditions, the UE addresses ambiguity in measurement gap implementation, enhancing handover accuracy and resource management in wireless communication systems.
Patent Information
- Application Number
- PCT/SE2025/051104
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2025-12-09
- Publication Date
- 2026-11-12
AI Technical Summary
The challenge in wireless communication systems is the ambiguity in implementing the Ratio of Measurement Gap Occasions (RMGO) by user equipment (UE), leading to misalignment between UE and the network, which can result in incorrect configuration and potential handover issues.
A method for determining and transmitting a recommended Ratio of Measurement Gap Occasions (RMGO) by the UE to the network, allowing for dynamic adjustment of measurement gaps based on performance-related values and conditions, such as signal strength and mobility, to facilitate other operations during measurement gaps without explicit cancellation.
This approach ensures accurate and unambiguous implementation of RMGO, enabling efficient resource allocation and reducing measurement gaps when necessary, thereby improving handover performance and supporting operations like extended reality services.
Smart Images

Figure SE2025051104_12112026_PF_FP_ABST
Abstract
Description
HANDLING THE RATIO OF MEASUREMENT GAP OCCASIONSTECHNICAL FIELD
[0001] The present disclosure is related to wireless communication systems and more particularly to a user equipment (UE) handling the ratio of measurement gap occasions.BACKGROUND
[0002] FIG. 1 illustrates an example of a new radio (NR) network (e.g., a 5th Generation (5G) network) including a 5G core (5GC) network 130, network nodes 120a-b (e.g., 5G base station (gNB)), multiple communication devices 110 (also referred to as user equipment (UE)).
[0003] Handover is a key functionality in a radio network which enables the 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. In some examples, the network nodes that serve the two cells are the same or a different network node (e.g., a gNB that has multiple transmission / reception points (TRPs) each serving a cell. In additional or alternative examples, the cells operate on same or a different carrier frequency. In additional or alternative examples, the cells operate on different carrier frequencies, but if the carrier frequencies are on same or a different frequency band (e.g., source cell operates on FR1 while target cell operates on FR2). In additional or alternative examples, the cells have same or a different radio access technology (RAT).SUMMARY
[0004] According to some embodiments, a method of operating a user equipment (UE) in a communications network is provided. The method includes determining a recommended ratio of measurement gap occasions (RMGO). The method further includes transmitting an indication of the recommended RMGO to a network node operating in the communications network.
[0005] According to other embodiments, a method of operating a network node in a communications network is provided. The method includes receiving an indication of a recommended ratio of measurement gap occasions (RMGO) from a user equipment (UE) operating in the communications network. The method further includes reallocating resources associated with the UE based on the indication of the recommended RMGO.
[0006] According to other embodiments, a user equipment (UE), a network node, a computer program, computer program product, non-transitory computer readable medium, host, or system is provided to perform one of the above methods.
[0007] Certain embodiments may provide one or more of the following technical advantages. Some embodiments make it possible to correctly and unambiguously implement theRatio of Measurement Gap Occasions (RM GO) in the UE. In some examples, correctly and unambiguously implementing the RMGO can prevent different UEs from implementing this differently, the RMGO information can be ambiguous leading to misalignment between a UE and the network which in turn leads to the broken feature, the network may misinterpret the RMGO information in UAI and configure the UE in a wrong way.BRIEF DESCRIPTION OF THE DRAWINGS
[0008] 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:
[0009] FIG. 1 is a schematic diagram illustrating an example of a 5thgeneration (“5G”) network;
[0010] FIG. 2 is a table illustrating an example of gap pattern configurations;
[0011] FIG. 3 is a table illustrating an example of applicability for gap pattern configurations;
[0012] FIG. 4 is a diagram illustrating an example of a MeasGapConfig information element (IE);
[0013] FIG. 5 is a table illustrating an example of extended reality, XR, traffic characteristics and requirements;
[0014] FIG. 6 is a flow chart illustrating an example of operations performed by a UE in accordance with some embodiments;
[0015] FIG. 7 is a flow chart illustrating an example of operations performed by a network node in accordance with some embodiments;
[0016] FIG. 8 is a block diagram of a communication system in accordance with some embodiments;
[0017] FIG. 9 is a block diagram of a user equipment in accordance with some embodiments; and
[0018] FIG. 10 is a block diagram of a network node in accordance with some embodiments.DETAILED DESCRIPTION
[0019] 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, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodiedin many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present / used in another embodiment.
[0020] Generally, a 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 to its serving gNB a measurement report. The reference signals related to mobility on which UE performs measurements in NR are synchronization signal block (SSB) and channel state information reference signal (CSI-RS). A SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). In NR the SSB can be configured with periodicities 5 ms, 10 ms, 20 ms, 40 ms, 80 ms and 160 ms. The CSI-RS in NR replaces the common reference signal (CRS) in long term evolution (LTE). The CSI-RS can be used for link adaptation purposes (e.g., the UE reports suggested number of layers, pre-coder and modulation and coding scheme (MCS), and for mobility purposes wherein the UE reports the signal strength of the CSI-RS.
[0021] Especially when UE would need to perform inter-frequency measurement (e.g., perform measurement on SSB / CSI-RS on a different carrier frequency than UE currently operating on), the UE may not be capable of simultaneously receiving and transmitting on its serving cell. Measurement gaps are defined (configured) time locations where UE can perform measurements without being required to receive nor transmit. The UE may need measurement gaps to perform inter-frequency measurement but may also require measurement gaps for intrafrequency measurements. Besides measurement gaps for SSB / CSI-RS measurements, the UE may also need measurement gaps for other purposes. In some examples, measurement gaps (e.g., positioning measurement gap) may be used to perform measurements on positioning reference signals. In additional or alternative examples, measurement gaps (e.g., multi-universal subscriber identity module (MUSIM) may be used for purposes such as cell identification and measurement, paging monitoring, system information block (SIB) acquisition, and / or on-demand SI request of the target cell in the target network. In additional or alternative examples, measurement gaps may be used for uplink (UL) gap for transmission (Tx) power management.
[0022] All measurement gaps are similar in the sense that they all have a gap length. The gap length is a time duration where UE does preparations and measures. MUSIM measurement gap can be a-periodic in the sense that the measurement gap occurs at a specific RRC configured starting system frame number (SFN) and starting subframe. MUSIM measurement gap can alsobe configured as periodic with a gap repetition period. All other measurement gaps are periodic. All measurement gaps except positioning measurement gap are configured via RRC. Positioning measurement gaps can be pre-configured via RRC and then activated and de-activated by MAC CE signaling.
[0023] 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 does not support independent measurement gap patterns for different frequency ranges, in order for the requirements to apply the network must provide a single per-UE measurement gap pattern for concurrent monitoring of all frequency layers.
[0024] 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 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.
[0025] If the UE is configured via LPP to measure PRS for any RSTD, PRS-RSRP, UE Rx-Tx time difference measurement and PRS-RSRPP measurement, in order for the requirements to apply, the network must provide:• 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• if UE supports independent measurement gap patterns for different frequency ranges for PRS measurement, i.e. supporting independentGapConfigPRS-r!7, 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.
[0026] 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.
[0027] During the per-UE measurement gaps the UE is not required to conduct reception / transmission from / to the corresponding 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.
[0028] During the per-UE measurement gaps 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.
[0029] During the per-UE measurement gaps the UE is 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.
[0030] 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.
[0031] During the per-UE measurement gaps the UE 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.
[0032] During the per-UE measurement gaps 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.
[0033] During the per-UE measurement gaps the UE is 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 measurement(s), PRS measurement(s) and the signals used for random access procedure.
[0034] UEs shall support the measurement gap patterns listed in FIG. 2 based on the applicability specified in FIG. 3. UE determines measurement gap timing based on gap offset configuration and measurement gap timing advance configuration provided by higher layer signalling.
[0035] In regards to FIG. 3, in E-UTRA-NR dual connectivity mode, if GSM or UTRA TDD or UTRA FDD inter-RAT frequency layer is configured to be monitored, only measurement gap pattern #0 and #1 can be used for per-FR gap in E-UTRA and FR1 if configured, or for per-UE gap. In NR-E-UTRA dual connectivity mode, if UTRA FDD inter-RAT frequency layer is configured to be monitored for SRVCC, only measurement gap pattern #0 and #1 can be used for per-FR gap in E-UTRA and FR1 if configured, or for per-UE gap.
[0036] In E-UTRA-NR dual connectivity mode, non-NR RAT includes E-UTRA, UTRA and / or GSM. In NR-E-UTRA dual connectivity mode, non-NR RAT means E-UTRA, and UTRA for SRVCC.
[0037] When E-UTRA inter-frequency RSTD measurements are configured and the UE requires measurement gaps for performing such measurements, only Gap Pattern #0 can be used.
[0038] For UE supporting supportedGapPattern-NRonfy-NEDC or mecisGapP citterns -NRonfy-ENDC-r 16 but not supporting supportedGapP cittern for the corresponding gap patterns among GP2-11, the corresponding gap patterns are not applicable to measurement of non-NR RATs.
[0039] Inclusion of positioning measurements: Measurement purpose which includes E- UTRA measurements includes also E-UTRA RSRP and E-UTRA RSRQ measurements for E-CID.
[0040] Measurement gap patterns #24 and #25 can be requested only when the UE is configured at least with any of RSTD, UE Rx-Tx, PRS-RSRP or PRS-RSRPP measurements requiring such gaps and can only be used during the corresponding positioning measurement period
[0041] Inclusion of positioning measurements for measurement gaps: Measurement purpose which includes any of FR1 and FR2 measurements includes also RSTD, UE Rx-Tx, PRS-RSRP and PRS-RSRPP measurements.
[0042] FIG. 4 illustrates an example of a MeasGapConfig IE. The MeasGapConfig specifies the measurement gap configuration and controls setup / release of measurement gaps.
[0043] XR applications typically generate traffic with bounded latency requirements, as modelled by 3GPP. Examples of XR traffic characteristics and requirements are shown FIG. 5.
[0044] In an incoming LS, RAN2 has received a request to implement the following in RAN2 specifications:• The information in UAI: a ratio (R) of gap occasions that is recommended for cancellation during a time period of 1 second.o R e {0, 20, 40, 60}%
[0045] In addition, it was also agreed that the solution to cancel / skip measurement gaps in the UE by the network is based on a dynamic indication in the downlink control information (DCI), which is also referred to as the dynamic approach for measurement gap cancellation. An indication in the DCI would tell the UE whether to skip / cancel a particular measurement gap occasion to allow for scheduling of UL / DL traffic. A semi-static indication approach (via RRC,e.g., based on some paterns) for measurement gap cancellation is still under discussion in some 3 GPP groups.
[0046] Measurement gap cancellation in 3GPP Rel-19 is discussed in the context of XR, but this can potentially be extended, as already proposed by several companies, to beyond the XR feature, e.g., to more general RRM.
[0047] There currently exist certain challenge(s). Although it was agreed that the UE Assistance Information (UAI) can include a ratio of the gap occasions (a.k.a. ratio of measurement gap occasions or RMGO) over a time period, it is unclear how / when this UAI is triggered by the UE. While some of these aspects can be specified, others can be left up to UE implementation.
[0048] Various embodiments herein address the above challenges. In some embodiments, a Ratio of Measurement Gap Occasions (RMGO) can be determined and transmited. In additional or alternative embodiments, the RMGO can be a zero RMGO. In additional or alternative embodiments, measurement gaps associated with RMGO can be determined. In additional or alternative embodiments, a static RMGO is provided to indicate UE’s ability to perform other operations during measurement gaps without explicit cancellation of specific measurement gap occasions.
[0049] Embodiments performed by a UE are described below.
[0050] In some embodiments, the UE determines and sends the RMGO. In additional or alternative embodiments, the RMGO is a zero RMGO. In additional or alternative embodiments, the UE determines the measurement gaps associated with the RMGO. In additional or alternative embodiments, the UE can provide static RMGO to indicate UE’s ability to perform other operations during measurement gaps without explicit cancellation of specific measurement gap occasions.
[0051] In some examples, the RMGO can be included in User Assistance Information (UAI). In additional or alternative examples, the RMGO can be sent to facilitate the time resource allocation for XR service, to enable the time resources from measurement gaps for XR data. In additional or alternative examples, the RMGO can further include the information about how evenly / unevenly distributed the expected cancelled measurement gaps during the associated time period (e.g., 1 second).
[0052] Embodiments associated with a UE determining and sending the RMGO are described below.
[0053] In some embodiments, the UE can determine or set the RMGO as a function, F, of the performance-related values, V_i, associated with the cells in a set S (the size of set |S| is 1 or larger). A performance-related value, V_i, can comprise a performance-related or performanceimpacting metric / characteristic (e.g., UE speed, UE activity state, DRX configuration, power saving mode operation, etc) or measurement, e.g., signal strength or signal quality (RSRP, RSRQ, SINR, RSSI, etc.). The function itself can be, e.g., a measurement of the signal strength or quality of a cell, min- or max-function, the worst or performance-limiting V i among the cells in S, an average or weighted average over multiple cells in S, or a mapping table or mapping function (see e.g. Example 2 below. In one example, the set S can include one or multiple serving cells. In another example, the set S can include at least one neighbor cell. In another example, set S comprises cells measured by the UE in the measurement gaps.
[0054] Example 1 : RMGO = F (w_l , V_1 , ... , w_i, V_i, ... , w_N, V_N), where w_i is a weight factor for cell i (in specific examples, w_i can be omitted, can be a scaling factor of 1, or a compensation additive value of 0), V_i is the performance-related value associated with cell i, cells 1..N are comprised in set S of length N.
[0055] Example 2:RMGO =< > < << <>
[0056] In additional or alternative emboidments, the function can be one or more signal strength threshold values enabling the UE to switch between the RMGO’s. For example, with the current set of RMGO’s, if the measured signal strength is greater than thresholdl, then the UE can indicate that the RMGO can be set to 60% i.e., the channel conditions are robust and more occasions can be skipped given that it is unlikely to trigger a handover. If the measured signal strength is less than a thresholdl but greater than threshold2, the UE can indicate that the RMGO be set to 40% i.e., indicating that the channel conditions are worsening with higher likeliness of a handover. Hence, lesser percentage of occasions can be skipped. Similarly for thresholds and threshold4.
[0057] These threshold values can either be provided by the network based on corresponding uplink measurements or chosen by the UE based on implementation.
[0058] In some embodiments, the change, e.g. derivative, in the performance-related value, V i, such as signal strength, triggers UE to report anew RMGO. For example, if serving RSRP (filtered or un-filtered) is degraded more than a threshold the UE may report a lower RMGO. In some embodiments triggers for new RMGO is based on both signal strength (as in aboveembodiments) and the change in signal strength. For example, a new RMGO may only be triggered due to change in signal strength if the signal strength itself is above or below a threshold.
[0059] In additional or alternative embodiments, the function can be the mobility state of the UE i.e., if the UE is stationary, then it can indicate a preference to have a higher percentage of RMGO as opposed to when the UE is mobile, where due to varying channel conditions and higher chances of a handover, the UE can indicate a lower percentage of the RMGO.
[0060] In additional or alternative embodiments, the UE based on the determination methods as described in the above embodiments, can send an RMGO in the UAI towards the network. The UE also based on the determination methods, update the RGMO and re-send the new value in a subsequent UAI.
[0061] In additional or alternative embodiments, the UE can be configured with a prohibit timer to prevent the UE from sending the updates to the RGMO very often. This prohibit timer is configured by the network in a DL RRC message and upon reception, the UE applies this value between RGMO updates i.e., the updated RGMO can only be sent if the prohibit timer is not running. The timer is started every time an RGMO is sent in the UAI. The prohibit timer may also be cancelled if UE receives a RRC message including a RRC (re-)configuration. The RRC (re-)configuration being one or more out of: MG configuration or re-configuration; DRX configuration or re-configuration; and / or UE triggers transmission of (other) UE assistance information such as UEAssistancelnformation message initiated to provide UL traffic information, suggested DRX configuration and / or MG periodicity.
[0062] For example, if UE configured with a first MG configuration started the prohibit timer receives a second MG configuration, then UE cancels / stops the prohibit timer.
[0063] The UE may report multiple RMGOs, e.g. one RMGO for current MG configuration and a RMGO together with one or more suggested / preferred MG periodicities / time-offsets. For example, if current MG periodicity is Pl the UE may report RMGO1 but also report the 2-tuple (RMGO2, P2) with a suggested new MG periodicity and an associated RMGO. In some examples, the UE reports alternatively or additionally a preferred MG time-offset.
[0064] If the threshold as described above are configured by the network, it can provide the thresholds in a downlink (DL) RRC message. It can also be chosen by the UE based on implementation.
[0065] In additional or alternative examples, the UE can reevaluate and change upon the need the RMGO, when performance of a neighbor cell (for measuring which measurement gaps are used) changes, e.g., RMGO can be decreased when its performance degrades to below a threshold or increased when its performance increases to above a threshold. In one embodimentthe UAI-indicated RMGO is determined as the maximum RMGO for which the performance-related requirements can be fulfilled with an offset. In some examples the offset is zero meaning that the performance-related requirements can be fulfilled if ratio of cancelled MGOs does not exceed the UAI-indicated RMGO. In examples with non-zero offset, if performance-related requirement equals R, then if ratio of cancelled MGOs does not exceed the UAI-indicated RMGO then performance is not worse than R-offset. Th offset parameter may be part of MG configuration (RRC-configured) or be a parameter chosen by a UE implementation.
[0066] In additional or alternative embodiments, the UAI-reported RMGO is determined by UE under the assumption that cancelled MGO are approximately or close to uniformly distributed during X seconds. For example, if the time between two consecutive MGO is P and the cancelling ratio is R, e.g. R = 0, 0.2, .0.4, 0.6, then the UE assumes the time between two consecutive non-cancelled MGO does not exceed P / (1-R) + k * P, where k is a non-negative integer. Several alternatives for the formula “P / (1-R)” is possible e.g. floor(P / (l-R)), ceil(P / (l -R)) or rounding upwards of downwards to nearest multiple of P.
[0067] In some examples, RMGO is set depending on UE activity state (see Example 3 above) or UE power saving mode operation, e.g., a first RMGO is provided by the UE for a first DRX configuration, a second RMGO is provided for a second DRX configuration, etc. The UE can choose a lower RMGO for a longer DRX cycle (e.g., due to a bigger impact on RRM measurements of measurement gap cancellation when the measurement samples are already sparse) compared to that for no DRX or shorter DRX. The UE can choose a lower RMGO for a larger max(MGRP, DRX cycle length) and a higher RGGO for a smaller max(MGRP, DRX cycle length).
[0068] In additional or alternative embodiments, RMGO is determined based on UE-obtained UL traffic information e.g. UL traffic information obtained from application layer in UE. In further other embodiments the RMGO is alternatively or additionally determined based on obtained DL traffic information and / or DL and / or UL scheduled pattem / frequency / rate.
[0069] Embodiments associated with zero RMGO are described below.
[0070] In some embodiments, the UE can send RMGO including 0 to indicate a specific UE behavior or request. In some examples, the UE can send RMGO as 0 to cancel the previous RMGO, In additional or alternative examples, the UE can send RMGO as 0 to indicate no further need for measurement gap cancellation. In additional or alternative examples, the UE can send RMGO as 0 to indicate the UE ability to perform a specific UE operation (e.g., XR operation) without cancelling measurement gaps. In additional or alternative examples, the UE can send RMGO as 0 to indicate the UE ability to perform a specific UE operation (e.g., XR operation), while meeting the corresponding performance-related requirements for thisoperation, without explicit cancelling of specific measurement gaps by the network node. In additional or alternative examples, the UE can send RM GO as 0 to request a stop or suspension of an XR operation (e.g., due to poor radio conditions at the UE, UE performance degradation, power saving needs, etc.).
[0071] Embodiments associated with determining the measurement gaps associated with RM GO are described below.
[0072] In some embodiments, the UE can be configured with multiple measurement gap patterns, hence it may be not clear with which measurement gap pattern RMGO is associated with.
[0073] In additional or alternative embodiments, the UE provides RMGO together with the additional information indicative of the applicable measurement gap pattern. In some examples, UE can provide a first RMGO associated with a first measurement gap pattern and a second RMGO associated with a second measurement gap pattern.
[0074] In some examples, the additional information can include at least one frequency or frequency range to indicate the measurement gap pattern for which RMGO applies, e.g., the UE indicates FR1 if RMGO applies for the measurement gap pattern configured for FR1.
[0075] In additional or alternative examples, the UE can be configured with concurrent gap configurations with gap types of perUE, perFRl and perFR2. The UE can individually derive the RMGO per gap type and indicate which RMGO applies to which of the measurement gap types. For example, RMG01 can apply to gapUE while RMGO2 can apply to perFRl.
[0076] In additional or alternative examples, the additional information can include measurement gap pattern ID. The additional information can include a cell ID or cell group ID measured in the measurement gaps associated with the RMGO.
[0077] Embodiments associated with providing RMGO to indicate UE capability are described below.
[0078] In some embodiments, RMGO can be dynamically (re)defined and updated upon the need, depending on radio conditions, performance metric, UE speed, UE current preference, UE activity state, power saving state, etc.
[0079] In additional or alternative embodiments, RMGO is a static parameter reflecting UE capability to handle measurement gap reallocation. In this case, the UE can provide RMGO only once, e.g., in the beginning of the operation which may rely on the UE’s RMGO information such as in the beginning of the XR operation which may require cancelled measurement gaps.
[0080] Embodiments performed by a network node include reallocating time resources based on the RMGO received from the UE.
[0081] In some embodiments, a network node receiving the RMGO information from a UE reallocates the time resources, which were earlier allocated for UE measurement gaps, to some other UE operation, wherein the RMGO is determined interpreted by the network node, and acted upon inline with and based on the embodiments described for the UE. In one example, the resources are reallocated from UE measurement gaps to XR data (in DL and / or UL).
[0082] For example, if UE reports a decrease in RMGO the network aims to reduce RMGO cancelling for the UE by adapting scheduling and link adaption of the UE e.g. increasing the amount of assigned resources (e.g. increasing UE’s scheduling weight) and / or choosing a more reliable MCS selection when UE scheduled outside MGOs. In another example, if UE reports a new RMGO the network may alternatively or additionally trigger a re-configuration of the MG configuration, e.g. changing the MG periodicity and / or time-offset.
[0083] Operations of a UE 900 (implemented using the structure of FIG. 9) will now be discussed with reference to the flow charts of FIG. 6 according to some embodiments of inventive concepts. For example, modules may be stored in memory 910 of FIG. 9, and these modules may provide instructions so that when the instructions of a module are executed by respective UE processing circuitry 902, UE 900 performs respective operations of the flow chart.
[0084] FIG. 6 illustrates an example of operations performed by a UE to handle determining and sending a RMGO.
[0085] At block 610, processing circuitry 902 receives, via communication interface 912, configuration information.
[0086] At block 620, processing circuitry 902 transmits, via communication interface 912, an indication of a first recommended RMGO.
[0087] At block 630, processing circuitry 902 initiates a prohibit timer. In some embodiments, initiating the prohibit timer includes initiating the prohibit timer in response to transmitting the indication of the first recommended RMGO.
[0088] At block 640, processing circuitry 902 determines a second recommended RMGO. In some embodiments, the second recommended RMGO is an update to the first recommended RMGO.
[0089] In additional or alternative embodiments, determining the second recommended RMGO includes determining to set the second recommended RMGO to be zero based on determining at least one of: 1) to cancel a previous RMGO; 2) that there is no further need for measurement gap cancellation; 3) that the UE is capable of performing a specific operation without cancelling a measurement occasion gap; 4) the UE is capable of performing the specific operation while meeting a corresponding performance-related requirements for the specificoperation without explicit cancelling of the measurement occasion gap; and 5) to request a stop or suspension of an extended reality, XR operation.
[0090] In additional or alternative embodiments, determining the second recommended RM GO includes determining the second recommended RMGO based on at least one of: 1) a measurement of signal quality on a cell of the UE; 2) a measurement of signal strength on the cell of the UE; 3) a mobility of the UE; 4) a UE activity state; 5) a UE power saving mode; 6) uplink traffic information; 7) downlink traffic information; 8) radio conditions; 9) UE speed; and 10) UE current preference.
[0091] In additional or alternative embodiments, determining the recommended RMGO includes determining the second recommended RMGO based on the configuration information.
[0092] At block 650, processing circuitry 902 determines that the prohibit timer has expired or stopped. In some embodiments, determining that the prohibit timer has expired or stopped includes: receiving a measurement gap, MG, configuration and / or a discontinuous reception, DRX, configuration; and responsive to receiving the MG configuration and / or the DRX configuration, stopping the prohibit timer.
[0093] In additional or alternative embodiments, determining that the prohibit timer has expired or stopped includes: determining that a trigger condition has been met for transmitting other information to the network node; and responsive to determining that the trigger condition has been met for transmitting the other information, stopping the prohibit timer.
[0094] In additional or alternative embodiments, determining that the prohibit timer has expired or stopped includes determining that an amount of time has elapsed. In some examples, the configuration information includes an indication of the amount of time.
[0095] At block 660, processing circuitry 902 transmits, via communication interface 912, an indication of the recommended RMGO. In some embodiments, transmitting the indication of the second recommended RMGO comprises transmitting the indication of the second recommended RMGO to the network node subsequent to determining that the prohibit timer has expired or been stopped.
[0096] In additional or alternative embodiments, the second recommended RMGO is a recommended RMGO associated with a first type of measurement gap occasion. Determining the second recommended RMGO includes determining the recommended RMGO associated with the first type of measurement gap occasion and a recommended RMGO that is associated with a second type of measurement gap occasion that is different than the first type of measurement gap occasion. Transmitting the indication of the second recommended RMGO includes transmitting an indication of the recommended RMGO associated with the first type of measurement gap and the second recommended RMGO associated with the second type ofmeasurement gap. In some examples, the first type of measurement gap occasion and the second type of measurement gap occasion are different by being associated with at least one of: different measurement gap patterns; different frequencies; different frequency ranges different periodicities; different power states of the UE; and different purposes. In additional or alternative examples, the different purposes include at least one of: positioning; cell identification; measurement paging monitoring; system information block acquisition; on-demand system information request of a target cell in a target network; and uplink gap for transmit power management.
[0097] In additional or alternative embodiments, transmitting the indication of the recommended RMGO includes transmitting the indication of the recommended RMGO as part of UE assistance information, UAL
[0098] Various operations from the flow chart of FIG. 6 may be optional with respect to some embodiments of UEs and related methods.
[0099] Operations of a network node 1000 (implemented using the structure of FIG. 10) will now be discussed with reference to the flow charts of FIG. 7 according to some embodiments of inventive concepts. For example, modules may be stored in memory 1004 of FIG. 10, and these modules may provide instructions so that when the instructions of a module are executed by respective network node processing circuitry 1002, network node 1000 performs respective operations of the flow chart.
[0100] FIG. 7 illustrates an example of operations performed by a network node for having a UE handle determining and providing a RMGO.
[0101] At block 710, processing circuitry 1002 transmits, via communication interface 1006, configuration information. In some embodiments, the configuration information includes an indication of an amount of time to wait between transmitting updates to the recommended RMGOs.
[0102] At block 720, processing circuitry 1002 receives, via communication interface 1006, an indication of a first recommended RMGO.
[0103] At block 730, processing circuitry 1002 receives, via communication interface 1006, an indication of a second recommended RMGO. In some embodiments, the second recommended RMGO is an update to the first recommended RMGO. In additional or alternative embodiments, receiving the indication of the second recommended RMGO includes receiving the indication of the second recommended RMGO as part of UE assistance information, UAL
[0104] In some embodiments, receiving the indication of the second recommended RMGO includes receiving an indication of a first recommended RMGO that is associated with a first type of measurement gap occasion and a second recommended RMGO that is associated with asecond type of measurement gap occasion that is different than the first type of measurement gap occasion. In some examples, the first type of measurement gap occasion and the second type of measurement gap occasion are different by being associated with at least one of: different measurement gap patterns; different frequencies; different frequency ranges; different periodicities; different power states of the UE; and different purposes. In additional or alternative examples, the different purposes includes at least one of: positioning; cell identification; measurement paging monitoring; system information block acquisition; on-demand system information request of a target cell in a target network; and uplink gap for transmit power management.
[0105] At block 740, processing circuitry 1002 reallocates resources associated with the UE based on the indication of the recommended RM GO. In some embodiments, receiving the indication of the second recommended RMGO includes receiving an indication that the second recommended RMGO is zero. Reallocating the resources includes determining, based on the second recommended RMGO being zero, at least one of: to cancel a previous RMGO; that there is no further need for measurement gap cancellation; that the UE is capable of performing a specific operation without cancelling a measurement occasion gap; the UE is capable of performing the specific operation while meeting a corresponding performance-related requirements for the specific operation without explicit cancelling of the measurement occasion gap; and to request a stop or suspension of an extended reality, XR operation.
[0106] In additional or alternative embodiments, reallocating the resources includes adapting scheduling and / or link adaptation of the UE based on the indication of the second recommended RMGO.
[0107] In additional or alternative embodiments, reallocating the resources includes transmitting measurement gap re-configuration information to the UE, the measurement gap reconfiguration information based on the indication of the second recommended RMGO.
[0108] Various operations from the flow chart of FIG. 7 may be optional with respect to some embodiments of network nodes and related methods.
[0109] FIG. 8 shows an example of a communication system 800 in accordance with some embodiments.
[0110] In the example, the communication system 800 includes a telecommunications network 802 that includes an access network 804, such as a radio access network (RAN), and a core network 806, which includes one or more core network nodes 808. The access network 804 includes one or more access network nodes or base stations of various types, access network nodes 810A and 810B are depicted (which may be collectively referred to as network nodes 810), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPPaccess points (APs). Some embodiments of the access network 804 may include more than one access network technology. The network nodes 810 of access network 804 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 812A, 812B, 812C, and 812D (one or more of which may be generally referred to as UEs 812) to the core network 806 over one or more wireless connections.
[0111] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion 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 telecommunications network 802 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 802 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 network nodes to implement one or more functionalities of any network node in the telecommunications network 802, including one or more access network nodes 810 and / or core network nodes 808.
[0112] 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). An ORAN 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 network 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.
[0113] The network nodes 810 facilitate direct or indirect connection of one or more UEs 812 to the core network 806 over one or more wireless connections. 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 800 may includeany 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 800 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.
[0114] The UEs 812 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 810 and other communication devices. Similarly, the network nodes 808, 810 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 802) with the UEs 812 and / or with other network nodes or equipment in the telecommunications network 802 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 802. More specifically, UEs 812 may send messages, data, and / or other signals to network nodes 808, 810 or other elements of the telecommunications network 802 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 808, 810 may send messages, data, and other signals to UEs 8122, other network nodes 808, 810, and other devices in telecommunications network 802 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 812 by transmitting the message to an access network node 810 that will then transmit the message to the intended UE 812.Similarly, a core network node 108 may receive a particular message from a UE 812 by receiving the message from an access network node 810 that itself received the message from the UE 812.
[0115] In the depicted example, the core network 806 connects elements of the access network 804 (e.g., one or more of the network nodes 810) to one or more host computing systems, such as host 816. 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 806 includes one or more core network nodes (e.g., core network node 808) of various types, one or more of which may be generally referred to as network nodes 808. Network nodes 808 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 808. Example core network nodes providefunctions 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).
[0116] The host 816 may be under the ownership or control of a service provider other than an operator or provider of the access network 804 and / or the telecommunications network 802. The host 816 may be operated by the service provider or on behalf of the service provider. The host 816 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.
[0117] As a whole, the communication system 800 of FIG. 8 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 800 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 (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 800 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 800 supporting different standards, protocols, or rule sets.
[0118] As one example, in certain embodiments, access network 804 may contain some access network nodes 810 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 810 support (or the same access network nodes 810 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 802 may support multiple generations of relatedcommunication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 104 and / or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.
[0119] Telecommunications network 802 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 802. For example, the telecommunications network 802 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.
[0120] In some examples, one or more of the UEs 812 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 804 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 804.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).
[0121] In the example, the hub 814 communicates with the access network 804 to facilitate indirect communication between one or more UEs (e.g., UE 812C and / or 812D) and network nodes (e.g., network node 810B). In some examples, the hub 814 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 814 may be a broadband router enabling access to the core network 806 for the UEs. As another example, the hub 814 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 810, or by executable code, script, process, or other instructions in the hub 814.
[0122] As another example, the hub 814 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, the hub 814 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 814 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 814 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 814 acts as a proxyserver or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.
[0123] The hub 814 may have a constant / persistent or intermittent connection to the network node 810B. The hub 814 may also allow for a different communication scheme and / or schedule between the hub 814 and UEs (e.g., UE 812C and / or 812D), and between the hub 814 and the core network 806. In other examples, the hub 814 is connected to the core network 806 and / or one or more UEs via a wired connection. Moreover, the hub 814 may be configured to connect to an M2M service provider over the access network 804 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 810 while still connected via the hub 814 via a wired or wireless connection. In some embodiments, the hub 814 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 810B. In other embodiments, the hub 814 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 810B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.
[0124] FIG. 9 shows a wireless device 900, which may be configured to operate in communication system 800 of FIG. 8 or in communication system QQ200 of FIG. QQ20. The wireless device 900 may be alternatively referred to as a UE 900, like a UE 812 within the context of communication system 800, or as a station (STA) 900 or as a non-access-point station (non-AP STA) 900, like a STA QQ212 within the context of the communication system QQ200, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device 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, and wireless terminal. Other examples include any type of 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.
[0125] A wireless device 900 may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, wireless device 900 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 900 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, wireless device 900 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).
[0126] In particular embodiments, wireless device 900 includes processing circuitry 902 that is operatively coupled via a bus 904 to an input / output interface 906, a power source 908, a memory 910, a communication interface 912, and / or any other component, or any combination thereof. Certain embodiments of wireless device 900 may include all or a subset of the components shown in FIG. 9. The level of integration between the components may vary from one embodiment of wireless device 900 to another. In general, in a particular embodiment of wireless device 900, processing circuitry 902, input / output interface 906, power source 908, memory 910, and communication interface 912 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 900. Further, certain embodiments of wireless devices 900 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0127] The processing circuitry 902 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 910. The processing circuitry 902 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 902 may include multiple central processing units (CPUs).
[0128] In the example, the input / output interface 906 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 wireless device 900. 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, asensor, 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.
[0129] In some embodiments, the power source 908 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 to supply power to circuitry or to charge an associated battery. The power source 908 may further include power circuitry for delivering power from the power source 908 itself, and / or an external power source, to the various parts of wireless device 900 via input circuitry or an interface such as an electrical power cable. Power source 908 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 900 to which power is supplied.
[0130] The memory 910 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 readonly memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 910 includes one or more programs 914, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 916. The memory 910 may store, for use by wireless device 900, any of a variety of various operating systems or combinations of operating systems.
[0131] The memory 910 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 910 may allow wireless device 900 to access instructions, programs and thelike, stored on transitory or non-transitory memory media, 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 910, which may be or comprise a device-readable storage medium.
[0132] The processing circuitry 902 may be configured to communicate with an access network or other network via or using the communication interface 912. The communication interface 912 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 922. The communication interface 912 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 wireless device or a network node in an access network). Each transceiver may include a transmitter 918 and / or a receiver 920 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 918 and receiver 920 may be coupled to one or more antennas (e.g., antenna 922) and may share circuit components, software or firmware, or alternatively be implemented separately.
[0133] In the illustrated embodiment, communication functions of the communication interface 912 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), 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 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 / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
[0134] In particular embodiments, wireless device 900 may provide an output of data captured via a sensor, through its communication interface 912, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 900 can be communicated through a wireless connection to a network node via another wireless device 900. In particular embodiments, such 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).
[0135] As another example, wireless device 900 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, wireless device 900 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.
[0136] Wireless device 900, 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, 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 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. In particular embodiments, wireless device 900 represents an loT device that 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 example embodiment of wireless device 900 shown in FIG. 9.
[0137] As yet another specific example, in an loT scenario, wireless device 900 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 wireless device and / or a network node. Wireless device 900 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, wireless device 900 may implement the 3GPP NB-IoT standard. In other scenarios, wireless device 900 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.
[0138] In practice, any number of wireless devices 900 may be used together with respect to a single use case. For example, a first wireless device 900 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a secondwireless device 900 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 900 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 wireless device 900 can also include more than one of the functionalities described above. For example, wireless device 900 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
[0139] FIG. 10 shows a network node 1000 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 telecommunications network. In accordance with respective embodiments, network node 1000 may be configured to operate in communication system 800 of FIG. 8, like network nodes 808 or 810, or in communication system QQ200 of FIG. QQ2, like an AP QQ210 or a station QQ212. 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) andNRNodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).
[0140] Network nodes 1000 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. Network node 1000 may be a relay node or a relay donor node controlling a relay. Network nodes 1000 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 O-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).
[0141] Other examples of network nodes 1000 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).
[0142] In particular embodiments, network node 1000 includes a processing circuitry 1002, a memory 1004, a communication interface 1006, and a power source 1008. In general, in aparticular embodiment of network node 1000, processing circuitry 1002, memory 1004, communication interface 1006, and power source 1008 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 1000.
[0143] The network node 1000 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 1000 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities 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 1000 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 1004 or portions of memory 1004 for different RATs) and some components may be reused (e.g., a same antenna 1010 may be shared by different RATs). The network node 1000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1000, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), 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 1000.
[0144] The processing circuitry 1002 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 components, such as the memory 1004, to provide network node 1000 functionality.
[0145] In some embodiments, the processing circuitry 1002 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1002 includes one or more of radio frequency (RF) transceiver circuitry 1012 and baseband processing circuitry 1014. In some embodiments, the RF transceiver circuitry 1012 and the baseband processing circuitry 1014 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 1012 and baseband processing circuitry 1014 may be on the same chip or set of chips, boards, or units.
[0146] The memory 1004 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotelymounted 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 computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1002. The memory 1004 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 1002 and utilized by the network node 1000. The memory 1004 may be used to store any calculations made by the processing circuitry 1002 and / or any data received via the communication interface 1006. In some embodiments, the processing circuitry 1002 and memory 1004 is integrated.
[0147] The communication interface 1006 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 1006 comprises port(s) / terminal(s) 1016 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 900 may be capable of wireless communication and communication interface 1006 may also include radio front-end circuitry 1018 that may be coupled to, or in certain embodiments a part of, an antenna 1010. Particular embodiments of radio front-end circuitry 1018 include filter(s) 1020 and amplifier(s) 1022. The radio front-end circuitry 1018 may be connected to an antenna 1010 and processing circuitry 1002. The radio front-end circuitry may be configured to condition signals communicated between antenna 1010 and processing circuitry 1002. The radio front-end circuitry 1018 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 1018 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 1020 and / or amplifiers 1022. The radio signal(s) may then be transmitted via the antenna 1010. Similarly, when receiving data, the antenna 1010 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1018. The digital data may be passed to the processing circuitry 1002. In other embodiments, the communication interface may comprise different components and / or different combinations of components.
[0148] In certain alternative embodiments, network node 1000 may be capable of wireless communication but does not include separate radio front-end circuitry 1018, instead, the processing circuitry 1002 includes radio front-end circuitry and is connected to the antenna 1010. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1012 is part of the communication interface 1006. In still other embodiments, the communication interface1006 includes one or more ports or terminals 1016, the radio front-end circuitry 1018, and the RF transceiver circuitry 1012, as part of a radio unit (not shown), and the communication interface 1006 communicates with the baseband processing circuitry 1014, which is part of a digital unit (not shown).
[0149] The antenna 1010 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1010 may be coupled to the radio front-end circuitry 1018 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 1010 is separate from the network node 1000 and connectable to the network node 1000 through one or more interfaces or ports.
[0150] The antenna 1010, communication interface 1006, and / or the processing circuitry 1002 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 1000. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 1010, the communication interface 1006, and / or the processing circuitry 1002 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 1000. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.
[0151] The power source 1008 provides power to the various components of network node 1000 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1008 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1000 with power for performing the functionality described herein. For example, the network node 1000 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 1008. As a further example, the power source 1008 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 if the external power source fails.
[0152] Embodiments of the network node 1000 may include additional components beyond those shown in FIG. 10 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 1000 may include user interface equipment to allow input of information into the network node 1000 and to allowoutput of information from the network node 1000. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1000.
[0153] 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.
[0154] 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.
Claims
CLAIMSWhat is claimed is:
1. A method of operating a user equipment, UE, in a communications network, the method comprising:determining (640) a recommended ratio of measurement gap occasions, RM GO; and transmitting (660) an indication of the recommended RMGO to a network node operating in the communications network.
2. The method of Claim 1, wherein determining the recommended RMGO comprises determining the recommended RMGO based on a UE current preference.
3. The method of any of Claims 1-2, wherein determining the recommended RMGO comprises determining the recommended RMGO based on at least one of:a measurement of signal quality on a cell of the UE;a measurement of signal strength on the cell of the UE;a mobility of the UE;a UE activity state;a UE power saving mode;uplink traffic information;downlink traffic information;radio conditions; andUE speed.
4. The method of any of Claims 1-3, further comprising:determining (650) that a prohibit timer has expired or stopped,wherein transmitting the indication of the recommended RMGO comprises transmitting the indication of the recommended RMGO to the network node subsequent to determining that the prohibit timer has expired or been stopped.
5. The method of Claim 4, wherein the indication of the recommended RMGO is a second indication of a second recommended RMGO,the method further comprising:initiating (630) the prohibit timer in response to transmitting a first indication of a first recommended RMGO.
6. The method of any of Claims 4-5, wherein determining that the prohibit timer has expired or stopped comprises:receiving a measurement gap, MG, configuration and / or a discontinuous reception, DRX, configuration; andresponsive to receiving the MG configuration and / or the DRX configuration, stopping the prohibit timer.
7. The method of any of Claims 4-6, wherein determining that the prohibit timer has expired or stopped comprises:determining that a trigger condition has been met for transmitting other information to the network node; andresponsive to determining that the trigger condition has been met for transmitting the other information, stopping the prohibit timer.
8. The method of any of Claims 4-7, wherein determining that the prohibit timer has expired or stopped comprises determining that an amount of time has elapsed.
9. The method of Claim 8, further comprising:receiving (610) configuration information from the network node, the configuration information including an indication of the amount of time.
10. The method of any of Claims 1-9, further comprising:receiving (610) configuration information from the network node,wherein determining the recommended RMGO comprises determining the recommended RMGO based on the configuration information.
11. The method of any of Claims 1-10, wherein the recommended RMGO is a first recommended RMGO associated with a first type of measurement gap occasion,wherein determining the recommended RMGO comprises determining the first recommended RMGO and a second recommended RMGO that is associated with a second type of measurement gap occasion that is different than the first type of measurement gap occasion, andwherein transmitting the indication of the recommended RMGO comprises transmitting an indication of the first recommended RMGO and the second recommended RMGO.
12. The method of Claim 11, wherein the first type of measurement gap occasion and the second type of measurement gap occasion are different by being associated with at least one of:different measurement gap patterns;different frequencies;different frequency ranges;different periodicities;different power states of the UE; anddifferent purposes.
13. The method of any of Claims 1-13, wherein transmitting the indication of the recommended RMGO comprises transmitting the indication of the recommended RMGO as part of UE assistance information, UAI.
14. The method of any of Claims 1-14, wherein the indication of the recommended RMGO is a second indication of a second recommended RMGO,the method further comprising:prior to determining the second recommended RMGO, transmitting (620) an indication of a first recommended RMGO to the network node,wherein the second recommended RMGO is an update to the first recommended RMGO.
15. The method of any of Claims 1-14, wherein determining the recommended RMGO comprises determining to set the recommended RMGO to be zero based on determining at least one of:to cancel a previous RMGO;that there is no further need for measurement gap cancellation;that the UE is capable of performing a specific operation without cancelling a measurement occasion gap;the UE is capable of performing the specific operation while meeting a corresponding performance-related requirements for the specific operation without explicit cancelling of the measurement occasion gap; andto request a stop or suspension of an extended reality, XR operation.
16. A method of operating a network node in a communications network, the method comprising:receiving (730) an indication of a recommended ratio of measurement gap occasions, RM GO, from a user equipment, UE, operating in the communications network; and reallocating (750) resources associated with the UE based on the indication of the recommended RMGO.
17. The method of Claim 16, wherein receiving the indication of the recommended RMGO comprises receiving an indication that the recommended RMGO is zero,wherein reallocating the resources comprises determining, based on the recommended RMGO being zero, at least one of:to cancel a previous RMGO;that there is no further need for measurement gap cancellation;that the UE is capable of performing a specific operation without cancelling a measurement occasion gap;the UE is capable of performing the specific operation while meeting a corresponding performance-related requirements for the specific operation without explicit cancelling of the measurement occasion gap; andto request a stop or suspension of an extended reality, XR operation.
18. The method of Claim 16, wherein reallocating the resources comprises adapting scheduling and / or link adaptation of the UE based on the indication of the recommended RMGO.
19. The method of Claim 16, wherein reallocating the resources comprises transmitting measurement gap re-configuration information to the UE, the measurement gap re-configuration information based on the indication of the recommended RMGO.
20. The method of any of Claims 16-19, further comprising:transmitting (710) configuration information to the UE, the configuration information including an indication of an amount of time to wait between transmitting updates to the recommended RMGO.
21. The method of any of Claims 16-20, wherein the recommended RMGO is a first recommended RMGO associated with a first type of measurement gap occasion,wherein receiving the indication of the recommended RMGO comprises receiving an indication of the first recommended RMGO and a second recommended RMGO that is associated with a second type of measurement gap occasion that is different than the first type of measurement gap occasion.
22. The method of Claim 21, wherein the first type of measurement gap occasion and the second type of measurement gap occasion are different by being associated with at least one of:different measurement gap patterns;different frequencies;different frequency rangesdifferent periodicities;different power states of the UE; anddifferent purposes.
23. The method of Claim 22, wherein the different purposes comprise at least one of:positioning;cell identification;measurement paging monitoring;system information block acquisition; andon-demand system information request of a target cell in a target network.
24. The method of any of Claims 16-23, wherein receiving the indication of the recommended RMGO comprises receiving the indication of the recommended RMGO as part of UE assistance information, UAL25. The method of any of Claims 16-24, wherein the indication of the recommended RMGO is a second indication of a second recommended RMGO,the method further comprising:prior to receiving the indication of the second recommended RMGO, receiving (720) an indication of a first recommended RMGO from the UE,wherein the second recommended RMGO is an update to the first recommended RMGO.
26. A user equipment, UE, (900) adapted to perform operations comprising:determining (640) a recommended ratio of measurement gap occasions, RM GO; and transmitting (660) an indication of the recommended RMGO to a network node operating in the communications network.
27. The UE of Claim 26, further adapted to perform any of the operations of Claims 2-15.
28. A computer program comprising program code to be executed by processing circuitry (902) of a user equipment, UE, (900), whereby execution of the program code causes the UE to perform operations comprising:determining (640) a recommended ratio of measurement gap occasions, RMGO; and transmitting (660) an indication of the recommended RMGO to a network node operating in the communications network.
29. The computer program of Claim 34, the operations further comprising any of the operations of Claims 2-15.
30. A computer program product comprising a non-transitory storage medium (910) including program code to be executed by processing circuitry (902) of a user equipment, UE, (900), whereby execution of the program code causes the UE to perform operations comprising:determining (640) a recommended ratio of measurement gap occasions, RMGO; and transmitting (660) an indication of the recommended RMGO to a network node operating in the communications network.
31. The computer program product of Claim 30, the operations further comprising any of the operations of Claims 2-15.
32. A network node (1000) adapted to perform operations comprising:receiving (730) an indication of a recommended ratio of measurement gap occasions, RMGO, from a user equipment, UE, operating in the communications network; and reallocating (750) resources associated with the UE based on the indication of the recommended RMGO.
33. The network node of Claim 32, further adapted to perform any of the operations of Claims34. A computer program comprising program code to be executed by processing circuitry (1002) of a network node (1000), whereby execution of the program code causes the network node to perform operations comprising:receiving (730) an indication of a recommended ratio of measurement gap occasions, RM GO, from a user equipment, UE, operating in the communications network; and reallocating (750) resources associated with the UE based on the indication of the recommended RMGO.
35. The computer program of Claim 34, the operations further comprising any of the operations of Claims 17-25.
36. A computer program product comprising a non-transitory storage medium (1004) including program code to be executed by processing circuitry (1002) of a network node (1000), whereby execution of the program code causes the network node to perform operations comprising:receiving (730) an indication of a recommended ratio of measurement gap occasions, RMGO, from a user equipment, UE, operating in the communications network; and reallocating (750) resources associated with the UE based on the indication of the recommended RMGO.
37. The computer program product of Claim 36, the operations further comprising any of the operations of Claims 17-25.
