FRAMEWORK FOR DYNAMIC RESOURCE MANAGEMENT WITHIN A

SHARED SLICE

TECHNICAL FIELD

The present disclosure relates to wireless communication and in particular, arrangements for dynamic resource management within a shared slice.

BACKGROUND

Recently, there have been discussions on dynamic management of resources for so-called ‘big slices’ such as enhanced mobile broadband (eMBB) and where it is desirable to allocate dedicate control plane resources to some verticals.

In recent discussions, the term ‘super slice’ was introduced. Such ‘super slice’ provides a long-term management of a resource pool associated to a specific vertical service, such as eMBB or vehicle-to-everything (V2X), where the (super) sliced resources are associated to this service category. It has been considered to study this concept by proposing dynamic control level mechanisms to pin resources within a (super slice provided) resource pool to specific customers, such as those of a customer that the home operator (of the super slice) has a business relationship with (such as a mobile virtual network operation (MVNO)). The particular focus is on the enabling nature of service-based architecture (SBA) for those mechanisms and the super slice concept overall.

The realization of an (enhanced) service-based architecture (eSBA) in 3 ^rd Generation Partnership Project (3 GPP) 5 ^th Generation (5G, also called New Radio or NR) control planes utilize named-based relations in a service function chain (SFC). The SFC may be defined through the control plane interactions for the specific use cases. As specified in 3GPP Technical Specification (TS) 23.501 and/or 3GPP TS 23.502, the realization of 5G control planes following the SBA design may assume hypertext transport protocol (HTTP) as the main protocol for interaction. This lifts the message exchange between control plane services (CPSs) onto the level of an exchange between two named entities. For instance, the message exchange to establish an authenticated session or “PDU Session” (i.e., protocol data unit session) such as referred to in 3 GPP, can be described as:

UE <-> amf.3gppnetwork.mnc.mcc.org <-> smf.3gppnetwork.mnc.mcc.org, 2 where the naming here is only an example. Note that the naming could also include information relation to slicing, such as slicing identifier, as a sub-domain. Furthermore, the named identifiers are targeting the Service (in particular the network function (NF)) and not a specific or pre-defined endpoint.

3 GPP considers that an expected benefit for the introduction of such named relations is the execution of service functionality in different CPS instances, e.g., “to support dynamic and automatic addition, update and planned removal of CP NFs and/or services in virtualized environments”. This is particularly driven by the envisioned stateless execution of a CPS transaction, which allows the direction to any particular service instance to even change from one transaction to another.

In any such (SBA-based) control plane realizations, the ability to flexibly direct traffic to any suitable service instance within the proper set is crucial, with the choice of ‘suitable’ left to the realization of the SCP functionality of the SBA platform, or the service consumer, or both. The shortest path is often an applied policy for suitability, which may result in traffic for the next hop of the Service Function Path (SFP) always being sent to the topologically nearest service instance. The service itself may be provisioned by Service Function Endpoints (SFEs). These Endpoints are added dynamically to the resource pool, serving the service request, according to the lifecycle management procedures of the Endpoints.

Although such dynamic management and flexibility may be desirable, it has some drawbacks.

SUMMARY

Some embodiments advantageously provide methods and apparatuses for arrangements for dynamic resource management within a shared slice.

In one embodiment, a network node is configured to as a result of a registration of a user equipment (UE), determine to identify a network slice based at least in part on information comprising an indication that at least one network function (NF) type is to be a dedicated resource for the network slice; and indicate the identified network slice as an allowed network slice supported for the UE.

In one embodiment, a network node is configured to request to register a profile for the NF at a network repository function (NRF), the profile comprising an 3 information element (IE) indicating one of that the NF is (i) available as a dedicated resource and (ii) is reserved as the dedicated resource.

In one embodiment, a network node is configured to register and/or update a profile for a network function (NF) to comprise information indicating one of that the NF is (i) available as a dedicated resource and (ii) is reserved as the dedicated resource.

According to one aspect, a method implemented in a first network node is described. The method comprises receiving a wireless device registration request comprising network slice information associated with a requested network slice; selecting any one of the first network node and a second network node as a dedicated resource for the requested network slice based at least in part on the received wireless device registration request; and transmitting a wireless device registration response based at least on the selected any one of the first network node and the second network node.

In some embodiments, the network slice information comprises an indication that at least one network node is to be the dedicated resource for the requested network slice.

In some other embodiments, the method further includes transmitting a profile registration request to a third network node to register a profile of the first network node at the third network node.

In one embodiment, the profile includes an information element (IE) indicating whether the first network node is available for reservation.

In another embodiment, the method further includes receiving a profile registration response, from the third network node, including a list of network nodes available for reservation.

In some embodiments, the third network node comprises a network repository function (NRF) node.

In some other embodiments, the method further includes: transmitting, in response to the wireless device registration request, a discovery request to the third network node to discover at least one network node indicated as one dedicated resource; and receiving a discovery response, from the third network node, including a list of the at least one network node indicated as one dedicated resource. 4

In one embodiment, selecting any one of the first network node and the second network node as the dedicated resource for the requested network slice includes: selecting an existing network node that is already reserved for the requested network slice, the existing network node being any one of the first network node and the second network node; and selecting another network node that is available to be reserved for the requested network slice.

In another embodiment, the method further includes: when the first network node is selected as the dedicated resource, transmitting the wireless device registration response including an indication that the first network node is the dedicated resource; and when the second network node is selected as the dedicated resource, transmitting the wireless device registration response including an indication to reroute the wireless device registration request to the selected second network node.

In some embodiments, the method further includes: receiving a protocol data unit (PDU) session establishment request; and in response to the PDU session establishment request, selecting a fourth network node, the fourth network node comprising a session management function (SMF) node and being another dedicated resource.

In some other embodiments, the method further includes transmitting a context creation request to the fourth network node. The context creation request includes a dedicated session management function (SMF) indicator configured to trigger the fourth network node to be dedicated for the requested network slice. The requested network slice is associated with the PDU session establishment request.

In one embodiment, the first network node comprises a first access and mobility function (AMF) node and the second network node comprises a second AMF node.

According to another aspect, a first network node is described. The first network node comprises processing circuitry and a communication interface in communication with the processing circuitry. The communication interface is configured to: receive a wireless device registration request comprising network slice information associated with a requested network slice; and transmitting a wireless device registration response based at least on a selected any one of the first network node and a second network node. The processing circuitry is configured to select any 5 one of the first network node and the second network node as a dedicated resource for the requested network slice based at least in part on the received wireless device registration request.

In some embodiments, the network slice information comprises an indication that at least one network node is to be the dedicated resource for the requested network slice.

In some other embodiments, the communication interface is further configured to transmit a profile registration request to a third network node to register a profile of the first network node at the third network node.

In one embodiment, the profile includes an information element (IE) indicating whether the first network node is available for reservation.

In another embodiment, the communication interface is further configured to receive a profile registration response, from the third network node, including a list of network nodes available for reservation.

In some embodiments, the third network node comprises a network repository function (NRF) node.

In some other embodiments, the communication interface is further configured to: transmit, in response to the wireless device registration request, a discovery request to the third network node to discover at least one network node indicated as one dedicated resource; and receive a discovery response, from the third network node, including a list of the at least one network node indicated as one dedicated resource.

In one embodiment, the processing circuitry configured to select any one of the first network node and the second network node as the dedicated resource for the requested network slice is further configured to select an existing network node that is already reserved for the requested network slice, the existing network node being any one of the first network node and the second network node and select another network node that is available to be reserved for the requested network slice.

In another embodiment, the communication interface is further configured to: when the first network node is selected as the dedicated resource, transmit the wireless device registration response including an indication that the first network node is the dedicated resource; and when the second network node is selected as the 6 dedicated resource, transmit the wireless device registration response including an indication to reroute the wireless device registration request to the selected second network node.

In some embodiments, the communication interface is further configured to: receive a protocol data unit (PDU) session establishment request; and in response to the PDU session establishment request, selecting a fourth network node, the fourth network node comprising a session management function (SMF) node and being another dedicated resource.

In some other embodiments, the communication interface is further configured to transmit a context creation request to the fourth network node. The context creation request includes a dedicated session management function (SMF) indicator configured to trigger the fourth network node to be dedicated for the requested network slice. The requested network slice is associated with the PDU session establishment request.

In one embodiment, the first network node comprises a first access and mobility function (AMF) node and the second network node comprises a second AMF node.

