WO2023060182A1

WO2023060182A1 - Local release mechanism for network slicing

Info

Publication number: WO2023060182A1
Application number: PCT/US2022/077682
Authority: WO
Inventors: Sridhar Prakasam; Nirlesh KOSHTA; Krisztian Kiss; Vijay Venkataraman
Original assignee: Apple Inc
Current assignee: Apple Inc
Priority date: 2021-10-08
Filing date: 2022-10-06
Publication date: 2023-04-13
Anticipated expiration: 2024-04-08

Abstract

A user equipment (UE) is configured to register with an allowed network slice, receive a timer duration value for a network slice specific deactivation timer corresponding to the allowed network slice and operate the network slice specific deactivation timer, wherein the network slice specific deactivation timer is configured to trigger a local release of the allowed network slice at the UE.

Description

Local Release Mechanism for Network Slicing

Inventors : Sridhar Prakasam, Nirlesh Koshta, Kris ztian Kiss and Vij ay Venkataraman

Background

[ 0001 ] A user equipment (UE ) may connect to a network that deploys multiple network slices . Generally, a network slice refers to an end-to-end logical network that is configured to provide a particular service and/or possess particular network characteristics . Each network slice may be isolated from one another but run on a shared network infrastructure . Thus , each network slice may share network resources but facilitate di f ferent functionality .

[ 0002 ] The network may be configured to perform network slice quota management . For example , the network may restrict the number of UEs registered to a particular network slice to ensure that there are available network slice resources for the registered UEs . However, there may be a subset of registered UEs that are not actually utili zing the network slice . This may create a scenario where one or more UEs are unable to access a network slice due to network slice quota management . Meanwhile , not all of the UEs registered to that network slice are actually utili zing the network slice .

Summary

[ 0003 ] Some exemplary embodiments are related to a processor of a user equipment (UE ) configured to perform operations . The operations include registering with an allowed network slice , receiving a timer duration value for a network slice speci fic deactivation timer corresponding to the allowed network slice and operating the network slice speci fic deactivation timer, wherein the network slice speci fic deactivation timer is configured to trigger a local release of the allowed network slice at the UE .

[ 0004 ] Other exemplary embodiments are related to a user equipment (UE ) having a transceiver configured to communicate with a network and a processor communicatively coupled to the transceiver and configured to perform operations . The operations include registering with an allowed network slice , receiving a timer duration value for a network slice speci fic deactivation timer corresponding to the allowed network slice and operating the network slice speci fic deactivation timer, wherein the network slice speci fic deactivation timer is configured to trigger a local release of the allowed network slice at the UE .

[ 0005 ] Still further exemplary embodiments are related to a network function configured to perform operations . The operations include transmitting a registration accept message comprising an allowed network slice to a user equipment (UE ) , transmitting a timer duration value for a network slice speci fic deactivation timer corresponding to the allowed network slice and operating the network slice speci fic deactivation timer on the network side , wherein the network slice speci fic deactivation timer is configured to trigger a local release of the allowed network slice on the network side .

[ 0006 ] Additional exemplary embodiments are related to a network function configured to perform operations . The operations include receiving a packet data unit ( PDU) session establishment request from a user equipment (UE ) , transmitting a timer duration value for a PDU session specific deactivation timer to the UE and operating the PDU session specific deactivation timer on the network side, wherein the PDU session specific deactivation timer is configured to trigger a local release of the PDU session on the network side.

Brief Description of the Drawings

[0007] Fig. 1 shows an exemplary network arrangement according to various exemplary embodiments.

[0008] Fig. 2 shows an exemplary network architecture according to various exemplary embodiments.

[0009] Fig. 3 shows an exemplary user equipment (UE) according to various exemplary embodiments.

[0010] Fig. 4 shows an exemplary base station according to various exemplary embodiments.

[0011] Fig. 5 shows a signaling diagram illustrating an example of the network slice specific deactivation timer according to various exemplary embodiments.

[0012] Fig. 6 shows a signaling diagram illustrating an example of the packet data unit (PDU) session specific deactivation timer according to various exemplary embodiments.

[0013] Fig. 7 shows a signaling diagram illustrating an example of utilizing the network slice specific deactivation timer in conjunction with the PDU session specific deactivation timer according to various exemplary embodiments. [ 0014 ] Fig . 8 shows a signaling diagram illustrating an example of an access and mobility management function (AMF) change while the exemplary timers are running according to various exemplary embodiments .

[ 0015 ] Fig . 9 shows a signaling diagram illustrating an example of the session management function ( SMF) change while the exemplary timers are running according to various exemplary embodiments .

Detailed Description

[ 0016 ] The exemplary embodiments may be further understood with reference to the following description and the related appended drawings , wherein like elements are provided with the same reference numerals . The exemplary embodiments relate to network slicing . As will be described in more detail below, the exemplary embodiments introduce mechanisms to locally release a configured network slice and/or packet data unit ( PDU) session .

[ 0017 ] The exemplary embodiments are described with regard to a user equipment (UE ) . However, the use of the term "UE" is merely for illustrative purposes . The exemplary embodiments may be utili zed with any electronic component that may establish a connection with a network and is configured with the hardware , software , and/or firmware to exchange information and data with the network . Therefore , the UE as described herein is used to represent any suitable electronic component .

[ 0018 ] The exemplary embodiments are described with regard to a fi fth generation ( 5G) network that supports network slicing . Generally, network slicing refers to a network architecture in which multiple end-to-end logical networks run on a shared physical network infrastructure. Each network slice may be configured to provide a particular set of capabilities and/or characteristics. Thus, the physical infrastructure of the 5G network may be sliced into multiple virtual networks, each configured for a different purpose. Throughout this description, reference to a network slice may represent any type of end-to- end logical network that is configured to serve a particular purpose and implemented on the 5G physical infrastructure.

[0019] Those skilled in the art will understand that 5G may support a variety of different use cases, e.g., enhanced mobile broadband (eMBB) , enhanced machine type communication (eMTC) , industrial internet of things (IIoT) , ultra-reliable low-latency communication (URLLC) , etc. Each type of use case may relate to various different types of applications and/or services. A network slice may be characterized by a type of use case, a type of application and/or service, the entity that provides the application and/or service via the network slice, etc. However, any example in this description that characterizes a network slice in a specific manner is only provided for illustrative purposes. As mentioned above, throughout this description, reference to a network slice may represent any type of end-to- end logical network that is configured to serve a particular purpose and is implemented on the 5G physical infrastructure.

