Adjustment of user device behavior controlled by the home public land mobility network.

Abstract

A method, system, apparatus, and computer program product for configuring a user equipment (UE) for operator control of UE behavior in registering and deregistering with a network slice and establishing and releasing PDU sessions in a communication system. A network entity may receive a registration request message from the UE. The network entity may determine one or more public land mobile network (PLMN) types or PLMN identities and associated UE behavior policy versions based at least in part on the registration request message. The network entity may request the UE behavior policies. The network entity may provide UE configuration update information to the UE.

Description

Technical Field

[0001] This application incorporates PCT Application No. PCT / EP2021 / 066092, filed on Jun. 15, 2021, which claims priority to U.S. Provisional Patent Application No. 63 / 048,818, filed on Jul. 7, 2020, the entire disclosures of both applications being incorporated herein by reference.

Background Art

[0002] This section presents aspects that may be useful for a better understanding of the present invention. Thus, the description of this section should be read from this perspective and should not be construed as an admission or understanding of what is included or not included in the prior art.

[0003] The fourth generation (4G) wireless mobile telecommunications technology, also known as Long Term Evolution (LTE) technology, is designed to provide high data rate and large capacity mobile multimedia, particularly for human interaction. Next generation or fifth generation (5G) technology is intended to be used not only for human interaction but also for machine-type communication in the so-called Internet of Things (IoT) network.

[0004] The 3rd Generation Partnership Project (3GPP) 5G technology is a next generation wireless system and network architecture that can provide ultra-wideband and ultra-robust, low latency connectivity. 5G technology improves various telecommunications services provided to end users and helps support large-scale broadband that provides on-demand gigabytes per second bandwidth for both uplink and downlink transmissions. Next generation systems utilizing 5G architecture utilize virtualized radio access network (RAN) functions and core network functions.

[0005] In 5G networks, network slicing is a concept for running multiple logical networks as virtually independent business operations on a common physical infrastructure. Network slices are considered independent, virtualized, end-to-end networks. Currently, standardization efforts are underway to simplify how network slices are defined, how user devices are registered and unregistered to network slices, and how protocol data unit (PDU) sessions are authorized to network slices. However, under current 3GPP specifications, enforcing such activities is complex and typically dependent on user devices, meaning that network operators have little control over user device behavior during such activities. [Overview of the project] [Means for solving the problem]

[0006] According to exemplary embodiments, methods, apparatus, and computer program products are provided for providing operator control of user device behavior in registering with and unregistering from network slices, and in establishing and releasing PDU sessions in a communication system. Specific UE behavior policies regarding the UE can be determined by the network entity.

[0007] In one exemplary embodiment, a method is provided in which a network entity of a communication system receives a registration request message from a user device (UE). The method may further include, at least in part, determining i) one or more PLMN (public land mobile network) types or PLMN identities associated with UE behavior relating to the UE, and ii) versions of the associated UE behavior policies for each of the one or more PLMN types or PLMN identities, based at least in part on the registration request message. The method may further include, in response to the request for a UE behavior policy, requesting a UE behavior policy from another network entity based at least in part on i) one or more PLMN types or PLMN identities, or ii) versions of the associated UE behavior policies. The method may further include providing the UE with UE configuration information in a registration approval message, wherein the UE configuration information includes an indication of one or more PLMN types or PLMN identities and versions of the associated UE behavior policies.

[0008] In some embodiments, the method provides a UE with UE configuration update information when a PLMN type or PLMN identity indicates a visited public land mobile network (VPLMN) type or VPLMN identity and a UE behavior policy allows the corresponding VPLMN to modify one or more aspects of the UE behavior policy, the UE configuration update information may further include an indication of an updated version of the relevant UE behavior policy relating to the VPLMN or VPLMN identity.

[0009] In some embodiments, the method may further include subscribing to subscription information updates for UE behavior policies associated with a UE. In some embodiments, the method further includes receiving subscription information updates to UE behavior policies associated with a UE. In some embodiments, the method further includes providing UE configuration update information to a UE, wherein the UE configuration update information includes an indication of an updated version of the associated UE behavior policy. In some embodiments, subscription information to a UE behavior policy is received when a policy control function updates the UE behavior policy.

[0010] In some embodiments, the method further includes receiving one or more authorization flags, the one or more of which indicate whether the visited PLMN, or the PLMN identity of the visited PLMN, is authorized to modify the UE behavior policy with respect to one or more of the components of the UE behavior policy.

[0011] In some embodiments, the PLMN is at least one of the home public land mobile network (HPLMN) type or the visited public land mobile network (VPLMN) type. In some embodiments, the registration request message further includes information indicating that the UE supports or requires the configuration of a UE behavior policy.

[0012] In one exemplary embodiment, a device is provided in a network entity of a communication system that includes means for receiving a registration request message from a user device (UE). The device may further include means for determining, at least in part, i) one or more PLMN (Public Land Mobile Network) types or PLMN identities associated with UE behavior relating to the UE, and ii) versions of the associated UE behavior policies for each of the one or more PLMN types or PLMN identities, based at least in part on the registration request message. The device may further include means for requesting a UE behavior policy from another network entity in response to a request for a UE behavior policy, based at least in part on i) one or more PLMN types or PLMN identities, or ii) versions of the associated UE behavior policies. The device may further include means for providing the UE with UE configuration information in a registration approval message, wherein the UE configuration information includes an indication of one or more PLMN types or PLMN identities and versions of the associated UE behavior policies.

[0013] In some embodiments, the device provides means for providing UE configuration update information to a UE when a PLMN type or PLMN identity indicates a visited public land mobile network (VPLMN) type or VPLMN identity, and a UE behavior policy allows a corresponding VPLMN to modify one or more aspects of the UE behavior policy, wherein the UE configuration update information includes an indication of an updated version of the relevant UE behavior policy relating to the VPLMN or VPLMN identity.

[0014] In some embodiments, the device may further include means for subscribing to subscription information updates for UE behavior policies associated with a UE. In some embodiments, the method further includes receiving subscription information updates to UE behavior policies associated with a UE. In some embodiments, the device may further include means for providing UE configuration update information to a UE, wherein the UE configuration update information includes an indication of an updated version of the associated UE behavior policy. In some embodiments, subscription information to a UE behavior policy is received when a policy control function updates the UE behavior policy.

[0015] In some embodiments, the device further includes means for receiving one or more authorization flags, the one or more authorization flags indicating whether the visited PLMN, or the PLMN identity of the visited PLMN, is authorized to modify the UE behavior policy with respect to one or more components of the UE behavior policy.

[0016] In some embodiments, the PLMN is at least one of a Home Public Land Mobile Network (HPLMN) type or a Visited Public Land Mobile Network (VPLMN) type. In some embodiments, the registration request message further includes information indicating that the UE supports or requires the configuration of a UE behavior policy.

[0017] In another exemplary embodiment, a device can be provided comprising at least one processor and at least one memory containing computer program code for one or more programs, wherein at least one memory and computer program code are configured by at least one processor to cause the device to receive registration request messages from user equipment (UEs) in at least one network entity of a communication system. The device may further include computer program code configured by at least one processor to cause the device to determine, at least, based at least in part on the registration request message, i) one or more PLMN (Public Land Mobile Network) types or PLMN identities associated with UE behavior relating to the UE, and ii) versions of the associated UE behavior policies for each of the one or more PLMN types or PLMN identities. The device may further include computer program code configured by at least one processor to cause the device to request UE behavior policies from another network entity in response to a request for a UE behavior policy, at least, based at least in part on i) one or more PLMN types or PLMN identities, or ii) at least one of the associated UE behavior policy versions. The device may include computer program code configured by at least one processor to cause the device to provide UE configuration information to at least the UE in a registration approval message, and the UE configuration information may include an indication of one or more PLMN types or PLMN identities and the respective versions of the associated UE behavior policy.

[0018] In some embodiments, the device may include, by at least one processor, computer program code configured to cause the device to provide UE configuration update information to the UE when the PLMN type or PLMN identity indicates a Visited Public Land Mobile Network (VPLMN) type or VPLMN identity, and the UE behavior policy allows the corresponding VPLMN to modify one or more aspects of the UE behavior policy, and the UE configuration update information may further include an indication of an updated version of the relevant UE behavior policy relating to the VPLMN or VPLMN identity.

[0019] In some embodiments, the device may include computer program code configured by at least one processor to cause the device to subscribe to subscription information updates for UE behavior policies associated with the UE. In some embodiments, the device may include computer program code configured by at least one processor to cause the device to receive subscription information updates for UE behavior policies associated with the UE. In some embodiments, the device may include computer program code configured by at least one processor to cause the device to provide UE configuration update information to the UE, the UE configuration update information including an indication of an updated version of the associated UE behavior policy. In some embodiments, subscription information for the UE behavior policy is received when a policy control function updates the UE behavior policy.

[0020] In some embodiments, the device may include computer program code configured by at least one processor to cause the device to receive at least one authorization flag, the one or more authorization flags indicating whether the visited PLMN, or the visited PLMN's PLMN identity, is authorized to modify the UE behavior policy with respect to one or more components of the UE behavior policy.

[0021] In some embodiments, the PLMN is at least one of a Home Public Land Mobile Network (HPLMN) type or a Visited Public Land Mobile Network (VPLMN) type. In some embodiments, the registration request message further includes information indicating that the UE supports or requires the configuration of a UE behavior policy.

[0022] In another exemplary embodiment, a computer program product can be provided comprising a non-temporary computer-readable storage medium storing computer executable program code instructions, wherein the computer executable program code instructions include program code instructions configured to receive registration request messages from user equipment (UEs) in a network entity of a communication system at runtime. The computer executable program code instructions including the program code instructions may be further configured to determine, at runtime, at least in part, based on the registration request message, i) one or more PLMN (Public Land Mobile Network) types or PLMN identities associated with UE behavior relating to the UE, and ii) versions of the associated UE behavior policies for each of the one or more PLMN types or PLMN identities. The computer executable program code instructions including the program code instructions may be further configured to request a UE behavior policy from another network entity at runtime in response to a request for a UE behavior policy, at least in part based on i) one or more PLMN types or PLMN identities, or ii) versions of the associated UE behavior policies. Computer executable program code instructions, including program code instructions, may, at runtime, provide the UE with UE configuration information in a registration and approval message, and the UE configuration information may be further configured to include one or more PLMN types or PLMN identities and their respective versions of the associated UE behavior policy.

