Apparatus, method and computer program

Abstract

An apparatus, method and computer program are provided for causing a user device to perform: when the user device is located in a first domain, receiving assistance information from a first network function located in the first domain, the assistance information identifying a user plane server that provides a positioning service for the user device through a user plane of another domain; and after executing the switching of the user equipment from the first domain to the other domain, establishing a data connection with a user plane server based on the auxiliary information, so as to provide a positioning service for the user equipment through a user plane of the other domain.

Description

Technical Field

[0001] Various examples described herein relate generally to apparatus, methods and computer programs, and more particularly (but not exclusively) to apparatus, methods for apparatus and computer programs. Background Art

[0002] A communication system may be viewed as a facility that enables a communication session between two or more entities (such as communication devices, base stations and / or other nodes) by providing bearers between the various entities involved in the communication path.

[0003] The communication system may be a wireless communication system. Examples of wireless systems include public land mobile networks (PLMNs) operating based on radio standards (such as those provided by 3GPP), satellite-based communication systems, and different wireless local networks, such as wireless local area networks (WLANs). Wireless systems can typically be divided into cells and are therefore often referred to as cellular systems.

[0004] Communication systems and associated equipment typically operate according to a given standard or specification that lists what the various entities associated with the system are permitted to do and how it should be achieved. The communication protocols and / or parameters that will be used for the connection are also typically defined. An example of a standard is the so-called 5G standard. Summary of the invention

[0005] According to a first aspect, a method for a user equipment is provided, the method comprising: when the user equipment is located in a first domain, receiving auxiliary information from a first network function located in the first domain, the auxiliary information identifying a user plane server that provides a positioning service for the user equipment through a user plane of another domain; and after performing a handover of the user equipment from the first domain to another domain, establishing a data connection with the user plane server based on the auxiliary information, so as to provide a positioning service for the user equipment through the user plane of another domain.

[0006] The data connection may be a Packet Data Network (PDN) connection; and wherein the assistance information is used to reach a user plane server through the PDN connection.

[0007] The assistance information may be received before a command for said handover is sent to the user equipment.

[0008] The first domain may be configured as a 3rd Generation Partnership Project 3GPP 5G system 5GS; and wherein the other domain may be configured as a 3GPP Evolved Packet System EPS.

[0009] The assistance information may be received from the access and mobility function via non-access stratum NAS signaling.

[0010] The assistance information may be received within a downlink NAS transport message from the access and mobility function.

[0011] The assistance information may be received from the positioning management function via Long Term Evolution Positioning Protocol (LPP) signaling.

[0012] The assistance information may be received within the Location Services User Plane LCUP Assistance Information data from the Location Management Function.

[0013] The assistance information may be received from the location management function via secure user plane positioning SUPL signaling.

[0014] The assistance information may be received within a SUPL Initiation message from the Location Management Function.

[0015] The first network function may be an access and mobility function.

[0016] The first network function may be a positioning management function.

[0017] The first network function may be a positioning service user plane function.

[0018] The auxiliary information may include address information of the user plane server.

[0019] The assistance information may include at least one of the following: an address of a user plane server; a unique identifier of the user plane server; a positioning service-related identifier; one or more fully qualified domain names (FQDNs) of the user plane server; secure user plane positioning assistance information for establishing a user plane connection in the second domain; or transport layer security assistance information for establishing a user plane connection in the second domain.

[0020] According to a second aspect, a method for a first network function located in a first domain is provided, the method comprising: determining that a user equipment receiving a positioning service through a user plane via the first domain is to be switched from the first domain to another domain; and providing auxiliary information to the user equipment, the auxiliary information identifying a user plane server for providing the positioning service to the user equipment through a user plane of the other domain after the user equipment is switched to the second domain.

[0021] Determining that the user equipment is to be handed over may be performed based on receiving a handover indication from a mobility management entity.

[0022] Providing may include providing the assistance information directly to the user equipment.

[0023] Providing may include providing the assistance information indirectly to the user equipment via at least one of: a positioning management function; or a positioning service user plane function.

[0024] The first network function may be an access and mobility function.

[0025] The auxiliary information may include address information of the user plane server.

[0026] The assistance information may include at least one of the following: an address of a user plane server; a unique identifier of the user plane server; a positioning service-related identifier; one or more fully qualified domain names (FQDNs) of the user plane server; secure user plane positioning assistance information for establishing a user plane connection in the second domain; or transport layer security assistance information for establishing a user plane connection in the second domain.

[0027] According to a third aspect, a method for a first network function located in a first domain is provided, the method comprising: receiving a positioning request for a user equipment located in the first domain; determining that the user equipment has previously received a positioning service through a user plane via another domain; and providing auxiliary information to the user equipment, the auxiliary information identifying a user plane server for providing positioning services for the user equipment through the user plane.

[0028] Determining that the user equipment has previously received positioning services over the user plane via another domain may be performed based on receiving a handover indication from the mobility management entity.

[0029] Providing may include providing the assistance information directly to the user equipment.

[0030] Providing may include providing the assistance information indirectly to the user equipment via at least one of: a positioning management function; or a positioning service user plane function.

[0031] The first network function may be an access and mobility function.

[0032] The auxiliary information may include address information of the user plane server.

[0033] The assistance information may include at least one of the following: an address of a user plane server; a unique identifier of the user plane server; a positioning service-related identifier; one or more fully qualified domain names (FQDNs) of the user plane server; secure user plane positioning assistance information for establishing a user plane connection in the second domain; or transport layer security assistance information for establishing a user plane connection in the second domain.

[0034] According to a fourth aspect, a method for a second network function located in a first domain is provided, the method comprising: receiving auxiliary information from a first network function located in the first domain, the auxiliary information identifying a user plane server for providing positioning services to a user equipment via a user plane of another domain; and providing the auxiliary information to the user equipment.

[0035] The second network function may be at least one of the following: a positioning management function; or a positioning service user plane function.

[0036] The first network function may be an access and mobility function.

[0037] The auxiliary information may include address information of the user plane server.

[0038] The assistance information may include at least one of the following: an address of a user plane server; a unique identifier of the user plane server; a positioning service-related identifier; one or more fully qualified domain names (FQDNs) of the user plane server; secure user plane positioning assistance information for establishing a user plane connection in the second domain; or transport layer security assistance information for establishing a user plane connection in the second domain.

[0039] According to a fifth aspect, a device for a user equipment is provided, the device comprising a component for performing the following operations: when the user equipment is located in a first domain, receiving auxiliary information from a first network function located in the first domain, the auxiliary information identifying a user plane server that provides a positioning service for the user equipment through a user plane of another domain; and after performing a handover of the user equipment from the first domain to another domain, establishing a data connection with the user plane server based on the auxiliary information, so as to provide a positioning service for the user equipment through the user plane of another domain.

[0040] The data connection may be a Packet Data Network (PDN) connection; and wherein the assistance information is used to reach a user plane server through the PDN connection.

[0041] The assistance information may be received before a command for said handover is sent to the user equipment.

[0042] The first domain may be configured as a 3rd Generation Partnership Project 3GPP 5G system 5GS; and wherein the other domain may be configured as a 3GPP Evolved Packet System EPS.

[0043] The assistance information may be received from the access and mobility function via non-access stratum NAS signaling.

[0044] The assistance information may be received within a downlink NAS transport message from the access and mobility function.

[0045] The assistance information may be received from the positioning management function via Long Term Evolution Positioning Protocol (LPP) signaling.

[0046] The assistance information may be received within the Location Services User Plane LCUP Assistance Information data from the Location Management Function.

[0047] The assistance information may be received from the location management function via secure user plane positioning SUPL signaling.

[0048] The assistance information may be received within a SUPL Initiation message from the Location Management Function.

[0049] The first network function may be an access and mobility function.

[0050] The first network function may be a positioning management function.

[0051] The first network function may be a positioning service user plane function.

[0052] The auxiliary information may include address information of the user plane server.

[0053] The assistance information may include at least one of the following: an address of a user plane server; a unique identifier of the user plane server; a positioning service-related identifier; one or more fully qualified domain names (FQDNs) of the user plane server; secure user plane positioning assistance information for establishing a user plane connection in the second domain; or transport layer security assistance information for establishing a user plane connection in the second domain.

[0054] According to a sixth aspect, a device for a first network function located in a first domain is provided, the device comprising a component for performing the following operations: determining that a user equipment receiving a positioning service through a user plane via the first domain is about to be switched from the first domain to another domain; and providing auxiliary information to the user equipment, the auxiliary information identifying a user plane server for providing a positioning service to the user equipment through a user plane of another domain after the user equipment is switched to the second domain.

[0055] Determining that the user equipment is to be handed over may be performed based on receiving a handover indication from a mobility management entity.

[0056] The means for providing may include means for providing the assistance information directly to the user equipment.

[0057] The means for providing may comprise means for providing the assistance information to the user equipment indirectly via at least one of: a positioning management function; or a positioning service user plane function.

[0058] The first network function may be an access and mobility function.

[0059] The auxiliary information may include address information of the user plane server.

[0060] The assistance information may include at least one of the following: an address of a user plane server; a unique identifier of the user plane server; a positioning service-related identifier; one or more fully qualified domain names (FQDNs) of the user plane server; secure user plane positioning assistance information for establishing a user plane connection in the second domain; or transport layer security assistance information for establishing a user plane connection in the second domain.

[0061] According to a seventh aspect, a device for a first network function located in a first domain is provided, the device comprising components for performing the following operations: receiving a positioning request for a user equipment located in the first domain; determining that the user equipment has previously received positioning services through a user plane via another domain; and providing auxiliary information to the user equipment, the auxiliary information identifying a user plane server for providing positioning services to the user equipment through the user plane.

[0062] Determining that the user equipment has previously received positioning services over the user plane via another domain may be performed based on receiving a handover indication from the mobility management entity.

[0063] The means for providing may include means for providing the assistance information directly to the user equipment.

[0064] The means for providing may comprise means for providing the assistance information to the user equipment indirectly via at least one of: a positioning management function; or a positioning service user plane function.

[0065] The first network function may be an access and mobility function.

[0066] The auxiliary information may include address information of the user plane server.

[0067] The assistance information may include at least one of the following: an address of a user plane server; a unique identifier of the user plane server; a positioning service-related identifier; one or more fully qualified domain names (FQDNs) of the user plane server; secure user plane positioning assistance information for establishing a user plane connection in the second domain; or transport layer security assistance information for establishing a user plane connection in the second domain.

[0068] According to an eighth aspect, a device for a second network function located in a first domain is provided, the device comprising a component for performing the following operations: receiving auxiliary information from a first network function located in the first domain, the auxiliary information identifying a user plane server for providing positioning services to a user equipment via a user plane of another domain; and providing the auxiliary information to the user equipment.

[0069] The second network function may be at least one of the following: a positioning management function; or a positioning service user plane function.

[0070] The first network function may be an access and mobility function.

[0071] The auxiliary information may include address information of the user plane server.

[0072] The assistance information may include at least one of the following: an address of a user plane server; a unique identifier of the user plane server; a positioning service-related identifier; one or more fully qualified domain names (FQDNs) of the user plane server; secure user plane positioning assistance information for establishing a user plane connection in the second domain; or transport layer security assistance information for establishing a user plane connection in the second domain.

[0073] According to a ninth aspect, a device for a user equipment is provided, the device comprising: at least one processor; and at least one memory comprising code, which, when executed by the at least one processor, causes the device to perform: when the user equipment is located in a first domain, receiving auxiliary information from a first network function located in the first domain, the auxiliary information identifying a user plane server that provides positioning services for the user equipment through a user plane of another domain; and after performing a handover of the user equipment from the first domain to another domain, establishing a data connection with the user plane server based on the auxiliary information, so as to provide positioning services for the user equipment through a user plane of another domain.

[0074] The data connection may be a Packet Data Network (PDN) connection; and wherein the assistance information is used to reach a user plane server through the PDN connection.

[0075] The assistance information may be received before a command for said handover is sent to the user equipment.

[0076] The first domain may be configured as a 3rd Generation Partnership Project 3GPP 5G system 5GS; and wherein the other domain may be configured as a 3GPP Evolved Packet System EPS.

[0077] The assistance information may be received from the access and mobility function via non-access stratum NAS signaling.

[0078] The assistance information may be received within a downlink NAS transport message from the access and mobility function.

[0079] The assistance information may be received from the positioning management function via Long Term Evolution Positioning Protocol (LPP) signaling.

[0080] The assistance information may be received within the Location Services User Plane LCUP Assistance Information data from the Location Management Function.

[0081] The assistance information may be received from the location management function via secure user plane positioning SUPL signaling.

[0082] The assistance information may be received within a SUPL Initiation message from the Location Management Function.

[0083] The first network function may be an access and mobility function.

[0084] The first network function may be a positioning management function.

[0085] The first network function may be a positioning service user plane function.

[0086] The auxiliary information may include address information of the user plane server.

