Managing vplmn configuration updates in ue due to home plmn configuration changes

Abstract

To provide methods and apparatuses, including computer program products, for managing configuration updates.SOLUTION: In some exemplary embodiments, there may be provided an apparatus including at least one processor and at least one memory including a computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to at least: receive an indication regarding whether a home network makes a change to previous configuration information for the apparatus; and delete, when the received indication represents the change, the previous configuration information stored at the apparatus. Related systems, methods, and articles of manufacture are also described.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS 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 incorporated herein by reference for all purposes.

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

[0003] As cellular systems, including fifth-generation (5G) systems, support an ever-increasing number of devices and services, including applications with a wide range of use cases and diverse needs in terms of bandwidth, latency, and reliability requirements, cellular systems need to prioritize resources across the wireless access network and core network (and / or, for example, across the control plane and user plane) to support differentiation between different services. Summary of the Invention [Problem to be solved by the invention]

[0004] Methods and apparatus, including computer program products, are provided for managing configuration updates. [Means for solving the problem]

[0005] In some example embodiments, an apparatus may be provided that includes at least one processor and at least one memory containing computer program code, the at least one memory and the computer program code, together with the at least one processor, configured to at least cause the apparatus to receive an indication as to whether a home network has made a change to previous configuration information of the apparatus, and to delete the previous configuration information stored in the apparatus when the received indication indicates that a change has been made.

[0006] In some variations, one or more of the features disclosed herein, including the following features, may be optionally included in any workable combination. The device may be further configured to at least receive configuration information including the indication. The deletion of previous configuration information includes deletion of previous configuration information associated with the home network and the visited network. The deletion of the previous configuration information may include at least one network slice identifier. The deletion may enable the device to obtain updated configuration information of at least the visited network and / or the home network currently serving the device. When an indication indicating a change associated with the home network is received, the device may further cause at least updated configuration information of at least one other visited network to replace the deleted previous configuration information. After obtaining the received configuration information, the device may at least wait to perform registration to obtain the updated configuration information until updated user equipment route and access selection policies are received. The device may further cause at least the configuration information of the visited network to be updated when an indication indicating a change associated with the home network is received, and may cause only the configuration information of the visited network to be updated when an indication indicating that a change associated with the home network has been made is not received. The indication may represent the home network indicating to the visited network currently serving the user equipment that a change in the home network should be taken into account in the visited network for configuring the device.

[0007] The above aspects and features may be implemented into a system, apparatus, method, and / or article, depending on the desired configuration. The details of one or more variations of the subject matter described herein are set forth in the accompanying drawings and the description below. Features and advantages of the subject matter described herein will be apparent from the description, drawings, and claims.

[0008] In the drawings, like labels are used to refer to the same or similar items within the drawings. [Brief explanation of the drawings]

[0009] [Figure 1] 1 illustrates an example of a portion of a 5G wireless network, according to some exemplary embodiments. [Figure 2] 1 illustrates an example process flow for a VPLMN configuration update, according to some exemplary embodiments. [Figure 3] 10 illustrates another example of a process flow for a VPLMN configuration update, according to some exemplary embodiments. [Figure 4] 1 illustrates an example of a network node, according to some exemplary embodiments. [Figure 5] 1 illustrates an example of an apparatus, according to some exemplary embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0010] 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 use with the VPLMN, for example, to enable access to one or more services available in the VPLMN. The UE's configuration information may be changed, for example, by a local decision in the VPLMN. Alternatively or additionally, the UE's configuration information may be changed, for example, by a change in the UE's subscription information in the HPLMN.

[0011] To further explain, a UE may access services in the HPLMN and / or VPLMN based on the UE's configuration information, which may be based on subscription information indicating authorized and / or available services. The UE's subscription information may change, for example, because the HPLMN makes or initiates a change 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(s) at the HPLMN. Thus, a change in the subscription information (which may be stored in a unified data management (UDM) node at the HPLMN) may trigger a change to the UE's configuration information for operation with the HPLMN and / or VPLMN.

