TECHNICAL FIELD

Embodiments presented herein relate to location determination of a wireless device, and particularly to methods, a wireless device, a Location Retrieval Function / Location Server entity, an evolved Packet Data Gateway entity, computer programs, and a computer program product for location

determination of a wireless device served by a non-3GPP radio access network.

BACKGROUND

In communications networks, there may be a challenge to obtain good performance and capacity for a given communications protocol, its

parameters and the physical environment in which the communications network is deployed.

For example, during events such as an Emergency Call (EC) it can be required that the emergency call operator can retrieve the location of the caller to enable dispatch of emergency responders to the location of the caller. The location of the caller is defined by the location of the device (e.g. such as a wireless device e.g. in the form of a user equipment; UE) used by the caller to make the EC and hence the location of the caller can be determined by finding the location of the device. Note that the device may be handheld or fitted or otherwise arranged in a computer or a tablet or similar or even in a vehicle or similar. Here it may be that the computer, tablet or vehicle or similar initiates the EC. For ECs being handled over cellular radio access networks such positioning is supported by the cellular radio access network itself.

However, when the device used to make the EC uses wireless local area network (WLAN) access and does not have any cell coverage, then the cellular radio access network cannot be used to locate the device. In this respect, so- called Wi-Fi access is defined as any WLAN access that is based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards. Four other mechanisms that instead can be used will be summarized next.

A first example is location information included in a SIP INVITE message, where SIP is short for Session Initiation Protocol, and where SIP INVITE is a type of message defined according to SIP. This location information can be precise (e.g., given by Global Positioning System (GPS) coordinates) but is only provided at the time of initiation of the call.

As a second example, if the device is operatively connected to the network via a managed Wi-Fi network, then based on what Wi-Fi Access Point (AP) the device attaches to, the network can provide location information that has been configured for the AP.

As a third example, if the device is operatively connected to the network via an unmanaged Wi-Fi network (e.g., a local Wi-Fi network in a residential area), the used Internet Protocol (IP) address of the device can be tracked in order to determine the location of the device.

As a fourth example, the device can be queried for its current location using the Secure User Plane (SUPL) mechanism where the network sends a SIP request to the device which triggers the device to set up a Transport Layer Security (TLS) connection to the network over which the device provides its current location.

Some issues with the above listed solutions have been identified and will be summarized next.

In the first example, if the device is moving, the current position of the device will not be identical to the initial location of the device as given at the time of initiation of the call. This could happen if the Wi-Fi AP itself is moving (e.g., provided in a train or a bus).

The second example is only valid for a subset of all Wi-Fi networks and is neither valid for residential Wi-Fi networks nor mobile Wi-Fi networks. In the third example, if a Virtual Private Network (VPN) service is used, then the point of presence for the IP address might be completely different than the position of the device. Also, even without using VPN services, the precision of tracking IP addresses might not be good enough for some services (for example if the device makes an EC and the operator needs to track the device).

In the fourth example, even though this mechanism is already standardized there is currently limited support in commercial device. Further, this mechanism requires a complex configuration in the device with additional TLS certificates and requires a separate TLS/TCP (Transmission Control Protocol) connection to a Location Retrieval Function / Location Server (LRF/LS). Further, the use of SUPL for location retrieval risks to interfere with existing SUPL functionality towards device vendor specific Location Servers. Additionally, the mechanism is not supported for SIM-less (where SIM is short for Subscriber Identity Module) devices, so called secondary devices, for example tablets and laptop computers.

Hence, there is still a need for an improved location determination of a wireless device.

SUMMARY

An object of embodiments herein is to provide efficient location

determination of a wireless device.

According to a first aspect there is presented a method for location

determination of a wireless device served by a non-3GPP radio access network, e.g. a WLAN radio access or a LTE unlicensed access. The method is performed by the wireless device. The method comprises receiving a location request for the location of the wireless device sent by a Location Retrieval Function and/or Location Server (LRF/LS), entity during an ongoing communications session on an already established connection The method comprises obtaining location information defining the location of the wireless device. The method comprises providing the location information defining the location of the wireless device to the LRF/LS entity on the already established connection.

According to a second aspect there is presented a wireless device for location determination of the wireless device served by a non-3GPP radio access network, e.g. a WLAN radio access or a LTE unlicensed access. The wireless device comprises processing circuitry. The processing circuitry is configured to cause the wireless device to receive a location request for the location of the wireless device sent by a Location Retrieval Function and/or Location Server (LRF/LS) entity during an ongoing communications session on an already established connection. The processing circuitry is configured to cause the wireless device to obtain location information defining the location of the wireless device. The processing circuitry is configured to cause the wireless device to provide the location information defining the location of the wireless device to the LRF/LS entity on the already established

connection.

According to a third aspect there is presented a wireless device for location determination of the wireless device served by a non-3GPP radio access network, e.g. a WLAN radio access or a LTE unlicensed access. The wireless device comprises processing circuitry and a computer program product. The computer program product stores instructions that, when executed by the processing circuitry, causes the wireless device to perform a method according to the first aspect.

According to a fourth aspect there is presented a wireless device for location determination of the wireless device served by a non-3GPP radio access network, e.g. a WLAN radio access or a LTE unlicensed access. The wireless device comprises a receive module configured to receive a location request for the location of the wireless device sent by a Location Retrieval Function and/or Location Server (LRF/LS) entity during an ongoing communications session on an already established connection. The wireless device comprises an obtain module configured to obtain location information defining the location of the wireless device. The wireless device comprises a first provide module configured to provide the location information defining the location of the wireless device to the LRF/LS entity on the already established connection.

According to a fifth aspect there is presented a computer program for location determination of a wireless device served by a non-3GPP radio access network, e.g. a WLAN radio access or a LTE unlicensed access, the computer program comprising computer program code which, when run on processing circuitry of the wireless device, causes the wireless device to perform a method according to the first aspect. According to a sixth aspect there is presented a method for location determination of a wireless device served by a non-3GPP radio access network, e.g. a WLAN radio access or a LTE unlicensed access. The method is performed by a Location Retrieval Function and/or Location Server

(LRF/LS) entity. The method comprises receiving a location request for the location of the wireless device sent by a Public-Safety Answering Point

(PSAP) entity. The method comprises providing the location request for the location of the wireless device to the wireless device during an ongoing communications session with the wireless device on an already established connection. The method comprises receiving location information defining the location of the wireless device, which location information is sent by the wireless device on the already established connection. The method comprises providing the location information to the PSAP entity.

According to a seventh aspect there is presented a Location Retrieval

Function and/or Location Server (LRF/LS) entity for location determination of a wireless device served by a non-3GPP radio access network, e.g. a WLAN radio access or a LTE unlicensed access. The LRF/LS entity comprises processing circuitry. The processing circuitry is configured to cause the LRF/LS entity to receive a location request for the location of the wireless device sent by a PSAP entity. The processing circuitry is configured to cause the LRF/LS entity to provide the location request for the location of the wireless device to the wireless device during an ongoing communications session with the wireless device on an already established connection. The processing circuitry is configured to cause the LRF/LS entity to receive location information defining the location of the wireless device, which location information is sent by the wireless device on the already established connection. The processing circuitry is configured to cause the LRF/LS entity to provide the location information to the PSAP entity.

