Managing vplmn configuration update in ue due to home plmn configuration change

Abstract

Methods and apparatus, including computer program products, are provided for managing configuration updates. In some example embodiments, an apparatus can be provided that includes at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to receive an indication as to whether a home network changed previous configuration information for the apparatus; and delete the previous configuration information stored at the apparatus when the received indication indicates that the change was made. Related systems, methods, and articles are also described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of and priority to U.S. Provisional Application No. 62 / 674,465, filed May 21, 2018, entitled “Managing VPLMN Configuration Updates in the UE Due to Home PLMN Configuration Changes,” the entire contents of which are hereby incorporated by reference herein for all purposes. Technical Field

[0003] The subject matter described herein relates to wireless technology. Background Art

[0004] As cellular systems, including fifth generation (5G) systems, support an increasing number of devices and services, including applications with a wide range of use cases and diverse needs with respect to bandwidth, latency, and reliability requirements, cellular systems may need to prioritize resources across the radio access network and the core network (and / or, for example, across the control plane and the user plane) to support differentiation between different services. Summary of the Invention

[0005] Methods and apparatus, including computer program products, are provided for managing configuration updates.

[0006] In some example embodiments, a device may be provided, comprising: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the device to at least: receive an indication as to whether a home network has made a change to previous configuration information for the device; and when the received indication indicates that the change has been made, delete the previous configuration information stored at the device.

[0007] In some variants, one or more of the features disclosed herein, including the following features, may optionally be included in any feasible combination. The device may be further caused to at least: receive configuration information including the indication. Deleting the previous configuration information includes deleting the previous configuration information associated with the home network and the visited network. Deleting the previous configuration information may include at least one network slice identifier. The deletion may enable the device to obtain updated configuration information for at least the visited network and / or the home network currently serving the device. The device may be further caused to at least: when receiving the indication representing the change associated with the home network, receive the updated configuration information for at least one other visited network to replace the deleted previous configuration information. The device may also be configured to at least: after obtaining the received configuration information, wait to perform registration to obtain the updated configuration information until an updated user equipment routing and access selection policy is received. The device may be further caused to at least: update configuration information for the visited network when receiving the indication indicating the change associated with the home network; and update only configuration information for the visited network when not receiving the indication indicating the change associated with the home network. The indication may indicate that the home network indicates to the visited network currently serving the user equipment that the device will be configured in the visited network taking into account the change in the home network.

[0008] Depending on the desired configuration, the aspects and features mentioned above can be implemented in systems, devices, methods, and / or articles of manufacture. The details of one or more variations of the subject matter described herein are set forth in the accompanying drawings and the following description. The features and advantages of the subject matter described herein will be apparent from the description and drawings, and from the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] In the attached figure:

[0010] Figure 1 An example of a portion of a 5G wireless network is shown according to some example embodiments;

[0011] Figure 2 shows an example of a process flow for a VPLMN configuration update according to some example embodiments;

[0012] Figure 3 Another example of a process flow for a VPLMN configuration update according to some example embodiments is shown;

[0013] Figure 4 shows an example of a network node according to some example embodiments; and

[0014] Figure 5 Examples of devices according to some example embodiments are shown.

[0015] Like numbers are used to refer to the same or similar items in the drawings. DETAILED DESCRIPTION

[0016] In a 5G system, a user equipment (UE) may roam from a home public land mobile network (HPLMN) to a visited public land mobile network (VPLMN). In this case, the UE may have configuration information for the VPLMN, for example, to enable access to one or more services available at the VPLMN. For example, the configuration information for the UE may change due to local decisions at the VPLMN. Alternatively or additionally, the UE's configuration information may change due to, for example, a change in the UE's subscription information at the HPLMN.

[0017] To further illustrate, a UE may access services at the HPLMN and / or VPLMN based on configuration information of the UE, which may be based on subscription information indicating allowed and / or available services. The UE's subscription information may change due to, for example, a change made or initiated by the HPLMN to the UE's subscription, in which case VPLMN-related configuration information for one or more services may also need to be updated to be consistent with the change at the HPLMN. Thus, a change in subscription information (which may be stored in a unified data management (UDM) node in the HPLMN) may trigger a change to the UE's configuration information for operation in the HPLMN and / or VPLMN.

[0018] The VPLMN and HPLMN configuration information may have different values, and the VPLMN may establish a mapping without the HPLMN being aware of the values ​​used locally within the VPLMN. For example, if the HPLMN changes the UE's subscription, the VPLMN may need to independently update the configuration information including subscription-related information so that the UE has the latest VPLMN information. To further illustrate, the subscription information at the HPLMN may change the QoS or another aspect of the network slice, or the subscription information may completely change the fact that a slice may be accessible, or the subscription may include new slices that the UE can use. Such a change may trigger a corresponding change in the configuration information used by the VPLMN.

[0019] When the HPLMN configuration changes, for example, with respect to a UE's subscription, the VPLMN configuration with respect to the UE's subscription may need to be updated. When the UE registers in the VPLMN, the HPLMN may push updated configuration information to the VPLMN (as mentioned, the updated configuration information is stored at a network node, such as the UDM (which may serve as a repository for storing this and other configuration and / or subscription information)). However, when the UE is visiting another VPLMN, the new VPLMN may receive the latest configuration or subscription information for the UE, but the VPLMN may not be able to detect whether the information represents a change because the VPLMN may not have state information about the UE's configuration or subscription information, and thus the UE may not trigger the change or update.

[0020] In some example embodiments, when the UE receives a configuration information update that includes information related to the UE's subscription (e.g., a network slice identifier, such as Network Slice Selection Assistance Information NSSAI), the UE may also receive an indication, such as a cause code, regarding the update. If the update is due to a local change of the VPLMN, the UE may update the VPLMN-related information that the UE maintains stored at the UE.

