Apparatuses and methods for signalling for locating a device

APPARATUSES AND METHODS FOR SIGNALLING FOR LOCATING A DEVICE

TECHNICAL FIELD

[0001 ] The present application relates to a field of wireless radio communications, and more particularly to one or more devices configured for signalling in determining location of a target device in wireless radio communication. Furthermore, the invention relates to corresponding methods and a computer program.

BACKGROUND

[0002] In wireless radio communication, location services, LCS, are a network provided technology, which enables the positioning of devices, such as mobile phones. LCS may be used, for example, in radio resource management, beam management, lawful interception, or emergency calls, etc. The location of a device can be determined through various methods. For example, in a simple case, multiple base stations can transmit signals to the device, and based on how long these signals take to reach the device, with the known locations of the base stations, the location of the device can be determined.

[0003] With new radio communication technologies, more accurate positioning services are becoming possible. For example, with the upcoming 5G technology, positioning with accuracy better than one metre may be supported. However, high accuracy positioning may not be beneficial in all situations, if the location cannot be provided with low latency.

SUMMARY

[0004] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0005] It is an object to provide methods for reduce latency and signalling in location services in wireless radio communication. The object is achieved by the features of the independent claims. Further implementation forms are provided in the dependent claims, the description and the figures. [0006] According to a first aspect, a network positioning device is configured to receive a location service request, LSR; determine a location of a target device according to the LSR; determine if a client device that initiated the LSR is connected to a same radio access network, RAN, as the target device; and transmit a location service response addressed directly to the client device, if the client device and the target device are connected to the same RAN, otherwise transmit the location service response meant for a network management device further including an identification of the network positioning device, wherein the location service response comprises the location of the target device. This may, for example, reduce latency and signalling, which in turn may increase the accuracy of the positioning.

[0007] In a further implementation form of the first aspect, the network positioning device is further configured to store information about the LSR, wherein the information is such that the network positioning device can identify an upcoming LSR from the client device, if so instructed in the LSR; stop the upcoming LSR from being forwarded, if the upcoming LSR matches the information; determine an another location of the target device according to the upcoming LSR; and transmit an another location service response to the upcoming LSR. This may enable the network positioning device to respond to an LSR more quickly and with less delay. This may reduce latency and signalling, which in turn may increase the accuracy of the positioning.

[0008] In a further implementation form of the first aspect, the network positioning device is further configured to receive measurement results from multiple transmission and reception points, TRPs; and perform target device positioning computation based on the measurement results. This may enable more accurate positioning. This may reduce latency and signalling, which in turn may increase the accuracy of the positioning.

[0009] In a further implementation form of the first aspect, the client device and the target device are the same device. Thus, a device can obtain its own location more quickly. This may reduce latency and signalling, which in turn may increase the accuracy of the positioning.

[001 0] In a further implementation form of the first aspect, the network positioning device is further configured to periodically transmit a new location service response. This may reduce signalling further, because additional LSRs are not needed for updated location information. This may reduce latency and signalling, which in turn may increase the accuracy of the positioning.

[001 1 ] According to a second aspect, a network management device is configure to receive a location service request, LSR; make a decision on whether the LSR is forwarded to a core network positioning device or to a network positioning device, wherein the decision is based on the LSR; include into the LSR an instruction for the network positioning device, wherein the instruction is such that the network positioning device can identify or admit an upcoming LSR; and forward the LSR according to the decision. Thus, additional information may, for example, be taken into account when forwarding the LSR. According to the example, this may reduce latency and signalling, which in turn may increase the accuracy of the positioning.

[001 2] In a further implementation form of the second aspect, the instruction instructs the network positioning device to store information about the LSR, wherein the information is such that the network positioning device can identify the upcoming LSR from the client device. This may allow the network positioning device to fulfil upcoming LSRs more quickly. This may reduce latency and signalling, which in turn may increase the accuracy of the positioning.

[001 3] In a further implementation form of the second aspect, the instruction instructs the network positioning device to admit the upcoming LSR from the client device. Thus, the client device may address the upcoming LSR directly to the network positioning device. This may reduce latency and signalling, which in turn may increase the accuracy of the positioning.

