Control plane based steering of roaming and equivalent standalone non-public networks

Abstract

A method for control plane based steering of roaming in a communications network, the method comprising: receiving at an Access and Mobility Management Function, AMF, from a User Equipment, UE, comprising a Mobile Equipment, ME, when registering in a non-subscribed standalone non-public network, SNPN, a first indication that the ME supports or does not support Steering of Roaming SNPN Selection Information, SOR-SNPN-SI; transmitting from the AMF to a Unified Data Management, UDM, a second indication that the ME supports or does not support SOR-SNPN-SI; and storing or deleting at the UDM an indicator of ME support of SOR-SNPN-SI based on the second indication. In some embodiments the UDM stores an "ME support of SOR-SNPN-SI" indicator if the ME of the UE supports SOR-SNPN-SI. In some embodiments the UDM deletes a stored "ME support of SOR-SNPN-SI" indicator if the ME of the UE does not support SOR-SNPN-SI.

Description

[0001] CONTROL PLANE BASED STEERING OF ROAMING AND EQUIVALENT STANDALONE NON-PUBLIC NETWORKS

[0002] TECHNICAL FIELD

[0003] The present invention generally relates to standalone non-public networks (SNPNs) in 3GPP mobile networks, and more specifically, the invention relates to determining the capability of a User Equipment to support control plane-based steering of roaming and Steering of Roaming SNPN Selection Information (SOR-SNPN-SI).

[0004] BACKGROUND

[0005] In the Third Generation Partnership Project (3GPP) specifications, a standalone non-public network (SNPN) is a type of network (communications network, mobile network or cellular network), which offers network services to a restricted, specified set of User Equipments (UE), and is independent of the public network. A UE is mainly only able to operate in its subscribed SNPN. However, a UE supporting access to an SNPN using credentials from a credentials holder may register in a non-subscribed SNPN, and the subscribed SNPN or the HPLMN may control which non-subscribed SNPN the UE selects using control plane based steering of roaming and Steering of Roaming SNPN Selection Information (SOR-SNPN-SI). A UE supporting access to an SNPN using credentials from a credentials holder shall support control plane based steering of roaming and SOR-SNPN-SI.

[0006] To enable a Unified Data Management (UDM) to distinguish between (a) UEs supporting access to an SNPN using credentials from a credentials holder (to which control plane based steering of roaming with SOR-SNPN-SI can be performed), and (b) UEs not supporting access to an SNPN using credentials from a credentials holder and UEs (to which control plane based steering of roaming with SOR-SNPN-SI cannot be performed), the UE indicates that the ME of the UE supports SOR-SNPN-SI in a 5GMM capability Information Element (IE) of REGISTRATION REQUEST when the UE registers in the subscribed SNPN. In a non-subscribed SNPN, no indication of ME's support of SOR-SNPN-SI is needed as only a UE supporting access to an SNPN using credentials from a credentials holder can select a non-subscribed SNPN and thus ME of any UE in non-subscribed SNPN supports SOR-SNPN-SI.

[0007] Thus, the UDM determines that it is possible to perform control plane based steering of roaming and SOR-SNPN-SI towards a UE in an SNPN if: (1 ) the UE is in the subscribed SNPN, and the AMF indicates to the UDM that the ME supports SOR-SNPN-SI (the AMF does so when the UE indicates that ME supports SOR-SNPN-SI in 5GMM capability IE of REGISTRATION REQUEST); or (2) the UE is in non-subscribed SNPN.

[0008] A UE supporting equivalent SNPNs but not supporting access to an SNPN using credentials from a credentials holder can also register in a non-subscribed SNPN, if the non-subscribed SNPN was indicated as an equivalent SNPN when the UE previously registered in the subscribed SNPN. Such UE does not need to support control plane based steering of roaming with SOR-SNPN-SI as the UE is able to register only in the subscribed SNPN or a non-subscribed SNPN, which was indicated as an equivalent SNPN when the UE previously registered in the subscribed SNPN. The selection of such non-subscribed SNPN is controlled by network provided list of equivalent SNPNs (and not by SOR-SNPN-SI).

[0009] A problematic aspect is that when a UE is in a non-subscribed SNPN and the subscribed SNPN is an equivalent SNPN, the UDM is not able to distinguish the following cases: (a) the UE supporting access to an SNPN using credentials from a credentials holder (such UE supports control plane based steering of roaming and SOR-SNPN-SI but does not provide indication of SOR-SNPN-SI support); and (b) the UE supporting equivalent SNPNs but not supporting access to an SNPN using credentials from a credentials holder. Such UE does not need to support control plane based steering of roaming and SOR-SNPN-SI.

[0010] Thus, the UDM is unable to determine whether the UDM can perform a control plane based steering of roaming with SOR-SNPN-SI to a UE in non-subscribed SNPN when the nonsubscribed SNPN is an equivalent to the subscribed SNPN. This uncertainty can lead to inefficient network resource management and performance issues. SUMMARY

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

[0012] An object of the invention is to enable the UDM to perform a control plane based steering of roaming with SOR-SNPN-SI to a LIE in non-subscribed SNPN when the non-subscribed SNPN is an equivalent to the subscribed SNPN.

[0013] This disclosure provides a method for control plane based steering of roaming in a communications network, the method comprises receiving at an Access and Mobility Management Function (AMF) from a User Equipment (UE) comprising a Mobile Equipment (ME) when registering in a non-subscribed standalone non-public network (SNPN) a first indication that the ME supports or does not support Steering of Roaming SNPN Selection Information (SOR-SNPN-SI); transmitting from the AMF to a Unified Data Management, UDM, a second indication that the ME supports or does not support SOR-SNPN-SI; and storing or deleting at the UDM an indicator of ME support of SOR-SNPN-SI based on the second indication. In some embodiments, the UDM stores an "ME support of SOR-SNPN- SI" indicator if the ME of the UE supports SOR-SNPN-SI. In some embodiments, the UDM deletes a stored "ME support of SOR-SNPN-SI" indicator if the ME of the UE does not support SOR-SNPN-SI. In some embodiments, the first indication is received from the UE at the AMF when the UE supports equivalent SNPNs and access to an SNPN using credentials from a credentials holder. In some embodiments, the second indication indicates that the UE supports equivalent SNPNs, the UE is in an equivalent SNPN of the subscribed SNPN, and the ME does not support SOR-SNPN-SI if the AMF is in a equivalent SNPN of the subscribed SNPN, the UE supports equivalent SNPNs and the UE does not indicate that ME supports SOR-SNPN-SI. In some embodiments, the first indication is included in a 5GMM capability IE of the registration request.