According to one aspect, a system is described. The system comprises a first network node, a second network node, and a third network node. The first network node comprises first processing circuitry and a first communication interface in communication with the first processing circuitry. The first communication interface is configured to: receive a protocol data unit (PDU) session establishment request; and transmit a context creation request to the second network node. The context creation request includes a dedicated session management function indicator configured to trigger the second network node to be dedicated for a requested network slice. The requested network slice is associated with the PDU session establishment request. The first processing circuitry is configured to, in response to the PDU session establishment request, select the second network node as a dedicated resource based on a list of network nodes available for reservation.

The second network node comprises second processing circuitry and a second communication interface in communication with the second processing circuitry. The second communication interface is configured to receive the context creation request; 7 transmit a profile registration request to the third network node to register a profile of the second network node at the third network node, where the profile includes an information element (IE) indicating whether the second network node is available for reservation; and transmit a node registration request to the third network node to register the second network node at the third network node as dedicated for reservation. The second processing circuitry is configured to dedicate the second network node for the requested network slice.

In some embodiments, the first network node comprises an access and mobility function (AMF) node, the second network node comprises a session management function (SMF) node, and the third network node comprises a network repository function (NRF) node.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

FIG. 1 illustrates an example system architecture according to some embodiments of the present disclosure;

FIG. 2 illustrates yet another example system architecture and example hardware arrangements for devices in the system, according to some embodiments of the present disclosure;

FIG. 3 is a flowchart of an example process in an AMF according to some embodiments of the present disclosure;

FIG. 4 is a flowchart of an example process in an SMF according to some embodiments of the present disclosure;

FIG. 5 is a flowchart of an example process in an NSSF according to some embodiments of the present disclosure;

FIG. 6 is flowchart of an example process in an NRF according to one embodiment of the present disclosure;

FIG. 7 is flowchart of an example process in a first network node, e.g., an AMF, according to some embodiments of the present disclosure; 8

FIG. 8 is a call flow diagram illustrating an example UE registration process according to some embodiments of the present disclosure;

FIG. 9 is a call flow diagram illustrating an example AMF re-allocation procedure according to some embodiments of the present disclosure;

FIG. 10 is a call flow diagram illustrating an example SMF selection procedure according to some embodiments of the present disclosure;

FIG. 11 is a call flow diagram illustrating another example SMF selection procedure according to some embodiments of the present disclosure;

FIG. 12 is a call flow diagram illustrating an example NRF procedure related to SMF reservation according to some embodiments of the present disclosure;

FIG. 13 is a call flow diagram illustrating another example NRF procedure according to embodiments of the present disclosure; and

FIG. 14 is a call flow diagram illustrating yet another example NRF procedure according to some embodiments of the present disclosure.

DETAILED DESCRIPTION

As described above, the ability to flexibly direct traffic to any suitable service instance to provide dynamic management of resources has some drawbacks. In particular some customers may desire to have complete isolation at the control plane and/or user plane. Some embodiments of the present disclosure provide arrangements to address such issues.

Some embodiments may provide arrangements to support at least two different embodiments.

AMF

A single-network slice selection assistance information (S-NSSAI) identifies a network slice. An S-NSSAI that is required or requested to have a dedicated AMF and/or a dedicated SMF for the S-NSSAI may have a separate instance (e.g., an NF instance for AMF that may be separate from and/or separate NF instance for SMF), even if the S-NSSAI (e.g., network slice, or more specifically, NFs instances and resources (e.g., compute, storage and networking resources) that may form the network slice happens to be shared amongst e.g., multiple consumers and/or services. 9

In some embodiments, the AMF node 16 is configured with the following information element (IE) regarding an S-NSSAI requiring/requesting a dedicated AMF and/or a dedicated SMF:

- S-NSSAI identifier (ID): o Dedicated AMF required/requested o Dedicated SMF required/requested.

Terms different from the above terms may be used, but the function may be the same.

In some embodiments, there can be as many S-NSSAIs as needed configured in the AMF nodes 16.

NSSF

Optionally, additionally or alternatively, in some embodiments, this information can be configured in a NSSF node and returned at UE registration in 5GC, when the AMF node queries the NSSF node. This may be provided by an update to the NSSF’s nssf_NSSelection_Get service operation.

In some embodiments, if the NSSF performs this operation (e.g., of providing an NF instance, such as AMF, and/or associated resources that are dedicated to a particular slice identified by the S-NSSAI) the NSSF adjusts the returned Allowed S- NSSAI, according to one or more of the following:

-If the UE subscribed S-NSSAI includes one or more S-NSSAI that requires/requests dedicated resources (e.g., computer, storage, network resources, which may in a cloud environment) then the NSSF node selects one S-NSSAI that requires both AMF and SMF dedicated resources and/or includes that one in the Allowed S-NSSAI.

-If there is none (e.g., no S-NSSAI requiring both AMF and SMF dedicated resources), then if there is one or more S-NSSAI that requires dedicated SMF resources, the NSSF node selects one S-NSSAI that requires dedicated SMF resource and/or includes that one in the Allowed S-NSSAI.

-If there is none (e.g., no S-NSSAI requiring dedicated SMF resources), and if there is one or more S-NSSAIs that requires dedicated AMF resources, the NSSF node selects that one S-NSSAI and/or includes that one in the Allowed S-NSSAI. 10

-If there is no S-NSSAI requiring any dedicated resources than regular processing may be performed by the NSSF node.

-In some embodiments, one S-NSSAI requiring dedicated resources is returned in the Allowed S-NSSAI. No other S-NSSAI is included in the Allowed S- NSSAI. If there are no S-NSSAI requiring dedicated resources, then normal processing may be assumed by the NSSF node.

The above logic can have a different order of priority in different embodiments.

In some embodiments, the selected AMF (e.g., selected by the RAN connected to the UE) depends on one or more of the NSSF procedures above and may return information about an appropriate AMF accordingly (e.g., itself if appropriate and/or information about a target AMF).

In some embodiments, the NSSF node may perform a new AMF discovery procedure described below. The new AMF discovery procedure may select an appropriate AMF if dedicated AMF resources is required for the Allowed S-NSSAI and/or returned by the NSSF node in the response.

Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to dynamic resource management within a shared slice. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms 11

“comprises,” “comprising,” “includes” and/or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.

In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The UE herein can be any type of wireless device capable of communicating with a network node or another UE over radio signals. In some embodiments, the UE may be an autonomous machine configured to communicate via IMS. The UE herein can by any type of communication device capable of communicating with another UE, an application server (AS), a network node, a server, an IMS NF or other IMS network node, via a wired connection and/or a wireless connection. The UE may also be a radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), low-cost and/or low-complexity UE, a sensor equipped with UE, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (IoT) device, or a Narrowband IoT (NB-IOT) device etc.

In some embodiments, the term “node” is used herein and can be (and/or comprise) any kind of network node (NN), such as, , a network function (NF) node, a mobility management node (e.g., Mobility Management Entity (MME) and/or Access and Mobility Function (AMF)), a gateway node (e.g., access gateway), a session 12 management node (e.g., session management function (SMF) node such as a home SMF (H- SMF), a visited SMF (V- SMF), roaming SMF (R-SMF), etc.), a network slice selection function (NSSF) node, a user plane function (UPF) node, an AS node or any network node. In some embodiments, the network node may be, for example, a subscriber database node (e.g., unified data repository (UDR), home subscriber server (HSS)), a core network node, a Fifth Generation (5G) and/or New Radio (NR) network node, an Evolved Packet System (EPS) node, an Internet Protocol (IP) Multimedia Subsystem (IMS) node, an Serving-CSCF node, an Interrogating-CSCF node, a network repository function (NRF) node (e.g., a home NRF (H-NRF), a visited NRF (V-NRF), etc.), a unified data management (UDM) node, a network exposure function (NEF) node, a home subscriber server (HSS) node, a home location register (HLR) node, a policy control function (PCF) node, authentication server function (AUSF) node, a data network (DN) node, etc.

In yet other embodiments, the network node may include (and/or be) any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), relay node, integrated access and backhaul (IAB), donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node.

In some embodiments, one or more of the nodes described herein may be more generally considered and/or comprise a network function (NF) and may be referred to as a NF node. For example, the AMF, SMF, NSSF and NRF described herein may be more generally referred to as NF nodes. 13