According to an eighth aspect there is presented a Location Retrieval Function and/or Location Server (LRF/LS) entity for location determination of a wireless device served by a non-3GPP radio access network, e.g. a WLAN radio access or a LTE unlicensed access. The LRF/LS entity comprises processing circuitry and a computer program product. The computer program product stores instructions that, when executed by the processing circuitry, causes the LRF/LS entity to perform a method according to the sixth aspect. According to a ninth aspect there is presented a Location Retrieval Function and/or Location Server (LRF/LS) entity for location determination of a wireless device served by a non-3GPP radio access network, e.g. a WLAN radio access or a LTE unlicensed access. The LRF/LS entity comprises a first receive module configured to receive a location request for the location of the wireless device sent by a PSAP entity. The LRF/LS entity comprises a first provide module configured to provide the location request for the location of the wireless device to the wireless device during an ongoing communications session with the wireless device on an already established connection. The LRF/LS entity comprises a second receive module configured to receive location information defining the location of the wireless device, which location information is sent by the wireless device on the already established connection. The LRF/LS entity comprises a second provide module configured to provide the location information to the PSAP entity.

According to a tenth aspect there is presented a computer program for location determination of a wireless device served by a non-3GPP radio access network, e.g. a WLAN radio access or a LTE unlicensed access, the computer program comprising computer program code which, when run on processing circuitry of an LRF/LS entity, causes the LRF/LS to perform a method according to the sixth aspect.

According to an eleventh aspect there is presented a method for location determination of a wireless device served by a non-3GPP radio access network, e.g. a WLAN radio access or a LTE unlicensed access. The method is performed by an evolved Packet Data Gateway (ePDG) entity. The method comprises receiving a location request for the location of the wireless device sent by a Location Retrieval Function and/or Location Server (LRF/LS) entity during an ongoing communications session with the wireless device on an already established connection. The method comprises providing the location request for the location of the wireless device to the wireless device on the already established connection. The method comprises receiving location information defining the location of the wireless device, which location information is sent by the wireless device on the already established connection. The method comprises providing the location information defining the location of the wireless device to the LRF/LS entity on the already established connection.

According to a twelfth aspect there is presented an ePDG, entity for location determination of a wireless device served by a non-3GPP radio access network, e.g. a WLAN radio access or a LTE unlicensed access. The ePDG entity comprises processing circuitry. The processing circuitry is configured to cause the ePDG entity to receive a location request for the location of the wireless device sent by a Location Retrieval Function and/or Location Server (LRF/LS) entity during an ongoing communications session with the wireless device on an already established connection. The processing circuitry is configured to cause the ePDG entity to provide the location request for the location of the wireless device to the wireless device on the already

established connection. The processing circuitry is configured to cause the ePDG entity to receive location information defining the location of the wireless device, which location information is sent by the wireless device on the already established connection. The processing circuitry is configured to cause the ePDG entity to provide the location information defining the location of the wireless device to the LRF/LS entity on the already established connection.

According to a thirteenth aspect there is presented an ePDG entity for location determination of a wireless device served by a non-3GPP radio access network, e.g. a WLAN radio access or a LTE unlicensed access. The ePDG entity comprises processing circuitry and a computer program product. The computer program product stores instructions that, when executed by the processing circuitry, causes the ePDG entity to perform a method according to the eleventh aspect

According to a fourteenth aspect there is presented an ePDG entity for location determination of a wireless device served by a non-3GPP radio access network, e.g. a WLAN radio access or a LTE unlicensed access. The ePDG entity comprises a first receive module configured to receive a location request for the location of the wireless device sent by a Location Retrieval Function and/or Location Server (LRF/LS) entity during an ongoing communications session with the wireless device on an already established connection. The ePDG entity comprises a first provide module configured to provide the location request for the location of the wireless device to the wireless device on the already established connection. The ePDG entity comprises a second receive module configured to receive location

information defining the location of the wireless device, which location information is sent by the wireless device on the already established connection. The ePDG entity comprises a second provide module configured to cause the ePDG entity to provide the location information defining the location of the wireless device to the LRF/LS entity on the already established connection.

According to a fifteenth aspect there is presented a computer program for location determination of a wireless device served by a non-3GPP radio access network, e.g. a WLAN radio access or a LTE unlicensed access, the computer program comprising computer program code which, when run on processing circuitry of an ePDG entity, causes the ePDG entity to perform a method according to the eleventh aspect.

According to a sixteenth aspect there is presented a computer program product comprising a computer program according to at least one of the fifth aspect, the tenth aspect, and the fifteenth aspect, and a computer readable storage medium on which the computer program is stored. The computer readable storage medium can be a non-transitory computer readable storage medium.

Advantageously these methods, these wireless devices, these LRF/LS entities, these ePDG entities, and these computer programs provide efficient location determination of the wireless device.

Location of the wireless device can be required also for non-emergency calls for various services, charging, and policy control. Advantageously, the methods are applicable also in cases when the wireless device receives an incoming call and the network wants to verify the location of the wireless device before starting ringing at the wireless device.

Advantageously the location of the wireless device can be determined at the moment it is requested by a PSAP operator and there is no risk that decisions are based on old location information if the wireless device is moving. The PSAP operator may need to send multiple queries to the wireless device if the wireless device is continuously moving during the EC.

Advantageously the methods can be used for all kinds of Wi-Fi access networks, such as managed and unmanaged Wi-Fi networks.

Advantageously, even if the wireless device is operatively connected via VPN to the network, the wireless device can determine where it is located and can thus provide the correct location information to the network. There is, for example, thus no risk the location of the termination point of the VPN tunnel is given to the PSAP operator. Advantageously, as the methods leverage on protocols already supported by wireless devices, there is no need for additional specific configurations in the wireless devices and no protocols to be supported and new connections to be established. For example, both Internet Key Exchange (IKE) and Session Initiation Protocol (SIP) connections are established between the wireless device and the network when the EC is set up and according to embodiments disclosed herein, such connections can be re-used to convey the location information as needed during the EC. There is hence no need for the wireless device to establish an additional TLS connection. Advantageously, the methods are applicable for both SIM devices as well as SIM -less devices.

It is to be noted that any feature of the first, second, third, fourth, fifth, sixth seventh, eight, ninth, tenth, eleventh, twelfth, thirteenth, fifteenth and sixteenth aspects may be applied to any other aspect, wherever appropriate. Likewise, any advantage of the first aspect may equally apply to the second, third, fourth, fifth, sixth, seventh, eight, ninth, tenth, eleventh, twelfth, thirteenth, fifteenth, and/or sixteenth aspect, respectively, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following detailed disclosure, from the attached dependent claims as well as from the drawings.

Generally, all terms used in the claims are to be interpreted according to their ordinary meaning in the technical field, unless explicitly defined otherwise herein. All references to "a/an/the element, apparatus, component, means, step, etc." are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless explicitly stated.

BRIEF DESCRIPTION OF THE DRAWINGS

The inventive concept is now described, by way of example, with reference to the accompanying drawings, in which: Fig. l is a schematic diagram illustrating a communication network according to embodiments;

Fig. 2 is a signalling diagram according to state of the art;

Figs. 3, 4, and 5 are flowcharts of methods according to embodiments; Figs. 6 and 7 are signalling diagrams according to embodiments;

Fig. 8a is a schematic diagram showing functional units of a wireless device according to an embodiment;

Fig. 8b is a schematic diagram showing functional modules of a wireless device according to an embodiment; Fig. 9a is a schematic diagram showing functional units of a LRF/LS entity according to an embodiment;

