Reducing the impact of location measurements on RLF procedures.

Abstract

Exemplary embodiments of the present disclosure relate to an apparatus, method, and computer-readable storage medium for mitigating the impact of positioning on radio link failure (RLF) procedures. In the method, an apparatus performs an RLF process and performs a positioning process, and at least one of the RLF process or the positioning process is coordinated to mitigate collisions between the processes.

Description

[Technical Field]

[0001] Various exemplary embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly to an apparatus, method, and computer-readable storage medium for mitigating the impact of position measurements on radio link failure (RLF) procedures. [Background technology]

[0002] The Internet of Things (IoT) over non-terrestrial networks (NTN) is supported in 3rd Generation Partnership Project (3GPP) Release 18 (Rel-18). Mobility and performance enhancements in Rel-18 anticipate that simultaneous operation of both Global Positioning Satellite System (GNSS) and NTN Narrowband (NB)-IoT / eMTC (enhanced Machine-Type Communication) may not be possible.

[0003] For GNSS measurements, an evolved NodeB (eNB) may aperiodically schedule GNSS measurement gaps so that the user equipment (UE) can acquire new GNSS position corrections before the expiration of the current GNSS position. However, the eNB may not be aware that the UE is experiencing link problems because the UE may not report link problems unless specifically configured by the eNB. Therefore, 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, an apparatus is provided, the apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least perform a radio link failure process and a position measurement process, wherein at least one of the radio link failure process or the position measurement process is adjusted to mitigate collisions between the radio link failure process and the position measurement process.

[0005] In a second aspect of the present disclosure, an apparatus is provided, the apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: receive, from a further device, a first radio link monitoring report of an early out-of-sync event or a second radio link monitoring report of an early in-sync event, the early out-of-sync event and the early in-sync event being associated with a radio link failure process performed by the further device; and transmit, to the further device, a configuration of a shift time of a measurement gap of a position measurement process performed by the further device to mitigate collisions between the radio link failure process and a position measurement process.

[0006] In a third aspect of the present disclosure, a method is provided, the method including: performing a radio link failure process and performing a position measurement process, wherein at least one of the radio link failure process or the position measurement process is adjusted to mitigate collisions between the radio link failure process and the position measurement process.

[0007] In a fourth aspect of the present disclosure, a method is provided, the method including receiving, at an apparatus, from a further apparatus a first radio link monitoring report of an early out-of-sync event or a second radio link monitoring report of an early in-sync event, where the early out-of-sync event and the early in-sync event are associated with a radio link failure process performed by the further apparatus, and transmitting to the further apparatus a configuration of a measurement gap shift time of the position measurement process performed by the further apparatus to mitigate collisions between the radio link failure process and the position measurement process.

[0008] In a fifth aspect of the present disclosure, an apparatus is provided, the apparatus including: means for performing a radio link failure process; and means for performing a position measurement process, wherein at least one of the radio link failure process or the position measurement process is adjusted to mitigate collisions between the radio link failure process and the position measurement process.

[0009] In a sixth aspect of the present disclosure, an apparatus is provided, the apparatus including: means for receiving, from a further apparatus, a first radio link monitoring report of an early out-of-sync event or a second radio link monitoring report of an early in-sync event, where the early out-of-sync event and the early in-sync event are associated with a radio link failure process performed by the further apparatus; and means for transmitting to the further apparatus a configuration of a shift time of a measurement gap of a position measurement process performed by the further apparatus to mitigate collisions between the radio link failure process and a position measurement process.

[0010] In a seventh aspect of the present disclosure, there is provided a computer-readable medium having stored thereon instructions for causing an apparatus to perform at least a method according to the third or fourth aspect.

[0011] It should be understood that this Summary section is not intended to identify 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 be readily apparent through the following description.

[0012] Some example embodiments will now be described with reference to the accompanying drawings. [Brief explanation of the drawings]

[0013] [Figure 1] 1 illustrates an exemplary communication environment in which exemplary embodiments of the present disclosure may be implemented. [Figure 2A] 1 illustrates a diagram of an example RLF procedure in accordance with some example embodiments. [Figure 2B] 1 illustrates a diagram of an example scenario in which GNSS measurements are performed during an RLF procedure, in accordance with some example embodiments of the present disclosure. [Figure 3] 1 illustrates a flowchart of a method according to some exemplary embodiments of the present disclosure. [Figure 4] 1 illustrates a flowchart of an example process for coordinating RLF processes, according to some example embodiments of the present disclosure. [Figure 5] 10 illustrates a flowchart of an example process for adjusting a measurement gap, according to some example embodiments of the present disclosure. [Figure 6] 10 shows a flowchart of an example process for adjusting a measurement gap, according to some other example embodiments of the present disclosure. [Figure 7] FIG. 1 shows a simplified block diagram of an apparatus suitable for implementing exemplary embodiments of the present disclosure. [Figure 8] 1 illustrates a block diagram of an exemplary computer-readable medium according to some exemplary embodiments of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0014] Throughout the drawings, the same or similar reference numbers represent the same or similar elements.

[0015] The principles of the present disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are set forth for illustrative purposes only, to aid those skilled in the art in understanding and practicing the present disclosure, but are not intended to suggest any limitation on the scope of the present disclosure. The embodiments described herein can be implemented in various ways other than those described below.

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

[0017] References in this disclosure to "one embodiment," "embodiment," "example embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment is required to include the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is believed to be within the knowledge of one of ordinary skill in the art to affect such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

[0018] Although the terms "first," "second," and the like may be used herein to describe various elements, it is understood that 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 could be referred to as a second element, and similarly, a second element could 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 terms.

[0019] As used herein, "at least one of the following: " and " "At least one of" and similar phrases, where a list of two or more elements is joined by "and" or "or," means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0020] As used herein, unless expressly stated, 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 intervening steps.

