Methods to indicate global navigation satellite system (GNSS) inference detection to impacted entities operating in cellular network

Abstract

A method, system and apparatus are disclosed for detecting and reporting interference issues that impact entities in a cellular network. In some embodiments a method implemented in a user equipment (UE) (22) that is configured to communicate with a network node (16), is provided. The method includes determining an existence of an interference issue related to a satellite navigation system signal, and reporting the interference issue to a location management function (LMF) node (15).

Description

[0001] METHODS TO INDICATE GLOBAL NAVIGATION SATELLITE SYSTEM (GNSS) INFERENCE DETECTION TO IMPACTED ENTITIES OPERATING IN CELLULAR NETWORK

[0002] TECHNICAL FIELD

[0003] The present disclosure relates to wireless communications, and in particular, to detecting and reporting interference issues that impact entities in a cellular network.

[0004] BACKGROUND

[0005] The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile user equipments (UE), as well as communication between network nodes and between UEs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

[0006] Positioning in 4G / LTE / Evolved Packet Core (EPC) and 5G / NR / 5GC is supported by the architecture in FIG. 1, with direct interactions between a user equipment (UE) and a location server 2 via an LTE Positioning Protocol (LPP). Moreover, there are also interactions between the location server 2 and a serving radio base station (BS) 4 (e.g., network node) via the LPPa protocol, to some extent supported by interactions between the radio base station 4 and the UE via a Radio Resource Control (RRC) protocol. The radio base station 4 interacts with a mobility network entity (MNE) 6 via a first interface protocol (also referred to as a “1stinterface”), and the mobility network entity 6 interacts with the location server 2 via a second interface protocol (also referred to as a “2ndinterface”). In some applications, the location server 2 interacts with a Global Navigation Satellite System (GNSS) correction data provider (CDP) 8 via a third interface protocol (also referred to as a “3rdinterface”).

[0007] In 3 GPP LTE, 4G / LTE / EPC and 5G / NR / 5GC, the servers / nodes / functions / interfaces / protocols are named as follows:

[0008]

[0009]

[0010] In both cases, the location server 2 can also be interacting with the UE directly over user plane communication carrying LPP with signaling defined by Open Mobile Alliance (OMA) Secure UserPlane Location (SUPL) or some other user plane signaling. In case of SUPL, the location server 2 is denoted SUPL Location Platform (SLP) and the UE is denoted SUPL Enabled Terminal (SET).

[0011] There are several options for the interface, signaling and message handling over the third interface between the location server 2 and a correction data provider 8. One option is message handling defined by a Radio Technical Commission for Maritime (RTCM) special committee with the user plane signaling protocol Networked Transport of RTCM via Internet Protocol (NTRIP). RTCM SC initially defined differential corrections to GNSS.

[0012] 3GPP Release 9 (Rel 9) introduced support for assisted Global Navigation Satellite System (GNSS), and the scope of the assistance data has been refined over the releases. In Release (Rel 15), support for Real Time Kinematics (RTK) GNSS was introduced. The assistance data is generated based on observations from one or more reference stations, where a reference station is a node with known position and known antenna configuration, and a GNSS receiver capable of measuring signals from one or more satellite systems, where the satellite systems comprise one or more satellites, and each satellite transmits one or more signals. Typically, the GNSS RTK assistance data is provided by a separate function, correction data provider or NRTK server.

[0013] GNSS represents a generic system, with examples GPS, GLONASS, GALILEO and BeiDou. These systems are based on a number of GNSS satellites, each transmitting GNSS signals associated to a specific GNSS signal identity. The satellites follow tailored orbits around the globe.

[0014] FIG. 2 illustrates the different 4G / LTE / EPC and 5G / NR / 5GC entities in another architecture, including , a home subscriber system (HSS), unified data management (UDM), location service (LCS) client, Gateway Mobile Location Center (GMLC), mobility management entity (MME), Enhanced Serving Mobile Location Center (E-SMLC), Evolved Universal UMTS Terrestrial Radio Access Network (E-UTRAN), network exposure function (NEF), location management function (LMF), application function (AF), access and mobility management function (AMF) and radio access network (RAN).

[0015] 5G positioning methods based on 5G signals is realized with downlink positioning reference signals, associated to a specific radio resource, which may be transmitted using a radio beam with directivity. Each positioning reference signal is associated to an identifier. One or more such signals are transmitted from a specific transmission point associated to a radio base station.

[0016] Positioning methods rely on measurements, and several positioning methods rely on device measurements of GNSS signals, WiFi signals, Bluetooth signals, beacon signals, RAT-dependent signals, etc. Such device measurements are subject to errors or feared events, and a subset of such errors or feared events are due to the local environment of the device.

[0017] FIG. 3 illustrates one typical example of an interference issue or error or feared event - multipath signal propagation. On the left side, some GNSS signals are received via a line of sight path and some via a reflected non-line of sight path. The right side of FIG.

[0018] 3 illustrates a similar situation for a terrestrial radio network, where some signals are received via a line of sight path and some via a reflected non-line of sight path. The time of flight of a non-line-of-sight signal does not reflect the distance between the transmitter and device, leading to a measurement error due to the local environment of the device.

[0019] Other examples of local environment measurement issues are, but not limited to: unintentional interference from other radio transmitters;

[0020] intentional interference from other radio transmitters, often denoted jamming; intentional fake radio signals to lure the device to measure radio signal time of flight not corresponding to reality, often referred to as spoofing.

[0021] FIG. 4 depicts the overall 5G RAN (NG-RAN) architecture. The NG-RAN includes a set of gNBs (e.g., network nodes) connected to the 5G core network via an NG interface. The gNBs are interconnected via the Xn interface. A gNB may consist of a gNB-CU (Central Unit) and one or more gNB-DUs (Distribution Unit). The gNB-CU unit and a gNB-DU units are connected with an Fl logical interface. One gNB-DU is connected to one gNB-CU. NG, Xn, and Fl represent logical interfaces.FIG. 5 depicts a gNB with split architecture. Here, the gNB-CU hosts the RRC and the control plane part of the PDCP; the gNB-DU hosts the RLC, MAC and physical layer.

[0022] GNSS signals are used by a base station as a source of synchronization. Similarly, the UEs performing Sidelink operation out of cellular coverage also use GNSS signals as a reference source for synchronization. However, if GNSS signals are spoofed or jammed, it would impact the cellular network entities such as base stations and UEs which rely upon GNSS for synchronization.

[0023] Hence, existing systems suffer from various issues that may impact cellular network entities.

[0024] SUMMARY

[0025] Some embodiments advantageously provide methods, systems, and apparatuses for detecting and reporting interference issues (GNSS signal outage, temporary loss, spoofing, jamming, etc.) that impact entities in a cellular network.

[0026] In some embodiments, an LMF informs the network node (gNBs) via a standardized interface (NRPPa) on the GNSS as to the existence of jamming and / or spoofing whereby the gNB can change its synchronization source if they rely upon that GNSS signal.

[0027] In some embodiments, the gNB informs out-of-coverage UEs via preconfiguration or broadcast. In some cases, the broadcast is relayed to out-of-coverage UEs using a relay UE.

[0028] In some embodiments, when the gNB serves UEs via a satellite, the UE-provided location upon registration may be needed to be verified by the gNB. If the gNB uses GNSS to verify the UE location, the verification will not be correct.

[0029] Some embodiments provide arrangements where the LMF informs the base network nodes via a standardized interface (NRPPa) about the existence of GNSS spoofing and / or jamming whereby the network nodes change their synchronization source if the network nodes rely upon that GNSS signal.

[0030] In some embodiments, the network nodes further inform the out-of-coverage UEs via preconfiguration or broadcast. In some embodiments, the broadcast is relayed to the out-of-coverage UE using a relay UE.

