Apparatus, method and computer program

Abstract

Apparatus, method and computer program There is provided an apparatus comprising means for performing obtaining a profile of a network entity and providing, to the network entity based on the profile of the network entity, a request to intervene in a roaming data session of a user equipment, wherein the request comprises a first identifier of the user equipment and a second identifier of the apparatus, wherein a connection is established between a visited network serving the user equipment and a home network of the user equipment via the apparatus.

Description

[0001] Title

[0002] Apparatus, method and computer program

[0003] Field

[0004] The present application relates to a method, apparatus, system and computer program and in particular but not exclusively to roaming intermediary triggered UE deregistration and PDU session termination.

[0005] Background

[0006] A communication system can be seen as a facility that enables communication sessions between two or more entities such as user terminals, base stations and / or other nodes by providing carriers between the various entities involved in the communications path. A communication system can be provided for example by means of a communication network and one or more compatible communication devices. The communication sessions may comprise, for example, communication of data for carrying communications such as voice, video, electronic mail (email), text message, multimedia and / or content data and so on. Non-limiting examples of services provided comprise two-way or multi-way calls, data communication or multimedia services and access to a data network system, such as the Internet.

[0007] In a wireless communication system at least a part of a communication session between at least two stations occurs over a wireless link. Examples of wireless systems comprise public land mobile networks (PLMN), satellite based communication systems and different wireless local networks, for example wireless local area networks (WLAN). Some wireless systems can be divided into cells, and are therefore often referred to as cellular systems.

[0008] A user can access the communication system by means of an appropriate communication device or terminal. A communication device of a user may be referred to as user equipment (UE) or user device. A communication device is provided with an appropriate signal receiving and transmitting apparatus for enabling communications, for example enabling access to a communication network or communications directly with other users. The communication device may access a carrier provided by a station, for example a base station of a cell, and transmit and / or receive communications on the carrier. The communication system and associated devices typically operate in accordance with a given standard or specification which sets out what the various entities associated with the system are permitted to do and how that should be achieved. Communication protocols and / or parameters which shall be used for the connection are also typically defined. One example of a communications system is Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN) (3G radio). Other examples of communication systems are the long-term evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio-access technology and so-called 5G or New Radio (NR) networks. NR is being standardized by the 3rd Generation Partnership Project (3GPP). Other examples of communication systems include 5G-Advanced (NR Rel-18 and beyond) and 6G.

[0009] Summary

[0010] In a first aspect there is provided a method comprising obtaining a profile of a network entity and providing, to the network entity based on the profile of the network entity, a request to intervene in a roaming data session of a user equipment, wherein the request comprises a first identifier of the user equipment and a second identifier of the apparatus, wherein a connection is established between a visited network serving the user equipment and a home network of the user equipment via the apparatus.

[0011] The request to intervene in the roaming data session of the user equipment may be a request to trigger a deregistration of the user equipment.

[0012] The network entity may comprise an access and mobility management function of the visited network.

[0013] Obtaining the profile of the network entity may comprise providing, to a network repository function in the visited network, a discovery request comprising an indication that the request is received from a roaming intermediary and receiving, from the network repository function, a discovery response comprising the profile of the network entity.

[0014] The discovery request may comprise an identifier of the network entity.

[0015] The identifier of the network entity may be a GUAM I of the network entity or UUID of the network entity. The network entity may comprise a user data management network function of the home network.

[0016] Obtaining the profile of the network entity comprises providing, to a network repository function in the home network, a discovery request comprising an indication that the request is received from a roaming intermediary and receiving, from the network repository function, a discovery response comprising the profile of network entity.

[0017] The discovery request may comprise the identifier of the user equipment.

[0018] The request to intervene in the roaming data session of the user equipment may be a request to trigger a release of a protocol data unit session of the user equipment.

[0019] The network entity may comprise a session management function of the home network.

[0020] Obtaining the profile of the network entity may comprise providing, to a network repository function of the home network, a discovery request comprising an indication that the request is received from a roaming intermediary and receiving, from the network repository function, a discovery response comprising the profile of the network entity.

[0021] The discovery request may comprise an identifier of the network entity.

[0022] The identifier of the network entity may comprise a UIIID of the network entity.

[0023] The first identifier of the user equipment may comprise a context reference. The method may comprise storing the UIIID of the network entity and the context reference at the apparatus and updating the UIIID of the first entity and the context reference when the user equipment relocates to a further network entity.

[0024] In a second aspect, there is provided a method comprising, at a network entity, receiving from an apparatus, a request to intervene in a roaming data session of a user equipment, wherein the request comprises a first identifier of the user equipment and a second identifier of the apparatus, wherein a connection is established between a visited network serving the user equipment and a home network of the user equipment via the apparatus. The request to intervene in the roaming data session of the user equipment may be a request to trigger a deregistration of the user equipment.

[0025] The network entity may comprise an access and mobility management function of the visited network or a user data management network function of the home network.

[0026] When the network entity comprises the user data management network function, the method may comprise providing the request to an access and mobility management of the visited network.

[0027] The request to an access and mobility management of the visited network may comprise an indication the request was triggered by a roaming intermediary.

[0028] The request to intervene in the roaming data session of the user equipment may be a request to trigger a release of a protocol data unit session of the user equipment.

[0029] The network entity may comprise a session management function of the home network.