[0087] The assistance information may include at least one of the following: an address of a user plane server; a unique identifier of the user plane server; a positioning service-related identifier; one or more fully qualified domain names (FQDNs) of the user plane server; secure user plane positioning assistance information for establishing a user plane connection in the second domain; or transport layer security assistance information for establishing a user plane connection in the second domain.

[0088] According to a tenth aspect, a device for a first network function located in a first domain is provided, the device comprising: at least one processor; and at least one memory comprising code, which, when executed by the at least one processor, causes the device to perform: determining that a user equipment receiving a positioning service through a user plane via the first domain is about to be switched from the first domain to another domain; and providing auxiliary information to the user equipment, the auxiliary information identifying a user plane server for providing a positioning service to the user equipment through a user plane of another domain after the user equipment is switched to the second domain.

[0089] Determining that the user equipment is to be handed over may be performed based on receiving a handover indication from a mobility management entity.

[0090] Providing may include providing the assistance information directly to the user equipment.

[0091] Providing may include providing the assistance information indirectly to the user equipment via at least one of: a positioning management function; or a positioning service user plane function.

[0092] The first network function may be an access and mobility function.

[0093] The auxiliary information may include address information of the user plane server.

[0094] The assistance information may include at least one of the following: an address of a user plane server; a unique identifier of the user plane server; a positioning service-related identifier; one or more fully qualified domain names (FQDNs) of the user plane server; secure user plane positioning assistance information for establishing a user plane connection in the second domain; or transport layer security assistance information for establishing a user plane connection in the second domain.

[0095] According to an eleventh aspect, a device for a first network function located in a first domain is provided, the device comprising: at least one processor; and at least one memory comprising code, which, when executed by the at least one processor, causes the device to perform: receiving a positioning request for a user equipment located in the first domain; determining that the user equipment has previously received positioning services through a user plane via another domain; and providing auxiliary information to the user equipment, the auxiliary information identifying a user plane server for providing positioning services to the user equipment through the user plane.

[0096] Determining that the user equipment has previously received positioning services over the user plane via another domain may be performed based on receiving a handover indication from the mobility management entity.

[0097] Providing may include providing the assistance information directly to the user equipment.

[0098] Providing may include providing the assistance information indirectly to the user equipment via at least one of: a positioning management function; or a positioning service user plane function.

[0099] The first network function may be an access and mobility function.

[0100] The auxiliary information may include address information of the user plane server.

[0101] The assistance information may include at least one of the following: an address of a user plane server; a unique identifier of the user plane server; a positioning service-related identifier; one or more fully qualified domain names (FQDNs) of the user plane server; secure user plane positioning assistance information for establishing a user plane connection in the second domain; or transport layer security assistance information for establishing a user plane connection in the second domain.

[0102] According to the twelfth aspect, a device for a second network function located in a first domain is provided, the device comprising: at least one processor; and at least one memory comprising code, which, when executed by the at least one processor, causes the device to perform: receiving auxiliary information from the first network function located in the first domain, the auxiliary information identifying a user plane server for providing positioning services to a user equipment through a user plane of another domain; and providing the auxiliary information to the user equipment.

[0103] The second network function may be at least one of the following: a positioning management function; or a positioning service user plane function.

[0104] The first network function may be an access and mobility function.

[0105] The auxiliary information may include address information of the user plane server.

[0106] The assistance information may include at least one of the following: an address of a user plane server; a unique identifier of the user plane server; a positioning service-related identifier; one or more fully qualified domain names (FQDNs) of the user plane server; secure user plane positioning assistance information for establishing a user plane connection in the second domain; or transport layer security assistance information for establishing a user plane connection in the second domain.

[0107] According to the thirteenth aspect, a device for a user equipment is provided, the device comprising: a receiving circuit for receiving auxiliary information from a first network function located in the first domain when the user equipment is located in the first domain, the auxiliary information identifying a user plane server that provides positioning services for the user equipment through a user plane of another domain; and an establishing circuit for establishing a data connection with the user plane server based on the auxiliary information after performing a handover of the user equipment from the first domain to another domain, so as to provide positioning services for the user equipment through the user plane of another domain.

[0108] The data connection may be a Packet Data Network (PDN) connection; and wherein the assistance information is used to reach a user plane server through the PDN connection.

[0109] The assistance information may be received before a command for said handover is sent to the user equipment.

[0110] The first domain may be configured as a 3rd Generation Partnership Project 3GPP 5G system 5GS; and wherein the other domain may be configured as a 3GPP Evolved Packet System EPS.

[0111] The assistance information may be received from the access and mobility function via non-access stratum NAS signaling.

[0112] The assistance information may be received within a downlink NAS transport message from the access and mobility function.

[0113] The assistance information may be received from the positioning management function via Long Term Evolution Positioning Protocol (LPP) signaling.

[0114] The assistance information may be received within the Location Services User Plane LCUP Assistance Information data from the Location Management Function.

[0115] The assistance information may be received from the location management function via secure user plane positioning SUPL signaling.

[0116] The assistance information may be received within a SUPL Initiation message from the Location Management Function.

[0117] The first network function may be an access and mobility function.

[0118] The first network function may be a positioning management function.

[0119] The first network function may be a positioning service user plane function.

[0120] The auxiliary information may include address information of the user plane server.

[0121] The assistance information may include at least one of the following: an address of a user plane server; a unique identifier of the user plane server; a positioning service-related identifier; one or more fully qualified domain names (FQDNs) of the user plane server; secure user plane positioning assistance information for establishing a user plane connection in the second domain; or transport layer security assistance information for establishing a user plane connection in the second domain.

[0122] According to a fourteenth aspect, a device for a first network function located in a first domain is provided, the device comprising: a determination circuit for determining that a user equipment receiving a positioning service through a user plane via the first domain is to be switched from the first domain to another domain; and a circuit for providing auxiliary information to the user equipment, the auxiliary information identifying a user plane server for providing a positioning service to the user equipment through a user plane of another domain after the user equipment is switched to the second domain.

[0123] Determining that the user equipment is to be handed over may be performed based on receiving a handover indication from a mobility management entity.

[0124] The providing circuitry for providing may comprise providing circuitry for providing the auxiliary information directly to the user equipment.

[0125] The providing circuitry for providing may comprise providing circuitry for providing the assistance information indirectly to the user equipment via at least one of: a positioning management function; or a positioning service user plane function.

[0126] The first network function may be an access and mobility function.

[0127] The auxiliary information may include address information of the user plane server.

[0128] The assistance information may include at least one of the following: an address of a user plane server; a unique identifier of the user plane server; a positioning service-related identifier; one or more fully qualified domain names (FQDNs) of the user plane server; secure user plane positioning assistance information for establishing a user plane connection in the second domain; or transport layer security assistance information for establishing a user plane connection in the second domain.

[0129] According to a fifteenth aspect, a device for a first network function located in a first domain is provided, the device comprising: a receiving circuit for receiving a positioning request for a user equipment located in the first domain; a determining circuit for determining that the user equipment has previously received a positioning service through a user plane via another domain; and a providing circuit for providing auxiliary information to the user equipment, the auxiliary information identifying a user plane server for providing positioning services to the user equipment through the user plane.

[0130] Determining that the user equipment has previously received positioning services over the user plane via another domain may be performed based on receiving a handover indication from the mobility management entity.

[0131] The providing circuitry for providing may comprise providing circuitry for providing the auxiliary information directly to the user equipment.

[0132] The providing circuitry for providing may comprise providing circuitry for providing the assistance information indirectly to the user equipment via at least one of: a positioning management function; or a positioning service user plane function.

[0133] The first network function may be an access and mobility function.

[0134] The auxiliary information may include address information of the user plane server.

[0135] The assistance information may include at least one of the following: an address of a user plane server; a unique identifier of the user plane server; a positioning service-related identifier; one or more fully qualified domain names (FQDNs) of the user plane server; secure user plane positioning assistance information for establishing a user plane connection in the second domain; or transport layer security assistance information for establishing a user plane connection in the second domain.

[0136] According to the sixteenth aspect, a device for a second network function located in a first domain is provided, the device comprising: a receiving circuit for receiving auxiliary information from the first network function located in the first domain, the auxiliary information identifying a user plane server for providing positioning services to a user equipment through a user plane of another domain; and a providing circuit for providing the auxiliary information to the user equipment.

[0137] The second network function may be at least one of the following: a positioning management function; or a positioning service user plane function.

[0138] The first network function may be an access and mobility function.

[0139] The auxiliary information may include address information of the user plane server.

[0140] The assistance information may include at least one of the following: an address of a user plane server; a unique identifier of the user plane server; a positioning service-related identifier; one or more fully qualified domain names (FQDNs) of the user plane server; secure user plane positioning assistance information for establishing a user plane connection in the second domain; or transport layer security assistance information for establishing a user plane connection in the second domain.

[0141] According to the seventeenth aspect, a non-transitory computer-readable medium is provided, comprising program instructions for causing an apparatus for a user equipment to execute: when the user equipment is located in a first domain, receiving auxiliary information from a first network function located in the first domain, the auxiliary information identifying a user plane server that provides positioning services for the user equipment through a user plane of another domain; and after performing a handover of the user equipment from the first domain to another domain, establishing a data connection with the user plane server based on the auxiliary information, for providing positioning services for the user equipment through a user plane of another domain.

[0142] The data connection may be a Packet Data Network (PDN) connection; and wherein the assistance information is used to reach a user plane server through the PDN connection.

[0143] The assistance information may be received before a command for said handover is sent to the user equipment.

[0144] The first domain may be configured as a 3rd Generation Partnership Project 3GPP 5G system 5GS; and wherein the other domain may be configured as a 3GPP Evolved Packet System EPS.

[0145] The assistance information may be received from the access and mobility function via non-access stratum NAS signaling.

[0146] The assistance information may be received within a downlink NAS transport message from the access and mobility function.

[0147] The assistance information may be received from the positioning management function via Long Term Evolution Positioning Protocol (LPP) signaling.

[0148] The assistance information may be received within the Location Services User Plane LCUP Assistance Information data from the Location Management Function.

[0149] The assistance information may be received from the location management function via secure user plane positioning SUPL signaling.

[0150] The assistance information may be received within a SUPL Initiation message from the Location Management Function.

[0151] The first network function may be an access and mobility function.

[0152] The first network function may be a positioning management function.

[0153] The first network function may be a positioning service user plane function.

[0154] The auxiliary information may include address information of the user plane server.

[0155] The assistance information may include at least one of the following: an address of a user plane server; a unique identifier of the user plane server; a positioning service-related identifier; one or more fully qualified domain names (FQDNs) of the user plane server; secure user plane positioning assistance information for establishing a user plane connection in the second domain; or transport layer security assistance information for establishing a user plane connection in the second domain.

[0156] According to an eighteenth aspect, a non-transitory computer-readable medium comprising program instructions is provided, which includes program instructions for causing an apparatus for a first network function located in a first domain to execute: determining that a user equipment receiving a positioning service through a user plane via the first domain is about to switch from the first domain to another domain; and providing auxiliary information to the user equipment, the auxiliary information identifying a user plane server for providing a positioning service to the user equipment through a user plane of another domain after the user equipment is switched to the second domain.

[0157] Determining that the user equipment is to be handed over may be performed based on receiving a handover indication from a mobility management entity.

[0158] Providing may include providing the assistance information directly to the user equipment.

[0159] Providing may include providing the assistance information indirectly to the user equipment via at least one of: a positioning management function; or a positioning service user plane function.

[0160] The first network function may be an access and mobility function.

[0161] The auxiliary information may include address information of the user plane server.

[0162] The assistance information may include at least one of the following: an address of a user plane server; a unique identifier of the user plane server; a positioning service-related identifier; one or more fully qualified domain names (FQDNs) of the user plane server; secure user plane positioning assistance information for establishing a user plane connection in the second domain; or transport layer security assistance information for establishing a user plane connection in the second domain.

[0163] According to the nineteenth aspect, a non-transitory computer-readable medium comprising program instructions is provided, which includes program instructions for causing an apparatus for a first network function located in a first domain to execute: receiving a positioning request regarding a user equipment located in the first domain; determining that the user equipment has previously received positioning services through a user plane via another domain; and providing auxiliary information to the user equipment, the auxiliary information identifying a user plane server for providing positioning services to the user equipment through the user plane.

[0164] Determining that the user equipment has previously received positioning services over the user plane via another domain may be performed based on receiving a handover indication from the mobility management entity.

[0165] Providing may include providing the assistance information directly to the user equipment.

[0166] Providing may include providing the assistance information indirectly to the user equipment via at least one of: a positioning management function; or a positioning service user plane function.

[0167] The first network function may be an access and mobility function.

[0168] The auxiliary information may include address information of the user plane server.

[0169] The assistance information may include at least one of the following: an address of a user plane server; a unique identifier of the user plane server; a positioning service-related identifier; one or more fully qualified domain names (FQDNs) of the user plane server; secure user plane positioning assistance information for establishing a user plane connection in the second domain; or transport layer security assistance information for establishing a user plane connection in the second domain.