[0014] A first aspect of the invention relates to a method for control plane based steering of roaming in a communications network, the method performed by an Access and Mobility Management Function (AMF), the method comprising receiving at the AMF from a User Equipment (UE) comprising a Mobile Equipment (ME) when registering in a non-subscribed standalone non-public network (SNPN) a first indication that the ME supports or does not support Steering of Roaming SNPN Selection Information (SOR-SNPN-SI); and transmitting from the AMF to a Unified Data Management, UDM, a second indication that the ME supports or does not support SOR-SNPN-SI. In some embodiments, the first indication is received from the UE at the AMF when the UE supports equivalent SNPNs and access to an SNPN using credentials from a credentials holder. In some embodiments, the second indication indicates that the UE supports equivalent SNPNs, the UE is in an equivalent SNPN of the subscribed SNPN, and the ME does not support SOR-SNPN-SI if the AMF is in a equivalent SNPN of the subscribed SNPN, the UE supports equivalent SNPNs and the UE does not indicate that ME supports SOR-SNPN-SI. In some embodiments, the first indication is included in a 5GMM capability IE of the registration request.

[0015] A second aspect of the invention relates to a method for control plane based steering of roaming in a communications network, the method performed by a Unified Data Management (UDM), the method comprising receiving at the UDM from an Access and Mobility Management Function (AMF) a second indication that a Mobile Equipment (ME) supports or does not support SOR-SNPN-SI when a User Equipment, UE, comprising the ME registers in a non-subscribed standalone non-public network (SNPN); and storing or deleting at the UDM an indicator of ME support of SOR-SNPN-SI based on the second indication. In some embodiments, the UDM stores an "ME support of SOR-SNPN-SI" indicator if the ME of the UE supports SOR-SNPN-SI. In some embodiments, the UDM deletes a stored "ME support of SOR-SNPN-SI" indicator if the ME of the UE does not support SOR-SNPN-SI. In some embodiments, the UE supports equivalent SNPNs and access to an SNPN using credentials from a credentials holder. In some embodiments, the second indication indicates that the UE supports equivalent SNPNs, the UE is in an equivalent SNPN of the subscribed SNPN, and the ME does not support SOR-SNPN-SI if the AMF is in an equivalent SNPN of the subscribed SNPN, the UE supports equivalent SNPNs and the UE does not indicate that ME supports SOR-SNPN-SI.

[0016] Advantageously, the UDM is enabled to know whether the UDM can perform a control plane based steering of roaming with SOR-SNPN-SI to a UE in non-subscribed SNPN when the non-subscribed SNPN is an equivalent to the subscribed SNPN.

[0017] BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to best describe the manner in which the disclosed concepts may be implemented, as well as define other objects, advantages and features of the disclosure, a more particular description is provided below and is illustrated in the appended drawings. Understanding that these drawings depict only exemplary embodiments of the invention and are not therefore to be considered to be limiting in scope, the examples will be described and explained with additional specificity and detail through the use of the accompanying drawings.

[0019] Figure 1 illustrates an example networked system in accordance with particular embodiments of the solution described herein.

[0020] Figure 2 illustrates an example signaling diagram showing a procedure according to particular embodiments of the solution described herein.

[0021] Figure 3 illustrates an example flowchart showing a method performed by a mobile network node according to particular embodiments of the solution described herein.

[0022] Figure 4 illustrates an example flowchart showing a method performed by a mobile network node according to particular embodiments of the solution described herein.

[0023] Figure 5 illustrates an example block diagram of a mobile network node configured in accordance with particular embodiments of the solution described herein.

[0024] Figure 6 illustrates an example block diagram of a mobile network node configured in accordance with particular embodiments of the solution described herein.

[0025] Figure 7 illustrates an example block diagram of a virtualized environment.

[0026] DETAILED DESCRIPTION

[0027] The invention will now be described in detail hereinafter with reference to the accompanying drawings, in which examples of embodiments or implementations of the invention are shown. The invention may, however, be embodied or implemented 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 will fully convey the scope of present invention to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present / used in another embodiment. These embodiments of the disclosed subject matter are presented as teaching examples and are not to be construed as limiting the scope of the disclosed subject matter. For example, certain details of the described embodiments may be modified, omitted, or expanded upon without departing from the scope of the described subject matter.

[0028] The example embodiments described herein arise in the context of a telecommunications network, including but not limited to a telecommunications network that conforms to and / or otherwise incorporates aspects of a fifth generation (5G) architecture. Figure 1 is an example networked system 100 in accordance with example embodiments of the present disclosure. Figure 1 specifically illustrates User Equipment (UE) 101 , which may be in communication with a (Radio) Access Network (RAN) 102 and Access and Mobility Management Function (AMF) 106 and User Plane Function (UPF) 103. The AMF 106 may, in turn, be in communication with core network services including Session Management Function (SMF) 107 and Policy Control Function (PCF) 111. The core network services may also be in communication with an Application Server / Application Function (AS / AF) 113. Other networked services also include Network Slice Selection Function (NSSF) 108, Authentication Server Function (AUSF) 105, User Data Management (UDM) 112, Network Exposure Function (NEF) 109, Network Repository Function (NRF) 110, User Data Repository (UDR) 114, Network Data Analytics Function (NWDAF) 115, and Data Network (DN) 104. In some example implementations of embodiments of the present disclosure, each one of the entities in the networked system 100 are considered to be a Network Function (NF). One or more additional instances of the NFs may be incorporated into the networked system.

[0029] The solution described herein aims to enable the UDM to perform a control plane based steering of roaming with SOR-SNPN-SI to a UE in non-subscribed SNPN when the nonsubscribed SNPN is an equivalent to the subscribed SNPN.