[0023] In some embodiments, a computer executable program code instruction, including a program code instruction, may, at runtime, provide the UE with UE configuration update information if the PLMN type or PLMN identity indicates a Visited Public Land Mobile Network (VPLMN) type or VPLMN identity, and the UE behavior policy allows the corresponding VPLMN to modify one or more aspects of the UE behavior policy, and the UE configuration update information may be further configured to include an indication of an updated version of the relevant UE behavior policy relating to the VPLMN or VPLMN identity.

[0024] In some embodiments, a computer executable program code instruction, including a program code instruction, may be further configured at runtime to subscribe to subscription information updates regarding UE behavior policies associated with the UE. In some embodiments, a computer executable program code instruction, including a program code instruction, may be further configured at runtime to receive subscription information updates to UE behavior policies associated with the UE. In some embodiments, a computer executable program code instruction, including a program code instruction, may be further configured at runtime to provide UE configuration update information to the UE, and the UE configuration update information may be further configured to include an indication of the updated version of the associated UE behavior policy. In some embodiments, subscription information to the UE behavior policy is received when a policy control function updates the UE behavior policy.

[0025] In some embodiments, a computer executable program code instruction, including a program code instruction, may be further configured to receive one or more authorization flags at runtime, and the one or more authorization flags may indicate whether the visited PLMN, or the PLMN identity of the visited PLMN, is authorized to modify the UE behavior policy with respect to one or more components of the UE behavior policy.

[0026] In some embodiments, the PLMN is at least one of a home public land mobile network (HPLMN) type or a visited public land mobile network (VPLMN) type. In some embodiments, the registration request message further includes information indicating that the UE supports or requires the configuration of the UE behavior policy.

[0027] In one exemplary embodiment, in a user equipment, in response to a registration request message previously sent from the UE to a network entity, receiving, from the network entity of the communication system, a registration approval message including UE configuration information, where the UE configuration information includes one or more indications of one or more PLMN types or PLMN identities associated with UE behavior regarding the UE, a method is provided. The method may further include adapting the UE behavior according to the received UE behavior according to the UE behavior policy indicated in the registration approval message.

[0028] In some embodiments, the method further includes storing one or more PLMN types or PLMN identities and respective versions of the associated UE behavior policies.

[0029] In some embodiments, the method further includes providing a registration request message to the network entity, where the registration request message includes an indication of whether the UE supports or requires the configuration of the UE behavior policy.

[0030] In some embodiments, the method further includes, in the UE, storing respective versions of the UE behavior associated with the one or more PLMN types or PLMN identities, where the storing is performed before receiving the registration approval message in the UE. In some embodiments, storing the respective versions of the associated UE behavior is performed upon receiving a previous registration approval message including UE configuration information.

[0031] In some embodiments, the registration request message further includes an indication of the version of the currently configured UE behavior policy. In some embodiments, the registration approval message further includes a command for the user device to request all S-NSSAIs of the configured NSSAI, or a command for the user device to request all S-NSSAIs of the NSSAI configured by default. In some embodiments, the UE configuration information further includes an indication of each version of the UE behavior associated with the one or more PLMN types or PLMN identities.

[0032] In another exemplary embodiment, a user device is provided with means for receiving a registration approval message from a network entity of a communication system in response to a registration request message previously sent from a UE to a network entity, wherein the UE configuration information includes one or more indications of one or more PLMN types or PLMN identities associated with UE behavior relating to the UE. The device may further be configured with means for adapting UE behavior according to the received UE behavior in accordance with the UE behavior policy indicated in the registration approval message.

[0033] In some embodiments, the device may be further configured to include means for storing one or more PLMN types or PLMN identities and their respective versions of associated UE behavior policies.

[0034] In some embodiments, the device may be further configured with means for providing a registration request message to a network entity, the registration request message including an indication of whether the UE supports or requires the configuration of a UE behavior policy.

[0035] In some embodiments, the device is further configured to include means for storing in the UE each version of UE behavior associated with one or more PLMN types or PLMN identities, wherein the storage is performed before the UE receives the registration approval message. In some embodiments, the storage of each version of associated UE behavior is performed upon receipt of a previous registration approval message, which includes UE configuration information.

[0036] In some embodiments, the registration request message further includes an indication of the version of the currently configured UE behavior policy. In some embodiments, the registration approval message further includes a command for the user device to request all S-NSSAIs of the configured NSSAI, or a command for the user device to request all S-NSSAIs of the NSSAI configured by default. In some embodiments, the UE configuration information further includes an indication of each version of the UE behavior associated with the one or more PLMN types or PLMN identities.

[0037] In another exemplary embodiment, the device comprises at least one processor and at least one memory containing computer program code for one or more programs, wherein the at least one memory and computer program code are configured by the at least one processor to cause the device to receive a registration approval message containing UE configuration information from a network entity of a communication system in response to a registration request message previously sent from a UE to a network entity in a user device, and the UE configuration information contains one or more indications of one or more PLMN types or PLMN identities associated with UE behavior relating to the UE. The at least one memory and computer program code may be further configured by the at least one processor to cause the device to at least adapt UE behavior according to the received UE behavior in accordance with the UE behavior policy indicated in the registration approval message.

[0038] In some embodiments, at least one memory and computer program code may be further configured, by at least one processor, to cause the device to store at least one or more PLMN types or PLMN identities and their respective versions of associated UE behavior policies.

[0039] In some embodiments, at least one memory and computer program code may be further configured by at least one processor to cause the device to provide at least one registration request message to a network entity, the registration request message including an indication of whether the UE supports or requires the configuration of a UE behavior policy.

[0040] In some embodiments, at least one memory and computer program code may be further configured by at least one processor to cause the device to store, at least in the UE, each version of the UE behavior associated with the one or more PLMN types or PLMN identities, and such storage may occur before the UE receives the registration approval message. In some embodiments, the storage of each version of the associated UE behavior occurs upon receipt of a previous registration approval message, which includes UE configuration information.

[0041] In some embodiments, the registration request message further includes an indication of the version of the currently configured UE behavior policy. In some embodiments, the registration approval message further includes a command for the user device to request all S-NSSAIs of the configured NSSAI, or a command for the user device to request all S-NSSAIs of the NSSAI configured by default. In some embodiments, the UE configuration information further includes an indication of each version of the UE behavior associated with the one or more PLMN types or PLMN identities.

[0042] In another exemplary embodiment, a computer program product can be provided comprising a non-temporary computer-readable storage medium storing computer executable program code instructions, wherein the computer executable program code instructions are configured, at runtime, in a user device, to receive a registration approval message from a network entity of a communication system, in response to a registration request message previously sent from a UE to a network entity, and the UE configuration information includes one or more indications of one or more PLMN types or PLMN identities associated with UE behavior relating to the UE. The computer executable program code instructions, including the program code instructions, may be further configured, at runtime, to adapt UE behavior according to the received UE behavior, in accordance with the UE behavior policy indicated in the registration approval message.

[0043] In some embodiments, a computer executable program code instruction, including program code instructions, may be further configured to store, at runtime, one or more PLMN types or PLMN identities and their respective versions of associated UE behavior policies.

[0044] In some embodiments, a computer executable program code instruction, including a program code instruction, may be further configured to provide a registration request message to a network entity at runtime, and the registration request message may include an indication of whether the UE supports or requires the configuration of a UE behavior policy.

[0045] In some embodiments, a computer executable program code instruction, including program code instructions, may be further configured to store, at runtime, in the UE, each version of the UE behavior associated with the one or more PLMN types or PLMN identities, such that the storage occurs before the UE receives the registration approval message. In some embodiments, the storage of each version of the associated UE behavior occurs upon receiving a previous registration approval message, which includes UE configuration information.

[0046] In some embodiments, the registration request message further includes an indication of the version of the currently configured UE behavior policy. In some embodiments, the registration approval message further includes a command for the user device to request all S-NSSAIs of the configured NSSAI, or a command for the user device to request all S-NSSAIs of the NSSAI configured by default. In some embodiments, the UE configuration information further includes an indication of each version of the UE behavior associated with the one or more PLMN types or PLMN identities.

[0047] While specific exemplary embodiments of this disclosure have been described in general terms, this specification will henceforth refer to the accompanying drawings, which are not necessarily drawn to scale. [Brief explanation of the drawing]

[0048] [Figure 1] This figure shows an exemplary system environment in which an exemplary embodiment of the present invention can be implemented. [Figure 2] This is a block diagram of a core network device configured according to exemplary embodiments of the present disclosure. [Figure 3] This figure shows an exemplary transmission within a communication system for determining a user equipment policy regarding user equipment, according to an exemplary embodiment of the present disclosure. [Figure 4]This figure shows an exemplary transmission within a communication system for determining a user device policy relating to user devices determined by a policy control function, according to an exemplary embodiment of the present disclosure. [Figure 5] This figure shows an exemplary workflow of various components of a communication system according to an exemplary embodiment. [Figure 6] This figure shows an exemplary workflow of various components of a communication system according to an exemplary embodiment. [Figure 7] This figure shows an exemplary workflow of various components of a communication system according to an exemplary embodiment. [Modes for carrying out the invention]

[0049] Hereafter, this specification will describe in more detail some embodiments of the present invention with reference to the accompanying drawings. The accompanying drawings show some, but not all, embodiments of the present invention. In fact, various embodiments of the present invention can be embodied in many different forms and should not be construed as being limited to the embodiments described herein; rather, these embodiments are provided so that this disclosure satisfies the appropriate legal requirements. Throughout, similar reference numbers represent similar elements. As used herein, the terms “data,” “content,” “information,” and similar terms may be used interchangeably to refer to data that can be transmitted, received, and / or stored in accordance with embodiments of the present invention. Accordingly, the use of any such terms should not be construed as limiting the spirit and scope of embodiments of the present invention.

