User equipment, network node, and methods performed therein

Abstract

Embodiments herein disclose, for example, a method performed by a network node (130) for handling sensing of one or more sensing objects in a wireless communication network. The network node obtains an indication of a position of a radio network node (12) in the wireless communication network. The network node triggers a calibration procedure of the position of the radio network node upon fulfillment of a condition.

Description

[0001] USER EQUIPMENT, NETWORK NODE, AND METHODS PERFORMED THEREIN

[0002] TECHNICAL FIELD

[0003] Embodiments herein relate to a user equipment (UE), a network node, and methods performed therein regarding wireless communication. Furthermore, a computer program product and a computer readable storage medium are also provided herein. In particular, embodiments herein relate to handling sensing of objects in a wireless communication network.

[0004] BACKGROUND

[0005] In a typical wireless communication network, UEs, also known as wireless communication devices, mobile stations, stations (STA) and / or wireless devices, communicate via a Radio Access Network (RAN) with one or more core networks (CN). The RAN covers a geographical area which is divided into service areas or cells, with each service area or cell being served by a radio network node such as an access node e.g. a Wi-Fi access point or a radio base station (RBS), which in some networks may also be called, for example, a NodeB, a gNodeB, or an eNodeB. The service area or cell is a geographical area where radio coverage is provided by the radio network node. The radio network node operates on radio frequencies to communicate over an air interface with the UEs within range of the radio network node. The radio network node communicates over a downlink (DL) to the UE and the UE communicates over an uplink (UL) to the radio network node.

[0006] A Universal Mobile Telecommunications System (UMTS) is a third generation (3G) telecommunication network, which evolved from the second generation (2G) Global System for Mobile Communications (GSM). The UMTS terrestrial radio access network (UTRAN) is essentially a RAN using wideband code division multiple access (WCDMA) and / or High-Speed Packet Access (HSPA) for communication with user equipment. In a forum known as the Third Generation Partnership Project (3GPP), telecommunications suppliers propose and agree upon standards for present and future generation networks and investigate e.g. enhanced data rate and radio capacity. In some RANs, e.g. as in UMTS, several radio network nodes may be connected, e.g., by landlines or microwave, to a controller node, such as a radio network controller (RNC) or a base station controller (BSC), which supervises and coordinates various activities of the plural radio network nodes connected thereto. The RNCs are typically connected to one or more core networks.

[0007] Specifications for the Evolved Packet System (EPS) have been completed within the 3GPP and coming 3GPP releases, such as New Radio (NR), are worked on. The EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long-Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network. E-UTRAN / LTE is a 3GPP radio access technology wherein the radio network nodes are directly connected to the EPC core network. As such, the Radio Access Network (RAN) of an EPS has an essentially “flat” architecture comprising radio network nodes connected directly to one or more core networks.

[0008] With the emerging 5G technologies such as NR, the use of very many transmit- and receive-antenna elements may be of great interest as it makes it possible to utilise beamforming, such as transmit-side and receive-side beamforming. Transmit-side beamforming means that the transmitter can amplify the transmitted signals in a selected direction or directions, while suppressing the transmitted signals in other directions. Similarly, on the receive-side, a receiver can amplify signals from a selected direction or directions, while suppressing unwanted signals from other directions. NR is connected to the 5G Core Network (5GC) which comprises a number of Network Functions (NF) such as Session Management Function (SMF), Access Management Function (AMF), Authentication Service Function (ALISF), Policy Control Function (PCF), Unified Data Manager (UDM), Network Repository Function (NRF), Network Exposure Function (NEF), just to mention some. In the 5GC, NFs can discover other NFs by using a discovery service provided by the NRF.

[0009] Sensing objects follows some of the principles that are being used by animals for echolocation. That is, a pulse is emitted, usually with high frequency, that in aspects of wave packets travel until it hits a reflecting / scattering surface after which a (partial) reflection of the original pulse travels back to the transmitter or some other receiver. With this technique some animal species can navigate in darkness with very high precision, see LIZ LANGLEY (2021) Echolocation is nature’s built-in sonar. Here’s how it works. National Geographic, Feb 3, 2021. https: / / www.nationalgeographic.com / animals / article / echolocation-is-nature-built-in-sonar-here-is- how-it-works.

[0010] The ’’technique” is also used in many different applications. Some obvious examples are the radars used to navigate airplanes and the lidar now available in many cars as well as in some consumer electronics such as smartphones and tablets. However, radar can also be used for input to small devices since the radar can detect movements of a person’s fingers. One aspect distinguishing lidar and radar is typically that radar signals are more capable of penetrating surface layers of an object, whereas lidar typically scatters and reflects from object’s surface.

[0011] To describe some of the phenomena a brief look at geophysics can be used. There are several geophysical methods that rely on the abovementioned principles. One very commonly used method is reflection seismics where an energy pulse is transmitted into the ground. When the pulse encounters an object, e.g., a boundary between two types of rock or a fracture zone, where the physical properties differ enough, this causes a reflection that travels back to the transmitter. However, if the original pulse hits the boundary at a high enough angle, the original wave may be refracted instead. Naturally, a wave or pulse that is sent through a mountain may, even if parts of the energy is reflected, travel though the mountain, however, being affected by the physical properties on its path. This type of data is also used for investigations, e.g., using tomography or when characterising and identifying sources of earthquakes. These methods work well also using a radar to transmit the first pulse, however, radar investigations are used for other purposes. The property that determines if there will be a radar reflection is the dielectric constant (rather than the physical properties for seismic waves). Furthermore, modifications and design of surface dielectric constants are what typically is considered in design of stealth vessels, and also using other wavelengths for medical applications e.g. x-ray machines for determining a fractured bone.

[0012] Fig. 1a shows: A) Communication and monostatic sensing by gNB using orthogonal waveforms, showing radar resources and DL / LIL communication resources. B) Bistatic sensing by mobile node reusing communication waveform radiated by gNB, whereas DL may be reused for radar.

[0013] The principles exemplified above also work for WIFI. Given the operating frequency and output power of ordinary WIFI, such as IEEE 802.11 , limits the possible types of investigations. I.e. the WIFI waves will attenuate quickly, especially in solid materials, so it may be difficult to detect anything behind reinforced concrete walls.

[0014] A WiFi sensing session usually follows these steps, see C. Chen, H. Song, Q. Li, F. Meneghello, F. Restuccia and C. Cordeiro, "Wi-Fi Sensing Based on IEEE 802.11bf," in IEEE Communications Magazine, vol. 61 , no. 1, pp. 121-127, January 2023, doi: 10.1109 / MCOM.007.2200347. Wi-Fi Sensing Based on IEEE 802.11 bf:

[0015] Sensing session setup is a process for sensing-capable devices to discover each other, establish security context, and exchange basic sensing capabilities. This process could be omitted for monostatic sensing where the Tx and Rx are in the same device;

[0016] Sensing measurement setup is a process for the sensing initiator and sensing responder(s) to negotiate and agree on operational parameters associated with a specific sensing ap- plication, including role assignment (transmitter or receiver), PHY parameters (bandwidth, number of spatial streams etc.), type of sensing measurement report, and preferred scheduling information (sensing periodicity, duration, etc.). This process could be omitted for monostatic sensing where the Tx and Rx are in the same device;

[0017] Sensing measurement instance is a process where actual sensing measurements take place; and

[0018] Sensing measurement setup termination and sensing session termination terminate an established sensing measurement setup and sensing session, respectively.

[0019] WIFI sensing exploits radio channel changes measured, e.g., as amplitude and phase. This channel environment changes, e.g., when a person or object moves in this area and alters the radio path. The radio measurements are analyzed to identify and possibly characterize the reason for changes in the environment.

[0020] Since there are advantages with being able to detect, e.g., movement, using radio waves there are already commercial implementations of WIFI sensing. Several example of Wi-Fi sensing in disclosed in “Wi-Fi Sensing: Applications and Challenges” by A. M. Khalili, Abdel-Hamid Soliman, Md Asaduzzaman, Alison Griffiths; https: / / arxiv.org / abs / 1901.00715, which provides a range of more and less successful indoor as well as outdoor applications, such as: health monitoring, activity classification, gesture recognition, people-counting, through the wall (using “sensing”), emotion recognition, attention monitoring, keystrokes recognition, drawing in the air, imaging, step counting, speed estimation, sleep detection, traffic monitoring, smoking detection, metal detection, sign language recognition, humidity estimation, wheat moisture detection, and fruit ripeness detection.