[0030] This disclosure provides a method for control plane based steering of roaming in a communications network, the method comprises receiving at an Access and Mobility Management Function (AMF) from a User Equipment (UE) comprising a Mobile Equipment (ME) when registering in a non-subscribed standalone non-public network (SNPN) a first indication that the ME supports or does not support Steering of Roaming SNPN Selection Information (SOR-SNPN-SI); transmitting from the AMF to a Unified Data Management, UDM, a second indication that the ME supports or does not support SOR-SNPN-SI; and storing or deleting at the UDM an indicator of ME support of SOR-SNPN-SI based on the second indication. In some embodiments, the UDM stores an "ME support of SOR-SNPN- SI" indicator if the ME of the LIE supports SOR-SNPN-SI. In some embodiments, the UDM deletes a stored "ME support of SOR-SNPN-SI" indicator if the ME of the UE does not support SOR-SNPN-SI. In some embodiments, the first indication is received from the UE at the AMF when the UE supports equivalent SNPNs and access to an SNPN using credentials from a credentials holder. In some embodiments, the second indication indicates that the UE supports equivalent SNPNs, the UE is in an equivalent SNPN of the subscribed SNPN, and the ME does not support SOR-SNPN-SI if the AMF is in a equivalent SNPN of the subscribed SNPN, the UE supports equivalent SNPNs and the UE does not indicate that ME supports SOR-SNPN-SI. In some embodiments, the first indication is included in a 5GMM capability IE of the registration request.

[0031] A first aspect of the invention relates to a method for control plane based steering of roaming in a communications network, the method performed by an Access and Mobility Management Function (AMF), the method comprising receiving at the AMF from a User Equipment (UE) comprising a Mobile Equipment (ME) when registering in a non-subscribed standalone non-public network (SNPN) a first indication that the ME supports or does not support Steering of Roaming SNPN Selection Information (SOR-SNPN-SI); and transmitting from the AMF to a Unified Data Management, UDM, a second indication that the ME supports or does not support SOR-SNPN-SI. In some embodiments, the first indication is received from the UE at the AMF when the UE supports equivalent SNPNs and access to an SNPN using credentials from a credentials holder. In some embodiments, the second indication indicates that the UE supports equivalent SNPNs, the UE is in an equivalent SNPN of the subscribed SNPN, and the ME does not support SOR-SNPN-SI if the AMF is in a equivalent SNPN of the subscribed SNPN, the UE supports equivalent SNPNs and the UE does not indicate that ME supports SOR-SNPN-SI. In some embodiments, the first indication is included in a 5GMM capability IE of the registration request.

[0032] A second aspect of the invention relates to a method for control plane based steering of roaming in a communications network, the method performed by a Unified Data Management (UDM), the method comprising receiving at the UDM from an Access and Mobility Management Function (AMF) a second indication that a Mobile Equipment (ME) supports or does not support SOR-SNPN-SI when a User Equipment, UE, comprising the ME registers in a non-subscribed standalone non-public network (SNPN); and storing or deleting at the UDM an indicator of ME support of SOR-SNPN-SI based on the second indication. In some embodiments, the UDM stores an "ME support of SOR-SNPN-SI" indicator if the ME of the LIE supports SOR-SNPN-SI. In some embodiments, the UDM deletes a stored "ME support of SOR-SNPN-SI" indicator if the ME of the UE does not support SOR-SNPN-SI. In some embodiments, the UE supports equivalent SNPNs and access to an SNPN using credentials from a credentials holder. In some embodiments, the second indication indicates that the UE supports equivalent SNPNs, the UE is in an equivalent SNPN of the subscribed SNPN, and the ME does not support SOR-SNPN-SI if the AMF is in an equivalent SNPN of the subscribed SNPN, the UE supports equivalent SNPNs and the UE does not indicate that ME supports SOR-SNPN-SI.

[0033] This disclosure further provides a method for control plane based steering of roaming in a communications network, the method comprising: registering a User Equipment (UE) in a non-subscribed standalone non-public network (SNPN); transmitting from the UE to an Access and Mobility Management Function (AMF), when the UE supports equivalent SNPNs and access to an SNPN using credentials from a credentials holder, an indication that the Mobile Equipment (ME) supports Steering of Roaming SNPN Selection Information (SOR- SNPN-SI) in a 5GMM capability IE of Registration Request; transmitting from the UE to an Access and Mobility Management Function (AMF), when the UE supports equivalent SNPNs, an indication that the UE supports equivalent SNPNs in a 5GMM capability IE of Registration Request; determining at a Unified Data Management (UDM) that ME of the UE in an SNPN supports SOR-SNPN-SI based on an indication received from the AMF. In some embodiments, the method further comprises: transmitting from the AMF to the UDM an indication that the UE supporting equivalent SNPNs is in a non-subscribed SNPN and the subscribed SNPN is an equivalent SNPN, if the AMF is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN and the UE supports equivalent SNPNs; and / or if the UE indicates that ME supports SOR-SNPN-SI, transmitting from the AMF to the UDM an indication that ME supports SOR-SNPN-SI. In some embodiments, the UDM determines that the ME of the UE in an SNPN supports SOR-SNPN-SI if: the UE is in the subscribed SNPN, and the AMF indicates to the UDM that ME supports SOR-SNPN-SI; the UE is in a nonsubscribed SNPN and the AMF does not indicate to the UDM that the UE supporting equivalent SNPNs is in a non-subscribed SNPN and the subscribed SNPN is an equivalent SNPN; or the UE is in a non-subscribed SNPN, the AMF indicates that the UE supporting equivalent SNPNs is in a non-subscribed SNPN and the subscribed SNPN is an equivalent SNPN, and the AMF indicates to the UDM that the ME supports SOR-SNPN-SI. In some embodiments, the method further comprises transmitting from the AMF to the UDM an indication that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI if the AMF is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the LIE supports equivalent SNPNs and the UE does not indicate that ME supports SOR-SNPN-SI in 5GMM capability IE of REGISTRATION REQUEST. In some embodiments, the UDM determines that ME of the UE in an SNPN supports SOR-SNPN-SI if: the UE is in the subscribed SNPN, and the AMF indicates to the UDM that ME supports SOR-SNPN-SI; or the UE is in a non-subscribed SNPN and the AMF does not indicate to the UDM that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI. In some embodiments, the method further comprises: transmitting from the UE to the AMF either an indication that ME supports SOR-SNPN-SI in 5GMM capability IE of REGISTRATION REQUEST, or an indication that ME does not support SOR-SNPN-SI; and transmitting from the AMF to the UDM that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME supports SOR-SNPN-SI, if the AMF serving the UE is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports equivalent SNPNs and the UE indicates that ME supports SOR-SNPN-SI; or that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI, if the AMF serving the UE is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports equivalent SNPNs and the UE does not indicate that ME supports SOR-SNPN-SI. In some embodiments, the UDM determines that ME of the UE in an SNPN supports SOR- SNPN-SI if: the UE is in the subscribed SNPN, and the AMF indicates to the UDM that ME supports SOR-SNPN-SI; the UE is in a non-subscribed SNPN and the AMF does not indicate to the UDM that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME supports SOR-SNPN-SI, or that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI; or the UE is in a nonsubscribed SNPN and the AMF indicates to the UDM that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME supports SOR-SNPN-SI.