[001 4] In a further implementation form of the second aspect, the core network positioning device comprises a positioning node in a core network, and the network positioning device comprises a positioning node in a radio access network. For example, different LSR may be fulfilled in different parts of the network. This may reduce latency and signalling, which in turn may increase the accuracy of the positioning.

[001 5] In a further implementation form of the second aspect, the decision is affected by quality of service information in the LSR, wherein a coarse-grained LSR is forwarded to the core network positioning device and a fine-grained LSR is forwarded to the network positioning device. This may reduce singling during fine-grained positioning, because measurement results do not need to be transmitted between a radio access network and a core network. This may reduce latency and signalling, which in turn may increase the accuracy of the positioning.

[001 6] In a further implementation form of the second aspect, the decision is affected by topological or geographical location of the client device and the target device. For example, the unwanted signalling may be reduced. This may reduce latency and signalling, which in turn may increase the accuracy of the positioning.

[001 7] In a further implementation form of the second aspect, the network management device is further configure to receive a location service response, wherein the location service response comprises an identification of the network positioning device; and forward the location service response. For example, the client device may address an upcoming LSR directly to the network positioning device. This may reduce latency and signalling, which in turn may increase the accuracy of the positioning.

[001 8] In a further implementation form of the second aspect, the network management device comprises a mobility management entity or an access and mobility management entity. Thus, the method is applicable to multiple wireless communication technologies. This may reduce latency and signalling, which in turn may increase the accuracy of the positioning.

[001 9] According to a third aspect, a client device is configured to transmit a first location service request, LSR, in order to obtain a location of a target device; and receive a location service response to the first LSR, wherein the location service response comprises the location of the target device and an identification, ID, of a network positioning device. For example, the client device may address an upcoming LSR directly to the network positioning device. This may reduce latency and signalling, which in turn may increase the accuracy of the positioning.

[0020] In a further implementation form of the third aspect, the client device is further configured to transmit a second LSR addressed directly to the network positioning device based on the ID in order to obtain an updated location of the target device. This may reduce latency and signalling, which in turn may increase the accuracy of the positioning.

[0021 ] In a further implementation form of the third aspect, the client device is further configured to include information about quality of service in the first LSR. This may allow the network management device to forward the LSR correctly. This may reduce latency and signalling, which in turn may increase the accuracy of the positioning.

[0022] In a further implementation form of the third aspect, the client device is further configured to transmit an acknowledgement message. For example, the network positioning device can confirm that the client device received the LS response. This may reduce latency and signalling, which in turn may increase the accuracy of the positioning.

[0023] In a further implementation form of the third aspect, the client device comprises a LCS client or a UE-requestor. For example, the client device may be any of many different devices. This may reduce latency and signalling, which in turn may increase the accuracy of the positioning.

[0024] According to a fourth aspect, a method comprises: receiving a location service request, LSR; determining a location of a target device according to the LSR; determining if a client device that initiated the LSR is connected to a same radio access network, RAN, as the target device; and transmitting a location service response addressed directly to the client device, if the client device and the target device are connected to the same RAN, otherwise transmitting the location service response meant for a network management device further including an identification of a network positioning device, wherein the location service response comprises the location of the target device.

[0025] According to a fifth aspect, a method comprises: receiving a location service request, LSR; making a decision on whether the LSR is forwarded to a core network positioning device or to a network positioning device, wherein the decision is based on the LSR; including into the LSR an instruction for the network positioning device, wherein the instruction is such that the network positioning device can identify or admit an upcoming LSR; and forwarding the LSR according to the decision.

[0026] According to a sixth aspect, a method comprises: transmitting a first location service request, LSR, in order to obtain a location of a target device; and receiving a location service response to the first LSR, wherein the location service response comprises the location of the target device and an identification, ID, of a network positioning device.

[0027] According to a seventh aspect, a computer program is provided, comprising program code configured to perform a method according to the fourth aspect, the fifth aspect, or the sixth aspect when the computer program is executed on a computer.

[0028] Many of the attendant features will be more readily appreciated as they become better understood by reference to the following detailed description considered in connection with the accompanying drawings.

DESCRIPTION OF THE DRAWINGS

[0029] The present description will be better understood from the following detailed description read in light of the accompanying drawings, wherein:

[0030] FIG. 1 illustrates a schematic representation of a block diagram of a wireless radio network according to an example;

[0031 ] FIG. 2 illustrates a schematic representation of a location services request process initiated by an external device according to an example;

[0032] FIG. 3 illustrates a schematic representation of a location service request process initiated by a device requesting for the location of a device that is connected to the same radio access network according to an example;

[0033] FIG. 4 illustrates a schematic representation of a location services request process initiated by a device requesting for its own location according to an example; and

[0034] FIG. 5 illustrates a schematic representation of multiple location services request processes initiated by a device requesting for its own location according to an example;

[0035] FIG. 6 illustrates a schematic representation of multiple location services request processes initiated by a device requesting for the location of a device that is connected to the same radio access network according to an example;

[0036] FIG. 7 illustrates a schematic representation of two consecutive location requests according to an example;

[0037] FIG. 8 illustrates a schematic representation of a network positioning device according to an example;

[0038] FIG. 9 illustrates a schematic representation of a network management device according to an example; and

[0039] FIG. 10 illustrates a schematic representation of a client device according to an example. [0040] Like references are used to designate like parts in the accompanying drawings.

DETAILED DESCRIPTION

[0041 ] The detailed description provided below in connection with the appended drawings is intended as a description of the examples and is not intended to represent the only forms in which the example may be constructed or utilized. However, the same or equivalent functions and structures may be accomplished by different examples.

[0042] According to an example, when an external location services, LCS, client requires the location of a target user equipment, UE, it sends a location service request, LSR, to a core network, CN. In the CN, the LSR is forwarded to an access and mobility management function, AMF. The AMF decides based on the LSR whether the LSR is forwarded to a location management function, LMF, or to a positioning computation function, PCF. This decision may be affected, for example, by the quality of service, QoS, of the LSR or by the geographical or topological location of the LCS client and the target UE. For fine-grained, high accuracy positioning the LSR is forwarded to the PCF, and the AMF may instruct the PCF to admit any upcoming LSRs from the external LCS client. The PCF may be located in a radio access network, RAN, to which the target UE is also connected. This may reduce signalling between the RAN and the CN during positioning determination. After the PCF has determined the location of the target UE, it sends a location service, LS, response back to the AMF, and the LS response comprises the identification, ID, of the PCF. The LS response is forwarded back to the external LCS client. Since the LS response comprises the ID of the PCF and the PCF has been instructed to admit any upcoming LSRs from the external LCS client, the external LCS client can transmit further LSRs directly addressed to the PCF, if it needs up-to-date information about the position of the target UE. Thus, unnecessary signalling and latency are reduced, because the LCS client can address any upcoming LSRs directly to the PCF.

[0043] According to another example, a UE can also request for its own location. In such a case, the UE transmits an LSR to the AMF, and the AMF makes a forwarding decision like with an external LCS client in the previous example. However, the AMF can also include an instruction into the LSR for the PCF to store information about the LSR, so that the PCF can recognize upcoming LSRs from the same UE, where the UE again requests for its own position. Furthermore, the LSR comprises the ID of the UE. Thus, after the PCF has determined the fine-grained location of the UE, the PCF sends an LS response addressed directly to the UE based on the ID. This reduces signalling and latency, because the response does not need to be forwarded through the AMF or any other nodes in the CN. Furthermore, since the PCF can recognize any upcoming FSRs from the UE, the PCF can stop the FSR from being forwarded to the CN, determine the new position of the UE, and send a new FS response directly to the UE. Thus, any FSRs or FS responses after the first FSR do no need to go through the CN, which further reduces signalling and latency. This example may also be applicable to cases where a UE requests for the location of a target UE, and both UEs are connected to the same RAN. It should be appreciated that the reduction of latency by any example herein may also increase the accuracy of the positioning information, because the positioning information is more up-to-date.

[0044] FIG. 1 illustrates a schematic representation of a wireless radio communication network according to an example. Parts relating to the example are presented in the FIG. 1. Furthermore, naming of the nodes in the network follows the naming scheme of 5G technology in its current form. However, it should be noted that this naming scheme may change over time. Additionally, most of the nodes presented in the figure have a corresponding node in other radio technologies, such as 4G. Thus, the following discussion regarding any example also applies to those technologies.