[0020] A network slice may be identified by single network slice selection assistance information (S-NSSAI) . Each instance of S-NSSAI may be associated with a public land mobile network (PLMN) and may include the slice service type (SST) and a slice descriptor (SD) . The SST may identify the expected behavior of the corresponding network slice with regard to services, features and characteristics. Those skilled in the art will understand that the SST may be associated with a standardized SST value. The SD may identify any one or more entities associated with the network slice. For example, the SD may indicate an owner or an entity that manages the network slice (e.g., carrier) and/or the entity that the is providing the application/service via the network slice (e.g., a third-party, the entity that provides the application or service, etc.) . In some embodiments, the same entity may own the slice and provide the service (e.g., carrier services) . Throughout this description, S-NSSAI refers to a single network slice and the terms "NSSAI" or "S-NSSAIs" may be used interchangeably to refer to one or more network slices.

[0021] The UE may be configured to perform any of a wide variety of different tasks. Thus, the UE may be configured to utilize one or more network slices. To provide an example, the UE may utilize a first network slice for one or more carrier services (e.g., voice, multimedia messaging service (MMS) , Internet, etc.) and a second different network slice for a third-party service. However, the configured purpose of a network slice is beyond the scope of the exemplary embodiments. The exemplary embodiments are not limited to any particular type of network slice.

[0022] The exemplary embodiments are also described with regard to network slice quota management. Generally, network slice quota management refers to the concept of the network managing access to network slice resources to ensure that network slice resources are available to the UEs registered to the network slice. To provide one example, the network may not configure the UE with a requested network slice if a maximum number of UEs are already registered to that network slice. [0023] A UE may request access to one or more network slices as part of a registration request. However, the UE may be configured to request a network slice during initial registration even when the UE will not actually utilize the network slice until a later time (if at all) . In addition, under conventional circumstances, the UE and the network may maintain the registered network slice configuration for an indefinite amount of time. From the perspective of the network operator, this type of UE behavior may create a less than ideal scenario where network slice quota management forces the network to deny one or more UEs access to a particular network slice to ensure that resources are available for the registered UEs. Meanwhile, some of those registered UEs will not utilize the network slice until a later time (if at all) . Not only may this prevent a UE from accessing a network slice it needs to utilize, but it is also an inefficient use of resources to maintain an allowed network slice that is not being utilized by the corresponding UE.

[0024] In one aspect, the exemplary embodiments introduce a network slice specific deactivation timer. The network slice specific deactivation timer may be configured to trigger a local release of a network slice on the UE side and the network side. Additional details regarding the operation of network slice specific deactivation timer will be provided below. Reference to the term "network slice specific deactivation timer" is merely provided for illustrative purposes. Different entities may refer to a similar concept by a different name.

[0025] The exemplary embodiments are also described with regard to a PDU session. Those skilled in the art will understand that the term "PDU session" generally refers to a logical connection between the UE and a data network. The UE may be configured with one or more PDU sessions within a particular network slice.

[0026] The presence of a PDU session within a network slice may indicate that a UE is utilizing or likely to utilize network slice resources and thus, may provide the basis for operating the network slice specific deactivation timer. However, like the configured or allowed network slice, the UE may be configured to initiate PDU session establishment even though the UE will not utilize the PDU session until a later timer (if at all) . In addition, the UE and the network may maintain the PDU session for an indefinite amount of time.

[0027] In another aspect, the exemplary embodiments introduce a PDU session specific deactivation timer. The PDU session specific deactivation timer may be configured to trigger a local release of a PDU session on the UE side and the network side. Additional details regarding operation of the PDU session specific deactivation timer will be provided below. Reference to the term "PDU session specific deactivation timer" is merely provided for illustrative purposes. Different entities may refer to a similar concept by a different name. The exemplary mechanisms may be used independently from one another, in conjunction with one another, with currently implemented network slicing mechanisms, future implementations of network slicing mechanisms and/or independently from other network slicing mechanisms .

[0028] Fig. 1 shows an exemplary network arrangement 100 according to various exemplary embodiments. The exemplary network arrangement 100 includes a UE 110. Those skilled in the art will understand that the UE 110 may be any type of electronic component that is configured to communicate via a network, e.g., mobile phones, tablet computers, desktop computers, smartphones, phablets, embedded devices, wearables, Internet of Things (loT) devices, etc. It should also be understood that an actual network arrangement may include any number of UEs being used by any number of users. Thus, the example of a single UE 110 is merely provided for illustrative purposes .

[0029] The UE 110 may be configured to communicate with one or more networks. In the example of the network configuration 100, the network with which the UE 110 may wirelessly communicate is a 5G NR radio access network (RAN) 120. However, the UE 110 may also communicate with other types of networks (e.g., 5G cloud RAN, a next generation RAN (NG-RAN) , a long-term evolution (LTE) RAN, a legacy cellular network, a wireless local area network (WLAN) , etc.) and the UE 110 may also communicate with networks over a wired connection. With regard to the exemplary embodiments, the UE 110 may establish a connection with the 5G NR RAN 120. Therefore, the UE 110 may have a 5G NR chipset to communicate with the 5G NR RAN 120.

[0030] The 5G NR RAN 120 may be a portion of a cellular network that may be deployed by a network carrier (e.g., Verizon, AT&T, T-Mobile, etc.) . The 5G NR RAN 120 may include, for example, nodes, cells or base stations (e.g., Node Bs, eNodeBs, HeNBs, eNBS, gNBs, gNodeBs, macrocells, microcells, small cells, femtocells, etc.) that are configured to send and receive traffic from UEs that are equipped with the appropriate cellular chip set. [0031] Those skilled in the art will understand that any association procedure may be performed for the UE 110 to connect to the 5G NR-RAN 120. For example, as discussed above, the 5G NR-RAN 120 may be associated with a particular cellular provider where the UE 110 and/or the user thereof has a contract and credential information (e.g., stored on a SIM card) . Upon detecting the presence of the 5G NR-RAN 120, the UE 110 may transmit the corresponding credential information to associate with the 5G NR-RAN 120. More specifically, the UE 110 may associate with a specific base station, e.g., the next generation Node B (gNB) 120A.

[0032] The network arrangement 100 also includes a cellular core network 130, the Internet 140, an IP Multimedia Subsystem (IMS) 150, and a network services backbone 160. The cellular core network 130 may refer an interconnected set of components that manages the operation and traffic of the cellular network. It may include the evolved packet core (EPC) and/or the fifth generation core (5GC) . The cellular core network 130 also manages the traffic that flows between the cellular network and the Internet 140. The IMS 150 may be generally described as an architecture for delivering multimedia services to the UE 110 using the IP protocol. The IMS 150 may communicate with the cellular core network 130 and the Internet 140 to provide the multimedia services to the UE 110. The network services backbone 160 is in communication either directly or indirectly with the Internet 140 and the cellular core network 130. The network services backbone 160 may be generally described as a set of components (e.g., servers, network storage arrangements, etc.) that implement a suite of services that may be used to extend the functionalities of the UE 110 in communication with the various networks .