[0021] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of 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. Furthermore, it will be understood that the terms "comprises," "comprising," "having," "having," "includes," and / or "including," as used herein, specify the presence of stated features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0022] As used in this application, the term "circuitry" may refer to one or more or all of the following: (a) Hardware-only circuit implementations (e.g., implementations using only analog and / or digital circuits); (b) For example (where applicable), a combination of the following hardware circuitry and software: (i) a combination of analog and / or digital hardware circuitry(s) and software / firmware; (ii) any portion of software-based hardware processor(s) (including digital signal processor(s)), software, and memory(s) that cooperate to cause a device, such as a mobile phone or server, to perform various functions; and (c) Hardware circuit(s) and / or processor(s), such as microprocessor(s) or part of microprocessor(s), that require software (e.g., firmware) for operation, although software may not be present if not necessary for operation.

[0023] This definition of circuit applies to all uses of the term in this application, including any claims. As a further example, the term circuit, as used herein, also encompasses an embodiment of a simple hardware circuit or processor(s), or a portion of a hardware circuit or processor, as well as its (or their) accompanying software and / or firmware. The term circuit also encompasses, for example, a baseband 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, if applicable to certain claim elements.

[0024] As used herein, the term "communication network" refers to a network conforming to any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), and Narrowband Internet of Things (NB-IoT). Furthermore, communications between terminal devices and network devices in a 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. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will, of course, be future communication technologies and systems in which the present disclosure can be embodied. The scope of the present disclosure should not be considered limited to only the aforementioned systems.

[0025] As used herein, the term "network device" refers to a node in a communication network through which a terminal device accesses and receives service from the network. Depending on the terminology and technology applied, a network device may refer to: a base station (BS) or access point (AP), e.g., a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also referred to as a gNB), a remote radio unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, an integrated access and backhaul (IAB) node, a low-power node, e.g., a femto, pico, non-terrestrial based network (NTN) or non-terrestrial based network device, e.g., a satellite network device, a low Earth orbit (LEO) satellite, and a geosynchronous orbit (GEO) satellite, an airborne network device, etc. In some exemplary embodiments, a Radio Access Network (RAN) split architecture comprises a centralized unit (CU) and a distributed unit (DU) in an IAB donor node. An IAB node comprises a mobile terminal (IAB-MT) portion that acts like a UE towards a parent node, and the DU portion of the IAB node acts like a base station towards the next-hop IAB node.

[0026] The term "terminal device" refers to any end device that may be capable of wireless communication. By way of example and not limitation, a terminal device may be referred to as a communication device, user equipment (UE), subscriber station (SS), mobile subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cell phones, smartphones, voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded equipment (LEE), laptop mounted equipment (LME), USB dongles, smart devices, wireless customer premises equipment (CPE), Internet of Things (IoT) devices, watches or other wearables, head-mounted displays (HMD), vehicles, drones, medical equipment and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial processing and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, and the like. Terminal devices may also correspond to the mobile termination (MT) portion of an IAB node (e.g., a relay node). In the following description, the terms "terminal device", "communication device", "terminal", "user equipment", and "UE" may be used interchangeably.

[0027] As used herein, the terms "resource," "transmission resource," "resource block," "physical resource block" (PRB), "uplink resource," or "downlink resource" may refer to any resource for performing communication, such as communication between a terminal device and a network device, including time-domain resources, frequency-domain resources, spatial-domain resources, code-domain resources, or other resources that enable communication. Hereinafter, unless explicitly stated, both frequency-domain and time-domain resources are used as examples of transmission resources to describe some exemplary embodiments of the present disclosure. It should be noted that the exemplary embodiments of the present disclosure are equally applicable to other resources in other domains.

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

[0029] Based on the Release 17 (Rel-17) specifications, user equipment (UE) may use GNSS operation to pre-compensate any uplink transmissions towards satellites to ensure time and frequency alignment. As noted above, IoT over NTN is supported in 3GPP Rel-18. Rel-18 mobility and performance enhancements anticipate that simultaneous operation of both GNSS and NTN NB-IoT / eMTC may not be possible. Thus, the eNB may schedule "GNSS measurement gaps" where the UE may use GNSS to acquire new position corrections, but the UE may not be able to operate NB-IoT / eMTC during the gaps.

[0030] Situations may exist where a UE has a scheduled GNSS measurement gap that coincides with a radio link failure (RLF) procedure. For example, if the UE determines an OoS count of N310, the UE may start a timer T310. Because the UE may perform GNSS measurements immediately after starting T310, the UE may not be able to detect an IS indication and therefore may declare RLF. This is problematic because it triggers an RRC connection re-establishment procedure, which may render the UE unavailable for further immediate communication with the eNB. In some cases, the UE may have recovered from RLF if it had not performed GNSS measurements, and therefore the RLF and RRC connection re-establishment procedures may have been avoided.

[0031] Always setting a longer T310 (e.g., longer than the UE's GNSS measurements) may not be a useful option, as it may be desirable to quickly detect radio link problems at any other time during the connection.

[0032] Exemplary embodiments of the present disclosure propose a scheme for handling the interruption of an RLF procedure by GNSS measurements. In this scheme, at least one of the RLF process or a position measurement process (e.g., a GNSS measurement process) performed by a device such as a UE is coordinated to mitigate collisions between the two processes. In the context of the present disclosure, the RLF process and the position measurement process may also be referred to as an RLF procedure and a position measurement procedure, respectively. In some exemplary embodiments, when an RLF procedure and a GNSS measurement (e.g., in the case of an NTN) may collide, some new UE behaviors may be defined. For example, the UE may extend or pause the T310 timer if the T310 timer may collide with a GNSS measurement gap. Detailed behaviors may be described in the following paragraphs.

[0033] In this way, the UE may be prevented from declaring a fake or false RLF during GNSS measurements due to a faulty IS evaluation during the GNSS measurements. Such a declaration may result in a subsequent RRC connection re-establishment, which may result in high power consumption and signaling overhead. A scheme according to an example embodiment of the present disclosure may save UE energy and minimize signaling, making it more efficient.

[0034] 1 illustrates an exemplary communication environment 100 in which exemplary embodiments of the present disclosure may be implemented. In the communication environment 100, multiple communication devices, including a first device 110 and a second device 120, may communicate with each other.

[0035] For purposes of explanation, some exemplary embodiments are described below with first apparatus 110 operating as a terminal device, such as a UE, and second apparatus 120 operating as a network device, such as a gNB. However, in some exemplary embodiments, operations described in conjunction with a terminal device may be implemented in a network device or other device, and operations described in conjunction with a network device may be implemented in a terminal device or other device.

[0036] In some demonstrative embodiments, when 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), while 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 120 is a transmitting (TX) device (or transmitter) and the first device 110 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 demonstrative embodiments, both the first device 110 and the second device 120 may be terminal devices capable of communicating with each other on a sidelink (SL).

