Inter-PLMN subscription management in independent non-public networks

Abstract

The present disclosure provides a method for managing inter-PLMN subscriptions to network repository functions of independent non-public networks in a communication network. The method includes receiving, at a first network node, a subscription request from a network function consumer; sending a subscription request from the first network node to the second network node; creating a subscription identifier at the second network node, the subscription identifier comprising a mobile country code (MCC), a mobile network code (MNC), and a network identifier (NID) of an independent non-public network (SNPN); sending the subscription identifier from the second network node to the first network node; and providing the subscription identifier from the first network node to the network function consumer.

Description

TECHNICAL FIELD

[0001] The present invention relates generally to communication networks, and more specifically, to systems and methods for managing inter-public land mobile network (PLMN) subscriptions in standalone non-public networks (SNPNs). BACKGROUND

[0002] Non-public networks (NPNs) are networks designed for non-public use, which can be deployed in various configurations, utilizing both virtual and physical network elements. The concept of a private network is contained within NPNs, referring to isolated network deployments that do not interact with public networks. Among many possible NPN configurations, 3GPP identifies two main categories: standalone non-public networks (SNPNs) and public network integrated NPNs (PNI-NPNs).

[0003] SNPNs represent a type of NPN that does not rely on network functions provided by a public land mobile network (PLMN) (or more simply, a mobile network operator). When an SNPN is deployed as isolated, it corresponds to the concept of a private network. This means that SNPNs require a higher level of investment and commitment from the network operator.

[0004] In this context, a network function (NF) service consumer discovers a NF service producer based on an SNPN-ID, which includes a PLMN-ID and a network identifier (NID) (PLMN-ID + NID). However, due to the variety of configurations and evolving network technologies, subscription management and interactions between SNPNs and PLMNs remain challenging.

[0005] Current methods for managing subscriptions in standalone non-public network (SNPN) scenarios present several issues. When a network function (NF) service consumer in a visited network subscribes to a home PLMN network repository function (NRF), it contacts a local NRF in the visited PLMN. Then, the local network repository function (NRF) needs to contact the home PLMN NRF, which can route the request to the final NRF hosting the NF service producer.

[0006] In these scenarios, a NF consumer in a visited PLMN can create a subscription on the home NRF (i.e., the NRF in the SNPN) to receive notifications about profile changes for a set of NF instances. This subscription is created via the local NRF in the visited PLMN. The home NRF generates a subscription ID containing routing information (e.g., the identity of the SNPN) and sends this subscription ID to the NF consumer in the visited PLMN through the local NRF.

[0007] The NF consumer can also interact with the newly created subscription (e.g., modify or terminate the subscription) by sending HTTP requests to the resource:... / subscriptions / {subscriptionID} based on the subscription ID. Including the routing information in the subscription ID allows the local NRF in the visited PLMN to not maintain the state of each created subscription in the different home PLMNs, which would otherwise be unmanageable.

[0008] The current definition of the subscription ID, which is as follows: <mcc> + <mnc> +"-"+ <originalsubscriptionid>The problematic aspect of the regular expression pattern: ^([0-9]{5,6}-)?[^-]+$) is that it fails to route the request correctly to the proper NRF in the SNPN-ID. Therefore, using the current subscription ID definition, it is not feasible to manage inter-PLMN subscriptions to the NRF of a SNPN. A more efficient approach is needed to manage subscriptions in SNPN scenarios, ensuring proper routing and communication between the NRF, NF service consumers, and NF service producers. SUMMARY

[0009] The invention is set out in the appended set of claims.

[0010] The object of the invention is to provide an efficient and reliable method for managing inter-PLMN subscriptions to the Network Repository Function (NRF) of a Standalone Non-Public Network (SNPN) in a communication network. The proposed solution aims to overcome the limitations of the current subscription ID definition by including a Network Identifier (NID) of the SNPN and thus allowing the correct routing of requests to the proper NRF in the SNPN-ID.

[0011] One aspect of the invention relates to a method, performed by a first network node, for managing inter-PLMN subscriptions to the Network Repository Function of a Standalone Non-Public Network in a communication network. The method comprises receiving, at the first network node, a subscription request from a network function consumer; sending, from the first network node to a second network node, the subscription request; receiving, at the first network node, a subscription identifier from the second network node, the subscription identifier comprising a Mobile Country Code (MCC), a Mobile Network Code (MNC), and a Network Identifier (NID) of the Standalone Non-Public Network (SNPN); and providing, from the first network node to the network function consumer, the subscription identifier. In some embodiments, the subscription identifier is generated in the following format:

[0012] <mcc> + <mnc>+""-""+"":nid= <nid> :""+ <originalsubscriptionid>In some embodiments, the subscription identifier further includes a magic cookie to maintain compatibility with earlier API versions. In some embodiments, the subscription identifier includes the NID of the SNPN after the magic cookie. In some embodiments, the magic cookie is "x3Lf57A". In some embodiments, the subscription identifier is generated in a format as follows:

[0013] <mcc> + <mnc>+""-""+<magic_cookie>+"":nid= <nid> :""+ <originalsubscriptionid>In some embodiments, the NF service consumer in the visited PLMN uses the subscription identifier to modify or terminate the subscription. In some embodiments, the local NRF in the visited PLMN does not maintain a status of each created subscription in a different home PLMN. In some embodiments, the local NRF routes the subscription request to the SNPN NRF based on the MCC, the MNC, and the NID. In some embodiments, the first network node is a local network repository function in a visited public land mobile network, the second network node is a home network repository function in a home public land mobile network, and the network function consumer is a network function service consumer in the visited public land mobile network.

[0014] Another aspect of the disclosure relates to a method for managing inter-PLMN subscriptions to a network repository function of a standalone non-public network in a communication network performed by a second network node. The method includes receiving, at a second network node from a first network node, a subscription request; creating, at the second network node, a subscription identifier, the subscription identifier comprising a mobile country code (MCC), a mobile network code (MNC), and a network identifier (NID) of the standalone non-public network (SNPN); and sending, from the second network node to the first network node, the subscription identifier. In some embodiments, the subscription identifier is generated in a format of:

[0015] <mcc> + <mnc>+""-""+"":nid= <nid> :""+ <originalsubscriptionid>In some embodiments, the subscription identifier further includes a magic cookie to maintain compatibility with earlier API versions. In some embodiments, the subscription identifier includes the NID of the SNPN after the magic cookie. In some embodiments, the magic cookie is "x3Lf57A". In some embodiments, the subscription identifier is generated in a format as follows:

[0016] <mcc> + <mnc>+""-""+<magic_cookie>+"":nid= <nid> :""+ <originalsubscriptionid>In some embodiments, the NF service consumer in the visited PLMN uses the subscription identifier to modify or terminate the subscription. In some embodiments, the local NRF in the visited PLMN does not maintain a status of each created subscription in a different home PLMN. In some embodiments, the local NRF routes the subscription request to the SNPN NRF based on the MCC, the MNC, and the NID. In some embodiments, the first network node is a local network repository function in a visited public land mobile network, the second network node is a home network repository function in a home public land mobile network, and the network function consumer is a network function service consumer in the visited public land mobile network.

