ADJUSTING USER EQUIPMENT BEHAVIOR CONTROLLED BY A HOME PUBLIC LAND MOBILE NETWORK - Patent application

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 June 15, 2021, which claims priority to U.S. Provisional Patent Application No. 63 / 048,818, filed July 7, 2020, both of which are incorporated by reference in their entireties herein. [Background technology]

[0002] This section presents aspects that may be helpful in making the invention better understood. Accordingly, the statements in this section are to be read in this light and not understood as admissions that something is in the prior art or that something is not in the prior art.

[0003] The fourth generation (4G) wireless mobile telecommunications technology, also called Long Term Evolution (LTE) technology, was designed to provide high capacity mobile multimedia at high data rates, especially for human interaction. The 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) networks.

[0004] 3rd Generation Partnership Project (3GPP) 5G technology is a next-generation wireless system and network architecture capable of delivering ultra-wideband and ultra-robust, low-latency connectivity. 5G technology will help improve the various telecommunications services offered to end users and support massive broadband that will deliver gigabytes of bandwidth per second on demand for both uplink and downlink transmissions. Next-generation systems utilizing the 5G architecture will utilize virtualized Radio Access Network (RAN) 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. A network slice is considered as an independent virtualized end-to-end network. Currently, standardization efforts are underway to simplify how network slices are defined, how user equipment registers and deregisters to network slices, and how protocol data unit (PDU) sessions are admitted to network slices. However, in current 3GPP specifications, enforcing such activities is complex and typically user equipment dependent, which means that network operators have little control over user equipment behavior during such activities. Summary of the Invention [Means for solving the problem]

[0006] According to an exemplary embodiment, a method, an apparatus, and a computer program product are provided for providing operator control of user equipment behavior in registering and deregistering with a network slice, and in establishing and releasing PDU sessions in a communication system. A specific UE behavior policy for a UE can be determined by a network entity.

[0007] In one exemplary embodiment, a method is provided at a network entity of a communication system, the method including receiving a registration request message from a user equipment (UE). The method may further include determining, 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 for the UE, and ii) a version of an associated UE behavior policy for each of the one or more PLMN types or PLMN identities. The method may further include, in response to the request for the UE behavior policy, requesting a UE behavior policy from another network entity based at least in part on at least one of i) the one or more PLMN types or PLMN identities, or ii) the version of the associated UE behavior policy. The method may further include providing UE configuration information to the UE in a registration accept message, the UE configuration information including an indication of one or more of the PLMN types or PLMN identities and respective versions of the associated UE behavior policy.

[0008] In some embodiments, the method may further include, 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, providing UE configuration update information to the UE, where the UE configuration update information includes an indication of an updated version of the associated UE behavior policy for the VPLMN or VPLMN identity.

[0009] In some embodiments, the method may further include subscribing to subscription information updates relating to UE behavior policies associated with the UE. In some embodiments, the method further includes receiving subscription information updates to UE behavior policies associated with the UE. In some embodiments, the method further includes providing 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, the subscription information to the UE behavior policy is received when the 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 authorization flags indicating whether the visited PLMN, or a 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 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 configuration of a UE behavior policy.

[0012] In one exemplary embodiment, an apparatus is provided comprising means for receiving a registration request message from a user equipment (UE) at a network entity of a communication system. The apparatus may further include means for determining, 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 for the UE, and ii) a version of an associated UE behavior policy for each of the one or more PLMN types or PLMN identities. The apparatus may further include means for requesting a UE behavior policy from another network entity, based at least in part on at least one of i) the one or more PLMN types or PLMN identities, or ii) a version of the associated UE behavior policy, in response to the request for the UE behavior policy. The apparatus may further include means for providing UE configuration information in a registration accept message to the UE, the UE configuration information including an indication of one or more of the PLMN types or PLMN identities and a respective version of the associated UE behavior policy.

[0013] In some embodiments, the apparatus may further include means for providing UE configuration update information to the UE 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, where the UE configuration update information includes an indication of an updated version of the associated UE behavior policy for the VPLMN or VPLMN identity.

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

[0015] In some embodiments, the apparatus further includes means for receiving one or more authorization flags, the one or more authorization flags indicating whether the visited PLMN, or a 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.

[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 configuration of a UE behavior policy.

[0017] In another example embodiment, an apparatus may be provided, comprising at least one processor and at least one memory including computer program code for one or more programs, the at least one memory and the computer program code configured by the at least one processor to cause the apparatus to receive, at least at a network entity of a communication system, a registration request message from a user equipment (UE). The apparatus may include computer program code further configured by the at least one processor to cause the apparatus to determine, at least based in part on the registration request message, i) one or more PLMN (Public Land Mobile Network) types or PLMN identities associated with a UE behavior for the UE, and ii) a version of an associated UE behavior policy for each of the one or more PLMN types or PLMN identities. The apparatus may include computer program code further configured by the at least one processor to cause the apparatus to request, at least in response to a request for a UE behavior policy, a UE behavior policy from another network entity based at least in part on at least one of i) the one or more PLMN types or PLMN identities, or ii) a version of the associated UE behavior policy. The apparatus may include computer program code further configured, by the at least one processor, to cause the apparatus to at least provide, to the UE, UE configuration information in the registration accept message, the UE configuration information including an indication of one or more of a PLMN type or PLMN identity and a respective version of an associated UE behavior policy.

[0018] In some embodiments, the apparatus may include computer program code further configured, by the at least one processor, to cause the apparatus to provide UE configuration update information to the UE at least when the PLMN type or PLMN identity indicates a visited public land mobile network (VPLMN) type or VPLMN identity and the UE behavior policy permits the 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 associated UE behavior policy with respect to the VPLMN or VPLMN identity.

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

[0020] In some embodiments, the apparatus may include computer program code further configured, by the at least one processor, to cause the apparatus to at least receive one or more authorization flags, the one or more authorization flags indicating whether the visited PLMN, or a 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.

[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 configuration of a UE behavior policy.

[0022] In another example embodiment, a computer program product may be provided comprising at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored thereon, the computer-executable program code instructions including program code instructions configured, upon execution, to receive a registration request message from a user equipment (UE) at a network entity of a communication system. The computer-executable program code instructions including the program code instructions may be further configured, upon execution, to determine, 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 a UE behavior for the UE, and ii) a version of an associated UE behavior policy 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, upon execution, to request a UE behavior policy from another network entity, based at least in part on at least one of i) the one or more PLMN types or PLMN identities, or ii) a version of the associated UE behavior policy, in response to the request for the UE behavior policy. The computer executable program code instructions, including the program code instructions, may be further configured, upon execution, to provide UE configuration information in a registration accept message to the UE, the UE configuration information including an indication of one or more of a PLMN type or PLMN identity and a respective version of an associated UE behavior policy.

[0023] In some embodiments, the computer-executable program code instructions including the program code instructions may be further configured, when executed, to: provide UE configuration update information to the UE 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, the UE configuration update information including an indication of an updated version of the associated UE behavior policy with respect to the VPLMN or VPLMN identity.