[0012] The configuration information of the VPLMN and the HPLMN may have different values, and the mapping may be established by the VPLMN 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 separately update the configuration information, including subscription-related information, so that the UE has the latest VPLMN information. To further explain, the HPLMN's subscription information may change the QoS or another aspect of the network slice, or may completely change the fact that a particular slice can be accessed, or the subscription may include a new slice that the UE can use. This change may trigger a corresponding change in the configuration information for using the VPLMN.

[0013] For example, if the HPLMN configuration changes with respect to a change in the UE's subscription, an update of the VPLMN configuration for the UE's subscription may be necessary. While the UE is registered with the VPLMN, the HPLMN may push configuration information for the update to the VPLMN (the configuration information is stored in a network node such as a UDM (which, as described above, may act as a repository for storing this and other configuration and / or subscription information)). However, when the UE is visiting another VPLMN, although the new VPLMN may receive the UE's latest configuration or subscription information, because the VPLMN may not have state information for the UE's configuration or subscription information, the VPLMN may not be able to detect whether the information represents a change, and therefore the UE may not trigger the change or update.

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

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

[0016] Furthermore, when 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 it requires initial configuration information from the VPLMN (e.g., as if the UE were 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(s). In the case of a network slicing VPLMN configuration, the UE may, for example, remove the NSSAI configured for the PLMN and its mapping of the NSSAI configured for the HPLMN to the S-NSSAI, its mapping of the allowed NSSAIs and NSSAI configured for the HPLMN to the S-NSSAI, and any rejected S-NSSAIs for the PLMN. This deletion allows the UE to appear to the network as a UE requiring initial configuration when performing the registration procedure, and the network may provide the UE with the initial configuration when the UE accesses the VPLMN as part of the registration.

[0017] To further explain, if an indicator such as a cause code indicates that the update is due to a change in the HPLMN configuration, the UE may locally delete certain configuration information (e.g., the NSSAIs described above) such as network slicing configuration information for some, if not all, other VPLMNs, as previously described. Thus, when the UE performs registration procedures with these other VPLMNs, the UE may not send a request for NSSAI(s) but instead receive the VPLMN's configuration from the network. This received configuration information may include a slice identifier, such as an S-NSSAI, for use in the VPLMN to map to an HPLMN value.

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

[0019] FIG. 1 illustrates an example of a portion of a 5G wireless network 100, according to some exemplary embodiments.

[0020] The 5G wireless network 100 may include user equipment (UE) 150 configured to wirelessly couple to a radio access network (RAN) 152 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.

[0021] Network 100 may include a core network that may include an Access and Mobility Management Function (AMF) 154, a Visited Session Management Function (V-SMF) 156, a Visited Policy Control Function (v-PCF) 160, a Visited Network Slice Selection Function (v-NSSF) 164, and / or a Visited User Plane Function (V-UPF) 158. In the example of FIG. 1, devices 152-164 may be associated with a Visited Public Land Mobile Network (VPLMN) 166.

[0022] Network 100 and / or the core network may also include devices with functionality supporting a Home Public Land Mobile Network (HPLMN) 170. For example, these devices within 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, an Integrated 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.

[0023] 1 also shows service interfaces such as N1, N2, N3, N4, N6, N7, N11, N15, N18, N24, etc. The architecture, nodes (including the AMF, V-PCF, H-PCF, H-SMF, V-SMF, and other devices shown in FIG. 1), and service interfaces may be specified according to standards such as 3GPP TS 23.501, although other standards or proprietary interfaces may also be used.

[0024] A network slice refers to a logical network that provides specific network functions and network characteristics. A network slice may be considered as a logical end-to-end network that can be dynamically created, so that a given UE may access different network slices through the same radio access network (e.g., through the same radio interface). Network slices may provide different services and / or have different QoS needs / requirements. 3GPP TS 23.501, the system architecture for 5G systems, describes examples of network slices.

[0025] The UE's subscription information may indicate configuration information related to the quantity, QoS type, and / or identity of network slices. The UE's configuration information (provided by the network when registering with 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 indicates the expected behavior of the network slice in terms of capabilities and services; and / or b) slice differentiation information (SD), which is optional information that complements the slice / service type(s) to differentiate between multiple network slices of the same slice / service type.

[0026] 2 illustrates an example of a process 200, according to some example embodiments. The description of FIG. 2 also refers to FIG.

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

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

[0029] During registration with the network, UE 150 may register with another VPLMN, in which case when the indication represents a change in the HPLMN configuration, the UE may not send a request for NSSAI(s) and instead may receive configuration information from the network at 220, including network slicing configuration information for the VPLMN. This configuration information may include a slice identifier, such as an S-NSSAI, for use with the VPLMN and a mapping of that slice identifier to a value used in the HPLMN.

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

[0031] When the indication represents a local VPLMN configuration change, the UE may update stored configuration information, including network slicing information, of the serving VPLMN without affecting (e.g., deleting, updating, etc.) the configuration of other PLMNs (208, 230 - No). In some example embodiments, the UE may determine that the UE's configuration change is local based on not receiving an indication.

[0032] 3 illustrates an example of a process 300, according to some example embodiments. The description of FIG. 3 also refers to FIG.

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

[0034] 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 this 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 slicing subscription has changed.

[0035] If the UE is notified that the network slicing subscription information has changed, the UE may locally delete the network slicing information that the UE has for all other PLMNs, as described above (i.e., the UE may not send the requested NSSAI when registering with another PLMN, and the serving PLMN may update the UE configuration for the serving PLMN). The UE also updates its current PLMN information with any received values, and, if a URSP is required, waits for an updated URSP (UE Route and Access Selection Policy) before performing a new registration procedure.

[0036] In some example embodiments, if a subscribed S-NSSAI changes and the UE is unreachable at the time of the change, a Universal Data Repository (UDR) flag may be set in the PLMN to ensure that when the UE becomes reachable and the UE registers with the AMF in the PLMN, the AMF is notified that the subscription data contains an updated set of S-NSSAIs. As the AMF successfully updates the UE, the UE may be requested to register with an indication to the AMF that updates the UDM 178 and resets this flag.

[0037] To further explain, the S-NSSAI (which may be in the NSSAI configured for the HPLMN) may match the S-NSSAI subscribed for the UE when they are provided to the UE. When the subscribed S-NSSAI(s) are updated for a serving PLMN to which the UE 150 is registered (e.g., by removing an old S-NSSAI and / or adding a new S-NSSAI), the AMF 154 (via the base station 152 labeled “(R)AN”) may update the UE with a mapping relating to the NSSAI configured for the serving VPLMN, the allowed NSSAI, and / or the NSSAI configured for the HPLMN. However, as noted above, only the NSSAI configured for the current serving VPLMN is updated to match the new subscription information. Thus, if the UE accesses another VPLMN different from the HPLMN and the NSSAI configured for this VPLMN is stored, this information becomes outdated. The UE may store NSSAIs configured for several VPLMNs in addition to the currently serving VPLMN, so that the UE may not need to configure with the configured NSSAIs when returning to these VPLMNs.

[0038] The NSSAI configured for the serving PLMN includes an S-NSSAI value, which may be used by the serving PLMN and may be associated with a mapping of each S-NSSAI of the configured NSSAI to one or more corresponding S-NSSAI values ​​of the NSSAI configured for the HPLMN. Upon registration, when providing requested NSSAIs to the network, a UE of a given PLMN may include and use the S-NSSAI that applies to this PLMN (which may include and / or associate a mapping of each S-NSSAI of the requested NSSAI to the S-NSSAI of the NSSAI configured for the HPLMN that is part of the configured and / or authorized NSSAIs applicable to this PLMN). Upon successful completion of the UE registration procedure over a radio access type, the UE may obtain an authorized NSSAI for this access type, which may include one or more S-NSSAIs from the AMF (which may include associating a mapping from the authorized NSSAI to the NSSAI configured for the HPLMN). These S-NSSAIs are valid for the current registration area and access type provided by the AMF to which the UE is registered and may be used by the UE (up to a given number of simultaneous network slices or PDU sessions).

[0039] When a UE is provisioned with a configured NSSAI for a PLMN and / or an associated mapping from this configured NSSAI to an NSSAI configured for an HPLMN, both configured NSSAIs (and / or associated mappings, if any) may be stored in the UE until a newly configured NSSAI (and / or associated mappings) for this PLMN is provisioned to the UE.

[0040] When the UE is provisioned with a newly configured NSSAI for a PLMN (and / or a new associated mapping from this configured NSSAI to the configured NSSAI for the HPLMN), the UE may replace the stored (old) configured NSSAI for this PLMN with the newly configured NSSAI for this PLMN, as described above, the UE may delete any stored associated mapping from this old configured NSSAI for this PLMN to the configured NSSAI for the HPLMN and store the associated mapping from this new configured NSSAI to the configured NSSAI for the HPLMN, if any, and the UE may also delete stored allowed NSSAIs and associated mappings and rejected S-NSSAIs for this PLMN.

[0041] The UE may continue to store the received configured NSSAI for the PLMN and its associated mapping to the configured NSSAI for the HPLMN even when registering with another PLMN, although the number of configured NSSAIs and associated mappings that the UE continues to store for PLMNs other than the HPLMN may be up to the UE implementation.

[0042] When a VPLMN performs a configuration update for a UE registered with the VPLMN (e.g., due to a change in the subscribed S-NSSAI(s)), this may result in an update to the NSSAI configured for the serving PLMN and / or the associated mapping from the NSSAI configured for the serving PLMN to the NSSAI configured for the HPLMN. If the configuration update affects the S-NSSAI(s) of the currently authorized NSSAI, an update to the authorized NSSAI and / or the associated mapping from the authorized NSSAI to the NSSAI configured for the HPLMN may be performed.

[0043] When the configured NSSAI changes, the UE may only replace the NSSAI configured 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 NSSAIs for other PLMNs and the mapping of the configured NSSAI for the HPLMN to the S-NSSAI value also become invalid and outdated. However, since the AMFs of other PLMNs may not have received the updated configuration (and are not aware of this change either), these PLMNs do not trigger a change in the configured NSSAI due to the subscription change. This means that the UE will not be properly configured when returning to these PLMNs.

[0044] When the requested NSSAI is not included or the S-NSSAI is rejected by the PLMN, the AMF may update the UE slice configuration information of the PLMN.

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

[0046] As mentioned above, the UE may be configured by the HPLMN using network slice configuration information. For example, the HPLMN may push the configuration information to the UDM, and the configuration information may be provided to the UE via the AMF and the base station. The network slice configuration information may include one or more configured NSSAI(s). A configured NSSAI may apply to either one PLMN or all PLMNs that do not have a specific configured NSSAI (e.g., this can be an NSSAI that includes only an S-NSSAI with a standard value; see, e.g., 3GPP TS 23.501, section 5.15.2.1). At most one NSSAI is configured per PLMN. A PLMN's configured NSSAI may include an S-NSSAI with a standard value or a PLMN-specific value. The NSSAI configured for the serving PLMN may include an S-NSSAI value, which may be used by the serving PLMN and may be associated with a mapping from each S-NSSAI in the configured NSSAI to one or more corresponding S-NSSAI values ​​in the NSSAI configured for the HPLMN.

[0047] The S-NSSAI of the configured NSSAI for the HPLMN may match the S-NSSAI subscribed for the UE as described above when they are provided to the UE. If the subscribed S-NSSAI(s) are updated (e.g., remove old ones and / or add new ones) and are applicable to the serving PLMN to which the UE is 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 NSSAI configured for the HPLMN.

[0048] When the UE provides the network with the requested NSSAIs upon registration, for a given PLMN, the UE may only include and use the S-NSSAIs applicable to this PLMN (and possibly associated with a mapping from each S-NSSAI of the requested NSSAI to the S-NSSAI of the NSSAI configured for the HPLMN that is part of the configured and / or authorized NSSAIs applicable to this PLMN). Upon successful completion of the UE registration procedure via an access type, the UE may obtain the authorized NSSAIs for this access type, which may include one or more S-NSSAIs from the AMF associated with a mapping from the authorized NSSAIs to the NSSAIs configured for the HPLMN. These S-NSSAIs may be valid for the current registration area and access type provided by the AMF to which the UE 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 one or more rejected S-NSSAIs along with the cause and justification of the rejection from the AMF. The S-NSSAI may be rejected for the entire PLMN or for the current registration area.

[0049] The UE remains RM-REGISTERED in the PLMN regardless of access type, and the UE cannot retry registration to the rejected S-NSSAI for the entire PLMN until this rejected S-NSSAI is deleted. The UE remains RM-REGISTERED in the PLMN, but the UE cannot retry registration to the rejected S-NSSAI in its current registration area until it moves out of its current registration area.

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

[0051] The PLMN's authorized NSSAI and access type (and any associated mapping of this authorized NSSAI to an NSSAI configured for the HPLMN) may be stored in the UE when received. The UE may store this authorized NSSAI and any associated mapping of the authorized NSSAI to an NSSAI configured for the HPLMN (which may also be retained when the UE is turned off).

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

[0053] If received, a rejected S-NSSAI for the entire PLMN may be stored in the UE in RM-REGISTERED state with this PLMN regardless of the access type or until deleted.

[0054] If a rejected S-NSSAI is received for the current registration area, it may be stored in the UE in the RM-REGISTERED state until the UE moves out of the current registration area or until the UE is deleted.

[0055] One or more S-NSSAIs of 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 regarding how each S-NSSAI of the allowed NSSAIs corresponds to the S-NSSAI(s) of the NSSAIs configured for the HPLMN. This mapping information may be sufficient to enable the UE to associate an S-NSSAI with a corresponding S-NSSAI from the allowed NSSAIs according to the Network Slice Selection Policy (NSSP) of the URSP rules (e.g., see the rules defined in TS 23.503) for a given application.

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

[0057] When the HPLMN performs a configuration update of 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 NSSAI configured for the HPLMN. If the configuration update affects the S-NSSAI of a currently authorized NSSAI, there may also be an update to the authorized NSSAI and / or the associated mapping, if any, from the authorized NSSAI to the NSSAI configured for the HPLMN.

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

[0059] A UE whose configured NSSAI for the serving PLMN has been updated and which has deleted its stored allowed NSSAI may initiate a registration procedure to receive a new valid allowed NSSAI, as described above.

[0060] Figure 4 shows a block diagram of a network node 400, according to some example embodiments. The network node 400 may be configured to provide one or more network-side operations, for example, as described with respect to Figure 3. A mobile wireless network may also similarly have multiple network nodes 400. For example, a network node may be incorporated into one or more of the devices 152-180.

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

[0062] FIG. 5 illustrates a block diagram of the device 10, according to some example embodiments.

[0063] 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, as well as other network nodes (e.g., devices 152-184).

[0064] Device 10 may include at least one antenna 12 in communication with a transmitter 14 and a receiver 16. Alternatively, the transmit and receive antennas may be separate. Device 10 may also include a processor 20 configured to send and receive signals to and from each of the transmitter and receiver, and to control device functions. Processor 20 may be configured to control the functions of the transmitter and receiver by issuing control signals via electrical leads to the transmitter and receiver. Similarly, processor 20 may be configured to control other elements of device 10 by issuing control signals via electrical leads connecting processor 20 to other elements, such as a display or memory. Processor 20 may be embodied in a variety of ways, including, for example, a circuit, at least one processing core, one or more microprocessors with associated digital signal processor(s), one or more processors without associated digital signal processor(s), one or more coprocessors, 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. Thus, although shown as a single processor in FIG. 5, in some example embodiments, processor 20 may include multiple processors or processing cores.

[0065] Device 10 may be capable of operating with one or more air interface standards, communication protocols, modulation types, access types, etc. Signals transmitted and received by processor 20 may include signal information according to applicable cellular system air interface standards and / or any number of different wired or wireless network technologies, including, but not limited to, Institute of Electrical and Electronics Engineers (IEEE) 802.11, 802.16, 802.3, ADSL, DOCSIS, Wi-Fi, Wireless Local Access Network (WLAN) technologies, etc. Additionally, these signals may include voice data, user-generated data, user-requested data, etc.

[0066] For example, device 10 and / or the cellular modem therein may be capable of operating according to 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, device 10 may be capable of operating according to 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. Further, for example, device 10 may be capable of operating according to 2.5G wireless communication protocols General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), etc. Additionally, for example, device 10 may be capable of operating according to a 3G wireless communication protocol, 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. Device 10 may also be capable of operating according to a 3.9G wireless communication protocol, such as Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), etc. Additionally, for example, device 10 may be capable of operating according to a 4G wireless communication protocol, such as LTE Advanced, 5G, etc., as well as similar wireless communication protocols that may be subsequently developed.

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