[0031] In some embodiments, when the network node serves UEs via a satellite and the UE provides location upon Registration, the UE location may need to be verified by the network node. If the network node uses GNSS to verify the UE location, the verificationmay not be correct. In some embodiments, the indication of GNSS spoofing and / or jamming is also indicated to the gNB-DU via an Fl interface, where the source of synchronization is located at the DU part of the network node. In some embodiments, the indication is also signaled from the AMF to the network node via the NG interface.

[0032] In some embodiments, when the LMF determines that there is GNSS spoofing and / or jamming, it determines which GNSS-ID frequency is impacted and reports it to other NW nodes such as AMF, network node (gNB), etc. The network node may broadcast such impacted nodes as part of the Public Warning System System Information Block (PWS SIB) or inform via dedicated signaling or via SIB-12 or SIB-23 (as defined in TS 38.331 vs 18.3.0) for out of coverage UEs which use GNSS as their synchronization source.

[0033] In some embodiments, whether there is jamming, spoofing or any GNSS synchronization-related error (e.g., deviation), the LMF notifies the other network nodes with a confidence level. For example, the content in the table below from LPP (TS 37.355 v 18.3.0) can be used in NRPPa to denote which GNSS ID and GNSS frequencies are impacted.

[0034] The LMF may also determine a confidence level on the GNSS spoofing / jamming based upon different factors. In some embodiments, the confidence level is determined by how many numbers of UEs have reported such an issue. For example, if only one or very few UEs have reported the issue, the confidence may be low. However, if many UEs provide feedback then the confidence is larger. Thus, the confidence can be directly proportional to the number of feedback messages received.

[0035] In some embodiments, the confidence level can be based upon how frequently the feedback on interference arises. For example, if multiple users respond within a certain short time interval, the confidence can be high. In some embodiments, the UEs may include the timestamp that the interference was detected and / or the duration until the interference was detected. The LMF may use this information to inform the AMF / network nodes (gNBs) so these network nodes can gauge the severity of the problem and take necessary remedies / actions.

[0036] Common GNSS Information Elements

[0037] GNSS-FrequencylD

[0038] The IE GNSS -Frequency ID is used to indicate a specific GNSS link / frequency. The interpretation of GNSS Frequency ID depends on the GNSS ID.

[0039] For example:- ASN1 START

[0040] GNSS-FrequencyID-rl5 ::= SEQUENCE {

[0041] gnss-FrequencyID-rl5 INTEGER (0 .. 7),

[0042] - ASN1STOP

[0043] GNSS-FrequencylD field descriptions

[0044] gnss -Frequency ID

[0045] This field specifies a particular GNSS link / frequency. The interpretation of gnss- FrequencylD depends on the GNSS ID and is as shown in the Value & Explanation relation table below:

[0046] Value & Explanation relation

[0047]

[0048]

[0049] In accordance with one aspect of the present disclosure, a network node configured to communicate with a UE is provided. The network node is configured to receive from nan LMF node, an indication of an interference issue. The network node is furtherconfigured to, in response to the indication of the interference issue, perform at least one action.

[0050] In some embodiments of this aspect, the at least one action includes changing its synchronization source.

[0051] In some embodiments, the at least one action includes notifying an out-of-coverage UE of the interference issue.

[0052] In some embodiments, the network node is further configured to verify a location of the out-of-coverage UE before notifying the out-of-coverage UE of the interference issue.

[0053] In some embodiments, the interference issue is associated with a Global Navigation Satellite System (GNSS) signal.

[0054] In some embodiments, the interference issue is associated with a clock accuracy error or a timing error of the GNSS signal.

[0055] In some embodiments, the indication of the interference issue received from the LMF node includes at least one of frequency, band, satellite vehicle ID (SV-ID), Global Navigation Satellite System Identification (GNSS ID), and clock accuracy error.

[0056] In some embodiments, the indication from the LMF node includes a confidence level.

[0057] In some embodiments, the confidence level is determined by how many UEs have reported the interference issue.

[0058] In some embodiments, the interference issue is one or more of intentional interference from other radio transmitters, intentional fake radio signals, spoofing, jamming and feared events.

[0059] In accordance with another aspect of the present disclosure, a method implemented in a network node that is configured to communicate with a UE, is provided. The method includes receiving, from an LMF node, an indication of an interference issue, and in response to the indication of the interference issue, performing at least one action.

[0060] In some embodiments of this aspect, the at least one action includes changing its synchronization source.

[0061] In some embodiments, the at least one action includes notifying an out-of-coverage UE of the interference issue.

[0062] In some embodiments, the method further includes verifying a location of the out-of-coverage UE before notifying the out-of-coverage UE of the interference issue.In some embodiments, the interference issue is associated with a Global Navigation Satellite System (GNSS) signal.

[0063] In some embodiments, the interference issue is associated with a clock accuracy error or a timing error of the GNSS signal.

[0064] In some embodiments, the indication of the interference issue received from the LMF node includes at least one of frequency, band, satellite vehicle ID (SV-ID), Global Navigation Satellite System Identification (GNSS ID), and clock accuracy error.

[0065] In some embodiments, the indication from the LMF node includes a confidence level.

[0066] In some embodiments, the confidence level is determined by how many UEs have reported the interference issue.

[0067] In some embodiments, the interference issue is one or more of intentional interference from other radio transmitters, intentional fake radio signals, spoofing, jamming and feared events.

[0068] In accordance with aspect embodiment of the present disclosure, a UE configured to communicate with a network node, is provided. The UE is configured to determine an existence of an interference issue related to a satellite navigation system signal and report the interference issue to an LMF node.

[0069] In some embodiments of this aspect, the reporting of the interference issue includes reporting a time stamp of when the interference issue was determined.

[0070] In some embodiments, the interference issue is associated with a Global Navigation Satellite System (GNSS) signal.

[0071] In some embodiments, the UE is further configured to identify which GNSS signal includes the interference issue.

[0072] In some embodiments, the LMF node confirms the interference issue, and wherein the UE is further configured to change the UE’s synchronization source upon the confirmation of the interference issue by the LMF node.

[0073] In some embodiments, the UE is an assistance UE, wherein the UE is further configured to report, to the LMF node, the UE’s capability for detecting the interference issue, receive a configuration from the LMF node for detecting the interference issue, monitor for the interference issue based on the configuration, and report, to the LMF node whether the interference issue was detected based on the monitoring.

[0074] In some embodiments, the UE is further configured to receive notification of the interference issue from the network node.In some embodiments, the UE is further configured to report to the LMF node that the interference issue no longer exists.

[0075] In some embodiments, the interference issue is one or more of intentional interference from other radio transmitters, intentional fake radio signals, spoofing, jamming and feared events.

[0076] In accordance with another aspect of the present disclosure, a method implemented in a UE that is configured to communicate with a network node, is provided. The method includes determining an existence of an interference issue related to a satellite navigation system signal, and reporting the interference issue to an LMF node.

[0077] In some embodiments of this aspect, the reporting of the interference issue includes reporting a time stamp of when the interference issue was determined.

[0078] In some embodiments, the interference issue is associated with a Global Navigation Satellite System (GNSS) signal.

[0079] In some embodiments, the method further includes identifying which GNSS signal includes the interference issue.

[0080] In some embodiments, the LMF node confirms the interference issue, the method further comprising changing the UE’s synchronization source upon the confirmation of the interference issue by the LMF node.

[0081] In some embodiments, the UE is an assistance UE, and the method further includes reporting, to the LMF node, the UE’s capability for detecting the interference issue, receiving a configuration from the LMF node for detecting the interference issue, monitoring for the interference issue based on the configuration, and reporting, to the LMF node, whether the interference issue was detected based on the monitoring.

[0082] In some embodiments, the method further includes receiving notification of the interference issue from the network node.

[0083] In some embodiments, the method further includes reporting to the LMF node that the interference issue no longer exists.

[0084] In some embodiments, the interference issue is one or more of intentional interference from other radio transmitters, intentional fake radio signals, spoofing, jamming and feared events.

[0085] In accordance with another aspect of the present disclosure, a Location Management Function (LMF) node configured to communicate with a network node, is provided. The LMF node is configured to determine that an interference issue exists and transmit an indication of the interference issue to the network node.In some embodiments of this aspect, the indication of the interference issue includes a confidence level.

[0086] In some embodiments, the confidence level is determined by how UEs have reported the interference issue.

[0087] In some embodiments, the LMF node is further configured to receive a notification from at least one UE that has detected the interference issue, the determining that the interference issue exists being based on the notification from the at least one UE.

[0088] In some embodiments, the LMF node is further configured to inform a Random Access Network (RAN) node of the interference issue.

[0089] In some embodiments, the LMF node is further configured to inform an access and mobility function (AMF), of the interference issue for subsequent notification of the interference issue to the network node.

[0090] In some embodiments, indicating the interference issue to the network node includes reporting at least one of frequency, band, satellite vehicle ID (SV-ID), Global Navigation Satellite System Identification (GNSS ID), and clock accuracy error.

[0091] In some embodiments, the LMF node is further configured to identify an assistance UE that can assist in identifying the interference issue, configure the assistance UE to detect the interference issue, and receive a report from the assistance UE as to whether the interference issue was detected.

[0092] In some embodiments, the interference issue is one or more of intentional interference from other radio transmitters, intentional fake radio signals, spoofing, jamming and feared events.

[0093] In accordance with another aspect of the present disclosure, a method implemented an LMF node, the LMF node configured to communicate with a network node, is provided, The method includes determining that an interference issue exists and transmitting an indication of the interference issue to the network node.

[0094] In some embodiments of this aspect, the indication of the interference issue includes a confidence level.

[0095] In some embodiments, the confidence level is determined by how UEs have reported the interference issue.

[0096] In some embodiments, the method further includes receiving a notification from at least one U that has detected the interference issue, the determining that the interference issue exists being based on the notification from the at least one UE.In some embodiments, the method further includes informing a Random Access Network (RAN) node of the interference issue.

[0097] In some embodiments, the method further includes informing an access and mobility function (AMF) of the interference issue for subsequent notification of the interference issue to the network node.

[0098] In some embodiments, indicating the interference issue to the network node includes reporting at least one of frequency, band, satellite vehicle ID (SV-ID), Global Navigation Satellite System Identification (GNSS ID), and clock accuracy error.

[0099] In some embodiments, the method further includes identifying an assistance UE that can assist in identifying the interference issue, configuring the assistance UE to detect the interference issue, and receiving a report from the assistance UE as to whether the interference issue was detected.

[0100] In some embodiments, the interference issue is one or more of intentional interference from other radio transmitters, intentional fake radio signals, spoofing, jamming and feared events.

[0101] BRIEF DESCRIPTION OF THE DRAWINGS

[0102] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0103] FIG. 1 illustrates an example of LTE positioning architecture;