[0050] Furthermore, as used herein, the term “circuit” refers to (a) a hardware-only circuit implementation (e.g., an implementation of an analog circuit and / or a digital circuit); (b) a combination of a circuit and a computer program product that includes software and / or firmware instructions stored in one or more computer-readable memories that cooperate to cause the device to perform one or more functions described herein; and (c) a circuit that requires software or firmware to operate even if the software or firmware is not physically present, such as a microprocessor or a part of a microprocessor. This definition of “circuit” applies to all uses of the term herein, including any claims. As a further example, as used herein, the term “circuit” also includes an implementation that includes one or more processors and / or parts thereof and accompanying software and / or firmware. As defined herein, “computer-readable storage medium” which refers to a physical storage medium (e.g., a volatile or non-volatile memory device) may be distinguished from “computer-readable transmission medium” which refers to an electromagnetic signal.

[0051] The 3rd Generation Partnership Project (3GPP) Fifth Generation (5G) technology is a next-generation wireless system and network architecture capable of providing ultra-wideband, ultra-robust, low-latency connectivity. 5G technology will improve the various telecommunications services offered to end users and help support massive broadband, providing gigabytes per second of bandwidth on demand for both uplink and downlink transmissions. Next-generation systems utilizing the 5G architecture leverage virtualized radio access network (RAN) and core network capabilities.

[0052] This specification describes embodiments relating to exemplary communication systems and related techniques for providing data transport in communication systems. However, it should be understood that the scope of the claims is not limited to the specific types of communication systems and / or processes disclosed. Embodiments can be implemented in various other types of communication systems using alternative processes and operations. For example, while described in the context of wireless cellular systems utilizing 3rd Generation Partnership Project (3GPP) system elements such as 3GPP Next Generation Systems (5G), the disclosed embodiments can be readily adapted to various other types of communication systems.

[0053] According to exemplary embodiments implemented in a 5G communication system environment, one or more 3GPP technical specifications (TS) and technical reports (TR) provide further descriptions of user equipment and network elements / functions and / or operations interacting with one or more exemplary embodiments (e.g., 3GPP TS 23.501, 3GPP TS 23.502, 3GPP TS 33.501, and 3GPP TR 33.899). Other 3GPP TS / TR documents provide other conventional details that will be understood by those skilled in the art. However, while exemplary embodiments are well suited to implementations associated with the 5G-related 3GPP standards described above, alternative embodiments are not necessarily intended to be limited to any particular standard.

[0054] In 5G networks, network slicing is a concept for running multiple logical networks as virtually independent business operations on a common physical infrastructure. Network slices are considered independent, virtualized, end-to-end networks. Currently, efforts are underway to standardize how network slices are defined, how user devices are registered to and unregistered from network slices, and how protocol data unit (PDU) sessions are authorized to network slices. However, under current 3GPP specifications, enforcing such activities is complex and typically dependent on user devices, meaning that network operators have little control over user device behavior during such activities. While this disclosure may describe the invention in relation to 5G communication systems, the invention is also applicable to, but not limited to, other networks and network technologies such as 4G, LTE, and 3G.

[0055] According to exemplary embodiments, methods, apparatus, and computer program products are provided for determining which user device policy to apply to a user device, thereby providing operator control over user device behavior in registering with and unregistering to network slices, and establishing and releasing PDU sessions in a communication system.

[0056] In communication systems such as 5G systems, user equipment (UE) may subscribe to one or more network slices. A UE subscription may include multiple network slices, each identified by network slice selection assistance information (NSSAI). Thus, network slices may be identified by single network slice selection assistance information (S-NSSAI). One or more of these S-NSSAIs may be marked as default S-NSSAIs. Default S-NSSAIs can identify network slices that a UE can or should use, for example, if the UE has not requested a network slice in a particularly requested NSSA before the UE is configured with a configured NSSAII. Under current standards, such as those mentioned herein, and when the UE is configured with a configured NSSAI, these current standards leave the UE free to request any of these configured NSSAIs based on local logic. Therefore, there are no restrictions on the behavior of a UE requesting one or more configured NSSAIs. Under the current standard, the only available mechanism is for the UE's Home Public Land Mobile Network (HPLMN) to configure the UE with a default configured NSSAI, which the UE uses when it has not yet received a configured NSSAI in the Serving PLMN.

[0057] However, this approach has several problems, one of which is that the UE may always omit requests for S-NSSAIs that the operator wants the UE to use in order to provide essential services or updates to the UE. Also, many UEs currently on the market are configured to advance requests for all S-NSSAIs within the configured NSSAI in such cases, without considering the actual need. This can mean, for example, that it may be pointless for an operator to deploy a network slice-specific Access and Mobility Management Function (AMF), because all UEs behaving in this way typically become AMFs that support all S-NSSAIs simultaneously. Such a situation with respect to the network may mean that only a general AMF is used and must switch between network slices, or must be configured to function within or between multiple network slices, which can result in inefficient network messaging, lack of specific network slices, and / or inefficient signaling of NSSAIs. For example, under current standards and associated network / UE configurations, a UE configured for a large-scale Internet of Things (MIoT) slice and an enhanced mobile broadband (eMBB) slice will typically, or always, be an AMF that supports both, even if the UE rarely needs to use eMBB (for example, only when the UE needs to update its software).MIoT-specific AMFs have become one of the main drivers of network slicing, and for example, in evolved packet systems (EPS) of dedicated core networks, they were defined to support mobility management entities (MMEs) that are primarily or exclusively dedicated to Internet of Things (IoT) technology and connectivity (e.g., MMEs that manage small amounts of data and / or rarely connect to a large number of devices, or MMEs that support small amounts of data transmission in the control plane).

[0058] According to current standards, if a UE can access or is configured to access more than a certain number of network slices, for example, more than nine network slices, the UE may, or will, apply logic outside the network operator's control when deciding which of the eight or more network slices it will not request.

[0059] Conversely, some UEs may request only one network slice in relation to their application, and then decide to relinquish the requested network slice after the application that required it has stopped using it. Operators who are launched and released fairly frequently may want to minimize this type of behavior. Therefore, operators have no way to enforce network slice registration / unregistration behavior regarding UEs, or UE behavior regarding associating PDU sessions with network slices. According to current relevant standards, for example, an operator who deploys only AMFs that serve all network slices simultaneously may actually want to enforce for all UEs to minimize UEs joining and leaving network slices via registration procedures, because such AMFs are at least nearly meaningless in the network unless, for example, some network slices also have limits on the number of UEs that can be connected, require additional authentication and authorization for UEs to connect, or have a default Access Point Name (APN).

[0060] Therefore, according to current relevant standards, operators typically have no way of configuring the UE to decide when to relinquish a network slice after the last application using the network slice has stopped doing so, for example, using a hysteresis timer. For example, if an application operated by the UE frequently joins and leaves a network slice (e.g., joins and leaves the network slice more than a certain number of times per unit time), this can cause an undesirable signaling load.

[0061] Accordingly, this specification describes methods, apparatus, and computer program products for resolving some or all of the above limitations of current relevant standards and / or other limitations of current relevant standards. Specifically, it describes methods, apparatus, and computer program products that enable operators to control UE behavior. By enabling control of UE behavior by network operators, network slice operators, APN operators, AMF operators, or other network entities, operators can coordinate UE behavior within their networks, network slices, or network entities in a manner that is adaptable to the deployment and minimizes signaling load, thereby reducing unnecessary bandwidth dedicated to such signaling and enrollment / de-enrollment and other such activities. A similar approach can be adopted within a network slice to control, for example, which PDU sessions are established, can be established, or should be established only when requested by an application. According to current relevant standards, UEs are not currently required to establish PDU sessions with Data Network Names (DNNs). For example, if these are configured in a UE route selection policy (URSP), the establishment of such PDU sessions is only required when an application requires it. In other words, the approach described allows operators to control the UE behavior when forming a Requested NSSAI and when requesting PDU sessions within a network slice.

[0062] In some embodiments, a UE operator can control UE behavior based at least partially on UE behavior information associated with at least one of the relevant HPLMN or Destination Public Land Mobile Network (VPLMN). For example, an HPLMN may provide UE behavior information to control UE behavior but not provide authorization for the VPLMN to modify UE behavior. Thus, a UE operator can control UE behavior based at least partially on UE behavior information from the relevant HPLMN. In another example, an HPLMN may not provide information to control UE behavior, and therefore the VPLMN may provide UE behavior information. Thus, a UE operator can control UE behavior based at least partially on UE behavior information from the relevant VPLMN. In yet another example, if an HPLMN provides authorization for the VPLMN to modify UE behavior, a UE operator can control UE behavior based at least partially on UE behavior information associated with the HPLMN, VPLMN, or a combination thereof (for example, using UE behavior information from both the HPLMN and the VPLMN).

[0063] In some embodiments, the network entity and / or UE can be configured so that the network operator can control the UE's behavior. In some embodiments, in addition to being able to provide the UE with configured NSSAI and URSP, the network entity can also provide the UE with configuration information that instructs the UE to reconfigure itself to control its behavior in forming requested NSSAI and also in establishing PDU sessions. This information may be S-NSSAI-based, DNN-based, and / or global-based.

[0064] Figure 1 shows an exemplary communication system environment in which an exemplary embodiment of the present invention can be implemented. The depiction of the system environment 100 in Figure 1 is not intended to limit or otherwise restrict the embodiments described and contemplated herein to any particular configuration of elements or systems, nor is it intended to exclude alternative configurations or systems relating to sets of configurations and systems that may be used in connection with embodiments of the present invention. Rather, Figure 1 and the system environment 100 disclosed therein are presented solely to provide an exemplary basis and context for facilitating some of the functions, aspects, and uses of the methods, apparatus, and computer program products disclosed and contemplated herein. While many aspects and components shown in Figure 1 are shown as independent, separate elements, it should be understood that other configurations may also be used in connection with the methods, apparatus, and computer programs described herein, including configurations that combine, omit, and / or add aspects and components.