Fig. 9b is a schematic diagram showing functional modules of a LRF/LS entity according to an embodiment;

Fig. 10a is a schematic diagram showing functional units of a ePDG entity according to an embodiment;

Fig. 10b is a schematic diagram showing functional modules of a ePDG entity according to an embodiment; and

Fig. 11 shows one example of a computer program product comprising computer readable means according to an embodiment. DETAILED DESCRIPTION

The inventive concept will now be described more fully hereinafter with reference to the accompanying drawings, in which certain embodiments of the inventive concept are shown. This inventive concept may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided by way of example so that this disclosure will be thorough and complete, and will fully convey the scope of the inventive concept to those skilled in the art. Like numbers refer to like elements throughout the description. Any step or feature illustrated by dashed lines should be regarded as optional.

Fig. l is a schematic diagram illustrating a communications network 100 where embodiments presented herein can be applied. The communications network 100 comprises a radio access network 120, a core network 130, and a service network 140.

The radio access network 120 comprises at least one radio access network node 110. The radio access network node could be a radio base station, a base transceiver station, a node B, an Evolved node B, or an Access Point (AP), e.g. a Wi-Fi AP in case the radio access network 120 is a Wi-Fi radio access network. As disclosed above, so-called Wi-Fi access is defined as any WLAN access that is based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards. The radio access network 120 is operatively connected to the core network 130 which in turn is operatively connected to the service network 140. The radio access network 120 thereby provides network access to at least one wireless device 150. The wireless device 150 could be a portable wireless device, a mobile station, a mobile phone, a handset, a wireless local loop phone, a user equipment (UE), a smartphone, a laptop computer, or a tablet computer. Note that the wireless device 150 may be handheld or fitted or otherwise arranged in a stationary computer, a laptop computer or a tablet computer or similar or even in a vehicle or similar.

The core network 130 comprises a Location Retrieval Function and/or Location Server (LRF/LS) entity 160 (the LRF may e.g. comprise the LS, or be implemented in or hosted by the LS and the terms may be used together as LRF/LS or separately as LRF or LS to indicate the same function), an evolved Packet Data Gateway (ePDG) entity 170, and an Emergency Call Session Control Function (E-CSCF) entity 180. The core network 130 may further comprise other entities and devices, such as an Authentication, Authorization, and Accounting (AAA) server entity, a Mobility Management Entity (MME) entity, and a Home Subscriber Server (HSS) entity.

The service network 140 comprises a Public-Safety Answering Point (PSAP) entity 190. On example of a service network 140 is the Internet. As noted above, the wireless device 150 can be queried for its current location using the SUPL mechanism where the network 100 sends a SIP request to the wireless device 150 which triggers the wireless device 150 to set up a TLS connection to the network 100 over which the wireless device 150 provides its current location. The SUPL mechanism will now be disclosed with reference to the signalling diagram of Fig. 2.

S400: A communications session between the wireless device 150 and the PSAP entity 190 is ongoing over Wi-Fi access.

A Location Retrieval Function and/or Location server (LRF/LS) entity 160 uses the Mobile Station International Subscriber Directory Number

(MSISDN) of the wireless device 150 to send an initial message via PPG or to send an initial message over the User Datagram Protocol (UDP) using the IP address from INVITE and hence causes steps S401 and S402 or step S403 to be performed:

S401: The LRF/LS entity 160 transmits the MSISDN to the PPG in a SUPL INIT message.

S402: The PPG transmits the SUPL INIT message comprising the MSISDN to the wireless device 150 in a SIP PUSH message.

S403: The LRF/LS entity 160 transmits the SUPL INIT message to the IP address of the INVITE in an UDP message. The wireless device 150 establishes a SUPL session over a wireless local area network (WLAN) and performs steps S404 and S405: S404: The wireless device 150 establishes a TLS connection to the LRF/LS entity 160.

S405: The wireless device 150 and the LRF/LS entity 160 exchanges SUPL messages where the location information of the wireless device 150 is provided to the LRF/LS entity 160 as User Equipment Provided Location Information (UPLI). The LRF/LS entity 160 thereby receives the location information of the wireless device 150

As also noted above, the mechanism illustrated in Fig. 2 requires a new connection to be established between the wireless device 150 and the LRF/LS entity 160. Particularly, a TLS connection is established in above step S404. Thus, the mechanism illustrated in Fig. 2 does not use any possible ongoing communications session (e.g. an EC) for retrieving the location of the wireless device 150.

The embodiments disclosed herein relate to mechanisms for location determination of a wireless device 150 served by a non-3GPP radio access network 100, e.g., a WLAN access or a Long Term Evolution (LTE) network operating in an unlicensed frequency band (so-called LTE unlicensed access). Particularly, the embodiments disclosed herein relate to efficient location determination of the wireless device 150 without having to establish a new connection.

In order to obtain such mechanisms there is provided a wireless device 150, a method performed by the wireless device 150, a computer program product comprising code, for example in the form of a computer program, that when run on processing circuitry of the wireless device 150, causes the wireless device 150 to perform the method. In order to obtain such mechanisms there is further provided a LRF/LS entity 160, a method performed by the LRF/LS entity 160, and a computer program product comprising code, for example in the form of a computer program, that when run on processing circuitry of the LRF/LS entity 160, causes the LRF/LS entity 160 to perform the method. In order to obtain such mechanisms there is further provided a ePDG entity 170, a method performed by the ePDG entity 170, and a computer program product comprising code, for example in the form of a computer program, that when run on processing circuitry of the ePDG entity 170, causes the ePDG entity 170 to perform the method. In general terms, at least some of the embodiments disclosed herein are based on the wireless device 150 is located by a query from the network 100 to the wireless device 150. The querying mechanisms re-uses a protocol that the wireless device 150 anyway is using during an ongoing communications session and enables the wireless device 150 to be located although it has moved after the communications session has been set up.

Fig. 3 is a flow chart illustrating embodiments of methods for insert purpose as performed by the wireless device 150. Fig. 4 is a flow chart illustrating embodiments of methods for insert purpose as performed by the LRF/LS entity 160. Fig. 5 is a flow chart illustrating embodiments of methods for insert 3 purpose as performed by the ePDG entity 170.

Reference is now made to Fig. 3 illustrating a method for location

determination of a wireless device 150 served by a non-3GPP radio access network 120 as performed by the wireless device 150 according to an embodiment. In this respect the radio access network 120 is therefore assumed to be a non- 3GPP radio access network (i.e., not a GSM EDGE Radio Access Network (GERAN), Universal Terrestrial Radio Access Network (UTRAN), or an Evolved Universal Terrestrial Radio Access Network (E-UTRAN), where GSM is short for Global System for Mobile Communications and where EDGE is short for Enhanced Data rates for GSM Evolution). Examples of such non- 3GPP radio access networks 120 are WLANs such as unmanaged Wi-Fi networks, managed Wi-Fi networks, or even LTE -unlicensed networks which thus provide WLAN radio access or LTE unlicensed access. In this respect, managed Wi-Fi implies that the network operator has control, directly or via partners, of the radio access all the way from the core network 130 to (and including) the Wi-Fi access point in the radio access network 120.

Unmanaged Wi-Fi typically provides radio access where the network operator control ends at the ePDG entity 170, i.e. where the transport between the ePDG entity 170 to the Wi-Fi access point in the radio access network 120 is not under the control of the network operator.

