Method, apparatus and computer program

Abstract

There is provided a method, apparatus, and computer program for causing a unified data management, UDM, to perform: receiving, from a core network function, a request for first combined subscription information for both a user equipment and a user, wherein the request comprises a first identifier and a second identifier, wherein the second identifier identifies a user of a user equipment, and the first identifier identifies the user equipment; retrieving subscription information for the user based on the first identifier; retrieving subscription information for the user equipment based on the second identifier; determining whether the subscription information for the user and the subscription information for the user equipment can be combined to form the first combined subscription information; and transmitting, to the core network function, an indication that indicates whether the first combined subscription information can be formed.

Description

METHOD, APPARATUS AND COMPUTER PROGRAMRELATED APPLICATIONS

[0001] This patent application claims the benefit of priority of Indian Provisional Patent Application No. 202411010972 filed February 16, 2024, which is hereby incorporated by reference as if reproduced in its entirety.TECHNICAL FIELD

[0002] Various example embodiments of this disclosure relate to a method, apparatus, system and computer program and in particular but not exclusively to apparatus for retrieving subscription information that is common for a user equipment and a user.BACKGROUND

[0003] A communication network can be seen as a facility that enables communications between two or more communication devices, or provides communication devices access to a data network. A mobile or wireless communication network is one example of a communication network. A communication device may be provided with a service by an application server.

[0004] Such communication networks operate in according with standards such as those provided by 3 GPP (Third Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). Examples of standards are the so-called 5G (5th Generation) standards provided by 3GPP.SUMMARY

[0005] Some example embodiments of this disclosure will be described with respect to certain aspects. These aspects are not intended to indicate key or essential features of the embodiments of this disclosure, nor are they intended to be used to limit the scope of thereof. Other features, aspects, and elements will be readily apparent to a person skilled in the art in view of this disclosure.

[0006] According to a first aspect, there is provided an apparatus, the apparatus comprising means for causing a unified data management, UDM, to perform: receiving, from a core network function, a request for first combined subscription information for both a user equipment and a user, wherein the request comprises a first identifier and a second identifier, wherein the second identifier identifies a user of a user equipment, and the first identifier identifies the user equipment; retrieving subscription information for the user based on the first identifier; retrieving subscription information for the user equipment based on the second identifier; determining whether the subscription information for the user and thesubscription information for the user equipment can be combined to form the first combined subscription information; and transmitting, to the core network function, an indication that indicates whether the first combined subscription information can be formed.

[0007] According to a second aspect, there is provided a method for an apparatus, for causing a unified data management, UDM, to perform: receiving, from a core network function, a request for first combined subscription information for both a user equipment and a user, wherein the request comprises a first identifier and a second identifier, wherein the second identifier identifies a user of a user equipment, and the first identifier identifies the user equipment; retrieving subscription information for the user based on the first identifier; retrieving subscription information for the user equipment based on the second identifier; determining whether the subscription information for the user and the subscription information for the user equipment can be combined to form the first combined subscription information; and transmitting, to the core network function, an indication that indicates whether the first combined subscription information can be formed.

[0008] According to a third aspect, there is provided an apparatus comprising: at least one processor; and at least one memory comprising code that, when executed by the at least one processor, causes a unified data management, UDM, to perform: receiving, from a core network function, a request for first combined subscription information for both a user equipment and a user, wherein the request comprises a first identifier and a second identifier, wherein the second identifier identifies a user of a user equipment, and the first identifier identifies the user equipment; retrieving subscription information for the user based on the first identifier; retrieving subscription information for the user equipment based on the second identifier; determining whether the subscription information for the user and the subscription information for the user equipment can be combined to form the first combined subscription information; and transmitting, to the core network function, an indication that indicates whether the first combined subscription information can be formed.

[0009] According to a fourth aspect, there is provided an apparatus for a unified data management, UDM, the apparatus comprising: receiving circuitry for receiving, from a core network function, a request for first combined subscription information for both a user equipment and a user, wherein the request comprises a first identifier and a second identifier, wherein the second identifier identifies a user of a user equipment, and the first identifier identifies the user equipment; retrieving circuitry for retrieving subscription information for the user based on the first identifier; retrieving circuitry for retrieving subscriptioninformation for the user equipment based on the second identifier; determining circuitry for determining whether the subscription information for the user and the subscription information for the user equipment can be combined to form the first combined subscription information; and transmitting circuitry for transmitting, to the core network function, an indication that indicates whether the first combined subscription information can be formed.

[0010] The following may apply in respect of each (e.g., any and / or all) of the first to fourth aspects.

[0011] The indication may indicate that the first subscription information cannot be formed.

[0012] The indication may identify at least one reason why the first subscription information cannot be formed.

[0013] The apparatus may further be caused to perform: combining the subscription information for the user and the subscription information for the user equipment to form the first subscription information; and transmitting, to the core network function, the first subscription information.

[0014] The indication may indicate that the first subscription information can be formed.

[0015] The retrieving the subscription information for the user based on the second identifier may comprise: identifying another UDM or a unified data register, UDR, that is maintaining subscription information for the user corresponding to the second identifier using at least one of a lookup table or information identifying the another UDM or UDR that is comprised in the second identifier; and retrieving the subscription information for the user based on the second identifier from the another UDM or UDR.

[0016] The apparatus may transmit, to the another UDM, a request to register the core network function as serving the user, wherein the request to register the core network function as serving the user equipment comprises the first identifier and the second identifier.

[0017] The retrieving the subscription information for the user equipment based on the first identifier may comprise: identifying another UDM and / or a unified data register, UDR, that is maintaining the subscription information for the user equipment corresponding to the first identifier using a lookup table; and retrieving the subscription information for the user equipment corresponding to the first identifier from the another UDM and / or UDR.

[0018] The apparatus may be caused to perform: transmitting, to the another UDM and / or UDR, a request to register the core network function as serving the user equipment, wherein the request to register the core network function as serving the user equipment comprises the first identifier and the second identifier.

[0019] The determining whether the first subscription information can be combined to form the first subscription information may comprise: identifying, for a same parameter in each of the subscription information for the user and the subscription information for the user equipment, respective values for said parameter; and determining whether the respective values are compatible with each other, wherein when it is determined that the respective values are compatible with each other, determining that the subscription information for the user and the subscription information for the user equipment can be combined to form the first subscription information, and when it is determined that the respective values are incompatible with each other, determining that the subscription information for the user and the subscription information for the user equipment cannot be combined to form the first subscription information.

[0020] The core network function may comprise at least one of: an access and mobility management function, a session management function, a policy control function, a charging function, or a short message service function.

[0021] According to a fifth aspect, there is provided an apparatus comprising means for causing an access and mobility management function, AMF to perform: receiving a first registration request, the first registration request comprising an indication that indicates that the first registration request is for registering a user equipment and a user with the AMF, and a first identifier identifying the user equipment; sending, to a first unified data management function, UDM, a request for combined subscription information for both the user equipment and the user, the request comprising the first identifier identifying the user equipment and the second identifier identifying the user; receiving, from the first UDM, an indication that indicates whether the combined subscription information for both the user equipment and the user can be formed; and determining, based on the indication, whether to accept or deny the first registration request.

[0022] According to a sixth aspect, there is provided a method for an apparatus for causing an access and mobility management function, AMF to perform: receiving a first registration request, the first registration request comprising an indication that indicates that the first registration request is for registering a user equipment and a user with the AMF, and a first identifier identifying the user equipment; sending, to a first unified data management function, UDM, a request for combined subscription information for both the user equipment and the user, the request comprising the first identifier identifying the user equipment and the second identifier identifying the user; receiving, from the first UDM, an indication thatindicates whether the combined subscription information for both the user equipment and the user can be formed; and determining, based on the indication, whether to accept or deny the first registration request.

[0023] According to a seventh aspect, there is provided an apparatus comprising: at least one processor; and at least one memory comprising code that, when executed by the at least one processor, causes an access and mobility management function, to perform: receiving a first registration request, the first registration request comprising an indication that indicates that the first registration request is for registering a user equipment and a user with the AMF, and a first identifier identifying the user equipment; sending, to a first unified data management function, UDM, a request for combined subscription information for both the user equipment and the user, the request comprising the first identifier identifying the user equipment and the second identifier identifying the user; receiving, from the first UDM, an indication that indicates whether the combined subscription information for both the user equipment and the user can be formed; and determining, based on the indication, whether to accept or deny the first registration request.

[0024] According to an eighth aspect, there is provided an apparatus for an access and mobility management function, AMF, the apparatus comprising: receiving circuitry for receiving a first registration request, the first registration request comprising an indication that indicates that the first registration request is for registering a user equipment and a user with the AMF, and a first identifier identifying the user equipment; sending circuitry for sending, to a first unified data management function, UDM, a request for combined subscription information for both the user equipment and the user, the request comprising the first identifier identifying the user equipment and the second identifier identifying the user; receiving circuitry for receiving, from the first UDM, an indication that indicates whether the combined subscription information for both the user equipment and the user can be formed; and determining circuitry for determining, based on the indication, whether to accept or deny the first registration request.

[0025] The following may apply in respect of each (e.g., any and / or all) of the fifth to eighth aspects.

[0026] The AMF may be caused to perform: sending, to the first UDM a request to register the AMF with the UDM for the user equipment and the user, the request to register comprising the first identifier identifying the user equipment and a second identifier identifying the user; and receiving a response to the request to register that indicates whetherthe registration of the AMF for the user equipment and the user has been performed successfully, wherein the sending the request for the combined subscription information is performed when the response to the transmitted request to register indicates that the registration of the AMF for the user equipment and the user has been performed successfully.

[0027] The indication that indicates that the first registration request is for registering a user equipment and a user with the AMF may comprise the second identifier identifying the user.

[0028] The AMF may be caused to perform receiving the second identifier from the user equipment in a secured non-access stratum message sent after the first registration request.

[0029] The second identifier that identifies the user may correspond to a network access identifier, NAI.

[0030] The secured non-access stratum message and / or second identifier may further comprise information identifying the UDM as being a UDM that stores subscription information for the user.

[0031] The indication from the UDM may indicate that the subscription information for both the combined subscription information for both the user equipment and the user cannot be formed, and, based on the indication from the UDM, the determining comprises determining to deny the first registration request.