[0045] The radio network comprises, a user equipment, UE 101, UE 103, a radio access network, RAN, 110 a core network, CN, 120 and an external location services, ECS, client 102. UE 101, UE 103 or the LCS client 102 may also be referred to as a client device, a target device, or a target UE depending on their function in an LCS process. The RAN 110 further comprises three transmission and reception points, TRPs, 111 and a base station, gNB 113. It should be appreciated that the number of TRPs 111 is only an example that illustrates that the UEs 101, 103 can be connected to multiple TRPs 111 and that multiple TRPs 111 can be connected to a single gNB 113. Furthermore, each TRP 111 comprises a location measurement unit, LMU, 112. The gNB, in turn, comprises a positioning computation function, PCF, 114. The PCF 114 can also be positioned in other locations within the RAN 110. For example, some other node than the gNB 113 can comprise the PCF 114, the PCF 114 can be an independent node located, for example, between the gNB 113 and the CN 120, or even some node in the CN 120 close to the RAN 110 can comprise the PCF 114. Furthermore, the PCF 114 may be implemented as an independent device, or it may be implemented in the same device with some another node or nodes of the network. The PCF 114 or the device implementing the functionality of the PCF 114 may also be referred to as a network positioning device according to an example.

[0046] The CN 120 further comprises an access and mobility management function, AMF, 122 a location management function, LMF, 121 and an LCS entity 123. The AMF 122 may also be called a mobility management entity, MME. Furthermore, the AMF 122 or a device implementing the functionality of the AMF 122 may be refer to as a network management device according to an example. The LMF 121 may also be called an evolved serving mobile location server, E-SMLC, and the LMF 121 or the device implementing the functionality of the LMF 121 may be referred to as a core network positioning device. The LCS entity 123 may be, for example, a gateway mobile location entity, GMLC. The LMF 121 or the PCF 114 may also be referred to as a positioning node.

[0047] The UEs 101, 103 are connected to the three TRPs 111, which in turn are connected to the gNB 113. The gNB 113 connects all of devices and nodes connected to it to the CN 120. Any external devices, such as the external LCS client 102, are connected to the CN 120 through the LCS entity 123, which authorizes any external connections in the control layer of the CN 120. The external LCS client 102 may be, for example, another UE from another network. In such a case, the LCS client 102 may be connected to the CN 120 through its own CN and RAN. The external LCS client 102 may also be any other network node or device outside of the CN 120 and the RAN 110.

[0048] The location of a device connected to the network may be requested by a few parties. For example, a device, such as UE 101 or UE 103, may request for its own location or a device may request for the position of another device. In the latter case, there are also multiple possibilities. The two devices may be connected to the same RAN. For example, UE 103 may request for the location of UE 101. Alternatively, a device outside the network presented in the figure, such as LCS client 102, may request for the location of one of the UEs 101, 103.

[0049] FIG. 2 illustrates a schematic representation of a location service request process according to an example. The process is initiated by an external LCS client 102. This client may be, for example, an external user equipment, UE, requesting for the position of another client, in this case the target UE 101. The term external may refer to the fact that the LCS client 102 is not part of the same CN or RAN as the rest of the nodes depicted in the figure. The LCS client 102 transmits a location service request, LSR, 201 to the LCS entity 123, wherein the LSR 201 comprises a request to locate the target UE 101. Additionally, the LSR 201 may comprise requests for additional location information, such as the velocity or speed of the target UE 101. The target UE 101 may be, for example, a mobile phone, a cellular telephone, a computer tablet or a laptop with wireless capability. The LCS entity 123 authorizes the LCS client 102 and queries a home subscribed server, HSS, in order to find the address of the access and mobility management function, AML, 122. The LCS entity forwards the LSR 201 to the AML in operation 202.