[0033] Fig. 2 shows an exemplary network architecture 200 according to various exemplary embodiments. The following description will provide a general overview of the various components of the exemplary architecture 200. The specific operations performed by the components with respect to the exemplary embodiments will be described in greater detail after the description of the architecture 200.

[0034] Those skilled in the art will understand that the components of the exemplary architecture 200 may reside in various physical and/or virtual locations relative to the network arrangement 100 of Fig. 1. These locations may include, within the access network (e.g., RAN 120) , within the core network 130, as separate components outside of the locations described with respect to Fig. 1, etc.

[0035] In Fig. 2, the various components are shown as being connected via connections labeled Nx (e.g., Nl, N2, Nil, Nnsq) . Those skilled in the art will understand that each of these connections (or interfaces) are defined in the 3GPP Specifications. The exemplary architecture 200 is using these connections in the manner in which they are defined in the 3GPP Specifications. Furthermore, while these interfaces are termed connections throughout this description, it should be understood that these interfaces are not required to be direct wired or wireless connections, e.g., the interfaces may communicate via intervening hardware and/or software components. To provide an example, the UE 110 may exchange signals over the air with the gNB 120A. However, in the architecture 200 the UE 110 is shown as having a connection to the access and mobility management function (AMF) 205 . This connection or interface is not a direct communication link between the UE 110 and the AMF 205 , instead, it is a connection that is facilitated by intervening hardware and software components . Thus , throughout this description the terms "connection" and " interface" may be used interchangeably to describe the Nx interface between the various components .

[ 0036 ] The architecture 200 includes the UE 110 and the 5G NR RAN 120 . The UE 110 and the 5G NR RAN 120 are connected to the AMF 205 . The AMF 205 is generally responsible for connection and mobility management in the 5G NR RAN 120 . For example , the AMF 205 may perform operations related to registration management between the UE 110 and the core network 130 . The exemplary embodiments are not limited to an AMF that performs the above referenced operations . Those skilled in the art will understand the variety of di f ferent types of operations an AMF may perform . Further, reference to a single AMF 205 is merely for illustrative purposes , an actual network arrangement may include any appropriate number of AMFs .

[ 0037 ] The AMF 205 is connected to the session management function ( SMF) 210 . The SMF 210 may perform operations related to session management such as , but not limited to , session establishment , session release , IP address allocation, policy and QoS enforcement , etc . The exemplary embodiments are not limited to an SMF that performs the above referenced operations . Those skilled in the art will understand the variety of di f ferent types of operations a SMF may perform . Further, reference to a single SMF 210 is merely for illustrative purposes , an actual network arrangement may include any appropriate number of SMFs .

[ 0038 ] The AMF 205 and the SMF 210 are also connected to the network slice quota function (NSQ) 215 . The NSQ 215 may be configured to perform operations related to controlling the number of UEs registered per network slice . For example , the NSQ 215 may perform operations such as , but not limited to , maintaining a count of a number of registered UEs for a S-NSSAI and maintaining a count of a number of active PDU sessions for a S-NSSAI . To provide a more speci fic example , when deployed, the NSQ 215 may receive a registration request from the SMF 215 indicating that the UE 110 wants to register to a particular S- NSSAI and/or register a PDU session within the particular S- NSSAI . The NSQ 215 then checks the count of registered UEs within the S-NSSAI and determines whether the network slice quota has been reached . The NSQ 215 may then accept or rej ect the request . However, reference to a quota concept is merely provided for illustrative purposes . Those skilled in the art will understand that di f ferent entities may refer to similar concepts by a di f ferent name . For example , third generation partnership program ( 3GPP ) networks may use the terms quota and admission control to refer to the same concept .

[ 0039 ] The exemplary embodiments are not limited to an NSQ that performs the above referenced operations . Those skilled in the art will understand the variety of di f ferent types of operations a NSQ may perform . Further, reference to a single NSQ 215 is merely for illustrative purposes , an actual network arrangement may include any appropriate number of NSQs . [0040] Fig. 3 shows an exemplary UE 110 according to various exemplary embodiments. The UE 110 will be described with regard to the network arrangement 100 of Fig. 1. The UE 110 may include a processor 305, a memory arrangement 310, a display device 315, an input/output (I/O) device 320, a transceiver 325 and other components 330. The other components 330 may include, for example, an audio input device, an audio output device, a power supply, a data acquisition device, ports to electrically connect the UE 110 to other electronic devices, etc.

[0041] The processor 305 may be configured to execute a plurality of engines of the UE 110. For example, the engines may include a network slice specific deactivation engine 335 and a PDU session specific deactivation engine 340. The network slice specific deactivation engine 335 may perform various operations related to managing the network slice specific deactivation timer and triggering the local release of the registered network slice. The PDU session specific deactivation engine 340 may perform various operations related to managing the PDU session specific deactivation timer and triggering the local release of the PDU session.

[0042] The above referenced engines 335, 340 each being an application (e.g., a program) executed by the processor 305 is merely provided for illustrative purposes. The functionality associated with the engines 335, 340 may also be represented as a separate incorporated component of the UE 110 or may be a modular component coupled to the UE 110, e.g., an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry to receive signals and processing circuitry to process the signals and other information. The engines may also be embodied as one application or separate applications. In addition, in some UEs, the functionality described for the processor 305 is split among two or more processors such as a baseband processor and an applications processor. The exemplary embodiments may be implemented in any of these or other configurations of a UE .

[0043] The memory arrangement 310 may be a hardware component configured to store data related to operations performed by the UE 110. The display device 315 may be a hardware component configured to show data to a user while the I/O device 320 may be a hardware component that enables the user to enter inputs. The display device 315 and the I/O device 320 may be separate components or integrated together such as a touchscreen. The transceiver 325 may be a hardware component configured to establish a connection with the 5G NR-RAN 120, an LTE-RAN (not pictured) , a legacy RAN (not pictured) , a WLAN (not pictured) , etc. Accordingly, the transceiver 325 may operate on a variety of different frequencies or channels (e.g., set of consecutive frequencies) .

[0044] Fig. 4 shows an exemplary base station 400 according to various exemplary embodiments. The base station 400 may represent the gNB 120A or any other access node through which the UE 110 may establish a connection and manage network operations .