[0021] However, if the indicator (such as a cause code) indicates that the update is due to a change in HPLMN configuration (such as the UE's subscription), the UE may store the received update as a change in VPLMN configuration and a change in HPLMN configuration. For some (if not all) other VPLMN configurations, the UE may record or indicate that these updates may be invalid due to the change in HPLMN configuration.

[0022] In addition, in the event that an indicator (such as a cause code) indicates that the update is due to a change in the HPLMN configuration, when the UE accesses another VPLMN, the UE may operate as if the UE requires initial configuration information from the VPLMN (e.g., initial configuration information as if the UE is accessing the VPLMN for the first time). For example, the UE may delete (e.g., remove, reset, etc.) all UE configuration information for the VPLMN. For the case of a network slice VPLMN configuration, the UE may, for example, remove the configured NSSAI for the PLMN and its mapping to the S-NSSAI in the configured NSSAI for the HPLMN, the allowed NSSAI and its mapping to the S-NSSAI in the configured NSSAI for the HPLMN, and any rejected S-NSSAI in the PLMN. Such deletion may cause the UE to appear to the network as a UE requiring initial configuration when performing a registration procedure, and cause the network to provide the UE with initial configuration when the UE accesses the VPLMN as part of the registration.

[0023] To further illustrate, when the indicator (such as a cause code) indicates that the update is due to a change in the HPLMN configuration, as mentioned, the UE may locally delete certain configuration information for some (if not all) other VPLMNs, such as network slice configuration information (e.g., NSSAI as mentioned above). Thus, when the UE performs a registration procedure in these other VPLMNs, the UE may not send a request for NSSAI, but may receive the configuration for the VPLMN from the network. Such received configuration information may include a slice identifier for the VPLMN and mapped to an HPLMN value, such as S-NSSAI.

[0024] In some example embodiments, before the UE performs a new registration procedure, the UE may wait for updated policies, such as URSP (UE Routing and Access Selection Policy), from the network in the serving VPLMN, since the URSP may also change when the UE's subscription to the S-NSSAI has changed.

[0025] Figure 1 An example of a portion of a 5G wireless network 100 is shown, according to some example embodiments.

[0026] The 5G wireless network 100 may include a user equipment (UE) 150 configured to wirelessly couple to a radio access network (RAN) 152, which is served by wireless access points (such as base stations, wireless local area network access points, home base stations, and / or other types of wireless access points).

[0027] The network 100 may include a core network, which may include an access and mobility management function (AMF) 154, a visit session management function (V-SMF) 156, an access policy control function (v-PCF) 160, a visit network slice selection function (v-NSSF) 164, and / or a visit user plane function (V-UPF) 158. Figure 1 In the example of FIG, devices 152 to 164 may be associated with a visited public land mobile network (VPLMN) 166.

[0028] The network 100 and / or the core network may also include devices with functionality to support a home public land mobile network (HPLMN) 170. For example, these devices in the HPLMN 170 may include devices and corresponding functionality for "home" wireless local area network (WLAN) access, offload, and / or non-3GPP access. These devices may include a home SMF 172, a home PCF 174, a home NSSF 176, unified data management 178, an authentication server function (AUSF) 180, an application function (AF) 182, a home user plane function (H-UPF) 184, and a data network (DN) 186.

[0029] Figure 1 Also shown are service interfaces such as N1, N2, N3, N4, N6, N7, N11, N15, N18, N24, etc. The architecture, nodes (including AMF, V-PCF, H-PCF, H-SMF and V-SMF, and Figure 1 other devices shown herein) and service interfaces, but other standard and proprietary interfaces may also be used.

[0030] A network slice refers to a logical network that provides specific network capabilities and network characteristics. A network slice can be considered a dynamically created logical end-to-end network, so that a given UE can access different network slices through the same radio access network (e.g., through the same radio interface). Network slices can provide different services and / or have different QoS needs / requirements. 3GPP TS 23.501 (System Architecture for 5G Systems) describes an example of network slicing.

[0031] The UE's subscription information may indicate configuration information related to the number, QoS type and / or identity of network slices. The UE's configuration information (provided by the network when registering in a PLMN such as a VPLMN and / or HPLMN) may include one or more network slice identifiers, such as one or more single NSSAIs (S-NSSAIs). The S-NSSAI may consist of: a) a slice / service type (SST), which refers to the expected network slice behavior in terms of features and services; and / or b) a slice differentiator (SD), which is optional information that supplements the slice / service type to distinguish between multiple network slices of the same slice / service type.

[0032] Figure 2 An example of a process 200 is shown, according to some example embodiments. Figure 2 The description also refers to Figure 1 .

[0033] At 205, according to some example embodiments, user equipment 150 may receive configuration information from the network and / or an indication as to whether the configuration information represents a change (such as an update or modification) local to the VPLMN (which is currently serving the UE) or a change associated with the HPLMN. In some example embodiments, the configuration information may be received in a message (such as a registration accept message or a UE configuration update message). The indication may be included in the configuration information or separately signaled to the UE. The presence of the indication may indicate that a configuration change has been made to the UE's HPLMN, and the configuration change needs to be applied to the UE's configuration at the VPLMN. In some implementations, the indication (or lack thereof) may indicate that the UE's configuration information should be updated locally so as to affect only the UE's configuration for the currently serving VPLMN and not other VPLMNs (or HPLMNs). In some example embodiments, the indication is included in the configuration information. For example, the configuration information may represent configuration information for the currently serving VPLMN and include an indication signaled to the UE whether the UE's configuration information needs to be changed. Alternatively or additionally, the indication may be provided to the UE separately from the configuration information.