[0017] Another aspect of the present invention relates to a method performed by a network function consumer for managing a subscription to a second network node of a standalone non-public network, SNPN, in a communication network, the method performed by a network function consumer, the method comprising: sending a subscription request to a first network node; receiving a subscription identifier from the first network node; wherein the subscription identifier comprises a mobile country code, MCC, a mobile network code, MNC, and a network identifier, NID, of the SNPN.

[0018] Further aspects of the present invention relate to mobile network nodes, in particular a first network node (110, 500), a network function consumer (700), and a second network node (110, 600) configured to perform the respective methods described herein. Further aspects of the present invention relate to computer programs and computer program products.

[0019] In some embodiments, the first network node is a local NRF (local NRF) in a visited public land mobile network. In some embodiments, the network function consumer is a network function service consumer (NFc) in the visited PLMN. In some embodiments, the second network node is a home NRF (home NRF) in a home public land mobile network.

[0020] Advantageously, the proposed solution enables improved routing and communication by incorporating a network identifier (NID) of a standalone non-public network (SNPN) into a subscription ID. The proposed solution facilitates correct routing and communication between a network repository function (NRF), a network function (NF) service consumer, and a NF service producer. This leads to more efficient and reliable management of inter-PLMN subscriptions in SNPN scenarios.

[0021] Further advantageously, the proposed solution does not require the home PLMN to maintain the status of each created subscription in the visited public land mobile network (PLMN) by the local NRF. This reduces the complexity and overhead associated with managing inter-PLMN subscriptions, resulting in a more scalable and manageable system.

[0022] Further advantageously, the proposed solution provides backward compatibility with earlier API versions by including the magic cookie in the subscription ID. This enables seamless interaction between different versions of the API, thereby improving the overall interoperability of the system.

[0023] Further advantageously, the proposed solution allows NF service consumers in the visited PLMN to interact with the subscription identifier to modify or terminate the subscription. This provides greater control and flexibility for NF service consumers to manage their subscriptions, ultimately enhancing the user experience.

[0024] Further advantageously, the proposed solution is applicable to a wide range of non-public network configurations, including both standalone non-public networks (SNPNs) and public network integrated non-public networks (PNI-NPNs). This broad applicability ensures that the invention can be effectively utilized in a variety of networking environments.

[0025] Further advantageously, the proposed solution enables better isolation of non-public networks from public networks by incorporating the SNPN-ID in the subscription ID, thereby reducing potential security risks and ensuring a higher level of privacy for users operating within non-public network environments.

[0026] Additional objects, features, and advantages of the concepts disclosed herein will be apparent to those skilled in the art upon review of the following description, claims, and drawings, or can be learned by practice of the technology and concepts presented herein. BRIEF DESCRIPTION OF DRAWINGS

[0027] In order to best describe the manner in which the disclosed concepts can be implemented, and to define other objects, advantages, and features of the present disclosure, a more particular description will be rendered by reference to the following drawings, which are illustrative of the example embodiments, and are not intended to limit the scope of the application. Example embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings in which:

[0028] Figure 1 An example networking system is shown in accordance with particular embodiments of the solutions described herein;

[0029] Figure 2A , 2B And 2C show example signaling diagrams illustrating processes in accordance with particular embodiments of the solutions described herein;

[0030] Figure 3A An example flow diagram illustrating a method performed by a mobile network node according to particular embodiments of the solutions described herein is shown;

[0031] Figure 3B An example flow diagram illustrating a method performed by a mobile network node according to particular embodiments of the solutions described herein is shown;

[0032] Figure 4 An example flow diagram illustrating a method performed by a mobile network node according to particular embodiments of the solutions described herein is shown;

[0033] Figure 5 An example block diagram of a mobile network node configured according to particular embodiments of the solutions described herein is shown;

[0034] Figure 6 An example block diagram of a mobile network node configured according to particular embodiments of the solutions described herein is shown;

[0035] Figure 7 An example block diagram of a mobile network node configured according to particular embodiments of the solutions described herein is shown;

[0036] Figure 8 An example block diagram of a virtualization environment is shown. DETAILED DESCRIPTION

[0037] The present application will now be described in detail with reference to the drawings, which show examples of embodiments or implementations of the application. However, the application can be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and fully convey the scope of the application to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment can be assumed to be present / used in another embodiment by default. These embodiments of the disclosed subject matter are provided as examples to teach someone skilled in the art and should not be construed to limit the scope of the disclosed subject matter. For example, specific details of the described embodiments can be modified, omitted or extended in ways known to those skilled in the art without departing from the scope of the described subject matter.

[0038] The example embodiments described herein arise in the context of telecommunications networks, including but not limited to telecommunications networks compliant with and / or otherwise incorporating aspects of the Fifth Generation (5G) architecture. Figure 1 is an example networking system 100 according to example embodiments of the present disclosure. Figure 1 A user equipment (UE) 101 is shown in particular, which can communicate with a (radio) access network (RAN) 102, an access and mobility management function (AMF) 106, and a user plane function (UPF) 103. The AMF 106, in turn, can communicate with core network services, including a session management function (SMF) 107 and a policy control function (PCF) 111. The core network services can also communicate with an application server / application function (AS / AF) 113. Other networking services include a network slice selection function (NSSF) 108, an authentication server function (AUSF) 105, a user data management (UDM) 112, a network exposure function (NEF) 109, a network repository function (NRF) 110, and a data network (DN) 104. In some example implementations of embodiments of the present disclosure, each entity in the networking system 100 is considered a network function (NF). One or more additional instances of NFs can be incorporated into the networking system.

[0039] The solution described herein aims to provide an efficient and reliable method for managing inter-PLMN subscription to a Network Repository Function (NRF) of a Standalone Non-Public Network (SNPN) in a communication network. The proposed solution aims to overcome the limitations of the current subscription ID definition by including a Network Identifier (NID) of the SNPN and thus allowing to correctly route the request to the appropriate NRF in the SNPN-ID.

[0040] The present disclosure provides a method for managing inter-PLMN subscription to a Network Repository Function of a Standalone Non-Public Network in a communication network. The method comprises: receiving, at a first network node, a subscription request from a network function consumer; sending, from the first network node, the subscription request to a second network node; creating, at the second network node, a subscription identifier comprising a Mobile Country Code (MCC), a Mobile Network Code (MNC), and a Network Identifier (NID) of a Standalone Non-Public Network (SNPN); sending, from the second network node, the subscription identifier to the first network node; and providing, from the first network node, the subscription identifier to the network function consumer. In some embodiments, the subscription identifier is generated in a format comprising:

[0041] <mcc> + <mnc>+""-""+"":nid= <nid> :""+ <originalsubscriptionid>In some embodiments, the subscription identifier further includes a magic cookie to maintain compatibility with earlier API versions. In some embodiments, the subscription identifier includes the SNPN’s NID after the magic cookie. In some embodiments, the magic cookie is “x3Lf57A”. In some embodiments, the subscription identifier is generated in the following format:

[0042] <mcc> + <mnc>+""-""+<magic_cookie>+"":nid= <nid> :""+ <originalsubscriptionid>In some embodiments, the NF service consumer in the visited PLMN uses the subscription identifier to modify or terminate the subscription. In some embodiments, the local NRF in the visited PLMN does not maintain the status of each created subscription in different home PLMNs. In some embodiments, the local NRF routes the subscription request to the SNP NNF based on the MCC, MNC, and NID. In some embodiments, the first network node is a local network repository function in a visited public land mobile network, the second network node is a home network repository function in a home public land mobile network, and the network function consumer is a network function service consumer in the visited public land mobile network.

[0043] One aspect of the disclosure relates to a method performed by a first network node for managing inter-PLMN subscriptions to a network repository function of a standalone non-public network in a communication network. The method comprises receiving, at the first network node, a subscription request from a network function consumer; sending, from the first network node, the subscription request to a second network node; receiving, at the first network node, a subscription identifier from the second network node, the subscription identifier comprising a mobile country code (MCC), a mobile network code (MNC), and a network identifier (NID) of a standalone non-public network (SNPN); and providing, from the first network node, the subscription identifier to the network function consumer. In some embodiments, the subscription identifier is generated in a format of:

[0044] <mcc> + <mnc>+""-""+"":nid= <nid> :""+ <originalsubscriptionid>In some embodiments, the subscription identifier further includes a magic cookie to maintain compatibility with earlier API versions. In some embodiments, the subscription identifier includes the SNPN’s NID after the magic cookie. In some embodiments, the magic cookie is “x3Lf57A”. In some embodiments, the subscription identifier is generated in the following format:

[0045] <mcc> + <mnc>+""-""+<magic_cookie>+"":nid= <nid> :""+ <originalsubscriptionid>In some embodiments, the NF service consumer in the visited PLMN uses the subscription identifier to modify or terminate the subscription. In some embodiments, the local NRF in the visited PLMN does not maintain the status of each created subscription in different home PLMNs. In some embodiments, the local NRF routes the subscription request to the SNP NNF based on the MCC, MNC, and NID. In some embodiments, the first network node is a local network repository function in a visited public land mobile network, the second network node is a home network repository function in a home public land mobile network, and the network function consumer is a network function service consumer in the visited public land mobile network.

[0046] Another aspect of the disclosure relates to a method performed by a second network node for managing inter-PLMN subscriptions to a network repository function of a standalone non-public network in a communication network. The method includes receiving, at the second network node from a first network node, a subscription request; creating, at the second network node, a subscription identifier, the subscription identifier including a mobile country code (MCC), a mobile network code (MNC), and a network identifier (NID) of a standalone non-public network (SNPN); and sending, from the second network node to the first network node, the subscription identifier. In some embodiments, the subscription identifier is generated in a format of:

[0047] <mcc> + <mnc>+""-""+"":nid= <nid> :""+ <originalsubscriptionid>In some embodiments, the subscription identifier further includes a magic cookie to maintain compatibility with earlier API versions. In some embodiments, the subscription identifier includes the SNPN’s NID after the magic cookie. In some embodiments, the magic cookie is “x3Lf57A”. In some embodiments, the subscription identifier is generated in the following format:

[0048] <mcc> + <mnc>+""-""+<magic_cookie>+"":nid= <nid> :""+ <originalsubscriptionid>In some embodiments, the NF service consumer in the visited PLMN uses the subscription identifier to modify or terminate the subscription. In some embodiments, the local NRF in the visited PLMN does not maintain the status of each created subscription in different home PLMNs. In some embodiments, the local NRF routes the subscription request to the SNP NNF based on the MCC, MNC, and NID. In some embodiments, the first network node is a local network repository function in a visited public land mobile network, the second network node is a home network repository function in a home public land mobile network, and the network function consumer is a network function service consumer in the visited public land mobile network.

[0049] Another aspect of the present disclosure relates to a method performed by a network function consumer for managing a subscription to a second network node of a standalone non-public network (SNPN) in a communication network, the method performed by the network function consumer, the method comprising: sending, to a first network node, a subscription request; receiving, from the first network node, a subscription identifier; wherein the subscription identifier comprises a mobile country code (MCC), a mobile network code (MNC), and a network identifier (NID) of the SNPN. In some embodiments, the subscription identifier is generated in a format of:

[0050] <mcc> + <mnc>+""-""+"":nid= <nid> :""+ <originalsubscriptionid>.

[0051] In some embodiments, the subscription identifier further includes a magic cookie to maintain compatibility with earlier Application Programming Interface, API, versions. In some embodiments, the subscription identifier includes the SNPN’s NID after the magic cookie. In some embodiments, the magic cookie is “x3Lf57A”. In some embodiments, the subscription identifier is generated in the following format:

[0052] <mcc> + <mnc>+""-""+<magic_cookie>+"":nid= <nid> :""+ <originalsubscriptionid>.

[0053] In some embodiments, the network function consumer uses the subscription identifier to modify or terminate the subscription. In some embodiments, the first network node does not maintain the status of the created subscription in each of the different home public land mobile networks, PLMNs. In some embodiments, the first network node is a local network repository function in a visited public land mobile network, the second network node is a home network repository function in a home public land mobile network, and the network function consumer is a network function service consumer in the visited public land mobile network.

[0054] The disclosure also provides mobile network nodes, in particular a first network node (110, 500), a network function consumer (700), and a second network node (110, 600) configured to perform the respective methods described herein. In some embodiments, the first network node is a local NRF (local NRF) 110 in a visited public land mobile network. In some embodiments, the network function consumer is a network function service consumer (NFc) in a visited PLMN. In some embodiments, the second network node is a home NRF (home NRF) 110 in a home public land mobile network.

[0055] The disclosure also provides corresponding computer programs and computer program products, including code in the form of computer programs that, when run on processing circuitry of a mobile network node, causes the mobile network node to perform the disclosed methods.

[0056] The solution and features included therein are further described below.

[0057] The proposed solution provides an improved method for managing inter-PLMN subscriptions to a network repository function (NRF) of a standalone non-public network (SNPN) in a communication network. The method enhances the routing and communication between the NRF, a network function (NF) service consumer, and a NF service producer, resulting in more efficient and reliable management of inter-PLMN subscriptions in SNPN scenarios.

[0058] The method involves receiving a subscription request at a local NRF in a visited public land mobile network (PLMN), sending the request to a home NRF in a home PLMN, and creating a subscription identifier at the home NRF, the subscription identifier comprising a mobile country code (MCC), a mobile network code (MNC), and a network identifier (NID) of the SNPN. The subscription identifier is then sent to the local NRF in the visited PLMN and provided to the NF service consumer.

