Managing VPLMN configuration updates in UEs due to home PLMN configuration changes

Abstract

Methods and apparatus, including computer program products, are provided for managing configuration updates. In some example embodiments, an apparatus may be provided, the apparatus comprising: at least one processor; and at least one memory, the at least one memory comprising computer program code, the at least one memory and the computer program code are configured to, with the at least one processor, cause the device to at least: receive an indication as to whether a home network changes previous configuration information for the device; and deleting the previous configuration information stored at the device when the received indication indicates that the change has been made. Related systems, methods, and articles of manufacture are also described.

Description

[0001] This application is a Divisional of the patent application filed on May 21, 2019, as International Application No. PCT / IB2019 / 054205, entered into the Chinese national phase on January 5, 2021, as Chinese National Application No. 201980045321.4, and entitled “Managing VPLMN Configuration Updates in the UE Due to Home PLMN Configuration Changes.”

[0002] Cross Reference to Related Applications

[0003] 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

[0004] The subject matter described herein relates to wireless technology. BACKGROUND

[0005] As cellular systems, including Fifth Generation (5G) systems, support more and more devices and services, including applications with a wide range of use cases and diverse needs with respect to bandwidth, latency, and reliability requirements, the cellular systems can need to prioritize resources (and / or, for example, prioritize across control plane and user plane) across radio access networks and core networks to support differentiation among different services. SUMMARY

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

[0007] 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 made a change to 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.

[0008] In some variations, one or more of the features disclosed herein including the following features can optionally be included in any workable combination. The device can be further caused to at least: receive configuration information including the indication. The deleting the previous configuration information includes deleting previous configuration information associated with the home network and visited network. The deleting the previous configuration information can include at least one network slice identifier. The deleting can 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 can be further caused to at least: receive the updated configuration information for at least one other visited network to replace the deleted previous configuration information when the indication representing the change associated with the home network is received. The device can 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 route and access selection policy is received. The device can be further caused to at least: update configuration information for the visited network when the indication representing the change associated with the home network is received; and only update configuration information for the visited network when no indication representing the change associated with the home network is received. The indication can represent the home network indicating to the visited network currently serving a user equipment that the home network's change is to be considered in the visited network to configure the device.

[0009] 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 description below. According to the specification and drawings, and according to the claims, features and advantages of the subject matter described herein will become apparent. BRIEF DESCRIPTION OF DRAWINGS

[0010] In the drawings:

[0011] Figure 1 An example of a portion of a 5G wireless network is shown in accordance with some example embodiments;

[0012] Figure 2 An example of a process flow for VPLMN configuration update is shown in accordance with some example embodiments;

[0013] Figure 3 Another example of a process flow for VPLMN configuration update is shown in accordance with some example embodiments;

[0014] Figure 4 An example of a network node is shown in accordance with some example embodiments; and

[0015] Figure 5 An example of a device is shown in accordance with some example embodiments.

[0016] Like reference numerals are used to refer to like or similar items throughout the drawings. DETAILED DESCRIPTION

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

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

[0019] The VPLMN and HPLMN configuration information can have different values, and the VPLMN can establish mappings while the HPLMN is not aware of the values used locally within the VPLMN. For example, if the HPLMN changes the subscription for the UE, the VPLMN can need to independently update configuration information including subscription related information so that the UE has the latest VPLMN information. To further illustrate, the subscription information at the HPLMN can change the QoS or another aspect of a network slice, or the subscription information can completely change the fact that a certain slice can be accessible, or the subscription can include a new slice that the UE can use. Such a change can trigger a corresponding change in configuration information for use by the VPLMN.

[0020] When the HPLMN configuration changes, e.g., with respect to a subscription of the UE, the VPLMN configuration with respect to the UE's subscription can need to be updated. When the UE is registered in the VPLMN, the HPLMN can push updated configuration information (as mentioned, stored at network nodes such as the UDM, which can serve as a repository for storing such configuration information and other configuration and / or subscription information) to the VPLMN. However, when the UE is visiting another VPLMN, the new VPLMN can receive the latest configuration or subscription information for the UE, but the VPLMN can not be able to detect whether the information represents a change, as the VPLMN can not have state information about the UE's configuration or subscription information, so the UE can not trigger a change or update.

[0021] 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 can also receive an indication, such as a cause code, about the update. If the update is due to a local change by the VPLMN, the UE can update the VPLMN related information that the UE maintains at the UE.

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