[0045] The base station 400 may include a processor 405, a memory arrangement 410, an input/output (I/O) device 415, a transceiver 420, and other components 425. The other components 425 may include, for example, an audio input device, an audio output device, a battery, a data acquisition device, ports to electrically connect the base station 400 to other electronic devices, etc.

[0046] The processor 405 may be configured to execute a plurality of engines for the base station 400. For example, the engines may include a network slicing engine 430. The network slicing engine 430 may perform various operations related to enabling network slicing including, but not limited to, facilitating communication between the UE 110 and various network components (e.g., AMF 205, SMF 210, etc.) .

[0047] The above noted engine 430 being an application (e.g., a program) executed by the processor 405 is only exemplary. The functionality associated with the engine 430 may also be represented as a separate incorporated component of the base station 400 or may be a modular component coupled to the base station 400, e.g., an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry to receive signals and processing circuitry to process the signals and other information. In addition, in some base stations, the functionality described for the processor 305 is split among a plurality of processors (e.g., a baseband processor, an applications processor, etc.) . The exemplary embodiments may be implemented in any of these or other configurations of a base station.

[0048] The memory 410 may be a hardware component configured to store data related to operations performed by the base station 400. The I/O device 415 may be a hardware component or ports that enable a user to interact with the base station 400. The transceiver 420 may be a hardware component configured to exchange data with the UE 110 and any other UE in the system 100. The transceiver 420 may operate on a variety of different frequencies or channels (e.g., set of consecutive frequencies) . Therefore, the transceiver 420 may include one or more components (e.g., radios) to enable the data exchange with the various networks and UEs.

[0049] In one aspect, the exemplary embodiments introduce a network slice specific deactivation timer. The network slice specific deactivation timer may be configured to trigger the local release of a configured or allowed network slice on the UE 110 side and the network side. The signaling diagram 500 provides an example of operating the network slice specific deactivation timer independently from the PDU session specific deactivation timer. An example of utilizing the network slice specific deactivation timer in conjunction with the PDU session specific deactivation timer are provided below with regard to the signaling diagram 700 of Fig. 7.

[0050] Fig. 5 shows a signaling diagram 500 illustrating an example of the network slice specific deactivation timer. The signaling diagram 500 will be described with regard to the network arrangements 100-200 of Figs. 1-2 and the UE 110 of Fig. 3.

[0051] The signaling diagram 500 includes the UE 110, the AMF 205, the NSQ 215 and the SMF 210. As will be described in more detail below, the UE 110 and the network may each operate a network slice specific deactivation timer corresponding to the UE 110 and a particular network slice. In this example, when the UE 110 has at least one PDU session within the network slice associated with the network slice specific deactivation timer, the network slice specific deactivation timer does not run. [0052] In 505, the UE 110 transmits a registration request to the AMF 205. The registration request may include requested NSSAI . In this example, a single network slice is discussed and may be referred to as "network slice A." However, reference to network slice A is not intended to limit the exemplary embodiments in any way and is merely utilized to for illustrative purposes to identify a particular network slice. In addition, reference to a single network slice is also provided as an example. The UE 110 may request multiple different network slices in the requested NSSAI and each allowed network slice may have its own network slice specific deactivation timer.

[0053] Although not shown in the signaling diagram 500, in some embodiments, the UE 110 may transmit capability information to the network indicating that the UE 110 is capable of operating a network slice specific deactivation timer. However, the exemplary embodiments are not required to utilize capability information to indicate to the network that the UE 110 is configured with this capability. For instances, to provide another example, this capability may be configured in the universal subscriber identity module (USIM) . The exemplary embodiments may utilize any explicit or implicit indication to indicate to the network whether the UE 110 is able to operate the network slice specific deactivation timer.

[0054] In 510, the network determines a network slice specific deactivation timer value. The network slice specific deactivation timer configuration may be determined by factors such as, but not limited to, a real-time network load, a projected network load, network slice subscription information corresponding to the UE 110, the type of requested network slice, a number of UEs registered to the network slice, a number of PDU session within the network slice, etc. The network slice specific deactivation timer value may be determined on a per UE basis or on a group basis depending on the characteristics of the group of UEs.

[0055] In this example, the AMF 205 and the NSQ 215 are shown as determining the network slice specific deactivation timer value on behalf of the network. However, this is just an example, any appropriate type of network component (e.g., network function, server, etc.) may be configured to determine the network slice specific deactivation timer value for the UE 110.

[0056] In 515, the AMF 205 transmits the registration accept message to the UE 110 in response to the registration request. The registration accept message may include the allowed NSSAI and a network slice specific deactivation timer value corresponding to one or more of the allowed NSSAI.

[0057] In some embodiments, the network may determine that it is unnecessary to configure a network slice specific deactivation timer for the UE 110 and network slice A. In this type of scenario, the network may not provide a network slice specific deactivation timer value for network slice A or may provide a value that indicates that the UE 110 is not to utilize a network slice specific deactivation timer for network slice A.

[0058] In 520, the UE 110 initiates the network slice specific deactivation timer. The UE 110 may configure the network slice specific deactivation timer based on the network slice specific deactivation timer value provided by the network. In 522, the AMF 205 initiates its own network slice specific deactivation timer corresponding to the UE 110 and allowed network slice (e.g., network slice A) . However, this is merely provided as an example. Any appropriate network component may operate the network slice specific deactivation timer on the network side.

[0059] In the signaling diagram 500, the duration of the network slice specific deactivation timer value is illustrated by the dotted line 524. However, those skilled in the art will understand that in an actual deployment scenario there may be relatively minor differences between the duration and/or start time between the network slice specific deactivation timer on the UE 110 side and the network slice specific deactivation timer operated on the network side. In addition, the exemplary embodiments do not require the network to operate its own network slice specific deactivation timer and any other appropriate indication may be utilized by the network to determine whether the allowed network slice configuration is still active at the UE 110.

[0060] Operations 525a-540a provide an example of network slice specific deactivation timer operation when a PDU session establishment procedure is initiated prior to the expiration of the network slice specific deactivation timer. In contrast, operations 525b-530b provide an example of network slice specific deactivation timer operation when PDU session establishment is not initiated and/or completed prior to the expiration of the network slice specific deactivation timer.

[0061] In 525a, the UE 110 initiates activation of a PDU session on the allowed network slice, e.g., network slice A. For example , an application running on the UE 110 may want to access the network slice to receive and/or transmit data to a server hosted on the Internet 140 or any other appropriate type of data network .