[0104] FIG. 2 illustrates an example of the different 4G / LTE / EPC and 5G / NR / 5GC entities in an architecture;

[0105] FIG. 3 illustrates an example of signals that GNSS satellites transmit;

[0106] FIG. 4 is a block diagram of the overall 5G RAN (NG-RAN) architecture;

[0107] FIG. 5 is a block diagram of a base station with split architecture;

[0108] FIG. 6 is a schematic diagram of an example network architecture illustrating a communication system according to the principles in the present disclosure;

[0109] FIG. 7 is a block diagram of several entities of FIG. 6 according to some embodiments of the present disclosure;

[0110] FIG. 8 is a flowchart of an example process in a network node according to some embodiments of the present disclosure;

[0111] FIG. 9 is a flowchart of another example process in a network node according tosome embodiments of the present disclosure;

[0112] FIG. 10 is a flowchart of an example process in a UE according to some embodiments of the present disclosure;

[0113] FIG. 11 is a flowchart of another example process in a UE according to some embodiments of the present disclosure;

[0114] FIG. 12 is a flowchart of an example process in an LMF according to some embodiments of the present disclosure;

[0115] FIG. 13 is a flowchart of another example process in an LMF according to some embodiments of the present disclosure;

[0116] FIG. 14 is a block diagram of a virtualization environment according to some embodiments of the present disclosure;

[0117] FIG. 15 is a signaling diagram of an example process according to some embodiments of the present disclosure;

[0118] FIG. 16 is a signaling diagram of another example process according to some embodiments of the present disclosure; and

[0119] FIG. 17 is a signaling diagram of still another example process according to some embodiments of the present disclosure.

[0120] DETAILED DESCRIPTION

[0121] As discussed above, GNSS signals are used by a base station as a source of synchronization. Similarly, the UEs performing Sidelink operation out of cellular coverage also use GNSS signals as a reference source for synchronization. However, if GNSS signals are spoofed or jammed, it would impact the cellular network entities such as base stations and UEs which rely upon GNSS for synchronization.

[0122] The terms “jamming” and “spoofing” used here are defined as “interference issues” or “feared events” that may affect the entities of a cellular network.

[0123] Some solutions rely upon crowd source-based solution where UEs may detect the GNSS jamming and / or spoofing (interference issue) and inform the LMF. However, it is unclear how other network entities (network node and out-of-coverage UEs) can be aware of the issue and what the content of a such a message should be.

[0124] Some embodiments of the present disclosure may advantageously allow a network node to receive, as part of NRPPa or NGAP message (new or existing), an indication of the estimated GNSS spoofing and jamming from the LMF and change its synchronization source if the network node is using the impacted GNSS signal / frequency as itssynchronization source.

[0125] Some embodiments of the present disclosure may advantageously allow that the network node (e.g., gNB) may further inform UEs (via, for example, broadcast) so that the UEs which are also using this spoofed / jammed GNSS signal as their synchronization source can change their synchronization source (for example, change from a GNSS synchronization source to a cellular synchronization source).

[0126] In some embodiments, a gNB-DU, receives as part of an F1AP message (new or existing), an indication of the estimated synchronization delay due to GNSS spoofing and jamming, and reports it as an error.

[0127] In some embodiments, the GNSS interference issue will be known to network nodes and UEs which rely upon GNSS as their synchronization source and therefore can change their synchronization source to another GNSS-type or use non-GNSS technology as their synchronization source.

[0128] Before describing in detail example embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to detecting and reporting interference issues that impact entities in a cellular network.

[0129] Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0130] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. 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 will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

[0131] In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections.

[0132] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. 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 will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0133] The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multistandard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a user equipment (UE) such as a wireless device (WD) or a radio network node.

[0134] In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The UE herein can be any type of user equipment capable of communicating with a network node or another UE over radiosignals, such as a wireless device (WD). The UE may also be a radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), low-cost and / or low-complexity UE, a sensor equipped with UE, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device etc.

[0135] Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell / multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

[0136] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR) and / or 6G, may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. It is contemplated that other 3GPP systems may make use of the concepts and arrangements disclosed herein. For example, a disclosure relating to NR may also be implementable in a 6G system and / or an LTE system, a disclosure relating to 6G may also be implementable in a NR and / or LTE system, and a disclosure relating to LTE may also be implementable in a NR and / or 6G system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

[0137] Note further, that functions described herein as being performed by a user equipment or a network node may be distributed over a plurality of user equipments and / or network nodes. In other words, it is contemplated that the functions of the network node and user equipment described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

[0138] Unless otherwise defined, all terms (including 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. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in thecontext of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0139] Some embodiments are directed to detecting interference issues that impact entities in a cellular network.