[0032] The indication from the first UDM may identify at least one reason for the combined subscription information for both the user equipment and the user being unable to be formed, and wherein the AMF is caused to perform transmitting information indicative of the at least one reason to the user equipment.

[0033] The indication from the first UDM may indicate that the combined subscription information for both the user equipment and the user can be formed, and, based on the indication from the UDM, the determining may comprise determining to deny the first registration request.

[0034] The AMF may be caused to perform receiving, from the first UDM, the combined subscription information for both the user equipment and the user, and the apparatus further comprises means for obtaining, from a policy control function, at least one policy for the user equipment based on the received first identifier and on the second identifier that identifies the user, wherein the at least one policy is for configuring the user equipment for communications with a core network.

[0035] The AMF may be caused to perform: receiving, from the user equipment, a second request to register the user equipment with the AMF for another user; determining, based onthe at least one policy, whether to obtain second combined subscription information for both the user equipment and the another specific user; and either rejecting the second request or obtaining the second combined subscription information based on the result of the determining whether to obtain the second subscription information.

[0036] The AMF may be caused to perform obtaining the second subscription information; and determining whether to release the first registration based on the at least one policy.

[0037] The AMF may be caused to perform providing the first and second identifiers to a core network function.

[0038] The core network function may comprise at least one of a session management function, a policy control function, a charging function, or a short message service function.

[0039] The AMF may be caused to perform selecting the first UDM based on the first identifier or the second identifier.

[0040] The selecting the first UDM may comprise using the first identifier and / or second identifier as an index to identify the first UDM, and / or the selecting may comprise extracting an identifier for the first UDM from the second identifier.

[0041] The AMF may be caused to perform: before sending the first registration request, causing at least one of the user or the user equipment to be authenticated in the network.

[0042] According to a ninth aspect, there is provided an apparatus comprising means for causing a core network function to perform: receiving a first service request for a specific user of a user equipment; sending, to a first unified data management function, UDM, a request for subscription information corresponding to both the first user equipment and the specific user, the request comprising a first identifier identifying the user equipment and a second identifier identifying the specific user; receiving, from the first UDM, an indication that indicates whether the subscription information corresponding to both the user equipment and the user can be formed; and determining whether to fulfil the service request based on the indication.

[0043] According to a tenth aspect, there is provided a method for an apparatus for causing a core network function to perform: receiving a first service request for a specific user of a user equipment; sending, to a first unified data management function, UDM, a request for subscription information corresponding to both the first user equipment and the specific user, the request comprising a first identifier identifying the user equipment and a second identifier identifying the specific user; receiving, from the first UDM, an indication that indicateswhether the subscription information corresponding to both the user equipment and the user can be formed; and determining whether to fulfil the service request based on the indication.

[0044] According to an eleventh aspect, there is provided an apparatus comprising: at least one processor; and at least one memory comprising code that, when executed by the at least one processor, causes a core network function, to perform: receiving a first service request for a specific user of a user equipment; sending, to a first unified data management function, UDM, a request for subscription information corresponding to both the first user equipment and the specific user, the request comprising a first identifier identifying the user equipment and a second identifier identifying the specific user; receiving, from the first UDM, an indication that indicates whether the subscription information corresponding to both the user equipment and the user can be formed; and determining whether to fulfil the service request based on the indication.

[0045] According to a twelfth aspect, there is provided an apparatus for a core network function, the apparatus comprising: receiving circuitry for receiving a first service request for a specific user of a user equipment; sending circuitry for sending, to a first unified data management function, UDM, a request for subscription information corresponding to both the first user equipment and the specific user, the request comprising a first identifier identifying the user equipment and a second identifier identifying the specific user; receiving circuitry for receiving, from the first UDM, an indication that indicates whether the subscription information corresponding to both the user equipment and the user can be formed; and determining circuitry for determining whether to fulfil the service request based on the indication.

[0046] The following may apply in respect of each (e.g., any and / or all) of the ninth to twelfth aspects.

[0047] The first service request may comprise the second identifier.

[0048] The first service request may be received from an access and mobility management function, AMF.

[0049] The second identifier that identifies the user may correspond to a network access identifier, NAI.

[0050] The second identifier may comprise information identifying the UDM or UDR as being a UDM or UDR that stores subscription data for the user.

[0051] The indication from the UDM may indicate that the first subscription information corresponding to both the user equipment and user cannot be formed.

[0052] The indication from the UDM may identify at least one reason for why the first subscription information cannot be formed, and the apparatus may further be caused to perform transmitting information indicative of the at least one reason to the access and mobility management function.

[0053] The indication from the UDM may indicate that the first subscription information can be formed.

[0054] The core network function may further be caused to perform receiving the first subscription information subscription information from the UDM; and fulfilling the service request based on the first subscription information.

[0055] The core network function may comprise at least one of a session management function, a policy control function, a charging function, or a short message service function.

[0056] The core network function may further be caused to perform selecting the first UDM based on the first identifier or the second identifier.

[0057] The selecting the first UDM may comprise: using the first identifier and / or second identifier as an index to identify the first UDM, and / or the selecting the first UDM comprises means for extracting an identifier for the first UDM from the second identifier.

[0058] According to a thirteenth aspect, there is provided a user equipment comprising means for performing: transmitting, to a core network of a communication network, a request comprising a first identifier that identifies a user equipment, and an indication that the request is for a specific user; transmitting to the core network, a second identifier that identifies the specific user of the user equipment; receiving, from the core network, at least one policy based on the first and second identifiers; and communicating with the core network based on the at least one policy.

[0059] According to a fourteenth aspect, there is provided a method for a user equipment, the method comprising: transmitting, to a core network of a communication network, a request comprising a first identifier that identifies a user equipment, and an indication that the request is for a specific user; transmitting to the core network, a second identifier that identifies the specific user of the user equipment; receiving, from the core network, at least one policy based on the first and second identifiers; and communicating with the core network based on the at least one policy.

[0060] According to a fifteenth aspect, there is provided an apparatus comprising: at least one processor; and at least one memory comprising code that, when executed by the at least one processor, causes a user equipment to perform: transmitting, to a core network of acommunication network, a request comprising a first identifier that identifies a user equipment, and an indication that the request is for a specific user; transmitting to the core network, a second identifier that identifies the specific user of the user equipment; receiving, from the core network, at least one policy based on the first and second identifiers; and communicating with the core network based on the at least one policy.

[0061] According to a sixteenth aspect, there is provided a user equipment comprising: transmitting circuitry for transmitting, to a core network of a communication network, a request comprising a first identifier that identifies a user equipment, and an indication that the request is for a specific user; transmitting circuitry for transmitting to the core network, a second identifier that identifies the specific user of the user equipment; receiving circuitry for receiving, from the core network, at least one policy based on the first and second identifiers; and communicating circuitry for communicating with the core network based on the at least one policy.

[0062] The following may apply in respect of each (e.g., any and / or all) of the thirteenth to sixteenth aspects.

[0063] The user equipment may further be caused to perform answering an authentication challenge received from the core network to authenticate the end-user.

[0064] The user equipment may further be caused to perform receiving, from the core network, an indication of whether a combined user equipment and user registration has been accepted or rejected based on the request.

[0065] The user equipment may further be caused to perform outputting to the user at least one reason indicating why a combined user equipment and user registration has been rejected.

[0066] In all of the above first to sixteenth aspects, the second identifier may comprise a network access identifier, and / or the first identifier may comprise at least one of a subscription Concealed identifier or a Globally Unique Temporary Identifier.

[0067] According to an aspect, there is provided a non-transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least the method according to any of the preceding aspects.

[0068] 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.DESCRIPTION OF FIGURES

[0069] Some example embodiments will now be described, by way of non-limiting and illustrative example only, with reference to the accompanying Figures in which:

[0070] Figure 1 shows a representation of a 5thgeneration communication system;

[0071] Figure 2 shows a representation of an apparatus for the communication system of Figure 1 according to some example embodiments;

[0072] Figure 3 shows a representation of an apparatus according to some example embodiments;

[0073] Figure 4 shows network signalling;

[0074] Figures 5 to 7 illustrate example network signalling; and

[0075] Figures 8 to 11 illustrate example operations that may be performed by apparatus described herein.DETAILED DESCRIPTION

[0076] The following relates to methods, apparatus, and computer programs for enabling subscription information (which is also referred to as “subscription data” in 3GPP TS 29.505) that is applicable for both a user equipment (UE) and a specific user of that UE.

[0077] The subscription information may relate to at least one core network function and / or

[0078] In the following various example embodiments are explained with reference to communication devices capable of communication with a communication system. Before explaining in detail the embodiments of the methods and apparatuses of the present disclosure, a 5thgeneration communication system (5GS) of a communication network, an access network and a core network (5GC) of the 5GS, and communication devices that communicate with the 5GS are briefly explained with reference to Figures 1, 2, 3, and 4.

[0079] Figure 1 shows a schematic representation of a 5G communication system (5GS) of a public land mobile network (PLMN) or standalone non public network (SNPN) connected to a data network. The 5GS may comprise a user equipment (UE), an access network such as a 5G radio access network (5G-RAN) or next generation radio access network (NG- RAN), a 5G core network (5GC). An application function may be deployed or hosted on a computing system of the 5GS as trusted application function or may be deployed or hosted on one or more application servers of the data network. Such application functions are untrusted application functions. The 5GS connects the UE to a data network via the access network and the 5GC (e.g., a UPF of the 5GC).

[0080] The 5G-RAN may comprise one or more radio access nodes, such as gNodeB (GNB). A gNB may include one or more gNodeB (GNB) distributed units connected to one or moregNodeB (GNB) centralized units. It is noted that the presently described principles apply equally for other 5G access nodes (ANs) such as an Untrusted non 3GPP access terminated at a non-3GPP inter-working function (N3IWF), a Trusted non 3GPP access terminated at a trusted non-3GPP gateway function (TNGF), and / or Wireline access to a 3GPP Core terminated at a Wireline Access Gateway Function (W-AGF).

[0081] The 5GC has a service-based architecture and comprises a plurality of network functions, including: Network Slice Selection Function (NSSF); Network Exposure Function; Network Repository Function (NRF); Policy Control Function (PCF); Unified Data Management (UDM); Application Function (AF); Authentication Server Function (AUSF); an Access and Mobility Management Function (AMF); and Session Management Function (SMF), and a user plane function (UPF). Figure 1 also shows the various interfaces (Nl, N2 etc.) that may be implemented between the various elements of the system. It is understood that all network functions that may be deployed in a 3 GPP Core network have not been drawn in order to keep the figure simple