[0021] Other recent accomplishments are described in Tim Newcomb, Poplar Mechanics, published: JAN 19, 2023, “Scientists Can Now Use WiFi to See Through People's Walls” https: / / www.popularmechanics.com / technology / security / a42575068 / scientists-use-wifi-to-see- through-walls / where it is claimed that similar solutions are capable of see through walls using WiFi “sensing”.

[0022] Other mentionable works in the area are e.g. Jiaqi Geng, Dong Huang, Fernando De la Torre, “DensePose From WiFi", https: / / arxiv.org / pdf / 2301.00250.pdf and Mingmin Zhao et al., MIT CSAIL, 2018, “Through-Wall Human Pose Estimation Using Radio Signals”, https: / / openaccess.thecvf.com / content_cvpr_2018 / CameraReady / 2406.pdf.

[0023] There are advantages with a standard so although there are commercial implementations of WiFi sensing, the IEEE 802.11 working group has formed a new Task Group, 802.11bf, to develop a new amendment to define necessary PHY and MAC protocols to support Wi-Fi sensing in all spectrum bands, including sub-7 GHz bands (2.4 GHz, 5 GHz, and 6 GHz band), as well as 60 GHz millimeter wave (mmWave) band. IEEE 802.11 bf defines two variants of sensing measurement instances for sub-7 GHz sensing. Trigger-based (TB) sensing measurement instance is used when an AP is the sensing initiator, whereas non-Trigger based (non-TB) sensing measurement instance applies to scenarios where a non-AP STA is the sensing initiator.

[0024] Joint communication and sensing is in principle the same as WIFI sensing, however, in 3GPP the process is referred to as Integrated sensing and communications (ISAC) to emphasize that the same (radio) resources are used both for ordinary communication and for sensing measurements. The sensing process discussed in the previous section is almost identical to a process for ISAC in a cellular system.

[0025] Fig. 1b shows a principle of radar operation see e.g., Monserrat, O. (2012). Deformation measurement and monitoring with GB-SAR. For this background description of ISAC the emphasis is put on a radar-like sensing setup. In short, with radar a radio pulse is transmitted towards the anticipated target, e.g., the pulse is transmitted in a certain spatial direction or implicitly according to a spatial direction of a specific “beam”. When the pulse hits the target, assuming that the difference in electrical properties is large enough, a reflection is generated that travels back to the transmitter. From the travel time between transmission and reception of the reflection, it is possible the calculate the distance to the reflector, and combined with knowledge of the pulse’s transmission direction, a position of the target relative to the transmitter may be calculated.

[0026] There are numerous papers describing L1 problems and solutions see e.g., Reiner Thoma et al. (2012) Joint communication and Radar Sensing: An overview. EuCAP 2021 convened session “Convergence of Mobile Radio and Radar”, e.g., using OFDM to create a radar-like pulse. Another interesting set of L1 problems is to handle reflections, e.g., is the received reflection a first arrival, e.g., as in a line of sight (LOS) scenario, or are there several arrivals, e.g., as in a Non line of sight (NLOS) scenario. In a NLOS situation, your "first arrival", which is a first signal path detected by e.g. device, may very well also be reflection in itself, as all signals ending up at the device have been subject to e.g. wall bouncing and scattering. To be able to correctly handle reflections the receiver needs high time resolution and powerful signal processing. Consequently, the sensing capability of a UE may be limited since the receiver (and antenna constellation) is not capable enough. OFDM signal processing for radar, which resembles spread spectrum reception, is based on normalised matched filter processing, which is implemented by complex division in frequency domain. An advantage of OFDM is its ability to maintain carrier orthogonality if correctly processed. Naturally, prerequisites are Tx / Rx synchronisation, symbol lengths shorter than the typical channel coherence time, and correct handling of the cyclic prefix (CPX). For radar-like ISAC, the range (resp. delay) and Doppler estimation factorises, which simplifies processing and makes it more flexible. Another advantage is the low estimation variance as leakage variance disappears when Tx and Rx are synchronised. A disadvantage of OFDM is the non-optimum peak- to-average power ratio (PAPR). In case of ISAC it is difficult to optimise due to the unknown communication signal, i.e., the reflection, which is not under user control and must be recovered at the receiver.

[0027] Also, radar-like ISAC measurements can be monostatic and bistatic. It is obvious that if more information than the distance to an object is needed, a simple arrival time from the reflection is not enough, but probably additional measurements from different directions are needed.

[0028] Different types of sensing deployments are shown in Fig. 1c: Monostatic

[0029] The sensing transmitter and sensing receiver are at the same location and may even be (in) the same device. The sensing measurement takes place in a radar-like manner by measuring the echoes of a sensing transmission. Bistatic

[0030] The sensing transmitter and sensing receiver are two distinct devices. This may be 2 gNBs

[0031] (in a 3GPP network) or 2 APs (WIFI). The sensing measurement is carried out at the sensing receiver by taking measurements sent from the sensing transmitter. In some cases, the measurement receiver may be a UE (or STA); the transmitter being the gNB (or AP) or in the other direction.

[0032] Multi-static

[0033] In a multi-static setup, there could be one transmitter and several receivers. This is a common setup in geophysics (reflection seismics) and could probably be useful in some scenarios also for “cellular” sensing.

[0034] SUMMARY

[0035] As part of developing embodiments herein one or more problems have been identified. Performance requirements of sensing applications are relying on accurate and trustful location and orientation of each antenna element in the base station, or transmission point, antenna array; i.e. similarly to giving a friend instructions over the phone such as “the entrance to the shop is 25 m ahead” assumes that you are standing on the left side of the street; thus the instruction is only valid if you give this statement in relation to a correct reference location. E.g. if you are standing on the wrong side of the street, your instruction will fail accordingly.

[0036] For cellular-based ISAC operations, typically hardware impairments that affect this performance may include changes to location and / or orientation of an antenna array over time, e.g., due to incorrect installation, weather, aging, etc.

[0037] An accuracy of cellular localisation varies depending on the scenario and variations may be rather large, and to some extent unknown. Therefore, it is difficult to rely on measurements for critical situations, e.g., to determine if there is an object behind the corner you are about to turn with your car. This variability will prevail even with sensing.

[0038] One source of error is the direction of any of the transmitter / receiver node and another source of error may be the deployment positions thereof. For example, in a monostatic scenario it may be so that the assumed position of the base station, such as a gNB, is the actual position. However, an error in the actual position propagates onto all calculations. In a bistatic scenario the risk and impact of errors become even larger.

[0039] One related aspect for an end-user using a localisation service provided in an ISAC meaning is that he / she cannot really know if e.g. the network-provided position is accurate, or accurate enough, or what uncertainties that may be associated thereto. One aspect is that the ISAC solution itself, as being addressed in this idea, is affected by assumed true ground location being wrong, or that further positioning performance of the ISAC node e.g. due to propagation environment, weather conditions, etc., may perform poorly, and these two sources of errors may also add up.

[0040] In the aspect of ISAC positioning algorithms’ performance, the end user may typically be provided with accuracy information of the used service as such. In the other aspect where ISAC positioning algorithms’ performance may be biased due to faulty assumed reference position of the base station node, such information must in the first place be available for the system. Then, with that in place, the system may either provide towards the users a localisation information, i.e. , corrected device position estimate, compensated or corrected for the derived localisation error. Anyhow, to compensate for a faulty assumed base station position, the network must first have the capability to determine such.

[0041] One may assume that the transmission point’s location is correct, and based on that suggests a solution where, given known reference positions acquired from reference devices, such as UE, RAN node, etc., misaligned antenna direction is detected and compensated for.

[0042] An object of embodiments herein is to handle sensing procedures in a wireless communication network in a more accurate manner.

[0043] According to an aspect the object is achieved, according to some embodiments herein, by providing a method performed by a network node for handling sensing of one or more sensing objects in a wireless communication network. The network node obtains an indication of a position of a radio network node, such as a transmission point, in the wireless communication network; and triggers a calibration procedure of the position of the radio network node upon fulfillment of a condition.

