Operator control over user equipment behavior in communication systems during registration and deregistration with network slices and establishment and release of PDU sessions.

Abstract

Methods, systems, apparatus, and computer program products for operator control of UE behavior during registration and deregistration with network slices and establishment and release of PDU sessions in a communication system. A network entity may transmit a registration acceptance message to the UE, which includes configuration information including instructions for the UE to request all Single Network Slice Selection Assistance Information (S-NSSAI) configured with Network Slice Selection Assistance Information (NSSAI) or instructions for the UE to request all S-NSSAIs configured by default with NSSAI. Alternatively, the network entity may transmit configuration information to the UE in a downlink non-access stratum transmission message or a UE configuration update message, which includes instructions for the UE to always establish all Protocol Data Unit (PDU) sessions for all data network names associated with a Single Network Slice Selection Assistance Information (S-NSSAI).

Description

[0001] This application is a divisional application of the invention patent application with international application number PCT / EP2021 / 066092, international application date June 15, 2021, entered the Chinese national phase on February 27, 2023, Chinese national application number 202180053340.9, entitled "Operator control of user equipment behavior during registration and deregistration with network slices and establishment and release of PDU sessions in a communication system". Background Technology This section introduces aspects that can help to better understand the invention. Therefore, the statements in this section should be understood from this perspective and should not be construed as an admission of what exists in the prior art or what does not exist in the prior art.

[0002] Fourth-generation (4G) wireless mobile telecommunications technology (also known as Long Term Evolution (LTE) technology) is designed to provide high-capacity mobile multimedia with high data rates, particularly for human interaction. Next-generation or fifth-generation (5G) technology is not only used for human interaction but also for machine-type communication in so-called Internet of Things (IoT) networks.

[0003] The 3rd Generation Partnership Project (3GPP) 5G technology is a next-generation radio system and network architecture that can provide extreme broadband and ultra-robust low-latency connectivity. 5G technology improves the various telecommunications services offered to end users and helps support massive broadband, i.e., providing gigabytes per second of bandwidth for both uplink and downlink transmissions on demand. Next-generation systems utilizing the 5G architecture leverage virtual radio access network (RAN) and core network functions.

[0004] In 5G networks, network slicing is a concept used to run multiple logical networks as virtually independent service operations on a shared physical infrastructure. A network slice is viewed as an independent, virtualized end-to-end network. Currently, standardization work is underway to simplify the definition of network slices, the registration and deregistration of user equipment (UEs) with network slices, and the admission of Protocol Data Unit (PDU) sessions to network slices. However, under current 3GPP specifications, implementing such activities is complex and typically left to the UEs, meaning network operators have little control over UE behavior during such activities. Summary of the Invention

[0005] Methods, apparatus, and computer program products are provided according to example embodiments to provide operator control over user equipment behavior in a communication system when registering and deregistering with network slices and establishing and releasing PDU sessions.

[0006] In one example embodiment, a method is provided, comprising: receiving a registration request message from a user equipment (UE) at a network entity of a communication system; if the registration request message includes information indicating that the UE supports or requires network control slice selection behavior, in response to receiving the registration request message, transmitting a registration acceptance or rejection message from the network entity to the UE, the configuration information including instructions for the UE to request all single network slice selection assistive information (S-NSSAI) configured with network slice selection assistive information (NSSAI) or instructions for the UE to request all S-NSSAIs configured by default with NSSAI; and providing the configuration information from the network entity to the UE via a downlink non-access stratum transmission message or a UE configuration update message, the configuration information including instructions for the UE to request all S-NSSAIs configured with NSSAI or instructions for the UE to request all S-NSSAIs configured by default with NSSAI. In some embodiments, the registration acceptance or rejection message or the downlink non-access stratum transmission or UE configuration update message includes instructions for the UE to always request a subset of S-NSSAIs from the configured NSSAIs. In some embodiments, a subset of S-NSSAIs is identified by one or more flags associated with each S-NSSAI provided to the user equipment in the configured NSSAIs or default configured NSSAIs, wherein the one or more S-NSSAIs are determined by the network based on local policies or based on information received from the user equipment's subscription information. In some embodiments, the registration accept or reject message or downlink non-access stratum transport or UE configuration update message includes instructions for the user equipment to request only S-NSSAIs with active applications. In some embodiments, the registration accept or reject message or downlink non-access stratum transport or UE configuration update message includes instructions for the user equipment to release network slices that are no longer used by any application, thereby excluding released network slices from the next requested NSSAI.

[0007] According to another embodiment, a method can be performed, the method comprising: receiving, at a user equipment, a registration acceptance or rejection message from a network entity in response to a registration request message previously transmitted from the user equipment to a network entity of a communication system, the registration request message including information indicating that the user equipment supports or requires network control slice selection behavior, the registration acceptance or rejection message including instructions for the user equipment to request all single network slice selection assistance information (S-NSSAI) configured with network slice selection assistance information (NSSAI) or instructions for the user equipment to request all S-NSSAIs that are configured by default with NSSAI; receiving a downlink non-access stratum transport message or a UE configuration update message including configuration information, the configuration information including instructions for the user equipment to request all S-NSSAIs configured with NSSAI or instructions for the user equipment to request all S-NSSAIs that are configured by default with NSSAI; and configuring the user equipment to request all S-NSSAIs configured with NSSAI or configured by default with NSSAI when the user equipment is in the communication system. In some embodiments, the registration accept or reject message, downlink non-access stratum transport message, or UE configuration update message includes an instruction for the user equipment to always request a subset of S-NSSAIs in the configured NSSAIs, the method further comprising: configuring the user equipment to always request a subset of S-NSSAIs in the configured NSSAIs. In some embodiments, the S-NSSAI subset is identified by one or more flags associated with each S-NSSAI provided to the user equipment in the configured NSSAIs or default configured NSSAIs. In some embodiments, the registration accept or reject message, downlink non-access stratum transport message, or UE configuration update message includes an instruction for the user equipment to request only S-NSSAIs with active applications, the method further comprising: configuring the user equipment to request only S-NSSAIs with active applications. In some embodiments, the registration accept or reject message downlink non-access stratum transmission message or UE configuration update message includes a timer configured to cause the user equipment to release a network slice that is no longer used by any application, thereby excluding the released network slice from the next requested NSSAI. The method further includes: configuring the user equipment to release a network slice that is no longer used by any application based on the value of the timer, and excluding the released network slice from the next requested NSSAI.

[0008] According to another embodiment, an apparatus may be provided, the apparatus including at least one processor and at least one memory, the at least one memory including computer program code for one or more programs, the at least one memory and the computer program code being configured together with the at least one processor to cause the apparatus to at least: receive a registration request message from a user equipment at the apparatus; if the registration request message includes information indicating that the user equipment supports or requires network control slice selection behavior, in response to receiving the registration request message, transmit from the apparatus to the user equipment a registration acceptance or rejection message including configuration information, the configuration information including instructions for the user equipment to request all single network slice selection assistance information (S-NSSAI) configured with network slice selection assistance information (NSSAI) or instructions for the user equipment to request all S-NSSAIs configured by default with NSSAI; and provide configuration information from the apparatus to the user equipment via a downlink non-access stratum transmission message or a UE configuration update message, the configuration information including instructions for the user equipment to request all S-NSSAIs configured with NSSAI or instructions for the user equipment to request all S-NSSAIs configured by default with NSSAI. In some embodiments, the registration accept or reject message or downlink non-access stratum transport or UE configuration update message includes 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 is identified by one or more flags associated with each S-NSSAI provided to the user equipment in the configured NSSAIs or default configured NSSAIs, wherein the one or more S-NSSAIs are determined by the network based on local policies or based on information received from the user equipment's subscription information. In some embodiments, the registration accept or reject message or downlink non-access stratum transport or UE configuration update message includes instructions for the user equipment to request only S-NSSAIs with active applications. In some embodiments, the registration accept or reject message or downlink non-access stratum transport or UE configuration update message includes instructions for the user equipment to release network slices no longer used by any application, thereby excluding released network slices from the next requested NSSAI.

[0009] According to another embodiment, an apparatus may be provided, the apparatus including at least one processor and at least one memory, the at least one memory including computer program code for one or more programs, the at least one memory and the computer program code being configured together with the at least one processor to cause the apparatus to at least: receive a registration acceptance or rejection message from a network entity in response to a registration request message previously transmitted from the apparatus to a network entity of a communication system, the registration request message including information indicating that the apparatus supports or requires network control slice selection behavior, the registration acceptance or rejection message including instructions for the apparatus to request all single network slice selection assistance information (S-NSSAI) configured with network slice selection assistance information (NSSAI) or instructions for the apparatus to request all S-NSSAIs configured by default with NSSAI; receive a downlink non-access stratum transmission message or a UE configuration update message including configuration information, the configuration information including instructions for the apparatus to request all S-NSSAIs configured with NSSAI or instructions for the apparatus to request all S-NSSAIs configured by default with NSSAI; and configure the apparatus to request all S-NSSAIs configured with NSSAI or configured by default with NSSAI when the apparatus is in a communication system. In some embodiments, the registration accept message includes instructions for the device to always request a subset of S-NSSAIs in the configured NSSAIs, and wherein at least one memory and computer program code are configured, together with at least one processor, to further configure the device to always request a subset of S-NSSAIs in the configured NSSAIs. In some embodiments, the S-NSSAI subset is identified by one or more flags associated with each S-NSSAI provided to the device in the configured NSSAIs or default configured NSSAIs. In some embodiments, the registration accept or reject message or downlink non-access stratum transport message or UE configuration update message includes instructions for the device to request only S-NSSAIs with active applications, and wherein at least one memory and computer program code are configured, together with at least one processor, to further configure the device to request only S-NSSAIs with active applications. In some embodiments, the registration accept or reject message downlink non-access stratum transmission message or UE configuration update message includes a timer configured to cause the device to release a network slice that is no longer used by any application, thereby excluding the released network slice from the next requested NSSAI, and wherein at least one memory and computer program code are configured, together with at least one processor, to further: configure the device to release a network slice that is no longer used by any application based on the value of the timer, and exclude the released network slice from the next requested NSSAI.

[0010] According to another embodiment, an apparatus may be provided, comprising: components for receiving a registration request message from a user equipment at a network entity of a communication system; components for transmitting a registration acceptance or rejection message from the network entity to the user equipment in response to receiving the registration request message, wherein the registration request message includes information indicating that the user equipment supports or requires network control slice selection behavior, the configuration information including instructions for the user equipment to request all single network slice selection assistance information (S-NSSAI) configured with network slice selection assistance information (NSSAI) or instructions for the user equipment to request all S-NSSAIs configured by default with NSSAI; and components for providing the configuration information from the network entity to the user equipment via a downlink non-access stratum transmission message or a UE configuration update message, the configuration information including instructions for the user equipment to request all S-NSSAIs configured with NSSAI or instructions for the user equipment to request all S-NSSAIs configured by default with NSSAI. In some embodiments, the registration acceptance or rejection message or the downlink non-access stratum transmission or UE configuration update message includes instructions for the user equipment to always request a subset of S-NSSAIs from the configured NSSAIs. In some embodiments, a subset of S-NSSAIs is identified by one or more flags associated with each S-NSSAI provided to the user equipment in the configured NSSAIs or default configured NSSAIs, wherein the one or more S-NSSAIs are determined by the network based on local policies or based on information received from the user equipment's subscription information. In some embodiments, the registration accept or reject message or downlink non-access stratum transport or UE configuration update message includes instructions for the user equipment to request only S-NSSAIs with active applications. In some embodiments, the registration accept or reject message or downlink non-access stratum transport or UE configuration update message includes instructions for the user equipment to release network slices that are no longer used by any application, thereby excluding released network slices from the next requested NSSAI.