[0082] Each network function (NF) of the 5GC may provide one or more services to other network functions of the 5GC (or a NF of a 5GC of another communication network (e.g., another PLMN) via Application Programming Interfaces (APIs). Each NF can also register itself and the services it supports (e.g., the services it offers other network functions) to the NRF of the core network 108. The NRF may be used by any network function to discover other network functions (or instances of NFs) and the services the other NFs support (e.g., services the other NFs provide). Any NF may consume (e.g., use) the services provided and exposed by another NF. A NF that consumes a service of another network function is generally referred to as a network function service consumer (NFc). A network function that provides and exposes one or more of its services is referred to as a network function service producer (NFp).

[0083] In the below examples, reference will be made to various core network function that obtain subscription information for a user equipment (UE) from a UDM. Subscription information can be obtained from the UDM at various different times (e.g., during registration, session establishment, etc.). To illustrate an example of this, the obtaining of subscription information with reference to the registration process of a UE with an AMF is discussed below with reference to Figure 4.

[0084] Figure 4 illustrates an existing general registration procedure that is described in Section 4.2.2.2 of 3GPP TS 23.502. In particular, only some of the signalling and / or methodsof this Section are reproduced in Figure 4 in order to provide a contrast with the newly introduced methods of Figure 5 (discussed later).

[0085] Figure 4 illustrates signalling that may be performed between a UE 401, an access network node 402, an access and mobility management function (AMF) 403, a session management function (SMF) 404, and a unified data management (UDM) 405, and a policy control function (PCF) 406.

[0086] During 4001, the UE 401 signals a registration request to AMF 402. Although not shown, this registration request may first be received from the UE 401 by the access network node 402, which selects the AMF 403 for receiving the registration request.

[0087] Section 4.2.2.2 of 3GPP TS 23.502 describes the registration request of 4001 as comprising a registration type, and at least one of an indication of a subscription concealed identifier (SUCI), a 5G globally unique temporary identifier (5G-GUTI) that identifies a mobile device and its associated subscription information, or a permanent equipment identifier (PEI).

[0088] The “registration type” indicates whether the registration request is for an initial registration (e.g., the UE is in a resource management (RM) deregistered state), a mobility registration update (e.g., the UE is in an RM registered state and initiates a registration procedure due to mobility and / or due to the UE updating the UE’s capabilities or protocol parameters, or to request a change of the set of network slice that the UE is allowed to use), a periodic registration update (e.g., the UE is in an RM registered state and initiates a registration procedure based on the periodic registration update timer expiry), an emergency registration (e.g., the UE is in a limited service state), a disaster roaming initial registration or a disaster roaming mobility registration update.

[0089] Based on the received registration request, during 4002 the UE 401, the access network node 402, the access and mobility management function (AMF) 403, the session management function (SMF) 404, and the unified data management (UDM) may perform operations for authenticating the UE 401, and / or obtaining any existing UE context in another AMF. This is described in more detail in Section 4.2.2.2 of 3GPP TS 23.502.

[0090] During 4003, the AMF 403 performs a UDM selection, which results in the selection of UDM 405. This selection is performed based on the received SUPI in Section 4.2.2.2 of 3GPP TS 23.502.

[0091] During 4004, the AMF 403 signals the selected UDM 405. This signalling may comprise the registration request for the UE. This signalling may be performed using anNudm_UECM_Regi strati on service operation. The signalling of 4004 may be for registering AMF 403 with the UDM 405 using Nudm_UECM_Regi strati on for the access for the UE to the AMF 403 to be registered (and for the AMF 403 to subscribe to be notified when the UDM deregisters the AMF 403 during a later registration procedure for another AMF).

[0092] During 4005, the selected UDM 405 signals the AMF 403 to confirm that the AMF 403 has been registered as facilitating network access for the UE 401.

[0093] During 4006, the AMF 403 signals the selected UDM 405. This signalling may comprise a request for subscription information for the UE 401. This signalling may comprise the SUPI received during 4001. This signalling may be performed using an Nudm_SDM_Get service operation. The signalling of 4006 may be for retrieving subscription information for the UE 401 corresponding to only the subscription identifier SUPI. According to Section 4.2.2.2 of 3GPP TS 23.502, this subscription request may request subscription information for the subscriber identifier corresponding to at least one of: Access and Mobility Subscription data, SMF Selection Subscription data, UE context in SMF data, or location services (LCS) mobile origination (depending on the registration type).

[0094] Stated differently, there are a plurality of different types of subscription information that may be requested by at least one network function. Some of these types of subscription information are provided below in Table 1, with reference to the key (e.g., the identifier) that may be used as an index for identifying that subscription data.Table 1 Example types of Subscription information

[0095] During 4007, the selected UDM 405 signals the AMF 403 to provide the requested subscription information of 4006 to the AMF 403.

[0096] Where applicable, the AMF 403 may obtain policy information or request UE policy update by signalling a request (that may or may not comprise the requested subscription information) to a policy control function 406. Later on, when the registration of the UE has been completed the AMF may, based on further UE signaling, contact the SMF in order to have a data session established for the UE.

[0097] For example, the AMF 403 may signal the PCF 406 for requesting policy information corresponding to the UE 401. This signalling may comprise at least part of the subscription information received during 4006. Based on this request, the PCF 406 provides the requested policy information corresponding to the UE’s subscription information to the AMF 403. The AMF 403 may use this subscription information for configuring at least one communication parameter and / or at least one network function for communication between the UE and the core network.

[0098] The AMF may signal the registration of the UE 401 to the SMSF (not shown on the figure).

[0099] Once any updates have been made to existing policy, during 4008 the AMF 403 signals the UE 401 to confirm that the registration has been accepted.

[0100] Figure 2 illustrates an example of a control apparatus 200 for controlling a function of at least one core network function illustrated on Figure 1. The control apparatus 200 may comprise at least one random access memory (RAM) 211a, at least on read only memory (ROM) 211b, at least one processor 212, 213 and a network interface 214. The at least one processor 212, 213 may be coupled to the RAM 211a and the ROM 21 lb. The at least one processor 212, 213 may be configured to execute an appropriate software code 215. Execution of the software code 215 may for example may cause the apparatus to perform operations for controlling a function of the SEPP and / or roaming intermediary (as applicable). The software code 215 may be stored in the ROM 211b. In some embodiments, each function of the SEPP and / or RI is deployed or hosted on a control apparatus 200. In alternative embodiments, two or more functions of the SEPP and / or RI may share a control apparatus.

[0101] Figure 3 illustrates an example of a communication device 300, such as the UE illustrated on Figure 1. The communication device 300 may be provided by any device capable of sending and receiving radio signals. Non-limiting examples of a communication device 300 comprise a user equipment, 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), a personal data assistant (PDA) or a tablet provided with wireless communication capabilities, a machine-type communications (MTC) device, an Internet of things (loT) type communication device or any combinations of these or the like. The communication device 300 may comprise a transceiver for transmitting and / or receiving, for example, wireless signals carrying communications, for example radio signals. The communications may be one or more of voice, electronic mail (email), text messages, multimedia data, machine data and so on.

[0102] The communication device 300 may receive wireless signals (e.g., radio signals) over an air or radio interface 307 via appropriate apparatus for receiving and may transmit wireless signals via appropriate apparatus for transmitting radio signals. In Figure 3 transceiver is designated schematically by block 306. The transceiver 306 may comprise, for example, a radio part and associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device and may comprise one or more antenna elements. The antenna arrangement may be a multi-input multi output (MIMO) antenna.

[0103] The communication device 300 may be provided with at least one processor 301, at least one memory ROM 302a, at least one RAM 302b and other possible components 303 for use in software and hardware aided execution of tasks it is designed to perform, including control of access to and communications with access networks (e.g., the 5G-RAN or NG- RAN illustrated in Figure 1) and other communication devices. The at least one processor 301 is coupled to the RAM 302b and the ROM 302a. The at least one processor 301 may be configured to execute an appropriate software code 308. The software code 308 may for example allow to perform one or more operations of the communication device. The software code 308 may be stored in the ROM 302a.

[0104] The processor, the ROM, and the RAM, the transceiver and other circuitry of the communication device (e.g., a modem) can be provided on a circuit board, in chipsets, or in a system on chip. The circuit board, chipsets or system on chip is denoted by reference 304. The communication device 300 may optionally have a user interface such as key pad 305, touch sensitive screen or pad, combinations thereof or the like. Optionally one or more of a display, a speaker and a microphone may be provided depending on the type of communication device.

[0105] In general, and as illustrated above with respect to Figure 4, a UE is associated with a subscription identifier that is unique for that apparatus and that can be used as an index for obtaining subscription information corresponding to that UE.

[0106] However, in some situations, there may be multiple users that use a same UE to connect to a network at different times. It would be useful to provide a method for enabling each of these users to be associated with their own subscription information for receiving services based on the subscription information of the users. In the following, subscription information corresponding to a user will be called “user profile data”, and subscription information corresponding to a UE will be called “UE subscription data”.

[0107] To address this, the following proposes the use of a so-called “combined” subscription (also referred to herein as a “merged” subscription). This combined subscription is formed based on subscription data corresponding to the user, and subscription data corresponding to the UE.

[0108] The combined subscription information may be formed by at least one UDM. The combined subscription information may be formed by at least one UDM based on receipt of a registration request that comprises both a UE identifier (e.g., a subscription identifier suchas SUCI and / or GUTI) and a user identifier (e.g., an NAI), and / or based on a request for subscription information.

[0109] A UDM may combine User Profile data and UE subscription data to form the combined subscription data in at least one of a plurality of different ways. The way in which User Profile data and UE subscription data may be combined to form the combined subscription data may be based on locally configured operator policies. Some examples of what these policies may include are provided below.

[0110] As a first example, for some parameters (e.g., the data network name (DNN), slice related session management (SM) subscription information, allowed PDU Session Types, allowed Session and Service Continuity (SSC) mode, etc.), the UDM may be configured to run a logical AND operation, such that the values of that parameter are only combined and sent to a requesting 5GC NF when the same values are present in both User Profile data and UE subscription data.

[0111] As another example, for some parameters (e.g., the Generic Public Subscriber Identifier (GPSI)), the information in User Profile data supersedes the same information in UE subscription data.