[0068] Device 10 may also include a user interface, including, for example, earphone or speaker 24, ringer 22, microphone 26, display 28, a user input interface, etc., which may be operatively coupled to processor 20. Display 28 may include a touch-sensitive display, as described above, allowing a user to make selections, input values, etc., by touch and / or gestures. Processor 20 may also include user interface circuitry configured to control at least some functionality of one or more elements of the user interface, such as speaker 24, ringer 22, microphone 26, and display 28. Processor 20 and / or 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 memory accessible to processor 20, e.g., volatile memory 40, non-volatile memory 42, etc. Device 10 may include a battery for powering various circuitry associated with the mobile terminal, e.g., a circuit for providing mechanical vibration as a detectable output. The user input interface may include devices that allow the apparatus 20 to receive data, such as a keypad 30 (which may be a virtual keyboard presented on the display 28 or an externally connected keyboard) and / or other input devices.

[0069] As shown in FIG. 5 , device 10 may also include one or more mechanisms for sharing and / or obtaining data. For example, device 10 may include a short-range radio frequency (RF) transceiver and / or interrogator 64, such that data may be shared with and / or obtained from electronic devices according to RF technology. Device 10 may also include other short-range transceivers, such as an infrared (IR) transceiver 66, a Bluetooth™ (BT) transceiver 68 operating using Bluetooth™ wireless technology, a wireless universal serial bus (USB) transceiver 70, a Bluetooth™ low energy transceiver, a ZigBee transceiver, an ANT transceiver, a cellular device-to-device transceiver, a wireless local area link transceiver, and / or any other short-range wireless technology. Device 10, particularly the short-range transceiver, may be able to transmit data to and / or receive data from electronic devices that are near the device, e.g., within 10 meters. The apparatus 10, which includes a Wi-Fi or wireless local area network modem, may also be capable of transmitting and / or receiving data from electronic devices according to various wireless network technologies, including WLAN technologies such as 6LoWpan, Wi-Fi, Wi-Fi low power, IEEE802.11 technology, IEEE802.15 technology, IEEE802.16 technology, etc.