[0170] According to the twentieth aspect, a non-transitory computer-readable medium comprising program instructions is provided, which includes program instructions for causing an apparatus for a second network function located in a first domain to execute: receiving auxiliary information from a first network function located in the first domain, the auxiliary information identifying a user plane server for providing positioning services to a user equipment through a user plane of another domain; and providing the auxiliary information to the user equipment.

[0171] The second network function may be at least one of the following: a positioning management function; or a positioning service user plane function.

[0172] The first network function may be an access and mobility function.

[0173] The auxiliary information may include address information of the user plane server.

[0174] The assistance information may include at least one of the following: an address of a user plane server; a unique identifier of the user plane server; a positioning service-related identifier; one or more fully qualified domain names (FQDNs) of the user plane server; secure user plane positioning assistance information for establishing a user plane connection in the second domain; or transport layer security assistance information for establishing a user plane connection in the second domain.

[0175] According to the twenty-first aspect, a method for a user equipment is provided, the method comprising: receiving auxiliary information from a first network function located in a first domain based on a previous indication that a user plane-based positioning service session for the user equipment is active in another domain, wherein the auxiliary information identifies a user plane server for providing positioning services to the user equipment through the user plane of the first domain; and after performing a handover of the user equipment from another domain to the first domain, establishing a data connection with the user plane server based on the auxiliary information for providing positioning services to the user equipment through the user plane of the first domain.

[0176] The data connection may be a Packet Data Network (PDN) connection; and wherein the assistance information is used to reach a user plane server through the PDN connection.

[0177] The assistance information may be received before a command for said handover is sent to the user equipment.

[0178] The first domain may be configured as a 3rd Generation Partnership Project 3GPP 5G system 5GS; and wherein the other domain may be configured as a 3GPP Evolved Packet System EPS.

[0179] The assistance information may be received from the access and mobility function via non-access stratum NAS signaling.

[0180] The assistance information may be received within a downlink NAS transport message from the access and mobility function.

[0181] The assistance information may be received from the positioning management function via Long Term Evolution Positioning Protocol (LPP) signaling.

[0182] The assistance information may be received within the Location Services User Plane LCUP Assistance Information data from the Location Management Function.

[0183] The assistance information may be received from the location management function via secure user plane positioning SUPL signaling.

[0184] The assistance information may be received within a SUPL Initiation message from the Location Management Function.

[0185] The first network function may be an access and mobility function.

[0186] The first network function may be a positioning management function.

[0187] The first network function may be a positioning service user plane function.

[0188] The auxiliary information may include address information of the user plane server.

[0189] The assistance information may include at least one of the following: an address of a user plane server; a unique identifier of the user plane server; a positioning service-related identifier; one or more fully qualified domain names (FQDNs) of the user plane server; secure user plane positioning assistance information for establishing a user plane connection in the second domain; or transport layer security assistance information for establishing a user plane connection in the second domain.

[0190] According to the twenty-second aspect, a device for a user equipment is provided, the device comprising a component for performing the following operations: based on a previous indication that a user plane-based positioning service session for the user equipment is active in another domain, receiving auxiliary information from a first network function located in a first domain, wherein the auxiliary information identifies a user plane server for providing positioning services to the user equipment through the user plane of the first domain; and after performing a handover of the user equipment from another domain to the first domain, establishing a data connection with the user plane server based on the auxiliary information for providing positioning services to the user equipment through the user plane of the first domain.

[0191] The data connection may be a Packet Data Network (PDN) connection; and wherein the assistance information is used to reach a user plane server through the PDN connection.

[0192] The assistance information may be received before a command for said handover is sent to the user equipment.

[0193] The first domain may be configured as a 3rd Generation Partnership Project 3GPP 5G system 5GS; and wherein the other domain may be configured as a 3GPP Evolved Packet System EPS.

[0194] The assistance information may be received from the access and mobility function via non-access stratum NAS signaling.

[0195] The assistance information may be received within a downlink NAS transport message from the access and mobility function.

[0196] The assistance information may be received from the positioning management function via Long Term Evolution Positioning Protocol (LPP) signaling.

[0197] The assistance information may be received within the Location Services User Plane LCUP Assistance Information data from the Location Management Function.

[0198] The assistance information may be received from the location management function via secure user plane positioning SUPL signaling.

[0199] The assistance information may be received within a SUPL Initiation message from the Location Management Function.

[0200] The first network function may be an access and mobility function.

[0201] The first network function may be a positioning management function.

[0202] The first network function may be a positioning service user plane function.

[0203] The auxiliary information may include address information of the user plane server.

[0204] The assistance information may include at least one of the following: an address of a user plane server; a unique identifier of the user plane server; a positioning service-related identifier; one or more fully qualified domain names (FQDNs) of the user plane server; secure user plane positioning assistance information for establishing a user plane connection in the second domain; or transport layer security assistance information for establishing a user plane connection in the second domain.

[0205] According to the twenty-third aspect, a device for a user equipment is provided, the device comprising: at least one processor; and at least one memory comprising code, which, when executed by the at least one processor, causes the device to perform: based on a previous indication that a user plane-based positioning service session for the user equipment is active in another domain, receiving auxiliary information from a first network function located in a first domain, wherein the auxiliary information identifies a user plane server for providing positioning services to the user equipment through the user plane of the first domain; and after performing a handover of the user equipment from another domain to the first domain, establishing a data connection with the user plane server based on the auxiliary information for providing positioning services to the user equipment through the user plane of the first domain.

[0206] The data connection may be a Packet Data Network (PDN) connection; and wherein the assistance information is used to reach a user plane server through the PDN connection.

[0207] The assistance information may be received before a command for said handover is sent to the user equipment.

[0208] The first domain may be configured as a 3rd Generation Partnership Project 3GPP 5G system 5GS; and wherein the other domain may be configured as a 3GPP Evolved Packet System EPS.

[0209] The assistance information may be received from the access and mobility function via non-access stratum NAS signaling.

[0210] The assistance information may be received within a downlink NAS transport message from the access and mobility function.

[0211] The assistance information may be received from the positioning management function via Long Term Evolution Positioning Protocol (LPP) signaling.

[0212] The assistance information may be received within the Location Services User Plane LCUP Assistance Information data from the Location Management Function.

[0213] The assistance information may be received from the location management function via secure user plane positioning SUPL signaling.

[0214] The assistance information may be received within a SUPL Initiation message from the Location Management Function.

[0215] The first network function may be an access and mobility function.

[0216] The first network function may be a positioning management function.

[0217] The first network function may be a positioning service user plane function.

[0218] The auxiliary information may include address information of the user plane server.

[0219] The assistance information may include at least one of the following: an address of a user plane server; a unique identifier of the user plane server; a positioning service-related identifier; one or more fully qualified domain names (FQDNs) of the user plane server; secure user plane positioning assistance information for establishing a user plane connection in the second domain; or transport layer security assistance information for establishing a user plane connection in the second domain.

[0220] According to the twenty-fourth aspect, a device for a user equipment is provided, the device comprising: a receiving circuit for receiving auxiliary information from a first network function located in a first domain based on a previous indication that a user plane-based positioning service session for the user equipment is active in another domain, wherein the auxiliary information identifies a user plane server for providing positioning services to the user equipment through the user plane of the first domain; and an establishing circuit for establishing a data connection with the user plane server based on the auxiliary information after performing a handover of the user equipment from another domain to the first domain, for providing positioning services to the user equipment through the user plane of the first domain.

[0221] The data connection may be a Packet Data Network (PDN) connection; and wherein the assistance information is used to reach a user plane server through the PDN connection.

[0222] The assistance information may be received before a command for said handover is sent to the user equipment.

[0223] The first domain may be configured as a 3rd Generation Partnership Project 3GPP 5G system 5GS; and wherein the other domain may be configured as a 3GPP Evolved Packet System EPS.

[0224] The assistance information may be received from the access and mobility function via non-access stratum NAS signaling.

[0225] The assistance information may be received within a downlink NAS transport message from the access and mobility function.

[0226] The assistance information may be received from the positioning management function via Long Term Evolution Positioning Protocol (LPP) signaling.

[0227] The assistance information may be received within the Location Services User Plane LCUP Assistance Information data from the Location Management Function.

[0228] The assistance information may be received from the location management function via secure user plane positioning SUPL signaling.

[0229] The assistance information may be received within a SUPL Initiation message from the Location Management Function.

[0230] The first network function may be an access and mobility function.

[0231] The first network function may be a positioning management function.

[0232] The first network function may be a positioning service user plane function.

[0233] The auxiliary information may include address information of the user plane server.

[0234] The assistance information may include at least one of the following: an address of a user plane server; a unique identifier of the user plane server; a positioning service-related identifier; one or more fully qualified domain names (FQDNs) of the user plane server; secure user plane positioning assistance information for establishing a user plane connection in the second domain; or transport layer security assistance information for establishing a user plane connection in the second domain.

[0235] According to the twenty-fifth aspect, a non-transitory computer-readable medium is provided, comprising program instructions for causing an apparatus for a user equipment to execute: based on a previous indication that a user plane-based positioning service session for the user equipment is active in another domain, receiving auxiliary information from a first network function located in a first domain, wherein the auxiliary information identifies a user plane server for providing positioning services to the user equipment through the user plane of the first domain; and after performing a handover of the user equipment from another domain to the first domain, establishing a data connection with the user plane server based on the auxiliary information for providing positioning services to the user equipment through the user plane of the first domain.

[0236] The data connection may be a Packet Data Network (PDN) connection; and wherein the assistance information is used to reach a user plane server through the PDN connection.

[0237] The assistance information may be received before a command for said handover is sent to the user equipment.

[0238] The first domain may be configured as a 3rd Generation Partnership Project 3GPP 5G system 5GS; and wherein the other domain may be configured as a 3GPP Evolved Packet System EPS.

[0239] The assistance information may be received from the access and mobility function via non-access stratum NAS signaling.

[0240] The assistance information may be received within a downlink NAS transport message from the access and mobility function.

[0241] The assistance information may be received from the positioning management function via Long Term Evolution Positioning Protocol (LPP) signaling.

[0242] The assistance information may be received within the Location Services User Plane LCUP Assistance Information data from the Location Management Function.

[0243] The assistance information may be received from the location management function via secure user plane positioning SUPL signaling.

[0244] The assistance information may be received within a SUPL Initiation message from the Location Management Function.

[0245] The first network function may be an access and mobility function.

[0246] The first network function may be a positioning management function.

[0247] The first network function may be a positioning service user plane function.

[0248] The auxiliary information may include address information of the user plane server.

[0249] The assistance information may include at least one of the following: an address of a user plane server; a unique identifier of the user plane server; a positioning service-related identifier; one or more fully qualified domain names (FQDNs) of the user plane server; secure user plane positioning assistance information for establishing a user plane connection in the second domain; or transport layer security assistance information for establishing a user plane connection in the second domain.

[0250] According to a twenty-sixth aspect, there is provided a computer program product stored on a medium, which can cause an apparatus to perform any method as described herein.

[0251] According to a twenty-seventh aspect, there is provided an electronic device, which may comprise the apparatus as described herein.

[0252] According to a twenty-ninth aspect, there is provided a chipset, which may include the apparatus as described herein. BRIEF DESCRIPTION OF THE DRAWINGS

[0253] Some examples will now be described, by way of illustration only, with reference to the accompanying drawings, in which:

[0254] Figure 1A and 1B A schematic representation of a 5G system is shown;

[0255] Figure 2 shows a schematic representation of a network device;

[0256] Figure 3 A schematic representation of a user equipment is shown;

[0257] Figure 4 A schematic representation of a non-volatile storage medium storing instructions that, when executed by a processor, allow the processor to perform one or more steps of some example methods is shown;

[0258] Figure 5 shows a schematic representation of a network;

[0259] Figures 6A to 6B shows example signaling;

[0260] Figures 7A to 7B shows example signaling;

[0261] Figures 8 to 12 illustrates example operations that may be performed by the apparatus described herein; and

[0262] 13 and 14 illustrate example signaling. DETAILED DESCRIPTION

[0263] For the sake of brevity and clarity, these aspects are described below with reference to 5G wireless communication systems and Evolved Packet System (EPS). However, it will be appreciated that these aspects are not limited to these wireless communication systems and may, for example, be applied to other wireless communication systems (e.g., current 6G proposals, IEEE 802.11, etc.).

[0264] Before describing the examples in detail, refer to Figure 1A and Figure 1B Some general principles of 5G wireless communication systems are briefly described.