[0034] A further aspect of the invention relates to a method for control plane based steering of roaming in a communications network, the method performed by an Access and Mobility Management Function (AMF), the method comprising: receiving from a User Equipment (UE) at the Access and Mobility Management Function (AMF), when the UE supports equivalent SNPNs and access to an SNPN using credentials from a credentials holder, an indication that the Mobile Equipment (ME) supports Steering of Roaming SNPN Selection Information (SOR-SNPN-SI) in a 5GMM capability IE of Registration Request; receiving from the LIE at the Access and Mobility Management Function (AMF), when the LIE supports equivalent SNPNs, an indication that the UE supports equivalent SNPNs in a 5GMM capability IE of Registration Request. In some embodiments, the method further comprises: transmitting from the AMF to a Unified Data Management (UDM) an indication that the UE supporting equivalent SNPNs is in a non-subscribed SNPN and the subscribed SNPN is an equivalent SNPN, if the AMF is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN and the UE supports equivalent SNPNs; and / or if the UE indicates that ME supports SOR-SNPN-SI, transmitting from the AMF to a Unified Data Management (UDM) an indication that ME supports SOR-SNPN-SI. In some embodiments, the method further comprises transmitting from the AMF to the UDM an indication that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI if the AMF is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports equivalent SNPNs and the UE does not indicate that ME supports SOR-SNPN-SI in 5GMM capability IE of REGISTRATION REQUEST. In some embodiments, the method further comprises: receiving from the UE at the AMF either an indication that ME supports SOR-SNPN-SI in 5GMM capability IE of REGISTRATION REQUEST, or an indication that ME does not support SOR-SNPN-SI; and transmitting from the AMF to a Unified Data Management (UDM): that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME supports SOR-SNPN-SI, if the AMF serving the UE is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports equivalent SNPNs and the UE indicates that ME supports SOR-SNPN-SI; or that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI, if the AMF serving the UE is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports equivalent SNPNs and the UE does not indicate that ME supports SOR- SNPN-SI.

[0035] A further aspect of the invention relates to a method for control plane based steering of roaming in a communications network, the method performed by a Unified Data Management (UDM), the method comprising: determining at the Unified Data Management (UDM) that ME of the UE in an SNPN supports SOR-SNPN-SI based on an indication received from the AMF. In some embodiments, the method further comprises: receiving from the AMF at the UDM an indication that the LIE supporting equivalent SNPNs is in a nonsubscribed SNPN and the subscribed SNPN is an equivalent SNPN, if the AMF is in a nonsubscribed SNPN, the subscribed SNPN is an equivalent SNPN and the LIE supports equivalent SNPNs; and / or if the UE indicates that ME supports SOR-SNPN-SI, receiving from the AMF at the UDM an indication that ME supports SOR-SNPN-SI. In some embodiments, the UDM determines that the ME of the UE in an SNPN supports SOR- SNPN-SI if: the UE is in the subscribed SNPN, and the AMF indicates to the UDM that ME supports SOR-SNPN-SI; the UE is in a non-subscribed SNPN and the AMF does not indicate to the UDM that the UE supporting equivalent SNPNs is in a non-subscribed SNPN and the subscribed SNPN is an equivalent SNPN; or the UE is in a non-subscribed SNPN, the AMF indicates that the UE supporting equivalent SNPNs is in a non-subscribed SNPN and the subscribed SNPN is an equivalent SNPN, and the AMF indicates to the UDM that the ME supports SOR-SNPN-SI. In some embodiments, the method further comprises receiving from the AMF at the UDM an indication that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI if the AMF is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports equivalent SNPNs and the UE does not indicate that ME supports SOR-SNPN-SI in 5GMM capability IE of REGISTRATION REQUEST. In some embodiments, the UDM determines that ME of the UE in an SNPN supports SOR-SNPN-SI if: the UE is in the subscribed SNPN, and the AMF indicates to the UDM that ME supports SOR-SNPN-SI; or the UE is in a non-subscribed SNPN and the AMF does not indicate to the UDM that the UE supporting equivalent SNPNs is in a nonsubscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI. In some embodiments, the method further comprises: receiving from the AMF at the UDM: that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME supports SOR-SNPN-SI, if the AMF serving the UE is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports equivalent SNPNs and the UE indicates that ME supports SOR- SNPN-SI; or that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI, if the AMF serving the UE is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports equivalent SNPNs and the UE does not indicate that ME supports SOR-SNPN-SI. In some embodiments, the UDM determines that ME of the UE in an SNPN supports SOR-SNPN-SI if: the LIE is in the subscribed SNPN, and the AMF indicates to the LIDM that ME supports SOR-SNPN-SI; the LIE is in a non-subscribed SNPN and the AMF does not indicate to the UDM that the UE supporting equivalent SNPNs is in a nonsubscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME supports SOR- SNPN-SI, or that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI; or the UE is in a non-subscribed SNPN and the AMF indicates to the UDM that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME supports SOR-SNPN-SI.

[0036] Advantageously, the UDM is enabled to determine whether the UDM can perform a control plane based steering of roaming with SOR-SNPN-SI to a UE in non-subscribed SNPN when the non-subscribed SNPN is an equivalent to the subscribed SNPN.

[0037] This disclosure also provides mobile network nodes, particularly an Access and Mobility Management Function (AMF) (106, 500), and a Unified Data Management (UDM) (112, 600) configured to perform the respective methods as described herein.

