Apparatus, method, and computer program

Abstract

An apparatus, a method, and a computer program are provided for causing a user equipment to: when the user equipment is located in a first domain, receive, from a first network function located in the first domain, assistance information identifying a user plane server that provides location services to the user equipment via a user plane of another domain; and after a handover of the user equipment from the first domain to the other domain is performed, establish a data connection with the user plane server for providing location services to the user equipment via the user plane of the other domain based on the assistance information.

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, and computer programs for apparatus. [Background technology]

[0002] A communication system can be considered to be a facility that enables communication sessions between two or more entities, such as communication devices, base stations, and / or other nodes, by providing carriers 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 under radio standards such as those provided by 3GPP, satellite-based communication systems, and different wireless local networks, e.g., wireless local area networks (WLANs). Wireless systems may generally be divided into cells and are therefore often referred to as cellular systems.

[0004] Communication systems and associated devices typically operate according to a given standard or specification that describes what various entities associated with the system are allowed to do and how that should be accomplished. The communication protocols and / or parameters to be used for the connections are also typically defined. Examples of standards include the so-called 5G standard. Summary of the Invention [Means for solving the problem]

[0005] According to a first aspect, there is provided a method for a user equipment, the method comprising: when the user equipment is located in a first domain, receiving, from a first network function located in the first domain, assistance information identifying a user plane server that provides location services for the user equipment via a user plane of another domain; and after a handover of the user equipment from the first domain to the other domain is performed, establishing a data connection with the user plane server for providing location services for the user equipment via a user plane of the other domain based on the assistance information.

[0006] The data connection may be a packet data network, PDN, connection; the assistance information is utilized to reach a user plane server via the PDN connection.

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

[0008] A first domain may be configured as a 5G system (5GS) of the Third Generation Partnership Project (3GPP); another domain may be configured as a 3GPP Evolved Packet System (EPS).

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

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

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

[0012] The assistance information may be received from the location management function as location service user plane, LCUP, assistance information data.

[0013] The assistance information may be received from the location management function via Secure User Plane Location, SUPL, signaling.

[0014] The assistance information may be received from the location management function in a SUPL initiation message.

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

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

[0017] The first network function may be a location services user plane function.

[0018] The support information may include address information of a user plane server.

[0019] The assistance information may include at least one of: an address of a user plane server; a unique identifier of the user plane server; a location service correlation 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 to the second domain; or transport layer security assistance information for establishing a user plane connection to the second domain.

[0020] According to a second aspect, there is provided a method for a first network function located in a first domain, the method comprising: determining that a user equipment receiving location services via a user plane via the first domain should be handed over from the first domain to another domain; and providing assistance information to the user equipment identifying a user plane server for providing location services to the user equipment via the user plane of the other domain after the user equipment has been handed over to the second domain.

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

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

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

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

[0025] The support information may include address information of a user plane server.

[0026] The assistance information may include at least one of: an address of a user plane server; a unique identifier of the user plane server; a location service correlation 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 to the second domain; or transport layer security assistance information for establishing a user plane connection to the second domain.

[0027] According to a third aspect, there is provided 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 the first domain; determining that the user equipment has previously received location services via a user plane via another domain; and providing assistance information to the user equipment identifying a user plane server for providing location services to the user equipment via the user plane.

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

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

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

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

[0032] The support information may include address information of a user plane server.

[0033] The assistance information may include at least one of: an address of a user plane server; a unique identifier of the user plane server; a location service correlation 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 to the second domain; or transport layer security assistance information for establishing a user plane connection to the second domain.

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

[0035] The second network function may be at least one of: a location management function; or a location services user plane function.

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

[0037] The support information may include address information of a user plane server.

[0038] The assistance information may include at least one of: an address of a user plane server; a unique identifier of the user plane server; a location service correlation 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 to the second domain; or transport layer security assistance information for establishing a user plane connection to the second domain.

[0039] According to a fifth aspect, there is provided an apparatus for a user equipment, the apparatus comprising: means for receiving, when the user equipment is located in a first domain, assistance information identifying a user plane server that provides location services to the user equipment via a user plane of another domain, from a first network function located in the first domain; and means for establishing, after a handover of the user equipment from the first domain to the other domain is performed, based on the assistance information, a data connection with the user plane server for providing location services to the user equipment via a user plane of the other domain.

[0040] The data connection may be a packet data network, PDN, connection; the assistance information is utilized to reach a user plane server via the PDN connection.

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

[0042] A first domain may be configured as a 5G system (5GS) of the Third Generation Partnership Project (3GPP); another domain may be configured as a 3GPP Evolved Packet System (EPS).

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

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

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

[0046] The assistance information may be received from the location management function as location service user plane, LCUP, assistance information data.

[0047] The assistance information may be received from the location management function via Secure User Plane Location, SUPL, signaling.

[0048] The assistance information may be received from the location management function in a SUPL initiation message.

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

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

[0051] The first network function may be a location services user plane function.

[0052] The support information may include address information of a user plane server.

[0053] The assistance information may include at least one of: an address of a user plane server; a unique identifier of the user plane server; a location service correlation 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 to the second domain; or transport layer security assistance information for establishing a user plane connection to the second domain.

[0054] According to a sixth aspect, there is provided an apparatus for a first network function located in a first domain, the apparatus comprising: means for determining that a user equipment receiving location services via a user plane via the first domain should be handed over from the first domain to another domain; and means for providing assistance information to the user equipment identifying a user plane server for providing location services to the user equipment via the user plane of the other domain after the user equipment is handed over to the second domain.

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

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

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

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

[0059] The support information may include address information of a user plane server.

[0060] The assistance information may include at least one of: an address of a user plane server; a unique identifier of the user plane server; a location service correlation 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 to the second domain; or transport layer security assistance information for establishing a user plane connection to the second domain.

[0061] According to a seventh aspect, there is provided an apparatus for a first network function located in a first domain, the apparatus comprising: means for receiving a location request for a user equipment located in the first domain; means for determining that the user equipment has previously received location services via a user plane via another domain; and means for providing assistance information to the user equipment identifying a user plane server for providing location services to the user equipment via the user plane.

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

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

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

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

[0066] The support information may include address information of a user plane server.

[0067] The assistance information may include at least one of: an address of a user plane server; a unique identifier of the user plane server; a location service correlation 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 to the second domain; or transport layer security assistance information for establishing a user plane connection to the second domain.

[0068] According to an eighth aspect, there is provided an apparatus for a second network function located in a first domain, the apparatus comprising: means for receiving, from a first network function located in the first domain, assistance information identifying a user plane server for providing location services to a user equipment via a user plane of another domain; and means for providing the assistance information to the user equipment.

[0069] The second network function may be at least one of: a location management function; or a location services user plane function.

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

[0071] The support information may include address information of a user plane server.

[0072] The assistance information may include at least one of: an address of a user plane server; a unique identifier of the user plane server; a location service correlation 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 to the second domain; or transport layer security assistance information for establishing a user plane connection to the second domain.

[0073] According to a ninth aspect, there is provided an apparatus for user equipment, the apparatus comprising: at least one processor; and at least one memory including code that, when executed by the at least one processor, causes the apparatus to: when the user equipment is located in a first domain, receive, from a first network function located in the first domain, assistance information identifying a user plane server that provides location services to the user equipment via a user plane of another domain; and after a handover of the user equipment from the first domain to the other domain is performed, establish a data connection with the user plane server for providing location services to the user equipment via a user plane of the other domain based on the assistance information.

[0074] The data connection may be a packet data network, PDN, connection; the assistance information is utilized to reach a user plane server via the PDN connection.

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

[0076] A first domain may be configured as a Third Generation Partnership Project (3GPP) 5G system (5GS); another domain may be configured as a 3GPP Evolved Packet System (EPS).

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

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

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

[0080] The assistance information may be received from the location management function as location service user plane, LCUP, assistance information data.

[0081] The assistance information may be received from the location management function via Secure User Plane Location, SUPL, signaling.

[0082] The assistance information may be received from the location management function in a SUPL initiation message.

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

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

[0085] The first network function may be a location services user plane function.

[0086] The support information may include address information of a user plane server.

[0087] The assistance information may include at least one of: an address of a user plane server; a unique identifier of the user plane server; a location service correlation 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 to the second domain; or transport layer security assistance information for establishing a user plane connection to the second domain.

[0088] According to a tenth aspect, there is provided an apparatus for a first network function located in a first domain, the apparatus comprising: at least one processor; and at least one memory containing code that, when executed by the at least one processor, causes the apparatus to: determine that a user equipment receiving location services over a user plane via the first domain should be handed over from the first domain to another domain; and provide assistance information to the user equipment identifying a user plane server for providing location services to the user equipment over the user plane of the other domain after the user equipment is handed over to the second domain.

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

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

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

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

[0093] The support information may include address information of a user plane server.

[0094] The assistance information may include at least one of: an address of a user plane server; a unique identifier of the user plane server; a location service correlation 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 to the second domain; or transport layer security assistance information for establishing a user plane connection to the second domain.

[0095] According to an eleventh aspect, there is provided an apparatus for a first network function located in a first domain, the apparatus comprising: at least one processor; and at least one memory containing code that, when executed by the at least one processor, causes the apparatus to: receive a location request for user equipment located in the first domain; determine that the user equipment has previously received location services via a user plane via another domain; and provide assistance information to the user equipment identifying a user plane server for providing location services to the user equipment via the user plane.

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

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

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

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

[0100] The support information may include address information of a user plane server.

[0101] The assistance information may include at least one of: an address of a user plane server; a unique identifier of the user plane server; a location service correlation 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 to the second domain; or transport layer security assistance information for establishing a user plane connection to the second domain.

[0102] According to a twelfth aspect, there is provided an apparatus for a second network function located in a first domain, the apparatus comprising: at least one processor; and at least one memory containing code that, when executed by the at least one processor, causes the apparatus to: receive, from a first network function located in the first domain, assistance information identifying a user plane server for providing location services to a user equipment via a user plane of another domain; and provide the assistance information to the user equipment.

[0103] The second network function may be at least one of: a location management function; or a location services user plane function.

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

[0105] The support information may include address information of a user plane server.

[0106] The assistance information may include at least one of: an address of a user plane server; a unique identifier of the user plane server; a location service correlation 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 to the second domain; or transport layer security assistance information for establishing a user plane connection to the second domain.