It is assumed that the location of the wireless device 150 is requested by the network 100. The wireless device 150 is therefore configured to perform steps S104-S108:

S104: The wireless device 150 receives a location request for the location of the wireless device 150. The location request is sent by a LRF/LS entity 160 during an ongoing communications session on an already established connection. Examples of how the location request can be received will be disclosed below. Examples of ongoing communications sessions will be disclosed below. Examples of established connections will be disclosed below. S106: The wireless device 150 obtains location information defining the location of the wireless device 150. Examples of location information will be disclosed below.

S108: The wireless device 150 provides the location information defining the location of the wireless device 150 to the LRF/LS entity 160 on the already established connection.

This method enables the network 100 to query the wireless device 150 of its location without setting up a dedicated communications session for this querying. This method further enables the network 100 to query the wireless device 150 on any kind of Wi-Fi access or other non-3GPP radio access for the location of the wireless device 150. The query is realized by extending the usage of at least one existing protocol (such as IKE or SIP) already supported by the wireless device 150. Embodiments relating to further details of location determination of a wireless device 150 served by a non-3GPP radio access network 120 as performed by the wireless device 150 will now be disclosed.

In terms of ongoing communications sessions, the location of the wireless device 150 can be requested anytime the communications session is ongoing on the already established connection; the request is thus not performed in connection with the establishment (i.e., setup) of the connection. That is, even if the wireless device 150 has moved in a geographical sense since the setup of the thus established connection, the movement is not assumed to cause termination of the established connection. Hence, the term ongoing communications session is to be interpreted as a communications session that already has been set up prior to step S104 being executed and is still ongoing when step S104 is executed.

There can be different examples of ongoing communications sessions.

According to an embodiment the ongoing communications session is an ongoing emergency call.

The ongoing emergency call can be handled, or managed, by the PSAP entity 190. According to an embodiment the wireless device 150 is therefore configured to perform step S102: S102: The wireless device 150 provides a device identifier of the wireless device 150 to the PSAP entity 190, preferably during setup of the emergency call. However, the device identifier of the wireless device 150 may be provided after the setup of the emergency call, but preferably before the wireless device 150 is queried in step S104. An example of how such a device identifier can be utilized during the location determination of the wireless device 150 will be explained in the second particular embodiment disclosed below with reference to Fig. 7.

Step S102 is performed prior to step S104. l8

In terms of step S104 according to which the wireless device 150 receives a location request sent by a LRF/LS entity 160, the location request can be sent by the LRF/LS entity 160 via one or more other entities/functions/nodes before it arrives at the wireless device 150. For example, the request can be sent by the LRF/LS entity 160 to a MME or a serving gateway (SGW) of the core network 130 (the MME and the SGW are not shown in the figures), which MME or SGW in turn forwards the request to radio access network node 110, which then forwards the request to the wireless device 150.

Further, it is foreseen that any of the intermediate entities/functions/nodes can change the request from the LRF/LS entity 160 and then forward/send another type of request towards the wireless device 150, assuming that the wireless device 150 still is able to correctly interpret the request.

In terms of step S106 according to which the wireless device obtains location information it is, according to embodiments, assumed that the information defining the location is by the wireless device 150 obtained e.g. from a positioning system, e.g. such as a Global Navigation Satellite System (GNSS), a Global Positioning System (GPS), a GALILEO navigation system, a

Globalnaya Navigatsionnaya Sputnikovaya Sistema (GLONASS), or a BeiDou Navigation Satellite System (BeiDou-2), of the wireless device 150. Hence, in order for the wireless device 150 to be able to obtain such location

information it is preferred that the wireless device 150 is equipped with a GPS entity or similar, or configured to be operatively connected to an external GPS entity or similar, from which the location information can be obtained. Alternatively, the information defining the location is by the wireless device 150 obtained from signal measurements made by the wireless device 150.

In terms of step S108 according to which the wireless device 150 provides the location information defining the location of the wireless device 150 to the LRF/LS entity 160 on the already established connection it is, according to embodiments, assumed that the wireless device 150 actually addresses the LRF/LS entity 160. This can be accomplished by the wireless device 150 invoking (e.g. encapsulating) the IP address or similar of the LRF/LS entity 160 and the wireless device 150 therefore provides (e.g., sends) the location information to the LRF/LS entity 160, even if there may be one or more intermediate functions/entities/nodes which receives the location

information from the wireless device 150 before the location information arrives at the LRF/LS entity 160.

Details of the already established connection will now be disclosed. It can be assumed that the already established connection is a connection at least between the wireless device 150 and the LRF/LS entity 160, but it could be between the wireless device 150 and the PSAP entity 190. According to a first embodiment the already established connection is not related to the ongoing communications session (i.e., not related to an ongoing Emergency Call). One example scenario is where the wireless device 150 already is attached to the ePDG entity 170 and thus has an already established connection once the mentioned ongoing communications session is set up. According to this first embodiment the request is received from the LRF/LS entity 160 via the ePDG entity 170 on the already established connection. An example of the established connection according to this first embodiment is an Internet Key Exchange (IKE) connection. The location request can then be received in an IKE INFORMATIONAL message with configuration attribute indicating that location information is requested (e.g., LOC_REQ). The configuration attribute could alternatively be defined by the IKEv2 Configuration Payload Attribute Types as provided in RFC5996 and by the Internet Assigned Numbers Authority (IANA). The location information can then be provided in an IKE INFORMATIONAL message with attribute UPLI. UPLI is then the same configuration payload attribute type as above (with length identical to zero defining the request, and length not identical to zero being the actual location information).

According to a second embodiment the already established connection is related to the ongoing communications session, where the already

established connection is used for, and initiated by, the ongoing

communications session itself. According to this second embodiment the request is received from the LRF/LS entity 160 via the E-CSCF entity 180. An example of the established connection according to this second embodiment is a Session Initiation Protocol (SIP) connection. The location request can then be received in an INFO message with attribute UPLI request. The location information can then be provided in a 200 OK message with attribute UPLI.

According to some aspects, the information defining the location of the wireless device 150 defines User Equipment Provided Location Information (UPLI). Reference is now made to Fig. 4 illustrating a method for location

determination of a wireless device 150 served by a non-3GPP radio access network 120 as performed by the LRF and/or LS entity 160 according to an embodiment. The LRF may e.g. comprise the LS or be implemented in or hosted by the LS and the terms may be used together as LRF/LS or separately as LRF or LS to indicate the same function.

It is assumed that the location of the wireless device 150 is requested by the network 100. The LRF/LS entity 160 is therefore configured to perform steps S202-S204:

S202: The LRF/LS entity 160 receives a location request for the location of the wireless device 150 sent by the PSAP entity 190. Examples of the location request will be provided below.

S204: The LRF/LS entity 160 provides the location request for the location of the wireless device 150 to the wireless device. The location request is provided during an ongoing communications session with the wireless device 150 on an already established connection.

It is assumed that the location request is received by the wireless device 150 as in step S104 and that the wireless device 150 performs steps S106 and S108 in response thereto. The LRF/LS entity 160 is therefore configured to perform steps S206-S208: S206: The LRF/LS entity 160 receives the location information defining the location of the wireless device 150, which location information is sent by the wireless device 150 on the already established connection.

S208: The LRF/LS entity 160 provides the location information to the PSAP entity 190.

Embodiments relating to further details of location determination of a wireless device 150 served by a non-3GPP radio access network 120 as performed by the LRF/LS entity 160 will now be disclosed.

