Control plane-based roaming guidance and equivalent independent non-public network

Abstract

A method for control plane based roaming booting in a communication network, the method comprising: receiving, at an access and mobility management function (AMF) from a user equipment (UE) comprising a mobile equipment (ME), a first indication that the ME supports or does not support roaming booting SNPN selection information SOR-SNPN-SI when registering in a non-subscribing independent non-public network, SNPN; transmitting, from the AMF to a Uniform Data Management (UDM), a second indication that the ME supports or does not support SOR-SNPN-SI; and based on the second indication, storing or deleting, at the UDM, an indicator that the ME supports SOR-SNPN-SI. In some embodiments, if the ME of the UE supports SOR-SNPN-SI, then the UDM stores an indicator of "ME support of SOR-SNPN-SI". In some embodiments, if the ME of the UE does not support the SOR-SNPN-SI, then the UDM deletes a stored "ME support of SOR-SNPN-SI" indicator.

Description

Technical Field

[0001] This invention generally relates to a standalone non-public network (SNPN) in a 3GPP mobile network, and more specifically, to the ability of a user equipment to determine roaming guidance and roaming guidance SNPN selection information (SOR-SNPN-SI) based on the control plane. Background Technology

[0002] In the 3GPP specifications, a Standalone Non-Public Network (SNPN) is a network type (communication network, mobile network, or cellular network) that provides network services to a limited, designated set of User Equipments (UEs) and is independent of public networks. UEs primarily operate only within their subscribed SNPN. However, UEs supporting access to an SNPN using certificates from a certificate holder can register in a non-subscribed SNPN, and the subscribed SNPN or HPLMN can use control plane-based roaming guidance and roaming guidance SNPN selection information (SOR-SNPN-SI) to control which non-subscribed SNPN the UE selects. UEs supporting access to an SNPN using certificates from a certificate holder should support control plane-based roaming guidance and SOR-SNPN-SI.

[0003] In order for Unified Data Management (UDM) to distinguish between (a) UEs that support access to the SNPN using certificates from the certificate holder (to which control plane-based roaming guidance with SOR-SNPN-SI can be performed) and (b) UEs that do not support access to the SNPN using certificates from the certificate holder and the UE (to which control plane-based roaming guidance with SOR-SNPN-SI cannot be performed), when a UE registers in the subscribed SNPN, the UE indicates in the 5GMM Capability Information Element (IE) of the registration request that the UE's ME supports SOR-SNPN-SI.

[0004] In a non-subscribed SNPN, the ME does not need to support the SOR-SNPN-SI instruction because only UEs that support accessing the SNPN using certificates from the certificate holder can choose a non-subscribed SNPN, and therefore the ME of any UE in a non-subscribed SNPN supports SOR-SNPN-SI.

[0005] Therefore, the UDM determines that it is possible to perform control plane-based roaming guidance and SOR-SNPN-SI toward the UE in the SNPN if the following conditions are met: (1) the UE is in a subscribed SNPN and the AMF instructs the ME to support SOR-SNPN-SI to the UDM (the AMF does this when the UE instructs the ME to support SOR-SNPN-SI in the 5GMM capability IE of the registration request); or (2) the UE is in a non-subscribed SNPN.

[0006] If a non-subscribed SNPN is indicated as an equivalent SNPN when the UE has previously registered in one, then a UE that supports the equivalent SNPN but does not support accessing the SNPN using a certificate from a certificate holder can also register in a non-subscribed SNPN. Such a UE does not need to support control plane-based roaming guidance with SOR-SNPN-SI, because the UE can only register in either a subscribed SNPN or a non-subscribed SNPN (which is indicated as an equivalent SNPN when the UE has previously registered in one). The selection of this non-subscribed SNPN is controlled by the network-provided list of equivalent SNPNs (not by SOR-SNPN-SI).

[0007] The problematic aspect is that when the UE is in a non-subscribed SNPN and the subscribed SNPN is an equivalent SNPN, the UDM cannot distinguish between the following cases: (a) the UE supports accessing the SNPN using a certificate from a certificate holder (this UE supports control plane-based roaming guidance and SOR-SNPN-SI, but does not provide an indication of SOR-SNPN-SI support); and (b) the UE supports an equivalent SNPN, but does not support accessing the SNPN using a certificate from a certificate holder. This type of UE does not need to support control plane-based roaming guidance and SOR-SNPN-SI.

[0008] Therefore, when a non-subscribed SNPN is equivalent to a subscribed SNPN, the UDM cannot determine whether it can perform control plane-based roaming guidance with SOR-SNPN-SI for the UE in the non-subscribed SNPN. This uncertainty may lead to inefficient network resource management and performance issues. Summary of the Invention

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

[0010] The purpose of this invention is to enable the UDM to perform control plane-based roaming guidance with SOR-SNPN-SI on the UE in the non-subscribed SNPN when the non-subscribed SNPN is equivalent to the subscribed SNPN.

[0011] This disclosure provides a method for roaming guidance based on the control plane in a communication network. The method includes: receiving, at the Access and Mobility Management Function (AMF), a first indication from a User Equipment (UE) including a Mobile Equipment (ME) indicating whether the ME supports or does not support roaming guidance SNPN selection information (SOR-SNPN-SI); transmitting from the AMF to the Unified Data Management (UDM) a second indication indicating whether the ME supports or does not support SOR-SNPN-SI; and storing or deleting an indication of ME support for SOR-SNPN-SI at the UDM based on the second indication. In some embodiments, if the UE's ME supports SOR-SNPN-SI, the UDM stores the "ME support of SOR-SNPN-SI" indication. In some embodiments, if the UE's ME does not support SOR-SNPN-SI, the UDM deletes the stored "ME support of SOR-SNPN-SI" indication. In some embodiments, when the UE supports an equivalent SNPN and accesses the SNPN using a certificate from a certificate holder, the first indication is received from the UE at the AMF. In some embodiments, if the AMF is in the equivalent SNPN of the subscribed SNPN, the UE supports the equivalent SNPN, and the UE does not indicate that the ME supports SOR-SNPN-SI, then the second indication indicates that the UE supports the equivalent SNPN, the UE is in the equivalent SNPN of the subscribed SNPN, and the ME does not support SOR-SNPN-SI. In some embodiments, the first indication is included in the 5GMM capability IE of the registration request.

