Mitigating impact of positioning measurements on RLF processes

Abstract

Example embodiments of the present disclosure relate to devices, methods, and computer-readable storage media for mitigating the impact of positioning measurements on a radio link failure (RLF) process. In one method, a device performs an RLF procedure and performs a positioning measurement procedure. At least one of the RLF process or the positioning measurement process is adjusted to mitigate conflicts between the processes.

Description

Technical Field

[0001] Various example embodiments of the present disclosure relate generally to the field of telecommunications, and in particular to apparatus, methods, and computer-readable storage media for mitigating the impact of positioning measurements on a radio link failure (RLF) procedure. Background Art

[0002] The Internet of Things (IoT) over non-terrestrial networks (NTNs) is supported in 3rd Generation Partnership Project (3GPP) Release 18 (Rel-18). Among the enhancements related to mobility and performance in Rel-18, it is assumed that simultaneous operation of both Global Navigation Satellite System (GNSS) and NTN narrowband (NB)-IoT / enhanced machine type communications (eMTC) may not be possible.

[0003] For GNSS measurements, an evolved NodeB (eNB) may occasionally schedule GNSS measurement gaps so that a user equipment (UE) can obtain a new GNSS position fix before the validity of the current GNSS position expires. However, the eNB may not be aware that the UE is experiencing link issues because the UE may not report those link issues unless specifically configured by the eNB. Consequently, it may happen that the UE has scheduled GNSS measurement gaps that may coincide with an RLF procedure. Summary of the Invention

[0004] In a first aspect of the present disclosure, a device is provided. The device includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the device to at least: perform a radio link failure procedure; and perform a positioning measurement procedure, wherein at least one of the radio link failure procedure or the positioning measurement procedure is adjusted to mitigate a conflict between the radio link failure procedure and the positioning measurement procedure.

[0005] In a second aspect of the present disclosure, a device is provided. The device includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the device to at least: receive a first radio link monitoring report for an early out-of-sync event or a second radio link monitoring report for an early synchronization event from another device, the early out-of-sync event and the early synchronization event being associated with a radio link failure procedure performed by the other device; and send a configuration of a shift time for a measurement gap used for a positioning measurement procedure to be performed by the other device to the other device, to mitigate a conflict between the radio link failure procedure and the positioning measurement procedure.

[0006] In a third aspect of the present disclosure, a method is provided, comprising: performing a radio link failure procedure; and performing a positioning measurement procedure, wherein at least one of the radio link failure procedure or the positioning measurement procedure is adjusted to mitigate a conflict between the radio link failure procedure and the positioning measurement procedure.

[0007] In a fourth aspect of the present disclosure, a method is provided. The method includes: receiving, at a device, a first radio link monitoring report for an early out-of-sync event or a second radio link monitoring report for an early synchronization event from another device, the early out-of-sync event and the early synchronization event being associated with a radio link failure procedure performed by the other device; and sending, to the other device, a configuration of a shift time for a measurement gap used for a positioning measurement procedure to be performed by the other device, to mitigate a conflict between the radio link failure procedure and the positioning measurement procedure.

[0008] In a fifth aspect of the present disclosure, a device is provided. The device includes: means for performing a radio link failure procedure; and means for performing a positioning measurement procedure, wherein at least one of the radio link failure procedure or the positioning measurement procedure is adjusted to mitigate a conflict between the radio link failure procedure and the positioning measurement procedure.

[0009] In a sixth aspect of the present disclosure, a device is provided. The device includes: a component for receiving a first radio link monitoring report for an early out-of-sync event or a second radio link monitoring report for an early synchronization event from another device, the early out-of-sync event and the early synchronization event being associated with a radio link failure procedure performed by the other device; and a component for sending a configuration of a shift time for a measurement gap for a positioning measurement procedure to be performed by the other device to the other device to mitigate a conflict between the radio link failure procedure and the positioning measurement procedure.

[0010] In a seventh aspect of the present disclosure, a computer-readable medium is provided, wherein the computer-readable medium includes instructions stored thereon for causing a device to at least execute the method according to the third aspect or the fourth aspect.

[0011] It should be understood that the invention summary section is neither intended to identify the key or essential features of the embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become readily apparent through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Some example embodiments will now be described with reference to the accompanying drawings, in which:

[0013] Figure 1An example communication environment is shown in which example embodiments of the present disclosure may be implemented;

[0014] Figure 2A A diagram illustrating an example RLF process according to some example embodiments;

[0015] Figure 2B A diagram illustrating an example scenario of performing GNSS measurements during an RLF procedure according to some example embodiments of the present disclosure;

[0016] Figure 3 A flowchart illustrating a method according to some example embodiments of the present disclosure;

[0017] Figure 4 A flowchart illustrating an example process for adjusting an RLF process according to some example embodiments of the present disclosure is shown;

[0018] Figure 5 A flowchart illustrating an example process for adjusting a measurement gap according to some example embodiments of the present disclosure is shown;

[0019] Figure 6 A flowchart illustrating an example process for adjusting a measurement gap according to some other example embodiments of the present disclosure is shown;

[0020] Figure 7 shows a simplified block diagram of a device suitable for implementing an example embodiment of the present disclosure; and

[0021] Figure 8 A block diagram of an example computer-readable medium is shown, according to some example embodiments of the present disclosure.

[0022] Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. DETAILED DESCRIPTION

[0023] The principles of the present disclosure will now be described with reference to some example embodiments. It should be understood that these embodiments are described only for illustrative purposes and to assist those skilled in the art in understanding and implementing the present disclosure, without implying any limitation on the scope of the present disclosure. The embodiments described herein can be implemented in various ways except for the manner described below.

[0024] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0025] References in this disclosure to "one embodiment," "an embodiment," "an example embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment will necessarily include the particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. In addition, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, it should be understood that it is within the knowledge of those skilled in the art to implement such feature, structure, or characteristic in conjunction with other embodiments, whether or not explicitly described.

[0026] It should be understood that although the terms "first" and "second" and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element, without departing from the scope of the example embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed items.

[0027] As used herein, “at least one of: ” and “at least one of ” and similar expressions mean at least any one of the elements, or at least any two or more of the elements, or at least all of the elements, where the list of two or more elements is linked by “and” or “or”.

[0028] As used herein, unless explicitly stated otherwise, performing a step "in response to A" does not indicate that the step is performed immediately after "A" occurs and may include one or more intermediate steps.

[0029] The terms used herein are for the purpose of describing particular embodiments only and are not intended to be limiting of the example embodiments. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that when used herein, the terms "comprises," "comprising," "has," "having," "includes," and / or "including" specify the presence of stated features, elements, and / or components, etc., but do not preclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0030] As used in this application, the term "circuitry" may refer to one or more or all of the following:

[0031] (a) hardware circuit implementations only (such as implementations in analog and / or digital circuitry only), and

[0032] (b) a combination of hardware circuitry and software such as (if applicable):

[0033] (i) a combination of analog and / or digital hardware circuitry and software / firmware, and