[0011] According to another embodiment, an apparatus may be provided, comprising: means for receiving a registration acceptance or rejection message from a network entity at a user equipment in response to a registration request message previously transmitted from the user equipment to a network entity of a communication system, the registration request message including information indicating that the user equipment supports or requires network control slice selection behavior, the registration acceptance or rejection message including instructions for the user equipment to request all single network slice selection assistance information (S-NSSAI) configured with network slice selection assistance information (NSSAI) or instructions for the user equipment to request all S-NSSAIs that are configured by default with NSSAI; means for receiving a downlink non-access stratum transmission message or a UE configuration update message including configuration information, the configuration information including instructions for the user equipment to request all S-NSSAIs configured with NSSAI or instructions for the user equipment to request all S-NSSAIs that are configured by default with NSSAI; and means for configuring the user equipment to request all S-NSSAIs configured with NSSAI or configured by default with NSSAI when the user equipment is in the communication system. In some embodiments, the registration accept or reject message or downlink non-access stratum transmission message or UE configuration update message includes instructions for the user equipment to always request a subset of S-NSSAIs in the configured NSSAIs, and the means further includes: a component for configuring the user equipment to always request a subset of S-NSSAIs in the configured NSSAIs. In some embodiments, the S-NSSAI subset is identified by one or more flags associated with each S-NSSAI provided to the user equipment in the configured NSSAIs or default configured NSSAIs. In some embodiments, the registration accept or reject message or downlink non-access stratum transmission message or UE configuration update message includes instructions for the user equipment to request only S-NSSAIs with active applications, and the means further includes: a component for configuring the user equipment to request only S-NSSAIs with active applications. In some embodiments, the registration accept or reject message downlink non-access stratum transmission message or UE configuration update message includes a timer configured to cause the user equipment to release a network slice that is no longer used by any application, thereby excluding the released network slice from the next requested NSSAI. The apparatus further includes components for configuring the user equipment to release a network slice that is no longer used by any application based on the value of the timer and for excluding the released network slice from the next requested NSSAI.

[0012] According to another embodiment, a computer program product may be provided, comprising at least one non-transitory computer-readable storage medium storing computer-executable program code instructions therein, the computer-executable program code instructions including program code instructions configured, when executed, to: receive a registration request message from a user equipment at a network entity of a communication system; if the registration request message includes information indicating that the user equipment supports or requires network control slice selection behavior, in response to receiving the registration request message, transmit a registration acceptance or rejection message from the network entity to the user equipment including configuration information, the configuration information including instructions for the user equipment to request all single network slice selection assistance information (S-NSSAI) configured with network slice selection assistance information (NSSAI) or instructions for the user equipment to request all S-NSSAIs configured by default with NSSAI; and provide configuration information from the network entity to the user equipment via a downlink non-access stratum transmission message or a UE configuration update message, the configuration information including instructions for the user equipment to request all S-NSSAIs configured with NSSAI or instructions for the user equipment to request all S-NSSAIs configured by default with NSSAI. In some embodiments, the registration accept or reject message or downlink non-access stratum transport or UE configuration update message includes 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 is identified by one or more flags associated with each S-NSSAI provided to the user equipment in the configured NSSAIs or default configured NSSAIs, wherein the one or more S-NSSAIs are determined by the network based on local policies or based on information received from the user equipment's subscription information. In some embodiments, the registration accept or reject message or downlink non-access stratum transport or UE configuration update message includes instructions for the user equipment to request only S-NSSAIs with active applications. In some embodiments, the registration accept or reject message or downlink non-access stratum transport or UE configuration update message includes instructions for the user equipment to release network slices no longer used by any application, thereby excluding released network slices from the next requested NSSAI.

[0013] According to another embodiment, a computer program product includes at least one non-transitory computer-readable storage medium storing computer-executable program code instructions therein, the computer-executable program code instructions including program code instructions configured, when executed, to: receive a registration acceptance or rejection message from a network entity at a user equipment in response to a registration request message previously transmitted from the user equipment to a network entity of a communication system, the registration request message including information indicating that the user equipment supports or requires network control slice selection behavior, the registration acceptance or rejection message including information for the user equipment to request configured network slice selection assistance information (NS). The system receives instructions for all Single Network Slice Selection Auxiliary Information (S-NSSAI) of the SAI or instructions for the user equipment to request all S-NSSAIs of the default configured NSSAI; receives downlink non-access stratum transport messages or UE configuration update messages including configuration information, such configuration information including instructions for the user equipment to request all S-NSSAIs of the configured NSSAI or instructions for the user equipment to request all S-NSSAIs of the default configured NSSAI; and configures the user equipment to request all S-NSSAIs of the configured NSSAI or the default configured NSSAI when the user equipment is in a communication system. In some embodiments, the registration accept or reject message or downlink non-access stratum transport message or UE configuration update message includes instructions for the user equipment to always request a subset of S-NSSAIs in the configured NSSAI, and wherein the computer-executable program code instructions include program code instructions that, when executed, are configured to: configure the user equipment to always request a subset of S-NSSAIs in the configured NSSAI. In some embodiments, a subset of S-NSSAIs is identified by one or more flags associated with each S-NSSAI provided to the user equipment in the configured NSSAIs or default configured NSSAIs. In some embodiments, the registration accept or reject message or downlink non-access stratum transport message or UE configuration update message includes instructions for the user equipment to request only S-NSSAIs with active applications, and wherein the computer-executable program code instructions include program code instructions configured, upon execution, to: configure the user equipment to request only S-NSSAIs with active applications. In some embodiments, the registration accept or reject message downlink non-access stratum transport message or UE configuration update message includes a timer configured to cause the user equipment to release network slices no longer used by any application, thereby excluding released network slices from the next requested NSSAI, and wherein the computer-executable program code instructions include program code instructions configured, upon execution, to: configure the user equipment to release network slices no longer used by any application based on the value of the aforementioned timer, and exclude released network slices from the next requested NSSAI.

[0014] According to another embodiment, a method can be performed, comprising: receiving configuration information from a network entity in a communication system in a downlink non-access stratum transmission message or a UE configuration update message at a user equipment (UE), the configuration information including an instruction that the UE always establishes all Protocol Data Unit (PDU) sessions for all data network names associated with a Single Network Slice Selection Auxiliary Information (S-NSSAI); and configuring the UE to always establish all PDU sessions for all data network names associated with the S-NSSAI. In some embodiments, the configuration information includes a request that the UE by default establish a specific PDU session or subset of PDU sessions associated with the S-NSSAI when the S-NSSAI is identified by a data network name associated with a flag, the method further comprising: configuring the UE by default to establish a specific PDU session or subset of PDU sessions associated with the S-NSSAI when the S-NSSAI is identified by a data network name associated with a flag, the method further comprising: configuring the UE by default to establish a specific PDU session or subset of PDU sessions associated with the S-NSSAI when the S-NSSAI is identified by a data network name associated with a flag. In some embodiments, the configuration information includes a request from a user equipment (UE) to establish a PDU session in a network slice identified by S-NSSAI at least when no DNN is configured for S-NSSAI, and the method further includes configuring the UE to establish a PDU session in a network slice identified by S-NSSAI at least when no DNN is configured for S-NSSAI. In some embodiments, the configuration information includes a request from a UE to establish a PDU session in a network slice identified by S-NSSAI only when at least one application needs to use the PDU session, and the method further includes configuring the UE to establish a PDU session in a network slice identified by S-NSSAI only when at least one application needs to use the PDU session. In some embodiments, the configuration information includes a request from a UE to provide an explicit timer that causes the UE to release a PDU session no longer associated with any application, and the method further includes configuring the UE to provide an explicit timer that causes the UE to release a PDU session no longer associated with any application.

[0015] According to another embodiment, an apparatus may be provided, comprising at least one processor and at least one memory, the at least one memory including computer program code for one or more programs, the at least one memory and the computer program code being configured, together with the at least one processor, to cause the apparatus to at least: receive configuration information from a network entity in a communication system in a downlink non-access stratum transmission message or a UE configuration update message, the configuration information including instructions that the apparatus always establish all Protocol Data Unit (PDU) sessions for all data network names associated with Single Network Slice Selection Auxiliary Information (S-NSSAI); and configure the apparatus to always establish all PDU sessions for all data network names associated with S-NSSAI. In some embodiments, the configuration information includes a request that the apparatus by default establish a specific PDU session or subset of PDU sessions associated with S-NSSAI when S-NSSAI is identified by a data network name associated with a flag, wherein the at least one memory and the computer program code are further configured, together with the at least one processor, to cause the apparatus to at least: configure the apparatus to by default establish a specific PDU session or subset of PDU sessions associated with S-NSSAI when S-NSSAI is identified by a data network name associated with a flag. In some embodiments, the configuration information includes a request for the device to establish a PDU session in a network slice identified by S-NSSAI at least when no DNN is configured for S-NSSAI, wherein at least one memory and computer program code are further configured, together with at least one processor, to cause the device to at least: configure the device to establish a PDU session in a network slice identified by S-NSSAI at least when no DNN is configured for S-NSSAI. In some embodiments, the configuration information includes a request for the device to establish a PDU session in a network slice identified by S-NSSAI only when at least one application needs to use the PDU session, wherein at least one memory and computer program code are further configured, together with at least one processor, to cause the device to at least: configure the device to establish a PDU session in a network slice identified by S-NSSAI only when at least one application needs to use the PDU session. In some embodiments, the configuration information includes a request for the device to provide an explicit timer that causes the device to release a PDU session no longer associated with any application, wherein at least one memory and computer program code are further configured, together with at least one processor, to cause the device to at least: configure the device to provide an explicit timer that causes the device to release a PDU session no longer associated with any application.

[0016] According to another embodiment, an apparatus is provided that may include: a component for receiving configuration information from a network entity in a communication system during a downlink non-access stratum transmission message or a UE configuration update message, the configuration information including instructions that the apparatus always establishes all Protocol Data Unit (PDU) sessions for all data network names associated with a Single Network Slice Selection Auxiliary Information (S-NSSAI); and a component for configuring the apparatus to always establish all PDU sessions for all data network names associated with the S-NSSAI. In some embodiments, the configuration information includes a request that the apparatus by default establish a specific PDU session or subset of PDU sessions associated with the S-NSSAI when the S-NSSAI is identified by a data network name associated with a flag, the apparatus further including: a component for configuring the apparatus to by default establish a specific PDU session or subset of PDU sessions associated with the S-NSSAI when the S-NSSAI is identified by a data network name associated with a flag. In some embodiments, the configuration information includes a request for the device to establish a PDU session in a network slice identified by S-NSSAI at least when no DNN is configured for S-NSSAI, and the device further includes a component for configuring the device to establish a PDU session in a network slice identified by S-NSSAI at least when no DNN is configured for S-NSSAI. In some embodiments, the configuration information includes a request for the device to establish a PDU session in a network slice identified by S-NSSAI only when at least one application needs to use the PDU session, and the device further includes a component for configuring the device to establish a PDU session in a network slice identified by S-NSSAI only when at least one application needs to use the PDU session. In some embodiments, the configuration information includes a request for the device to provide an explicit timer that causes the device to release PDU sessions no longer associated with any application, and the device further includes a component for configuring the device to provide an explicit timer that causes the device to release PDU sessions no longer associated with any application.

[0017] According to another embodiment, a computer program product may be provided, comprising at least one non-transitory computer-readable storage medium storing computer-executable program code instructions therein, the computer-executable program code instructions including program code instructions configured, when executed, to: receive configuration information from a network entity in a communication system in a downlink non-access stratum transmission message or a UE configuration update message at a user equipment, the configuration information including instructions for the user equipment to always establish all Protocol Data Unit (PDU) sessions for all data network names associated with Single Network Slice Selection Auxiliary Information (S-NSSAI); and to configure the user equipment to always establish all PDU sessions for all data network names associated with S-NSSAI. In some embodiments, the configuration information includes a request from a user equipment to establish, by default, a specific PDU session or subset of PDU sessions associated with the S-NSSAI when the S-NSSAI is identified by a data network name associated with the flag. The computer-executable program code instructions further include program code instructions configured, when executed, to configure the user equipment to establish, by default, a specific PDU session or subset of PDU sessions associated with the S-NSSAI when the S-NSSAI is identified by a data network name associated with the flag. In some embodiments, the configuration information includes a request from a user equipment to establish a PDU session in a network slice identified by the S-NSSAI when at least no DNN is configured for the S-NSSAI. The computer-executable program code instructions further include program code instructions configured, when executed, to configure the user equipment to establish a PDU session in a network slice identified by the S-NSSAI when at least no DNN is configured for the S-NSSAI. In some embodiments, the configuration information includes a request from the user equipment to establish a PDU session in a network slice identified by S-NSSAI only when at least one application needs to use the PDU session, wherein the computer-executable program code instructions further include program code instructions configured, when executed, to configure the user equipment to establish a PDU session in a network slice identified by S-NSSAI only when at least one application needs to use the PDU session. In some embodiments, the configuration information includes a request from the user equipment to provide an explicit timer that causes the user equipment to release a PDU session no longer associated with any application, wherein the computer-executable program code instructions further include program code instructions configured, when executed, to configure the user equipment to provide an explicit timer that causes the user equipment to release a PDU session no longer associated with any application.