[0265] Figure 1AA schematic representation of a 5G system (5GS) 100 is shown. The 5GS may include a user equipment (UE) 102 (which may also be referred to as a communication device or terminal), a 5G access network (AN) (which may be a 5G radio access network (RAN) or any other type of 5G AN, such as a non-3GPP interworking function (N3IWF) / trusted non-3GPP gateway function (TNGF) for non-trusted / trusted non-3GPP access or a wired access gateway function (W-AGF) for wired access) 104, a 5G core (5GC) 106, one or more application functions (AF) 108, and one or more data networks (DN) 110.

[0266] A 5G RAN may include one or more gNodeB (gNB) distributed unit functions connected to one or more gNodeB (gNB) unit functions. A RAN may include one or more access nodes.

[0267] 5GC 106 may include one or more access and mobility management functions (AMF) 112, one or more session management functions (SMF) 114, one or more authentication server functions (AUSF) 116, one or more unified data management (UDM) functions 118, one or more user plane functions (UPF) 120, one or more unified data repository (UDR) functions 122, one or more network repository functions (NRF) 128, and / or one or more network open functions (NEF) 124. The role of NEF is to provide a secure opening of network services (e.g., voice, data connection, billing, user data, etc.) to third parties. Although NRF 128 does not show its interface, it will be understood that this is for clarity reasons and that NRF 128 may have multiple interfaces with other network functions.

[0268] The 5GC 106 also includes a network data analysis function (NWDAF) 126. The NWDAF is responsible for providing network analysis information based on requests from one or more network functions or devices within the network. The network functions may also subscribe to the NWDAF 126 to receive information from it. Thus, the NWDAF 126 is also configured to receive and store network information from one or more network functions or devices within the network. Data collection by the NWDAF 126 may be performed based on at least one subscription to an event provided by at least one network function.

[0269] The network may further include a management data analysis service (MDAS) producer or an MDAS management service (MnS) producer. The MDAS MnS producer may provide data analysis in the management plane, taking into account parameters such as load level and / or resource utilization. For example, an MDAS MnS producer of a network function (NF) may collect load-related performance data of the NF, such as the resource usage status of the NF. Analysis of the collected data may provide a prediction of resource usage information in a predefined future time window. The analysis may also suggest appropriate actions, such as scaling of resources, admission control, load balancing of services, etc.

[0270] Figure 1B A schematic representation of a 5GC as represented in the current 3GPP specification is shown. It will be understood that this architecture is intended to illustrate potential components that may be included in a core network, and the principles described so far are not limited to a core network comprising only the described components.

[0271] Figure 1B A 5GC 106' is shown, which includes a UPF 120' connected to an SMF 114' via an N4 interface. The SMF 114' is connected to each of the UDM 122', NEF 124', NWDAF 126', AF 108', Policy Control Function (PCF) 130', AMF 112', and Charging Function 132' via an interconnect medium, which also connects these network functions to each other. The 5G Core 106' further includes a Network Repository Function (NRF) 133' and a Network Function 134' connected to the interconnect medium.

[0272] 3GPP has released several releases (Rel) for defining operational communication protocols related to communication networks. Certain goals and work are set with respect to Release 18 (Rel. 18).

[0273] Another example network is the Evolved Packet System (EPS). The UE communicates with the Evolved Packet Core (EPC) via a base station (eg, eNB), which can send signals to the Serving Gateway (SGW) and the Mobility Management Entity (MME).

[0274] The MME is a key control node for the LTE access network. The MME is involved in the bearer activation / deactivation process and is also responsible for selecting a serving gateway for the UE at initial attach and intra-LTE handover involving Core Network (CN) node relocation.

[0275] The SGW routes and forwards user data packets while also acting as the mobility anchor point for the user plane during inter-eNB handovers and as the anchor point for mobility between LTE and other 3GPP technologies.

[0276] 3GPP is studying use cases, technical requirements and corresponding enhancements as part of the ongoing Rel-18 enhancements. At least one of these key issues involves how to support location service continuity given the mobility of the UE.

[0277] 3GPP defines the handling of ongoing services / sessions during mobility for certain use cases, such as, for example, voice calls or data sessions. In particular, the handling of location services (LCS) during mobility procedures is defined in the 3GPP standard with respect to control plane procedures. Certain proposals have considered providing LCS sessions over the user plane for providing positioning services. However, it has not yet been studied how such user plane LCS sessions will be affected as a result of a UE switching from a first network domain to a second network domain. Therefore, it is not clear whether an ongoing LCS session over the user plane should be terminated or maintained after a mobility-based event. Furthermore, it is not defined how such continuity will work if the LCS session continues.

[0278] There are a variety of impacts associated with this.

[0279] For example, an LCS session may be terminated in response to a mobility event. In this case, the LCS client must re-initiate the session after the process. This introduces additional network signaling, which for some use cases may be considered an inefficient use of overhead resources.

[0280] Furthermore, the Location Management Function (LMF) may not be aware of mobility based events at all. This may result in inaccurate location estimates being obtained for mobile UEs.

[0281] Furthermore, since there is no clear specification, inter-vendor testing may fail when network functions from different vendors make different assumptions about whether another network function supports continuity of LCS sessions. For example, the AMF from vendor 1 may operate with the expectation that continuity should work, while the LMF from vendor 2 may not support continuity.

[0282] Furthermore, LCS sessions may be enabled as part of other critical services such as, for example, emergency calls. Due to the lack of certainty, these critical services may be affected, leading to regulatory issues.

[0283] The present application has determined that at least one of the above problems may be alleviated by providing a mechanism for handling LCS sessions for different mobility procedures in the user plane. In particular, the present application has determined that it may be useful to specify how LCS session continuity may be provided in the case of mobility based events.

[0284] The following provides example signaling that can be performed by the entities described herein. By way of illustrative example, these signalings are discussed in the context of an Evolved Packet System (EPS) and a 5G System (5GS).

[0285] Fig. 6A and Figure 6B Figure 1 shows example signaling that may be performed when a UE moves from a 5GS to an Evolved Packet System. Fig. 6A Execute after the operation Figure 6B operation.

[0286] Fig. 6A and Figure 6B Signaling is shown that can be performed between: UE 601, Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) 602, Next Generation Radio Access Network (NG_RAN) 603, MME 604, AMF 605, Evolved Serving Mobile Positioning Center (E_SMLC) 606 (which is a positioning function located in EPS), Positioning Management Function Positioning Service User Plane (LMF_LCUP) 607, Gateway Mobile Positioning Center (GMLC) 608, and LCS Client 609.

[0287] LMF_LCUP refers to the LCS service function implemented by LMF, however it will be understood that the present description is not limited thereto. The term "LCUP" used herein may refer to a network element or network function for location services on a user plane, which may, for example, correspond to the user plane portion of the LMF or the secure user plane location (SUPL) platform defined in the Open Mobile Alliance (OMA) specification. The LCUP function may handle location operations on the user plane and may be used together with an associated LMF, for example, to enhance location services on the control plane. The LMF and the associated LCUP may be located in the same area (e.g., co-located with each other), or may communicate via an interface or implement specific behavior. Additionally or alternatively, the LMF and the associated LCUP may also support similar location methods so that they may match each other.

[0288] The Gateway Mobile Location Center (GMLC) includes the functionality required to support location-based services (LBS). In a Global System for Mobile Communications (GSM), UMTS, or LTE network, the GMLC is the first node accessed by an external LBS client. The GMLC can request routing information from the Home Location Register (HLR) or the Home Subscriber Server (HSS). After performing registration authorization, it sends a location request to the Visited Mobile Switching Center (VMSC), SGSN Serving GPRS Support Node (SGSN), or Mobile Switching Center (MSC) server and receives the final location estimate from the corresponding entity.

[0289] During 6001, an LCS session is established for UE 601 via the 5G user plane.

[0290] During 6002, the NG_RAN 603 determines that a handover is to be performed for handing over the UE 601 from the 5GS to the EPS. The determination may be performed based on any of a number of factors. For example, the determination may be made based on (e.g., in response to) determining that the UE 601 may obtain better quality of service and / or quality of experience with other networks.

[0291] During 6003, based on the determination of 6002, NG_RAN 603 sends a signal to AMF 605. This signaling of 6003 may request to switch UE 601 from 5GS to EPS.

[0292] During 6004, based on the signaling of 6003, AMF 605 signals MME 604 a relocation request regarding UE 601. The relocation request indicates that UE 601 is to be switched from 5GS to EPS.

[0293] During 6005, MME 604 responds to the signaling of 6004. The signaling of 6005 may include a relocation response.

[0294] During 6006, the AMF 605 determines that a user plane LCS session is active for the UE 601. The AMF 605 may determine that a given UE has an active LCS session when the AMF 605 has previously requested the LMF to provide positioning for the UE 601. The positioning request may provide an LCS related identifier to the AMF. In addition, the AMF 605 may determine that a given UE has an active LCS session when the LMF signals information (which may be forwarded to the radio access network and / or the UE) to the AMF 605 including the same LCS related identifier that the AMF 601 had previously sent. This may allow the AMF 605 to remain aware of whether a user plane LCS session is active for the UE 601.

[0295] Based on this determination, the AMF 605 may determine to provide information related to LCS user plane assistance for the UE (such as, for example, Internet Protocol (IP address or FQDN)) to the UE 601. Examples of the assistance information are provided further below. The assistance information may be signaled to the UE in any of a number of different ways.

[0296] For example, the AMF 605 may provide the assistance information to the UE 601 by directly signaling the assistance information to the UE 601 using a non-access stratum (NAS) signaling procedure. Fig. 6A6007. The example signaling of 6007 may be implemented by signaling LCUP assistance data to UE 601.

[0297] The LCUP assistance information may be received in a number of different ways. In some examples, the assistance data may be signaled using a NAS:DL-NAS-Transport service operation.

[0298] As another example, the AMF 605 may signal the assistance information indirectly to the UE 601 via the LMF_LCUP 607. This is shown with respect to 6008a-6009a and with respect to 6008b-6009b, both of which are further described below.

[0299] 6008a-6009a show example information where the AMF 605 provides assistance information indirectly to the UE 601 via the LMF_LCUP 607 and the LMF_LCUP 607 uses the LPP to signal the assistance information to the UE.

[0300] During 6008a, the AMF 605 sends a signal to the LMF_LCUP 607. The LMF_LCUP 607 may signal the assistance information to the UE 601 based on the signal from the AMF 605 in 6008a. The signal may, for example, trigger the LMF_LCUP 607 to signal the assistance information to the UE 601. The signaling of 6008a may include a Nlmf_Location_Prepare_Transfer service operation.

[0301] During 6009a, LMF_LCUP 607 sends a signal to UE 601. The signaling may include the LCUP assistance data mentioned above. The signaling may be implemented using LPP service operations.

[0302] 6008b-6009b show example information where the AMF 605 provides assistance information indirectly to the UE 601 via the LMF_LCUP 607 and the LMF_LCUP 607 signals the assistance information to the UE using SUPL.

[0303] During 6008b, the AMF 605 signals the LMF_LCUP 607. The LMF_LCUP 607 may signal the assistance information to the UE 601 based on the signal from the AMF 605 in 6008b. The signal may, for example, trigger the LMF_LCUP 607 to signal the assistance information to the UE 601. The signaling of 6008b may include a Nlmf_Location_Prepare_Transfer service operation.

[0304] During 6009b, LMF_LCUP 607 sends a signal to UE 601. The signaling may include SUPL-INIT service operations.

[0305] Having provided the auxiliary information to the UE via at least one of 6007 to 6009b, during 6010, the AMF 605 signals a handover command regarding the UE 601 to the NG_RAN 603. The handover command may indicate that the UE 601 is to be handed over from 5GS to EPS. The handover command may be signaled using HO_Command signaling.

[0306] During 6011, the E-UTRAN network 602 signals an indication to the MME 604 that the UE 601 has been handed over to the E-UTRAN network. This may be signaled using the HO_Notify service operation.

[0307] During 6012, after the handover of UE 601 to EPS has been completed, UE 601 uses the PDN connection corresponding to the PDU session it used on 5GS to connect to the user plane positioning server interface to contact the user plane positioning server whose address was provided to the UE during 6007, 6009a and / or 6009b.

[0308] 6013 to 6014 relate to AMF 605 cancelling a previously configured LCS session in 5GS.

[0309] During 6013, AMF 605 sends a signal to LMF_LCUP 607. This signaling of 6013 indicates that the location service session is to be cancelled in 5GS. This signaling can be implemented using, for example, the Nlmf_Location_CancelLocation_Request service mechanism.

[0310] During 6014, the user plane LCS session is canceled.

[0311] During 6015, the AMF 605 sends a signal to the GMLC 608. The signaling of 6015 may provide an indication to the GMLC 608 that the UE 601 has been handed over from 5GS to EPS. The signaling of 6015 may additionally provide the GMLC 608 with an identifier of the UE 601, an indication that the LCS session has failed, and / or an identifier of the MME 604. The signaling of 6015 may be implemented using, for example, a Namf_Location_ProvidePositioningInfo Resp service operation.

[0312] 6016 and 6017 involve requesting an entity on the EPS to provide a positioning element for UE 601.

