UE and PDU session counting for network slice remapping / replacement

Abstract

A method, comprising: receiving, by a NSACF, a first message 305 comprising at least one of an update indication identifying a first and a second network slice or an update indication identifying that

Description

[0002] Network slicing is a feature of a fifth generation (5G) network to support different services using the same underlying mobile network infrastructure, described, for example in third generation partnership project (3GPP) TS 38.300. Network slices may differ either in their service requirements (e.g., ultra-reliable low latency communication (URLLC) and enhanced mobile broadband (eMBB)).

[0003] A network slice is uniquely identified via the single-network slice selection assistance information (S-NSSAI). Current 3GPP specifications allow a user equipment (UE) to be simultaneously connected and served by, for example, up to eight slices corresponding to eight network slices (eight S-NSSAIs) as per 3GPP TS 38.300. On other hand, each cell may support tens, or even hundreds, of slices (e.g., a tracking area (TA)) may support up to 1024 network slices as described in 3GPP TS 38.423. SUMMARY

[0004] In an aspect of the present disclosure, a method includes receiving, by a first apparatus, a first message from a second apparatus, wherein the first message comprises at least one of an update indication identifying a first network slice and a second network slice and an indication identifying that the first network slice is replaced with the second network slice, wherein the first apparatus is configured for the first network slice and the second network slice wherein the first network slice includes a first quota and the second network slice includes a second quota and a single-network slice selection assistance information (S-NSSAI) policy to be used in case of a network slice replacement associated with serving a user equipment (UE) from the first network slice to serving the UE from the second network slice. Based on the S-NSSAI policy, the first apparatus performs a first update to at least one of the first quota of the first network slice or the second quota of the second network slice. The first apparatus receives a second message from the second apparatus, wherein the second message comprises an indication that communication with the UE is ceased and at least one of an indication indicating the first network slice or the second network slice, and based on the S-NSSAI policy, performs a second update to at least one of the first quota of the first network slice or the second quota of the second network slice.

[0005] In an aspect of the method, the first quota includes an indication of a number of users allowed access to the first network slice and the second quota includes an indication of a number of users allowed access to the second network slice.

[0006] In an aspect of the method, the performing the first update to the second quota of the second network slice includes adding to a counter of users of the second network slice.

[0007] In an aspect of the method, the second quota includes an indication of a number of protocol data unit (PDU) sessions allowed access to the second network slice.

[0008] In an aspect of the method, the performing the first update to the second quota of the second network slice includes adding to a counter of PDU sessions of the second network slice.

[0009] In an aspect of the method, the performing the second update to the first quota of the first network slice includes subtracting from a counter of users of the first network slice.

[0010] In an aspect of the method, the performing the second update to the first quota of the first network slice includes subtracting from a counter of protocol data unit (PDU) sessions of the first network slice.

[0011] In an aspect of the method, the performing the first update to the second quota of the second network slice includes maintaining a counter for the second quota at a same value.

[0012] In an aspect of the method, the performing the first update to the first quota of the first network slice includes maintaining a counter for the first quota at a same value.

[0013] In an aspect of the method, the first apparatus includes a network slice admission control function (NSACF).

[0014] In an aspect of the method, the NSACF receives the first message from an access and mobility management function (AMF).

[0015] In an aspect of the present disclosure, a method includes serving, by a first apparatus, a user equipment (UE) associated with a first network slice. Upon determination of a network slice replacement of the first network slice with a second network slice, the first apparatus transmits to at least one of a second apparatus associated with the first slice, a first message, wherein the first message comprises at least one of an update indication identifying the first network slice and the second network slice or an indication that the first network slice is replaced with the second network slice, and upon determination of the UE deregistering from the network, transmits a second message to at least the second apparatus, wherein the second message comprises an indication that the UE communication is ceased and at least one of an indication indicating the first network slice or the second network slice.

[0016] In an aspect of the method, the second apparatus is a first network slice admission control function (NSACF).

[0017] In an aspect of the method, the second apparatus is associated with the first network slice and the second network slice.

[0018] In an aspect of the method, the method further includes transmitting, by the first apparatus, the first message to a third apparatus associated with the second network slice.

[0019] In an aspect of the method, the third apparatus is a second NSACF.

[0020] In an aspect of the method, the first apparatus is an access and mobility management function (AMF) or a session management function (SMF).

[0021] In an aspect of the present disclosure, an apparatus includes at least one processor, and at least one memory storing instructions which, when executed by the at least one processor, cause the apparatus at least to perform any of the foregoing methods.

[0022] In an aspect of the present disclosure, a processor-readable medium storing instructions which, when executed by at least one processor of an apparatus, cause the apparatus at least to perform any of the foregoing methods.

[0023] According to some aspects, there is provided the subject matter of the independent claims. Some further aspects are defined in the dependent claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Some example embodiments will now be described with reference to the accompanying drawings.

[0025] FIG. 1 is a diagram of an example embodiment of wireless networking between a network system and a user equipment (UE), according to one illustrated aspect of the disclosure;

[0026] FIG. 2 is a diagram of example components of a network system, according to one illustrated aspect of the disclosure;

[0027] FIG. 3 is a diagram of an example embodiment of signals and operations among a UE, an AMF, and an NSACF, according to one illustrated aspect of the disclosure;

[0028] FIG. 4 is a diagram of an example embodiment of signals and operations among a UE, an AMF, and multiple NSACFs, according to one illustrated aspect of the disclosure;

[0029] FIG. 5 is a diagram of an example embodiment of signals and operations among a UE, multiple AMFs, and multiple NSACFs, according to one illustrated aspect of the disclosure;

[0030] FIG. 6 is a diagram of an example embodiment of signals and operations among a UE, an AMF, and an NSACF, according to one illustrated aspect of the disclosure;

[0031] FIG. 7 is a diagram of an example embodiment of signals and operations among a UE, an AMF, and multiple NSACFs, according to one illustrated aspect of the disclosure;

[0032] FIG. 8 is a diagram of an example embodiment of signals and operations among a UE, multiple AMFs, and multiple NSACFs, according to one illustrated aspect of the disclosure;

[0033] FIG. 9 is a diagram of an example embodiment of signals and operations among a UE, an AMF, SMF, and an NSACF, according to one illustrated aspect of the disclosure; and

[0034] FIG. 10 is a diagram of an example embodiment of components of a UE or of a network apparatus, according to one illustrated aspect of the present disclosure. DETAILED DESCRIPTION

[0035] In the following description, certain specific details are set forth in order to provide a thorough understanding of disclosed aspects. However, one skilled m the relevant art will recognize that aspects may be practiced without one or more of these specific details or with other methods, components, materials, etc. In other instances, well-known structures associated with transmitters, receivers, or transceivers have not been shown or described in detail to avoid unnecessarily obscuring descriptions of the aspects.

[0036] Reference throughout this specification to “one aspect” or “an aspect” means that a particular feature, structure, or characteristic described in connection with the aspect is included in at least one aspect. Thus, the appearances of the phrases “in one aspect” or “in an aspect” in various places throughout this specification are not necessarily all referring to the same aspect. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more aspects.

[0037] Embodiments described in the present disclosure may be implemented in wireless networking apparatuses, such as, without limitation, apparatuses utilizing Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile communications (GSM, 2G), GSM EDGE radio access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, 3G) based on basic wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), Long Term Evolution (LTE), LTE-Advanced, enhanced LTE (eLTE), 5G New Radio (5G NR), 5G Advance, 6G (and beyond) and 802.1 lax (Wi-Fi 6), among other wireless networking systems. The term ‘eLTE’ here denotes the LTE evolution that connects to a 5G core. LTE is also known as evolved UMTS terrestrial radio access (EUTRA) or as evolved UMTS terrestrial radio access network (EUTRAN).

[0038] The present disclosure may use the term “serving network device” to refer to a network node or network device (or a portion thereof) that services a UE. As used herein, the terms “transmit to,” “receive from,” and “cooperate with,” (and their variations) include communications that may or may not involve communications through one or more intermediate devices or nodes. The term “acquire” (and its variations) includes acquiring in the first instance or reacquiring after the first instance. The term “connection” may mean a physical connection or a logical connection.

[0039] The present disclosure uses 5G NR as an example of a wireless network and may use smartphones and / or extended reality headsets as an example of UEs. It is intended and shall be understood that such examples are merely illustrative, and the present disclosure is applicable to other wireless networks and user equipment.