[0034] (ii) any portion of a hardware processor (including a digital signal processor), software, and memory with software that work together to enable a device (such as a mobile phone or server) to perform various functions, and

[0035] (c) Hardware circuits and / or processors, such as a microprocessor or portion of a microprocessor, that require software (e.g., firmware) to operate, but in which case the software may not be present when not required for operation.

[0036] This definition of circuitry applies to all uses of the term in this application, including in any claims. As another example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. For example, and where applicable to a particular claim element, the term circuitry also covers a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0037] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), Advanced LTE (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. In addition, communication between terminal devices and network devices in the communication network may be performed according to any suitable generation of communication protocols, including but not limited to first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) communication protocols and / or any other protocols currently known or developed in the future. The embodiments of the present disclosure may be applied to various communication systems. In view of the rapid development in communications, there will certainly be future types of communication technologies and systems that can be used to embody the present disclosure. It should not be considered that the scope of the present disclosure is limited to the aforementioned systems.

[0038] As used herein, the term "network device" refers to a node in a communication network via which a terminal device accesses the network and receives services from the network. Depending on the terminology and technology applied, a network device may refer to a base station (BS) or an access point (AP), such as a Node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a NR NB (also known as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a repeater, an integrated access and backhaul (IAB) node, a low-power node (such as a femto node, a micro node), a non-terrestrial network (NTN) or an ungrounded network device (such as a satellite network device, a low earth orbit (LEO) satellite and a geostationary earth orbit (GEO) satellite), an aircraft network device, etc. In some example embodiments, a radio access network (RAN) split architecture includes a centralized unit (CU) and a distributed unit (DU) at an IAB donor node. The IAB node includes a mobile terminal (IAB-MT) portion that behaves like a UE to a parent node, and the DU portion of the IAB node behaves like a base station to a next-hop IAB node.

[0039] The term "terminal device" refers to any end device that can perform wireless communication. As an example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS) or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smart phones, voice over IP (VoIP) phones, wireless local loop phones, tablet computers, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), game terminal devices, music storage and playback devices, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronic devices, devices operating on commercial and / or industrial wireless networks, etc. The terminal device may also correspond to the mobile terminal (MT) part of an IAB node (eg, a relay node).In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" may be used interchangeably.

[0040] As used herein, the terms "resource," "transmission resource," "resource block," "physical resource block" (PRB), "uplink resource," or "downlink resource" may refer to any resource used to perform communication (e.g., communication between a terminal device and a network device), such as a resource in the time domain, a resource in the frequency domain, a resource in the space domain, a resource in the code domain, or any other resource that enables communication. Hereinafter, unless explicitly stated otherwise, resources in both the frequency domain and the time domain will be used as examples of transmission resources to describe some example embodiments of the present disclosure. It should be noted that the example embodiments of the present disclosure are also applicable to other resources in other domains.

[0041] Radio link monitoring (RLM) may require radio link related measurements, which can be used to estimate whether the UE can reliably receive and decode the physical downlink control channel (PDCCH). In RLM, the UE can detect physical layer problems in radio resource control (RRC)_CONNECTED mode. For example, after receiving a predetermined or network-configured number (e.g., N310) of consecutive out-of-synchronization (or "out-of-sync") (OoS) indications for the source primary cell (PCell) from the lower layer, the UE can start a timer, such as T310. For recovery from physical layer problems, the UE can detect an in-synchronization (or "in-sync") (IS) indication for the PCell. After receiving a predetermined or network-configured number (e.g., N311) of consecutive "in-sync" indications for the PCell from the lower layer while the timer (such as T310) is running, the UE can stop the timer. In this case, the UE can maintain the RRC connection without explicit signaling, that is, the UE can maintain the entire radio resource configuration. Periods of time during which Layer 1 does not report "In Sync" or "Out of Sync" may not affect the evaluation of the number of consecutive "In Sync" or "Out of Sync" indications.

[0042] Based on the Release 17 (Rel-17) specifications, user equipment (UE) can utilize GNSS operation to pre-compensate any uplink transmissions toward satellites to ensure time and frequency alignment. As described above, 3GPP Rel-18 supports IoT over NTN. However, Rel-18 enhancements related to mobility and performance assume that simultaneous operation of both GNSS and NTN NB-IoT / eMTC may not be possible. The eNB may therefore schedule "GNSS measurement gaps" during which the UE can utilize GNSS to obtain a new position fix, but the UE may not be able to operate NB-IoT / eMTC during these gaps.

[0043] There may be situations where the UE has scheduled GNSS measurement gaps that coincide with a Radio Link Failure (RLF) procedure. For example, if the UE has determined the N310 Out-of-Service (OoS) count, the UE may start the T310 timer. Shortly after starting T310, the UE may perform GNSS measurements and, as a result, may not detect an IS indication and may declare RLF. This is problematic because it will trigger an RRC connection re-establishment procedure, which may render the UE unavailable for further immediate communications with the eNB. In some cases, if the UE were not performing GNSS measurements, the UE may have already recovered from the RLF and, therefore, may have avoided the RLF procedure and the RRC connection re-establishment procedure.