In some embodiments, a Third Generation Partnership Project (3GPP) core network (e.g., 5GC) may include a Service Based Architecture (SBA) in which Network Functions (NFs) provide one or more services to one or more service consumers. This can be performed, for example, via Hyper Text Transfer Protocol/Representational State Transfer (HTTP/REST), application programming interfaces (APIs), etc. Generally, the various services may be considered self- contained functionalities that can be changed and modified in an isolated manner without affecting other services. Furthermore, the services may include various service operations, which may be more granular divisions of the overall service functionality. In some embodiments, in order to access a service, both the service name and the targeted service operation is to be indicated. The interactions between service consumers and service producers may be, for example, a “request/response” or “subscribe/notify” type or yet other types of interactions. In some embodiments, a network repository functions (NRF) may allow NFs to discover the services offered by other NFs, and Data Storage Functions (DSFs) may allow NFs to store its context. In some embodiments, the 5GC SBA model may provide e.g., modularity, reusability and/or self-containment of NFs, which may be compatible with virtualization technologies.

In some embodiments, one or more of the nodes described herein may be more generally considered and/or comprise an application function (AF) and may be referred to as an AF node.

In some embodiments, an AF may interact with a 3GPP core network (e.g., 5GC) to provide one or more of services. Based on operator deployment, an AF may be trusted by the operator to interact directly with relevant network functions (NFs). AFs not permitted by the operator to access directly the NFs may use, for example, an external exposure framework (e.g., via a network exposure function (NEF)) to interact with relevant NFs. In some embodiments, the AF may provide one or more services to a user/UE, in which, for example, a packet-based service data flow is provided to the user/UE, e.g., the streaming of video and/or audio data packets from a content provider to a subscriber of a mobile communications network. The AF may for example be attached to or part of the 3 GPP Policy and Charging (PCC) architecture and may be specified in one or more particular 3GPP Technical Specifications. 14

In some embodiments, the various AF nodes and NF nodes that may be described herein may be referred to by their function names and/or more generally as network nodes and/or nodes.

A node described herein may include physical components, such as processors, allocated processing elements, or other computing hardware, computer memory, communication interfaces, and other supporting computing hardware. The node may use dedicated physical components, or the node may be allocated use of the physical components of another device, such as a computing device or resources of a datacenter, in which case the node may be said to be virtualized. A node may be associated with multiple physical components that may be located either in one location, or may be distributed across multiple locations.

An indication generally may explicitly and/or implicitly indicate the information it represents and/or indicates. Implicit indication may for example be based on position and/or resource used for transmission. Explicit indication may for example be based on a parametrization with one or more parameters, and/or one or more index or indices corresponding to a table, and/or one or more bit patterns representing the information.

In some embodiments, the term “dedicated” may be interchangeable with the term “isolated” and/or “reserved”.

A network slice is identified by single network slice selection assistance information (S-NSSAI). NSSAI generally refers to a list of one or more S-NSSAIs. Each S-NSSAI may be defined by values conveyed in an S-NSSAI information element (IE).

In some embodiments, a network slice is formed of a plurality of resources (e.g., computer, storage, network resources) e.g., from a resource pool. In some embodiments, at least one first resource is shared with at least one other consumer or user. In some embodiments, the at least one first resource forming the network slice is a dynamic resource type, the dynamic resource type being different from a dedicated resource type. In some embodiments, at least one second resource forming the network slice is a dedicated resource type which is not shared with any other consumers and/or users to e.g., as discussed above, provide for dynamic resource management within a shared slice while allowing certain resources to be not shared, 15 i.e., dedicated to a specific consumer that may desire complete isolation at the control plane and user plane.

Note also that some embodiments of the present disclosure may be supported by standard documents disclosed in Third Generation Partnership Project (3GPP) technical specifications. That is, some embodiments of the description can be supported by the above documents. In addition, all the terms disclosed in the present document may be described by the above standard documents.

Note that although terminology from one particular wireless system, such as, for example, 3 ^rd Generation Partnership Project (3GPP), Long Term Evolution (LTE), 5 ^th Generation (5G) and/or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation 3GPP 6th Generation (6G) or later Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

It should be understood that the indicators, flags, events and/or messages discussed in the present disclosure may have any name and may not be limited to the specific names used herein, which may be exemplary and/or descriptive, such as, “reservation IE”, “SMFDedicatedID”, and “available for reservation” since the indicator, flag, event or message may, for example, be given another name in a technical specification, such as a 3GPP Technical Specification (TS) even though the use/function is as disclosed in the present disclosure.

Note further, that functions described herein as being performed by an AMF, SMF, NSSF and NRF described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein. 16

Referring to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 1 a schematic diagram of the system 10, according to one embodiment, constructed in accordance with the principles of the present disclosure. The system 10 in FIG. 1 is a non-limiting example and other embodiments of the present disclosure may be implemented by one or more other systems and/or networks. Referring to FIG. 1, system 10 includes UEs such as UE 12a and UE 12b and an access network, such as a radio access network (RAN) 14.

The RAN 14 is connectable to a core network over a wired and/or wireless connection. The core network (and/or system 10) may include one or more network nodes (NN) 15 (e.g., NN 15a, 15b, 15c, 15d, referred to collectively as NN 15). NNs 15 may include (and/or be) one or more of the following: a mobility management node, such as an AMF node 16, a session management node, such as SMF node 18, a network slice selection function (NSSF) node 20 and an NRF node 22.

It should be understood that the system 10 may include numerous nodes of those shown in FIG. 1, as well as additional nodes not shown in FIG. 1. In addition, the system 10 may include many more connections/interfaces than those shown in FIG. 1.

The system 10 may include one or more nodes having a selector 24, determiner 26, dedicator 28 and reserver 30.

AMF node 16 is configured to include a selector 24 configured to perform any step and/or task and/or function and/or method and/or feature described in the present disclosure, e.g., as a result of a registration of a user equipment (UE), determine to identify a network slice based at least in part on information comprising an indication that at least one network function (NF) type is to be a dedicated resource for the network slice; and indicate the identified network slice as an allowed network slice supported for the UE.

SMF node 18 is configured to include a determiner 26 configured to perform any step and/or task and/or function and/or method and/or feature described in the present disclosure, e.g., as a result of a registration of a user equipment (UE), determine to identify a network slice based at least in part on information comprising an indication that at least one network function (NF) type is to be a dedicated resource 17 for the network slice; and indicate the identified network slice as an allowed network slice supported for the UE.

In one embodiment, a NSSF node 20 is configured to include a dedicator 28 configured to perform any step and/or task and/or function and/or method and/or feature described in the present disclosure, e.g., request to register a profile for the NF at a network repository function (NRF), the profile comprising an information element (IE) indicating one of that the NF is (i) available as a dedicated resource and (ii) is reserved as the dedicated resource.

In one embodiment, a NRF node 22 includes a reserver 30 that is configured to perform any step and/or task and/or function and/or method and/or feature described in the present disclosure, e.g., register and/or update a profile for a network function (NF) to comprise information indicating one of that the NF is (i) available as a dedicated resource and (ii) is reserved as the dedicated resource.

Example implementations, in accordance with some embodiments, of AMF node 16, SMF node 18, NSSF node 20 and NRF node 22, which may include any of the devices/nodes discussed herein and will now be described with reference to FIG.

2.

The AMF node 16 includes a communication interface 32, processing circuitry 34, and memory 36. The communication interface 32 may be configured to communicate with any of the nodes in the system 10 according to some embodiments of the present disclosure. In some embodiments, the communication interface 32 may be formed as or may include, for example, one or more radio frequency (RF) transmitters, one or more RF receivers, and/or one or more RF transceivers, and/or may be considered a radio interface. In some embodiments, the communication interface 32 may also include a wired interface.

The processing circuitry 34 may include one or more processors 38 and memory, such as, the memory 36. In particular, in addition to a traditional processor and memory, the processing circuitry 34 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 38 may be configured to access (e.g., write to and/or read from) the memory 36, which may 18 comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Thus, the AMF node 16 may further include software stored internally in, for example, memory 36, or stored in external memory (e.g., database) accessible by the AMF node 16 via an external connection. The software may be executable by the processing circuitry 34. The processing circuitry 34 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., AMF node 16. The memory 36 is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software may include instructions stored in memory 36 that, when executed by the processor 38 and/or selector 24 causes the processing circuitry 34 and/or configures the AMF node 16 to perform the processes described herein with respect to the AMF node 16 (e.g., processes described with reference to FIG. 3 and/or FIG. 7 and/or any of the other figures).

The SMF node 18 includes a communication interface 40, processing circuitry 42, and memory 44. The communication interface 40 may be configured to communicate with the UE 12 and/or other elements in the system 10 according to some embodiments of the present disclosure. In some embodiments, the communication interface 40 may be formed as or may include, for example, one or more radio frequency (RF) transmitters, one or more RF receivers, and/or one or more RF transceivers, and/or may be considered a radio interface. In some embodiments, the communication interface 40 may also include a wired interface.