[0030] In a third aspect there is provided an apparatus, comprising means for performing obtaining a profile of a network entity; and providing, to the network entity based on the profile of the network entity, a request to intervene in a roaming data session of a user equipment, wherein the request comprises a first identifier of the user equipment and a second identifier of the apparatus, wherein a connection is established between a visited network serving the user equipment and a home network of the user equipment via the apparatus.

[0031] The request to intervene in the roaming data session of the user equipment may be a request to trigger a deregistration of the user equipment.

[0032] The network entity may comprise an access and mobility management function of the visited network.

[0033] Obtaining the profile of the network entity may comprise providing, to a network repository function in the visited network, a discovery request comprising an indication that the request is received from a roaming intermediary and receiving, from the network repository function, a discovery response comprising the profile of the network entity.

[0034] The discovery request may comprise an identifier of the network entity. The identifier of the network entity may be a GUAM I of the network entity or UUID of the network entity.

[0035] The network entity may comprise a user data management network function of the home network.

[0036] Obtaining the profile of the network entity comprises providing, to a network repository function in the home network, a discovery request comprising an indication that the request is received from a roaming intermediary and receiving, from the network repository function, a discovery response comprising the profile of network entity.

[0037] The discovery request may comprise the identifier of the user equipment.

[0038] The request to intervene in the roaming data session of the user equipment may be a request to trigger a release of a protocol data unit session of the user equipment.

[0039] The network entity may comprise a session management function of the home network.

[0040] Obtaining the profile of the network entity may comprise providing, to a network repository function of the home network, a discovery request comprising an indication that the request is received from a roaming intermediary and receiving, from the network repository function, a discovery response comprising the profile of the network entity.

[0041] The discovery request may comprise an identifier of the network entity.

[0042] The identifier of the network entity may comprise a UUID of the network entity.

[0043] The first identifier of the user equipment may comprise a context reference. The apparatus may comprise means for performing storing the UUID of the network entity and the context reference at the apparatus and updating the UUID of the first entity and the context reference when the user equipment relocates to a further network entity.

[0044] In a fourth aspect there is provided an apparatus, comprising means for performing, at a network entity, receiving from an apparatus, a request to intervene in a roaming data session of a user equipment, wherein the request comprises a first identifier of the user equipment and a second identifier of the apparatus, wherein a connection is established between a visited network serving the user equipment and a home network of the user equipment via the apparatus.

[0045] The request to intervene in the roaming data session of the user equipment may be a request to trigger a deregistration of the user equipment.

[0046] The network entity may comprise an access and mobility management function of the visited network or a user data management network function of the home network.

[0047] When the network entity comprises the user data management network function, the apparatus may comprise means for providing the request to an access and mobility management of the visited network.

[0048] The request to an access and mobility management of the visited network may comprise an indication the request was triggered by a roaming intermediary.

[0049] The request to intervene in the roaming data session of the user equipment may be a request to trigger a release of a protocol data unit session of the user equipment.

[0050] The network entity may comprise a session management function of the home network.

[0051] In a fifth aspect there is provided an apparatus comprising at least one processor, and at least one memory storing instructions which, when executed by the processor, cause the apparatus at least to perform a method according to the first aspect

[0052] In a sixth aspect there is provided an apparatus comprising at least one processor, and at least one memory storing instructions which, when executed by the processor, cause the apparatus at least to perform, at a network entity, a method according to the second aspect.

[0053] In a seventh aspect there is provided an computer readable medium comprising instructions which, when executed by an apparatus, cause the apparatus to perform at least the method according to the first aspect.

[0054] In an eight aspect there is provided a computer readable medium comprising instructions which, when executed by an apparatus, cause the apparatus to perform at least the method according to the second aspect. In an aspect there is provided a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method according to the first or second aspects.

[0055] In the above, many different embodiments have been described. It should be appreciated that further embodiments may be provided by the combination of any two or more of the embodiments described above.

[0056] Description of Figures

[0057] Embodiments will now be described, by way of example only, with reference to the accompanying Figures in which:

[0058] Figure 1 shows a schematic diagram of an example 5GS communication system;

[0059] Figure 2 shows a schematic diagram of an example mobile communication device;

[0060] Figure 3 shows a schematic diagram of an example control apparatus;

[0061] Figure 4 shows a schematic diagram of roaming intermediaries between Operator A and Operator B;

[0062] Figure 5 shows a flowchart of a method according to an example embodiment;

[0063] Figure 6 shows a flowchart of a method according to an example embodiment;

[0064] Figure 7 shows a flowchart according to an example embodiment

[0065] Figure 8 shows a service operation according to an example embodiment;

[0066] Figure 9 shows a flowchart according to an example embodiment;

[0067] Figure 10 shows a service operation according to an example embodiment;

[0068] Figure 11 shows a flowchart according to an example embodiment

[0069] Figure 12 shows a service operation according to an example embodiment. Detailed description

[0070] Before explaining in detail the examples, certain general principles of a wireless communication system and mobile communication devices are briefly explained with reference to Figure 1 , Figure 2 and Figure 3 to assist in understanding the technology underlying the described examples.