[0012] A first aspect of the invention relates to a method for roaming guidance based on the control plane in a communication network, the method being performed by an Access and Mobility Management Function (AMF), the method comprising: upon registration in a non-subscribed Independent Non-Public Network (SNPN), receiving at the AMF a first indication from a User Equipment (UE) including a Mobile Equipment (ME) indicating whether the ME supports or does not support Roaming Guidance SNPN Selection Information (SOR-SNPN-SI); and transmitting from the AMF to a Unified Data Management Device (UDM) a second indication indicating whether the ME supports or does not support SOR-SNPN-SI. In some embodiments, the first indication is received at the AMF from the UE when the UE supports an equivalent SNPN and accesses the SNPN using a certificate from a certificate holder. In some embodiments, if the AMF is in an equivalent SNPN of a subscribed SNPN, the UE supports the equivalent SNPN, and the UE does not indicate that the ME supports SOR-SNPN-SI, then the second indication indicates that the UE supports the equivalent SNPN, the UE is in an equivalent SNPN of the subscribed SNPN, and the ME does not support SOR-SNPN-SI. In some embodiments, the first indication is included in the 5GMM capability IE of the registration request.

[0013] A second aspect of the invention relates to a method for roaming guidance based on the control plane in a communication network, the method being performed by a unified data management (UDM), the method comprising: when a user equipment (UE) including a mobile device (ME) registers in a non-subscription independent non-public network (SNPN), receiving at the UDM a second indication from an access and mobility management function (AMF) whether the ME supports or does not support SOR-SNPN-SI; and based on the second indication, storing or deleting an indication at the UDM that the ME supports SOR-SNPN-SI. In some embodiments, if the ME of the UE supports SOR-SNPN-SI, the UDM stores the “ME support of SOR-SNPN-SI” indication. In some embodiments, if the ME of the UE does not support SOR-SNPN-SI, the UDM deletes the stored “ME support of SOR-SNPN-SI” indication. In some embodiments, the UE supports an equivalent SNPN and accesses the SNPN using a certificate from a certificate holder. In some embodiments, if the AMF is in the equivalent SNPN of the subscribed SNPN, the UE supports the equivalent SNPN, and the UE does not indicate that the ME supports SOR-SNPN-SI, then the second indication indicates that the UE supports the equivalent SNPN, the UE is in the equivalent SNPN of the subscribed SNPN, and the ME does not support SOR-SNPN-SI.

[0014] Advantageously, when a non-subscribed SNPN is equivalent to a subscribed SNPN, it enables the UDM to know whether the UDM can perform control plane-based roaming guidance with SOR-SNPN-SI for the UE in the non-subscribed SNPN. Attached Figure Description

[0015] To best describe the ways in which the disclosed concepts can be implemented, and to define other objects, advantages, and features of this disclosure, a more specific description is provided below, illustrated in the accompanying drawings. It should be understood that these drawings depict only exemplary embodiments of the invention and are therefore not intended to be limiting of the scope; examples will be described and explained with additional features and details using the drawings.

[0016] Figure 1 An example networking system based on a specific embodiment of the solution described herein is shown.

[0017] Figure 2 An example signaling diagram is shown, illustrating the process of a specific embodiment of the solution described herein.

[0018] Figure 3 An example flowchart is shown, illustrating a method performed by a mobile network node according to a specific embodiment of the solution described herein.

[0019] Figure 4 An example flowchart is shown, illustrating a method performed by a mobile network node according to a specific embodiment of the solution described herein.

[0020] Figure 5 An example block diagram of a mobile network node configured according to a specific embodiment of the solution described herein is shown.

[0021] Figure 6 An example block diagram of a mobile network node configured according to a specific embodiment of the solution described herein is shown.

[0022] Figure 7 An example block diagram of a virtualized environment is shown. Detailed Implementation

[0023] The invention will now be described in detail below with reference to the accompanying drawings, which illustrate examples of embodiments or implementations of the invention. However, the invention can 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 the 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 assumed to be present / used in another embodiment. These embodiments of the disclosed subject matter are presented as illustrative examples and should not be construed as limiting the scope of the disclosed subject matter. For example, certain details of the embodiments may be modified, omitted, or extended without departing from the scope of the subject matter.

[0024] The example embodiments described herein appear in the context of telecommunications networks, including but not limited to telecommunications networks that conform to and / or otherwise incorporate aspects of the fifth-generation (5G) architecture. Figure 1 This is an example networking system 100 according to an example embodiment of the present disclosure. Figure 1 Specifically, a User Equipment (UE) 101 is illustrated, which can communicate with a (Radio) Access Network (RAN) 102 and Access and Mobility Management Functions (AMF) 106 and User Plane Functions (UPF) 103. AMF 106 can further communicate with core network services including Session Management Functions (SMF) 107 and Policy Control Functions (PCF) 111. The core network services can also communicate with Application Server / Application Functions (AS / AF) 113. Other networking services 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 Analysis Function (NWDAF) 115, and Data Network (DN) 104. In some example implementations of embodiments of this disclosure, each of the entities in the networking system 100 is considered a Network Function (NF). One or more additional instances of NFs may be incorporated into the networking system.

[0025] The solution described in this paper aims to enable the UDM to perform control plane-based roaming guidance with SOR-SNPN-SI for UEs in a non-subscribed SNPN when the non-subscribed SNPN is equivalent to a subscribed SNPN.

[0026] This disclosure provides a method for roaming guidance based on the control plane in a communication network. The method includes: receiving, at the Access and Mobility Management Function (AMF), a first indication from a User Equipment (UE) including a Mobile Equipment (ME) indicating whether the ME supports or does not support roaming guidance SNPN selection information (SOR-SNPN-SI); transmitting from the AMF to the Unified Data Management (UDM) a second indication indicating whether the ME supports or does not support SOR-SNPN-SI; and storing or deleting an indication of ME support for SOR-SNPN-SI at the UDM based on the second indication. In some embodiments, if the UE's ME supports SOR-SNPN-SI, the UDM stores the "ME support of SOR-SNPN-SI" indication. In some embodiments, if the UE's ME does not support SOR-SNPN-SI, the UDM deletes the stored "ME support of SOR-SNPN-SI" indication. In some embodiments, when the UE supports an equivalent SNPN and accesses the SNPN using a certificate from a certificate holder, the first indication is received from the UE at the AMF. In some embodiments, if the AMF is in the equivalent SNPN of the subscribed SNPN, the UE supports the equivalent SNPN, and the UE does not indicate that the ME supports SOR-SNPN-SI, then the second indication indicates that the UE supports the equivalent SNPN, the UE is in the equivalent SNPN of the subscribed SNPN, and the ME does not support SOR-SNPN-SI. In some embodiments, the first indication is included in the 5GMM capability IE of the registration request.