[0037] Communications in communication environment 100 may be conducted according to any suitable communications protocol(s), such as, without limitation, cellular communications protocols such as first generation (1G), second generation (2G), third generation (3G), fourth generation (4G), fifth generation (5G), sixth generation (6G), wireless local network communications protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocols now known or later developed. Further, communications may utilize any suitable wireless communications technology, such as, without limitation, code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplex (FDD), time division duplex (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiplexing (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), and / or any other technology now known or later developed.

[0038] It should be understood that the number of devices is for illustrative purposes only, without implying any limitation, and communication environment 100 may include any number of devices suitable for implementing embodiments of the present disclosure.

[0039] In environment 100, first device 110 may perform an RLF process as needed. An example RLF process is described with reference to FIG. 2A, which illustrates an example RLF procedure 200 according to some example embodiments.

[0040] In procedure 200, after the first device 110 in RRC connected mode determines a (consecutive) OoS count of N310, the first device 110 may start a T310 timer at time 205. If a (consecutive) IS count of N311 is determined while the T310 timer is running, the T310 timer may be stopped at time 210 and revert to an OoS count. When the T310 timer expires, the first device 110 may declare an RLF. If RRC connection re-establishment fails (e.g., within a timer such as T311), the first device 110 may transition to an RRC idle mode.

[0041] The next values ​​of the counters and timers may be used in the following RLF procedure 200.

[0042] [Table 1]

[0043] Additionally, the first device 110 may perform a position measurement process, such as a network-configured or scheduled GNSS measurement process, via the second device 120, e.g., an eNB. For example, the second device 120 may occasionally trigger the first device 110 to perform GNSS measurements, e.g., via a media access control (MAC) control element (CE). Thus, the first device 110 in the RRC connected mode may reacquire GNSS position corrections through gaps, as triggered by the second device 120. In an example, the first device 110 may report the GNSS position correction duration of measurements during the initial access stage to the second device 120. During the connected mode, the first device 110 may report the GNSS validation period to the second device 120 via the MAC CE. Based on such reports, the second device 120 may trigger GNSS measurements for the first device 110. Alternatively, or in addition, if the first device 110 does not receive a trigger to make a GNSS measurement from the second device 120, the first device 110 may autonomously (if configured by the network) reacquire GNSS.

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

[0045] FIG. 2B illustrates an example scenario 220 in which GNSS measurements are performed during an RLF procedure, in accordance with some example embodiments of the present disclosure.

[0046] In scenario 220, because the first device 110 determined an OoS count of N310, after starting the T310 timer at time 225, the first device 110 may 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 be able to detect an IS indication and may not have an opportunity to count the IS before the expiration of T310.

[0047] In various exemplary embodiments, first device 110 may adjust at least one of the RLF process or the position measurement process to mitigate collisions between the two processes. For example, first device 110 may extend or pause the T310 timer and / or shift or postpone a configured measurement gap to avoid interrupting the RLF process with the measurement process.

[0048] Some exemplary embodiments of the present disclosure are described in detail below with reference to FIGS.

[0049] 3 shows a flowchart of an example method 300 according to some example embodiments of the present disclosure. Method 300 may be implemented in either first device 110 or second device 120, as shown in FIG. 1. For purposes of explanation, method 300 will be described from the perspective of first device 110 of FIG. 1.

[0050] In block 310, the first device 110 executes the RLF process. The RLF process may be executed when several conditions are met. For example, as shown in FIG. 2A, the first device 110 may determine an OoS count, and if the OoS count is greater than or equal to a threshold count (e.g., N310), the first device 110 may start a timer such as T310.

[0051] In block 320, the first device 110 performs a position measurement process, such as a GNSS measurement process, as needed. For example, the first device 110 may be scheduled by the network to perform the position measurement process, e.g., via a second device 120, such as a network device. Alternatively, or in addition, the first device 110 may be configured by the network to perform the position measurement process autonomously.

[0052] According to an exemplary embodiment of the present disclosure, if the two processes may collide with each other, at least one of the two processes is coordinated by the first device 110. The RLF process and the position measurement process may be performed by the first device 110 in any order. As an example, if the RLF process is postponed until the position measurement process is completed, the RLF process may be performed after the position measurement process. As another example, if the RLF process is paused before the start of the position measurement process and continued after the position measurement process is completed, the position measurement process may be performed during the entire RLF process. Alternatively, or in addition, if the position measurement process is shifted or postponed, the RLF process may be performed before the position measurement process.

[0053] The RLF process and / or the position measurement process may be coordinated in any suitable manner to mitigate collisions therebetween. In some demonstrative embodiments, the RLF process may be adjusted if it is likely to collide with the position measurement process. For example, if first device 110 determines that the position measurement process is imminent, first device 110 may determine the state of a timer, such as T310 (as shown in FIG. 3), for the RLF process and may make a corresponding adjustment.

[0054] An imminent positioning process may be determined if the first device 110 determines that a measurement gap used for the positioning process needs to start within a threshold time interval, such as a few seconds. The measurement gap may be scheduled by the network (e.g., via the second device 120) or may be autonomously triggered by the first device 110. The threshold time interval may be network configured or UE implemented.

[0055] In some demonstrative embodiments, first device 110 may determine whether a timer is running or not started. A running timer may mean that a predetermined number (e.g., N310) of OoS may have been detected and an IS may be evaluated. That is, the RLF process is initiated. In this case, first device 110 may adjust the timer and thus perform the RLF process based on the adjusted timer to mitigate collisions between the RLF process and the impending position measurement process.

[0056] The timer may be adjusted in any suitable manner. In some exemplary embodiments, the first device 110 may pause the timer during the position measurement process. For example, the timer may be paused at or before the start of a measurement gap, and the remaining portion of the timer may be continued when the measurement ends. In this way, the duration of the timer may bypass the measurement gap to avoid collisions between the RLF process and the position measurement process.

[0057] In some demonstrative embodiments, the first device 110 may extend the value of the timer to cover the length of the measurement gap. For example, the timer may be extended at the start of the measurement gap so that the timer cannot expire during the measurement gap, thereby avoiding collisions between the RLF process and the position 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 length of the timer may be three times or more the current length of the timer, e.g., 3 x currentT310.

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

[0059] By adjusting the timer, the RLF process and the position measurement process may be staggered. The first device 110 may continue to perform IS evaluation when the position measurement is completed according to the remaining time of the timer.

[0060] In some exemplary embodiments, the first device 110 may adjust the timer by taking the IS count into consideration. For example, the first device 110 may determine whether a condition is met that the IS count associated with the RLF process is greater than or equal to a threshold count (referred to as a "first threshold count") and less than a further threshold count (referred to as a "second threshold count") used to stop the timer (such as N311 shown in FIG. 2A). The first threshold count may be less than the second threshold count. If the condition is met, the first device 110 may consider that it has recovered from the radio problem at the start of the position measurement. In this case, the first device 110 may stop the timer. Therefore, a new OoS evaluation, i.e., determination of the OoS count, may be initiated after the measurement ends. If the condition is not met, the first device 110 may adjust the timer as described above.

[0061] In some demonstrative embodiments, the first device 110 may adjust a timer based on a comparison of the actual measurement time and a network-configurable measurement gap. For example, the first device 110 may determine the length of time required to perform the position measurement process, e.g., as the actual measurement time. The first device 110 may then determine whether a condition is met that the length of time is less than the length of the measurement gap. For example, the duration or length of the gap may be configured by the network, e.g., via the second device 120.

[0062] If this condition is met, the first device 110 may assume that a configured measurement gap margin exists before or after the measurement process ends. The first device 110 may use such margin for the RLF process. For example, the first device 110 may postpone the start of the position measurement process until the timer stops or the RLF process completes. If this condition is not met, the first device 110 may adjust the timer as described above.

[0063] To further separate the RLF process and the position measurement process, in some exemplary 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 met. The offset may be network-configured or UE-implemented. If met, which may mean the required time is significantly shorter than the configured time, the first device 110 may attempt to complete the RLF process before initiating the position measurement process. For example, the first device 110 may continue to count IS indications of recovery N311 or until the expiration of a timer such as T310.

[0064] In some demonstrative embodiments, the first device 110 may determine whether a condition is met that the remaining time on the timer is below a threshold time (referred to as the “first threshold time”) and the time until the start of the measurement gap is below a further threshold time (referred to as the “second threshold time”). The second threshold time is less than the first threshold time. If the condition is met, meaning that RLF will soon be declared and the RRC connection may be lost, the first device 110 may continue the RLF process without initiating a position measurement process at the start of the measurement gap. If the condition is not met, the first device 110 may adjust the timer as described above.

[0065] In some exemplary embodiments, first device 110 may also consider the IS count to make a decision regarding such continuation of the RLF process. For example, first device 110 may compare the IS count associated with the RLF process with a threshold count (referred to as the third threshold count). The third threshold count may be set according to the number of ISs, such as N311, for recovery. For example, the third threshold count may be much less than N311. If the IS count is less than the third threshold count, it may mean that first device 110 may have counted far fewer ISs and may therefore declare RLF, after which first device 110 may continue the RLF process.

[0066] If a timer such as T310 is otherwise paused, extended, or adjusted for a measurement gap, first device 110 may not be able to perform IS evaluation. Thus, in some exemplary embodiments, first device 110 may adjust IS evaluation associated with the RLF process accordingly. For example, IS evaluation may be paused during the position measurement process.

[0067] Alternatively, or in addition, the period of IS evaluation may be extended to cover the length of the measurement gap. The extension may be performed based on a configuration value, which may correspond to the measurement gap duration or a scaling factor. In some exemplary embodiments, this period extension 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 a further device (e.g., second device 120), which may be a network device or a terminal device. After the measurement gap is complete, first device 110 may fall back to the configured evaluation period, which may be based on, for example, T310 status and discontinuous reception (DRX) configuration.

[0068] In some demonstrative embodiments, the first device 110 may determine that the timer for the RLF process has not been started. In this case, the first device 110 may determine an OoS count to be used to start the timer. If the OoS count is non-zero, the first device 110 may reset the OoS count or hold the OoS count to continue after the position measurement process. The resetting or holding 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 so that the RLF process may not collide with the position measurement.

[0069] An exemplary process for adjusting the RLF process is described below with reference to FIG.

[0070] 4 shows a flowchart of an example process 400 for coordinating RLF processes at first device 110, according to some example embodiments of the present disclosure. In this example, GNSS measurements may be performed by first device 110 as an example of location measurements.

[0071] 4, at 402, the first device 110 may determine that a GNSS measurement gap is about to start, for example, within 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 as a UE. At 404, the first device 110 may determine whether a timer, such as T310, for the RLF process is running. If T310 is running, the first device 110 may adjust the T310 timer and stop IS evaluation when the GNSS measurement gap starts.

[0072] The timer may be adjusted in two optional ways. Option A is shown at 406, where the T310 timer may be paused until the GNSS measurements end. For example, the first device 110 may pause the T310 timer at the start of the GNSS measurement gap and continue the remaining portion of the T310 timer when the GNSS measurements end. Option B is shown at 408, where the T310 timer may be extended to cover the length of the GNSS measurement gap. For example, the UE may extend T310 at the start of the GNSS measurement gap so that the T310 timer cannot expire during the GNSS measurement gap.

[0073] After the timer is adjusted, the first device 110 may start GNSS measurements at 410. At 412, the first device 110 may determine whether the GNSS measurements have ended. If yes, the first device 110 may continue radio link monitoring (RLM). For example, the first device 110 may continue to evaluate the IS when the GNSS measurements have ended according to the remaining time on the T310 timer.

[0074] In an exemplary embodiment, the first device 110 may evaluate the number of ISs and determine whether any ISs have already been detected during T310. In 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, that stops T310. If yes, the first device 110 may be considered to have recovered from the radio problem at the start of the GNSS measurements and may therefore begin a new evaluation, e.g., a new count of OoS after the GNSS measurements end. Then, in 418, the first device 110 may stop T310 if GNSS measurements are imminent. If no, option A or B may be implemented.

[0075] In an example embodiment, at 420, the first device 110 may determine if the time required to perform the GNSS measurements is less than the configured GNSS measurement gap, and if yes, 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 measurements. If no, option A or B may be implemented.

[0076] In an example embodiment, at 424, the first device 110 may determine whether the time remaining in T310 is below a (network-configured) threshold time labeled thr2 and the time until the start of a GNSS measurement gap is below a threshold time labeled thr3, where thr2 > thr3. If yes, the first device 110 may continue the IS evaluation period instead of initiating a GNSS measurement gap because it would likely lose the RRC connection (e.g., at 428) because it would immediately declare an RLF.

[0077] This decision may also depend on the number of ISs already counted if N311 is different from 1. As shown in FIG. 4, at 426, the first device 110 may determine whether the count number of ISs, labeled #IS, is much less than N311. If yes, at 428, the first device 110 may complete an RLF procedure instead of GNSS measurements. For example, the first device 110 may make this decision if N311 is 10 but the first device 110 has too few counted ISs to declare an RLF.

[0078] In an exemplary embodiment, at 404, if it is determined that T310 is not running, but the first device 110 has a non-zero number of counted OoSs, the first device 110 may continue counting after the GNSS measurement gap or may reset the count. This may also depend on whether the number of OoSs is above or below a (network-configured) threshold. As shown in FIG. 4, at 430, the first device 110 may determine whether the count number of OoSs labeled #OoS exceeds a threshold count labeled thr4. If yes, at 432, the first device 110 may continue the #OoS count after the GNSS measurement. If no, at 434, the first device 110 may reset the #OoS count. In an example, the first device 110 may be configured to either retain the current OoS / IS count and continue counting after the GNSS measurement gap, or to reset the OoS / IS count upon completion of the GNSS measurement gap.

[0079] In addition to or instead of the RLF process, the first device 110 may adjust the position measurement process to mitigate collisions between the two processes. In some exemplary embodiments, the first device 110 may adjust the measurement gap to mitigate collisions. Some exemplary embodiments in this regard are described below with reference to FIGS. 5 and 6.

[0080] 5 shows a flowchart of an example process 500 for adjusting a measurement gap, according to some example embodiments of the present disclosure. Process 500 may be performed by first device 110. For purposes of explanation, process 500 will be described from the perspective of first device 110 of FIG. 1.

[0081] 5, in block 510, first device 110 may detect an early out-of-sync (or "early de-sync") event associated with the RLF process. In block 520, first device 110 may adjust a measurement gap of the position measurement process to mitigate collisions. In block 530, first device 110 may perform the position measurement process based on the adjusted measurement gap.

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

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

[0084] In some demonstrative embodiments, first device 110 may adjust the measurement gap in consideration of an in-early-sync (or "early-sync") event, which may mean that first device 110 has nearly recovered from a radio link problem. For example, first device 110 may consider shifting or postponing the measurement gap after detecting an "early-sync" event associated with the RLF process.

[0085] An “early-syncing” event may also be reported to the network. For example, if an “early-syncing” event is detected, first device 110 may initiate transmission of a UEAssistanceInformation message to report the event to the network. In some demonstrative embodiments, in response to detecting the “early-syncing” event, first device 110 may transmit an RLM report of the “early-syncing” event (referred to as a second RLM report) to a further device (such as second device 120), which may be a network device or a terminal device. Upon transmission of the second RLM report, first device 110 may adjust a measurement gap.

[0086] 6 shows a flowchart of an example process 600 for adjusting a measurement gap in accordance with some other example embodiments of the present disclosure. Process 600 may be performed by second device 120. For purposes of explanation, process 600 will be described from the perspective of second device 120 of FIG. 1.

[0087] 6, in block 610, the second device 120 may receive a first radio link monitoring report of an early out-of-sync event or a second radio link monitoring report of an early in-sync event from an additional device, such as the first device, where the early out-of-sync event and the early in-sync event are associated with an RLF process performed by the additional device.

[0088] In block 620, the second device 120 may transmit to the further device a configuration of a shift time of the measurement gap of the position measurement process performed by the further device to mitigate collisions between the RLF process and the position measurement process.

[0089] All operations and features relating to the second device 120 and network described above with reference to Figures 3-5 are equally applicable to the process 600 and have similar effect, and details are omitted for the sake of brevity.

[0090] In some demonstrative embodiments, an apparatus capable of performing either method 300 or process 500 (e.g., first apparatus 110 of FIG. 1 ) may comprise means for performing the respective operations of method 300 and process 500. The means may be implemented in any suitable manner. For example, the means may be implemented in a circuit or a software module. The apparatus may be implemented as or included in first apparatus 110 of FIG. 1 .

[0091] In some demonstrative embodiments, an apparatus includes means for performing a radio link failure process and means for performing a position measurement process, wherein at least one of the radio link failure process or the position measurement process is adjusted to mitigate collisions between the radio link failure process and the position measurement process.

[0092] In some demonstrative embodiments, the means for executing the radio link failure process includes means for determining whether a timer for the radio link failure process is running or not started based on a determination that a measurement gap for the positioning process should start within a threshold time interval, means for adjusting the timer to mitigate collisions based on a determination that the timer is running, and means for executing the radio link failure process based on the adjusted timer.

[0093] In some exemplary embodiments, the means for adjusting the timer includes means for pausing the timer during the position determination process.

[0094] In some exemplary embodiments, the means for adjusting the timer includes means for extending the value of the timer to cover the length of the measurement gap.

[0095] In some exemplary embodiments, the timer is extended based on a first configuration from the further device to a first extension time of the timer.

[0096] In some demonstrative embodiments, the means for adjusting the timer includes means for determining whether a condition is met that an in-sync count associated with the radio link failure process is greater than or equal to a first threshold count and less than a second threshold count used to stop the timer, where the first threshold count is less than the second threshold count; and means for adjusting the timer based on a determination that the condition is not met.

[0097] In some exemplary embodiments, the apparatus further includes means for stopping the timer upon determining that the condition is met.

[0098] In some demonstrative embodiments, the means for adjusting the timer includes means for determining a length of time necessary to perform a position measurement process, means for determining whether a condition is met that the length of time is less than a length of a measurement gap, and means for adjusting the timer based on a determination that the condition is not met.

[0099] In some demonstrative embodiments, the apparatus further includes means for postponing initiation of the position measurement process until the timer stops or the radio link failure process is completed based on a determination that the condition is met.

[0100] In some demonstrative embodiments, the means for adjusting the timer includes means for determining whether a condition is met that the time remaining on the timer is less than a first threshold time and the time until the start of the measurement gap is less than a second threshold time, where the second threshold time is less than the first threshold time, and means for adjusting the timer based on a determination that the condition is not met.

[0101] In some demonstrative embodiments, the apparatus further includes means for continuing the radio link failure process without initiating the position measurement process at the start of the measurement gap based on a determination that the condition is met.

[0102] In some demonstrative embodiments, the means for continuing the radio link failure process includes means for comparing the in-sync count to a third threshold count, the in-sync count being associated with the radio link failure process, the third threshold count being less than a second threshold count used to stop the timer, and means for continuing the radio link failure process based on a determination that the in-sync count is below the third threshold count.

[0103] In some exemplary embodiments, the apparatus further includes means for adjusting an in-sync evaluation associated with the radio link failure process.

[0104] In some exemplary embodiments, the means for adjusting the intra-sync evaluation includes means for pausing the intra-sync evaluation during the position determination process.

[0105] In some exemplary embodiments, the means for adjusting the in-sync evaluation includes means for extending the period of the in-sync evaluation to cover the length of the measurement gap.

[0106] In some exemplary embodiments, the period of in-sync evaluation is extended based on a second configuration from the further device to a second extension time of the period.

[0107] In some demonstrative embodiments, the apparatus further includes means for determining, based on a determination that the timer has not been started, an out-of-sync count to be used to start the timer, and means for resetting the out-of-sync count or keeping the out-of-sync count continued after the position measurement process, based on a determination that the out-of-sync count is non-zero.

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

[0109] In some demonstrative embodiments, the means for performing the position measurement process includes means for adjusting a measurement gap of the position measurement process to mitigate collisions after detecting an early out-of-sync event associated with the radio link failure process, and means for performing the position measurement process based on the adjusted measurement gap.

[0110] In some exemplary embodiments, the means for adjusting the measurement gap includes means for shifting or postponing the measurement gap.

[0111] In some exemplary embodiments, the measurement gap is shifted based on a third configuration from the additional device to the shift time of the measurement gap.

[0112] In some demonstrative embodiments, the means for performing the position measurement process further includes means for transmitting a first radio link monitoring report of the early out-of-sync event to the further device in response to detecting the early out-of-sync event, and the third configuration is received in response to transmitting the first radio link monitoring report.

[0113] In some exemplary embodiments, the means for adjusting the measurement gap includes means for adjusting the measurement gap after detecting an early in-sync event associated with a radio link failure process.

[0114] In some demonstrative embodiments, the means for adjusting the measurement gap includes means for transmitting a second radio link monitoring report of the early intra-sync event to the further device in response to detecting the early intra-sync event, and means for adjusting the measurement gap upon transmission of the second radio link monitoring report.

[0115] In some exemplary embodiments, the apparatus further includes means for performing other operations in method 300 or process 500 or some exemplary embodiments of first device 110. In some exemplary embodiments, the means includes at least one processor and at least one memory that stores instructions, which when executed by the at least one processor, cause execution of the apparatus.

[0116] In some demonstrative embodiments, an apparatus capable of performing any of process 600 (e.g., second apparatus 120 of FIG. 1 ) may include means for performing each operation of process 600. The means may be implemented in any suitable manner. For example, the means may be implemented in a circuit or a software module. The apparatus may be implemented as or included in second apparatus 120 of FIG. 1 .

[0117] In some demonstrative embodiments, the apparatus includes means for receiving from the further apparatus a first radio link monitoring report of an early out-of-sync event or a second radio link monitoring report of an early in-sync event, where the early out-of-sync event and the early in-sync event are associated with a radio link failure process performed by the further apparatus, and means for transmitting to the further apparatus a configuration of a measurement gap shift time of the positioning process performed by the further apparatus to mitigate collisions between the radio link failure process and the positioning process.

[0118] In some exemplary embodiments, the apparatus further includes means for performing process 600 or other operations in some exemplary embodiments of second device 120. In some exemplary embodiments, the means includes at least one processor and at least one memory that stores instructions, which when executed by the at least one processor, cause execution of the apparatus.

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

[0120] The communications module 740 is for two-way communication. The communications module 740 has one or more communications interfaces to facilitate communication with one or more other modules or devices. The communications interfaces may represent any interface necessary for communication with other network elements. In some demonstrative embodiments, the communications module 740 may include at least one antenna.

[0121] The processor 710 may be of any type suitable for a local technology network and may include, by way of non-limiting example, one or more of 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. The device 700 may have multiple processors, such as application specific integrated circuit chips that are time-slaved to a clock that synchronizes the main processor.

[0122] The memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memory 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 memory include, but are not limited to, random access memory (RAM) 722 and other volatile memory that does not persist while power is off.

[0123] The computer program 730 includes computer-executable instructions that are executed by the associated processor 710. The instructions of the program 730 may include instructions for performing the operations / acts of some example embodiments of the present disclosure. The program 730 may be stored in a memory, such as the ROM 724. The processor 710 can load the program 730 into the RAM 722 to perform any appropriate operations and processes.

[0124] An exemplary embodiment of the present disclosure may be implemented by a program 730 such that the apparatus 700 can execute any of the processes of the present disclosure described with reference to Figures 3 to 6. An exemplary embodiment of the present disclosure may also be implemented by hardware or a combination of software and hardware.

[0125] In some exemplary embodiments, the program 730 may be tangibly contained in a computer-readable medium that may be included in the device 700 (such as memory 720) or in other storage accessible by the device 700. The device 700 may load the program 730 from the computer-readable medium into RAM 722 for execution. In some exemplary 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 not a limitation regarding the permanence of the data storage (e.g., RAM vs. ROM), but rather a limitation of the medium itself (i.e., tangible as opposed to a signal).

[0126] 8 shows an example of a computer readable medium 800, 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.

[0127] In general, various embodiments of the present disclosure may be implemented in hardware or special purpose 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. While various aspects of the embodiments of the present disclosure have been illustrated and described as block diagrams, flowcharts, or using some other graphical representations, it should be understood that the blocks, apparatus, systems, techniques, or methods described herein may be implemented, by way of non-limiting example, in hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing device, or some combination thereof.

[0128] Some exemplary embodiments of the present disclosure also provide at least one computer program product tangibly stored on a computer-readable medium, such as a non-transitory computer-readable medium. The computer program product includes computer-executable instructions, such as those included in program modules, that execute on a target physical or virtual processor device to perform any of the methods described above. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split among program modules as desired in various embodiments. The machine-executable instructions of a program module may be executed in a local device or in a distributed device. In a distributed device, the program modules may be located in both local and remote storage media.

[0129] Program code for performing the methods 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 apparatus such that, when executed by the processor or controller, the program code causes the functions / acts specified in the flowcharts and / or block diagrams to be performed. The program code may run 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.

[0130] In the context of the present disclosure, computer program code or associated data may be carried by any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations as described above, examples of which include a signal, a computer-readable medium, and the like.

[0131] 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, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of computer-readable storage media may include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0132] Furthermore, while operations are shown in a particular order, this should not be understood as requiring such operations to be performed in the particular order or sequentially shown, or to perform all of the illustrated operations, to achieve desirable results. In certain situations, multitasking and parallel processing may be advantageous. Similarly, while details of several specific implementations are included in the foregoing description, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features that may be unique to particular embodiments. Unless explicitly stated otherwise, certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, unless explicitly stated otherwise, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable subcombination.