The processing circuitry 42 may include one or more processors 46 and memory, such as, the memory 44. In particular, in addition to a traditional processor and memory, the processing circuitry 42 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 46 may be configured to access (e.g., write to and/or read from) the memory 44, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer 19 memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Thus, the SMF node 18 may further include software stored internally in, for example, memory 44, or stored in external memory (e.g., database) accessible by the SMF node 18via an external connection. The software may be executable by the processing circuitry 42. The processing circuitry 42 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by the SMF node 18. The memory 44 is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software may include instructions stored in memory 44 that, when executed by the processor 46 and/or determiner 26, causes the processing circuitry 42 and/or configures the SMF node 18 to perform the processes described herein with respect to the SMF node 18 (e.g., processes described with reference to FIG. 4 and/or any of the other figures).

The NSSF node 20 includes a communication interface 48, processing circuitry 50, and memory 52. The communication interface 48 may be configured to communicate with any of the nodes in the system 10 according to some embodiments of the present disclosure. In some embodiments, the communication interface 48 may be formed as or may include, for example, one or more radio frequency (RF) transmitters, one or more RF receivers, and/or one or more RF transceivers, and/or may be considered a radio interface. In some embodiments, the communication interface 48 may also include a wired interface.

The processing circuitry 50 may include one or more processors 54 and memory, such as, the memory 52. In particular, in addition to a traditional processor and memory, the processing circuitry 50 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 54 may be configured to access (e.g., write to and/or read from) the memory 52, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) 20 and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Thus, the NSSF node 20 may further include software stored internally in, for example, memory 52, or stored in external memory (e.g., database) accessible by the NSSF node 20 via an external connection. The software may be executable by the processing circuitry 50. The processing circuitry 50 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by the NSSF node 20. The memory 52 is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software may include instructions stored in memory 52 that, when executed by the processor 54 and/or dedicator 28, causes the processing circuitry 50 and/or configures the NSSF node 20 to perform the processes described herein with respect to the NSSF node 20, such as FIG. 5.

The NRF node 22 includes a communication interface 56, processing circuitry 58, and memory 60. The communication interface 56 may be configured to communicate with any of the nodes in the system 10 according to some embodiments of the present disclosure. In some embodiments, the communication interface 56 may be formed as or may include, for example, one or more radio frequency (RF) transmitters, one or more RF receivers, and/or one or more RF transceivers, and/or may be considered a radio interface. In some embodiments, the communication interface 56 may also include a wired interface.

The processing circuitry 58 may include one or more processors 62 and memory, such as, the memory 60. In particular, in addition to a traditional processor and memory, the processing circuitry 58 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 62 may be configured to access (e.g., write to and/or read from) the memory 60, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory). 21

Thus, the NRF node 22 may further include software stored internally in, for example, memory 60, or stored in external memory (e.g., database) accessible by the NRF node 22 via an external connection. The software may be executable by the processing circuitry 58. The processing circuitry 58 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by the NRF node 22. The memory 60 is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software may include instructions stored in memory 60 that, when executed by the processor 62 and/or reserver 30, causes the processing circuitry 58 and/or configures the NRF node 22 to perform the processes described herein with respect to the NRF node 22, such as FIG. 6.

In FIG. 2, the connection between the devices AMF node 16, SMF node 18, NSSF node and NRF node 22 is shown without explicit reference to any intermediary devices or connections. However, it should be understood that intermediary devices and/or connections may exist between these devices, although not explicitly shown.

Although FIG. 2 shows selector 24, determiner 26, dedicator 28 and reserver 30, as being within a respective processor, it is contemplated that these elements may be implemented such that a portion of the elements is stored in a corresponding memory within the processing circuitry. In other words, the elements may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

In some embodiments, the inner workings of AMF node 16, SMF node 18, NSSF node and NRF node 22 may be as shown in FIG. 2 and independently, the surrounding network topology may be that of FIG. 1.

FIG. 3 is a flowchart of an example process in an AMF node 16 according to some embodiments of the present disclosure. One or more Blocks and/or functions and/or methods performed by the AMF node 16 may be performed by one or more elements of AMF node 16 such as by selector 24 in processing circuitry 34, memory 36, processor 38, communication interface 32, etc. according to the example process/method. The example process includes as a result of a registration of a user equipment (UE), determining (Block S100), such as via selector 24, processing circuitry 34, memory 36, processor 38, and/or communication interface 32, 22 to identify a network slice based at least in part on information comprising an indication that at least one network function (NF) type is to be a dedicated resource for the network slice. The process includes indicating (Block S102), such as via selector 24, processing circuitry 34, memory 36, processor 38, and/or communication interface 32, the identified network slice as an allowed network slice supported for the UE.

In some embodiments, when the information about the network slice comprises the indication that the at least one NF type is to be the dedicated resource for the network slice, determining, such as via selector 24, processing circuitry 34, memory 36, processor 38, and/or communication interface 32, to include only a single network slice as the allowed network slice for the UE; otherwise, determining to include a list of one or more network slices as the allowed network slice for the UE.

In some embodiments, the information comprises an information element (IE) configured at the network node, the IE comprising the indication of the at least one NF type and a network slice identifier identifying the network slice that requires the dedicated resource. In some embodiments, the at least one NF type comprises at least one of an access and mobility management function (AMF) and a session management function (SMF) that is to form the network slice.

In some embodiments, determining to identify the network slice based at least in part on the information comprising the indication that the at least one NF type is to be the dedicated resource for the network slice comprises: selecting, such as via selector 24, processing circuitry 34, memory 36, processor 38, and/or communication interface 32, the network slice out of a plurality of network slices supported for the UE based at least in part on which ones and/or how many NF types are to be dedicated resources for the network slices. In some embodiments, the network node comprising an access and management function (AMF).

In some embodiments, registering and/or updating, such as via selector 24, processing circuitry 34, memory 36, processor 38, and/or communication interface 32, a profile for the AMF at a network repository function (NRF), the profile comprising an information element (IE) indicating one of that the AMF is (i) available as a dedicated resource for a network slice and (ii) is reserved as the dedicated resource for a particular network slice. In some embodiments, indicating the identified network 23 slice as the allowed network slice comprises, sending, such as via selector 24, processing circuitry 34, memory 36, processor 38, and/or communication interface 32, an indication of the identified network slice as the allowed network slice to the UE in a registration accept message.

In some embodiments, the process further includes determining, such as via selector 24, processing circuitry 34, memory 36, processor 38, and/or communication interface 32, that the AMF is able to serve the allowed network slice based on whether the AMF is currently reserved or is available as the dedicated resource for the allowed network slice and if the AMF is available as the dedicated resource updating a profile of the AMF at a network repository function to indicate a reservation of the AMF as the dedicated resource for the allowed network slice. In some embodiments, the method further includes determining, such as via selector 24, processing circuitry 34, memory 36, processor 38, and/or communication interface 32, that the AMF is unable to serve the allowed network slice based on that the AMF is currently reserved for a different network slice or is unavailable as the dedicated resource and as a result of the determination that the AMF is unable to serve the allowed network slice, selecting a target AMF that is able to serve the allowed network slice. In some embodiments, selecting comprises selecting the target AMF that is currently reserved as the dedicated resource for the allowed network slice or that is available as the dedicated resource.

In some embodiments, determining that the at least NF type that is to be the dedicated resource for the network slice comprises a session management function (SMF) and as a result of PDU session establishment request, selecting, such as via selector 24, processing circuitry 34, memory 36, processor 38, and/or communication interface 32, a target SMF that is able to serve the allowed network slice and indicating, such as via selector 24, processing circuitry 34, memory 36, processor 38, and/or communication interface 32, to the selected target SMF to operate as the dedicated resource for the allowed network slice associated with the PDU session establishment request. In some embodiments, indicating to the selected target SMF comprises sending a Nsmf_PDUSession_CreateSMContext request comprising an indicator indicated to operate as the dedicated resource for the allowed network slice associated with the PDU session establishment request. 24

FIG. 4 is a flowchart of an example process in SMF node 18 according to some embodiments of the present disclosure. One or more Blocks and/or functions and/or methods performed by the SMF node 18 may be performed by one or more elements of SMF node 18 such as determiner 26 in processing circuitry 42, memory 44, processor 46, communication interface 40, etc. according to the example process/method. The example process includes requesting (Block S104), such as via determiner, processing circuitry 42, memory 44, processor 46, communication interface 40, to register a profile for the NF at a network repository function (NRF), the profile comprising an information element (IE) indicating one of that the NF is (i) available as a dedicated resource and (ii) is reserved as the dedicated resource.