[0024] In some embodiments, the computer executable program code instructions including the program code instructions, when executed, may be further configured to subscribe to subscription information updates relating to a UE behavior policy associated with the UE. In some embodiments, the computer executable program code instructions including the program code instructions, when executed, may be further configured to receive subscription information updates to a UE behavior policy associated with the UE. In some embodiments, the computer executable program code instructions including the program code instructions, when executed, may be further configured 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, the subscription information to the UE behavior policy is received when the policy control function updates the UE behavior policy.

[0025] In some embodiments, the computer executable program code instructions including the program code instructions may be further configured, upon execution, to receive one or more authorization flags, the one or more authorization flags indicating whether the visited PLMN, or a 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.

[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 configuration of a UE behavior policy.

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

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

[0029] 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 configuration of a UE behavior policy.

[0030] In some embodiments, the method further includes storing, at the UE, a version of each UE behavior associated with the one or more PLMN types or PLMN identities, wherein said storing occurs prior to receiving the registration accept message at the UE. In some embodiments, storing the version of each associated UE behavior occurs upon receipt of a previous registration accept message including UE configuration information.

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

[0032] In another example embodiment, an apparatus is provided comprising: means for receiving, in a user equipment, from a network entity of a communications system in response to a registration request message previously transmitted from the UE to the network entity, a registration accept message including UE configuration information, the UE configuration information including one or more indications of one or more PLMN types or PLMN identities associated with a UE behavior for the UE. The apparatus may be further configured with means for adapting the UE behavior according to the received UE behavior in accordance with a UE behavior policy indicated in the registration accept message.

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

[0034] In some embodiments, the apparatus 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 configuration of a UE behavior policy.

[0035] In some embodiments, the apparatus is further configured with means for storing, at the UE, a version of each UE behavior associated with the one or more PLMN types or PLMN identities, wherein the storing occurs prior to receiving the registration accept message at the UE. In some embodiments, storing the version of each associated UE behavior occurs upon receipt of a previous registration accept message including UE configuration information.

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

[0037] In another example embodiment, an apparatus may be provided that includes at least one processor and at least one memory including computer program code for one or more programs, where the at least one memory and computer program code are configured by the at least one processor to cause the apparatus to at least receive, at a user equipment, from a network entity of the communication system in response to a registration request message previously transmitted from the UE to the network entity, a registration accept 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 a UE behavior for the UE. The at least one memory and computer program code may be further configured by the at least one processor to at least cause the apparatus to adapt the UE behavior according to the received UE behavior according to a UE behavior policy indicated in the registration accept message.

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

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

[0040] In some embodiments, the at least one memory and computer program code may be further configured by the at least one processor to cause the apparatus to at least store, at the UE, respective versions of UE behavior associated with the one or more PLMN types or PLMN identities, the storing occurring prior to receiving the registration accept message at the UE. In some embodiments, storing respective versions of associated UE behavior occurs upon receipt of a previous registration accept message including UE configuration information.

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

[0042] In another example embodiment, a computer program product may be provided comprising at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored thereon, the computer-executable program code instructions being configured, when executed, at a user equipment to: receive, from a network entity of the communications system, in response to a registration request message previously transmitted from the UE to the network entity, a registration accept message including UE configuration information, the UE configuration information including one or more indications of one or more PLMN types or PLMN identities associated with a UE behavior for the UE. The computer-executable program code instructions including the program code instructions, when executed, may be further configured to adapt the UE behavior according to the received UE behavior in accordance with a UE behavior policy indicated in the registration accept message.

[0043] In some embodiments, the computer-executable program code instructions including the program code instructions may be further configured to, upon execution, store one or more PLMN types or PLMN identities and respective versions of associated UE behavior policies.

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

[0045] In some embodiments, the computer executable program code instructions including the program code instructions, when executed, may be further configured to store, at the UE, a respective version of a UE behavior associated with the one or more PLMN types or PLMN identities, the storing occurring prior to receiving, at the UE, the registration accept message. In some embodiments, storing the respective version of an associated UE behavior occurs upon receipt of a previous registration accept message including UE configuration information.

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

[0047] Having described in general terms certain exemplary embodiments of the present disclosure, reference is now made hereinafter to the accompanying drawings, which are not necessarily drawn to scale, and in which: [Brief description of the drawings]

[0048] [Figure 1] FIG. 1 illustrates an exemplary system environment in which implementations according to exemplary embodiments of the present invention may take place. [Diagram 2] FIG. 2 is a block diagram of a core network device configured according to an exemplary embodiment of the present disclosure. [Diagram 3] FIG. 2 illustrates an example transmission within a communication system for determining a user equipment policy for a user equipment, in accordance with an example embodiment of the present disclosure. [Figure 4]FIG. 2 illustrates an exemplary transmission within a communication system for determining a user equipment policy for a user equipment determined by a policy control function in accordance with an exemplary embodiment of the present disclosure. [Diagram 5] FIG. 2 illustrates an example workflow of various components of a communication system according to an example embodiment. [Figure 6] FIG. 2 illustrates an example workflow of various components of a communication system according to an example embodiment. [Figure 7] FIG. 2 illustrates an example workflow of various components of a communication system according to an example embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0049] Some embodiments of the present invention will now be described in more detail hereinafter with reference to the accompanying drawings. Some, but not all, embodiments of the present invention are shown in the accompanying drawings. Indeed, various embodiments of the present invention may 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 will satisfy applicable legal requirements. Like reference numbers refer to like elements throughout. As used herein, the terms "data," "content," "information," and similar terms may be used interchangeably to refer to data that may be transmitted, received, and / or stored according to embodiments of the present invention. Thus, the use of any such terms should not be construed as limiting the spirit and scope of the embodiments of the present invention.

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

[0051] 3rd Generation Partnership Project (3GPP) fifth generation (5G) technology is the next generation of wireless systems and network architectures capable of delivering ultra-wideband and ultra-robust, low-latency connectivity. 5G technology will help improve the various telecommunications services offered to end users and support massive broadband that will deliver gigabytes of bandwidth per second on demand for both uplink and downlink transmissions. Next generation systems utilizing the 5G architecture will utilize virtualized Radio Access Network (RAN) and core network functions.

[0052] The embodiments are described herein in conjunction with an exemplary communication system and related techniques for providing data transport in a communication system. However, it should be understood that the scope of the claims is not limited to the particular type of communication system and / or process disclosed. The embodiments may be implemented in various other types of communication systems using alternative processes and operations. Although described in the context of a wireless cellular system utilizing 3rd Generation Partnership Project (3GPP) system elements, such as 3GPP Next Generation System (5G), the disclosed embodiments may be readily adapted to various other types of communication systems.

[0053] In accordance with the exemplary embodiments implemented in a 5G communication system environment, one or more 3GPP technical specifications (TS) and technical reports (TR) provide further description of user equipment and network elements / functions and / or operations that interact 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 the exemplary embodiments are well suited for implementation associated with the 5G-related 3GPP standards discussed 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. A network slice is considered as an independent virtualized end-to-end network. Currently, standardization efforts are underway to simplify how network slices are defined, how user equipment is registered and deregistered from a network slice, and how protocol data unit (PDU) sessions are admitted to a network slice. However, in current 3GPP specifications, enforcing such activities is complex and typically user equipment dependent, which means that network operators have little control over user equipment behavior during such activities. Although the present disclosure may describe the invention in the context of a 5G communication system, the invention also applies to other networks and network technologies such as, but not limited to, 4G, LTE, 3G, etc.