[0133] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it is to be understood that the present disclosure, as defined in the appended claims, is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. at least one processor; at least one memory for storing instructions; wherein the instructions, when executed by the at least one processor, cause at least performing a radio link failure process; performing a location determination process; causing the device to execute The apparatus, wherein at least one of the radio link failure process or the position measurement process is coordinated to mitigate collisions between the radio link failure process and the position measurement process.

2. performing the radio link failure process determining whether a timer for the radio link failure process is running or not started based on a determination that a measurement gap for the positioning process should start within a threshold time interval; adjusting the timer to mitigate the collision based on a determination that the timer is running; performing the radio link failure process based on the adjusted timer; The apparatus of claim 1 , comprising:

3. The apparatus of claim 2 , wherein adjusting the timer includes pausing the timer during the location determination process.

4. The apparatus of claim 2 , wherein adjusting the timer comprises extending the value of the timer to cover the length of the measurement gap.

5. The device of claim 4 , wherein the timer is extended based on a first configuration from a further device to a first extension time of the timer.

6. adjusting the timer comprises determining whether a condition is met that an in-sync count associated with the radio link failure process is greater than or equal to a first threshold count and less than a second threshold count used to stop the timer, wherein the first threshold count is less than the second threshold count; adjusting the timer based on a determination that the condition is not satisfied; and The apparatus according to any one of claims 2 to 5, comprising:

7. The apparatus of claim 6 , wherein the apparatus is further configured to stop the timer upon determining that the condition is met.

8. adjusting the timer determining the length of time required to perform the location determination process; determining whether a condition is met that the time length is less than the length of the measurement gap; adjusting the timer based on a determination that the condition is not satisfied; The apparatus according to any one of claims 2 to 7, comprising:

9. 9. The apparatus of claim 8, wherein the apparatus is further configured to postpone initiation of the position measurement process until stopping the timer or completion of the radio link failure process based on determining that the condition is met.

10. adjusting the timer determining whether a condition is met in which the remaining time on the timer is less than a first threshold time and the time to a start of the measurement gap is less than a second threshold time, the second threshold time being less than the first threshold time; adjusting the timer based on a determination that the condition is not satisfied; and The apparatus according to any one of claims 2 to 9, comprising:

11. 11. The apparatus of claim 10, wherein the apparatus is further configured to, based on a determination that the condition is met, continue the radio link failure process without initiating the position measurement process at the start of the measurement gap.

12. Continuing the radio link failure process includes: comparing an in-sync count to a third threshold count, the in-sync count being associated with the radio link failure process, the third threshold count being less than a second threshold count used to stop the timer; continuing the radio link failure process based on a determination that the in-sync count is less than the third threshold count; The apparatus of claim 11 , comprising:

13. The device according to any of claims 2 to 12, wherein said device is further adapted to adjust an in-sync evaluation associated with said radio link failure process.

14. The apparatus of claim 13 , wherein adjusting the in-sync evaluation comprises pausing the in-sync evaluation during the position determination process.

15. The apparatus of claim 13 , wherein adjusting the in-sync evaluation comprises extending a period of the in-sync evaluation to cover the length of the measurement gap.

16. The device of claim 15 , wherein the period of the in-sync evaluation is extended based on a second configuration from a further device to a second extension of the period.

17. The apparatus further comprises: determining an out-of-sync count to be used to start the timer based on a determination that the timer has not been started; 17. The apparatus of claim 2, further comprising: based on a determination that the out-of-sync count is non-zero, resetting the out-of-sync count or keeping the out-of-sync count continued after the position determination process.

18. 18. The apparatus of claim 17, wherein the resetting or holding is performed based on a determination that the out-of-sync count is less than or equal to a fourth threshold count.

19. performing the position determination process, adjusting a measurement gap of the positioning process to mitigate the collisions after detecting an early out-of-sync event associated with the radio link failure process; performing the position measurement process based on the adjusted measurement gap; 19. The apparatus of any preceding claim, comprising:

20. 20. The apparatus of claim 19, wherein adjusting the measurement gap comprises shifting or postponing the measurement gap.

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