In some embodiments, the method further includes receiving, such as via determiner, processing circuitry 42, memory 44, processor 46, communication interface 40, an indication to operate as the dedicated resource for a network slice associated with a protocol data unit (PDU) session establishment request from a user equipment (UE). In some embodiments, when the IE indicates that the NF is available as the dedicated resource and as a result of a PDU session being established for the UE in the network slice, determining, such as via determiner, processing circuitry 42, memory 44, processor 46, communication interface 40, to update the profile at the NRF to indicate that the NF is reserved as the dedicated resource for the network slice. In some embodiments, the NF is a session management function (SMF)

FIG. 5 is a flowchart of an example process in a NSSF node 20 according to some embodiments of the present disclosure. One or more Blocks and/or functions and/or methods performed by the NSSF node 20 may be performed by one or more elements of NSSF node 20 such as by dedicator 28 in processing circuitry 50, memory 52, processor 54, communication interface 48, etc. according to the example process/method. The example process includes as a result of a registration of a user equipment (UE), determining (Block S106), such as via dedicator 28, processing circuitry 50, memory 52, processor 54 and/or communication interface 48, to identify a network slice based at least in part on information comprising an indication that at least one network function (NF) type is to be a dedicated resource for the network slice. The process includes indicating (Block S108), such as via dedicator 28, 25 processing circuitry 50, memory 52, processor 54 and/or communication interface 48, the identified network slice as an allowed network slice supported for the UE.

In some embodiments, when the information about the network slice comprises the indication that the at least one NF type is to be the dedicated resource for the network slice, determining, such as via dedicator 28, processing circuitry 50, memory 52, processor 54 and/or communication interface 48, to include only a single network slice as the allowed network slice for the UE; otherwise, determining to include a list of one or more network slices as the allowed network slice for the UE.

In some embodiments, the information comprises an information element (IE) configured at the network node, the IE comprising the indication of the at least one NF type and a network slice identifier identifying the network slice that requires the dedicated resource. In some embodiments, the at least one NF type comprises at least one of an access and mobility management function (AMF) and a session management function (SMF) that is to form the network slice.

In some embodiments, determining to identify the network slice based at least in part on the information comprising the indication that the at least one NF type is to be the dedicated resource for the network slice comprises: selecting, such as via dedicator 28, processing circuitry 50, memory 52, processor 54 and/or communication interface 48, the network slice out of a plurality of network slices supported for the UE based at least in part on which ones and/or how many NF types are to be dedicated resources for the network slices. In some embodiments, the network node comprising a network slice selection function (NSSF). In some embodiments, indicating the identified network slice as the allowed network slice comprises, sending, such as via dedicator 28, processing circuitry 50, memory 52, processor 54 and/or communication interface 48, an indication of the identified network slice as the allowed network slice to a mobility management function (AMF) as a result of a request from the AMF for network slice selection information for the UE.

FIG. 6 is a flowchart of an example process in NRF node 22 according to some embodiments of the present disclosure. One or more Blocks and/or functions and/or methods performed by the NRF node 22 may be performed by one or more elements of NRF node 22 such as reserver 30 in processing circuitry 58, memory 60, processor 62, communication interface 56, etc. according to the example 26 process/method. The example process includes registering and/or updating (Block SI 10), such as via reserver 30, processing circuitry 58, memory 60, processor 62 and/or communication interface 56, a profile for a network function (NF) to comprise information indicating one of that the NF is (i) available as a dedicated resource and (ii) is reserved as the dedicated resource.

In some embodiments, the information is an information element (IE) associated with the NF. In some embodiments, the network node comprises a network slice selection function (NSSF). In some embodiments, when the information indicates that the NF is available as the dedicated resource, determining, such as via reserver 30, processing circuitry 58, memory 60, processor 62 and/or communication interface 56, to reserve the NF as the dedicated resource for an application server (AS) providing a roaming service and updating, such as via reserver 30, processing circuitry 58, memory 60, processor 62 and/or communication interface 56, the profile for the NF to indicate that the NF is reserved as the dedicated resource for the AS. In some embodiments, as a result of a discovery request identifying the AS, allocating, such as via reserver 30, processing circuitry 58, memory 60, processor 62 and/or communication interface 56, the NF to the AS when the NF is available as the dedicated resource or the NF is currently reserved as the dedicated resource for the identified AS.

FIG. 7 is a flowchart of an example process (i.e., method) in a first network node e.g., comprising an AMF node 16 according to some embodiments of the present disclosure. One or more Blocks and/or functions and/or methods performed by the AMF node 16 may be performed by one or more elements of AMF node 16 such as by selector 24 in processing circuitry 34, memory 36, processor 38, communication interface 32, etc. according to the example process/method. The example process includes receiving (Block SI 12), such as via selector 24, processing circuitry 34, memory 36, processor 38, and/or communication interface 32, a wireless device registration request comprising network slice information associated with a requested network slice; selecting (Block SI 14), such as via selector 24, processing circuitry 34, memory 36, processor 38, and/or communication interface 32, any one of the first network node 15a and a second network node 15b as a dedicated resource for the requested network slice based at least in part on the received wireless 27 device registration request; and transmitting (Block SI 16), such as via selector 24, processing circuitry 34, memory 36, processor 38, and/or communication interface 32, a wireless device registration response based at least on the selected any one of the first network node 15a and the second network node 15b.

In some embodiments, the network slice information comprises an indication that at least one network node 15 (e.g., an AMF configured with the network slice information) is to be the dedicated resource for the requested network slice.

In some other embodiments, the method further includes transmitting a profile registration request to a third network node 15c to register a profile of the first network node 15a at the third network node 15c.

In one embodiment, the profile includes an information element (IE) indicating whether the first network node 15a is available for reservation.

In another embodiment, the method further includes receiving a profile registration response, from the third network node 15c, including a list of network nodes available for reservation.

In some embodiments, the third network node 15c comprises a network repository function, NRF, node 22.

In some other embodiments, the method further includes: transmitting, in response to the wireless device registration request, a discovery request to the third network node 15c to discover at least one network node indicated as one dedicated resource; and receiving a discovery response, from the third network node 15c, including a list of the at least one network node indicated as one dedicated resource.

In one embodiment, selecting any one of the first network node 15a and the second network node 15b as the dedicated resource for the requested network slice includes: selecting an existing network node that is already reserved for the requested network slice, the existing network node being any one of the first network node 15a and the second network node 15b; and selecting another network node that is available to be reserved for the requested network slice.

In another embodiment, the method further includes: when the first network node 15a is selected as the dedicated resource, transmitting the wireless device 28 registration response including an indication that the first network node 15a is the dedicated resource; and when the second network node 15b is selected as the dedicated resource, transmitting the wireless device registration response including an indication to reroute the wireless device registration request to the selected second network node 15b.

In some embodiments, the method further includes: receiving a protocol data unit, PDU, session establishment request; and in response to the PDU session establishment request, selecting a fourth network node 15d, the fourth network node 15d comprising a session management function, SMF, node 18 and being another dedicated resource.

In some other embodiments, the method further includes transmitting a context creation request to the fourth network node 15d. The context creation request includes a dedicated session management function (SMF) indicator configured to trigger the fourth network node 15d to be dedicated for the requested network slice. The requested network slice is associated with the PDU session establishment request.

In one embodiment, the first network node 15a comprises a first access and mobility function (AMF) node 16a and the second network node 15b comprises a second AMF node 16b.

Having generally described arrangements for dynamic resource management within a shared slice, a more detailed description of some of the embodiments are provided as follows with reference to FIGS. 8-14, and which may be implemented by one or more of the nodes (e.g., NNs 15) discussed herein, such as AMF node 16, SMF node 18, NSSF node 20 and NRF node 22.

The call flow diagram of FIG. 8 shows an example impact on the UE registration call flow to support the above solution.

Registration Procedure

FIG. 8 depicts an example of a general UE registration procedure according to some embodiments of the present disclosure. In particular, at step S200 a registration request is received by RAN 14. At step S202, AMF selection is performed. At step S204, a registration request is transmitted by RAN 14. At step S206, a request for context transfer is transmitted by AMF 16a, and at step S208, a response corresponding to the request for context transfer is received by AMF 16a. At step 29

S210, an identity request is transmitted by UE 12 to AMF 16a, and an identity response is received by the UE 12 at step S212. At step S214, AUSF selection is performed by AMF 16a.

At step S216 one or more steps associated with authentication security is performed. At step S218 a message, e.g., including