[0018] According to another embodiment, a method can be performed comprising: providing configuration information from a network entity in a communication system to a user equipment (UE) in a downlink non-access stratum transport message or a UE configuration update message, the configuration information including an instruction from the UE to always establish all Protocol Data Unit (PDU) sessions for all data network names associated with a Single Network Slice Selection Auxiliary Information (S-NSSAI). In some embodiments, the configuration information includes a request from the UE to by default establish a specific PDU session or subset of PDU sessions associated with the S-NSSAI when the S-NSSAI is identified by a data network name associated with a flag. In some embodiments, the configuration information includes a request from the UE to establish PDU sessions in a network slice identified by the S-NSSAI at least when no DNN is configured for the S-NSSAI. In some embodiments, the configuration information includes a request from the UE to establish PDU sessions in a network slice identified by the S-NSSAI only when at least one application requires the use of the PDU session. In some embodiments, the configuration information includes a request from the UE to provide an explicit timer that causes the UE to release PDU sessions no longer associated with any application.

[0019] According to another embodiment, an apparatus may be provided, comprising at least one processor and at least one memory, the at least one memory including computer program code for one or more programs, the at least one memory and the computer program code being configured, together with the at least one processor, to cause the apparatus to at least: provide configuration information from the apparatus to a user equipment in a downlink non-access stratum transport or UE configuration update message, the configuration information including instructions for the user equipment to always establish all Protocol Data Unit (PDU) sessions for all data network names associated with Single Network Slice Selection Auxiliary Information (S-NSSAI). In some embodiments, the configuration information includes a request from the apparatus to by default establish a specific PDU session or subset of PDU sessions associated with the S-NSSAI when the S-NSSAI is identified by a data network name associated with a flag. In some embodiments, the configuration information includes a request from the apparatus to establish a PDU session in a network slice identified by the S-NSSAI at least when no DNN is configured for the S-NSSAI. In some embodiments, the configuration information includes a request from the apparatus to establish a PDU session in a network slice identified by the S-NSSAI only when at least one application requires the use of the PDU session. In some embodiments, the configuration information includes a request from the device to provide an explicit timer that causes the device to release a PDU session that is no longer associated with any application.

[0020] According to another embodiment, an apparatus may be provided, comprising: a component for providing configuration information from a network entity in a communication system to a user equipment (UE) in a downlink non-access stratum transmission message or a UE configuration update message, the configuration information including instructions for the UE to always establish all Protocol Data Unit (PDU) sessions for all data network names associated with a Single Network Slice Selection Auxiliary Information (S-NSSAI). In some embodiments, the configuration information includes a request for the apparatus to by default establish a specific PDU session or subset of PDU sessions associated with the S-NSSAI when the S-NSSAI is identified by a data network name associated with a flag. In some embodiments, the configuration information includes a request for the apparatus to establish PDU sessions in a network slice identified by the S-NSSAI at least when no DNN is configured for the S-NSSAI. In some embodiments, the configuration information includes a request for the apparatus to establish PDU sessions in a network slice identified by the S-NSSAI only when at least one application requires the use of the PDU session. In some embodiments, the configuration information includes a request for the apparatus to provide an explicit timer that causes the apparatus to release PDU sessions no longer associated with any application.

[0021] According to another embodiment, a computer program product may be provided, comprising at least one non-transitory computer-readable storage medium storing computer-executable program code instructions, the computer-executable program code instructions being configured, when executed, to: provide configuration information from a network entity in a communication system to a user equipment in a downlink non-access stratum transmission message or a UE configuration update message, the configuration information including instructions for the user equipment to always establish all Protocol Data Unit (PDU) sessions for all data network names associated with Single Network Slice Selection Auxiliary Information (S-NSSAI). In some embodiments, the configuration information includes a request for the user equipment to by default establish a specific PDU session or subset of PDU sessions associated with the S-NSSAI when the S-NSSAI is identified by a data network name associated with a flag. In some embodiments, the configuration information includes a request for the user equipment to establish a PDU session in a network slice identified by the S-NSSAI at least when no DNN is configured for the S-NSSAI. In some embodiments, the configuration information includes a request for the user equipment to establish a PDU session in a network slice identified by the S-NSSAI only when at least one application requires the use of the PDU session. In some embodiments, the configuration information includes a request from the user equipment to provide an explicit timer that causes the user equipment to release a PDU session that is no longer associated with any application. Attached Figure Description

[0022] After a general description of certain exemplary embodiments of the invention, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale. In the drawings:

[0023] Figure 1 An example system environment is described in which an implementation according to an example embodiment of the invention may be executed;

[0024] Figure 2 This is a block diagram of a core network device configured according to an exemplary embodiment of the present disclosure;

[0025] Figure 3 An example transmission for registering to a network slice between a user equipment and a communication system according to an example embodiment of the present disclosure is shown;

[0026] Figure 4 An example transmission between a network entity and a user equipment in a communication system according to an example embodiment of the present disclosure is shown for updating the user equipment configuration for a network slice.

[0027] Figure 5 An example transmission between a user equipment and a communication system for configuring user equipment behavior for network slicing is illustrated according to an example embodiment of the present disclosure;

[0028] Figure 6 An example workflow of various components of a communication system according to an example embodiment is shown;

[0029] Figure 7 An example workflow of various components of a communication system according to an example embodiment is shown;

[0030] Figure 8 An example workflow of various components of a communication system according to an example embodiment is shown;

[0031] Figure 9 An example workflow of various components of a communication system according to an example embodiment is shown;

[0032] Figure 10 An example workflow of various components of a communication system according to an example embodiment is shown;

[0033] Figure 11 An example workflow of various components of a communication system according to an example embodiment is shown;

[0034] Figure 12 An example workflow for the various components of a communication system according to an example embodiment is shown; and

[0035] Figure 13 An example workflow for the various components of a communication system according to an example embodiment is shown. Detailed Implementation

[0036] Some embodiments of the invention will now be described more fully below with reference to the accompanying drawings, which illustrate some, but not all, embodiments of the invention. In fact, various embodiments of the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. The same reference numerals refer to the same elements throughout. As used herein, the terms “data,” “content,” “information,” and similar terms are used interchangeably to refer to data capable of being transmitted, received, and / or stored according to embodiments of the invention. Therefore, the use of any such terms should not be construed as limiting the spirit and scope of the embodiments of the invention.

[0037] Furthermore, as used herein, the term "circuit system" means (a) a hardware circuit implementation (e.g., an implementation in an analog circuit system and / or a digital circuit system); (b) a combination of circuitry and (multiple) computer program products comprising software and / or firmware instructions stored on one or more computer-readable storage media, which work together to cause a device to perform one or more functions described herein; and (c) circuitry requiring software or firmware to operate even if the software or firmware is not physically present, such as, for example, (multiple) microprocessors or portions thereof. This definition of "circuit system" applies to all uses of the term herein, including in any claim. As another example, as used herein, the term "circuit system" also includes an implementation comprising one or more processors and / or portions thereof, along with accompanying software and / or firmware. As defined herein, "computer-readable storage medium" referring to a physical storage medium (e.g., a volatile or non-volatile memory device) can be distinguished from "computer-readable transmission medium" referring to an electromagnetic signal.

[0038] The 3rd Generation Partnership Project (3GPP) fifth-generation (5G) technology is a next-generation radio system and network architecture that can provide extreme broadband and ultra-robust low-latency connectivity. 5G technology improves the various telecommunications services offered to end users and helps support massive broadband, i.e., providing gigabytes per second of bandwidth for both uplink and downlink transmissions on demand. Next-generation systems utilizing the 5G architecture leverage virtual radio access network (RAN) and core network functions.

[0039] This document will illustrate embodiments in conjunction with example communication systems and related techniques for providing data transmission within those systems. However, it should be understood that the scope of the claims is not limited to the specific types of communication systems and / or processes disclosed. Embodiments can be implemented in a variety of other types of communication systems using alternative processes and operations. For example, although illustrated in the context of wireless cellular systems utilizing 3GPP system elements such as 3GPP Next Generation Systems (5G), the disclosed embodiments are directly applicable to a variety of other types of communication systems.

[0040] According to illustrative embodiments implemented in a 5G communication system environment, one or more 3GPP Technical Specifications (TS) and Technical Reports (TRs) provide further explanations of user equipment and network elements / functions and / or operations that interact with one or more illustrative 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 additional general details that will be recognized by those skilled in the art. However, while the illustrative embodiments are well-suited for implementations associated with the aforementioned 5G-related 3GPP standards, alternative embodiments are not necessarily intended to be limited to any particular standard.

[0041] In 5G networks, network slicing is a concept for running multiple logical networks as virtually independent service operations on a shared physical infrastructure. A network slice is viewed as an independent, virtualized end-to-end network. Currently, standardization work is underway to simplify the definition of network slices, the registration and deregistration of user equipment (UEs) with network slices, and the admission of Protocol Data Unit (PDU) sessions to network slices. However, under current 3GPP specifications, implementing such activities is complex and typically the responsibility of the UEs, meaning network operators have little control over UE behavior during such activities. While this disclosure may describe the invention in conjunction with 5G communication systems, the invention is also applicable to and includes other networks and network technologies, such as 4G, LTE, 3G, etc., without limitation.

[0042] Methods, apparatus, and computer program products are provided according to example embodiments to provide operator control over user equipment behavior in a communication system when registering and deregistering with network slices and establishing and releasing PDU sessions.

[0043] In communication systems such as 5G systems, a User Equipment (UE) can subscribe to one or more network slices. A UE subscription may include several network slices, each identified by Network Slice Selection Assistance Information (NSSAI). Therefore, a network slice can be identified by a single Network Slice Selection Assistance Information (S-NSSAI). One or more of these S-NSSAIs can be designated as the default S-NSSAI. The default S-NSSAI can identify network slices that the UE can or should use if it has not requested any network slices, particularly in the requested NSSA, for example, before it has been configured with a configured NSSAI. Under current standards such as those mentioned herein, and where the UE has already been configured with a configured NSSAI, these current standards allow the UE complete freedom to request any of these based on local logic. Thus, there are no constraints on the behavior upon which the UE bases its request for one or more configured NSSAIs. Under the current standard, the only available mechanism is for the UE's Home Public Land Mobile Network (HPLMN) to configure a default configured NSSAI for the UE. When the UE has not yet received a configured NSSAI in the serving PLMN, the UE will use the default configured NSSAI.

[0044] However, this approach has several problems, including the possibility that the UE might ignore requests for S-NSSAIs that the operator intends for the UE to use, for example, to provide basic services or updates. Furthermore, many UEs on the market today are configured to continue requesting all S-NSSAIs in the configured NSSAIs in this situation, regardless of actual needs. This could mean, for example, that operators will find deploying network slice-specific access and mobility management functions (AMFs) pointless, as all UEs operating in this way will typically end up with an AMF that supports all S-NSSAIs simultaneously. This situation in the network could mean using only a generic AMF and having to switch between network slices, or being configured to operate within or between multiple network slices, potentially leading to inefficient network messaging, a lack of dedicated network slices, inefficient NSSAI signaling, etc. For example, under current standards and associated network / UE configurations, UEs configured for Massive Internet of Things (MIoT) slices and enhanced mobile broadband (eMBB) slices typically or always end up with 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). AMF dedicated to MIoT has been one of the main drivers of network slicing, and is defined, for example, in the Evolved Packet System (EPS) of a dedicated core network, as a Mobility Management Entity (MME) that supports primarily or exclusively Internet of Things (IoT) technologies and connections (e.g., an MME that manages small amounts of data and / or a small number of connected devices, or an MME that supports small data transmissions on the control plane).

[0045] According to current standards, if a UE can access or is configured to access a certain number of network slices, such as more than eight network slices, then the UE can or will apply logic outside the network operator's control to determine which of the eight or more network slices it does not need to request.

[0046] Conversely, some UEs may decide to request only one network slice associated with an application, and then abandon that network slice after the application that required it stops using it. If applications are launched and deployed very frequently, some operators may want to minimize this type of behavior. Therefore, operators have no way to enforce network slice registration / deregistration behavior on UEs, or UE behavior regarding the association of PDU sessions with network slices. According to current relevant standards, for example, operators deploying only AMFs that simultaneously serve all network slices might indeed want to enforce all UEs through the registration process to minimize UE joining and leaving network slices, since they are practically meaningless in their network—unless, for example, some network slices have limitations on the number of connected UEs, require additional authentication and authorization for UEs to connect, or have a default access point name (APN).