[0027] A first aspect of the invention relates to a method for roaming guidance based on the control plane in a communication network, the method being performed by an Access and Mobility Management Function (AMF), the method comprising: upon registration in a non-subscription Independent Non-Public Network (SNPN), receiving at the AMF a User Equipment (UE) including a Mobile Equipment (ME) a ​​first indication indicating whether the ME supports or does not support Roaming Guidance SNPN Selection Information (SOR-SNPN-SI); and transmitting from the AMF to a Unified Data Management Device (UDM) a second indication indicating whether the ME supports or does not support SOR-SNPN-SI. In some embodiments, the first indication is received at the AMF from the UE when the UE supports an equivalent SNPN and accesses the SNPN using a certificate from a certificate holder. In some embodiments, if the AMF is in an equivalent SNPN of the subscribed SNPN, the UE supports the equivalent SNPN, and the UE does not indicate that the ME supports SOR-SNPN-SI, then the second indication indicates that the UE supports the equivalent SNPN, the UE is in an equivalent SNPN of the subscribed SNPN, and the ME does not support SOR-SNPN-SI. In some embodiments, the first indication is included in the 5GMM capability IE of the registration request.

[0028] A second aspect of the invention relates to a method for roaming guidance based on the control plane in a communication network, the method being performed by a unified data management (UDM), the method comprising: when a user equipment (UE) including a mobile device (ME) registers in a non-subscription independent non-public network (SNPN), receiving at the UDM a second indication from an access and mobility management function (AMF) whether the ME supports or does not support SOR-SNPN-SI; and based on the second indication, storing or deleting an indication at the UDM that the ME supports SOR-SNPN-SI. In some embodiments, if the ME of the UE supports SOR-SNPN-SI, the UDM stores the “ME support of SOR-SNPN-SI” indication. In some embodiments, if the ME of the UE does not support SOR-SNPN-SI, the UDM deletes the stored “ME support of SOR-SNPN-SI” indication. In some embodiments, the UE supports an equivalent SNPN and accesses the SNPN using a certificate from a certificate holder. In some embodiments, if the AMF is in the equivalent SNPN of the subscribed SNPN, the UE supports the equivalent SNPN, and the UE does not indicate that the ME supports SOR-SNPN-SI, then the second indication indicates that the UE supports the equivalent SNPN, the UE is in the equivalent SNPN of the subscribed SNPN, and the ME does not support SOR-SNPN-SI.

[0029] This disclosure also provides a method for roaming guidance based on the control plane in a communication network, the method comprising: registering a user equipment (UE) in a non-subscription independent non-public network (SNPN); when the UE supports an equivalent SNPN and accesses the SNPN using a certificate from a certificate holder, transmitting from the UE in the 5GMM capability IE of the registration request an indication that the mobile device (ME) supports roaming guidance SNPN selection information (SOR-SNPN-SI) to the Access and Mobility Management Function (AMF); when the UE supports an equivalent SNPN, transmitting from the UE in the 5GMM capability IE of the registration request an indication that the UE supports an equivalent SNPN to the AMF; and based on the indication received from the AMF, determining at the Unified Data Management (UDM) that the UE's ME supports SOR-SNPN-SI in the SNPN. In some embodiments, the method further includes: if the AMF is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the UE supports the equivalent SNPN, then transmitting from the AMF to the UDM an indication that the UE supporting the equivalent SNPN is in a non-subscribed SNPN and the subscribed SNPN is an equivalent SNPN; and / or if the UE indicates that the ME supports SOR-SNPN-SI, then transmitting from the AMF to the UDM an indication that the ME supports SOR-SNPN-SI. In some embodiments, the UDM determines that the ME of the UE in the SNPN supports SOR-SNPN-SI if the following occurs: the UE is in a subscribed SNPN, and the AMF indicates to the UDM that the 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 the equivalent SNPN is in a non-subscribed SNPN, and the subscribed SNPN is the equivalent SNPN; or the UE is in a non-subscribed SNPN, the AMF indicates that the UE supporting the equivalent SNPN is in a non-subscribed SNPN, and the subscribed SNPN is the equivalent SNPN, and the AMF indicates to the UDM that the ME supports SOR-SNPN-SI. In some embodiments, the method further includes transmitting an indication from the AMF to the UDM that if the AMF is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports the equivalent SNPN, and the UE does not indicate in the 5GMM capability IE of the registration request that the ME supports SOR-SNPN-SI, then the AMF transmits the indication that the UE 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 UDM determines that the ME of the UE in the SNPN supports SOR-SNPN-SI if the following occurs: the UE is in a subscribed SNPN and the AMF indicates to the UDM that the 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 supports the equivalent SNPN. The UE is in a non-subscribed SNPN, the subscribed SNPN is the equivalent SNPN, and the ME does not support SOR-SNPN-SI. In some embodiments, the method further includes: transmitting from the UE to the AMF in the 5GMM capability IE of the registration request the following indication: an indication that the ME supports SOR-SNPN-SI, or an indication that the ME does not support SOR-SNPN-SI; and if the AMF of the serving UE is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports the equivalent SNPN, and the UE indicates that the ME supports SOR-SNPN-SI, then transmitting from the AMF to the UDM the indication that the UE supporting the equivalent SNPN is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME supports SOR-SNPN-SI; or if the AMF of the serving UE is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports the equivalent SNPN, and the UE does not indicate that the ME supports SOR-SNPN-SI, then the UE supporting the equivalent SNPN 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 UDM determines that the ME of the UE in the SNPN supports SOR-SNPN-SI if the following occurs: the UE is in a subscribed SNPN, and the AMF indicates to the UDM that the 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 supports the equivalent SNPN is in a non-subscribed SNPN, the subscribed SNPN is the equivalent SNPN, and the ME supports SOR-SNPN-SI; or the UE supports the equivalent SNPN is in a non-subscribed SNPN, the subscribed SNPN is the 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 supports the equivalent SNPN is in a non-subscribed SNPN, the subscribed SNPN is the equivalent SNPN, and the ME supports SOR-SNPN-SI.