[0023] Further, in the case where the indicator, such as the cause code, indicates that the update is due to a change in the HPLMN configuration, when the UE visits other VPLMNs, the UE can operate as if the UE needs initial configuration information from the VPLMN, e.g., initial configuration information as if the UE is visiting the VPLMN for the first time. For example, the UE can delete (e.g., remove, reset, etc.) all UE configuration information for the VPLMN. For the case of network slice VPLMN configuration, the UE may, for example, remove the configured NSSAI for the PLMN and its mapping to S-NSSAIs in the configured NSSAI for the HPLMN, the allowed NSSAI and its mapping to S-NSSAIs in the configured NSSAI for the HPLMN, any rejected S-NSSAI in the PLMN. Such deletion can result in the UE appearing to the network as a UE that needs initial configuration when performing a registration procedure, and cause the network to provide initial configuration to the UE when the UE visits the VPLMN as part of a registration.

[0024] To further illustrate, when the indicator (such as a cause code) indicates that the update is due to a change in HPLMN configuration, as mentioned, the UE can 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 can not send a request for NSSAI, but can receive a configuration for the VPLMN from the network. Such received configuration information can include slice identifiers, such as S-NSSAI, for use at the VPLMN and mapped to HPLMN values.

[0025] In some example embodiments, the UE can wait for an updated policy from the network, such as a URSP (UE Route and Access Selection Policy), in the serving VPLMN before the UE performs a new registration procedure, as the URSP can also change when the UE’s subscription to S-NSSAI has changed.

[0026] Figure 1 An example of a portion of a 5G wireless network 100 is shown in accordance with some example embodiments.

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

[0028] The network 100 can include a core network that can 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 Figure 1 In examples, the apparatuses 152-164 can be associated with a visited public land mobile network (VPLMN) 166.

[0029] The network 100 and / or the core network can also include apparatuses with functionality to support a home public land mobile network (HPLMN) 170. For example, these apparatuses in the HPLMN 170 can include apparatuses and corresponding functionality for “home” wireless local area network (WLAN) access, offload, and / or non-3GPP access. These apparatuses can include a home SMF 172, a home PCF 174, a home NSSF 176, a 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.

[0030] Figure 1 Service interfaces are also shown, such as N1, N2, N3, N4, N6, N7, N11, N15, N18, N24, and so on. The architecture, nodes (including AMF, V-PCF, H-PCF, H-SMF, and V-SMF, as well as other devices shown at 200) and service interfaces can be defined according to standards such as 3GPP TS 23.501, but other standards as well as proprietary interfaces can be used. Figure 1

[0031] A network slice refers to a logical network that provides specific network capabilities and network characteristics. A network slice can be viewed as a logical end-to-end network that can be created dynamically, such 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 the 5G System) describes examples of network slices.

[0032] Subscription information of a UE can indicate configuration information related to the number of network slices, QoS types, and / or identities. Configuration information of a UE (provided by the network when registered in a PLMN such as a VPLMN and / or HPLMN) can include one or more network slice identifiers, such as one or more Single-NSSAIs (S-NSSAIs). An S-NSSAI can consist of a) a Slice / Service Type (SST), which refers to the intended network slice behavior in terms of features and services, and / or b) a Slice Differentiator (SD), which is optional information that complements the Slice / Service Type to differentiate among multiple network slices of the same Slice / Service Type.

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

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

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

[0036] When the indication represents an HPLMN configuration change, during registration with the network, the UE 150 can register in another VPLMN, in which case the UE can not send a request for NSSAI, but instead receive configuration information from the network at 220 that includes network slice configuration information for the VPLMN. This configuration information can include slice identifiers, such as S-NSSAIs, for use at the VPLMN and their mapping to values for use in the HPLMN.

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

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

[0039] Figure 3 An example of a process 300 is shown in accordance with some example embodiments. Figure 3 The description of Figure 1 .

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

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

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

[0043] In some example embodiments, when the subscribed S-NSSAIs change and when the UE is not reachable at the time of the change, a Universal Data Repository (UDR) flag can be set in the HPLMN to ensure that when the UE registers with the AMF in a PLMN while 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 can be requested to register with the AMF at the indication to reset this flag to update the UDM 178.