[0071] An example of a suitable communications system is the 5G or NR concept. Network architecture in NR may be similar to that of LTE-advanced. Base stations of NR systems may be known as next generation NodeBs (gNBs). Changes to the network architecture may depend on the need to support various radio technologies and finer Quality of Service (QoS) support, and some on-demand requirements for e.g. QoS levels to support Quality of Experience (QoE) for a user. Also network aware services and applications, and service and application aware networks may bring changes to the architecture. Those are related to Information Centric Network (ICN) and User-Centric Content Delivery Network (UC-CDN) approaches. NR may use Multiple Input - Multiple Output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in co-operation with smaller stations and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.

[0072] Future networks may utilise network functions virtualization (NFV) which is a network architecture concept that proposes virtualizing network node functions into “building blocks” or entities that may be operationally connected or linked together to provide services. A virtualized network function (VNF) may comprise one or more virtual machines running computer program codes using standard or general type servers instead of customized hardware. Deployments may be cloud-native network function (CNF) based, where network functions comprise one or more pods. Cloud computing or data storage may also be utilized. In radio communications this may mean node operations are to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. It should also be understood that the distribution of labour between core network operations and base station operations may differ from that of LTE or may even be nonexistent.

[0073] Figure 1 shows a schematic representation of a 5G system (5GS) 100. The 5GS may comprise a user equipment (UE) 102 (which may also be referred to as a communication device or a terminal), a 5G radio access network (5GRAN) 104, a 5G core network (5GCN) 106, one or more internal or external application functions (AF) 108 and one or more data networks (DN) 110.

[0074] An example 5G core network (CN) comprises functional entities. The 5GCN 106 may comprise one or more Access and mobility Management Functions (AMF) 112, one or more session management functions (SMF) 114, an authentication server function (ALISF) 116, a Unified Data Management (UDM) 118, one or more user plane functions (UPF) 120, a Unified Data Repository (UDR) 122 and / or a Network Exposure Function (NEF) 124. The UPF is controlled by the SMF (Session Management Function) that receives policies from a PCF (Policy Control Function).

[0075] The CN may be connected to a UE via the Radio Access Network (RAN) or through fixed access via a non-3GPP Interworking Function (N3IWF). The 5GRAN may comprise one or more gNodeB (gNB) Distributed Unit (DU) functions connected to one or more gNodeB (gNB) Centralized Unit (CU) functions. The RAN may comprise one or more access nodes.

[0076] A User Plane Function (UPF) referred to as PDU Session Anchor (PSA) may be responsible for forwarding frames back and forth between the DN and the tunnels established over the 5G towards the UE(s) exchanging traffic with the DN.

[0077] A possible mobile communication device will now be described in more detail with reference to Figure 2 showing a schematic, partially sectioned view of a communication device 200. Such a communication device is often referred to as user equipment (UE) or terminal. An appropriate mobile communication device may be provided by any device capable of sending and receiving radio signals. Non-limiting examples comprise a mobile station (MS) or mobile device such as a mobile phone or what is known as a ’smart phone’, a computer provided with a wireless interface card or other wireless interface facility (e.g., USB dongle), personal data assistant (PDA) or a tablet provided with wireless communication capabilities, voice over IP (VoIP) phones, portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart devices, wireless customer-premises equipment (CPE), or any combinations of these or the like. A mobile communication device may provide, for example, communication of data for carrying communications such as voice, electronic mail (email), text message, multimedia and so on. Users may thus be offered and provided numerous services via their communication devices. Non-limiting examples of these services comprise two-way or multi-way calls, data communication or multimedia services or simply an access to a data communications network system, such as the Internet. Users may also be provided broadcast or multicast data. Non-limiting examples of the content comprise downloads, television and radio programs, videos, advertisements, various alerts, and other information.

[0078] A mobile device is typically provided with at least one data processing entity 201 , at least one memory 202 and other possible components 203 for use in software and hardware aided execution of tasks it is designed to perform, including control of access to and communications with access systems and other communication devices. The data processing, storage and other relevant components can be provided on an appropriate circuit board and / or in chipsets. This feature is denoted by reference 204. The user may control the operation of the mobile device by means of a suitable user interface such as key pad 205, voice commands, touch sensitive screen or pad, combinations thereof or the like. A display 208, a speaker and a microphone can be also provided. Furthermore, a mobile communication device may comprise appropriate connectors (either wired or wireless) to other devices and / or for connecting external accessories, for example hands-free equipment, thereto.

[0079] The mobile device 200 may receive signals over an air or radio interface 207 via appropriate apparatus for receiving and may transmit signals via appropriate apparatus for transmitting radio signals. In Figure 2 transceiver apparatus is designated schematically by block 206. The transceiver apparatus 206 may be provided for example by means of a radio part and associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device.

[0080] Figure 3 shows an example of a control apparatus 300 for a communication system, for example to be coupled to and / or for controlling a station of an access system, such as a RAN node, e.g. a base station, eNB or gNB, a relay node or a core network node such as an MME or Serving Gateway (S-GW) or Packet Data Network Gateway (P-GW), or a core network function such as AMF / SMF, or a server or host. The method may be implemented in a single control apparatus or across more than one control apparatus. The control apparatus may be integrated with or external to a node or module of a core network or RAN. In some embodiments, base stations comprise a separate control apparatus unit or module. In other embodiments, the control apparatus can be another network element such as a radio network controller or a spectrum controller. In some embodiments, each base station may have such a control apparatus as well as a control apparatus being provided in a radio network controller. The control apparatus 300 can be arranged to provide control on communications in the service area of the system. The control apparatus 300 comprises at least one memory 301 , at least one data processing unit 302, 303 and an input / output interface 304. Via the interface the control apparatus can be coupled to a receiver and a transmitter of the base station. The receiver and / or the transmitter may be implemented as a radio front end or a remote radio head.