[0065] As shown in Figure 1, the system environment includes one or more user devices (UEs) 102 configured to communicate wirelessly with network 106 via an access network or the like. User devices can be configured in a variety of different ways, but can embody as mobile terminals such as personal digital assistants (PDAs), mobile phones, smartphones, pagers, mobile televisions, gaming devices, laptop computers, cameras, tablet computers, communication devices, pads, headsets, touch surfaces, video recorders, audio / video players, radios, e-books, positioning devices (e.g., Global Positioning System (GPS) devices), or any combination of the aforementioned types and other types of voice and text and multimodal communication systems. The system environment 100 shown in Figure 1 also includes one or more access points 104a and 104b, such as base stations, including but not limited to Node B and evolved Node B (eNB). Cellular access points, such as base stations, may define and service one or more cells. The access point can then communicate with a network 106, such as a core network, via a gateway, thereby establishing a cellular radio access network that allows user equipment 102 to communicate with the network. The system environment 100 in Figure 1 may include multiple different cellular radio access cells and / or networks or parts of such networks, including, for example, a 5G radio access network, an LTE (Long-Term Evolution) radio access network, and a UMTS (Universal Mobile Telecommunications System) radio access network. In some exemplary implementations, equipment and other infrastructure associated with multiple different cellular radio access networks may be located in or near structures and / or other equipment associated with specific access points, such as access points 104a and 104b.

[0066] In some implementations of system environment 100, the cellular radio access network served by access points 104a, 104b, and any other access points within a given area is identical in the sense that user equipment 102 moves from the area served by access point 104a to the area served by access point 104b. User equipment 102 can access network 106 via the radio access network provided across the access points. Although not shown, the system may also include a controller associated with one or more of the cellular access points, such as a base station, to facilitate the operation of the access points and the management of user equipment 102 communicating with the access points. As shown in Figure 1, the system may also include one or more wireless local area networks (WLANs), each WLAN may be served by a WLAN access point 108 configured to establish wireless communication with user equipment. Thus, user equipment can communicate with the network via WLAN access points, as shown by solid lines in Figure 1, or alternatively, via cellular access points, as shown by dashed lines. Wireless access networks and core networks may consist of additional network elements such as routers, switches, servers, gateways, and / or controllers.

[0067] In this regard, the implementation and / or allocation of network slices within a network environment can be achieved by a device 200 as shown in Figure 2. This device is embodied and / or may be embodied by one or more UEs, such as user equipment 102, or any of the other devices discussed with respect to Figure 1, such as access points 104a and / or 104b, one or more WLAN access points 108, and / or devices that are incorporated into or otherwise associated with the system environment 100. Alternatively, the device 200 may be embodied by another device outside of such a device. For example, the device may be embodied by a computing device such as a personal computer, computer workstation, or server, or by any of various mobile computing devices such as mobile terminals, including but not limited to smartphones and tablet computers.