[0044] According to another aspect the object is achieved, according to some embodiments herein, by providing a method performed by a UE for handling sensing of one or more sensing objects in a wireless communication network. The UE determines a position and / or trajectory of the UE, and receives, from a network node, an indication of a determined position and / or trajectory of the UE, determined at the network node. The UE compares the UE determined position and / or trajectory with the network node determined position and / or trajectory; and triggers a calibration procedure of the position of a radio network node based on the comparison.

[0045] It is furthermore provided herein a computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the methods herein, as performed by the UE, and the network node, respectively. It is additionally provided herein a computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to the methods herein, as performed by the UE, and the network node, respectively. According to yet another aspect the object is achieved, according to some embodiments herein, by providing a UE, and a network node configured to perform the methods herein, respectively.

[0046] Hence, according to an aspect the object is achieved by providing a network node for handling sensing of one or more sensing objects in a wireless communication network. The network node is configured to obtain an indication of a position of a radio network node in the wireless communication network; and trigger a calibration procedure of the position of the radio network node upon fulfillment of a condition.

[0047] According to another aspect the object is achieved, according to some embodiments herein, by providing a UE for handling sensing of one or more sensing objects in a wireless communication network. The UE is configured to determine a position and / or trajectory of the UE, and receive, from a network node, an indication of a determined position and / or trajectory of the UE, determined at the network node. The UE is configured to compare the UE determined position and / or trajectory with the network node determined position and / or trajectory; and trigger a calibration procedure of the position of a radio network node based on the comparison.

[0048] Thus, it is herein disclosed methods and devices for how to trigger a calibration procedure of the radio network node when a condition is fulfilled. As an example, one may perform sensing of an object in a known location and based on, and from a calculated offset of a known UE-reference position and a sensed UE-position, for a sufficiently large number of trusted UEs, determine the actual position of the radio network node such as a transmitter / receiver. This may then improve, for example, when determining the position of sensed object and, thus, embodiments herein handle the sensing procedure in the wireless communication network in a more accurate manner.

[0049] BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Embodiments will now be described in more detail in relation to the enclosed drawings, in which:

[0051] Fig. 1a shows an overview depicting aspects in sensing procedures according to prior art;

[0052] Fig. 1b is a schematic overview depicting principle of radar operation according to prior art;

[0053] Fig. 1c is a schematic overview depicting sensing according to prior art;

[0054] Fig. 2 shows an overview depicting a wireless communication network according to embodiments herein;

[0055] Fig. 3 shows a combined flowchart and signalling scheme according to some embodiments herein;

[0056] Fig. 4 shows a combined flowchart and signalling scheme according to some embodiments herein;

[0057] Fig. 5 shows a combined flowchart and signalling scheme according to some embodiments herein; Fig. 6 shows a schematic flowchart depicting a method performed by a network node according to embodiments herein;

[0058] Fig. 7 shows a schematic flowchart depicting a method performed by a UE according to embodiments herein;

[0059] Fig. 8 shows a combined flowchart and signalling scheme according to some embodiments herein;

[0060] Fig. 9 is a schematic overview depicting a network node according to embodiments herein;

[0061] Fig. 10 is a schematic overview depicting a UE according to embodiments herein;

[0062] Fig. 11 schematically illustrates embodiments of a communication system,

[0063] Fig. 12 is a generalized block diagram of embodiments of a UE,

[0064] Fig. 13 is a generalized block diagram of embodiments of a network node, and

[0065] Fig. 14 is a generalized block diagram of embodiments of a virtualization environment.

[0066] DETAILED DESCRIPTION

[0067] Embodiments herein relate to wireless communication networks in general. Fig. 2 is a schematic overview depicting a wireless communication network 1. The wireless communication network 1 comprises one or more RANs and one or more CNs. The wireless communication network 1 may use one or a number of different technologies. Embodiments herein relate to recent technology trends that are of particular interest in a New Radio (NR) context, however, embodiments are also applicable in further development of existing wireless communications systems such as e.g. LTE or Wideband Code Division Multiple Access (WCDMA).

[0068] In the wireless communication network 1, one or more UEs such as a user equipment (UE) 10 exemplified herein as a wireless device such as a mobile station, a non-access point (non- AP) station (STA), a STA and / or a wireless terminal, are comprised communicating via e.g. one or more Access Networks (AN), e.g. radio access network (RAN), to one or more core networks (CN). It should be understood by the skilled in the art that “UE” is a non-limiting term which means any terminal, wireless communications terminal, user equipment, narrowband internet of things (NB- loT) device, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station capable of communicating using radio communication with a radio network node within an area served by the radio network node. According to embodiments herein the UE may be a sensing UE, i.e. , a UE capable of performing one or more sensing measurements in an area.

[0069] The wireless communication network 1 comprises a first radio network node 12 or just radio network node 12, providing radio coverage over a geographical area, a first service area 11 or first cell, of a first radio access technology (RAT), such as NR, LTE, or similar. The first radio network node 12 may be a transmission and reception point such as an access node, an access controller, a base station, e.g. a radio base station such as a gNodeB (gNB), an evolved Node B (eNB, eNode B), a NodeB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), a transmission arrangement of a radio base station, a stand-alone access point or any other network unit or node capable of communicating with a UE within the area served by the first radio network node depending e.g. on the first radio access technology and terminology used. The first radio network node may be referred to as a serving radio network node wherein the service area may be referred to as a serving cell, and the serving network node communicates with the wireless device in form of DL transmissions to the wireless device and UL transmissions from the wireless device. It should be noted that a service area may be denoted as cell, beam, beam group or similar to define an area of radio coverage. It should be noted that a service area may be denoted as cell, beam, beam group or similar to define an area of radio coverage. According to embodiments herein the radio network node 12 may be performing sensing transmissions and / or reception, i.e. , the radio network node 12 may be capable of performing one or more sensing measurements in an area.

[0070] The wireless communication network 1 may further comprise a number of network nodes providing applications, such as an application server (AS), e.g. in NR, or network functions (NF) or actually instantiations of NFs also referred to as NF instances, such as a first network node 15, for example, a sensing function, a sensing node such as a Sensing Control Function (SCF), or an operation and maintenance (O&M) node, holding information of e.g. network deployment data such as transmission point position.

[0071] According to embodiments herein methods are suggested for handling or managing sensing procedures to detect objects such as a sensing object 150 in the wireless communication network 1.

[0072] The respective node may be a standalone server, a cloud-implemented server, a distributed server or processing resources in a server farm or same node. Embodiments herein may be implemented as physical bare metal, virtual or cloud native such as Kubernetes environment in, e.g., hyper-cloud networks.

[0073] According to embodiments herein a network node 130 such as the radio network node 12 or the first network node 15, when being involved in a sensing procedure for detecting one or more objects, obtains an indication of a position of the radio network node 12 in the wireless communication network, and triggers a calibration procedure of the position of the radio network node upon fulfillment of a condition. As an example, the radio network node 12 may position itself and / or the UE 10 and may, based on reported positions of the radio network node 12 and / or UE, initiate a repositioning of the radio network node 12 when these positions differ.

[0074] As a result of embodiments herein one may perform one or more of the following: • compensate ISAC-based position request from devices in respect to said updated true radio network node position, and / or

[0075] • provide to O&M management nodes holding information of e.g. network deployment data such as transmission point position, with e.g.: o a suggestion for position update, and / or o a delta value in respect to current used position, and / or o a position estimation metric carrying information of one or more of the following:

[0076] ■ number of devices participating in said position estimate,

[0077] ■ type of device, such as vehicle, UE, fixed terminal (FTE) / Customer Premises Equipment (CPE), etc.

[0078] ■ type of ISAC, such as 5G location service (LCS) capabilities, etc., including

[0079] • estimated LOS probability (0..100 %) in current connection

[0080] ■ trust value describing said devices affiliation in respect to mobile network operator (MNO), corporate subscription user, private user, roamed user, etc.,

[0081] ■ device’s out of band (OoB) position method, such as Global Navigation Satellite system (GNSS), WiFi, Bluetooth such as Bluetooth low energy (BLE), Radio-frequency identification (RFID), ultra-wideband (UWB)-based solutions, dead reckoning, etc., and associated accuracy, or

[0082] ■ Etc. o Etc.