[0038] This disclosure also provides the corresponding computer program and computer program products comprising code, for example in the form of a computer program, that when run on processing circuitry of the mobile network nodes causes the mobile network nodes to perform the disclosed methods.

[0039] In the solution disclosed herein, if the UE registers in a non-subscribed SNPN, supports equivalent SNPNs and supports access to an SNPN using credentials from a credentials holder, the UE indicates that ME supports SOR-SNPN-SI in 5GMM capability IE of REGISTRATION REQUEST. This is an extension of usage of existing indication, which is used in the subscribed SNPN.

[0040] If the AMF serving the UE is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the UE supports equivalent SNPNs:

[0041] 1 ) the AMF indicates to the UDM that the UE supporting equivalent SNPNs is in a nonsubscribed SNPN and the subscribed SNPN is an equivalent SNPN; and

[0042] 2) if the UE indicates that ME supports SOR-SNPN-SI, the AMF indicates to the UDM that ME supports SOR-SNPN-SI.

[0043] The UDM determines that ME of the UE in an SNPN supports SOR-SNPN-SI if: 1 ) the LIE is in the subscribed SNPN, and the AMF indicates to the UDM that ME supports SOR-SNPN-SI;

[0044] 2) the LIE is in a non-subscribed SNPN and the AMF does not indicate to the UDM that the UE supporting equivalent SNPNs is in a non-subscribed SNPN and the subscribed SNPN is an equivalent SNPN; or

[0045] 3) the UE is in a non-subscribed SNPN, the AMF indicates that the UE supporting equivalent SNPNs is in a non-subscribed SNPN and the subscribed SNPN is an equivalent SNPN, and the AMF indicates to the UDM that the ME supports SOR-SNPN-SI.

[0046] Alternatively, if the UE registers in a non-subscribed SNPN, supports equivalent SNPNs and supports access to an SNPN using credentials from a credentials holder, the UE indicates that ME supports SOR-SNPN-SI in 5GMM capability IE of REGISTRATION REQUEST. This is an extension of usage of existing indication, which is used in the subscribed SNPN.

[0047] If the AMF serving the UE is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports equivalent SNPNs and the UE does not indicate that ME supports SOR-SNPN-SI in 5GMM capability IE of REGISTRATION REQUEST, the AMF indicates to the UDM that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR- SNPN-SI.

[0048] The UDM determines that ME of the UE in an SNPN supports SOR-SNPN-SI if:

[0049] 1 ) the UE is in the subscribed SNPN, and the AMF indicates to the UDM that ME supports SOR-SNPN-SI;

[0050] 2) the UE is in a non-subscribed SNPN and the AMF does not indicate to the UDM that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI.

[0051] Alternatively, if the UE registers in a non-subscribed SNPN, supports equivalent SNPNs and supports access to an SNPN using credentials from a credentials holder, the UE indicates that ME supports SOR-SNPN-SI in 5GMM capability IE of REGISTRATION REQUEST. This is an extension of usage of existing indication, which is used in the subscribed SNPN.

[0052] If the AMF serving the UE is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports equivalent SNPNs and a) the UE indicates that ME supports SOR-SNPN-SI in 5GMM capability IE of REGISTRATION REQUEST, the AMF indicates to the UDM that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME supports SOR-SNPN-SI. b) the UE does not indicate that ME supports SOR-SNPN-SI in 5GMM capability IE of REGISTRATION REQUEST, the AMF indicates to the UDM that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI.

[0053] The UDM determines that ME of the UE in an SNPN supports SOR-SNPN-SI if:

[0054] 1 ) the UE is in the subscribed SNPN, and the AMF indicates to the UDM that ME supports SOR-SNPN-SI;

[0055] 2) the UE is in a non-subscribed SNPN and the AMF does not indicate to the UDM neither that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME supports SOR-SNPN-SI, nor that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI.

[0056] 3) the UE is in a non-subscribed SNPN and the AMF indicates to the UDM that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME supports SOR-SNPN-SI.

[0057] Hereinafter, drawings showing examples of embodiments of the solution are described in detail.

[0058] Figure 2 is a signaling diagram illustrating a procedure for control plane based steering of roaming in a communications network. The procedure is performed by a UE 101 , an AMF 106, a UDM 112 and a SOR-AF 113.

[0059] The steps of the procedure are as follows:

[0060] In step 1 , the UE transmits to the AMF a Registration Request.

[0061] In step 2, the AMF initiates the registration procedure by sending a Nudm UECM Registration request to the UDM. This message includes the deletion of the "ME support of SOR-CMCI" indicator if the NAS registration type is either "initial" or "emergency". The UDM responds with a Nudm UECM Registration response. In step 3, the AMF sends a Nudm SDM Get request to the LIDM. This step involves a decision-making process regarding whether to send SOR (Steering of Roaming) information, whether to request ACK from the LIE, and how to obtain the SOR-SNPN-SI. In step 3b, the LIDM transmits a Nsoarf_SoR_Get request to the SOR-AF, which responds with a Nsoarf_SoR_Get response in step 3c. In step 3d, the UDM secures the information.

[0062] In step 4, the UDM sends a Nudm SDM Get response back to the AMF.

[0063] In step 5, the AMF sends a Nudm SDM Subscribe request to the UDM.

[0064] In step 6, the AMF then sends a Registration Accept message to the UE.

[0065] In step 7, the UE performs a steering of roaming information security check and completes the registration process.

[0066] In step 8, if the security check fails, the UE performs SNPN (Standalone Non-Public Network) or PLMN (Public Land Mobile Network) selection procedure and ends the procedure, completing the registration.

[0067] In step 9, the UE completes the registration process.

[0068] In step 10, the AMF sends a Nudm SDM Info request to the UDM, which then sends a Nsoarf SoRJnfo request to the SOR-AF in step 10a.

[0069] In step 11 , the UE performs the SNPN or SPN selection procedure if a higher priority SNPN or PLMN is available.

[0070] The procedure disclosed herein includes the following when the AMF is located in the nonsubscribed SNPN and the UDM is located in the HPLMN or subscribed SNPN.