[0034] When the indication indicates a change in HPLMN configuration (e.g., which may be due to a change in the UE's subscription information), the UE may delete the previously stored configuration information locally at the UE (e.g., at 208, 210). The deleted configuration information may include network slice configuration information, such as the configured NSSAI for the PLMN, its mapping to the S-NSSAI in the configured NSSAI for the HLMN, allowed NSSAIs and their mapping to the S-NSSAI in the configured NSSAI for the HPLMN, any rejected S-NSSAI in the PLMN, and the like. Additionally, the deleted configuration information may be for some, if not all, other VPLMNs. For example, the UE may delete previously stored network slice configuration information stored for all VPLMNs. More specifically, the UE may delete slice information for all other PLMNs while retaining any "current" configuration received at 205 for the currently serving VPLMN.

[0035] When the indication indicates a change in HPLMN configuration, the UE 150 may be registered in another VPLMN during registration with the network, in which case the UE may not send a request for NSSAI, but instead receive configuration information including network slice configuration information for the VPLMN from the network at 220. This configuration information may include a slice identifier for the VPLMN, such as S-NSSAI, and its mapping to a value for the HPLMN.

[0036] In some example embodiments, at 220, before the UE performs a new registration procedure, the UE may wait for an updated policy from the network in the serving PLMN, such as a URSP (UE Routing and Access Selection Policy), since the URSP may also change when the UE's subscription to the S-NSSAI changes.

[0037] When the indication indicates a local VPLMN configuration change, the UE may update the stored configuration information including network slice information for the serving VPLMN without affecting (e.g., deleting, updating, etc.) configurations for other PLMNs (NO at 208, 230). In some example embodiments, the UE may determine that the UE configuration change is a local configuration change based on not receiving the indication.

[0038] Figure 3 An example of a process 300 is shown, according to some example embodiments. Figure 3 The description also refers to Figure 1 .

[0039] At 310, according to some example embodiments, a network node, such as base station 152, may receive configuration information and / or an indication of whether the configuration information represents a change local to the VPLMN (such as an update or modification) or a change associated with the HPLMN from AMF 154. At 320, the network node may provide the configuration information and / or an indication of whether the configuration information represents a change local to the VPLMN (such as an update or modification) or a change associated with the HPLMN to UE 150.

[0040] In some example embodiments, when an AMF, such as AMF 154, updates UE 150, the AMF may indicate to the UE (via base station 152) whether the update is due to a change in the subscribed S-NSSAI. The AMF may detect such an update or change because the AMF receives updated data from UDM 178 or because the AMF receives an indication from the UDM that the UE's network slice subscription has changed.

[0041] If the UE is notified that the network slice subscription information has changed, then as mentioned, the UE may locally delete the network slice information that the UE has for all other PLMNs (i.e., so that when the UE registers in other PLMNs, it does not send the requested NSSAI, and the serving PLMN may update the UE configuration for the serving PLMN). It also updates the current PLMN information with any received values. Additionally, if a URSP is required, the UE will wait for an updated URSP (UE Routing and Access Selection Policy) before performing a new registration procedure.

[0042] In some example embodiments, when the subscribed S-NSSAI changes and when the UE is unreachable at the time of the change, a Universal Data Repository (UDR) flag may be set in the HPLMN to ensure that when the UE registers with the AMF in the PLMN when it is reachable, the AMF is notified that the subscription data includes an updated set of S-NSSAIs. Since the AMF successfully updated the UE, the UE may be requested to register with the AMF under instruction to update the UDM 178 to reset this flag.

[0043] To further illustrate, the S-NSSAI (which may be in the configured NSSAI for the HPLMN) may match the UE's subscribed S-NSSAI when it is provided to the UE. When the subscribed S-NSSAI for the serving PLMN in which the UE 150 is registered is updated (e.g., by removing the old S-NSSAI and / or adding a new S-NSSAI), the AMF 154 may (via the base station 152 labeled "(R)AN") update the UE with the serving VPLMN's configured NSSAI, allowed NSSAI, and / or mappings associated with the configured NSSAI for the HPLMN. However, as mentioned above, only the configured NSSAI for the currently serving VPLMN will be updated to match the new subscription information. Therefore, if the UE visits another VPLMN other than the HPLMN and has a stored configured NSSAI for this VPLMN, this information will be outdated. The UE may also store the configured NSSAI for multiple VPLMNs in addition to the currently serving VPLMN, so that when returning to these VPLMNs, the UE may not need to be configured with the configured NSSAI.

[0044] The configured NSSAI for a serving PLMN includes S-NSSAI values ​​that may be used in the serving PLMN and may be associated with a mapping of each S-NSSAI in the configured NSSAI to one or more corresponding S-NSSAI values ​​in the configured NSSAI for the HPLMN. When providing the requested NSSAI to the network upon registration, a UE in a given PLMN may include and use the S-NSSAI applicable to this PLMN (this may include and / or be associated with a mapping of each S-NSSAI in the requested NSSAI to an S-NSSAI of a configured NSSAI for the HPLMN that is part of the configured and / or allowed NSSAI applicable to this PLMN). Upon successful completion of the UE's registration procedure for a radio access type, the UE may obtain the allowed NSSAI for this access type from the AMF, the allowed NSSAI including one or more S-NSSAIs (this may include an association with a mapping of the allowed NSSAI to the configured NSSAI for the HPLMN). These S-NSSAIs are valid for the current registration area and access type provided by the AMF with which the UE has registered and can be used by the UE (up to a given number of simultaneous network slices or PDU sessions).

[0045] When the configured NSSAI for a PLMN and / or the associated mapping of this configured NSSAI to the configured NSSAI for the HPLMN is provided to the UE, the configured NSSAI (and / or the associated mapping, if any) may be stored in the UE until a new configured NSSAI (and / or the associated mapping) for this PLMN is provided in the UE.

[0046] When a new configured NSSAI for a PLMN (and / or a new associated mapping of this configured NSSAI to a configured NSSAI for the HPLMN) is provided, as mentioned, the UE may replace any stored (old) configured NSSAI for this PLMN with the new configured NSSAI for this PLMN; and the UE may delete any stored associated mapping of this old configured NSSAI for this PLMN to a configured NSSAI for the HPLMN, and store an associated mapping of this new configured NSSAI to a configured NSSAI for the HPLMN (if any); and the UE may delete any stored allowed NSSAI and associated mappings and rejected S-NSSAI for this PLMN.

[0047] Even when registered in another PLMN, the UE may keep stored the received configured NSSAI for the PLMN and the associated mapping to the configured NSSAI for the HPLMN. However, the number of configured NSSAIs and associated mappings that will remain stored in the UE for PLMNs other than the HPLMN may depend on the UE implementation.

[0048] If a VPLMN performs a configuration update on a UE registered in the VPLMN (e.g., due to a change in the subscribed S-NSSAI), this may result in an update to the configured NSSAI for the serving PLMN and / or the associated mapping of the configured NSSAI for the serving PLMN to the configured NSSAI for the HPLMN. If the configuration update affects the S-NSSAI in the currently allowed NSSAI, an update to the allowed NSSAI and / or the associated mapping of the allowed NSSAI to the configured NSSAI for the HPLMN may be implemented.

[0049] When the configured NSSAI changes, the UE may only replace the configured NSSAI for the current PLMN. This is the correct behavior when the change is due to a VPLMN decision for the VPLMN. However, when the change is due to a subscription change, the stored configured NSSAI for other PLMNs and the mapping to the S-NSSAI value in the configured NSSAI for the HPLMN may also become invalid and out of date. However, the AMF in the other PLMNs may not have received the updated configuration (and the other PLMNs are unaware of the change), so these PLMNs will not trigger a change in the configured NSSAI due to the subscription change. This means that when returning to these PLMNs, the UE will not be configured correctly.

[0050] When the requested NSSAI is not included or when S-NSSAI is rejected in the PLMN, the AMF may update the UE slice configuration information for the PLMN.

[0051] When the UE does not have a configuration for a VPLMN, the UE may not include the requested NSSAI in the VPLMN registration request. The VPLMN (if applicable) may then configure the UE with the configured NSSAI for the PLMN. When the PLMN updates the configured NSSAI for the UE, as mentioned, the PLMN may explicitly indicate to the UE whether the change is due to a local configuration change or whether the change is due to a change in the HPLMN configuration. If the change is due to a HPLMN configuration change, then (1) the UE may locally delete the network slice configuration information it has for all other PLMNs and may wait for an updated URSP before performing a new registration procedure, because when the EU subscription to the S-NSSAI changes, the URSP will also change. Alternatively, if the change is due only to a locally serving PLMN, the UE may update the information for the serving PLMN without affecting the configuration for other PLMNs.

[0052] As mentioned, the UE may be configured with network slicing configuration information by the HPLMN. For example, the HPLMN may push configuration information to the UDM, which may be provided to the UE via the AMF and the base station. The network slicing configuration information may include one or more configured NSSAIs. The configured NSSAI may be applicable to one PLMN or all PLMNs without a specific configured NSSAI (for example, this may be feasible for an NSSAI that only contains an S-NSSAI with a standard value, see, for example, 3GPP TS 23.501, clause 5.15.2.1). There may be at most one configured NSSAI per PLMN. The configured NSSAI of a PLMN may include an S-NSSAI with a standard value or a PLMN-specific value. The configured NSSAI for a serving PLMN may include S-NSSAI values ​​that may be applicable in the serving PLMN and may be associated with a mapping of each S-NSSAI in the configured NSSAI to one or more corresponding S-NSSAI values ​​in the configured NSSAI for the HPLMN.

[0053] As mentioned, the S-NSSAI in the configured NSSAI for the HPLMN may match the subscribed S-NSSAI for the UE when it is provided to the UE. When the subscribed S-NSSAI is updated (e.g., the old one is removed and / or the new one is added) and it is applicable to a serving PLMN in which the UE may be registered, the AMF may update the UE with the configured NSSAI and / or allowed NSSAI of the serving PLMN and / or the associated mapping with the configured NSSAI for the HPLMN.

[0054] When providing the requested NSSAI to the network at registration time, a UE in a given PLMN may only include and use the S-NSSAI applicable to this PLMN (and possibly associated with a mapping of each S-NSSAI in the requested NSSAI to an S-NSSAI configured for the HPLMN as part of the configured and / or allowed NSSAI applicable to this PLMN). Upon successful completion of the UE's registration procedure for an access type, the UE may obtain from the AMF the allowed NSSAIs for this access type, which may include one or more S-NSSAIs, possibly associated with a mapping of the allowed NSSAIs to the configured NSSAIs for the HPLMN. These S-NSSAIs may be valid for the current registration area and access type provided by the AMF with which the UE has registered, and may be used simultaneously by the UE (up to the maximum number of simultaneous network slices or PDU sessions). The UE may also obtain from the AMF one or more rejected S-NSSAIs with the rejection reason and justification. The S-NSSAI may be rejected in the entire PLMN or in the current registration area.

[0055] When the UE remains RM-REGISTERED in a PLMN regardless of the access type, the UE may not re-attempt registration for a rejected S-NSSAI in the entire PLMN until the rejected S-NSSAI is deleted. When the UE remains RM-REGISTERED in a PLMN, the UE may not re-attempt registration for a rejected S-NSSAI in the current registration area until the S-NSSAI is moved out of the current registration area.

[0056] The UE may store (S-)NSSAI as follows: When the configured NSSAI for a PLMN and / or an associated mapping of this configured NSSAI to the configured NSSAI for an HPLMN is provided to the UE, the configured NSSAI (and / or associated mapping, if present) may be stored in the UE until a new configured NSSAI and / or associated mapping for this PLMN is provided in the UE (or when the HPLMN configuration changes). When a new configured NSSAI for a PLMN and / or a new associated mapping of this configured NSSAI to a configured NSSAI for an HPLMN is provided, or when removal of the configuration for a PLMN is requested due to an HPLMN configuration change, the UE may replace any stored (e.g., old) configured NSSAI for this PLMN (if applicable) with the new configured NSSAI for this PLMN; and the UE may delete any stored associated mapping of this old configured NSSAI for this PLMN to the configured NSSAI for the HPLMN, and store the associated mapping of this new configured NSSAI to the configured NSSAI for the HPLMN (if present and applicable); and the UE may delete any stored allowed NSSAI and associated mappings and rejected S-NSSAI for this PLMN;

[0057] If received, the allowed NSSAI and access type for the PLMN (and any associated mapping of such allowed NSSAI to the configured NSSAI for the HPLMN) may be stored in the UE. The UE may store such allowed NSSAI and any associated mapping of allowed NSSAI to the configured NSSAI for the HPLMN (this may also be persistent when the UE is switched off).

[0058] The UE may persistently store the allowed NSSAIs and any associated mappings of the allowed NSSAIs to the configured NSSAIs for the HPLMN.

[0059] If received, S-NSSAIs rejected in the entire PLMN may be stored in the UE while being RM-REGISTERED in this PLMN regardless of access type, or until they are deleted.

[0060] If received, the rejected S-NSSAI in the current registration area may be stored in the UE while being RM-REGISTERED until the UE moves out of the current registration area, or until the S-NSSAI is deleted.

[0061] One or more of the S-NSSAIs in the allowed NSSAIs provided to the UE may have values ​​that are not part of the UE's slice configuration information for the serving PLMN. In this case, the allowed NSSAIs are associated with mapping information about how each S-NSSAI in the allowed NSSAIs corresponds to the S-NSSAI of the configured NSSAI for the HPLMN. This mapping information may be sufficient to allow the UE to associate the S-NSSAI with the corresponding S-NSSAI from the allowed NSSAIs according to the network slice selection policy (NSSP) of the URSP rules (see, for example, the rules defined in TS 23.503) for a given application.

[0062] At any time, the AMF may provide the UE with the newly configured NSSAI for the serving PLMN, associated with the mapping of the configured NSSAI to the configured NSSAI for the HPLMN. The configured NSSAI for the serving PLMN and the mapping information may be determined in the AMF (if the AMF is allowed to determine the network slice configuration for the entire PLMN based on the configuration) or by the NSSF. The AMF may provide the newly configured NSSAI as part of the UE configuration update procedure.

[0063] If the HPLMN performs a configuration update on a UE registered with the HPLMN (e.g., due to a change in the subscribed S-NSSAI), this may result in an update to the configured NSSAI for the HPLMN. If the configuration update affects the S-NSSAI in the currently allowed NSSAI, an update to the allowed NSSAI and / or the associated mapping of the allowed NSSAI to the configured NSSAI for the HPLMN (if any) may also be possible.

[0064] If a VPLMN performs a configuration update on a UE registered in the VPLMN (e.g., due to a change in the subscribed S-NSSAI), this may result in an update to the configured NSSAI for the serving PLMN and / or the associated mapping of the configured NSSAI for the serving PLMN to the configured NSSAI for the HPLMN. If the configuration update affects the S-NSSAI in the currently allowed NSSAI, an update to the allowed NSSAI and / or the associated mapping of the allowed NSSAI to the configured NSSAI for the HPLMN may also be implemented.

[0065] As mentioned, a UE whose configured NSSAI for the serving PLMN has been updated and whose stored allowed NSSAI has been deleted may initiate a registration procedure to receive a new valid allowed NSSAI.

[0066] Figure 4 1 shows a block diagram of a network node 400 according to some example embodiments. For example, the network node 400 may be configured to provide Figure 3 Furthermore, the mobile wireless network may also have a plurality of network nodes 400. For example, the network node may be incorporated into one or more of the devices 152 to 180.

[0067] According to some example embodiments, network node 400 may include a network interface 402, a processor 420, and a memory 404. Network interface 402 may include a wired and / or wireless transceiver to enable access to other nodes including base stations, devices 152 to 180, the Internet, and / or other nodes. Memory 404 may include volatile and / or non-volatile memory including program code that, when executed by at least one processor 420, provides, among other things, the processes disclosed herein, including processes 200, 300, 400, and the like.

[0068] Figure 5 A block diagram of an apparatus 10 is shown, according to some example embodiments.

[0069] Apparatus 10 may represent user equipment, such as user equipment 150. Apparatus 10 or portions thereof may be implemented in other network nodes including base stations / WLAN access points and other network nodes (eg, devices 152 to 184).

[0070] The device 10 may include at least one antenna 12 in communication with a transmitter 14 and a receiver 16. Optionally, the transmitting antenna and the receiving antenna may be separate. The device 10 may also include a processor 20 configured to provide signals to and receive signals from the transmitter and receiver, respectively, and to control the operation of the device. The processor 20 may be configured to control the operation of the transmitter and receiver by implementing control signaling via electrical leads to the transmitter and receiver. Similarly, the processor 20 may be configured to control other elements of the device 10 by implementing control signaling via electrical leads connecting the processor 20 to other elements (such as a display or memory). The processor 20 may be embodied in a variety of ways, including circuitry, at least one processing core, one or more microprocessors with an attached digital signal processor, one or more processors without an attached digital signal processor, one or more co-processors, one or more multi-core processors, one or more controllers, processing circuitry, one or more computers, various other processing elements including integrated circuits (e.g., application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), etc.), or some combination thereof. Therefore, although in Figure 520 is shown as a single processor, but in some example embodiments, processor 20 may include multiple processors or processing cores.