[0055] According to example embodiments, methods, apparatus, and computer program products are provided for determining which user equipment policies apply to a user equipment, thereby providing operator control of user equipment behavior in registering and deregistering with a network slice, as well as in establishing and releasing PDU sessions in a communication system.

[0056] In a communication system, such as a 5G system, a user equipment (UE) may subscribe to one or more network slices. A UE subscription may include multiple network slices, each identified by a network slice selection assistance information (NSSAI). Thus, a network slice may be identified by a single network slice selection assistance information (S-NSSAI). One or more of these S-NSSAIs may be marked as a default S-NSSAI. The default S-NSSAI may identify a network slice that the UE may or should be using, for example, if the UE has not requested a network slice in a specifically 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 is no constraint on the behavior of a UE requesting one or more configured NSSAIs. Under current standards, the only mechanism available is for the UE's Home Public Land Mobile Network (HPLMN) to configure the UE with a Default configured NSSAI that the UE uses when it has not yet received a configured NSSAI in the Serving PLMN.

[0057] However, there are some problems with this approach, such as the fact that at any time the UE may omit to request an S-NSSAI that the operator wants the UE to use to provide the UE with essential services or updates. Also, many UEs currently on the market are configured in such cases to proceed with requests for all S-NSSAIs in the configured NSSAI without considering the actual need, which may mean, for example, that it is futile for an operator to deploy a network slice-specific Access and Mobility management Function (AMF), since all UEs that behave in this way will typically be AMFs that support all S-NSSAIs simultaneously. Such a situation for a network may mean that only a general AMF is used and must switch between network slices or be configured to work in or between multiple network slices, which may result in inefficient network messaging, lack of specialized network slices, and / or inefficient signaling of NSSAIs, etc. For example, under current standards and associated network / UE configurations, a UE configured for a massive 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 (e.g., only when the UE needs to update its software).MIoT-specific AMF has been one of the main drivers for network slicing, e.g. in evolved packet systems (EPS) in Dedicated core networks, which were defined to support mobility management entities (MMEs) primarily or exclusively dedicated to Internet of Things (IoT) technologies 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 is capable of or configured to access more than a certain number of network slices, e.g., more than eight network slices, the UE may or does apply logic outside the network operator's control in deciding which of the eight or more network slices it will not request.

[0059] Conversely, some UEs may request only one network slice in connection with an application and then decide to abandon the requested network slice after the application that required it stops using it. Some operators may want to minimize this type of behavior if applications are launched and released quite frequently. Thus, operators have no way to enforce network slice registration / deregistration behavior on UEs, or UE behavior regarding associating PDU sessions with network slices. According to current relevant standards, for example, operators who deploy only AMFs that serve all network slices simultaneously may actually want to enforce for all UEs the minimization of UE joining and leaving the network slices through the registration procedure, since in fact, such AMFs are at least almost meaningless in the network, unless, for example, some network slices also have a limit on the number of UEs connected, unless the UE requires additional authentication and authorization to connect, or unless they have a default Access Point Name (APN).

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

[0061] Thus, methods, apparatus, and computer program products are described herein to address some or all of the above limitations of current relevant standards and / or other limitations of current relevant standards, i.e., methods, apparatus, and computer program products that allow an operator to control UE behavior. By enabling the control of UE behavior by a network operator, network slice operator, APN operator, AMF operator, or another network entity, operators can tailor UE behavior in their network, network slice, or network entity in a manner that is adapted to the deployment and that can minimize signaling load, reducing unnecessary bandwidth dedicated to such signaling and registration / deregistration and other such activities. A similar approach can also be employed within a network slice to control which PDU sessions are established, which can or should be established, for example, only if an application requests it. According to current relevant standards, currently, there is no need for a UE to establish a PDU session with a Data Network Name (DNN). For example, if these are configured in the UE route selection policy (URSP), the establishment of that PDU session is only required when an application requires it. In other words, the described approach allows an operator to control UE behavior when forming a Requested NSSAI and when requesting a PDU session within a network slice.

[0062] In some embodiments, the UE operator may control the UE behavior based at least in part on UE behavior information associated with at least one of an associated HPLMN or a visited public land mobile network (VPLMN). For example, the HPLMN may provide UE behavior information for controlling the UE behavior and may not provide authorization for changing the UE behavior by the VPLMN. Thus, the UE operator may control the UE behavior based at least in part on UE behavior information from the associated HPLMN. As another example, the HPLMN may not provide information for controlling the UE behavior and thus the VPLMN may provide the UE behavior information. Thus, the UE operator may control the UE behavior based at least in part on UE behavior information from the associated VPLMN. As yet another example, if the HPLMN provides authorization to the VPLMN to change the UE behavior, the UE operator may control the UE behavior based at least in part on UE behavior information associated with the HPLMN, the VPLMN, or a combination thereof (e.g., using UE behavior information from both the HPLMN and the VPLMN).

[0063] In some embodiments, the network entity and / or the UE can be configured to allow the operator of the network to control UE behavior. In some embodiments, in addition to being able to provide the UE with the configured NSSAI and URSP, the network entity can also provide the UE with configuration information that instructs the UE to reconfigure the UE to control behavior in forming the requested NSSAI and also in establishing the PDU session. This information can be on a per S-NSSAI basis, a per DNN basis, and / or a global basis.

[0064] FIG. 1 illustrates an exemplary communication system environment in which implementations according to exemplary embodiments of the present invention may occur. The depiction of the system environment 100 in FIG. 1 is not intended to limit or otherwise constrain the embodiments described and contemplated herein to any particular configuration of elements or systems, nor is it intended to exclude alternative configurations or systems of the set of configurations and systems that may be used in connection with embodiments of the present invention. Instead, FIG. 1 and the system environment 100 disclosed therein are presented only to provide an exemplary basis and context for facilitating some of the functionality, aspects, and uses of the methods, apparatus, and computer program products disclosed and contemplated herein. Although many of the aspects and components illustrated in FIG. 1 are shown as separate and distinct elements, it should be understood that other configurations may be used in connection with the methods, apparatus, and computer programs described herein, including configurations that combine, omit, and / or add aspects and / or components.

[0065] As shown in FIG. 1, the system environment includes one or more user equipment (UE) 102 configured to communicate wirelessly with a network 106 via an access network or the like. Although the user equipment can be configured in a variety of different ways, the user equipment can be embodied as a mobile terminal, such as a personal digital assistant (PDA), a mobile phone, a smart phone, a pager, a mobile television, a gaming device, a laptop computer, a camera, a tablet computer, a communicator, a pad, a headset, a touch surface, a video recorder, an audio / video player, a radio, an electronic book, a positioning device (e.g., a global positioning system (GPS) device), or any combination of the aforementioned types and other types of voice and text and multimodal communication systems. The system environment 100 shown in FIG. 1 also includes one or more access points 104a and 104b, such as base stations, including but not limited to Node Bs and evolved Node Bs (eNBs). A cellular access point, such as a base station, may define and serve one or more cells. The access points may then communicate with a network 106, such as a core network, via a gateway such that the access points establish a cellular radio access network through which the user equipment 102 may communicate with the network. The system environment 100 of FIG. 1 may include multiple different cellular radio access cells and / or networks or portions of such networks, including, for example, a 5G radio access network, a Long-Term Evolution (LTE) radio access network, a universal mobile telecommunications system (UMTS) radio access network, etc. In some example implementations, equipment and other infrastructure associated with the multiple different cellular radio access networks may be located in or near a structure and / or other equipment associated with a particular access point, such as access points 104a and 104b.