[0081] A Roaming Intermediary (Rl) may refer to an entity that provides roaming related services.

[0082] An Rl may be deployed between networks (e.g., between an H-PLMN (Home PLMN) and a V-PLMN (visited PLMN)) in roaming scenarios. For example, RIs may facilitate the deployment and operation of roaming services between a client operator and a set of selected connected operators via the N32 Interface (e.g., using a N32-c connection).

[0083] Roaming Intermediaries may optionally offer value added services (e.g. Analytics, Charging, Rate limiting, etc.). To do so, the Rl may need to have full visibility of the UE state, which means that the Rl may either have interconnect exclusivity or operators may implement a solution that assures that all traffic for a specific UE is handled by a single Rl. RIs may generate their own messages towards the PLMNs.

[0084] Each operator uses a SEPP (Security and Edge Protection Proxy) in its network border to facilitate communications between networks of different operators. The communications between two SEPPs may go through / via more than one Rl, e.g., up to two RIs.

[0085] Figure 4 shows a schematic diagram of two RIs deployed between the SEPPS of two networks (e.g., PLMNs, SNPNs (standalone non-public networks), NPNs) of two operators A and B.

[0086] An Rl may be a Roaming Hub (RH) or an IPX (Internetwork Packet Exchang) service provider.

[0087] A Service Hub may act as a Roaming Intermediary in a system of 5G or beyond.

[0088] A Roaming Hub may refer to a type of Roaming Intermediary, e.g., as defined by GSMA (Groups Speciale Mobile Association).

[0089] An Rl may have the ability to intervene in roaming data sessions at any time, in order to limit roaming data usage by limiting throughput and / or stopping ongoing data sessions, e.g., as agreed with a client H-PLMN. This ability to intervene may require anchoring the media in this Rl (i.e., user plane traffic of the PDU shall also traverse the same Rl, otherwise the Rl will not be, e.g., able to measure how much traffic each PDU is using).

[0090] An Rl may be able to intervene on roaming data sessions on the basis of individual PDU sessions and across all PDU sessions of the roamers of a given roaming relationship between two PLMNs.

[0091] All N32 messages between MNOs (mobile network operators) may be transferred via one or more RIs. The RI / RH may have the ability to prevent the establishment of and the termination of N32-c and N32-f connections / interfaces, for example if this is required due to contractual reasons of the MNOs.

[0092] In an embodiment, N32-c connection / interface is used for context management for security capability negotiation on the N32 interface.

[0093] In an embodiment, N32-f connection / interface is used for forwarding of inter-NF (network function) signalling across networks (e.g., PLMNs, SNPNs or NPNs).

[0094] For example, when RIs offer value added services, the RIs may need to Deregister UEs or Release PDU sessions when / if certain conditions are met. As of now, RIs do not have means to trigger UE deregistration or PDU session release.

[0095] Figure 5 shows a flowchart of a method according to an example embodiment. The method may be performed at an apparatus. The apparatus may comprise an Rl, such as a RH.

[0096] In 501 , the method comprises obtaining a profile of a network entity.

[0097] In 502, the method comprises providing, to the network entity based on the profile of the network entity, a request to intervene in a roaming data session of a user equipment, wherein the request comprises a first identifier of the user equipment and a second identifier of the apparatus, wherein a connection is established between a visited network serving the user equipment and a home network of the user equipment via the apparatus.

[0098] Figure 6 shows a flowchart of a method according to an example embodiment. The method may be performed at an apparatus. The apparatus may comprise a network entity, such as an AMF, UDM or SMF. In 602, the method comprises receiving from an apparatus, a request to intervene in a roaming data session of a user equipment, wherein the request comprises a first identifier of the user equipment and a second identifier of the apparatus, wherein a connection is established between a visited network serving the user equipment and a home network of the user equipment via the apparatus.

[0099] Methods as described with reference to Figures 5 and 6 may provide a mechanism for RIs to initiate / trigger deregistration of a UE and / or to initiate release of (a) PDU session(s).

[0100] The Home network may comprise a PLMN, NPN or SNPN. The Visited network may comprise a PLMN, NPN, or SNPN.

[0101] The profile of the network entity may for example be an address, e.g., a service interface address, or an identifier of the network entity (for example IP (internet protocol) address and / or FQDN (fully qualified domain name)). The profile may also comprise a network function profile (or parts thereof) of the network entity. The NF profile may comprise general parameters of the NF Instance and the parameters of different NF Service Instances exposed by the NF Instance, if applicable.

[0102] The connection may be, for example, an N32-c connection and / or N32-f connection, or any other suitable connection for transmitting data and / or signalling between networks.

[0103] The term providing may encompass transmitting or sending by an apparatus or an entity.

[0104] The request to intervene in the roaming data session of the user equipment may be a request to trigger a deregistration of the user equipment.

[0105] Two alternative solutions are considered for UE Deregistration; an AMF based solution and a UDM based solution.