[0313] During 6016, the GMLC 608 sends a signal to the MME 604. The signaling of 6016 may request the MME 604 to provide the GMLC 608 with a positioning estimate for the positioning of the UE 601. The signaling may include an identifier of the UE 601 (such as the identifier provided during 6015). The signaling may include an indication of the quality of service (QoS) associated with the requested LCS. The indication of the quality of service (QoS) and the UE identity sent to the MME may correspond to the EPS conversion of the parameters sent to the AMF.

[0314] During 6017, MME 604 sends a signal to E_SMLC 606. The signaling may include a request for positioning of UE 601. The signaling of 6017 may include an identifier of UE 601 provided during 6016. The signaling of 6017 may include the QoS included in the signaling of 6016.

[0315] During 6018, an LCS session is established through the EPC user plane. In particular, given the PDN connection to the user plane server, the E-SMLC 606 chooses to use the user plane data for the LCS session. During 6018 on the EPS side, OMA-SUPL (not shown) may also be involved. It is assumed that the process of 6018 provides the E_SMLC 606 with a positioning estimate for the UE 601.

[0316] During 6019, the E-SMLC 606 sends a signal to the MME 604. The signaling provides the MME 604 with a positioning estimate for the UE 601. The signaling may include the identifier of the UE 601 provided during 6017.

[0317] During 6020, MME 604 sends a signal to GMLC 608. The signaling of 6020 may include the positioning estimate of 6019. The signaling of 6020 may include an identifier of UE 601.

[0318] During 6021, the GMLC 608 sends a signal to the LCS client 609. The signaling of 6021 may include the positioning estimate of 6020. The signaling of 6021 may include an identifier of the UE 601.

[0319] The positioning estimation discussed above may be as specified in the EPS specification. For example, providing the information of 6007 to 6009b (including 6007 and 6009b) to the UE may not affect how subsequent positioning is provided via EPS. In addition, the LCS client is unaware of any UE mobility processing, and LCS session continuity is maintained.

[0320] However, SUPL may be indicated for both the EPS side and the 5GS side for enabling reuse of user plane sessions, which simplifies signaling in the UE and the 5G Core.

[0321] The assistance information described above may include: an identifier and / or address of a user plane server for the UE (e.g., an IP address and / or a fully qualified domain name (FQDN) of the user plane server / LCUP / LMF_LCUP); and / or assistance data for assisting in establishing a secure (e.g., TLS) connection between the UE and the (positioning) user plane server; and / or assistance data for assisting in signaling between the UE and the (positioning) user plane server. For example, when the UE is in 5GS, the assistance information provides the UE with information to be used when the UE is in EPS.

[0322] The LCUP instance assistance information may alternatively or additionally include security information for establishing a user plane (UP) session between a terminal device and an LCUP function instance (e.g., LMF_LCUP). The security information may include security material that the UE can use to establish a user plane session between the UE and the LCUP. In some examples, the security information may include transport layer security (e.g., TLS) attribute information for establishing a protected user plane connection. The TLS attribute information may, for example, correspond to a key that will be used as a pre-shared key to protect a TLS link between the UE and the LCUP. It can be used to establish an SSL / TLS connection between the UE and the LCUP. In some examples, the security information may further include a hash-based message authentication code field, for example, when the UE wants to start a session via a SUPL position initialization (POS INIT) message to initiate a positioning protocol session.

[0323] In some examples, the LCUP instance assistance information may alternatively or additionally include relevant information about an ongoing control plane positioning process. The relevant information includes information for associating the ongoing control plane positioning process with the user plane connection to further ensure the security of the user plane connection. A network element such as an LMF may allocate a relevant identifier as relevant information for a positioning request, which may include, for example, an LMF address and a positioning request identifier. The LMF may provide the relevant identifier as part of the LCUP assistance information to the terminal device through the control plane, for example via LTE Positioning Protocol (LPP) signaling. In subsequent operations to establish a user plane connection between the terminal device and the LUCP, the relevant identifier may be used to associate the ongoing control plane positioning process with the user plane connection, which will be described below.

[0324] The LCUP assistance information may further include information about ports at the LCUP function instance, such as a Transmission Control Protocol (TCP) or a Unified Datagram Protocol (UDP) port at the LCUP. Additionally or alternatively, the LCUP assistance information may also include information about positioning methods or protocols supported by the LCUP function instance.

[0325] The UE may store the received assistance information and, after the user equipment is handed over to EPS, initiate a PDN connection or use the PDU session handed over to EPS as a PDN connection in order to contact the (positioning) user plane server for which it has received its contact information in the assistance data address / identifier. When the FQDN is provided in the assistance data, the UE may initiate a domain name service (DNS) query to the DNS server for obtaining the address of the user plane server. Once on LTE, the UE then autonomously establishes such a connection to the user plane server (e.g., without receiving a trigger from the LTE / EPS network). This may ensure that there is no impact on the LTE network in certain use cases.

[0326] The UE may further perform signaling to establish a TLS connection on top of the user plane connection. The UE may further perform signaling in SUPL to ensure that the SUPL connection is ready for the eSMLC to establish an LCS session on top of the SUPL, TLS, and IP protocol layers.

[0327] Fig. 7A and Figure 7B It shows how the presently described techniques can be applied in the case where a user equipment moves from EPS to 5GS. Fig. 7A Execute after the operation Figure 7B operation.

[0328] Fig. 7A and Figure 7B Signaling that may be performed by: UE 701, E-UTRAN 702, NG-RAN 703, AMF 704, E_SMLC 705, LMF_LCUP 706, NRF 707, MNE 708, GMLC 709, and LCS Client 710 is shown.

[0329] During 7001, an LCS session is established through the user plane of EPS.

[0330] During 7002, E-UTRAN 702 determines that the UE is to be handed over from EPS to 5GS.

[0331] During 7003, based on the determination of 7002, E-UTRAN 703 sends a signal to MME 708. This signaling of 7003 indicates a request for handover for handing over the UE from EPS to 5GS.

[0332] During 7004, E-UTRAN 702 detects a LCS user plane session currently established with respect to UE 701. The LCS user plane session is detected by E-UTRAN 702 monitoring usage of an LCS-related identifier associated with UE 701 signaled via E-UTRAN 702.

[0333] During 7005, the MME 708 sends a signal to the AMF 704. The signaling of 7005 includes an indication that the UE 701 will switch from the EPS to the 5GS. The signaling of 7005 includes an indication that the UE 701 has an existing user-plane-based LCS session active in the EPS. As described above, the AMF 605 can know that there is an ongoing active LCS session for a given UE on the 5GS based on the receipt of the positioning service-related identifier. In this example, the MME 708 can also know that there is an active LCS session for the UE 701 by receiving and / or sending signaling including a similar related identifier. Therefore, the MME 708 can know the LCS session status without sending specified signaling to the MME 708 for this purpose. For example, the LCS user plane session is detected by the MME 708 monitoring the use of the LCS-related identifier associated with the UE 701 that is signaled via the MME 708.

[0334] During 7006, MME 708 responds to the signaling of 7005.

[0335] During 7007, MME 708 sends a signal to E-UTRAN 702. The signaling may include a handover command for E-UTRAN to handover UE 701 to NG_RAN 702.

[0336] During 7008, NG_RAN 703 sends a signal to AMF 704. The signaling may inform the AMF that handover of UE 701 to NG-RAN has been performed.

[0337] 7009 to 7012 involve canceling the LCS session in the EPS network.

[0338] During 7009, MME 708 sends a signal to E_SMLC 705. The signaling of 7009 includes an instruction to cancel the LCS session in the EPS network.

[0339] During 7010, the user plane LCS session is canceled in the EPS network.

[0340] During 7011, the MME 708 sends a signal to the GMLC 709. The signaling of 7011 may include a positioning response. The signaling of 7011 may include an identifier of the UE 701. The signaling of 7011 may include a failure indication. The signaling of 7011 may include an indication that a handover to 5GS has been performed. The signaling of 7011 may include an address of the AMF 704 (or some other identifier that may be used to obtain an address for the address of the AMF 704).

[0341] During 7012, the GMLC 709 signals the AMF 704 identifier in signaling at 7011. The signaling at 7012 may request positioning of the UE 701. The signaling at 7012 may include the identifier of the UE 701 provided during 7011. The signaling at 7012 may include an indication of the quality of service of the LCS session.

[0342] During 7013, AMF 704 determines whether AMF 704 has previously received information about the LCS session through the user plane. For example, AMF 704 determines whether AMF 704 has previously received signaling 7005 from MME 708.

[0343] Based on AMF 704 determining that AMF has previously received the LCS session information, AMF 704 provides the address of the LCS user plane server to UE 701. This provision may be implemented via 7014, and / or via 7015a and 7016a, and / or via 7015b and 7016b. These operations are further described below.

[0344] During 7014, AMF 704 sends a signal to UE 701. The signaling of 7014 may include LCUP assistance data. The LCUP assistance data may be as described above with respect to Fig. 6A and Figure 6B described.

[0345] During 7015a, the AMF 704 sends a signal to the LMF_LCUP 706. The signaling of 7015a may include a request for the LMF_LCUP to provide LCUP assistance data to the UE 701. The signaling of 7015a may include an identifier of the UE 701. The signaling of 7015a may include an LCS-related identifier associated with the UE 701. The signaling of 7015a may include an indication of the QoS of the LCS session received during 7012. The signaling of 7015a may include an indication that the UE 701 has an associated user plane LCS session.

[0346] During 7016a, LMF_LCUP 706 sends a signal to UE 701. This signaling of 7016a provides LCUP assistance data to UE 701. This signaling of 7016a may be provided using LPP.

[0347] During 7015b, the AMF 704 sends a signal to the LMF_LCUP 706. The signaling of 7015b may include a request for the LMF_LCUP to provide LCUP assistance data to the UE 701. The signaling of 7015b may include an identifier of the UE 701. The signaling of 7015b may include an LCS-related identifier associated with the UE 701. The signaling of 7015b may include an indication of the QoS of the LCS session received during 7012. The signaling of 7015b may include an indication that the UE 701 has an associated user plane LCS session.

[0348] During 7016b, LMF_LCUP 706 sends a signal to UE 701. This signaling of 7016b provides LCUP assistance data to UE 701. This signaling of 7016b may be provided using OMA-SUPL.

[0349] During 7017, a user plane LCS session is established through 5GS.

[0350] During 7018, LMF_LCUP 706 sends a signal to AMF 704. The signaling of 7018 may include a location estimate for UE 701. The signaling of 7018 may include an identifier of UE 701. The signaling of 7018 may include an LCS-related identifier of 7016a or 7016b. The signaling of 7018 may include an Nlmf_Location_DetermineLocationResponse service operation. The signaling of 7018 may be signaled based on the signaling of 7015.

[0351] During 7019, the AMF 704 sends a signal to the GLMC 709. The signaling may include the positioning estimate provided in 7018. The signaling may include the identifier of the UE 701 provided in the signaling of 7018. The signaling of 7019 may include a Namf_Location_ProvidePositionInfo Respons service operation.

[0352] During 7020, the GMLC 709 sends a signal to the LCS client 710. The signaling of 7020 may include the positioning estimate provided in 7019. The signaling may include the identifier of the UE 701 provided in the signaling of 7019.

[0353] exist Fig. 7A and Figure 7B In this example, the LMF may select to conduct the LCS session over the user plane based on the receipt of the indication from the AMF. The LMF may alternatively or additionally select to conduct the LCS session over the user plane based on the internal configuration of the LMF.

[0354] exist FIG. 6A to FIG. 6B and FIG. 7A to FIG. 7B In both of the above examples, the user plane connection from the UE is handled just like other packet data unit (PDU) sessions to assist in keeping the LCS active over the user plane session during mobility.

[0355] However, SUPL is indicated for both EPS side and 5GS side to enable reuse, thereby simplifying signaling in UE and 5G Core.

[0356] The assistance information described above may include: an identifier and / or address of the UE's user plane server (e.g., an IP address and / or a fully qualified domain name (FQDN) of the user plane server); and / or assistance data for assisting in establishing a protected (e.g., TLS) connection between the UE and the user plane (positioning) server; and / or assistance data for assisting in signaling between the UE and the (positioning) user plane server. In some examples, the assistance information provides the UE with information to be used when the UE is in 5GS.

[0357] The assistance information described above may include at least one of the following: an identifier and / or address of the UE's user plane server (e.g., an IP address and / or a fully qualified domain name (FQDN) of the user plane server); and / or assistance data for assisting in establishing a protected (e.g., TLS) connection between the UE and the (positioning) user plane server; and / or assistance data for assisting in signaling between the UE and the (positioning) user plane server. In some examples, when the UE is in 5GS, the assistance information provides the UE with information to be used when the UE is in EPS.