[0070] The device 10 may include memory, such as a subscriber identity module (SIM) 38, a removable user identity module (R-UIM), an eUICC, a UICC, etc., which may store information elements associated with a mobile subscriber. In addition to the SIM, the device 10 may include other removable and / or fixed memory. The device 10 may include volatile memory 40 and / or nonvolatile memory 42. For example, the volatile memory 40 may include random access memory (RAM), including dynamic and / or static RAM, on-chip or off-chip cache memory, etc. The 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, magnetic tape, optical disk drives, and / or media, non-volatile random access memory (NVRAM), etc. Like the volatile memory 40, the non-volatile memory 42 may include a cache area for temporary storage of data. At least a portion of the volatile and / or non-volatile memory may be embedded in the processor 20. The memory may store one or more software programs, instructions, information, data, etc. that may be used by the device to perform the operations disclosed herein. Alternatively or additionally, the device may be configured to cause the operations disclosed herein with respect to network nodes, including base stations / WLAN access points and UEs.

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

[0072] Some of the embodiments disclosed herein may be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic. The software, application logic, and / or hardware may reside, for example, on memory 40, controller 20, or electronic components. In some exemplary embodiments, the application logic, software, or instruction set is maintained on any one of various 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 transmit instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer or data processor circuitry; in the example shown in FIG. 5, the computer-readable medium may include a non-transitory computer-readable storage medium, 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.