[0106] In an example embodiment of an AMF based solution, Rl triggered UE Deregistration via AMF is provided.

[0107] For an AMF based solution, the network entity may comprise an access and mobility management function of the visited network. Obtaining the profile of the network entity may comprise providing, to a network repository function in the visited network, a discovery request comprising an indication that the request is received from a roaming intermediary and receiving, from the network repository function, a discovery response comprising the profile of the network entity.

[0108] The discovery request may comprise an identifier, e.g., GlIAMI (Globally Unique AMF Identifier) or UUID (Universally unique identifier), of the network entity.

[0109] Figure 7 shows an example flowchart for Rl triggered deregistration via AMF.

[0110] During UE registration, the Rl stores the GUAMI of the AMF currently serving each UE (or alternatively the UUID of the AMF, if the AMF supports sending its own identity in the 3gpp-Sbi-Peer-lnfo.).

[0111] When / if the Roaming Intermediary decides that a UE may need to be deregistered, the Rl discovers a Service interface address of the serving AMF by sending NF Discovery Request to the NRF in the Serving PLMN (vNRF). This is an example of obtaining the profile of the AMF, wherein obtaining the profile of the AMF comprises providing, to a network repository function in the visited network, a discovery request and receiving, from the network repository function, a discovery response comprising the profile of the AMF.

[0112] The address of the NRF in the Serving Network may be known or e.g., learned via the HTTP CONNECT from the cSEPP to the Rl (for example 3gpp-Sbi-Nrf-Uri header could be used for this purpose). The discovery request may include an identifier of the network entity. In the example shown in Figure 7, the Rl provides the GUAMI of the Serving AMF as a discovery parameter (in an alternative embodiment, the UUID of the serving AMF may be provided as a discovery parameter).

[0113] In order to support Rl as a NRF consumer, the NFType Enumeration Table 6.1.6.3.3-1 of the NRF API 29.510 may be extended to include Roaming Intermediaries so as to be used by the Rl as the value for the requester-nf-type query parameter. This is an example of an indication that the request is received from a roaming intermediary.

[0114] In an embodiment, the field “NFtype” refers to or indicates / identifies NF types known to the NRF. For example, the field “NFtype” represents different types of Network Functions or Network Entities that can be found in the 5GC (5G core network). Based on Table 1, the definition of the field “NFtype” is further extended to the Rl (as underlined). Table 1 illustrates an example extension of a NFType Enumeration Table to include RIs.

[0115] Table 1 : Enumeration NFType

[0116] After the Rl receives the NF Discovery Response including the AMF profile from the v- NRF, the Rl sends a Service Request to the AMF to request Deregistration of the UE providing the SlIPI (Subscription Permanent Identifier) of the UE and / or the Rl Identity / identifier. This is an example of providing a request to an AMF to trigger a deregistration of a user equipment, wherein the request comprises a first identifier of the UE (e.g., SUPI) and a second identifier of the apparatus (e.g., Rl identity / identifier).

[0117] In the example flowchart shown in Figure 7, the Request is sent to the Communication Service (namf-comm) which is extended with a new operation (Deregister UE) (alternatively a new Service API (application programming interface) may be defined for this purpose). The operation may not be immediately applied on the individual UE context Resource ( / ue-contexts / {ueContextld}) since the Rl may not be aware of the UEs 5G- GUTI of the UE which is used as the Context-Id value. Thus, the operation may be defined on the parent resource ( / ue-context) and the Request payload may include the SUPI of the UE. The payload may further contain the Roaming Intermediary ID.

[0118] The Rl Identity / identifier may also be present in an HTTP Header User-Agent. The Roaming Intermediary Network Identity / identifier may be added by the SEPP in the 3gpp- Sbi-Originating-Network-ld Header.

[0119] Figure 8 illustrates a service operation in an example embodiment where the Rl requests UE deregistration via the AMF. In the example shown in Figure 8, the Rl triggers UE Deregistration by sending a Service Request to the AMF serving the UE using an example operation of the AMF Communication Service API. The AMF accordingly proceeds with the deregistration of the UE in a manner similar to an AMF-initiated Deregistration procedure operation.

[0120] Table 2 depicts the attributes of the UEDeregister message payload shown in Figure 8 of the new operation.

[0121] Table 2: Definition of type UEDeregister

[0122] In an example embodiment of a UDM based solution, Rl triggered UE Deregistration via UDM is provided.

[0123] In an example embodiment of a UDM based solution, the network entity may comprise a user data management network function of the home network.

[0124] Obtaining the profile of the network entity may comprise providing, to a network repository function in the home network, a discovery request comprising an indication that the request is received from a roaming intermediary and receiving, from the network repository function, a discovery response comprising the profile of network entity.

[0125] The discovery request may comprise the identifier of the user equipment (e.g., SUPI).

[0126] Figure 9 shows an example flowchart for Rl triggered deregistration via UDM.

[0127] When / if the Roaming Intermediary decides that a UE may need to be deregistered, the Rl discovers the Service interface of a UDM by sending NF Discovery Request to the NRF in the UE Home Network. This is an example of obtaining the profile of the UDM, wherein obtaining the profile of the UDM comprises providing, to a network repository function in the home network, a discovery request and receiving, from the network repository function, a discovery response comprising the profile of the UDM. The address of the NRF in the Serving Network may be known or e.g., learned via the HTTP CONNECT from the cSEPP to the Rl (e.g., 3gpp-Sbi-Nrf-Uri header could be used for this purpose). The Rl may provide the SlIPI of the UE as a discovery parameter (this is an example of the discovery request including an identifier of the UE). In order to support Rl as a NRF consumer the NFType Enumeration may be extended, for example as illustrated in Table 1.