[0071] Device 10 may be capable of operating under one or more air interface standards, communication protocols, modulation types, access types, etc. The signals sent and received by processor 20 may include signaling information in accordance with the air interface standard of the applicable cellular system, and / or any number of different wired or wireless networking technologies, including but not limited to Wi-Fi, wireless local access network (WLAN) technologies such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, 802.16, 802.3, ADSL, DOCSIS, etc. In addition, these signals may include voice data, user-generated data, user-requested data, etc.

[0072] For example, the device 10 and / or the cellular modem therein may be capable of operating in accordance with various first generation (1G) communication protocols, second generation (2G or 2.5G) communication protocols, third generation (3G) communication protocols, fourth generation (4G) communication protocols, fifth generation (5G) communication protocols, Internet Protocol Multimedia Subsystem (IMS) communication protocols (e.g., Session Initiation Protocol (SIP)), etc. For example, the device 10 may be capable of operating in accordance with 2G wireless communication protocols IS-136, Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), IS-95, Code Division Multiple Access (CDMA), etc. Furthermore, for example, the device 10 may be capable of operating in accordance with 2.5G wireless communication protocols General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), etc. Additionally, for example, the device 10 may be capable of operating in accordance with 3G wireless communication protocols such as Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 2000 (CDMA2000), Wideband Code Division Multiple Access (WCDMA), Time Division Synchronous Code Division Multiple Access (TD-SCDMA), etc. The device 10 may additionally be capable of operating in accordance with 3.9G wireless communication protocols such as Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), etc. Additionally, for example, the device 10 may be capable of operating in accordance with 4G wireless communication protocols such as LTE-Advanced, 5G, etc., as well as similar wireless communication protocols that may be subsequently developed.