[0107] According to a thirteenth aspect, there is provided an apparatus for user equipment, the apparatus comprising: a receiving circuit for receiving, when the user equipment is located in a first domain, assistance information identifying a user plane server that provides location services to the user equipment via a user plane of another domain, from a first network function located in the first domain; and an establishing circuit for establishing, after a handover of the user equipment from the first domain to the other domain is performed, a data connection with the user plane server for providing location services to the user equipment via a user plane of the other domain, based on the assistance information.

[0108] The data connection may be a packet data network, PDN, connection; the assistance information is utilized to reach a user plane server via the PDN connection.

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

[0110] A first domain may be configured as a Third Generation Partnership Project (3GPP) 5G system (5GS); another domain may be configured as a 3GPP Evolved Packet System (EPS).

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

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

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

[0114] The assistance information may be received from the location management function within the location service user plane, LCUP, assistance information data.

[0115] The assistance information may be received from the location management function via Secure User Plane Location, SUPL, signaling.

[0116] The assistance information may be received from the location management function in a SUPL initiation message.

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

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

[0119] The first network function may be a location services user plane function.

[0120] The support information may include address information of a user plane server.

[0121] The assistance information may include at least one of: an address of a user plane server; a unique identifier of the user plane server; a location service correlation 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 to the second domain; or transport layer security assistance information for establishing a user plane connection to the second domain.

[0122] According to a fourteenth aspect, there is provided an apparatus for a first network function located in a first domain, the apparatus comprising: a determining circuit for determining that a user equipment receiving location services via a user plane via the first domain should be handed over from the first domain to another domain; and a providing circuit for providing assistance information to the user equipment identifying a user plane server for providing location services to the user equipment via a user plane of the other domain after the user equipment is handed over to the second domain.

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

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

[0125] The providing circuitry for providing may configure the providing circuitry to indirectly provide the assistance information to the user equipment via at least one of a location management function; or a location services user plane function.

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

[0127] The support information may include address information of a user plane server.

[0128] The assistance information may include at least one of: an address of a user plane server; a unique identifier of the user plane server; a location service correlation 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 to the second domain; or transport layer security assistance information for establishing a user plane connection to the second domain.

[0129] According to a fifteenth aspect, there is provided an apparatus for a first network function located in a first domain, the apparatus comprising: a receiving circuit for receiving a location request related to a user equipment located in the first domain; a determining circuit for determining that the user equipment has previously received location services via a user plane via another domain; and a providing circuit for providing assistance information to the user equipment identifying a user plane server for providing location services to the user equipment via the user plane.

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

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

[0132] The providing circuitry for providing may configure the providing circuitry to indirectly provide the assistance information to the user equipment via at least one of a location management function; or a location services user plane function.

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

[0134] The support information may include address information of a user plane server.

[0135] The assistance information may include at least one of: an address of a user plane server; a unique identifier of the user plane server; a location service correlation 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 to the second domain; or transport layer security assistance information for establishing a user plane connection to the second domain.

[0136] According to a sixteenth aspect, there is provided an apparatus for a second network function located in a first domain, the apparatus comprising: a receiving circuit for receiving assistance information from a first network function located in the first domain, the assistance information identifying a user plane server for providing location services to a user equipment via a user plane of another domain; and a providing circuit for providing the assistance information to the user equipment.

[0137] The second network function may be at least one of: a location management function; or a location services user plane function.

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

[0139] The support information may include address information of a user plane server.

[0140] The assistance information may include at least one of: an address of a user plane server; a unique identifier of the user plane server; a location service correlation 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 to the second domain; or transport layer security assistance information for establishing a user plane connection to the second domain.

[0141] According to a seventeenth aspect, there is provided a non-transitory computer-readable medium including program instructions, the program instructions causing an apparatus for user equipment to: when the user equipment is located in a first domain, receive, from a first network function located in the first domain, assistance information identifying a user plane server that provides location services to the user equipment via a user plane of another domain; and after a handover of the user equipment from the first domain to another domain is performed, establish a data connection with the user plane server for providing location services to the user equipment via the user plane of the other domain based on the assistance information.

[0142] The data connection may be a packet data network, PDN, connection; the assistance information is utilized to reach a user plane server via the PDN connection.

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

[0144] A first domain may be configured as a Third Generation Partnership Project (3GPP) 5G system (5GS); another domain may be configured as a 3GPP Evolved Packet System (EPS).

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

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

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

[0148] The assistance information may be received from the location management function as location service user plane, LCUP, assistance information data.

[0149] The assistance information may be received from the location management function via Secure User Plane Location, SUPL, signaling.

[0150] The assistance information may be received from the location management function in a SUPL initiation message.

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

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

[0153] The first network function may be a location services user plane function.

[0154] The support information may include address information of a user plane server.

[0155] The assistance information may include at least one of: an address of a user plane server; a unique identifier of the user plane server; a location service correlation 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 to the second domain; or transport layer security assistance information for establishing a user plane connection to the second domain.

[0156] According to an eighteenth aspect, there is provided a non-transitory computer-readable medium including program instructions that cause an apparatus for a first network function located in a first domain to: determine that a user equipment receiving location services via a user plane via the first domain should be handed over from the first domain to another domain; and provide assistance information to the user equipment identifying a user plane server for providing location services to the user equipment via a user plane of the other domain after the user equipment is handed over to the second domain.

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

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

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

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

[0161] The support information may include address information of a user plane server.

[0162] The assistance information may include at least one of: an address of a user plane server; a unique identifier of the user plane server; a location service correlation 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 to the second domain; or transport layer security assistance information for establishing a user plane connection to the second domain.

[0163] According to a nineteenth aspect, a non-transitory computer-readable medium including program instructions is provided, the program instructions causing an apparatus for a first network function located in a first domain to: receive a location request for a user equipment located in the first domain; determine that the user equipment previously received location services via a user plane via another domain; and provide assistance information to the user equipment identifying a user plane server for providing location services to the user equipment via the user plane.

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

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

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

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

[0168] The support information may include address information of a user plane server.

[0169] The assistance information may include at least one of: an address of a user plane server; a unique identifier of the user plane server; a location service correlation 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 to the second domain; or transport layer security assistance information for establishing a user plane connection to the second domain.

[0170] According to a twentieth aspect, there is provided a non-transitory computer-readable medium including program instructions, the program instructions causing an apparatus for a second network function located in a first domain to: receive, from a first network function located in the first domain, assistance information identifying a user plane server for providing location services to user equipment via a user plane of another domain; and provide the assistance information to the user equipment.

[0171] The second network function may be at least one of: a location management function; or a location services user plane function.

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

[0173] The support information may include address information of a user plane server.

[0174] The assistance information may include at least one of: an address of a user plane server; a unique identifier of the user plane server; a location service correlation 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 to the second domain; or transport layer security assistance information for establishing a user plane connection to the second domain.

[0175] According to a 21st aspect, there is provided 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 was active in another domain, the assistance information identifying a user plane server for providing location services to the user equipment via the user plane of the first domain; and after a handover of the user equipment from the other domain to the first domain is performed, establishing a data connection with the user plane server for providing location services to the user equipment via the user plane of the first domain based on the assistance information.

[0176] The data connection may be a packet data network, PDN, connection; the assistance information is utilized to reach a user plane server via the PDN connection.

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

[0178] A first domain may be configured as a Third Generation Partnership Project (3GPP) 5G system (5GS); another domain may be configured as a 3GPP Evolved Packet System (EPS).

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

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

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

[0182] The assistance information may be received from the location management function as location service user plane, LCUP, assistance information data.

[0183] The assistance information may be received from the location management function via Secure User Plane Location, SUPL, signaling.

[0184] The assistance information may be received from the location management function in a SUPL initiation message.

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

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

[0187] The first network function may be a location services user plane function.

[0188] The support information may include address information of a user plane server.

[0189] The assistance information may include at least one of: an address of a user plane server; a unique identifier of the user plane server; a location service correlation 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 to the second domain; or transport layer security assistance information for establishing a user plane connection to the second domain.

[0190] According to a 22nd aspect, there is provided an apparatus for user equipment, the apparatus comprising: means for 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 was active in another domain, the assistance information identifying a user plane server for providing location services to the user equipment via the user plane of the first domain; and means for establishing a data connection with a user plane server for providing location services to the user equipment via the user plane of the first domain based on the assistance information after a handover of the user equipment from the other domain to the first domain is performed.

[0191] The data connection may be a packet data network, PDN, connection; the assistance information is utilized to reach a user plane server via the PDN connection.

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

[0193] A first domain may be configured as a Third Generation Partnership Project (3GPP) 5G system (5GS); another domain may be configured as a 3GPP Evolved Packet System (EPS).

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

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

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

[0197] The assistance information may be received from the location management function within the location service user plane, LCUP, assistance information data.

[0198] The assistance information may be received from the location management function via Secure User Plane Location, SUPL, signaling.

[0199] The assistance information may be received from the location management function in a SUPL initiation message.

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

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

[0202] The first network function may be a location services user plane function.

[0203] The support information may include address information of a user plane server.

[0204] The assistance information may include at least one of: an address of a user plane server; a unique identifier of the user plane server; a location service correlation 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 to the second domain; or transport layer security assistance information for establishing a user plane connection to the second domain.

[0205] According to a 23rd aspect, there is provided an apparatus for user equipment, the apparatus comprising: at least one processor; and at least one memory containing code that, when executed by the at least one processor, causes the apparatus to: receive 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 was active in another domain, the assistance information identifying a user plane server for providing location services to the user equipment via the user plane of the first domain; and after a handover of the user equipment from the other domain to the first domain is performed, establish a data connection with the user plane server for providing location services to the user equipment via the user plane of the first domain based on the assistance information.

[0206] The data connection may be a packet data network, PDN, connection; the assistance information is utilized to reach a user plane server via the PDN connection.

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

[0208] A first domain may be configured as a Third Generation Partnership Project (3GPP) 5G system (5GS); another domain may be configured as a 3GPP Evolved Packet System (EPS).

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

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

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

[0212] The assistance information may be received from the location management function within the location service user plane, LCUP, assistance information data.

[0213] The assistance information may be received from the location management function via Secure User Plane Location, SUPL, signaling.