[0047] Thus, according to current relevant standards, operators typically cannot configure UEs with, for example, hysteresis timers to allow the UE to determine when to relinquish a network slice after the last application using that network slice stops using it. If, for example, applications operated by the UE frequently join and leave network slices (e.g., joining and leaving network slices more than a certain number of times per unit time), this can lead to undesirable signaling load.

[0048] Thus, this document describes methods, apparatuses, and computer program products for addressing some or all of the aforementioned limitations and / or other limitations of current relevant standards. Therefore, such methods, apparatuses, and computer program products that allow operators to control UE behavior are described. By allowing network operators, network slice operators, APN operators, AMF operators, or another network entity to control UE behavior, operators can tune UE behavior within their networks, network slices, or network entities in a manner suitable for their deployment and in a way that minimizes signaling load and reduces unnecessary bandwidth dedicated to such signaling and registration / deregistration, as well as other such activities. A similar approach can also be used within a network slice to control which PDU sessions will be established and which PDU sessions can or should be established, for example, only when applications request them. According to current relevant standards, UEs are not currently required to establish PDU sessions with a Data Network Name (DNN), for example, only when applications require them, provided these sessions are configured in the UE Routing Policy (URSP). In other words, the method allows operators to control UE behavior when NSSAI is requested and when PDU sessions are requested within a network slice.

[0049] In some embodiments, network entities and / or UEs can be configured to enable network operators to control UE behavior. In some embodiments, in addition to providing the UE with configured NSSAI and URSP, network entities can also provide the UE with configuration information instructing the UE to reconfigure itself to control UE behavior when a requested NSSAI is formed and when a PDU session is established. This information can be per-S-NSSAI based, per-DNN based, and / or globally based.

[0050] In some embodiments, to control which S-NSSAIs the UE includes in the requested NSSAI message, the PLMN may instruct the UE to request all S-NSSAIs in the configured NSSAIs in the registration acceptance message or in the UE configuration update, or configure the UE to request all S-NSSAIs in the configured NSSAIs by any other means. In some embodiments, by default, the UE may be configured to request any S-NSSAI of the serving PLMN that maps to S-NSSAIs in the default configured NSSAIs.

[0051] In some embodiments, the operator may, for example, in a registration acceptance message, in a UE configuration update, or by any other suitable means, instruct the UE to always request at least an explicitly specified subset of the S-NSSAIs in the configured NSSAIs. In some embodiments, these may be at least the default S-NSSAIs provided by the HPLMN. In some embodiments, this subset may be identified by a flag associated with each S-NSSAI provided to the UE in the configured NSSAIs or in the default configured NSSAIs.

[0052] In some embodiments, the operator may, for example, in a registration acceptance message, in a UE configuration update, or by any other suitable means, instruct the UE to request only S-NSSAI with active applications.

[0053] In some embodiments, the operator may instruct the UE to request S-NSSA only if an active application is using S-NSSA, for example, in a registration acceptance message, in a UE configuration update, or by any other suitable means. In some embodiments, if the UE is configured to request S-NSSA only if an active application is using S-NSSA, the UE or a network entity may provide an explicit timer that causes the UE to release a network slice that is no longer used by any application, for example, by excluding the network slice in the next requested NSSSA. Thus, the operator can implement a kind of hysteresis.

[0054] In some embodiments, in order to control the establishment and release of PDU sessions, the network may, for example, configure the UE to always establish all PDU sessions associated with S-NSSAI in a UE configuration update that provides URSP or through any other URSP configuration method.

[0055] In some embodiments, to control the UE in establishing and releasing PDU sessions from network slices, the network may, for example, configure the UE by default to establish a specific PDU session or a subset of PDU sessions. In some embodiments, a network entity may transmit instructions to the UE to establish a specific PDU session or a subset of PDU sessions by default in response to a message from a network entity explicitly identified in the UE configuration information. For example, the UE configuration information may be provided in the URSP by associating a flag with a DNN associated with S-NSSAI. In some embodiments, the serving PLMN may use a local policy or a default DNN for S-NSSAI (if available) provided by the HPLMN.

[0056] In some embodiments, to control the UE in establishing and releasing PDU sessions from network slices, the network can configure the UE to establish a PDU session only when at least one application needs to use the PDU session. For example, no PDU session may be established unless an application needs to use the PDU session, is launched on the UE, and has requested data transfer capabilities for the PDU session DNN. In some embodiments, to control the UE in establishing and releasing PDU sessions from network slices, when the UE is configured to establish a PDU session only when an active application is using the PDU session, the network can configure the UE to provide an explicit timer that causes the UE to release PDU sessions no longer associated with any application, thus allowing the operator to implement a certain hysteresis. In some embodiments, the network can be configured to cause the UE to have the appropriate necessary connections so that the UE is provided with optimal service according to network policies and the correct signaling load can be controlled by the network.

[0057] Figure 1 An example communication system environment is described in which an implementation according to an example embodiment of the invention can be executed. Figure 1 The description of system environment 100 herein is not intended to limit or otherwise restrict the embodiments described and contemplated herein to any particular configuration of elements or systems, nor is it intended to exclude any alternative configurations or systems that can be used in conjunction with embodiments of the invention. Rather, Figure 1 The system environment 100 disclosed herein is presented merely to provide an example basis and context to facilitate the understanding of some of the features, aspects, and uses of the methods, apparatus, and computer program products disclosed and contemplated herein. It should be understood that, although... Figure 1Many of the aspects and components shown are illustrated as separate, individual elements, but other configurations can be used in conjunction with the methods, apparatus, and computer programs described herein, including configurations that combine, omit, and / or add aspects and / or components.

[0058] like Figure 1 As shown, the system environment includes one or more user equipment (UE) 102, which is configured to wirelessly communicate with network 106, such as via an access network. Although user equipment can be configured in various ways, it can be embodied as a mobile terminal, such as a portable digital assistant (PDA), mobile phone, smartphone, pager, mobile TV, gaming device, laptop computer, camera, tablet computer, communicator, tablet, headset, touchscreen, video recorder, audio / video player, radio, e-book reader, positioning device (e.g., Global Positioning System (GPS) device), or any combination of the above, as well as other types of voice and text and multi-mode communication systems. Figure 1 The system environment 100 shown also includes one or more access points 104a and 104b, such as base stations, including but not limited to NodeBs, evolved NodeBs (eNBs), etc. A cellular access point (such as a base station) can define and serve one or more cells. The access point can then communicate with a network 106 (such as a core network) via a gateway, enabling the access point to establish a cellular radio access network through which user equipment 102 can communicate with the network. Figure 1 The system environment 100 may include multiple different cellular radio access cells and / or networks or parts of such networks, including, for example, 5G radio access networks, LTE (Long Term Evolution) radio access networks, and UMTS (Universal Mobile Telecommunications System) radio access networks. In some example implementations, equipment and other infrastructure associated with multiple different cellular radio access networks may be located at or near structures and / or other equipment associated with a specific access point (such as access points 104a and 104b).

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

[0060] In this respect, the implementation and / or allocation of network slices in the network environment can be determined by... Figure 2 The device 200 shown is used to complete this process. This device can be implemented by one or more UEs (such as user equipment 102) or related devices. Figure 1 Any other devices discussed (such as access points 104a and / or 104b, one or more of WLAN access points 108, and / or devices that may be combined with or otherwise associated with system environment 100) may be embodied and / or incorporated therein. Alternatively, device 200 may be embodied by another device external to such a device. For example, the device may be embodied by a computing device such as a personal computer, computer workstation, server, or any of a variety of mobile computing devices such as mobile terminals, including but not limited to smartphones, tablets, etc.

[0061] In some embodiments, 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 service, internet access, or third-party service), 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), Next Generation Radio Access Network (NG-RAN), 5G Equipment Identifier Register (5G-EIR), Network Data Analysis Function (NWDAF), and Charging Function (CHF). The system environment may also include the following network entities: Serving Communication Agent (SCP) and Secure Edge Protection Agent (SEPP).

[0062] Regardless of how device 200 is embodied, the device of the example embodiment is configured to include a processor 202 and a memory device 204, and optionally a user interface 206 and / or a communication interface 208, or is configured to otherwise communicate with them. In some embodiments, the processor (and / or coprocessor or auxiliary processor or any other processing circuitry system otherwise associated with the processor) may communicate with the memory device via a bus to transfer 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) including gates configured to store data (e.g., bits) that can be retrieved by a machine (e.g., a computing device, such as a processor). According to an example embodiment of the invention, the memory device may be configured to store information, data, content, applications, instructions, etc., enabling the device to perform various functions. For example, the memory device may be configured to buffer input data for processor processing. Additionally or alternatively, the memory device may be configured to store instructions for processor execution.

[0063] As described above, device 200 can be embodied by a computing device. However, in some embodiments, the device can be embodied as a chip or chipset. In other words, the device can include one or more physical packages (e.g., chips) that include materials, components, and / or wires on a structural component (e.g., a substrate). The structural component can provide physical strength, dimensional conservation, and / or electrical interaction constraints for the component circuitry systems included thereon. Therefore, in some cases, the device can be configured to implement embodiments of the invention on a single chip or as a single "system-on-a-chip." Thus, in some cases, a chip or chipset can constitute a means for performing one or more operations to provide the functions described herein.

[0064] Processor 202 can be embodied in a variety of different ways. For example, a processor can be embodied as one or more of a variety of hardware processing units including a processing circuitry system, such as a coprocessor, microprocessor, controller, digital signal processor (DSP), processing element with or without an accompanying DSP, or various other processing circuitry systems including an integrated circuit, such as an ASIC (Application-Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), microcontroller unit (MCU), hardware accelerator, application-specific computer chip, etc. Thus, in some embodiments, the processor may include one or more processing cores configured to execute independently. Multi-core processors can enable multiprocessing within a single physical package. Additionally or alternatively, the processor may include one or more processors configured in series via a bus to enable independent execution of instructions, pipelines, and / or multithreading.

[0065] In an example embodiment, processor 202 may be configured to execute instructions stored in memory device 204 or otherwise accessible to the processor. Alternatively or additionally, the processor may be configured to perform hard-coded functions. Thus, whether configured by hardware or software methods, or by a combination thereof, the processor may represent an entity (e.g., physically embodied in a circuit system) capable of performing operations according to embodiments of the invention when appropriately configured. Therefore, for example, when the processor is embodied as an ASIC, FPGA, etc., the processor may be hardware specifically configured to perform the operations described herein. Alternatively, as another example, when the processor is embodied as an executor of software instructions, the instructions may specifically configure the processor to perform the algorithms and / or operations described herein when the instructions are executed. However, in some cases, the processor may be a processor of a particular device (e.g., a pass-through display or a mobile terminal) configured to further configure the processor to employ embodiments of the invention by using instructions for performing the algorithms and / or operations described herein. The processor may include clocks, arithmetic logic units (ALUs), and logic gates, etc., configured to support processor operation.

[0066] Device 200 may optionally include a communication interface 208. The communication interface can be any component, such as a device or circuitry system embodied in hardware or a combination of hardware and software, configured to receive and / or transmit data to and from a network and / or any other device or module communicating with the device. In this regard, the communication interface may include, for example, an antenna (or multiple antennas) and supporting hardware and / or software for enabling communication with a wireless communication network. Additionally or alternatively, the communication interface may include circuitry for interacting with the antenna(s) to induce signal transmission via the antenna(s) or for processing reception of signals received via the antenna(s). In some environments, the communication interface may alternatively or additionally 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.

[0067] The following provides example transmissions between the UE and network entities. The following example transmissions provide the necessary predictive steps or messages. The information between "[]" is optional and may be included if, for example, the UE is provided with configured NSSAI and / or URSP at the same time as the UE behavior is configured.

[0068] Figure 3An example transmission for registering the UE to a network slice is illustrated between the UE and the AMF of the communication system. In some embodiments, at point 1, the UE may send a registration request message to the AMF. The AMF or another suitable network entity of the communication system may determine, for example, the expected UE behavior for requested NSSAI formation and / or for DNN establishment based on local policies or information received from the UDM. Thus, as part of the consideration by the AMF or other network entity regarding whether the UE should register with the communication system (e.g., core network, network slice, requested network slice, AMF, etc.), the AMF or other network entity may determine whether the UE is configured to provide control over certain aspects of registration / deregistration to the network entity (e.g., the AMF). Then, if the UE is configured in this way, at point 2, the network entity (e.g., the AMF) may return a registration acceptance message to the UE. In some embodiments, the network entity (e.g., the AMF) may return a registration acceptance message to the UE even if the UE is not configured in this way.