[0040] FIG. 1 is a diagram depicting an example of wireless networking between a network system 100 and a user equipment (UE) 150. The network system 100 may include one or more network nodes 120, one or more seivers 110, and / or one or more network equipment 130 (e.g., test equipment). The network nodes 120 will be described in more detail below. As used herein, the term “network apparatus” may refer to any component of the network system 100, such as the server 110, the network node 120, the network equipment 130, any component(s) of the foregoing, and / or any other component^) of the network system 100. Examples of network apparatuses include, without limitation, apparatuses implementing aspects of 5G NR, among others. The present disclosure describes embodiments related to 5G NR and embodiments that involve aspects defined by 3rd Generation Partnership Project (3GPP). However, it is contemplated that embodiments relating to other wireless networking technologies are encompassed within the scope of the present disclosure.

[0041] The following description provides further details of examples of network nodes. In a 5G NR network, a gNodeB (also known as gNB) may include, e.g., a node that provides new radio (NR) user plane and control plane protocol terminations towards the UE and that is connected via an NG interface to the 5G core (5GC), e.g., according to 3GPP TS 38.300 section 3.2, which is hereby incorporated by reference herein.

[0042] A gNB supports various protocol layers, e.g., Layer 1 (LI) - physical layer, Layer 2 (L2), and Layer 3 (L3).

[0043] The layer 2 (L2) of NR is split into the following sublayers: Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP) and Sendee Data Adaptation Protocol (SDAP), where, e.g.: o The physical layer offers to the MAC sublayer transport channels; o The MAC sublayer offers to the RLC sublayer logical channels; o The RLC sublayer offers to the PDCP sublayer RLC channels; o The PDCP sublayer offers to the SDAP sublayer radio bearers; o The SDAP sublayer offers to 5GC quality of service (QoS) flows; o Control channels include broadcast control channel (BCCH) and physical control channel (PCCH).

[0044] Layer 3 (L3) includes, e.g., radio resource control (RRC), e.g., according to 3GPP TS 38.300 section 6, which is hereby incorporated by reference herein.

[0045] A gNB central unit (gNB-CU) includes, e.g., a logical node hosting, e.g., radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB or RRC and PDCP protocols of the en-gNB, that controls the operation of one or more gNB distributed units (gNB-DUs). The gNB-CU terminates the Fl interface connected with the gNB-DU. A gNB-CU may also be referred to herein as a CU, a central unit, a centralized unit, or a control unit.

[0046] A gNB Distributed Unit (gNB-DU) includes, e.g., a logical node hosting, e.g., radio link control (RLC), media access control (MAC), and physical (PHY) layers of the gNB or en-gNB, and its operation is partly controlled by the gNB-CU. One gNB-DU supports one or multiple cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the Fl interface connected with the gNB-CU. A gNB-DU may also be referred to herein as DU or a distributed unit.

[0047] As used herein, the term “network node” may refer to any of a gNB, a gNB-CU, or a gNB-DU, or any combination of them. A RAN (radio access network) node or network node such as, e.g., a gNB, gNB-CU, or gNB-DU, or parts thereof, may be implemented using, e.g., an apparatus with at least one processor and / or at least one memory with processor-readable instructions (“program”) configured to support and / or provision and / or process CU and / or DU related functionality and / or features, and / or at least one protocol (sub-)layer of a RAN (radio access network), e.g., layer 2 and / or layer 3. Different functional splits between the central and distributed unit are possible. An example of such an apparatus and components will be described in connection with FIG. 10 below.

[0048] The gNB-CU and gNB-DU parts may, e.g., be co-located or physically separated. The gNB-DU may even be split further, e.g., into two parts, e.g., one including processing equipment and one including an antenna. A central unit (CU) may also be called baseband unit / radio equipment controller / cloud-RAN / virtual-RAN (BBU / REC / C-RAN / V-RAN), open-RAN (O-RAN), or part thereof. A distributed unit (DU) may also be called remote radio head / remote radio unit / radio equipment / radio unit (RRIURRU / RE / RU), or part thereof. Hereinafter, in various example embodiments of the present disclosure, a network node, which supports at least one of central unit functionality or a layer 3 protocol of a radio access network, may be, e.g., a gNB-CU. Similarly, a network node, wduch supports at least one of distributed unit functionality or a layer 2 protocol of the radio access network, may be, e.g., a gNB-DU.

[0049] A gNB-CU may support one or multiple gNB-DUs. A gNB-DU may support one or multiple cells and, thus, could support a serving cell for a user equipment (UE) or support a candidate cell for handover, dual connectivity, and / or carrier aggregation, among other procedures.

[0050] The user equipment (UE) 150 may be or include a wireless or mobile device, an apparatus with a radio interface to interact with a RAN (radio access network), a smartphone, an in-vehicle apparatus, an loT device, or a M2M device, among other types of user equipment. Such UE 150 may include: at least one processor; and at least one memory including program code; where the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform certain operations, such as, e.g., RRC connection to the RAN. An example of components of a UE will be described in connection with FIG. 10. In embodiments, the UE 150 may be configured to generate a message (e.g., including a cell ID) to be transmitted via radio towards a RAN (e.g., to reach and communicate with a serving cell). In embodiments, the UE 150 may generate and transmit and receive RRC messages containing one or more RRC PDUs (packet data units). Persons skilled in the art will understand RRC protocol as well as other procedures a UE may perform.

[0051] With continuing reference to FIG. 1, in the example of a 5G NR network, the network system 100 provides one or more cells, which define a coverage area of the network system 100. As described above, the network system 100 may include a gNB of a 5G NR network or may include any other apparatus configured to control radio communication and manage radio resources within a cell. As used herein, the term “resource” may refer to radio resources, such as a resource block (RB), a physical resource block (PRB), a radio frame, a subframe, a time slot, a sub-band, a frequency region, a sub-carrier, a beam, etc. In embodiments, the network node 120 may be called a base station.

[0052] FIG. 1 provides an example and is merely illustrative of a network system 100 and a UE 150. Persons skilled in the art will understand that the network system 100 includes components not illustrated m FIG. 1 and will understand that other user equipment may be in communication with the network system 100.

[0053] FIG. 2 is a block diagram of example components of the network system 100 of FIG. 1. A 5G NR network may be described as an example of the network system 100, and it is intended that aspects of the following description shall be applicable to other types of network systems, as well. The network system may operate in accordance with the signals and connections shown m FIG. 1 such that the UE 150 is in communication with the network system 100 through the radio access network 225. Additionally, the network system may be divided into user plane components and functions and control plane components and functions, as shown and described herein. Unless indicated otherwise, the terms “component”, “function”, and “sendee” may be used interchangeably herein, and they may refer to and be implemented by instructions executed by one or more processors.

[0054] Example functions of the components are described below. The example functions are merely illustrative, and it shall be understood that additional operations and functions may be performed by the components described herein. Additionally, the connections between components may be virtual connections over service-based interfaces such that any component may communicate with any other component. In this manner, any component may act as a service “producer,” for any other component that is a service “consumer,” to provide services for network functions.

[0055] For example, a core network 210 is described in the control plane of the network system. The core network 210 may include an authentication server function (AUSF) 211, an access and mobility function (AMF) 212, and a session management function (SMF) 213. The core network 210 may also include a network slice selection function (NSSF) 214, a network exposure function (NEF) 215, a network repository function (NRF) 216, and a unified data management function (UDM) 217, which may include a uniform data repository (UDR) 224.

[0056] Additional components and functions of the core network 210 may include an application function 218, policy control function (PCF) 219, network data analytics function (NWDAF) 220, analytics data repository function (ADRF) 221, management data analytics function (MDAF) 222, operations and management function (0AM) 223, and network slice admission control function (NSACF) 228.

[0057] The user plane includes the UE 150, a radio access network (RAN) 225, a user plane function (UPF) 226, and a data network (DN) 227. The RAN 225 may include one or more components described in connection with FIG. 1, such as one or more network nodes. However, the RAN 225 may not be limited to such components. The UPF 226 provides connection for data being transmitted over the RAN 225. The DN 226 identifies services from service providers, Internet access, and third party services, for example.

[0058] The AMF 212 processes connection and mobility tasks. The AUSF 211 receives authentication requests from the AMF 212 and interacts with UDM 217 to authenticate and validate network responses for determination of successful authentication. The SMF 213 conducts packet data unit (PDU) session management, as well as manages session context with the UPF 226.

[0059] The NSSF 214 may select a network slicing instance (NSI) and determine the allowed network slice selection assistance information (NSSAI). This selection and determination is utilized to set the AMF 212 to provide service to the LIE 150. The NEF 215 secures access to network services for third parties to create specialized network services. The NRF 216 acts as a repository to store network functions to allow the functions to register with and discover each other.

[0060] The UDM 217 generates authentication vectors for use by the AUSF 211 and ADM 212 and provides user identification handling. The UDM 217 may be connected to the UDR 224 which stores data associated with authentication, applications, or the like. The AF 218 provides application services to a user (e.g., streaming services, etc.). The PCF 219 provides policy control functionality. For example, the PCF 219 may assist in network slicing and mobility management, as well as provide quality of service (QoS) and charging functionality.