[0066] In some implementations of the system environment 100, the cellular radio access networks served by the access points 104a, 104b, and any other access points in a given area are identical in the sense that the user equipment 102 moves from an area served by the access point 104a to an area served by the access point 104b. The user equipment 102 can access the 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, for example, a base station, to facilitate operation of the access points and management of the user equipment 102 communicating with the access points. As shown in FIG. 1, the system may also include one or more wireless local area networks (WLANs), each of which may be served by a WLAN access point 108 configured to establish wireless communications with the user equipment. Thus, the user equipment may communicate with the network via a WLAN access point, as shown by a solid line in FIG. 1, or alternatively, via a cellular access point, as shown by a dashed line. The radio access network and the core network 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 accomplished by an apparatus 200 as shown in FIG. 2. The apparatus may be embodied and / or incorporated by one or more UEs, such as user equipment 102, or any of the other devices discussed with respect to FIG. 1, such as access points 104a and / or 104b, one or more WLAN access points 108, and / or devices that may be incorporated or otherwise associated with the system environment 100. Alternatively, the apparatus 200 may be embodied by another device external to such a device. For example, the apparatus may be embodied by a computing device, such as a personal computer, a computer workstation, a server, or any of a variety of mobile computing devices, such as a mobile terminal, including but not limited to a smartphone, tablet computer, and the like.

[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 (UE) Function (UEF), User Node Function (UENS ... 5G 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 device 200 is embodied, the device 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 co-processor or any other processing circuitry that assists or is otherwise associated with the processor) can communicate with the memory device via a bus for passing information between components of the device. The memory device may be non-transitory 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) with gates configured to store data (e.g., bits) that may be retrievable 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. for enabling the device to perform various functions in accordance with the exemplary embodiments of the present 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 mentioned 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., chips) that include materials, components, and / or wires on a structural assembly (e.g., a baseboard). The structural assembly may provide physical strength, size conservation, and / or electrical interaction limitations for the component circuits contained therein. Thus, the apparatus may in some cases be configured to implement embodiments of the present invention on a single chip or as a single "system-on-chip." Thus, in some cases, the chip or chipset may constitute a means for performing one or more operations to provide the functionality described herein.

[0071] The processor 202 may be embodied in a variety of ways. For example, the processor may be embodied as one or more of a variety of hardware processing means including a processing circuit, such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing element with or without an associated DSP, or various other processing circuits including integrated circuits, such as an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), a microcontroller unit (MCU), a hardware accelerator, a dedicated computer chip, etc. Thus, in some embodiments, the processor may include one or more processing cores configured to perform independently. A multi-core processor may enable multi-processing within a single physical package. Additionally or alternatively, the processor may include one or more processors in a tandem configuration via a bus to enable independent execution of instructions, pipelining, and / or multi-threaded processing.

[0072] In an exemplary embodiment, 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 hard-coded functions. Thus, whether configured by hardware or software methods or a combination thereof, the processor may represent an entity (e.g., physically embodied in a circuit) that is correspondingly configured to perform operations in accordance with embodiments of the present invention. Thus, for example, when the processor is embodied as an ASIC, FPGA, or the like, the processor may be hardware that is specially configured to perform the operations described herein. Alternatively, as another example, when the processor is embodied as an execution body of software instructions, the instructions may specially configure the processor to perform the algorithms and / or operations described herein when 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) that is configured to employ embodiments of the present invention by further configuring the processor with instructions to perform the algorithms and / or operations described herein. A 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 and from any other device or module in communication with the device. In this regard, the communication interface may include, for example, an antenna (or multiple antennas) and supporting hardware and / or software for enabling communication with a wireless communication network. Additionally or alternatively, the communication interface may include circuitry for interacting with the antenna to cause transmission of signals via the antenna or to process reception of signals received via the antenna. In some environments, alternatively or in addition, the communication interface may support wired communication. Thus, for example, the communication interface may include a communication modem and / or other hardware / software for supporting communication via cable, digital subscriber line (DSL), universal serial bus (USB), or other mechanisms.

[0074] Hereinafter, exemplary transmissions between the UE and network entities are presented. The following exemplary transmissions provide the expected steps or messaging required. Information enclosed in "[]" is optional and may be included, for example, when the UE is provided with a configured NSSAI and / or URSP at the same time that the UE behavior is configured.

[0075] FIG. 3 illustrates exemplary transmissions between a UE and various network entities of a communication system for configuring the UE with a UE behavior policy.

[0076] In operation 0, the UE 301 may provide an initial REGISTRATION REQUEST message with a PLMN (e.g., VPLMN or HPLMN) to the AMF 303 via the (Radio) Access Network ((R)AN) node 302. The REGISTRATION REQUEST message may indicate whether the UE is currently configured with 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 configuration of a UE behavior policy. The AMF 303 may determine one or more PLMN types or PLMN identities associated with UE behavior for the UE 301 based at least in part on the registration request message. The PLMN type may include a HPLMN type or a VPLMN type. The PLMN identity may provide an indication of which aspects (i.e., features, 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 a version of the UE behavior policy.

[0077] In operation 1, the AMF 303 may obtain access and mobility information from the UDM 304. The 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 if 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 if the non-access stratum message is a protocol data unit session establishment non-access stratum message.

[0078] Further, the AMF 303 may request and / or obtain a UE behavior policy from the UDM 304 based at least in part on at least one of one or more PLMN types or PLMN identities, or a version of an associated UE behavior policy. In particular, the AMF 303 may provide an indication of a version of the UE behavior policy to the UDM 304, which may then provide the UE behavior policy to the AMF 303. The UE behavior policy may describe UE behavior control for the UE 301. Furthermore, in some embodiments, the UE behavior policy may describe one or more authorization flags. The one or more authorization flags may indicate whether the VPLMN is authorized to modify the UE behavior policy. In some embodiments, the AMF 304 may request the UE behavior policy from the UDM 304 during a Nudm_UECM_registration message between the AMF 303 and the UDM 304.

[0079] In some embodiments, the HPLMN may selectively provide authorization for certain portions of the UE behavior policy. For example, the HPLMN may allow modification and / or configuration of the UE behavior to register with a particular network slice or all configured network slices based at least in part on usage. As another example, the HPLMN may allow modification and / or configuration of the UE behavior for the time before the UE can decide to deregister with a particular network slice. In some embodiments, the HPLMN may also provide ranges for the configuration of policies in the VPLMN or set maximum and / or minimum values ​​for the UE behavior policy if applicable.

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

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

[0082] In operation 3, the AMF 303 may subscribe to subscription information updates from the UDM 304. The AMF 303 may subscribe to such updates via a Nudm_SDM_subscribe message. When the AMF 303 subscribes to the subscription information updates, the AMF 303 may receive one or more updates regarding an associated UE behavior policy when the UE behavior policy is changed and / or modified in the associated HPLMN.

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

[0084] In operation 5, once the UE 301 is in CM connected mode, the AMF 303 may provide a UE configuration update to the UE 301. In some embodiments, the UE configuration update may be operable to provide operator control of UE behavior in registering and deregistering with a network slice, and / or establishing and releasing PDU sessions in a communication system. In some embodiments, the AMF may determine a desired UE behavior with respect to requested NSSAI formation and / or DNN establishment for a particular UE, a particular network slice, a global network or communication system, and / or the like, 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 for the configured NSSAI, URSP, network, network slice, PDU session, AMF, and / or the like. In some embodiments, the UE configuration update command message may further include UE behavior support information, which may be similar or identical to the UE behavior support information. In some embodiments, the UE behavior assistance information may include an indication as to whether the associated UE policy is from an HPLMN, a VPLMN, or a combination thereof, and / or an indication as to the version of the UE behavior policy. In some embodiments, if the 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), the UE configuration update information may include an indication of an updated version of the associated UE behavior policy for the VPLMN or VPLMN identity. Thus, the VPLMN can modify the UE behavior policy locally without having to update the subscription to the HPLMN.