[0044] To further illustrate, an S-NSSAI, which can be in the configured NSSAI for the HPLMN, can match the UE's subscribed S-NSSAIs when it is provided to the UE. When the subscribed S-NSSAIs for the PLMN of a service in which the UE 150 is registered are updated (e.g., by removing old S-NSSAIs and / or adding new S-NSSAIs), the AMF 154 can update the UE (via the base station 152 labeled "(R)AN") with the configured NSSAI, allowed NSSAI, and / or mappings associated with the configured NSSAI for the HPLMN of the service's VPLMN. But as mentioned above, only the configured NSSAI for the VPLMN of the current service will be updated to match the new subscription information. Thus, if the UE accesses another VPLMN different from the HPLMN and it has a configured NSSAI stored for this VPLMN, this information will be outdated. The UE can store configured NSSAIs for multiple VPLMNs in addition to the VPLMN of the current service, so that when returning to these VPLMNs, the UE can not need to be configured with the configured NSSAI.

[0045] The configured NSSAI for a PLMN includes S-NSSAI values that are applicable in the PLMN for the service, and can 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 at registration, a UE in a given PLMN can include and use the S-NSSAI applicable to this PLMN (this can include a mapping of each S-NSSAI in the requested NSSAI to S-NSSAI in the configured NSSAI for the HPLMN as part of the configured and / or allowed NSSAI applicable to this PLMN, and / or associated with this mapping). After successful completion of the registration procedure for the UE for a radio access type, the UE can obtain from the AMF the allowed NSSAI for this access type, which includes one or more S-NSSAI (this can include being associated with a mapping of the allowed NSSAI to the configured NSSAI for the HPLMN). These S-NSSAI are valid for the current registration area and access type provided by the AMF to which the UE has registered, and can be used by the UE (up to a given number of simultaneous network slices or PDU sessions).

[0046] 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 present) can all be stored in the UE until a new configured NSSAI (and / or associated mapping) for this PLMN is provided in the UE.

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

[0048] The UE can keep stored the received configured NSSAI for a PLMN and the associated mapping to the configured NSSAI for the HPLMN even when registered in another PLMN. However, the number of configured NSSAI and associated mapping that will be kept stored in the UE for PLMNs other than the HPLMN can depend on the UE implementation.

[0049] If the VPLMN performs a configuration update for a UE registered in the VPLMN (e.g. due to a change of subscription of S-NSSAIs), this can result in an update of 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 impacts S-NSSAIs in the currently allowed NSSAI, an update of the allowed NSSAI and / or the associated mapping of the allowed NSSAI to the configured NSSAI for the HPLMN can be implemented.

[0050] When the configured NSSAI changes, the UE can only replace the configured NSSAI for the current PLMN. This is the correct behavior when the change is due to a VPLMN decision of the VPLMN. However, when the change is due to a change of subscription, the stored configured NSSAI for other PLMNs and the mapping to the S-NSSAI values in the configured NSSAI for the HPLMN also become invalid and outdated. However, the AMFs in the other PLMNs can not receive the updated configuration (the other PLMNs are also not aware of this change), so these PLMNs will not trigger a change of the configured NSSAI due to the change of subscription. This means that when returning to these PLMNs, the UE will not be correctly configured.

[0051] The AMF can update the UE slice configuration information for a PLMN when the requested NSSAI is not included or when an S-NSSAI is rejected in the PLMN.

[0052] When the UE does not have a configuration for the VPLMN, the UE can not include a requested NSSAI in the VPLMN registration request. The VPLMN can then configure the UE with a configured NSSAI for the PLMN, if applicable. When the PLMN updates the configured NSSAI for the UE, as mentioned, the PLMN can 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 HPLMN configuration. If the change is due to a HPLMN configuration change, (1) the UE can locally delete its network slice configuration information it has for all other PLMNs, and can wait for an updated URSP before performing a new registration procedure, as the URSP is also changed when the UE's subscription to S-NSSAIs changes. In addition, if the change is only due to a locally served PLMN, the UE can update the information for the serving PLMN without affecting the configuration for other PLMNs.

[0053] As mentioned, a UE can be configured with network slice configuration information by the HPLMN. For example, the HPLMN can push configuration information to the UDM, which can be provided to the UE via the AMF and base station. The network slice configuration information can include one or more configured NSSAIs. A configured NSSAI can be applicable to one PLMN or to all PLMNs without a specific configured NSSAI (e.g., this can be feasible for a NSSAI containing only S-NSSAIs with standard values, see, e.g., 3GPP TS 23.501, clause 5.15.2.1). There is at most one configured NSSAI per PLMN. The configured NSSAI for a PLMN can include S-NSSAIs with standard values or PLMN-specific values. The configured NSSAI for a serving PLMN can include S-NSSAI values that can be used in the serving PLMN, and can 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.

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

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