[0358] The LCUP instance assistance information may alternatively or additionally include security information for establishing a user plane (UP) session between the terminal device and the LCUP function instance. The security information may include security material that the UE can use to establish a user plane session between the UE and the LCUP. In some examples, the security information may include transport layer security (e.g., TLS) attribute information for establishing a protected user plane connection. The TLS attribute information may, for example, correspond to a key that will be used as a pre-shared key to protect a TLS link between the UE and the LCUP. It can be used to establish an SSL / TLS connection between the UE and the LCUP. In some examples, the security information may further include a hash-based message authentication code field, for example, when the UE wants to start a session via a SUPL position initialization (POS INIT) message to initiate a positioning protocol session.

[0359] In some examples, the LCUP instance assistance information may alternatively or additionally include relevant information about an ongoing control plane positioning process. The relevant information includes information for associating the ongoing control plane positioning process with the user plane connection to further ensure the security of the user plane connection. A network element such as an LMF may allocate a relevant identifier as relevant information for a positioning request, which may include, for example, an LMF address and a positioning request identifier. The LMF may provide the relevant identifier as part of the LCUP assistance information to the terminal device through the control plane, for example via LTE Positioning Protocol (LPP) signaling. In subsequent operations to establish a user plane connection between the terminal device and the LUCP, the relevant identifier may be used to associate the ongoing control plane positioning process with the user plane connection, which will be described below.

[0360] The LCUP assistance information may further include information about ports at the LCUP function instance, such as a Transmission Control Protocol (TCP) or a Unified Datagram Protocol (UDP) port at the LCUP. Additionally or alternatively, the LCUP assistance information may also include information about positioning methods or protocols supported by the LCUP function instance.

[0361] The UE may store the received assistance information and initiate a PDN connection to the receiver user plane address / identifier after the user equipment is handed over to EPS. When the FQDN is provided, the UE may initiate a Domain Name Service (DNS) query to the DNS server for obtaining the address of the user plane server. Once on LTE, the UE then autonomously establishes such a connection to the user plane server (e.g., without receiving a trigger from the LTE / EPS network). This will ensure that there is no impact on the LTE network.

[0362] Figures 8 to 12 Shows 6A to 7B Aspects of the above examples.

[0363] Figure 8 Relates to operations that can be performed by a user device.

[0364] During 801, when the user equipment is located in a first domain, the user equipment receives assistance information from a first network function located in the first domain, the assistance information identifying a user plane server providing a positioning service for the user equipment through a user plane of another domain.

[0365] During 802, after performing handover of the user equipment from the first domain to another domain, the user equipment establishes a data connection with a user plane server based on the auxiliary information, so as to provide positioning services for the user equipment through a user plane of another domain.

[0366] These operations may be performed when a user device is handed over from a first domain to another domain.

[0367] The data connection may be a Packet Data Network (PDN) connection; and wherein the assistance information is used to reach a user plane server through the PDN connection.

[0368] The assistance information may be received before a command for the handover is sent to the user equipment.

[0369] The first domain may be configured as a 3rd Generation Partnership Project 3GPP 5G system 5GS; and wherein the other domain may be configured as a 3GPP Evolved Packet System EPS.

[0370] The assistance information may be received from the access and mobility function via non-access stratum, NAS, signaling.

[0371] The assistance information may be received within a downlink NAS transport message from the access and mobility function.

[0372] The assistance information may be received from the positioning management function via Long Term Evolution Positioning Protocol (LPP) signaling.

[0373] The assistance information may be received within a location services user plane LCUP assistance information data from a location management function.

[0374] The assistance information may be received from the positioning management function via secure user plane positioning SUPL signaling.

[0375] The assistance information may be received within a SUPL Initiation message from a location management function.

[0376] The first network function may be an access and mobility function.

[0377] The first network function may be a positioning management function.

[0378] The first network function may be a positioning service user plane function.

[0379] After the data connection is established, the user equipment can use the data connection to send data. The data connection can be used to provide positioning services to the user equipment through a user in another domain.

[0380] Fig. 9 Operations that may be performed by an apparatus for user equipment are shown.

[0381] During 901, the user equipment receives assistance information from a first network function located in a first domain based on a previous indication that a user plane-based location service session for the user equipment is active in another domain, wherein the assistance information identifies a user plane server for providing location services for the user equipment via a user plane of the first domain. The indication may have been previously sent from the MME to the AMF.

[0382] During 902, after performing handover of the user equipment from another domain to the first domain, the user equipment establishes a data connection with a user plane server based on the auxiliary information, so as to provide positioning services for the user equipment through the user plane of the first domain.

[0383] When a user device switches from another domain to the first domain, it can execute Fig. 9 of these operations.

[0384] The data connection may be a Packet Data Network (PDN) connection; and wherein the assistance information is used to reach a user plane server through the PDN connection.

[0385] The assistance information may be received before a command for the handover is sent to the user equipment.

[0386] The first domain may be configured as a 3rd Generation Partnership Project 3GPP 5G system 5GS; and wherein the other domain may be configured as a 3GPP Evolved Packet System EPS.

[0387] The assistance information may be received from the access and mobility function via non-access stratum, NAS, signaling.

[0388] The assistance information may be received within a downlink NAS transport message from the access and mobility function.

[0389] The assistance information may be received from the positioning management function via Long Term Evolution Positioning Protocol (LPP) signaling.

[0390] The assistance information may be received within a location services user plane LCUP assistance information data from a location management function.

[0391] The assistance information may be received from the positioning management function via secure user plane positioning SUPL signaling.

[0392] The assistance information may be received within a SUPL Initiation message from a location management function.

[0393] The first network function may be an access and mobility function.

[0394] The first network function may be a positioning management function.

[0395] The first network function may be a positioning service user plane function.

[0396] After the data connection is established, the user equipment may use the data connection to send data. The data connection may be used to provide a positioning service to the user equipment through a user of the first domain.

[0397] Fig.10 The operations that can be performed by the first network function located in the first domain are shown. The first network function may correspond to the above Figure 8 and / or Fig. 9 Describe the first network function.

[0398] During 1001, a first network function determines that a user equipment receiving a location service over a user plane via a first domain is to be handed over from the first domain to another domain.

[0399] During 1002, a first network function provides assistance information to a user equipment, the assistance information identifying a user plane server for providing a positioning service for the user equipment through a user plane of another domain after the user equipment is handed over to a second domain.

[0400] Determining that the user equipment is to be handed over is performed based on receiving a handover indication from a mobility management entity.

[0401] Fig.11 The operations that can be performed by the first network function located in the first domain are shown. The first network function may correspond to the above Figure 8 and / or Fig. 9 Describe the first network function.

[0402] The providing may include providing the assistance information directly to the user equipment.

[0403] The providing may include providing the assistance information indirectly to the user equipment via at least one of: a positioning management function; or a positioning service user plane function.

[0404] During 1101 , a first network function receives a location request regarding a user equipment located in a first domain.

[0405] During 1102, the first network function determines that the user equipment has previously received positioning services over a user plane via another domain.

[0406] During 1103, the first network function provides auxiliary information to the user equipment, the auxiliary information identifying a user plane server for providing positioning services for the user equipment via a user plane. In the case where the UE is switched from the first domain to the second domain, the user plane may be a user plane of another domain. In the case where the user equipment is switched from another domain to the first domain, the user plane may be in the first domain.

[0407] Determining that the user equipment has previously received positioning services over the user plane via another domain may be performed based on receiving a handover indication from the mobility management entity.

[0408] The providing may include providing the assistance information directly to the user equipment.

[0409] The providing may include providing the assistance information indirectly to the user equipment via at least one of: a positioning management function; or a positioning service user plane function.

[0410] Fig.12 Operations that may be performed by a second network function located in the first domain are shown. The second network function may be associated with Fig.10 and Fig.11 The user equipment may be Figure 8 or Fig. 9 user equipment, or some other user equipment.

[0411] During 1201 , a second network function receives assistance information from a first network function located in a first domain, the assistance information identifying a user plane server for providing a positioning service for a user equipment via a user plane of another domain.

[0412] During 1202, the second network function provides the assistance information to the user equipment.

[0413] The second network function may be at least one of the following: a positioning management function; or a positioning service user plane function.

[0414] Figures 10 to 12 The first network function in the example may be an access and mobility function.

[0415] Figures 8 to 12 The auxiliary information function in the example may include address information of the user plane server.

[0416] Figures 8 to 12The assistance information function in the example may include at least one of the following: an address of a user plane server; a unique identifier of the user plane server; a positioning service-related identifier; one or more fully qualified domain names (FQDNs) of the user plane server; secure user plane positioning assistance information for establishing a user plane connection in the second domain; or transport layer security assistance information for establishing a user plane connection in the second domain.

[0417] exist Figures 8 to 12 In the above example, the first domain may be 5GS, and the other domain may be EPS. Alternatively, the first domain may be EPS, and the second domain may be 5GS.

[0418] The above examples illustrate that for the specific case of movement between 5GS and EPS, the mechanism can be asymmetric with respect to the direction of movement of the user equipment.

[0419] For example, in the case of 5GS to EPS mobility, EPS-related assistance information can be provided in 5GS, and the UE switched to EPS can use the information after moving to EPS.

[0420] When the UE moves in the opposite direction (i.e., the UE switches from EPS to 5GS), no assistance information is provided to the UE when the UE is in EPS. This may help minimize the impact on EPS. However, an optional indication is provided from the MME to the AMF, which may indicate the presence of such an LCS / UP session in the EPS, which the UE uses for positioning services when the UE is in the EPS. The AMF may choose to use (or) configure based on the LMF to initiate an LCS / user plane session in the 5GS.

[0421] A potential change request showing how the above example can be reflected in the current specification is provided as Appendix A.

[0422] Figure 2An example of a control device for a communication system is shown, the control device being coupled to a station of the access system and / or a station for controlling the access system, such as a RAN node (e.g., a base station, gNB), a central unit of a cloud architecture or a node of a core network (such as an MME or S-GW), a scheduling entity (such as a spectrum management entity), or a server or host (e.g., a device hosting an NRF, NWDAF, AMF, SMF, UDM / UDR, etc.). The control device may be integrated with a node or module of the core network or RAN or located outside it. In some examples, the base station includes a separate control device unit or module. In other examples, the control device may be another network element, such as a radio network controller or a spectrum controller. The control device 200 may be configured to provide control of communications in a service area of ​​the system. The device 200 includes at least one memory 201, at least one data processing unit 202, 203, and an input / output interface 204. Via the interface, the control device may be coupled to a receiver and a transmitter of the device. The receiver and / or transmitter may be implemented as a radio front end or a remote radio head. For example, the control device 200 or the processor 201 may be configured to execute appropriate software code to provide control functionality.

[0423] Now refer to Figure 3 describing in more detail possible wireless communication devices, Figure 3 A schematic partial cross-sectional view of a communication device 300 is shown. Such a communication device is generally referred to as a user equipment (UE) or terminal. A suitable mobile communication device can be provided by any device capable of sending and receiving radio signals. Non-limiting examples include a mobile station (MS) or a mobile device (such as a mobile phone or a so-called "smart phone"), a computer with a wireless interface card or other wireless interface facilities (e.g., a USB adapter), a personal data assistant (PDA) or a tablet computer with wireless communication capabilities, or any combination of these, etc. The mobile communication device can provide, for example, data communications for carrying communications (such as voice, e-mail (email), text messages, multimedia, etc.). Therefore, a user can be given or provided with a variety of services via his communication device. Non-limiting examples of these services include two-way or multi-way calls, data communications or multimedia services, or access to data communication network systems (such as the Internet) only. Broadcast or multicast data can also be provided to users. Non-limiting examples of content include downloads, television and radio broadcast programs, videos, advertisements, various alarms, and other information.

[0424] A wireless communication device may be, for example, a mobile device (that is, a device that is not fixed to a particular location), or it may be a fixed / stationary device. A wireless device may be configured to utilize human interaction for communication, or may not require human interaction for communication. As described herein, the term UE or "user" is used to refer to any type of wireless communication device.

[0425] The wireless device 300 may receive signals over the air or radio interface 307 via suitable means for receiving, and may transmit signals via suitable means for transmitting radio signals. Figure 3 In the embodiment of the present invention, the transceiver arrangement is schematically indicated by block 306. The transceiver arrangement 306 may be provided, for example, by means of a radio component and an associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the wireless device.

[0426] The wireless device is typically provided with at least one data processing entity 301, at least one memory 302 and possibly other components 303 for software and hardware assisted execution of the tasks it is designed to perform, including controlling access to and communication with access systems and other communication devices. Data processing, storage and other related control means may be provided on a suitable circuit board and / or in a chipset. This feature is indicated by reference numeral 304. The user may control the operation of the wireless device by means of a suitable user interface such as a keypad 305, voice commands, a touch-sensitive screen or touchpad, a combination thereof, etc. A display screen 308, a speaker and a microphone may also be provided. In addition, the wireless communication device may include suitable connectors (wired or wireless) to other devices and / or for connecting external accessories (e.g., a hands-free device).