[0128] The Rl sends a Service Request to the UDM to Deregister the UE providing the SUPI of the UE and / or Rl Identity. This is an example of providing a request to a UDM to trigger a deregistration of a user equipment, wherein the request comprises a first identifier of the UE (SUPI) and a second identifier of the apparatus (Rl identity).

[0129] In the example flowchart of Figure 9, the Request sent to the new operation (DeregisterUE) of the UE Context Management Service ( nudm-uecm) that allows Rl request UE deregistration by sending a relevant Request the ‘7{ueld} / registrations” resource (alternatively a new Service API may be defined for this purpose). The payload of the Request and the HTTP extensions may be equivalent to the one defined in the AMF based solution.

[0130] When / if the network entity comprises a UDM, a method as described with reference to Figure 5 may comprise providing the request to an access and mobility management of the visited network. The request to an access and mobility management of the visited network comprises an indication the request was triggered by or transmitted from a roaming intermediary. For example, the request may comprise the field “NFType” set as “Rl”.

[0131] Figure 10 shows an example service operation where the Rl requests UE deregistration via UDM.

[0132] In this example, the Roaming Intermediaries trigger the UE Deregistration by sending a Service Request to the UDM serving the UE using an operation of the UE Context Management Service API (or possibly alternative API defined for this purpose). UDM accordingly informs the AMF to Deregister the UE in a similar manner performed today when the UE Subscription is withdrawn. In this example embodiment, the UDM informs the AMF via the DeregistrationNotification Notification operation including the DeregistrationData as defined in 29.503 section

[0133] 5.3.2.3. This is an example of providing the request to an AMF of the visited network. In an embodiment, the AMF informs the UE about the deregistration, terminates the PCF associations and triggers the SMF to release the UE’s PDU sessions, e.g., in accordance with AMF procedures described in 3GPP TS 23.502 V18.4.0 (2023-12) Section 4.2.2.3.

[0134] The DeregistrationReason attribute of the DeregistrationData may be extended with a new reason that indicates that it was triggered by a Roaming Intermediary. Table 3 shows an example of an Enumeration table for Deregistration reasons extended to include an indication that the deregistration was triggered by an Rl (as underlined). This is an example of an indication the request was triggered by a roaming intermediary. Table 3: Enumeration DeregistrationReason

[0135] In case there is an alternative Roaming Intermediary that supports interconnect between the Operators there may be optional mechanism to allow the UE to Re-register immediately so that the Serving Operation connects via an alternative Roaming Intermediary.

[0136] The request to intervene in the roaming data session of the user equipment may be a request to trigger a release of a protocol data unit session of the user equipment. The network entity may comprise a session management function of the home network.

[0137] Obtaining the profile of the network entity may comprise providing, to a network repository function of the home network, a discovery request comprising an indication that the request is received from a roaming intermediary and receiving, from the network repository function, a discovery response comprising the profile of the network entity. The discovery request may comprise an identifier, e.g., UIIID, of the network entity.

[0138] Figure 11 shows an example flowchart for Rl triggered PDU session release.

[0139] The first identifier of the user equipment may comprise a context reference and the method may comprise storing the UIIID of the network entity and the context reference at the apparatus and updating the UIIID of the first entity and the context reference when the user equipment relocates to a further network entity.

[0140] The Rl stores the UUID of the Serving H-SMF and the Context Reference for each UE and updates it whenever UE is relocated to another SMF. This is possible if the H-SMF supports sending its own identity in the 3gpp-Sbi-Peer-lnfo.

[0141] When / if the Roaming Intermediary decides that a PDU session may need to be terminated, the Rl discovers the Service interface of the SMF by sending NF Discovery Request to the NRF in the UE Home Network (the address of the NRF in the Home Network of the UE is known) providing the UUID of the SMF as a discovery query parameter. Obtaining the profile of the SMF by providing, to a network repository function of the home network, a discovery request and receiving, from the network repository function, a discovery response comprising the profile of the SMF.

[0142] The Rl sends a release SM Context service Requests to the SMF to Release the PDU in the relevant resource ( / sm-context / {smContextRef}). of the PDUSession Service (nsmf- pdu ). This is an example of providing to the SMF, a request to release a PDU session of the UE. The SMF may inform the AMF and the UPF about the PDU termination in accordance with the network requested PDU Session Release for Home-routed Roaming procedure described in 3GPP TS 23.502 V18.4.0 (2023-12) section 4.3.4.3

[0143] Figure 12 shows an example service operation where the Rl requests PDU session release via SMF.

[0144] In an example embodiment, RIs may trigger the PDU Release by sending a Service Request to the SMF serving the UE using the Release operations of the PDU Session Service. The Request is sent to the H-SMF in the Home network of the UE. The procedure follows the SMF triggered PDU session release.

[0145] In an embodiment, a Cause value of the request in FIG. 12 can be defined in the Cause enumeration to be used for this purpose as illustrated in Table 4.