[0140] Referring to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 6 a schematic diagram of a communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and / or NR (5G) and / or 6G, which comprises an access network 12, such as a radio access network, and a core network 14. Core network 14 may include one or more core network nodes such as location management function (LMF) node 15 (including indication unit 32, described below). The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first user equipment (UE) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second UE 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of UEs 22a, 22b (collectively referred to as user equipments 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding network node 16. Note that although only two UEs 22, three network nodes 16 and one LMF 15 are shown for convenience, the communication system may include many more UEs 22, network nodes 16 and / or core network nodes 15.

[0141] Also, it is contemplated that a UE 22 can be in simultaneous communication and / or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a UE 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, UE 22 can be in communication with network node 16 such as an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0142] A network node 16 (eNB or gNB) is configured to include a resynchronization unit 24, which is configured to perform one or more network node 16 functions described herein, such as, for example, changing the synchronization source of the network node.A UE 22 is configured to include a reconfiguration unit 26 which is configured to perform one or more UE 22 functions as described herein, such as, for example, reconfiguring the synchronization source of the UE 22 upon receiving notification from the network node 16.

[0143] A LMF node 15 is configured to include an indication unit 32 which is configured to perform one or more LMF node 15 functions as described herein.

[0144] Example implementations, in accordance with an embodiment, of the UE 22, network node 16 and core network node 15 discussed in the preceding paragraphs will now be described with reference to FIG. 7.

[0145] The communication system 10 includes a network node 16 provided in a communication system 10 and including hardware 28 enabling it to communicate with the UE 22 and core network node 15. The hardware 28 may include a radio interface 30 for setting up and maintaining at least a wireless connection 33 with a UE 22 located in a coverage area 18 served by the network node 16. The radio interface 30 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 30 includes an array of antennas 34 to radiate and receive signal(s) carrying electromagnetic waves.

[0146] In the embodiment shown, the hardware 28 of the network node 16 further includes processing circuitry 36. The processing circuitry 36 may include a processor 38 and a memory 40. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 36 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 38 may be configured to access (e.g., write to and / or read from) the memory 40, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0147] Thus, the network node 16 further has software 42 stored internally in, for example, memory 40, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 42 may be executable by the processing circuitry 36. The processing circuitry 36 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by network node 16.Processor 38 corresponds to one or more processors 38 for performing network node 16 functions described herein. The memory 40 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 42 may include instructions that, when executed by the processor 38 and / or processing circuitry 36, causes the processor 38 and / or processing circuitry 36 to perform the processes described herein with respect to network node 16. For example, processing circuitry 36 of the network node 16 may include resynchronizaton unit 24 which is configured to perform one or more network node 16 functions described herein, such as, for example, changing the synchronization source of the network node.

[0148] The communication system 10 further includes the UE 22 already referred to. The UE 22 may have hardware 44 that may include a radio interface 46 configured to set up and maintain a wireless connection 33 with a network node 16 serving a coverage area 18 in which the UE 22 is currently located. The radio interface 46 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 46 includes an array of antennas 48 to radiate and receive signal(s) carrying electromagnetic waves.

[0149] The hardware 44 of the UE 22 further includes processing circuitry 50. The processing circuitry 50 may include a processor 52 and memory 54. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 50 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 52 may be configured to access (e.g., write to and / or read from) memory 54, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0150] Thus, the UE 22 may further comprise software 56, which is stored in, for example, memory 54 at the UE 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the UE 22. The software 56 may be executable by the processing circuitry 50. The software 56 may include a client application 58. The client application 58 may be operable to provide a service to a human or non-human user via the UE 22.The processing circuitry 50 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by UE 22. The processor 52 corresponds to one or more processors 52 for performing UE 22 functions described herein. The UE 22 includes memory 54 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 56 and / or the client application 58 may include instructions that, when executed by the processor 52 and / or processing circuitry 50, causes the processor 52 and / or processing circuitry 50 to perform the processes described herein with respect to UE 22. For example, the processing circuitry 50 of the UE 22 may include reconfiguration unit 26, which is configured to perform one or more UE 22 functions as described herein, such as, for example, reconfiguring the synchronization source of the UE 22 upon receiving notification from the network node 16.

[0151] The communication system 10 further includes LMF node 15 provided in a communication system 10 and including hardware 94 enabling it to communicate with network node 16 such as via one or more connections 35. The hardware 94 may include a communication interface 96 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10. The communication interface 96 may be configured to facilitate a connection 35 to network node 16.

[0152] In the embodiment shown, the hardware 94 of LMF node 15 further includes processing circuitry 98. The processing circuitry 98 may include a processor 100 and a memory 102. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 98 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 100 may be configured to access (e.g., write to and / or read from) the memory 102, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory). Thus, LMF node 15 further has software 104 stored internally in, for example, memory 102, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the LMF node 15 via an external connection. The software 104 may be executable by the processing circuitry 98. The processing circuitry 98 may be configuredto control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by LMF node 15. Processor 100 corresponds to one or more processors 100 for performing LMF node 15 functions described herein. The memory 102 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 104 may include instructions that, when executed by the processor 100 and / or processing circuitry 98, causes the processor 100 and / or processing circuitry 98 to perform the processes described herein with respect to LMF node 15. For example, processing circuitry 98 of the LMF node 15 may include indication unit 32 that is configured to perform one or more LMF node 15 functions described herein.

[0153] In some embodiments, the inner workings of the network node 16, UE 22 and core network node 15 (e.g., LMF node 15) may be as shown in FIG. 7 and independently, the surrounding network topology may be that of FIG. 6.

[0154] The wireless connection 33 between the UE 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and / or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc. In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.

[0155] Although FIGS. 6 and 7 show various “units” such as resynchronization unit 24, reconfiguration unit 26 and indication unit 32 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0156] FIG. 8 is a flowchart of an example process in a network node 16 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the resynchronization unit 24), processor 38, and / or radio interface 30. Network node 16 is configured to receive (Block S106) from LMF node 15, an indication of an interference issue related to a satellite navigation systemsignal, and in response to the indication of the interference issue, change (Block SI 08) its synchronization source.

[0157] In some embodiments, network node 16 is further configured to change its synchronization source to another satellite navigation system signal or to a non-satellite navigation system source.

[0158] In some embodiments, network node 16 is further configured to notify an out-of-coverage UE 22 of the interference issue.

[0159] In some embodiments, network node 16 is further configured to verify a location of the out-of-coverage UE 22 before notifying the out-of-coverage UE 22 of the interference issue.

[0160] In some embodiments, the interference issue is associated with a Global Navigation Satellite System (GNSS) signal.

[0161] In some embodiments, the interference issue is associated with a clock accuracy error or a timing error of the GNSS signal.

[0162] In some embodiments, the indication of the interference issue received from the LMF node 15 includes at least one of frequency, band, satellite vehicle ID (SV-ID), Global Navigation Satellite System Identification (GNSS ID), and clock accuracy error.

[0163] In some embodiments, the interference issue is timing error related to a System Frame Number (SFN) frame.

[0164] In some embodiments, network node 16 is further configured to take into account a synchronization indication as compensation error.

[0165] In some embodiments, wherein the notification from the LMF node 15 includes a confidence level.

[0166] In some embodiments, the confidence level is determined by how many UEs have reported the interference issue.

[0167] FIG. 9 is a flowchart of another example process in a network node 16 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the resynchronization unit 24), processor 38, and / or radio interface 30. Network node 16 is configured to receive (Block SI 10) from a location management function (LMF) node 15, an indication of an interference issue. Network node 16 is further configured to, in response to the indication of the interference issue, perform (Block SI 12) at least one action.In some embodiments, the at least one action includes changing its synchronization source.

[0168] In some embodiments, the at least one action includes notifying an out-of-coverage UE 22 of the interference issue.

[0169] In some embodiments, network node 16 is further configured to verify a location of the out-of-coverage UE 22 before notifying the out-of-coverage UE 22 of the interference issue.

[0170] In some embodiments, the interference issue is associated with a Global Navigation Satellite System (GNSS) signal.

[0171] In some embodiments, the interference issue is associated with a clock accuracy error or a timing error of the GNSS signal.

[0172] In some embodiments, the indication of the interference issue received from the LMF node 15 includes at least one of frequency, band, satellite vehicle ID (SV-ID), Global Navigation Satellite System Identification (GNSS ID) and clock accuracy error.