[0068] In some embodiments, the system environment 100 may include one or more of the following network functions (NFs): Authentication Server Function (AUSF), Access and Mobility Management Function (AMF), Data Network (DN), e.g., operator services, Internet access or third-party services, Unstructured Data Storage Function (UDSF), Network Exposure Function (NEF), Network Repository Function (NRF), Network Slice Selection Function (NSSF), Policy Control Function (PCF), Session Management Function (SMF), Unified Data Management (UDM), Unified Data Repository (UDR), User Plane Function (UPF), UE Radio Capability Management Function (UCMF), Application Function (AF), User Equipment (User Equipment (UE), Next Generation-Radio Access Network (NG-RAN), 5G-Equipment Identity Register (5G-EIR), Network Data Analytics Function (NWDAF), and Charging Function (CHF).The system environment may further include the following network entities: a Service Communication Proxy (SCP) and a Security Edge Protection Proxy (SEPP).

[0069] Regardless of how the apparatus 200 is embodied, the apparatus of the exemplary embodiment is configured to include, or otherwise communicate with, a processor 202 and a memory device 204, and optionally a user interface 206 and / or a communication interface 208. In some embodiments, the processor (and / or a coprocessor or any other processing circuit assisting the processor or otherwise associated with the processor) can communicate with the memory device via a bus for passing information between components of the apparatus. The memory device may be non-temporary and may include, for example, one or more volatile and / or non-volatile memories. In other words, for example, the memory device may be an electronic storage device (e.g., a computer-readable storage medium) having gates configured to store data (e.g., bits) that may be retrieved by a machine (e.g., a computing device such as a processor). The memory device may be configured to store information, data, content, applications, instructions, etc., to enable the apparatus to perform various functions according to the exemplary embodiments of the invention. For example, the memory device may be configured to buffer input data for processing by the processor. Additionally or alternatively, the memory device may also be configured to store instructions for execution by the processor.

[0070] As described above, the apparatus 200 may be embodied by a computing device. However, in some embodiments, the apparatus may be embodied as a chip or chipset. In other words, the apparatus may comprise one or more physical packages (e.g., a chip) including materials, components, and / or wires on a structural assembly (e.g., a baseboard). The structural assembly can provide physical strength, size preservation, and / or limitations on electrical interactions with the component circuits contained therein. Thus, in some cases, the apparatus may be configured to implement embodiments of the present invention on a single chip or as a single "system on a chip". Thus, in some cases, the chip or chipset may constitute means for performing one or more operations to provide the functions described herein.

[0071] The processor 202 can be embodied in various ways. For example, the processor can be embodied as one or more processing circuits, such as coprocessors, microprocessors, controllers, digital signal processors (DSPs), processing elements with or without associated DSPs, or various other processing circuits, such as ASICs (Application-Specific Integrated Circuits), FPGAs (Field-Programmable Gate Arrays), microcontroller units (MCUs), hardware accelerators, and dedicated computer chips, among other hardware processing means. Thus, in some embodiments, the processor may include one or more processing cores configured to operate independently. A multicore processor may enable multiprocessing within a single physical package. As an addition or alternative, the processor may include one or more processors configured in tandem via a bus, enabling independent instruction execution, pipeline processing, and / or multithreaded processing.

[0072] In exemplary embodiments, the processor 202 may be configured to execute instructions stored in the memory device 204, or otherwise accessible to the processor. Alternatively or additionally, the processor may be configured to execute hardcoded functions. Thus, whether configured by hardware or software methods, or a combination thereof, the processor can represent entities (e.g., physically embodied in a circuit) that are configured accordingly and capable of operating according to embodiments of the present invention. For example, when the processor is embodied as an ASIC or FPGA, the processor may be hardware specifically configured to perform the operations described herein. Alternatively, as another example, when the processor is embodied as an executable of software instructions, the instructions may specifically configure the processor to perform the algorithms and / or operations described herein when the instructions are executed. However, in some cases, the processor may be the processor of a particular device (e.g., a pass-through display or a mobile terminal) configured to employ embodiments of the present invention by further configuring the processor with instructions for performing the algorithms and / or operations described herein. The processor may include, among other things, a clock, an arithmetic logic unit (ALU), and logic gates configured to support the operation of the processor.

[0073] The device 200 may optionally include a communication interface 208. The communication interface may be any means, such as a device or circuit embodied in hardware or a combination of hardware and software, configured to receive and / or transmit data to and from a network and / or to any other device or module communicating with the device. In this regard, the communication interface may include, for example, an antenna (or multiple antennas) and supporting hardware and / or software to enable communication with a wireless communication network. Additionally or alternatively, the communication interface may include circuitry for interacting with the antenna to cause the transmission of signals through the antenna or to process the reception of signals received through the antenna. In some environments, alternatively or further, the communication interface may support wired communication. Thus, for example, the communication interface may include a communication modem and / or other hardware / software to support communication via cable, digital subscriber line (DSL), universal serial bus (USB), or other mechanisms.

[0074] This specification will henceforth present exemplary transmissions between the UE and network entities. The following exemplary transmissions provide the expected steps or messaging required. Information enclosed in "[ ]" is optional and may be included, for example, if the configured NSSAI and / or URSP are provided to the UE at the same time that the UE behavior is configured.

[0075] Figure 3 shows an exemplary transmission between the UE and various network entities of the communication system for configuring the UE according to the UE behavior policy.

[0076] In operation 0, UE301 may provide AMF303 with an initial REGISTRATION REQUEST message in the PLMN (e.g., VPLMN or HPLMN) via the (Radio) Access Network ((R)AN) node 302. The REGISTRATION REQUEST message may indicate whether the UE is currently configured by UE behavior from the HPLMN or VPLMN, and / or may provide an indication of the currently configured UE behavior. In some embodiments, the registration request message may include an indication of whether the UE supports or requires the configuration of a UE behavior policy. Based at least in part on the registration request message, AMF303 may determine one or more PLMN types or PLMN identities associated with the UE behavior relating to UE301. The PLMN types may include HPLMN types or VPLMN types. The PLMN identities may provide an indication of which aspects (i.e., functions, values, etc.) of the UE behavior are configured by the respective PLMN (e.g., HPLMN or VPLMN). In some embodiments, the REGISTRATION REQUEST may further provide an indication of the version of the UE behavior policy.

[0077] In operation 1, AMF303 may obtain access and mobility information from UDM304. Access and mobility information may include an access and mobility management non-access stratum temporary identifier. The non-access stratum temporary identifier may correspond to a session management non-access stratum temporary identifier when the non-access stratum message is a session management non-access stratum message. In some embodiments, the non-access stratum temporary identifier corresponds to an access and mobility management non-access stratum temporary identifier when the non-access stratum message is a protocol data unit session establishment non-access stratum message.

[0078] Furthermore, AMF303 may request and / or retrieve a UE behavior policy from UDM304 based at least partially on one or more PLMN types or PLMN identities, or versions of associated UE behavior policies. In particular, AMF303 may provide UDM304 with an indication of the version of the UE behavior policy, and UDM304 may then provide AMF303 with the UE behavior policy. The UE behavior policy may describe UE behavior controls relating to UE301. Furthermore, in some embodiments, the UE behavior policy may describe one or more authorization flags. One or more authorization flags may indicate whether the VPLMN is authorized to modify the UE behavior policy. In some embodiments, AMF304 may request a UE behavior policy from UDM304 during a Nudm_UECM_registration message between AMF303 and UDM304.

[0079] In some embodiments, HPLMN may selectively provide authorization with respect to specific parts of the UE behavior policy. For example, HPLMN may allow modification and / or configuration of UE behavior to register with a specific network slice or all configured network slices, at least in part, based on usage. As another example, HPLMN may allow modification and / or configuration of UE behavior in the time before the UE is able to decide to unregister with a particular network slice. In some embodiments, HPLMN may also provide a range for setting policies in VPLMN, or set maximum and / or minimum values ​​for UE behavior policies, where applicable.

[0080] In operation 2, the AMF303 may complete the registration request to the UE301. In some embodiments, the AMF303 may provide the UE301 with a REGISTRATION ACCEPT message. The REGISTRATION ACCEPT message may include the configured NSSAI, UE behavior support information, and / or similar information. In some embodiments, a network entity (e.g., AMF) sends such a REGISTRATION ACCEPT message (e.g., including UE behavior support information) to the UE, thereby enabling the UE to be configured to follow network entity instructions regarding the control of UE behavior during registration / deregistration and / or PDU session establishment / release. Furthermore, the REGISTRATION ACCEPT message may also include an indication of whether the UE behavior policy is associated with an HPLMN or VPLMN associated with the UE301.

[0081] When UE301 receives a REGISTRATION ACCEPT message, the UE may apply, or otherwise provide, new behavior provided by the network, for example, in UE behavior support information. In some embodiments, UE behavior support information may provide an instruction that the UE is configured to request all S-NSSAI in the configured NSSAI. In some embodiments, UE behavior support information may provide an instruction that the UE is configured, by default, to request any S-NSSAI of the serving PLMN that maps to an S-NSSAI in the default configured NSSAI. In some embodiments, UE behavior support information may provide an instruction that the UE is configured to always request at least a well-identified subset of S-NSSAI in the configured NSSAI. In some embodiments, the well-identified subset of S-NSSAI in the configured NSSAI may be at least the default S-NSSAI provided by the HPLMN, or may include them. In some embodiments, the well-identified subset may be identified by flags associated with some or each S-NSSAI provided to the UE in the configured NSSAI or the default configured NSSAI. In some embodiments, UE behavior support information can provide instructions that configure the UE to request only S-NSSAIs that have an active application associated with the UE, such as an application run by the UE. In some embodiments, if the UE is configured to request only S-NSSAs when an active application is using a network slice, the UE can provide instructions that configure the UE to provide an explicit timer that causes the UE to release network slices that are no longer used by any application, for example, by excluding the network slice to be released from the next requested NSSAI, thereby allowing the operator to implement a kind of hysteresis.

[0082] In operation 3, AMF303 may subscribe to subscription information updates from UDM304. AMF303 can subscribe to such updates via the Nudm_SDM_subscribe message. When AMF303 subscribes to subscription information updates, AMF303 may receive one or more updates to the associated UE behavior policy if the UE behavior policy is changed and / or modified in the associated HPLMN.

[0083] In operation 4, if the AMF303 receives one or more updates regarding relevant UE behavior policies for UE301, the AMF303 may attempt to provide configuration updates to UE301. However, if UE301 is not in connection management (CM) connected mode, the AMF303 may provide a network-triggered service request to UE301. Alternatively, UE301 may provide a service request to the AMF303.

[0084] In operation 5, when UE301 enters CM connection mode, AMF303 may provide UE configuration updates to UE301. In some embodiments, UE configuration updates may be operable to provide operator control over UE behavior in registering with and unregistering with network slices, and / or establishing and releasing PDU sessions in communication systems. In some embodiments, AMF may determine desired UE behavior regarding requested NSSAI formation and / or DNN establishment with respect to a particular UE, a particular network slice, a global network or communication system, and / or similar, based on local policies or information received, for example, from a UDM. In some embodiments, the UE configuration update command message may include other identifying information regarding configured NSSAI, URSP, network, network slice, PDU session, AMF, and / or similar. In some embodiments, the UE configuration update command message may further include UE behavior support information, which may be similar to or identical to UE behavior support information. In some embodiments, UE behavior support information may include an indication of whether the relevant UE policy is from an HPLMN, VPLMN, or a combination thereof, and / or an indication of the version of the UE behavior policy. In some embodiments, if a PLMN type or PLMN identity indicates a VPLMN type or VPLMN identity, and the UE behavior policy allows the corresponding VPLMN to modify one or more aspects of the UE behavior policy (as permitted by the HPLMN), then the UE configuration update information may include an indication of the updated version of the relevant UE behavior policy with respect to the VPLMN or VPLMN identity. Thus, the VPLMN can modify the UE behavior policy locally without having to renew its subscription to the HPLMN.

[0085] For example, a network entity such as an AMF can send a message containing UE behavior support information and / or similar information. In some embodiments, a network entity (e.g., an AMF) can send such a message (e.g., containing UE behavior support information) to a UE, thereby configuring the UE to follow network entity instructions for controlling UE behavior during the establishment and / or release of a PDU session with a network slice. Upon receiving the message, the UE can apply, or otherwise provide, any new behavior provided by the network, for example, in the UE behavior support information. In some embodiments, the UE behavior support information can provide an instruction that configures the UE to request all S-NSSAIs within a configured NSSAI. In some embodiments, the UE behavior support information can provide an instruction that, by default, configures the UE to request any S-NSSAIs of a serving PLMN that map to S-NSSAIs within a default configured NSSAI. In some embodiments, the UE behavior support information can provide an instruction that configures the UE to always request at least a well-specified subset of S-NSSAIs within a configured NSSAI. In some embodiments, a well-specified subset of S-NSSAIs within a configured NSSAI may be at least the default S-NSSAIs provided by HPLMN, or may include them. In some embodiments, the well-specified subset may be identified by flags associated with some or each S-NSSAI provided to the UE in the configured NSSAI or default configured NSSAI. In some embodiments, UE behavior support information may provide instructions that configure the UE to request only S-NSSAIs that have an active application associated with the UE, e.g., an application run by the UE.In some embodiments, UE behavior support information can provide instructions that the UE is configured to provide an explicit timer to cause the UE to release network slices that are no longer used by any application, for example, by excluding the network slice to be released from the next requested NSSAI, when the UE is configured to request only S-NSSAs when an active application is using a network slice, thereby allowing the operator to implement a kind of hysteresis.

[0086] In some embodiments, UE behavior support information can provide instructions that the UE is configured to always establish all PDU sessions associated with the S-NSSAI. In some embodiments, UE behavior support information can provide instructions that the UE is configured to establish a specific PDU session or a subset of PDU sessions by default. In some embodiments, a specific PDU session or a subset of PDU sessions can be explicitly identified in UE configuration information or a message containing UE configuration information. In some embodiments, UE configuration information can be provided in URSP by associating a flag with the DNN associated with the S-NSSAI. In some embodiments, the serving PLMN can use a local policy or default DNN regarding the S-NSSAI provided by the HPLMN, if any.

[0087] In certain exemplary embodiments, the UE may be configured to maintain and update a database of UE configuration information in local storage. For example, if the network has previously provided the UE with relevant UE configuration information (e.g., in a previous registration approval or otherwise), the network may be configured to provide identification of the PLMN type or PLMN ID in the subsequent UE configuration information in the registration approval message (e.g., without indication of each version of the UE behavior). In response to receiving the subsequent UE configuration information, the UE may be configured to retrieve the corresponding version information in local storage and adapt the UE behavior according to the corresponding UE behavior policy (e.g., also stored in the database). Thus, the UE can be configured to store the UE behavior policy and associated version information in local storage for later use. Alternatively, the UE can also be configured to store default UE behavior policies corresponding to one or more PLMN types or PLMN IDs in local storage for later use.

[0088] In some embodiments, UE behavior support information may optionally be provided in or with downlink non-access layer transport messages from a network entity to user equipment. In some other embodiments, UE behavior support information may optionally be provided in or with UE configuration update messages from a network entity to user equipment. In some embodiments, UE behavior support information may include configuration information that includes instructions for user equipment to request all S-NSSAIs of a configured NSSAI, or all S-NSSAIs of a default configured NSSAI. In some embodiments, registration approval or rejection messages, downlink non-access layer transport messages, or UE configuration update messages may include instructions for user equipment to always request a subset of S-NSSAIs within a configured NSSAI. In some embodiments, the subset of S-NSSAIs may be explicitly indicated or identified by one or more flags associated with each S-NSSAI provided to user equipment within a configured NSSAI or a default configured NSSAI, where the one or more S-NSSAIs are determined by the network based on local policies or information received from user equipment subscription information. In some embodiments, registration approval or rejection messages, downlink non-access layer transport messages, or UE configuration update messages may include instructions for user equipment to request only S-NSSAIs that have active applications. In some embodiments, registration approval or rejection messages, downlink non-access layer transport messages, or UE configuration update messages may include instructions for user equipment to release network slices that are no longer used by any application, thereby excluding the released network slices from the next requested NSSAI.

[0089] In operation 6, UE301 may provide AMF303 with a UE configuration update complete message. The UE configuration update complete message may include an acknowledgment that UE301 has successfully received the UE configuration update and / or performed the associated update.

[0090] In operation 7, AMF303 may provide UDM304 with an acknowledgment that UE301 has been successfully configured. AMF may provide this acknowledgment if HPLMN provides a UE behavior policy. In some embodiments, AMF303 may provide the acknowledgment via a Nudm_SDM_Info request message.

[0091] Figure 4 shows an exemplary transmission between the UE and various network entities of the communication system for configuring UE behavior using the UE configuration update procedure.

[0092] In Action 0, the PCF401 associated with the HPLMN may decide to update the UE behavior policy. The PCF401 can securely configure UE behavior using the UE Configuration Update procedure for transparent UE policy delivery as defined in clause 4.2.4.3 of TS 23.502. These policies are identified by specific policy section identifiers (PSIs). The HPLMN may contain one or more PSIs for policies that can be authorized to be changed by the VPLMN, for example, by using one or more authentication flags.

[0093] In operation 1, PCF401 may provide AMF301 with an indication of the updated UE behavior policy. PCF401 can provide the indication via a Namf_Communication_N1N2MessageTransfer message.

[0094] In operation 2, the AMF303 may attempt to provide a configuration update to the UE301. However, if the UE301 is not in connection management (CM) connection mode, the AMF303 may provide a network trigger service request to the UE301. Alternatively, the UE301 may provide a service request to the AMF303.

[0095] In operation 3, when UE301 enters CM connection mode, AMF303 may provide UE301 with a UE configuration update. Operation 3 in Figure 4 may be substantially the same as operation 5 described in Figure 3.

[0096] In operation 4, UE301 may provide AMF303 with a UE configuration update complete message. Operation 4 in Figure 4 may be substantially the same as operation 6 described in Figure 3.

[0097] In operation 5, the AMF303 may provide the PCF401 with an acknowledgment that the UE301 has been successfully configured. In some embodiments, the AMF303 may provide the acknowledgment via a Namf_Communication_N1MessageNotify message.

[0098] Referring next to Figure 5, exemplary workflows of various components of a communication system are shown according to exemplary embodiments such as the UE, R(AN), AMF, UDM, PCF, or other components mentioned above in relation to other figures, for example. Referring next to Figure 5, 501 shows a method 500 that can be performed by one or more of the described entities, including means for receiving registration request messages from user equipment in a network entity of the communication system, such as a processor 202 and a communication interface 208. In some embodiments, method 500 may include, in 502, determining one or more PLMN types or one or more PLMN identities and a version of the UE behavior policy relating to the UE. The one or more PLMN types or one or more PLMN identities and a version of the UE behavior policy relating to the UE may be determined at least in part based on the registration request message. The PLMN types may include HPLMN types or VPLMN types. In some embodiments, method 500 may include requesting a UE behavior policy from, for example, a UDM. A request for a UE behavior policy may, in 503, be at least partially based on one or more PLMN types or one or more PLMN identities, or a version of the associated UE behavior policy, in response to the UE behavior policy. In some embodiments, method 500 further includes receiving one or more authorization flags. One or more authorization flags may be received along with the UE behavior policy. One or more authorization flags indicate whether the visited PLMN is authorized to modify the UE behavior policy. In some embodiments, method 500 may, in 504, include providing UE configuration information to the UE. The UE configuration information may include one or more PLMN types or one or more PLMN identities, and an indication of the version of the associated UE behavior policy.

[0099] In some embodiments, if a PLMN type or PLMN identity indicates a VPLMN type or VPLMN identity and a UE behavior policy allows the corresponding VPLMN to modify one or more aspects of the UE behavior policy, method 500 may further include providing the UE with UE configuration update information, wherein the UE configuration update information includes an indication of an updated version of the associated UE behavior policy relating to the VPLMN or VPLMN identity.

[0100] Referring next to Figure 6, exemplary workflows of various components of the communication system are shown according to exemplary embodiments such as the UE, R(AN), AMF, UDM, PCF, or other components mentioned above in relation to other figures, for example. Referring next to Figure 6, 601 shows a method 600 that can be performed by one or more of the described entities, including a processor 202 and a communication interface 208, which includes means for subscribing to subscription information updates for the UE behavior policy. In some embodiments, method 600 may include, 602, receiving subscription information updates to the UE behavior policy. In some embodiments, subscription information to the UE behavior policy is received when a policy billing function updates the UE behavior policy. In some embodiments, method 600 may include, 603, providing UE configuration update information to the UE. The UE configuration update information may include an indication of the updated version of the relevant UE behavior policy.

[0101] Referring next to Figure 7, exemplary workflows of various components of a communication system are shown according to exemplary embodiments such as UE, R(AN), AMF, UDM, PCF, or other components mentioned earlier in relation to other figures, for example. Referring next to Figure 7, method 700 is shown in 701, which can be performed by one or more of the described entities, including means for providing a registration request message to a network entity, such as a processor 202 and a communication interface 208. The registration request message includes an indication of whether the UE supports or requires the configuration of a UE behavior policy. In some embodiments, the registration request message further includes an indication of the version of the currently configured UE behavior policy. In some embodiments, method 700 may include, in 702, receiving a registration approval message from the network. The registration approval message may include UE configuration information, which may include one or more indications of one or more PLMN types or PLMN identities and the respective versions of the associated UE behavior policies. The registration approval message may include a UE behavior policy. In some embodiments, Method 700 may include storing one or more PLMN types or PLMN identities, such as those received in a registration approval message, and the respective versions of the associated UE behavior policies. In some embodiments, the registration approval message may include a command in which the user device requests all S-NSSAIs of the configured NSSAI, or a command in which the user device requests all S-NSSAIs of the NSSAI configured by default. In some embodiments, Method 700 may include adapting the UE behavior in accordance with the UE behavior policy indicated in the registration approval message.

[0102] In certain exemplary embodiments, the UE may be configured to maintain and update a database of UE configuration information in local storage. For example, if the network has previously provided the UE with relevant UE configuration information (e.g., in a previous registration approval or otherwise), the network may be configured to provide identification of the PLMN type or PLMN identity (e.g., without indication of each version of the UE behavior) within the subsequent UE configuration information in the registration approval message. In response to receiving the subsequent UE configuration information, the UE may be configured to retrieve the corresponding version information in local storage and adapt the UE behavior according to the corresponding UE behavior policy (e.g., also stored in the database). Thus, the UE can be configured to store the UE behavior policy and associated version information in local storage for later use. Alternatively, the UE can also be configured to store default UE behavior policies corresponding to one or more PLMN types or PLMN IDs in local storage for later use.

[0103] Therefore, as described above, the methods, apparatus, and computer program products of the exemplary embodiments provide an enforcement mechanism regarding the maximum number of PDU sessions per network slice in a communication system. Specific UE behavior policies regarding UEs can be determined by network entities. In some embodiments, the methods, apparatus, and computer program products provide an enforcement mechanism in a manner that is coordinated among UEs having PDU sessions.

[0104] As described above, Figure 5-7 is a flowchart of various methods that can be performed, for example, by apparatus 200 and / or according to a computer program product, according to exemplary embodiments of the present disclosure. It should be understood that each block of the flowchart, and combinations of blocks within the flowchart, can be implemented by various means, such as hardware, firmware, processors, circuits, and / or other devices related to the execution of software, including one or more computer program instructions. For example, one or more of the procedures described above can be embodied by computer program instructions. In this regard, computer program instructions that embody the procedures described above may be stored in a memory device 204 of an apparatus employing embodiments of the present disclosure and executed by the processor 202 of the apparatus. As understood, any such computer program instructions can be loaded into a computer or other programmable device (e.g., hardware) to create a machine, thereby causing the resulting computer or other programmable device to implement the functions specified in the flowchart blocks. These computer program instructions may also be stored in computer-readable memory and may instruct the computer or other programmable device to function in a particular way, thereby causing the instructions stored in computer-readable memory to produce a manufactured item, and the execution of the instructions to implement the functions specified in the flowchart blocks. Computer program instructions may be loaded into a computer or other programmable device, and a series of actions may be performed on the computer or other programmable device to create a computer implementation process, thereby providing the instructions executed on the computer or other programmable device to perform actions to implement the functions specified in the flowchart blocks.

[0105] Therefore, a computer program product is defined as a computer program product in which computer program instructions, such as computer-readable program code portions, are stored in at least one non-temporary computer-readable storage medium, and the computer program instructions, such as computer-readable program code portions, are configured to perform the functions described above at runtime, for example, in relation to the communication flowchart in Figure 3-5 or as part of the system in Figure 1. In other embodiments, the computer program instructions, such as computer-readable program code portions, do not need to be stored or otherwise embodied in a non-temporary computer-readable storage medium; instead, they may be embodied in a temporary medium, which is also configured to perform the functions described above at runtime.

[0106] Therefore, the blocks in a flowchart support combinations of means for performing a specified function, and combinations of actions for performing a specified function. It should also be understood that one or more blocks in a flowchart, and combinations of blocks within a flowchart, can be implemented by a dedicated hardware-based computer system or a combination of dedicated hardware and computer instructions to perform a specified function.

[0107] In some embodiments, certain behaviors among those described above may be modified or further enhanced. Furthermore, in some embodiments, additional optional behaviors may be included. Modifications, additions, or enhancements to the above behaviors may be performed in any order and in any combination.

[0108] Accordingly, this specification provides, in exemplary embodiments, methods, apparatus, and computer program products for providing operator control of user device behavior in registering with and unregistering to network slices, and in establishing and releasing PDU sessions in communication systems. Specific UE behavior policies with respect to the UE may be determined by the network entity.

[0109] In one exemplary embodiment, a method is provided in which a network entity of a communication system receives a registration request message from a user device (UE). The method may further include, at least in part, determining i) one or more PLMN (Public Land Mobile Network) types or PLMN identities associated with UE behavior relating to the UE, and ii) versions of the associated UE behavior policies for each of the one or more PLMN types or PLMN identities, based at least in part on the registration request message. The method may further include, in response to the request for a UE behavior policy, requesting a UE behavior policy from another network entity based at least in part on i) one or more PLMN types or PLMN identities, or ii) versions of the associated UE behavior policies. The method may further include providing the UE with UE configuration information in a registration approval message, wherein the UE configuration information includes an indication of one or more PLMN types or PLMN identities and versions of the associated UE behavior policies.