[0214] The assistance information may be received from the location management function in a SUPL initiation message.

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

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

[0217] The first network function may be a location services user plane function.

[0218] The support information may include address information of a user plane server.

[0219] The assistance information may include at least one of: an address of a user plane server; a unique identifier of the user plane server; a location service correlation 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 to the second domain; or transport layer security assistance information for establishing a user plane connection to the second domain.

[0220] According to a 24th aspect, there is provided an apparatus for user equipment, the apparatus comprising: a receiving circuit for 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 was active in another domain, the assistance information identifying a user plane server for providing location services to the user equipment via a user plane of the first domain; and an establishing circuit for establishing a data connection with a user plane server for providing location services to the user equipment via a user plane of the first domain based on the assistance information after a handover of the user equipment from the other domain to the first domain is performed.

[0221] The data connection may be a packet data network, PDN, connection; the assistance information is utilized to reach a user plane server via the PDN connection.

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

[0223] A first domain may be configured as a Third Generation Partnership Project (3GPP) 5G system (5GS); another domain may be configured as a 3GPP Evolved Packet System (EPS).

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

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

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

[0227] The assistance information may be received from the location management function within the location service user plane, LCUP, assistance information data.

[0228] The assistance information may be received from the location management function via Secure User Plane Location, SUPL, signaling.

[0229] The assistance information may be received from the location management function in a SUPL initiation message.

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

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

[0232] The first network function may be a location services user plane function.

[0233] The support information may include address information of a user plane server.

[0234] The assistance information may include at least one of: an address of a user plane server; a unique identifier of the user plane server; a location service correlation 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 to the second domain; or transport layer security assistance information for establishing a user plane connection to the second domain.

[0235] According to a twenty-fifth aspect, there is provided a non-transitory computer-readable medium including program instructions, the program instructions causing an apparatus for user equipment to: receive 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 was active in another domain, the assistance information identifying a user plane server for providing location services to the user equipment via the user plane of the first domain; and after a handover of the user equipment from the other domain to the first domain is performed, establishing a data connection with the user plane server for providing location services to the user equipment via the user plane of the first domain based on the assistance information.

[0236] The data connection may be a packet data network, PDN, connection; the assistance information is utilized to reach a user plane server via the PDN connection.

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

[0238] A first domain may be configured as a Third Generation Partnership Project (3GPP) 5G system (5GS); another domain may be configured as a 3GPP Evolved Packet System (EPS).

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

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

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

[0242] The assistance information may be received from the location management function within the location service user plane, LCUP, assistance information data.

[0243] The assistance information may be received from the location management function via Secure User Plane Location, SUPL, signaling.

[0244] The assistance information may be received from the location management function in a SUPL initiation message.

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

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

[0247] The first network function may be a location services user plane function.

[0248] The support information may include address information of a user plane server.

[0249] The assistance information may include at least one of: an address of a user plane server; a unique identifier of the user plane server; a location service correlation 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 to the second domain; or transport layer security assistance information for establishing a user plane connection to the second domain.

[0250] According to a twenty-sixth aspect, there is provided a computer program product stored on a medium capable of causing an apparatus to perform any of the methods described herein.

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

[0252] According to a twenty-ninth aspect, there is provided a chipset that may comprise an apparatus as described herein.

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

[0254] [Figure 1A] 1 is a schematic diagram of a 5G system. [Figure 1B] 1 is a schematic diagram of a 5G system. [Figure 2] FIG. 1 is a schematic diagram of a network device. [Figure 3] FIG. 1 is a schematic diagram of a user equipment. [Figure 4] 1 is a schematic diagram of a non-volatile memory medium storing instructions that, when executed by a processor, enable the processor to perform one or more of the steps of some example methods. [Figure 5] FIG. 1 is a schematic diagram of a network. [Figure 6A] FIG. 1 illustrates exemplary signaling. [Figure 6B] FIG. 1 illustrates exemplary signaling. [Figure 7A] FIG. 1 illustrates exemplary signaling. [Figure 7B] FIG. 1 illustrates exemplary signaling. [Figure 8] 10A-10C illustrate example operations that may be performed by the devices described herein. [Figure 9] 10A-10C illustrate example operations that may be performed by the devices described herein. [Figure 10] 10A-10C illustrate example operations that may be performed by the devices described herein. [Figure 11] 10A-10C illustrate example operations that may be performed by the devices described herein. [Figure 12] 10A-10C illustrate example operations that may be performed by the devices described herein. DETAILED DESCRIPTION OF THE INVENTION

[0255] For brevity and clarity, these aspects are described below with reference to 5G wireless communication systems and Evolved Packet Systems (EPS), but it will be understood that these aspects are not limited to these wireless communication systems and may also be applied, for example, to other wireless communication systems (e.g., current 6G proposals, IEEE 802.11, etc.).

[0256] Before describing these examples in detail, some general principles of 5G wireless communication systems will be briefly described with reference to Figures 1A and 1B.

[0257] 1A shows a schematic diagram of a 5G system (5GS) 100. The 5GS may comprise a user equipment (UE) 102 (which may also be referred to as a communications device or terminal), a 5G access network (AN) (which may be a 5G radio access network (RAN) or any other type of 5G AN, e.g., a non-3GPP interworking function (N3IWF) / trusted non-3GPP gateway function (TNGF) for untrusted / trusted non-3GPP access, or a wireline access gateway function (W-AGF) for wireline access) 104, a 5G core (5GC) 106, one or more application functions (AFs) 108, and one or more data networks (DNs) 110.

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

[0259] The 5GC 106 may comprise one or more Access and Mobility Management Functions (AMFs) 112, one or more Session Management Functions (SMFs) 114, one or more Authentication Server Functions (AUSFs) 116, one or more Unified Data Management (UDM) Functions 118, one or more User Plane Functions (UPFs) 120, one or more Unified Data Repository (UDR) Functions 122, one or more Network Repository Functions (NRFs) 128, and / or one or more Network Exposure Functions (NEFs) 124. The role of the NEFs is to provide secure opening of network services (e.g., voice, data connectivity, charging, subscriber data, etc.) to third parties. While the interfaces of the NRF 128 are not shown for clarity, it is understood that the NRF 128 may have multiple interfaces with other network functions.

[0260] The 5GC 106 also includes a network data analysis function (NWDAF) 126. The NWDAF is responsible for providing network analysis information in response to requests from one or more network functions or devices within the network. A network function may also subscribe to and receive information from the NWDAF 126. 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 based on at least one subscription to events provided by at least one network function.

[0261] The network may further comprise 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 including, for example, load levels and / or resource utilization. For example, an MDAS MnS producer for 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 forecast of resource usage information for a predefined future time frame. This analysis may also recommend appropriate actions, such as resource scaling, admission control, traffic load balancing, etc.

[0262] Figure 1B shows a schematic diagram of 5GC as defined in current 3GPP specifications. This architecture is intended to illustrate potential components that may be included in a core network, and it will be understood that the principles described herein are not limited to core networks with only the components described.

[0263] 1B shows a 5G Core 106' comprising 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 interconnection medium that also connects these network functions to each other. The 5G Core 106' further comprises a Network Repository Function (NRF) 133' and Network Function 134' that connect to this interconnection medium.

[0264] 3GPP has issued several Releases (Rel. 18) to define operational communication protocols related to communication networks. Specific objectives and functions are set out in relation to Release 18 (Rel. 18).

[0265] Another exemplary network is an Evolved Packet System (EPS). UEs communicate with an Evolved Packet Core (EPC) via base stations (e.g., eNBs), which can signal to a Serving Gateway (SGW) and a Mobility Management Entity (MME).

[0266] The MME is the main control node for the LTE access network. It is involved in the bearer activation / deactivation process and is also responsible for selecting the serving gateway for the UE during initial attach and intra-LTE handovers involving relocation of the core network (CN) node.

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

[0268] 3GPP is working on use cases, technical requirements, and corresponding enhancements as part of the ongoing Rel-18 enhancements. At least one of these key challenges relates to how to address continuity of location services given UE mobility.

[0269] 3GPP defines the handling of ongoing services / sessions during mobility for specific use cases (e.g., voice calls or data sessions). In particular, the handling of location services (LCS) during mobility procedures is defined in the 3GPP standards in relation to control plane procedures. Specific proposals consider providing LCS sessions on the user plane to provide location services. However, no work has been done on how such user plane LCS sessions are affected as a result of a UE being handed off from a first network domain to a second network domain. Therefore, it is unclear whether ongoing LCS sessions on the user plane should be terminated or maintained after a mobility-based event. Furthermore, if an LCS session is continued, how that continuity works is also undefined.

[0270] There are several implications associated with this.

[0271] For example, an LCS session may be terminated in response to a mobility event, in which case the LCS client must resume the session after a procedure, which results in additional network signaling, which may be considered an inefficient use of overhead resources for certain use cases.

[0272] Furthermore, the Location Management Function (LMF) may not be aware of any movement-based events, which may lead to inaccurate location estimates for moving UEs.

[0273] Furthermore, the lack of a clear specification can lead to cross-vendor testing failures when network functions from different vendors make different assumptions about whether another network function supports LCS session continuity. For example, vendor 1's AMF may operate with the expectation that continuity should work, but vendor 2's LMF may not support continuity.

[0274] Additionally, LCS sessions may be enabled as part of other critical services (e.g., emergency calls), which may be affected by a lack of reliability, which could lead to regulatory issues.

[0275] The present application recognizes that at least one of the aforementioned problems can be alleviated by providing a mechanism for handling LCS sessions on the user plane for different mobility procedures. In particular, the present application recognizes that it may be useful to specify how LCS session continuity can be provided in the event of a mobility-based event.

[0276] Below is provided exemplary signaling that may be implemented by the entities described herein, which are discussed, by way of example, in the context of Evolved Packet Systems (EPS) and 5G Systems (5GS).

[0277] 6A and 6B show example signaling that may be performed when a UE moves from a 5GS to an evolved packet system. The operations of FIG. 6B may be performed after the operations of FIG. 6A.

[0278] 6A and 6B illustrate signaling that may take place between a UE 601, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) 602, a Next Generation Radio Access Network (NG_RAN) 603, an MME 604, an AMF 605, an Evolved Serving Mobile Location Center (E_SML C) 606 (a location function located within the EPS), a Location Management Function Location Services User Plane (LMF_LCUP) 607, a Gateway Mobile Location Center (GMLC) 608, and an LCS Client 609.

