Apparatus, method, and computer program for subscriber based routing of signaling to target communication network
The solution addresses the challenge of routing signalling messages in communication networks by determining RVAS eligibility and identifying a TPLMN for subscriber-based routing, efficiently handling signalling messages and minimizing home network traffic, thus enabling seamless service provision across different networks.
Patent Information
- Application Number
- GB2023007342
- Authority / Receiving Office
- GB · GB
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-17
- Publication Date
- 2024-11-20
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
TECHNICAL FIELD
[0001] Various example embodiments generally relate to the field of communication networks. Some example embodiments relate to an apparatus, method, and computer program for subscriber-based routing of signalling to a target wireless communication network. BACKGROUND
[0002] A communications network, such as a mobile communications network, may need to handle (e.g., process) and forward signalling pertaining to user equipment (UE) of specific subscribers from their home communications network to other communications networks. When roaming, a UE of a subscriber may be located at a coverage area of a communications network that is not the home communications network of the subscriber. A mechanism is required for routing signalling pertaining to UE of the subscriber and sent to the home communications network of this subscriber so that it can be received at a target communications network. SUMMARY
[0003] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
[0004] Example embodiments of the present disclosure improve routing in a communication network. This and other benefits may be achieved by the features of the independent claims. Further example embodiments are provided in the dependent claims, the description, and the drawings.
[0005] According to a first aspect, an apparatus for a home public land mobile network (HPLMN) is disclosed. The apparatus may comprise at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive an authentication request to authenticate a subscriber of the home public land mobile network from a serving public land mobile network (serving PLMN), determine whether the subscriber is eligible for a roaming value-added service (RVAS) based, at least, on subscription data of the subscriber and an identifier of the serving PLMN, and determine a target public land mobile network (TPLMN) for the authentication request based on the subscriber being eligible for the RVAS. Throughout this disclosure, RVAS may be understood as any service for subscriber-based routing of signalling to a TPLMN.
[0006] According to an example embodiment, the authentication request comprises a subscription concealed identifier (SUCI) and wherein the instructions, when executed by the at least one processor, cause the apparatus to obtain a subscription permanent identifier (SUPI) of the subscriber from the SUCI and obtain the SUPI for determining the subscription data of the subscriber.
[0007] According to an example embodiment, the instructions, when executed by the at least one processor, cause the apparatus to provide the authentication request to an authentication server function (AUSF) of the TPLMN.
[0008] According to an example embodiment, the instructions, when executed by the at least one processor, cause the apparatus to discover the AUSF of the TPLMN based, at least, on an identifier of the TPLMN.
[0009] According to an example embodiment, the instructions, when executed by the at least one processor, cause the apparatus to discover the AUSF of the TPLMN based also on a routing identifier.
[0010] According to an example embodiment, the instructions, when executed by the at least one processor, cause the apparatus to provide a roaming value-added service (RVAS) indication and / or an identifier of the TPLMN to an authentication server function (AUSF) of the HPLMN.
[0011] According to a second aspect, an apparatus of a target public land mobile network (TPLMN) is disclosed. The apparatus may comprise at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, from a home public land mobile network (HPLMN) an authentication request to authenticate a subscriber of the HPLMN, the authentication request originating at a serving public land mobile network (serving PLMN) and comprising, at least, a subscription permanent identifier (SUPI) of the subscriber and an identifier of the serving PLMN, and provide a response to the authentication request to an authentication server function (AUSF) of the TPLMN, the response comprising, at least, an identifier of the TPLMN, an identifier of a group of TPLMNs that includes the TPLMN, an authentication vector and an authentication and key management for applications (AKMA) identifier.
[0012] According to a third aspect, an apparatus of a target public land mobile network (TPLMN) is disclosed. The apparatus may comprise at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, from a unified data management function (UDM) of a home public land mobile network (HPLMN), an authentication request to authenticate a subscriber of the HPLMN, the authentication request originating at a serving public land mobile network (serving PLMN), provide the authentication request to a UDM of the TPLMN, receive, from the UDM of the TPLMN, an initial response to the authentication request, the initial response comprising, at least, an identifier of the TPLMN, an identifier of a group of TPLMNs that includes the TPLMN, an authentication vector and an authentication and key management for applications (AKMA) identifier, store an expected response token for the subscriber and compute a hash of the expected response token for the subscriber, and provide a response to the authentication request to an authentication server function (AUSF) of the HPLMN, the response comprising, at least, the hash of the expected response token, an identifier of the AUSF of the TPLMN, the identifier of the TPLMN, the identifier of the group of TPLMNs that includes the TPLMN, the authentication vector and the authentication and key management for applications (AKMA) identifier.
[0013] According to a fourth aspect, an apparatus of a serving public land mobile network (serving PLMN) is disclosed. The apparatus may comprise at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: send an authentication request to authenticate a subscriber of a home public land mobile network (HPLMN) to an authentication server function (AUSF) of the HPLMN, receive a response to the authentication request from the AUSF of the HPLMN, the response comprising an identifier of a target public land mobile network (TPLMN), and include the identifier of the TPLMN as an identifier of the HPLMN in a context of a device associated with the subscriber.
[0014] According to an example embodiment, the response further comprises an identifier of the AUSF of the TPLMN, and the instructions, when executed by the at least one processor, cause the apparatus to: include the identifier of the AUSF of the TPLMN in the context of the device.
[0015] According to an example embodiment, the identifier of the AUSF of the TPLMN is a callback uniform resource identifier. The callback uniform resource identifier may be understood as a location for directing signalling once the subscriber has been authenticated.
[0016] According to an example embodiment, the response further comprises any or all of the following: an identifier of a group of TPLMNs that includes the TPLMN and an authentication vector.
[0017] According to an example embodiment, the response comprises a roaming value-added service (RVAS) indication.
[0018] According to an example embodiment, the instructions, when executed by the at least one processor, cause the apparatus to reinitiate authentication by sending another authentication request to authenticate the subscriber to an AUSF of the TPLMN.
[0019] According to a fifth aspect, an apparatus of a home public land mobile network (HPLMN) is disclosed. The apparatus may comprise at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, from a serving public land mobile network (serving PLMN), a service request from a device associated with a subscriber of the HPLMN, wherein the service request comprises a subscription identifier of the subscriber, and determine a target public land mobile network (TPLMN) based, at least, on the subscription identifier of the subscriber.
[0020] According to an example embodiment, the subscription identifier is a subscription concealed identifier (SUCI) and the instructions, when executed by the at least one processor, cause the apparatus to provide the service request to the TPLMN based on a routing identifier without obtaining a subscription permanent identifier (SUPI) of the subscriber from the SUCI.
[0021] According to an example embodiment, the subscription identifier is a subscription permanent identifier (SUPI) and instructions, when executed by the at least one processor, cause the apparatus to determine the TPLMN by determining, based at least on the SUPI, whether the subscriber is eligible for routing to the TPLMN and based on determining that the subscriber is eligible for routing to the TPLMN, provide the service request to the TPLMN.
[0022] According to an example embodiment, the determining whether the subscriber is eligible for routing to the TPLMN comprises determining whether the subscriber is eligible for a roaming value-added service (RVAS).
[0023] According to an example embodiment, the TPLMN is determined also based on an identifier of the serving PLMN.
[0024] According to an example embodiment, the instructions, when executed by the at least one processor, cause the apparatus to discover an authentication server function (AUSF) of the TPLMN based on the TPLMN and, optionally, a routing identifier, for forwarding the service request, by the UDM of the HPLMN, to the TPLMN.
[0025] According to an example embodiment, the instructions, when executed by the at least one processor, cause the apparatus to discover the AUSF of the TPLMN based also on a routing identifier.
[0026] According to an example embodiment, the service request is provided to an authentication server function (AUSF) of the TPLMN.
[0027] According to an example embodiment, the instructions, when executed by the at least one processor cause the apparatus to, relay all authorized messages received from the serving PLMN to the TPLMN via HPLMN and / or all authorized messages received from the TPLMN to the serving PLMN via HPLMN.
[0028] According to an example embodiment, the instructions, when executed by the at least one processor, cause the apparatus to reject the service request and send a rejection message which causes the UDM of the HPLMN to provide the service request to a service communication proxy function (SCP) of the HPLMN or to a security edge protection proxy function (SEPP) of the HPLMN, the rejection message comprising an identifier of the TPLMN.
[0029] According to an example embodiment, the rejection message comprises a cause code, the cause code causing the UDM of the HPLMN to send the rejection message to the SCP or the SEPP of the HPLMN.
[0030] According to an example embodiment, the instructions, when executed by the at least one processor, cause the apparatus to send the service request to the SCP or the SEPP of the HPLMN, the service request comprising a header having an identifier of the TPLMN.
[0031] According to an example embodiment, the serving PLMN is different from the HPLMN.
[0032] According to a sixth aspect, a method for a home public land mobile network (HPLMN) is disclosed. The method comprises: receiving an authentication request to authenticate a subscriber of the HPLMN from a serving public land mobile network (serving PLMN), determining whether the subscriber is eligible for a roaming value-added service (RVAS) based, at least, on subscription data of the subscriber and an identifier of the serving PLMN, and determining a target public land mobile network (TPLMN) based on the subscriber being eligible for the RVAS.
[0033] According to a seventh aspect, a method for a target public land mobile network (TPLMN) is disclosed. The method comprises: receiving, from a home public land mobile network (HPLMN), an authentication request to authenticate a subscriber of the HPLMN, the authentication request originating at a serving public land mobile network (serving PLMN) and comprising, at least, a subscription permanent identifier (SUPI) of the subscriber and an identifier of the serving PLMN, and providing a response to the authentication request to an authentication server function (AUSF) of the TPLMN, the response comprising, at least, an identifier of the TPLMN, an identifier of a group of TPLMNs that includes the TPLMN, an authentication vector and an authentication and key management for applications (AKMA) identifier.
[0034] According to an eighth aspect, a method for a target public land mobile network (TPLMN) is disclosed. The method comprises: receiving, from a unified data management function (UDM) of a home public land mobile network (HPLMN), an authentication request to authenticate a subscriber of the HPLMN, the authentication request originating at a serving public land mobile network (serving PLMN), providing the authentication request to a UDM of the TPLMN, receiving, from the UDM of the TPLMN, an initial response to the authentication request, the initial response comprising, at least, an identifier of the TPLMN, an identifier of a group of TPLMNs that includes the TPLMN, an authentication vector and an authentication and key management for applications (AKMA) identifier, storing an expected response token for the subscriber and computing a hash of the expected response token for the subscriber, and providing a response to the authentication request to an authentication server function (AUSF) of the HPLMN, the response comprising, at least, the hash of the expected response token, an identifier of the AUSF of the TPLMN, the identifier of the TPLMN, the identifier of the group of TPLMNs that includes the TPLMN, the authentication vector and the authentication and key management for applications (AKMA) identifier.
[0035] According to a ninth aspect, a method for a serving public land mobile network (serving PLMN) is disclosed. The method comprises: sending an authentication request to authenticate a subscriber of a home public land mobile network (HPLMN) to an authentication server function (AUSF) of the HPLMN, receiving a response to the authentication request from the AUSF of the HPLMN, the response comprising an identifier of a target public land mobile network (TPLMN), and including the identifier of the TPLMN as an identifier of the HPLMN in a context of a device associated with the subscriber.
[0036] According to a tenth aspect, a method for a home public land mobile network (HPLMN) is disclosed. The method comprises: receiving, from a serving public land mobile network (serving PLMN), a service request from a device associated with a subscriber of the HPLMN, wherein the service request comprises a subscription identifier of the subscriber, and determining a target public land mobile network (TPLMN) based, at least, on the subscription identifier of the subscriber.
[0037] According to an eleventh aspect, a computer program, a computer program product or a computer readable medium is disclosed. The computer program, computer program product or (non-transitory) computer readable medium may comprise instructions stored thereon for performing a method according to any of the aspects or embodiments disclosed herein or causing a method according to any of the aspects or embodiments disclosed herein to be performed.
[0038] Example embodiments of the present disclosure can thus provide devices, methods, and computer programs for improving routing in a communication network. Any example embodiment may be combined with one or more other example embodiments. These and other aspects of the present disclosure will be apparent from the example embodiment(s) described below. Computer program(s) may be stored on a (non-transitory) computer readable medium, for example as program instructions stored thereon for performing, or causing performance by an apparatus of, any example embodiment of the method(s) disclosed herein. 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).
[0039] DESCRIPTION OF THE DRAWINGS
[0040] The accompanying drawings, which are included to provide a further understanding of the example embodiments and constitute a part of this specification, illustrate example embodiments and, together with the description, help to explain the example embodiments. In the drawings:
[0041] FIG. 1 illustrates an example of an apparatus configured to practice one or more example embodiments;
[0042] FIG. 2 illustrates an example of a message sequence and operations for routing when a UE is connected to a serving PLMN and sends an authentication request to a HPLMN;
[0043] FIG. 3 illustrates another example of a message sequence and operations for routing when a UE is connected to a serving PLMN and sends an authentication request to a HPLMN;
[0044] FIG. 4 illustrates an example of a message sequence and operations for routing when a UE is connected to a serving PLMN and sends a service request to a HPLMN;
[0045] FIG. 5 illustrates another example of a message sequence and operations for routing when a UE is connected to a serving PLMN and sends a service request to a HPLMN;
[0046] FIG. 6 illustrates an example of a method for a HPLMN;
[0047] FIG. 7 illustrates an example of a method for a TPLMN;
[0048] FIG. 8 illustrates another example of a method for a TPLMN;
[0049] FIG. 9 illustrates an example of a method for a serving PLMN;
[0050] FIG. 10 illustrates another example of a method for a HPLMN.
[0051] FIG. 11 illustrates one more example of a method for a HPLMN.
[0052] Like references are used to designate like parts in the accompanying drawings.
[0053] DETAILED DESCRIPTION
[0054] Reference will now be made in detail to example embodiments, examples of which are illustrated in the accompanying drawings. The detailed description provided below in connection with the appended drawings is intended as a description of the present examples and is not intended to represent the only forms in which the present example may be constructed or utilized. The description sets forth the functions of the example and the sequence of steps for constructing and operating the example. However, the same or equivalent functions and sequences may be accomplished by different examples.
[0055] A communication network may be provided with a mechanism for forwarding signalling (e.g., control plane messages) pertaining to a UE associated with a subscriber from the subscriber’s home public land mobile network (HPLMN) to a target public land mobile network (TPLMN) to enable handling (e.g. processing) of signalling pertaining by UE by the target PLMN. The mechanism is configured to forward signalling to appropriate network functions in a target PLMN for handling (e.g., processing), which minimizes the signalling handled in the HPLMN.
[0056] An operator of a HPLMN of a subscriber may have an agreement (e.g., a service level agreement (SLA)) with an operator of a TPLMN and routing policies for routing signalling (e.g., control plane messages) from the HPLMN to the TPLMN for handling (e.g., processing). In case of UEs connected via a serving public land mobile network (serving PLMN), it can be assumed that signalling is forwarded to the TPLMN by the HPLMN.
[0057] A mechanism for subscriber-based routing of signalling to a particular communication network may be provided in a HPLMN of a subscriber. This mechanism forwards signalling received from a UE from the HPLMN to a TPLMN. Some operators of communication networks, such as multi-national operators, may operate more than one PLMN and hence the PLMN of such operators may be identified using more than one identifier (e.g., PLMN ID, i.e. an identifier (ID) for a public land mobile network (PLMN)). Due to business and operational demands, it may be necessary for to route signalling of a certain customers, typically associated with a certain International Mobile Subscriber Identifier (IMSI) range of Universal Subscriber Identity Modules (USIMs) of a PLMN to another PLMN and to further handle the subscriber there. This means the UE is not handled by the “real” HPLMN, according to mobile network code (MNC) and mobile country code (MCC), but by some alternative PLMN. The subscriber based routing of signalling from a home PLMN to a target PLMN, as disclosed herein, can allow several national subsidiaries of a multi-national network operator to offer various services for different customer segments (e.g., for a group of customers) but for operational efficiency the actual service for a certain customer segment (e.g., certain group of customers) may be provided by one or more dedicated PLMNs of the . The subscriber-based routing of signalling of subscribers of a HPLMN can be made invisible to a UE associated with subscriber and the UE associated with subscriber therefore does not need any additional functionality to support this feature (e.g., to operate with PLMN that supports RVAS (e.g., is capable of routing signalling of subscribers).
[0058] A permanent identifier for the UE (generally referred to herein as UE ID), such as Subscription Permanent Identifier (SUPI) or Subscription Concealed Identifier (SUCI) contains an identifier of a HPLMN of a subscriber (generally referred to as Home Network Identifier (e.g., MCC-MNC)), therefore, all signalling (e.g., control plane messages) received from a UE associated with a subscriber can be routed from serving PLMN to HPLMN. However, from an identifier of the subscriber (e.g., SUPI and / or SUCI) it is not possible to identify the TPLMN for a subscriber that needs to be contacted for handling the signalling related to that subscriber. The HPLMN thus cannot straightforwardly forward signalling for a subscriber to a TPLMN, which is different from the HPLMN.
[0059] Subscription data of the subscriber may be handled and / or managed at a TPLMN. Any or all services, such as authentication and / or authorization services for authenticating and / or authorization a subscriber of the HPLMN may be performed by the TPLMN. The subscription data of the subscriber may include an indication that the subscription (for the subscriber or a SUPI range) is handled and / or managed at a TPLMN.
[0060] In a first solution the serving PLMN redirects signalling (e.g., control plane messages) received from the UE to the TPLMN based on information received from the HPLMN. In a second solution, the HPLMN may transfer any or all signalling received from the serving PLMN to the TPLMN by acting as a proxy.
[0061] A UE associated with a subscriber may use an N1 interface to send signalling (e.g., control plane signalling) to an access and mobility function of a communication network via a radio access network (RAN). RAN may comprise one or more access nodes (AN), for example, 5G radio access network nodes (e.g., a gNB).
[0062] A communication system of a PLMN may comprise any or all of the following network functions. Access and mobility management function (AMF) and / or security anchor function (SEAF) may receive signalling (e.g., connection and session request related messages) sent by a UE associated with a subscriber (using the N1 interface. Any reference to AMF may herein be considered as a reference to SEAF and vice versa. AMF and / or SEAF may control connection and mobility management in a communication system of a PLMN. The AMF and / or SEAF may be located in a serving PLMN, to which the UE may be connected / registered. Authentication server function (AUSF) may be configured to authentication, for example for 3GPP access and / or untrusted non-3GPP access. User data management (UDM) function and / or authentication credential repository and processing function (ARPF) may be configured to support, for example, handling user identification (“user identification handling”) (e.g., storage and management of SUPI for each subscriber of the PLMN), support of de-concealment of privacy-protected subscription identifier (SUCI) and / or subscription management. Any reference to UMD may herein be considered as a reference to ARPF and vice versa.
[0063] FIG. 1 illustrates an example of an apparatus 100 configured to practice one or more embodiments described herein. The apparatus 100 may comprise a device (e.g., a computing system) implementing or comprising one or more network functions, or in general a device configured to implement functionality described herein. The apparatus 100 may comprise at least one processor 102. The at least one processor 102 may comprise, for example, one or more of various processing devices, such as for example a central processing unit (CPU), graphic processing unit (CPU), a tensor processing unit, a multi-core processor, a co-processor, a microprocessor, a controller, a digital signal processor (DSP), a processing circuitry with or without an accompanying DSP, or various other processing devices including integrated circuits such as, for example, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a microcontroller unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like.
[0064] The apparatus 100 may further comprise at least one memory 104. The memory 104 may be configured to store, for example, computer program code or the like, for example operating system software and application software. The memory 104 may comprise one or more volatile memory devices, one or more nonvolatile memory devices, and / or a combination thereof. For example, the memory may be embodied as magnetic storage devices (such as hard disk drives, magnetic tapes, etc.), optical magnetic storage devices, or semiconductor memories (such as mask ROM, PROM (programmable ROM), EPROM (erasable PROM), flash ROM, RAM (random access memory), etc.). The memory 104 may be provided as a (non-transitory) computer readable medium.
[0065] The apparatus 100 may further comprise a communication interface 108 configured to enable apparatus 100 to transmit and / or receive information. The communication interface 108 may comprise an internal communication interface such as for example an interface (e.g., SBI or reference point) between different network functions or network function instances of the apparatus 100.
[0066] When the apparatus 100 is configured to implement some functionality, some component and / or components of apparatus 100, such as for example the at least one processor 102 and / or the at least one memory 104, may be configured to implement this functionality. Furthermore, when the at least one processor 102 is configured to implement some functionality, this functionality may be implemented using instructions 106 comprised, for example, in the at least one memory 104.
[0067] The functionality described herein may be performed, at least in part, by one or more computer program product components such as software components. According to an example embodiment, the apparatus 100 comprises a processor or processor circuitry, such as for example a microcontroller, configured by the instructions 106, when executed, to execute the embodiments of the operations and functionality described herein. The instructions 106 which, when executed by the at least one processor 102, cause performance of apparatus 100 may be provided as program code.
[0068] Alternatively, or in addition, the functionality described herein can be performed, at least in part, by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include field-programmable gate arrays (FPGAs), applicationspecific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip systems (SOCs), complex programmable logic devices (CPLDs), graphics processing units (GPUs), or the like.
[0069] The apparatus 100 may be configured to perform method(s) described herein or comprise means for performing method(s) described herein. In one example, the means comprises the at least one processor 102, the at least one memory 104 including the instructions 106 of a network function configured to, when executed by the at least one processor 102, cause apparatus 100 to perform the method(s).
[0070] The apparatus 100 may comprise, for example, a network device, for example, a server, a base station, or the like. Although apparatus 100 is illustrated as a single device, it is appreciated that, wherever applicable, functions of apparatus 100 may be distributed to a plurality of devices.
[0071] The serving PLMN may comprise AMF and / or SEAF (illustrated as “AMF” or “SEAF” in the Figs. 2-5). The HPLMN may comprise AUSF (illustrated as “H-AUSF” in the Figs. 2-5) and / or UMD / ARPF (illustrated as “H-UDM / ARPF” in the Figs. 2-5). A TPLMN may comprise AUSF (illustrated as “T-AUSF” in the Figs) and / or UDM / ARPF (illustrated as “T-UDM / ARPF” in the Figs).
[0072] FIG. 2 illustrates an example of a sequence of messages sent by various entities of a HPLMN and a TPLMN and operations performed by various entities of the HPLMN and the TPLMN for routing signalling sent by an UE associated with subscriber of the HPLMN to the HPLMN. In this example, the UE is connected to a serving PLMN and providing an authentication request to a HPLMN. The authentication request is received from the HPLMN to a TPLMN.
[0073] At 201, the serving PLMN (e.g., SEAF and / or AMF of serving PLMN) receives signalling (e.g., a control plane message such as a N1 message) sent by the UE associated with a subscriber of the HPLMN. The control plane message (e.g., illustrated as N1 message in Fig. 2) sent by the UE includes a SUCI of the UE that is used to authenticate the UE. At 202, the serving PLMN (e.g., a SEAF and / or AMF of the serving PLMN) may provide the SUCI together with a name of the serving PLMN (illustrated as “SN-name” in Fig. 2) to the HPLM of the subscriber associated with the UE. The SUCI and the SN-name may be provided by the serving PLMN (e.g, the SEAF or AMF of the serving PLMN) to the HPLM of the subscriber associated with the UE by sending an authentication request that includes SUCI and the SN-name to the H-AUSF of the HPLMN. The authentication request may be sent by the serving PLMN (e.g, the SEAF or AMF of the serving PLMN) to the HPLMN a service based interface (SBI) message bus and the authentication request may be a Nausf UEAuthentication Authenticate Request message as illustrated in FIG. 2. At 203, the HPLMN (e.g., the H-AUSF) provides the SUCI and the SN name to H-UDM and / or the H-ARPF of the HPLM. The H-AUSF may provide the SUCI and the SN name to the UDM and / or the ARPF of the HPLM by sending an authentication request to the HPLMN (e.g., H-UDM and / or H-ARPF] that includes SUCI and the SN name. The authentication request may be sent to the H-UDM and / or H-ARPF using a SBI message bus of the HPLMN and the authentication request may be a NudmUEAuthenticationGet Request message as illustrated in Fig. 2. The HPLMN (e g., the H-UDM and / or the H-ARPF) may deconceal a SUCI included in the authentication request received to obtain a SUPI, e.g., using a subscriber identity de-concealing function (SIDF). The HPLMN (e.g., H-UDM and / or H-ARPF) may check the subscription data of the subscriber stored in the H-UDM and / or H-ARPF against the SUPI and determine, based on the subscription data, that the subscriber associated with the UE is eligible for a roaming value-added service (RVAS). The RVAS may be understood as any service for subscriber-based routing of signalling to the TPLMN (e.g., routing of signalling of a subscriber of a UE to the TPLMN). The HPLMN (e.g., the H-UDM-H-ARPF]) may utilize the SUPI and optionally also an identifier of the serving PLMN (e.g., in the case the UE is roaming and connected to the serving PLMN) to determine if the subscriber is eligible for RVAS (e.g., routing of signalling of the subscriber associated with the UE to the TPLMN). If signalling of the subscriber associated with UE is eligible for routing to a TPLMN, the HPLMN (e.g., UDM and / or ARPF) may determine the TPLMN (e.g., an identifier of the TPLMN) based on the subscription data of the subscriber associated with the UE. The HPLMN (e.g., UDM and / or ARPF) may also utilize an identifier of the serving PLMN for determining the TPLMN (e.g., the identifier of the TPLMN). At 216, when the HPLMN (e.g., UDM and / or ARPF) receives the authentication request, the HLPLM (e.g., the H-UDM and / or H-ARPF) may de-conceal the SUCI to determine the SUPI of the subscriber and generate an authentication vector (AV) for the subscriber.
[0074] At 204, the HPLMN (e.g., H-UDM and / or H-ARPF) may provide the SUCI (or SUPI if the SUPI is de-concealed from the SUCI), the SN name and an address of the H-AUSF to the TPLMN. The HPLMN (e.g, H-UDM and / or H-ARPF) may provide the SUCI (or SUPI if the SUPI is de-concealed from the SUCI), the SN name and an address of the H-AUSF to the TPLMN by sending an authentication request to the TPLMN (e.g., T-AUSF that includes SUCI (or SUPI if the SUPI is de-concealed from the SUCI), the SN name and an address of the H-AUSF to the TPLMN. The authentication request may be sent by the H-UDM and / or H-ARPF using a SBI message bus of the HPLMN and / or H-ARPF and the authentication request may be a NumdUEAuthenticationGetRequest message as illustrated in Fig. 2. The TPLMN (e g., T-AUSF) may be discovered based on an identifier of the TPLMN and, optionally, a routing ID for identifying a routing path to the TPLMN (if present). At 205, the TPLMN (e.g., T-AUSF) may determine UDM and / or ARPF of the TPLMN and provide the authorization request to the UDM / ARPF of the TPLMN. The authorization request may be sent by the T-AUSF via a SBI message bus and the authorization request may be a Numd UEAuthentication GetRequest message as illustrated in Fig. 2. At 206, the TPLMN (e.g., T-UDM and / or T-ARPF] may provide an initial response comprising an identifier of the TPLMN, an identifier of a group of TPLMNs that includes the TPLMN (UDM-group ID), an authentication vector (AV) and an authentication and key management for applications (AKMA) identifier. The initial response may be sent by the T-UDM and / or T-ARPF) via a SBI of the T-T-PLMN and the initial response may be a NumdUEAuthenticationCreated Response message as illustrated in Fig. 2. A routing from the serving PLMN (e.g., AMF and / or SEAF of the serving PLMN) to the TPLMN may be pre-determined, for example based on a pre-negotiation between the serving PLMN and the TPLMN. Any feature negotiation techniques known to a person skilled in the art of communication networks systems may be utilized.
[0075] At 207, the TPLMN (e.g., T-AUSF) may store an expected response token (RES) for the subscriber and compute a hash of the expected response token (XRES) for the subscriber. At 208, the TPLMN (e.g., AUSF) may provide a response the HXRES, the P-UDM group ID, an identifier of the TPLMN (optionally with an identifier of the AUSF of the TPLMN, e.g. as a callback uniform resource identifier i.e. a callback URI) and the AV to the HPLMN (e.g. AUSF). The response may be sent by the AUSF via a SBI) message bus and the response may be a Numd UEAuthentication Created Response message as illustrated in Fig. 2. At 209, the HPLMN (e.g., AUSF) may provide a response comprising the HXRES, the P-UDM group ID, an identifier of the TPLMN and the AV to the serving PLMN (e.g., SEAF and / or AMF). The response may be sent by the AUSF via a SBI message bus and the response may be a Nausf UEAuthentication Authenticate Response message as illustrated in Fig. 2. At 210, the serving PLMN (e.g., SEAF and / or AMF) may store the identifier of the TPLMN as an identifier of the HPLMN in a context of the UE (e.g., a UE context for the UE associated with the subscriber). The serving PLMN (e.g., SEAF and / or AMF of the serving PLMN) may also store the identifier of the AUSF of the TPLMN in the context of the UE.
[0076] At 211, the serving PLMN [(e.g., the SEAF and / or AMF of the serving PLMN) may send an authentication request to the UE associated with the subscriber. The authentication request may comprise an authentication response (RES*). At 212, based on receiving the authentication response (RES*) from the UE associated with the subscriber, the serving PLMN (e.g. SEAF and / or AMF) may calculate or compute a hash of the authentication response (HRES) and compare it with the HXRES received from the TPLMN (e.g. AUSF) via the HPLMN (e.g. AUSF). At 213, the serving PLMN (e.g., SEAF and / or AMF of the serving PLMN) may provide an authentication request that includes the RES* to the TPLMN (e.g., the T-AUSF), e.g., based on the stored identifier of the TPLMN and, optionally, T-AUSF of the TPLMN, e.g. the callback URI. The authentication request may be sent by the SEAF and / or AMF via a SBI message bus and the authentication request may be a Nausf UEAuthentication Authenticate Request message as illustrated in Fig. 2. At 214, the TPLMN (e.g. AUSF) may authenticate the subscriber associated with UE, e.g. by verifying the RES*. Once the subscriber associated with UE is authenticated, the serving PLMN (e.g., SEAF and / or AMF) may use for all procedures for the (authenticated) subscriber associated with UE (e.g., registration, PDU session establishment etc.), the TPLMN as the HPLMN. At 215 an authentication response is provided to the serving PLMN (e.g., SEAF and / or AMF). The authentication response may comprise a result of authentication, e.g., whether the RES* has been correctly verified or not. The authentication response may also comprise the SUPI and / or a unified anchor key (Kseaf) of the serving PLMN. The authentication response may be sent by the AUSF of the TPLMN via a SBI) message bus and the authentication response may be a Nausf UEAuthentication Authenticate Response message as illustrated in Fig. 2.
[0077] FIG. 3 illustrates another example of a sequence of messages sent by various entities of a HPLMN and a TPLMN and operations performed by various entities of the HPLMN and the TPLMN for routing signalling sent by an UE associated with subscriber of the HPLMN to the HPLMN. In this example, the UE is connected to a serving PLMN and providing an authentication request to a HPLMN. The authentication request is received from the serving PLMN (e.g. SEAF and / or AMF) to a TPLMN after receiving an identifier of the TPLMN from the HPLMN.
[0078] At 301, the serving PLMN (e.g. SEAF and / or AMF) receives signalling (e.g., a control plane message such as a N1 message) sent by the UE associated with a subscriber of the HPLMN. The control plane message (e.g., illustrated as N1 message in Fig. 3) sent by the UE includes a SUCI of the UE that is used to authenticate the UE. At 302, the serving PLMN (e.g. a SEAF and / or AMF of the serving PLMN) may provide the SUCI together with a name of the serving PLMN (illustrated as “SN-name” in Fig. 3) to the HPLM of the subscriber associated with the UE. The SUCI and the SN-name may be provided to the HPLM of the subscriber associated with the UE by sending an authentication request that includes SUCI and the SN-name to the H-AUSF of the HPLMN. The authentication request may be sent by the SEAF and / or AMF via a SBI message bus and the authentication request may be a Nausf UEAuthentication Authenticate Request message as illustrated in Fig. 3. At 303, the HPLMN (e.g. H-AUSF) provides the SUCI and the SN name to H-UDM and / or the H-ARPF of the HPLM. The H-AUSF may provide the SUCI and the SN name to the UDM and / or ARPF of the HPLM by sending an authentication request to the HPLMN (e.g. H-UDM and / or H-ARPF] that includes SUCI and the SN name. The authentication request may be sent to the H-UDM and / or H-ARPF via a SBI message bus and the authentication request may be a NudmUEAuthenticationGet Request message as illustrated in Fig. 3. The HPLMN (e.g., the H-UDM and / or the H-ARPF) may de-conceal a SUCI included in the authentication request received to obtain a SUPI, e.g. using a subscriber identity de-concealing function (SIDF). The HPLMN (e.g. H-UDM and / or H-ARPF) may check the subscription data of the subscriber stored in the H-UDM and / or H-ARPF against the SUPI and determine based on the subscription data, that the subscriber associated with the UE is eligible for a roaming value-added service (RVAS). The RVAS may be understood as any service for subscriber-based routing of signalling to the TPLMN. The HPLMN (e.g. the H-UDM and / or H-ARPF) may utilize the SUPI and optionally also an identifier of the serving PLMN (e.g., in the case the UE is roaming and connected to the serving PLMN) to determine if the authentication request is eligible for routing of signalling of the subscriber associated with the UE to the TPLMN. If signalling of the subscriber associated with UE is eligible for routing to a TPLMN, the HPLMN (e.g. UDM and / or ARPF) may determine the TPLMN (e.g., an identifier of the TPLMN) based on the subscription data of the subscriber associated with the UE. The HPLMN (e.g. UDM and / or ARPF) may also utilize an identifier of the serving PLMN for determining the TPLMN (e.g., the identifier of the TPLMN).
[0079] At 304, when the HPLMN (e.g., UDM and / or ARPF) receives the authentication request, the HPLMN (e.g., the H-UDM and / or H-ARPF) may deconceal the SUCI to determine the SUPI of the subscriber. However, in this example any AV for the subscriber need not be generated. The HPLMN (e.g., UDM and / or ARPF) may check eligibility of signalling of the subscriber associated with the UE for routing to the TPLMN based on the UE subscription data and, optionally, the identifier of the serving PLMN. If signalling of the subscriber associated with UE is eligible for routing to the TPLMN, the HPLMN (e.g., UDM and / or ARPF) need not generate the AV for the subscriber nor provide a de-concealed SUPI to the AUSF of the HPLMN. Instead, the HPLMN (e.g., UDM and / or ARPF) may provide a RVAS indication, that may indicate that signalling of the subscriber associated with the UE is eligible for routing to the TPLMN, and / or an identifier of the TPLMN. The HPLMN (e g., UDM and / or ARPF) may determine the TPLMN (e g., an identifier of the TPLMN) based on the subscription data of the subscriber associated with the UE and may also utilize an identifier of the serving PLMN for determining the target PLMN (e.g., the identifier of the TPLMN). At 305, the HPLMN (e.g. UDM and / or ARPF) may provide a response comprising an identifier of the TPLMN and, optionally, the RVAS indication to the AUSF of the HPLMN. The response may be sent by the UDM and / or ARPF) via SBI message bus and the response may be a Numd UEAuthentication Created Response message as illustrated in Fig. 3. At 306, upon receiving the identifier of the TPLMN and, optionally, the RVAS indication, the HPLMN (e.g. AUSF) may provide a response comprising these to the serving PLMN (e.g. SEAF and / or AMF). The response may be sent by the AUSF via a SBI message bus and the response may be a Numd UEAuthentication Created Response as illustrated in Fig. 3.
[0080] At 307, when the serving PLMN (e.g. SEAF and / or AMF) receives the RVAS indication from the HPLMN and / or based on its local configuration, if the serving PLMN (e.g. SEAF and / or AMF) supports the RVAS feature, may use the identifier of the TPLMN (received from the HPLMN (e.g. AUSF)) as an identifier of the HPLMN in a context of the UE / subscriber. A routing from the serving PLMN (e.g., AMF and / or SEAF of the serving PLMN) to the TPLMN may be predetermined, for example based on a pre-negotiation between the serving PLMN and the TPLMN. Any feature negotiation techniques known to a person skilled in the art of communication systems may be utilized. The serving PLMN (e.g., SEAF and / or AMF of the serving PLMN) may reinitiate the authentication procedure with the TPLMN (e.g. AUSF and / or UDM and / or ARPF of the TPLMN). For this purpose, it may send another authentication request to the TPLMN (e.g. AUSF and / or UDM and / or ARPF of the TPLMN). Any or all other procedures of the serving PLMN may henceforth be carried out with the TPLMN. The serving PLMN (e.g. SEAF and / or AMF) may replace HPLMN with TPLMN (or the identifiers thereof) for any or all authenticated procedures. For unauthenticated procedures of subscriber associated with the UE, the abovementioned operations 301-307 may still be followed.
[0081] Any of the routing as described herein may be utilized in a roaming case or in a non-roaming case. In a roaming case the serving PLMN is different from the HPLMN, whereas in the non-roaming case the serving PLMN is the HPLMN. In the non-roaming case, the serving PLMN (e.g. SEAF and / or AMF) may thus be replaced in the examples provided herein with the HPLMN (e.g. SEAF and / or AMF). The routing mechanism may remain otherwise as illustrated in the examples.
[0082] The examples presented with reference to FIGS. 2 and 3 allow UE authentication via redirecting signalling. In both cases, HPLMN provides information for the serving PLMN to facilitate direct access from the serving PLMN to the TPLMN.
[0083] The examples may involve the following effects. The example of FIG. 2 may impact the AUSF and UDM and / or ARPF of both the HPLMN and the TPLMN and changes can be made there to handle the existing authentication procedures differently. Additional RVAS-related subscriptions may also be introduced in the HPLMN (UDM and / or ARPF). The example of FIG. 2 may also impact serving PLMN (SEAF and / or AMF), as it may replace the HPLMN with TPLMN for any or all NF discovery and / or SBI procedures. The example of FIG. 3 may impact the AUSF and UDM and / or ARPF of the HPLMN but does not need to impact the UDM and / or ARPF or AUSF of the TPLMN. The example of FIG. 2 may also cause a minor impact on the serving PLMN (SEAF and / or AMF), to replace an identifier of the HPLMN with that of the TPLMN received during the authentication attempt towards the HPLMN.
[0084] In solutions in accordance with both examples, signalling and data traffic at the HPLMN may be significantly reduced, as the signalling and data traffic can be routed from the serving PLMN to the TPLMN without transmitting it through the HPLMN. In solutions in accordance with both examples, the subscription data of the UE for the serving PLMN may be provisioned in the TPLMN. In solutions in accordance with both the examples, a multinational operator may choose to deploy specialized service such as IMS in one PLMN and offer the same service by treating that PLMN as TPLMN when the user is roaming or not roaming. For normal UE (not requiring IMS and / or non-RVAS UE) can still be served in the HPLMN. In solutions in accordance with both examples, there can be impact on the serving PLMN (e.g., SEAF and / or AMF) (for roaming).
[0085] In some examples, the serving PLMN is only connected to HPLMN or, at least, has no direct connection possible to the TPLMN. In such a case, any or all messages from the serving PLMN may be relayed to the TPLMN via the HPLMN. In such a case, the serving PLMN is different from the HPLMN. It may also be assumed that once subscription is transferred to the TPLMN, then credentials are also transferred from the HPLMN to the TPLMN. Therefore, it may be assumed that only the TPLMN can de-conceal the SUCI. These features are illustrated in the following examples with reference to FIGS. 4 and 5.
[0086] FIGS. 4 and 5 illustrate two examples of a sequence of messages sent by various entities of a HPLMN and a TPLMN and operations performed by various entities of the HPLMN and the TPLMN for routing signalling sent by an UE associated with subscriber of the HPLMN to the HPLMN. In these examples, the UE is connected to a serving PLMN and providing a service request to a HPLMN. The initial operations may be the same in both cases.
[0087] Optionl:
[0088] For all UEs that are being migrated to the TPLMN, an operator may assign a routing ID. At 401, there are two options. Either (option a)
[0089] At 401, the serving PLMN (e.g., SEAF and / or AMF) may provide a service request from the UE associated with a subscriber of the HPLMN to the HPLMN. The service request may be provided from the serving PLMN (e.g., SEAF and / or AMF) to the UDM and / or ARPF of the HPLMN directly (illustrated option a) or via the AUSF of the HPLMN (illustrated option b). The service request may comprise an authentication message.
[0090] At 402, the HPLMN (e.g., UDM and / or ARPF) may determine whether the UE is eligible for a RVAS and / or routing to the TPLMN. The service request, or the authentication message therein, from the serving PLMN (e.g., SEAF and / or AMF) to the HPLM (e.g., AUSF or UDM and / or ARPF) may comprise a SUCI or a SUPI. If it is SUCI, the HPLMN (e.g., UDM and / or ARPF) may provide the service request, or the authentication message therein, to the TPLMN (e.g., AUSF). This may be done based on the routing ID. If the service request, or the authentication message therein (e.g. as a reauthentication case) targeted to the HPLMN (e.g. UDM and / or ARPF) comprises a SUPI (instead of a SUCI), targeted to UDM, then the HPLMN (e.g. UDM and / or ARPF) may check the subscription data of the subscriber stored in the H-UDM and / or H-ARPF to determine, based on the subscription data, whether the subscriber associated with the UE is eligible for a RVAS feature. If signalling of the subscriber associated with the UE is eligible for routing to a TPLMN, the HPLMN (e.g., UDM and / or ARPF) may determine the TPLMN (e.g., an identifier of the TPLMN). This may be done based on the subscription data of the subscriber associated with the UE, such as the SUPI. The HPLMN (e.g., UDM and / or ARPF) may also utilize an identifier of the serving PLMN for determining the TPLMN (e.g., the identifier of the TPLMN), e.g., in the case of roaming, to determine if the service request is eligible for routing to the TPLMN. The HPLMN (e.g., UDM) may provide the service request to the TPLMN (e.g. AUSF). The TPLMN or the AUSF thereof may be discovered based on an identifier of the TPLMN and, optionally, the routing ID for identifying a routing path to the TPLMN (if present).
[0091] As illustrated in FIG. 4, in a first example the service request may be provided from the HPLMN (e.g., UDM and / or ARPF) to the TPLMN at 403. The service request may be provided from the HPLMN (e.g., UDM and / or ARPF) to the UDM and / or ARPF of the TPLMN directly (illustrated option a) or via the AUSF of the TPLMN (illustrated option b). The service request may comprise the authentication message. At 404 and 405, a response from the TPLMN (e.g. UDM and / or ARPF) may be provided to the HPLMN (e.g. UDM and / or ARPF) to be relayed to the serving PLMN. The message may be provided via the AUSF of the TPLMN. At 406, the response may be provided from the HPLMN (e.g. UDM and / or ARPF) to the serving PLMN (e.g. SEAF and / or AMF). The response may be provided from the HPLMN (e.g., UDM and / or ARPF) to the serving PLMN (e.g., SEAF and / or AMF) directly (illustrated option b) or via the AUSF of the HPLMN (illustrated option a). The response may be provided with a callback of the HPLMN (e.g., UDM and / or ARPF) so that following messages from the serving PLMN to the TPLMN can be relayed via the HPLMN. At 407, any or all following authenticated messages may be relayed from the serving PLMN to the TPLMN via the HPLMN.
[0092] As illustrated in FIG. 5, in a second example the first operations 401 and 402 may be as described above with reference to both FIGS. 4 and 5. However, in this example the AUSF and / or UDM and / or ARPF of the HPLMN does not need to become an AUSF and / or UDM and / or ARPF client. At 503, after the TPLMN has been determined, the HPLMN (e.g., UDM and / or ARPF) may reject the service request and send a rejection message which causes the UDM and / or ARPF of the HPLMN to provide the service request to a service communication proxy function (SCP) of the HPLMN or to a security edge protection proxy function (SEPP) of the HPLMN. The rejection message may comprise an identifier of the TPLMN, for example in a header of the rejection message. The rejection message may also comprise a cause code for facilitating the signalling from the HPLMN to be relayed to the TPLMN via the SCP of the HPLMN or the SEPP of the HPLMN. At 504, the SCP and / or SEPP of the HPLMN may then redirect the message and / or the service request to the TPLMN (e.g., AUSF or UDM and / orARPF). The message and / or the service request may be provided from the SCP / SEPP of the HPLMN to the UDM and / or ARPF of the TPLMN directly (illustrated option b) or via the AUSF of the TPLMN (illustrated option a). At 505, the TPLMN (e.g., UDM and / or ARPF) may provide a response to the message and / or the service request to the serving PLMN (e.g. SEAF and / or AMF). The response may be provided via the AUSF of the TPLMN and the SCP and / or SEPP of the HPLMN. The SCP and / or SEPP of the HPLMN may then relay any or all messages from the serving PLMN to the TPLMN or vice versa.
[0093] In case of home routing, a session management function (SMF) of the serving PLMN may select the SMF of the HPLMN. Once the SMF of the HPLMN receives the session management data (SMData) from the UDM where TPLMN details are given (e.g., H-UDM), then the SMF of the HPLMN may forward the request to a SMF of the TPLMN.
[0094] FIG. 6 illustrates an example of a method for a HPLMN. At 601, the method may comprise receiving an authentication request to authenticate a subscriber of a HPLMN from a serving PLMN, e.g., as in response to operation 203 or 303 in Figs 2 and 3. At 602, the method may comprise obtaining a subscription permanent identifier (SUPI) of the subscriber from the SUCI and obtaining the SUPI for determining the subscription data of the subscriber e.g. as at 304 in Fig. 3. At 603, the method may comprise determining whether the subscriber is eligible for a RVAS based, at least, on subscription data of the subscriber and an identifier of the serving PLMN. At 604, the method may comprise determining a TPLMN based on the subscriber being eligible for the RVAS. At 605, the method may comprise discovering the AUSF of the TPLMN based, at least, on an identifier of the TPLMN and, optionally, on a routing identifier. At 606, the method may comprise providing the authentication request to an authentication server function (AUSF) of the TPLMN, e.g., as at 204 in Fig. 2. At 607, the method may comprise providing a roaming value-added service (RVAS) indication and / or an identifier of the TPLMN to an authentication server function (AUSF) of the HPLMN, e.g., as at 305 in Fig. 3.
[0095] FIG. 7 illustrates an example of a method for a TPLMN. At 701, the method may comprise receiving, from a HPLMN, an authentication request to authenticate a subscriber of the HPLMN, the authentication request originating at a serving PLMN and comprising, at least, a subscription permanent identifier (SUPI) of the subscriber and an identifier of the serving PLMN, e.g., as in response to operation 205 in Fig. 2. At 702, the method may comprise providing a response to the authentication request to an AUSF of A TPLMN, the response comprising, at least, an identifier of the TPLMN, an identifier of a group of TPLMNs that includes the TPLMN, an authentication vector and an AKMA identifier, e.g., as at 206 in Fig. 2.
[0096] FIG. 8 illustrates another example of a method for a TPLMN. At 801, the method may comprise receiving, from a UDM of a HPLMN, an authentication request to authenticate a subscriber of the HPLMN, the authentication request originating at a serving PLMN, e.g., as in response to operation 204 in Fig. 2. At 802, the method may comprise providing the authentication request to a UDM of a TPLMN e.g., as at 205 in Fig. 2. At 803, the method may comprise receiving, from the UDM of the TPLMN, an initial response to the authentication request, the initial response comprising, at least, an identifier of the TPLMN, an identifier of a group of TPLMNs that includes the TPLMN, an authentication vector and an AKMA identifier, e.g., as in response to operation 206 in Fig. 2. At 804, the method may comprise storing an expected response token for the subscriber and computing a hash of the expected response token for the subscriber, e.g., as at 207 in Fig. 2. At 805, the method may comprise providing a response to the authentication request to an AUSF of the HPLMN, the response comprising, at least, the hash of the expected response token, an identifier of the AUSF of the TPLMN, the identifier of the TPLMN, the identifier of the group of TPLMNs that includes the TPLMN, the authentication vector and the AKMA identifier, e.g., as at 208 in Fig. 2.
[0097] FIG. 9 illustrates an example of a method for a serving PLMN. At 901, the method may comprise sending an authentication request to authenticate a subscriber of a HPLMN to an AUSF of the HPLMN, e.g. as at 202 or 302 in Figs. 2 and 3. At 902, the method may comprise receiving a response to the authentication request from the AUSF of the HPLMN, the response comprising an identifier of a TPLMN, e.g. as in response to operation 209 in Fig. 2 or to operation 306 in Fig. 3, and, optionally, an identifier of the AUSF of the TPLMN, the identifier of AUSF of the TPLMN optionally being a callback uniform resource identifier. The response may further optionally comprise any or all of the following: an identifier of a group of TPLMNs that includes the TPLMN and an authentication vector and / or a roaming value-added service (RVAS) indication. At 903, the method may comprise including the identifier of the TPLMN as an identifier of the HPLMN in a context of a device associated with the subscriber, e.g., as at 210 in Fig. 2, optionally, the identifier of the AUSF of the TPLMN in the context of the device. At 904, the method may comprise reinitiating authentication by sending another authentication request to authenticate the subscriber to an AUSF of the TPLMN, e.g., as at 307 in Fig. 3.
[0098] FIG. 10 illustrates another example of a method for a HPLMN. At 1001, the method may comprise receiving, e.g., as in response to operation 401 in Fig. 4, from a serving PLMN, a service request from a device associated with a subscriber of a HPLMN, wherein the service request comprises a subscription identifier of the subscriber. At 1002, the method may comprise determining a TPLMN based, at least, on the subscription identifier of the subscriber, e.g., as at 402 in Fig. 4.
[0099] At 1003, the method comprises, the subscription identifier being a SUCI, e.g. as at option “a)” at 401 in Fig. 4, providing a service request to the TPLMN based on a routing identifier without obtaining a SUPI of the subscriber from the SUCI, e.g., as at option “a” at 403 in Fig. 4. Alternatively at 1004, the method comprises, the subscription identifier being a SUPI, e.g., as at option “b)” at 401 in Fig. 4, determining the TPLMN by determining, based at least on the SUPI and, optionally, on an identifier of the serving PLMN, whether the subscriber is eligible for routing to the TPLMN, e.g. as at 402 in Fig. 4. The determining whether the subscriber is eligible for routing to the TPLMN may comprise determining whether the subscriber is eligible for a roaming value-added service (RVAS). At 1005, the method may comprise discovering an authentication server function (AUSF) of the TPLMN based on the TPLMN and, optionally, a routing identifier, for forwarding the service request, by the UDM or ARPF of the HPLMN, to the TPLMN. At 1006, the method may comprise, based on determining that the subscriber is eligible for routing to the TPLMN, providing the service request to the TPLMN, e.g., as at option “b” at 403 in Fig. 4.
[00100] At 1007, the method may comprise providing the service request to AUSF of the TPLMN, e.g., as at 406 in Fig. 4. At 1008, the method may comprise relaying all authorized messages received from the serving PLMN to the TPLMN via HPLMN and / or all authorized messages received from the TPLMN to the serving PLMN via HPLMN, e.g., as at 407 in Fig. 4.
[00101] FIG. 11 illustrates one more example of a method for a HPLMN. At 1101, the method may comprise receiving, e.g., as in response to operation 401 in Fig. 5, from a serving PLMN, a service request from a device associated with a subscriber of a HPLMN, wherein the service request comprises a subscription identifier of the subscriber. At 1102, the method may comprise determining a TPLMN based, at least, on the subscription identifier of the subscriber, e.g., as at 402 in Fig. 5.
[00102] At 1103, the method may comprise rejecting the service request, e.g. as at 503 in Fig. 5, and sending a rejection message which causes the UDM or ARPF of the HPLMN to provide the service request to a service communication proxy function (SCP) of the HPLMN or to a security edge protection proxy function (SEPP) of the HPLMN, the rejection message comprising an identifier of the TPLMN and, optionally, a cause code, the cause code causing the UDM or ARPF of the HPLMN to send the rejection message to the SCP or the SEPP of the HPLMN. At 1104, the method may comprise sending the service request to the SCP or the SEPP of the HPLMN, e.g. as at 503 in Fig. 5, the service request comprising a header having an identifier of the TPLMN.
[00103] In the methods described in Figs. 6-11, the serving PLMN may be different from the HPLMN.
[00104] Above, any reference to a “UE” or a “user equipment” may be considered as a reference to a subscriber of a HPLMN and / or to a device associated with the subscriber of the HPLMN.
[00105] Further features of the methods directly result from the functionality of the network functions described throughout the description, claims, and drawings, and are therefore not repeated here. An apparatus, such as for example a network device configured to implement one or more network functions, may be configured to perform or cause performance of any aspect of the method(s) described herein. Further, a computer program or a computer program product may comprise instructions for causing, when executed, a device to perform any aspect of the method(s) described herein. Further, a device may comprise means for performing any aspect of the method(s) described herein. According to an example embodiment, the means comprises at least one processor, and memory including program code, the at least one processor, and program code configured to, when executed by the at least one processor, cause the device to perform any aspect of the method(s).
[00106] Any range or device value given herein may be extended or altered without losing the effect sought. Also, any embodiment may be combined with another embodiment unless explicitly disallowed.
[00107] Although the subject matter has been described in language specific to structural features and / or acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as examples of implementing the claims and other equivalent features and acts are intended to be within the scope of the claims.
[00108] It will be understood that the benefits and advantages described above may relate to one embodiment or may relate to several embodiments. The embodiments are not limited to those that solve any or all of the stated problems or those that have any or all of the stated benefits and advantages. It will further be understood that reference to 'an' item may refer to one or more of those items.
[00109] The steps or operations of the methods described herein may be carried out in any suitable order, or simultaneously where appropriate. Additionally, individual blocks may be deleted from any of the methods without departing from the scope of the subject matter described herein. Aspects of any of the example embodiments described above may be combined with aspects of any of the other example embodiments described to form further example embodiments without losing the effect sought.
[00110] The term 'comprising' is used herein to mean including the method, blocks, or elements identified, but that such blocks or elements do not comprise an exclusive list and a method or apparatus may contain additional blocks or elements.
[00111] Although subjects may be referred to as ‘first’ or ‘second’ subjects, this does not necessarily indicate any order or importance of the subjects. Instead, such attributes may be used solely for the purpose of making a difference between subjects.
[00112] As used in this application, the term ‘circuitry’ may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and (b) combinations of hardware circuits and software, such as (as applicable):(i) a combination of analog and / or digital hardware circuit(s) with software / firmware and (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 (c) 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. This definition of circuitry applies to all uses of this term in this application, including in any claims.
[00113] 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.
[00114] It will be understood that the above description is given by way of example only and that various modifications may be made by those skilled in the art. The above specification, examples and data provide a complete description of the structure and use of exemplary embodiments. Although various embodiments have been described above with a certain degree of particularity, or with reference to one or more individual embodiments, those skilled in the art could make numerous alterations to the disclosed embodiments without departing from scope of this specification.
[00115] The expression “at least one of A or B” in this document means A, or B, or both AandB.
Claims
1. An apparatus of a home public land mobile network (HPLMN), the apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:receive an authentication request to authenticate a subscriber of the home public land mobile network from a serving public land mobile network (serving PLMN),determine whether the subscriber is eligible for a roaming value-added service (RVAS) based, at least, on subscription data of the subscriber and an identifier of the serving PLMN, anddetermine a target public land mobile network (TPLMN) for the authentication request based on the subscriber being eligible for the RVAS.
2. The apparatus according to claim 1, wherein the authentication request comprises a subscription concealed identifier (SUCI) and wherein the instructions, when executed by the at least one processor, cause the apparatus to obtain a subscription permanent identifier (SUPI) of the subscriber from the SUCI and obtain the SUPI for determining the subscription data of the subscriber.
3. The apparatus according to any preceding claim, wherein the instructions, when executed by the at least one processor, cause the apparatus to provide the authentication request to an authentication server function (AUSF) of the TPLMN.
4. The apparatus according to claim 3, wherein the instructions, when executed by the at least one processor, cause the apparatus to discover the AUSF of the TPLMN based, at least, on an identifier of the TPLMN.
5. The apparatus according to claim 4, wherein the instructions, when executed by the at least one processor, cause the apparatus to discover the AUSF of the TPLMN based also on a routing identifier.
6. The apparatus according to claim 1 or 2, wherein the instructions, when executed by the at least one processor, cause the apparatus to provide a roaming value-added service (RVAS) indication and / or an identifier of the TPLMN to an authentication server function (AUSF) of the HPLMN.
7. An apparatus of a target public land mobile network (TPLMN), the apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:receive, from a home public land mobile network (HPLMN) an authentication request to authenticate a subscriber of the HPLMN, the authentication request originating at a serving public land mobile network (serving PLMN) and comprising, at least, a subscription permanent identifier (SUPI) of the subscriber and an identifier of the serving PLMN, andprovide a response to the authentication request to an authentication server function (AUSF) of the TPLMN, the response comprising, at least, an identifier of the TPLMN, an identifier of a group of TPLMNs that includes the TPLMN, an authentication vector and an authentication and key management for applications (AKMA) identifier.
8. An apparatus of a target public land mobile network (TPLMN), the apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:receive, from a unified data management function (UDM) or authentication credential repository and processing function (ARPF) of a home public land mobile network (HPLMN), an authentication request to authenticate a subscriber of the HPLMN, the authentication request originating at a serving public land mobile network (serving PLMN),provide the authentication request to a UDM or ARPF of the TPLMN, receive, from the UDM or ARPF of the TPLMN, an initial response to the authentication request, the initial response comprising, at least, an identifier of the TPLMN, an identifier of a group of TPLMNs that includes the TPLMN, an authentication vector and an authentication and key management for applications (AKMA) identifier,store an expected response token for the subscriber and compute a hash of the expected response token for the subscriber, andprovide a response to the authentication request to an authentication server function (AUSF) of the HPLMN, the response comprising, at least, the hash of the expected response token, an identifier of the AUSF of the TPLMN, the identifier of the TPLMN, the identifier of the group of TPLMNs that includes the TPLMN, the authentication vector and the authentication and key management for applications (AKMA) identifier.
9. An apparatus of a serving public land mobile network (serving PLMN), comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:send an authentication request to authenticate a subscriber of a home public land mobile network (HPLMN) to an authentication server function (AUSF) of the HPLMN,receive a response to the authentication request from the AUSF of the HPLMN, the response comprising an identifier of a target public land mobile network (TPLMN), andinclude the identifier of the TPLMN as an identifier of the HPLMN in a context of a device associated with the subscriber.
10. The apparatus according to claim 9, wherein the response further comprises an identifier of the AUSF of the TPLMN, and the instructions, when executed by the at least one processor, cause the apparatus to:include the identifier of the AUSF of the TPLMN in the context of the device.
11. The apparatus according to claim 10, wherein the identifier of the AUSF of the TPLMN is a callback uniform resource identifier.
12. The apparatus according to any of claims 9-11, wherein the response further comprises any or all of the following: an identifier of a group of TPLMNs that includes the TPLMN and an authentication vector.
13. The apparatus according to any of claims 9-12, wherein the response comprises a roaming value-added service (RVAS) indication.
14. The apparatus according to any of claims 9-13, wherein the instructions, when executed by the at least one processor, cause the apparatus to reinitiate authentication by sending another authentication request to authenticate the subscriber to an AUSF of the TPLMN.
15. An apparatus of a home public land mobile network (HPLMN), the apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:receive, from a serving public land mobile network (serving PLMN), a service request from a device associated with a subscriber of the HPLMN, wherein the service request comprises a subscription identifier of the subscriber, anddetermine a target public land mobile network (TPLMN) based, at least, on the subscription identifier of the subscriber.
16. The apparatus according to claim 15, wherein the subscription identifier is a subscription concealed identifier (SUCI) and the instructions, when executed by the at least one processor, cause the apparatus to provide the service request tothe TPLMN based on a routing identifier without obtaining a subscription permanent identifier (SUPI) of the subscriber from the SUCI.
17. The apparatus according to claim 15, wherein the subscription identifier is a subscription permanent identifier (SUPI) and instructions, when executed by the at least one processor, cause the apparatus to determine the TPLMN by determining, based at least on the SUPI, whether the subscriber is eligible for routing to the TPLMN and based on determining that the subscriber is eligible for routing to the TPLMN, provide the service request to the TPLMN.
18. The apparatus according to claim 17, wherein the determining whether the subscriber is eligible for routing to the TPLMN comprises determining whether the subscriber is eligible for a roaming value-added service (RVAS).
19. The apparatus according to claim 17 or 18, wherein the TPLMN is determined also based on an identifier of the serving PLMN.
20. The apparatus according to any of claims 17-19, wherein the instructions, when executed by the at least one processor, cause the apparatus to discover an authentication server function (AUSF) of the TPLMN based on the TPLMN and, optionally, a routing identifier, for forwarding the service request, by the UDM or ARPF of the HPLMN, to the TPLMN.
21. The apparatus according to claim 20, wherein the instructions, when executed by the at least one processor, cause the apparatus to discover the AUSF of the TPLMN based also on a routing identifier.
22. The apparatus according to any of claims 15-21, wherein the service request is provided to an authentication server function (AUSF) of the TPLMN.
23. The apparatus according to any of claims 15-22, wherein the instructions, when executed by the at least one processor cause the apparatus to, relay all authorized messages received from the serving PLMN to the TPLMN viaHPLMN and / or all authorized messages received from the TPLMN to the serving PLMN via HPLMN.
24. The apparatus according to claim 15, wherein the instructions, when executed by the at least one processor, cause the apparatus to reject the service request and send a rejection message which causes the UDM or ARPF of the HPLMN to provide the service request to a service communication proxy function (SCP) of the HPLMN or to a security edge protection proxy function (SEPP) of the HPLMN, the rejection message comprising an identifier of the TPLMN.
25. The apparatus according to claim 24, wherein the rejection message comprises a cause code, the cause code causing the UDM or ARPF of the HPLMN to send the rejection message to the SCP or the SEPP of the HPLMN.
26. The apparatus according to claim 24 or 25, wherein the instructions, when executed by the at least one processor, cause the apparatus to send the service request to the SCP or the SEPP of the HPLMN, the service request comprising a header having an identifier of the TPLMN.
27. The apparatus according to any preceding claim, wherein the serving PLMN is different from the HPLMN.
28. A method for a home public land mobile network (HPLMN), the method comprising:receiving an authentication request to authenticate a subscriber of the HPLMN from a serving public land mobile network (serving PLMN),determining whether the subscriber is eligible for a roaming value-added service (RVAS) based, at least, on subscription data of the subscriber and an identifier of the serving PLMN,anddetermining a target public land mobile network (TPLMN) based on the subscriber being eligible for the RVAS.
29. A method for a target public land mobile network (TPLMN), the method comprising:receiving, from a home public land mobile network (HPLMN), an authentication request to authenticate a subscriber of the HPLMN, the authentication request originating at a serving public land mobile network (serving PLMN) and comprising, at least, a subscription permanent identifier (SUPI) of the subscriber and an identifier of the serving PLMN, andproviding a response to the authentication request to an authentication server function (AUSF) of the TPLMN, the response comprising, at least, an identifier of the TPLMN, an identifier of a group of TPLMNs that includes the TPLMN, an authentication vector and an authentication and key management for applications (AKMA) identifier.
30. A method for a target public land mobile network (TPLMN), the method comprising:receiving, from a unified data management function (UDM) or authentication credential repository and processing function (ARPF) of a home public land mobile network (HPLMN), an authentication request to authenticate a subscriber of the HPLMN, the authentication request originating at a serving public land mobile network (serving PLMN),providing the authentication request to a UDM or ARPF of the TPLMN,receiving, from the UDM or ARPF of the TPLMN, an initial response to the authentication request, the initial response comprising, at least, an identifier of the TPLMN, an identifier of a group of TPLMNs that includes the TPLMN, an authentication vector and an authentication and key management for applications (AKMA) identifier,storing an expected response token for the subscriber and computing a hash of the expected response token for the subscriber, andproviding a response to the authentication request to an authentication server function (AUSF) of the HPLMN, the response comprising, at least, the hash of the expected response token, an identifier of the AUSF of the TPLMN, theidentifier of the TPLMN, the identifier of the group of TPLMNs that includes the TPLMN, the authentication vector and the authentication and key management for applications (AKMA) identifier.
31. A method for a serving public land mobile network (serving PLMN), the method comprising:sending an authentication request to authenticate a subscriber of a home public land mobile network (HPLMN) to an authentication server function (AUSF) of the HPLMN,receiving a response to the authentication request from the AUSF of the HPLMN, the response comprising an identifier of a target public land mobile network (TPLMN), andincluding the identifier of the TPLMN as an identifier of the HPLMN in a context of a device associated with the subscriber.
32. A method for a home public land mobile network (HPLMN), the method comprising:receiving, from a serving public land mobile network (serving PLMN), a service request from a device associated with a subscriber of the HPLMN, wherein the service request comprises a subscription identifier of the subscriber, and determining a target public land mobile network (TPLMN) based, at least, on the subscription identifier of the subscriber.
33. A computer readable medium comprising instructions stored thereon for performing a method according to any of claims 28 to 32.