[0110] In some embodiments, the method provides a UE with UE configuration update information when a PLMN type or PLMN identity indicates a visited public land mobile network (VPLMN) type or VPLMN identity and a UE behavior policy allows the corresponding VPLMN to modify one or more aspects of the UE behavior policy, the UE configuration update information may further include an indication of an updated version of the relevant UE behavior policy relating to the VPLMN or VPLMN identity.

[0111] In some embodiments, the method may further include subscribing to subscription information updates for UE behavior policies associated with a UE. In some embodiments, the method further includes receiving subscription information updates to UE behavior policies associated with a UE. In some embodiments, the method further includes providing UE configuration update information to a UE, wherein the UE configuration update information includes an indication of an updated version of the associated UE behavior policy. In some embodiments, subscription information to a UE behavior policy is received when a policy control function updates the UE behavior policy.

[0112] In some embodiments, the method further includes receiving one or more authorization flags, the one or more of which indicate whether the visited PLMN, or the PLMN identity of the visited PLMN, is authorized to modify the UE behavior policy with respect to one or more components of the UE behavior policy.

[0113] In some embodiments, the PLMN is at least one of a Home Public Land Mobile Network (HPLMN) type or a Visited Public Land Mobile Network (VPLMN) type. In some embodiments, the registration request message further includes information indicating that the UE supports or requires the configuration of a UE behavior policy.