[0112] As another example, for some parameters (e.g., Quality of Service (QoS) parameters), the UDM takes the lowest (most limitative vale). For example if the UE is allowed to get 5QI 8 while the user is allowed to get 5QI 9, the combined subscription information specifies 5QI 9 (which corresponds to a lower QoS than 5QI 8). As another example, if Interworking with an enhanced packet system (EPS) indication indicates that no EPS interworking is to performed in any of the User Profile data and the UE subscription data, then no EPS interworking is allowed according to the combined subscription.

[0113] As another example, when a parameter is not present in the User profile, values for that parameter in UE subscription data is used for the combined subscription data.

[0114] Further, for some parameters (e.g., Trace Requirements) the UDM may run a logical addition such that the Trace Requirements comprised in the combined subscription data sent to the 5GC NF comprises Trace Requirements from User Profile data and Trace Requirements from UE subscription data.

[0115] Various ways in which the combined subscription data can be used and / or formed are discussed below with reference to Figures 5 to 6.

[0116] As mentioned above, Figure 4 illustrates example signalling that may be performed between entities during a registration procedure. 5 illustrate how such registration signallingmay be adapted to use both a user identifier and a subscription identifier to obtain combined subscription information to be formed that corresponds to both the user and the UE during a registration procedure.

[0117] Figure 5 illustrates signalling that may be performed between a user 501a, a UE 501b, an AMF 503, an SMF 504, a first UDM 505a, and a second UDM 505b.

[0118] Prior to 5001a, a user profile for the user 501a is provided in the second UDM 505b. This user profile may comprise subscription information that is specific for the user 501a.

[0119] Stated differently, there is provided dedicated user profiles for user subscription information.

[0120] A user profile may comprise at least one of the following parameters and considerations.1. User profile identifier. The identifier can be formatted as a network access identifier (NAI) and can be unique per operator. For example, any of the following may be a user profile identifier (also referred to herein as a user identifier): Name.MCCMNC.RoutingID@domain.com or string.routingld@domain.com or Name@domain.com (where domain is built out of the Mobile Country Code and / or Mobile Network Code of the operator and the__Routing Id e.g. domain = RIDxx.MNCyy.MCCzz)The name may be any string of number. As described below, the routing Id may be used to determine the UDM / UDR group storing the user profile.2. An indication of a mapped UE corresponding to that user profile (e.g., SUPI and / or GPSI).3. Slice and / or data network name (DNN) identifier and additional service parameters attached to the user profile. The user profile service parameters may be only a subset of the UE subscription profile that the user profile can register with during the registration to the network.

[0121] The user profile provision in the second UDM 505b could be performed done via any of a plurality of different mechanisms. For example, the user profile could be provided via Operations and Management (0AM) configurations by the operator. As another example, the user profile could be provided in the UDM from an application function via a network exposure function using the parameter provisioning services.

[0122] During 5001a, the user 501a provides a user identifier that identifies the user 501a to the UE 501b (e.g., User profile identifier).

[0123] During 5001b, the UE 501b signals a registration request to AMF 502. Although not shown, this registration request may first be received from the UE 501b by an access network node, which selects the AMF 503 for receiving the registration request.

[0124] In addition to the information described in Section 4.2.2.2 of 3GPP TS 23.502 as being comprised in the registration request of 5001b (e.g., a registration type, and at least one of an indication of a SUCI, a 5G GUTI, or a PEI), the registration request of 5001b further comprises the user identifier and / or an indication that the registration is for a user identifier. The AMF 503 may, once non access stratum (NAS) security has been set up with the UE 501b, request the identifier of the user 501a (e.g., using a secure signalling mechanism).

[0125] Based on the received registration request, during 5002 the UE 501b, the access and mobility management function (AMF) 503, the Authentication Server Function (AUSF), and the first unified data management (UDM) may perform operations for authenticating the UE 501b, . This is described in more detail in Section 4.2.2.2 of 3GPP TS 23.502 and in TS 33.501.

[0126] Then, during 5002b, the AMF 503 may, once NAS security has been set up with the UE 501b request identifier of the user 501a if it has not received it in registration request. The access and mobility management function (AMF) 503, the Authentication Server Function (AUSF), and the second unified data management (UDM) may perform operations for authenticating the user 501a.

[0127] During 5003, the AMF 503 performs a UDM selection, which results in the selection of the first UDM 505a in the present example. This selection is performed based on the received SUPI in Section 4.2.2.2 of 3GPP TS 23.502. Although not shown, it is understood that, as an example, the selection may instead be performed based on the received user identifier and result in the second UDM 505b being selected. For this latter case, the functions performed by the first and second UDMs in the following methods are swapped.

[0128] During 5004, the AMF 503 signals the selected first UDM 505a. This signalling may comprise the UDM registration request for the UE. This signalling may be performed using an Nudm__UECM_Regi strati on service operation. The signalling of 5004 may be for registering AMF 503 with the first UDM 505a using Nudm_UECM_Regi strati on for the access for the user 501a on the UE 501b to the AMF 503 to be registered (and for the AMF 503 to subscribe to be notified when the UDM deregisters the AMF 503 during a laterregistration procedure for another AMF). Thus, the UDM registration request 5004 may contain both the Identity of the user 501a and the Identity of the UE 501b (e.g. SUPI).

[0129] The selected first UDM may cause the second UDM to also perform a registration based on the registration request of 5004. This is illustrated in 5005 to 5006. Although not shown, the first UDM 505a may first select the second UDM 505b by determining that the second UDM 505b corresponds to the identifier of the user 501a.

[0130] During 5005, the first UDM 505a signals the second UDM 505b. This signalling may comprise the registration request for the user 501a on the UE 501b. This signalling of 5005 may be performed using an Nudm_UECM_Regi strati on service operation or a similar service operation.

[0131] During 5006, the second UDM 505b signals the selected first UDM 505a to confirm that the user 501a has been registered to use the UE 501b. During 5005 and / or 5006 the second UDM 505b may check whether the user 501a is not already registered to access to the network via another UE. Steps 5005 and 5006 are optional and may be replaced by the first UDM 505a checking in the subscription whether the registration of the User 501a on the UE 501b is allowed.

[0132] During 5007, the selected first UDM 505a signals the AMF 503 to confirm that the AMF 503 has been registered as facilitating network access for the user 501a on the UE 501b.

[0133] During 5008, the AMF 503 signals the selected first UDM 505a. This signalling may comprise a request for subscription information for the user 501a on the UE 501b. This signalling may comprise the subscription identifier (e.g., SUPI) for the UE 501b received during 5002. This signalling may be performed using an Nudm SDM Get service operation. The signalling of 5008 may be for retrieving subscription information for the UE 501b corresponding to the subscription identifier (e.g., SUPI) and for the user identifier. The user identifier may also (e.g,. in addition to the UE identifier) be comprised in the signalling of 5008. This subscription request may request subscription information for the subscriber identifier and the user identifier corresponding to at least one of: Access and Mobility Subscription data, SMF Selection Subscription data, UE context in SMF data, or location services (LCS) mobile origination (depending on the registration type).

[0134] During 5009, the selected first UDM 505a selects the second UDM 505b by determining that the second UDM 505b corresponds to the user 501a of the user identifier. This may be performed based on an earlier selection of the second UDM 505b (e.g., foroperations 5005 to 5006). The selection may be performed based on at least part of the user identifier. For example, the user identifier may comprise a routing ID (such as described herein in relation to a user profile), which may be used to identify the second UDM.

[0135] The selection may be performed in any of a plurality of different ways. For example, when at least part of the user identifier comprises a routing identifier (e.g., when the UE identifier comprises an NAI), the first UDM 505a may use the routing identifier to identify and select the second UDM 505b. As another example, the first UDM may be configured with, or otherwise have access to, a lookup table and / or correspondence table that pairs a user identifier (or a part thereof) with a specific UDM. In this latter case, the first UDM 505a may select the second UDM 505b by using the received user identifier as an index to lookup the second UDM that corresponds with that received user identifier.

[0136] During 5010, the first UDM 505a signals the second UDM 505b. This signalling may comprise a request for user subscription information corresponding to the user identifier. The signalling may comprise the user identifier.

[0137] During 5011, the second UDM 505b signals the first UDM 505a. this signalling may comprise the requested user subscription information of 5010 to the first UDM 505a.

[0138] During 5012, the first UDM 505a combines (e.g., merges) the received user subscription of 5011 with the UE subscription corresponding to the UE identifier to form so- called “merged” subscription information. This may be performed as discussed above.

[0139] During 5013, the merged subscription information is signalled to the AMF 503 from the first UDM 505a.

[0140] As described above in Figure 4, where applicable, the AMF 503 may obtain policy information and / or request UE policy update by signalling a request (that may or may not comprise the requested subscription information) to a policy control function 506.

[0141] For example, the AMF 503 may signal the PCF 506 for requesting policy information corresponding to the user 501a accessing the network via the UE 501b. This signalling may comprise at least part of the subscription information received during 5013. Based on this request, the PCF 506 provides the requested policy information corresponding to the UE’s subscription information to the AMF 503. The AMF 503 may use this subscription information for configuring at least one communication parameter and / or at least one network function for communication between the UE and the core network.

[0142] The AMF may signal the registration of the user 501a accessing the network via the UE 501b to the SMSF (not shown on the figure) providing both the identifier of the user501a and the identifier of the UE 501bthe AMF 503 signals the UE 501 during 5014 to confirm that the registration of 5001b has been accepted.

[0143] Subsequent to the registration being accepted during 5014, at least one core network function may obtain and use new merged subscription information that corresponds to a combination of user subscription information and UE subscription information and / or obtain and use the merged subscription information discussed above in relation to 5010. This is illustrated below with respect to a short message service function (SMSF) and / or an SMF in Figures 5 and 6 respectively.

[0144] Figure 6 illustrates signalling that may be performed between a user 601a, a UE 601b, an AMF 603, an SMSF 607, a first UDM 605a, and a second UDM 605b. The signalling of Figure 6 is for registering of the user 501a accessing the network via the UE 501b for SMS over a non access stratum signalling.

[0145] The signalling of Figure 6 may be performed between 5013 and 5014, and / or may be performed after 5014. The signalling of Figure 6 may be further understood in light of the context provided by Figure 4.13.3.1-1 of 3GPP 23.502.