[0173] In some embodiments, the indication from the LMF node 15 includes a confidence level.

[0174] In some embodiments, the confidence level is determined by how many UEs 22 have reported the interference issue.

[0175] In some embodiments, the interference issue is one or more of intentional interference from other radio transmitters, intentional fake radio signals, spoofing, jamming and feared events.

[0176] FIG. 10 is a flowchart of an example process in a UE 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of UE 22 such as by one or more of processing circuitry 50 (including the reconfiguration unit 26), processor 52, and / or radio interface 46. UE 22 is configured to detect (Block SI 14) an interference issue related to a satellite navigation system signal and report (Block SI 16) the interference issue to LMF node 15.

[0177] In some embodiments, the reporting of the interference issue includes reporting a time stamp of when the interference issue was detected.

[0178] In some embodiments, the interference issue is associated with a Global Navigation Satellite System (GNSS) signal.

[0179] In some embodiments, UE 22 is further configured to identify which GNSS signal includes the interference issue.In some embodiments, the LMF node 15 confirms the interference issue and UE 22 is further configured to change the UE’s synchronization source upon the confirmation of the interference issue by the LMF node 15.

[0180] In some embodiments, UE 22 is an assistance UE 22 that is further configured to report, to the LMF node 15, the UE’s capability for detecting the interference issue; receive a configuration from the LMF node 15 for detecting the interference issue; monitor for the interference issue based on the configuration; and report, to the LMF node 15, whether the interference issue was detected based on the monitoring.

[0181] FIG. 11 is a flowchart of another example process in a UE 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of UE 22 such as by one or more of processing circuitry 50 (including the reconfiguration unit 26), processor 52, and / or radio interface 46. UE 22 is configured to determine (Block SI 18) an existence of an interference issue related to a satellite navigation system signal. UE 22 is further configured to report (Block SI 20) the interference issue to a location management function (LMF) node 15.

[0182] In some embodiments, the reporting of the interference issue includes reporting a time stamp of when the interference issue was determined.

[0183] In some embodiments, the interference issue is associated with a Global Navigation Satellite System (GNSS) signal.

[0184] In some embodiments, the UE 22 is further configured to identify which GNSS signal includes the interference issue.

[0185] In some embodiments, the LMF node 15 confirms the interference issue, and wherein the UE 22 is further configured to change the UE’s synchronization source upon the confirmation of the interference issue by the LMF node 15.

[0186] In some embodiments, the UE 22 is an assistance UE 22, wherein the UE 22 is further configured to report, to the LMF node 15, the UE’s capability for detecting the interference issue, receive a configuration from the LMF node 15 for detecting the interference issue, monitor for the interference issue based on the configuration, and report, to the LMF node 15, whether the interference issue was detected based on the monitoring.

[0187] In some embodiments, the UE 22 is further configured to receive notification of the interference issue from the network node 16.

[0188] In some embodiments, the UE 22 is further configured to report to the LMF node 15 that the interference issue no longer exists.In some embodiments, the interference issue is one or more of intentional interference from other radio transmitters, intentional fake radio signals, spoofing, jamming and feared events.

[0189] FIG. 12 is a flowchart of an example process in LMF node 15 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of the LMF node 15 such as by one or more of processing circuitry, a processor, and / or a radio interface. The LMF node 15 is configured to detect (Block SI 22) an interference issue and report (Block SI 24) the interference issue to the LMF node 15.

[0190] In some embodiments, the LMF node 15 is further configured to identify an assistance UE 22 that can assist in identifying the interference issue; configure the assistance UE 22 to detect the interference issue; and receive a report from the assistance UE 22 as to whether the interference issue was detected.

[0191] In some embodiments, reporting the interference issue includes reporting at least one of frequency, band, satellite vehicle ID (SV-ID), Global Navigation Satellite System Identification (GNSS ID), and clock accuracy error.

[0192] In some embodiments, the interference issue is a timing error related to a System Frame Number (SFN) frame.

[0193] In some embodiments, reporting the interference issue to the network node 16 includes a confidence level.

[0194] In some embodiments, the confidence level is determined by how many UEs 22 have reported the interference issue.

[0195] FIG. 13 is a flowchart of another example process in LMF node 15 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of the LMF node 15 such as by one or more of processing circuitry, a processor, and / or a radio interface. The LMF node 15 is configured to determine (Block SI 26) that an interference issue exists. The LMF node 15 is further configured to transmit, (Block SI 28) an indication of the interference issue to the network node 16.

[0196] In some embodiments, the indication of the interference issue includes a confidence level.

[0197] In some embodiments, the confidence level is determined by how UEs 22 have reported the interference issue.In some embodiments, the LMF node 15 is further configured to receive a notification from at least one UE 22 that has detected the interference issue, the determining that the interference issue exists being based on the notification from the at least one UE 22.

[0198] In some embodiments, the LMF node 15 is further configured to inform a Random Access Network (RAN) node 16 of the interference issue.

[0199] In some embodiments, the LMF node 15 is further configured to inform an access and mobility function (AMF), of the interference issue for subsequent notification of the interference issue to the network node.

[0200] In some embodiments, indicating the interference issue to the network node includes reporting at least one of frequency, band, satellite vehicle ID (SV-ID), Global Navigation Satellite System Identification (GNSS ID), and clock accuracy error.

[0201] In some embodiments, the LMF node 15 is further configured to identify an assistance UE 22 that can assist in identifying the interference issue, configure the assistance UE 22 to detect the interference issue, and receive a report from the assistance UE 22 as to whether the interference issue was detected.

[0202] In some embodiments, the interference issue is one or more of intentional interference from other radio transmitters, intentional fake radio signals, spoofing, jamming and feared events.

[0203] In some embodiments, the communication system 10 includes one or more Open-RAN (ORAN) network nodes 16. An ORAN network node 16 is a node in the communication system 10 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the communication system 10, including one or more network nodes 16 in the access network 12 and / or core network 14.

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

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

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

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

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

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

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

[0211] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing theprocesses and functions of the disclosure, the sections below provide details and examples of arrangements for detecting and reporting interference issues that impact entities in a cellular network.

[0212] One or more UE 22 functions described below may be performed by one or more of processing circuitry 50, reconfiguration unit 26, processor 52, radio interface 46, etc. One or more network node 16 functions described below may be performed by one or more of processing circuitry 36, processor 38, resynchronization unit 24, radio interface 30, etc. One or more core network node 15 (e.g., LMF node 15) described below may be performed by one or more of processing circuitry 98, processor 100, indication unit 32, communication interface 96, etc.

[0213] FIG. 15 is a signaling diagram of an example according to some embodiments of the present disclosure. In particular, in FIG. 15 the jamming / spoofing, i.e., interference issue, is reported from the LMF node 15 to the network node 16 and from the network node 16 to out-of-coverage UEs 22.

[0214] Some examples steps of FIG. 15 are described below:

[0215] 1. In Block SI 32, the UEs 22 may detect jamming / spoofing. In Block SI 34, the UEs 22 may report this to the LMF node 15 including on which GNSS signal (band, frequency) the jamming or spoofing was detected and inform the LMF node 15 of this. In some embodiments, the UE 22 may inform this to the LMF node 15 along with the time stamp when this was detected, e.g., the time stamp when the detection of the jamming / spoofing occurred is included in the reporting to the LMF node 15.

[0216] 2. In Block SI 36, the LMF node 15 may determine if there is real jamming / spoofing, i.e., confirm the jamming / spoofing reported at step S134. The LMF node 15 may interpret the jamming / spoofing in terms of clock accuracy error or as a timing error.

[0217] 3. In Block S138, the LMF node 15 may inform network nodes 16 who are serving the cells from where UEs 22 have detected the jamming / spoofing. Alternatively, the LMF node 15 may report it to the AMF and the AMF may then provide it over NGAP to different network nodes 16. In Block S140, network nodes 16 then change / update their synchronization source if they confirm that the GNSS signals that they are using have been spoofed / jammed.