[0114] In one exemplary embodiment, a device is provided in a network entity of a communication system that includes means for receiving a registration request message from a user device (UE). The device may further include means for determining, at least in part, i) one or more PLMN (Public Land Mobile Network) types or PLMN identities associated with UE behavior relating to the UE, and ii) versions of the associated UE behavior policies for each of the one or more PLMN types or PLMN identities, based at least in part on the registration request message. The device may further include means for requesting a UE behavior policy from another network entity in response to a request for a UE behavior policy, based at least in part on i) one or more PLMN types or PLMN identities, or ii) versions of the associated UE behavior policies. The device may further include means for providing the UE with UE configuration information in a registration approval message, wherein the UE configuration information includes an indication of one or more PLMN types or PLMN identities and versions of the associated UE behavior policies.

[0115] In some embodiments, the device provides means for providing UE configuration update information to a UE when a PLMN type or PLMN identity indicates a visited public land mobile network (VPLMN) type or VPLMN identity, and a UE behavior policy allows a corresponding VPLMN to modify one or more aspects of the UE behavior policy, wherein the UE configuration update information includes an indication of an updated version of the relevant UE behavior policy relating to the VPLMN or VPLMN identity.

[0116] In some embodiments, the device may further include means for subscribing to subscription information updates for UE behavior policies associated with a UE. In some embodiments, the method further includes receiving subscription information updates to UE behavior policies associated with a UE. In some embodiments, the device may further include means for providing UE configuration update information to a UE, wherein the UE configuration update information includes an indication of an updated version of the associated UE behavior policy. In some embodiments, subscription information to a UE behavior policy is received when a policy control function updates the UE behavior policy.

[0117] In some embodiments, the device further includes means for receiving one or more authorization flags, the one or more authorization flags indicating whether the visited PLMN, or the PLMN identity of the visited PLMN, is authorized to modify the UE behavior policy with respect to one or more components of the UE behavior policy.

[0118] In some embodiments, the PLMN is at least one of a Home Public Land Mobile Network (HPLMN) type or a Visited Public Land Mobile Network (VPLMN) type. In some embodiments, the registration request message further includes information indicating that the UE supports or requires the configuration of a UE behavior policy.

[0119] In another exemplary embodiment, a device can be provided comprising at least one processor and at least one memory containing computer program code for one or more programs, wherein at least one memory and computer program code are configured by at least one processor to cause the device to receive registration request messages from user equipment (UEs) in at least one network entity of a communication system. The device may further include computer program code configured by at least one processor to cause the device to determine, at least, based at least in part on the registration request message, i) one or more PLMN (Public Land Mobile Network) types or PLMN identities associated with UE behavior relating to the UE, and ii) versions of the associated UE behavior policies for each of the one or more PLMN types or PLMN identities. The device may further include computer program code configured by at least one processor to cause the device to request UE behavior policies from another network entity in response to a request for a UE behavior policy, at least, based at least in part on i) one or more PLMN types or PLMN identities, or ii) at least one of the associated UE behavior policy versions. The device may include computer program code configured by at least one processor to cause the device to provide UE configuration information to at least the UE in a registration approval message, and the UE configuration information may include an indication of one or more PLMN types or PLMN identities and the respective versions of the associated UE behavior policy.

[0120] In some embodiments, the device may include, by at least one processor, computer program code configured to cause the device to provide UE configuration update information to the UE when the PLMN type or PLMN identity indicates a Visited Public Land Mobile Network (VPLMN) type or VPLMN identity, and the UE behavior policy allows the corresponding VPLMN to modify one or more aspects of the UE behavior policy, and the UE configuration update information may further include an indication of an updated version of the relevant UE behavior policy relating to the VPLMN or VPLMN identity.

[0121] In some embodiments, the device may include computer program code configured by at least one processor to cause the device to subscribe to subscription information updates for UE behavior policies associated with the UE. In some embodiments, the device may include computer program code configured by at least one processor to cause the device to receive subscription information updates for UE behavior policies associated with the UE. In some embodiments, the device may include computer program code configured by at least one processor to cause the device to provide UE configuration update information to the UE, the UE configuration update information including an indication of an updated version of the associated UE behavior policy. In some embodiments, subscription information for the UE behavior policy is received when a policy control function updates the UE behavior policy.

[0122] In some embodiments, the device may include computer program code configured by at least one processor to cause the device to receive at least one authorization flag, the one or more authorization flags indicating whether the visited PLMN, or the visited PLMN's PLMN identity, is authorized to modify the UE behavior policy with respect to one or more components of the UE behavior policy.

[0123] In some embodiments, the PLMN is at least one of a Home Public Land Mobile Network (HPLMN) type or a Visited Public Land Mobile Network (VPLMN) type. In some embodiments, the registration request message further includes information indicating that the UE supports or requires the configuration of a UE behavior policy.

[0124] In another exemplary embodiment, a computer program product can be provided comprising a non-temporary computer-readable storage medium storing computer executable program code instructions, wherein the computer executable program code instructions include program code instructions configured to receive registration request messages from user equipment (UEs) in a network entity of a communication system at runtime. The computer executable program code instructions including the program code instructions may be further configured to determine, at runtime, at least in part, based on the registration request message, i) one or more PLMN (Public Land Mobile Network) types or PLMN identities associated with UE behavior relating to the UE, and ii) versions of the associated UE behavior policies for each of the one or more PLMN types or PLMN identities. The computer executable program code instructions including the program code instructions may be further configured to request a UE behavior policy from another network entity at runtime in response to a request for a UE behavior policy, at least in part based on i) one or more PLMN types or PLMN identities, or ii) versions of the associated UE behavior policies. Computer executable program code instructions, including program code instructions, provide the UE with UE configuration information in a registration and approval message at runtime, and the UE configuration information may be further configured to include one or more PLMN types or PLMN identities and their respective versions of the associated UE behavior policy.

[0125] In some embodiments, a computer executable program code instruction, including a program code instruction, may, at runtime, provide the UE with UE configuration update information if the PLMN type or PLMN identity indicates a Visited Public Land Mobile Network (VPLMN) type or VPLMN identity, and the UE behavior policy allows the corresponding VPLMN to modify one or more aspects of the UE behavior policy, and the UE configuration update information may be further configured to include an indication of an updated version of the relevant UE behavior policy relating to the VPLMN or VPLMN identity.

[0126] In some embodiments, a computer executable program code instruction, including a program code instruction, may be further configured at runtime to subscribe to subscription information updates regarding UE behavior policies associated with the UE. In some embodiments, a computer executable program code instruction, including a program code instruction, may be further configured at runtime to receive subscription information updates to UE behavior policies associated with the UE. In some embodiments, a computer executable program code instruction, including a program code instruction, may be further configured at runtime to provide UE configuration update information to the UE, and the UE configuration update information may be further configured to include an indication of the updated version of the associated UE behavior policy. In some embodiments, subscription information to the UE behavior policy is received when a policy control function updates the UE behavior policy.

[0127] In some embodiments, a computer executable program code instruction, including a program code instruction, may be further configured to receive one or more authorization flags at runtime, and the one or more authorization flags may indicate whether the visited PLMN, or the PLMN identity of the visited PLMN, is authorized to modify the UE behavior policy with respect to one or more components of the UE behavior policy.

[0128] In some embodiments, the PLMN is at least one of a Home Public Land Mobile Network (HPLMN) type or a Visited Public Land Mobile Network (VPLMN) type. In some embodiments, the registration request message further includes information indicating that the UE supports or requires the configuration of a UE behavior policy.

[0129] In one exemplary embodiment, a method is provided in which a user device receives a registration approval message from a network entity of a communication system in response to a registration request message previously sent from a UE to a network entity, wherein the UE configuration information includes one or more indications of one or more PLMN types or PLMN identities associated with UE behavior relating to the UE. The method may further include adapting the UE behavior according to the received UE behavior in accordance with the UE behavior policy indicated in the registration approval message.

[0130] In some embodiments, the method further includes storing one or more PLMN types or PLMN identities and their respective versions of associated UE behavior policies.

[0131] In some embodiments, the method further includes providing a registration request message to a network entity, the registration request message including an indication of whether the UE supports or requires the configuration of a UE behavior policy.

[0132] In some embodiments, the method further includes storing in the UE each version of the UE behavior associated with one or more PLMN types or PLMN identities, wherein the storage is performed before the UE receives the registration approval message. In some embodiments, the storage of each version of the associated UE behavior is performed when a previous registration approval message, which includes UE configuration information, is received.

[0133] In some embodiments, the registration request message further includes an indication of the version of the currently configured UE behavior policy. In some embodiments, the registration approval message further includes a command for the user device to request all S-NSSAIs of the configured NSSAI, or a command for the user device to request all S-NSSAIs of the NSSAI configured by default. In some embodiments, the UE configuration information further includes an indication of each version of the UE behavior associated with the one or more PLMN types or PLMN identities.