[0059] Further, the present invention includes a magic cookie in the subscription identifier to maintain compatibility with earlier API versions. NF service consumers can also interact with the subscription identifier to modify or terminate subscriptions, providing greater control and flexibility in managing their subscriptions.

[0060] By incorporating the SNPN-ID in the subscription identifier and not requiring the local NRF to maintain the state of each created subscription in different home PLMNs, the present invention provides a scalable, manageable, and secure solution for managing inter-PLMN subscriptions in various non-public network configurations.

[0061] To add the NID value, and to maintain compatibility with earlier API versions, it is proposed to define a "magic cookie” to maintain backward compatibility with earlier data formatting versions, and to define a structure for including the NID. For example:

[0062] <mcc> + <mnc>+"-"+"x3Lf57A"+":nid= <nid> :"+ <originalsubscriptionid>

[0063] For example:

[0064] (magic cookie = "x3Lf57A")

[0065] MCC = 123, MNC = 456, NID = 023f245ac42

[0066] OriginalSubscriptionID = subs987654

[0067] {subscriptionID} = 123456-x3Lf57A:nid=023f245ac42:subs987654

[0068] The presence of a "magic cookie" prevents accidental collision with subscription IDs generated by existing implementations.

[0069] The magic cookie is optional, i.e. the generated subscription identifier can skip it and be based only on nid=(11 characters):subsId, e.g.:

[0070] {subscriptionID} = 123456-nid=023f245ac42:subs987654

[0071] However, the use of a magic cookie is preferred (e.g. "x3Lf57A") as it is a strong mechanism, e.g. to ensure that older NRF implementations will not select a magic cookie value.

[0072] In a SNPN scenario, an NF consumer in a visited PLMN can create a subscription on the home NRF (i.e. the NRF in the SNPN) to receive notifications about profile changes for a set of NF instances. This subscription is created via a local NRF in the visited PLMN. The home NRF creates a subscription ID containing routing information (e.g. identity of the SNPN) that is sent to the NF consumer in the visited PLMN via the local NRF. This allows the NF consumer to also interact with this newly created subscription based on the subscription ID by sending HTTP requests to the resource: … / subscriptions / {subscriptionID} (e.g. to modify the subscription or to terminate the subscription).

[0073] Having routing information within the subscription ID allows the local NRF (NRF in the visited PLMN) to not maintain the state of each created subscription in different home PLMNs, which would otherwise be unmanageable.

[0074] The following detailed description illustrates examples of embodiments of the present solution by way of example.

[0075] Figure 2A is a signaling diagram illustrating a procedure for subscribing to NF instances in different PLMNs. The procedure is performed by a first network node (110, 500) and a second network node (110, 600). In some embodiments, the first network node is a local network repository function in a visited public land mobile network, and the second network node is a home network repository function in a home public land mobile network. The serving PLMN is the PLMN that provides services to the user equipment. In some embodiments, the visited public land mobile network is the serving PLMN. In some embodiments, the home public land mobile network is the serving PLMN.

[0076] These steps are performed between the NRF in the serving PLMN and the NRF in the home PLMN. The PLMN ID can be present in the SubscriptionData parameter. The NRF in the home PLMN returns a subscriptionID that identifies the created subscription. The new subscriptionID can be generated by the NRF in the serving PLMN or in the home PLMN and can be sent to the NF service consumer in the serving PLMN or to the NRF in the serving PLMN.

[0077] In step 1, the NRF in the serving PLMN sends a POST request to a resource URI in the NRF in the home PLMN representing the "subscriptions” collection resource. The request body includes the SubscriptionData received by the NRF in the serving PLMN from the NF service consumer in the serving PLMN, which contains data about the type of notifications the NF service consumer is interested in receiving and a callback URI where the NF service consumer is prepared to receive notifications from the NRF.

[0078] When the step 1 is performed for an update (a PATCH request is sent to the NRF, see Figure 2B ); the request includes the identity of the PLMN or SNPN of the NRF (MCC / MNC / NID values) as a prefix or component value of the susbscriptionID.

[0079] Similarly, when the deletion step is performed (a DELETE request is sent to the NRF, see Figure 2C ); the request includes the identity of the PLMN or SNPN of the NRF (MCC / MNC / NID values) as a prefix or component value of the susbscriptionID.

[0080] In step 2a, if successful, return "201 Created". If the subscription is created in the NRF in a home PLMN different from the one in which the subscription request is received, the NRF in the home PLMN in which the subscription request is received shall include in the subscriptionID information (in the first 5 or 6 digits and after the "-") e.g. in order to be able to forward a subsequent subscription modification or deletion request it can receive from the NRF in the serving PLMN to the NRF in the home PLMN that holds the subscription. The information to be included in the subscriptionID is left to implementation.

[0081] The NRF in the serving PLMN shall not keep the status of this created subscription and send to the NF service consumer in the serving PLMN a subscriptionID that includes the following structure:

[0082] If the home NRF is located in a PLMN:

[0083] <mcc> + <mnc> +"-"+ <originalsubscriptionid>

[0084] If the home NRF is located in the SNPN:

[0085] <mcc> + <mnc>+"-"+"x3Lf57A"+":nid="+ <nid> +":"+ <originalsubscriptionid>

[0086] The fixed 7-character string "x3Lf57A" is used to prevent accidental collisions with subscription IDs generated according to earlier versions of this specification, where the subscription ID can contain only MCC and MNC values; this mechanism is commonly referred to as a "magic cookie".

[0087] Example 1: If the NRF in a home PLMN (with MCC = 123 and MNC = 456) creates a subscription with value "subs987654", then the subscriptionID that the NRF in a serving PLMN will send to NF service consumers in the serving PLMN is:

[0088] "123456-subs987654"

[0089] Example 2: If the NRF in a SNPN (with MCC = 321, MNC = 654 and NID = 023f245ac42) creates a subscription with value "subs987654", then the subscriptionID that the NRF in a serving PLMN will send to NF service consumers in the serving PLMN is:

[0090] "321654-x3Lf57A:nid=023f245ac42:subs987654".

[0091] The URI in the Location header that the NRF in a serving PLMN returns to NF service consumers in the serving PLMN contains the modified <subscriptionid>and if it is an absolute URI, the apiRoot containing the address pointing to the NRF in the service PLMN. The subscriptionld attribute in the message body returned to the NF service consumer in the service PLMN is also included as modified above <subscriptionid>.

[0092] Step 2b is executed on failure or redirection. If the creation of the subscription at the NRF fails due to an error in the SubscriptionData JSON object in the request body, the NRF returns a "400 Bad request” status code with a ProblemDetails IE providing details of the error. If the creation of the subscription at the NRF fails due to an internal error in the NRF, the NRF returns a "500 Internal Server Error” status code with a ProblemDetails IE providing details of the error. In case of redirection, the NRF returns a 3xx status code containing a Location header with a URI pointing to an endpoint of another NRF service instance.