[0073] It should be understood that processor 20 may include circuitry for implementing the audio / video and logic functions of device 10. For example, processor 20 may include a digital signal processor device, a microprocessor device, an analog-to-digital converter, a digital-to-analog converter, and the like. The control and signal processing functions of device 10 may be allocated among these devices according to their respective capabilities. Processor 20 may also include an internal voice coder (VC) 20a, an internal data modem (DM) 20b, and the like. In addition, processor 20 may include functionality for operating one or more software programs that may be stored in memory. Generally speaking, processor 20 and the stored software instructions may be configured to cause device 10 to perform actions. For example, processor 20 may be capable of operating a connectivity program, such as a web browser. The connectivity program may allow device 10 to transmit and receive web content, such as location-based content, according to protocols such as Wireless Application Protocol, WAP, Hypertext Transfer Protocol, HTTP, and the like.

[0074] Device 10 may also include a user interface, including, for example, an earpiece or speaker 24, a ringer 22, a microphone 26, a display 28, a user input interface, and the like, which may be operably coupled to processor 20. As mentioned above, display 28 may include a touch-sensitive display, which a user can touch and / or gesture to make selections, enter values, and the like. Processor 20 may also include user interface circuitry configured to control at least some functions of one or more elements of the user interface, such as speaker 24, ringer 22, microphone 26, display 28, and the like. Processor 20 and / or the user interface circuitry including processor 20 may be configured to control one or more functions of one or more elements of the user interface via computer program instructions (e.g., software and / or firmware) stored in a memory accessible to processor 20 (e.g., volatile memory 40, non-volatile memory 42, and the like). Device 10 may include a battery for powering various circuits associated with the mobile terminal (e.g., circuitry for providing mechanical vibration as a detectable output). The user input interface may include means allowing apparatus 20 to receive data, such as a keypad 30 (which may be a virtual keyboard presented on display 28 or an externally coupled keyboard) and / or other input means.

[0075] like Figure 5 As shown, the device 10 may also include one or more mechanisms for sharing and / or obtaining data. For example, the device 10 may include a short-range radio frequency (RF) transceiver and / or interrogator 64 so that data can be shared with and / or obtained from electronic devices based on RF technology. The device 10 may include other short-range transceivers, such as infrared (IR) transceivers 66, Bluetooth TMBluetooth™ (BT) transceiver 68, wireless universal serial bus (USB) transceiver 70, Bluetooth TM Low power transceiver, ZigBee transceiver, ANT transceiver, cellular device to device transceiver, wireless local area link transceiver and / or any other short-range radio technology. For example, device 10 and in particular the short-range transceiver may be able to transmit data to and / or receive data from an electronic device within a proximity area of ​​the device, such as within 10 meters. Device 10 including a Wi-Fi or wireless local area network modem may also be able to transmit data to and / or receive data from an electronic device according to various wireless networking technologies, including 6LoWpan, Wi-Fi, low power Wi-Fi, WLAN technologies such as IEEE 802.11 technology, IEEE 802.15 technology, IEEE 802.16 technology, etc.