[0085] For example, a message including UE behavior assistance information and / or the like may be sent from a network entity such as the AMF. In some embodiments, a network entity (e.g., AMF) may send such a message (e.g., including UE behavior assistance information) to the UE, such that the UE may be configured to follow the network entity instructions for control of UE behavior during establishment and / or release of a PDU session with a network slice. When the UE receives the message, the UE may apply or otherwise provide a new behavior provided by the network, for example, in the UE behavior assistance information. In some embodiments, the UE behavior assistance information may provide an instruction that the UE is configured to request all S-NSSAIs in the configured NSSAI. In some embodiments, the UE behavior assistance 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, the UE behavior assistance information may provide an instruction that the UE is configured to always request at least a well-specified subset of S-NSSAIs in the configured NSSAI. In some embodiments, the well-specified subset of S-NSSAIs in the configured NSSAI may be or may include at least the default S-NSSAIs provided by the HPLMN. In some embodiments, the well-specified subset may be identified by a flag associated with some or each S-NSSAI provided to the UE in the configured NSSAI or the default configured NSSAI. In some embodiments, the UE behavior assistance information may provide instructions that the UE is configured to request only S-NSSAIs that have active applications associated with the UE, e.g., applications operated by the UE.In some embodiments, the UE behavior support information may provide instructions that if the UE is configured to only request an S-NSSA if an active application is using the network slice, the UE is configured to provide an explicit timer to cause the UE to release a network slice that is no longer being used by any application, e.g., by excluding the network slice to be released from the next requested NSSAI, thereby allowing the operator to implement a kind of hysteresis.

[0086] In some embodiments, the UE behavior support information may provide instructions that the UE is configured to always establish all PDU sessions associated with the S-NSSAI. In some embodiments, the UE behavior support information may provide instructions that the UE is configured to establish a specific PDU session or a subset of PDU sessions by default. In some embodiments, the specific PDU session or a subset of PDU sessions may be explicitly identified in the UE configuration information or a message including the UE configuration information. In some embodiments, the UE configuration information may be provided in the URSP by associating a flag with the DNN associated with the S-NSSAI. In some embodiments, the serving PLMN may use a local policy or a default DNN for 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 a local storage. For example, the network may be configured to provide an identification of a PLMN type or PLMN Id (e.g., without an indication of the respective version of the UE behavior) in subsequent UE configuration information in a registration acceptance message if the network has previously provided the UE with the relevant UE configuration information (e.g., in a previous registration acceptance or otherwise). In response to receiving the subsequent UE configuration information, the UE may be configured to retrieve the corresponding version information in the local storage and adapt the UE behavior according to the corresponding UE behavior policy (e.g., also stored in a database). Thus, the UE may be configured to store the UE behavior policy and associated version information in the local storage for later use. Alternatively, the UE may be configured to store default UE behavior policies corresponding to one or more PLMN types or PLMN Ids in the local storage for later use.

[0088] In some embodiments, the UE behavior assistance information may be optionally provided in or with a downlink non-access stratum transport message from the network entity to the user equipment. In some other embodiments, the UE behavior assistance information may be optionally provided in or with a UE configuration update message from the network entity to the user equipment. In some embodiments, the UE behavior assistance information may include configuration information including instructions for the user equipment to request all S-NSSAIs of configured NSSAIs or instructions for the user equipment to request all S-NSSAIs of default configured NSSAIs. In some embodiments, the registration accept or reject message, the downlink non-access stratum transport message, or the UE configuration update message may include instructions for the user equipment to always request a subset of S-NSSAIs in the configured NSSAIs. 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 the user equipment in the configured NSSAI or the default configured NSSAI, where the one or more S-NSSAIs are determined by the network based on a local policy or based on information received from subscription information of the user equipment. In some embodiments, the registration accept or reject message, the downlink non-access stratum transport message, or the UE configuration update message may include instructions for the user equipment to request only S-NSSAIs that have active applications. In some embodiments, the registration accept or reject message, the downlink non-access stratum transport message, or the UE configuration update message may include instructions for the user equipment to release network slices that are no longer being used by any application, thereby excluding the released network slices from the next requested NSSAI.

[0089] In operation 6, the UE 301 may provide a UE configuration update complete message to the AMF 303. The UE configuration update complete message may include an acknowledgment that the UE 301 has successfully received the UE configuration update and / or performed the associated updates.

[0090] In operation 7, the AMF 303 may provide an acknowledgement to the UDM 304 that the UE 301 has been successfully configured. The AMF may provide this acknowledgement if the HPLMN provides a UE behavior policy. In some embodiments, the AMF 303 may provide the acknowledgement via a Nudm_SDM_Info request message.

[0091] FIG. 4 illustrates exemplary transmissions between a UE and various network entities of a communication system for configuring UE behavior using a UE configuration update procedure.

[0092] In action 0, the PCF 401 associated with the HPLMN may decide to update UE behavior policies. The PCF 401 may securely configure the UE behavior using the UE Configuration Update procedure for transparent UE Policy delivery defined in clause 4.2.4.3 of TS 23.502. These policies are identified by specific Policy Section Identifiers (PSI). The HPLMN may include one or more PSIs for policies that can be authorized for modification by the VPLMN, for example by using one or more authorization flags.

[0093] In operation 1, the PCF 401 may provide an indication of the updated UE behavior policy to the AMF 301. The PCF 401 may provide the indication via a Namf_Communication_N1N2MessageTransfer message.

[0094] In operation 2, the AMF 303 may attempt to provide a configuration update to the UE 301. However, if the UE 301 is not in a connection management (CM) connected mode, the AMF 303 may provide a network-triggered service request to the UE 301. Alternatively, the UE 301 may provide a service request to the AMF 303.

[0095] In Operation 3, when UE 301 enters the CM connected mode, AMF 303 may provide a UE configuration update to UE 301. Operation 3 in Figure 4 may be substantially similar to Operation 5 described in Figure 3.

[0096] In operation 4, the UE 301 may provide a UE configuration update complete message to the AMF 303. Operation 4 in Figure 4 may be substantially similar to operation 6 described in Figure 3.