[0030] Another aspect of the present invention relates to a method for roaming guidance based on the control plane in a communication network, the method being performed by an Access and Mobility Management Function (AMF), the method comprising: when the UE supports an equivalent SNPN and accesses the SNPN using a certificate from a certificate holder, transmitting at the AMF an indication from the user equipment (UE) in the 5GMM capability IE of the registration request that the mobile device (ME) supports roaming guidance SNPN selection information (SOR-SNPN-SI); and when the UE supports an equivalent SNPN, receiving at the AMF an indication from the UE in the 5GMM capability IE of the registration request that the UE supports an equivalent SNPN. In some embodiments, the method further includes: if the AMF is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the UE supports the equivalent SNPN, then transmitting from the AMF to the Unified Data Management (UDM) an indication that the UE supporting the equivalent SNPN is in a non-subscribed SNPN and the subscribed SNPN is an equivalent SNPN; and / or if the UE instructs the ME to support SOR-SNPN-SI, then transmitting from the AMF to the Unified Data Management (UDM) an indication that the ME supports SOR-SNPN-SI. In some embodiments, the method further includes: if the AMF is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports the equivalent SNPN, and the UE does not instruct the ME to support SOR-SNPN-SI in the 5GMM capability IE of the registration request, then transmitting from the AMF to the UDM an indication that the UE supporting the equivalent SNPN 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 includes: receiving from the UE at the AMF in the 5GMM capability IE of the registration request: an indication that the ME supports SOR-SNPN-SI, or an indication that the ME does not support SOR-SNPN-SI; and if the AMF of the serving UE is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports the equivalent SNPN, and the UE indicates that the ME supports SOR-SNPN-SI, then transmitting from the AMF to the Unified Data Management (UDM) the following: UE supporting equivalent SNPN is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME supports SOR-SNPN-SI; or if the AMF of the serving UE is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports the equivalent SNPN, and the UE does not indicate that the ME supports SOR-SNPN-SI, then UE supporting equivalent SNPN is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI.

[0031] Another aspect of the invention relates to a method for control plane-based roaming guidance in a communication network, the method being performed by a unified data management (UDM), the method comprising: determining at the unified data management (UDM) that the ME of a UE in an SNPN supports SOR-SNPN-SI based on an indication received from an AMF. In some embodiments, the method further comprises: if the AMF is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the UE supports the equivalent SNPN, then receiving from the AMF at the UDM an indication that the UE supporting the equivalent SNPN is in a non-subscribed SNPN and the subscribed SNPN is an equivalent SNPN; and / or if the UE indicates that the ME supports SOR-SNPN-SI, then receiving from the AMF at the UDM an indication that the ME supports SOR-SNPN-SI. In some embodiments, the UDM determines that the ME of the UE in the SNPN supports SOR-SNPN-SI if the following occurs: the UE is in a subscribed SNPN, and the AMF indicates to the UDM that the 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 the equivalent SNPN is in a non-subscribed SNPN, and the subscribed SNPN is the equivalent SNPN; or the UE is in a non-subscribed SNPN, the AMF indicates that the UE supporting the equivalent SNPN is in a non-subscribed SNPN, and the subscribed SNPN is the equivalent SNPN, and the AMF indicates to the UDM that the ME supports SOR-SNPN-SI. In some embodiments, the method further includes receiving from the AMF at the UDM an indication that the UE supports the equivalent SNPN, the SNPN is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports the equivalent SNPN, and the UE does not indicate that the ME supports SOR-SNPN-SI in the 5GMM capability IE of the registration request. In some embodiments, the UDM determines that the UE's ME in the SNPN supports SOR-SNPN-SI if: the UE is in a subscribed SNPN and the AMF indicates to the UDM that the 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 supports the equivalent SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI.In some embodiments, the method further includes receiving from the AMF at the UDM: if the AMF of the serving UE is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports the equivalent SNPN, and the UE instructs the ME to support SOR-SNPN-SI, then the UE supporting the equivalent SNPN is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME supports SOR-SNPN-SI; or if the AMF of the serving UE is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports the equivalent SNPN, and the UE does not instruct the ME to support SOR-SNPN-SI, then the UE supporting the equivalent SNPN 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 UDM determines that the ME of the UE in the SNPN supports SOR-SNPN-SI if the following occurs: the UE is in a subscribed SNPN and the AMF indicates to the UDM that the 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 supports the equivalent SNPN is in a non-subscribed SNPN, the subscribed SNPN is the equivalent SNPN, and the ME supports SOR-SNPN-SI; or the UE supports the equivalent SNPN is in a non-subscribed SNPN, the subscribed SNPN is the 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 supports the equivalent SNPN is in a non-subscribed SNPN, the subscribed SNPN is the equivalent SNPN, and the ME supports SOR-SNPN-SI.

[0032] Advantageously, when a non-subscribed SNPN is equivalent to a subscribed SNPN, it enables the UDM to determine whether the UDM can perform control plane-based roaming guidance with SOR-SNPN-SI for the UE in the non-subscribed SNPN.

[0033] This disclosure also provides mobile network nodes, particularly Access and Mobility Management Functions (AMF) (106, 500) and Unified Data Management (UDM) (112, 600), configured to perform the corresponding methods described herein.

[0034] This disclosure also provides corresponding computer programs and computer program products including code (e.g., in the form of computer programs) that, when run on the processing circuitry of a mobile network node, cause the mobile network node to perform the disclosed methods.

[0035] In the solution disclosed herein, if the UE registers in a non-subscribed SNPN, supports an equivalent SNPN, and supports accessing the SNPN using a certificate from a certificate holder, then the UE instructs the ME to support SOR-SNPN-SI in the 5GMM capability IE of the registration request. This is an extension of the usage of existing instructions for subscribed SNPNs.