[0044] Always configuring a longer T310 (eg, longer than the UE's GNSS measurements) may not be a useful option, since at any other point during the connection it may be desirable to detect radio link problems quickly.

[0045] The example embodiments of the present disclosure propose a solution for handling a situation where an RLF process is interrupted by a GNSS measurement. With the solution, at least one of an RLF process or a positioning measurement process (such as a GNSS measurement process) performed by a device (such as a UE) is adjusted to mitigate the conflict between the two processes. In the context of the present disclosure, the RLF process and the positioning measurement process may also be referred to as an RLF process and a positioning measurement process, respectively. In some example embodiments, if the RLF process and the GNSS measurement (e.g., for NTN) may conflict, some new UE behaviors may be defined. For example, if the T310 timer may conflict with a GNSS measurement gap, the UE may extend or suspend the T310 timer. Detailed behaviors may be discussed in the following paragraphs.

[0046] In this way, it is possible to prevent the UE from declaring a false or erroneous RLF during GNSS measurements due to a failure in IS evaluation during GNSS measurements. Such a declaration may result in a subsequent RRC connection re-establishment, which may result in greater power consumption and signaling overhead. The solution according to the exemplary embodiments of the present disclosure can save UE energy and minimize signaling, which is more efficient.

[0047] Figure 1 An example communication environment 100 is shown in which example embodiments of the present disclosure may be implemented. In the communication environment 100, a plurality of communication devices including a first device 110 and a second device 120 may communicate with each other.

[0048] Hereinafter, for the purpose of illustration, some example embodiments are described in which the first device 110 operates as a terminal device (such as a UE) and the second device 120 operates as a network device (such as a gNB). However, in some example embodiments, the operations described in conjunction with the terminal device may be implemented at a network device or other device, and the operations described in conjunction with the network device may be implemented at a terminal device or other device.

[0049] In some example embodiments, if the first device 110 is a terminal device and the second device 120 is a network device, the link from the second device 120 to the first device 110 is referred to as a downlink (DL), and the link from the first device 110 to the second device 120 is referred to as an uplink (UL). In the DL, the second device 110 is a transmitting (TX) device (or transmitter), and the first device 120 is a receiving (RX) device (or receiver). In the UL, the first device 110 is a TX device (or transmitter), and the second device 120 is an RX device (or receiver). In some example embodiments, both the first device 110 and the second device 120 may be terminal devices that can communicate with each other in a sidelink (SL).

[0050] Communications in the communication environment 100 may be implemented according to any suitable communication protocol, including, but not limited to, first generation (1G), second generation (2G), third generation (3G), fourth generation (4G), fifth generation (5G), sixth generation (6G), or similar cellular communication protocols, wireless local area network communication protocols (such as Institute of Electrical and Electronics Engineers (IEEE) 802.11), and / or any other protocol currently known or developed in the future. Furthermore, communications may utilize any suitable wireless communication technology, including, but not limited to, code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplexing (FDD), time division duplexing (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiplexing (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), and / or any other technology currently known or developed in the future.

[0051] It should be understood that the number of devices is for illustration purposes only and does not imply any limitation. Communication environment 100 may include any suitable number of devices for implementing embodiments of the present disclosure.

[0052] In the environment 100, the first device 110 may perform an RLF procedure when necessary. Figure 2A Describing an example RLF process, the figure shows an example RLF process 200 according to some example embodiments.

[0053] In process 200, after the first device 110 in RRC connected mode determines N310 (consecutive) OoS counts, the first device 110 may start a T310 timer at time 205. If N311 (consecutive) IS counts are determined while the T310 timer is running, the T310 timer may stop at time 210 and return to the OoS count. When the T310 timer expires, the first device 110 may declare an RLF. If the RRC connection reestablishment fails (e.g., within a timer (such as T311)), the first device 110 may move to RRC idle mode.

[0054] The following values ​​for counters and timers may be used for the RLF process 200:

[0055]

[0056] Furthermore, first device 110 may perform a positioning measurement procedure, such as a GNSS measurement procedure, as configured or scheduled by the network, for example, via second device 120 (such as an eNB). For example, second device 120 may aperiodically trigger first device 110 to perform GNSS measurements, for example, via a Medium Access Control (MAC) Control Element (CE). Thus, first device 110 in RRC connected mode may reacquire a GNSS position fix through gaps when triggered by second device 120. In an example, first device 110 may report a GNSS position fix duration for measurement to second device 120 during an initial access phase. In connected mode, first device 110 may report a GNSS verification duration to second device 120 using a MAC CE. Based on this reporting, second device 120 may trigger GNSS measurements by first device 110. Alternatively or additionally, if first device 110 does not receive a trigger to perform GNSS measurements from second device 120, first device 110 may autonomously reacquire GNSS (if configured by the network).

[0057] During the GNSS measurement process, the first device 110 may not be able to perform radio link monitoring (RLM) for the RLF process to estimate whether the first device 110 can reliably receive and decode the PDCCH, such as Figure 2B shown.

[0058] Figure 2B An example scenario 220 of performing GNSS measurements during an RLF procedure is shown, according to some example embodiments of the present disclosure.

[0059] In scenario 220, after the first device 110 has determined the N310 OoS count and therefore starts the T310 timer at time 225, the first device 110 can perform GNSS measurements 230. During this period, the first device 110 may not be able to perform RLF-related measurements. For example, the first device 110 may not detect an IS indication and have no opportunity to count IS before T310 expires.

[0060] In various example embodiments, the first device 110 may adjust at least one of the RLF process or the positioning measurement process to mitigate conflicts between the two processes. For example, the first device 110 may extend or pause the T310 timer and / or shift or postpone the configured measurement gap to avoid the RLF process being interrupted by the measurement process.

[0061] The following will refer to Figures 3 to 6 Some example embodiments of the present disclosure are described in detail.

[0062] Figure 3 1 shows a flow chart of an example method 300 according to some example embodiments of the present disclosure. The method 300 may be performed as follows: Figure 1 For the purpose of discussion, the first device 110 or the second device 120 will be implemented. Figure 1 The method 300 is described from the perspective of the first device 110.

[0063] At block 310, the first device 110 performs an RLF procedure. The RLF procedure may be performed when certain conditions are met. For example, Figure 2A As shown, the first device 110 can determine an OoS count, and if the OoS count is equal to or greater than a threshold count (such as N310), the first device 110 can start a timer, such as T310.

[0064] At block 320, the first device 110 performs a positioning measurement process, such as a GNSS measurement process, for example, when needed. For example, the first device 110 may be scheduled by the network, for example, via the second device 120 (such as a network device), to perform the positioning measurement process. Alternatively or in addition, the first device 110 may be configured by the network to autonomously perform the positioning measurement process.

[0065] According to an exemplary embodiment of the present disclosure, if two processes may conflict with each other, at least one of the two processes is adjusted by the first device 110. The RLF process and the positioning measurement process can be performed by the first device 110 in any order. As an example, if the RLF process is postponed until the positioning measurement process is completed, the RLF process can be performed after the positioning measurement process. As another example, if the RLF process is suspended before the start of the positioning measurement process and resumed after the positioning measurement process is completed, the positioning measurement process can be performed during the entire RLF process. Alternatively or additionally, if the positioning measurement process is shifted or postponed, the RLF process can be performed before the positioning measurement process.

[0066] The RLF process and / or the positioning measurement process may be adjusted in any suitable manner to mitigate conflicts therebetween. In some example embodiments, if the RLF process may conflict with the positioning measurement process, the RLF process may be adjusted. For example, if the first device 110 determines that a positioning measurement process is imminent, the first device 110 may determine a timer (such as T310) for the RLF process. Figure 3 The status shown)) and further make corresponding adjustments.

[0067] If the first device 110 determines that a measurement gap for a positioning measurement procedure will begin within a threshold time interval (such as a few seconds), the upcoming positioning measurement procedure may be determined. The measurement gap may be scheduled by the network (e.g., via the second device 120) or triggered autonomously by the first device 110. The threshold time interval may be network-configured or UE-implemented.

[0068] In some example embodiments, first device 110 may determine whether a timer is running or not. A running timer may mean that a predetermined number (e.g., N310) of Out-of-Service (OoS) may have been detected and IS may be evaluated. In other words, an RLF procedure is initiated. In this case, first device 110 may adjust the timer and, based on the adjusted timer, perform an RLF procedure to mitigate conflicts between the RLF procedure and an upcoming positioning measurement procedure.

[0069] The timer can be adjusted in any suitable manner. In some example embodiments, first device 110 can pause the timer during the positioning measurement process. For example, the timer can be paused at or before the start of a measurement gap and can be resumed for the remainder of the timer when the measurement is complete. In this way, the timer duration can bypass measurement gaps to avoid conflicts between the RLF process and the positioning measurement process.