[ 0062 ] In 530a, the UE 110 stops the network slice speci fic deactivation timer . In some embodiments , the network slice speci fic deactivation timer may initially be paused to account for the possibility of a PDU session establishment failure or rej ection . I f the PDU session establishment procedures fails , the network slice speci fic deactivation timer may resume running . I f the PDU session establishment procedure is a success , the UE 110 may stop operating the network slice speci fic deactivation timer for this network slice until the timer is restarted, reset or the network slice is release . In 535a, the UE 110 transmits a PDU session establishment request to the SME 210 . In this example , the PDU session establishment request indicates that the UE 110 wants to activate a PDU session on network slice A. In 540a, the SME 210 transmits a PDU session establishment accept message to the UE 110 . Although shown as occurring before the PDU session establishment signaling, in some embodiments , the UE 110 may stop the network slice speci fic deactivation timer in response to the PDU session establishment request or accept . For instance , the UE 110 may not indicate a particular network slice in the PDU session establishment request . In this type of scenario , the UE 110 may stop a network slice speci fic deactivation timer corresponding to the network slice identi fied in the PDU session establishment accept message . Although not shown in the signaling diagram 500 , the network slice speci fic deactivation timer may be restarted after the PDU session release or DRB release . After the timer is restarted, the signaling diagram may return to 525a i f another PDU session or DRB is established. Alternatively, the signaling diagram 500 may continue to 525b.

[0063] In 525b, the UE 110 performs a local release of the allowed network slice (e.g., network slice A) in response to the expiration of the network slice specific deactivation timer. In this example, since PDU session establishment was not initiated and/or completed prior to the expiration of the network slice specific deactivation timer, the UE 110 releases the configuration for network slice A. Thus, the UE 110 may no longer be configured to perform operations related to maintaining the network slice configuration for network slice A.

[0064] In 530b, the AMF 205 performs a local release of the allowed network slice (e.g., network slice A) for the UE 110. In this example, since PDU session establishment was not initiated and/or completed prior to the expiration of the network slice specific deactivation timer, the AMF 205 releases configuration of network slice A for the UE 110. The UE 110 and the network are each operating their own timer (or other appropriate mechanism) and thus, do not need to explicitly communicate with one another to know that the allowed network slice is to be released or confirm that the allowed network slice has been released. The network no longer has to reserve network slice resources on the network slice A for the UE 110. The UE 110 may, at a later time, re-register to the network slice A using the standard registration request process.

[0065] Although not shown in the signaling diagram 500, prior to the expiration of the network slice specific deactivation timer, the network may transmit a configuration update command

(CUC) to the UE 110 associated with network slice A. The CUC may be configured to include a new network slice specific deactivation timer value. For example, the AMF 205 may transmit the CUC to the UE 110 in response to the network identifying a change in network load or subscription information. In some embodiments, the CUC may trigger the UE 110 to update the network slice specific deactivation timer value to a larger value. In other embodiments, the CUC may trigger the UE 110 to update the network slice specific deactivation timer value to a smaller value.

[0066] In another aspect, the exemplary embodiments introduce a PDU slice specific deactivation timer. The PDU slice specific deactivation timer may be configured to trigger the local release of a PDU session on the UE 110 side and the network side. The signaling diagram 600 provides an example of operating the PDU slice specific deactivation timer independently from the network slice specific deactivation timer. An example of utilizing the network slice specific deactivation timer in conjunction with the PDU session specific deactivation timer are provided below with regard to the signaling diagram 700 of Fig. 7.

[0067] Fig. 6 shows a signaling diagram 600 illustrating an example of the PDU session specific deactivation timer. The signaling diagram 600 will be described with regard to the network arrangements 100-200 of Figs. 1-2 and the UE 110 of Fig. 3.

[0068] The signaling diagram 600 includes the UE 110, the AMF 205, the NSQ 215 and the SMF 210. As will be described in more detail below, the UE 110 and the network may each operate a PDU slice specific deactivation timer corresponding to the UE 110 and a PDU session.

[0069] In 605, the UE 110 transmits a PDU session establishment request to the SME 210. In this example, the example PDU session may be identified as "PDU session ID-1." However, reference to PDU session ID-1 is not intended to limit the exemplary embodiments in any way and is merely utilized to for illustrative purposes to identify a particular PDU session. In addition, reference to a single PDU session within a network slice is also provided as an example. The UE 110 may request multiple different PDU sessions within the same network slice and each PDU session ID may correspond to its own PDU session specific deactivation timer.

[0070] Although not shown in the signaling diagram 600, in some embodiments, the UE 110 may transmit capability information to the network indicating that the UE 110 is capable of operating a PDU session specific deactivation timer. However, the exemplary embodiments are not required to utilize capability information to indicate to the network that the UE 110 is configured with this feature. The exemplary embodiments may utilize any explicit or implicit indication to indicate to the network whether the UE 110 is able to operate the PDU session specific deactivation timer.

[0071] In 610, the network determines a PDU session specific deactivation timer value. The PDU session specific deactivation timer configuration may be determined by factors such as, but not limited to, a real-time network load, a projected network load, network slice subscription information corresponding to the UE 110, the type of requested network slice, a number of UEs registered to the network slice, a number of PDU session within the network slice, etc. The PDU session specific deactivation timer value may be determined on a per UE basis or on a group basis depending on the characteristics of the group of UEs.

[0072] In this example, the SME 210 and the NSQ 215 are shown as determining the PDU session specific deactivation timer value on behalf of the network. However, this is just an example, any appropriate type of network component (e.g., network function, server, etc.) may be configured to determine the PDU session specific deactivation timer value for the UE 110.

[0073] In 615, the SME 210 transmits the PDU establishment accept message to the UE 110 in response to the PDU establishment request. The PDU establishment accept message may include a PDU session ID (e.g., PDU session ID-1) and a corresponding PDU session specific deactivation timer value.

[0074] In some embodiments, the network may determine that it is unnecessary to configure a PDU session specific deactivation timer for the UE 110 and PDU session ID-1. In this type of scenario, the network may not provide a PDU session specific deactivation timer value for PDU session ID-1 or may provide a value that indicates that the UE 110 is not to utilize a PDU session specific deactivation timer for PDU session ID-1.

[0075] At this time, it is assumed that the UE 110 is configured with a data radio bearer (DRB) for PDU session ID-1. In 620, the UE 110 initiates the PDU session specific deactivation timer when the corresponding DRB is released or suspended. The UE 110 may configure the PDU session specific deactivation timer based on the PDU session specific deactivation timer value provided by the network. In 622, the SMF 210 initiates its own PDU session specific deactivation timer corresponding to the UE 110 and PDU session (e.g., PDU session ID-1) . However, this is merely provided as an example. Any appropriate network component may operate the PDU session specific deactivation timer on the network side.