[0146] During 6001, the AMF 603 selects SMSF 607. This selection may be performed based on the merged subscription information received by the AMF during 5013. For example, the merged subscription information may comprise at least one set of parameters that define properties of the SMSF to be selected during 6001. As another example, the merged subscription information may comprise at least one identifier that can be used for identifying the SMSF 607 as the SMSF 607 to be selected during 6001.

[0147] During 6002, the AMF 603 signals the SMSF 607. This signalling may comprise a request to activate an SMS service for the UE 601. This signalling may comprise an Nsmsf_SMService_Activate service operation.

[0148] In an example, this signalling of 6002 may comprise at least part of the merged subscription information of 5013 (e.g., a part of the merged subscription information relating to the SMSF alone, such as SMSF management subscription information). In such an example, the SMSF 607 may use the at least part of the merged subscription information to apply in respect of communications with the UE 601 using non-access stratum signalling. The SMSF 607 may proceed directly to 6010 following this.

[0149] In another example, this signalling of 6002 may comprise both the subscriber identifier (e.g., SUPI), and user identifier received during 5001b and / or 5002b (e.g., the signalling of 6002 may not comprise at least part of the merged subscription information).The SMSF may be configured to use at least one of the subscription identifier and user identifier comprised in the signalling of 6002 to select a UDM from which to obtain subscription information. This is illustrated by the signalling of 6003 to 6010.

[0150] During 6003, the SMSF 607 performs a UDM selection. This selection may be performed based on the received subscriber identifier (e.g., SUPI), and user identifier. This selection results in the selection of the first UDM 605a in the present example but may also result in the second UDM 605b being selected. For this latter case, the functions performed by the first and second UDMs in the following methods are swapped.

[0151] During 6004, the SMSF 607 signals the selected first UDM 605a. This signalling may comprise a request for registering the SMSF for SMS service on behalf of the user and the UE and a request for subscription information for SMS service on behalf of the user and the UE (e.g., the signalling 6004 may comprise a registration request and a subscription get for the user 601a on the UE 601b (e.g., the signalling may comprise both identifiers of the user 601a and of the UE 601b for each of the registration request and the subscription get request). This signalling may be performed using an Nudm_UECM_Regi strati on service operation. The signalling of 6004 may be for registering SMSF 603 with the first UDM 605a using Nudm__UECM_Regi strati on.

[0152] This signalling. This signalling of 6004 may also include an Nudm_SDM_Get service operation for retrieving subscription information for the UE 601b corresponding to the subscription identifier (e.g., SUPI) and for the user identifier. This subscription request may request subscription information for the subscription identifier and the user identifier corresponding to at least one of: SMS Management Subscription data

[0153] During 6005, the selected first UDM 605a selects the second UDM 605b by determining that the second UDM 605b corresponds to the user 601a of the user identifier. The selection may be performed based on at least part of the user identifier. For example, the user identifier may comprise a routing ID (such as described herein in relation to a user profile), which may be used to identify the second UDM.

[0154] The selection may be performed in any of a plurality of different ways. For example, when at least part of the user identifier comprises a routing identifier (e.g., when the UE identifier comprises an NAI), the first UDM 605a may use the routing identifier to identify and select the second UDM 605b. As another example, the first UDM may be configured with, or otherwise have access to, a lookup table and / or correspondence table that pairs a user identifier (or a part thereof) with a specific UDM. In this latter case, the first UDM 605amay select the second UDM 605b by using the received user identifier as an index to lookup the second UDM that corresponds with that received user identifier. As another example, information to select the second UDM 605b may have been received by the first UDM 605a in step 6004 from the SMSF 607 whereby the SMF 607 has itself received it from the AMF 603 in step 6002

[0155] During 6006, the first UDM 605a signals the second UDM 605b. This signalling may comprise a request for user subscription information corresponding to the user identifier. The signalling may comprise the user identifier.

[0156] During 6007, the second UDM 605b signals the first UDM 605a. This signalling may comprise the requested user subscription information of 6006.

[0157] .During 6008, the first UDM 605a combines (e.g., merges) the received user subscription of 6007 with the UE subscription corresponding to the UE identifier to form so- called “merged” or “combined” subscription information.

[0158] During 6009, the combined subscription information is signalled to the SMSF 607 from the first UDM 605a.

[0159] During 6010, the SMSF 607 responds to the AMF 603 signalling of 6002 (e.g., using the Nsmsf_SMService_Activate service operation response message). The AMF stores SMSF Information received during 6009 as part of the UE context.

[0160] Figure 7 illustrates signalling that may be performed between a user 701a, a UE 701b, an AMF 703, an SMF 704, a first UDM 705a, and a second UDM 705b. The signalling of Figure 7 is for establishing a PDU session that corresponds to the combination of the user identifier and the subscription identifier.

[0161] The signalling of Figure 7 may be performed after 5014. The signalling of Figure 7 may be further understood in light of the context provided by Figure 4.3.2.2.1of 3GPP 23.502.

[0162] During 7000 the UE 701b signals via an NAS PDU session establishment request, a request to establish a PDU session.

[0163] During 7001, the AMF 703 selects SMF 704. This selection may be performed based on a received PDU session establishment request received from the UE 701b. This selection may be performed based on the merged subscription information received by the AMF during 5013. For example, the merged subscription information may comprise at least one set of parameters that define properties of the SMF to be selected during 7001. As anotherexample, the merged subscription information may comprise at least one identifier that can be used for identifying the SMF 704 as the SMF 704 to be selected during 7001.

[0164] During 7002, the AMF 703 signals the SMF 704. This signalling may comprise a request to create session management context for the PDU session to be established for the UE 701b. This signalling may comprise an Nsmf_PDUSession_CreateSMContext Request service operation.

[0165] In an example, this signalling may comprise both the subscriber identifier (e.g., SUPI), and user identifier determined during the registration of the user 701a / 501a onto the UE 70 lb / 50 lb (as detailed in FIG. 5). The SMF may be configured to use at least one of the subscription identifier and user identifier comprised in the signalling of 7002 to select a UDM from which to obtain session management subscription information. This is illustrated by the signalling of 7003 to 7010.

[0166] During 7003, the SMF 704 performs a UDM selection. This selection may be performed based on the received identifiers of the user 501a and of the UE 501b or based on UDM selection information provided by the AMF instep 7002. This may result in the selection of the first UDM 705a in the present example Although not shown, it is understood that, as another example, the selection may instead be performed based on the received user identifier and result in the second UDM 705b being selected. For this latter case, the functions performed by the first and second UDMs in the following methods are swapped.

[0167] During 7004, the SMF 704 signals the selected first UDM 705a. This signalling may comprise a request for registering the SMF for the PDU session established on behalf of the user and the UE and a request for subscription information for the PDU session established on behalf of the user and the UE (e.g., the signalling may comprise a registration request and a subscription information get). This signalling for the registration request may be performed using an Nudm_UECM_Regi strati on service operation. The signalling of 7004 may be for registering SMF 704 with the first UDM 705a using Nudm_UECM_Regi strati on for the access for the UE to the SMF 704 to be registered.

[0168] The signalling to get subscription information may be performed using an Nudm SDM Get service operation. The signalling of 7004 may be for retrieving subscription information for the UE 701b corresponding to the subscription identifier (e.g., SUPI) and for the user identifier. This subscription request may request subscription information for the subscription identifier and the user identifier corresponding to at least one of: Session Management Subscription data

[0169] During 7005, the selected first UDM 705a selects the second UDM 705b by determining that the second UDM 705b corresponds to the user 701a of the user identifier. The selection may be performed based on at least part of the user identifier. For example, the user identifier may comprise a routing ID (such as described herein in relation to a user profile), which may be used to identify the second UDM.

[0170] The selection may be performed in any of a plurality of different ways. For example, when at least part of the user identifier comprises a routing identifier (e.g., when the UE identifier comprises an NAI), the first UDM 705a may use the routing identifier to identify and select the second UDM 705b. As another example, the first UDM may be configured with, or otherwise have access to, a lookup table and / or correspondence table that pairs a user identifier (or a part thereof) with a specific UDM. In this latter case, the first UDM 705a may select the second UDM 705b by using the received user identifier as an index to lookup the second UDM that corresponds with that received user identifier. As another example, information to select the second UDM 705b may have been received by the first UDM 705a during 7004 from the SMF, where the SMF 704 has itself received it from the AMF 703 in step 7002.

[0171] During 7006, the first UDM 705a signals the second UDM 705b. This signalling may comprise a request for user subscription information corresponding to the user identifier. The signalling may comprise the user identifier.

[0172] During 7007, the second UDM 705b signals the first UDM 705a. This signalling may comprise the requested user subscription information of 7006.

[0173] .During 7008, the first UDM 705a combines (e.g., merges) the received user subscription of 7007 with the UE subscription corresponding to the UE identifier to form so- called “merged” or “combined” subscription information.

[0174] During 7009, the combined subscription information is signalled to the SMF 704 from the first UDM 705a.

[0175] During 7010, the SMF 704 responds to the UE via the AMF 703 signalling of 7002 e.g., using the Namf_Communication_NlN2MessageTransfer service operation) and the AMF transfers the NAS PDU session establishment response to the UE 701b via the 5G AN 702. An Nsmf_PDUSession_CreateSMContext response may have already been sent to the AMF but is not shown in Figure 7 for simplicity .

[0176] In general, the above examples of Figures 5 to 7 illustrate a new method to a wireless network that allows the dynamic association of a first identifier (ID1) with a second identifier(ID2), where ID1 identifies the User using a device (e.g., User Equipment UE in a 3GPP network) and ID2 identifies the device or the subscription of the device used by the User (e.g., a SIM of an User Equipment UE in a 3GPP network).

[0177] ID1 may belong to a defined set of user identifiers that are dedicated to at least one ID2. Stated differently, there may be a plurality of users (each user having or otherwise corresponding to a respective value for ID1) that access a network using a same UE having ID2.

[0178] Further, ID1 may belong to different sets of user identifiers, where each set is dedicated to ID2. Stated differently, each user (each user having or otherwise corresponding to a respective value for ID1) may access a network using a plurality of different UE, each UE having a respective value for ID2.

[0179] ID1 may be provided as an NAI, SUPI, and / or GPSI. This is illustrated in Table 2, below, which shows at least one field of the user profile as comprising at least one user identifier.Table 2 User Profile parameters

[0180] ID2 may be provided as a SUPI, and / or a GPSI.