[0093] Figure 2B is a signaling diagram illustrating a procedure for updating a subscription to NF instances in different PLMNs. The procedure is performed by a first network node (110, 500) and a second network node (110, 600). In some embodiments, the first network node is a local network repository function in a visited public land mobile network, and the second network node is a home network repository function in a home public land mobile network. The serving PLMN is the PLMN that provides service to the user equipment. In some embodiments, the visited public land mobile network is the serving PLMN. In some embodiments, the home public land mobile network is the serving PLMN.

[0094] The update of the subscription in different PLMNs is done by updating the subscription resource identified by the "subscriptionID”.

[0095] In step 1B, a PATCH request is sent from the NRF in the serving PLMN to the NRF in the home PLMN; the request includes the identity of the PLMN or SNPN of the NRF (MCC / MNC / NID values) as a component value of the susbcriptionID.

[0096] Steps 1B-2B (a-c) are performed between the NRF in the serving PLMN and the NRF in the home PLMN. The subscriptionID sent to the NRF in the home PLMN does not contain the identity of the PLMN (i.e., it is the same as the subscriptionID value originally generated by the NRF in the home PLMN). The NRF in the home PLMN returns a status code with the result of the operation.

[0097] Figure 2C is a signaling diagram illustrating a procedure for subscription deletion for NF instances in different PLMNs. The procedure is performed by a first network node (110, 500) and a second network node (110, 600). In some embodiments, the first network node is a local network repository function in a visited public land mobile network, and the second network node is a home network repository function in a home public land mobile network. The serving PLMN is the PLMN that provides service to the user equipment. In some embodiments, the visited public land mobile network is the serving PLMN. In some embodiments, the home public land mobile network is the serving PLMN.

[0098] Subscription deletion in different PLMNs is done by deleting the resource identified by "subscriptionID" in the NRF of the home PLMN.

[0099] In step 1C, a DELETE request is sent from the NRF in the serving PLMN to the NRF in the home PLMN; the request includes the identity of the PLMN or SNPN of the NRF (MCC / MNC / NID values) as component values of the susbcriptionID.

[0100] Steps 1C-2C (a-b) are performed between the NRF in the serving PLMN and the NRF in the home PLMN. The subscriptionID sent to the NRF in the home PLMN does not contain the identity of the PLMN (i.e., it is the same as the subscriptionID value originally generated by the NRF in the home PLMN). The NRF in the home PLMN returns a status code with the operation result.

[0101] Accordingly, the present disclosure proposes a method for managing a subscription to a second network node of a standalone non-public network, SNPN, in a communication network, the method comprising: receiving (S-301), at a first network node (500), a first subscription request from a network function consumer; sending (S-302), from the first network node to the second network node, a second subscription request; sending (S-402), from the second network node to the first network node, a first subscription identifier; and sending (S-304), from the first network node to the network function consumer, a second subscription identifier; wherein the first subscription identifier or the second subscription identifier comprises a mobile country code, MCC, a mobile network code, MNC, and a network identifier, NID, of the SNPN.

[0102] The following detailed description shows flow diagrams of examples of embodiments of the solution.

[0103] Embodiments correspond to methods performed by and involving a network function consumer (700), a first network node (110, 500) and a second network node (110, 600). In some embodiments, the first network node is a local network repository function in a visited public land mobile network, the second network node is a home network repository function in a home public land mobile network. In some embodiments, the network function consumer is a network function service consumer in the visited public land mobile network.

[0104] Figure 3A is a flowchart illustrating a method performed by a first network node for managing inter-PLMN subscription to a network repository function of a standalone non-public network in a communication network.

[0105] In step S-301, the first network node receives a subscription request from a network function consumer.

[0106] In step S-302, the first network node sends a subscription request to a second network node.

[0107] In step S-303, the first network node receives a subscription identifier from the second network node, the subscription identifier comprising a mobile country code (MCC), a mobile network code (MNC) and a network identifier (NID) of a standalone non-public network SNPN.

[0108] In step S-304, the first network node provides the subscription identifier to the network function consumer.

[0109] In some embodiments, the subscription identifier is generated in a format as follows:

[0110] <mcc> + <mnc>+""-""+"":nid= <nid> :""+ <originalsubscriptionid>.

[0111] In some embodiments, the subscription identifier further includes a magic cookie to maintain compatibility with earlier API versions.

[0112] In some embodiments, the subscription identifier includes the NID of the SNPN after the magic cookie.

[0113] In some embodiments, the magic cookie is "x3Lf57A".

[0114] In some embodiments, the subscription identifier is generated in the following format:

[0115] <mcc> + <mnc>+""-""+<magic_cookie>+"":nid= <nid> :""+ <originalsubscriptionid>.

[0116] In some embodiments, the NF service consumer in the visited PLMN uses the subscription identifier to modify or terminate the subscription.

[0117] In some embodiments, the local NRF in the visited PLMN does not maintain the status of each created subscription in different home PLMNs.

[0118] In some embodiments, the local NRF routes the subscription request to the SNPN NRF based on the MCC, MNC, and NID.

[0119] In some embodiments, the first network node is a local network repository function in a visited public land mobile network, the second network node is a home network repository function in a home public land mobile network, and the network function consumer is a network function service consumer in the visited public land mobile network.

[0120] Figure 3B is a flowchart illustrating a method performed by a network function consumer for managing inter-PLMN subscriptions to a network repository function of a standalone non-public network in a communication network.

[0121] In step S-302, the first network node sends a subscription request to the second network node.

[0122] In step S-303, the first network node receives a subscription identifier from the second network node, the subscription identifier comprising a mobile country code (MCC), a mobile network code (MNC), and a network identifier (NID) of a standalone non-public network (SNPN).

[0123] In some embodiments, the subscription identifier is generated in the following format:

[0124] <mcc> + <mnc>+""-""+"":nid= <nid> :""+ <originalsubscriptionid>.

[0125] In some embodiments, the subscription identifier further includes a magic cookie to maintain compatibility with earlier API versions.

[0126] In some embodiments, the subscription identifier includes the NID of the SNPN after the magic cookie.

[0127] In some embodiments, the magic cookie is "x3Lf57A".

[0128] In some embodiments, the subscription identifier is generated in the following format:

[0129] <mcc> + <mnc>+""-""+<magic_cookie>+"":nid= <nid> :""+ <originalsubscriptionid>.

[0130] In some embodiments, the NF service consumer in the visited PLMN uses the subscription identifier to modify or terminate the subscription.

[0131] In some embodiments, the local NRF in the visited PLMN does not maintain the status of each created subscription in different home PLMNs.

[0132] In some embodiments, the local NRF routes the subscription request to the SNPN NRF based on the MCC, MNC, and NID.

[0133] In some embodiments, the first network node is a local network repository function in a visited public land mobile network, the second network node is a home network repository function in a home public land mobile network, and the network function consumer is a network function service consumer in the visited public land mobile network.