[0069] In some embodiments, the registration acceptance message may include configured NSSAIs, UE behavior assistance information, etc. In some embodiments, a network entity (e.g., AMF) may transmit such a registration acceptance message (e.g., including UE behavior assistance information) to the UE, such that the UE can be configured to follow network entity instructions for UE behavior control during registration / deregistration and / or PDU session establishment / release. Once the UE receives the registration acceptance message, the UE can, for example, apply new behaviors provided by the network in the UE behavior assistance information, or otherwise. In some embodiments, the UE behavior assistance information may provide instructions for the UE to be configured to request all S-NSSAIs in the configured NSSAIs. In some embodiments, the UE behavior assistance information may provide instructions for the UE to be configured by default to request any S-NSSAIs of the serving PLMN mapped to the S-NSSAIs in the default configured NSSAIs. In some embodiments, the UE behavior assistance information may provide instructions for the UE to be configured to always request at least an explicitly specified subset of the S-NSSAIs in the configured NSSAIs. In some embodiments, the explicitly specified subset of S-NSSAIs in the configured NSSAIs may be or at least include the default S-NSSAIs provided by the HPLMN. In some embodiments, explicitly specifying a subset can be identified by flags associated with some or each S-NSSAI provided to the UE in the configured NSSAI or in the default configured NSSAI. In some embodiments, UE behavior assistance information can provide instructions that the UE is configured to request only S-NSSAIs with an active application (e.g., an application operated by the UE) associated with it. In some embodiments, UE behavior assistance information can provide instructions that if the UE is configured to request S-NSSA only if an active application is using a network slice, the UE can be configured to provide an explicit timer that causes the UE to release a network slice that is no longer used by any application, for example, by excluding the network slice to be released from the next requested NSSAI, thus allowing the operator to implement some kind of hysteresis.

[0070] Figure 4An example transmission for UE configuration updates between a UE and the AMF of a communication system is illustrated. In some embodiments, the UE configuration update may be operable to provide operator control over UE behavior in the communication system when registering and deregistering with and / or establishing and releasing PDU sessions. In some embodiments, the AMF may determine the desired UE behavior for requested NSSAI formation and / or DNN establishment, for example, based on local policies or information received from the UDM, regarding a specific UE, a specific network slice, the network, or the communication system in a global manner. In some embodiments, at point 1, the AMF may then provide a UE configuration update command message to the UE. In some embodiments, the UE configuration update command message may include configured NSSAI, URSP, other identification information about the network, network slice, PDU session, AMF, etc. In some embodiments, the UE configuration update command message may also include UE behavior assistance information, which may be related to the above regarding... Figure 3 The aforementioned UE behavior assistance information is similar or identical.

[0071] For example, a message may be transmitted from a network entity (such as an AMF) that includes UE behavior assistance information. In some embodiments, a network entity (e.g., an AMF) may transmit a message (e.g., including UE behavior assistance information) to the UE such that the UE can be configured to follow network entity instructions for UE behavior control during the establishment and / or release of a PDU session with a network slice. Once the UE receives the message, the UE can, for example, apply a new behavior provided by the network in the UE behavior assistance information, or otherwise. In some embodiments, the UE behavior assistance information may provide instructions for the UE to be configured to request all S-NSSAIs in the configured NSSAI. In some embodiments, the UE behavior assistance information may provide instructions for the UE to be configured by default to request any S-NSSAIs of the serving PLMN mapped to the S-NSSAIs in the default configured NSSAIs. In some embodiments, the UE behavior assistance information may provide instructions for the UE to be configured to always request at least an explicitly specified subset of the S-NSSAIs in the configured NSSAIs. In some embodiments, the explicitly specified subset of S-NSSAIs in the configured NSSAIs may be or at least include the default S-NSSAIs provided by the HPLMN. In some embodiments, explicitly specifying a subset can be identified by flags associated with some or each S-NSSAI provided to the UE in the configured NSSAI or in the default configured NSSAI. In some embodiments, UE behavior assistance information can provide instructions that the UE is configured to request only S-NSSAIs with an active application (e.g., an application operated by the UE) associated with it. In some embodiments, UE behavior assistance information can provide instructions that if the UE is configured to request S-NSSA only if an active application is using a network slice, the UE can be configured to provide an explicit timer that causes the UE to release a network slice that is no longer used by any application, for example, by excluding the network slice to be released from the next requested NSSAI, thus allowing the operator to implement some kind of hysteresis.

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

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

[0074] Figure 5Example transmissions for UE behavior configuration between a UE and a network entity (e.g., an AMF) of a communication system are illustrated. In some embodiments, UE configuration updates may be operable to provide operator control over UE behavior in the communication system during any suitable interaction with the network or network entity (such as the AMF), such as when registering and deregistering with a network slice and / or establishing and releasing a PDU session. In some embodiments, the AMF may provide UE behavior assistance information to the UE according to any suitable means or method. In some embodiments, the UE may request, retrieve, or receive UE behavior assistance information from a network entity such as the AMF according to any suitable means or method. In some embodiments, the AMF or UE may determine the desired UE behavior for requested NSSAI formation and / or DNN establishment, for example, based on local policies or information received from another network entity such as a UDM, regarding a specific UE, a specific network slice, the network or communication system in a global manner, etc. In some embodiments, the UE may retrieve or receive from a network entity and / or the network entity may be configured to send UE behavior assistance information to the UE, along with one or more configured NSSAIs, URSPs, other identification information about the network, network slices, PDU sessions, and the AMF, etc. In some embodiments, the UE configuration update command message may further include UE behavior assistance information, which may be related to the information mentioned above. Figure 3 The aforementioned UE behavior assistance information is similar or identical.

[0075] For example, UE behavior assistance information may be operable to cause the UE to be configured to follow network entity instructions for UE behavior control during the establishment and / or release of PDU sessions with network slices. In some embodiments, the UE may, for example, apply new behaviors provided by the network in the UE behavior assistance information, or otherwise provided. In some embodiments, the UE behavior assistance information may provide instructions for the UE to be configured to request all S-NSSAIs in the configured NSSAI. In some embodiments, the UE behavior assistance information may provide instructions for the UE to be configured by default to request any S-NSSAIs of the serving PLMN mapped to S-NSSAIs in the default configured NSSAI. In some embodiments, the UE behavior assistance information may provide instructions for the UE to be configured to always request at least an explicitly specified subset of S-NSSAIs in the configured NSSAI. In some embodiments, the explicitly specified subset of S-NSSAIs in the configured NSSAI may be or at least include the default S-NSSAIs provided by the HPLMN. In some embodiments, the explicitly specified subset may be identified by flags associated with some or each S-NSSAI provided to the UE in the configured NSSAI or in the default configured NSSAI. In some embodiments, UE behavior assistance information can provide instructions that the UE is configured to request S-NSSAI only for active applications (e.g., applications operated by the UE) associated with it. In some embodiments, UE behavior assistance information can provide instructions such that if the UE is configured to request S-NSSA only if an active application is using a network slice, the UE can be configured to provide an explicit timer that causes the UE to release a network slice that is no longer used by any application, for example, by excluding the network slice to be released from the next requested NSSAI, thus allowing the operator to implement a certain hysteresis.

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

[0077] Now for reference Figure 6According to an example embodiment, example workflows for various components of a communication system are shown, such as the UE, AMF, V-NSSF, SMF, or other components previously described, for example, in conjunction with other diagrams. Reference is now made to... Figure 6 Method 10 is illustrated. Method 10 can be performed by one or more of the entities described above, including components such as processor 202 and communication interface 208 for receiving a registration request message from a user equipment at a network entity in the communication system at point 11. In some embodiments, method 10 may include, at point 12, in response to receiving the registration request message, transmitting a registration acceptance or rejection message from the network entity to the user equipment, in the presence of information indicating that the user equipment supports or requires network control slice selection behavior, if the registration request message includes configuration information, such configuration information includes instructions for the user equipment to request all single network slice selection assistance information (S-NSSAI) configured with network slice selection assistance information (NSSAI) or instructions for the user equipment to request all S-NSSAIs configured by default with NSSAI. In some embodiments, method 10 may optionally include: at 13, providing configuration information from a network entity to a user equipment via a downlink non-access stratum transmission message or a UE configuration update message, the configuration information including instructions for the user equipment to request all S-NSSAIs that have been configured with NSSAI or instructions for the user equipment to request all S-NSSAIs that have been configured with NSSAI by default.

[0078] Now for reference Figure 7 According to an example embodiment, an example workflow of various components of a communication system is shown, such as a UE or other components previously described, for example, in conjunction with other diagrams. Reference is now made to... Figure 7The diagram illustrates a method 20 that can be performed by one or more of the aforementioned entities, including components such as a processor 202 and a communication interface 208, for receiving a registration acceptance or rejection message from a network entity at point 21 at the user equipment in response to a registration request message previously transmitted from the user equipment to the network entity of the communication system. The registration request message includes information indicating that the user equipment supports or requires network control slice selection behavior. The registration acceptance or rejection message includes instructions for the user equipment to request all single network slice selection assistive information (S-NSSAI) configured with network slice selection assistive information (NSSAI) or for the user equipment to request all S-NSSAIs configured by default with NSSAI. In some embodiments, method 20 may further include, at point 22, receiving a downlink non-access stratum transport message or a UE configuration update message including configuration information, such as instructions for the user equipment to request all S-NSSAIs configured with NSSAI or for the user equipment to request all S-NSSAIs configured by default with NSSAI. In some embodiments, optionally, method 20 may further include: at 23, configuring the user equipment to request all S-NSSAIs that are configured NSSAIs or default configured NSSAIs when the user equipment is in a communication system. In some embodiments, optionally, method 20 may further include: at 24, configuring the user equipment to always request a subset of S-NSSAIs from the configured NSSAIs.

[0079] Now for reference Figure 8 According to an example embodiment, an example workflow of various components of a communication system is shown, such as a UE or other components previously described, for example, in conjunction with other diagrams. Reference is now made to... Figure 8The diagram illustrates a method 30 that can be performed by one or more of the aforementioned entities, including components such as processor 202 and communication interface 208 for receiving a registration acceptance or rejection message from a network entity at point 31 at the user equipment in response to a registration request message previously transmitted from the user equipment to the network entity of the communication system. The registration request message includes configuration information indicating that the user equipment supports or requires network control slice selection behavior. The registration acceptance or rejection message includes instructions for the user equipment to request all single network slice selection assistive information (S-NSSAI) configured with network slice selection assistive information (NSSAI) or instructions for the user equipment to request all S-NSSAIs configured by default with NSSAI. In some embodiments, method 30 may further include, at point 32, receiving a downlink non-access stratum transport message or a UE configuration update message including configuration information, such as instructions for the user equipment to request all S-NSSAIs configured with NSSAI or instructions for the user equipment to request all S-NSSAIs configured by default with NSSAI. In some embodiments, optionally, method 30 may further include: at 33, configuring the user equipment to request all S-NSSAIs that are configured with NSSAI or are configured with NSSAI by default when the user equipment is in a communication system. In some embodiments, optionally, method 30 may further include at 34, configuring the user equipment to request only S-NSSAIs with active applications.

[0080] Now for reference Figure 9 According to an example embodiment, an example workflow of various components of a communication system is shown, such as a UE or other components previously described, for example, in conjunction with other diagrams. Reference is now made to... Figure 9The diagram illustrates a method 40 that can be performed by one or more of the aforementioned entities, including components such as processor 202 and communication interface 208 for receiving a registration acceptance or rejection message from a network entity at point 41 at the user equipment in response to a registration request message previously transmitted from the user equipment to the network entity of the communication system. The registration request message includes configuration information indicating that the user equipment supports or requires network control slice selection behavior. The registration acceptance or rejection message includes instructions for the user equipment to request all single network slice selection assistive information (S-NSSAI) configured with network slice selection assistive information (NSSAI) or instructions for the user equipment to request all S-NSSAIs configured by default with NSSAI. In some embodiments, method 40 may further include, at point 42, receiving a downlink non-access stratum transport message or a UE configuration update message including configuration information, such as instructions for the user equipment to request all S-NSSAIs configured with NSSAI or instructions for the user equipment to request all S-NSSAIs configured by default with NSSAI. In some embodiments, optionally, method 40 may further include: at 43, configuring the user equipment to request all S-NSSAIs that are configured with NSSAI or are configured with NSSAI by default when the user equipment is in a communication system. In some embodiments, optionally, method 40 may further include at 44, configuring the user equipment to release network slices that are no longer used by any application based on the value of the timer described above, and excluding released network slices from the next requested NSSAI.