[0036] If the serving UE's AMF is in a non-subscribed SNPN, then the subscribed SNPN is the equivalent SNPN, and the UE supports the equivalent SNPN: 1) The AMF indicates to the UDM that the UE supporting the equivalent SNPN is in a non-subscribed SNPN, and the subscribed SNPN is the equivalent SNPN; and 2) If the UE instructs the ME to support SOR-SNPN-SI, the AMF instructs the UDM to instruct the ME to support SOR-SNPN-SI.

[0037] The UDM determines that the UE's ME in the SNPN supports SOR-SNPN-SI if the following occurs: 1) The UE is in the subscribed SNPN, and the AMF instructs the UDM that the ME supports SOR-SNPN-SI; 2) The UE is in a non-subscribed SNPN, and the AMF has not indicated to the UDM that a UE supporting an equivalent SNPN is in a non-subscribed SNPN, and the subscribed SNPN is an equivalent SNPN; or 3) When the UE is in a non-subscribed SNPN, the AMF indicates that the UE supports the equivalent SNPN in the non-subscribed SNPN, and the subscribed SNPN is the equivalent SNPN, and the AMF indicates to the UDM that the ME supports SOR-SNPN-SI.

[0038] Alternatively, if the UE registers in a non-subscribed SNPN, supports an equivalent SNPN, and supports accessing the SNPN using a certificate from a certificate holder, the UE instructs the ME to support SOR-SNPN-SI in the 5GMM capability IE of the registration request. This is an extension of the usage of existing instructions for subscribed SNPNs.

[0039] If the serving UE's AMF is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports the equivalent SNPN, and the UE does not indicate in the 5GMM capability IE of the registration request that the ME supports SOR-SNPN-SI, then the AMF indicates to the UDM that the UE supporting the equivalent SNPN is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI.

[0040] The UDM determines that the UE's ME in the SNPN supports SOR-SNPN-SI if the following occurs: 1) The UE is in the subscribed SNPN, and the AMF instructs the UDM that the ME supports SOR-SNPN-SI; 2) The UE is in a non-subscribed SNPN, and the AMF does not indicate to the UDM that the UE supports the equivalent SNPN. The subscribed SNPN is the equivalent SNPN, and the ME does not support SOR-SNPN-SI.

[0041] Alternatively, if the UE registers in a non-subscribed SNPN, supports an equivalent SNPN, and supports accessing the SNPN using a certificate from a certificate holder, the UE instructs the ME to support SOR-SNPN-SI in the 5GMM capability IE of the registration request. This is an extension of the usage of existing instructions for subscribed SNPNs.

[0042] If the serving UE's AMF is in a non-subscribed SNPN, then the subscribed SNPN is the equivalent SNPN, the UE supports the equivalent SNPN, and a) In the 5GMM capability IE of the registration request, the UE instructs the ME to support SOR-SNPN-SI. The AMF instructs the UDM to support the UE in the non-subscribed SNPN, the subscribed SNPN is the equivalent SNPN, and the ME supports SOR-SNPN-SI.

[0043] b) The UE did not indicate in the 5GMM capability IE of the registration request that the ME support SOR-SNPN-SI, the AMF indicated to the UDM that the UE supports the equivalent SNPN in the non-subscribed SNPN, the subscribed SNPN is the equivalent SNPN, and the ME does not support SOR-SNPN-SI.

[0044] The UDM determines that the UE's ME in the SNPN supports SOR-SNPN-SI if the following occurs: 1) The UE is in the subscribed SNPN, and the AMF instructs the UDM that the ME supports SOR-SNPN-SI; 2) The UE is in a non-subscribed SNPN, and the AMF does not indicate to the UDM that the UE supports the equivalent SNPN. The subscribed SNPN is the equivalent SNPN, and the ME supports SOR-SNPN-SI. Alternatively, the UE supports the equivalent SNPN in a non-subscribed SNPN, the subscribed SNPN is the equivalent SNPN, and the ME does not support SOR-SNPN-SI.

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

[0046] The accompanying drawings, which illustrate an example of an embodiment of the solution, are described in detail below.

[0047] Figure 2 This is a signaling diagram illustrating the roaming guidance process based on the control plane in a communication network. This process is performed by UE101, AMF 106, UDM112, and SOR-AF 113.

[0048] The steps of this process are as follows: In step 1, the UE sends a registration request to the AMF.

[0049] In step 2, the AMF initiates the registration process by sending a Nudm_UECM_Registration request to the UDM. If the NAS registration type is "Initial" or "Urgent," this message includes the removal of the "ME support of SOR-CMCI" indicator. The UDM responds with a Nudm_UECM_Registration response.

[0050] In step 3, the AMF sends a Nudm_SDM_Get request to the UDM. This step involves a decision-making process regarding whether to send SOR (Roaming Guidance) information, whether to request an ACK from the UE, and how to obtain the SOR-SNPN-SI. In step 3b, the UDM transmits an Nsoarf_SoR_Get request to the SOR-AF, and the SOR-AF responds with an Nsoarf_SoR_Get response in step 3c. In step 3d, the UDM secures this information.

[0051] In step 4, UDM sends a Nudm_SDM_Get response back to AMF.

[0052] In step 5, the AMF sends a Nudm_SDM_Subscribe request to the UDM.

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

[0054] In step 7, the UE performs a roaming guidance information security check and completes the registration process.

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

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

[0057] In step 10, the AMF sends a Nudm_SDM_Info request to the UDM, and the UDM then sends an Nsoarf_SoR_Info request to the SOR-AF in step 10a.

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

[0059] When the AMF is located in a non-subscribed SNPN and the UDM is located in an HPLMN or a subscribed SNPN, the procedures disclosed herein include the following.

[0060] In step 1, the UE initiates an initial registration, emergency registration, or registration process for mobility and periodic registration updates to the AMF by sending a registration request message with a 5GS registration type IE indicating "Initial Registration," "Emergency Registration," or "Mobility Registration Update." If the UE supports accessing the SNPN using a certificate from the certificate holder and an equivalent SNPN, the UE should indicate ME support for SOR-SNPN-SI in its 5GMM capabilities.