[0070] In some example embodiments, first device 110 may extend the timer value to cover the length of the measurement gap. For example, the timer may be extended at the beginning of the measurement gap so that the timer does not expire during the measurement gap, thereby avoiding conflicts between the RLF process and the positioning measurement process. The extension value may be an absolute number that may correspond to the duration of the measurement gap. Alternatively or in addition, the extension value may be a multiplication factor. For example, the extended time length of the timer may be three or more times longer than the current time length of the timer, e.g., 3×current T310.

[0071] The extension may be network-configured. For example, the timer may extend the timer's extension duration (referred to as the "first extension duration") based on a configuration (referred to as the "first configuration") from another device (such as the second device 120), which may be a network device or a terminal device. Alternatively or additionally, the extension may be UE implementation-specific. For example, the first extension duration of the timer may be set by the first device 110 depending on a specific implementation.

[0072] Adjusting the timer may stagger the RLF process and the positioning measurement process.The first device 110 may continue to perform IS evaluation when the positioning measurement has been completed according to the remaining portion of the timer.

[0073] In some example embodiments, the first device 110 may adjust the timer by taking into account the IS count. For example, the first device 110 may determine whether the IS count associated with the RLF process is equal to or greater than a threshold count (referred to as a "first threshold count") and less than another threshold count (referred to as a "second threshold count") for stopping the timer (such as Figure 2A The first threshold count may be less than the second threshold count. If the condition is met, first device 110 may assume that it has recovered from the radio issue at the start of the positioning measurement. In this case, first device 110 may stop the timer. Thus, a new OoS evaluation, i.e., determining the OoS count, may be started after the measurement is completed. If the condition is not met, first device 110 may adjust the timer as described above.

[0074] In some example embodiments, first device 110 may adjust the timer based on a comparison of the actual measurement time with a measurement gap, which may be network-configured. For example, first device 110 may determine the length of time required to perform a positioning measurement procedure as, for example, the actual measurement time. First device 110 may then determine whether a condition is met where the length of time is shorter than the length of the measurement gap. For example, the duration or length of the gap may be configured by the network, such as via second device 120.

[0075] If this condition is met, the first device 110 may assume that there is a margin for the configured measurement gap before or after the measurement process is completed. The first device 110 may use this margin for the RLF process. For example, the first device 110 may postpone the start of the positioning measurement process until the timer expires or the RLF process is completed. If this condition is not met, the first device 110 may adjust the timer as described above.

[0076] To further separate the RLF procedure from the positioning measurement procedure, in some example embodiments, the first device 110 may consider the difference between the required time length and the measurement gap. For example, the first device 110 may determine whether the required measurement time + offset < measurement gap is satisfied. The offset may be network-configured or UE-implemented. If satisfied, which may mean that the required time is significantly shorter than the configured time, the first device 110 may attempt to complete the RLF procedure before starting the positioning measurement procedure. For example, the first device 110 may continue to count N311 IS indications for recovery, or continue IS counting until a timer (such as T310) expires.

[0077] In some example embodiments, first device 110 may determine whether a condition is satisfied that the remaining time of the timer is less than a threshold time (referred to as the "first threshold time") and the time until the start of the measurement gap is less than another threshold time (referred to as the "second threshold time"). The second threshold time is shorter than the first threshold time. If the condition is satisfied, this may mean that RLF is likely to be declared soon and the RRC connection will be released, so first device 110 may continue the RLF process without initiating a positioning measurement process at the start of the measurement gap. If the condition is not satisfied, first device 110 may adjust the timer as described above.

[0078] In some example embodiments, first device 110 may also consider an IS count in making a decision about continuing the RLF procedure. For example, first device 110 may compare an IS count associated with the RLF procedure with a threshold count (referred to as a third threshold count). The third threshold count may be set based on the number of recovered ISs (such as N311). For example, the third threshold count may be much lower than N311. If the IS count is less than the third threshold count, this may mean that first device 110 may have counted significantly fewer ISs and therefore may declare RLF, and first device 110 may continue the RLF procedure.

[0079] When a timer (such as T310) is suspended, extended, or otherwise adjusted due to a measurement gap, first device 110 may be unable to perform IS evaluation. Therefore, in some example embodiments, first device 110 may adjust IS evaluation associated with the RLF process accordingly. For example, IS evaluation may be suspended during a positioning measurement process.

[0080] Alternatively or additionally, the IS evaluation period may be extended to cover the length of the measurement gap. The extension may be performed based on a configured value, which may correspond to a measurement gap duration or a scaling factor. In some example embodiments, the extension of the period may be network-configured. For example, the period may be extended by an extension time (referred to as a "second extension time") based on a configuration (referred to as a "second configuration") from another device, such as the second device 120, which may be a network device or a terminal device. After the measurement gap is completed, the first device 110 may fall back to the configured evaluation period, which may be based on, for example, a T310 state and a discontinuous reception (DRX) configuration.

[0081] In some example embodiments, first device 110 may determine that the timer for the RLF procedure has not been started. In this case, first device 110 may determine an Out of Service (OoS) count to start the timer. If the OoS count is non-zero, first device 110 may reset the OoS count or retain the OoS count to continue after the positioning measurement procedure. Resetting or retaining the OoS count may also depend on whether the count exceeds a threshold greater than 0 but less than N310. Thus, the start of the timer may be delayed, and the RLF procedure may not conflict with the positioning measurement.

[0082] The following will refer to Figure 4 An example process for adjusting the RLF process is discussed.

[0083] Figure 4 A flow chart of an example process 400 for adjusting an RLF process at a first device 110 according to some example embodiments of the present disclosure is shown. In this example, GNSS measurements may be performed by the first device 110 as an example of positioning measurements.

[0084] like Figure 4 As shown, at 402, the first device 110 may determine that a GNSS measurement gap is imminent, e.g., starting in x seconds. The GNSS measurement gap may be scheduled by the second device 120, which may be a network device (such as an eNB), or may be autonomously triggered by the first device 110, which may be a terminal device (such as a UE). At 404, the first device 110 may determine whether a timer (such as T310) for the RLF procedure is running. If T310 is running, the first device 110 may adjust the T310 timer when the GNSS measurement gap begins and stop the IS evaluation.

[0085] The timer can be adjusted in two optional ways. Option A, shown at 406, can pause the T310 timer until the GNSS measurement has completed. For example, the first device 110 can pause the T310 timer at the start of the GNSS measurement gap and continue the remainder of the T310 timer when the GNSS measurement is complete. Option B, shown at 408, can extend the T310 timer to cover the length of the GNSS measurement gap. For example, the UE can extend T310 at the start of the GNSS measurement gap so that the T310 timer does not expire during the GNSS measurement gap.

[0086] After adjusting the timer, at 410, the first device 110 may begin GNSS measurements. At 412, the first device 110 may determine whether the GNSS measurements have completed. If so, the first device 110 may continue radio link monitoring (RLM). For example, the first device 110 may continue evaluating IS when the GNSS measurements have completed based on the remaining portion of the T310 timer.

[0087] In an example embodiment, the first device 110 may evaluate the number of ISs and determine whether any ISs have been detected during T310. At 416, the first device 110 may determine whether the number of ISs is greater than a (network-configured) threshold count (labeled thr1) but less than a threshold count (such as N311), which would stop T310. If so, the first device 110 may assume that it has recovered from the radio issue at the beginning of the GNSS measurement and therefore begin a new evaluation, such as a new count of OoS, after the GNSS measurement has completed. Then, at 418, when a GNSS measurement is imminent, the first device 110 may stop T310. If not, options A or B may be implemented.

[0088] In an example embodiment, at 420, the first device 110 may determine whether the time required to perform the GNSS measurement is shorter than the configured GNSS measurement gap. If so, at 422, the first device 110 may attempt to complete an RLF procedure, such as counting N311 IS or waiting for T310 to expire, before starting the GNSS measurement. If not, option A or B may be implemented.

[0089] In an example embodiment, at 424, the first device 110 may determine whether the remaining time of T310 is less than a (network-configured) threshold time (labeled thr2), and whether the time until the start of the GNSS measurement gap is less than a threshold time (labeled thr3), where Threshold 2 > Threshold 3. If so, the first device 110 may continue the IS evaluation period rather than starting the GNSS measurement gap, as it is likely that RLF will be declared soon and the RRC connection will be released accordingly (e.g., at 428).

[0090] If N311 is different from 1, the decision may also depend on the number of ISs that have been counted. Figure 4 As shown, at 426, the first device 110 can determine whether the number of counted ISs (labeled as #IS) is significantly less than N311. If so, the first device 110 can complete the RLF process instead of the GNSS measurement at 428. For example, if N311 is 10, but the first device 110 counted too few ISs to declare RLF, the first device 110 can make this decision.

[0091] In an example embodiment, if it is determined at 404 that T310 is not running, but the first device 110 has counted a non-zero number of OoS, the first device 110 may continue counting after the GNSS measurement gap, or reset the count. This may also depend on whether the number of OoS is above or below a (network configured) threshold. Figure 4 As shown, at 430, the first device 110 may determine whether the counted number of OoS (labeled as #OoS) is higher than a threshold count (labeled as thr4). If so, at 432, the first device 110 may continue counting #OoS after the GNSS measurement. If not, at 434, the first device 110 may reset the #OoS count. In an example, the first device 110 may be configured to maintain the current OoS / IS count and continue counting after the GNSS measurement gap, or to reset the OoS / IS count after the GNSS measurement gap is completed.

[0092] In addition to or in lieu of the RLF process, the first device 110 may adjust the positioning measurement process to mitigate the conflict between the two processes. In some example embodiments, the first device 110 may adjust the measurement gap to mitigate the conflict. Figure 5 and Figure 6 Some example implementations in this regard are discussed.

[0093] Figure 5 FIG. 5 is a flow chart illustrating an example process 500 for adjusting a measurement gap according to some example embodiments of the present disclosure. The process 500 may be implemented by the first device 110. For discussion purposes, the process 500 will be described in detail. Figure 1 The process 500 is described from the perspective of the first device 110 in FIG.

[0094] like Figure 5As shown, at block 510, the first device 110 may detect an early-out-of-synchronization (or "early-out-of-sync") event associated with an RLF process. At block 520, the first device 110 may adjust a measurement gap used for a positioning measurement process to mitigate collisions. At block 530, the first device 110 may perform a positioning measurement process based on the adjusted measurement gap.

[0095] In an example embodiment, if RLM reporting is configured, the first device 110 (such as a UE) may notify the network (e.g., the second device 120, such as a BS) of an upcoming RLM event. For example, if an "early out-of-sync" event is detected, the first device 110 may initiate the transmission of a UEAssistanceInformation message to report the event to the network. In this scenario, both the first device 110 and the network may be aware of the "early out-of-sync" event. Therefore, measurement gaps, which may be configured by the network, may be adjusted to facilitate the RLF process.

[0096] The measurement gap may be adjusted in any suitable manner. In some example embodiments, the measurement gap may be shifted or postponed to bypass the RLF. The gap shift may be based on a previously configured value (e.g., a value equal to T310) or indicated by the network (e.g., via the second device 120) in response to an RLM report. In some example embodiments, the shift time of the measurement gap may be shifted based on a configuration (referred to as a "third configuration") from another device (such as the second device 120), which may be a network device or a terminal device. In some example embodiments, the third configuration may be received by the first device 110 after the first device 110 sends an RLM report for the event to the other device after detecting an "early out-of-sync" event (referred to as a "first RLM report").

[0097] In some example embodiments, first device 110 may adjust the measurement gap to take into account an early-in-synchronization (or "early-in-sync") event, which may mean that first device 110 has almost recovered from the radio link problem. For example, first device 110 may consider shifting or postponing the measurement gap after detecting an "early-in-sync" event associated with an RLF procedure.

[0098] The "early synchronization" event may also be reported to the network. For example, if an "early synchronization" event is detected, the first device 110 may initiate the transmission of a UEAssistanceInformation message to report the event to the network. In some example embodiments, in response to detecting the "early synchronization" event, the first device 110 may send an RLM report (referred to as a second RLM report) for the "early synchronization" event to another device (such as the second device 120), which may be a network device or a terminal device. After sending the second RLM report, the first device 110 may adjust the measurement gap.

[0099] Figure 6 FIG. 6 is a flow chart illustrating an example process 600 for adjusting a measurement gap according to some other example embodiments of the present disclosure. The process 600 may be implemented by the second device 120. For discussion purposes, the following will be discussed. Figure 1 The process 600 is described from the perspective of the second device 120 in FIG.

[0100] like Figure 6 As shown, at block 610, the second device 120 may receive a first radio link monitoring report for an early out-of-sync event or a second radio link monitoring report for an early in-sync event from another device (such as the first device). The early out-of-sync event and the early in-sync event are associated with an RLF procedure performed by the other device.

[0101] At block 620 , the second device 120 may transmit, to another device, a configuration of a shift time for a measurement gap for a positioning measurement procedure to be performed by the other device to mitigate a conflict between the RLF procedure and the positioning measurement procedure.

[0102] As mentioned above Figures 3 to 5 All operations and features described in relation to the second device 120 and the network are equally applicable and have similar effects to the process 600. For the sake of brevity, details will be omitted.

[0103] In some example embodiments, a device capable of performing any of the method 300 and the process 500 (e.g., Figure 1 The first device 110 in the embodiment may include components for performing the corresponding operations of the method 300 and the process 500. The components may be implemented in any suitable form. For example, the components may be implemented as a circuit system or a software module. The device may be implemented as Figure 1 The first device 110 in or is included in the first device.

[0104] In some example embodiments, an apparatus includes: means for performing a radio link failure procedure; and means for performing a positioning measurement procedure, wherein at least one of the radio link failure procedure or the positioning measurement procedure is adjusted to mitigate a conflict between the radio link failure procedure and the positioning measurement procedure.

[0105] In some example embodiments, means for performing a radio link failure procedure includes: means for determining whether a timer for the radio link failure procedure is running or not started based on a determination that a measurement gap for a positioning measurement procedure will begin within a threshold time interval; means for adjusting the timer to mitigate conflicts based on the determination that the timer is running; and means for performing the radio link failure procedure based on the adjusted timer.

[0106] In some example embodiments, the means for adjusting the timer comprises means for pausing the timer during the positioning measurement procedure.

[0107] In some example embodiments, the means for adjusting the timer comprises means for extending the value of the timer to cover the length of the measurement gap.

[0108] In some example embodiments, the timer extends a first extended time of the timer based on a first configuration from another device.

[0109] In some example embodiments, the component for adjusting the timer includes: a component for determining whether a condition is met that a synchronization count associated with a radio link failure process is equal to or greater than a first threshold count and less than a second threshold count for stopping the timer, the first threshold count being less than the second threshold count; and a component for adjusting the timer based on a determination that the condition is not met.

[0110] In some example embodiments, the apparatus further comprises means for stopping the timer based on a determination that the condition is satisfied.

[0111] In some example embodiments, the means for adjusting the timer includes: means for determining a length of time required to perform a positioning measurement process; means for determining whether a condition is met that the length of time is shorter than a length of a measurement gap; and means for adjusting the timer based on a determination that the condition is not met.

[0112] In some example embodiments, the apparatus further comprises means for deferring the start of the positioning measurement procedure until the timer is stopped or the radio link failure procedure is completed based on the determination that the condition is satisfied.

[0113] In some example embodiments, the means for adjusting the timer includes: means for determining whether a condition is satisfied that a remaining time of the timer is less than a first threshold time and a time until the start of the measurement gap is less than a second threshold time, the second threshold time being shorter than the first threshold time; and means for adjusting the timer based on a determination that the condition is not satisfied.

[0114] In some example embodiments, the apparatus further comprises means for continuing the radio link failure procedure without initiating a positioning measurement procedure at the beginning of the measurement gap based on a determination that the condition is satisfied.

[0115] In some example embodiments, the means for continuing the radio link failure process includes: means for comparing a synchronization count with a third threshold count, the synchronization count being associated with the radio link failure process and the third threshold count being less than a second threshold count for stopping the timer; and means for continuing the radio link failure process based on a determination that the synchronization count is less than the third threshold count.

[0116] In some example embodiments, the apparatus further comprises means for adjusting a synchronization assessment associated with the radio link failure procedure.

[0117] In some example embodiments, the means for adjusting the synchronization assessment includes means for suspending the synchronization assessment during the positioning measurement process.

[0118] In some example embodiments, the means for adjusting the synchronization assessment comprises means for extending a period of the synchronization assessment to cover a length of the measurement gap.

[0119] In some example embodiments, the period of the synchronous evaluation is extended by a second extended time of the period based on a second configuration from the other device.

[0120] In some example embodiments, the apparatus further comprises: means for determining an out-of-sync count for starting the timer based on a determination that the timer is not started; and means for resetting the out-of-sync count or retaining the out-of-sync count to continue after the positioning measurement process based on a determination that the out-of-sync count is non-zero.

[0121] In some example embodiments, resetting or retaining is performed based on a determination that the out-of-sync count is equal to or less than a fourth threshold count.

[0122] In some example embodiments, means for performing a positioning measurement procedure includes: means for adjusting a measurement gap for the positioning measurement procedure to mitigate collisions after detecting an early out-of-sync event associated with a radio link failure procedure; and means for performing the positioning measurement procedure based on the adjusted measurement gap.

[0123] In some example embodiments, the means for adjusting the measurement gap comprises means for shifting or delaying the measurement gap.

[0124] In some example embodiments, the measurement gap is shifted by a shift time of the measurement gap based on a third configuration from another device.

[0125] In some example embodiments, the means for performing the positioning measurement procedure further comprises means for sending a first radio link monitoring report for the early out-of-synchronization event to another device in response to detecting the early out-of-synchronization event, wherein the third configuration is received in response to sending the first radio link monitoring report.

[0126] In some example embodiments, the means for adjusting the measurement gap comprises means for adjusting the measurement gap upon detecting an early synchronization event associated with a radio link failure procedure.

[0127] In some example embodiments, the means for adjusting the measurement gap comprises: means for sending a second radio link monitoring report for the early synchronization event to the other device in response to detecting the early synchronization event; and means for adjusting the measurement gap after sending the second radio link monitoring report.

[0128] In some example embodiments, the apparatus further comprises means for performing the method 300 or the process 500 or other operations in some example embodiments of the first device 110. In some example embodiments, the means comprises: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform.

[0129] In some example embodiments, a device capable of performing any of process 600 (e.g., Figure 1 The second device 120 in the embodiment may include components for performing the corresponding operations of process 600. The components may be implemented in any suitable form. For example, the components may be implemented as a circuit system or a software module. The device may be implemented as Figure 1 The second device 120 in or included in the second device.

[0130] In some example embodiments, a device includes: a component for receiving a first radio link monitoring report for an early out-of-sync event or a second radio link monitoring report for an early synchronization event from another device, the early out-of-sync event and the early synchronization event being associated with a radio link failure procedure performed by the other device; and a component for sending to the other device a configuration of a shift time for a measurement gap for a positioning measurement procedure to be performed by the other device to mitigate a conflict between the radio link failure procedure and the positioning measurement procedure.

[0131] In some example embodiments, the apparatus further comprises means for performing process 600 or other operations in some example embodiments of second device 120. In some example embodiments, the means comprises: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform.

[0132] Figure 7 is a simplified block diagram of an apparatus 700 suitable for implementing an example embodiment of the present disclosure. The apparatus 700 may be provided to implement a communication device, such as Figure 1 The first device 110 or the second device 120 is shown. As shown, the device 700 includes one or more processors 710, one or more memories 720 coupled to the processor 710, and one or more communication modules 740 coupled to the processor 710.

[0133] The communication module 740 is configured for bidirectional communication. The communication module 740 has one or more communication interfaces to facilitate communication with one or more other modules or devices. A communication interface may represent any interface necessary to communicate with other network elements. In some example embodiments, the communication module 740 may include at least one antenna.

[0134] Processor 710 may be of any type suitable for the local technology network and, as non-limiting examples, may include one or more of the following: a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 700 may have multiple processors, such as application specific integrated circuit chips, which are time-controlled by a clock that synchronizes a main processor.

[0135] The memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 724, electrically programmable read-only memory (EPROM), flash memory, hard disks, compact disks (CDs), digital video disks (DVDs), optical disks, laser disks, and other magnetic and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 722 and other volatile memories that will not be maintained for the duration of a power outage.

[0136] The computer program 730 includes computer-executable instructions executed by the associated processor 710. The instructions of the program 730 may include instructions for performing the operations / actions of some example embodiments of the present disclosure. The program 730 may be stored in a memory (e.g., ROM 724). The processor 710 may perform any suitable actions and processes by loading the program 730 into the RAM 722.

[0137] The exemplary embodiments of the present disclosure may be implemented with the aid of a program 730, such that the device 700 may execute the following steps: Figures 3 to 6 Any process of the present disclosure discussed. Example embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0138] In some example embodiments, the program 730 may be tangibly embodied in a computer-readable medium (such as memory 720) that may be included in the device 700 or other storage device accessible by the device 700. The device 700 may load the program 730 from the computer-readable medium to the RAM 722 for execution. In some example embodiments, the computer-readable medium may include any type of non-transitory storage medium, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. The term "non-transitory" as used herein is a limitation on the medium itself (i.e., tangible, not a signal), not a limitation on the persistence of data storage (e.g., RAM vs. ROM).

[0139] Figure 8 An example of a computer readable medium 800 is shown which may be in the form of a CD, DVD, or other optical storage disc.The computer readable medium 800 has the program 730 stored thereon.

[0140] In general, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are shown and described as block diagrams, flow charts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or a controller or other computing device, or some combination thereof.

[0141] Some example embodiments of the present disclosure also provide at least one computer program product, which is tangibly stored on a computer-readable medium (such as a non-transitory computer-readable storage medium). The computer program product includes computer-executable instructions, such as those included in a program module, which are executed on a target physical or virtual processor in a device to perform any of the methods described above. Generally, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of a program module can be combined or separated between program modules as needed. The machine-executable instructions for a program module can be executed in a local or distributed device. In a distributed device, a program module can be located in both local and remote storage media.

[0142] The program code for performing the method of the present disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device so that when executed by the processor or controller, the program code implements the functions / operations specified in the flow chart and / or block diagram. The program code may be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0143] In the context of the present disclosure, computer program code or related data can be carried by any suitable carrier to enable an apparatus, device or processor to perform various processes and operations as described above. Examples of carriers include signals, computer-readable media, etc.

[0144] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or apparatuses, or any suitable combination of the foregoing. More specific examples of computer readable storage media would include an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0145] In addition, although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in a sequential order or requiring that all operations shown be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details have been included in the above discussion, these should not be understood as limitations on the scope of this disclosure, but rather as descriptions of features that may be specific to a particular embodiment. Unless explicitly stated, some features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, unless explicitly stated, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable subcombination.

[0146] Although the disclosure has been described in language specific to structural features and / or methodological acts,

[0147] It is to be understood, however, that the present disclosure as defined in the appended claims is not necessarily limited to the foregoing description.

[0148] Rather, the specific features and acts described above are intended to be used as a means of implementing the rights

[0149] Required sample form public.

Claims

1. A device, comprising: at least one processor; as well as at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least perform: performing radio link failure procedures; as well as Perform positioning measurement process, At least one of the radio link failure procedure or the positioning measurement procedure is adjusted to mitigate a conflict between the radio link failure procedure and the positioning measurement procedure.

2. The apparatus of claim 1 , wherein performing the radio link failure procedure comprises: determining whether a timer for the radio link failure procedure is running or inactive based on a determination that a measurement gap for the positioning measurement procedure will begin within a threshold time interval; Based on a determination that the timer is running, adjusting the timer to mitigate the conflict; as well as The radio link failure procedure is performed based on the adjusted timer.

3. The apparatus of claim 2 , wherein adjusting the timer comprises: The timer is paused during the positioning measurement procedure.

4. The apparatus of claim 2 , wherein adjusting the timer comprises: The value of the timer is extended to cover the length of the measurement gap. The device of claim 4 , wherein the timer extends the first extension time of the timer based on a first configuration from another device.

6. The apparatus of any one of claims 2 to 5, wherein adjusting the timer comprises: determining whether a condition is satisfied that a synchronization count associated with the radio link failure procedure is equal to or greater than a first threshold count and less than a second threshold count for stopping the timer, the first threshold count being less than the second threshold count; as well as Based on a determination that the condition is not met, the timer is adjusted.

7. The apparatus of claim 6, further comprising: Based on a determination that the condition is satisfied, the timer is stopped.

8. The apparatus of any one of claims 2 to 7, wherein adjusting the timer comprises: determining a length of time required to perform the positioning measurement process; determining whether a condition that the time length is shorter than the length of the measurement gap is satisfied; Based on a determination that the condition is not met, the timer is adjusted.

9. The apparatus of claim 8, further comprising: Based on a determination that the condition is satisfied, starting of the positioning measurement procedure is postponed until the timer is stopped or the radio link failure procedure is completed.

10. The apparatus of any one of claims 2 to 9, wherein adjusting the timer comprises: determining whether a condition is satisfied that a remaining time of the timer is less than a first threshold time and a time until the start of the measurement gap is less than a second threshold time, the second threshold time being shorter than the first threshold time; as well as Based on a determination that the condition is not met, the timer is adjusted.

11. The apparatus of claim 10, wherein the apparatus is further caused to perform: Based on a determination that the condition is satisfied, the radio link failure procedure is continued without initiating the positioning measurement procedure at the start of the measurement gap.

12. The apparatus of claim 11 , wherein continuing the radio link failure procedure comprises: comparing a synchronization count to a third threshold count, the synchronization count being associated with the radio link failure procedure and the third threshold count being less than a second threshold count for stopping the timer; as well as Based on a determination that the synchronization count is less than the third threshold count, the radio link failure procedure is continued.

13. The apparatus of any one of claims 2 to 12, wherein the apparatus is further caused to perform: A synchronization assessment associated with the radio link failure procedure is adjusted.

14. The apparatus of claim 13, wherein adjusting the synchronization assessment comprises: The synchronization evaluation is suspended during the positioning measurement process.

15. The apparatus of claim 13, wherein adjusting the synchronization assessment comprises: The period of the synchronization evaluation is extended to cover the length of the measurement gap. 16 . The device of claim 15 , wherein the period of the synchronous evaluation is extended by a second extension time of the period based on a second configuration from another device.

17. The apparatus of any one of claims 2 to 16, wherein the apparatus is further configured to: Based on a determination that the timer is not started, determining an out-of-sync count for starting the timer; and Based on a determination that the out-of-sync count is non-zero, the out-of-sync count is reset, or the out-of-sync count is retained to continue after the positioning measurement process. 18 . The apparatus of claim 17 , wherein the resetting or the retaining is performed based on a determination that the out-of-sync count is equal to or less than a fourth threshold count.

19. The apparatus according to any one of claims 1 to 18, wherein performing the positioning measurement process comprises: After detecting an early out-of-sync event associated with the radio link failure procedure, adjusting a measurement gap for the positioning measurement procedure to mitigate the conflict; as well as The positioning measurement process is performed based on the adjusted measurement gap.

20. The apparatus of claim 19, wherein adjusting the measurement gap comprises: The measurement gap is shifted or postponed.

21. The apparatus of claim 20, wherein the measurement gap is shifted by a shift time of the measurement gap based on a third configuration from another apparatus.

22. The apparatus of claim 21, wherein performing the positioning measurement process further comprises: In response to detecting the early out-of-sync event, sending a first radio link monitoring report for the early out-of-sync event to the other device; The third configuration is received in response to sending the first radio link monitoring report.

23. The apparatus of any one of claims 19 to 22, wherein adjusting the measurement gap comprises: The measurement gap is adjusted upon detecting an early synchronization event associated with the radio link failure procedure.

24. The apparatus of claim 23, wherein adjusting the measurement gap comprises: In response to detecting the early synchronization event, sending a second radio link monitoring report for the early synchronization event to another device; as well as After sending the second radio link monitoring report, adjusting the measurement gap.

25. A device comprising: at least one processor; as well as at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least perform: receiving, from another device, a first radio link monitoring report for an early out-of-sync event or a second radio link monitoring report for an early in-sync event, the early out-of-sync event and the early in-sync event being associated with a radio link failure procedure performed by the other device; as well as A configuration of a shift time for a measurement gap used for a positioning measurement procedure to be performed by the other device is transmitted to the other device to mitigate a conflict between the radio link failure procedure and the positioning measurement procedure.

26. A method comprising: At the device, performing radio link failure procedures; as well as Perform positioning measurement process, At least one of the radio link failure procedure or the positioning measurement procedure is adjusted to mitigate a conflict between the radio link failure procedure and the positioning measurement procedure.

27. The method of claim 26, wherein performing the radio link failure procedure comprises: determining whether a timer for the radio link failure procedure is running or inactive based on a determination that a measurement gap for the positioning measurement procedure will begin within a threshold time interval; Based on a determination that the timer is running, adjusting the timer to mitigate the conflict; as well as The radio link failure procedure is performed based on the adjusted timer.

28. The method of claim 27, wherein adjusting the timer comprises: The timer is paused during the positioning measurement procedure.

29. The method of claim 28, wherein adjusting the timer comprises: The value of the timer is extended to cover the length of the measurement gap.

30. The method of claim 29, wherein the timer extends the first extension time of the timer based on a first configuration from another device.

31. The method of any one of claims 27 to 30, wherein adjusting the timer comprises: determining whether a condition is satisfied that a synchronization count associated with the radio link failure procedure is equal to or greater than a first threshold count and less than a second threshold count for stopping the timer, the first threshold count being less than the second threshold count; as well as Based on a determination that the condition is not met, the timer is adjusted.

32. The method of claim 31 , further comprising causing the device to: Based on a determination that the condition is satisfied, the timer is stopped.

33. The method of any one of claims 27 to 32, wherein adjusting the timer comprises: determining a length of time required to perform the positioning measurement process; determining whether a condition that the time length is shorter than the length of the measurement gap is satisfied; Based on a determination that the condition is not met, the timer is adjusted.

34. The method of claim 33, further comprising causing the device to: Based on a determination that the condition is satisfied, starting of the positioning measurement procedure is postponed until the timer is stopped or the radio link failure procedure is completed.

35. The method of any one of claims 27 to 34, wherein adjusting the timer comprises: determining whether a condition is satisfied that a remaining time of the timer is less than a first threshold time and a time until the start of the measurement gap is less than a second threshold time, the second threshold time being shorter than the first threshold time; as well as Based on a determination that the condition is not met, the timer is adjusted.

36. The method of claim 35, further comprising causing the device to: Based on a determination that the condition is satisfied, the radio link failure procedure is continued without initiating the positioning measurement procedure at the start of the measurement gap.

37. The method of claim 36, wherein continuing the radio link failure procedure comprises: comparing a synchronization count to a third threshold count, the synchronization count being associated with the radio link failure procedure and the third threshold count being less than a second threshold count for stopping the timer; as well as Based on a determination that the synchronization count is less than the third threshold count, the radio link failure procedure is continued.

38. The method of any one of claims 27 to 35, wherein the device is further caused to perform: A synchronization assessment associated with the radio link failure procedure is adjusted.

39. The method of claim 38, wherein adjusting the synchronization assessment comprises: The synchronization evaluation is suspended during the positioning measurement process.

40. The method of claim 38, wherein adjusting the synchronization assessment comprises: The period of the synchronization evaluation is extended to cover the length of the measurement gap.

41. The method of claim 40, wherein the period of the synchronous evaluation is extended by a second extension time based on a second configuration from another device.

42. The method of any one of claims 27 to 41, wherein the device is further caused to: Based on a determination that the timer is not started, determining an out-of-sync count for starting the timer; and Based on a determination that the out-of-sync count is non-zero, the out-of-sync count is reset, or the out-of-sync count is retained to continue after the positioning measurement process.

43. The method of claim 42, wherein the resetting or the retaining is performed based on a determination that the out-of-sync count is equal to or less than a fourth threshold count.

44. The method of any one of claims 26 to 43, wherein performing the positioning measurement process comprises: After detecting an early out-of-sync event associated with the radio link failure procedure, adjusting a measurement gap for the positioning measurement procedure to mitigate the conflict; as well as The positioning measurement process is performed based on the adjusted measurement gap.

45. The method of claim 44, wherein adjusting the measurement gap comprises: The measurement gap is shifted or postponed.

46. ​​The method of claim 45, wherein the measurement gap is shifted by a shift time of the measurement gap based on a third configuration from another device.

47. The method of claim 46, wherein performing the positioning measurement process further comprises: In response to detecting the early out-of-sync event, sending a first radio link monitoring report for the early out-of-sync event to the other device; The third configuration is received in response to sending the first radio link monitoring report.

48. The method of any one of claims 44 to 47, wherein adjusting the measurement gap comprises: The measurement gap is adjusted upon detecting an early synchronization event associated with the radio link failure procedure.

49. The method of claim 48, wherein adjusting the measurement gap comprises: In response to detecting the early synchronization event, sending a second radio link monitoring report for the early synchronization event to another device; as well as After sending the second radio link monitoring report, adjusting the measurement gap.

50. A method comprising: At the device, receiving, from another device, a first radio link monitoring report for an early out-of-sync event or a second radio link monitoring report for an early in-sync event, the early out-of-sync event and the early in-sync event being associated with a radio link failure procedure performed by the other device; as well as A configuration of a shift time for a measurement gap used for a positioning measurement procedure to be performed by the other device is transmitted to the other device to mitigate a conflict between the radio link failure procedure and the positioning measurement procedure.

51. A device comprising: means for performing a radio link failure procedure; as well as A component for performing a positioning measurement process, At least one of the radio link failure procedure or the positioning measurement procedure is adjusted to mitigate a conflict between the radio link failure procedure and the positioning measurement procedure.

52. A device comprising: means for receiving, from another device, a first radio link monitoring report for an early out-of-sync event or a second radio link monitoring report for an early in-sync event, the early out-of-sync event and the early in-sync event being associated with a radio link failure procedure performed by the other device; as well as means for transmitting to the other device a configuration of a shift time for a measurement gap for a positioning measurement procedure to be performed by the other device to mitigate a conflict between the radio link failure procedure and the positioning measurement procedure.

53. A computer-readable medium comprising instructions stored thereon for causing a device to at least perform the method of any one of claims 26 to 49 or claim 50.

Images