[0076] Device 10 may include memory, such as a subscriber identity module (SIM) 38, which may store information elements related to a mobile user, a removable user identity module (R-UIM), an eUICC, a UICC, and the like. In addition to the SIM, device 10 may also include other removable and / or fixed memory. Device 10 may include volatile memory 40 and / or non-volatile memory 42. For example, volatile memory 40 may include random access memory (RAM), including dynamic and / or static RAM, on-chip or off-chip cache memory, and the like. Non-volatile memory 42, which may be embedded and / or removable, may include, for example, read-only memory, flash memory, magnetic storage devices such as hard disks, floppy disk drives, tapes, optical disk drives and / or media, non-volatile random access memory (NVRAM), and the like. Similar to volatile memory 40, non-volatile memory 42 may include a cache area for temporarily storing data. At least a portion of the volatile and / or non-volatile memory may be embedded in processor 20. The memory may store one or more software programs, instructions, information segments, data, and / or the like that can be used by the device to perform the operations disclosed herein. Alternatively or additionally, the device may be configured to initiate the operations disclosed herein with respect to base stations / WLAN access points and network nodes including UEs.

[0077] The memory may include an identifier, such as an International Mobile Equipment Identity (IMEI) code, that can uniquely identify device 10. In an example embodiment, processor 20 may be configured using computer code stored at memory 40 and / or 42 to provide the operations disclosed herein with respect to base stations / WLAN access points and network nodes including UEs (see, e.g., processes 200 and / or 300).

[0078] Some of the embodiments disclosed herein may be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic. For example, the software, application logic, and / or hardware may reside on the memory 40, the control device 20, or an electronic component. In some example embodiments, the application logic, software, or instruction set is maintained on any of a variety of conventional computer-readable media. In the context of this document, a "computer-readable medium" may be any non-transitory medium that can contain, store, communicate, propagate, or transport instructions for use by, or in connection with, an instruction execution system, apparatus, or device, such as a computer or data processor circuit, wherein Figure 5 As an example, computer-readable media may include non-transitory computer-readable storage media, which may be any medium that can contain or store instructions for use by, or in connection with, an instruction execution system, apparatus, or device, such as a computer.

[0079] Without in any way limiting the scope, interpretation, or application of the claims appended hereto, a technical effect of one or more of the example embodiments disclosed herein may be improved UE configuration.

[0080] Depending on the desired configuration, the subject matter described herein may be embodied in systems, devices, methods, and / or articles. For example, the base stations and user equipment (or one or more components thereof) and / or processes described herein may be implemented using one or more of the following: a processor that executes program code, an application-specific integrated circuit (ASIC), a digital signal processor (DSP), an embedded processor, a field programmable gate array (FPGA), and / or a combination thereof. These different implementations may include implementations in the form of one or more computer programs that can be executed and / or interpreted on a programmable system comprising at least one programmable processor that may be dedicated or general-purpose, the at least one programmable processor being coupled to receive data and instructions from a storage system, at least one input device, and at least one output device and to transmit data and instructions to them. These computer programs (also referred to as programs, software, software applications, applications, components, program codes, or codes) include machine instructions for programmable processors and may be implemented in high-level programs and / or object-oriented programming languages, and / or in assembly / machine languages. As used herein, the term "computer-readable medium" refers to any computer program product, machine-readable medium, computer-readable storage medium, device, and / or apparatus (e.g., a disk, an optical disk, a memory, a programmable logic device (PLD)) for providing machine instructions and / or data to a programmable processor, including a machine-readable medium that receives machine instructions. Similarly, systems are also described herein that may include a processor and a memory coupled to the processor. The memory may include one or more programs that cause the processor to perform one or more of the operations described herein.

[0081] Although several variations have been described in detail above, other modifications or additions are possible. In particular, in addition to the features and / or variations set forth herein, other features and / or variations may be provided. Furthermore, the implementations described above may involve various combinations and subcombinations of the disclosed features and / or combinations and subcombinations of several other features disclosed above. Other embodiments may be within the scope of the appended claims.

[0082] If desired, the different functions discussed herein can be performed in different orders and / or simultaneously with each other. In addition, if desired, one or more of the functions described above may be optional or may be combined. Although various aspects of some of the embodiments are set forth in the independent claims, other aspects of some of the embodiments include other combinations of features from the described embodiments and / or dependent claims with features of the independent claims, rather than only including the combinations explicitly set forth in the claims. It should also be noted herein that although example embodiments have been described above, these descriptions should not be considered to have a restrictive meaning. Instead, there are several changes and modifications that can be made without departing from the scope of some of the embodiments as defined by the appended claims. Other embodiments may be within the scope of the appended claims. The term "based on" includes "at least based on". Unless otherwise indicated, the use of the phrase "such as" means "such as".

Claims

1. A method for managing network configuration information of a user equipment accessing a network, the method comprising: receiving, at the user equipment, an indication that subscription information of the user equipment has been changed in a home public land mobile network (HPLMN) of the user equipment while registering with a first visited public land mobile network (VPLMN); Based on the indication, using the user equipment, delete network slice selection assistance information NSSAI configured and stored at the user equipment for a second VPLMN, the second VPLMN being different from the first VPLMN currently serving the user equipment; receiving, at the user equipment, a second configured NSSAI for the second VPLMN during a registration procedure with the second VPLMN; as well as After deleting the configured NSSAI for the second VPLMN, replacing the configured NSSAI for the second VPLMN previously stored at the user equipment with the second configured NSSAI for the second VPLMN received at the user equipment.

2. The method of claim 1 , wherein the requested NSSAI requested by the second VPLMN from the user equipment during the registration process is the configured NSSAI.

3. The method of claim 1 , wherein the receiving the indication that the subscription information of the user equipment has been changed in the HPLMN of the user equipment causes the user equipment to operate as required for an initial NSSAI of the second VPLMN during the registration process with the second VPLMN.

4. The method of claim 3, wherein the initial NSSAI required for the second VPLMN is the second configured NSSAI for the second VPLMN received at the user equipment during the registration process with the second VPLMN.

5. The method of claim 1 , wherein the receiving the second configured NSSAI for the second VPLMN is caused by the user equipment operating as if accessing the second VPLMN for the first time with respect to requiring an initial NSSAI during the registration process with the second VPLMN.

6. The method of claim 1 , wherein the deleting the configured NSSAI for the second VPLMN further comprises deleting a mapping of a third configured NSSAI for the first VPLMN to one or more single NSSAIs-NSSAIs in a fourth configured NSSAI for the HPLMN, an allowed NSSAI for the first VPLMN, a mapping of the allowed NSSAI for the first VPLMN to the one or more S-NSSAIs in the fourth configured NSSAI for the HPLMN, or any rejected S-NSSAI associated with the first VPLMN.

7. The method of claim 1, wherein the deleting further comprises: In response to receiving the indication, deleting any configured NSSAI stored locally at the user equipment for any PLMN, wherein the any PLMN includes at least the first VPLMN, the second VPLMN, and the HPLMN of the user equipment.