[0181] As illustrated above, the dynamic association of a value of ID1 with a value of ID2 can be performed during another network procedure (e.g., Registration procedure in 3GPPas described above with reference to Figure 5).

[0182] The dynamic association may be performed based on receipt of an indication parameter, IPDA. For example, when IPDA is comprised in signalling received at a core network function (e.g., an Access and Mobility Management Function, AMF), the core network function may use receipt of IPDA to trigger processes for causing ID1 to be dynamically associated with ID2.

[0183] IPDA may be pre-configured in the UE and be provided as a new parameter from the UE to a NF. Alternatively, the IPDA may be pre-configured in a core NF. The NF may belong to the (Radio) Access Network (R)AN or Core Network (CN). Further, a first NF may provide IPDA to a second NF, where both NFs may be located in (R)AN or CN in any combination.

[0184] When a first NF that is responsible for the Access Management (e.g., AMF in 3GPP networks) receives the IPDA from the UE, the first NF causes a received ID1 and ED2 to be forwarded to a second NF, where the second NF is responsible for retrieving subscription information based on the received ID1 and ID2.

[0185] The second NF may query a third NF to retrieve respective subscription information of ID1 and / or subscription information of ID2, and combine the respective subscription information according to a defined policy to form a common set of combined subscription information for the current user using the UE. For example, when the second NF stores subscription information of ID1, the second NF may contact the third NF to retrieve subscription information of ID2 from the third NF. Analogously, when the second NF stores subscription information of ID2, the second NF may contact the third NF to retrieve subscription information of ID1 from the third NF.

[0186] The second NF provides the common set, or at least selected parts of the common set, of the combined subscription information to at least one other NF (e.g., an AMF, anSMSF, a PCF, and / or an SMF). The UE that the User is using may also receive the common set, or at least selected parts of the common set, of the combined subscription information. Respective protocols that are used to exchange messages between NFs and a NF with a device may be updated to support the common set or at least selected parts of the common set of subscription information.

[0187] When a new User (whose ID1 is herein represented by ID3) wants to use the UE with which ID1 is already registered, the UE may inform the new User that an association of ID1 with ID2 already exist. The new User may provide an input to the UE that indicates to the UE to initiate a new dynamic association of ID3 with ID2.

[0188] Based on this received input (or some other local configuration to proceed with the register ID3 with EDI), the first NF and / or the second NF may initiate actions for handling the association of EDI and ID2 subsequent to a request for ID3 to be registered as being associated with ID3.

[0189] For example, a first policy may define setting communication services defined for the association of ID1 with ID2 to inactive and initiate new communication services for the new association ID3 with ID2 i.e., multiple dynamic associations of user IDs with a single UE ID coexists.

[0190] As another example, a second policy may not allow multiple Users using a single device. When a network function applies this second policy, then the communication services for EDI with ID2 association are terminated, and the association EDI with ED2 is replaced by the association of ID3 with ID2.

[0191] When it is not possible to combine the different subscription information of the user and the UE, a registration reject message may be transmitted to the UE.

[0192] It would be useful for the registration reject message to comprise information identifying the reason for the registration reject message being transmitted. For example, the registration reject message may comprise a bit pattern that corresponds to a registration rejection reason of “USER identity not allowed). The registration reject message may comprise another bit pattern that corresponds to at least one of the following reasons for the rejection: a) Time parameter not allowed - Next X duration. b) Location not allowed. c) UE not allowed d) network not allowed for the user.

[0193] When the UE receives rejection reason a) or c), the UE may abstain from initiating any further registration procedure using the same User identifier as the user identifier that was rejected for a duration of time (e.g., X timing units, which may be either preconfigured or signalled as part of the rejection message).

[0194] When the UE receives rejection reason b), the UE may output an error message to the user that indicates that the user is not allowed to register in that location.

[0195] When the UE receives rejection reason d)), the UE may abstain from reregistering the user with the UE in that network.

[0196] Similar such options may be possible for rejection messages transmitted during the PDU Session Establishment procedure.

[0197] At least some of the features of the above-mentioned examples are highlighted below with respect to Figures 8 to 11.

[0198] Figure 8 illustrates features that may be performed by an apparatus for causing a UDM to perform the steps of Figure 8. The functionality of the apparatus of Figure 8 may be performed by the apparatus described in connection with Figure 2.

[0199] During 801, the apparatus receives, from a core network function, a request for first combined subscription information for a user equipment and a user, wherein the request comprises a first identifier and a second identifier, wherein the second identifier identifies a user of a user equipment, and the first identifier identifies the user equipment.

[0200] The core network function may comprise an apparatus for performing functionality of at least one of an AMF, and SMF, a PCF, a charging function, or an SMSF. The core network function may correspond to the apparatus of at least one of Figures 9 or 10.

[0201] The request for first combined subscription information may comprise at least one of the second identifier or the first identifier. The identifier of the user equipment may be as described above. The identifier of the user may be as described above.

[0202] During 802, the apparatus retrieves, subscription information for the user based on the first identifier.

[0203] During 803, the apparatus retrieves subscription information for the user equipment based on the second identifier.

[0204] During 804, the apparatus determines whether the (retrieved) subscription information for the user and the (retrieved) subscription information for the user equipment can be combined to form the first combined subscription information.

[0205] During 805, the apparatus transmits, to the core network function, an indication that indicates whether the first combined subscription information can be formed.

[0206] The indication transmitted to the core network function may indicate that the first subscription information cannot be formed. This type of indication may be transmitted when the apparatus determines during 804 that the (retrieved) subscription information for the user and the (retrieved) subscription information for the user equipment cannot be combined to form the first combined subscription information. In such a situation, the indication may identify at least one reason why the first subscription information is unable to be formed. One or more ways of performing this may be as described above in relation to the registration rejection messages.

[0207] When the apparatus determines during 804 that the (retrieved) subscription information for the user and the (retrieved) subscription information for the user equipment can be combined to form the first combined subscription information, the apparatus may combine the subscription information for the user and the subscription information for the user equipment to form the first subscription information, and transmit, to the core network function, the first subscription information. In this example, the indication indicates that the first subscription information can be formed. The indication may comprise the presence of the first subscription information itself (e.g., the first subscription information forms the indication). The indication that indicates that the subscription information for the use and the subscription information for the user equipment can be combined may be separate (e.g., comprised in a separate field from) the first subscription information.

[0208] When at least one of the above-mentioned retrieving steps involves retrieving subscription information from another UDM, the apparatus of Figure 8 may cause the

[0209] The retrieving the subscription information for the user based on the second identifier may comprise identifying another UDM or a unified data register, UDR, that is maintaining subscription information for the user corresponding to the second identifier using at least one of a lookup table or information identifying the another UDM or UDR that is comprised in the second identifier, and retrieving the subscription information for the user based on the second identifier from the another UDM or UDR. This may correspond to the situation when the UDM caused to perform 801 to 805 comprises (e.g., stores) subscription information for the user equipment, while the another UDM comprises subscription information for the user. The second identifier may be used as an index to a lookup table that pairs the second identifier with the another UDM. The second identifier may comprise an identifier for theanother UDM when, for example, the second identifier comprises an NAI that comprises a routing id corresponding to the another UDM.

[0210] When the another UDM comprises subscription information for the user, the UDM may cause the another UDM to register the core network function (e.g., an AMF) as serving the user equipment. Stated differently, the UDM is caused to transmit, to the another UDM, a request to register the core network function as serving the user, wherein the request to register the core network function as serving the user equipment comprises the first identifier and the second identifier.

[0211] The retrieving the subscription information for the user equipment based on the first identifier may comprise identifying another UDM and / or a unified data register, UDR, that is maintaining the subscription information for the user equipment corresponding to the first identifier using a lookup table, and retrieving the subscription information for the user equipment corresponding to the first identifier from the another UDM and / or UDR. This may correspond to the situation when the UDM caused to perform 801 to 805 comprises (e.g., stores) subscription information for the user, while the another UDM comprises subscription information for the user equipment. The first identifier may be used as an index to a lookup table that pairs the first identifier with the another UDM.

[0212] When the another UDM comprises subscription information for the user equipment, the UDM may cause the another UDM to register the core network function (e.g., an AMF) as serving the user equipment. Stated differently, the UDM is caused to transmit, to the another UDM, a request to register the core network function as serving the user equipment, wherein the request to register the core network function as serving the user equipment comprises the first identifier and the second identifier.

[0213] The determining whether the first subscription information can be combined to form the first subscription information may comprise: identifying, for a same parameter in each of the subscription information for the user and the subscription information for the user equipment, respective values for said parameter; and determining whether the respective values are compatible with each other, wherein when it is determined that the respective values are compatible with each other, determining that the subscription information for the user and the subscription information for the user equipment can be combined to form the first subscription information, and when it is determined that the respective values are incompatible with each other, determining that the subscription information for the user and the subscription information for the user equipment cannot be combined to form the firstsubscription information. The determination of whether the respective values are compatible with each other may be as described above in relation to the policies for combining subscription information.

[0214] Figure 9 illustrates operations that may be performed by an apparatus for causing an access and mobility management function, AMF to perform the features of 901 to 904. The AMF may correspond to the core network function discussed above in relation to Figure 8. The functionality of the apparatus of Figure 9 may be performed by the apparatus described in connection with Figure 2.

[0215] During 901, the apparatus receives a first registration request, the first registration request comprising an indication that indicates that the first registration request is for registering a user equipment and a user with the AMF and a first identifier identifying the user equipment.

[0216] During 902, the apparatus sends, to the first unified data management function, UDM, a request for combined subscription information for both the user equipment and the user, the request comprising the first identifier identifying the user equipment and the second identifier identifying the user. The first UDM may correspond to the first UDM of Figure 8.

[0217] During 903, the apparatus receives, from the first UDM, an indication that indicates whether the combined subscription information for both the user equipment and the user can be formed.

[0218] During 904, the apparatus determines, based on the indication, whether to accept or deny the first registration request.

[0219] The apparatus may send, to a first unified data management function, UDM, a request to register the AMF with the UDM for the user equipment and the user, the request to register comprising the first identifier identifying the user equipment and a second identifier identifying the user. The apparatus may receive a response to the request to register that indicates whether the registration of the AMF for the user equipment and the user has been performed successfully. 902 may be performed based on the response to the request indicating that the registration of the AMF for the user equipment and the user has been performed successfully.