[0056] When the UE remains RM-REGISTERED in a PLMN regardless of the access type, the UE can not re-attempt registration for a rejected S-NSSAI throughout the PLMN until this rejected S-NSSAI is deleted. When the UE remains RM-REGISTERED in a PLMN, the UE can 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.

[0057] The UE can store (S-)NSSAI as follows. When a configured NSSAI for a PLMN and / or an associated mapping of this configured NSSAI to a configured NSSAI for the HPLMN is provided to the UE, the configured NSSAI (and / or the associated mapping, if present) can be stored in the UE until a new configured NSSAI for this PLMN and / or a new associated mapping of this configured NSSAI to a configured NSSAI for the HPLMN 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 the HPLMN is provided, or when removal of the configuration for a PLMN is requested due to HPLMN configuration change, the UE can replace any stored (e.g., old) configured NSSAI for this PLMN with the new configured NSSAI for this PLMN, if applicable; and the UE can delete any stored associated mapping of such old configured NSSAI for this PLMN to a configured NSSAI for the HPLMN, and store the associated mapping of such new configured NSSAI to a configured NSSAI for the HPLMN, if present and applicable; and the UE can delete any stored allowed NSSAI and associated mapping and rejected S-NSSAIs for this PLMN;

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

[0059] The UE can persistently store allowed NSSAI and any associated mapping of allowed NSSAI to a configured NSSAI for the HPLMN.

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

[0061] If received, the S-NSSAIs rejected in a current registration area can be stored in the UE while being RM-REGISTERED until the UE moves out of the current registration area, or until the S-NSSAIs are deleted.

[0062] One or more S-NSSAIs in the allowed NSSAI provided to the UE can have a value that is not part of the slice configuration information for the UE of the serving PLMN. In this case, the allowed NSSAI is associated with mapping information on how each S-NSSAI in the allowed NSSAI corresponds to an S-NSSAI of the configured NSSAI for the HPLMN. This mapping information can be sufficient to allow the UE to associate S-NSSAIs from the allowed NSSAI with corresponding S-NSSAIs from the allowed NSSAI for a given application according to the network slice selection policy (NSSP) of the URSP rules (see, e.g., the rules defined in TS 23.503).

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

[0064] If the HPLMN performs a configuration update for a UE registered in the HPLMN (e.g., due to a change of subscribed S-NSSAIs), this can result in an update of the configured NSSAI for the HPLMN. If the configuration update affects S-NSSAIs in the current allowed NSSAI, an update of the allowed NSSAI and / or the associated mapping (if present) of the allowed NSSAI to the configured NSSAI for the HPLMN can also be feasible.

[0065] If the VPLMN performs a configuration update for a UE registered in the VPLMN (e.g., due to a change of subscribed S-NSSAIs), this can result in an update of 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 S-NSSAIs in the current allowed NSSAI, an update of the allowed NSSAI and / or the associated mapping of the allowed NSSAI to the configured NSSAI for the HPLMN can also be feasible.

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

[0067] Figure 4 A block diagram of a network node 400 is shown in accordance with some example embodiments. For example, the network node 400 can be configured to provide one or more network-side operations as described in relation to Figure 3 Furthermore, a mobile wireless network can also have multiple network nodes 400. For example, a network node can be incorporated into one or more of the apparatuses 152-180.

[0068] In accordance with some example embodiments, the network node 400 can include a network interface 402, a processor 420, and a memory 404. The network interface 402 can include wired and / or wireless transceivers to enable access to other nodes including base stations, apparatuses 152-180, the Internet, and / or other nodes. The memory 404 can include volatile and / or nonvolatile memory that includes program code, which when executed by the at least one processor 420, among other things, provides processes disclosed herein including processes 200, 300, 400, etc.

[0069] Figure 5 A block diagram of an apparatus 10 is shown in accordance with some example embodiments.

[0070] The apparatus 10 can represent a user equipment such as user equipment 150. The apparatus 10 or portions therein can be implemented in other network nodes including base stations / WLAN access points as well as other network nodes (e.g., apparatuses 152-184).

[0071] The apparatus 10 can include at least one antenna 12 in communication with a transmitter 14 and a receiver 16. Alternatively, the transmitting and receiving antennas can be separate. The apparatus 10 can also include a processor 20 configured to provide signals to and receive signals from the transmitter and receiver, respectively, and to control the functioning of the apparatus. The processor 20 can be configured to control the functioning of the transmitter and receiver by effecting control signaling through electrical leads to the transmitter and receiver. Likewise, the processor 20 can be configured to control other elements of the apparatus 10 by effecting control signaling through electrical leads connecting the processor 20 to the other elements, such as a display or a memory. The processor 20 may, for example, be embodied in a variety of manners, including a circuit, at least one processing core, one or more microprocessors, one or more processors with accompanying digital signal processors, one or more co-processors, one or more Figure 5The processor 20 is shown as a single processor, but in some example embodiments, the processor 20 can comprise multiple processors or processing cores.

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