According to an embodiment the location request is in step S202 received in a Fetch Location message on interface ATIS or on interface TIA J-STD-036- C.

As disclosed above, the ongoing communications session can be an ongoing emergency call.

As disclosed above, it can be assumed that the already established connection is a connection at least between the wireless device 150 and the LRF/LS entity 160, but it could be between the wireless device 150 and the PSAP entity 190.

In line with what has been disclosed above, the request can in step S204 be provided to the wireless device 150 via the ePDG entity 170. Further in line with what has been disclosed above, the established connection can be an IKE connection. The location request can then be provided in a Fetch

Location message with attribute MSISDN or IMEI. The location information can then be received in a Fetch Location message with attribute UPLI.

In line with what has been disclosed above, the request can in step S204 be provided to the wireless device 150 via the E-CSCF entity 180. Further in line with what has been disclosed above, the established connection can be a SIP connection. The location request can then be provided in a Request for UPLI message. The location information can then be received in an UPLI response message. As disclosed above, the information defining the location of the wireless device 150 can define UPLI.

Reference is now made to Fig. 5 illustrating a method for location

determination of a wireless device 150 served by a non-3GPP radio access network 120 as performed by the ePDG entity 170 according to an

embodiment.

It is assumed that the location of the wireless device 150 is requested by the network 100. It is further assumed that the LRF/LS entity 160 performs steps S202-S204 as disclosed above. The ePDG entity 170 is therefore configured to perform steps S302-S304:

S302: The ePDG entity 170 receives a location request for the location of the wireless device 150. The location request is sent by the LRF/LS entity 160 during an ongoing communications session with the wireless device 150 on an already established connection. S304: The ePDG entity 170 provides the location request for the location of the wireless device 150 to the wireless device 150 on the already established connection.

It is assumed that the location request is received by the wireless device 150 as in step S104 and that the wireless device 150 performs steps S106 and S108 in response thereto. The ePDG entity 1701s therefore configured to perform steps S306-S308:

S306: The ePDG entity 170 receives the location information defining the location of the wireless device 150 sent by the wireless device 150 on the already established connection. S308: The ePDG entity 170 provides the location information defining the location of the wireless device 150 to the LRF/LS entity 160 on the already established connection. As disclosed above, it can be assumed that the already established connection is a connection at least between the wireless device 150 and the LRF/LS entity 160, but it could be between the wireless device 150 and the PSAP entity 190. Two particular embodiments for location determination of a wireless device 150 served by a non-3GPP radio access network 120 will now be disclosed with references to the signalling diagrams of Figs. 6 and 7.

A first particular embodiment for location determination of a wireless device 150 served by a non-3GPP radio access network 120 based on at least some of the above disclosed embodiments will now be disclosed in detail with reference to Fig. 6. This first particular embodiment is based on the wireless device 150 being queried via the ePDG entity 170 using IKE.

This network initiated location procedure will be triggered by the PSAP entity 190. The PSAP entity 190 sends to the LRF and/or LS entity 160 a location update request for the wireless device 150 which is engaged in an EC session

(5503) . The LRF may e.g. comprise the LS or be implemented in or hosted by the LS and the terms may be used together as LRF/LS or separately as LRF or LS to indicate the same function. The LRF/LS entity 160 communicates

(5504) with the ePDG entity 170 associated with the wireless device 150 (using the IMEI/MSISDN of the wireless device 150 to locate the ePDG entity 170). The ePDG entity 170 queries the wireless device 150 using IKE as described above for an updated location (S505), enabling the wireless device 150 to provide its new location (S506). This device provided location can be a GPS location and/or an IP address, civic address, or similar. The ePDG entity 170 returns the updated location information of the wireless device 150 to the LRF/LS entity 160 (S507), which in turn returns it to the PSAP entity 190 (S508). Details of this procedure will now be disclosed.

S500: A communications session between the wireless device 150 and the PSAP entity 190 is ongoing over Wi-Fi access. The communications session involves handling an EC made by the wireless device 150. S501: The wireless device 150 is either stationary or moving during the ongoing communications session.

S502: The wireless device 150 performs a change of AP with IP continuity or a change of AP using the IKEv2 Mobility and Multihoming (MOBIKE) protocol. For example, the wireless device 150 may be attached to an AP which itself is mobile, for example an AP mounted in a vehicle or when the wireless device 150 is tethering with a cell phone. In this case the wireless device 150 will not change AP even if it is moving or the AP may be stationary and the wireless device 150 moves within the coverage area of the AP.

Alternatively, the wireless device 150 may move relative the AP it is operatively connected to and thereby re-attach to another AP. In case the Wi- Fi access network supports IP continuity, then the change of AP will not be noticed by the ePDG entity 170 and LRF/LS entity 160. If MOBIKE is used, then the change of AP will not be noticed by the LRF/LS entity 160. However, if the wireless device 150 moves then the location of the wireless device 150 will change, even if no change in AP is noticed.

It is assumed that the PSAP operator during the call requires the location of the wireless device 150 to be retrieved. This causes steps S503-S508 to be performed. S503: The PSAP entity 190 determines to identify the location of the wireless device 150 and therefore provides a location request for the location of the wireless device 150 in terms of a Fetch Location message with argument either the MSISDN/IMEI of the wireless device 150 or a reference identity "Ref Id" indicative of a device identifier of the wireless device 150 to the LRF/LS entity 160 using an applicable interface, e.g., per ATIS/TIA J-STD- 036-C. The method is thereby applicable for both wireless devices 150 with SIM as well as SIM-less wireless devices 150. One way to implement step S503 is to perform step S202.

S504: The LRF/LS entity 160 locates which ePDG entity 170 to fetch the location of the wireless device 150 from. For example, this can be done by the LRF/LS entity 160 keeping a session database which is populated when the EC connection is set up at attach time. The LRF/LS entity 160 then forwards the received Fetch Location message to the ePDG entity 170 using an applicable interface, e.g. Diameter. One way to implement step S504 is to perform steps S204, S302.

S505: The ePDG entity 170 sends a location request to the wireless device 150 over IKE. The protocols used between the ePDG entity 170 and the wireless device 150 are IKEv2 (signaling, RFC5996) and IPsec (payload). The ePDG entity 170 thus provides the location request for the location of the wireless device 150 to the wireless device 150 in an IKE INFORMATIONAL message with configuration attribute LOC_REQ indicating that location information is requested. One way to implement step S505 is to perform steps S104, S304.

S506: The wireless device 150 retrieves its UPLI from internal sources such as a WLAN access function and potential positioning function and responds back to the ePDG entity 170. The UPLI can be derived as for the UPLI in initial invite per 3GPP TS 24.229 V13.4.0 Section 5.1.6.8.2 and Section 5.1.6.8.3. The wireless device 150 thus obtains location information defining the location of the wireless device 150 and then responds to the location request by providing the location information in an IKE INFORMATIONAL message with the configuration attribute UPLI, where the UPLI defines the location of the wireless device 150, to the ePDG entity 170. One way to implement step S506 is to perform any of steps S106, S108, S306.

S507: The ePDG entity 170 forwards the received location information in a Fetch Location message with the configuration attribute UPLI to the LRF/LS entity 160. One way to implement step S507 is to perform steps S308, S206.