[0146] Table 4: Enumeration Cause

[0147] To improve security, it may be possible to enforce OAuth 2.0 Access Token based authorization in order to grant service access to the new Service operations in accordance to the procedures defined in 3GPP TS 33.510 V18.4.0 (2023-12). This requires that the NFType should support Roaming Intermediary as discussed above for the Discovery operation. The Roaming Intermediary may have a Nflnstanceld since it is a mandatory attribute of the OAuth token request payload.

[0148] An apparatus may comprise means for performing obtaining a profile of a network entity; and providing, to the network entity based on the profile of the network entity, a request to intervene in a roaming data session of a user equipment, wherein the request comprises a first identifier of the user equipment and a second identifier of the apparatus, wherein a connection is established between a visited network serving the user equipment and a home network of the user equipment via the apparatus. The apparatus may comprise a user equipment as described with reference to Figure 2, be the user equipment or be comprised in the user equipment or a chipset for performing at least some actions of / for the user equipment.

[0149] An apparatus may comprise means for performing, at a network entity, receiving from an apparatus, a request to intervene in a roaming data session of a user equipment, wherein the request comprises a first identifier of the user equipment and a second identifier of the apparatus, wherein a connection is established between a visited network serving the user equipment and a home network of the user equipment via the apparatus.

[0150] The apparatus may comprise the network entity or a network function such as AMF, UDM or SMF, be the network entity or network function or be comprised in the network entity or network function or a chipset for performing at least some actions of / for the network entity or network function.

[0151] In an embodiment, the apparatus comprising a network function refers to a device / apparatus which is configured to perform or performs at least part of functionalities of the network function or to a device / apparatus which comprises circuitry (e.g., chipset) configured to perform or performing at least part of functionalities of the network function.

[0152] It should be understood that the apparatuses may comprise or be coupled to other units or modules etc., such as radio parts or radio heads, used in or for transmission and / or reception. Although the apparatuses have been described as one entity, different modules and memory may be implemented in one or more physical or logical entities.

[0153] It is noted that whilst some embodiments have been described in relation to 5G networks, similar principles can be applied in relation to other networks and communication systems such as 6G networks or 5G-Advanced networks. Therefore, although certain embodiments were described above by way of example with reference to certain example architectures for wireless networks, technologies and standards, embodiments may be applied to any other suitable forms of communication systems than those illustrated and described herein.

[0154] It is also noted herein that while the above describes example embodiments, there are several variations and modifications which may be made to the disclosed solution without departing from the scope of the present invention. As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0155] In general, the various embodiments may be implemented in hardware or special purpose circuitry, software, logic or any combination thereof. Some aspects of the disclosure may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto. While various aspects of the disclosure may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

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

[0157] (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and

[0158] (b) combinations of hardware circuits and software, such as (as applicable):

[0159] (i) a combination of analog and / or digital hardware circuit(s) with software / firmware and

[0160] (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and

[0161] I hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.”

[0162] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device. The embodiments of this disclosure may be implemented by computer software executable by a data processor of the mobile device, such as in the processor entity, or by hardware, or by a combination of software and hardware. Computer software or program, also called program product, including software routines, applets and / or macros, may be stored in any apparatus-readable data storage medium and they comprise program instructions to perform particular tasks. A computer program product may comprise one or more computerexecutable components which, when the program is run, are configured to carry out embodiments. The one or more computer-executable components may be at least one software code or portions of it.

[0163] Further in this regard it should be noted that any blocks of the logic flow as in the Figures may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software may be stored on such physical media as memory chips, or memory blocks implemented within the processor, magnetic media such as hard disk or floppy disks, and optical media such as for example DVD and the data variants thereof, CD. The physical media is a non-transitory media. The term “non-transitory,” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).

[0164] The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The data processors may be of any type suitable to the local technical environment, and may comprise one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASIC), FPGA, gate level circuits and processors based on multi core processor architecture, as non-limiting examples.

[0165] Embodiments of the disclosure may be practiced in various components such as integrated circuit modules. The design of integrated circuits is by and large a highly automated process. Complex and powerful software tools are available for converting a logic level design into a semiconductor circuit design ready to be etched and formed on a semiconductor substrate.

[0166] The scope of protection sought for various embodiments of the disclosure is set out by the independent claims. The embodiments and features, if any, described in this specification that do not fall under the scope of the independent claims are to be interpreted as examples useful for understanding various embodiments of the disclosure.

[0167] The foregoing description has provided by way of non-limiting examples a full and informative description of the exemplary embodiment of this disclosure. However, various modifications and adaptations may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of the teachings of this disclosure will still fall within the scope of this invention as defined in the appended claims. Indeed, there is a further embodiment comprising a combination of one or more embodiments with any of the other embodiments previously discussed.

Claims

Claims1. An apparatus, comprising means for performing: obtaining a profile of a network entity; and providing, to the network entity based on the profile of the network entity, a request to intervene in a roaming data session of a user equipment, wherein the request comprises a first identifier of the user equipment and a second identifier of the apparatus; wherein a connection is established between a visited network serving the user equipment and a home network of the user equipment via the apparatus.

2. The apparatus of claim 1 , wherein the request to intervene in the roaming data session of the user equipment is a request to trigger a deregistration of the user equipment.