[0134] In another exemplary embodiment, a user device is provided with means for receiving a registration approval message from a network entity of a communication system in response to a registration request message previously sent from a UE to a network entity, wherein the UE configuration information includes one or more indications of one or more PLMN types or PLMN identities associated with UE behavior relating to the UE. The device may further be configured with means for adapting UE behavior according to the received UE behavior in accordance with the UE behavior policy indicated in the registration approval message.

[0135] In some embodiments, the device may be further configured to include means for storing one or more PLMN types or PLMN identities and their respective versions of associated UE behavior policies.

[0136] In some embodiments, the device may be further configured with means for providing a registration request message to a network entity, the registration request message including an indication of whether the UE supports or requires the configuration of a UE behavior policy.

[0137] In some embodiments, the device is further configured to include means for storing in the UE each version of UE behavior associated with one or more PLMN types or PLMN identities, wherein the storage is performed before the UE receives the registration approval message. In some embodiments, the storage of each version of associated UE behavior is performed upon receipt of a previous registration approval message, which includes UE configuration information.

[0138] In some embodiments, the registration request message further includes an indication of the version of the currently configured UE behavior policy. In some embodiments, the registration approval message further includes a command for the user device to request all S-NSSAIs of the configured NSSAI, or a command for the user device to request all S-NSSAIs of the NSSAI configured by default. In some embodiments, the UE configuration information further includes an indication of each version of the UE behavior associated with the one or more PLMN types or PLMN identities.

[0139] In another exemplary embodiment, a device can be provided comprising at least one processor and at least one memory containing computer program code for one or more programs, wherein the at least one memory and computer program code are configured by at least one processor to cause the device to receive a registration approval message containing UE configuration information from a network entity of a communication system in response to a registration request message previously sent from a UE to a network entity in a user device, and the UE configuration information contains one or more indications of one or more PLMN types or PLMN identities associated with UE behavior relating to the UE. The at least one memory and computer program code may be further configured by at least one processor to cause the device to adapt UE behavior according to the received UE behavior, in accordance with the UE behavior policy indicated in the registration approval message.

[0140] In some embodiments, at least one memory and computer program code may be further configured, by at least one processor, to cause the device to store at least one or more PLMN types or PLMN identities and their respective versions of associated UE behavior policies.

[0141] In some embodiments, at least one memory and computer program code may be further configured by at least one processor to cause the device to provide at least one registration request message to a network entity, the registration request message including an indication of whether the UE supports or requires the configuration of a UE behavior policy.

[0142] In some embodiments, at least one memory and computer program code may be further configured by at least one processor to cause the device to store, at least in the UE, each version of the UE behavior associated with the one or more PLMN types or PLMN identities, and such storage may occur before the UE receives the registration approval message. In some embodiments, the storage of each version of the associated UE behavior occurs upon receipt of a previous registration approval message, which includes UE configuration information.

[0143] In some embodiments, the registration request message further includes an indication of the version of the currently configured UE behavior policy. In some embodiments, the registration approval message further includes a command for the user device to request all S-NSSAIs of the configured NSSAI, or a command for the user device to request all S-NSSAIs of the NSSAI configured by default. In some embodiments, the UE configuration information further includes an indication of each version of the UE behavior associated with the one or more PLMN types or PLMN identities.

[0144] In another exemplary embodiment, a computer program product can be provided comprising a non-temporary computer-readable storage medium storing computer executable program code instructions, wherein the computer executable program code instructions are configured, at runtime, in a user device, to receive a registration approval message from a network entity of a communication system, in response to a registration request message previously sent from a UE to a network entity, and the UE configuration information includes one or more indications of one or more PLMN types or PLMN identities associated with UE behavior relating to the UE. The computer executable program code instructions, including the program code instructions, may be further configured, at runtime, to adapt UE behavior according to the received UE behavior, in accordance with the UE behavior policy indicated in the registration approval message.

[0145] In some embodiments, a computer executable program code instruction, including program code instructions, may be further configured to store, at runtime, one or more PLMN types or PLMN identities and their respective versions of associated UE behavior policies.

[0146] In some embodiments, a computer executable program code instruction, including a program code instruction, may be further configured to provide a registration request message to a network entity at runtime, and the registration request message may include an indication of whether the UE supports or requires the configuration of a UE behavior policy.

[0147] In some embodiments, a computer executable program code instruction, including program code instructions, may be further configured to store, at runtime, in the UE, each version of the UE behavior associated with the one or more PLMN types or PLMN identities, such that the storage occurs before the UE receives the registration approval message. In some embodiments, the storage of each version of the associated UE behavior occurs upon receiving a previous registration approval message, which includes UE configuration information.

[0148] In some embodiments, the registration request message further includes an indication of the version of the currently configured UE behavior policy. In some embodiments, the registration approval message further includes a command for the user device to request all S-NSSAIs of the configured NSSAI, or a command for the user device to request all S-NSSAIs of the NSSAI configured by default. In some embodiments, the UE configuration information further includes an indication of each version of the UE behavior associated with the one or more PLMN types or PLMN identities.

[0149] Those skilled in the art in the field to which the invention relates, who benefit from the teachings shown in the foregoing description and the associated drawings, will recall many modifications and other embodiments of the invention described herein. Therefore, it should be understood that the invention is not limited to the specific embodiments disclosed, and that modifications and other embodiments are also intended to be included within the scope of the appended claims. Certain terms are used herein, but they are used only in a general descriptive sense and not for limiting purposes.

Claims

1. In a network entity of a communication system, receiving a registration request message from a user device (UE) and Based at least partially on the registration request message, i) determine one or more PLMN (Public Land Mobile Network) types or PLMN identities associated with UE behavior relating to the UE, and ii) determine the version of the associated UE behavior policy for each of the one or more PLMN types or PLMN identities, i) requesting a UE behavior policy from another network entity based at least partially on one or more PLMN types or PLMN identities, or ii) at least one version of the associated UE behavior policy, The UE is provided with UE configuration information in a registration approval message, wherein the UE configuration information includes an indication of one or more PLMN types or PLMN identities and the respective versions of the associated UE behavior policy. Methods that include...

2. The method according to claim 1, wherein the PLMN is at least one of the Home Public Land Mobile Network (HPLMN) type or the Visited Public Land Mobile Network (VPLMN) type.

3. The method according to claim 1 or 2, wherein the registration request message further includes information indicating that the UE supports or requires the configuration of a UE behavior policy.

4. A method in a user device (UE), Providing a registration request message to a network entity of a communication system, wherein the registration request message includes an indication of whether the UE supports the configuration of a UE behavior policy. In response to a registration request message, the network entity receives a registration approval message containing UE configuration information indicating a UE behavior policy for UE behavior in registering with at least one network slice, wherein the UE configuration information includes an indication of one or more PLMN identities associated with the UE behavior. The UE behavior must be adapted in accordance with the UE behavior policy indicated in the registration approval message. Includes, A method wherein the registration approval message includes configured network slice selection support information (NSSAI), and the UE configuration information includes a command in which the user device requests only single network slice selection support information (S-NSSAI) that has an active application associated with it.

5. To remember one or more PLMN types or PLMN identities and their respective versions of the associated UE behavior policy. The method according to claim 4, further comprising:

6. Providing a registration request message to a network entity, wherein the registration request message includes an indication of whether the UE supports or requires the configuration of a UE behavior policy. The method according to claim 4 or 5, further comprising:

7. The method according to claim 4 or 5, wherein the registration request message further includes an indication of the version of the currently configured UE behavior policy.

8. The method according to claim 4 or 5, wherein the registration approval message further includes a command for the user device to request all single network slice selection support information (S-NSSAI) of the configured network slice selection support information (NSSAI), or a command for the user device to request all S-NSSAI of the network slice selection support information (NSSAI) that is configured by default.

9. The method according to claim 4 or 5, wherein the UE configuration information further includes indications for each version of the UE behavior associated with the one or more PLMN types or PLMN identities.

10. In the UE, storing each version of the UE behavior associated with one or more PLMN types or PLMN identities, wherein the storage is performed before the UE receives the registration approval message. The method according to claim 4 or 5, further comprising:

11. The method according to claim 4 or 5, wherein each version of the associated UE behavior is stored when a pre-registration approval message containing UE configuration information is received.

12. A device comprising at least one processor and at least one memory containing computer program code for one or more programs, wherein the at least one memory and the computer program code are provided to the device by the at least one processor, In a network entity of a communication system, a registration request message is received from a user device (UE). Based at least partially on the registration request message, the system determines: i) one or more PLMN (Public Land Mobile Network) types or PLMN identities associated with UE behavior regarding the UE, and ii) the version of the associated UE behavior policy for each of the one or more PLMN types or PLMN identities. In response to a request for a UE behavior policy, another network entity may request a UE behavior policy based at least partially on i) one or more PLMN types or PLMN identities, or ii) at least one version of the associated UE behavior policy. The UE is required to provide UE configuration information in the registration approval message, and the UE configuration information includes one or more PLMN types or PLMN identities, along with indications of the respective versions of the associated UE behavior policy. A device configured in such a way.

13. The apparatus according to claim 12, wherein the PLMN is at least one of the Home Public Land Mobile Network (HPLMN) type or the Visited Public Land Mobile Network (VPLMN) type.

14. At least one memory and computer program code are provided to the device by at least one processor, If a PLMN type or PLMN identity indicates a VPLMN type or VPLMN identity, and the UE behavior policy allows the corresponding VPLMN to modify one or more aspects of the UE behavior policy, then the UE is required to provide UE configuration update information, which includes an indication of the updated version of the relevant UE behavior policy relating to the VPLMN or VPLMN identity. The apparatus according to claim 12 or 13, further configured as follows.

15. At least one memory and computer program code are provided to the device by at least one processor, Subscribe to updates on subscription information related to UE behavior policies associated with UE. The apparatus according to claim 12 or 13, further configured as follows.

Images