[0073] Without limiting in any way the scope, interpretation, or application of the following claims, one or more technical effects of the example embodiments disclosed herein may be an improved UE configuration.

[0074] The subject matter described herein may be embodied in systems, devices, methods, and / or articles, depending on the desired configuration. For example, the base station and user equipment (or one or more components therein) and / or processes described herein may be implemented using one or more processors executing program code, application-specific integrated circuits (ASICs), digital signal processors (DSPs), embedded processors, field-programmable gate arrays (FPGAs), and / or combinations thereof. These various embodiments may include implementation in one or more computer programs executable and / or interpretable on a programmable system including at least one programmable processor, which may be special-purpose or general-purpose, coupled to a storage system, at least one input device, and at least one output device for transmitting and receiving data and instructions. These computer programs (also known as programs, software, software applications, applications, components, program code, or code) include machine instructions for the programmable processor and may be implemented in a high-level procedural and / or object-oriented programming language, and / or assembly / machine language. As used herein, the term "computer-readable medium" refers to any computer program product, machine-readable medium, computer-readable medium, apparatus, and / or device (e.g., magnetic disk, optical disk, memory, programmable logic circuit (PLD)) used to provide machine instructions and / or data to a programmable processor, including a machine-readable medium for receiving machine instructions. Similarly, systems are described herein that may include a processor and a memory coupled to the processor. The memory may contain one or more programs that cause the processor to perform one or more of the operations described herein.