[0071] In step 1 , the UE initiates initial registration, emergency registration or registration procedure for mobility and periodic registration update to the AMF by sending a REGISTRATION REQUEST message with the 5GS registration type IE indicating "initial registration", "emergency registration" or "mobility registration updating". If the UE supports access to an SNPN using credentials from a credentials holder and equivalent SNPNs, the UE shall indicate ME's support for SOR-SNPN-SI in the 5GMM capability.

[0072] In step 2, upon receiving the REGISTRATION REQUEST message, the AMF executes the registration procedure. As part of the registration procedure: a) the AMF provides the registration type to the UDM using Nudm UECM Registration; and b) if required, the AMF indicates to the UDM that the UE supporting equivalent SNPNs is in a non-subscribed SNPN and the subscribed SNPN is an equivalent SNPN; c) if required, the AMF informs the UDM whether the ME supports SOR-SNPN-SI.

[0073] As a consequence, in case of the 5GS registration type message indicates "initial registration" or "emergency registration" the UDM shall delete the stored "ME support of SOR-CMCI" indicator, if any, and the stored "ME support of SOR-SNPN-SI-LS" indicator, if any, in UDR using Nudr DM Update service operation.

[0074] The UDM shall store or delete the "ME support of SOR-SNPN-SI" indicator.

[0075] Nudr DM Update service operation corresponds to Nudr DR Update service operation.

[0076] If the UE supports access to an SNPN using credentials from a credentials holder, the UE shall indicate ME's support for SOR-SNPN-SI in the 5GMM capability when registering in: a) the subscribed SNPN; or b) a non-subscribed SNPN, if the UE supports equivalent SNPNs.

[0077] When: a) the UE indicates ME's support for SOR-SNPN-SI in the 5GMM capability in initial registration or emergency registration; or b) ME's support for SOR-SNPN-SI changes in mobility registration update, and the AMF is: a) in the subscribed SNPN; or b) in a non-subscribed SNPN, the subscribed SNPN of the UE is an equivalent SNPN, and the UE supports equivalent SNPNs; the AMF shall inform the UDM whether the ME supports SOR-SNPN-SI in the Nudm UECM Registration.

[0078] If the AMF serving the UE is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the UE supports equivalent SNPNs, the AMF indicates to the UDM that the UE supporting equivalent SNPNs is in a non-subscribed SNPN and the subscribed SNPN is an equivalent SNPN in the Nudm UECM Registration.

[0079] The UDM shall determine that a ME of the UE in an SNPN supports SOR-SNPN-SI if:

[0080] 1 ) the UE is in the subscribed SNPN, and the AMF indicates to the UDM that ME supports SOR-SNPN-SI;

[0081] 2) the UE is in a non-subscribed SNPN and the AMF does not indicate to the UDM that the UE supporting equivalent SNPNs is in a non-subscribed SNPN and the subscribed SNPN is an equivalent SNPN; or

[0082] 3) the UE is in a non-subscribed SNPN, the AMF indicates that the UE supporting equivalent SNPNs is in a non-subscribed SNPN and the subscribed SNPN is an equivalent SNPN, and the AMF indicates to the UDM that the ME supports SOR-SNPN-SI.

[0083] When handling the Nudm UECM Registration for a UE in an SNPN, if the UDM determines that the ME of the UE in an SNPN supports SOR-SNPN-SI, the UDM shall store the "ME support of SOR-SNPN-SI" indicator otherwise the UDM deletes the stored "ME support of SOR-SNPN-SI" indicator, if any.

[0084] Instead of indicating "the UE supporting equivalent SNPNs is in a non-subscribed SNPN and the subscribed SNPN is an equivalent SNPN" and "the ME supports SOR-SNPN-SI", the AMF may indicate "the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI" in the condition indicated in alternative 2 and the UDM will use it as per the disclosure herein.

[0085] Instead of indicating "the UE supporting equivalent SNPNs is in a non-subscribed SNPN and the subscribed SNPN is an equivalent SNPN" and "the ME supports SOR-SNPN-SI" in two separate indications, the AMF may include a single indication to indicate either: a) "the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME supports SOR-SNPN-SI" or b) "the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI" Hereinafter, flowcharts showing examples of embodiments of the solution are described in detail.

[0086] Figure 3 is a flowchart illustrating a method for control plane based steering of roaming in a communications network, the method performed by an Access and Mobility Management Function (AMF) 106.

[0087] In step S-301 , the AMF may receive from a User Equipment (UE), when the UE supports equivalent SNPNs and access to an SNPN using credentials from a credentials holder, an indication that the Mobile Equipment (ME) supports Steering of Roaming SNPN Selection Information (SOR-SNPN-SI) in a 5GMM capability IE of Registration Request.

[0088] In step S-302, the AMF may receive from the UE, when the UE supports equivalent SNPNs, an indication that the UE supports equivalent SNPNs in a 5GMM capability IE of Registration Request.

[0089] In step S-303, the AMF may transmit to a Unified Data Management (UDM) an indication that the UE supporting equivalent SNPNs is in a non-subscribed SNPN and the subscribed SNPN is an equivalent SNPN, if the AMF is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN and the UE supports equivalent SNPNs; and / or if the UE indicates that ME supports SOR-SNPN-SI, transmits from the AMF to a Unified Data Management (UDM) an indication that ME supports SOR-SNPN-SI.

[0090] In step S-304, the AMF may transmit to the UDM an indication that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI if the AMF is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports equivalent SNPNs and the UE does not indicate that ME supports SOR-SNPN-SI in 5GMM capability IE of REGISTRATION REQUEST.

[0091] In step S-305, the AMF may receive from the UE either an indication that ME supports SOR- SNPN-SI in 5GMM capability IE of REGISTRATION REQUEST, or an indication that ME does not support SOR-SNPN-SI.

[0092] In step S-306, the AMF may transmit to a Unified Data Management (UDM): that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME supports SOR-SNPN-SI, if the AMF serving the UE is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports equivalent SNPNs and the UE indicates that ME supports SOR-SNPN-SI; or that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI, if the AMF serving the UE is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports equivalent SNPNs and the UE does not indicate that ME supports SOR-SNPN-SI.

[0093] Figure 4 is a flowchart illustrating a method for control plane based steering of roaming in a communications network, the method performed by a Unified Data Management (UDM) 112.

[0094] In step S-401 , the UDM may determine that ME of the UE in an SNPN supports SOR-SNPN- SI based on an indication received from the AMF.