Namf_Communication_RegistrationStatusUpdate is transmitted from AMF 16a to AMF 16b. At step S220, an identity request and/or identity response is transmitted/received by UE 12. At step S222 a message is transmitted/received, e.g., including N5g-eir_EquipmentIdentityCheck_Get. At step S224, UDM selection is performed by AMF 16a. At step S226, a message is transmitted/received by AMF 16a, e.g., including a Nudm_UECM_Registration, and at step S228, a message is transmitted/received by AMF 16a, e.g., including (and/or associated with) Nudm_SDM_Get (). At step S230, AMF processing is performed by AMF 16a, and a subscription request is transmitted to NN 15 (e.g., UDM). At step S234, a notification is transmitted to AMF 16b. At step S236, a PCF selection is performed by AMF 16a, and at step S238, a request to unsubscribe (e.g., Nudm_SDM_Unsubscribe) is transmitted to NN 15a. At step S240, a policy association is established/modified, and at step S242, a request to update/release context is transmitted by AMF 16a to SMF 18. In sum, FIG. 8 depicts a registration procedure, e.g., described in 3GPP TS 23.502, section 4.2.2.2.2, but with the addition of a new AMF processing procedure described in more detail below:

An example of the new handling in AMF node 16a for processing the new IE associated with S-NSSAI related to dedicated resources is described. The processing implemented by AMF node 16a (e.g., step S230) shown in FIG. 8) as AMF processing occurring after the new AMF (i.e., AMF 16a) receives the Nudm_SDM_Get service response in step S228 and before the new AMF sends a Nudm_SDM_Subscribe request in step S232). The example handling may be related to the requested S-NSSAI and can be explained as follows (note that some embodiments may perform the AMF processing for other types of S-NSSAI, such as configured and/or subscribed S-NSSAI):

-If the AMF configuration option is used, and there is no additional IE related to AMF and/or SMF dedicated resources configured for any of the requested and 30 allowed S-NSSAI, then the rest of the call flow continues as per the normal registration procedure since e.g., dedicated resources are not requested, and the below steps are not executed.

-If the NSSF option is supported as described above, then it may be assumed that NSSF node 20 includes the Allowed S-NSSAI. In this example, this step may be skipped. Otherwise, if the UE 12 requested one or more S-NSSAI that requires dedicated resources then the AMF node 16a may perform one or more of the following:

-Upon receiving requested S-NSSAI in the registration request message from RAN 14, the AMF node 16a determines whether a requested S-NSSAI requires both AMF and SMF dedicated resources. If the requested S-NSSAI requires both, AMF node 16a selects one of the requested S-NSSAI that requires both AMF and SMF dedicated resources, includes it in the Allowed S-NSSAI and continues the rest of the call flow depicted. In a one embodiment, the AMF node 16 selects one S- NSSAI that requires both AMF and SMF dedicated resources and/or includes the one S-NSSAI in the Allowed S-NSSAI. The Allowed S-NSSAI is included in the registration accept message to the UE 12 and the registration complete message to the RAN 14.

-If there is no requested S-NSSAI that requires both AMF and SMF dedicated resources, then AMF node 16a determines whether there is one or more requested S-NSSAI that requires dedicated SMF resources. If the requested S-NSSAI requires dedicated SMF resources, the AMF node 16 selects one requested S-NSSAI that requires dedicated SMF resources, includes it in the Allowed S-NSSAI, and/or continues the rest of the call flow shown. In one embodiment, the AMF node 16 selects one S-NSSAI that requires dedicated SMF resources and/or includes that one in the Allowed S-NSSAI.

-If there is no requested S-NSSAI that requires dedicated SMF resources, AMF node 16a determines whether there is one or more requested S- NSSAI that requires dedicated AMF resources. If there is one or more requested S- NSSAI that requires dedicated AMF resources, the AMF node 16a selects one of the one or more requested S-NSSAI and includes it in the Allowed S-NSSAI and/or continues with the rest of the call flow shown. 31

- One (or more than one) of the above selection steps and inclusion steps may be executed by the AMF node 16a depending on whether the associated conditions are satisfied as outlined above. In some embodiments, one S-NSSAI requiring dedicated resources is returned in the Allowed S-NSSAI. In some other embodiments, no other S-NSSAI is included in the Allowed S-NSSAI.

-If there is a request/requirement for dedicated SMF resources, then this will be acted upon when there is a UE protocol/packet data unit (PDU) establishment procedure to be invoked for the Allowed S-NSSAI.

-If no dedicated AMF resources are required for the requested (and Allowed) S-NSSAI, then the rest of the registration call flow executes.

-On the other hand, if there is a dedicated AMF required for the requested (and Allowed) S-NSSAI, then the following sub-actions may be performed:

-If the AMF node 16a selected by RAN 14 in step S202 for the UE registration is already dedicated to the requested S-NSSAI by the UE 12, then this AMF node 16a can be used, and/or the rest of registration call flow executes.

-On the other hand, if the AMF node 16a selected by RAN 14 cannot be used for requested S-NSSAI by the UE 12, or if the AMF node 16a is already reserved for a different S-NSSAI then, a new AMF node 16 is allocated by this AMF node 16a.

-If the NSSF node 20 indicated an AMF node 16 that can be used for the Allowed S-NSSAI, then it will be used, and the AMF node 16 profile is updated at e.g., NRF node 22, after a successful registration with the S-NSSAI in the reserved IE (this step is not shown in FIG. 8). Otherwise, the registration with AMF re-allocation applies, as shown in FIG. 9.

Registration AMF Re-allocation

FIG. 9 depicts an example registration AMF re-allocation procedure that may be based on 3GPP TS 23.502, but with the added behavior in AMF node 16a to support AMF isolation/dedicated resource requirement.

The new AMF behavior is described below with reference to FIG. 9:

In step S244, the AMF node 16a registers its profile in NRF node 22, A new IE which is descriptively called “dedicated for reservation” purposes and “reservation IE” is part of the new AMF node 16 profile and may be populated 32 with “Available for reservation” indication. This is based on the AMF nodes 16 being configured by the operator (e.g., via the IE that is configured in AMF or in NSSF, which indicates for an S-NSSAI that dedicated AMF and/or SMF is requested/requested) for reservation purposes as opposed to being shared e.g., amongst multiple services or consumers. In some embodiments, this IE may not be registered by the AMF node 16 in the NRF 22 if it is not configured for reservation.

In step S246, another AMF node 16b registers its profile as well.

In step S248, a non-access stratum (NAS) Registration message (i.e., a wireless device registration request) is received by RAN 14. This corresponds to step 1 in section 4.2.2.2.3 in 3 GPP TS 23.502.

In step S250, the selected source AMF node 16a determines (as described in the Registration procedure) that a new target AMF node 16b is to be discovered. This target AMF node 16b should be dedicated for reservation. The source AMF node 16a issues an NRF discovery service request to NRF node 22 to locate a new AMF node 16b that is suitable for this UE 12 for isolation purposes.

In step S252, the source AMF node 16a receives a list of suitable AMFs nodes 16 that are available.

In step S254, the source AMF node 16a requiring a dedicated AMF locates either an existing AMF node 16 that is already reserved for the requested S-NSSAI for the registering UE 12 if one is available; or the source AMF node 16a selects an AMF node 16 that is available for use to be reserved for the requested S-NSSAI. It the AMF node 16 does require a dedicated AMF then any AMF node 16 without the reservation IE may be considered a candidate for selection.

In step S256, the source AMF node 16a selects a target AMF node 16b, and then the source AMF node 16a send a reroute message to RAN 14 to reroute the NAS message.

In step S258, a NAS registration message is sent by RAN 14 to the target AMF node 16a. 33

In step S260, the target AMF node 16b that is dedicated for a specific/requested S-NSSAI updates its profile with the NRF node 22 so the AMF node 16b stores in the reservation IE the requested S-NSSAI.

PDU Establishment Procedure to Support Dedicated SMF

FIG. 10 illustrates example modifications in the PDU session establishment procedure to support a dedicated SMF for a specific dedicated SMF.

An example of the modifications to the PDU session establishment procedure according to some embodiments are explained below:

At step S262, a PDU Session Establishment Request is transmitted by UE 12 to AMF 16.

At step S264, AMF node 16 performs an SMF selection procedure as follows:

- If there is no need for a dedicated SMF resource as detected by AMF node 16 (explained above) then the existing call flow executes according to normal procedures.

- On the other hand, if there is a need for a dedicated SMF as detected by AMF node 16 (explained above), then a new discovery procedure shown after the PDU establishment procedure is adopted.