[0076] In the signaling diagram 600, the duration of the network slice specific deactivation timer value is illustrated by the dotted line 624. However, those skilled in the art will understand that in an actual deployment scenario there may be relatively minor differences between the duration and/or start time between the PDU session specific deactivation timer on the UE 110 side and the PDU session specific deactivation timer operated on the network side. In addition, the exemplary embodiments do not require the network to operate its own PDU session specific deactivation timer and any other appropriate indication may be utilized by the network to determine whether the PDU session configuration is still active at the UE 110.

[0077] Operations 625a-635a provide an example of a PDU session specific deactivation timer operation when a DRB is established for the PDU session prior to the expiration of the PDU session specific deactivation timer. In contrast, operations 625b-630b provide an example of PDU session specific deactivation timer operation when DRB establishment is not initiated and/or completed prior to the expiration of the PDU session specific deactivation timer.

[0078] In 625a, the UE 110 is triggered to establish a DRB on the PDU session, e.g., PDU session ID-1. For example, the UE 110 may have pending uplink data and initiates a service request procedure to establish the DRB . In another example , the DRB may be established in response to paging from the network indicating that data is to be transmitted to the UE 110 for the PDU session . In 630a, the UE 110 stops the PDU session speci fic deactivation timer . In 635a, the SME 210 stops the PDU session speci fic deactivation timer on the network side . Although not shown in the signaling diagram 600 , the PDU session speci fic deactivation timer may be restarted after the DRB release or suspension . After the timer is restarted, the signaling diagram may return to 625a i f another DRB establishment is triggered . Alternatively, the signaling diagram 600 may continue to 625b .

[ 0079 ] In 625b, the UE 110 performs a local release of the PDU session in response to the expiration of the PDU session speci fic deactivation timer . In this example , since DRB establishment was not initiated and/or completed prior to the expiration of the network slice speci fic deactivation timer, the UE 110 releases the configuration for the PDU session . Thus , the UE 110 may no longer be configured to perform operations related to maintaining the PDU session .

[ 0080 ] In 630b, the SME 210 performs a local release of the PDU session for the UE 110 . In this example , since DRB establishment was not initiated and/or completed prior to the expiration of the PDU session speci fic deactivation timer, the SME 210 releases configuration of PDU session ID- 1 for the UE 110 . The UE 110 and the network are each operating their own timer ( or other appropriate mechanism) and thus , do not need to explicitly communicate with one another to know that the PDU session is to be released or confirm that the PDU session has been released . The network no longer has to reserve network slice resources on network slice A for PDU session ID- 1 . [0081] Although not shown in either the signaling diagram 500 or 600, the network may modify one or more timer values using a modify PDU session command. This command may be triggered by the network based on network load, in response to a handover, a RAT reselection, a change in SMF, a change in AMF or any other appropriate condition or event. Alternatively, a modify PDU session request may be transmitted by the UE 110 to the network and in response, the modify PDU session accept message may include the updated network slice specific deactivation timer value and/or PDU session specific deactivation timer value.

[0082] Fig. 7 shows a signaling diagram 700 illustrating an example of utilizing the network slice specific deactivation timer in conjunction with the PDU session specific deactivation timer. The signaling diagram 700 will be described with regard to the network arrangements 100-200 of Figs. 1-2, the UE 110 of Fig. 3, the signaling diagram 500 of Fig. 5 and the signaling diagram 600 of Fig. 6.

[0083] The signaling diagram 700 includes the UE 110, the AMF 205, a user plane function (UPF) 702 and the SMF 210. In this example, it is assumed that the UE 110 has already been configured with an allowed NSSAI, network slice specific deactivation timer configuration information (e.g., timer duration, etc.) , a PDU session but no DRB and PDU session specific deactivation timer configuration information (e.g., timer duration, etc.) . For example, the UE 110 may be provided with a timer duration value corresponding to the network slice specific deactivation timer for network slice A and a timer duration value corresponding to the PDU session specific deactivation timer for PDU session ID-1. [0084] In 705, the network slice specific deactivation timer is running at the UE 110. In 710, the PDU session specific deactivation timer is running at the UE 110. In 715, the network slice specific deactivation timer is running at the AMF 205. In 720, the PDU session specific deactivation timer is running at the SME 210.

[0085] In this example, the DRB establishment is initiated by the network due to pending downlink data. However, in other embodiments, the DRB establishment may be initiated by the UE 110 in response to pending uplink data.

[0086] In 725, there is pending downlink data for the PDU session (e.g., PDU session ID-1) at the UPF 702. In 730, the SME 210 stops the PDU session specific deactivation timer in response to the pending downlink data. In 735, the AMF 205 stops the network slice specific deactivation timer in response to the pending downlink data.

[0087] In 740, the network performs a paging procedure and establishes a DRB on the PDU session. In 745, the UE 110 stops the network slice specific deactivation timer and the PDU session specific deactivation timer. The UE 110 now knows that the PDU session ID-1 on network slice A is about to be utilized for data transfer due to the establishment of the DRB in 740.

Thus, both the network slice and the PDU session are about to be utilized and the deactivation timer stops running.

[0088] In 750, the network releases or suspends the DRB for the PDU session after the data transfer ends. For example, the UE 110 may enter a radio resource control (RRC) inactive state where one or more DRBs for the PDU session are suspended. In another example, the UE 110 may enter a RRC idle state where the one or more DRBs for the PDU session are released. In 755, the UE 110 and the network restart the network slice specific deactivation timer (if no other PDU sessions have an active DRB on the network slice A) and the PDU session specific deactivation timer for PDU session ID-1.

[0089] In the signaling diagram 700, 760-775 show network slice specific deactivation timer handling and 780-795 show PDU session specific deactivation timer handling.

[0090] In 760, the network slice specific deactivation timer expires at the UE 110. In 765, the network slice specific deactivation timer expires at the network (e.g., AMF 205) . In 770, the UE 110 locally releases the network slice and the PDU sessions that belong to the network slice. In 775, the network locally releases the network slice and PDU sessions that belong to the network slice for the UE 110. In this example, the AMF 205 may perform the local release of the network slice and the SME 210 may perform the local release of the PDU session.

[0091] As indicated above, these timers may be operated on the network side on a per UE basis. In some embodiments, when the network slice specific deactivation timer expires, the network may release the PDU sessions on the network slice and adjust the network slice specific deactivation timer using a PDU session release command. This approach gives flexibility to the network to give preference to different types of subscriptions. For example, if the UE 110 was associated with a first subscription tier, the network may update the network slice specific deactivation timer instead of release it. However, if the UE 110 was associated with a lower subscription tier, the network may want to release the network slice and not update the network slice specific deactivation timer at the UE 110.