[0075] While several variations have been described above, other modifications or additions are possible. In particular, additional features and / or variations may be provided in addition to those described herein. Furthermore, the above-described embodiments may be directed to various combinations and subcombinations of the disclosed features and / or combinations and subcombinations of several additional features disclosed above. Other embodiments may be within the scope of the following claims.

[0076] Where appropriate, different functions discussed herein may be performed in different orders and / or concurrently with one another. Furthermore, where appropriate, one or more of the above functions may be optional or combined. While various aspects of some of the embodiments are set forth in independent claims, other aspects of some of the embodiments include other combinations of features of the described embodiments and / or dependent claims with features of the independent claims, rather than just the combinations explicitly set forth in the claims. It should also be noted that while the above describes exemplary embodiments, these descriptions should not be construed in a limiting sense herein. Rather, there are several variations and modifications that can be made without departing from the scope of some of the embodiments, as defined in the appended claims. Other embodiments may be within the scope of the following claims. The term "based on" includes "based at least on." The use of the phrase "such as" means "for example, such as," unless otherwise specified.

Claims

1. at least one processor; at least one memory containing computer program code; wherein the at least one memory and the computer program code, together with the at least one processor, cause the device to include at least: causing the home network to receive an indication regarding whether to make a change to network slice configuration information stored in the home network for the device; When the received indication indicates that the change has been made, the device is configured to delete stored network slice configuration information. The device.