[0095] In step S-402, the UDM may receive from the AMF an indication that the UE supporting equivalent SNPNs is in a non-subscribed SNPN and the subscribed SNPN is an equivalent SNPN, if the AMF is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN and the UE supports equivalent SNPNs; and / or if the UE indicates that ME supports SOR-SNPN-SI, receiving from the AMF at the UDM an indication that ME supports SOR- SNPN-SI.

[0096] In some embodiments, the UDM may determine that the ME of the UE in an SNPN supports SOR-SNPN-SI if: the UE is in the subscribed SNPN, and the AMF indicates to the UDM that ME supports SOR-SNPN-SI; the UE is in a non-subscribed SNPN and the AMF does not indicate to the UDM that the UE supporting equivalent SNPNs is in a non-subscribed SNPN and the subscribed SNPN is an equivalent SNPN; or the UE is in a non-subscribed SNPN, the AMF indicates that the UE supporting equivalent SNPNs is in a non-subscribed SNPN and the subscribed SNPN is an equivalent SNPN, and the AMF indicates to the UDM that the ME supports SOR-SNPN-SI.

[0097] In step S-403, the UDM may receive from the AMF an indication that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI if the AMF is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports equivalent SNPNs and the UE does not indicate that ME supports SOR-SNPN-SI in 5GMM capability IE of REGISTRATION REQUEST.

[0098] In some embodiments, the UDM may determine that ME of the UE in an SNPN supports SOR-SNPN-SI if: the UE is in the subscribed SNPN, and the AMF indicates to the UDM that ME supports SOR-SNPN-SI; or the UE is in a non-subscribed SNPN and the AMF does not indicate to the UDM that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI.

[0099] In step S-404, the UDM may receive from the AMF: that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME supports SOR-SNPN-SI, if the AMF serving the UE is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports equivalent SNPNs and the UE indicates that ME supports SOR-SNPN-SI; or that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI, if the AMF serving the UE is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports equivalent SNPNs and the UE does not indicate that ME supports SOR-SNPN-SI.

[0100] In some embodiments, the UDM may determine that ME of the UE in an SNPN supports SOR-SNPN-SI if: the UE is in the subscribed SNPN, and the AMF indicates to the UDM that ME supports SOR-SNPN-SI; the UE is in a non-subscribed SNPN and the AMF does not indicate to the UDM that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME supports SOR-SNPN-SI, or that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI; or the UE is in a nonsubscribed SNPN and the AMF indicates to the UDM that the UE supporting equivalent SNPNs is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME supports SOR-SNPN-SI.

[0101] Figure 5 is a block diagram illustrating elements of a mobile network node 500 of a mobile communications network. In some embodiments, the mobile network node 500 is an AMF 106. As shown, the mobile network node may include network interface circuitry 501 (also referred to as a network interface) configured to provide communications with other nodes of the core network and / or the network. The mobile network node may also include a processing circuitry 502 (also referred to as a processor) coupled to the network interface circuitry, and memory circuitry 503 (also referred to as memory) coupled to the processing circuitry. The memory circuitry 503 may include computer readable program code that when executed by the processing circuitry 502 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 502 may be defined to include memory so that a separate memory circuitry is not required. As discussed herein, operations of the mobile network node may be performed by processing circuitry 502 and / or network interface circuitry 501 . For example, processing circuitry 502 may control network interface circuitry 501 to transmit communications through network interface circuitry 501 to one or more other network nodes and / or to receive communications through network interface circuitry from one or more other network nodes. Moreover, modules may be stored in memory 503, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 502, processing circuitry 502 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to core network nodes).

[0102] Figure 6 is a block diagram illustrating elements of a mobile network node 600 of a mobile communications network. In some embodiments, the mobile network node 600 is a UDM 112. As shown, the mobile network node may include network interface circuitry 601 (also referred to as a network interface) configured to provide communications with other nodes of the core network and / or the network. The mobile network node may also include a processing circuitry 602 (also referred to as a processor) coupled to the network interface circuitry, and memory circuitry 603 (also referred to as memory) coupled to the processing circuitry. The memory circuitry 603 may include computer readable program code that when executed by the processing circuitry 602 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 602 may be defined to include memory so that a separate memory circuitry is not required. As discussed herein, operations of the mobile network node may be performed by processing circuitry 602 and / or network interface circuitry 601 . For example, processing circuitry 602 may control network interface circuitry 601 to transmit communications through network interface circuitry 601 to one or more other network nodes and / or to receive communications through network interface circuitry from one or more other network nodes. Moreover, modules may be stored in memory 603, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 602, processing circuitry 602 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to core network nodes).

[0103] Figure 7 is a block diagram illustrating a virtualization environment 700 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 700 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 700 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0104] Applications 702 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0105] Hardware 704 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 706 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 708a and 708b (one or more of which may be generally referred to as VMs 708), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 706 may present a virtual operating platform that appears like networking hardware to the VMs 708.

[0106] The VMs 708 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 706. Different embodiments of the instance of a virtual appliance 702 may be implemented on one or more of VMs 708, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment. In the context of NFV, a VM 708 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 708, and that part of hardware 704 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 708 on top of the hardware 704 and corresponds to the application 702.

[0107] Hardware 704 may be implemented in a standalone network node with generic or specific components. Hardware 704 may implement some functions via virtualization. Alternatively, hardware 704 may 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 710, which, among others, oversees lifecycle management of applications 702. In some embodiments, hardware 704 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may 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 with the use of a control system 712 which may alternatively be used for communication between hardware nodes and radio units.

[0108] Embodiments within the scope of the present invention may also include computer-readable media for carrying or having computer-executable instructions or data structures stored thereon. 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 tangible 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 the tangible computer-readable media. Computer-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Computer-executable instructions also include program modules that are executed by computers in standalone or network environments. Generally, 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 represent examples of corresponding acts for implementing the functions described in such steps.

[0109] Those of skill in the art will appreciate that other embodiments of the invention may be practiced in network computing environments with many types of computer system configurations, including personal computers, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. Embodiments may 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 by a combination thereof) through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

[0110] Communication at various stages of the described system can be performed through a local area network, a token ring network, the Internet, a corporate intranet, 802.11 series wireless signals, fiber-optic network, radio or microwave transmission, etc. Although the underlying communication technology may change, the fundamental principles described herein are still applicable.

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