3. The apparatus of claim 2, wherein the network entity comprises an access and mobility management function of the visited network.

4. The apparatus of claim 2 or claim 3, wherein obtaining the profile of the network entity comprises providing, to a network repository function in the visited network, a discovery request comprising an indication that the request is received from a roaming intermediary and receiving, from the network repository function, a discovery response comprising the profile of the network entity.

5. The apparatus of claim 4, wherein the discovery request comprises an identifier of the network entity.

6. The apparatus according to claim 5, wherein the identifier of the network entity is a globally unique access and mobility management function identifier of the network entity or universally unique identifier of the network entity.

7. The apparatus of claim 2, wherein the network entity comprises a user data management network function of the home network.

8. The apparatus of claim 7, wherein obtaining the profile of the network entity comprises providing, to a network repository function in the home network, a discovery request comprising an indication that the request is received from aroaming intermediary and receiving, from the network repository function, a discovery response comprising the profile of network entity.

9. The apparatus of claim 8, wherein the discovery request comprises the identifier of the user equipment.

10. The apparatus of claim 1, wherein the request to intervene in the roaming data session of the user equipment is a request to trigger a release of a protocol data unit session of the user equipment.

11. The apparatus of claim 10, wherein the network entity comprises a session management function of the home network.

12. The apparatus of any of claim 10 or claim 11 , wherein obtaining the profile of the network entity comprises providing, to a network repository function of the home network, a discovery request comprising an indication that the request is received from a roaming intermediary and receiving, from the network repository function, a discovery response comprising the profile of the network entity.

13. The apparatus of claim 12, wherein the discovery request comprises an identifier of the network entity.

14. The apparatus according to claim 13, wherein the identifier of the network entity comprises a universally unique identifier of the network entity.

15. The apparatus according to claim 14, wherein the first identifier of the user equipment comprises a context reference and comprising means for performing storing the UIIID of the network entity and the context reference at the apparatus and updating the ULI ID of the first entity and the context reference when the user equipment relocates to a further network entity.

16. An apparatus, comprising means for performing, at a network entity, receiving from an apparatus, a request to intervene in a roaming data session of a user equipment, wherein the request comprises a first identifier of the user equipment and a second identifier of the apparatus, wherein a connection is established between a visited network serving the user equipment and a home network of the user equipment via the apparatus.

17. The apparatus according to claim 16, wherein the request to intervene in the roaming data session of the user equipment is a request to trigger a deregistration of the user equipment.

18. The apparatus according to claim 17, wherein the network entity comprises an access and mobility management function of the visited network or a user data management network function of the home network.

19. The apparatus according to claim 18, wherein the network entity comprises the user data management network function and comprising means for providing the request to an access and mobility management of the visited network.

20. The apparatus according to claim 19, wherein the request to an access and mobility management of the visited network comprises an indication the request was triggered by a roaming intermediary.

21. The apparatus according to claim 16, wherein the request to intervene in the roaming data session of the user equipment is a request to trigger a release of a protocol data unit session of the user equipment.

22. The apparatus according to claim 21 , wherein the network entity comprises a session management function of the home network.

23. A method comprising: obtaining a profile of a network entity; and providing, to the network entity based on the profile of the network entity, a request to intervene in a roaming data session of a user equipment, wherein the request comprises a first identifier of the user equipment and a second identifier of the apparatus, wherein a connection is established between a visited network serving the user equipment and a home network of the user equipment via the apparatus.

24. A method comprising, at a network entity, receiving from an apparatus, a request to intervene in a roaming data session of a user equipment, wherein the request comprises a first identifier of the user equipment and a second identifier of the apparatus, wherein a connection is established between a visited network serving the user equipment and a home network of the user equipment via the apparatus.

25. An apparatus comprising at least one processor, and at least one memory storing instructions which, when executed by the processor, cause the apparatus at least to perform: obtaining a profile of a network entity; and providing, to the network entity based on the profile of the network entity, a request to intervene in a roaming data session of a user equipment, wherein the request comprises a first identifier of the user equipment and a second identifier of the apparatus, wherein a connection is established between a visited network serving the user equipment and a home network of the user equipment via the apparatus.

26. An apparatus comprising at least one processor, and at least one memory storing instructions which, when executed by the processor, cause the apparatus at least to perform, at a network entity, receiving from an apparatus, a request to intervene in a roaming data session of a user equipment, wherein the request comprises a first identifier of the user equipment and a second identifier of the apparatus, wherein a connection is established between a visited network serving the user equipment and a home network of the user equipment via the apparatus.

27. A computer readable medium comprising instructions which, when executed by an apparatus, cause the apparatus to perform at least the following: obtaining a profile of a network entity; and providing, to the network entity based on the profile of the network entity, a request to intervene in a roaming data session of a user equipment, wherein the request comprises a first identifier of the user equipment and a second identifier of the apparatus, wherein a connection is established between a visited network serving the user equipment and a home network of the user equipment via the apparatus.

28. A computer readable medium comprising instructions which, when executed by an apparatus, cause the apparatus to perform at least the following: at a network entity, receiving from an apparatus, a request to intervene in a roaming data session of a user equipment, wherein the request comprises a first identifier of the user equipment and a second identifier of the apparatus, wherein a connection is established between a visited network serving the user equipment and a home network of the user equipment via the apparatus.

Images