8. A user equipment, the user equipment being configured to manage network configuration information of an access network of the user equipment, the user equipment comprising: at least one processor; as well as At least one memory having instructions stored therein, which, when executed by the at least one processor, cause the user equipment to at least perform: receiving, at the user equipment, an indication that subscription information of the user equipment has been changed in a home public land mobile network (HPLMN) of the user equipment while registering with a first visited public land mobile network (VPLMN); Based on the indication, using the user equipment, delete network slice selection assistance information NSSAI configured and stored at the user equipment for a second VPLMN, the second VPLMN being different from the first VPLMN currently serving the user equipment; receiving, at the user equipment, a second configured NSSAI for the second VPLMN during a registration procedure with the second VPLMN; as well as After deleting the configured NSSAI for the second VPLMN, replacing the configured NSSAI for the second VPLMN previously stored at the user equipment with the second configured NSSAI for the second VPLMN received at the user equipment.

9. The user equipment of claim 8, wherein the requested NSSAI requested by the second VPLMN from the user equipment during the registration procedure is the configured NSSAI.

10. The user equipment of claim 8, wherein the receiving of the indication that the subscription information of the user equipment has been changed in the HPLMN of the user equipment causes the user equipment to operate as required for an initial NSSAI of the second VPLMN during the registration process with the second VPLMN.

11. The user equipment of claim 10, wherein the initial NSSAI required for the second VPLMN is the second configured NSSAI for the second VPLMN received at the user equipment during the registration process with the second VPLMN.

12. The user equipment of claim 8, wherein the receiving the second configured NSSAI for the second VPLMN is caused by the user equipment operating as if it is accessing the second VPLMN for the first time, with respect to requiring an initial NSSAI during the registration process with the second VPLMN.

13. The user equipment of claim 8, wherein the deleting the configured NSSAI for the second VPLMN further comprises deleting: a mapping of a third configured NSSAI for the first VPLMN to one or more single NSSAIs (S-NSSAIs) in a fourth configured NSSAI for the HPLMN, an allowed NSSAI for the first VPLMN, a mapping of the allowed NSSAI for the first VPLMN to the one or more S-NSSAIs in the fourth configured NSSAI for the HPLMN, or any rejected S-NSSAI associated with the first VPLMN.

14. The user equipment according to claim 8, wherein the deleting further comprises: In response to receiving the indication, deleting any configured NSSAI stored locally at the user equipment for any PLMN, wherein the any PLMN includes at least the first VPLMN, the second VPLMN, and the HPLMN of the user equipment.

15. A non-transitory computer-readable storage medium for managing network configuration information of a user device accessing a network, the non-transitory computer-readable storage medium comprising program code stored thereon, the program code causing the device to perform the method according to any one of claims 1 to 7 when executed by at least one processor of the device.

16. A method for managing network configuration information of a user equipment accessing a network, the method comprising: determining, while the user equipment is registering with a first visited public land mobile network (VPLMN), that subscription information of the user equipment stored in a home public land mobile network (HPLMN) of the user equipment has changed; as well as providing an indication to the user equipment that the subscription information of the user equipment stored in the HPLMN of the user equipment has changed, The instruction is operable to cause the user equipment to at least: deleting network slice selection assistance information NSSAI configured and stored at the user equipment for a second VPLMN, the second VPLMN being different from the first VPLMN currently serving the user equipment, Initiate a registration process with the second VPLMN, receiving, at the user equipment, a second configured NSSAI for the second VPLMN, and During the registration procedure initiated after the deletion of the configured NSSAI for the second VPLMN previously stored at the user equipment, the configured NSSAI for the second VPLMN previously stored at the user equipment is replaced with the second configured NSSAI for the second VPLMN received at the user equipment.

17. An apparatus configured to manage network configuration information of a user equipment accessing a network, the apparatus comprising: at least one processor; as well as at least one memory having stored thereon instructions that, when executed by the at least one processor, cause the apparatus to at least perform: determining, while the user equipment is registering with a first visited public land mobile network (VPLMN), that subscription information of the user equipment stored in a home public land mobile network (HPLMN) of the user equipment has changed; as well as providing an indication to the user equipment that the subscription information of the user equipment stored in the HPLMN of the user equipment has changed, The instruction is operable to cause the user equipment to at least: deleting network slice selection assistance information NSSAI configured and stored at the user equipment for a second VPLMN, the second VPLMN being different from the first VPLMN currently serving the user equipment, Initiate a registration process with the second VPLMN, receiving, at the user equipment, a second configured NSSAI for the second VPLMN, and During the registration procedure initiated after the deletion of the configured NSSAI for the second VPLMN previously stored at the user equipment, the configured NSSAI for the second VPLMN previously stored at the user equipment is replaced with the second configured NSSAI for the second VPLMN received at the user equipment.

18. A non-transitory computer-readable storage medium for managing network configuration information of a user device accessing a network, the non-transitory computer-readable storage medium comprising program code stored thereon, the program code, when executed by at least one processor of an apparatus, causing the apparatus to at least perform: determining, when the user equipment is registered with a first visited public land mobile network (VPLMN), that subscription information of the user equipment stored in a home public land mobile network (HPLMN) of the user equipment has changed; and providing an indication to the user equipment that the subscription information of the user equipment stored in the HPLMN of the user equipment has changed, The instruction is operable to cause the user equipment to at least: deleting network slice selection assistance information NSSAI configured and stored at the user equipment for a second VPLMN, the second VPLMN being different from the first VPLMN currently serving the user equipment, Initiate a registration process with the second VPLMN, receiving, at the user equipment, a second configured NSSAI for the second VPLMN, and During the registration procedure initiated after the deletion of the configured NSSAI for the second VPLMN previously stored at the user equipment, the configured NSSAI for the second VPLMN previously stored at the user equipment is replaced with the second configured NSSAI for the second VPLMN received at the user equipment.

19. A method for managing network configuration information of a user equipment accessing a network, the method comprising: Initiating a first registration procedure with a first visited public land mobile network VPLMN using the user equipment; receiving, at the user equipment, an indication that subscription information associated with the user equipment and stored in a home public land mobile network (HPLMN) of the user equipment has changed, when the user equipment is registered with and currently served by the first VPLMN; In response to receiving the indication, deleting, using the user equipment, configured network slice selection assistance information NSSAI stored locally at the user equipment and associated with a second VPLMN, the second VPLMN being different from the first VPLMN currently serving the user equipment; Initiating a second registration procedure with the second VPLMN; receiving, at the user equipment, a second configured NSSAI for the second VPLMN; as well as During the registration procedure initiated after the deletion of the configured NSSAI for the second VPLMN previously stored at the user equipment, the configured NSSAI for the second VPLMN previously stored at the user equipment is replaced with the second configured NSSAI for the second VPLMN received at the user equipment.