[0050] After receiving the LSR 201, the AML 122 decides whether to forward the LSR 201 to the location management function, LML, 121 or to the positioning computation function, PCL, 114. The LML 121 is located in the CN 120, while the PCL 114 may be positioned in the RAN 110 or close to the RAN 110, for example, in a node of the CN 120 that is directly interfacing with the RAN 110. The forwarding decision 203 can be affected by multiple factors. Lor example, the LSR 201 may comprise quality of service, QoS, information that indicates how accurate positioning the LCS client 102 requires. In the case of coarse-grained positioning, the LSR 201 should be forwarded to the LML 121, while for fine-grained positioning the LSR should be forwarded to the PCL 114. Coarse-grained positioning may refer to positioning less accurate than some threshold distance and fine-grained accuracy may refer to positioning more accurate than some threshold distance. Lor example, coarse grained may refer to positioning less accurate than 10 metres, m, or it may refer to positioning less accurate than 1 m. Line-grained may refer to, for example, positioning more accurate than 10 m or more accurate than 1 m. Additionally, if the target UE 101 is in idle mode, the AML 122 can perform a network initiated service request procedure to establish a connection to the target UE 101. Lurthermore, the user of the target UE 101 may be informed that positioning has been requested, and the user may need to confirm that positioning is allowed. In the case of fine-grained positioning, the LSR 201 may include information for the PCL 114 to admit any upcoming LSRs that the LCS client 102 may transmit directly addressed to the PCL 114 after the first LSR 201. [0051 ] Alternatively or in addition to the QoS, the forwarding decision

203 can also be affected by the topological or geographical location of the LCS client 102 and the target UE 101. For example, if the target UE 101 and the LCS client 102 are located geographically close to each other, and the nodes of the CN 120 are not located close to either device, it may be beneficial to forward the LSR 201 to the PCF 114 instead of the LMF 121. The AMF 122 may use various methods to determine if the LCS client 102 and the target UE 101 are topologically or geographically close. For example, the LSR may comprise identifications, IDs, of the LCS client 102 and the target UE 101, and the AMF 122 may use these IDs to query any available information about the position of the LCS client 102 and the target UE 101.

[0052] After the LSR 201 is forwarded to the next node either in operation

204 or 204’, the node in question, LMF 121 or PCF 114, uses various procedures 210 in order to locate the target UE 101 with the accuracy indicated by the LSR 201. Overlap of the procedures 211, 212, 213 with the nodes in the figure indicates which nodes may take part in which procedures. The PCF 114 may, for example, obtain measurement information from multiple TRPs 111 and determine the location of the target UE 101 based on these measurements. These measurements may be, for example downlink and uplink measurements between the target UE 101 and the TRPs 111 based on the angle of arrival and the time of arrival of signals. Since the PCF 114 may be located in the RAN 110, the measurement information from the TRPs 111 may not need to be transferred to the CN 120 at any point during the TRP procedures 213. Thus, signalling and latency during the procedures may be reduced. This improvement may be especially significant in 5G applications, where typically tens or hundreds of TRPs 111 may be connected to a single gNB. Other procedures may be, for example, various uplink and downlink measurements, enhanced cell ID, E-CID, positioning, or WLAN, Bluetooth, and barometric measurements.

[0053] After the positioning node, PCF 114 or LMF 121, has determined the location of the target UE 101, the node transmits a location service response to the AMF 122 in operation 205 or 205’, wherein the response comprises the determined location of the target UE 101, some information about the accuracy of the location, and optionally some other location information, such as the velocity or speed of the target UE 101. Additionally, in the operation 205, the location service response may include the ID of the PCF 114. [0054] The location of the target UE 101 in the LS response 205, 205’ and any other location related information can be expressed in various formats. For example, a geographic coordinate system, such as the World Geodetic System, or a local coordinate system can be used. In the latter case, the origin of a local coordinate system can be, for example, a gNB or a corner of a building. Furthermore, in addition to a Cartesian coordinate system, the location of the target UE 101 may be expressed, for example, using the distance and angle from an antenna, a scalar value that represents a position in a cell, or some combination of these. Additionally, the FS response may comprise the ID and location of the antenna and beam-related information. The use of a local coordinate system may be especially beneficial in fine-grained positioning and when the global location of the target UE is not of interest. Furthermore, different measurement units, such as metres or centimetres, can be used for the location depending, for example, on the requested accuracy.