[0112] 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 "includes," "including," "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, or components, and combinations thereof. Further, all terms used in the claims are to be interpreted according to their ordinary meaning in the technical field, unless explicitly defined otherwise herein. All references to ""a / an / the element, apparatus, component, means, module, step, etc."" are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, module, step, etc., unless explicitly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless explicitly stated.

Claims

CLAIMS1 . A method for control plane based steering of roaming in a communications network, the method comprising: receiving at an Access and Mobility Management Function, AMF, from a User Equipment, UE, comprising a Mobile Equipment, ME, when registering in a non-subscribed standalone non-public network, SNPN, a first indication that the ME supports or does not support Steering of Roaming SNPN Selection Information, SOR-SNPN-SI; transmitting from the AMF to a Unified Data Management, UDM, a second indication that the ME supports or does not support SOR-SNPN-SI; and storing or deleting at the UDM an indicator of ME support of SOR-SNPN-SI based on the second indication.

2. The method according to claim 1 , wherein the UDM stores an "ME support of SOR- SNPN-SI" indicator if the ME of the UE supports SOR-SNPN-SI.

3. The method according to claim 1 , wherein the UDM deletes a stored "ME support of SOR- SNPN-SI" indicator if the ME of the UE does not support SOR-SNPN-SI.

4. The method according to any one of claims 1 to 3, wherein the first indication is received from the UE at the AMF when the UE supports equivalent SNPNs and access to an SNPN using credentials from a credentials holder.

5. The method according to any one of claims 1 to 4, wherein the second indication indicates that the UE supports equivalent SNPNs, the UE is in an equivalent SNPN of the subscribed SNPN, and the ME does not support SOR-SNPN-SI if the AMF is in a equivalent SNPN of the subscribed SNPN, the UE supports equivalent SNPNs and the UE does not indicate that ME supports SOR-SNPN-SI.

6. The method according to any one of claims 1 to 5, wherein the first indication is included in a 5GMM capability IE of the registration request.

7. A method for control plane based steering of roaming in a communications network, the method performed by an Access and Mobility Management Function, AMF, the method comprising:receiving at the AMF from a User Equipment, UE, comprising a Mobile Equipment, ME, when registering in a non-subscribed standalone non-public network, SNPN, a first indication that the ME supports or does not support Steering of Roaming SNPN Selection Information, SOR-SNPN-SI; and transmitting from the AMF to a Unified Data Management, UDM, a second indication that the ME supports or does not support SOR-SNPN-SI.

8. The method according to claim 7, wherein the first indication is received from the UE at the AMF when the UE supports equivalent SNPNs and access to an SNPN using credentials from a credentials holder.

9. The method according to any one of claims 7 to 8, wherein the second indication indicates that the UE supports equivalent SNPNs, the UE is in an equivalent SNPN of the subscribed SNPN, and the ME does not support SOR-SNPN-SI if the AMF is in a equivalent SNPN of the subscribed SNPN, the UE supports equivalent SNPNs and the UE does not indicate that ME supports SOR-SNPN-SI.

10. The method according to any one of claims 7 to 9, wherein the first indication is included in a 5GMM capability IE of the registration request.11 . A method for control plane based steering of roaming in a communications network, the method performed by a Unified Data Management, UDM, the method comprising: receiving at the UDM from an Access and Mobility Management Function, AMF, a second indication that a Mobile Equipment, ME, supports or does not support Steering of Roaming SNPN Selection Information, SOR-SNPN-SI, when a User Equipment, UE, comprising the ME registers in a non-subscribed standalone non-public network, SNPN; and storing or deleting at the UDM an indicator of ME support of SOR-SNPN-SI based on the second indication.

12. The method according to claim 11 , wherein the UDM stores an "ME support of SOR- SNPN-SI" indicator if the ME of the UE supports SOR-SNPN-SI.

13. The method according to claim 11 , wherein the UDM deletes a stored "ME support of SOR-SNPN-SI" indicator if the ME of the UE does not support SOR-SNPN-SI.

14. The method according to any one of claims 11 to 13, wherein the UE supports equivalent SNPNs and access to an SNPN using credentials from a credentials holder.

15. The method according to any one of claims 11 to 14, wherein the second indication indicates that the UE supports equivalent SNPNs, the UE is in an equivalent SNPN of the subscribed SNPN, and the ME does not support SOR-SNPN-SI if the AMF is in a equivalent SNPN of the subscribed SNPN, the UE supports equivalent SNPNs and the UE does not indicate that ME supports SOR-SNPN-SI.

16. Apparatus for control plane based steering of roaming in a communications network, the apparatus comprising a processor and a memory, the memory containing instructions executable by the processor such that the apparatus is operable to: receive from a User Equipment, UE, comprising a Mobile Equipment, ME, when registering in a non-subscribed standalone non-public network, SNPN, a first indication that the ME supports or does not support Steering of Roaming SNPN Selection Information, SOR-SNPN-SI; transmit to a Unified Data Management, UDM, a second indication that the ME supports or does not support SOR-SNPN-SI.

17. The apparatus according to claim 16 further operable to perform the method of any one of claims 8 to 10.

18. Apparatus for control plane based steering of roaming in a communications network, the apparatus comprising a processor and a memory, the memory containing instructions executable by the processor such that the apparatus is operable to: receive from an Access and Mobility Management Function, AMF, a second indication that a Mobile Equipment, ME, supports or does not support SOR-SNPN-SI when a User Equipment, UE, comprising the ME registers in a non-subscribed standalone nonpublic network, SNPN; and store or delete an indicator of ME support of SOR-SNPN-SI based on the second indication.

19. The apparatus according to claim 18 further operable to perform the method of any one of claims 12 to 15.

20. A system comprising an apparatus as defined in claim 16, and an apparatus as defined in claim 18.21 . 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 one of claims from 7 to 10 and from 11 to 15.

22. A computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to perform a method according to any one of claims from 7 to 10 and from 11 to 15.

23. A computer program product, embodied on a non-transitory machine-readable medium, comprising instructions which are executable by a processor, causing the processor to perform the method according to any one of claims from 7 to 10 and from 11 to 15.

Images