[0097] In operation 5, the AMF 303 may provide an acknowledgement to the PCF 401 that the UE 301 has been successfully configured. In some embodiments, the AMF 303 may provide the acknowledgement via a Namf_Communication_N1MessageNotify message.

[0098] 5, an example workflow of various components of a communication system is illustrated according to an example embodiment, such as a UE, R(AN), AMF, UDM, PCF, or other components, such as those previously described in connection with other figures. Referring now to FIG. 5, a method 500 is illustrated that may be performed by one or more of the described entities, including means for receiving a registration request message from a user equipment at a network entity of the communication system, such as the processor 202 and the communication interface 208, at 501. In some embodiments, the method 500 may include determining, at 502, one or more PLMN types or one or more PLMN identities and a version of a UE behavior policy for the UE. The one or more PLMN types or one or more PLMN identities and a version of a UE behavior policy for the UE may be determined based at least in part on the registration request message. The PLMN type may include a HPLMN type or a VPLMN type. In some embodiments, the method 500 may include requesting a UE behavior policy, for example, from a UDM. The request for the UE behavior policy may be based at least in part 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, at 503. In some embodiments, the method 500 further includes receiving one or more authorization flags. The one or more authorization flags may be received along with the UE behavior policy. The one or more authorization flags indicate whether the visited PLMN is authorized to modify the UE behavior policy. In some embodiments, the method 500 may include providing UE configuration information to the UE, at 504. The UE configuration information may include an indication of one or more PLMN types or one or more PLMN identities, and a version of the associated UE behavior policy.

[0099] In some embodiments, if the 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, the method 500 may further include providing UE configuration update information to the UE, where the UE configuration update information includes an indication of an updated version of the associated UE behavior policy for the VPLMN or VPLMN identity.

[0100] 6, an example workflow of various components of a communication system is illustrated according to an example embodiment, such as a UE, R(AN), AMF, UDM, PCF, or other components, such as those previously described in connection with other figures. Referring now to FIG. 6, a method 600 is illustrated that may be performed by one or more of the described entities including means for subscribing to subscription information updates related to UE behavior policies, such as the processor 202 and the communication interface 208, at 601. In some embodiments, the method 600 may include receiving, at 602, a subscription information update to a UE behavior policy. In some embodiments, the subscription information to a UE behavior policy is received when a policy charging function updates the UE behavior policy. In some embodiments, the method 600 may include providing, at 603, UE configuration update information to the UE. The UE configuration update information may include an indication of an updated version of the associated UE behavior policy.

[0101] 7, an example workflow of various components of a communication system is illustrated according to an example embodiment, such as a UE, R(AN), AMF, UDM, PCF, or other components, such as those previously described in connection with other figures. Referring now to FIG. 7, a method 700 is illustrated that may be performed by one or more of the described entities including means for providing a registration request message to a network entity, such as the processor 202 and the communication interface 208, at 701. The registration request message includes an indication of whether the UE supports or requires configuration of a UE behavior policy. In some embodiments, the registration request message further includes an indication of a version of a currently configured UE behavior policy. In some embodiments, the method 700 may include receiving a registration acknowledgement message from the network, at 702. The registration acknowledgement message may include UE configuration information, which may include an indication of one or more of one or more PLMN types or PLMN identities and respective versions of associated UE behavior policies. The registration acknowledgement message may include the UE behavior policy. In some embodiments, the method 700 may include storing one or more PLMN types or PLMN identities, such as those received in a registration accept message, and respective versions of associated UE behavior policies. In some embodiments, the registration accept message may include instructions for the user equipment to request all S-NSSAIs for configured NSSAIs or instructions for the user equipment to request all S-NSSAIs for default configured NSSAIs. In some embodiments, the method 700 may include adapting the UE behavior according to the UE behavior policies indicated in the registration accept message.

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

[0103] Thus, as described above, the method, apparatus, and computer program product of the exemplary embodiments provide an enforcement mechanism regarding the maximum number of PDU sessions per network slice in a communication system. A specific UE behavior policy for a UE can be determined by a network entity. In some embodiments, the method, apparatus, and computer program product provide the enforcement mechanism in a coordinated manner between UEs having PDU sessions.

[0104] As mentioned above, FIGS. 5-7 are flowcharts of various methods that may be performed, for example, by the apparatus 200 and / or in accordance with a computer program product, according to an exemplary embodiment of the present disclosure. It should be understood that each block of the flowchart, and combinations of blocks in the flowchart, may be implemented by various means, such as hardware, firmware, processors, circuits, and / or other devices associated with the execution of software that includes one or more computer program instructions. For example, one or more of the procedures described above may be embodied by computer program instructions. In this regard, computer program instructions that embody the procedures described above may be stored by the memory device 204 of an apparatus employing an embodiment of the present disclosure and executed by the processor 202 of the apparatus. As will be understood, any such computer program instructions may be loaded into a computer or other programmable apparatus (e.g., hardware) to create a machine, such that the resulting computer or other programmable apparatus implements the functions specified in the flowchart blocks. These computer program instructions may be stored in a computer-readable memory and may instruct the computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory create an article of manufacture, and execution of the instructions implements the functions specified in the flowchart blocks. The computer program instructions may be loaded into a computer or other programmable device and a sequence of operations executed on the computer or other programmable device to create a computer-implemented process, whereby the instructions executing on the computer or other programmable device provide operations for implementing the functions specified in the flowchart blocks.

[0105] Thus, a computer program product is defined when computer program instructions, such as computer readable program code portions, are stored by at least one non-transitory computer readable storage medium, and the computer program instructions, such as computer readable program code portions, when executed are configured to perform the functions described above, for example, in connection with the communication flow charts of Figures 3-5 or as part of the system of Figure 1. In other embodiments, computer program instructions, such as computer readable program code portions, need not be stored or otherwise embodied by a non-transitory computer readable storage medium, but instead may be embodied by a transitory medium, where the computer program instructions, such as computer readable program code portions, are also configured to perform the functions described above when executed.

[0106] Thus, the blocks of the flowcharts support combinations of means for performing the specified functions, and combinations of operations for performing the specified functions. It will also be understood that one or more blocks of the flowcharts, and combinations of blocks within the flowcharts, can be implemented by a dedicated hardware-based computer system that performs the specified functions, or a combination of dedicated hardware and computer instructions.

[0107] In some embodiments, certain of the above operations may be modified or further enhanced. Additionally, in some embodiments, additional optional operations may be included. Modifications, additions, or enhancements to the above operations may be performed in any order and in any combination.

[0108] Thus, provided herein, in accordance with example embodiments, are methods, apparatus, and computer program products for providing operator control of user equipment behavior in registering and deregistering with a network slice, and in establishing and releasing PDU sessions in a communication system. A particular UE behavior policy for a UE may be determined by a network entity.

[0109] In one exemplary embodiment, a method is provided at a network entity of a communication system, the method including receiving a registration request message from a user equipment (UE). The method may further include determining, 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 for the UE, and ii) a version of an associated UE behavior policy for each of the one or more PLMN types or PLMN identities. The method may further include, in response to the request for the UE behavior policy, requesting a UE behavior policy from another network entity based at least in part on at least one of i) the one or more PLMN types or PLMN identities, or ii) the version of the associated UE behavior policy. The method may further include providing UE configuration information to the UE in a registration accept message, the UE configuration information including an indication of one or more of the PLMN types or PLMN identities and respective versions of the associated UE behavior policy.