[0218] o In some embodiments, the network node 16 then receives an indication that the GNSS synch source received from the UE 22 by LMF node 15 is not stable due to spoofing / jamming.o In some embodiments, the network node 16 receives, from the LMF node 15, the jamming / spoofing indication in terms of which frequency, band, satellite vehicle ID (SV-ID), GNSS ID, and clock accuracy error.

[0219] o In some embodiments, the network node 16 receives the jamming / spoofing indication as a timing error related to the System Frame Number (SFN) time.

[0220] o In some embodiments, the network node 16 takes into account the synchronization indication as compensation error.

[0221] 4. In some embodiments, in the case of split network node architecture (shown in FIG. 5), the gNB-CU that receives the report of jamming / spoofing described above may report it to the gNB-DU over an F1AP message. The gNB-DU may update and align the synchronization source to compensate for the error due to spoofing / j amming or change to another unimpacted source.

[0222] 5. In Block SI 42, the network nodes 16 may also inform the out-of-coverage UEs 22 of the jamming / spoofing, where the out-of-cov erage UEs 22 may also be using the GNSS signal as reference source for synchronization. This may be done, for example, via a relay UE, pre-configurations, broadcast procedure, etc.

[0223] FIG. 16 is a signaling diagram of another example according to some embodiments of the present disclosure. UE 22 detects jamming / spoofing (Block S143). In Block S144, the PRU UEs 22 which are capable of detecting jamming / spoofing, report their capability to the LMF node 15. In Block S146, the LMF node 15 may then, identify which UEs 22 can further assist. In Block S148, the LMF node 15 then configures jamming / spoofing detection to such PRU UEs 22. In Block SI 50, if the PRU UEs 22 happen to identify the interference, the PRU UEs 22 report to the LMF node 15 either that jamming / spoofing was detected or report that no jamming / spoofing was detected.

[0224] Embodiment examples with respect to 3GPP TS 38.455 and 3GPP TS 38.413:

[0225] In some embodiment, a NRPPa procedure to notify the GNSS interference detection is specified between the LMF node 15 and the RAN node 16. In some embodiments, the network node 16 (RAN node) CU forwards the information to the network node 16 (RAN node) DU using an F1AP message.

[0226] In some embodiments, the notification of the GNSS interference detection message can be performed by the LMF node 15 as part of an ongoing positioning session via NRPPa, or the LMF node 15 may notify the AMF and the AMF then notifies this to the RAN nodes 16 using NGAP protocol. In some embodiments, the LMF node 15 may alsoprovide the information about the cell ID from where the jamming / spoofing detection was detected, and the AMF notifies those RAN nodes 16 that serve the impacted cell.

[0227] FIG. 17 is a signaling diagram of an example according to some embodiments of the present disclosure. In Block S152, the LMF node 15 provides a notification of an environment issue as part of an ongoing positioning sessions with network node 16.

[0228] Table 9.1.4.1 below is an example where the LMF node 15 sends its notification out to the network nodes 16 as part of an ongoing positioning session.

[0229] > <

[0230] >

[0231]

[0232]

[0233]

[0234]

[0235]

[0236] >

[0237] <

[0238] >

[0239]

[0240]

[0241] ""

[0242]

[0243] ""

[0244]

[0245] 9.2.X GNSS Interference Detected error

[0246] This Information Element (IE) indicates the GNSS Interference Detection from the LMF node 15 to the RAN Node 16.

[0247] Note: The same message can be sent from the LMF node 15 to the AMF (NL1 interface) and from the AMF to network node 16 via NGAP. Further gNB-CU can send the same message to the gNB-DU via Fl AP.

[0248] The table below illustrates this embodiment.

[0249] >

[0250]

[0251] >

[0252] >

[0253]

[0254]

[0255] Examples

[0256] Example 1. A method implemented in a user equipment (UE) 22 that is configured to communicate with a network node 16, the method comprising determining an existence of an interference issue related to a satellite navigation system signal; and reporting the interference issue to a location management function (LMF) node 15.

[0257] Example 2. The method of Example 1, wherein the reporting of the interference issue includes reporting a time stamp of when the interference issue was determined.

[0258] Example 3. The method of any one of Examples 1 and 2, wherein the interference issue is associated with a Global Navigation Satellite System (GNSS) signal.

[0259] Example 4. The method of Example 3, further comprising identifying which GNSS signal includes the interference issue.

[0260] Example 5. The method of any one of Examples 1-4, wherein the LMF node 15 confirms the interference issue, the method further comprising changing the UE’s synchronization source upon the confirmation of the interference issue by the LMF node 15.

[0261] Example 6. The method of any one of Examples 1-5, wherein the UE 22 is an assistance UE (22), the method further comprising: reporting, to the LMF node 15, the UE’s capability for detecting the interference issue; receiving a configuration from the LMF node 15 for detecting the interference issue; monitoring for the interference issue based on the configuration; and reporting, to the LMF node 15, whether the interference issue was detected based on the monitoring.

[0262] Example 7. The method of any one of Examples 1-6, further comprising receiving notification of the interference issue from the network node 16.

[0263] Example 8. The method of any one of Examples 1-7, further comprising reporting to the LMF node 15 that the interference issue no longer exists.

[0264] Example 9. The method of any one of Examples 1-8, wherein the interference issue is one or more of intentional interference from other radio transmitters, intentional fake radio signals, spoofing, jamming and feared events.

[0265] Example 10. A user equipment (UE) 22 configured to communicate with a network node 16, the UE 22 configured to, and / or comprising a radio interface and / or processing circuitry configured to: determine an existence of an interference issue relatedto a satellite navigation system signal; and report the interference issue to a location management function (LMF) node 15.

[0266] Example 11. The UE 22 of Example 10, wherein the reporting of the interference issue includes reporting a time stamp of when the interference issue was determined.

[0267] Example 12. The UE 22 of any one of Examples 10 and 11, wherein the interference issue is associated with a Global Navigation Satellite System (GNSS) signal.

[0268] Example 13. The UE 22 of Example 12, wherein the UE 22 is further configured to identify which GNSS signal includes the interference issue.

[0269] Example 14. The UE 22 of any one of Examples 10-13, wherein the LMF node 15 confirms the interference issue, and wherein the UE 22 is further configured to change the UE’s synchronization source upon the confirmation of the interference issue by the LMF node 15.

[0270] Example 15. The UE 22 of any one of Examples 10-14, wherein the UE 22 is an assistance UE 22, wherein the UE 22 is further configured to: report, to the LMF node 15, the UE’s capability for detecting the interference issue; receive a configuration from the LMF node 15 for detecting the interference issue; monitor for the interference issue based on the configuration; and report, to the LMF node 15, whether the interference issue was detected based on the monitoring.

[0271] Example 16. The UE 22 of any one of Examples 10-15, wherein the UE 22 is further configured to receive notification of the interference issue from the network node 16.

[0272] Example 17. The UE 22 of any one of Examples 10-16, wherein the UE 22 is further configured to report to the LMF node 15 that the interference issue no longer exists.

[0273] Example 18. The UE 22 of any one of Examples 10-17, wherein the interference issue is one or more of intentional interference from other radio transmitters, intentional fake radio signals, spoofing, jamming and feared events.

[0274] Example 19. A method implemented in a network node 16 that is configured to communicate with a user equipment (UE) 16 the method comprising: receiving, from a location management function (LMF) node 15 an indication of an interference issue; and in response to the indication of the interference issue, performing at least one action .

[0275] Example 20. The method of Example 19, wherein the at least one action includes changing its synchronization source.

[0276] Example 21. The method of any one of Examples 19 and 20, wherein the at leastone action includes notifying an out-of-coverage UE 22 of the interference issue.

[0277] Example 22. The method of Example 21, further comprising verifying a location of the out-of-coverage UE 22 before notifying the out-of-coverage UE 22 of the interference issue.