[0092] In 780, the PDU session specific deactivation timer expires at the UE 110. In this example for PDU session specific deactivation timer handling, it is assumed that the network slice specific deactivation timer is still running. In 785, the PDU session specific deactivation timer expires at the network (e.g., SME 210) . In 790, the UE 110 locally release the PDU session. In 795, the network releases the PDU session for the UE 110. In this example, the SME 210 performs the local release of the PDU session.

[0093] In another embodiment, the UE 110 may allow the network slice specific deactivation timer to run after a PDU session has been established on the network slice. When a DRB corresponding to the PDU session is not active or suspended, both the network slice specific deactivation timer and the PDU session specific deactivation timer may be running. In this scenario, when the network slice specific deactivation timer expires and a PDU session is active but without a DRB or with a suspended DRB, the UE 110 may locally release both the PDU session and the network slice. When the network slice specific deactivation timer expires and no PDU session is active for the network slice, then the UE 110 locally releases the network slice .

[0094] As indicated above, the network may also update the network slice specific deactivation timer and/or the PDU session specific deactivation using other types of PDU session commands (e.g., modify PDU session command, modify PDU session accept, etc.) In other embodiments, the network may update the network slice specific deactivation timer and/or the PDU session specific deactivation using CUC . Accordingly, in some embodiments the UE 110 and the network release the network slice and/or PDU session without any signaling occurring after the local release. In other embodiments, the UE 110 and/or the network may update the timer values before either of the timers expire. In further embodiments, the UE 110 and/or the network may update the network slice specific deactivation timer but release the PDU session specific deactivation timer.

[0095] In some embodiments, the UE 110 may also be operating various backoff timers (e.g., T3584, T3585, etc.) . In this type of scenario, if slice specific or data network specific backoff timers are activated, the UE 110 may fallback to the backoff timer handling and not activate PDU session establishment until the backoff timers expires even if the network slice specific deactivation timer or the PDU session specific deactivation timer expire. Thus, in some embodiments, the UE 110 and/or network may wait to perform the local release until both the backoff timer and the corresponding exemplary slice specific or PDU session specific timer expire.

[0096] Fig. 8 shows a signaling diagram 800 illustrating an example of an AMF change while the exemplary timers are running. The signaling diagram 800 will be described with regard to the network arrangements 100-200 of Figs. 1-2 and the UE 110 of Fig. 3.

[0097] The signaling diagram 800 includes the UE 110, a target AMF 802, a source AMF 804 and a NSQ 806. In this example is it assumed that the network slice specific deactivation timer is running and the PDU session specific deactivation timer is running .

[0098] In 810, the UE 110 selects a new cell which results in an AMF change. For example, the UE 110 may be connected to the source AMF 804 and the serving AMF is to be changed to the target AMF 802.

[0099] In 815, the UE 110 transmits a registration request to the target AMF 802. The registration request may include requested NSSAI .

[00100] In some embodiments, the target AMF 802 may provide new timer values for one or more of the requested network slices. The network may determine the new timer values based on AMF configuration, UE 110 subscription information and/or network load. In other embodiments, the target AMF 802 may not provide a new timer value and the UE 110 may continue to run the currently configured timers. Thus, the AMF 802 may determine the remaining timer for the slice and/or PDU session and then provide a new timer value or let the current timer continue to run. To make this determination the target AMF 802 may communicate with the NSQ 806 and/or the source AMF 804.

[00101] In 820, the target AMF 802 transmits a registration accept message to the UE 110. In this example, it is assumed that the target AMF 802 provides a new timer value for the network slice specific deactivation timer and a new tier value for the PDU session specific deactivation timer. Thus, the new timer values may be provided to the UE 110 in the registration accept message. If no new timer values are provided by the network, then the UE 110 continues to use the currently configured timer values.

[00102] In 825, the UE 110 starts the network slice specific deactivation timer and the PDU session specific deactivation timer using the new timer values provided by the target AMF 802.

[00103] Fig. 9 shows a signaling diagram 900 illustrating an example of a SME change while the exemplary timers are running. The signaling diagram 900 will be described with regard to the network arrangements 100-200 of Figs. 1-2 and the UE 110 of Fig. 3.

[00104] The signaling diagram 900 includes the UE 110, an AMF 902, a source SME 904, a target SME 906 and an NSQ 908. In this example is it assumed that the network slice specific deactivation timer is running and the PDU session specific deactivation timer is running.

[00105] In 910, the source SME 904 determines that SME reallocation is to be performed. For example, in session and service continuity (SSC) mode 1, 2, 3 for PDU sessions, respective actions are taken by the UE 110, SMEs 904-906 and the AMF 902. If the UE 110 has a PDU session that is operating in SSC mode 3, then the UE 110 may be triggered to initiate PDU session establishment towards the target SME 906. In other cases, the UE 110 PDU session may be transferred to the target SME 906 and the target SME 906 may initiate the PDU session modification command. An example of the UE 110 initiates PDU session to the target SME 906 is shown in 915a-925a. An example of the network initiated PDU session modification to the target SME 906 is shown in 915b-925b. [00106] In 915a, the UE transmits a PDU session establishment request to the target SME 906. In 920a, the target SME 906 may communicate with the NSQ 908 to determine new timer values for a specific PDU session. The new timer values may be based on SME configuration, UE subscription information and/or network load. In 925a, the target SME 906 transmits the PDU session establishment accept message to the UE 110. This message may include a new timer value for the network slice specific deactivation timer and/or the new timer value for the PDU session specific deactivation timer.

[00107] In 915b, the target SME 906 may communicate with the NSQ 908 to determine new timer values for a specific PDU session. The new timer values may be based on SME configuration, UE subscription information and/or network load. In 920b, the target SME 906 may transmit a PDU session modification command to the UE 110. The modification command may include a new timer value for the network slice specific deactivation timer and/or the new timer value for the PDU session specific deactivation timer. In 925b, the UE 110 may transmit a PDU session modification accept message to the target SME 906.

[00108] In response to either 915a-925a or 915b-925b, in 930, the UE 110 may start the network slice specific deactivation timer using the new value and/or the PDU session specific deactivation timer using the new value. In other embodiments, the network may not provide any new timer values and the UE 110 may continue to run the timers configured prior to changing to the target SME 906. [00109] In some embodiments, there may be some network slice which may only have mobile originating (MO) traffic. For instance, network slices configured for things such as, but not limited to, power meters, loT devices and background applications for mobile phones may only have MO traffic and not have any mobile terminating (MT) traffic. For this type of network slice, the UE 110 may delay registration of the corresponding network slice until a data transfer is to be performed. Since this type of information is typically non- critical it is ok to have a relatively small delay.