[0220] The indication that indicates that the first registration request is for registering a user equipment and a user with the AMF may comprise the second identifier identifying the user.

[0221] The AMF may be caused to receive the second identifier from the user equipment in a secured non-access stratum message sent after the first registration request.

[0222] The second identifier that identifies the user may correspond to a network access identifier, NAI. The second identifier and / or the secured non-access stratum message may further comprise information identifying the UDM as being a UDM that stores subscription information for the user.

[0223] The UDM may deny the first registration request when the indication from the UDM indicates that the subscription information for (e.g., corresponding to) both the combined subscription information for both the user equipment and the user cannot be formed. The indication from the first UDM may identify at least one reason for the combined subscription information for both the user equipment and the user being unable to be formed. In this case, the AMF may be caused to transmit information indicative of the at least one reason to the user equipment.

[0224] The indication from the first UDM may indicate that the combined subscription information for both the user equipment and the user can be formed.

[0225] The AMF may be caused to receive from the first UDM, the combined subscription information for both the user equipment and the user, and the apparatus further comprises means for obtaining, from a policy control function, at least one policy for the user equipment based on the received first identifier and on the second identifier that identifies the user, wherein the at least one policy is for configuring the user equipment for communications with a core network.

[0226] The AMF may be caused to receive, from the user equipment, a second request to register the user equipment with the AMF for another user, determine, based on the at least one policy, whether to obtain second combined subscription information for both the user equipment and the another specific user, and either reject the second request or obtain the second combined subscription information based on the result of the determining whether to obtain the second subscription information. This may be described above. The AMF may further be caused to obtain the second subscription information, and determine whether to release the first registration based on the at least one policy.

[0227] The AMF may further be caused to provide the first and second identifiers to a core network function. The core network function may be the core network function of Figure 10.

[0228] The core network function may comprise at least one of a session management function, a policy control function, a charging function, or a short message service function.

[0229] The AMF may select the first UDM based on the first identifier or the second identifier. The selecting the first UDM may comprise using the first identifier and / or second identifier as an index to identify the first UDM, and / or the extracting an identifier for the first UDM from the second identifier.

[0230] The apparatus may be caused to, before sending the first registration request, causing at least one of the user or the user equipment to be authenticated in the network.

[0231] Figure 10 illustrates operations that may be performed by an apparatus for a code network function. The core network function may correspond to the core network function of Figure 8 and / or Figure 9. The core network function may comprise at least one of a session management function, a policy control function, a charging function, or a short message service function. The functionality of the apparatus of Figure 10 may be performed by the apparatus described in connection with Figure 2.

[0232] During 1001, the apparatus may receiving a first service request for a specific user of a user equipment. The first service request may correspond to a service provided by the core network function (e.g., a session management service for an SMF, etc.).

[0233] During 1002, the apparatus sends, to a first unified data management function, UDM, a request for subscription information corresponding to both the first user equipment and the specific user, the request comprising a first identifier identifying the user equipment and a second identifier identifying the specific user. The first service request may comprise the first identifier and / or the second identifier.

[0234] During 1003, the apparatus receives, from the first UDM, an indication that indicates whether the subscription information corresponding to both the user equipment and the user can be formed.

[0235] During 1004, the apparatus determines whether to fulfil the service request based on the indication.

[0236] The first service request may comprise the second identifier. The second identifier that identifies the user may correspond to a network access identifier, NAI. The second identifier may further comprise information identifying the UDM or UDR as being a UDM or UDR that stores subscription information for the user.

[0237] The first service request may be received from an access and mobility management function, AMF.

[0238] The indication from the UDM may indicate that the first subscription information corresponding to both the user equipment and user cannot be formed. In such a case, theindication from the UDM may further identify at least one reason for the first subscription information cannot be formed, and the apparatus may further be caused to transmit information indicative of the at least one reason to the access and mobility management function.

[0239] The indication from the UDM may indicate that the first subscription information can be formed.

[0240] The apparatus of Figure 10 may further receive the first subscription information subscription information from the UDM, and fulfil the service request based on the first subscription information.

[0241] The core network function may further be caused to perform selecting the first UDM based on the first identifier or the second identifier. The selecting the first UDM may comprise: using the first identifier and / or second identifier as an index to identify the first UDM, and / or the selecting the first UDM comprises means for extracting an identifier for the first UDM from the second identifier. This may be as described above.

[0242] Figure 11 illustrates operations that may be performed by a user equipment. The apparatus of Figure 11 may be as described above in relation to Figure 3.

[0243] During 1101, the apparatus transmits, to a core network of a communication network, a request comprising a first identifier that identifies a user equipment, and an indication that the request is for a specific user.

[0244] During 1102, the apparatus transmits to the core network, a second identifier that identifies the specific user of the user equipment;

[0245] During 1103, the apparatus receives, from the core network, at least one policy based on the first and second identifiers.

[0246] During 1104, the apparatus communicates with the core network based on the at least one policy.

[0247] The apparatus may be caused to answer an authentication challenge received from the core network to authenticate the end-user.

[0248] The apparatus may be caused to receive, from the core network, an indication of whether a combined user equipment and user registration has been accepted or rejected based on the request.

[0249] The apparatus may be caused to output to the user (e.g., via a display) at least one reason indicating why a combined user equipment and user registration has been rejected.

[0250] In all of the above examples of Figures 8 to 11, the second identifier may comprise a network access identifier. In all of the above examples of Figures 8 to 11, first identifier may comprise at least one of a subscription Concealed identifier or a Globally Unique Temporary Identifier.

[0251] It is understood that references in the above to various network functions (e.g., to an AMF, an SMF, etc.) may comprise apparatus that perform at least some of the functionality associated with those network functions. Further, an apparatus comprising a network function may comprise a virtual network function instance of that network function.

[0252] 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.

[0253] 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. 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.

[0254] 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.

[0255] 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.

[0256] 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.

[0257] As used herein, 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 / firm ware 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.”

[0258] This definition of circuitry applies to all uses of this term herein, including in any claims. As a further example, as used herein, 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.

[0259] he 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 computer-executable 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.

[0260] 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 softwaremay 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.

[0261] 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).

[0262] 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.

[0263] Various example 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.

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

[0265] The foregoing description has provided, by way of non-limiting and illustrative examples, a full and informative description of the various example embodiments 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 claims. However, all such and similar modifications of the teachings will still fall within the various example embodiments of the disclosure as set forth in the claims. By way of non-limiting and illustrative example, thereis a further example embodiment comprising a combination of one or more example embodiments with any of the other example embodiments previously discussed.

Claims

Claims1. An apparatus, the apparatus comprising means for causing a unified data management, UDM, to perform operations, the operations comprising: receiving, from a core network function, a request for first combined subscription information for both a user equipment and a user, wherein the request comprises a first identifier and a second identifier, wherein the second identifier identifies a user of a user equipment, and the first identifier identifies the user equipment; retrieving subscription information for the user based on the first identifier; retrieving subscription information for the user equipment based on the second identifier; determining whether the subscription information for the user and the subscription information for the user equipment can be combined to form the first combined subscription information; and transmitting, to the core network function, an indication that indicates whether the first combined subscription information can be formed.

2. The apparatus as claimed in claim 1, wherein the indication indicates that the first subscription information cannot be formed.

3. The apparatus as claimed in claim 2, wherein the indication identifies at least one reason why the first subscription information cannot be formed.

4. The apparatus as claimed in claim 1, wherein the operations further comprise: combining the subscription information for the user and the subscription information for the user equipment to form the first subscription information; and transmitting, to the core network function, the first subscription information.

5. The apparatus as claimed in claim 4, wherein the indication indicates that the first subscription information can be formed.

6. The apparatus as claimed in any of claims 1 to 5, wherein the retrieving the subscription information for the user based on the second identifier comprises: identifying another UDM or a unified data register, UDR, that is maintaining subscription information for the user corresponding to the second identifier using at least one of a lookup table or information identifying the another UDM or UDR that is comprised in the second identifier; and retrieving the subscription information for the user based on the second identifier from the another UDM or UDR.

7. The apparatus as claimed in claim 6, wherein the operations further comprise: transmitting, to the another UDM, a request to register the core network function as serving the user, wherein the request to register the core network function as serving the user equipment comprises the first identifier and the second identifier.

8. The apparatus as claimed in any of claims 1 to 5, wherein the retrieving the subscription information for the user equipment based on the first identifier comprises: identifying another UDM and / or a unified data register, UDR, that is maintaining the subscription information for the user equipment corresponding to the first identifier using a lookup table; and retrieving the subscription information for the user equipment corresponding to the first identifier from the another UDM and / or UDR.

9. The apparatus as claimed in claim 8, wherein the operations further comprise: transmitting, to the another UDM and / or UDR, a request to register the core network function as serving the user equipment, wherein the request to register the core network function as serving the user equipment comprises the first identifier and the second identifier.

10. The apparatus as claimed in any of claims 1 to 9, wherein the determining whether the first subscription information can be combined to form the first subscription information comprises: identifying, for a same parameter in each of the subscription information for the user and the subscription information for the user equipment, respective values for said parameter; anddetermining whether the respective values are compatible with each other, wherein when it is determined that the respective values are compatible with each other, determining that the subscription information for the user and the subscription information for the user equipment can be combined to form the first subscription information, and when it is determined that the respective values are incompatible with each other, determining that the subscription information for the user and the subscription information for the user equipment cannot be combined to form the first subscription information.

11. The apparatus as claimed in any of claims 1 to 10, wherein the core network function comprises at least one of: an access and mobility management function, a session management function, a policy control function, a charging function, or a short message service function.

12. The apparatus, the apparatus comprising means for causing an access and mobility management function, AMF to perform operations, the operations comprising: receiving a first registration request, the first registration request comprising an indication that indicates that the first registration request is for registering a user equipment and a user with the AMF, and a first identifier identifying the user equipment; sending, to a first unified data management function, UDM, a request for combined subscription information for both the user equipment and the user, the request comprising the first identifier identifying the user equipment and the second identifier identifying the user; receiving, from the first UDM, an indication that indicates whether the combined subscription information for both the user equipment and the user can be formed; and determining, based on the indication, whether to accept or deny the first registration request.