[0061] In step 2, upon receiving a registration request message, the AMF executes the registration process. As part of the registration process: a) The AMF uses Nudm_UECM_Registration to provide the registration type to the UDM; and b) If necessary, the AMF indicates to the UDM that the UE supporting the equivalent SNPN is in the non-subscribed SNPN, and the subscribed SNPN is the equivalent SNPN; c) If necessary, the AMF notifies the UDM whether the ME supports SOR-SNPN-SI.

[0062] Therefore, if the 5GS registration type message indicates "initial registration" or "emergency registration", the UDM should use the Nudr_DM_Update service operation to delete the "ME support of SOR-CMCI" indicator (if any) and the "ME support of SOR-SNPN-SI-LS" indicator (if any) stored in the UDR.

[0063] UDM should store or delete the “ME support of SOR-SNPN-SI” indicator.

[0064] The Nudr_DM_Update service operation corresponds to the Nudr_DR_Update service operation.

[0065] If the UE supports accessing the SNPN using a certificate from a certificate holder, the UE should indicate ME's support for SOR-SNPN-SI in the 5GMM capabilities when registering in the following: a) Subscribed SNPN; or b) Non-subscribed SNPN, if the UE supports an equivalent SNPN.

[0066] when: a) The UE indicates ME support for SOR-SNPN-SI in the 5GMM capabilities during initial or emergency registration; or b) ME's support for SOR-SNPN-SI changed in the mobile registration update. And AMF: a) In the subscribed SNPN; or b) In a non-subscribed SNPN, the UE's subscribed SNPN is an equivalent SNPN, and the UE supports the equivalent SNPN; Then the AMF should notify the UDM in Nudm_UECM_Registration whether the ME supports SOR-SNPN-SI.

[0067] If the AMF of the serving UE is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the UE supports the equivalent SNPN, then the AMF indicates to the UDM in Nudm_UECM_Registration that the UE supporting the equivalent SNPN is in a non-subscribed SNPN, and the subscribed SNPN is an equivalent SNPN.

[0068] If the following occurs, the UDM should determine that the UE's ME in the SNPN supports SOR-SNPN-SI: 1) The UE is in the subscribed SNPN, and the AMF instructs the UDM that the ME supports SOR-SNPN-SI; 2) The UE is in a non-subscribed SNPN, and the AMF has not indicated to the UDM that a UE supporting an equivalent SNPN is in a non-subscribed SNPN, and the subscribed SNPN is an equivalent SNPN; or 3) When the UE is in a non-subscribed SNPN, the AMF indicates that the UE supports the equivalent SNPN in the non-subscribed SNPN, and the subscribed SNPN is the equivalent SNPN, and the AMF indicates to the UDM that the ME supports SOR-SNPN-SI.

[0069] When processing the Nudm_UECM_Registration of a UE in the SNPN, if the UDM determines that the ME of the UE in the SNPN supports SOR-SNPN-SI, the UDM should store the “ME support of SOR-SNPN-SI” indicator; otherwise, the UDM should delete the stored “ME support of SOR-SNPN-SI” indicator (if any).

[0070] Instead of indicating “the UE supporting the equivalent SNPN is in a non-subscribed SNPN and the subscribed SNPN is the equivalent SNPN” and “ME supports SOR-SNPN-SI”, AMF may indicate in the condition indicated in Alternate 2 “the UE supporting the equivalent SNPN is in a non-subscribed SNPN, the subscribed SNPN is the equivalent SNPN, and ME does not support SOR-SNPN-SI”, and UDM will use it in accordance with the disclosure herein.

[0071] Instead of indicating "UEs supporting equivalent SNPNs are in non-subscribed SNPNs and subscribed SNPNs are equivalent SNPNs" and "MEs support SOR-SNPN-SI" in two separate instructions, the AMF can include a single instruction to indicate: a) "UEs supporting equivalent SNPNs have non-subscribed SNPNs, subscribed SNPNs are equivalent SNPNs, and the UE supports SOR-SNPN-SI", or b) "UEs that support equivalent SNPNs are in non-subscribed SNPNs, subscribed SNPNs are equivalent SNPNs, and MEs do not support SOR-SNPN-SI."

[0072] The following section provides a detailed description of an example flowchart illustrating an embodiment of the solution.

[0073] Figure 3 This is a flowchart illustrating a method for roaming guidance based on the control plane in a communication network, which is performed by the Access and Mobility Management Function (AMF) 106.

[0074] In step S-301, when the user equipment (UE) supports the equivalent SNPN and accesses the SNPN using a certificate from the certificate holder, the AMF can receive an indication from the UE in the 5GMM capability IE of the registration request that the mobile device (ME) supports roaming-guided SNPN selection information (SOR-SNPN-SI).

[0075] In step S-302, when the UE supports the equivalent SNPN, the AMF can receive an indication from the UE that the UE supports the equivalent SNPN from the 5GMM capability IE in the registration request.

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

[0077] In step S-304, if the AMF is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports the equivalent SNPN, and the UE does not indicate in the 5GMM capability IE of the registration request that the ME supports SOR-SNPN-SI, then the AMF can transmit to the UDM an indication that the UE supports the equivalent SNPN in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI.

[0078] In step S-305, the AMF can receive an indication from the UE in the 5GMM capability IE of the registration request that the ME supports SOR-SNPN-SI, or an indication that the ME does not support SOR-SNPN-SI.

[0079] In step S-306, the AMF can transmit to the Unified Data Management (UDM) the following: if the AMF of the serving UE is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports the equivalent SNPN, and the UE instructs the ME to support SOR-SNPN-SI, then the UE supporting the equivalent SNPN is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME supports SOR-SNPN-SI; or if the AMF of the serving UE is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports the equivalent SNPN, and the UE does not instruct the ME to support SOR-SNPN-SI, then the UE supporting the equivalent SNPN is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI.

[0080] Figure 4 This is a flowchart illustrating a method for roaming guidance based on the control plane in a communication network, which is performed by Unified Data Management (UDM) 112.

[0081] In step S-401, the UDM can determine the ME support of the UE in the SNPN for SOR-SNPN-SI based on the indication received from the AMF.

[0082] In step S-402, if the AMF is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the UE supports the equivalent SNPN, then the UDM can receive from the AMF an indication that the UE supports the equivalent SNPN in a non-subscribed SNPN and the subscribed SNPN is an equivalent SNPN; and / or if the UE indicates that the ME supports SOR-SNPN-SI, then the UDM receives from the AMF an indication that the ME supports SOR-SNPN-SI.