[0081] Now for reference Figure 10 According to an example embodiment, an example workflow of various components of a communication system is shown, such as a UE or other components previously described, for example, in conjunction with other diagrams. Reference is now made to... Figure 10 The diagram illustrates a method 50 that can be performed by one or more of the aforementioned entities, which include components such as processor 202 and communication interface 208 for receiving configuration information from a network entity in the communication system at point 51 in a downlink non-access stratum transmission message or UE configuration update message at the user equipment. This configuration information includes instructions for the user equipment to always establish all Protocol Data Unit (PDU) sessions for all data network names associated with a Single Network Slice Selection Auxiliary Information (S-NSSAI). Optionally, in some embodiments, method 50 may further include: at point 52, configuring the user equipment to always establish all PDU sessions for all data network names associated with the S-NSSAI. Optionally, in some embodiments, method 50 may further include: at point 53, configuring the user equipment to by default establish a specific PDU session or subset of PDU sessions associated with the S-NSSAI if the S-NSSAI is identified by a data network name associated with a flag.

[0082] Now for reference Figure 11 According to an example embodiment, an example workflow of various components of a communication system is shown, such as a UE or other components previously described, for example, in conjunction with other diagrams. Reference is now made to... Figure 11 The diagram illustrates a method 60 that can be performed by one or more of the aforementioned entities, which include components such as processor 202 and communication interface 208 for receiving configuration information from a network entity in the communication system at point 61 in a downlink non-access stratum transmission message or UE configuration update message at the user equipment. This configuration information includes instructions for the user equipment to always establish all Protocol Data Unit (PDU) sessions for all data network names associated with Single Network Slice Selection Assistance Information (S-NSSAI). Optionally, in some embodiments, method 60 may further include, at point 62, configuring the user equipment to always establish all PDU sessions for all data network names associated with S-NSSAI. Optionally, in some embodiments, method 60 may further include, at point 63, configuring the user equipment to establish PDU sessions in the network slice identified by S-NSSAI, at least when no DNN is configured for S-NSSAI.

[0083] Now for reference Figure 12 According to an example embodiment, an example workflow of various components of a communication system is shown, such as a UE or other components previously described, for example, in conjunction with other diagrams. Reference is now made to... Figure 12 The diagram illustrates a method 70 that can be performed by one or more of the aforementioned entities, which include components such as processor 202 and communication interface 208 for receiving configuration information from a network entity in the communication system at point 71 in a downlink non-access stratum transmission message or UE configuration update message at the user equipment. This configuration information includes instructions for the user equipment to always establish all Protocol Data Unit (PDU) sessions for all data network names associated with Single Network Slice Selection Auxiliary Information (S-NSSAI). Optionally, in some embodiments, method 70 may further include: at point 72, configuring the user equipment to always establish all PDU sessions for all data network names associated with S-NSSAI. Optionally, in some embodiments, method 70 may further include: at point 73, configuring the user equipment to establish a PDU session in the network slice identified by S-NSSAI only when at least one application requires the use of the PDU session. Optionally, in some embodiments, method 70 may further include: at point 74, configuring the user equipment to provide an explicit timer that causes the user equipment to release PDU sessions no longer associated with any application.

[0084] Now for reference Figure 13According to an example embodiment, an example workflow of various components of a communication system is shown, such as a UE or other components previously described, for example, in conjunction with other diagrams. Reference is now made to... Figure 13 The diagram illustrates a method 80 that can be performed by one or more of the aforementioned entities, which include components such as processor 202 and communication interface 208 for providing configuration information from a network entity in the communication system to the user equipment in a downlink non-access stratum transmission message or UE configuration update message at 81. The configuration information includes instructions for the user equipment to always establish all protocol data unit (PDU) sessions for all data network names associated with Single Network Slice Selection Auxiliary Information (S-NSSAI).

[0085] As described above, the methods, apparatus, and computer program products of the example embodiments thus provide an enforcement mechanism for the maximum number of PDU sessions per network slice in a communication system. In some embodiments, the methods, apparatus, and computer program products provide the above enforcement mechanism in a manner that emphasizes the presence of PDU sessions among UEs.

[0086] As mentioned above, Figures 6-13 This is a flowchart illustrating various methods that can be executed by, for example, apparatus 200 and / or a computer program product according to exemplary embodiments of the present disclosure. It should be understood that each block of the flowchart, and combinations of blocks in the flowchart, can be implemented by various means, such as hardware, firmware, processors, circuit systems, and / or other devices associated with the execution of software including one or more computer program instructions. For example, one or more of the processes described above can be implemented by computer program instructions. In this regard, the computer program instructions embodying the processes described above can be stored by a memory device 204 of an apparatus employing embodiments of the present disclosure and executed by a processor 202 of that apparatus. As will be appreciated, any such computer program instructions can be loaded onto a computer or other programmable apparatus (e.g., hardware) to produce a machine, such that the resulting computer or other programmable apparatus performs the functions specified in the flowchart blocks. These computer program instructions can also be stored in a computer-readable storage medium that can instruct the computer or other programmable apparatus to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of art, the execution of which performs the functions specified in the flowchart blocks. Computer program instructions may also be loaded onto a computer or other programmable device to cause a series of operations to be performed on the computer or other programmable device to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable device, provide operations for implementing the function specified in the flowchart box.

[0087] Therefore, a computer program product is defined where computer program instructions (such as computer-readable program code portions) are stored by at least one non-transitory computer-readable storage medium, wherein the computer program instructions (such as computer-readable program code portions) are configured to perform the above, for example, in combination, upon execution. Figures 3-5 Communication flowchart or as Figure 1 The functions described are part of the system. In other embodiments, computer program instructions (such as computer-readable program code portions) do not need to be stored or otherwise embodied by a non-transitory computer-readable storage medium, but may be embodied by a transient medium, wherein the computer program instructions (such as computer-readable program code portions) are configured to still perform the functions described above when executed.

[0088] Therefore, the boxes in a flowchart support combinations of components for performing a specified function and combinations of operations for performing that specified function. It will also be understood that one or more boxes in a flowchart, as well as combinations of boxes in a flowchart, can be implemented by a dedicated hardware-based computer system or a combination of dedicated hardware and computer instructions that performs the specified function.

[0089] In some embodiments, certain operations described above may be modified or further amplified. Furthermore, in some embodiments, additional optional operations may be included. Modifications, additions, or amplifications of the above operations may be performed in any order and in any combination.

[0090] Thus, this document describes methods, apparatus, and computer program products provided according to exemplary embodiments to provide operator control over user equipment behavior in a communication system when registering and deregistering with network slices and establishing and releasing PDU sessions.

[0091] In one example embodiment, a method is provided, comprising: receiving a registration request message from a user equipment (UE) at a network entity of a communication system; if the registration request message includes information indicating that the UE supports or requires network control slice selection behavior, in response to receiving the registration request message, transmitting a registration acceptance or rejection message from the network entity to the UE, the configuration information including instructions for the UE to request all single network slice selection assistive information (S-NSSAI) configured with network slice selection assistive information (NSSAI) or instructions for the UE to request all S-NSSAIs configured by default with NSSAI; and providing the configuration information from the network entity to the UE via a downlink non-access stratum transmission message or a UE configuration update message, the configuration information including instructions for the UE to request all S-NSSAIs configured with NSSAI or instructions for the UE to request all S-NSSAIs configured by default with NSSAI. In some embodiments, the registration acceptance or rejection message or the downlink non-access stratum transmission or UE configuration update message includes instructions for the UE to always request a subset of S-NSSAIs from the configured NSSAIs. In some embodiments, a subset of S-NSSAIs is identified by one or more flags associated with each S-NSSAI provided to the user equipment in the configured NSSAIs or default configured NSSAIs, wherein the one or more S-NSSAIs are determined by the network based on local policies or based on information received from the user equipment's subscription information. In some embodiments, the registration accept or reject message or downlink non-access stratum transport or UE configuration update message includes instructions for the user equipment to request only S-NSSAIs with active applications. In some embodiments, the registration accept or reject message or downlink non-access stratum transport or UE configuration update message includes instructions for the user equipment to release network slices that are no longer used by any application, thereby excluding released network slices from the next requested NSSAI.

[0092] According to another embodiment, a method can be performed, the method comprising: at a user equipment, in response to a registration request message previously transmitted from the user equipment to a network entity of a communication system, receiving a registration acceptance or rejection message from the network entity, the registration request message including information indicating that the user equipment supports or requires network control slice selection behavior, the registration acceptance or rejection message including instructions for the user equipment to request all single network slice selection assistance information (S-NSSAI) configured with network slice selection assistance information (NSSAI) or instructions for the user equipment to request all S-NSSAIs configured by default with NSSAI; receiving a downlink non-access stratum transport message or a UE configuration update message including configuration information, the configuration information including instructions for the user equipment to request all S-NSSAIs configured with NSSAI or instructions for the user equipment to request all S-NSSAIs configured by default with NSSAI; and configuring the user equipment to request all S-NSSAIs configured with NSSAI or configured by default with NSSAI when the user equipment is in the communication system. In some embodiments, the registration accept or reject message, downlink non-access stratum transport message, or UE configuration update message includes an instruction for the user equipment to always request a subset of S-NSSAIs in the configured NSSAIs, the method further comprising: configuring the user equipment to always request a subset of S-NSSAIs in the configured NSSAIs. In some embodiments, the S-NSSAI subset is identified by one or more flags associated with each S-NSSAI provided to the user equipment in the configured NSSAIs or default configured NSSAIs. In some embodiments, the registration accept or reject message, downlink non-access stratum transport message, or UE configuration update message includes an instruction for the user equipment to request only S-NSSAIs with active applications, the method further comprising: configuring the user equipment to request only S-NSSAIs with active applications. In some embodiments, the registration accept or reject message downlink non-access stratum transmission message or UE configuration update message includes a timer configured to cause the user equipment to release a network slice that is no longer used by any application, thereby excluding the released network slice from the next requested NSSAI. The method further includes: configuring the user equipment to release a network slice that is no longer used by any application based on the value of the timer, and excluding the released network slice from the next requested NSSAI.

[0093] According to another embodiment, an apparatus may be provided, the apparatus including at least one processor and at least one memory, the at least one memory including computer program code for one or more programs, the at least one memory and the computer program code being configured together with the at least one processor to cause the apparatus to at least: receive a registration request message from a user equipment at the apparatus; in response to receiving the registration request message, if the registration request message includes information indicating that the user equipment supports or requires network control slice selection behavior, transmit a registration acceptance or rejection message from the apparatus to the user equipment including configuration information, the configuration information including instructions for the user equipment to request all single network slice selection assistance information (S-NSSAI) configured with network slice selection assistance information (NSSAI) or instructions for the user equipment to request all S-NSSAIs configured by default with NSSAI; and provide configuration information from the apparatus to the user equipment via a downlink non-access stratum transmission message or a UE configuration update message, the configuration information including instructions for the user equipment to request all S-NSSAIs configured with NSSAI or instructions for the user equipment to request all S-NSSAIs configured by default with NSSAI. In some embodiments, the registration accept or reject message or downlink non-access stratum transport or UE configuration update message includes 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 is identified by one or more flags associated with each S-NSSAI provided to the user equipment in the configured NSSAIs or default configured NSSAIs, wherein the one or more S-NSSAIs are determined by the network based on local policies or based on information received from the user equipment's subscription information. In some embodiments, the registration accept or reject message or downlink non-access stratum transport or UE configuration update message includes instructions for the user equipment to request only S-NSSAIs with active applications. In some embodiments, the registration accept or reject message or downlink non-access stratum transport or UE configuration update message includes instructions for the user equipment to release network slices no longer used by any application, thereby excluding released network slices from the next requested NSSAI.