13. The apparatus as claimed in claim 12, wherein the operations further comprise: sending, to the first UDM a request to register the AMF with the UDM for the user equipment and the user, the request to register comprising the first identifier identifying the user equipment and a second identifier identifying the user; and receiving a response to the request to register that indicates whether the registration of the AMF for the user equipment and the user has been performed successfully,wherein the sending the request for the combined subscription information is performed when the response to the transmitted request to register indicates that the registration of the AMF for the user equipment and the user has been performed successfully.

14. The apparatus as claimed in any of claims 12 to 13, wherein the indication that indicates that the first registration request is for registering a user equipment and a user with the AMF comprises the second identifier identifying the user.

15. The apparatus as claimed in any of claims 12 to 14, further wherein the operations further comprise receiving the second identifier from the user equipment in a secured non-access stratum message sent after the first registration request.

16. The apparatus as claimed in any of claims 12 to 15, wherein the second identifier that identifies the user corresponds to a network access identifier, NAI.

17. The apparatus as claimed in claim 16, wherein the secured non-access stratum message and / or second identifier further comprises information identifying the UDM as being a UDM that stores subscription information for the user.

18. The apparatus as claimed in any of claims 1 to 17, wherein the indication from the UDM indicates that the subscription information for both the combined subscription information for both the user equipment and the user cannot be formed, and, based on the indication from the UDM, the determining comprises determining to deny the first registration request.

19. The apparatus as claimed in claim 18, wherein the indication from the first UDM identifies at least one reason for the combined subscription information for both the user equipment and the user being unable to be formed, and wherein the operations further comprise transmitting information indicative of the at least one reason to the user equipment.

20. The apparatus as claimed any of claims 12 to 17, wherein the indication from the first UDM indicates that the combined subscription information for both the user equipment and the user can be formed, and, based on the indication from the UDM, the determining comprises determining to deny the first registration request.

21. The apparatus as claimed in claim 20, wherein the operations further comprise receiving, from the first UDM, the combined subscription information for both the user equipment and the user, and the apparatus further comprises means for obtaining, from a policy control function, at least one policy for the user equipment based on the received first identifier and on the second identifier that identifies the user, wherein the at least one policy is for configuring the user equipment for communications with a core network.

22. The apparatus as claimed in claim 21, wherein the operations further comprise: receiving, from the user equipment, a second request to register the user equipment with the AMF for another user; determining, based on the at least one policy, whether to obtain second combined subscription information for both the user equipment and the another specific user; and either rejecting the second request or obtaining the second combined subscription information based on the result of the determining whether to obtain the second subscription information.

23. The apparatus as claimed in claim 21, wherein the operations further comprise: obtaining the second subscription information; and determining whether to release the first registration based on the at least one policy.

24. The apparatus as claimed in any of claims 20 to 23, wherein the operations further comprise providing the first and second identifiers to a core network function.

25. The apparatus as claimed in claim 24, wherein the core network function comprises at least one of a session management function, a policy control function, a charging function, or a short message service function.

26. The apparatus as claimed in any of claims 12 to 25, wherein the operations further comprise selecting the first UDM based on the first identifier or the second identifier.

27. The apparatus as claimed in claim 26, wherein the selecting the first UDM comprises: using the first identifier and / or second identifier as an index to identify the first UDM, and / or the selecting comprises means for extracting an identifier for the first UDM from the second identifier.

28. The apparatus as claimed in any of claims 12 to 27, wherein operations further comprise: before sending the first registration request, causing at least one of the user or the user equipment to be authenticated in the network.

29. An apparatus comprising means for causing a core network function to perform operations, the operations comprising: receiving a first service request for a specific user of a user equipment; sending, to a first unified data management function, UDM, a request for subscription information corresponding to both the first user equipment and the specific user, the request comprising a first identifier identifying the user equipment and a second identifier identifying the specific user; receiving, from the first UDM, an indication that indicates whether the subscription information corresponding to both the user equipment and the user can be formed; and determining whether to fulfil the service request based on the indication.

30. The apparatus as claimed in claim 29, wherein the first service request comprises the second identifier.

31. The apparatus as claimed in claim 29 to 30, wherein the first service request is received from an access and mobility management function, AMF.

32. The apparatus as claimed in any of claims 29 to 31, wherein the second identifier that identifies the user corresponds to a network access identifier, NAI.

33. The apparatus as claimed in claim 32, wherein the second identifier comprises information identifying the UDM or UDR as being a UDM or UDR that stores subscription data for the user.

34. The apparatus as claimed in any of claims 29 to 33, wherein the indication from the UDM indicates that the first subscription information corresponding to both the user equipment and user cannot be formed.

35. The apparatus as claimed in claim 34, wherein the indication from the UDM identifies at least one reason for the first subscription information cannot be formed, and the apparatus further comprises means for transmitting information indicative of the at least one reason to the access and mobility management function.

36. The apparatus as claimed in any of claims 29 to 33, wherein the indication from the UDM indicates that the first subscription information can be formed.

37. The apparatus as claimed in claim 36, wherein the operations further comprise: receiving the first subscription information subscription information from the UDM; and fulfilling the service request based on the first subscription information.

38. The apparatus as claimed in any of claims 29 to 37, wherein the core network function comprises at least one of a session management function, a policy control function, a charging function, or a short message service function.

39. An apparatus as claimed in any of claims 29 to 38, wherein the operations further comprise selecting the first UDM based on the first identifier or the second identifier.

40. The apparatus as claimed in claim 39, wherein the selecting the first UDM comprises: using the first identifier and / or second identifier as an index to identify the first UDM, and / or the selecting the first UDM comprises extracting an identifier for the first UDM from the second identifier.

41. A user equipment comprising means for performing operations, the operations comprising: transmitting, to a core network of a communication network, a request comprising a first identifier that identifies a user equipment, and an indication that the request is for a specific user; andtransmitting to the core network, a second identifier that identifies the specific user of the user equipment; receiving, from the core network, at least one policy based on the first and second identifiers; and communicating with the core network based on the at least one policy.

42. The user equipment as claimed in claim 41 wherein the operations further comprise at least one of the following: answering an authentication challenge received from the core network to authenticate the end-user; receiving, from the core network, an indication of whether a combined user equipment and user registration has been accepted or rejected based on the request; or outputting to the user at least one reason indicating why a combined user equipment and user registration has been rejected.

43. The apparatus as claimed in any preceding claim, wherein the second identifier comprises a network access identifier, and / or wherein the first identifier comprises at least one of a subscription Concealed identifier or a Globally Unique Temporary Identifier.

44. A method performed by a unified data management entity, the method comprising: receiving, from a core network function, a request for first combined subscription information for both a user equipment and a user, wherein the request comprises a first identifier and a second identifier, wherein the second identifier identifies a user of a user equipment, and the first identifier identifies the user equipment; retrieving subscription information for the user based on the first identifier; retrieving subscription information for the user equipment based on the second identifier; determining whether the subscription information for the user and the subscription information for the user equipment can be combined to form the first combined subscription information; andtransmitting, to the core network function, an indication that indicates whether the first combined subscription information can be formed.

45. A method performed by an access and mobility management function, the method comprising: receiving a first registration request, the first registration request comprising an indication that indicates that the first registration request is for registering a user equipment and a user with the AMF, and a first identifier identifying the user equipment; sending, to a first unified data management function, UDM, a request for combined subscription information for both the user equipment and the user, the request comprising the first identifier identifying the user equipment and the second identifier identifying the user; receiving, from the first UDM, an indication that indicates whether the combined subscription information for both the user equipment and the user can be formed; and determining, based on the indication, whether to accept or deny the first registration request.

46. A method performed by a core network function, the method comprising: receiving a first service request for a specific user of a user equipment; sending, to a first unified data management function, UDM, a request for subscription information corresponding to both the first user equipment and the specific user, the request comprising a first identifier identifying the user equipment and a second identifier identifying the specific user; receiving, from the first UDM, an indication that indicates whether the subscription information corresponding to both the user equipment and the user can be formed; and determining whether to fulfil the service request based on the indication.

47. A method performed by a user equipment, the method comprising: transmitting, to a core network of a communication network, a request comprising a first identifier that identifies a user equipment, and an indication that the request is for a specific user; and transmitting to the core network, a second identifier that identifies the specific user of the user equipment; receiving, from the core network, at least one policy based on the first and second identifiers; and communicating with the core network based on the at least one policy.

48. A computer program, the computer program comprising instructions of a unified data management entity, wherein when the computer program is executed by a computer, the computer is caused to carry out: receiving, from a core network function, a request for first combined subscription information for both a user equipment and a user, wherein the request comprises a first identifier and a second identifier, wherein the second identifier identifies a user of a user equipment, and the first identifier identifies the user equipment; retrieving subscription information for the user based on the first identifier; retrieving subscription information for the user equipment based on the second identifier; determining whether the subscription information for the user and the subscription information for the user equipment can be combined to form the first combined subscription information; and transmitting, to the core network function, an indication that indicates whether the first combined subscription information can be formed.

49. A computer program comprising instructions an access and mobility management function, AMF, wherein when the computer program is executed by a computer, the computer is caused to carry out: receiving a first registration request, the first registration request comprising an indication that indicates that the first registration request is for registering a userequipment and a user with the AMF, and a first identifier identifying the user equipment; sending, to a first unified data management function, UDM, a request for combined subscription information for both the user equipment and the user, the request comprising the first identifier identifying the user equipment and the second identifier identifying the user; receiving, from the first UDM, an indication that indicates whether the combined subscription information for both the user equipment and the user can be formed; and determining, based on the indication, whether to accept or deny the first registration request.

50. A computer program comprising instructions of a core network function, wherein when the computer program is executed by a computer, the computer is caused to carry out: receiving a first service request for a specific user of a user equipment; sending, to a first unified data management function, UDM, a request for subscription information corresponding to both the first user equipment and the specific user, the request comprising a first identifier identifying the user equipment and a second identifier identifying the specific user; receiving, from the first UDM, an indication that indicates whether the subscription information corresponding to both the user equipment and the user can be formed; and determining whether to fulfil the service request based on the indication.

51. A computer program comprising instructions, wherein when the program is executed by a user equipment, the user equipment is caused to carry out: transmitting, to a core network of a communication network, a request comprising a first identifier that identifies a user equipment, and an indication that the request is for a specific user; and transmitting to the core network, a second identifier that identifies the specific user of the user equipment;receiving, from the core network, at least one policy based on the first and second identifiers; and communicating with the core network based on the at least one policy.

Images