[0083] In some embodiments, if: the UE is in a subscribed SNPN, and the AMF indicates to the UDM that the 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 supports the equivalent SNPN is in a non-subscribed SNPN, and the subscribed SNPN is the equivalent SNPN; or the UE is in a non-subscribed SNPN, the AMF indicates that the UE supports the equivalent SNPN is in a non-subscribed SNPN, and the subscribed SNPN is the equivalent SNPN, and the AMF indicates to the UDM that the ME supports SOR-SNPN-SI, then the UDM can determine that the ME of the UE in the SNPN supports SOR-SNPN-SI.

[0084] In step S-403, if the AMF is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports the equivalent SNPN, and the UE does not indicate in the 5GMM capability IE of the registration request that the ME supports SOR-SNPN-SI, then the UDM can receive from the AMF an indication that the UE supports the equivalent SNPN in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI.

[0085] In some embodiments, if: the UE is in a subscribed SNPN, and the AMF indicates to the UDM that the 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 supports the equivalent SNPN, the subscribed SNPN is the equivalent SNPN, and the ME does not support SOR-SNPN-SI, then the UDM can determine that the ME of the UE in the SNPN supports SOR-SNPN-SI.

[0086] In step S-404, the UDM can receive from the AMF: if the AMF of the serving UE is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports the equivalent SNPN, and the UE instructs the ME to support SOR-SNPN-SI, then the UE supporting the equivalent SNPN is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME supports SOR-SNPN-SI; or if the AMF of the serving UE is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, the UE supports the equivalent SNPN, and the UE does not instruct the ME to support SOR-SNPN-SI, then the UE supporting the equivalent SNPN is in a non-subscribed SNPN, the subscribed SNPN is an equivalent SNPN, and the ME does not support SOR-SNPN-SI.

[0087] In some embodiments, if: the UE is in a subscribed SNPN, and the AMF indicates to the UDM that the 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 the equivalent SNPN is in a non-subscribed SNPN, the subscribed SNPN is the equivalent SNPN, and the ME supports SOR-SNPN-SI; or the UE supporting the equivalent SNPN is in a non-subscribed SNPN, the subscribed SNPN is the 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 the equivalent SNPN is in a non-subscribed SNPN, the subscribed SNPN is the equivalent SNPN, and the ME supports SOR-SNPN-SI, then the UDM can determine that the ME of the UE in the SNPN supports SOR-SNPN-SI.

[0088] Figure 5This is a block diagram illustrating the elements of a mobile network node 500 in a mobile communication 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 communication with the core network and / or other nodes of the network. The mobile network node may 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 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, the processing circuitry 502 may be defined to include memory, such that a separate memory circuitry is not required. As discussed herein, the operation of the mobile network node may be performed by the processing circuitry 502 and / or the network interface circuitry 501. For example, the processing circuitry 502 may control the network interface circuitry 501 to transmit communication to one or more other network nodes and / or receive communication from one or more other network nodes via the network interface circuitry. Furthermore, modules can be stored in memory 503, and these modules can provide instructions such that when the instructions of the modules are executed by processing circuit 502, processing circuit 502 performs corresponding operations (e.g., operations discussed below with respect to example embodiments involving core network nodes).

[0089] Figure 6This is a block diagram illustrating the elements of a mobile network node 600 in a mobile communication 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 communication with the core network and / or other nodes of the network. The mobile network node may 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 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, the processing circuitry 602 may be defined to include memory, such that a separate memory circuitry is not required. As discussed herein, the operation of the mobile network node may be performed by the processing circuitry 602 and / or the network interface circuitry 601. For example, the processing circuitry 602 may control the network interface circuitry 601 to transmit communication to one or more other network nodes and / or receive communication from one or more other network nodes via the network interface circuitry. Furthermore, modules can be stored in memory 603, and these modules can provide instructions such that when the instructions of the modules are executed by processing circuit 602, processing circuit 602 performs corresponding operations (e.g., operations discussed below with respect to example embodiments involving core network nodes).

[0090] Figure 7 This is a block diagram illustrating a virtualization environment 700 in which functionality implemented by some embodiments can be virtualized. In this context, virtualization means creating a virtual version of a device or apparatus, which may include a virtualized hardware platform, storage devices, and networking resources. As used herein, virtualization can be applied to any apparatus or component thereof described herein and involves at least a portion of its functionality being implemented as one or more virtual components. Some or all of the functionality described herein can 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 hardware nodes, which are hardware computing devices such as network nodes, UEs, core network nodes, or hosts. Furthermore, in embodiments where virtual nodes do not require radio connectivity (e.g., core network nodes or hosts), the nodes can be virtualized entirely. In some embodiments, the virtualization environment 700 includes components defined by the O-RAN Alliance, such as an O-cloud environment orchestrated via an O-2 interface by a service management and orchestration framework.

[0091] Application 702 (which may alternatively be referred to as a software instance, virtual device, network function, virtual node, virtual network function, etc.) runs in virtualization environment 700 to implement some of the features, functions, and / or benefits of some embodiments disclosed herein.

[0092] Hardware 704 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices as described herein, such as network interfaces, input / output interfaces, etc. The software can 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 collectively referred to as VM 708), and / or perform any functions, features, and / or benefits described with respect to some embodiments described herein. Virtualization layer 706 can present a virtual operating platform to VM 708 that appears to be networked hardware.

[0093] VM 708 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage devices, and can be operated by a corresponding virtualization layer 706. Different embodiments of instances of virtual devices 702 can be implemented on one or more VMs 708, and the implementations can be performed in different ways. Hardware virtualization is referred to in some contexts as Network Functions Virtualization (NFV). NFV can be used to integrate many types of network devices onto industry-standard high-capacity server hardware, physical switches, and physical storage devices, which can reside in data centers and customer premises.

[0094] In the context of NFV, VM 708 can be a software implementation of the physical machine running the program as if it were running on a physical, non-virtualized machine. Each of the VM 708 and the portion of the hardware 704 that executes that VM (whether dedicated to that VM or shared by that VM with other VMs) form a separate virtual network element. Still within the context of NFV, the virtual network function is responsible for handling specific network functions running on one or more VMs 708 above the hardware 704 and corresponds to application 702.