[0073] For example, the device 10 and / or cellular modem(s) therein can be capable of operating under different 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 can be capable of operating under 2G wireless communication protocols IS-136, Time Division Multiple Access TDMA, Global System for Mobile communication, GSM, IS-95, Code Division Multiple Access CDMA, etc. Also, for example, the device 10 can be capable of operating under 2.5G wireless communication protocols General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), etc. Further, for example, the device 10 can be capable of operating under 3G wireless communication protocols such as Universal Mobile Telecommunication 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 can additionally be capable of operating under 3.9G wireless communication protocols such as Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), etc. Further, for example, the device 10 can be capable of operating under 4G wireless communication protocols such as LTE Advanced, 5G, etc., as well as similar wireless communication protocols subsequently developed.

[0074] 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.

[0075] 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.

[0076] 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, a wireless universal serial bus (USB) transceiver 70, a Bluetooth TM The short-range transceiver can be a Bluetooth™ (BT) transceiver 68, a wireless universal serial bus (USB) transceiver 70, a Bluetooth

[0077] The device 10 can include memory, such as a user identity module (SIM) 38 that can store information elements related to a mobile subscriber, a removable user identity module (R-UIM), an eUICC, a UICC, and / or the like. In addition to the SIM, the device 10 can include other removable and / or fixed memory. The device 10 can include volatile memory 40 and / or non-volatile memory 42. For example, volatile memory 40 can include random access memory (RAM) including dynamic and / or static RAM, on- and / or off-chip cache memory, and / or the like. Non-volatile, memory 42, which can be embedded and / or removable, can include, for example, read-only memory, flash memory, magnetic storage, for example, a hard disk, an optical disk drive and / or media, non-volatile random access memory (NVRAM), and / or the like. Like volatile memory 40, non-volatile memory 42 can include a cache area for temporary storage of data. At least a portion of the volatile and / or non-volatile memory can be embedded in the processor 20. The memory can store one or more software programs, instructions, pieces of information, data, and / or the like which can be used by the device in

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

[0079] Some of the example embodiments disclosed herein can be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic. The software, application logic, and / or hardware can reside on memory 40, control device 20, or electronic components of the device. In some example embodiments, the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media. In the context of this document, a "computer-readable medium" can be any non-transitory medium that can contain, store, communicate, propagate or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer-readable medium can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. Figure 5 An example is shown at where the computer-readable medium can include a non-transitory computer-readable storage medium that can be any medium that can contain or store the program for use by or in connection with the instruction execution system, apparatus, or device, such as a computer.

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

[0081] The subject matter described herein can be embodied in systems, apparatus, methods, and / or articles depending on the desired configuration. For instance, the base stations and user devices (or one or more components thereof) and / or processes described herein can be implemented using one or more of the following: a processor executing program code, an application-specific integrated circuit (ASIC), a digital signal processor (DSP), an embedded processor, a field-programmable gate array (FPGA), and / or combinations thereof. These various implementations can include implementations in one or more computer programs that can execute on a programmable system including at least one programmable processor coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device. These computer programs (also known as programs, software, software applications, applications, components, program code, or code) include machine instructions for the programmable processor, and can be implemented in a high-level procedural and / or object-oriented programming language, and / or in assembly / machine language. As used herein, the term "computer-readable medium" refers to any computer program product, machine-readable medium, computer-readable storage medium, device, and / or means for providing machine instructions and / or data to a programmable processor (e.g., a magnetic disk, a magneto-optical disk, a solid state drive, a memory, a programmable logic device (PLD)), including a machine-readable medium that receives machine instructions. Similarly, it is also described herein that a system can include a processor and a memory coupled to the processor. The memory can include one or more programs that cause the processor to perform one or more of the operations described herein.

[0082] Although several modifications and additions have been described above, other modifications and additions can be possible. Specifically, other features and / or variations can be provided in addition to those set forth herein. Moreover, the implementations described above can be directed to various combinations and sub-combinations of the disclosed features and / or combinations and sub-combinations of several other features disclosed above. Other implementations can be within the scope of the claims.