[0279] It is understood that LMF_LCUP refers to an LCS service function implemented by the LMF, although the description is not limited thereto. As used herein, the term "LCUP" can refer to a network element or network function for location services on the user plane, which can correspond, for example, to the user plane portion of the LMF or the Secure User Plane Location (SUPL) platform defined in the Open Mobile Alliance (OMA) specifications. The LCUP function can handle location operations on the user plane and can be used with an associated LMF, for example, to enhance location services on the control plane. The LMF and the associated LCUP can be located in the same area, for example, co-located with each other, or can communicate via an interface or implementation-specific operations. Additionally or alternatively, the LMF and the associated LCUP can also support similar location methods so that they can be compatible with each other.

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

[0281] At 6001, an LCS session is established for UE 601 on the 5G user plane.

[0282] At 6002, the NG_RAN 603 determines that a handover should be performed to handover the UE 601 from 5GS to EPS. This determination may be made based on any of a number of factors. For example, this determination may be made based on (e.g., in response to) a determination that the UE 601 may obtain a better quality of service and / or quality of experience with another network.

[0283] At 6003, based on the determination of 6002, the NG_RAN 603 signals to the AMF 605. This signaling of 6003 may request that the UE 601 be handed over from 5GS to EPS.

[0284] At 6004, based on the signaling of 6003, the AMF 605 signals a relocation request for the UE 601 to the MME 604. The relocation request indicates that the UE 601 should be handed over from 5GS to EPS.

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

[0286] In 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 activated an LCS session when the AMF 605 previously requested that the LMF provide the location for this UE 601. This location request may provide the AMF with an LCS correlation identifier. Furthermore, the AMF 605 may determine that a given UE activated an LCS session when the LMF signaled information to the AMF 605 (which may be forwarded to the radio access network and / or the UE) that included the same LCS correlation identifier that the AMF 601 previously sent. This allows the AMF 605 to remain aware of whether a user plane LCS session is active for the UE 601.

[0287] Based on this determination, the AMF 605 may decide to provide the UE 601 with information regarding the UE's LCS user plane assistance (e.g., Internet Protocol (IP address or FQDN), etc.). Examples of assistance information are provided further below. This assistance information may be signaled to the UE in any of several different ways.

[0288] For example, the AMF 605 may provide the assistance information to the UE 601 by signaling the assistance information directly to the UE 601 using a non-access stratum (NAS) signaling procedure. This is represented in Figure 6A as 6007. The example signaling of 6007 may be achieved by signaling LCUP assistance data to the UE 601.

[0289] The LCUP assistance information can be received in many different ways. In some examples, this assistance data can be signaled using the NAS:DL-NAS-Transport service operation.

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

[0291] 6008a-6009a show exemplary information in which the AMF 605 indirectly provides assistance information to the UE 601 via the LMF_LCUP 607, and the LMF_LCUP 607 signals the assistance information to the UE using LPP.

[0292] In 6008a, the AMF 605 signals to the LMF_LCUP 607. The LMF_LCUP 607 may signal the assistance information to the UE 601 based on this signal from the AMF 605 in 6008a. This signal may, for example, trigger the LMF_LCUP 607 to signal the assistance information to the UE 601. This signaling in 6008a may include an Nlmf_Location_Prepare_Transfer service operation.

[0293] At 6009a, the LMF_LCUP 607 signals to the UE 601. This signaling may include the LCUP assistance data described above. This signaling may be performed using LPP service operations.

[0294] 6008b-6009b show exemplary information in which the AMF 605 indirectly provides assistance information to the UE 601 via the LMF_LCUP 607, and the LMF_LCUP 607 signals the assistance information to the UE using SUPL.

[0295] In 6008b, the AMF 605 signals to the LMF_LCUP 607. The LMF_LCUP 607 may signal the assistance information to the UE 601 based on this signal from the AMF 605 in 6008b. This signal may, for example, trigger the LMF_LCUP 607 to signal the assistance information to the UE 601. This signaling in 6008b may include an Nlmf_Location_Prepare_Transfer service operation.

[0296] At 6009b, LMF_LCUP 607 signals to UE 601. This signaling may include a SUPL-INIT service operation.

[0297] Once the assistance information has been provided to the UE via at least one of 6007 through 6009b, the AMF 605 signals a handover command for the UE 601 to the NG_RAN 603 at 6010. The handover command may indicate that the UE 601 should be handed over from 5GS to EPS. The handover command may be signaled using HO_Command signaling.

[0298] At 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.

[0299] In 6012, after the handover of UE 601 to EPS is completed, UE 601 interfaces with the user plane location server using the PDN connection corresponding to the PDU session it was using on 5GS and communicates with the user plane location server having the address provided to the UE in 6007, 6009a, and / or 6009b.

[0300] 6013 to 6014 relate to AMF 605 canceling a pre-configured LCS session in 5GS.

[0301] In 6013, the AMF 605 signals to the LMF_LCUP 607. This signaling in 6013 indicates that the location service session should be canceled in 5GS. This signaling can be done, for example, using the Nlmf_Location_CancelLocation_Request service mechanism.

[0302] At 6014, the user plane LCS session is cancelled.

[0303] At 6015, the AMF 605 signals to the GMLC 608. This signaling at 6015 may provide an indication to the GMLC 608 that the UE 601 has been handed over from 5GS to EPS. This signaling at 6015 may additionally provide the GMLC 608 with an identifier for the UE 601, an indication that there was an LCS session failure, and / or an identifier of the MME 604. The signaling at 6015 may be done, for example, using the Namf_Location_ProvidePositioningInfo Resp service operation.

[0304] 6016 and 6017 relate to an entity on the EPS being requested to provide a location element for the UE 601.

[0305] At 6016, the GMLC 608 signals to the MME 604. This signaling at 6016 may request that the MME 604 provide the GMLC 608 with a location estimate for the location of the UE 601. This signaling may include an identifier for the UE 601 (such as the identifier provided in 6015). This signaling may include an indication of the quality of service (QoS) associated with the requested LCS. The indication of quality of service (QoS) and UE identity sent to the MME may correspond to an EPS translation of the parameters sent to the AMF.

[0306] In 6017, the MME 604 signals to the E_SML C 606. This signaling may include a request for the location of the UE 601. This signaling in 6017 may include the identifier of the UE 601 provided in 6016. This signaling in 6017 may include the QoS included in the signaling in 6016.

[0307] At 6018, an LCS session is established on the EPC user plane. In particular, taking into account the PDN connection to the user plane server, the E-SMLC 606 chooses to conduct the LCS session using user plane data. OMA-SUPL (not shown) may also be involved at 6018 on the EPS side. The process of 6018 may provide the E_SMLC 606 with a location estimate for the UE 601.

[0308] At 6019, the E-SMLC 606 signals to the MME 604. This signaling provides the MME 604 with a location estimate for the UE 601. This signaling may include the identifier of the UE 601 provided at 6017.

[0309] At 6020, the MME 604 signals to the GML-C 608. This signaling at 6020 may include a location estimate at 6019. This signaling at 6020 may include an identifier for the UE 601.

[0310] In 6021, the GML-C 608 signals to the LCS client 609. This signaling in 6021 may include the location estimate in 6020. This signaling in 6021 may include an identifier for the UE 601.

[0311] The location estimation discussed above may be in accordance with what is specified in the EPS specifications. For example, providing the UE with information 6007 to 6009b (inclusive) does not affect how subsequent location is provided via EPS. Furthermore, the LCS client is unaware of any UE mobility handling, and LCS session continuity is maintained.

[0312] However, SUPL can be indicated as being used on both the EPS and 5GS sides to allow reuse of user plane sessions, which simplifies signaling in the UE and 5G core.