[0055] After receiving the FS response 205, 205’, the AMF forwards the response to the FCS entity 123 in operation 206 or 206’, and the FCS entity 123, in turn, forwards the response to the FCS client 102. In the case of fine-grained positioning performed by the PCF 114, the FCS client 102 transmits an acknowledgement message 207, which is forwarded through the FCS entity 123 and the AMF 122 to the PCF 114. Furthermore, since the FS response 205 comprised the ID of the PCF 114, the FCS client 102 can address the next FSR 208, and any upcoming FSRs after this, directly to the PCF 114 using the ID, if the FCS client 102 requires new up-to-date location information about the target UE 101. Furthermore, since the AMF 122 instructed the PCF 114 to admit any upcoming FSRs from the FCS client 102, any upcoming FSRs do not need to be authorized by the FCS entity 123.

[0056] FIG. 3 illustrates a schematic representation of location service request process when a UE 103 requests for the location of a target UE 102 according to an example, and the UEs are connected to the same radio access network. The process is initiated by the UE 103 as it transmits an FSR 301. Since the UE 103 requests for the location of a target UE 101, the request should first be authorized by the FCS entity 123, which forwards the request to the AMF 122. Fike with the previous example, the AMF 122 makes a forwarding decision 203 based on the FSR. This decision can be affected by the QoS of the FSR and by the geographical or topological location of the UE 103 and the target UE 101. A fine-grained FSR may be forwarded to the PCF 114, and coarse- grained LSR may be forwarded to the LMF 121. However, now the fine-grained LSR may comprise information for the PCF 114 that enables the PCF 114 to send the LS response directly to the UE 103. This information may be, for example the ID of the UE 103. This may be beneficial because the target UE 101 and UE 103 are connected to the same RAN 110 which comprises the PCF 114. This way, in the operation 302, the LS response does not need to be forwarded back to the AMF 122, which is located in the CN 120, and then forwarded again to the UE 103 through the RAN 110. This can reduce signalling and latency, because unnecessary message forwards are circumvented and signalling between the RAN 110 and the CN 120 is reduced.

[0057] After the positioning node, LMF 121 or PCF 114, has determined the location of the target UE 101, it transmits an LS response. In the case of LMF 121 and coarse-grained positioning, the LS response is transmitted to the AMF 122 in operation 205’, and the AMF 122 forwards the LS response back to the UE 103 in operation 302’ . This is basically the same method as in the previous example when a LSR was initiated by an external LCS client 102, but now the LS response does not need to go through the LCS entity 123, because the UE 103 is connected to the RAN 110 that is connected to the CN 120. In the case of fine-grained positioning, the PCF 114 directly transmits the LS response to the UE 103 in operation 302 using the information in the LSR 301 as described above. Additionally the PCF 114 may transmit acknowledgement messages to the AMF 122 and to the LCS entity 123. After receiving the LS response 302, the UE 103 sends an acknowledgement message 303 to the PCF 114.

[0058] FIG. 4 illustrates a schematic representation of a location service request process when a UE 101 requests for its own location according to an example. In this example, the LCS client and the target UE are the same device. Furthermore, this can be considered to be an example of the example presented in FIG. 3. The process is initiated by the UE 101 as it transmits an LSR 301 to the AMF 122. The UE 101 is connected to the RAN 110 that is connected to the CN 120 which comprises the AMF 122 and the UE 101 requests for its own location. Therefore, the LSR does not need to go through or be authorised by the LCS entity 123 like occurred with an external LSR client and with an UE requesting the position of another UE within the same RAN. Like with the previous examples, the AMF 122 makes a forwarding decision 203 based on the LSR 301. A fine-grained LSR is forwarded to the PCF 114, and a coarse-grained LSR is forwarded to the LMF 121. Again, the fine-grained LSR comprises information for the PCF 114 to send the LS response directly to the UE 101. This information may be, for example the ID of the UE 101. This may be beneficial because the location was requested by the UE 101 and the UE 101 is connected to the same RAN 110 as which comprises the PCF 114. This way, at the operation 302, the LS response does not need to be forwarded back to the AMF 122, which is located in the CN 120, and then forwarded again to the UE 101. This can reduce signalling and latency, because unnecessary message forwards are circumvented.