S508: The LRF/LS entity 160 forwards the received location information to the PSAP entity 190. One way to implement step S507 is to perform step S208. A second particular embodiment for location determination of a wireless device 150 served by a non-3GPP radio access network 120 based on at least some of the above disclosed embodiments will now be disclosed in detail with reference to Fig. 7. This second particular embodiment is based on the wireless device 150 being queried via IMS using SIP.

This network initiated location procedure will be triggered by the PSAP entity 190. The PSAP entity 190 sends to the LRF and/or LS entity 160 a location update request for the wireless device 150 which is engaged in an EC session

(5602) . The LRF may e.g. comprise the LS or be implemented in or hosted by the LS and the terms may be used together as LRF/LS or separately as LRF or

LS to indicate the same function. The LRF/LS entity 160 sends a request to that effect to the E-CSCF entity 180 associated with the wireless device 150

(5603) . The LRF/LS entity 160 establishes the association during the emergency session establishment procedure. The E-CSCF entity 180 in turn uses the established emergency signalling channel with the wireless device 150 to send a request to the wireless device 150 to update its location (S604). This device provided location can be a GPS location and/or an IP address, civic address, or similar. The wireless device 150 returns its updated location in the response to the E-CSCF entity 180 (S605). The E-CSCF entity 180 forwards the response to the LRF/LS entity 160 (S606). The LRF/LS entity 160 proxies the response to the PSAP entity 190 (S607). Details of this procedure will now be disclosed.

S600: A communications session between the wireless device 150 and the PSAP entity 190 is ongoing over Wi-Fi access. The ongoing communications session involves handling an EC made by the wireless device 150. During the setup of the EC it is preferred that the wireless device 150 provides a device identifier of the wireless device 150 to the PSAP entity 190 (for example the International Mobile Station Equipment Identity (IMEI) of the wireless device 150) to enable that the correct wireless device 150 later can be queried (e.g. as described later with reference to step S604) in case the subscription contains multiple devices. However, the device identifier of the wireless device 150 may be provided after the setup of the EC but preferably before the device is queried. One way to implement step S600 is to perform step S102.

S601: The wireless device 150 either makes a change of AP while retaining its IP address due to IP continuity in the radio access network 120 or due to MOBIKE or is moving without changing APs.

It is assumed that the PSAP operator during the call requires the location of the wireless device 150 to be retrieved. This causes steps S602-S607 to be taken.

S602: The PSAP entity 190 determines to identify the location of the wireless device 150 and therefore provides a location request for the location of the wireless device 150 in terms of a Fetch Location message with argument either the MSISDN of the wireless device 150 or a reference identity "Ref Id" indicative of a device identifier of the wireless device 150 to the LRF/LS entity 160 using an applicable interface, e.g., per ATIS/TIA J-STD-036-C. The method is thereby applicable for both wireless devices 150 with SIM as well as SIM-less wireless devices 150. One way to implement step S602 is to perform step S202.

S603: The LRF/LS entity 160 sends a request for the UPLI of the wireless device 150 received by the E-CSCF entity 180. Any suitable protocol may be used. These include, but are not limited to, the Simple Object Access Protocol (SOAP), the Hypertext Transfer Protocol (HTTP) or the Diameter protocol. The request contains identification of the wireless device 150 interns of the IP Multimedia Public Identity (IMPU) of the A-party (derived from P-Asserted- Id from the Emergency Call INVITE) and the device instance (derived from the "sip.instance" feature tag in the Emergency Call INVITE. The signaling is scoped to the correct wireless device 150 using the device identifier provided at EC setup (see step S600). One way to implement step S603 is to perform step S204.

S604: The E-CSCF entity 180 forwards the request or at least a part of request to the wireless device 150, preferably in the form of an INFO message with attribute UPLI request. Particularly, the E-CSCF entity 180 can send a SIP INFO message (inside the EC dialog) containing an Extensible Markup Language (XML)) body querying the current UPLI, including a Presence Information Data Format Location Object (PIDF-LO). The SIP signalling is scoped to the correct device using the device identifier provided at EC setup. One way to implement step S604 is to perform step S104.

S605: Triggered by the request received in step S604, the wireless device 150 provides its current UPLI, which defines the location information of the wireless device 150, to the E-CSCF entity 180, including a PIDF-LO in a 200 OK SIP message with the UPLI as attribute. In other words, the E-CSCF entity 180 receives the location information of the wireless device 150. One way to implement step S605 is to perform steps S106, S108.

S606: The E-CSCF entity 180 forwards the received location information of the wireless device 150 to the LRF/LS entity 160, preferably in an UPLI response message. One way to implement step S606 is to perform step S206.

S607: The LRF/LS entity 160 forwards the received location information to the PSAP entity 190. One way to implement step S607 is to perform step S208.

The second particular embodiment is applicable for both EPC-integrated (where EPC is short for Evolved Packet Core) Wi-Fi access and non-EPC- integrated Wi-Fi access and any wireless access using SIP for call control (for example Voice over LTE (VoLTE)), while the first particular embodiment described above with reference to Fig. 6 is applicable for EPC-integrated Wi- Fi access only. In general terms, IKE is used between the wireless device 150 and the EPC (implementing the core network 130), and for a wireless device 150 which is not EPC-integrated there is no IKE signaling present to the wireless device 150 and thus the first particular embodiment is not

applicable. For non-EPC-integrated Wi-Fi access, the wireless device 150 will still use SIP for the actual EC and thus the second particular embodiment will always be applicable. Fig. 8a schematically illustrates, in terms of a number of functional units, the components of a wireless device 150 according to an embodiment.

Processing circuitry 810 is provided using any combination of one or more of a suitable central processing unit (CPU), multiprocessor, microcontroller, digital signal processor (DSP), etc., capable of executing software instructions stored in a computer program product 1110a (as in Fig. 11), e.g. in the form of a storage medium 830. The processing circuitry 810 may further be provided as at least one application specific integrated circuit (ASIC), or field programmable gate array (FPGA). Particularly, the processing circuitry 810 is configured to cause the wireless device 150 to perform a set of operations, or steps, S102-S108, as disclosed above. For example, the storage medium 830 may store the set of operations, and the processing circuitry 810 may be configured to retrieve the set of operations from the storage medium 830 to cause the wireless device 150 to perform the set of operations. The set of operations may be provided as a set of executable instructions. Thus the processing circuitry 810 is thereby arranged to execute methods as herein disclosed.

The storage medium 830 may also comprise persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, solid state memory or even remotely mounted memory.

The wireless device 150 may further comprise a communications interface 820 for communications with entities of the core network 130 and the service network 140 via the radio access network 120. As such the communications interface 220 may comprise one or more transmitters and receivers, comprising analogue and digital components.

The processing circuitry 810 controls the general operation of the wireless device 150 e.g. by sending data and control signals to the communications interface 820 and the storage medium 830, by receiving data and reports from the communications interface 820, and by retrieving data and instructions from the storage medium 830. Other components, as well as the related functionality, of the wireless device 150 are omitted in order not to obscure the concepts presented herein.

Fig. 8b schematically illustrates, in terms of a number of functional modules, the components of a wireless device 150 according to an

embodiment. The wireless device 150 of Fig. 8b comprises a number of functional modules; a receive module 810a configured to perform step S104, an obtain module 810b configured to perform step S106, and a first provide module 810c configured to perform step S108. The wireless device 150 of Fig. 8b may further comprise a number of optional functional modules, such as a second provide module 8iod configured to perform step S102. In general terms, each functional module 8ioa-8iod may be implemented in hardware or in software. Preferably, one or more or all functional modules 8ioa-8iod may be implemented by the processing circuitry 810, possibly in cooperation with functional units 820 and/or 830. The processing circuitry 210 may thus be arranged to from the storage medium 830 fetch instructions as provided by a functional module 8ioa-8iod and to execute these instructions, thereby performing steps S102-S108.