[0313] The assistance information mentioned above may include: an identifier and / or address for a user plane server for the UE (e.g., an IP address and / or 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 (location) user plane server; and / or assistance data for assisting signaling between the UE and the (location) user plane server. For example, the assistance information provides the UE with information to be used when the UE is in EPS and when the UE is in 5GS.

[0314] Alternatively, or in addition, the LCUP instance assistance information may include security information for establishing a user plane (UP) session between the 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 secure user plane connection. The TLS attribute information may correspond, for example, to a key to be used as a pre-shared key to secure a TLS link between the UE and the LCUP, which may 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 initiates the session with a SUPL Position Initialization (POS INIT) message to initiate a positioning protocol session.

[0315] In some examples, the LCUP instance assistance information may alternatively or additionally include correlation information regarding an ongoing control plane location procedure. The correlation information includes information used to correlate an ongoing control plane location procedure with a user plane connection to further ensure the security of the user plane connection. A network element such as an LMF may also assign a correlation identifier to a location request as correlation information, which may include, for example, an LMF address and a location request identifier. The LMF may also provide the correlation identifier to the terminal device as part of the LCUP assistance information on the control plane, for example, via LTE Positioning Protocol (LPP) signaling. In operations subsequent to establishing a user plane connection between the terminal device and the LUCP, the correlation identifier may be used to correlate an ongoing control plane location procedure with the user plane connection, as described below.

[0316] The LCUP support information may further include information about ports in the LCUP function instance, for example, Transmission Control Protocol (TCP) or Uniform Datagram Protocol (UDP) ports in the LCUP. Additionally or alternatively, the LCUP support information may also include information about location methods or protocols that the LCUP function instance supports.

[0317] The UE can store the received assistance information and initiate a PDN connection after the user equipment is handed over to the EPS, or can use the PDU session handed over to the EPS as a PDN connection to access the (location) user plane server with the access information received in the assistance data address / identifier. The UE can initiate a Domain Name Service (DNS) query to a DNS server to obtain the address for the user plane server when an FQDN is provided in the assistance data. The UE establishes this connection with the user plane server autonomously (e.g., without receiving a trigger from the LTE / EPS network) once a connection is established over LTE. This can ensure that impacts on the LTE network are avoided in certain use cases.

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

[0319] 7A and 7B illustrate how the techniques currently described herein can be applied when user equipment moves from EPS to 5GS. The operations of FIG. 7B can be performed after the operations of FIG. 7A.

[0320] 7A and 7B show signaling that may be performed by a UE 701, an E-UTRAN 702, an NG-RAN 703, an AMF 704, an E_SML C 705, an LMF_LCUP 706, an NRF 707, an MNE 708, a GMLC 709, and an LCS client 710.

[0321] At 7001, an LCS session is established on the user plane of the EPS.

[0322] At 7002, the E-UTRAN 702 determines that the UE should be handed over from EPS to 5GS.

[0323] At 7003, based on the determination of 7002, the E-UTRAN 703 signals to the MME 708. This signaling at 7003 indicates that a handover is requested to handover the UE from EPS to 5GS.

[0324] At 7004, the E-UTRAN 702 detects a currently established LCS user plane session for the UE 701. This LCS user plane session can be detected by the E-UTRAN 702 monitoring the use of an LCS correlation identifier associated with the UE 701 as signaled via the E-UTRAN 702.

[0325] At 7005, the MME 708 signals to the AMF 704. This signaling at 7005 includes an indication that the UE 701 is being handed over from EPS to 5GS. This signaling at 7005 includes an indication that an existing user plane-based LCS session was active in the EPS for the UE 701. As described above, the AMF 605 can recognize the existence of an active LCS session for a given UE on 5GS from receiving a location service correlation identifier. In this case, the MME 708 can similarly recognize the existence of an active LCS session for the UE 701 by receiving and / or transmitting signaling including a similar correlation identifier. Thus, the MME 708 can recognize the LCS session state without designated signaling to the MME 708 for this purpose. For example, an LCS user plane session may be detected by the MME 708 by monitoring the use of an LCS correlation identifier associated with the UE 701 as signaled via the MME 708.

[0326] At 7006, the MME 708 responds to the signaling of 7005.

[0327] At 7007, the MME 708 signals to the E-UTRAN 702. This signaling may include a handover command to have the E-UTRAN handover the UE 701 to the NG_RAN 702.

[0328] At 7008, the NG_RAN 703 signals to the AMF 704. This signaling may inform the AMF that the handover of the UE 701 to the NG-RAN has been performed.

[0329] 7009 to 7012 relate to the cancellation of an LCS session within an EPS network.

[0330] At 7009, the MME 708 signals to the E_SML C 705. This signaling at 7009 includes an instruction to cancel the LCS session in the EPS network.

[0331] At 7010, the user plane LCS session is canceled within the EPS network.

[0332] In 7011, the MME 708 signals to the GMLC 709. This signaling of 7011 may include a location 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 for the AMF 704 (or some other identifier that can be used to obtain an address for the address for the AMF 704).

[0333] In 7012, the GMLC 709 signals an identifier of the AMF 704 in signaling 7011. This signaling 7012 may request the location of the UE 701. This signaling 7012 may include the identifier for the UE 701 provided in 7011. The signaling 7012 may include an indication of quality of service for the LCS session.

[0334] In 7013, the AMF 704 determines whether the AMF 704 has previously received information about an LCS session on the user plane. For example, the AMF 704 determines whether the AMF 704 has previously received signaling 7005 from the MME 708.

[0335] Based on the AMF 704 determining that the AMF has previously received the LCS session information, the AMF 704 provides the address of an LCS user plane server to the UE 701. This provisioning may occur via 7014, and / or via 7015a and 7016a, and / or via 7015b and 7016b, which are further described below.

[0336] At 7014, the AMF 704 signals to the UE 701. This signaling at 7014 may include LCUP assistance data. The LCUP assistance data may be as described above in connection with Figures 6A and 6B.

[0337] At 7015a, the AMF 704 signals to the LMF_LCUP 706. This signaling at 7015a may include a request to the LMF_LCUP to provide LCUP assistance data to the UE 701. This signaling at 7015a may include an identifier for the UE 701. This signaling at 7015a may include an LCS correlation identifier associated with the UE 701. This signaling at 7015a may include an indication of QoS for the LCS session received at 7012. This signaling at 7015a may include an indication that a user plane LCS session associated with the UE 701 exists.

[0338] At 7016a, the LMF_LCUP 706 signals to the UE 701. This signaling at 7016a provides LCUP assistance data to the UE 701. This signaling at 7016a may be provided using LPP.

[0339] At 7015b, the AMF 704 signals to the LMF_LCUP 706. This signaling in 7015b may include a request to the LMF_LCUP to provide LCUP assistance data to the UE 701. This signaling in 7015b may include an identifier for the UE 701. This signaling in 7015b may include an LCS correlation identifier associated with the UE 701. This signaling in 7015b may include an indication of QoS for the LCS session received in 7012. This signaling in 7015b may include an indication that a user plane LCS session associated with the UE 701 exists.

[0340] At 7016b, the LMF_LCUP 706 signals to the UE 701. This signaling at 7016b provides LCUP assistance data to the UE 701. This signaling at 7016b may be provided using OMA-SUPL.

[0341] At 7017, a user plane LCS session is established over the 5GS.

[0342] In 7018, the LMF_LCUP 706 signals to the AMF 704. This signaling of 7018 may include a location estimate for the UE 701. This signaling of 7018 may include an identifier for the UE 701. This signaling of 7018 may include an LCS correlation identifier of 7016a or 7016b. This signaling of 7018 may include an Nlmf_Location_DetermineLocationResponse service operation. This signaling of 7018 may be signaled based on the signaling of 7015.

[0343] At 7019, the AMF 704 signals to the GLMC 709. This signaling may include the location estimate provided in 7018. This 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 response service operation.

[0344] At 7020, the GMLC 709 signals to the LCS client 710. This signaling at 7020 may include the location estimate provided at 7019. This signaling may include the identifier of the UE 701 provided in the signaling at 7019.

[0345] In this example of Figures 7A and 7B, the LMF may choose to have an LCS session on the user plane based on receiving an indication from the AMF. Alternatively, or in addition, the LMF may choose to have an LCS session on the user plane based on an internal configuration of the LMF.

[0346] In both of the above examples of Figures 6A-6B and 7A-7B, the user plane connection from the UE is treated like any other packet data unit (PDU) session to help maintain LCS over the user plane session and remains active during movement.

[0347] However, SUPL is shown as being used on both the EPS and 5GS sides to allow for reuse, which simplifies signaling in the UE and 5G core.

[0348] The assistance information mentioned 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 to assist in establishing a secure (e.g., TLS) connection between the UE and the user plane (location) server; and / or assistance data to assist in signaling between the UE and the (location) user plane server. In some examples, the assistance information provides the UE with information to be used when the UE is in 5GS.

[0349] The aforementioned assistance information may include at least one of: 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 secure (e.g., TLS) connection between the UE and the (location) user plane server; and / or assistance data for assisting signaling between the UE and the (location) user plane server. In some examples, the assistance information provides the UE with information to be used by the UE in EPS when the UE is in 5GS.

[0350] Alternatively or additionally, the LCUP instance assistance information may 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 (TLS) attribute information for establishing a secure user plane connection. The TLS attribute information may correspond, for example, to a key to be used as a pre-shared key for securing a TLS link between the UE and the LCUP, which may 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 initiates a session with a SUPL Position Initialization (POS INIT) message to initiate a positioning protocol session.

[0351] In some examples, the LCUP instance assistance information may alternatively or additionally include correlation information regarding an ongoing control plane location procedure. The correlation information includes information used to correlate an ongoing control plane location procedure with a user plane connection to further ensure the security of the user plane connection. A network element such as an LMF may also assign a correlation identifier to a location request as correlation information, which may include, for example, an LMF address and a location request identifier. The LMF may also provide the correlation identifier to the terminal device as part of the LCUP assistance information on the control plane, for example, via LTE Positioning Protocol (LPP) signaling. In operations subsequent to establishing a user plane connection between the terminal device and the LUCP, the correlation identifier may be used to correlate an ongoing control plane location procedure with the user plane connection, as described below.

[0352] The LCUP support information may further include information about ports in the LCUP function instance, for example, Transmission Control Protocol (TCP) or Uniform Datagram Protocol (UDP) ports in the LCUP. Additionally or alternatively, the LCUP support information may also include information about location methods or protocols that the LCUP function instance supports.

[0353] The UE can 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 UE is provided with the FQDN, it can initiate a Domain Name Service (DNS) query to a DNS server to obtain the address of the user plane server. Once the UE establishes a connection over LTE, it establishes this connection to the user plane server autonomously (e.g., without receiving a trigger from the LTE / EPS network). This ensures that there is no impact on the LTE network.

[0354] 8 to 12 show embodiments of the above example of FIGS. 6A to 7B.

[0355] FIG. 8 relates to operations that may be performed by user equipment.

[0356] At 801, a user equipment receives, when the user equipment is located in a first domain, assistance information from a first network function located in the first domain that identifies a user plane server that provides location services for the user equipment on a user plane of another domain.

[0357] At 802, after a handover of the user equipment from a first domain to another domain is performed, the user equipment establishes a data connection with a user plane server for providing location services to the user equipment on a user plane of the other domain based on the assistance information.

[0358] These operations may be performed when the user equipment is being handed over from a first domain to another domain.

[0359] The data connection may be a packet data network, PDN, connection; the assistance information is utilized to reach a user plane server via the PDN connection.

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

[0361] A first domain may be configured as a Third Generation Partnership Project (3GPP) 5G system (5GS); another domain may be configured as a 3GPP Evolved Packet System (EPS).

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

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

[0364] The assistance information may be received from the location management function via Long Term Evolution Positioning Protocol, LPP, signaling.

[0365] The assistance information may be received from the location management function within the location service user plane, LCUP, assistance information data.

[0366] The assistance information may be received from the location management function via Secure User Plane Location, SUPL, signaling.

[0367] The assistance information may be received from the location management function in a SUPL initiation message.

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

[0369] The first network function may be a location management function.

[0370] The first network function may be a location services user plane function.

[0371] After establishing the data connection, the user equipment can use this data connection to transmit data, which can be used to provide location services to the user equipment on the user plane of another domain.

[0372] FIG. 9 illustrates operations that may be performed by an apparatus for user equipment.

[0373] In 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 was active in another domain, the assistance information identifying a user plane server for providing location services for the user equipment via the user plane of the first domain. This indication may have been previously transmitted from the MME to the AMF.

[0374] At 902, after a handover of the user equipment from another domain to the first domain is performed, the user equipment establishes a data connection with a user plane server for providing location services to the user equipment via a user plane of the first domain based on the assistance information.

[0375] These operations of FIG. 9 may be performed when a user equipment is being handed over from another domain to a first domain.

[0376] The data connection may be a packet data network, PDN, connection; the assistance information is utilized to reach a user plane server via the PDN connection.

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

[0378] A first domain may be configured as a Third Generation Partnership Project (3GPP) 5G system (5GS); another domain may be configured as a 3GPP Evolved Packet System (EPS).

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

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

[0381] The assistance information may be received from the location management function via Long Term Evolution Positioning Protocol, LPP, signaling.

[0382] The assistance information may be received from the location management function as location service user plane, LCUP, assistance information data.

[0383] The assistance information may be received from the location management function via Secure User Plane Location, SUPL, signaling.

[0384] The assistance information may be received from the location management function in a SUPL initiation message.

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

[0386] The first network function may be a location management function.

[0387] The first network function may be a location services user plane function.

[0388] After establishing the data connection, the user equipment can use the data connection to transmit data, and the data connection can be used to provide location services to the user equipment via the user plane of the first domain.

[0389] Figure 10 illustrates operations that may be performed by a first network function located in a first domain. The first network function may correspond to the first network function described above in relation to Figures 8 and / or 9.

[0390] At 1001, a first network function determines that a user equipment receiving location services over a user plane via a first domain should be handed over from the first domain to another domain.

[0391] At 1002, a first network function provides assistance information to a user equipment to identify a user plane server for providing location services to the user equipment via a user plane of another domain after the user equipment is handed over to a second domain.

[0392] The determination that the user equipment should be handed over is made based on receiving a handover indication from a mobility management entity.

[0393] Figure 11 illustrates operations that may be performed by a first network function located in a first domain. The first network function may correspond to the first network function described above in relation to Figures 8 and / or 9.

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

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

[0396] At 1101, a first network function receives a location request for a user equipment located within a first domain.

[0397] At 1102, a first network function determines that the user equipment previously received location services via a user plane via another domain.

[0398] At 1103, the first network function provides the user equipment with assistance information identifying a user plane server for providing location services to the user equipment via a user plane. If the UE is handed over from a first domain to a second domain, the user plane may be a user plane of another domain. If the user equipment is handed over from another domain to the first domain, the user plane may be located in the first domain.

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

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

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

[0402] Figure 12 shows operations that may be performed by a second network function located in the first domain. The second network function may interact with at least one of the devices of Figures 10 and 11 to forward assistance information to a user equipment. The user equipment may be the user equipment of Figure 8 or Figure 9, or some other user equipment.

[0403] At 1201, a second network function receives, from a first network function located in a first domain, assistance information identifying a user plane server for providing location services to user equipment via a user plane of another domain.

[0404] At 1202, a second network function provides assistance information to the user equipment.

[0405] The second network function may be at least one of: a location management function; or a location services user plane function.

[0406] In the examples of Figures 10 to 12, the first network function may be an access and mobility function.

[0407] In the examples of Figures 8 to 12, the assistance information function may include address information of a user plane server.

[0408] In the examples of Figures 8 to 12, the assistance information function may include at least one of: an address of a user plane server; a unique identifier of the user plane server; a location service correlation 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 assistance information for establishing a user plane connection in the second domain.

[0409] In the above examples of Figures 8 through 12, a first domain can be 5GS and another domain can be EPS. Alternatively, a first domain can be EPS and a second domain can be 5GS.

[0410] The above examples show that in the specific case of moving between 5GS and EPS, the mechanism may be asymmetric with respect to the direction in which the user equipment moves.

[0411] For example, in the case of a move from 5GS to EPS, EPS-related assistance information can be provided in 5GS, and the UE being handed over to EPS can use this information after moving to EPS.

[0412] When the UE is moved in the opposite direction (i.e., the UE is handed over from EPS to 5GS), no assistance information is provided to the UE while it is located in the EPS. This can help minimize the impact on the EPS. However, an optional indication is provided from the MME to the AMF that can indicate the existence of such LCS / UP sessions in the EPS that were used by the UE while it was located in the EPS for location services. The AMF can choose to use it based on (or based on) the LMF configuration to initiate an LCS / user plane session in 5GS.

[0413] A possible change request showing how the above example could be reflected in the current specification is provided in Appendix A.

[0414] FIG. 2 illustrates an example of a control device for a communication system, where the control device is to be coupled to and / or for controlling a station of an access system such as a RAN node, e.g., a base station, a gNB, a central unit of a cloud architecture or a node of a core network, e.g., an MME or S-GW, a scaling entity such as a spectrum management entity, or a server or host, e.g., an apparatus hosting an NRF, an NWDAF, an AMF, an SMF, or a UDM / UDR. The control device can be integrated with a node or module of the core network or RAN, or can be located outside thereof. In some examples, a base station comprises a separate control device unit or module. In other examples, the control device can be another network element, such as a radio network controller or a spectrum controller. The control device 200 can be arranged to provide control over communications within a coverage area of ​​the system. The device 200 comprises at least one memory 201, at least one data processing unit 202, 203, and an input / output interface 204. The control device can be coupled to a receiver and a transmitter of the device via the interface. The receiver and / or transmitter can be implemented as a radio front end or a remote radio head. For example, the controller 200 or processor 201 may be configured to execute appropriate software code to provide the control functionality.

[0415] Possible wireless communication devices are now described in more detail with reference to FIG. 3 , which illustrates a schematic, partial cross-sectional view of a communication device 300. Such communication devices are often referred to as user equipment (UE) or terminals. Suitable mobile communication devices can be provided by any device capable of transmitting and receiving radio signals. Non-limiting examples include mobile stations (MS) or mobile devices, such as mobile phones or "smartphones," computers equipped with wireless interface cards or other wireless interface mechanisms (e.g., USB dongles), personal data assistants (PDAs) or tablets equipped with wireless communication capabilities, or any combination thereof. Mobile communication devices can provide communication of data, for example, to convey voice, electronic mail (email), text messages, multimedia, and other communications. Thus, users can be provided with and offered numerous services via their communication devices. Non-limiting examples of these services include two-way or multi-way calls, data communication or multimedia services, or simply access to a data communication network system such as the Internet. Users can also be offered broadcast or multicast data, non-limiting examples of which content include downloads, television and radio programs, videos, advertisements, various alerts, and other information.

[0416] A wireless communication device may, for example, be a mobile device, i.e., a device that is not fixed to a particular location, or may be a 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.

[0417] The wireless device 300 can receive signals via an air or radio interface 307 via suitable equipment for reception and can transmit signals via suitable equipment for transmitting radio signals. In Figure 3, a transceiver unit is generally designated by block 306. The transceiver unit 306 can be provided, for example, by a radio part and an associated antenna arrangement. The antenna arrangement can be located internal or external to the wireless device.

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

[0419] FIG. 4 shows a schematic diagram of non-volatile memory media 400a (e.g., a computer 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, enable the processor to perform one or more of the steps of the method of FIG. 8 and / or FIG. 9 and / or FIG. 10 and / or FIG. 11 and / or FIG. 12 and / or methods described elsewhere above.

[0420] As provided herein, various aspects are described in the detailed description of examples and in the claims. Generally, some examples may be implemented in hardware or special purpose 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 may be executed by a controller, microprocessor, or other computing device, but examples are not limited thereto. While various examples may be shown and described as block diagrams, flowcharts, or using some other graphical representation, it will be appreciated that these blocks, apparatus, systems, techniques, or methods described herein may be implemented in, by way of non-limiting example, hardware, software, firmware, special purpose circuits or logic, general-purpose hardware or controller, or other computing device, or any combination thereof.

[0421] These examples may be implemented by computer software stored in a memory and executable by at least one data processor of the relevant entity, or by hardware, or by a combination of software and hardware. Further, in this regard, it should be noted that any procedures described above, e.g., in Figures 8 and / or 9 and / or 10 and / or 11 and / or 12, and / or elsewhere, may represent program steps, or interconnected logic circuits, blocks, and functions, or a combination of program steps and logic circuits, blocks, and functions. Software may be stored on physical media, such as memory chips or blocks embodied within a processor, magnetic media (such as hard disks or floppy disks), and optical media (e.g., DVDs and their data variants, CDs, etc.).

[0422] The memory may be of any type suitable for the local technology 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 technology environment and may include, by way of non-limiting examples, one or more of 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.

[0423] Additionally or alternatively, some examples may be implemented using circuitry that may be configured to perform one or more of the functions and / or method steps described above, and that may be provided in a base station and / or a communication device and / or a core network entity.

[0424] As used in this application, the term "circuit" may refer to one or more or all of the following: (a) Hardware-only circuit implementations (e.g., analog and / or digital circuit-only implementations); (b) Combinations of hardware circuitry and software, etc. (i) a combination of analog and / or digital hardware circuitry and software / firmware; and (ii) any portion of hardware processors, software (including digital signal processors), software, and memory that function together to cause an apparatus, such as a communications device or base station, to perform the various functions described above; and (c) Hardware circuitry and / or processors, such as microprocessors or portions of microprocessors, that require software (e.g., firmware) to operate but that may not be present when software is not used for operation.

[0425] This definition of circuit applies to all uses of the term in this application, including any claims. As a further example, as used in this application, the term circuit also encompasses a simple hardware circuit or processor (or processors), or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware implementation. The term circuit also encompasses, for example, integrated devices.

[0426] The above description provides a complete and informative description of several examples, by way of non-limiting example. However, various modifications and applications will become apparent to those skilled in the art in view of the above description, when read in conjunction with the accompanying drawings and claims. However, all such similar modifications of these teachings will still fall within the scope of the claims.

[0427] Although different examples have been 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 can be applied, these examples are not limited to such architectures. These examples can also be applied to other types of communication networks having suitable means by appropriately adjusting parameters and procedures. Some examples of alternatives to suitable systems include Universal Mobile Telecommunications System (UMTS) Radio Access Network (UTRAN), Wireless Local Area Network (WLAN or WiFi), Worldwide Interoperability for Microwave Access (WiMAX), Bluetooth®, Personal Communications Services (PCS), ZigBee®, Wideband Code Division Multiple Access (WCDMA), systems using Ultra-Wideband (UWB) technology, sensor networks, Mobile Ad Hoc Networks (MANETs), and Internet Protocol Multimedia Subsystem (IMS), or any combination thereof.

[0428] 5 shows an example of a simplified system architecture showing only some elements and functional entities, which are all logical units and whose implementation may differ from those shown. The connections shown in FIG. 5 are logical connections; the actual physical connections may differ. It will be apparent to those skilled in the art that a system typically includes functions and structures other than those shown in FIG. 5.

[0429] However, these examples are not limited to the systems given as examples, and a person skilled in the art will be able to apply this solution to other communication systems with the required characteristics.

[0430] The example of Figure 5 illustrates a portion of an exemplary radio access network. For example, the radio access network may support sidelink communications, which are described in more detail below.

[0431] 5 shows devices 500 and 502. Devices 500 and 502 are configured to wirelessly connect over one or more communication channels by node 504. Node 504 is further connected to a core network 506. In one example, node 504 may be an access node such as a NodeB (for example) that serves devices within a cell. In one example, node 504 may be a non-3GPP access node. The physical link from a device to a NodeB (for example) is referred to as an uplink or reverse link, and the physical link from a NodeB (for example) to a device is referred to as a downlink or forward link. It should be understood that a NodeB (for example) or their functionality may be implemented by using any node, host, server, access point, or other entity suitable for such use.

[0432] A communication system typically comprises two or more (e.g.) NodeBs, where the (e.g.) NodeBs may also be configured to communicate with each other via wired or wireless links designed for that purpose. These links may be used for signaling purposes. A (e.g.) NodeB is a computing device configured to control radio resources of the communication system to which the (e.g.) NodeB is coupled. A NodeB may also be referred to as a base station, an access point, or any other type of interfacing device, including a relay station capable of operating in a wireless environment. A (e.g.) NodeB includes or is connected to a transceiver. A connection is provided from the (e.g.) NodeB's transceiver to an antenna unit that establishes a bidirectional radio link to the device. The antenna unit may comprise multiple antennas or antenna elements. A (e.g.) NodeB is further connected to a core network 506 (CN or Next Generation Core NGC). Depending on the technology deployed, a NodeB (for example) is connected to a Serving and Packet Data Network Gateway (S-GW+P-GW) or User Plane Function (UPF) to route and forward user data packets, provide device connectivity to one or more external packet data networks and a Mobility Management Entity (MME) or Access Mobility Management Function (AMF), and control device access and mobility.

[0433] Examples of devices include subscriber units, user devices, user equipment (UE), user terminals, terminal devices, mobile stations, mobile devices, and the like.

[0434] A device generally refers to a mobile or stationary device (e.g., a portable or non-portable computing device) and includes wireless mobile communication devices that operate with or without a universal subscriber identity module (USIM), including, but not limited to, the following types of devices: mobile phones, smartphones, personal digital assistants (PDAs), handsets, devices that use wireless modems (such as alarms or measurement devices), laptop and / or touchscreen computers, tablets, game consoles, notebooks, and multimedia devices. It should be understood that a device can also be almost exclusively an uplink-only device, an example of which is a camera or video camera that loads images or video clips onto a network. A device can also be a device capable of operating within an Internet of Things (IoT) network, a scenario in which objects have the ability to communicate data over a network without the need for human-to-human or human-to-computer interaction, such as in smart power grids and connected vehicles. A device can also utilize the cloud. In some applications, a device can constitute a user-portable device (such as a watch, earphones, or glasses) with a wireless portion, with computations performed in the cloud.

[0435] A device refers to a type of equipment that is allocated and provided with resources on the air interface, and therefore any features described herein with respect to a device can be implemented with a corresponding equipment, such as a relay node. One example of such a relay node is a Layer 3 relay (self-backhauling relay) toward a base station. The device (or in some examples, the Layer 3 relay node) is configured to perform one or more of the user equipment functions.

[0436] The various techniques described herein can also be applied to cyber-physical systems (CPS), systems in which cooperating computational elements control physical entities. CPS can enable the implementation and utilization of a large number of interconnected information and communication technologies, ICTs, and devices (sensors, actuators, processors, microcontrollers, etc.) embedded within physical objects in different locations. Mobile cyber-physical systems, in which the physical system has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronic devices transported by humans or animals.

[0437] Additionally, although the device has been shown as a single entity, it may be implemented with different units, processors and / or memory units (not all of which are shown in FIG. 5).

[0438] 5G will enable the use of many more base stations or nodes, multiple-input multiple-output (MIMO) antennas, than LTE (the so-called small cell concept), including macro sites operating in cooperation with smaller stations, and will employ various radio technologies depending on service requirements, use cases, and / or available frequency bands. 5G mobile communications will support a wide range of use cases and related applications, including video streaming, augmented reality, different methods of data sharing, and various forms of machine-type applications (e.g., (massive) machine-type communications (mMTC) involving vehicle safety, different sensors, and real-time control). 5G is expected to have multiple air interfaces, e.g., below 6 GHz or above 24 GHz, cmWave, and mmWave, and will be able to integrate with existing legacy radio access technologies such as LTE. Integration with LTE could be implemented as a system, at least initially, where macro coverage is provided by LTE and 5G air interface access comes from small cells aggregated to LTE. In other words, 5G is planned to support both inter-RAT interoperability (e.g., LTE-5G) and inter-RI interoperability (inter-air interface interoperability, e.g., below 6 GHz - cmWave, above 6 or 24 GHz - cmWave and mmWave). One of the concepts expected to be used in 5G networks is network slicing, which allows multiple independent and dedicated virtual sub-networks (network instances) to be created within the same infrastructure to run services with different requirements in terms of latency, reliability, throughput, and mobility.

[0439] The LTE network architecture is fully decentralized in the radio and fully centralized in the core network. Low-latency applications and services in 5G require content to be pushed closer to the radio, which brings about local breakout and multi-access edge computing (MEC). 5G enables analytics and knowledge generation at the source of data. This approach requires leveraging resources that may not be continuously connected to the network, such as laptops, smartphones, tablets, and sensors. MEC provides a distributed computing environment for hosting applications and services. MEC also has the ability to store and process content closer to cellular subscribers for faster response times. Edge computing encompasses a wide range of technologies such as wireless sensor networks, mobile data collection, mobile signature analysis, collaborative distributed peer-to-peer ad hoc networking and processing, including local cloud / fog computing and grid / mesh computing, dew computing, mobile edge computing, cloudlets, distributed data storage and retrieval, autonomous self-healing networks, remote cloud services, augmented and virtual reality, data caching, Internet of Things (massive connectivity and / or latency critical), and critical communications (autonomous vehicles, road safety, real-time analytics, time-critical control, medical applications).

[0440] The communication system may also communicate with or use 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 support the use of cloud services, e.g., at least a portion of the core network operations may be implemented as cloud services (this is illustrated in FIG. 5 by "Cloud" 514). When implemented at a location remote from the core network, this may also be referred to as edge computing. The communication system may also comprise a central control entity, etc., that provides a mechanism for networks of different operators to cooperate, e.g., in spectrum sharing.

[0441] Computing technologies can be introduced into the Radio Access Network (RAN) by utilizing Network Function Virtualization (NFV) and Software-Defined Networking (SDN). Using edge cloud technologies can mean that access node operations are performed at least partially within a server, host, or node operatively coupled to a remote radio head or base station comprising the radio portion. It is also possible to distribute node operations among multiple servers, nodes, or hosts. Applying a Cloud RAN architecture allows 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 centrally (in the centralized unit CU 510).

[0442] 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 may even not exist. Some other technological innovations that are likely to be used in the future include Big Data and all-IP, which could change the way networks are built and managed. 5G (or New Radio NR) networks are designed to accommodate multiple tiers in which edge computing servers can be placed between the core and base stations or NodeBs (gNBs). One example of edge computing is MEC, which is defined by the European Telecommunications Standards Institute. It should be understood that MEC (and other edge computing protocols) can be applied to 4G networks as well.

[0443] 5G can also utilize satellite communications to enhance or complement the coverage of 5G services, for example by providing backhauling. Possible use cases are providing service continuity for machine-to-machine (M2M) or Internet of Things (IoT) devices, or passengers on board vehicles, Mobile Broadband (MBB), or ensuring service availability for critical communications and future rail, maritime, and aviation communications. Satellite communications can utilize not only geostationary orbit (GEO) satellite systems, but also low-earth orbit (LEO) satellite systems, especially megaconstellations (systems in which hundreds of (nano)satellites are deployed). Each satellite in a megaconstellation can cover several satellite-enabled network entities, forming ground cells. Ground cells can be formed by terrestrial relay nodes or by gNBs located on the ground or in the satellites.

[0444] The illustrated system is merely an example of a portion of a wireless access system; in practice, the system may include multiple (e.g.,) NodeBs, devices may access multiple wireless cells, and the system may also include other devices, such as physical layer relay nodes or other network elements. At least one of the (e.g.,) NodeBs may be a (e.g.,) Home NodeB. In addition, multiple different types of wireless cells may be provided within the geographical area of ​​the wireless communication system. Wireless cells include macrocells (or umbrella cells), which are large cells typically having diameters of up to tens of kilometers, or smaller cells such as micro, femto, or picocells. The (e.g.,) NodeB in FIG. 5 may provide any type of these cells. A cellular wireless system may be implemented as a multi-layer network including several types of cells.

[0445] Attachment A Contribution Summary: This attachment proposes an exemplary update to Solution #33 of KI#8.

[0446] - 1 Discussion The purpose of the FS_eLCS_Ph3 SID is to:

[0447] - WT#6: Studying enhancements for UE mobility, i.e., to support continuity of location services between EPS and 5GS; Key Challenge #8: Addressing continuity of location services during UE mobility involves: - For commercial location services, especially for vehicular (V2X) UE use cases, it is highly likely that the UE will move between EPS and 5GS, requiring continuous UE position measurements (periodic location services / LDR). The following UE movement scenarios were considered in response to this key challenge: - UE movement between EPS and 5GS (bidirectional).

[0448] - UE mobility between NG-RAN nodes.

[0449] This exemplary proposal provides an update to Solution #33 for LCS continuity in both directions between EPS and 5GS.

[0450] - 2 Illustrative Proposals It is proposed to update TR23.700-71 - "Study enhancement to the 5GC LoCation Services (LCS); Phase 3" as follows:

[0451] *** Changes Begin *** 6.0 Mapping Solutions to Key Challenges

[0452] [Table 1]

[0453] *** Next Change *** 6.x Solution #8: Supporting LCS mobility when the UE moves between 5GS and EPS 6.X.1 Introduction This solution addresses KI "Key Challenge #8: support of location service continuity in case of UE mobility".

[0454] Continuity of certain basic services, such as PDU sessions during movement, is currently defined. However, the handling of LCS sessions during the movement procedure is not specified. In particular, there is no specification as to whether ongoing LCS sessions should be terminated after the movement or continued, and if so, how continuity should work. This omission could have a number of implications.

[0455] - The LCS session may be terminated upon movement, and the LCS client must resume the session after this procedure.

[0456] - The LMF will not be able to see any of this movement, leading to inaccurate localization estimates.

[0457] - There is no clear specification, so cross-vendor testing may fail.

[0458] - LCS sessions may be enabled as part of other services (e.g. emergency calls) and those services may be affected by the current specification, which may raise regulatory issues.

[0459] At least some of these problems could be mitigated or prevented if there were clear specifications regarding how LCS sessions should be handled in different mobility procedures, and in particular whether continuity can be guaranteed by the network.

[0460] Exemplary considerations herein include: - EPC changes will be kept to a minimum so that legacy functionality can be phased in.

[0461] - No standardized interface between EPC-GMLC and 5GC-GMLC is defined. As per TS 23.273, chapter 4.2a, this interface, denoted as Lr', is not standardized and if EPC-GMLC and 5GC-GMLC are in the same location, Lr' is not required at all. This example does not require standardization of this interface.

[0462] - Providing a common procedure for all types of location requests (MO-LR / MT-LR with or without delayed location); - Provide a simple example that works when a movement event occurs, regardless of the current state of an ongoing location procedure; 6.X.2 Functional Description This exemplary proposal provides an example for transfer between 5GS and EPS with reference to Figures 13 and 14. Figures 12 and 13 show exemplary signaling.

[0463] 6.X.3 Procedure Referring to Figure 13, the following is provided:

[0464] [Table 2]

[0465] explanation: Steps 1-4 describe a successful MT-LR LCS session over 5GS (similar to steps 1.a. to 12 in Figure 6.1.2-1 of TS23.273).

[0466] Steps 5-14 describe the normal 5GS to EPS HO procedure (similar to steps 1 to 12.b in Figure 4.11.1.2.1-1 of TS23.502).

[0467] When the AMF receives the Relocation Response (step 10), it may start steps 15 and 17 in parallel with step 11.

[0468] Steps 15-16: The LCS Session on the 5GS is cancelled.

[0469] Step 17: The AMF notifies the 5GC-GMLC of the failure, including the reason "HO to EPC" and the target MME ID.

[0470] Step 18: The 5GC-GMLC forwards the location request to the EPC-GMLC, including all parameters of the LCS Request and the target MME ID.

[0471] Steps 19-24: An LCS Session is initiated on the EPS (similar to steps 1-10 in Figure 9.18 of TS23.271).

[0472] Steps 25-26: The UE location estimate is returned by the EPC-GMLC to the 5GC-GMLC, which then forwards it to the LCS Client.

[0473] Notes: As can be observed, this exemplary procedure is implemented in such a way that the continuity of the LCS session is ensured even if the LCS Client is not / cannot be aware of the mobility process.

[0474] - There is the possibility to map LCS QoS (from values ​​defined in 5GS to values ​​defined in 4GS), which can be done by GMLC. ○ For QoS attributes that are common between 5GS and EPS, the original LCS QoS definition values ​​can be used as is in EPS. ○ For QoS attributes specific to 5GS, QoS mapping can be performed to the strictest QoS value using best-effort processing of QoS Class.

[0475] If an LCS session was active via the 5GS user plane when the HO was triggered, the AMF (in step 10) may send user plane assistance data of the EPS-UP Server to the UE, either directly or via the LMF, before the HO is performed. The UE may then use this assistance data to connect to this server after a suitable PDN connection has been established or handed over, and the TLS and SUPL sessions may then be (re)established over the EPS, and the LCS session may continue in the user plane in the EPS.

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

[0477] [Table 3]

[0478] explanation: Steps 1-4 describe a successful MT-LR LCS session on the EPS (similar to steps 1 to 3 in Figure 6.1.2-1 of TS 23.271).

[0479] Steps 5-14 describe the normal EPS to 5GS HO procedure (similar to steps 1 through 16 in Figure 4.11.1.2.2.2-1 and steps 1-4 in Figure 4.11.1.2.2.3-1 of TS23.502).

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

[0481] Steps 15-16: The LCS Session on the EPS is canceled.

[0482] Step 17: The MME notifies the EPC-GMLC of the failure with the reason "HO to EPC" and the target AMF ID.

[0483] Step 18: EPC-GMLC forwards the location request including all parameters of the LCS Request and the target AMF ID to 5GC-GMLC.

[0484] Steps 19-24: An LCS Session is initiated over 5GS (similar to steps 1-23 in Figure 6.1.2-1 of TS 23.273).

[0485] Steps 25-26: The UE location estimate is returned from the 5GC-GMLC to the EPC-GMLC, which then forwards it to the LCS Client.

[0486] Notes: As can be observed, both exemplary procedures can be defined where the LCS client does not acknowledge mobility signaling, and where the continuity of the LCS session is ensured.

[0487] - There may be a mapping of LCS QoS (from values ​​defined for 5GS to values ​​defined for 4GS or vice versa), which can be done by GMLC. For QoS attributes that are common between 5GS and EPS, the original LCS QoS definition values ​​defined in 5GS can be used. For QoS attributes specific to EPS, QoS mapping can be performed to the strictest QoS value by using the best-effort processing of QoS Class.

[0488] - If the LMF is configured to use LCS over the 5GS user plane, the LMF chooses in step 24 to initiate the LCS session via the user plane.

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

[0490] [Table 4]

[0491] *** Changes End ***

Claims

1. 1. A method for a user equipment, comprising: receiving, when the user equipment is located in a first domain, assistance information from a first network function located in the first domain that identifies a user plane server that provides location services to the user equipment via a user plane of another domain; After a handover of the user equipment from the first domain to another domain is performed, establishing a data connection with a user plane server for providing location services to the user equipment via a user plane of the other domain based on the assistance information; A method comprising:

2. 1. A method for a user equipment, 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 services session of the user equipment was active in another domain, the assistance information identifying a user plane server for providing location services to the user equipment via a user plane of the first domain; After a handover of the user equipment from another domain to the first domain is performed, establishing a data connection with a user plane server for providing location services to the user equipment via a user plane of the first domain based on the assistance information; A method comprising:

3. 3. The method of claim 1, wherein the data connection is a packet data network, PDN, connection, and the assistance information is utilized to reach a user plane server via the PDN connection.

4. 3. The method according to claim 1, wherein assistance information is received before a command for the handover is sent towards the user equipment.

5. 3. The method of claim 1 or 2, wherein a first domain is configured as a 5G system 5GS of the Third Generation Partnership Project 3GPP and another 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 of claim 6 , wherein the assistance information is received from an access and mobility function via non-access stratum, NAS, signaling.

8. 8. The method of claim 7, wherein the assistance information is received from the access and mobility function in a downlink NAS transport message.

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

10. 10. The method of claim 9, wherein the assistance information is received from a location management function via Long Term Evolution Positioning Protocol, LPP, signaling.

11. 11. The method of claim 10, wherein the assistance information is received from a location management function as location services user plane, LCUP, assistance information data.

12. 10. The method of claim 9, wherein the assistance information is received from a location management function via secure user plane location, SUPL, signaling.

13. 13. The method of claim 12, wherein the assistance information is received from the location management function in a SUPL initiation message.

14. The method according to any one of claims 1 to 5, wherein the first network function is a location services user plane function.

15. 1. A method for a first network function located in a first domain, comprising: determining that a user equipment receiving location services via a user plane through a first domain should be handed over from the first domain to another domain; providing assistance information to the user equipment to identify a user plane server for providing location services to the user equipment via a user plane of another domain after the user equipment has been handed over to the second domain; A method comprising:

16. 16. The method of claim 15, wherein determining that the user equipment should be handed over is performed based on receiving a handover indication from a mobile management entity.

17. 1. A method for a first network function located in a first domain, comprising: receiving a location request for user equipment located within a first domain; determining that the user equipment previously received location services over a user plane via another domain; providing the user equipment with assistance information identifying a user plane server for providing location services to the user equipment via the user plane; A method comprising:

18. 18. The method of claim 17, wherein determining that the user equipment has previously received location services over a user plane via another domain is performed based on receiving a handover indication from a mobile management entity.

19. 19. The method of any of claims 15 to 18, wherein providing comprises providing the assistance information directly to the user equipment.

20. 19. The method of claim 15, wherein providing comprises indirectly providing the assistance information to the user equipment via at least one of a location management function or a location services user plane function.

21. 1. A method for a second network function located in a first domain, comprising: receiving, from a first network function located in a first domain, assistance information identifying a user plane server for providing location services to user equipment via a user plane of another domain; providing assistance information to the user equipment; A method comprising:

22. 22. The method of claim 21, wherein the second network function is at least one of a location management function or a location services user plane function.

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

24. The method of any of claims 1 to 23, wherein the assistance information includes address information of a user plane server.

25. 25. The method of claim 1, wherein the assistance information comprises at least one of an address of a user plane server, a unique identifier of the user plane server, a location service correlation 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 to the second domain, or transport layer security assistance information for establishing a user plane connection to the second domain.

26. Apparatus comprising means for carrying out the method of claim 1 or any of claims 3 to 14 when dependent on claim 1.

27. Apparatus comprising means for carrying out the method of claim 2 or any of claims 3 to 14 when dependent on claim 2.

28. Apparatus comprising means for carrying out the method of any of claims 15-16 or any of claims 19-20, 23 or 24-25 when dependent on any of claims 15-16.

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

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

31. A computer program comprising instructions which, when executed by an apparatus, cause the apparatus to perform a method according to claim 1 or any 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 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 of claims 15 to 16 or any of claims 19 to 20, 23 or 24 to 25 when dependent on any of claims 15 to 16.

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

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

Images