[0061] The NWDAF 220 collects data (e.g., from the UE 150 and the network system) to perform network analytics and provide insight to functions that utilize the analytics in the providing of services. The ADRF 221 allows the storage, retrieval, and removal of data and analytics by consumers. The MDAF 222 provides additional data analytics services for network functions. The 0AM 223 provides provisioning and management processing functions to manage elements in or connected to the network (e.g., UE 150, network nodes, etc.). The NSACF 228 enables monitoring at a slice level, and controls the number of registered UEs per single-network slice selection assistance information (S-NSSAI) and / or the number of PDU sessions.

[0062] FIG. 2 is merely an example of components of a network system, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the network system may include other components not illustrated in FIG. 2. In embodiments, the network system may not include every component illustrated in FIG. 2. In embodiments, the components and connections may be implemented with different connections than those illustrated m FIG. 2. Such and other embodiments are contemplated to be within the scope of the present disclosure.

[0063] As mentioned above, network slicing is a feature of a fifth generation (5G) network to support different services using the same underlying mobile network infrastructure, described, for example in third generation partnership project (3GPP) TS 38.300. Network slices may differ either in their service requirements (e.g., ultra-reliable low latency communication (URLLC) and enhanced mobile broadband (eMBB)).

[0064] A network slice is uniquely identified via the S-NSSAI. Current 3GPP specifications allow a user equipment (UE) to be simultaneously connected and served by, for example, up to eight slices corresponding to eight network slices (eight S-NSSAIs) per 3GPP TS 38.300. On other hand, each cell may support tens, or even hundreds, of slices (e.g., a tracking area (TA) may support up to 1024 network slices as described in 3GPP TS 38.423.

[0065] As mentioned above, to enable monitoring at a slice level, the NSACF network function in the core network controls the number of registered UEs per S-NSSAI and / or the number of PDU sessions that can be generated if the S-NSSAI is subject to admission control (e.g., as specified in 3GPP TS 23.501). In various embodiments, the NSACF may be configured with a maximum number of UEs and / or maximum number of PDU session allowed per S-NSSAI subject to admission control (NSAC). Die NSACF may be configured in various embodiments with details with respect to the applicable access types for the S-NSSAI (e.g., 3GPP access type or non-3GPP or both).

[0066] To facilitate further slice monitoring, in various embodiments, the NSACF may enable an event-based network slice status (e.g., number of registered UEs) notification and report it to consumer network functions (NFs). In various embodiments, the NSACF may be responsible for one or more S-NSSAIs and there may be one or multiple NSACFs deployed in the network. The phrase “number of UEs” and “number of registered UEs” may be used interchangeably herein.

[0067] In various embodiments, the NSACFs record the maximum number of registered UEs that can access an S-NSSAI that is subject to NSAC. When an event that causes the number of UEs of an S-NSSAI to increase, for instance the AMF may trigger a UE registration procedure (e.g., per clause 4.2.2.2.2 of 3GPP TS 23.502), and the NSACF confirms whether the UE ID exists in the list of registered UEs. If it does not, the NSACF checks if the maximum number of UEs for that S-NSSAI is reached. In case of such an occurrence, the NSACF applies admission control and may reject the UE registration in case that the maximum number of registered UEs for that S-NSSAI has been reached.

[0068] In various embodiments, the NSACF keeps track of the current number of PDU sessions existing per S-NSSAI that is subject to NSAC. In various embodiments, upon an event that triggers the number of PDU sessions of a UE within a network slice to increase (e.g., SMF that triggers PDU session establishment as per clause 4.3.2 of 3GPP TS 23.502 occurs), then the NSACF checks if the maximum number of PDU sessions for the particular S-NSSAI has been reached. If that is the case, the NSACF applies admission control. In that case the NSACF may reject the PDU session establishment in case that the maximum number of PDU sessions for that S-NSSAI has been reached.

[0069] In some embodiments, slices may either go into maintenance or have congestion in the core network side. In such cases, an alternative slice may be provided to the UE for the UE to utilize while the original slice is under maintenance or under congestion. In various embodiments, such an alternative slice may be provided by AMF, either via prior configuration by OAM or via a decision after contacting with other NFs such as the PCF or NSSF. The switch from original slice to alternative slice may be referred to as “re-mapping” or as replacement (and the alternative slice may be called “re-mapped or replaced slice”). Furthermore, slice remapping and slice replacement may be used interchangeably.

[0070] When core network slice remapping occurs, the NSACF may not be aware of the remapped slice, (e.g., the alternative slice), for which the AMF has chosen to replace the original slice. Without this information, the NS ACF cannot maintain accurate counting of the UEs / PDU sessions of the original slice, since from the AMF’s / SMF’s perspective the UEs / PDU sessions of the original slice now belong to the alternative slice. Therefore, the NSACF may continue increasing and decreasing the UE / PDU session count of the original slice that is remapped to the alternative slice by utilizing the available quota of the alternative slice. However, the quota of the alternative slice has been set to only account for UEs / PDU sessions which natively belong to the alternative slice, not for UEs / PDU sessions which have been re-mapped to the alternative slice.

[0071] Furthermore, in various embodiments, the alternative slice may not be subject to NS AC. In that case, the original slice which is subject to NS AC now has unlimited quota due to using the alternative slice that is quota free. This may cause non-compliance with previously agreed service level agreements (SLAs) between operators and network slice tenants.

[0072] Accordingly, in various embodiments, inaccurate PDU session or UE counting at the NSACF when slice remapping occurs may lead to misuse of resources of the alternative slice (and potentially unnecessary rejection of UEs that are using the alternative slice as their original slice) from UEs of the original slice remapped to this slice, as those resources of the alternative slice would otherwise be used by only the UEs that have native PDU sessions established with the alternative slice, (e.g., PDU sessions of the alternative slice that were not remapped from another original slice).

[0073] In various embodiments, inaccurate PDU session or UE counting at the NSACF when slice remapping occurs may lead to inaccurate slice quota application for the original slice. Slice quota, is potentially a service level agreement (SLA) parameter between the slice provider and the slice tenant, therefore, the slice provider (e.g., network operator) needs to ensure that it abides by these limits all the time, unless some exceptions are also agreed with the slice tenant.

[0074] As used herein, a communication with a radio access network (RAN) may refer to and mean a communication with a portion of a RAN, such as with a network node (e.g., a DU and / or a CU), or another portion of a RAN. As used herein, a communication with a core network may refer to and mean a communication with one or more services / applications of the core network, such as AMF or another service of a core network.

[0075] As described herein with regard to FIGS. 3-9, in various embodiments, components shown may correlate to the components described in FIGS. 1 and 2 above.

[0076] In accordance with the brief description, FIG. 3 is a diagram of an example embodiment of signals and operations among a UE, an AMF, and an NSACF, according to one illustrated aspect of the disclosure. As shown in FIG. 3, NSACF1 may be responsible and in control of both network slice 1 and network slice 2.

[0077] At operation 301, the UE joins the network and attempts to register at the AMF with a first network slice (slice 1) which is subject to NSAC.

[0078] At operation 302, the AMF transmits a request to the NSACF (NSACF1) to increase the counter of UEs for slice 1 and the NSACF receives the request to increase the counter of UEs for slice 1.

[0079] In case that at NSACF 1 the quota for the number of registered UEs for slice 1 has not been reached yet as in this example, then AMF accepts the UE registration and enters slice 1 in the allowed list of network slices. In various embodiments, slice 1 is the slice allowed to the UE.

[0080] At operation 303, slice replacement occurs (e.g., due to network congestion or maintenance of the slice 1). In various embodiments, slice 1 is replaced with slice 2. At operation 304, the NSACF is configured with a policy for slice remapping, for example, of the original slice 1. In various embodiments, the NSACF policy may be to use the original slice NSAC quotas for slice 1, even if slice 1 is remapped to an alternative slice. In various embodiments, the policy could be usage of the alternative slice’s quota or to not apply any quota at all.

[0081] At operation 305, the AMF transmits a message to update the UE counter at the NSACF to the NSACF and the NSACF receives the message to update the UE counter at the NSACF. In various embodiments, the message to update the UE counter at the NSACF may indicate that slice 1 is replaced with slice 2. In various embodiments, such indication may be effected via sending both slice 1 and slice 2 as the identifier (ID).

[0082] At operation 306, the NSACF implements the policy configured. In various example embodiments, the policy may include that the NSACF does not update the counter as the UE is already registered with slice 1 (e.g., the slice 1 counter was increased already) and the policy indicates usage of original slice’s quotas. In various embodiments, the NSACF maintains the counter at a same value the counter currently includes against any quota.

[0083] At operation 307, the UE deregisters from the network (e.g., possibly while being connected to slice 2 or slice 1). Upon the deregistration from the network, at operation 308, the AMF transmits a message to update the UE counter at the NSACF to the NSACF and the NSACF receives the message to update the UE counter at the NSACF. In various embodiments, the message may indicate that slice 1 is replaced with slice 2, and such indication could be via sending both slice 1 and slice 2 as the ID. The indication informs that the UE has deregistered, or simply deregistering of the UE from the slice(s). In various embodiments, deregistration does not present any additional change (e.g., a conventional decrease command is sent), as the NSACF may be already aware of the situation of the UE from registration.

[0084] Upon receipt of the message at operation 308, at operation 309, the NSACF implements the policy configured. In various embodiments, based upon the example described above, the NSACF may decrease only the counter of slice 1, as the UE was counted only for slice 1.

[0085] The operations of FIG. 3 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include other operations not illustrated in FIG. 3. In embodiments, the operations may not include every operation illustrated in FIG. 3. In embodiments, the operations may be implemented in a different order than that illustrated in FIG. 3. Such and other embodiments are contemplated to be within the scope of the present disclosure. Persons of skill in the art will appreciate that, although various example components are described as perform various functions, other components may perform those functions described in FIG. 3.

[0086] FIG. 4 is a diagram of an example embodiment of signals and operations among a UE, an AMF, and multiple NSACFs, according to one illustrated aspect of the disclosure. As shown in FIG. 4, NSACF1 may be responsible of control of slice 1 and NSACF2 may be responsible of control of slice 2.

[0087] At operation 401, the UE joins the network and attempts to register at the AMF with a first slice (slice 1).

[0088] At operation 402, the AMF transmits a request to the NSACF (NSACF1) to increase the counter of UEs for slice 1 and the NSACF 1 receives the request to increase the counter of UEs for slice 1.

[0089] In case that at NSACF 1 the quota for the number of registered UEs for slice 1 has not been reached yet as in this example, then AMF accepts the UE registration and enters slice 1 in the allowed list of network slices. In various embodiments, slice 1 is the slice allowed to the UE.

[0090] At operation 403, slice replacement occurs (e.g., due to network congestion or maintenance of slice 1). In various embodiments, slice 1 is replaced with slice 2.

[0091] At operation 404, NSACF 1 is configured with a policy for slice remapping, for example, of the original slice. In various embodiments, the NSACF policy may be to use the original slice NSAC quotas for slice 1, even if slice 1 is remapped to an alternative slice. In various embodiments, the policy could be usage of the alternative slice’s NSAC quota or to not apply any quota at all. In various embodiments, the NSAC quota is the UE quota or PDU session quota for admission control at the core network.

[0092] At operation 405, NSACF2 is configured similarly to NSACF1 at operation 404.

[0093] At operation 406, the AMF contacts both NSACF1 and NSACF2 controlling the respective slices. In various embodiments, at operation 407, the AMF transmits a message to update the UE counter at the NSACF to the NSACF1 and the NSACF1 receives the message to update the UE counter at the NSACF. In various embodiments, the message to update the UE counter at the NSACF may indicate that slice 1 is replaced with slice 2. In various embodiments, such indication may be effected via sending both slice 1 and slice 2 as the identifier (ID).

[0094] In various embodiments, at operation 408, the AMF transmits a message to update the UE counter at the NSACF to the NSACF2 and the NSACF2 receives the message to update the UE counter at the NSACF. In various embodiments, the message to update the UE counter at the NSACF may indicate that slice 1 is replaced with slice 2. In various embodiments, such indication may be effected via sending both slice 1 and slice 2 as the identifier (ID).

[0095] At operation 409, the NSACF1 implements the policy configured. In various example embodiments, the policy may include that the NSACF 1 does not update the counter as the UE is already registered with slice 1 (e.g., the slice 1 counter was increased already) and the policy indicates usage of original slice’s quotas.

[0096] At operation 410, the NSACF2 implements the policy configured. In various example embodiments, the policy may include that the NSACF2 does not update the counter as the UE is already registered with slice 1 and the policy indicates usage of original slice’s quotas.

[0097] At operation 411, the UE deregisters from the network (e.g., possibly while being connected to slice 2 or slice 1). For example, as depicted in FIG. 4, the UE may deregister while being connected with slice 2. Upon the deregistration from the network, at operation 412, the AMF contacts both NSACF1 and NSACF2 controlling the respective slices. In various embodiments, at operation 413, the AMF transmits a message to update the UE counter at the NSACF to the NSACF1 and the NSACF1 receives the message to update the UE counter at the NSACF. In various embodiments, the message may indicate that slice 1 is replaced with slice 2, and such indication could be via sending both slice 1 and slice 2 as the ID. The indication informs that the UE has deregistered, or simply deregistering of the UE from the slice(s). In various embodiments, deregistration does not present any additional change (e.g., a conventional decrease command is sent), as the NSACF may be already aware of the situation of the UE from registration.

[0098] In various embodiments, at operation 414, the AMF transmits a message to update the UE counter at the NSACF to the NSACF2 and the NSACF2 receives the message to update the UE counter at the NSACF. In various embodiments, the message may indicate that slice 1 is replaced with slice 2, and such indication could be via sending both slice 1 and slice 2 as the ID. The indication informs that the UE has deregistered, or simply deregistering of the UE from the slice(s). In various embodiments, deregistration does not present any additional change (e.g., a conventional decrease command is sent), as the NSACF may be already aware of the situation of the UE from registration.

[0099] Upon receipt of the message at operation 413, at operation 415, the NSACF1 implements the policy configured. In various embodiments, based upon the example described above, the NSACF1 may decrease only the counter of slice 1, as the UE was counted only for slice 1.

[00100] Upon receipt of the message at operation 414, at operation 416, the NSACF2 implements the policy configured. In various embodiments, based upon the example described above, the NSACF2 does not update the counter as the UE was counted only for slice 1 (e.g., the original slice).

[00101] The operations of FIG. 4 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include other operations not illustrated in FIG. 4. In embodiments, the operations may not include every operation illustrated in FIG. 4. In embodiments, the operations may be implemented in a different order than that illustrated in FIG. 4. Such and other embodiments are contemplated to be within the scope of the present disclosure. Persons of skill in the art will appreciate that, although various example components are described as perform various functions, other components may perform those functions described.

[00102] FIG. 5 is a diagram of an example embodiment of signals and operations among a UE, multiple AMFs, and multiple NSACFs, according to one illustrated aspect of the disclosure. In various embodiments, an inter AMF handover may be performed between AMF1 and AMF2. As shown in FIG. 5, NSACF1 may be responsible and in control of slice 1 and NSACF2 may be responsible and in control of slice 2.

[00103] At operation 501, the UE joins the network and attempts to register at the A MFI with a first slice (slice 1).

[00104] At operation 502, the AMF1 transmits a request to the NSACF (NSACF1) to increase the counter of UEs for slice 1 and the NSACF 1 receives the request to increase the counter of UEs for slice 1.

[00105] In case that at NSACF 1 the quota for the number of registered UEs for slice 1 has not been reached yet as in this example, then AMF accepts the UE registration and enters slice 1 in the allowed list of network slices. In various embodiments, slice 1 is the slice allowed to the UE.

[00106] At operation 503, slice replacement occurs (e.g., due to network congestion or maintenance of the slice 1). In various embodiments, slice 1 is replaced with slice 2.

[00107] At operation 504, NSACF1 and NSACF2 are configured with a policy for slice remapping, for example, of the original slice. In various embodiments, the NSACF policy may be to use the original slice quotas for slice 1, even if slice 1 is mapped to an alternative slice. In various embodiments, the policy could be usage of the alternative slice’s quota or to not apply any quota at all.

[00108] At operation 505, the AMF1 contacts both NSACF1 and NSACF2 controlling the respective slices. In various embodiments, at operation 506, the AMF1 transmits a message to update the UE counter at the NSACF to the NSACF1 and the NSACF1 receives the message to update the UE counter at the NSACF. In various embodiments, the message to update the UE counter at the NSACF may indicate that slice 1 is replaced with slice 2. In various embodiments, such indication may be effected via sending both slice 1 and slice 2 as the identifier (ID).

[00109] At operation 507, the NSACF1 implements the policy configured. In various example embodiments, the policy may include that the NSACF 1 does not update the counter as the UE is already registered with slice 1 (e.g., the slice 1 counter was increased already) and the policy indicates usage of original slice’s quotas.

[00110] In various embodiments, at operation 508 the AMF1 transmits a message to update the UE counter at the NSACF to the NSACF2 and the NSACF2 receives the message to update the UE counter at the NSACF. In various embodiments, the message to update the UE counter at the NSACF may indicate that slice 1 is replaced with slice 2. In various embodiments, such indication may be effected via sending both slice 1 and slice 2 as the identifier (ID).

[00111] At operation 509, the NSACF2 implements the policy configured. In various example embodiments, the policy may include that the NSACF2 does not update the counter as the UE is already registered with slice 1 and the policy indicates usage of original slice’s quotas.

[00112] At operation 510, the UE is handed over from a gNB controlled by AMF1 to a gNB controlled by AMF2, where in AMF2 the original slice 1 is not supported. At operation 511, the UE deregisters from the network (e.g., possibly while being connected to slice 2 or slice 1). In this example the UE deregisters while being connected to slice 2. Upon deregistration of the UE, several example options may be implemented.

[00113] In various embodiments, a first option (option 1) may include, at operation 512, AMF2 may not serve or support slice 1 and may discover the NSACF1 via the NRF. In various embodiments, at operation 513, the AMF2 transmits a message to update the UE counter at the NSACF to the NSACF1 and the NSACF1 receives the message to update the UE counter at the NSACF. In various embodiments, the message may indicate that slice 1 is replaced with slice 2, and such indication could be via sending both slice 1 and slice 2 as the ID. The indication informs that the UE has deregistered, or simply deregistering of the UE from the slice(s). In various embodiments, deregistration does not present any additional change (e.g., a conventional decrease command is sent), as the NSACF may be already aware of the situation of the UE from registration.

[00114] In various embodiments, at operation 514, the AMF2 transmits a message to update the UE counter at the NSACF to the NSACF2 and the NSACF2 receives the message to update the UE counter at the NSACF. In various embodiments, the message may indicate that slice 1 is replaced with slice 2, and such indication could be via sending both slice 1 and slice 2 as the ID. The indication informs that the UE has deregistered, or simply deregistering of the UE from the slice(s). In various embodiments, deregistration does not present any additional change (e.g., a conventional decrease command is sent), as the NSACF may be already aware of the situation of the UE from registration.

[00115] In various embodiments, a second option (option 2) may include, at operation 515, the AMF2 transmits a message to AMF1 that the UE is deregistering and the AMF1 receives the message that the UE is deregistering.

[00116] At operation 516, the AMF1 contacts NSACF1 and the AMF2 contacts NSACF2, which control the respective slices. In various embodiments, at operation 517, the AMF1 transmits a message to update the UE counter at the NSACF to the NSACF1 and the NSACF1 receives the message to update the UE counter at the NSACF. In various embodiments, the message may indicate that slice 1 is replaced with slice 2, and such indication could be via sending both slice 1 and slice 2 as the ID. The indication informs that the UE has deregistered, or simply deregistering of the UE from the slice(s). In various embodiments, deregistration does not present any additional change (e.g., a conventional decrease command is sent), as the NSACF may be already aware of the situation of the UE from registration.

[00117] In various embodiments, at operation 518, the AMF2 transmits a message to update the UE counter at the NSACF to the NSACF2 and the NSACF2 receives the message to update the UE counter at the NSACF. In various embodiments, the message may indicate that slice 1 is replaced with slice 2, and such indication could be via sending both slice 1 and slice 2 as the ID. The indication informs that the UE has deregistered, or simply deregistering of the UE from the slice(s). In various embodiments, deregistration does not present any additional change (e.g., a conventional decrease command is sent), as the NSACF may be already aware of the situation of the UE from registration.

[00118] In various embodiments, a third option (option 3) may include, at operation 519, the AMF2 contacts NSACF2. In various embodiments, at operation 520, the AMF2 transmits a message to update the UE counter at the NSACF to the NSACF2 and the NSACF2 receives the message to update the UE counter at the NSACF. In various embodiments, the message may indicate that slice 1 is replaced with slice 2, and such indication could be via sending both slice 1 and slice 2 as the ID. The indication informs that the UE has deregistered, or simply deregistering of the UE from the slice(s). In various embodiments, deregistration does not present any additional change (e.g., a conventional decrease command is sent), as the NSACF may be already aware of the situation of the UE from registration.

[00119] At operation 521, the NSACF2 transmits message to update the UE counter at the NSACF to the NSACF 1 and the NSACF1 receives the message to update the UE counter at the NSACF. In various embodiments, the message may indicate that slice 1 is replaced with slice 2, and such indication could be via sending both slice 1 and slice 2 as the ID. The indication informs that the UE has deregistered, or simply deregistering of the UE from the slice(s). In various embodiments, deregistration does not present any additional change (e.g., a conventional decrease command is sent), as the NSACF may be already aware of the situation of the UE from registration. In various embodiments, the NSACF2 may discover the NSACF1 based on served slices from the NRF.

[00120] Upon completion of options 1, 2 or 3, at operation 522, the NSACF1 implements the policy configured. In various embodiments, based upon the example described above, the NSACF 1 may decrease only the counter of slice 1, as the UE was counted only for slice 1.

[00121] Upon completion of options 1, 2 or 3, at operation 523, the NSACF2 implements the policy configured. In various embodiments, based upon the example described above, the NSACF2 does not update the counter as the UE was counted only for slice 1 (e.g., the original slice).

[00122] The operations of FIG. 5 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include other operations not illustrated in FIG. 5. In embodiments, the operations may not include every operation illustrated in FIG. 5. In embodiments, the operations may be implemented in a different order than that illustrated in FIG. 5. Such and other embodiments are contemplated to be within the scope of the present disclosure. Persons of skill in the art will appreciate that, although various example components are described as perform various functions, other components may perform those functions described.

[00123] FIG. 6 is a diagram of an example embodiment of signals and operations among a UE, an AMF, and an NSACF, according to one illustrated aspect of the disclosure. As shown in FIG. 6, NSACF1 may be responsible and in control of both slice 1 and slice 2.

[00124] At operation 601, the UE joins the network and attempts to register at the AMF with a first slice (slice 1).

[00125] At operation 602, the AMF transmits a request to the NSACF (NSACF1) to increase the counter of UEs for slice 1 and the NSACF receives the request to increase the counter of UEs for slice 1.

[00126] In case that at NSACF 1 the quota for the number of registered UEs for slice 1 has not been reached yet as in this example, then AMF accepts the UE registration and enters slice 1 in the allowed list of network slices. In various embodiments, slice 1 is the slice allowed to the UE.

[00127] At operation 603, slice replacement occurs (e.g., due to network congestion or maintenance of the slice 1). In various embodiments, slice 1 is replaced with slice 2. At operation 604, the AMF is configured with a policy for slice remapping, for example, per original slice. In various embodiments, the policy may be to use the original slice quotas for slice 1, even if slice 1 is remapped to an alternative slice. In various embodiments, the policy could be usage of the alternative slice’s quota or to not apply any quota at all.

[00128] At operation 605, the AMF does not transmit any message to the NSACF to update the UE counter at the NSACF based on the configured policy, as the UE is already registered with slice 1 (e.g., the slice 1 counter was already increased) and the policy indicates usage of original slice’s quotas.

[00129] At operation 606, the UE deregisters from the network (e.g., possibly while being connected to slice 2 or slice 1). Upon the deregistration from the network, at operation 607, the AMF contacts the NSACF for slice 1 as the UE has been counted for slice 1.

[00130] At operation 608, the AMF transmits a message to update the UE counter at the NSACF (e.g., count decrease command) to the NSACF and the NSACF receives the message to update the UE counter at the NSACF. In various embodiments, the count decrease command includes an indication for the NSACF to decrease the count for slice 1, since the UE was counted only for the original slice.

[00131] The operations of FIG. 6 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include other operations not illustrated in FIG. 6. In embodiments, the operations may not include every operation illustrated in FIG. 6. In embodiments, the operations may be implemented in a different order than that illustrated in FIG. 6. Such and other embodiments are contemplated to be within the scope of the present disclosure. Persons of skill in the art will appreciate that, although various example components are described as perform various functions, other components may perform those functions described.

[00132] FIG. 7 is a diagram of an example embodiment of signals and operations among a UE, an AMF, and multiple NSACFs, according to one illustrated aspect of the disclosure. As shown in FIG. 7, NSACF1 may control slice 1 and NSACF2 may control slice 2.

[00133] At operation 701, the UE joins the network and attempts to register at the AMF with a first slice (slice 1).

[00134] At operation 702, the AMF transmits a request to the NSACF (NSACF1) to increase the counter of UEs for slice 1 and the NSACF receives the request to increase the counter of UEs for slice 1.

[00135] In case that at NSACF 1 the quota for the number of registered UEs for slice 1 has not been reached yet as in this example, then AMF accepts the UE registration and enters slice 1 in the allowed list of network slices. In various embodiments, slice 1 is the slice allowed to the UE

[00136] At operation 703, slice replacement occurs (e.g., due to network congestion or maintenance of the slice 1). In various embodiments, slice 1 is replaced with slice 2. At operation 704, the AMF is configured with a policy for slice remapping, for example, per original slice. In various embodiments, the policy may be to use the original slice quotas for slice 1, even if slice 1 is mapped to an alternative slice. In various embodiments, the policy could be usage of the alternative slice’s quota or to not apply any quota at all.

[00137] At operation 705, the AMF does not transmit any message to the NSACF to update the UE counter at the NSACF based on the configured policy, as the UE is already registered with slice 1 (e.g., the slice 1 counter was already increased) and the policy indicates usage of original slice’s quotas.

[00138] At operation 706, the UE deregisters from the network (e.g., possibly while being connected to slice 2 or slice 1). In this example the UE deregisters the network while being connected to slice 2. Upon the deregistration from the network, at operation 707, the AMF contacts the NSACF for slice 1 as the UE has been counted for slice 1.

[00139] At operation 708, the AMF transmits a message to update the UE counter at the NSACF (e.g., count decrease command) to the NSACF1 and the NSACF1 receives the message to update the UE counter at the NSACF. In various embodiments, the count decrease command includes an indication for the NSACF 1 to decrease the count for slice 1, since the UE was counted only for the original slice.

[00140] The operations of FIG. 7 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include other operations not illustrated in FIG. 7. In embodiments, the operations may not include every operation illustrated in FIG. 7. In embodiments, the operations may be implemented in a different order than that illustrated in FIG. 7. Such and other embodiments are contemplated to be within the scope of the present disclosure. Persons of skill in the art will appreciate that, although various example components are described as perform various functions, other components may perform those functions described.

[00141] FIG. 8 is a diagram of an example embodiment of signals and operations among a UE, multiple AMFs, and multiple NSACFs, according to one illustrated aspect of the disclosure. In various embodiments, an inter AMF handover may be performed between AMF1 and AMF2 where the original slice 1 might not be supported. As shown in FIG. 8, NSACF1 may control slice 1 and NSACF2 may control slice 2.

[00142] At operation 801, the UE joins the network and attempts to register at the AMF with a first slice (slice 1).

[00143] At operation 802, the AMF transmits a request to the NSACF (NSACF1) to increase the counter of UEs for slice 1 and the NSACF receives the request to increase the counter of UEs for slice 1.

[00144] In case that at NSACF 1 the quota for the number of registered UEs for slice 1 has not been reached yet as in this example, then AMF accepts the UE registration and enters slice 1 in the allowed list of network slices. In various embodiments, slice 1 is the slice allowed to the UE

[00145] At operation 803, A MFI is configured with a policy for slice remapping, for example, per original slice. In various embodiments, the policy may be to use the original slice quotas for slice I, even if slice 1 is mapped to an alternative slice. In various embodiments, the policy could be usage of the alternative slice’s quota or to not apply any quota at all.

[00146] At operation 804, AMF2 is configured with a policy for slice remapping, for example, per original slice. In various embodiments, the policy may be to use the original slice quotas for slice 1, even if slice 1 is mapped to an alternative slice. In various embodiments, the policy could be usage of the alternative slice’s quota or to not apply any quota at all.

[00147] At operation 805, slice replacement occurs (e.g., due to network congestion or maintenance of the slice 1). In various embodiments, slice 1 is replaced with slice 2.

[00148] At operation 806, the AMF1 does not transmit any message to the NSACFs to update the UE counter at the NSACFs based on the configured policy, as the UE is already registered with slice 1 (e.g., the slice 1 counter was already increased) and the policy indicates usage of original slice’s quotas.

[00149] At operation 807, the NSACF2 implements the policy configured. In various example embodiments, the policy may include that the NSACF2 does not update the counter as the UE is already registered with slice 1 and the policy indicates usage of original slice’s quotas.

[00150] At operation 808, the UE is handed over from a gNB controlled by AMF1 to a gNB controlled by AMF2. At operation 809, the UE deregisters from the network (e.g., possibly while being connected to slice 2 or slice 1). For example, as depicted in FIG. 8, the UE deregisters from the network while being connected to slice 2. Upon deregistration of the UE, several example options may be implemented.

[00151] In various embodiments, a first option (option 1) may include, at operation 810, AMF2 may not serve slice 1 and may discover the NSACF1 via the NRF. In various embodiments, at operation 811, the AMF2 contacts the NSACF1. For example, at operation 812, the AMF2 transmits a message to update the UE counter at the NSACF (e.g., count decrease command) to the NSACF1 and the NSACF1 receives the message to update the UE counter at the NSACF. In various embodiments, the count decrease command includes an indication for the NSACF to decrease the count for slice 1, since the UE was counted only for the original slice.

[00152] In various embodiments, a second option (option 2) may include, at operation 813, the AMF2 transmits a message to AMF1 that the UE is deregistering and the A MFI receives the message that the UE is deregistering.

[00153] At operation 814, the ^^1\4F 1 contacts bJS.A.(3Fl. In various embodiments, at operation 815, the AMF1 transmits a message to update the UE counter at the NSACF (e.g., count decrease command) to the NSACF1 and the NSACF1 receives the message to update the UE counter at the NSACF. In various embodiments, the count decrease command includes an indication for the NSACF to decrease the count for slice 1, since the UE was counted only for the original slice.

[00154] In various embodiments, a third option (option 3) may include, at operation 816, the AMF2 contacts NSACF2. In various embodiments, at operation 817, the AMF2 transmits a message to update the UE counter at the NSACF to the NSACF2 and the NSACF2 receives the message to update the UE counter at the NSACF. In various embodiments, the message may indicate that slice 1 is replaced with slice 2, and such indication could be via sending both slice 1 and slice 2 as the ID. The indication informs that the UE has deregistered, or simply deregistering of the UE from the slice(s). In various embodiments, deregistration does not present any additional change (e.g., a conventional decrease command is sent), as the NSACF may be already aware of the situation of the UE from registration.

[00155] At operation 818, the NSACF2 transmits a message to update the UE counter at the NSACF to the NSACF 1 and the NSACF1 receives the message to update the UE counter at the NSACF. In various embodiments, the message may indicate that slice 1 is replaced with slice 2, and such indication could be via sending both slice 1 and slice 2 as the ID. The indication informs that the UE has deregistered, or simply deregistering of the UE from the slice(s). In various embodiments, deregistration does not present any additional change (e.g., a conventional decrease command is sent), as the NSACF may be already aware of the situation of the UE from registration. In various embodiments, the NSACF2 may discover the NSACF1 based on served slices from the NRF.

[00156] Upon completion of options 1, 2 or 3, at operation 819, the NSACF1 implements the policy configured. In various embodiments, based upon the example described above, the NSACF1 may decrease only the counter of slice 1, as the UE was counted only for slice 1.

[00157] Upon completion of options 1, 2 or 3, at operation 820, the NSACF2 implements the policy configured. In various embodiments, based upon the example described above, the NSACF2 does not update the counter as the UE was counted only for slice 1 (e.g., the original slice).

[00158] The operations of FIG. 8 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include other operations not illustrated in FIG. 8. In embodiments, the operations may not include every operation illustrated in FIG. 8. In embodiments, the operations may be implemented in a different order than that illustrated in FIG. 8. Such and other embodiments are contemplated to be within the scope of the present disclosure. Persons of skill in the art will appreciate that, although various example components are described as perform various functions, other components may perform those functions described.

[00159] FIG. 9 is a diagram of an example embodiment of signals and operations among a UE, an AMF, and SMF, and an NSACF, according to one illustrated aspect of the disclosure.

[00160] At operation 901, the UE joins the network and attempts to register at the AMF with a first slice (slice 1).

[00161] In case that at NSACF the quota for the number of registered UEs for slice 1 has not been reached yet as in this example, then AMF accepts the UE registration and enters slice 1 in the allowed list of network slices. In various embodiments, slice 1 is the slice allowed to the UE. In this scenario the UE already has established a PDU session for slice 1.

[00162] At operation 902, NSACF is configured with a policy for slice remapping, for example, per original slice. In various embodiments, the policy may be to use the original slice quotas for slice 1, even if slice 1 is mapped to an alternative slice. In various embodiments, the policy could be usage of the alternative slice’s quota or to not apply any quota at all.

[00163] At operation 903, slice replacement occurs (e.g., due to network congestion or maintenance of the slice 1). In various embodiments, slice 1 is replaced with slice 2. At operation 904, the AMF transmits a message to the SMF informing the SMF of the slice replacement, and the SMF receives the message informing of the slice replacement.

[00164] At operation 905, the PDU session is mapped from slice 1 to slice 2.

[00165] At operation 906, the SMF transmits a message to update the UE counter at the NSACF to the NSACF and the NSACF receives the message to update the UE counter at the NSACF. In various embodiments, the message to update the UE counter at the NSACF may indicate that slice 1 is replaced with slice 2. In various embodiments, such indication may be effected via sending both slice 1 and slice 2 as the identifier (ID).

[00166] At operation 907, the NSACF implements the policy configured. In various example embodiments, the policy may include that the NSACF does not update the counter as the UE is already registered with slice 1 (e.g., the slice 1 counter was increased already) and the policy indicates usage of original slice’s quotas.

[00167] At operation 908, the UE deregisters from the network (e.g., possibly from slice 2 or slice 1). Upon the deregistration from the network, at operation 909, the SMF transmits a message to update the UE counter at the NSACF to the NSACF and the NSACF receives the message to update the UE counter at the NSACF. In various embodiments, the message may indicate that slice 1 is replaced with slice 2, and such indication could be via sending both slice 1 and slice 2 as the ID. The indication informs that the UE has deregistered, or simply deregistering of the UE from the slice(s). In various embodiments, deregistration does not present any additional change (e.g., a conventional decrease command is sent), as the NSACF may be already aware of the situation of the UE from registration. The NSACF implements the configured policy. In various embodiments, for example, the NSACF decreases the counter of slice 1 only, as the UE / PDU session was only counted for slice 1.

[00168] The operations of FIG. 9 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include other operations not illustrated in FIG. 9. In embodiments, the operations may not include every operation illustrated in FIG. 9. In embodiments, the operations may be implemented in a different order than that illustrated in FIG. 9. Such and other embodiments are contemplated to be within the scope of the present disclosure. Persons of skill in the art will appreciate that, although various example components are described as perform various functions, other components may perform those functions described.

[00169] The following describes operations from the perspective of an NSACF. From such a perspective, in various embodiments a method may include receiving a first message from a second apparatus, wherein the first message comprises at least one of an update indication identifying a first network slice and a second network slice and an indication identifying that the first network slice is replaced with the second network slice, wherein the NSACF is configured for the first network slice and the second network slice wherein the first network slice includes a first quota and the second network slice includes a second quota and a single-network slice selection assistance information (S-NSSAI) policy to be used in case of a network slice replacement associated with serving a user equipment (UE) from the first network slice to serving the UE from the second network slice. Based on the S-NSSAI policy, the NSACF performs a first update to at least one of the first quota of the first network slice or the second quota of the second network slice, The NSACF receives a second message from the second apparatus, wherein the second message comprises an indication that communication with the UE is ceased and at least one of an indication indicating the first network slice or the second network slice, and based on the S-NSSAI policy, performs a second update to at least one of the first quota of the first network slice or the second quota of the second network slice.

[00170] The following describes operations from the perspective of an AMF or SMF (AMF / SMF). From such a perspective, in various embodiments a method may include serving, by an AMF / SMF, a user equipment (UE) associated with a first network slice. Upon determination of a network slice replacement of the first network slice with a second network slice, the AMF / SMF transmits to at least one of a second apparatus associated with the first slice, a first message, wherein the first message comprises at least one of an update indication identifying the first network slice and the second network slice or an indication that the first network slice is replaced with the second network slice, and upon determination of the UE deregistering from the network, transmits a second message to at least the second apparatus, wherein the second message comprises an indication that the UE communication is ceased and at least one of an indication indicating the first network slice or the second network slice.

[00171] Referring now to FIG. 10, there is shown a block diagram of example components of a UE or a network apparatus (e.g., of a RAN or a core network). The apparatus includes an electronic storage 1010, a processor 1020, a network interface 1040, and a memory 1050. The various components may be communicatively coupled with each other. The processor 1020 may be and may include any type of processor, such as a single-core central processing unit (CPU), a multi-core CPU, a microprocessor, a digital signal processor (DSP), a System-on-Chip (SoC), or any other type of processor. The memory 1050 may be a volatile type of memory, e.g., RAM, or a non-volatile type of memory, e.g., NAND flash memory. The memory 1050 includes processor-readable instructions that are executable by the processor 1020 to cause the apparatus to perform various operations, including those mentioned herein, such as the operations of FIGS. 3-9.

[00172] The electronic storage 1010 may be and include any type of electronic storage used for storing data, such as hard disk drive, solid state drive, optical disc, and / or other non-transitory computer-readable mediums, among other types of electronic storage. The electronic storage 1010 stores processor-readable instructions for causing or configured for causing the apparatus to perform its operations and also stores data associated with such operations, such as storing data relating to 5G NR standards, among other data. The network interface 1040 may implement wireless networking technologies such as 5G NR and / or other wireless networking technologies.

[00173] The components shown in FIG. 10 are merely examples, and persons skilled in the art will understand that an apparatus includes other components not illustrated and may include multiples of any of the illustrated components. Such and other embodiments are contemplated to be within the scope of the present disclosure.

[00174] Further embodiments of the present disclosure include the following examples.

[00175] Example 1.1. A first apparatus, including: means for receiving, by the first apparatus, a first message from a second apparatus, wherein the first message comprises at least one of an update indication identifying a first network slice and a second network slice and an indication identifying that the first network slice is replaced with the second network slice, wherein the first apparatus is configured for the first network slice and the second network slice wherein the first network slice includes a first quota and the second network slice includes a second quota and a single-network slice selection assistance information (S-NSSAI) policy to be used in case of a network slice replacement associated with serving a user equipment (UE) from the first network slice to serving the UE from the second network slice; means for, based on the S-NSSAI policy, performing, by the first apparatus, a first update to at least one of the first quota of the first network slice or the second quota of the second network slice; means for receiving, by the first apparatus, a second message from the second apparatus, wherein the second message comprises an indication that communication with the UE is ceased and at least one of an indication indicating the first network slice or the second network slice; and means for, based on the S-NSSAI policy, performing, by the first apparatus, a second update to at least one of the first quota of the first network slice or the second quota of the second network slice.

[00176] Example 1.2. The first apparatus of example 1.1, wherein the first quota includes an indication of a number of users allowed access to the first network slice and the second quota includes an indication of a number of users allowed access to the second network slice.

[00177] Example 1.3. The first apparatus of example 1.2, wherein the performing a first update to the second quota of the second network slice includes adding to a counter of users of the second network slice.

[00178] Example 1.4. The first apparatus of example 1.1, wherein the second quota includes an indication of a number of protocol data unit (PDU) sessions allowed access to the second network slice.

[00179] Example 1.5. The first apparatus of example 1.4, wherein the performing the first update to the second quota of the second network slice includes adding to a counter of PDU sessions of the second network slice.

[00180] Example 1.6. The first apparatus of example 1.1, wherein the performing the second update to the first quota of the first network slice includes subtracting from a counter of users of the first network slice.

[00181] Example 1.7. The first apparatus of example 1.1, wherein the performing the second update to the first quota of the first network slice includes subtracting from a counter of protocol data unit (PDU) sessions of the first network slice.

[00182] Example 1.8. The first apparatus of example 1.1, wherein the performing the first update to the second quota of the second network slice includes maintaining a counter for the second quota at a same value.

[00183] Example 1.9. The first apparatus of example 1.1, wherein the performing the first update to the first quota of the first network slice includes maintaining a counter for the first quota at a same value.

[00184] Example 1.10. The first apparatus of example 1.1, wherein the first apparatus includes a network slice admission control function (NSACF).

[00185] Example 1.11. The first apparatus of example 1.10, wherein the NSACF receives the first message from an access and mobility management function (AMF).

[00186] Example 2.1. A first apparatus, including: means for serving, by the first apparatus, a user equipment (UE) associated with a first network slice; means for, upon determination of a network slice replacement of the first network slice with a second network slice, transmitting, by the first apparatus to at least one of a second apparatus associated with the first slice, a first message, wherein the first message comprises at least one of an update indication identifying the first network slice and the second network slice or an indication that the first network slice is replaced with the second network slice; and means for, upon determination of the UE deregistering from the network, transmitting a second message to at least the second apparatus, wherein the second message comprises an indication that the UE communication is ceased and at least one of an indication indicating the first network slice or the second network slice.

[00187] Example 2.2. The first apparatus of example 2.1, wherein the second apparatus is a first network slice admission control function (NSACF).

[00188] Example 2.3. The first apparatus of example 2.2, wherein the second apparatus is associated with the first network slice and the second network slice.

[00189] Example 2.4. The first apparatus of example 2.2, further including means for transmitting, by the first apparatus, the first message to a third apparatus associated with the second network slice.

[00190] Example 2.5. The first apparatus of example 2.4, wherein the third apparatus is a second NSACF.

[00191] Example 2.6. The first apparatus of example 2.1, wherein the first apparatus is an access and mobility management function (AMF) or a session management function (SMF).

[00192] Example 3.1. An apparatus, including: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, cause the apparatus at least to: receive a first message from a second apparatus, wherein the first message comprises at least one of an update indication identifying a first network slice and a second network slice and an indication identifying that the first network slice is replaced with the second network slice, wherein the first apparatus is configured for the first network slice and the second network slice wherein the first network slice includes a first quota and the second network slice includes a second quota and a single-network slice selection assistance information (S-NSSAI) policy to be used in case of a network slice replacement associated with serving a user equipment (UE) from the first network slice to serving the UE from the second network slice; based on the S-NSSAI policy, perform a first update to at least one of the first quota of the first network slice or the second quota of the second network slice; receive a second message from the second apparatus, wherein the second message comprises an indication that communication with the UE is ceased and at least one of an indication indicating the first network slice or the second network slice; and based on the S-NSSAI policy, perform a second update to at least one of the first quota of the first network slice or the second quota of the second network slice.

[00193] Example 4.1. An apparatus, including: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, cause the apparatus at least to: serve a user equipment (UE) associated with a first network slice; upon determination of a network slice replacement of the first network slice with a second network slice, transmit to at least one of a second apparatus associated with the first slice, a first message, wherein the first message comprises at least one of an update indication identifying the first network slice and the second network slice or an indication that the first network slice is replaced with the second network slice; and upon determination of the UE deregistering from the network, transmit a second message to at least the second apparatus, wherein the second message comprises an indication that the UE communication is ceased and at least one of an indication indicating the first network slice or the second network slice.

[00194] The embodiments and aspects disclosed herein are examples of the present disclosure and may be embodied in various forms. For instance, although certain embodiments herein are described as separate embodiments, each of the embodiments herein may be combined with one or more of the other embodiments herein. Specific structural and functional details disclosed herein are not to be interpreted as limiting, but as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present disclosure in virtually any appropriately detailed structure. Like reference numerals may refer to similar or identical elements throughout the description of the figures.

[00195] As described above, in various embodiments, a first network node (e.g., AMF, SMF) may trigger an update towards an NSACF for a UE / PDU session count. The update may comprise increase or decrease of UE / PDU Session count. In various embodiments, the first network node may include, together with the update, an indication that this update is related to slice remapping. In various embodiments, the first network node may indicate the original and alternative S-NSSAI for which the remapping occurred.

[00196] In various embodiments, an NSACF, based on the notification from the first network node and based on a policy configured (e.g., by an operator) may update the UE / PDU session count accordingly. In various embodiments, an indicated policy may include that the quota of an alternative slice is used also for the original slice after slice remapping. In various embodiments, an indicated policy may include that the quota of the original slice is used even after slice remapping. In various embodiments, an indicated policy may include that no quota’s apply after remapping. In various embodiments, the counter of the original / alternative slice is updated accordingly.

[00197] The phrases “in an aspect,” “in aspects,” “in various aspects,” “in some aspects,” or “in other aspects” may each refer to one or more of the same or different aspects in accordance with this present disclosure. The phrase “a plurality of’ may refer to two or more.

[00198] In various embodiments, the terms “first message” and “second message”, as well as any subsequent messages may refer to any messages that are transmitted or received in an order and are not necessarily limited to any particular message.

[00199] In various embodiments, the terms “first”, “second”, as well as any subsequent terms such as “third”, “fourth”, for example, may refer to any messages, apparatus, components, devices, etc. and are not necessarily limited to any particular messages, apparatus, components, devices, etc.

[00200] The phrases “in an embodiment,” “in embodiments,” “in various embodiments,” “in some embodiments,” or “in other embodiments” may each refer to one or more of the same or different embodiments in accordance with the present disclosure. A phrase in the form “A or B” means “(A), (B), or (A and B).” A phrase in the form “at least one of A, B, or C” means “(A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C).”

[00201] Any of the herein described methods, programs, algorithms or codes may be converted to, or expressed in, a programming language or computer program. The terms “programming language” and “computer program,” as used herein, each include any language used to specify instructions to a computer, and include (but is not limited to) the following languages and their derivatives: Assembler, Basic, Batch files, BCPL, C, C+, C++, Delphi, Fortran, Java, JavaScript, machine code, operating system command languages, Pascal, Perl, PL1, Python, scripting languages, Visual Basic, metalanguages which themselves specify programs, and all first, second, third, fourth, fifth, or further generation computer languages. Also included are database and other data schemas, and any other meta-languages. No distinction is made between languages which are interpreted, compiled, or use both compiled and interpreted approaches. No distinction is made between compiled and source versions of a program. Thus, reference to a program, where the programming language could exist m more than one state (such as source, compiled, object, or linked) is a reference to any and all such states. Reference to a program may encompass the actual instructions and / or the intent of those instructions.

[00202] While aspects of the present disclosure have been shown in the drawings, it is not intended that the present disclosure be limited thereto, as it is intended that the present disclosure be as broad in scope as the art will allow and that the specification be read likewise. Therefore, the above description should not be construed as limiting, but merely as exemplifications of particular aspects. Those skilled in the art will envision other modifications within the scope and spirit of the claims appended hereto.

Claims

1. A method, comprising:receiving, by the first apparatus, a first message from a second apparatus, wherein the first message comprises at least one of an update indication identifying a first network slice and a second network slice or an update indication identifying that the first network slice is replaced with the second network slice, wherein the first apparatus is configured for the first network slice and the second network slice wherein the first network slice includes a first quota and the second network slice includes a second quota and a single-network slice selection assistance information (S-NSSAI) policy to be used in case of a network slice replacement associated with serving a user equipment (UE) from the first network slice to serving the UE from the second network slice;based on the S-NSSAI policy, performing, by the first apparatus, a first update to at least one of the first quota of the first network slice or the second quota of the second network slice;receiving, by the first apparatus, a second message from the second apparatus, wherein the second message comprises an indication that communication with the UE is ceased and at least one of an indication indicating the first network slice or the second network slice; andbased on the S-NSSAI policy, performing, by the first apparatus, a second update to at least one of the first quota of the first network slice or the second quota of the second network slice.

2. The method of claim 1, wherein the first quota includes an indication of a number of users allowed access to the first network slice and the second quota includes an indication of a number of users allowed access to the second network slice.

3. The method of claim 2, wherein the performing the first update to the second quota of the second network slice includes adding to a counter of users of the second network slice.

4. The method of claim 1, wherein the second quota includes an indication of a number of protocol data unit (PDU) sessions allowed access to the second network slice.

5. The method of claim 4, wherein the performing the first update to the second quota of the second network slice includes adding to a counter of PDU sessions of the second network slice.

6. The method of claim 1, wherein the performing the second update to the first quota of the first network slice includes subtracting from a counter of users of the first network slice.

7. The method of claim 1, wherein the performing the second update to the first quota of the first network slice includes subtracting from a counter of protocol data unit (PDU) sessions of the first network slice.

8. The method of claim 1, wherein the performing the first update to the second quota of the second network slice includes maintaining a counter for the second quota at a same value.

9. The method of claim 1, wherein the performing the first update to the first quota of the first network slice includes maintaining a counter for the first quota at a same value.

10. The method of claim 1, wherein the first apparatus includes a network slice admission control function (NSACF).

11. The method of claim 10, wherein the NSACF receives the first message from an access and mobility management function (AMF).

12. A method, comprising:serving, by a first apparatus, a user equipment (UE) associated with a first network slice;upon determination of a network slice replacement of the first network slice with a second network slice, transmitting, by the first apparatus to at least one of a second apparatus associated with the first slice, a first message, wherein the first message comprises at least one ofan update indication identifying the first network slice and the second network slice or an indication that the first network slice is replaced with the second network slice; andupon determination of the UE deregistering from the network, transmitting a second message to at least the second apparatus, wherein the second message comprises an indication that the UE communication is ceased and at least one of an indication indicating the first network slice or the second network slice.

13. The method of claim 12, wherein the second apparatus is a first network slice admission control function (NSACF).

14. The method of claim 13, wherein the second apparatus is associated with the first network slice and the second network slice.

15. The method of claim 13, further comprising transmitting, by the first apparatus, the first message to a third apparatus associated with the second network slice.

16. The method of claim 15, wherein the third apparatus is a second NSACF.

17. The method of claim 12, wherein the first apparatus is an access and mobility management function (AMF) or a session management function (SMF).

18. An apparatus, comprising:at least one processor; andat least one memory storing instructions which, when executed by the at least one processor, cause the apparatus at least to perform a method as in any of claims 1-17.

19. A processor-readable medium storing instructions which, when executed by at least one processor of an apparatus, cause the apparatus at least to perform a method as in any one of claims 1-17.

Images