2. The device of claim 1 , wherein the network slice configuration information stored in the home network is different from the network slice configuration information stored in the device.

3. The device further comprises at least When the received indication indicates that the change has been made, delete network slice configuration information stored in the device that is associated with the home network and / or one or more visited networks.

3. The device according to claim 1, wherein the device is caused to:

4. The device further comprises at least receiving updated network slice configuration information including or together with the indication; The device according to any one of claims 1 to 3, wherein the device is caused to:

5. The device according to any one of claims 1 to 4, wherein the deletion of the network slice configuration information stored in the device includes deletion of the network slice configuration information associated with at least one of the home network or the visited network.

6. The device according to any one of claims 1 to 5, wherein the network slice configuration information includes at least one network slice identifier.

7. The device of claim 5 or 6, wherein the deletion enables the device to obtain updated network slice configuration information of at least the visited network and / or the home network currently serving the device.

8. The device further comprises at least receiving updated network slice configuration information of at least one other visited network to replace the deleted network slice configuration information when the indication representing the change associated with the home network is received. The device according to any one of claims 1 to 7, wherein the device is caused to:

9. The device further comprises at least After obtaining the received network slice configuration information, wait to perform registration to obtain the updated network slice configuration information until an updated user equipment route and access selection policy is received. The apparatus of claim 8 , configured to:

10. The device further comprises at least updating network slice configuration information of the visited network when the indication representing the change associated with the home network is received; When no indication is received that the change associated with the home network has been made, only update the network slice configuration information of the visited network. The device according to any one of claims 5 to 9, wherein the device is caused to:

11. 11. The device of claim 5, wherein the indication represents the home network indicating to the visited network currently serving the user equipment that the change in the home network will be taken into account for configuring the device in the visited network.

12. receiving, at the user equipment, an indication as to whether a home network will make a change to network slice configuration information stored in the home network for the user equipment; When the received indication indicates that the change has been made, deleting network slice configuration information stored in the user equipment; and A method comprising:

13. The method of claim 12 , wherein the network slice configuration information stored in the home network is different from the network slice configuration information stored in the user equipment.

14. 14. The method of claim 12, wherein deleting comprises deleting network slice configuration information stored in the user equipment associated with the home network and / or one or more visited networks when the received indication indicates that the change has been made.

15. receiving updated network slice configuration information including or together with the indication; The method of any one of claims 12 to 14, further comprising:

16. The method according to any one of claims 12 to 15, wherein the deleting the network slice configuration information includes deleting the network slice configuration information associated with at least one of the home network or the visited network.

17. The method according to any one of claims 12 to 16, wherein the network slice configuration information stored in the user equipment includes at least one network slice identifier.

18. The method according to any one of claims 12 to 17, wherein the deleting enables obtaining updated network slice configuration information of at least the visited network and / or the home network currently serving the user equipment.

19. receiving updated network slice configuration information of at least one other visited network to replace the deleted network slice configuration information when the indication representing the change associated with the home network is received. The method of any one of claims 12 to 18, further comprising:

20. After obtaining the received network slice configuration information, waiting to perform registration to obtain the updated network slice configuration information until an updated user equipment route and access selection policy is received.

20. The method of claim 19, further comprising:

21. updating the network slice configuration information stored in the user equipment for the visited network when the indication representing the change associated with the home network is received; and updating only the network slice configuration information stored in the user equipment for the visited network when no indication indicating that the change associated with the home network has been made is received; and The method of any one of claims 12 to 20, further comprising:

22. 22. The method of claim 12, wherein the indication represents the home network indicating to the visited network currently serving the user equipment that the change in the home network will be taken into account for configuring the user equipment in the visited network.

23. means for receiving, by a home network, an indication as to whether to make a change to network slice configuration information stored in the home network for the device; means for deleting network slice configuration information stored in the device when the received indication indicates that the change has been made; An apparatus comprising:

24. Apparatus according to claim 23, further comprising means for carrying out the method according to any one of claims 13 to 22.

25. A non-transitory computer readable medium containing program code that, when executed, receiving, at the user equipment, an indication from a home network regarding whether to make a change to network slice configuration information stored in the home network for the user equipment; When the received indication indicates that the change has been made, deleting network slice configuration information stored in the user equipment; and The non-transitory computer-readable medium causes an operation comprising:

26. at least one processor; at least one memory containing computer program code; wherein the at least one memory and the computer program code, together with the at least one processor, cause the device to include at least: determining whether a change has been made to network slice configuration information stored in a home network for the user equipment; and causing the user equipment to provide an indication as to whether the change has been made to the network slice configuration information stored in the home network for the user equipment. The device.

27. The at least one memory and the computer program code, together with the at least one processor, cause the device to include at least: configured to cause the user equipment to provide updated network slice configuration information together with the indication of the change to the network slice configuration information stored in the home network; 27. The apparatus of claim 26.

28. determining that a change has been made to network slice configuration information stored in a home network for the user equipment; providing an indication to the user equipment that the change has been made to the network slice configuration information stored in the home network for the user equipment; A method comprising:

29. providing updated network slice configuration information to the user equipment together with the indication of the change to the network slice configuration information stored in the home network; 30. The method of claim 28, further comprising:

30. means for determining that a change has been made to network slice configuration information stored in a home network for the user equipment; means for providing to the user equipment an indication regarding the change to the network slice configuration information stored in the home network for the user equipment; An apparatus comprising:

31. means for providing updated network slice configuration information to the user equipment together with the indication of the change to the network slice configuration information stored in the home network; 31. The apparatus of claim 30, further comprising:

32. A non-transitory computer readable medium containing program code that, when executed, determining that a change has been made to network slice configuration information stored in a home network for the user equipment; providing an indication to the user equipment regarding the change to the network slice configuration information stored in the home network for the user equipment; The non-transitory computer-readable medium causes an operation comprising:

33. The program code, when executed, providing updated network slice configuration information to the user equipment together with the indication of the change to the network slice configuration information stored in the home network; 33. The non-transitory computer-readable medium of claim 32, causing an operation comprising:

Images