[0059] After the positioning node, LMF 121 or PCF 114, has determined the UE location, the node sends an LS response. In the case of LMF 121 and coarse grained positioning, the LS response is transmitted to the AMF 122 in operation 205’, which forwards the LS response back to the UE in operation 302’. This is basically the same operation as in the previous example when the position was requested by an external LCS client 102, but now the LS response does not need to go through the LCS entity 123, because the UE 101 is connected to the RAN 110 that is connected to the CN 120. In the case of fine-grained positioning, the PCF 114 directly addresses and transmits the LS response to the UE 101 in operation 302 using the information in the LSR 301 as described above. In this case, the UE 101 sends an acknowledgement message 303 to the PCF 114 after receiving the LS response 302.

[0060] FIG. 5 illustrates a schematic representation of a location service request process when a UE 101 requests for its own position according to another example. In this example, the coarse-grained positioning process is similar to that presented in FIG. 4. However, in the case of the fine-grained positioning, when the AMF 122 forwards the LSR 301 to the PCF 114 in operation 204, the AMF 122 includes an instruction into the LSR 301 for the PCF 114 to store information about the LSR 301. This information should be such that the PCF 114 can identify any upcoming LSRs from the UE 101, where the UE 101 requests for its own location. This information may be, for example, the ID of the UE 101 and an indication that the UE 101 requested for its own location. Alternatively or in addition to this, other relevant information about the LSR 301 may be stored. This information may also be referred to as the context of the LSR 301. It should be appreciated that the PCF 114 may store information about multiple LSRs from different LCS clients to, for example, a table data structure. The PCF 114 may then recognize an upcoming LSR my comparing it to the entries in the table. Rest of the operations concerning the LSR 301 and the corresponding LS response may be similar to the previous example.

[0061 ] If the UE 101 transmits another LSR 501 after the first LSR 301, since the PCL 114 has stored the information about the previous LSR 301, the PCL 114 can recognize that the UE 101 has previously requested for its own location by comparing LSR 501 to the information stored about LSR 301. Thus, the PCL 114 can directly address and send an LS response to the UE 101 in operation 502, and the UE 101 can respond by sending an acknowledgement 503 to the PCL 114. This way, any subsequent LSRs from the UE 101, where the UE 101 requests for its own position, do not need to be forwarded to the AML 122 or to the CN 120. This reduces signalling and latency even further.

[0062] The PCL 114 may also automatically transmit new LS responses to the UE 101 updating the location of the UE 101. These automatically triggered LS responses can be sent, for example, periodically or the PCL 114 can actively monitor the position of the UE 101 and send an LS response every time the location of the UE 101 changes more than some set threshold distance. Other quantities, such as speed, may also be used for the threshold. Whether this type of automatic triggering is needed, can be indicated in the original LSR 301. These automatic LS responses may reduce latency and signalling, because the UE 101 can receive multiple LS responses over some time period by transmitting only a single LSR.

[0063] Alternatively, the UE 301 may also transmit the second LSR 501 directly to the PCL 114, if the LS response 302 comprises the ID of the PCL 114. This would be a similar operation to that used in the example of LIG. 2. This method can also be combined with the method presented in LIG. 5. Lor example, the following LSR 501 may comprise a duration of event reporting attribute. If the UE 101 sends additional LSRs for updated location information after the duration of event reporting has expired, the LSR should be transmitted to the AML 122 instead of transmitting it directly to the PCL 114 using the ID. In such a situation, the PCL 114 may use the method of LIG. 5 to provide location information with low latency even when the LSR is transmitted to the AML 122.

[0064] It should be appreciated that the operations 501, 502, 503 presented in the example of LIG. 5 and the command from the AML 122 to the PCL 114 to store information about the first LSR may also be applied when a UE 103 requests for the location of another UE 101, and the UEs are connected to the same RAN. An example of this is presented in FIG. 6.

[0065] FIG. 7 illustrates a schematic representation of two consecutive