At step S266, the Nsmf_PDUSession_CreateSMContext service operation is extended to pass a Dedicated SMF indicator to the SMF node 18. This indicator instructs the SMF node 18 to be solely used for the S-NSSAI associated with the PDU Establishment.

In addition, if a dedicated SMF resource is required, the AMF node 16 includes the S-NSSAI and available information in step S266 to enable SMF node 18 to successfully perform its task.

At step S268 a subscription retrieval/subscription for updates is performed. At step S270, a context response is received at AMF 16. At step S272, PDU session authentication/authorization is performed. At step S274, PCF is selected by SMF 18, and a policy association is established/modified at step S276. At step S278, UPF selection is performed by SMF 18, and at step S280, a policy association is modified.

In addition, at step S294 shown in the SMF discovery procedure (shown in FIG. 11), the SMF node 18 that is dedicated for a specific/requested S-NSSAI 34 updates its profile with the NRF node 22 so the SMF node 18 stores in the reservation IE the requested S-NSSAI.

In some embodiments, step S294 is performed after successful PDU establishment to make sure that the selected SMF node 18 is not used later except for UEs 12 requesting that same S-NSSAI. This is a new behavior at least in SMF.

FIG. 11 shows a call flow depicting the example SMF selection procedure by AMF node 16. This same principle in AMF re-allocation and selection of a new AMF node 16 (e.g., FIG. 9) may be equally applied here, as well for SMF selection. The details of an example SMF selection algorithm is shown in FIG. 11. At step S282 a registration request transmitted, e.g., by SMF 18 to NRF 22. At step S284, a PDU Session Establishment Request is transmitted by UE 12. At step S286, a discovery service message is transmitted to NRF 22, and a corresponding response is received by AMF 16 at step S288. At step S290, one or more of the following steps may be performed: If an SMF dedicated for the requested S-NSSAI is available, then it is selected. If no SMF is available, then AMF selects an SMF available for reservation. If there is no need for a dedicated SMF as depicted by the absence of SMFDedicatedID indicator, then AMF selects an SMF that does not have a Reservation IE. At step S292, a PDU establishment procedure, e.g., as in 3GPP TS 23.502, may continue. Further, at step S294, registration is performed (e.g., requesting to store the S-NSSAI the SMF is dedicated for in the Reservation IE.

SMF nodes 18 to be dedicated for reservation may be configured by an operator for that purpose, e.g., so they can register their profile accordingly.

The section below shows the extension to the AMF’s Nsmf_PDUSession_CreateSMContext service operation so as to provide support for Dedicated SMF.

Nsmf_PDUSession_CreateSMContext service operation

Service operation name: Nsmf_PDUSession_CreateSMContext.

Description: It creates an AMF-SMF association to support a PDU Session.

Input, Required: subscription permanent identifier (SUPI) or permanent equipment identifier (PEI), data network name (DNN), AMF ID (AMF Instance ID), radio access technology (RAT) Type, Serving Network (public land mobile network 35

(PLMN) ID, or PLMN ID and network identification (NID), e.g., clause 5.18 of 3GPP TS 23.501).

Input, Optional: PEI, S-NSSAI(s) including SMFDEdidcatedID where applicable, PDU Session Id, N1 SM container, UE location information, UE Time Zone, AN type, H-SMF identifier/address, list of alternative H-SMF(s) if available, old PDU Session ID (if the AMF also received an old PDU Session ID from the UE as specified in clause 4.3.5.2), Subscription For PDU Session Status Notification, Subscription for DDN Failure Notification, NEF Correlation ID, indication that the SUPI has not been authenticated, PCF ID, PCF Group ID, DNN Selection Mode, UE PDN Connection Context, GPSI, UE presence in local area data network (LADN) service area, globally unique AMF ID (GUAMI), backup AMF(s) (if NF Type is AMF), Trace Requirements, Control Plane CIoT 5GS Optimization indication, Small Data Rate Control Status, APN Rate Control Status. Backup AMF(s) sent only once by the AMF to the SMF in its first interaction with the SMF, UE's Routing Indicator or UDM Group ID for the UE, evolved packet system (EPS) Bearer Status. Target ID (for EPS to 5GS handover), "Invoke NEF" flag, additional following three for SM context transfer: SMF transfer indication, Old SMF ID, session management (SM) context ID in old SMF (e.g., clause 4.26.5.3), handover (HO) Preparation Indication. Multi access (MA) PDU request indication, MA PDU Network-Upgrade Allowed indication, Indication on whether the UE is registered in both accesses.

Output, e.g., which may be required: Result Indication, and if successful SM Context ID.

Output, which may be optional: Cause, PDU Session ID, N2 SM information, N1 SM container, S-NSSAI(s).

When the PDU Session is for Emergency services for a UE without USIM, the AMF node 16 provides the PEI and not the SUPI as identifier of the UE. When the PDU Session is for Emergency services of an unauthenticated UE with a universal subscriber identity module (USIM), the AMF node 16 may provide both the SUPI and the PEI and may provide an indication that the SUPI has not been authenticated. 36

Extending the Model for RVAS Service providers

RVAS (i.e., roaming value-added services) are third party providers providing roaming services for inbound roamers on behalf of roaming partners of PLMNs and when the operators are small enough to be able to implement these roaming services on their own.

In these cases, the PLMN partner using RVAS SMFs 18 for example, which is a typical use case, would like to confine all traffic from RVAS SMF 18 to one or more of their SMFs 18, and be able to restrict that SMF 18 for RVAS SMF 18.

Some embodiments may extend the NRF 22 functionality as follows, using the call flow diagram of FIGS. 12-14 as examples:

FIGS. 12-14 illustrate an example of how the NRF 22 functionality may be extended to support being able to restrict traffic to only one or a subset of RVAS SMFs 18. FIG. 12 illustrates the H-NRF 22c dedicating H-SMF 18c for an RVAS and declaring it as available for registration according to some of the embodiments described above. The H-NRF 22C ensures that this H-SMF 18C is used exclusively for RVAS traffic using same approach depicted in non-RVAS scenarios. At step S296, a profile may be registered and/or the registered profile (e.g., a registered R- SMF profile) may include an indication that the SMF is selected and/or used for outbound roamers. The same R-SMF can be shared for multiple PLMNs. At step S298, a registration may be performed, e.g., including an SMF profile with additional IE for selection criteria for roaming selection in home routed scenarios) as described in step S296. At step S300 a registration is performed/requested. At step S302, H- NRF 22c determines that the NRF needs to process information. At step S304, H- NRF 22c determines that the NRF needs to also dedicate an H-SMF only for an RVAS and declare it as available for reservation exclusively for RVAS as described previously. At step S306, a registration is performed and/or requested. At step S308, a PDU session establishment request is made by UE 12. A discovery service request is made by AMF 16 at step S309, and a corresponding response received by AMF 16 at step S310. Another discovery service request is transmitted to V-NRF 22a at step S312, and V-NRF 22a transmits a corresponding response to H-NRF 22c. At step S316, an R-SMF is returned. At step S318, a response including R-SMF is transmitted 37 to V-NRF 22a, and at step S320 another response including R-SMF is transmitted to AMF 16.

FIG. 13 shows a different variant from the procedure in FIG.12 for the allocation of an available H-SMF node using similar techniques as those in non- RVAS case. At step S322 a context request, i.e.,

Nsmf_PDUSession_CreateSMContextReq(..), is made. At S324 a request to create a new PDU session is made to R-SMF 18b. At step S326, SUPI may be used to identify a target PLMN ID. A discovery service response is transmitted to H-NRF 22c at step 328, and the RVAS ID may be used to distinguish this case (i.e., the request) from local requests at step S330. The H-NRF may allocate an available H-SMF dedicated exclusively for RVAS and return it. In other words, in step S330, upon receipt at step S328 of the discovery service request from R-SMF 18b, the H-NRF 22c allocates an available H-SMF 18c, in step S330, and/or returns information about the allocation in step S332 . At step S336, H-NRF 22c updates the allocated H-SMF 18c and/or makes it reserved for the RVAS identifier (ID), which may occur after step S334. At step S334, R-SMF 18b initiates a Nsmf_PDUSession_CreatetReq towards the H-SMF 18c At step S338, H-SMF 18c determines that it is communicating with an R-SMF 18b. This PLMN interworks with RVAS -Presence of an VPLMN ID incoming request.