22. performing the position determination process further includes, in response to the detection of the early out-of-sync event, sending to the further device a first radio link monitoring report of the early out-of-sync event; 22. The apparatus of claim 21, wherein the third configuration is received in response to transmitting the first radio link monitoring report.

23. The apparatus of any of claims 19 to 22, wherein adjusting the measurement gap comprises adjusting the measurement gap after detecting an early in-sync event associated with the radio link failure process.

24. adjusting the measurement gap In response to the detection of the early intra-sync event, transmitting a second radio link monitoring report of the early intra-sync event to a further device; adjusting the measurement gap at the time of the transmission of the second radio link monitoring report; 24. The apparatus of claim 23, comprising:

25. at least one processor; at least one memory for storing instructions; wherein the instructions, when executed by the at least one processor, cause at least receiving, from a further device, a first radio link monitoring report of an early out-of-sync event or a second radio link monitoring report of an early in-sync event, the early out-of-sync event and the early in-sync event being associated with a radio link failure process executed by the further device; transmitting to the further device a configuration of a measurement gap shift time of the position measurement process executed by the further device in order to mitigate collisions between the radio link failure process and the position measurement process; The device causes the device to execute the above.

26. 1. A method comprising: In the apparatus, performing a radio link failure process; performing a location determination process; Including, The method, wherein at least one of the radio link failure process or the position measurement process is coordinated to mitigate collisions between the radio link failure process and the position measurement process.