[0134] Figure 4 is a flowchart illustrating a method performed by a second network node for managing inter-PLMN subscriptions to a network repository function of a standalone non-public network in a communication network.

[0135] In step S-401, the second network node receives a subscription request from a first network node.

[0136] In step S-402, the second network node creates a subscription identifier comprising a mobile country code (MCC), a mobile network code (MNC), and a network identifier (NID) of a standalone non-public network (SNPN).

[0137] In step S-403, the second network node sends the subscription identifier to the first network node.

[0138] In some embodiments, the subscription identifier is generated in the following format:

[0139] <mcc> + <mnc>+""-""+"":nid= <nid> :""+ <originalsubscriptionid>.

[0140] In some embodiments, the subscription identifier further includes a magic cookie to maintain compatibility with earlier API versions.

[0141] In some embodiments, the subscription identifier includes the NID of the SNPN after the magic cookie.

[0142] In some embodiments, the magic cookie is "x3Lf57A".

[0143] In some embodiments, the subscription identifier is generated in the following format:

[0144] <mcc> + <mnc>+""-""+<magic_cookie>+"":nid= <nid> :""+ <originalsubscriptionid>.

[0145] In some embodiments, the NF service consumer in the visited PLMN uses the subscription identifier to modify or terminate the subscription.

[0146] In some embodiments, the local NRF in the visited PLMN does not maintain the status of each created subscription in different home PLMNs.

[0147] In some embodiments, the local NRF routes the subscription request to the SNPN NRF based on the MCC, MNC, and NID.

[0148] In some embodiments, the first network node is a local network repository function in a visited public land mobile network, and the second network node is a home network repository function in a home public land mobile network.

[0149] Figure 5 is a block diagram illustrating elements of a mobile network node 500 of a mobile communication network. In some embodiments, the mobile network node 500 is a local NRF 110. As shown, the mobile network node can include network interface circuitry 501 (also referred to as a network interface) configured to provide communications with a core network and / or other nodes of the network. The mobile network node can also include processing circuitry 502 (also referred to as a processor) coupled to the network interface circuitry and memory circuitry 503 (also referred to as a memory) coupled to the processing circuitry. The memory circuitry 503 can include computer-readable program code that, when executed by the processing circuitry 502, causes the processing circuitry to perform operations in accordance with embodiments disclosed herein. According to other embodiments, the processing circuitry 502 can be defined to include the memory such that a separate memory circuitry is not needed. As discussed herein, the operations of the mobile network node can be performed by the processing circuitry 502 and / or the network interface circuitry 501. For example, the processing circuitry 502 can control the network interface circuitry 501 to transmit communications through the network interface circuitry 501 to one or more other network nodes and / or receive communications from one or more other network nodes through the network interface circuitry. Further, modules can be stored in the memory 503, and these modules can provide instructions to cause the processing circuitry 502 to perform respective operations (e.g., the operations discussed below with respect to example embodiments involving core network nodes) when the instructions of the modules are executed by the processing circuitry 502.

[0150] Figure 6 is a block diagram illustrating elements of a mobile network node 600 of a mobile communication network. In some embodiments, the mobile network node 600 is a home NRF 110. As shown, the mobile network node can include network interface circuitry 601 (also referred to as a network interface) configured to provide communication with the core network and / or other nodes of the network. The mobile network node can also include processing circuitry 602 (also referred to as a processor) coupled to the network interface circuitry and memory circuitry 603 (also referred to as a memory) coupled to the processing circuitry. The memory circuitry 603 can include computer-readable program code that, when executed by the processing circuitry 602, causes the processing circuitry to perform operations in accordance with embodiments disclosed herein. According to other embodiments, the processing circuitry 602 can be defined to include the memory such that a separate memory circuitry is not needed. As discussed herein, operations of the mobile network node can be performed by the processing circuitry 602 and / or the network interface circuitry 601. For example, the processing circuitry 602 can control the network interface circuitry 601 to transmit communications through the network interface circuitry 601 to one or more other network nodes and / or to receive communications from one or more other network nodes through the network interface circuitry. Further, modules can be stored in the memory 603, and these modules can provide instructions to cause the processing circuitry 602 to perform respective operations (e.g., operations discussed below with respect to example embodiments involving core network nodes) when the instructions of the modules are executed by the processing circuitry 602.

[0151] Figure 7 is a block diagram illustrating elements of a mobile network node 700 that is a mobile communication network. In some embodiments, the mobile network node 700 is a network function consumer. As illustrated, the mobile network node can include network interface circuitry 701 (also referred to as a network interface) configured to provide communication with a core network and / or other nodes of the network. The mobile network node can also include processing circuitry 702 (also referred to as a processor) coupled to the network interface circuitry and memory circuitry 703 (also referred to as a memory) coupled to the processing circuitry. The memory circuitry 703 can include computer-readable program code that, when executed by the processing circuitry 702, causes the processing circuitry to perform operations in accordance with embodiments disclosed herein. According to other embodiments, the processing circuitry 702 can be defined to include the memory, such that a separate memory circuitry is not needed. As discussed herein, the operations of the mobile network node can be performed by the processing circuitry 702 and / or the network interface circuitry 701. For example, the processing circuitry 702 can control the network interface circuitry 701 to transmit communications through the network interface circuitry 701 to one or more other network nodes and / or to receive communications from one or more other network nodes through the network interface circuitry. Further, modules can be stored in the memory 703, and these modules can provide instructions to cause the processing circuitry 702 to perform respective operations (e.g., the operations discussed below with respect to example embodiments involving core network nodes) when the instructions of the modules are executed by the processing circuitry 702.

[0152] Figure 8 is a block diagram illustrating a virtualization environment 800 in which functions, network functions or network nodes implemented by some embodiments of the present disclosure can be virtualized. In the present context, virtualization means the creation of virtual versions of devices or device components, which can include virtualization of hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device or component thereof described herein and involves embodiments in which at least part of the functionality is implemented as a virtual component or components. Some or all of the functionality described herein can be implemented as virtual components executed by one or more virtual machines, in one or more virtual environments 800 hosted by one or more hardware nodes, for example hardware computing devices operating as network nodes, UEs, core network nodes or hosts. Further, in embodiments in which the virtual node does not need radio connectivity (for example core network nodes or hosts), the node can be entirely virtualized. In some embodiments, the virtualization environment 800 includes components defined by the O-RAN Alliance, for example an O-Cloud environment orchestrated by a service management and orchestration framework via an O-2 interface.

[0153] The application 802, which can alternatively be referred to as a software instance, virtual appliance, network function, virtual node, virtual network function, etc., is run in the virtualization environment Q400 to implement certain features, functions, and / or benefits of some of the embodiments disclosed herein.

[0154] The hardware 804 comprises processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware

[0155] The VMs 808 comprise virtualized processing, memory, storage, and / or interfaces and can be run by a corresponding virtualization layer 806. Different embodiments of the instance of the virtual appliance 802 can be implemented in one or more of the VMs 808 and can be implemented in different ways.

[0156] In the context of NFV, the VMs 808 can be a software implementation of a physical machine that runs programs as if they were executing on the physical, non-virtualized

[0157] The hardware 804 can be implemented in a single network node with general or specific components. The hardware 804 can implement some functionality via virtualization. Alternatively, the hardware 804 can be part of a larger cluster of hardware, e.g., such as in a data center or CPE, where many hardware nodes work together and are managed via management and orchestration 810, which among others supervises life cycle management of applications 802. In some embodiments, the hardware 804 is coupled to one or more radio units, which each include one or more transmitters and one or more receivers that can be coupled to one or more antennas. The radio units can communicate directly with other hardware nodes via one or more appropriate networks, and can be used in combination with the virtual components to provide a virtual node with radio capabilities such as a radio access node or a base station. In some embodiments, some signaling can be provided using control system 812, which can alternatively be used for communication between the hardware nodes and the radio units.

[0158] Embodiments within the scope of the present invention can also include computer- readable media for carrying or having computer-executable instructions or data structures stored therein. Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code means in the form of computer-executable instructions or data structures. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or combination thereof) to a computer, the computer properly views the connection as a computer- readable medium. Thus, any such connection is properly termed a computer-readable medium. Combinations of the above should also be included within the scope of computer-readable media.

[0159] The computer-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing devices to perform a certain function or group of functions. The computer executable instructions also include program modules that are executed by the computer(s) in a coordinated or networked environment. Typically, program modules include routines, programs, objects, components, and data structures that perform particular tasks or implement particular abstract data types. Computer executable instructions, associated data structures, and program modules represent examples of the program code means for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps.

[0160] Those skilled in the art will appreciate that other embodiments of the application can be practiced in network computing environments with many types of computer system configurations, including personal computers, hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. Embodiments can also be practiced in distributed computing environments where tasks are performed by local and remote processing devices that are linked (either by hardwired links, wireless links, or a combination thereof) through a communications network. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

[0161] Communications for the various stages of the described system can be carried out through a local area network, a token ring network, the Internet, a corporate intranet, 802.11 series wireless signals, fiber optic networks, radio or microwave transmission, or the like. While the underlying communication technology can change, the basic principles described herein remain applicable.

[0162] The various embodiments described above are provided by way of illustration only and should not be construed as limiting the application. For example, the principles herein can be applied to any remotely controlled device. Further, those skilled in the art will recognize that communication between remotely controlled devices need not be limited to communication over a local area network, but can include communication over an infrared channel, Bluetooth, or any other suitable communication interface. Those skilled in the art will readily recognize various modifications and changes that can be made to the present application without following the example embodiments and applications illustrated and described herein, and without departing from the scope of the present disclosure.

[0163] The terminology used herein is for the purpose of describing various embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and "comprising", when used in this specification, specify the presence of stated features, integers, steps, operations, elements, or components, and combinations thereof, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or combinations thereof. Additionally, all terms used herein are intended to be interpreted in their broadest, ordinary way in the technical field, unless otherwise defined herein. All references to "a" or "one" or "the" element, device, component, means, step, etc., should be interpreted as including one or more instances of such element, device, component, means, step, etc., unless otherwise indicated. The steps of any method disclosed herein need not be performed in the exact order disclosed, unless explicitly stated.< / originalsubscriptionid> < / nid> < / mnc> < / mcc> < / originalsubscriptionid> < / nid> < / mnc> < / mcc> < / originalsubscriptionid> < / nid> < / mnc> < / mcc> < / originalsubscriptionid> < / nid> < / mnc> < / mcc> < / originalsubscriptionid> < / nid> < / mnc> < / mcc> < / originalsubscriptionid> < / nid> < / mnc> < / mcc> < / subscriptionid> < / subscriptionid> < / originalsubscriptionid> < / nid> < / mnc> < / mcc> < / originalsubscriptionid> < / mnc> < / mcc> < / originalsubscriptionid> < / nid> < / mnc> < / mcc> < / originalsubscriptionid> < / nid> < / mnc> < / mcc> < / originalsubscriptionid> < / nid> < / mnc> < / mcc> < / originalsubscriptionid> < / nid> < / mnc> < / mcc> < / originalsubscriptionid> < / nid> < / mnc> < / mcc> < / originalsubscriptionid> < / nid> < / mnc> < / mcc> < / originalsubscriptionid> < / nid> < / mnc> < / mcc> < / originalsubscriptionid> < / nid> < / mnc> < / mcc> < / originalsubscriptionid> < / nid> < / mnc> < / mcc> < / originalsubscriptionid> < / nid> < / mnc> < / mcc> < / originalsubscriptionid> < / nid> < / mnc> < / mcc> < / originalsubscriptionid> < / nid> < / mnc> < / mcc> < / originalsubscriptionid> < / nid> < / mnc> < / mcc> < / originalsubscriptionid> < / mnc> < / mcc>

Claims

1. A method for managing a subscription to a standalone non-public network, SNPN, in a communication network, the method comprising: receiving (S-301), at a first network node (500), a first subscription request from a network function consumer (700); sending (S-302), from the first network node, a second subscription request to a second network node (600); sending (S-402), from the second network node, a first subscription identifier to the first network node; and sending (S-304), from the first network node, a second subscription identifier to the network function consumer; wherein the first subscription identifier or the second subscription identifier comprises a mobile country code, MCC, a mobile network code, MNC, and a network identifier, NID, of the SNPN.

2. The method of claim 1, wherein, the first subscription identifier or the second subscription identifier is generated in a format of: <mcc> + <mnc>+""-""+"":nid= <nid> :""+ <originalsubscriptionid> 。< / originalsubscriptionid> < / nid> < / mnc> < / mcc> 3. The method of any one of claims 1-2, wherein, the first subscription identifier or the second subscription identifier further comprises a magic cookie to maintain compatibility with an earlier application programming interface, API, version.

4. The method of any one of claims 1 to 3, wherein, the first subscription identifier or the second subscription identifier comprises the NID of the SNPN after the magic cookie.

5. The method of any one of claims 1 to 4, wherein, the magic cookie is "x3Lf57A".

6. The method of any one of claims 1 to 5, wherein, the first subscription identifier or the second subscription identifier is generated in a format of: <mcc> + <mnc>+""-""+<magic_cookie>+"":nid= <nid> :""+ <originalsubscriptionid> 。< / originalsubscriptionid> < / nid> < / mnc> < / mcc> 7. The method of any one of claims 1 to 6, wherein, the network function consumer uses the second subscription identifier to modify or terminate the subscription.

8. The method of any one of claims 1 to 7, wherein, the first network node does not maintain a state of each created subscription.

9. The method of any one of claims 1 to 8, wherein, the first network node routes the subscription request to the second network node based on the MCC, the MNC, and the NID.