Fig. 9a schematically illustrates, in terms of a number of functional units, the components of a LRF/LS entity 160 according to an embodiment.

Processing circuitry 910 is provided using any combination of one or more of a suitable central processing unit (CPU), multiprocessor, microcontroller, digital signal processor (DSP), etc., capable of executing software instructions stored in a computer program product mob (as in Fig. 11), e.g. in the form of a storage medium 930. The processing circuitry 910 may further be provided as at least one application specific integrated circuit (ASIC), or field programmable gate array (FPGA).

Particularly, the processing circuitry 910 is configured to cause the LRF/LS entity 160 to perform a set of operations, or steps, S202-S208, as disclosed above. For example, the storage medium 930 may store the set of operations, and the processing circuitry 910 may be configured to retrieve the set of operations from the storage medium 930 to cause the LRF/LS entity 160 to perform the set of operations. The set of operations may be provided as a set of executable instructions. Thus the processing circuitry 910 is thereby arranged to execute methods as herein disclosed.

The storage medium 930 may also comprise persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, solid state memory or even remotely mounted memory.

The LRF/LS entity 160 may further comprise a communications interface 920 for communications with other entities of the core network 130, with entities of the service network 140, and with entities (such as the wireless device 150) served by the radio access network 120. As such the

communications interface 920 may comprise one or more transmitters and receivers, comprising analogue and digital components.

The processing circuitry 910 controls the general operation of the LRF/LS entity 160 e.g. by sending data and control signals to the communications interface 920 and the storage medium 930, by receiving data and reports from the communications interface 920, and by retrieving data and instructions from the storage medium 930. Other components, as well as the related functionality, of the LRF/LS entity 160 are omitted in order not to obscure the concepts presented herein. Fig. 9b schematically illustrates, in terms of a number of functional modules, the components of a LRF/LS entity 160 according to an

embodiment. The LRF/LS entity 160 of Fig. 9b comprises a number of functional modules; a first receive module 910a configured to perform step S202, a first provide module 910b configured to perform step S204, and a second receive module 910c configured to perform step S206, and a second provide module 9iod configured to perform step S208. The LRF/LS entity 160 of Fig. 9b may further comprise a number of optional functional modules. In general terms, each functional module 9ioa-9iod may be implemented in hardware or in software. Preferably, one or more or all functional modules 9ioa-9iod may be implemented by the processing circuitry 910, possibly in cooperation with functional units 920 and/or 930. The processing circuitry 910 may thus be arranged to from the storage medium 930 fetch instructions as provided by a functional module 910a- 9iod and to execute these instructions, thereby performing steps S202-S208. Fig. 10a schematically illustrates, in terms of a number of functional units, the components of an ePDG entity 170 according to an embodiment.

Processing circuitry 1010 is provided using any combination of one or more of a suitable central processing unit (CPU), multiprocessor, microcontroller, digital signal processor (DSP), etc., capable of executing software instructions stored in a computer program product mob (as in Fig. 11), e.g. in the form of a storage medium 1030. The processing circuitry 1010 may further be provided as at least one application specific integrated circuit (ASIC), or field programmable gate array (FPGA).

Particularly, the processing circuitry 1010 is configured to cause the ePDG entity 170 to perform a set of operations, or steps, S302-S308, as disclosed above. For example, the storage medium 1030 may store the set of

operations, and the processing circuitry 1010 may be configured to retrieve the set of operations from the storage medium 1030 to cause the ePDG entity 170 to perform the set of operations. The set of operations may be provided as a set of executable instructions. Thus the processing circuitry 1010 is thereby arranged to execute methods as herein disclosed.

The storage medium 1030 may also comprise persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, solid state memory or even remotely mounted memory. The ePDG entity 170 may further comprise a communications interface 320 for communications with other entities of the service network 140, with entities of the core network 130, and with entities (such as the wireless device 150) served by the radio access network 120. As such the communications interface 1020 may comprise one or more transmitters and receivers, comprising analogue and digital components. The processing circuitry 310 controls the general operation of the ePDG entity 170 e.g. by sending data and control signals to the communications interface 1020 and the storage medium 1030, by receiving data and reports from the communications interface 1020, and by retrieving data and instructions from the storage medium 1030. Other components, as well as the related functionality, of the ePDG entity 170 are omitted in order not to obscure the concepts presented herein.

Fig. 10b schematically illustrates, in terms of a number of functional modules, the components of an ePDG entity 170 according to an

embodiment. The ePDG entity 170 of Fig. 10b comprises a number of functional modules; a first receive module 1010a configured to perform step S302, a first provide module 1010b configured to perform step S304, and a second receive module 1010c configured to perform step S306, and a second provide module loiod configured to perform step S308. The ePDG entity 170 of Fig. 10b may further comprise a number of optional functional modules. In general terms, each functional module loioa-ioiod may be implemented in hardware or in software. Preferably, one or more or all functional modules loioa-ioiod may be implemented by the processing circuitry 1010, possibly in cooperation with functional units 1020 and/or 1030. The processing circuitry 1010 may thus be arranged to from the storage medium 1030 fetch instructions as provided by a functional module loioa-ioiod and to execute these instructions, thereby performing steps S302-S308.

The LRF/LS entity 160 and/or ePDG entity 170 may be provided as a standalone device or as a part of at least one further device. For example, the LRF/LS entity 160 and/or ePDG entity 170 may be provided in a node of the core network 130 or distributed between at least two devices or nodes in the core network 130.

Thus, a first portion of the instructions performed by the LRF/LS entity 160 and/or ePDG entity 170 may be executed in a first device, and a second portion of the of the instructions performed by the LRF/LS entity 160 and/or ePDG entity 170 may be executed in a second device; the herein disclosed embodiments are not limited to any particular number of devices on which the instructions performed by the LRF/LS entity 160 and/or ePDG entity 170 may be executed. Hence, the methods according to the herein disclosed embodiments are suitable to be performed by a LRF/LS entity 160 and/or ePDG entity 170 residing in a cloud computational environment. Therefore, although a single processing circuitry 810, 910, 1010 is illustrated in Figs. 8a, 9a, and 10a the processing circuitry 810, 910, 1010 may be distributed among a plurality of devices, or nodes. The same applies to the functional modules 8ioa-8iod, 9ioa-9iod, loioa-ioiod of Figs. 8b, 9b and 10b and the computer programs 1120a, 1120b, 1120c of Fig. 11 (see below).

The methods are advantageously provided as computer programs 1120a, 1120b, 1120c. Fig. 11 shows one example of a computer program product 1110a, mob, 1110c comprising computer readable means 1130. On this computer readable means 1130, a computer program 1120a can be stored, which computer program 1120a can cause the processing circuitry 810 and thereto operatively coupled entities and devices, such as the communications interface 820 and the storage medium 830, to execute methods according to embodiments described herein. The computer program 1120a and/or computer program product 1110a may thus provide means for performing any steps of the wireless device 150 as herein disclosed. On this computer readable means 1130, a computer program 1120b can be stored, which computer program 1120b can cause the processing circuitry 910 and thereto operatively coupled entities and devices, such as the communications interface 920 and the storage medium 930, to execute methods according to embodiments described herein. The computer program 1120b and/or computer program product mob may thus provide means for performing any steps of the LRF/LS entity 160 as herein disclosed. On this computer readable means 1130, a computer program 1120c can be stored, which computer program 1120c can cause the processing circuitry 1010 and thereto operatively coupled entities and devices, such as the communications interface 1020 and the storage medium 1030, to execute methods according to embodiments described herein. The computer program 1120c and/or computer program product moc may thus provide means for performing any steps of the ePDG entity 170 as herein disclosed.