[0110] In some embodiments, the method may further include, 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, providing UE configuration update information to the UE, where the UE configuration update information includes an indication of an updated version of the associated UE behavior policy for the VPLMN or VPLMN identity.

[0111] In some embodiments, the method may further include subscribing to subscription information updates relating to UE behavior policies associated with the UE. In some embodiments, the method further includes receiving subscription information updates to UE behavior policies associated with the UE. In some embodiments, the method further includes providing 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, the subscription information to the UE behavior policy is received when the 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 authorization flags indicating whether the visited PLMN, or a 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.

[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 configuration of a UE behavior policy.

[0114] In one exemplary embodiment, an apparatus is provided comprising means for receiving a registration request message from a user equipment (UE) at a network entity of a communication system. The apparatus may further include means for determining, 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 for the UE, and ii) a version of an associated UE behavior policy for each of the one or more PLMN types or PLMN identities. The apparatus may further include means for requesting a UE behavior policy from another network entity, based at least in part on at least one of i) the one or more PLMN types or PLMN identities, or ii) a version of the associated UE behavior policy, in response to the request for the UE behavior policy. The apparatus may further include means for providing UE configuration information in a registration accept message to the UE, the UE configuration information including an indication of one or more of the PLMN types or PLMN identities and a respective version of the associated UE behavior policy.

[0115] In some embodiments, the apparatus may further include means for providing UE configuration update information to the UE 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, where the UE configuration update information includes an indication of an updated version of the associated UE behavior policy for the VPLMN or VPLMN identity.

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

[0117] In some embodiments, the apparatus further includes means for receiving one or more authorization flags, the one or more authorization flags indicating whether the visited PLMN, or a 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.

[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 configuration of a UE behavior policy.

[0119] In another example embodiment, an apparatus may be provided, comprising at least one processor and at least one memory including computer program code for one or more programs, the at least one memory and the computer program code configured by the at least one processor to cause the apparatus to receive, at least at a network entity of a communication system, a registration request message from a user equipment (UE). The apparatus may include computer program code further configured by the at least one processor to cause the apparatus to determine, at least based in part on the registration request message, i) one or more PLMN (Public Land Mobile Network) types or PLMN identities associated with a UE behavior for the UE, and ii) a version of an associated UE behavior policy for each of the one or more PLMN types or PLMN identities. The apparatus may include computer program code further configured by the at least one processor to cause the apparatus to request, at least in response to a request for a UE behavior policy, a UE behavior policy from another network entity based at least in part on at least one of i) the one or more PLMN types or PLMN identities, or ii) a version of the associated UE behavior policy. The apparatus may include computer program code further configured, by the at least one processor, to cause the apparatus to at least provide, to the UE, UE configuration information in the registration accept message, the UE configuration information including an indication of one or more of a PLMN type or PLMN identity and a respective version of an associated UE behavior policy.

[0120] In some embodiments, the apparatus may include computer program code further configured, by the at least one processor, to cause the apparatus to provide UE configuration update information to the UE at least when the PLMN type or PLMN identity indicates a visited public land mobile network (VPLMN) type or VPLMN identity and the UE behavior policy permits the 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 associated UE behavior policy with respect to the VPLMN or VPLMN identity.

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

[0122] In some embodiments, the apparatus may include computer program code further configured, by the at least one processor, to cause the apparatus to at least receive one or more authorization flags, the one or more authorization flags indicating whether the visited PLMN, or a 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.

[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 configuration of a UE behavior policy.

[0124] In another example embodiment, a computer program product may be provided comprising at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored thereon, the computer-executable program code instructions including program code instructions configured, upon execution, to receive a registration request message from a user equipment (UE) at a network entity of a communication system. The computer-executable program code instructions including the program code instructions may be further configured, upon execution, to determine, 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 a UE behavior for the UE, and ii) a version of an associated UE behavior policy 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, upon execution, to request a UE behavior policy from another network entity, based at least in part on at least one of i) the one or more PLMN types or PLMN identities, or ii) a version of the associated UE behavior policy, in response to the request for the UE behavior policy. The computer executable program code instructions, including the program code instructions, when executed, may be further configured to provide UE configuration information in a registration accept message to the UE, the UE configuration information including an indication of one or more PLMN types or PLMN identities and respective versions of associated UE behavior policies.

[0125] In some embodiments, the computer-executable program code instructions including the program code instructions may be further configured, when executed, to: provide UE configuration update information to the UE 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, the UE configuration update information including an indication of an updated version of the associated UE behavior policy with respect to the VPLMN or VPLMN identity.

[0126] In some embodiments, the computer executable program code instructions including the program code instructions, when executed, may be further configured to subscribe to subscription information updates relating to a UE behavior policy associated with the UE. In some embodiments, the computer executable program code instructions including the program code instructions, when executed, may be further configured to receive subscription information updates to a UE behavior policy associated with the UE. In some embodiments, the computer executable program code instructions including the program code instructions, when executed, may be further configured 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, the subscription information to the UE behavior policy is received when the policy control function updates the UE behavior policy.

[0127] In some embodiments, the computer executable program code instructions including the program code instructions may be further configured, upon execution, to receive one or more authorization flags, the one or more authorization flags indicating whether the visited PLMN, or a 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.