[0083] In a related UE-centric aspect of the solution, further, if the UE 10 using e.g. GNSS or other internal sensor, finds that the sensing trajectory differs from the own trajectory, it may be due to the radio network node 12 has a position error for which the UE 10 may trigger initiation of a calibration procedure according to embodiments herein for repositioning the radio network node 12. Specifically, initiation of said calibration procedure may be acknowledged if number and type, such as vehicle, or FTE / CPE, etc., and associated trust of devices are determined acceptable according to some quality metric.

[0084] Embodiments herein enable the radio network node 12 in joint operation as a sensing node, to acquire OoB-based correction information, e.g., using internal sensors such as GNSS, from a set of UEs, such as trusted UEs, to be used to determine a potential offset factor between the radio network node’s assumed and true positions, to further compensate position data provided towards sensing-requesting devices, and / or to compensate for said position error in the radio network node’s own deployment information database.

[0085] Also, being able to determine that the position of the radio network node 12 is incorrect, compared to the expected position, can be used when optimising a network. For example, a radio network node significantly offset from its intended position will potentially cause an deviation between expected UE application coverage / performance in an area and what typical is reported from active UEs. Hence, not knowing that the position of the radio network node is wrong, one may spend time and processing capacity finding a root cause in e.g. algorithm tuning etc. that is not there, but that the problem only is due to misaligned reality / expectations.

[0086] If a deployment design assumes some location for the radio network node 12 to accomplish coverage along a street canyon, for example, assuming some beam pattern, then in practice having a radio network node located so that a part of the street canyon is not reachable with sufficient energy or LOS may be something optimisation will try to avoid. Thus, if the position is known to be erroneous the network can be configured to take action. An action may be to notify any receiver of positioning information (from sensing) that the accuracy is not good enough. Another action is to try to correct the measurements; l.e. use the detected difference from the expected position to calculate a correct position when performing sensing.

[0087] Fig. 3 is a combined flow chart and signalling scheme according to some embodiments herein.

[0088] Action 301. The network node 130 obtains the indication of the position of the radio network node 12 in the wireless communication network 1. The network node 130 may have a determined position of the radio network node 12 and may determine the position based on one or more positions of radio network nodes and / or UEs.

[0089] Action 302. The network node 130 and the UE 10 may perform a sensing procedure for detecting one or more sensing objects 150 in the wireless communication network 1.

[0090] Action 303. The network node 130 may obtain an indication that the position of the radio network node 12 is erroneous.

[0091] Action 304. The network node 130 triggers the calibration procedure of the position of the radio network node 12 when the position of the radio network node 12 is erroneous. The calibration procedure may be to reposition the radio network node 12 and / or to take the error into account in the sensing procedure.

[0092] Fig. 4 is a combined flow chart and signalling scheme according to some embodiments herein.

[0093] Action 401. The UE 10 may determine its position and / or trajectory. The UE 10 may retrieve the position from a GPS, a GNSS or similar. Action 402. The UE 10 may transmit to the network node 130 a request for requesting position and / or trajectory of the UE 10.

[0094] Action 403. The network node 130 may determine the position and / or trajectory of the UE 10.

[0095] Action 404. The network node 130 may transmit a response with the determined position and / or trajectory of the UE 10.

[0096] Action 405. The UE 10 may compare its determined position and / or trajectory with the the position and / or trajectory indicated in the response.

[0097] Action 406. In case the comparison indicates an erroneous position and / or trajectory, the UE 10 may transmit a trigger indication, such as a flag, a value, a difference value or similar, to the network node 130. The position may be determined erroneous in case the position differs above a threshold value.

[0098] Action 407. The network node 130 may then perform a calibration procedure to repositioning the radio network node 12.

[0099] Fig. 5 is a combined flow chart and signalling scheme according to some embodiments herein.

[0100] Action 501. The network node 130 may determine the position of the UE 10. This may be retrieved from the network node 130 within, using sensing data or similar. The network node 130 may also determine position related information such as trajectory of the UE 10.

[0101] Action 502. The network node 130 may transmit to the UE 10 a request for requesting position of the UE 10.

[0102] Action 503. The UE 10 may determine the position of the UE 10. The UE may determine position of method not using the radio network node 12 position such as GNSS, global positioning system (GPS), European Geostationary Navigation Overlay Service (EGNOS), Wide Area Augmentation System (WAAS), Russian Global Navigation Satellite system (GLONASS), BeiDou Navigation Satellite System, Galileo Navigation with Indian Constellation (NavIC), Quasi-Zenith Satellite System (QZSS), etc

[0103] Action 504. The UE 10 may transmit a response with the determined position of the UE 10. The UE 10 may transmit a position indication such as a reference value, a coordination indication, a distance value, a direction value and / or the like.

[0104] Action 505. The network node 130 may compare the determined position of the UE 10 with the the position indicated in the response.

[0105] Action 506. In case the comparison indicates a difference in the positions of the UE 10, the network node 130 may then perform a calibration procedure to re-positioning the radio network node 12. The method actions performed by the network node 130 for handling sensing of one or more sensing objects in the wireless communication network according to embodiments herein will now be described with reference to a flowchart depicted in Fig. 6. The actions do not have to be taken in the order stated below, but may be taken in any suitable order. Actions performed in some embodiments are marked with dashed boxes.

[0106] Action 601. The network node 130 obtains an indication of a position of the radio network node 12 in the wireless communication network. The indication may be a reference value, coordination values, or similar. The indication may be received from the radio network node 12, retrieved from within, received from another network node or configured at the network node 130. The indication of the position of the radio network node may be a position of the radio network node 12 and / or a position of a UE such as the UE. The position of the UE may indicate the position of the radio network node 12.

[0107] Action 602. The network node 130 may obtain from one or more UEs, reference position data related to the position of the radio network node 12. The reference position data may be the position of UEs, the radio network node 12 or a sensing object.

[0108] Action 603. The network node 130 may determine a UE position of at least one UE based on the position of the radio network node 12. The UE position may be determined by using sensing data, and / or similar.

[0109] Action 604. The network node 130 may request the at least one UE to provide its UE position not based on the position of the radio network node, for example, using internal sensors or similar.

[0110] Action 605. The network node 130 may receive a position indication from the UE indicating the UE position. The position indication may comprise a reference value, a coordination indication, a distance value, a direction value and / or the like.

[0111] Action 606. The network node 130 may compare the determined UE position with the received position indication. The calibration procedure may be triggered based on the comparison. For example, if a position delta between UE-position obtained from UE and determined UE position differs larger than a threshold value.

[0112] Action 607. The network node 130 may receive a request from one or more UEs for requesting position and / or trajectory of the respective UE.

[0113] Action 608. The network node 130 may determine a position and / or trajectory of at least one UE of the one or more UEs. This may be retrieved from the network node 130 within, using sensing data or similar.

[0114] Action 609. The network node 130 may transmit a response with the determined position and / or trajectory of the at least one UE. Action 610. The network node 130 may receive a trigger indication from one or more UEs indicating to trigger the calibration procedure. The trigger indication may be a value, a difference value, a flag, or similar.

[0115] Action 611. The network node 130 triggers a calibration procedure of the position of the radio network node 12 upon fulfillment of a condition. The condition may take the obtained indication into account. The condition may be related to an event, an occasion, a periodicity, a positioning difference to reported positions, receive a trigger indication from UE, UE positions and / or number of UEs reporting differing position indications from said indicated position. The calibration procedure may be triggered when the position of the indication, see action 601, differs from the position of the radio network node from the obtained reference position data, see action 602. The calibration procedure may be triggered when a position difference exceeds a threshold value. The position difference may be indicated by a difference between the position of the indication, see action 601 , and the position of the radio network node from the obtained reference position data, see action 602. The condition may define that if position offset>threshold for a number (more than 3) of trusted UEs requested for positioning, is determined, the radio network node 12 is considered mis-positioned, and a procedure to update the position is initiated. As an example, the network node 130 may obtain an indication of a position / trajectory of a UE in the wireless communication network, and the network node determines position / trajectory for said UE. The network node 130 may then compare the UE determined position and / or trajectory with the network node determined position and / or trajectory; and may trigger the calibration procedure of the position of the radio network node based on the comparison.

[0116] The calibration procedure may comprise repositioning the radio network node 12 and / or to take the position error into account in a signalling procedure such as sensing procedure, an optimization procedure, and / or radio coverage procedure.

[0117] The calibration procedure may comprise one or more of the following: ■