[0427] Figure 4 Schematic representations of non-volatile storage media 400a (e.g., a computer compact disk (CD) or digital versatile disk (DVD)) and 400b (e.g., a universal serial bus (USB) memory stick) storing instructions and / or parameters 402 that, when executed by a processor, allow the processor to perform Figure 8 and / or Fig. 9 and / or Fig.10 , and / or Fig.11 , and / or Fig.12 The method of, and / or one or more steps of a method otherwise previously described.

[0428] As provided herein, various aspects are described in the detailed description of the examples and in the claims. In general, some examples may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, but the examples are not limited thereto. Although various examples may be shown and described as block diagrams, flow charts, or shown and described using some other graphical representations, it will be understood that, as non-limiting examples, these boxes, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof.

[0429] The examples may be implemented by computer software (which is stored in a memory and can be executed by at least one data processor of the entity involved) or by hardware or a combination of software and hardware. Furthermore, in this regard, it should be noted that any process (e.g. Figure 8 and / or Fig. 9 and / or Fig.10 , and / or Fig.11 , and / or Fig.12 The software may be stored on a physical medium such as a memory chip, or a memory block implemented within a processor, a magnetic medium such as a hard disk or a floppy disk, and an optical medium such as, for example, a DVD and its data variants, CD, etc.

[0430] The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor may be of any type suitable for the local technical environment and may include, as non-limiting examples, one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a gate-level circuit, and a processor based on a multi-core processor architecture.

[0431] Alternatively or additionally, some examples may be implemented using a circuit. The circuit may be configured to perform one or more functions and / or method steps described previously. The circuit may be arranged in a base station and / or a communication device and / or a core network entity.

[0432] As used in this application, the term "circuitry" may refer to one or more or all of the following:

[0433] (a) hardware circuit implementation only (such as analog and / or digital circuit implementation only);

[0434] (b) a combination of hardware circuitry and software, such as:

[0435] (i) a combination of analog and / or digital hardware circuits with software / firmware, and

[0436] (ii) any portion of a hardware processor (including a digital signal processor) with software, software and memory that work together to enable an apparatus (such as a communication device or base station) to perform the various functions previously described; and

[0437] (c) Hardware circuits and / or processors, such as a microprocessor or portion of a microprocessor, that require software (e.g., firmware) to operate, but in which the software may not be present when not being used for operation.

[0438] This definition of "circuitry" applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term "circuitry" also covers an implementation of merely a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its accompanying software and / or firmware. The term "circuitry" also covers, for example, an integrated device.

[0439] The above description has been provided by way of non-limiting examples, i.e., a comprehensive and informative description of some examples. However, various modifications and variations may become apparent to those skilled in the relevant art in view of the above description when read in conjunction with the accompanying drawings and claims. However, all such and similar modifications of the teachings will still fall within the scope of the claims.

[0440] Different examples are described above using radio access architectures based on Long Term Evolution Advanced (LTE-Advanced, LTE-A) or New Radio (NR, 5G) as examples of access architectures to which the described techniques may be applied, but the examples are not limited to such architectures. By appropriately adjusting parameters and procedures, these examples may also be applied to other types of communication networks with suitable components. Some examples of other options for suitable systems are Universal Mobile Telecommunications System (UMTS) Radio Access Network (UTRAN), Wireless Local Area Network (WLAN or WiFi), Worldwide Interoperability for Microwave Access (WiMAX), Personal Communications Service (PCS), Wideband Code Division Multiple Access (WCDMA), systems using Ultra-Wideband (UWB) technology, sensor networks, mobile ad hoc networks (MANET), and Internet Protocol Multimedia Subsystem (IMS), or any combination thereof.

[0441] Figure 5 An example of a simplified system architecture is shown, which shows only some elements and functional entities, all of which are logical units, the implementation of which may differ from what is shown. Figure 5 The connections shown in are logical connections; the actual physical connections may be different. It is obvious to those skilled in the art that the system typically includes in addition to Figure 5 Other functions and structures than those shown in .

[0442] However, the examples are not limited to the systems given as examples, but a person skilled in the art may apply the solution to other communication systems having the necessary characteristics.

[0443] Figure 5 The example of FIG. 1 shows a portion of an exemplary radio access network. For example, the radio access network may support sidelink communications as described in more detail below.

[0444] Figure 5 Devices 500 and 502 are shown. Devices 500 and 502 are configured to be wirelessly connected to node 504 on one or more communication channels. Node 504 is further connected to core network 506. In one example, node 504 can be an access node, such as an (e / g)NodeB of a device in a serving cell. In one example, node 504 can be a non-3GPP access node. The physical link from the device to the (e / g)NodeB is referred to as an uplink or reverse link, and the physical link from the (e / g)NodeB to the device is referred to as a downlink or forward link. It should be understood that (e / g)NodeB or its functions can be implemented by using entities such as any node, host, server or access point suitable for such use.

[0445] The communication system typically includes more than one (e / g)NodeB, in which case the (e / g)NodeB may also be configured to communicate with each other via wired or wireless links designed for the purpose. These links may be used for signaling purposes. (e / g)NodeB is a computing device configured to control the radio resources of the communication system coupled thereto. NodeB may also be referred to as a base station, an access point or any other type of interface device, including a relay station capable of operating in a wireless environment. (e / g)NodeB includes a transceiver or is coupled to a transceiver. From the transceiver of the (e / g)NodeB, a connection to an antenna unit is provided, which establishes a bidirectional radio link to the device. The antenna unit may include multiple antennas or antenna units / elements. (e / g)NodeB is further connected to a core network 506 (CN or next generation core NGC). Depending on the deployed technology, the (e / g)NodeB is connected to a Serving and Packet Data Network Gateway (S-GW+P-GW) or a User Plane Function (UPF) for routing and forwarding user data packets and for providing connectivity of the device to one or more external packet data networks and to a Mobility Management Entity (MME) or Access Mobility Management Function (AMF) for controlling access and mobility of the device.

[0446] Examples of devices are subscriber units, user equipment, user equipment (UE), user terminals, terminal equipment, mobile stations, mobile devices, etc.

[0447] Devices generally refer to mobile or static devices (e.g., portable or non-portable computing devices), including wireless mobile communication devices operating with or without a Universal Subscriber Identity Module (USIM), including but not limited to the following types of devices: mobile phones, smart phones, personal digital assistants (PDAs), cell phones, devices using wireless modems (alarm or measurement devices, etc.), laptop and / or touch screen computers, tablets, game consoles, notebook computers, and multimedia devices. It should be understood that a device can also be a nearly exclusive uplink-only device, an example of which is a camera or video camera that uploads images or video clips to a network. A device can also be a device with the ability to operate in an Internet of Things (IoT) network, which is a scenario in which objects / objects have the ability to transmit data over a network without human-to-human or human-to-computer interaction, such as for smart grids and connected vehicles. Devices can also utilize the cloud. In some applications, a device can include a user-portable device (such as a watch, headphones, or glasses) with a radio component, and the calculation is performed in the cloud.

[0448] The device shows a type of apparatus for allocating and specifying resources on the air interface, and thus any features described herein with respect to the device can be implemented using a corresponding apparatus (such as a relay node). An example of such a relay node is a layer 3 relay (self-backhaul relay) toward a base station. The device (or in some examples, a layer 3 relay node) is configured to perform one or more user equipment functions.

[0449] The various techniques described herein may also be applied to cyber-physical systems (CPS) (systems of computing units / elements that coordinate the control of physical entities). CPS may be able to implement and utilize a large number of interconnected information and communication technology (ICT) devices (sensors, actuators, processors, microcontrollers, etc.) embedded in physical objects at different locations. Mobile cyber-physical systems (where the physical system in question has inherent mobility) are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robots and electronic devices transported by humans or animals.

[0450] Additionally, although the apparatus has been described as a single entity, different units, processors and / or memory units may be implemented. Figure 5 not all are shown).

[0451] 5G enables the use of multiple-input-multiple-output (MIMO) antennas, more base stations or nodes than LTE (the so-called small cell concept), including macro sites that operate in collaboration with smaller stations and adopt various radio technologies (depending on service requirements, use cases and / or available spectrum). 5G mobile communications support a wide range of use cases and related applications, including video streaming, augmented reality, different ways of sharing data, and various forms of machine-type applications (such as (massive) machine-type communications (mMTC), including vehicle safety, different sensors and real-time control). 5G is expected to have multiple radio interfaces (e.g., below 6 GHz or above 24 GHz, centimeter wave (cmWave) and millimeter wave (mmWave)), and also be able to integrate with existing legacy radio access technologies (such as LTE). At least in the early stages, integration with LTE can be implemented as a system in which macro coverage is provided by LTE and 5G radio interface access comes from small cells through aggregation to LTE. In other words, 5G is planned to support both inter-RAT operability (such as LTE-5G) and inter-RI operability (inter-radio interface operability, such as below 6GHz - cmWave, above 6 or 24GHz - cmWave and mmWave). One of the concepts considered for use in 5G networks is network slicing, where multiple independent and dedicated virtual subnetworks (network instances) can be created within the same infrastructure to run services with different requirements for latency, reliability, throughput and mobility.

[0452] LTE network architecture is completely distributed in the radio and completely centralized in the core network. Low-latency applications and services in 5G require content to be close to the radio, leading to local grooming and multi-access edge computing (MEC). 5G enables analysis and knowledge generation to be performed at the data source. This approach requires the use of resources that may not be continuously connected to the network, such as laptops, smartphones, tablets, and sensors. MEC provides a distributed computing environment for application and service hosting. It is also able to store and process content close to cellular users for faster response times. Edge computing covers a wide range of technologies such as wireless sensor networks, mobile data acquisition, mobile signature analysis, collaborative distributed peer-to-peer self-organizing networking and processing (also classified as local cloud / fog computing and grid / mesh computing, dew computing, mobile edge computing, cloudlet, distributed data storage and retrieval), autonomous self-healing networks, remote cloud services, augmented reality and virtual reality, data caching, Internet of Things (large-scale connectivity and / or latency critical), critical communications (autonomous driving vehicles, traffic safety, real-time analysis, time-critical control, healthcare applications).

[0453] The communication system may also be able to communicate with or utilize services provided by other networks 512, such as a public switched telephone network or a VoIP network or the Internet or a private network. The communication network may also be able to support the use of cloud services, for example, at least a portion of the core network operations may be provided as a cloud service (this is in the Figure 5 When performed away from the core network, this may also be referred to as edge computing. The communication system may also include a central control entity or the like, providing facilities for different operators' networks to collaborate, for example, in spectrum sharing.

[0454] Edge computing technology can be introduced into the radio access network (RAN) by utilizing network function virtualization (NFV) and software defined networking (SDN). Using edge cloud technology can mean performing access node operations at least partially in a server, host or node that is operably coupled to a remote radio head or a base station including a radio component. Node operations can also be distributed among multiple servers, nodes or hosts. The application of cloudRAN architecture enables RAN real-time functions to be performed at or near the remote antenna site (in the distributed unit DU 508) and non-real-time functions to be performed in a centralized manner (in the central unit CU 510).

[0455] It should also be understood that the distribution of work between core network operations and base station operations may be different from that of LTE, or even non-existent. Some other technological advances that may be used are big data and all-IP, which can change the way networks are constructed and managed. 5G (or New Radio NR) networks are designed to support multiple hierarchical structures, where edge computing servers can be placed between the core and the base station or NodeB (gNB). An example of edge computing is MEC defined by the European Telecommunications Standards Institute. It should be understood that MEC (and other edge computing protocols) can also be applied in 4G networks.

[0456] 5G can also make use of satellite communications to enhance or complement the coverage of 5G services, for example by providing backhaul. Possible use cases are providing service continuity for machine-to-machine (M2M) or Internet of Things (IoT) devices or for passengers on board vehicles, mobile broadband (MBB), or ensuring service availability for critical communications and future railway / maritime / aeronautical communications. Satellite communications can make use of geostationary earth orbit (GEO) satellite systems, but also low earth orbit (LEO) satellite systems, in particular mega-constellations (systems in which hundreds of (nano) satellites are deployed). Each satellite in a mega-constellation can cover multiple satellite-enabled network entities creating ground cells. Ground cells can be created by ground relay nodes, or by gNBs located on the ground or in satellites.

[0457] The system shown is only an example of a part of a radio access system, and in practice, the system may include multiple (e / g)NodeBs, a device may access multiple radio cells, and the system may also include other devices, such as physical layer relay nodes or other network units / elements. At least one of the (e / g)NodeBs may be a home / family (e / g)NodeB. Additionally, in a geographical area of ​​the radio communication system, multiple different types of radio cells as well as multiple radio cells may be provided. The radio cells may be macro cells (or umbrella cells), which are large cells, typically having a diameter of up to tens of kilometers, or smaller cells, such as micro cells, femto cells or pico cells. Figure 5 The (e / g)NodeBs may provide any type of these cells. A cellular radio system may be implemented as a multi-layer network comprising multiple types of cells.

[0458] Annex A

[0459] Summary of contribution: This attachment proposes an example update to solution #33 for KI #8

[0460]

[0461] 2 Example Proposal

[0462] The following update is proposed for TR 23.700-71 - "Study enhancement to the 5GC LoCation Services (LCS); Phase 3"

[0463] ***CHANGES BEGIN***

[0464] 6.0 Map solutions to key issues

[0465] Table 6.0-1: Mapping solutions to key issues

[0466]

[0467] ***Next Change***

[0468] 6.x Solution #8: Support LCS mobility when UE moves between 5GS and EPS

[0469] 6.X.1 Introduction

[0470] This solution addresses KI “Key Issue #8: Supporting Location Service Continuity in the Face of UE Mobility”.

[0471] The continuity of certain basic services (such as PDU sessions) during mobility is currently defined. However, the handling of LCS sessions during the mobility process is not specified. In particular, there is no specification on whether an ongoing LCS session will be terminated or continued after mobility and if continued, how the continuity will work. Due to this missing piece, many impacts may occur.

[0472] - An LCS session may be terminated upon mobility, wherein the LCS client has to re-initiate the session after the process.

[0473] -LMF may not be aware of mobility at all, leading to inaccurate positioning estimates.

[0474] - Inter-vendor testing may fail as there is no clear specification.

[0475] -LCS sessions can be enabled as part of other services (such as emergency calling) - which may be affected due to current specifications - leading to regulatory issues.

[0476] At least some of these problems could be mitigated or avoided if there were clear specifications on how LCS sessions would be handled in different mobility procedures, and in particular if the network could guarantee continuity.

[0477] The example considerations for this article are:

[0478] - Keep changes in EPC minimal to enable gradual changes to legacy functionality.

[0479] -No standardized interface between EPC-GMLC and 5GC-GMLC is defined. According to Section 4.2a. in TS23.273, this interface, denoted Lr', is not standardized and if EPC-GMLC and 5GC-GMLC are co-located, Lr' is not required at all. This example does not require standardization of this interface.

[0480] - Provides a common procedure for all types of positioning requests (MO-LR / MT-LR with / without delayed positioning);

[0481] - Provides a simple example that works regardless of the current state of the ongoing positioning process when a mobility event occurs;

[0482] 6.X.2 Functional Description

[0483] This example proposal provides an example for mobility between 5GS and EPS with reference to Figures 13 and 14. Fig.12 and FIG. 13 show example signaling.

[0484] 6.X.3 Procedure

[0485] Referring to Figure 13, the following is provided:

[0486]

[0487] describe:

[0488] Steps 1-4 describe a typical MT-LR LCS session on 5GS (similar to Figure 6.1.2-1 in TS 23.273).

[0489] Steps 1.a. to 12).