[0094] According to another embodiment, an apparatus may be provided, comprising at least one processor and at least one memory, the at least one memory including computer program code for one or more programs, the at least one memory and the computer program code being configured, together with the at least one processor, to cause the apparatus to at least: receive a registration acceptance or rejection message from a network entity in response to a registration request message previously transmitted from the apparatus to a network entity of a communication system, the registration request message including information indicating that the apparatus supports or requires network control slice selection behavior, the registration acceptance or rejection message including information for the apparatus to request that network slice selection be configured. The device receives instructions for selecting all single network slice auxiliary information (S-NSSAI) or for requesting all S-NSSAIs of the default configured NSSAI; receives downlink non-access stratum transmission messages or UE configuration update messages including configuration information, such configuration information including instructions for requesting all S-NSSAIs of the configured NSSAI or instructions for requesting all S-NSSAIs of the default configured NSSAI; and configures the device to request all S-NSSAIs of the configured NSSAI or the default configured NSSAI when the device is in a communication system. In some embodiments, the registration acceptance message includes instructions for the device to always request a subset of S-NSSAIs in the configured NSSAIs, and wherein at least one memory and computer program code are configured, together with at least one processor, to further: configure the device to always request a subset of S-NSSAIs in the configured NSSAIs. In some embodiments, the S-NSSAI subset is identified by one or more flags associated with each S-NSSAI provided to the device in the configured NSSAIs or the default configured NSSAIs. In some embodiments, the registration accept or reject message or downlink non-access stratum transmission message or UE configuration update message includes instructions for the device to request only S-NSSAIs with active applications, and wherein at least one memory and computer program code are configured, together with at least one processor, to further: configure the device to request only S-NSSAIs with active applications. In some embodiments, the registration accept or reject message downlink non-access stratum transmission message or UE configuration update message includes a timer configured to cause the device to release network slices no longer used by any application, thereby excluding released network slices from the next requested NSSAI, and wherein at least one memory and computer program code are configured, together with at least one processor, to further: configure the device to release network slices no longer used by any application based on the value of the timer, and to exclude released network slices from the next requested NSSAI.

[0095] According to another embodiment, an apparatus may be provided, comprising: components for receiving a registration request message from a user equipment at a network entity of a communication system; components for transmitting a registration acceptance or rejection message from the network entity to the user equipment, in response to receiving the registration request message, to configuration information including configuration information indicating that the user equipment supports or requires network control slice selection behavior, wherein the configuration information includes instructions for the user equipment to request all single network slice selection assistance information (S-NSSAI) configured with network slice selection assistance information (NSSAI) or instructions for the user equipment to request all S-NSSAIs configured by default with NSSAI; and components for providing configuration information from the network entity to the user equipment via a downlink non-access stratum transmission message or a UE configuration update message, wherein the configuration information includes instructions for the user equipment to request all S-NSSAIs configured with NSSAI or instructions for the user equipment to request all S-NSSAIs configured by default with NSSAI. In some embodiments, the registration acceptance or rejection message or the downlink non-access stratum transmission or UE configuration update message includes instructions for the user equipment to always request a subset of S-NSSAIs from the configured NSSAIs. In some embodiments, a subset of S-NSSAIs is identified by one or more flags associated with each S-NSSAI provided to the user equipment in the configured NSSAIs or default configured NSSAIs, wherein the one or more S-NSSAIs are determined by the network based on local policies or based on information received from the user equipment's subscription information. In some embodiments, the registration accept or reject message or downlink non-access stratum transport or UE configuration update message includes instructions for the user equipment to request only S-NSSAIs with active applications. In some embodiments, the registration accept or reject message or downlink non-access stratum transport or UE configuration update message includes instructions for the user equipment to release network slices that are no longer used by any application, thereby excluding released network slices from the next requested NSSAI.

[0096] According to another embodiment, an apparatus may be provided, comprising: a component for receiving, at a user equipment, a registration acceptance or rejection message from a network entity in response to a registration request message previously transmitted from the user equipment to a network entity of a communication system, the registration request message including information indicating that the user equipment supports or requires network control slice selection behavior, the registration acceptance or rejection message including instructions for the user equipment to request all single network slice selection assistance information (S-NSSAI) configured with network slice selection assistance information (NSSAI) or instructions for the user equipment to request all S-NSSAIs that are configured by default with NSSAI; a component for receiving a downlink non-access stratum transmission message or a UE configuration update message including configuration information, the configuration information including instructions for the user equipment to request all S-NSSAIs configured with NSSAI or instructions for the user equipment to request all S-NSSAIs that are configured by default with NSSAI; and a component for configuring the user equipment to request all S-NSSAIs configured with NSSAI or configured by default with NSSAI when the user equipment is in a communication system. In some embodiments, the registration accept or reject message or downlink non-access stratum transmission message or UE configuration update message includes instructions for the user equipment to always request a subset of S-NSSAIs in the configured NSSAIs, and the means further includes: a component for configuring the user equipment to always request a subset of S-NSSAIs in the configured NSSAIs. In some embodiments, the S-NSSAI subset is identified by one or more flags associated with each S-NSSAI provided to the user equipment in the configured NSSAIs or default configured NSSAIs. In some embodiments, the registration accept or reject message or downlink non-access stratum transmission message or UE configuration update message includes instructions for the user equipment to request only S-NSSAIs with active applications, and the means further includes: a component for configuring the user equipment to request only S-NSSAIs with active applications. In some embodiments, the registration accept or reject message downlink non-access stratum transmission message or UE configuration update message includes a timer configured to cause the user equipment to release a network slice that is no longer used by any application, thereby excluding the released network slice from the next requested NSSAI. The apparatus further includes components for configuring the user equipment to release a network slice that is no longer used by any application based on the value of the timer and for excluding the released network slice from the next requested NSSAI.

[0097] According to another embodiment, a computer program product may be provided, comprising at least one non-transitory computer-readable storage medium storing computer-executable program code instructions therein, the computer-executable program code instructions including program code instructions configured, when executed, to: receive a registration request message from a user equipment at a network entity of a communication system; if the registration request message includes information indicating that the user equipment supports or requires network control slice selection behavior, in response to receiving the registration request message, transmit a registration acceptance or rejection message from the network entity to the user equipment including configuration information, the configuration information including instructions for the user equipment to request all single network slice selection assistance information (S-NSSAI) configured with network slice selection assistance information (NSSAI) or instructions for the user equipment to request all S-NSSAIs configured by default with NSSAI; and provide configuration information from the network entity to the user equipment via a downlink non-access stratum transmission message or a UE configuration update message, the configuration information including instructions for the user equipment to request all S-NSSAIs configured with NSSAI or instructions for the user equipment to request all S-NSSAIs configured by default with NSSAI. In some embodiments, the registration accept or reject message or downlink non-access stratum transport or UE configuration update message includes 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 is identified by one or more flags associated with each S-NSSAI provided to the user equipment in the configured NSSAIs or default configured NSSAIs, wherein the one or more S-NSSAIs are determined by the network based on local policies or based on information received from the user equipment's subscription information. In some embodiments, the registration accept or reject message or downlink non-access stratum transport or UE configuration update message includes instructions for the user equipment to request only S-NSSAIs with active applications. In some embodiments, the registration accept or reject message or downlink non-access stratum transport or UE configuration update message includes instructions for the user equipment to release network slices no longer used by any application, thereby excluding released network slices from the next requested NSSAI.

[0098] According to another embodiment, a computer program product includes at least one non-transitory computer-readable storage medium storing computer-executable program code instructions therein, the computer-executable program code instructions including program code instructions configured, when executed, to: at a user equipment, in response to a registration request message previously transmitted from the user equipment to a network entity of a communication system, receive a registration acceptance or rejection message from the network entity, the registration request message including information indicating that the user equipment supports or requires network control slice selection behavior, the registration acceptance or rejection message including information for the user equipment to request configured network slice selection assistance information (NS). The system receives instructions for all Single Network Slice Selection Auxiliary Information (S-NSSAI) of the SAI or instructions for the user equipment to request all S-NSSAIs of the default configured NSSAI; receives downlink non-access stratum transport messages or UE configuration update messages including configuration information, such configuration information including instructions for the user equipment to request all S-NSSAIs of the configured NSSAI or instructions for the user equipment to request all S-NSSAIs of the default configured NSSAI; and configures the user equipment to request all S-NSSAIs of the configured NSSAI or the default configured NSSAI when the user equipment is in a communication system. In some embodiments, the registration accept or reject message or downlink non-access stratum transport message or UE configuration update message includes instructions for the user equipment to always request a subset of S-NSSAIs in the configured NSSAI, and wherein the computer-executable program code instructions include program code instructions that, when executed, are configured to: configure the user equipment to always request a subset of S-NSSAIs in the configured NSSAI. In some embodiments, a subset of S-NSSAIs is identified by one or more flags associated with each S-NSSAI provided to the user equipment in the configured NSSAIs or default configured NSSAIs. In some embodiments, the registration accept or reject message or downlink non-access stratum transport message or UE configuration update message includes instructions for the user equipment to request only S-NSSAIs with active applications, and wherein the computer-executable program code instructions include program code instructions configured, upon execution, to: configure the user equipment to request only S-NSSAIs with active applications. In some embodiments, the registration accept or reject message downlink non-access stratum transport message or UE configuration update message includes a timer configured to cause the user equipment to release network slices no longer used by any application, thereby excluding released network slices from the next requested NSSAI, and wherein the computer-executable program code instructions include program code instructions configured, upon execution, to: configure the user equipment to release network slices no longer used by any application based on the value of the aforementioned timer, and exclude released network slices from the next requested NSSAI.

[0099] According to another embodiment, a method can be performed, comprising: at a user equipment, receiving configuration information from a network entity in a communication system in a downlink non-access stratum transmission message or a UE configuration update message, the configuration information including an instruction that the user equipment always establishes all Protocol Data Unit (PDU) sessions for all data network names associated with a Single Network Slice Selection Auxiliary Information (S-NSSAI); and configuring the user equipment to always establish all PDU sessions for all data network names associated with the S-NSSAI. In some embodiments, the configuration information includes a request that the user equipment by default establish a specific PDU session or subset of PDU sessions associated with the S-NSSAI when the S-NSSAI is identified by a data network name associated with a flag, the method further comprising: configuring the user equipment to by default establish a specific PDU session or subset of PDU sessions associated with the S-NSSAI when the S-NSSAI is identified by a data network name associated with a flag, the method further comprising: configuring the user equipment to by default establish a specific PDU session or subset of PDU sessions associated with the S-NSSAI when the S-NSSAI is identified by a data network name associated with a flag. In some embodiments, the configuration information includes a request from a user equipment (UE) to establish a PDU session in a network slice identified by S-NSSAI at least when no DNN is configured for S-NSSAI, and the method further includes configuring the UE to establish a PDU session in a network slice identified by S-NSSAI at least when no DNN is configured for S-NSSAI. In some embodiments, the configuration information includes a request from a UE to establish a PDU session in a network slice identified by S-NSSAI only when at least one application needs to use the PDU session, and the method further includes configuring the UE to establish a PDU session in a network slice identified by S-NSSAI only when at least one application needs to use the PDU session. In some embodiments, the configuration information includes a request from a UE to provide an explicit timer that causes the UE to release a PDU session no longer associated with any application, and the method further includes configuring the UE to provide an explicit timer that causes the UE to release a PDU session no longer associated with any application.

[0100] According to another embodiment, an apparatus may be provided, the apparatus including at least one processor and at least one memory, the at least one memory including computer program code for one or more programs, the at least one memory and the computer program code being configured together with the at least one processor to cause the apparatus to at least: receive configuration information from a network entity in a communication system in a downlink non-access stratum transmission message or a UE configuration update message, the configuration information including instructions for the apparatus to always establish all Protocol Data Unit (PDU) sessions for all data network names associated with Single Network Slice Selection Assistance Information (S-NSSAI); and configure the apparatus to always establish all PDU sessions for all data network names associated with S-NSSAI. In some embodiments, the configuration information includes a request for the device to by default establish a specific PDU session or subset of PDU sessions associated with the S-NSSAI when the S-NSSAI is identified by a data network name associated with the flag, wherein at least one memory and computer program code are further configured, together with at least one processor, to cause the device to at least: configure the device to establish a specific PDU session or subset of PDU sessions associated with the S-NSSAI by default when the S-NSSAI is identified by a data network name associated with the flag. In some embodiments, the configuration information includes a request for the device to establish a PDU session in a network slice identified by the S-NSSAI when no DNN is configured for the S-NSSAI, wherein at least one memory and computer program code are further configured, together with at least one processor, to cause the device to at least: configure the device to establish a PDU session in a network slice identified by the S-NSSAI when no DNN is configured for the S-NSSAI. In some embodiments, the configuration information includes a request for the device to establish a PDU session in a network slice identified by S-NSSAI only when at least one application needs to use the PDU session, wherein at least one memory and computer program code are further configured, together with at least one processor, to cause the device to at least: configure the device to establish a PDU session in a network slice identified by S-NSSAI only when at least one application needs to use the PDU session. In some embodiments, the configuration information includes a request for the device to provide an explicit timer that causes the device to release a PDU session no longer associated with any application, wherein at least one memory and computer program code are further configured, together with at least one processor, to cause the device to at least: configure the device to provide an explicit timer that causes the device to release a PDU session no longer associated with any application.