[0278] Example 23. The method of any one of Examples 19-22, wherein the interference issue is associate with a Global Navigation Satellite System (GNSS) signal.

[0279] Example 24. The method of Example 23, wherein the interference issue is associated with a clock accuracy error or a timing error of the GNSS signal.

[0280] Example 25. The method of any one of Examples 19-24, wherein the indication of the interference issue received from the LMF node 15 includes at least one of frequency, band, satellite vehicle ID (SV-ID) Global Navigation Satellite System Identification (GNSS) ID, and clock accuracy error.

[0281] Example 26. The method of any one of Examples 19-25, wherein the indication from the LMF node 15 includes a confidence level.

[0282] Example 27. The method of Example 26, wherein the confidence level is determined by how many UEs 22 have reported the interference issue.

[0283] Example 28. The method of any one of Examples 19-27, wherein the interference issue is one or more of intentional interference from other radio transmitters, intentional fake radio signals, spoofing, jamming and feared events.

[0284] Example 29. A network node 16 configured to communicate with a user equipment (UE) 22, the network node 16 configured to, and / or comprising a radio interface and / or comprising processing circuitry configured to: receive, from a location management function (LMF) node 15 an indication of an interference issue; and in response to the indication of the interference issue, perform at least one action.

[0285] Example 30. The network node 16 of Example 29, wherein the at least one action includes changing its synchronization source.

[0286] Example 31. The network node 16 of any one of Examples 29 and 30, wherein the at least one action includes notifying an out-of-coverage UE 22 of the interference issue.

[0287] Example 32. The network node 16 of Example 31, wherein the network node 16 is further configured to verify a location of the out-of-coverage UE 22 before notifying the out-of-coverage UE 22 of the interference issue.

[0288] Example 33. The network node 16 of any one of Examples 29-32, wherein the interference issue is associated with a Global Navigation Satellite System (GNSS) signal.Example 34. The network node 16 of Example 33, wherein the interference issue is associated with a clock accuracy error or a timing error of the GNSS signal.

[0289] Example 35. The network node 16 of any one of Examples 29-34, wherein the indication of the interference issue received from the LMF node 15 includes at least one of frequency, band, satellite vehicle ID (SV-ID), Global Navigation Satellite System Identification (GNSS ID), and clock accuracy error.

[0290] Example 36. The network node 16 of any one of Examples 29-35, wherein the indication from the LMF node 15 includes a confidence level.

[0291] Example 37. The network node 16 of Example 36, wherein the confidence level is determined by how many UEs(22 have reported the interference issue.

[0292] Example 38. The network node 16 of any one of Examples 29-37, wherein the interference issue is one or more of intentional interference from other radio transmitters, intentional fake radio signals, spoofing, jamming and feared events.

[0293] Example 39. A method implemented in a Location Management Function (LMF) node 15 the LMF node 15 configured to communicate with a network node 16, the method comprising: determining that an interference issue exists; and transmitting an indication of the interference issue to the network node 16.

[0294] Example 40. The method of Example 39, wherein the indication of the interference issue includes a confidence level.

[0295] Example 41. The method of Example 40, wherein the confidence level is determined by how many user equipments, UEs 22 have reported the interference issue.

[0296] Example 42. The method of any one of Examples 39-41, further comprising receiving a notification from at least one UE 22 that has detected the interference issue, the determining that the interference issue exists being based on the notification from the at least one UE 22.

[0297] Example 43. The method of any one of Examples 39-42, further comprising informing a Random Access Network (RAN) node 16 of the interference issue.

[0298] Example 44. The method of any one of Examples 39-43, further comprising informing an access and mobility function (AMF) of the interference issue for subsequent notification of the interference issue to the network node.

[0299] Example 45. The method of any one of Examples 39-44, wherein indicating the interference issue to the network node includes reporting at least one of frequency, band, satellite vehicle ID, (SV-ID), Global Navigation Satellite System Identification, (GNSS ID), and clock accuracy error.Example 46. The method of any one of Examples 39-45, further comprising: identifying an assistance UE 22 that can assist in identifying the interference issue; configuring the assistance UE 22 to detect the interference issue; and

[0300] receiving a report from the assistance UE 22 as to whether the interference issue was detected.

[0301] Example 47. The method of any one of Examples 39-46, wherein the interference issue is one or more of intentional interference from other radio transmitters, intentional fake radio signals, spoofing, jamming and feared events.

[0302] Example 48. A Location Management Function (LMF) node 15, configured to communicate with a network node 16, the LMF node 15 configured to:

[0303] determine that an interference issue exists; and transmit an indication of the interference issue to the network node 16.

[0304] Example 49. The LMF node 15 of Example 48, wherein the indication of the interference issue includes a confidence level.

[0305] Example 50. The LMF node 15 of Example 49, wherein the confidence level is determined by how many user equipments (UEs) 22 have reported the interference issue.

[0306] Example 51. The LMF node 15 of any one of Examples 48-50, wherein the LMF node (15) is further configured to receive a notification from at least one UE 22 that has detected the interference issue, the determining that the interference issue exists being based on the notification from the at least one UE 22.

[0307] Example 52. The LMF node 15 of any one of Examples 48-51, wherein the LMF node 15 is further configured to inform a Random Access Network (RA) node 16 of the interference issue.

[0308] Example 53. The LMF node 15 of any one of Examples 48-52, wherein the LMF node 15 is further configured to inform an access and mobility function (AMF) of the interference issue for subsequent notification of the interference issue to the network node.

[0309] Example 54. The LMF node 15) of any one of Examples 48-53, wherein indicating the interference issue to the network node includes reporting at least one of frequency, band, satellite vehicle ID (SV-ID), Global Navigation Satellite System Identification (GNSS ID), and clock accuracy error.

[0310] Example 55. The LMF nod(15 of any one of Examples 48-54, wherein the LMF node 15 is further configured to: identify an assistance UE 22 that can assist in identifying the interference issue; configure the assistance UE 22 to detect the interference issue; and receive a report from the assistance UE 22 as to whether the interference issue wasdetected.

[0311] Example 56. The LMF nodel5) of any one of Examples 38-55, wherein the interference issue is one or more of intentional interference from other radio transmitters, intentional fake radio signals, spoofing, jamming and feared events.

[0312] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0313] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0314] These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks.The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0315] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0316] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0317] Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or

[0318] subcombination.It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

1. Claims:

1. A method implemented in a user equipment, UE, (22) that is configured to communicate with a network node (16), the method comprising:determining an existence of an interference issue related to a satellite navigation system signal (SI 18); andreporting the interference issue to a location management function, LMF, node (15) (SI 20).

2. The method of Claim 1, wherein the reporting of the interference issue includes reporting a time stamp of when the interference issue was determined.

3. The method of any one of Claims 1 and 2, wherein the interference issue is associated with a Global Navigation Satellite System, GNSS, signal.

4. The method of Claim 3, further comprising identifying which GNSS signal includes the interference issue.

5. The method of any one of Claims 1-4, wherein the LMF node (15) confirms the interference issue, the method further comprising changing the UE’s synchronization source upon the confirmation of the interference issue by the LMF node (15).

6. The method of any one of Claims 1-5, wherein the UE (22) is an assistance UE (22), the method further comprising:reporting, to the LMF node (15), the UE’s capability for detecting the interference issue;receiving a configuration from the LMF node (15) for detecting the interference issue;monitoring for the interference issue based on the configuration; and reporting, to the LMF node (15), whether the interference issue was detected based on the monitoring.

7. The method of any one of Claims 1-6, further comprising receiving notification of the interference issue from the network node (16).

8. The method of any one of Claims 1-7, further comprising reporting to the LMF node (15) that the interference issue no longer exists.

9. The method of any one of Claims 1-8, wherein the interference issue is one or more of intentional interference from other radio transmitters, intentional fake radio signals, spoofing, jamming and feared events.