20. The method of claim 19, wherein the deleting the configured NSSAI for the second VPLMN comprises deleting a mapping of a third configured NSSAI for the first VPLMN to one or more single NSSAIs (S-NSSAIs) in a fourth configured NSSAI for the HPLMN, an allowed NSSAI for the first VPLMN, a mapping of the allowed NSSAI for the first VPLMN to the one or more S-NSSAIs in the fourth configured NSSAI for the HPLMN, or any rejected S-NSSAIs associated with the first VPLMN.

21. The method of claim 19, wherein the deleting further comprises: In response to receiving the indication, deleting: all configured NSSAI stored at the user equipment.

22. A user equipment, the user equipment being configured to manage network configuration information of an access network of the user equipment, the user equipment comprising: at least one processor; as well as At least one memory having instructions stored thereon, which, when executed by the at least one processor, cause the user equipment to at least perform: Initiating a first registration procedure with a first visited public land mobile network VPLMN using the user equipment; receiving, at the user equipment, an indication that subscription information associated with the user equipment and stored in a home public land mobile network (HPLMN) of the user equipment has changed, when the user equipment is registered with and currently served by the first VPLMN; In response to receiving the indication, deleting, using the user equipment, configured network slice selection assistance information NSSAI stored locally at the user equipment and associated with a second VPLMN, the second VPLMN being different from the first VPLMN currently serving the user equipment; Initiating a second registration procedure with the second VPLMN; receiving, at the user equipment, a second configured NSSAI for the second VPLMN; as well as During the registration procedure initiated after the deletion of the configured NSSAI for the second VPLMN previously stored at the user equipment, the configured NSSAI for the second VPLMN previously stored at the user equipment is replaced with the second configured NSSAI for the second VPLMN received at the user equipment.

23. The user equipment of claim 22, wherein the deleting the configured NSSAI for the second VPLMN comprises deleting a mapping of a third configured NSSAI for the first VPLMN to one or more single NSSAIs (S-NSSAIs) in a fourth configured NSSAI for the HPLMN, an allowed NSSAI for the first VPLMN, a mapping of the allowed NSSAI for the first VPLMN to the one or more S-NSSAIs in the fourth configured NSSAI for the HPLMN, or any rejected S-NSSAI associated with the first VPLMN.

24. The user equipment of claim 22, wherein the deleting further comprises: In response to receiving the indication, deleting: all configured NSSAI stored at the user equipment.

25. A non-transitory computer-readable storage medium configured to manage network configuration information of a user device accessing a network, the non-transitory computer-readable storage medium having instructions stored thereon, which, when executed by at least one processor of a device, cause the user device to perform the method according to any one of claims 19 to 21.

26. A user equipment, the user equipment being configured to manage network configuration information of an access network of the user equipment, the user equipment comprising: at least one processor; as well as At least one memory having instructions stored thereon, which, when executed by the at least one processor, cause the user equipment to at least perform: receiving, while the user equipment is currently served by a first visited public land mobile network (VPLMN), an indication as to whether a change has been made to subscription information of the user equipment stored at a home public land mobile network (HPLMN) of the user equipment; marking deletion of configured network slice selection assistance information NSSAI stored locally at the user equipment and associated with a second VPLMN different from the first VPLMN currently serving the user equipment, if the indication received at the user equipment indicates that a change has been made to the subscription information of the user equipment stored at the HPLMN; After marking the deletion of the configured NSSAI for the second VPLMN, initiating a registration process with the second VPLMN; receiving a second configured NSSAI for the second VPLMN; as well as During the registration procedure initiated after the deletion of the configured NSSAI for the second VPLMN previously stored at the user equipment, replacing the configured NSSAI for the second VPLMN previously stored at the user equipment with the second configured NSSAI for the second VPLMN received at the user equipment.

27. A method for managing network configuration information of a user equipment accessing a network, the method comprising: receiving, while the user equipment is currently served by a first visited public land mobile network (VPLMN), an indication as to whether a change has been made to subscription information of the user equipment stored at a home public land mobile network (HPLMN) of the user equipment; marking deletion of configured network slice selection assistance information NSSAI stored locally at the user equipment and associated with a second VPLMN different from the first VPLMN currently serving the user equipment, if the indication received at the user equipment indicates that a change has been made to the subscription information of the user equipment stored at the HPLMN; After marking the deletion of the configured NSSAI for the second VPLMN, initiating a registration process with the second VPLMN; receiving a second configured NSSAI for the second VPLMN; as well as During the registration procedure initiated after the deletion of the configured NSSAI for the second VPLMN previously stored at the user equipment, replacing the configured NSSAI for the second VPLMN previously stored at the user equipment with the second configured NSSAI for the second VPLMN received at the user equipment.

28. A user equipment, the user equipment being configured to manage network configuration information of an access network of the user equipment, the user equipment comprising: at least one processor; as well as At least one memory having instructions stored thereon, which, when executed by the at least one processor, cause the user equipment to at least perform: receiving, while the user equipment is currently served by a first visited public land mobile network (VPLMN), an indication as to whether a change has been made to subscription information associated with the user equipment and stored at a home public land mobile network (HPLMN) of the user equipment; Based on the indication indicating the change to the subscription information associated with the user equipment and stored at the HPLMN of the user equipment, marking deletion of configured network slice selection assistance information NSSAI stored locally at the user equipment for a second VPLMN different from the first VPLMN currently serving the user equipment; After marking deletion of the configured NSSAI for the second VPLMN, receiving a configured NSSAI request at the user equipment during a subsequent registration procedure between the user equipment and the second VPLMN; receiving a second configured NSSAI for the second VPLMN as an initial NSSAI associated with the second VPLMN; as well as During the subsequent registration procedure initiated after deletion of the configured NSSAI for the second VPLMN having been marked, replacing the configured NSSAI for the second VPLMN stored at the user equipment with the second configured NSSAI for the second VPLMN received at the user equipment.

29. A method for managing network configuration information of a user equipment accessing a network, the method comprising: receiving, while the user equipment is currently served by a first visited public land mobile network (VPLMN), an indication as to whether a change has been made to subscription information associated with the user equipment and stored at a home public land mobile network (HPLMN) of the user equipment; Based on the indication indicating the change to the subscription information associated with the user equipment and stored at the HPLMN of the user equipment, marking deletion of configured network slice selection assistance information NSSAI stored locally at the user equipment for a second VPLMN different from the first VPLMN currently serving the user equipment; After marking deletion of the configured NSSAI for the second VPLMN, receiving a configured NSSAI request at the user equipment during a subsequent registration procedure between the user equipment and the second VPLMN; receiving a second configured NSSAI for the second VPLMN as an initial NSSAI associated with the second VPLMN; as well as During the subsequent registration procedure initiated after deletion of the configured NSSAI for the second VPLMN having been marked, replacing the configured NSSAI for the second VPLMN stored at the user equipment with the second configured NSSAI for the second VPLMN received at the user equipment.

Images