[00110] However, other network slices may be configured for both MO and MT traffic (e.g., video call, data call, voice call, voice over IP (VOIP) , gaming, streaming, etc.) . For these types of network slices, the UE 110 may register to the network slice and perform PDU session establishment during initial registration .

[00111] In further embodiments, there may be low latency network slices. For these type of network slices, the UE 110 may register to the network slice and perform PDU session establishment during initial registration. This may ensure that the bearers for these network slices are ready and available when the application corresponding application launches at the UE 110.

[00112] Those skilled in the art will understand that the above-described exemplary embodiments may be implemented in any suitable software or hardware configuration or combination thereof. An exemplary hardware platform for implementing the exemplary embodiments may include, for example, an Intel x86 based platform with compatible operating system, a Windows OS, a Mac platform and MAC OS , a mobile device having an operating system such as iOS , Android, etc . The exemplary embodiments of the above described method may be embodied as a program containing lines of code stored on a non-transitory computer readable storage medium that , when compiled, may be executed on a processor or microprocessor .

[ 00113 ] Although this application described various embodiments each having di f ferent features in various combinations , those skilled in the art will understand that any of the features of one embodiment may be combined with the features of the other embodiments in any manner not speci fically disclaimed or which is not functionally or logically inconsistent with the operation of the device or the stated functions of the disclosed embodiments .

[ 00114 ] It is well understood that the use of personally identi fiable information should follow privacy policies and practices that are generally recogni zed as meeting or exceeding industry or governmental requirements for maintaining the privacy of users . In particular, personally identi fiable information data should be managed and handled so as to minimi ze risks of unintentional or unauthori zed access or use , and the nature of authori zed use should be clearly indicated to users .

[ 00115 ] It will be apparent to those skilled in the art that various modi fications may be made in the present disclosure , without departing from the spirit or the scope of the disclosure . Thus , it is intended that the present disclosure cover modi fications and variations of this disclosure provided they come within the scope of the appended claims and their equivalent .

Claims

What is Claimed:

1. A processor of a user equipment (UE) configured to perform operations comprising: registering with an allowed network slice; receiving a timer duration value for a network slice specific deactivation timer corresponding to the allowed network slice; and operating the network slice specific deactivation timer, wherein the network slice specific deactivation timer is configured to trigger a local release of the allowed network slice at the UE .

2. The processor of claim 1, the operations further comprising : transmitting capability information to a network indicating that the UE is equipped with the network slice specific deactivation timer.

3. The processor of claim 1, wherein the UE does not run the network slice specific deactivation timer when at least one PDU session is configured within the allowed network slice.

4. The processor of claim 1, wherein when the network slice specific deactivation timer expires, the UE releases a packet data unit (PDU) session configured within the allowed network slice and adjusts the network slice specific deactivation timer based on a PDU session release command.

5. The processor of claim 1, the operations further comprising :

38 receiving a configuration update command (CUC) to adjust the timer duration value for the network slice specific deactivation timer.

6. The processor of claim 1, wherein the local release of the network slice is configured to occur after a backoff timer expires .

7. The processor of claim 6, wherein the backoff timer is T3584 or T3585.

8. The processor of claim 1, the operations further comprising : receiving a packet data unit session (PDU) session release command for a PDU session configured within the allowed network slice, wherein the PDU session release command indicates an adjustment to the network slice specific deactivation timer.

9. The processor of claim 1, the operations further comprising : receiving a modify PDU session command to modify the network slice specific deactivation timer.

10. The processor of claim 1, the operations further comprising : receiving a modify PDU session accept to modify the network slice specific deactivation timer.

11. The processor of claim 1, the operations further comprising : establishing a packet data unit (PDU) session within the allowed network slice, wherein the network slice specific

39 deactivation timer is configured to run when the PDU session is not configured with a data radio bearer (DRB) or configured with a suspended DRB.

12. The processor of claim 11, the operations further comprising : when the network slice specific deactivation timer expires, performing a local release of the PDU session and the allowed network slice.

13. The processor of claim 1, the operations further comprising : receiving a timer duration value for a packet data unit (PDU) session specific deactivation timer corresponding to a PDU session configured within the allowed network slice; and operating the PDU session specific deactivation timer, wherein the PDU session specific deactivation timer is configured to trigger a local release of the PDU session.

14. The processor of claim 13, wherein the UE is configured to initiate the PDU session specific deactivation timer when the PDU session is not configured with a data radio bearer (DRB) or the PDU session is configured with a suspended DRB.

15. The processor of claim 14, wherein the UE is configured to stop the PDU session specific deactivation timer when the PDU session is configured with the DRB.

17. The processor of claim 11, the operations further comprising :

40 receiving a new PDU session speci fic deactivation timer value from a target session management function ( SMF) in a PDU session modi fication command .

18 . The processor of claim 11 , the operations further comprising : receiving a new PDU session speci fic deactivation timer value from a target session management function ( SMF) in a PDU session establishment accept .

19 . The processor of claim 1 , the operations further comprising : receiving a new network slice speci fic deactivation timer value from a target access and mobility management function (AMF) .

20 . A network function configured to perform operations comprising : transmitting a registration accept message comprising an allowed network slice to a user equipment (UE ) ; transmitting a timer duration value for a network slice speci fic deactivation timer corresponding to the allowed network slice ; and operating the network slice speci fic deactivation timer on the network side , wherein the network slice speci fic deactivation timer is configured to trigger a local release of the allowed network slice on the network side .

21 . The network function of claim 20 , wherein the network function does not run the network slice speci fic deactivation timer when at least one PDU session is configured within the allowed network slice for the UE .

22. The network function of claim 20, the operations further comprising : transmitting a configuration update command (CUC) to adjust the timer duration value for the network slice specific deactivation timer at the UE .

23. The network function of claim 20, the operations further comprising : when the network slice specific deactivation timer expires, performing a local release of a packet data unit (PDU) session configured within the allowed network slice and the allowed network slice on the network side.

24. A network function configured to perform operations comprising : receiving a packet data unit (PDU) session establishment request from a user equipment (UE) ; transmitting a timer duration value for a PDU session specific deactivation timer to the UE; and operating the PDU session specific deactivation timer on the network side, wherein the PDU session specific deactivation timer is configured to trigger a local release of the PDU session on the network side.

25. The network function of claim 24, wherein the network function is configured to initiate the PDU session specific deactivation timer when the PDU session is not configured with a data radio bearer (DRB) or the PDU session is configured with a suspended DRB.

26. The network function of claim 25, wherein the network function is configured to stop the PDU session specific deactivation timer when the PDU session is configured with the DRB.

43