[0083] The various functions discussed herein can be performed in different orders and / or concurrently than described herein. Additionally, if desired, one or more of the functions described above can be optional or combined. Although various aspects of some of the embodiments are set forth in the independent claims, other aspects of some of the embodiments include further combinations of features from the described embodiments and / or from the dependent claims with the features of the independent claims, and not just those combinations explicitly set forth in the claims. It is also noted herein that while the above describes example embodiments, it is not intended to limit the scope of some of the embodiments as set forth in the appended claims. Rather, the intent is to cover all modifications and variations of some of the embodiments that fall within the scope of the claimed some of the embodiments as defined by the following claims. The term "based on" includes "based at least on." The use of the phrase "such as" indicates "such as, for example."

Claims

1. An apparatus, the apparatus 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 apparatus at least to: receive an indication about whether a change to network slice configuration information stored at a home network for the apparatus is made by the home network; and delete network slice configuration information stored at the apparatus when the received indication represents the change.

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

3. The apparatus of any one of claims 1 or 2, wherein the apparatus is further caused to at least: delete network slice configuration information stored at the apparatus associated with the home network and / or one or more visited networks when the received indication represents the change.

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

5. The device of any of claims 1 to 4, wherein deleting the network slice configuration information stored at the device comprises: delete the network slice configuration information associated with at least one of the home network or a visited network.

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

7. The apparatus of any one of claims 5 or 6, wherein the deletion enables the apparatus to obtain updated network slice configuration information for at least the visited network currently serving the apparatus and / or the home network.

8. The apparatus of any one of claims 1 to 7, wherein the apparatus is further caused to at least: receive updated network slice configuration information for 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.

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

10. The apparatus of any one of claims 5 to 9, wherein the apparatus is further caused to at least: update network slice configuration information for the visited network when the indication representing the change associated with the home network is received; and only update network slice configuration information for the visited network when no indication representing the change associated with the home network is received.

11. The apparatus of any one of claims 5 to 10, wherein the indication represents that the home network indicates to the visited network currently serving the user equipment that the apparatus is to be configured in the visited network taking into account the change of the home network.

12. A method comprising: receiving, at a user equipment, an indication of whether a home network changed network slice configuration information stored at the home network for the user equipment; and deleting, when the received indication represents the change, network slice configuration information stored at the user equipment.

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

14. The method of any one of claims 12 or 13, wherein deleting comprises: deleting, when the received indication represents the change, network slice configuration information stored at the user equipment associated with the home network and / or one or more visited networks.

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

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

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

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

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

20. The method of claim 19, further comprising: 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 routing and access selection policy is received.

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

22. The method of any of claims 12 to 21, wherein the indication represents the home network indicating to the visited network currently serving the user equipment that the change of the home network is to be considered in configuring the user equipment in the visited network.

23. An apparatus comprising: means for receiving an indication of whether a home network changed network slice configuration information stored at the home network for the apparatus; and means for deleting network slice configuration information stored at the device when the received indication represents the change.

24. The device of claim 23, further comprising means for performing the method of any one of claims 13-22.

25. A non-transitory computer-readable medium comprising program code that, when executed, causes operations comprising: receiving, at a user equipment, an indication of whether a change was made to network slice configuration information stored at a home network for the user equipment; and when the received indication represents the change, deleting network slice configuration information stored at the user equipment.

26. A device 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 at least to: determine whether a change was made to network slice configuration information stored at a home network for a user equipment; and provide an indication to the user equipment of whether the change was made to the network slice configuration information stored at the home network for the user equipment.

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

28. A method comprising: determining that a change was made to network slice configuration information stored at a home network for a user equipment; and providing an indication to the user equipment of the change to the network slice configuration information stored at the home network for the user equipment.

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

30. A device comprising: means for determining that a change was made to network slice configuration information stored at a home network for a user equipment; and means for providing an indication to the user equipment of the change to the network slice configuration information stored at the home network for the user equipment.

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

32. A non-transitory computer-readable medium comprising program code that, when executed, causes operations comprising: determining that a change was made to network slice configuration information stored at a home network for a user equipment; and providing an indication to the user equipment of the change to the network slice configuration information stored at the home network for the user equipment. determining that a change has been made to network slice configuration information stored at a home network for a user equipment; and providing an indication to the user equipment of the change to the network slice configuration information stored at the home network for the user equipment.

33. The non-transitory computer-readable medium of claim 32, wherein the program code, when executed, causes performance of operations comprising: providing updated network slice configuration information to the user equipment with the indication of the change to the network slice configuration information stored at the home network.

Images