[0118] - pre-configured in the network node 130 in the aspects how to behave, e.g. a set of illustration, 3D models, photos, etc., in the UE 10 could show the user how to place the UE 10 for correct position during a calibration session, o such as a physical orientation enabling best localisation performance depending on network deployment neighbouring area, e.g. device not with back- on-table, but held in an upright position, etc.;

[0119] - use specific known location(s), in the sense of e.g. access area, such as port, garage, no-cross line, traffic signal, bus stop, packet drop points, service center points, etc., where a specific OoB signal is associated with a physically well-defined location;

[0120] - environment scanning carried out by UE and / or the radio network node and associated geo-localisation lookup, such as: o Reading street signs, mapping street, street-view, landmarks, etc. to resolve e.g. a street-position, o OoB signals towards Reconfigurable intelligent surfaces (RlS)Zintelligent reflecting surface (IRS) operating in non-cellular domain,

[0121] - previously known / trusted location that the user-device has acknowledged: o Dead- reckoning based on inertial measurement unit (IMU) with regards to said from known / trusted previous locations

[0122] - GNSS solutions: such as GPS, EGNOS, WAAS, GLONASS, BeiDou Navigation Satellite System, NavIC, QZSS, etc.

[0123] Thus , the calibration procedure may comprise a sensing procedure involving a sensing function node, one or more radio network nodes, and / or one or more UEs. The calibration procedure may comprise to compensate an ISAC-based position request from a UE in respect to an updated true radio network node position; provide to a network node an indication of a position update of the radio network node, and / or provide a delta value in respect to current used position of the radio network node 12. The calibration procedure may further comprise notify any receiver of positioning information (from sensing) that the accuracy is not good enough, and / or correcting one or more measurements.

[0124] The method actions performed by the UE 10 for handling sensing of one or more sensing objects in the wireless communication network according to some embodiments herein will now be described with reference to a flowchart depicted in Fig. 7. The actions do not have to be taken in the order stated below, but may be taken in any suitable order. Actions performed in some embodiments are marked with dashed boxes.

[0125] Action 701. The UE 10 may request from the network node 130 a determined position and / or trajectory of the UE 10.

[0126] Action 702. The UE 10 determines the position and / or trajectory of the UE 10. This may be based on internal sensors, sensing data or similar.

[0127] Action 703. The UE 10 receives from the network node 130, the indication of the determined position and / or trajectory of the UE 10, determined at the network node 130. The indication may be received in the response to the request in action 701.

[0128] Action 704. The UE 10 compares the UE determined position and / or trajectory with the network node determined position and / or trajectory.

[0129] Action 705. The UE 10 triggers the calibration procedure of the position of the radio network node based on the comparison. The UE 10 may transmit the trigger indication to the network node 130. The trigger indication may be a value, a difference value, a flag, or similar.

[0130] Action 706. The UE 10 may perform a sensing procedure for calibrating the position of the radio network node 12. Thus, sensing using deployed RAN nodes, such as UEs and / or radio network nodes, to establish the existence or position of an object assumes that a correct position of each node is known. Any position error in the node position affects the sensing accuracy. As a user requesting sensing with some accuracy, one relies on that the system knows the position of each node with sufficient accuracy. Similarly, the systems assume that nodes are positioned according to the information with which the system is configured. Assuming there is a case where the requester is particularly keen on knowing that the sensing result is correct, there should be some method to check the accuracy. Such a procedure may also be used to check or maintain the positioning accuracy of the network. Introducing the capability of checking the accuracy of a radio network node’s position adds flexibility to the entire system of UEs and radio network nodes, i.e. when the system provides positioning of UEs or sensing for any type of object, of a size that is possible to detect with radio signalling.

[0131] An advantage of adding the capability of checking accuracy of the radio network node’s position to UEs and / or network nodes in the wireless communication network is flexibility regarding timing and calibration geometries as UEs can move throughout the wireless communication network.

[0132] A scenario when checking accuracy of the radio network node’s position is used could be when sensing is used for the first time. When a cell in the wireless communication network has been made capable of sensing UEs can be positioned in a known location; the network node 130 may perform measurements to see if the known position and measured positions are aligned. The calibration procedure of the radio network node’s position may be used regularly to make sure that the positions of the radio network nodes have not changed. For example, the UE 10 moving along a street in a cell can request that the network node 130 tracks the UE trajectory. If the UE 10, using e.g. GNSS or other internal sensor, finds that the sensing trajectory differs from the own trajectory it may be due to a position error of the radio network node 12 for which the calibration procedure is initiated.

[0133] A use case of embodiments herein may be to check for obstacles when driving a car. The driver or some system in the car may initiate the calibration procedure because some measurement on the route is incorrect, e.g., difference may be over a set threshold. To perform the calibration procedure a UE such as a car e.g. stops at a red light, a stop sign, or a parking space, from which there is LOS to a radio network node capable and configured for sensing. The car may have sensors to be able to determine its position with high accuracy, e.g. lidar, radar, camera, etc. Once the car has determined its position it connects with the radio network node 12 and asks the radio network node 12 to determine the position of the car using sensing procedure. Some function in the car compares its own position with the one determined by the radio network node 12. If the difference is large, e.g., above some threshold or several thresholds since the determination may have up to three dimensions, the car will notify the radio network node 12, and probably also the sensing control and Operations, Administration and Maintenance (OAM), that the radio network node 12 needs to calibrate its position.

[0134] In Fig. 8 it is shown a procedure for performing sensing of an area. An external (ext) application requests an area with coordination values (x,y,z,r) with ID and QoS to be sensed, action 801. The sensing central checks if request is acceptable at a map data base (dB), action 802. The sensing central may receive a response with map configuration indicating a radio network node for the requested coordination values, action 803. The sensing central may then activate or initiate sensing procedure at the correct radio network node, e.g., gNB, see action 804. An authentication procedure may be performed between the gNB and the sensing central, action 805. The gNB may configure radio signalling, action 806, and may then perform sensing measurement over the area, action 807. For the evaluation, the gNB may then send results to the sensing central that may perform calculations, action 808. The sensing central and the ext may then exchange results and / or billing information, action 809. It should be noted that sensing repositioning calculations and associated device communications may occur at the calculations action 808 given that some too large positioning error has been identified "during operations" of some positioning-sensing activity, initiated either from a device detecting "poor positioning data" or from a network node determining the same. During a positioning operation where e.g., a node has determined offset A is determined above threshold, this may trigger a re-positioning event from higher layers. On the other hand, if the repositioning calibration procedure is periodically initiated by some O&M node, perhaps triggered by some tornado, earthquake, etc., the sensing calibration procedure may occur as a sensing action itself where system identifies some nodes to question for positioning data and then calculations are done. In that case, the calibration procedure may involve and start to some extent at the external application or as an external event

[0135] For calibration purposes, a setup may comprise a UE with an embedded Subscriber Identity Module (eSIM), i.e. a device connected to the cellular network is used for the calibration. The eSIM provisioned for a UE means that the UE 10 has a trust and acknowledgement from its MNO towards sensing actions and required compute, i.e., access to said nodes, via its subscription. This means that authentication can be assumed present implicitly from the device being a 3GPP UE, or similar, with the advantages that less explicit signalling is required when setting up the measurement, e.g., the calibration sensing measurement can skip some of the signalling in Fig. 8. Embodiments herein may also be used outside a 3GPP infrastructure, that may however require similar joint-communication-sensing / processing framework to be described also in context of that connectivity.

[0136] There may be UEs involved in the embodiments herein that are dedicated for the calibration purpose. In the most basic case, the UE’s preference for taking part in the embodiments herein is part of the subscription information. It may be so that the UE 10 with a subscription has a lower rate or some other reason to take part in the embodiments herein. The UE 10 involved in the embodiments herein may furthermore have certain capabilities for sensing, e.g. there may be a certain type of device capability for a UE to assist the wireless communication network with sensing and calibration. The UE 10 involved in the embodiments herein may need to be configured accordingly and have enough power in the battery for the calibration and other communication; a certain type of device suited for calibration purposes given their power supply and scanning (lidar / image based) are vehicles. The UE 10 assumed to participate in said calibration procedure may also be considered trusted, e.g. as part of subscription, superusers, National Security Public Safety (NSPS), etc..

[0137] In the text below one or more examples of some embodiments are described. The process may be initiated for one of the exemplary reasons described above, or perhaps other reasons.