In the example of Fig. 11, the computer program product 1110a, mob, moc is illustrated as an optical disc, such as a CD (compact disc) or a DVD (digital versatile disc) or a Blu-Ray disc. The computer program product 1110a, mob, moc could also be embodied as a memory, such as a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), or an electrically erasable programmable read-only memory (EEPROM) and more particularly as a non-volatile storage medium of a device in an external memory such as a USB (Universal Serial Bus) memory or a Flash memory, such as a compact Flash memory. Thus, while the computer program 1120a, 1120b, 1120c is here schematically shown as a track on the depicted optical disk, the computer program 1120a, 1120b, 1120c can be stored in any way which is suitable for the computer program product 1110a, mob, moc.

Some embodiments described above may be summarized in the following manner:

One embodiment is directed to a method for location determination of a wireless device served by a non-3GPP radio access network, the method being performed by the wireless device. The method comprises:

receiving a location request for the location of the wireless device (150) sent by a LRF during an ongoing communications session on an already established connection;

obtaining location information defining the location of the wireless device; and

providing said location information defining the location of the wireless device to the LRF entity on said already established connection.

Said ongoing communications session may be an ongoing emergency call. The method may further comprise:

providing a device identifier of the wireless device to a PSAP entity during setup of the emergency call.

The request may be received from the LRF entity via an ePDG entity. The established connection may be an IKE connection.

The location request may be received in an IKE INFORMATIONAL message with configuration attribute indicating that location information is requested (e.g., LOC_REQ).

The location information may be provided in an IKE INFORMATIONAL message with attribute UPLI.

The request may be received from the LRF entity via an E-CSCF entity.

The established connection may be a SIP connection.

The location request may be received in an INFO message with attribute UPLI request. The location information may be provided in a 200 OK message with attribute UPLI.

The information defining the location of the wireless device may define UPLI.

Said information defining the location may be obtained from a GNSS, a GPS, a GALILEO navigation system, a GLONASS, or a BeiDou Navigation Satellite System, BeiDou-2, of the wireless device or from signal measurements made by the wireless device.

Another embodiment is directed to a method for location determination of a wireless device served by a non-3GPP radio access network, the method being performed by a LRF entity. The method comprises:

receiving a location request for the location of the wireless device sent by a Public-Safety Answering Point, PSAP, entity;

providing the location request for the location of the wireless device to the wireless device during an ongoing communications session with the wireless device on an already established connection;

receiving location information defining the location of the wireless device, which location information is sent by the wireless device on said already established connection; and

providing the location information to the PSAP entity.

Said ongoing session may be an ongoing emergency call. The request may be provided to the wireless device via an evolved an ePDG, entity.

The established connection may be an IKE connection.

The location request may be provided in a Fetch Location message with attribute MSISDN or IMEI. The location information may be received in a Fetch Location message with attribute UPLI.

The request may be provided to the wireless device via an E-CSCF entity.

The established connection may be a SIP connection.

The location request may be provided in a Request for UPLI message. The location information may be received in an UPLI response message.

The information defining the location of the wireless device may define UPLI.

The location request may be received in a Fetch Location message on interface ATIS or on interface TIA J-STD-036-C. Another embodiment is directed to a method for location determination of a wireless device served by a non-3GPP radio access network, the method being performed by an ePDG entity. The method comprises:

receiving a location request for the location of the wireless device sent by a LRF entity during an ongoing communications session with the wireless device on an already established connection;

providing the location request for the location of the wireless device to the wireless device on said already established connection;

receiving location information defining the location of the wireless device from the wireless device on said already established connection; and providing said location information defining the location of the wireless device to the LRF entity on said already established connection.

Another embodiment is directed to a wireless device for location

determination of the wireless device served by a non-3GPP radio access network, the wireless device comprising processing circuitry, the processing circuitry being configured to cause the wireless device to:

receive a location request for the location of the wireless device sent by a Location Retrieval Function, LRF, entity during an ongoing communications session on an already established connection;

obtain location information defining the location of the wireless device; and

provide said location information defining the location of the wireless device to the LRF entity on said already established connection.

Another embodiment is directed to a LRF entity for location determination of a wireless device served by a non-3GPP radio access network, the LRF entity comprising processing circuitry, the processing circuitry being configured to cause the LRF entity to:

receive a location request for the location of the wireless device sent by a PSAP entity;

provide the location request for the location of the wireless device to the wireless device during an ongoing communications session with the wireless device on an already established connection;

receive location information defining the location of the wireless device, which location information is sent by the wireless device on said already established connection; and

provide the location information to the PSAP entity.

Another embodiment is directed to an ePDG entity for location

determination of a wireless device served by a non-3GPP radio access network, the ePDG entity comprising processing circuitry, the processing circuitry being configured to cause the ePDG entity to:

receive a location request for the location of the wireless device sent by a LRF entity during an ongoing communications session with the wireless device on an already established connection;

provide the location request for the location of the wireless device to the wireless device on said already established connection;

receive location information defining the location of the wireless device, which location information is sent by the wireless device on said already established connection; and

provide said location information defining the location of the wireless device to the LRF entity on said already established connection.

Another embodiment is directed to a computer program for location determination of a wireless device served by a non-3GPP radio access network, the computer program comprising computer code which, when run on processing circuitry of the wireless device, causes the wireless device to: receive a location request for the location of the wireless device sent by a LRF entity during an ongoing communications session on an already established connection;

obtain location information defining the location of the wireless device; and

provide said location information defining the location of the wireless device to the LRF entity on said already established connection.

Another embodiment is directed to a computer program for location determination of a wireless device served by a non-3GPP radio access network, the computer program comprising computer code which, when run on processing circuitry of a LRF entity, causes the LRF entity to:

receive a location request for the location of the wireless device sent by a PSAP entity;

provide the location request for the location of the wireless device to the wireless device during an ongoing communications session with the wireless device on an already established connection;

receive location information defining the location of the wireless device, which location information is sent by the wireless device (150) on said already established connection; and

provide (S208) the location information to the PSAP entity (190).

Another embodiment is directed to a computer program for location determination of a wireless device served by a non-3GPP radio access network, the computer program comprising computer code which, when run on processing circuitry of an ePDG entity, causes the ePDG entity to:

receive a location request for the location of the wireless device sent by a

LRF entity during an ongoing communications session with the wireless device on an already established connection;

provide the location request for the location of the wireless device to the wireless device on said already established connection;

receive location information defining the location of the wireless device, which location information is sent by the wireless device on said already established connection; and

provide said location information defining the location of the wireless device to the LRF entity on said already established connection.

The inventive concept has mainly been described above with reference to a few embodiments. However, as is readily appreciated by a person skilled in the art, other embodiments than the ones disclosed above are equally possible within the scope of the inventive concept, as defined by the appended patent claims.