[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 configuration of a UE behavior policy.

[0129] In one example embodiment, a method is provided that includes receiving, in a user equipment, from a network entity of a communication system in response to a registration request message previously transmitted from the UE to the network entity, a registration accept message including UE configuration information, the UE configuration information including one or more indications of one or more PLMN types or PLMN identities associated with a UE behavior for the UE. The method may further include adapting the UE behavior according to the received UE behavior in accordance with a UE behavior policy indicated in the registration accept message.

[0130] In some embodiments, the method further includes storing one or more PLMN types or PLMN identities and 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 configuration of a UE behavior policy.

[0132] In some embodiments, the method further includes storing, at the UE, a version of each UE behavior associated with the one or more PLMN types or PLMN identities, said storing occurring prior to receiving the registration accept message at the UE. In some embodiments, storing the version of each associated UE behavior occurs upon receipt of a previous registration accept message including UE configuration information.

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

[0134] In another example embodiment, an apparatus is provided comprising: means for receiving, in a user equipment, from a network entity of a communications system in response to a registration request message previously transmitted from the UE to the network entity, a registration accept message including UE configuration information, the UE configuration information including one or more indications of one or more PLMN types or PLMN identities associated with a UE behavior for the UE. The apparatus may be further configured with means for adapting the UE behavior according to the received UE behavior in accordance with a UE behavior policy indicated in the registration accept message.

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

[0136] In some embodiments, the apparatus 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 configuration of a UE behavior policy.

[0137] In some embodiments, the apparatus is further configured with means for storing, at the UE, a version of each UE behavior associated with the one or more PLMN types or PLMN identities, wherein the storing occurs prior to receiving the registration accept message at the UE. In some embodiments, storing the version of each associated UE behavior occurs upon receipt of a previous registration accept message including UE configuration information.

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

[0139] In another example embodiment, an apparatus may be provided comprising at least one processor and at least one memory including computer program code for one or more programs, where the at least one memory and computer program code are configured by the at least one processor to cause the apparatus to at least receive, at a user equipment, from a network entity of the communication system in response to a registration request message previously transmitted from the UE to the network entity, the registration accept message including UE configuration information, the UE configuration information including one or more indications of one or more PLMN types or PLMN identities associated with UE behavior for the UE. The at least one memory and computer program code may be further configured by the at least one processor to cause the apparatus to adapt the UE behavior according to the received UE behavior according to at least a UE behavior policy indicated in the registration accept message.

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

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

[0142] In some embodiments, the at least one memory and computer program code may be further configured by the at least one processor to cause the apparatus to at least store, at the UE, respective versions of UE behavior associated with the one or more PLMN types or PLMN identities, the storing occurring prior to receiving the registration accept message at the UE. In some embodiments, storing respective versions of associated UE behavior occurs upon receipt of a previous registration accept message including UE configuration information.

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

[0144] In another example embodiment, a computer program product may be provided comprising at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored thereon, the computer-executable program code instructions being configured, when executed, at a user equipment to: receive, from a network entity of the communications system, in response to a registration request message previously transmitted from the UE to the network entity, a registration accept message including UE configuration information, the UE configuration information including one or more indications of one or more PLMN types or PLMN identities associated with a UE behavior for the UE. The computer-executable program code instructions including the program code instructions, when executed, may be further configured to adapt the UE behavior according to the received UE behavior in accordance with a UE behavior policy indicated in the registration accept message.

[0145] In some embodiments, the computer-executable program code instructions including the program code instructions may be further configured to, upon execution, store one or more PLMN types or PLMN identities and respective versions of associated UE behavior policies.

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

[0147] In some embodiments, the computer executable program code instructions including the program code instructions, when executed, may be further configured to store, at the UE, a respective version of a UE behavior associated with the one or more PLMN types or PLMN identities, the storing occurring prior to receiving, at the UE, the registration accept message. In some embodiments, storing the respective version of an associated UE behavior occurs upon receipt of a previous registration accept message including UE configuration information.

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

[0149] Many modifications and other embodiments of the inventions described herein will come to mind to one skilled in the art to which this invention pertains having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. It is to be understood, therefore, that the invention is not limited to the specific embodiments disclosed, and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

1. receiving, at a network entity of a communication system, a registration request message from a user equipment (UE); determining, based at least in part on the registration request message, i) one or more public land mobile network (PLMN) types or PLMN identities associated with UE behavior for the UE, and ii) an associated UE behavior policy version for each of the one or more PLMN types or PLMN identities; 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 at least one of: i) one or more PLMN types or PLMN identities; or ii) an associated UE behavior policy version; providing UE configuration information in a registration accept message to the UE, the UE configuration information including an indication of one or more of a PLMN type or a PLMN identity and respective versions of associated UE behavior policies; A method comprising:

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

3. providing UE configuration update information to the UE if the PLMN type or PLMN identity indicates a VPLMN type or VPLMN identity and the UE behavior policy permits the corresponding VPLMN to modify one or more aspects of the UE behavior policy, the UE configuration update information including an indication of an updated version of an associated UE behavior policy for the VPLMN or VPLMN identity; The method of claim 1 further comprising:

4. Subscribing to subscription information updates regarding UE behavior policies associated with the UE The method of claim 1 further comprising:

5. receiving a subscription information update to a UE behavior policy associated with the UE; providing UE configuration update information to the UE, the UE configuration update information including an indication of an updated version of an associated UE behavior policy; The method of claim 4 further comprising:

6. The method of claim 5 , wherein when the policy control function updates the UE behavior policy, subscription information to the UE behavior policy is received.

7. receiving a UE behavior policy from another network entity; receiving one or more authorization flags, the one or more authorization flags indicating whether the visited PLMN, or a 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; The method of claim 1 further comprising:

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

9. receiving, at a user equipment (UE), from a network entity of the communication system in response to a registration request message previously transmitted from the UE to the network entity, a registration accept message including UE configuration information, the UE configuration information including one or more indications of one or more PLMN types or PLMN identities associated with UE behavior for the UE; Adapting the UE behavior according to the UE behavior policy indicated in the registration accept message; A method comprising:

10. Storing one or more PLMN types or PLMN identities and respective versions of associated UE behavior policies The method of claim 9 further comprising:

11. providing a registration request message to a network entity, the registration request message including an indication of whether the UE supports or requires configuration of a UE behavior policy; The method of claim 9 further comprising:

12. The method of claim 9 , wherein the registration request message further includes an indication of a version of the currently configured UE behavior policy.

13. 10. The method of claim 9, wherein the registration accept message further includes an instruction for the user equipment to request all single network slice selection assistance information (S-NSAI) of a configured network slice selection assistance information (NSAI), or an instruction for the user equipment to request all S-NSAI of a default configured network slice selection assistance information (NSSAI).

14. The method of claim 9 , wherein the UE configuration information further includes an indication of a respective version of UE behavior associated with the one or more PLMN types or PLMN identities.

15. storing, at the UE, respective versions of UE behaviors associated with the one or more PLMN types or PLMN identities, said storing being performed prior to receiving the registration accept message at the UE; The method of claim 9 further comprising:

16. The method of claim 15, wherein storing each version of the associated UE behavior is performed upon receipt of a previous registration accept message including the UE configuration information.

17. An apparatus comprising at least one processor and at least one memory containing computer program code for one or more programs, the at least one memory and the computer program code being transmitted by the at least one processor to the apparatus, at least: receiving, at a network entity of the communication system, a registration request message from a user equipment (UE); determining, based at least in part on the registration request message, i) one or more public land mobile network (PLMN) types or PLMN identities associated with UE behavior for the UE, and ii) an associated UE behavior policy version for each of the one or more PLMN types or PLMN identities; in response to the request for the UE behavior policy, requesting a UE behavior policy from another network entity based at least in part on at least one of: i) one or more PLMN types or PLMN identities; or ii) an associated UE behavior policy version; having the UE provide UE configuration information in the registration accept message, the UE configuration information including an indication of one or more of a PLMN type or a PLMN identity and a respective version of an associated UE behavior policy; The apparatus is configured so as to

18. 20. The apparatus of claim 17, wherein the PLMN is at least one of a Home Public Land Mobile Network (HPLMN) type or a Visited Public Land Mobile Network (VPLMN) type.

19. At least one memory and computer program code are configured to cause the device, by at least one processor, to at least: If the PLMN type or PLMN identity indicates a VPLMN type or VPLMN identity and the UE behavior policy permits the corresponding VPLMN to modify one or more aspects of the UE behavior policy, the UE configuration update information causes the UE to provide UE configuration update information, the UE configuration update information including an indication of an updated version of the associated UE behavior policy for the VPLMN or VPLMN identity. The apparatus of claim 17 further configured to:

20. At least one memory and computer program code are configured to cause the device, by at least one processor, to at least: Subscribe to subscription information updates regarding UE behavior policies associated with the UE The apparatus of claim 17 further configured to:

Images