[0101] According to another embodiment, an apparatus is provided that may include: a component for receiving configuration information from a network entity in a communication system at the apparatus, in a downlink non-access stratum transmission message or a UE configuration update message, the configuration information including instructions that the apparatus always establishes all Protocol Data Unit (PDU) sessions for all data network names associated with a Single Network Slice Selection Auxiliary Information (S-NSSAI); and a component for configuring the apparatus to always establish all PDU sessions for all data network names associated with the S-NSSAI. In some embodiments, the configuration information includes a request that the apparatus by default establish a specific PDU session or subset of PDU sessions associated with the S-NSSAI when the S-NSSAI is identified by a data network name associated with a flag, the apparatus further including: a component for configuring the apparatus to by default establish a specific PDU session or subset of PDU sessions associated with the S-NSSAI when the S-NSSAI is identified by a data network name associated with a flag. In some embodiments, the configuration information includes a request for the device to establish a PDU session in a network slice identified by S-NSSAI at least when no DNN is configured for S-NSSAI, and the device further includes a component for configuring the device to establish a PDU session in a network slice identified by S-NSSAI at least when no DNN is configured for S-NSSAI. In some embodiments, the configuration information includes a request for the device to establish a PDU session in a network slice identified by S-NSSAI only when at least one application needs to use the PDU session, and the device further includes a component for configuring the device to establish a PDU session in a network slice identified by S-NSSAI only when at least one application needs to use the PDU session. In some embodiments, the configuration information includes a request for the device to provide an explicit timer that causes the device to release PDU sessions no longer associated with any application, and the device further includes a component for configuring the device to provide an explicit timer that causes the device to release PDU sessions no longer associated with any application.

[0102] According to another embodiment, a computer program product may be provided, comprising at least one non-transitory computer-readable storage medium storing computer-executable program code instructions therein, the computer-executable program code instructions including program code instructions configured, when executed, to: at a user equipment, in a downlink non-access stratum transmission message or a UE configuration update message, receive configuration information from a network entity in a communication system, the configuration information including instructions for the user equipment to always establish all Protocol Data Unit (PDU) sessions for all data network names associated with Single Network Slice Selection Auxiliary Information (S-NSSAI); and configure the user equipment to always establish all PDU sessions for all data network names associated with S-NSSAI. In some embodiments, the configuration information includes a request from a user equipment to establish, by default, a specific PDU session or subset of PDU sessions associated with the S-NSSAI when the S-NSSAI is identified by a data network name associated with the flag. The computer-executable program code instructions further include program code instructions configured, when executed, to configure the user equipment to establish, by default, a specific PDU session or subset of PDU sessions associated with the S-NSSAI when the S-NSSAI is identified by a data network name associated with the flag. In some embodiments, the configuration information includes a request from a user equipment to establish a PDU session in a network slice identified by the S-NSSAI when at least no DNN is configured for the S-NSSAI. The computer-executable program code instructions further include program code instructions configured, when executed, to configure the user equipment to establish a PDU session in a network slice identified by the S-NSSAI when at least no DNN is configured for the S-NSSAI. In some embodiments, the configuration information includes a request from the user equipment to establish a PDU session in a network slice identified by S-NSSAI only when at least one application needs to use the PDU session, wherein the computer-executable program code instructions further include program code instructions configured, when executed, to configure the user equipment to establish a PDU session in a network slice identified by S-NSSAI only when at least one application needs to use the PDU session. In some embodiments, the configuration information includes a request from the user equipment to provide an explicit timer that causes the user equipment to release a PDU session no longer associated with any application, wherein the computer-executable program code instructions further include program code instructions configured, when executed, to configure the user equipment to provide an explicit timer that causes the user equipment to release a PDU session no longer associated with any application.

[0103] According to another embodiment, a method can be implemented comprising: providing configuration information from a network entity in a communication system to a user equipment (UE) in a downlink non-access stratum transport message or a UE configuration update message, the configuration information including an instruction from the UE to always establish all Protocol Data Unit (PDU) sessions for all data network names associated with a Single Network Slice Selection Auxiliary Information (S-NSSAI). In some embodiments, the configuration information includes a request from the UE to by default establish a specific PDU session or subset of PDU sessions associated with the S-NSSAI when the S-NSSAI is identified by a data network name associated with a flag. In some embodiments, the configuration information includes a request from the UE to establish PDU sessions in a network slice identified by the S-NSSAI at least when no DNN is configured for the S-NSSAI. In some embodiments, the configuration information includes a request from the UE to establish PDU sessions in a network slice identified by the S-NSSAI only when at least one application requires the use of the PDU session. In some embodiments, the configuration information includes a request from the UE to provide an explicit timer that causes the UE to release PDU sessions no longer associated with any application.

[0104] According to another embodiment, an apparatus may be provided, comprising at least one processor and at least one memory, the at least one memory including computer program code for one or more programs, the at least one memory and the computer program code being configured, together with the at least one processor, to cause the apparatus to at least: provide configuration information from the apparatus to a user equipment in a downlink non-access stratum transport or UE configuration update message, the configuration information including instructions for the user equipment to always establish all Protocol Data Unit (PDU) sessions for all data network names associated with Single Network Slice Selection Auxiliary Information (S-NSSAI). In some embodiments, the configuration information includes a request from the apparatus to by default establish a specific PDU session or subset of PDU sessions associated with the S-NSSAI when the S-NSSAI is identified by a data network name associated with a flag. In some embodiments, the configuration information includes a request from the apparatus to establish a PDU session in a network slice identified by the S-NSSAI at least when no DNN is configured for the S-NSSAI. In some embodiments, the configuration information includes a request from the apparatus to establish a PDU session in a network slice identified by the S-NSSAI only when at least one application requires the use of the PDU session. In some embodiments, the configuration information includes a request from the device to provide an explicit timer that causes the device to release a PDU session that is no longer associated with any application.

[0105] According to another embodiment, an apparatus may be provided, comprising: a component for providing configuration information from a network entity in a communication system to a user equipment (UE) in a downlink non-access stratum transmission message or a UE configuration update message, the configuration information including instructions for the UE to always establish all Protocol Data Unit (PDU) sessions for all data network names associated with a Single Network Slice Selection Auxiliary Information (S-NSSAI). In some embodiments, the configuration information includes a request for the apparatus to by default establish a specific PDU session or subset of PDU sessions associated with the S-NSSAI when the S-NSSAI is identified by a data network name associated with a flag. In some embodiments, the configuration information includes a request for the apparatus to establish PDU sessions in a network slice identified by the S-NSSAI at least when no DNN is configured for the S-NSSAI. In some embodiments, the configuration information includes a request for the apparatus to establish PDU sessions in a network slice identified by the S-NSSAI only when at least one application needs to use the PDU session. In some embodiments, the configuration information includes a request for the apparatus to provide an explicit timer that causes the apparatus to release PDU sessions no longer associated with any application.

[0106] According to another embodiment, a computer program product may be provided, comprising at least one non-transitory computer-readable storage medium storing computer-executable program code instructions, the computer-executable program code instructions being configured, when executed, to: provide configuration information from a network entity in a communication system to a user equipment (UE) in a downlink non-access stratum transmission message or a UE configuration update message, the configuration information including instructions for the UE to always establish all Protocol Data Unit (PDU) sessions for all data network names associated with a Single Network Slice Selection Auxiliary Information (S-NSSAI). In some embodiments, the configuration information includes a request for the UE to by default establish a specific PDU session or subset of PDU sessions associated with the S-NSSAI when the S-NSSAI is identified by a data network name associated with a flag. In some embodiments, the configuration information includes a request for the UE to establish a PDU session in a network slice identified by the S-NSSAI at least when no DNN is configured for the S-NSSAI. In some embodiments, the configuration information includes a request for the UE to establish a PDU session in a network slice identified by the S-NSSAI only when at least one application requires the use of the PDU session. In some embodiments, the configuration information includes a request from the user equipment to provide an explicit timer that causes the user equipment to release a PDU session that is no longer associated with any application.

[0107] Those skilled in the art to which these inventions pertain will be able to conceive of many modifications and other embodiments of the invention set forth herein, benefiting from the teachings illustrated in the foregoing description and the accompanying drawings. Therefore, it should be understood 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 terminology is used herein, it is used only in a general and descriptive sense and not for purposes of limitation.

Claims

1. A method for communication, the method comprising: At the network entity of the communication system, a registration request message is received from the user equipment. If the registration request message includes information indicating that the user equipment supports or requires network control slice selection behavior, in response to receiving the registration request message, the network entity transmits a registration acceptance or rejection message including configuration information to the user equipment. The configuration information includes: an instruction for the user equipment to request all single network slice selection assistance information (S-NSSAI) configured with NSSAI, or an instruction for the user equipment to request all S-NSSAIs configured by default with NSSAI; and Configuration information is provided from the network entity to the user equipment via downlink non-access stratum transmission messages or UE configuration update messages. The configuration information includes: instructions for the user equipment to request all S-NSSAIs that have been configured with NSSAI, or instructions for the user equipment to request all S-NSSAIs that have been configured with NSSAI by default.

2. The method according to claim 1, The registration acceptance or rejection message or the downlink non-access stratum transmission or UE configuration update message includes: Instructions for the user equipment to always request the S-NSSAI subset from the configured NSSAI.

3. The method according to claim 2, The S-NSSAI subset is 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, wherein the one or more S-NSSAIs are determined by the network based on local policies or based on information received from the user equipment's subscription information.

4. The method according to claim 1, The registration acceptance or rejection message or the downlink non-access stratum transmission or UE configuration update message includes: The user equipment only requests instructions from S-NSSAI with active applications.

5. The method according to claim 4, The registration acceptance or rejection message, or the downlink non-access stratum transmission, or the UE configuration update message includes: Instructions for the user equipment to release network slices that are no longer used by any application, thereby excluding the released network slices from the next requested NSSAI.

6. A method for communication, the method comprising: At the user equipment, in response to a registration request message previously transmitted from the user equipment to a network entity of the communication system, a registration acceptance or rejection message is received from the network entity. The registration request message includes information indicating that the user equipment supports or requires configuration of network control slice selection behavior. The registration acceptance or rejection message includes: an instruction for the user equipment to request all single network slice selection assistance information S-NSSAIs that are configured with network slice selection assistance information NSSAI, or an instruction for the user equipment to request all S-NSSAIs that are configured with NSSAI by default. The system receives downlink non-access stratum transmission messages or UE configuration update messages that include configuration information, such as: instructions for the user equipment to request all S-NSSAIs that have been configured with NSSAI, or instructions for the user equipment to request all S-NSSAIs that have been configured with NSSAI by default; and... The user equipment is configured to request all S-NSSAIs of the configured NSSAI or the default configured NSSAI when the user equipment is in the communication system.

7. The method according to claim 6, The registration acceptance or rejection message, downlink non-access stratum transmission message, or UE configuration update message mentioned above include: Instructions for the user equipment to always request the S-NSSAI subset from the configured NSSAI. The method further includes: Configure the user equipment to always request the S-NSSAI subset from the configured NSSAI.

8. The method according to claim 7, The S-NSSAI subset is 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.

9. The method according to claim 6, The registration acceptance or rejection message, downlink non-access stratum transmission message, or UE configuration update message mentioned above include: The user equipment is used to request only S-NSSAI instructions with active applications. The method further includes: Configure the user equipment to only request S-NSSAI with active applications.

10. The method according to claim 9, The registration acceptance or rejection message, downlink non-access stratum transport message, or UE configuration update message includes a timer configured to cause the user equipment to release network slices no longer used by any application, thereby excluding released network slices from the next requested NSSAI. The method further includes: Configure the user equipment to release network slices that are no longer used by any application based on the value of the timer, and exclude the released network slices from the next requested NSSAI.

Images