10. The method of any one of claims 1 to 9, wherein, the first network node is a local network repository function in a visited public land mobile network, the second network node is a home network repository function in a home public land mobile network, and the network function consumer is a network function service consumer in the visited public land mobile network.

11. A method for managing a subscription to a standalone non-public network, SNPN, in a communication network, the method being performed by a first network node (500), the method comprising: receiving (S-301) a first subscription request from a network function consumer (700); sending (S-302) a second subscription request to a second network node (600); receiving (S-303) a first subscription identifier from the second network node; and sending (S-304) a second subscription identifier to the network function consumer; wherein the first subscription identifier or the second subscription identifier comprises a mobile country code, MCC, a mobile network code, MNC, and a network identifier, NID, of the SNPN.

12. The method of claim 11, wherein, the first subscription identifier or the second subscription identifier is generated in a format of: <mcc> + <mnc>+""-""+"":nid= <nid> :""+ <originalsubscriptionid> 。< / originalsubscriptionid> < / nid> < / mnc> < / mcc> 13. The method of any one of claims 11-12, wherein, the first subscription identifier or the second subscription identifier further comprises a magic cookie to maintain compatibility with an earlier application programming interface, API, version.

14. The method of any one of claims 11-13, wherein, the first subscription identifier or the second subscription identifier comprises the NID of the SNPN after the magic cookie.

15. The method of any one of claims 11-14, wherein, The magic cookie is ""x3Lf57A"".

16. The method of any one of claims 11-15, wherein, The first subscription identifier or the second subscription identifier is generated in a format comprising: <mcc> + <mnc>+""-""+<magic_cookie>+"":nid= <nid> :""+ <originalsubscriptionid> 。< / originalsubscriptionid> < / nid> < / mnc> < / mcc> 17. The method of any one of claims 11-16, wherein, The network function consumer uses the second subscription identifier to modify or terminate the subscription.

18. The method of any one of claims 11-17, wherein, The first network node does not maintain a state of each created subscription.

19. The method of any one of claims 11-18, wherein, The first network node routes the subscription request to the second network node based on the MCC, the MNC, and the NID.

20. The method of any one of claims 11-19, wherein, The first network node is a local network repository function in a visited public land mobile network, the second network node is a home network repository function in a home public land mobile network, and the network function consumer is a network function service consumer in the visited public land mobile network.

21. A method for managing a subscription to a standalone non-public network, SNPN, in a communication network, the method being performed by a second network node (600), the method comprising: receiving (S-401), from a first network node (500), a subscription request; sending (S-403), to the first network node, a subscription identifier; wherein the subscription identifier comprises a mobile country code, MCC, a mobile network code, MNC, and a network identifier, NID, of the SNPN.

22. The method of claim 21, wherein, The subscription identifier is generated in a format comprising: <mcc> + <mnc>+""-""+"":nid= <nid> :""+ <originalsubscriptionid> 。< / originalsubscriptionid> < / nid> < / mnc> < / mcc> 23. The method of any one of claims 21-22, wherein, The subscription identifier further comprises a magic cookie to maintain compatibility with earlier Application Programming Interface, API, versions.

24. The method of any one of claims 21-23, wherein, The subscription identifier comprises the NID of the SNPN after the magic cookie.

25. The method of any one of claims 21-24, wherein, The magic cookie is ""x3Lf57A"".

26. The method of any one of claims 21-25, wherein, The subscription identifier is generated in a format comprising: <mcc> + <mnc>+""-""+<magic_cookie>+"":nid= <nid> :""+ <originalsubscriptionid> 。< / originalsubscriptionid> < / nid> < / mnc> < / mcc> 27. The method of any one of claims 21-26, wherein, The subscription identifier is used by a network function consumer to modify or terminate the subscription.

28. The method of any one of claims 21-27, wherein, The first network node does not maintain a state of each created subscription.

29. The method of any one of claims 21-28, wherein, The first network node routes the subscription request to the second network node based on the MCC, the MNC, and the NID.

30. The method of any one of claims 21-29, wherein, The first network node is a local network repository function in a visited public land mobile network, the second network node is a home network repository function in a home public land mobile network, and the network function consumer is a network function service consumer in the visited public land mobile network.

31. A method for managing a subscription to a standalone non-public network, SNPN, in a communication network, the method being performed by a network function consumer (700), the method comprising: sending (S-302), to a first network node (500), a subscription request; receiving (S-303), from the first network node, a subscription identifier; wherein the subscription identifier comprises a mobile country code, MCC, a mobile network code, MNC, and a network identifier, NID, of the SNPN.

32. The method of claim 31, wherein, The subscription identifier is generated in a format comprising: <mcc> + <mnc>+""-""+"":nid= <nid> :""+ <originalsubscriptionid> 。< / originalsubscriptionid> < / nid> < / mnc> < / mcc> 33. The method of any one of claims 31-32, wherein, The subscription identifier further comprises a magic cookie to maintain compatibility with earlier Application Programming Interface, API, versions.

34. The method of any one of claims 31-33, wherein, The subscription identifier comprises the NID of the SNPN after the magic cookie.

35. The method of any one of claims 31-34, wherein, The magic cookie is "x3Lf57A".

36. The method of any one of claims 31-35, wherein, The subscription identifier is generated using a format of: <mcc> + <mnc>+""-""+<magic_cookie>+"":nid= <nid> :""+ <originalsubscriptionid> 。< / originalsubscriptionid> < / nid> < / mnc> < / mcc> 37. The method of any one of claims 31-36, wherein, The network function consumer uses the subscription identifier to modify or terminate the subscription.

38. The method of any one of claims 31-37, wherein, The first network node does not maintain a state of each created subscription.

39. The method of any one of claims 31-38, wherein, The first network node is a local network repository function in a visited public land mobile network, the second network node is a home network repository function in a home public land mobile network, and the network function consumer is a network function service consumer in the visited public land mobile network.

40. An apparatus for managing a subscription to a standalone non-public network (SNPN) in a communication network, the apparatus comprising a processor and a memory, the memory containing instructions executable by the processor to cause the apparatus to be operable to perform a method according to any of claims 11-20.

41. An apparatus for managing a subscription to a standalone non-public network (SNPN) in a communication network, the apparatus comprising a processor and a memory, the memory containing instructions executable by the processor to cause the apparatus to be operable to perform a method according to any of claims 21-30.

42. An apparatus for managing a subscription to a standalone non-public network (SNPN) in a communication network, the apparatus comprising a processor and a memory, the memory containing instructions executable by the processor to cause the apparatus to be operable to perform a method according to any of claims 31-39.

43. A system comprising the apparatus of claim 40, the apparatus of claim 41, and the apparatus of claim 42.

44. A computer-implemented system comprising one or more processors and one or more computer storage media storing computer-usable instructions that, when used by the one or more processors, cause the one or more processors to perform a method according to any of claims 11-39.

Images