[0490] Steps 5-14 describe the general 5GS to EPS handover process (similar to Figure 4 .11.1.2.1-1

[0491] Steps 1 to 12.b).

[0492] When the AMF receives the Relocation Response (step 10), it may initiate steps 15 and 17 in parallel with step 11. Steps 15-16: Cancel the LCS session on the 5GS.

[0493] Step 17: The AMF indicates the failure to the 5GC-GMLC with the reason being “Switch to EPC” and includes the target MMEID.

[0494] Step 18: 5GC-GMLC forwards the positioning request to EPC-GMLC, including all parameters requested by LCS and

[0495] Target MME ID.

[0496] Steps 19-24: Start an LCS session on EPS (similar to Fig. 9 .18, steps 1-10). Steps 25-26: EPC-GMLC returns the UE location estimate to 5GC-GMLC, which then

[0497] It is forwarded to the LCS client.

[0498] Note:

[0499] - It can be observed that this example process is done in a way where the LCS client is / may not be aware of the mobility handling and LCS session continuity is ensured.

[0500] - There can be a mapping of LCS QoS (from the values ​​defined for 5GS to the values ​​defined in 4GS) - this can be done by GMLC.

[0501] o For QoS attributes that are common between 5GS and EPS, the original LCS QoS definition values ​​can be the same as in

[0502] It is used in the same way as in EPS.

[0503] o For 5GS specific QoS attributes -> QoS mapping can be done for the most stringent QoS value and best effort processing within the QoS class.

[0504] - If the LCS session is active on the user plane in 5GS when the handover is triggered, the AMF (at step 10) may send the user plane assistance data of the EPS-UP server to the UE directly or through the LMF before the handover is completed. In turn, once a suitable PDN connection has been established or switched to, the UE may use this assistance data to reach the server and then (re)establish a TLS session and a SUPL session on EPS, through which,

[0505] The LCS session can continue in the user plane in EPS.

[0506] Referring to Figure 14, the following is provided:

[0507]

[0508] describe:

[0509] Steps 1-4 describe a normal MT-LR LCS session on EPS (similar to Figure 6.1.2-1 in TS 23.271).

[0510] Steps 1 to 3).

[0511] Steps 5-14 describe the general EPS to 5GS handover process (similar to Figure 4 .11.1.2.2.2-1, steps 1 to 16 and Figure 4 .Steps 1-4 in 11.1.2.2.3-1).

[0512] When the MME receives the Forward Relocation Response (step 10 ), it may initiate steps 15 and 17 in parallel with step 11 .

[0514] Steps 15-16: Cancel the LCS session on EPS.

[0515] Step 17: The MME indicates the failure to the EPC-GMLC with the reason being “Switchover to EPC” and includes the target AMF ID.

[0516] Step 18: EPC-GMLC forwards the positioning request to 5GC-GMLC, including all parameters requested by LCS and

[0517] Target AMF ID.

[0518] Steps 19-24: Start an LCS session on 5GS (similar to steps 1-23 in Figure 6.1.2-1 in TS23.273). Steps 25-26: 5GC-GMLC returns the UE positioning estimate to EPC-GMLC, which then

[0519] It is forwarded to the LCS client.

[0520] Note:

[0521] - It can be observed that two example procedures may be defined in such a way that the LCS client remains unaware of the mobility signaling and LCS session continuity is ensured.

[0522] - It is possible to have a mapping of LCS QoS (from values ​​defined for 5GS to values ​​defined in 4GS and vice versa)

[0523] ——This can be done by GMLC.

[0524] o For QoS attributes that are common between 5GS and EPS, the original LCS QoS definition values ​​can be used as in 5GS.

[0525] o For EPS specific QoS attributes -> QoS mapping can be done for the most stringent QoS value and best effort processing is done within the QoS class.

[0526] -If the LMF is configured to use LCS through the user plane in 5GS, the LMF chooses to initiate an LCS session through the user plane at step 24.

[0527] 6.X.4 Impact on Services, Entities, and Interfaces

[0528]

[0529] ***END OF CHANGES***

Claims

1. A method for a user equipment, the method comprising: When the user equipment is located in the first domain, receiving assistance information from a first network function located in the first domain, the assistance information identifying a user plane server that provides a positioning service for the user equipment via a user plane of another domain; as well as After performing handover of the user equipment from the first domain to the another domain, a data connection with the user plane server is established based on the auxiliary information to provide positioning services for the user equipment through the user plane of the another domain.

2. A method for a user equipment, the method comprising: receiving assistance information from a first network function located in a first domain based on a previous indication that a user plane based location service session for the user equipment is active in another domain, wherein the assistance information identifies a user plane server for providing location services for the user equipment over a user plane of the first domain; and After performing handover of the user equipment from the other domain to the first domain, a data connection with the user plane server is established based on the auxiliary information to provide positioning services for the user equipment through the user plane of the first domain.

3. The method according to any one of claims 1 or 2, wherein: The data connection is a Packet Data Network (PDN) connection; and wherein the assistance information is used to reach the user plane server through the PDN connection.

4. The method according to any one of claims 1 or 2, wherein: The assistance information is received before a command for the handover is sent to the user equipment.

5. The method according to claim 1 or 2, wherein: The first domain is configured as a 3rd Generation Partnership Project 3GPP 5G System 5GS; and wherein the other domain is configured as a 3GPP Evolved Packet System EPS.

6. The method according to any one of claims 1 to 5, wherein: The first network function is an access and mobility function.

7. The method according to claim 6, wherein: The assistance information is received from the access and mobility function via non-access stratum, NAS, signaling.

8. The method according to claim 7, wherein: The assistance information is received within a downlink NAS transport message from the access and mobility function.

9. The method according to any one of claims 1 to 5, wherein: The first network function is a positioning management function.

10. The method according to claim 9, wherein: The assistance information is received from the positioning management function via Long Term Evolution Positioning Protocol (LPP) signaling.

11. The method according to claim 10, wherein: The assistance information is received within a Location Services User Plane (LCUP) assistance information data from the Location Management Function.

12. The method according to claim 9, wherein: The assistance information is received from the positioning management function via secure user plane positioning (SUPL) signaling.

13. The method according to claim 12, wherein: The assistance information is received in a SUPL Initiation message from the location management function.

14. The method according to any one of claims 1 to 5, wherein: The first network function is a positioning service user plane function.

15. A method for a first network function located in a first domain, the method comprising: determining that a user equipment receiving a positioning service through a user plane via the first domain is to be handed over from the first domain to another domain; as well as The auxiliary information is provided to the user equipment, the auxiliary information identifying a user plane server for providing a positioning service for the user equipment through a user plane of the other domain after the user equipment is handed over to the second domain.

16. The method according to claim 15, wherein: Determining that the user equipment is to be handed over is performed based on receiving a handover indication from a mobility management entity.

17. A method for a first network function located in a first domain, the method comprising: receiving a location request for a user equipment located in a first domain; determining that the user equipment has previously received positioning services via another domain over a user plane; as well as The auxiliary information is provided to the user equipment, where the auxiliary information identifies a user plane server for providing a positioning service for the user equipment via a user plane.

18. The method according to claim 17, wherein: Determining that the user equipment has previously received positioning services over a user plane via another domain is performed based on receiving a handover indication from a mobility management entity.

19. The method according to any one of claims 15 to 18, wherein: The providing includes: providing the auxiliary information directly to the user equipment.

20. The method according to any one of claims 15 to 18, wherein: The providing comprises: providing the auxiliary information to the user equipment indirectly via at least one of: a positioning management function; or a positioning service user plane function.

21. A method for a second network function located in a first domain, the method comprising: receiving assistance information from a first network function located in the first domain, the assistance information identifying a user plane server for providing a positioning service for a user equipment via a user plane of another domain; as well as The auxiliary information is provided to the user equipment.

22. The method according to claim 21, wherein: The second network function is at least one of the following: a positioning management function; or a positioning service user plane function.

23. The method according to any one of claims 15 to 22, wherein: The first network function is an access and mobility function.

24. A method according to any one of the preceding claims, wherein: The auxiliary information includes address information of the user plane server.

25. A method according to any one of the preceding claims, wherein: The auxiliary information includes at least one of the following: the address of the user plane server; the unique identifier of the user plane server; a positioning service related identifier; One or more fully qualified domain names FQDNs of the user plane server; secure user plane location assistance information for establishing a user plane connection in the second domain; Or transport layer security auxiliary information used to establish a user plane connection in the second domain.

26. An apparatus comprising means for performing the method of claim 1, or any one of claims 3 to 14 when dependent on claim 1.

27. An apparatus comprising means for performing the method of claim 2, or any one of claims 3 to 14 when dependent on claim 2.

28. Apparatus comprising means for performing the method of any one of claims 15 to 16, or any one of claims 19 to 20, 23 or 24 to 25 when dependent on any one of claims 15 to 16.

29. Apparatus comprising means for performing the method of any one of claims 17 to 18, or any one of claims 19 to 20, 23 or 24 to 25 when dependent on any one of claims 17 to 18.

30. Apparatus comprising means for performing the method of any one of claims 21 to 22, or any one of claims 19 to 20, 23 or 24 to 25 when dependent on any one of claims 21 to 22.

31. A computer program comprising instructions which, when executed by an apparatus, cause the apparatus to perform the method of claim 1, or any one of claims 3 to 14 when dependent on claim 1.

32. A computer program comprising instructions which, when executed by an apparatus, cause the apparatus to perform the method of claim 2, or any one of claims 3 to 14 when dependent on claim 2.

33. A computer program comprising instructions which, when executed by an apparatus, cause the apparatus to perform the method of any one of claims 15 to 16, or any one of claims 19 to 20, 23 or 24 to 25 when dependent on any one of claims 15 to 16.

34. A computer program comprising instructions which, when executed by an apparatus, cause the apparatus to perform the method of any one of claims 17 to 18, or any one of claims 19 to 20, 23 or 24 to 25 when dependent on any one of claims 17 to 18.

35. A computer program comprising instructions which, when executed by an apparatus, cause the apparatus to perform the method of any one of claims 21 to 22, or any one of claims 19 to 20, 23 or 24 to 25 when dependent on any one of claims 21 to 22.

Images