FIG. 14 shows an example NRF procedure. More specifically, At step S340 a registration is performed and/or requested. At step S342 a request to subscribe is made, i.e., Nnrf_NFManagement_RVASSubscribe(). At step S344, another registration is performed and/or requested, e.g., between H-SMF 18c and H-NRF 22c. At step S345, an H-SMF is dedicated (and/or determined that it is needed to be dedicated) and declared as available for reservation. At step S346 another registration is performed and/or requested, e.g., between V-SMF 18a and V-NRF 22a. At step S348, a PDU session establishment request is made by UE 12. A discovery service request is made to V-NRF 22a at step S350, and a corresponding response transmitted at step S352. Another discovery service request is made to V-NRF 22a at step S354, for the target PLMN, and a corresponding request transmitted at step S356. At step S360, an R-SMF and/or H-SMF are/is discovered, and an R-SMF returned to V-SMF. At step S362, a notification is transmitted to R-SMF, e.g., including the H-SMF. At step S364, NRF updates the allocated H-SMF and makes it exclusively reserved for 38

RVAS ID. A response, e.g., including the R-SMF is transmitted at step S366 and another response, e.g., including the R-SMF is transmitted at step S368. In other words, FIG. 14 illustrates the H-NRF 22c dedicating an H-SMF 18c for an RVAS and declaring it as available for reservation after step S344. In addition, H-NRF 22c updates the allocated H-SMF 18c and makes it reserved for RVAS ID after step S362.

In some embodiments, when the information indicates that the NF is available as the dedicated resource, determining, such as via reserver 30, processing circuitry 58, memory 60, processor 62 and/or communication interface 56, to reserve the NF as the dedicated resource for an RVAS providing a roaming value added service and updating, such as via reserver 30, processing circuitry 58, memory 60, processor 62 and/or communication interface 56, the profile for the NF to indicate that the NF is reserved as the dedicated resource for the RVAS. In some embodiments, as a result of a discovery request identifying the RVAS, allocating, such as via reserver 30, processing circuitry 58, memory 60, processor 62 and/or communication interface 56, the NF to the RVAS when the NF is available as the dedicated resource or the NF is currently reserved as the dedicated resource for the identified RVAS.

It should be understood that although the example embodiments discussed herein focus primarily on dedicated resources for AMF and SMF, the techniques disclosed herein may be beneficial for any network node, such as NF or AF, for which dedicated resources are requested according to the techniques provided in this disclosure.

The following is a list of nonlimiting example embodiments:

Embodiment Al. A method implemented in a network node, the method comprising: as a result of a registration of a user equipment (UE), determining to identify a network slice based at least in part on information comprising an indication that at least one network function (NF) type is to be a dedicated resource for the network slice; and indicating the identified network slice as an allowed network slice supported for the UE. 39

Embodiment A2. The method of Embodiment Al, when the information about the network slice comprises the indication that the at least one NF type is to be the dedicated resource for the network slice, determining to include only a single network slice as the allowed network slice for the UE; otherwise, determining to include a list of one or more network slices as the allowed network slice for the UE.

Embodiment A3. The method of any one of Embodiments Al and A2, wherein the information comprises an information element (IE) configured at the network node, the IE comprising the indication of the at least one NF type and a network slice identifier identifying the network slice that requires the dedicated resource.

Embodiment A4. The method of any one of Embodiments A1-A3, wherein the at least one NF type comprises at least one of an access and mobility management function (AMF) and a session management function (SMF) that is to form the network slice.

Embodiment A5. The method of any one of Embodiments A1-A4, wherein determining to identify the network slice based at least in part on the information comprising the indication that the at least one NF type is to be the dedicated resource for the network slice comprises: selecting the network slice out of a plurality of network slices supported for the UE based at least in part on which ones and/or how many NF types are to be dedicated resources for the network slices.

Embodiment A6. The method of any one of Embodiments A1-A5, the network node comprising an access and management function (AMF).

Embodiment A7. The method of Embodiment A6, registering and/or updating a profile for the AMF at a network repository function (NRF), the profile comprising an information element (IE) indicating one of that the AMF is (i) available as a dedicated resource for a network slice and (ii) is reserved as the dedicated resource for a particular network slice. 40

Embodiment A8. The method of any one of Embodiments A6 and A7, wherein indicating the identified network slice as the allowed network slice comprises, sending an indication of the identified network slice as the allowed network slice to the UE in a registration accept message.

Embodiment A9. The method of any one of Embodiments A6 and A8, further comprising determining that the AMF is able to serve the allowed network slice based on whether the AMF is currently reserved or is available as the dedicated resource for the allowed network slice and if the AMF is available as the dedicated resource updating a profile of the AMF at a network repository function to indicate a reservation of the AMF as the dedicated resource for the allowed network slice.

Embodiment A10. The method of any one of Embodiments A6-A9, further comprising determining that the AMF is unable to serve the allowed network slice based on that the AMF is currently reserved for a different network slice or is unavailable as the dedicated resource and as a result of the determination that the AMF is unable to serve the allowed network slice, selecting a target AMF that is able to serve the allowed network slice.

Embodiment All. The method of Embodiment A 10, wherein selecting comprises selecting the target AMF that is currently reserved as the dedicated resource for the allowed network slice or that is available as the dedicated resource. Embodiment A 12. The method of any one of Embodiments A6-A11, determining that the at least NF type that is to be the dedicated resource for the network slice comprises a session management function (SMF) and as a result of PDU session establishment request, selecting a target SMF that is able to serve the allowed network slice and indicating to the selected target SMF to operate as the dedicated resource for the allowed network slice associated with the PDU session establishment request. 41

Embodiment A13. The method of Embodiment A12, wherein indicating to the selected target SMF comprises sending a Nsmf_PDUSession_CreateSMContext request comprising an indicator indicated to operate as the dedicated resource for the allowed network slice associated with the PDU session establishment request.

Embodiment A 14. The method of any one of Embodiments A1-A5, wherein the network node comprising a network slice selection function (NSSF).

Embodiment A15. The method of Embodiment A14, wherein indicating the identified network slice as the allowed network slice comprises, sending an indication of the identified network slice as the allowed network slice to a mobility management function (AMF) as a result of a request from the AMF for network slice selection information for the UE.

Embodiment Bl. A method implemented in a network node comprising a network function (NF), the method comprising: requesting to register a profile for the NF at a network repository function (NRF), the profile comprising an information element (IE) indicating one of that the NF is (i) available as a dedicated resource and (ii) is reserved as the dedicated resource.

Embodiment B2. The method of Embodiment B 1 , further comprising receiving an indication to operate as the dedicated resource for a network slice associated with a protocol data unit (PDU) session establishment request from a user equipment (UE).

Embodiment B3. The method of Embodiment B2, when the IE indicates that the NF is available as the dedicated resource and as a result of a PDU session being established for the UE in the network slice, determining to update the profile at the NRF to indicate that the NF is reserved as the dedicated resource for the network slice. 42

Embodiment B4. The method of any one of Embodiments B 1-B3, wherein the NF is a session management function (SMF).

Embodiment Cl. A method implemented in a network node, the method comprising: registering and/or updating a profile for a network function (NF) to comprise information indicating one of that the NF is (i) available as a dedicated resource and (ii) is reserved as the dedicated resource.

Embodiment C2. The method of Embodiment C 1 , wherein the information is an information element (IE) associated with the NF.

Embodiment C3. The method of any one of Embodiments Cl and C2, wherein the network node comprising a network slice selection function (NSSF).

Embodiment C4. The method of any one of Embodiments C1-C3, when the information indicates that the NF is available as the dedicated resource, determining to reserve the NF as the dedicated resource for an application server (AS) providing a roaming service and updating the profile for the NF to indicate that the NF is reserved as the dedicated resource for the AS.

Embodiment C5. The method of Embodiment C4, as a result of a discovery request identifying the AS, allocating the NF to the AS when the NF is available as the dedicated resource or the NF is currently reserved as the dedicated resource for the identified AS.

Embodiment Dl. A network node, the network node configured to, and/or comprising a radio interface and/or comprising processing circuitry configured to perform any one or more of the methods of Embodiments A1-A15. 43

Embodiment El. A network node, the network node configured to, and/or comprising a radio interface and/or comprising processing circuitry configured to perform any one or more of the methods of Embodiments B1-B4.

Embodiment FI. A network node, the network node configured to, and/or comprising a radio interface and/or comprising processing circuitry configured to perform any one or more of the methods of Embodiments C1-C4.

Embodiment Gl. A system comprising: a network node configured to operate according to any one or more of Embodiments A1-A15; a network node configured to operate according to any one or more of Embodiments B1-B4; and a network node configured to operate according to any one or more of Embodiments C1-C4.

As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, and/or computer program product. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

Some embodiments are described herein with reference to flowchart illustrations and/or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, 44 special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

It is to be understood that the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the 45 user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and/or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.