LSRs, when a UE 101 requests for its own location according to an example. This may be an example of selected operations presented in FIG. 5. The UE 101 first transmits the LSR 301 to the AMF 122. The AMF 122 forwards the request to the PCF 114 in operation 204, and instructs the PCF to store information 601 about the FSR 301. This information should be such that the PCF 114 can recognize any upcoming FSRs from the UE 101, where the UE 101 requests for its own location. For example, the PCF 114 can store into a table the ID of the UE 101 and an indication that the UE 101 requested for its own location. Naturally, the PCF 114 also uses the positioning procedures 210 to determine the location of the UE 101 and sends the location back to the UE 101 in an FS response 302.

[0066] After receiving the FS response 302, the UE 101 transmits another

FSR 501, where the UE 101 requests for an update to its own location. There may be some period of time between the UE 101 receiving the FS response 302 and transmitting the FSR 501. Since the PCF 114 is located in the RAN 110, for example in the gNB 113, the FSR 501 goes through the PCF 114. Thus, the PCF 114 can compare the FSR 501 to the information 601 that it has stored and identify that the same UE 101 has previously requested for its own location. The PCF 114 can therefore stop the FSR 501 from being forwarded further, fulfil the FSR 501 using the positioning procedures 210, and send an FS response 502, comprising the new location of the UE 101, directly back to the UE 101. This way, the FSR 501, or any subsequent FSR, does not need to leave the RAN 110. Thus unnecessary signalling between the RAN 110 and the CN 120 is circumvented, which may reduce the latency between when the UE 101 sends an FSR and when it receives an FS response. Therefore, the UE 101 may obtain more up-to-date location information.

[0067] FIGs 8, 9, and 10 illustrate schematic representations of a network positioning device 114, a network management device 122, and a client device 102, respectively, according to an example. Each of the devices 114, 122, 102 comprise a processor 701, 801, 901 and a network interface 702, 802, 902, wherein the processor 701, 801, 901 manages and implements the functionality of the device 114, 122, 102 and the network interface 702, 802, 902 may be used to interact with other devices within a network. The devices 114, 122, 102 can be configured to implement the functionality of one or more of the nodes presented herein. For example, the network positioning device 114 can be configured to function as a positioning computation function, PCF, the network management device 122 can be configured to function as an access and mobility management function, AMF, and the client device 102 can be configured to function as an LCS client. Alternatively or in addition to this, a single device 114, 122, 102 can be configured to implement the functionality of multiple nodes or functions. For example, within the core network, CN, 120, an AMF 122 and a location management function, LMF, 121 may be implemented with a single device.

[0068] The functionality described herein can be performed, at least in part, by one or more computer program product components such as software components. Alternatively, or in addition, the functionality described herein can be performed, at least in part, by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include Field-programmable Gate Arrays (FPGAs), Program- specific Integrated Circuits (ASICs), Program- specific Standard Products (ASSPs), System-on-a-chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), Graphics Processing Units (GPUs).

[0069] Any range or device value given herein may be extended or altered without losing the effect sought. Also any example may be combined with another example unless explicitly disallowed.

[0070] Although the subject matter has been described in language specific to structural features and/or acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as examples of implementing the claims and other equivalent features and acts are intended to be within the scope of the claims.

[0071 ] It will be understood that the benefits and advantages described above may relate to one example or may relate to several examples. The examples are not limited to those that solve any or all of the stated problems or those that have any or all of the stated benefits and advantages. It will further be understood that reference to 'an' item may refer to one or more of those items. The term‘and/or’ may be used to indicate that one or more of the cases it connects may occur. Both, or more, connected cases may occur, or only either one of the connected cases may occur.

[0072] The operations of the methods described herein may be carried out in any suitable order, or simultaneously where appropriate. Additionally, individual blocks may be deleted from any of the methods without departing from the spirit and scope of the subject matter described herein. Aspects of any of the examples described above may be combined with aspects of any of the other examples described to form further examples without losing the effect sought.

[007B] The term 'comprising' is used herein to mean including the method, blocks or elements identified, but that such blocks or elements do not comprise an exclusive list and a method or apparatus may contain additional blocks or elements.

[0074] It will be understood that the above description is given by way of example only and that various modifications may be made by those skilled in the art. The above specification, examples and data provide a complete description of the structure and use of exemplary examples. Although various examples have been described above with a certain degree of particularity, or with reference to one or more individual examples, those skilled in the art could make numerous alterations to the disclosed examples without departing from the spirit or scope of this specification.