[0138] • The UE 10 may find a physical location with LOS to the radio network node 12 that is to be position calibrated.

[0139] LOS may be determined from simulations based:

[0140] - on a deployment map;

[0141] - from image-based object-scenery recognition-classification;

[0142] - from measurement, using e.g. laser / lidar;

[0143] - determined from UE / device processing of DL reference symbols; and / or

[0144] - etc.

[0145] • In said acquired LOS position to the radio network node 12, the UE 10 may further acquire a local position relative object with known fixed location, where several methods may apply, such as:

[0146] - device sensors determine position relative a statue, or the corner of a building, i.e. something fixed that has a known location; multiple object lidar scanning / object recognition, e.g. “known roadsignl direction 34 degree at 3.3 m distance”, “known roadsign2 direction -55 degree at 6.3 m” distance, provides known true location; i.e., triangulation in respect to more than three known physical objects, and / or further according to exemplified use case, deployments, type of devices, etc.), e.g. according to list exemplified above

[0147] UE determines its true physical location such as coordinates for the UE, [X, Y, Z]ue + / - Location ErrorUE based on triangulation towards N known physical objects; and / or based on methods the calibration procedure examples, etc.

[0148] • The UE 10 or the network node 130 may:

[0149] - acquire from:

[0150] - a network sensing node, such as an SCF, or higher layers via SCF, etc., a request to perform “calibrate sensing” action, for example triggered by:

[0151] - accumulated calibration requests from other UEs or the network nodes; request from OAM / CN layer from external service; based on OoB sources; current / historical weather conditions; periodically;

[0152] - etc. ,

[0153] UE’s application layer, a request to perform embodiments herein, for example, triggered on preceding use of ISAC based sensing where an offset towards UE’s own positioning application data, e.g. road-lane alignment, stop sign / line localisation, etc., in vehicle application, is determined larger than a predefined threshold, and / or periodically, according to predefined schedule either acquired from SCF device application setting,

[0154] - etc.

[0155] - execute according to preceding acquired request, a sensing process by sending “calibrate sensing” command to a sensing node, depending on embodiment:

[0156] UE may in background using said OoB information establish a true physical location, and when obtained, e.g., position precision > threshold, initiate the calibration procedure with indicative message that “UE is ready for calibration”, and wait for inbound network-initiated calibration procedure to start, in which UE 10 supplies its true position value in a certain message body, where said message body may include:

[0157] - true OoB obtained physical position, or - any ISAC-related information requested from radio network node 12 as part of ongoing ISAC sensing action initiated from the radio network node 12, It should be noted that depending on positioning scheme assumed by network to obtain an estimate of UE’s position, system may require device to provide / report selected location services (LCS) information elements; and / or

[0158] - combinations thereof.

[0159] - The UE or network node 130 may after completion of said true location better than a precision threshold, provide towards sensing node its true position value in a certain message body, which upon detection by sensing node triggers further calibration actions in the sensing node, and / or

[0160] - Sensing node, such as an SCF, via the radio network node 12, may periodically request towards the UE 10 a true location estimate, which UE depending on availability, such as location / LOS, battery status, device-occupied-in-other- use, etc., may provide or decline.

[0161] From a network side, the calibration procedure according to some embodiments herein may be initiated by the network node 130 such as a Sensing node such as a SCF, according to one or more of the following:

[0162] • sensing node initiates sensing by sending a command to a correct radio network node targeting at least one UE that previously provided a true- location-available message

[0163] • radio network node performs required measurement and returns result to sensing node

[0164] • sensing node provides sensing result to its calibration functionality

[0165] • calibration functionality in Sensing node, then compares:

[0166] - sensing result associated with current position data from requested UE(s) with

[0167] - true-location data acquired from the same UE, and

[0168] • calibration functionality in the sensing node then calculates the difference in UE-location determined from said data sets, e.g. according to position_delta = norm_function(UEsensing, UEtrue, “2-norm”), and furthermore, If a position_delta > offset_threshold, i.e. that determined offset between sensing-estimated UE-position and true-known UE-position is larger than a sanity threshold, then

[0169] - store current offset value position_delta into set of position_delta values for acquired UEi and time-stamp, and associated with estimated location error acquired via UE-method-provided LocationErrorllE and SCF-method-provide LocationErrorSCF;

[0170] • the calibration procedure in the sensing node may:

[0171] - determine

[0172] - acquired position_delta values > set_threshold (i.e. sufficiently many samples), that furthermore are,

[0173] - distributed over sufficiently many:

[0174] - devices (represented by individual device i, and / or trusted users j, or a combination thereof depending on use-case),

[0175] - type of devices (smartphone, type A,B,C; smartwatch; tablet, laptop; ... , device capabilities),

[0176] - context parameter set {hour of day, winter / summer, weather conditions, road infrastructure status, etc.}

[0177] - further determined having as a set LocationErrorValue < threshold

[0178] I.e. that sufficiently many position-offset-samples are obtained, where said samples are “well aligned” in the aspect that all / most / enough of the position offset samples are in one certain offset-direction (with location error small enough), and where a sufficiently diverse set of users / devices have provided said data, typically ending up in an estimated distance offset measure (in 2D / 3D space) derived from a sufficiently narrow / well defined position offset value distribution, ...

[0179] - select determined position_delta as a position correction factor

[0180] - supply position correction factor towards

[0181] - a managing node such as a SCF managing system holding information of respective sensing transmission point, i.e. gNB, antennas, remote radio units (RRU), etc., assumed locations:

[0182] - so that next requests of positioning services are based on an updated and now more accurate assumption of location, e.g. as improvement towards problem description;

[0183] - so that next positioning data provided in accordance with a positioning request is provided, now including a position offset_correction_factor that application can apply to a next acquired value of ISAC-based positioning,

[0184] - furthermore, one may evaluate if the norm (UEsensing_position, UEtrue_position, “2- norm”) now is improved compared to a previously evaluation that triggered poor location estimate, or the UE may resupply towards SCF a repeated “calibrate sensing” request. Euclidean distance in an Euclidean space is defined by a norm on the associated Euclidean vector space, called the Euclidean norm, the 2-norm. Sometimes also called the magnitude of the vector.

[0185] - furthermore, one may disclose towards requesting device / application / user, information associated with said offset_correction_factor such as “high I medium I low” accuracy in respect how large the determined offset_correction_factor is compared to the requested accuracy of the considered user positioning service.

[0186] - an OAM node or CN node holding general deployment information associated with the cellular network, to further update:

[0187] - a database entry of respective ISAC transmission node’s physical location, with respect to determined offset_correction_factor, etc. Fig. 9 is a block diagram depicting embodiments of the network node 130, such as the radio network node 12, a sensing node, an OAM node, or a core network node, for handling sensing of one or more sensing objects in the wireless communications network according to embodiments herein.

[0188] The network node 130 may comprise processing circuitry 901, e.g., one or more processors, configured to perform the methods herein.

[0189] The network node 130 and / or the processing circuitry 901 is configured to obtain the indication of the position of the radio network node 12 in the wireless communication network.

[0190] The network node 130 and / or the processing circuitry 901 is configured to trigger the calibration procedure of the position of the radio network node 12 upon fulfillment of the condition. The condition may take the obtained indication into account. The condition may be related to an event, an occasion, a periodicity, a positioning difference to reported positions, UE positions, and / or number of UEs reporting differing position indications from said indicated position.

[0191] The network node 130 and / or the processing circuitry 901 may be configured to obtain from one or more UEs, reference position data related to the position of the radio network node 12, and the calibration procedure may be triggered when the position of the indication differs from the position of the radio network node 12 from the obtained reference position data. The calibration procedure may be triggered when the position difference exceeds a threshold value.

[0192] The network node 130 and / or the processing circuitry 901 may be configured to determine the UE position of at least one UE based on the position of the radio network node 12. The network node 130 and / or the processing circuitry 901 may be configured to request the at least one UE to provide its UE position not based on the position of the radio network node 12. The network node 130 and / or the processing circuitry 901 may be configured to receive the position indication from the at least one UE 10 indicating the UE position; and compare the determined UE position with the received position indication; and wherein the calibration procedure may be triggered based on the comparison.