[0095] Hardware 704 can be implemented in a standalone network node with general-purpose or special-purpose components. Hardware 704 can implement some functions via virtualization. Alternatively, hardware 704 can be part of a larger hardware cluster (e.g., in a data center or CPE), where many hardware nodes work together and are managed via management and orchestration 710, which, among other operations, oversees the lifecycle management of application 702. In some embodiments, hardware 704 is coupled to one or more radio units, each comprising 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 suitable network interfaces and can be used in conjunction with virtual components to provide a radio-capable virtual node, such as a radio access node or base station. In some embodiments, some signaling can be provided using control system 712, which can alternatively be used for communication between hardware nodes and radio units.

[0096] Embodiments within the scope of this invention may also include computer-readable media for carrying or storing computer-executable instructions or data structures thereon. Such a computer-readable medium can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, such tangible computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to carry or store desired program code components in the form of computer-executable instructions or data structures. When information is transmitted or provided to a computer via a network or another communication connection (hardwired, wireless, or a combination thereof), the computer appropriately considers that connection as a computer-readable medium. Therefore, any such connection is properly referred to as a computer-readable medium. Combinations of the foregoing should also be included within the scope of tangible computer-readable media.

[0097] Computer-executable instructions include, for example, instructions and data that cause a general-purpose computer, a special-purpose computer, or a special-purpose processing device to perform a particular function or group of functions. Computer-executable instructions also include program modules that are executed by a computer in a standalone or networked environment. Typically, program modules include routines, programs, objects, components, and data structures that perform a particular task or implement a particular abstract data type. Computer-executable instructions, associated data structures, and program modules represent examples of program code components used to perform steps of the methods disclosed herein. A particular sequence of such executable instructions or associated data structures represents examples of corresponding actions used to implement the functions described in these steps.

[0098] Those skilled in the art will understand that other embodiments of the invention can be practiced in networked computing environments with many types of computer system configurations, including personal computers, handheld devices, multiprocessor systems, microprocessor-based or programmable consumer electronics devices, network PCs, minicomputers, mainframes, etc. Embodiments can also be practiced in distributed computing environments, where tasks are performed by local and remote processing devices linked via a communication network (via hardwired links, wireless links, or combinations thereof). In a distributed computing environment, program modules can reside in local and remote memory storage devices.

[0099] Communication at each stage of the system can be performed via local area networks, token ring networks, the Internet, corporate intranets, 802.11 series wireless signals, fiber optic networks, radio or microwave transmissions, etc. Although potential communication technologies may change, the basic principles described herein remain applicable.

[0100] The various embodiments described above are provided for illustrative purposes only and should not be construed as limiting the invention. For example, the principles herein can be applied to any remote control device. Furthermore, those skilled in the art will recognize that communication between the remote device and the control device is not limited to communication over a local area network, but may include communication over an infrared channel, Bluetooth, or any other suitable communication interface. Those skilled in the art will readily recognize that various modifications and changes can be made to the invention without following the exemplary embodiments and applications shown and described herein, and without departing from the scope of this disclosure.

[0101] The terminology used herein is for the purpose of describing various embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a” (a, an) and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It will also be understood that the terms “include” and “including” and “comprise” (and “comprising”) as used in this specification designate the presence of the stated feature, integer, step, operation, element, or component, or combination thereof, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, or components, or combinations thereof. Furthermore, all terms used in the claims will be interpreted according to their ordinary meaning in the art, unless otherwise expressly defined herein. Unless otherwise expressly stated, all references to “a / the element, device, component, part, module, step, etc.” should be openly interpreted as referring to at least one instance of an element, device, component, part, module, step, etc. Unless expressly stated otherwise, the steps of any method disclosed herein are not necessarily performed in the exact order disclosed.

Claims

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

2. The method of 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 of 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 of any one of claims 1 to 3, wherein, The first indication is received at the AMF from the UE when the UE supports equivalent SNPN and accesses a SNPN using a credential from a credential holder.

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

6. The method of 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 roaming guidance in a communication 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, a first indication that the ME does or does not support roaming guidance SNPN selection information, SOR-SNPN-SI, when registering in a non-subscribed standalone non-public network, SNPN; and transmitting, from the AMF, to a Unified Data Management, UDM, a second indication that the ME does or does not support SOR-SNPN-SI.

8. The method of claim 7, wherein, The first indication is received at the AMF from the UE when the UE supports equivalent SNPN and accesses a SNPN using a credential from a credential holder.

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

10. The method of 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 roaming guidance in a communication network, the method being performed by a unified data management, UDM, the method comprising: receiving, at the UDM, a second indication that a mobile equipment, ME, of a user equipment, UE, supports or does not support roaming guidance SNPN selection information, SOR-SNPN-SI, from an access and mobility management function, AMF, when the UE is registered in a non-subscribed standalone non-public network, SNPN; and storing or deleting, at the UDM, an indicator that the ME supports SOR-SNPN-SI based on the second indication.

12. The method of claim 11, wherein, storing an "ME support of SOR-SNPN-SI” indicator by the UDM if the ME of the UE supports SOR-SNPN-SI.

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

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

15. The method of 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 a subscribed SNPN, and the ME does not support SOR-SNPN-SI if the AMF is in an equivalent SNPN of a subscribed SNPN, the UE supports equivalent SNPNs, and the UE does not indicate that the ME supports SOR-SNPN-SI.

16. An apparatus for control plane based roaming guidance in a communication 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 a first indication that a mobile equipment, ME, of a user equipment, UE, supports or does not support roaming guidance SNPN selection information, SOR-SNPN-SI, from the UE when registered in a non-subscribed standalone non-public network, SNPN; transmit a second indication that the ME supports or does not support SOR-SNPN-SI to a unified data management, UDM.

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

18. An apparatus for control plane based roaming guidance in a communication 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 a second indication that a mobile equipment, ME, of a user equipment, UE, supports or does not support SOR-SNPN-SI from an access and mobility management function, AMF, when the UE is registered in a non-subscribed standalone non-public network, SNPN; and store or delete an indicator that the ME supports SOR-SNPN-SI based on the second indication.

19. The apparatus of 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 the method of any one of claims 7-10 and 11-15.

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

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

Images