27. performing the radio link failure process determining whether a timer for the radio link failure process is running or not started based on a determination that a measurement gap for the positioning process should start within a threshold time interval; adjusting the timer to mitigate the collision based on a determination that the timer is running; performing the radio link failure process based on the adjusted timer; 27. The method of claim 26, comprising:

28. 28. The method of claim 27, wherein adjusting the timer includes pausing the timer during the location determination process.

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

30. 30. The method of claim 29, wherein the timer is extended based on a first configuration from a further device to a first extension time of the timer.

31. adjusting the timer determining whether a condition is met that an in-sync count associated with the radio link failure process is greater than or equal to a first threshold count and less than a second threshold count used to stop the timer, wherein the first threshold count is less than the second threshold count; adjusting the timer based on a determination that the condition is not satisfied; and The method of any one of claims 27 to 30, comprising:

32. 32. The method of claim 31, wherein the device is further configured to stop the timer based on a determination that the condition is met.

33. adjusting the timer determining the length of time required to perform the location determination process; determining whether a condition is met that the time length is less than the length of the measurement gap; adjusting the timer based on a determination that the condition is not satisfied; The method of any one of claims 27 to 32, comprising:

34. 34. The method of claim 33, wherein the device is further configured to postpone initiation of the position measurement process until stopping the timer or completion of the radio link failure process based on determining that the condition is met.

35. adjusting the timer determining whether a condition is met in which the remaining time on the timer is less than a first threshold time and the time to a start of the measurement gap is less than a second threshold time, the second threshold time being less than the first threshold time; adjusting the timer based on a determination that the condition is not satisfied; and The method of any one of claims 27 to 34, comprising:

36. 36. The method of claim 35, wherein the device is further configured to, based on determining that the condition is met, continue the radio link failure process without initiating the position measurement process at the start of the measurement gap.

37. Continuing the radio link failure process includes: comparing an in-sync count to a third threshold count, the in-sync count being associated with the radio link failure process, the third threshold count being less than a second threshold count used to stop the timer; continuing the radio link failure process based on a determination that the in-sync count is less than the third threshold count; 37. The method of claim 36, comprising:

38. The method according to any of claims 27 to 35, wherein the device is further adapted to adjust an in-sync evaluation associated with the radio link failure process.

39. 39. The method of claim 38, wherein adjusting the in-sync evaluation comprises pausing the in-sync evaluation during the position determination process.

40. 39. The method of claim 38, wherein adjusting the in-sync evaluation comprises extending a period of the in-sync evaluation to cover the length of the measurement gap.

41. 41. The method of claim 40, wherein the period of the in-sync evaluation is extended based on a second configuration from a further device to a second extension of the period.

42. The apparatus further comprises: determining an out-of-sync count to be used to start the timer based on a determination that the timer has not been started; resetting the out-of-sync count or keeping the out-of-sync count continued after the position determination process based on a determination that the out-of-sync count is non-zero; The method according to any one of claims 27 to 41.

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

44. performing the position determination process, adjusting a measurement gap of the positioning process to mitigate the collisions after detecting an early out-of-sync event associated with the radio link failure process; performing the position measurement process based on the adjusted measurement gap; The method of any one of claims 26 to 43, comprising:

45. 45. The method of claim 44, wherein adjusting the measurement gap comprises shifting or postponing the measurement gap.

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

47. performing the position determination process further includes, in response to the detection of the early out-of-sync event, sending to the further device a first radio link monitoring report of the early out-of-sync event; 47. The method of claim 46, wherein the third configuration is received in response to transmitting the first radio link monitoring report.

48. A method according to any of claims 44 to 47, wherein adjusting the measurement gap comprises adjusting the measurement gap after detecting an early in-sync event associated with the radio link failure process.

49. adjusting the measurement gap In response to the detection of the early intra-sync event, transmitting a second radio link monitoring report of the early intra-sync event to a further device; adjusting the measurement gap at the time of the transmission of the second radio link monitoring report; 49. The method of claim 48, comprising:

50. 1. A method comprising: In the apparatus, receiving, from a further device, a first radio link monitoring report of an early out-of-sync event or a second radio link monitoring report of an early in-sync event, the early out-of-sync event and the early in-sync event being associated with a radio link failure process executed by the further device; transmitting to the further device a configuration of a measurement gap shift time of the position measurement process executed by the further device in order to mitigate collisions between the radio link failure process and the position measurement process; The method comprising:

51. means for performing a radio link failure process; means for performing a position determination process; An apparatus comprising: The apparatus, wherein at least one of the radio link failure process or the position measurement process is coordinated to mitigate collisions between the radio link failure process and the position measurement process.

52. 1. An apparatus comprising: means for receiving, from a further device, a first radio link monitoring report of an early out-of-sync event or a second radio link monitoring report of an early in-sync event, the early out-of-sync event and the early in-sync event being associated with a radio link failure process executed by the further device; means for transmitting to said further device a configuration of a shift time of a measurement gap of said position measurement process executed by said further device in order to mitigate collisions between said radio link failure process and said position measurement process; The device comprising:

53. A computer readable medium comprising instructions, on which the instructions are stored, for causing an apparatus to perform at least the method of any of claims 26 to 49 or claim 50.

Images