[0193] The network node 130 and / or the processing circuitry 901 may be configured to receive the request from one or more UEs, for requesting position and / or trajectory of the respective UE. The network node 130 and / or the processing circuitry 901 may be configured to determine the position and / or trajectory of at least one UE of the one or more UEs; and to transmit the response with the determined position and / or trajectory of the at least one UE.

[0194] The network node 130 and / or the processing circuitry 901 may be configured to receive the trigger indication from the one or more UEs, indicating to trigger the calibration procedure.

[0195] The calibration procedure may comprise repositioning the radio network node 12.

[0196] The calibration procedure may comprise a sensing procedure involving a sensing function node, one or more radio network nodes, and / or one or more UEs. The calibration procedure may comprise: to compensate an ISAC-based position request from a UE, in respect to an updated true radio network node position; and / or provide to a network node an indication of a position update of the radio network node 12, and / or the delta value in respect to current used position of the radio network node.

[0197] The network node 130 may comprise a memory 905. The memory 905 comprises one or more units to be used to store data on, such as data packets, configuration, positioning information, sensing information, context data, UE information, calibration procedures, measurements, events and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the network node 130 may comprise a communication interface 906 comprising such as a transmitter, a receiver, a transceiver and / or one or more antennas.

[0198] The methods according to the embodiments described herein for the network node 130 are respectively implemented by means of e.g., a computer program product 907 or a computer program, comprising instructions, i.e. , software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the network node 130. The computer program product 907 may be stored on a computer-readable storage medium 908, e g., a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium 908, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the network node 130. In some embodiments, the computer-readable storage medium may be a transitory or a non- transitory computer-readable storage medium. Thus, embodiments herein may disclose a network node 130 for handling sensing of one or more sensing objects in a wireless communications network, wherein the network node 130 comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said network node 130 is operative to perform any of the methods herein.

[0199] Fig. 10 is a block diagram depicting embodiments of the UE 10 for handling sensing of one or more sensing objects in the wireless communications network according to embodiments herein.

[0200] The UE 10 may comprise processing circuitry 1001 , e.g., one or more processors, configured to perform the methods herein.

[0201] The UE 10 and / or the processing circuitry 1001 is configured to determine the position and / or the trajectory of the UE 10.

[0202] The UE 10 and / or the processing circuitry 1001 is configured to receive, from the network node 130, the indication of the determined position and / or trajectory of the UE 10, determined at the network node 130. The UE 10 and / or the processing circuitry 1001 is configured to compare the UE determined position and / or trajectory with the network node determined position and / or trajectory; and trigger the calibration procedure of the position of the radio network node based on the comparison.

[0203] The UE 10 and / or the processing circuitry 1001 may be configured to request from the network node 130 a determined position and / or trajectory of the UE; and the indication is received in a response to the request.

[0204] The UE 10 and / or the processing circuitry 1001 may be configured to trigger the calibration process by transmitting the trigger indication to the network node 130.

[0205] The UE 10 and / or the processing circuitry 1001 may be configured to perform a sensing procedure for calibrating the position of the radio network node 12.

[0206] The UE 10 may comprise a memory 1005. The memory 1005 comprises one or more units to be used to store data on, such as data packets, configuration, positioning information, sensing information, context data, UE information, calibration procedures, measurements, events and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the UE 10 may comprise a communication interface 1006 comprising such as a transmitter, a receiver, a transceiver and / or one or more antennas.

[0207] The methods according to the embodiments described herein for the UE 10 are respectively implemented by means of e.g., a computer program product 1007 or a computer program, comprising instructions, i.e. , software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the UE 10. The computer program product 1007 may be stored on a computer- readable storage medium 1008, e.g., a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium 1008, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the UE 10. In some embodiments, the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium. Thus, embodiments herein may disclose a UE 10 for handling sensing of one or more sensing objects in a wireless communications network, wherein the UE 10 comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said UE 10 is operative to perform any of the methods herein.

[0208] In some embodiments a more general term “network node” or “radio network node” is used and it can correspond to any type of radio-network node or any network node, which communicates with a UE and / or with another network node.

[0209] In some embodiments the non-limiting term wireless device or user equipment (UE) is used and it refers to any type of wireless device communicating with a network node and / or with another wireless device in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, proximity capable UE (aka ProSe UE), loT capable device, machine type UE or UE capable of machine to machine (M2M) communication, Tablet, mobile terminals, smart phone, reduced capability (RedCap) device, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, etc.

[0210] Embodiments are applicable to any RAT or multi-RAT systems, where the wireless device receives and / or transmit signals (e.g. data) e.g. NR, Wi-Fi, LTE, LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications / enhanced Data rate for GSM Evolution (GSM / EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.

[0211] As will be readily understood by those familiar with communications design, that functions means or circuits may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a wireless device or network node, for example.

[0212] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware and / or program or application data. Other hardware, conventional and / or custom, may also be included. Designers of communications devices will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0213] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according to one or more embodiments of the present disclosure.

[0214] Fig. 11 shows an example of a communication system QQ100 in accordance with some embodiments.

[0215] In the example, the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network QQ102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network QQ102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organisation) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network QQ102, including one or more network nodes QQ110 and / or core network nodes QQ108.

[0216] Examples of an ORAN network node include an open radio unit (0-Rll), an open distributed unit (0-Dll), 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 A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes QQ110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 over one or more wireless connections.

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

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

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

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

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

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

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

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

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

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

[0227] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0228] The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input / output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Fig. 12. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

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

[0230] In the example, the input / output interface QQ206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE QQ200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device. In some embodiments, the power source QQ208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and / or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0248] In certain alternative embodiments, the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio front-end circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).

[0249] The antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna QQ310 may be coupled to the radio front-end circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port.

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

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

[0252] Embodiments of the network node QQ300 may include additional components beyond those shown in Fig. 13 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300. In some embodiments providing a core network node, such as core network node of Fig. 11 , some components, such as the radio front-end circuitry QQ318 and the RF transceiver circuitry QQ312 may be omitted.

[0253] Fig. 14 is a block diagram illustrating a virtualization environment QQ500 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 QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment QQ500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface. Virtualization may facilitate distributed implementations of a network node, UE, core network node, or host.

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

[0255] Hardware QQ504 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 QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ508a and QQ508b (one or more of which may be generally referred to as VMs QQ508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.

[0256] The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, 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.

[0257] In the context of NFV, a VM QQ508 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 QQ508, and that part of hardware QQ504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.

[0258] Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 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 QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 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 signalling can be provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.

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

[0260] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0261] In some embodiments a more general term “network node” is used and it can correspond to any type of radio network node or any network node, which communicates with a wireless device and / or with another network node. Examples of network nodes are NodeB, Master eNB, Secondary eNB, a network node belonging to Master cell group (MCG) or Secondary Cell Group (SCG), base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), core network node e.g. Mobility Switching Centre (MSC), Mobile Management Entity (MME) etc., Operation and Maintenance (O&M), Operation Support System (OSS), Self-Organizing Network (SON), positioning node e.g. Evolved Serving Mobile Location Centre (E-SMLC), Minimizing Drive Test (MDT), etc.

[0262] In some embodiments, the non-limiting term wireless device or user equipment (UE) is used and it refers to any type of wireless device communicating with a network node and / or with another UE in a cellular or mobile communication system. Examples of UE are target device, device-to-device (D2D) UE, proximity capable UE (aka ProSe UE), machine type UE or UE capable of machine to machine (M2M) communication, PDA, PAD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles etc.

[0263] The embodiments are described for 5G. However the embodiments are applicable to any RAT or multi-RAT systems, where the UE receives and / or transmit signals (e.g. data) e.g. LTE, LTE FDD / TDD, WCDMA / HSPA, GSM / GERAN, Wi Fi, WLAN, CDMA2000 etc.

[0264] As will be readily understood by those familiar with communications design, functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a wireless device or network node, for example.

[0265] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and non-volatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications devices will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0266] It will be appreciated that the foregoing description and the accompanying drawings represent non-limiting examples of the methods and apparatus taught herein. As such, the apparatus and techniques taught herein are not limited by the foregoing description and accompanying drawings. Instead, the embodiments herein are limited only by the following claims and their legal equivalents.

[0267] References:

[0268] 1. LIZ LANGLEY (2021) Echolocation is nature's built-in sonar. Here's how it works. National Geographic, Feb 3, 2021. https: / / www.nationalgeographic.com / animals / article / echolocation-is-nature-built-in-sonar- here-is-how-it-works