10. A user equipment, UE, (22) configured to communicate with a network node (16), the UE (22) configured to, and / or comprising a radio interface and / or processing circuitry configured to:determine an existence of an interference issue related to a satellite navigation system signal; andreport the interference issue to a location management function, LMF, node (15).

11. The UE (22) of Claim 10, wherein the reporting of the interference issue includes reporting a time stamp of when the interference issue was determined.

12. The UE (22) of any one of Claims 10 and 11, wherein the interference issue is associated with a Global Navigation Satellite System, GNSS, signal.

13. The UE (22) of Claim 12, wherein the UE (22) is further configured to identify which GNSS signal includes the interference issue.

14. The UE (22) of any one of Claims 10-13, wherein the LMF node (15) confirms the interference issue, and wherein the UE (22) is further configured to change the UE’s synchronization source upon the confirmation of the interference issue by the LMF node (15).

15. The UE (22) of any one of Claims 10-14, wherein the UE (22) is an assistance UE (22), wherein the UE (22) is further configured to:report, to the LMF node (15), the UE’s capability for detecting the interference issue;receive a configuration from the LMF node (15) for detecting the interference issue;monitor for the interference issue based on the configuration; andreport, to the LMF node (15), whether the interference issue was detected based on the monitoring.

16. The UE (22) of any one of Claims 10-15, wherein the UE (22) is further configured to receive notification of the interference issue from the network node (16).

17. The UE (22) of any one of Claims 10-16, wherein the UE (22) is further configured to report to the LMF node (15) that the interference issue no longer exists.

18. The UE (22) of any one of Claims 10-17, wherein the interference issue is one or more of intentional interference from other radio transmitters, intentional fake radio signals, spoofing, jamming and feared events.

19. A method implemented in a network node (16) that is configured to communicate with a user equipment, UE, (16) the method comprising:receiving, from a location management function, LMF, node (15) an indication of an interference issue (SI 10); andin response to the indication of the interference issue, performing at least one action (SI 12).

20. The method of Claim 19, wherein the at least one action includes changing its synchronization source.

21. The method of any one of Claims 19 and 20, wherein the at least one action includes notifying an out-of-coverage UE (22) of the interference issue.

22. The method of Claim 21, further comprising verifying a location of the out-of-coverage UE (22) before notifying the out-of-coverage UE (22) of the interference issue.

23. The method of any one of Claims 19-22, wherein the interference issue is associated with a Global Navigation Satellite System, GNSS, signal.

24. The method of Claim 23, wherein the interference issue is associated with a clock accuracy error or a timing error of the GNSS signal.

25. The method of any one of Claims 19-24, wherein the indication of the interference issue received from the LMF node (15) includes at least one of frequency, band, satellite vehicle ID, SV-ID, Global Navigation Satellite System Identification, GNSS ID, and clock accuracy error.

26. The method of any one of Claims 19-25, wherein the indication from the LMF node (15) includes a confidence level.

27. The method of Claim 26, wherein the confidence level is determined by how many UEs (22) have reported the interference issue.

28. The method of any one of Claims 19-27, wherein the interference issue is one or more of intentional interference from other radio transmitters, intentional fake radio signals, spoofing, jamming and feared events.

29. A network node (16) configured to communicate with a user equipment UE, (22) the network node (16) configured to, and / or comprising a radio interface and / or comprising processing circuitry configured to:receive, from a location management function, LMF, node (15) an indication of an interference issue; andin response to the indication of the interference issue, perform at least one action.

30. The network node (16) of Claim 29, wherein the at least one action includes changing its synchronization source.

31. The network node (16) of any one of Claims 29 and 30, wherein the at least one action includes notifying an out-of-coverage UE (22) of the interference issue.

32. The network node (16) of Claim 31, wherein the network node (16) is further configured to verify a location of the out-of-coverage UE (22) before notifying the out-of-coverage UE (22) of the interference issue.

33. The network node (16) of any one of Claims 29-32, wherein the interference issue is associated with a Global Navigation Satellite System, GNSS, signal.

34. The network node (16) of Claim 33, wherein the interference issue is associated with a clock accuracy error or a timing error of the GNSS signal.

35. The network node (16) of any one of Claims 29-34, wherein the indication of the interference issue received from the LMF node (15) includes at least one of frequency, band, satellite vehicle ID, SV-ID, Global Navigation Satellite System Identification, GNSS ID, and clock accuracy error.

36. The network node (16) of any one of Claims 29-35, wherein the indication from the LMF node (15) includes a confidence level.

37. The network node (16) of Claim 36, wherein the confidence level is determined by how many UEs (22) have reported the interference issue.

38. The network node (16) of any one of Claims 29-37, wherein the interference issue is one or more of intentional interference from other radio transmitters, intentional fake radio signals, spoofing, jamming and feared events.

39. A method implemented in a Location Management Function, LMF, node (15) the LMF node (15) configured to communicate with a network node (16), the method comprising:determining that an interference issue exists (S126); andtransmitting an indication of the interference issue to the network node (16) (S128).

40. The method of Claim 39, wherein the indication of the interference issue includes a confidence level.

41. The method of Claim 40, wherein the confidence level is determined by how many user equipments, UEs, (22) have reported the interference issue.

42. The method of any one of Claims 39-41, further comprising receiving a notification from at least one UE (22) that has detected the interference issue, the determining that the interference issue exists being based on the notification from the at least one UE (22).

43. The method of any one of Claims 39-42, further comprising informing a Random Access Network, RAN, node (16) of the interference issue.

44. The method of any one of Claims 39-43, further comprising informing an access and mobility function, AMF, of the interference issue for subsequent notification of the interference issue to the network node.

45. The method of any one of Claims 39-44, wherein indicating the interference issue to the network node includes reporting at least one of frequency, band, satellite vehicle ID, SV-ID, Global Navigation Satellite System Identification, GNSS ID, and clock accuracy error.

46. The method of any one of Claims 39-45, further comprising: identifying an assistance UE (22) that can assist in identifying the interference issue;configuring the assistance UE (22) to detect the interference issue; and receiving a report from the assistance UE (22) as to whether the interference issue was detected.

47. The method of any one of Claims 39-46, wherein the interference issue is one or more of intentional interference from other radio transmitters, intentional fake radio signals, spoofing, jamming and feared events.

48. A Location Management Function, LMF, node (15), configured to communicate with a network node (16), the LMF node (15) configured to:determine that an interference issue exists; andtransmit an indication of the interference issue to the network node (16).

49. The LMF node (15) of Claim 48, wherein the indication of the interference issue includes a confidence level.

50. The LMF node (15) of Claim 49, wherein the confidence level is determined by how many user equipments, UEs, (22) have reported the interference issue.

51. The LMF node (15) of any one of Claims 48-50, wherein the LMF node (15) is further configured to receive a notification from at least one UE (22) that has detected the interference issue, the determining that the interference issue exists being based on the notification from the at least one UE (22).

52. The LMF node (15) of any one of Claims 48-51, wherein the LMF node (15) is further configured to inform a Random Access Network, RAN, node (16) of the interference issue.

53. The LMF node (15) of any one of Claims 48-52, wherein the LMF node (15) is further configured to inform an access and mobility function, AMF, of the interference issue for subsequent notification of the interference issue to the network node.

54. The LMF node (15) of any one of Claims 48-53, wherein indicating the interference issue to the network node includes reporting at least one of frequency, band, satellite vehicle ID, SV-ID, Global Navigation Satellite System Identification, GNSS ID, and clock accuracy error.

55. The LMF node (15) of any one of Claims 48-54, wherein the LMF node (15) is further configured to:identify an assistance UE (22) that can assist in identifying the interference issue; configure the assistance UE (22) to detect the interference issue; andreceive a report from the assistance UE (22) as to whether the interference issue was detected.

56. The LMF node (15) of any one of Claims 38-55, wherein the interference issue is one or more of intentional interference from other radio transmitters, intentional fake radio signals, spoofing, jamming and feared events.

Images