[0269] 2. C. Chen, H. Song, Q. Li, F. Meneghello, F. Restuccia and C. Cordeiro, "Wi-Fi Sensing Based on IEEE 802.11bf," in IEEE Communications Magazine, vol. 61, no. 1, pp. 121-127, January 2023, doi: 10.1109 / MCOM.007.2200347. Wi-Fi Sensing Based on IEEE 802.11bf

[0270] 3. C. Cordiero (2022) WIFI unleashed: WIFI 7, 6 GHz and beyond. Intel Corporation presentation.

[0271] 4. Reiner Thoma et al. (2012) Joint communication and Radar Sensing: An overview. EuCAP 2021 convened session "Convergence of Mobile Radio and Radar".

[0272] 5. Monserrat, O. (2012). Deformation measurement and monitoring with GB-SAR.

[0273] 6. A. M. Khalili, Abdel-Hamid Soliman, Md Asaduzzaman, Alison Griffiths; "Wi-Fi Sensing: Applications and Challenges", https: / / arxiv.org / abs / 1901.00715

[0274] 7. Tim Newcomb, Poplar Mechanics, published: JAN 19, 2023, "Scientists Can Now Use WiFi to See Through People's Walls" https: / / www.popularmechanics.com / technology / security / a42575068 / scientists-use-wifi- to-see-through-walls /

[0275] 8. Jiaqi Geng, Dong Huang, Fernando De la Torre, "DensePose From WiFi", https: / / arxiv.org / pdf / 2301.00250.pdf 9. Mingmin Zhao et al., MIT CSAIL, 2018, "Through-Wall Human Pose Estimation Using Radio Signals", https: / / openaccess.thecvf.com / content_cvpr_2018 / CameraReady / 2406.pdf

Claims

1. CLAIMS1. A method performed by a network node (130) for handling sensing of one or more sensing objects in a wireless communication network, the method comprising: obtaining (601) an indication of a position of a radio network node (12) in the wireless communication network; and triggering (611) a calibration procedure of the position of the radio network node (12) upon fulfillment of a condition.

2. The method according to claim 1, wherein the condition takes the obtained indication into account.

3. The method according to any of the claims 1-2, wherein the condition is related to an event, an occasion, a periodicity, a positioning difference to reported positions, user equipment, UE, positions, and / or number of UEs reporting differing position indications from said indicated position.

4. The method according to any of the claims 1-3, further comprising: obtaining (602), from one or more UEs, reference position data related to the position of the radio network node, and the calibration procedure is triggered when the position of the indication differs from the position of the radio network node from the obtained reference position data.

5. The method according to claim 4, wherein the the calibration procedure is triggered when a position difference exceeds a threshold value.

6. The method according to any of the claims 1-5, further comprising: determining (603) a user equipment, UE, position of at least one UE based on the position of the radio network node; requesting (604) the at least one UE to provide its UE position not based on the position of the radio network node; receiving (605) a position indication from the UE indicating the UE position; and comparing (606) the determined UE position with the received position indication; and wherein the calibration procedure is triggered based on the comparison.

7. The method according to any of the claims 1-6, further comprising receiving (607) a request from one or more user equipments, UE, for requesting position and / or trajectory of the respective UE; determining (608) a position and / or trajectory of at least one UE of the one or more UEs; and transmitting (609) a response with the determined position and / or trajectory of the at least one UE.

8. The method according to any of the claims 1-7, further comprising receiving (610) a trigger indication from one or more user equipments, UE, indicating to trigger the calibration procedure.

9. The method according to any of the claims 1-8, wherein the calibration procedure comprises repositioning the radio network node.

10. The method according to any of the claims 1-9, wherein the calibration procedure comprises a sensing procedure involving a sensing function node, one or more radio network nodes, and / or one or more UEs.

11. The method according to any of the claims 1-10, wherein the calibration procedure comprises to compensate an Integrated sensing and communications, ISAC, -based position request from a user equipment, UE, in respect to an updated true radio network node position; and / or provide to a network node an indication of a position update of the radio network node, and / or a delta value in respect to current used position of the radio network node.

12. A method performed by a user equipment, UE, (10) for handling sensing of one or more sensing objects in a wireless communication network, the method comprising: determining (702) a position and / or trajectory of the UE; receiving (703), from a network node (130), an indication of a determined position and / or trajectory of the UE, determined at the network node (130); comparing (704) the UE determined position and / or trajectory with the network node (130) determined position and / or trajectory; and triggering (705) a calibration procedure of the position of a radio network node (12) based on the comparison.

13. The method according to claim 12, further comprisingrequesting (701) from the network node (130) a determined position and / or trajectory of the UE; and the indication is received in a response to the request.

14. The method according to any of the claims 12-13, wherein triggering comprises transmitting a trigger indication to the network node (130).

15. The method according to any of the claims 12-14, further comprising performing (706) a sensing procedure for calibrating the position of the radio network node.

16. A network node (130) for handling sensing of one or more sensing objects in a wireless communication network, wherein the network node is configured to : obtain an indication of a position of a radio network node (12) in the wireless communication network; and trigger a calibration procedure of the position of the radio network node (12) upon fulfillment of a condition.

17. The network node (130) according to claim 16, wherein the condition takes the obtained indication into account.

18. The network node (130) according to any of the claims 16-17, wherein the condition is related to an event, an occasion, a periodicity, a positioning difference to reported positions, user equipment, UE, positions, and / or number of UEs reporting differing position indications from said indicated position.

19. The network node (130) according to any of the claims 16-19, wherein the network node is configured to: obtain, from one or more user equipments, UE, reference position data related to the position of the radio network node, and the calibration procedure is triggered when the position of the indication differs from the position of the radio network node (12) from the obtained reference position data.

20. The network node (130) according to claim 19, wherein the the calibration procedure is triggered when a position difference exceeds a threshold value.

21. The network node (130) according to any of the claims 16-20, wherein the network node (130) is configured to: determine a user equipment, UE, position of at least one UE based on the position of the radio network node (12); request the at least one UE to provide its UE position not based on the position of the radio network node (12); receive a position indication from the UE indicating the UE position; and compare the determined UE position with the received position indication; and wherein the calibration procedure is triggered based on the comparison.

22. The network node (130) according to any of the claims 16-21, wherein the network node is configured to receive a request from one or more user equipments, UE, for requesting position and / or trajectory of the respective UE; determine a position and / or trajectory of at least one UE of the one or more UEs; and transmit a response with the determined position and / or trajectory of the at least one UE.

23. The network node (130) according to any of the claims 16-22, wherein the network node is configured to receive a trigger indication from one or more user equipments, UE, indicating to trigger the calibration procedure.

24. The network node (130) according to any of the claims 16-23, wherein the calibration procedure comprises repositioning the radio network node.

25. The network node (130) according to any of the claims 16-24, wherein the calibration procedure comprises a sensing procedure involving a sensing function node, one or more radio network nodes, and / or one or more UEs.

26. The network node (130) according to any of the claims 16-25, wherein the calibration procedure comprises to compensate an Integrated sensing and communications, ISAC, -based position request from a user equipment, UE, in respect to an updated true radio network node position; and / or provide to a network node an indication of a position update of the radio network node, and / or a delta value in respect to current used position of the radio network node.

27. A user equipment, UE, (10) for handling sensing of one or more sensing objects in a wireless communication network, wherein the UE is configured to: determine a position and / or trajectory of the UE; receive, from a network node, an indication of a determined position and / or trajectory of the UE, determined at the network node; compare the UE determined position and / or trajectory with the network node determined position and / or trajectory; and trigger a calibration procedure of the position of a radio network node based on the comparison.

28. The UE (10) according to claim 27, wherein the UE is configured to request from the network node (130) a determined position and / or trajectory of the UE; and the indication is received in a response to the request.

29. The UE (10) according to any of the claims 27-28, wherein the UE is configured to trigger the calibration process by transmitting a trigger indication to the network node (130).

30. The UE (10) according to any of the claims 27-29, wherein the UE is configured to perform a sensing procedure for calibrating the position of the radio network node (12).

31. A computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the claims 1-15, as performed by the network node, and the UE, respectively.

32. A computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to the any of the claims 1-15, as performed by the network node, and the UE, respectively.

Images